diff options
author | Stefan Monnier <monnier@iro.umontreal.ca> | 2018-03-27 16:01:30 -0400 |
---|---|---|
committer | Stefan Monnier <monnier@iro.umontreal.ca> | 2018-03-27 16:01:30 -0400 |
commit | b56c56f203f8b066dd71e6ae6a254121b3ac3f08 (patch) | |
tree | d632f48b3d5394d914fd5ee764848f68e30b8c3d /lisp/minibuffer.el | |
parent | c13cd74322be25293e78412b8957fe639f560c54 (diff) | |
download | emacs-b56c56f203f8b066dd71e6ae6a254121b3ac3f08.tar.gz |
(completion-at-point-functions): Improve doc
Diffstat (limited to 'lisp/minibuffer.el')
-rw-r--r-- | lisp/minibuffer.el | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/lisp/minibuffer.el b/lisp/minibuffer.el index 3227917494e..6eded9c58fe 100644 --- a/lisp/minibuffer.el +++ b/lisp/minibuffer.el @@ -2072,7 +2072,12 @@ Currently supported properties are all the properties that can appear in match the text at point, then instead of reporting a completion failure, the completion should try the next completion function. As is the case with most hooks, the functions are responsible for -preserving things like point and current buffer.") +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').") (defvar completion--capf-misbehave-funs nil "List of functions found on `completion-at-point-functions' that misbehave. |