GNU bug report logs -
#19854
Document new behaviour of elisp at point completion wrt
Previous Next
Reported by: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
Date: Fri, 13 Feb 2015 16:11:02 UTC
Severity: normal
Found in version 25.0.50
Fixed in version 25.1
Done: Noam Postavsky <npostavs <at> users.sourceforge.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
On Sun, Jun 26, 2016 at 9:28 PM, Dmitry Gutov <dgutov <at> yandex.ru> wrote:
> To be thorough, though, AFAIK "function position" means something specific
> to a Lisp programmer: the first element of a list.
>
> Whereas we also look at whether the whole form is quoted (and if so, offer
> all kinds of symbols as completions anyway), and we can also offer
> function-only completions in a non-function position if the function
> position contains one of the known macros (such as cl-callf or
> declare-function).
Okay, maybe using the word "context" instead of "position" works
better? (trying not to get overly specific in the docstring)
(defun elisp-completion-at-point ()
"Function used for `completion-at-point-functions' in `emacs-lisp-mode'.
If the context at point allows only a certain category of
symbols (e.g. functions, or variables) then the returned
completions are restricted to that category. In contexts where
any symbol is possible (following a quote, for example),
functions are annotated with \"<f>\" via the
`:annotation-function' property."
This bug report was last modified 9 years and 24 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.