From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15183 invoked by alias); 24 Sep 2003 23:25:07 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 15176 invoked from network); 24 Sep 2003 23:25:06 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sources.redhat.com with SMTP; 24 Sep 2003 23:25:06 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id DFF9CD2DAF; Wed, 24 Sep 2003 16:25:04 -0700 (PDT) Date: Wed, 24 Sep 2003 23:25:00 -0000 From: Joel Brobecker To: Jim Ingham Cc: gdb-patches@sources.redhat.com Subject: Re: complete command doesn't work for files... Message-ID: <20030924232504.GL1020@gnat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-SW-Source: 2003-09/txt/msg00544.txt.bz2 Jim, I don't have any authority on the patch itself, but I do think that it would be really worth to directly insert inside the code the text of your changelog entry. I find it easier to find the relevant information when it's inside the code, as opposed to inside the ChangeLog. > * completer.c (complete_line): For filename completions, when you > look for > the last word before the cursor, actually start from the cursor & > work backwards, > rather than starting from the word you were handed. Starting > from the > word doesn't work if the input contains more than one word - as > it does > in the complete command. -- Joel