summaryrefslogtreecommitdiff
path: root/lisp/complete.el
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>2005-12-16 02:06:11 +0000
committerRichard M. Stallman <rms@gnu.org>2005-12-16 02:06:11 +0000
commit6c76000bb362bec90b11517846bab6ec92512085 (patch)
tree1ee9ee27409536a3519d4c6411946532f6ff5cd7 /lisp/complete.el
parent324d09a608b38bf46b1aedea3e29d0c717d86dfe (diff)
downloademacs-6c76000bb362bec90b11517846bab6ec92512085.tar.gz
(partial-completion-mode): Doc fix.
Diffstat (limited to 'lisp/complete.el')
-rw-r--r--lisp/complete.el9
1 files changed, 4 insertions, 5 deletions
diff --git a/lisp/complete.el b/lisp/complete.el
index f5ab178e1b3..7de670f793c 100644
--- a/lisp/complete.el
+++ b/lisp/complete.el
@@ -206,11 +206,10 @@ specially in \\[find-file]. For example,
See also the variable `PC-include-file-path'.
Partial Completion mode extends the meaning of `completion-auto-help' (which
-see) so that if it is neither nil nor t, Emacs will show the *Completions*
-buffer 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."
+see), so that if it is neither nil nor t, Emacs shows the `*Completions*'
+buffer only on the second attempt to complete. That is, if TAB finds nothing
+to complete, the first TAB just says \"Next char not unique\" and the
+second TAB brings up the `*Completionsf'* buffer."
:global t :group 'partial-completion
;; Deal with key bindings...
(PC-bindings partial-completion-mode)