emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] /srv/bzr/emacs/trunk r109835: * lisp/minibuffer.el (comple


From: Stefan Monnier
Subject: [Emacs-diffs] /srv/bzr/emacs/trunk r109835: * lisp/minibuffer.el (completion-at-point-functions): Complete docstring.
Date: Sat, 01 Sep 2012 00:28:24 -0400
User-agent: Bazaar (2.5.0)

------------------------------------------------------------
revno: 109835
fixes bug: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12254
committer: Stefan Monnier <address@hidden>
branch nick: trunk
timestamp: Sat 2012-09-01 00:28:24 -0400
message:
  * lisp/minibuffer.el (completion-at-point-functions): Complete docstring.
modified:
  lisp/ChangeLog
  lisp/minibuffer.el
=== modified file 'lisp/ChangeLog'
--- a/lisp/ChangeLog    2012-09-01 01:04:26 +0000
+++ b/lisp/ChangeLog    2012-09-01 04:28:24 +0000
@@ -1,3 +1,8 @@
+2012-09-01  Stefan Monnier  <address@hidden>
+
+       * minibuffer.el (completion-at-point-functions): Complete docstring
+       (bug#12254).
+
 2012-09-01  Paul Eggert  <address@hidden>
 
        Better seed support for (random).

=== modified file 'lisp/minibuffer.el'
--- a/lisp/minibuffer.el        2012-08-14 17:10:38 +0000
+++ b/lisp/minibuffer.el        2012-09-01 04:28:24 +0000
@@ -1821,7 +1821,9 @@
  `: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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]