(partial-completion-mode): Mention completion-auto-help in the doc string.

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index dd264bca5a6d126113b0bfeb1e8b5bb66f609dbf..de11de64de4e38e4570bd271c252534af4b1ca62 100644 (file)
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,5 +1,8 @@
 2005-11-19  Eli Zaretskii  <eliz@gnu.org>
 
+       * complete.el (partial-completion-mode): Mention
+       completion-auto-help in the doc string.
+
        * man.el (Man-highlight-references): Doc fix.  Reformat code in a
        more Lisp-ish way.
 

diff --git a/lisp/complete.el b/lisp/complete.el
index d3ff6c53988bf0902eec5626055a50c369339991..4a2ce48f152c69ce506da836c18e8d4a58f2c391 100644 (file)
--- a/lisp/complete.el
+++ b/lisp/complete.el
@@ -203,7 +203,14 @@ other file in that directory begin with that sequence of characters.
 Unless `PC-disable-includes' is non-nil, the `<...>' sequence is interpreted
 specially in \\[find-file].  For example,
 \\[find-file] <sys/time.h> RET finds the file `/usr/include/sys/time.h'.
-See also the variable `PC-include-file-path'."
+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."
   :global t :group 'partial-completion
   ;; Deal with key bindings...
   (PC-bindings partial-completion-mode)