public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/16265] New: difference between TAB completion and "complete" command
Date: Wed, 27 Nov 2013 16:27:00 -0000	[thread overview]
Message-ID: <bug-16265-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=16265

            Bug ID: 16265
           Summary: difference between TAB completion and "complete"
                    command
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: cli
          Assignee: unassigned at sourceware dot org
          Reporter: tromey at redhat dot com

Make a unique directory, e.g.:

mkdir /tmp/zzzzzzzzzzzz

Now in gdb:

(gdb) cd /tmp/zz<TAB>

I see:

(gdb) cd /tmp/zzzzzzzzzzzz/

Note the trailing "/".

Now try the complete command:

(gdb) complete cd /tmp/zz
cd /tmp/zzzzzzzzzzzz

Note the lack of the trailing "/".

This difference makes completion in Emacs harder to use.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2013-11-27 16:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 16:27 tromey at redhat dot com [this message]
2014-02-20 10:13 ` [Bug cli/16265] " gbenson at redhat dot com
2014-02-26  2:48 ` sergiodj at redhat dot com
2014-04-25  9:01 ` manu at gcc dot gnu.org
2024-01-12 11:04 ` cvs-commit at gcc dot gnu.org
2024-01-12 11:05 ` aburgess at redhat dot com

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=bug-16265-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).