From: A Soare <alinsoar@voila.fr>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: "Emacs Dev \[emacs-devel\]" <emacs-devel@gnu.org>
Subject: Re: partial-completion-mode in gdba
Date: Fri, 23 Mar 2007 11:32:29 +0100 (CET) [thread overview]
Message-ID: <16061940.603661174645949132.JavaMail.www@wwinf4203> (raw)
> A Soare writes:
> > > > 1. Emacs -Q
> > > >
> > > > 2. partial-completion-mode
> > > >
> > > > => partial-completion-mode on
> > > >
> > > > 3. gdba
> > > >
> > > > =>Run gdba (like this): gdb -annotate=3 /g/e/ <TAB>
> > > >
> > > > comint-dynamic-complete-as-filename: Opening directory: no such file or directory, /g/e/ [2 times]
> > >
> >
> > This is a bug.
>
> Why do you think it's a bug? Did it ever work for you? I doubt it. Partial
> completion mode seems to replace minibuffer-complete-* with PC-complete-* in
> the minibuffer keymaps but M-x gdba (and M-x gdb) uses read-from-minibuffer
> with the keymap gud-minibuffer-local-map. TAB is bound to
> comint-dynamic-complete-filename on this keymap which is why it doesn't work as
> you expect.
It reads a file name in fact, and because partial completion is on, when I press TAB after /g/e I expect to see /gnu/emacs, because in the root of my filesystem the only one directory that starts with 'g' is gnu, and the only dir. from /gnu is emacs et cetera.
I do not think that such a feature ever existed, so I think this is not a bug, just a missing feature.
Alin Soare.
next reply other threads:[~2007-03-23 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 10:32 A Soare [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-23 10:13 partial-completion-mode in gdba A Soare
2007-03-22 16:14 A Soare
2007-03-22 18:33 ` Stefan Monnier
2007-03-22 21:19 ` Nick Roberts
2007-03-21 13:00 A Soare
2007-03-21 12:03 A Soare
2007-03-21 12:49 ` Denis Bueno
2007-03-21 14:31 ` Stefan Monnier
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=16061940.603661174645949132.JavaMail.www@wwinf4203 \
--to=alinsoar@voila.fr \
--cc=emacs-devel@gnu.org \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.