From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sources.redhat.com
Subject: Re: completion regression?
Date: Sun, 08 Oct 2006 22:08:00 -0000 [thread overview]
Message-ID: <20061008220814.GA23132@nevyn.them.org> (raw)
In-Reply-To: <17705.28835.758720.533078@kahikatea.snap.net.nz>
On Mon, Oct 09, 2006 at 10:41:55AM +1300, Nick Roberts wrote:
>
> Completion doesn't seem to work as well as it used to, e.g in version 5.2. The
> manual doesn't differentiate but AFAICS there are three types: command,
> filename and location. Successful completion now always leaves a trailing
> space but its only really needed for commands (so following words can then be
> typed). It's not needed for locations and is a nuisance for filenames because
> using it on a filename requires the space to be deleted after successfully
> completing on each component/directory. It used to add a slash instead, which
> is much more useful.
Are you sure this isn't just happening for the very first time you do
it? This is a known bug, and I got a new hook added to readline5 that
would let us fix it, but never had time to get back to it. If it
worked before, I don't remember what changed that required the new
hook.
And obviously I've forgotten the details, since I just pulled up gdb
and typed "file /bin<tab>" and got a slash.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-08 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-08 21:44 Nick Roberts
2006-10-08 22:08 ` Daniel Jacobowitz [this message]
2006-10-08 23:00 ` Nick Roberts
2006-10-10 22:05 ` Nick Roberts
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=20061008220814.GA23132@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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