Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] More suggestive error_is_running message
Date: Wed, 11 Apr 2012 04:55:00 -0000	[thread overview]
Message-ID: <m3sjgb1098.fsf@redhat.com> (raw)
In-Reply-To: <20120411005611.GA10986@host2.jankratochvil.net> (Jan	Kratochvil's message of "Wed, 11 Apr 2012 02:56:11 +0200")

On Tuesday, April 10 2012, Jan Kratochvil wrote:

> On Tue, 10 Apr 2012 22:52:10 +0200, Sergio Durigan Junior wrote:
>> On Tuesday, April 10 2012, Jan Kratochvil wrote:
>> > +	   "and wait for '[Thread N] #1 stopped.'.)"));
>> 
>> Sorry for the nitpick: I guess we use `' (as in `interrupt'), and not ''.
>
> http://www.gnu.org/prep/standards/standards.html#Quote-Characters
> 	Although GNU programs traditionally used 0x60 (‘`’) for opening and
> 	0x27 (‘'’) for closing quotes, nowadays quotes ‘`like this'’ are
> 	typically rendered asymmetrically, so quoting ‘"like this"’ or ‘'like
> 	this'’ typically looks better. 
>
> I was surprised `this is no longer the standard'.

In such cases I never know if those new standards apply for new
projects, or for existing projects as well.  If they apply to existing
projects, then I'm not sure there should be any massive
replacement/adjustment in the codebase to reflect those new rules.

Anyway, I was surprised by this new rule as well.  Thanks for pointing
it out.

-- 
Sergio


  reply	other threads:[~2012-04-11  2:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 19:20 Jan Kratochvil
2012-04-10 21:30 ` Sergio Durigan Junior
2012-04-11  2:16   ` Jan Kratochvil
2012-04-11  4:55     ` Sergio Durigan Junior [this message]
2012-04-12 15:28       ` Tom Tromey
2012-04-11 15:35 ` Joel Brobecker
2012-04-11 15:48   ` [cancel] " Jan Kratochvil
2012-04-11 17:17     ` Joel Brobecker
2012-04-17 21:26       ` Jan Kratochvil
2012-04-17 23:01         ` Joel Brobecker

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=m3sjgb1098.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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