GNU bug report logs - #15219
Emacs Lisp mode and Lisp mode font-locking

Previous Next

Full log

Message #14 received at 15219 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Bozhidar Batsov <bozhidar.batsov <at> gmail.com>
Cc: Stefan Monnier <monnier <at> iro.umontreal.ca>, 15219 <at> debbugs.gnu.org
Subject: Re: bug#15219: Emacs Lisp mode and Lisp mode font-locking
Date: Wed, 30 Oct 2019 14:30:15 +0100

Bozhidar Batsov <bozhidar.batsov <at> gmail.com> writes:

> Anyways, I'd be happy to get just a fix for the keywords and &optional (and
> related) faces, since those are definitely off.

The complaint is that :foobar below uses font-lock-builtin-face and
&optional uses font-lock-type-face in emacs-lisp-mode.

(defun foo (bar &optional zot)
  (list :foobar bar))

This is defined in lisp-cl-font-lock-keywords in lisp-mode.el, and I
agree that separate faces should probably be used for those -- keywords
aren't builtins and &optional isn't a type.

:keywords are constants, I guess, but we use font-lock-constant-face for
catch/throw and the like, and I don't think we have anything that
vaguely makes sense for &optional.

Would adding new faces for these make sense?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.