[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#23648: [PATCH] `defun-declarations-alist' can be unintentionally mod
bug#23648: [PATCH] `defun-declarations-alist' can be unintentionally modified
Sun, 29 May 2016 16:11:02 +0200
I quite often get the following messages:
Warning: Unknown defun property ‘compiler-macro’ in ...
As far as I could trace it, the problem is indirectly caused by
`define-inline'. While definition of `defun-declarations-alist' does
contain `compiler-macro' in its init form, it can be removed later.
E.g. when I evaluated the variable, it was not there anymore, only
`gv-setter' was there.
It seems this is done unintentionally by `elisp-completion-at-point':
(list t (mapcar (lambda (x) (symbol-name (car x)))
;; FIXME: We should include some
;; docstring with each entry.
Here `delete-dups' destructively modifies a list that includes
`defun-declarations-alist' as its tail verbatim, not as a copy.
Attached patch should fix that.
* elisp-mode.el (elisp-completion-at-point): Fix to not alter
`defun-declarations-alist' by side effect.
Description: Text document
|[Prev in Thread]
||[Next in Thread]|
- bug#23648: [PATCH] `defun-declarations-alist' can be unintentionally modified,
Paul Pogonyshev <=