From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23033 invoked by alias); 14 Jan 2002 08:22:14 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 23001 invoked from network); 14 Jan 2002 08:22:12 -0000 Received: from unknown (HELO is.elta.co.il) (199.203.121.2) by sources.redhat.com with SMTP; 14 Jan 2002 08:22:12 -0000 Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id KAA14323; Mon, 14 Jan 2002 10:21:25 +0200 (IST) Date: Mon, 14 Jan 2002 00:22:00 -0000 From: Eli Zaretskii X-Sender: eliz@is To: Andrew Cagney cc: gdb@sources.redhat.com Subject: Re: how to format an error? In-Reply-To: <3C426042.8050807@cygnus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-01/txt/msg00144.txt.bz2 On Sun, 13 Jan 2002, Andrew Cagney wrote: > Given the attached, which is the correct way of formatting an error message: > > This is an error message. > this is an error message. > This is an error message > this is an error message I suggest the last variant. It goes with the GNU coding standards except for the capitalization. But capitalization is language-specific (e.g., in German, all nouns are capitalized), and it was recently discovered in Emacs development that a 100% adherence to the capitalization rule you cited produces wrong results in some cases. Most of the messages don't need caps, so I think losing that is the best alternative which is simple enough to adher to.