From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Patch to limit field name completion candidates
Date: Thu, 05 Jun 2008 20:50:00 -0000 [thread overview]
Message-ID: <m34p87d2u8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080605194553.GG25085@caradoc.them.org> (Daniel Jacobowitz's message of "Thu\, 5 Jun 2008 15\:45\:53 -0400")
Daniel> The patch and test are OK! Work out the NEWS and manual bits with
Daniel> Eli, and you're home free.
The NEWS part is pending.
Eli, how does this look for the manual?
Tom
2008-06-05 Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Completion): Add field name example.
*** gdb.texinfo 10 May 2008 09:06:02 -0600 1.495
--- gdb.texinfo 05 Jun 2008 14:40:33 -0600
***************
*** 1,6 ****
\input texinfo @c -*-texinfo-*-
@c Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1998,
! @c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006
@c Free Software Foundation, Inc.
@c
@c %**start of header
--- 1,6 ----
\input texinfo @c -*-texinfo-*-
@c Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1998,
! @c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2008
@c Free Software Foundation, Inc.
@c
@c %**start of header
***************
*** 1521,1526 ****
--- 1521,1538 ----
overload-resolution off} to disable overload resolution;
see @ref{Debugging C Plus Plus, ,@value{GDBN} Features for C@t{++}}.
+ @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
+
@node Help
@section Getting Help
next prev parent reply other threads:[~2008-06-05 20:50 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 [this message]
2008-06-06 10:13 ` Eli Zaretskii
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=m34p87d2u8.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sources.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