From: Tassilo Horn <tsdh@gnu.org>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: help-gnu-emacs@gnu.org, emacs-devel@gnu.org
Subject: Bug in Elisp font-locking (was: Concern around use of eval)
Date: Fri, 20 Mar 2015 18:19:43 +0100 [thread overview]
Message-ID: <87d243si1c.fsf_-_@gnu.org> (raw)
In-Reply-To: <878uerem09.fsf@gmail.com> (Thierry Volpiatto's message of "Fri, 20 Mar 2015 16:17:42 +0100")
Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:
>> (defun lh/gen-predicate (label)
>> (defalias (intern (concat "lh/" label "-p"))
> ^^^^^^
> In this case intern should not be highlighted, isn't it ?.
Indeed, it shouldn't be. But the font-lock entry for definitions which
applies the function name face here matches next to `defun', `defmacro',
or `defalias' also `cl-defstruct', and that may have the two forms
(defstruct struct-name ...)
(defstruct (struct-name OPTIONS) ...)
and therefore, the regexp simply skips the paren. The following patch
should fix that.
Cc-ing emacs-devel to ask if that's ok to commit. Is it? Or too much
hassle for just `defalias'? (I think that's the only definition form
which is implemented as a function where the name may be provided by a
funcall.)
--8<---------------cut here---------------start------------->8---
diff --git a/lisp/emacs-lisp/lisp-mode.el b/lisp/emacs-lisp/lisp-mode.el
index 6b30773..614fbc6 100644
--- a/lisp/emacs-lisp/lisp-mode.el
+++ b/lisp/emacs-lisp/lisp-mode.el
@@ -320,14 +320,18 @@
`( ;; Definitions.
(,(concat "(" el-defs-re "\\_>"
;; Any whitespace and defined object.
- "[ \t'\(]*"
- "\\(\\(?:\\sw\\|\\s_\\)+\\)?")
+ "[ \t']*"
+ ;; With defstruct, the name may follow a paren,
+ ;; e.g. (defstruct (foo-struct opts)...).
+ "\\(([ \t']*\\)?\\(\\(?:\\sw\\|\\s_\\)+\\)?")
(1 font-lock-keyword-face)
- (2 (let ((type (get (intern-soft (match-string 1)) 'lisp-define-type)))
- (cond ((eq type 'var) font-lock-variable-name-face)
- ((eq type 'type) font-lock-type-face)
- (t font-lock-function-name-face)))
- nil t))
+ (3 (let ((type (get (intern-soft (match-string 1)) 'lisp-define-type)))
+ (cond ((eq type 'var) font-lock-variable-name-face)
+ ((eq type 'type) font-lock-type-face)
+ ;; If match-string 2 is non-nil, we encountered a
+ ;; form like (defalias (intern (concat s "-p"))).
+ ((not (match-string 2)) font-lock-function-name-face)))
+ nil t))
;; Emacs Lisp autoload cookies. Supports the slightly different
;; forms used by mh-e, calendar, etc.
("^;;;###\\([-a-z]*autoload\\)" 1 font-lock-warning-face prepend))
--8<---------------cut here---------------end--------------->8---
Bye,
Tassilo
next prev parent reply other threads:[~2015-03-20 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 6:53 Concern around use of eval Les Harris
2015-03-19 8:00 ` Tassilo Horn
[not found] ` <mailman.2302.1426752018.31049.help-gnu-emacs@gnu.org>
2015-03-19 8:12 ` Joost Kremers
2015-03-19 8:31 ` Tassilo Horn
[not found] ` <mailman.2305.1426753885.31049.help-gnu-emacs@gnu.org>
2015-03-20 19:54 ` Joost Kremers
2015-03-19 14:07 ` Stefan Monnier
2015-03-20 15:17 ` Thierry Volpiatto
2015-03-20 17:19 ` Tassilo Horn [this message]
2015-03-20 17:31 ` Bug in Elisp font-locking Stefan Monnier
2015-03-20 17:43 ` Drew Adams
2015-03-20 18:47 ` Tassilo Horn
2015-03-20 20:38 ` Stefan Monnier
2015-03-20 22:45 ` Tassilo Horn
2015-03-21 2:33 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d243si1c.fsf_-_@gnu.org \
--to=tsdh@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=thierry.volpiatto@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).