From: Romain FRANCOISE <romain@orebokech.com>
Subject: Re: Status of shell-pcomplete integration?
Date: Tue, 03 Dec 2002 17:23:07 +0100 [thread overview]
Message-ID: <878yz7m5qs.fsf@orebokech.com> (raw)
In-Reply-To: <84u1hvt7y2.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Tue, 03 Dec 2002 16:53:41 +0100")
Kai Großjohann writes:
> What's the problem with the following?
> (require 'shell)
> (define-key shell-mode-map (kbd "TAB") 'pcomplete)
> (add-hook 'shell-mode-hook 'pcomplete-shell-setup)
> It seems to work. It does not defer loading of pcomplete until
> completion is actually used, but oh, well.
Provided you set pcomplete-cycle-completions to nil, it indeed seems to
work fine, with a few quirks:
- it doesn't complete filenames or directories containing spaces, even
if you escape them with backslashes. (With the completion cycling
turned on, it works)
- it doesn't complete environment variables, e.g.
$ cd $HOME/foo<TAB>
will not complete to
$ cd $HOME/foobar
but I think this is supposed to work with pcomplete, maybe John will
know how to fix it.
Romain.
--
Romain FRANCOISE <romain@orebokech.com> | They're nothing but scared
it's a miracle -- http://orebokech.com/ | little mice.
next prev parent reply other threads:[~2002-12-03 16:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-01 14:22 Status of shell-pcomplete integration? Romain FRANCOISE
2002-12-01 15:47 ` Kai Großjohann
2002-12-01 22:48 ` John Wiegley
2002-12-02 16:40 ` Kai Großjohann
2002-12-03 7:42 ` Kai Großjohann
2002-12-03 10:37 ` Romain FRANCOISE
2002-12-03 15:53 ` Kai Großjohann
2002-12-03 16:14 ` John Wiegley
2002-12-03 16:28 ` Romain FRANCOISE
2002-12-03 16:28 ` Stefan Monnier
2002-12-03 17:04 ` John Wiegley
2002-12-04 1:31 ` Miles Bader
2002-12-03 17:52 ` Kai Großjohann
2002-12-03 16:23 ` Romain FRANCOISE [this message]
2002-12-03 17:05 ` John Wiegley
2002-12-05 10:39 ` Kai Großjohann
2002-12-02 11:20 ` Mario Lang
2002-12-03 14:59 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878yz7m5qs.fsf@orebokech.com \
--to=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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).