public inbox for
help / color / mirror / Atom feed
From: Tom Tromey <>
Subject: Re: insight/107: completion behaves strangely
Date: Fri, 04 Jan 2002 15:23:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR insight/107; it has been noted by GNATS.

From: Tom Tromey <>
Subject: Re: insight/107: completion behaves strangely
Date: 04 Jan 2002 16:33:31 -0700

 >>>>> "Keith" == kseitz  <> writes:
 Keith>     We use gdb's "complete" command. If you run command-line
 Keith>     gdb and enter "complete b captured_ma", you'll see that it
 Keith>     returns the huge, repetitive list that you're seeing.
 Keith>     Have you submitted a PR against gdb?
 I'll do that at some point.
 readline handles the uniquifying for the CLI.
 For insight a workaround would be as simple as adding `[lrmdups ...]'

             reply	other threads:[~2002-01-04 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04 15:23 Tom Tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-04 13:10 kseitz

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:

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

  git send-email \ \ \ \ \

* 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).