Re: [python][patch] Add GDB Parameters functionality

[Eli Zaretskii <eliz@gnu.org>]

> Date: Tue, 27 Apr 2010 20:24:55 +0100
> From: Phil Muldoon <pmuldoon@redhat.com>
> 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<tab>' will complete looking for
> filenames:
> 
> Eg:
> 
> (gdb) set logging file ~/log<TAB>
> 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<TAB>
> 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.