From: Fernando Nasser <fnasser@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Improve completion of locations
Date: Tue, 05 Jun 2001 06:10:00 -0000 [thread overview]
Message-ID: <3B1CD993.5FD04FAE@redhat.com> (raw)
In-Reply-To: <200106050617.JAA27884@is.elta.co.il>
Eli Zaretskii wrote:
>
> > Date: Sat, 05 May 2001 21:00:08 +0300
> > From: "Eli Zaretskii" <eliz@is.elta.co.il>
> >
> > I'm seeking approval for the patches below, which improve GDB's
> > completion of locations in commands like "break LOCATION". The two
> > main improvements are:
> >
> > - GDB now considers file names as well as symbol names when you
> > type, e.g., "break foo". If there's a symbol foo_bar and a file
> > foo-bar.c, both will be shown in the list of possible completions.
> > Only files recorded in the debug info are used for completing file
> > names for these commands.
> >
> > - When the user types "break foo.c:bar TAB", only symbols defined in
> > the source file foo.c whose names begin with "bar" will be
> > considered for completion. This reduces the number of possible
> > completions by a large factor in many typical situations (I'd even
> > dare to say that it makes symbol completion a useful feature ;-).
> >
> > This is the last installment of my recent completion-related frenzy.
> > I'm now quite happy with GDB's completion ;-)
> >
> > AFAICS, the responsible maintainers who need to approve these patches
> > are Fernando, Elena, Michael Snyder, and someone for printcmd.c and
> > infcmd.c.
> >
> > 2001-05-05 Eli Zaretskii <eliz@is.elta.co.il>
> >
> > * completer.c (gdb_completer_loc_break_characters): New variable.
> > (line_completion_function): If we are completing on locations,
> > back up the start of word pointer past all characters which can
> > appear in a location spec.
> > (location_completer): New function.
> >
> > * completer.h: Add prototype for location_completer.
>
> It's been a month since I asked for approval of these patches, but the
> changes for completer.[ch] are still not approved nor rejected.
>
> Let me know how can I help you review these changes.
>
> TIA
Sorry Eli. I have a deadline at work and I could not review your patch
yet. I will try to do it by Friday or, if not possible, during the
weekend.
Thanks for your patience.
Regards,
Fernando
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2001-06-05 6:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 10:59 Eli Zaretskii
2001-05-05 11:26 ` Daniel Berlin
2001-05-05 23:15 ` Eli Zaretskii
2001-05-06 0:10 ` Daniel Berlin
2001-05-06 2:05 ` Eli Zaretskii
2001-05-06 9:38 ` Daniel Berlin
2001-05-06 10:04 ` Eli Zaretskii
2001-05-06 3:19 ` Eli Zaretskii
2001-05-08 13:32 ` Elena Zannoni
2001-05-09 3:46 ` Eli Zaretskii
2001-05-11 21:17 ` Elena Zannoni
2001-05-11 23:03 ` Eli Zaretskii
2001-05-14 13:39 ` Elena Zannoni
2001-05-25 1:39 ` Eli Zaretskii
2001-06-04 23:15 ` Eli Zaretskii
2001-06-05 6:10 ` Fernando Nasser [this message]
2001-06-05 10:58 ` Eli Zaretskii
2001-06-10 8:46 ` Fernando Nasser
2001-06-10 9:14 ` Daniel Berlin
2001-06-10 9:43 ` Fernando Nasser
2001-06-11 9:09 ` 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=3B1CD993.5FD04FAE@redhat.com \
--to=fnasser@redhat.com \
--cc=eliz@is.elta.co.il \
--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