* lisp/minibuffer.el (completion-at-point-functions): Complete docstring.

Fixes: debbugs:12254

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index 68bb8e06e8760988ab4da4a72a9774208bed29f9..c5b866e9d544d4c7d81a039133df56f44c891ae3 100644 (file)
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,8 @@
+2012-09-01  Stefan Monnier  <monnier@iro.umontreal.ca>
+
+       * minibuffer.el (completion-at-point-functions): Complete docstring
+       (bug#12254).
+
 2012-09-01  Paul Eggert  <eggert@cs.ucla.edu>
 
        Better seed support for (random).

diff --git a/lisp/minibuffer.el b/lisp/minibuffer.el
index cc2638d58de435eb6f445b9aa48544364052d314..a696fff7dc7d540b8f3fc900311a0e5792174533 100644 (file)
--- a/lisp/minibuffer.el
+++ b/lisp/minibuffer.el
@@ -1821,7 +1821,9 @@ Currently supported properties are all the properties that can appear in
  `:predicate'  a predicate that completion candidates need to satisfy.
  `:exclusive'  If `no', means that if the completion table fails to
    match the text at point, then instead of reporting a completion
-   failure, the completion should try the next completion function.")
+   failure, the completion should try the next completion function.
+As is the case with most hooks, the functions are responsible to preserve
+things like point and current buffer.")
 
 (defvar completion--capf-misbehave-funs nil
   "List of functions found on `completion-at-point-functions' that misbehave.