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

Previous Next

Package: emacs;

Reported by: Bozhidar Batsov <bozhidar.batsov <at> gmail.com>

Date: Fri, 30 Aug 2013 09:33:01 UTC

Severity: wishlist

Full log


View this message in rfc822 format

From: Bozhidar Batsov <bozhidar.batsov <at> gmail.com>
To: 15219 <at> debbugs.gnu.org
Subject: bug#15219: Emacs Lisp mode and Lisp mode font-locking
Date: Fri, 30 Aug 2013 12:32:05 +0300
[Message part 1 (text/plain, inline)]
I've noticed something odd about the font-locking in Emacs Lisp mode and Lisp mode - keyword args are highlighted using the font-lock-builtin-face and constructs like &optional are highlighted using font-lock-type-face. I guess this was was done way back and hasn't been updated in a while, but I think it might a good idea to revise this. Pretty sure those font faces are intended for different usage. I think it would be great if all Emacs programming modes used the built-in font-lock faces consistently, so that the meaning of certain faces doesn't change from mode to mode. I guess that the two modes might also start using the font-lock-built-in face to highlight their core functions (like car, cdr, mapcar, mapc, etc) - as Clojure mode does. Personally I feel that uses of the keyword face for things that are not special forms (like the when macro) should be replaced with uses of the built-in face.
I've posted this to devel a while back (http://lists.gnu.org/archive/html/emacs-devel/2013-07/msg00592.html) and Michael Heerdegen suggested reporting it as a bug as well.


-- 
Cheers,
Bozhidar

[Message part 2 (text/html, inline)]

This bug report was last modified 3 years and 246 days ago.

Previous Next


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