From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16751 invoked by alias); 19 Jan 2007 11:37:01 -0000 Received: (qmail 16739 invoked by uid 22791); 19 Jan 2007 11:37:00 -0000 X-Spam-Check-By: sourceware.org Received: from romy.inter.net.il (HELO romy.inter.net.il) (213.8.233.24) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 19 Jan 2007 11:36:55 +0000 Received: from HOME-C4E4A596F7 (IGLD-84-229-116-189.inter.net.il [84.229.116.189]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id GWZ07361 (AUTH halo1); Fri, 19 Jan 2007 13:36:51 +0200 (IST) Date: Fri, 19 Jan 2007 11:37:00 -0000 Message-Id: From: Eli Zaretskii To: gdb@sources.redhat.com Subject: Special characters in doc strings of GDB commands Reply-to: Eli Zaretskii 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-01/txt/msg00286.txt.bz2 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? 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.