Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Richard.Earnshaw@arm.com
Cc: Andrew Cagney <ac131313@cygnus.com>,
	gdb@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: how to format an error?
Date: Mon, 14 Jan 2002 03:08:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1020114130329.15686A-100000@is> (raw)
In-Reply-To: <200201141037.KAA23594@cam-mail2.cambridge.arm.com>


On Mon, 14 Jan 2002, Richard Earnshaw wrote:

> Hmm, I'd go for the third.  If the message were to appear in a GUI box, it 
> could well be a line of text on its own, such as
> 
>          ************* ERROR **************
>          *                                *
>          *    This is an error message    *
>          *                                *
>          **********************************
> 
> In such a context I think it would be very wrong to start this with a 
> lower-case letter.

It usually comes with something before it, like in

         foobar: this is an error message

So I think the problem that bothers you mostly doesn't exist.

> Given that, (and that a litteral will never appear in the first letter) 
> can we safely assume that we can capitalize the first letter during 
> printing?

No.  That's exactly what we discovered in Emacs: you cannot assume 
anything about proper capitalization, unless you are certain the message 
will always be in US English.  Any assumption you make will break in too 
many cases.


  reply	other threads:[~2002-01-14 11:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 20:36 Andrew Cagney
2002-01-14  0:22 ` Eli Zaretskii
2002-01-14  2:37   ` Richard Earnshaw
2002-01-14  3:08     ` Eli Zaretskii [this message]
2002-02-02  8:09   ` Andrew Cagney
2002-02-02  9:27     ` Eli Zaretskii
2002-02-03 19:22       ` Andrew Cagney

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=Pine.SUN.3.91.1020114130329.15686A-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=Richard.Earnshaw@arm.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.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