From: John Wiegley <johnw@gnu.org>
Subject: Re: [friedman@splode.com: some other observations on pcomplete]
Date: Tue, 12 Mar 2002 12:44:21 -0700 [thread overview]
Message-ID: <87sn75o9ka.fsf@alice.dynodns.net> (raw)
In-Reply-To: <vafy9gynlzz.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 12 Mar 2002 11:01:04 +0100")
>>>>> On Tue Mar 12, Kai writes:
> Maybe it would also be a good idea to configure pcomplete in the
> same way everywhere (by default), to get uniform behavior.
This is not a bad idea. Although, with the minibuffer prompting
recommended earlier, would that be enough to allow cycling to be the
default? Cycling is so much easier to use once you get used to it.
> Also, I gather that with pcomplete it's possible to complete on
> command arguments, as well. That's tres cool. The old completion
> doesn't offer that.
Yes, pcomplete search for a plain Lisp function, pcomplete/NAME, for
every command. This function's responsibility is to return a list of
possible completions for the current argument index (with full access
to all previous arguments, and the text before point). If more people
start using pcomplete, I would hope to see more customized completion
written for Emacs. Already it is very smart with regard to GNU make,
tar and cvs.
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-12 19:44 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 [this message]
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
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=87sn75o9ka.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).