From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22308 invoked by alias); 27 Apr 2010 19:36:52 -0000 Received: (qmail 22300 invoked by uid 22791); 27 Apr 2010 19:36:52 -0000 X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout23.012.net.il (HELO mtaout23.012.net.il) (80.179.55.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 27 Apr 2010 19:36:47 +0000 Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0L1J00D00VHK8U00@a-mtaout23.012.net.il> for gdb-patches@sourceware.org; Tue, 27 Apr 2010 22:36:22 +0300 (IDT) Received: from HOME-C4E4A596F7 ([77.127.125.239]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0L1J009SBVSIGLC0@a-mtaout23.012.net.il>; Tue, 27 Apr 2010 22:36:19 +0300 (IDT) Date: Tue, 27 Apr 2010 19:36:00 -0000 From: Eli Zaretskii Subject: Re: [python][patch] Add GDB Parameters functionality In-reply-to: <4BD73A07.7020706@redhat.com> To: Phil Muldoon Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83r5m0y9fp.fsf@gnu.org> References: <4BD592D9.1070801@redhat.com> <838w8ayu7a.fsf@gnu.org> <4BD6D7C7.9040804@redhat.com> <83wrvsyelz.fsf@gnu.org> <4BD73A07.7020706@redhat.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-04/txt/msg00920.txt.bz2 > Date: Tue, 27 Apr 2010 20:24:55 +0100 > From: Phil Muldoon > CC: gdb-patches@sourceware.org > > On 04/27/2010 06:44 PM, Eli Zaretskii wrote: > > >> +@item PARAM_STRING > >> +The value is a string. When the user modifies the string, any escapes > >> +sequences are translated and encoded by @value{GDBN}. > > > > I asked to say something about this translation, or provide an > > example. > > I'm just not sure what to say other than GDB will translate and encode > any escape sequences in the string. In fact, 'encoded' will probably > just do here without the 'translated' verb - it seems redundant with > the new encoded text. I think that is clearer. How about that with a > cross-reference to encoding (pxref{Character Sets})? Can you give me a couple of examples of this "translation"? Then I could suggest some simple explanation. > The classification of Parameter type in these cases is purely > to do with how completion works -- if the user chooses to use > completion. So 'set foo somefil' will complete looking for > filenames: > > Eg: > > (gdb) set logging file ~/log > log.txt log2.txt > > Whereas for a Parameter with the type PARAM_BOOLEAN (like set verbose) > it would complete like so: > > (gdb) set verbose o > off on > > Now that being said, I'm a little stumped how to explain all of this > within the context of these parameter types. Do you have any input > here? How about The value is a filename. This is just like @code{PARAM_STRING}, but uses file names for completion.