From: John Wiegley <johnw@gnu.org>
Subject: Re: [friedman@splode.com: some other observations on pcomplete]
Date: Wed, 13 Mar 2002 16:00:44 -0700 [thread overview]
Message-ID: <8766402hur.fsf@alice.dynodns.net> (raw)
In-Reply-To: <vaf3cz4y766.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Wed, 13 Mar 2002 13:38:09 +0100")
>>>>> On Wed Mar 13, Kai writes:
>> Could someone tell me what [pcomplete's features] are?
> I'm not an expert on this, but two things at least come to my mind:
> * pcomplete can offer context-sensitive completion...
> * After hitting TAB to pop up a *Completions* buffer, typing makes
> the buffer (window, actually) go away.
Here are a few others:
* It has several modes of prompting you with possible completions. It
can show you the list on first TAB, second TAB, or it can cycle.
* It can optionally expand the arguments that it completes, when
variable references are involved. Thus, calling pcomplete-expand on
$HOME/.zsh<TAB> will yield /home/johnw/.zshrc. This is not used by
default.
* It offers context-sensitive help, as well as completion lists. Try
calling `M-x pcomplete-help' when you are at "cvs add ". It will
pop up the info page for adding files to cvs.
* It will optionally pare members of completion lists, if that
argument has already been seen. For example, if I type "ls .zshrc
.zsh<TAB>", then .zshrc will not be in the second argument's
completion list.
* Last but not least, writing new context-sensitive completion
functions is EASY. Granted, the process needs documentation, but
basically you just call `pcomplete-here' and pass it a list, which
will set the completion list for that argument position. Take a
look at pcomplete/tar.
John
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-13 23:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 21:32 [friedman@splode.com: some other observations on pcomplete] Richard Stallman
2002-03-11 6:29 ` John Wiegley
2002-03-11 6:48 ` Miles Bader
2002-03-11 7:53 ` John Wiegley
2002-03-11 14:43 ` Stefan Monnier
2002-03-11 19:06 ` Richard Stallman
2002-03-11 19:35 ` John Wiegley
2002-03-12 10:01 ` Kai Großjohann
2002-03-12 19:44 ` John Wiegley
2002-03-13 10:58 ` Richard Stallman
2002-03-13 18:09 ` Colin Walters
2002-03-14 12:42 ` Richard Stallman
2002-03-14 19:29 ` John Wiegley
2002-03-11 23:58 ` Miles Bader
2002-03-11 20:46 ` Colin Walters
2002-03-12 18:12 ` Stefan Monnier
2002-03-12 18:13 ` Noah Friedman
2002-03-13 10:58 ` Richard Stallman
2002-03-13 12:38 ` Kai Großjohann
2002-03-13 23:00 ` John Wiegley [this message]
2002-03-15 3:42 ` Richard Stallman
2002-03-17 9:51 ` Kai Großjohann
2002-03-17 19:22 ` Richard Stallman
2002-03-19 16:15 ` Kai Großjohann
[not found] <Pine.SUN.3.91.1020314163415.20226A@is>
2002-03-15 16:24 ` Richard Stallman
2002-03-15 19:42 ` Jason Rumney
2002-03-17 10:05 ` Richard Stallman
2002-03-17 11:47 ` Eli Zaretskii
2002-03-18 9:05 ` Richard Stallman
2002-03-17 9:17 ` Karl Eichwalder
2002-03-17 19:22 ` 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=8766402hur.fsf@alice.dynodns.net \
--to=johnw@gnu.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.
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).