Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: completion regression?
Date: Tue, 10 Oct 2006 22:05:00 -0000	[thread overview]
Message-ID: <17708.6256.497894.641872@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20061008220814.GA23132@nevyn.them.org>

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

Actually, looking more carefully, I see now that Emacs causes most of the
problem.

 > And obviously I've forgotten the details, since I just pulled up gdb
 > and typed "file /bin<tab>" and got a slash.

I don't think there is a regression now.  The only (tiny) problem appears
completing on a sub-directory for the first time:

cd src/gd<TAB> gives "cd src/gdb "

and that exists in earlier versions.

In fact I see that completion has _improved_ and the "complete" command now
completes on filenames e.g from src/gdb directory:

(gdb) cd test<TAB><TAB>
testrun.log  testrun.sum  testsuite/

Formerly

(gdb) complete cd test
(gdb)

Currently:

(top-gdb) complete cd test
cd testrun.log
cd testrun.sum
cd testsuite
(gdb)

Could the "complete" command also add trailing slashes as with completion
from the command line? i.e

(top-gdb) complete cd test
cd testrun.log
cd testrun.sum
cd testsuite/
(gdb)


-- 
Nick                                           http://www.inet.net.nz/~nickrob


      parent reply	other threads:[~2006-10-10 22:05 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
2006-10-08 23:00   ` Nick Roberts
2006-10-10 22:05   ` Nick Roberts [this message]

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=17708.6256.497894.641872@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --cc=gdb@sources.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