From: Glenn Morris <rgm@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Romain Francoise <romain@orebokech.com>, 9554@debbugs.gnu.org
Subject: bug#9554: 24.0.50; shell-mode completion broken
Date: Fri, 30 Sep 2011 22:45:29 -0400 [thread overview]
Message-ID: <qwmxdl8m5y.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <8762kh85fb.fsf@gmx.de> (Michael Albinus's message of "Sun, 25 Sep 2011 09:08:56 +0200")
>>> 1) Create two files with `touch foo bar'. Then type `rm foo b' and try
>>> to complete 'bar'.
>>
>> That was reported a few weeks ago by Kenichi Handa, and I happen to fix
>> it just a few minutes ago.
>>
>>> 2) Try to scp a local file (e.g. `scp /<TAB>'). pcomplete insists on
>>> completing host names, not file names.
This is http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9377
> 3) Open a buffer dedicated to a remote host, for example "C-x f
> /scp:host:". Start `shell', it runs on the remote host. Goto a
> directory which does exist on the remote host, but not on the local
> one, for example "cd /sh <TAB>". It does not expand to "/share" as
> expected, instead it tries to complete the filename on the local host.
This is http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9616
Since it is better to have bug reports that focus on individual issues,
and since each issue in this report is the subject of another report, I
don't think this report needs to stay open. (The general issue of
"should shell use pcomplete by default" seems more like an emacs-devel
topic.)
next prev parent reply other threads:[~2011-10-01 2:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 21:30 bug#9554: 24.0.50; shell-mode completion broken Romain Francoise
2011-09-19 21:46 ` Glenn Morris
2011-09-20 1:44 ` Stefan Monnier
2011-09-20 5:56 ` Romain Francoise
2011-09-25 7:08 ` Michael Albinus
2011-10-01 2:45 ` Glenn Morris [this message]
[not found] ` <jwvk48mnhoo.fsf-monnier+emacs@gnu.org>
2011-10-03 17:26 ` bug#9377: " 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=qwmxdl8m5y.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=9554@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=romain@orebokech.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.
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.