Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Use double quotes in some gdb output
Date: Fri, 05 Jun 2026 15:06:20 -0600	[thread overview]
Message-ID: <8733z0hf3n.fsf@tromey.com> (raw)
In-Reply-To: <20260508142221.3434435-1-tromey@adacore.com> (Tom Tromey's message of "Fri, 8 May 2026 08:22:21 -0600")

>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:

Tom> I looked for spots where gdb was using `...' or ``...'' quoting, and
Tom> changed these to use double quotes instead.

Tom> I think it might be good to regularize output quoting in gdb.  My
Tom> proposal is to use double quotes, though single quotes would also be
Tom> fine.  Using `...', though, is a kind of older style and has fallen
Tom> out of favor in GNU; the relevant node is here:

Tom>     https://www.gnu.org/prep/standards/html_node/Quote-Characters.html

I'm going to check this in now.

I may also look at changing '...' to "..." in the output; that is,
standardize on double quotes.

Tom

      reply	other threads:[~2026-06-05 21:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 14:22 Tom Tromey
2026-06-05 21:06 ` Tom Tromey [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8733z0hf3n.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox