From: Keith Seitz <keiths@cygnus.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Insight List <insight@sourceware.cygnus.com>
Subject: Re: completion oddity
Date: Thu, 16 Aug 2001 14:21:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0108161419560.10383-100000@makita.cygnus.com> (raw)
In-Reply-To: <87itfndgb0.fsf@creche.redhat.com>
On 16 Aug 2001, Tom Tromey wrote:
> I built the latest Insight from the CVS trunk a couple days ago.
> I ran it on `jc1' (the Java compiler for GCC).
>
> In the console I type `b java_decode_<TAB>'.
> It completes this to `java_decode_option', but then beeps.
> If I hit TAB again, I see this:
>
> Completions:
> java_decode_option java_decode_option java_decode_option java_decode_option java_decode_option
I've spent the last hour or so looking at this... It's a lot more serious
than it appears. As you'd guess, these are bugs in gdb's completer. I've
submitted two bugs into gnats about the problems.
Sorry.
Keith
next prev parent reply other threads:[~2001-08-16 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 10:41 Tom Tromey
2001-08-16 11:15 ` Keith Seitz
2001-08-16 14:21 ` Keith Seitz [this message]
2001-08-16 14:59 ` Tom Tromey
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=Pine.GSO.4.33.0108161419560.10383-100000@makita.cygnus.com \
--to=keiths@cygnus.com \
--cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).