From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31868 invoked by alias); 4 Jan 2002 23:23:01 -0000 Mailing-List: contact insight-prs-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-prs-owner@sources.redhat.com Received: (qmail 31844 invoked by uid 71); 4 Jan 2002 23:23:01 -0000 Date: Fri, 04 Jan 2002 15:23:00 -0000 Message-ID: <20020104232301.31843.qmail@sources.redhat.com> To: kseitz@sources.redhat.com Cc: insight-prs@sourceware.cygnus.com, From: Tom Tromey Subject: Re: insight/107: completion behaves strangely Reply-To: Tom Tromey X-SW-Source: 2002-q1/txt/msg00050.txt.bz2 List-Id: The following reply was made to PR insight/107; it has been noted by GNATS. From: Tom Tromey To: kseitz@sources.redhat.com Cc: insight-gnats@sources.redhat.com 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? Nope. 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 ...]' somewhere. Tom