From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: completion-auto-help
Date: Thu, 10 Nov 2005 23:55:28 -0500 [thread overview]
Message-ID: <87lkzvpz2s.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <MEEKKIABFKKDFJMPIOEBIEGFCNAA.drew.adams@oracle.com> (Drew Adams's message of "Thu, 10 Nov 2005 17:30:56 -0800")
> The Elisp manual says this about it:
> If this variable is non-`nil', the completion commands
> automatically display a list of possible completions whenever
> nothing can be completed because the next character is not
> uniquely determined.
> In neither case are different non-nil values distinguished. So, I don't
> understand this code in complete.el:
> (if (or (eq completion-auto-help t)
> (and completion-auto-help
> (eq last-command this-command))
> (eq mode 'help))
complete.el extends the meaning of the variable so that a non-nil non-t
value means "show the help but only on the second attempt to complete".
I.e. if TAB finds nothing to complete, the first TAB will just say "[Next
char not unique]" without bringing up the *Completions* buffer, and the
second TAB will then bring up the *Completions* buffer.
It happens to be my favorite behavior.
> 2. New feature proposal - How about allowing for an
> "always-display-*Completions*' behavior:
> - t means what it means now
> - nil means what it means now
> - other means this:
We could have
t = what it means now
nil = what it means now
eager = what you suggest (always show the completions and update them
after each key stroke)
lazy = what complete.el does for non-nil non-t values
> IOW, with this value, the user would not need to hit `TAB' to display
> *Completions*. (S)he would see the list of completions whenever there are
> more than one. There is currently no way to make `completing-read',
> `read-file-name' etc. display *Completions* from the outset.
Indeed. The closest is icomplete-mode.
Stefan
next prev parent reply other threads:[~2005-11-11 4:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 1:30 completion-auto-help Drew Adams
2005-11-11 4:55 ` Stefan Monnier [this message]
2005-11-11 17:47 ` completion-auto-help Drew Adams
2005-11-11 18:39 ` completion-auto-help Drew Adams
2005-11-11 19:10 ` completion-auto-help Stefan Monnier
2005-11-11 19:32 ` completion-auto-help Drew Adams
2005-11-11 21:53 ` completion-auto-help Drew Adams
2005-11-11 22:43 ` completion-auto-help Drew Adams
2005-11-13 20:42 ` completion-auto-help Stefan Monnier
2005-11-13 21:06 ` completion-auto-help Drew Adams
2005-11-13 23:09 ` completion-auto-help Stefan Monnier
2005-11-13 23:40 ` completion-auto-help Drew Adams
2005-11-19 12:10 ` completion-auto-help Eli Zaretskii
2005-11-20 23:23 ` completion-auto-help Richard M. Stallman
2005-11-26 11:20 ` completion-auto-help Eli Zaretskii
2005-11-12 3:38 ` completion-auto-help Richard M. 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=87lkzvpz2s.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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).