[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
what is minibuffer-completion-confirm's purpose?
From: |
Chris Green |
Subject: |
what is minibuffer-completion-confirm's purpose? |
Date: |
Thu, 20 May 2004 15:06:42 -0400 |
User-agent: |
Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux) |
In XEmacs, I can set minibuffer-confirm-incomplete and that will
prevent me from accepting a minibuffer completion that doesn't already
exist without confirmation.
For example, C-x b *Unknown* will prompt saying [no completions,
confirm] if the buffer *Unknown* doesn't already exist or C-x f
.bashtc will also say [no completions, confirm].'
In Emacs 21.3.1 and current CVS,
minibuffer-completion-confirm seems to provide that same kind of
functionality by it's docstring. However, setting it to t doesn't
give me the desired behavior combined with emacs -q. Is there another
minibuffer customization I can perform to get the promping on unknown
behavior?
Thanks,
--
Chris Green <cmg@dok.org>
"Not everyone holds these truths to be self-evident, so we've worked
up a proof of them as Appendix A." -- Paul Prescod
- what is minibuffer-completion-confirm's purpose?,
Chris Green <=