From: Stefan Monnier Date: Sat, 1 Sep 2012 04:28:24 +0000 (-0400) Subject: * lisp/minibuffer.el (completion-at-point-functions): Complete docstring. X-Git-Tag: emacs-24.2.90~455 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=3d10e1343d65341d4d48633e0b561df86787c438;p=emacs.git * lisp/minibuffer.el (completion-at-point-functions): Complete docstring. Fixes: debbugs:12254 --- diff --git a/lisp/ChangeLog b/lisp/ChangeLog index 68bb8e06e87..c5b866e9d54 100644 --- a/lisp/ChangeLog +++ b/lisp/ChangeLog @@ -1,3 +1,8 @@ +2012-09-01 Stefan Monnier + + * minibuffer.el (completion-at-point-functions): Complete docstring + (bug#12254). + 2012-09-01 Paul Eggert Better seed support for (random). diff --git a/lisp/minibuffer.el b/lisp/minibuffer.el index cc2638d58de..a696fff7dc7 100644 --- 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.