From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11583 invoked by alias); 10 Feb 2007 20:47:37 -0000 Received: (qmail 11574 invoked by uid 22791); 10 Feb 2007 20:47:36 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Sat, 10 Feb 2007 20:47:32 +0000 Received: from drow by nevyn.them.org with local (Exim 4.63) (envelope-from ) id 1HFz85-0007hk-Um; Sat, 10 Feb 2007 15:47:30 -0500 Date: Sat, 10 Feb 2007 20:47:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: gdb@sources.redhat.com Subject: Re: Special characters in doc strings of GDB commands Message-ID: <20070210204729.GA29601@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , gdb@sources.redhat.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-02/txt/msg00070.txt.bz2 On Fri, Jan 19, 2007 at 01:36:56PM +0200, Eli Zaretskii wrote: > I see in cli-decode.c:print_doc_line that it displays the first line > only up to the first comma or period. However, I don't see this > special treatment of these two characters documented anywhere, neither > in gdb.texinfo (where it matters for doc strings given to user-defined > commands), nor in gdbint.texinfo (where it is important for GDB > developers who add new commands). > > Am I missing something? Not as far as I know. > Btw, should we have a mechanism to escape these special characters, at > least the comma? Sometimes a sentence looks very awkward or even > unclear unless you use a comma. Isn't this whole mechanism horribly i18n-unfriendly already? Perhaps we should just change it... -- Daniel Jacobowitz CodeSourcery