Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Patch to limit field name completion candidates
Date: Fri, 06 Jun 2008 10:13:00 -0000	[thread overview]
Message-ID: <uhcc6c1ot.fsf@gnu.org> (raw)
In-Reply-To: <m34p87d2u8.fsf@fleche.redhat.com>

> From: Tom Tromey <tromey@redhat.com>
> Date: Thu, 05 Jun 2008 14:49:35 -0600
> 
> + @cindex completion of field names
> + @cindex field name completion
> + When completing in an expression which looks up a field in a
> + structure, @value{GDBN} also tries to limit completions to the field
> + names available in the type of the left-hand-side:
> + 
> + @smallexample
> + (@value{GDBP}) p gdb_stdout.@key{M-?}
> + magic      to_delete  to_fputs   to_put     to_rewind  
> + to_data    to_flush   to_isatty  to_read    to_write   
> + @end smallexample
> + 

  Otherwise, 

This is good.  I have three comments:

 . in the @cindex entries, I think it's better to use "structure
   fields" instead of just "fields", at least in one of them;

 . please use @kbd{M-?}, not @key (there's no key labeled literally
   with M-?);

 . not every GDB user knows by heart the definition of the ui_file
   structure, so I'd add the following passage right after your text:

 @noindent
 This is because the @code{gdb_stdout} is a variable of the type
 @code{struct ui_file} that is defined in @value{GDBN} sources as
 follows:

 @smallexample
 struct ui_file
 @{
    int *magic;
    ui_file_flush_ftype *to_flush;
    ui_file_write_ftype *to_write;
    ui_file_fputs_ftype *to_fputs;
    ui_file_read_ftype *to_read;
    ui_file_delete_ftype *to_delete;
    ui_file_isatty_ftype *to_isatty;
    ui_file_rewind_ftype *to_rewind;
    ui_file_put_ftype *to_put;
    void *to_data;
 @}
 @end smallexample


  reply	other threads:[~2008-06-06 10:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13 17:01 Tom Tromey
2008-05-13 18:11 ` Eli Zaretskii
2008-05-13 18:20   ` Tom Tromey
2008-05-13 18:32     ` Daniel Jacobowitz
2008-05-13 18:36       ` Tom Tromey
2008-05-13 21:00       ` Eli Zaretskii
2008-05-13 20:52     ` Eli Zaretskii
2008-06-05 17:10 ` Daniel Jacobowitz
2008-06-05 19:21   ` Tom Tromey
2008-06-05 19:30     ` Eli Zaretskii
2008-06-05 20:02       ` Tom Tromey
2008-06-06  9:47         ` Eli Zaretskii
2008-06-05 19:46     ` Daniel Jacobowitz
2008-06-05 20:03       ` Tom Tromey
2008-06-05 20:08         ` Daniel Jacobowitz
2008-06-06  0:49           ` Tom Tromey
2008-06-06  2:32             ` Daniel Jacobowitz
2008-06-06  2:41               ` Tom Tromey
2008-06-06 10:28                 ` Eli Zaretskii
2008-06-06 17:50                   ` Tom Tromey
2008-06-06 19:46                     ` Eli Zaretskii
2008-06-06 19:54                       ` Daniel Jacobowitz
2008-06-05 20:50       ` Tom Tromey
2008-06-06 10:13         ` Eli Zaretskii [this message]
2008-06-06 10:53           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uhcc6c1ot.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox