summaryrefslogtreecommitdiff
path: root/lisp/minibuffer.el
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2018-04-01 12:19:49 +0300
committerEli Zaretskii <eliz@gnu.org>2018-04-01 12:22:39 +0300
commit9fee1b8fb3395bde2d2e28e46c6690c36f730780 (patch)
tree7c21b0d2845e9c2785e7ea1e613b11353d9b6301 /lisp/minibuffer.el
parent748f0fdd5a682d3bea79e3d30782686eae6d24df (diff)
downloademacs-9fee1b8fb3395bde2d2e28e46c6690c36f730780.tar.gz
Minor copyedits of completion-at-point-functions documentation
* lisp/minibuffer.el (completion-at-point-functions): * doc/lispref/minibuf.texi (Completion in Buffers): Fix wording and filling. (cherry picked from commit a8ddd05d7d32946b892b9faaba6c9736ed2ad847)
Diffstat (limited to 'lisp/minibuffer.el')
-rw-r--r--lisp/minibuffer.el9
1 files changed, 5 insertions, 4 deletions
diff --git a/lisp/minibuffer.el b/lisp/minibuffer.el
index ced0ce64b50..7e7856f3a96 100644
--- a/lisp/minibuffer.el
+++ b/lisp/minibuffer.el
@@ -2078,10 +2078,11 @@ Currently supported properties are all the properties that can appear in
As is the case with most hooks, the functions are responsible for
preserving things like point and current buffer.
-NOTE: These functions should be cheap to run since they're sometimes run from
-`post-command-hook' and they should ideally only choose which kind of
-completion table to use and not pre-filter it based on the current text between
-START and END (e.g. that would not obey `completion-styles').")
+NOTE: These functions should be cheap to run since they're sometimes
+run from `post-command-hook'; and they should ideally only choose
+which kind of completion table to use, and not pre-filter it based
+on the current text between START and END (e.g., they should not
+obey `completion-styles').")
(defvar completion--capf-misbehave-funs nil
"List of functions found on `completion-at-point-functions' that misbehave.