From: Nikolaj Schumacher <me@nschum.de>
To: Xah <xahlee@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: problem understanding font-lock-defaults structure
Date: Thu, 09 Oct 2008 19:16:37 +0200 [thread overview]
Message-ID: <m21vypk7t6.fsf@nschum.de> (raw)
In-Reply-To: <296d3d40-598c-4ea4-8394-c69975c0399f@a3g2000prm.googlegroups.com> (Xah's message of "Thu\, 9 Oct 2008 08\:29\:02 -0700 \(PDT\)")
Xah <xahlee@gmail.com> wrote:
> (setq myKeywordsLevel1
> (list
> ("Sin\\|Cos" . font-lock-function-name-face)
> ("π\\|∞" . font-lock-constant-face)
> ("x\\|y" . font-lock-variable-name-face)))
>
> Are you sure? It gives (invalid-function "Sin\\|Cos").
You're right.
(setq myKeywordsLevel1
(list (cons "Sin\\|Cos" font-lock-function-name-face)
(cons "π\\|∞" font-lock-constant-face)
(cons "x\\|y" font-lock-variable-name-face)))
I was looking only at the "(quote" line.
>> There's no need to use `, here. `font-lock-keywords' accepts symbols.
>> (setq font-lock-keywords '((myKeywordsLevel1 nil nil)))
>
> after eval that form, than i looked at the value of font-lock-keywords
> using describe-variable, it says:
My bad, too. I meant `font-lock-defaults' -- the variable you were
already using, and we were talking about. -keywords just crept in from
finger memory.
Here's a complete, working example:
(setq myKeywordsLevel1
'(("Sin\\|Cos" . font-lock-function-name-face)
("π\\|∞" . font-lock-constant-face)
("x\\|y" . font-lock-variable-name-face)))
(define-derived-mode foo-mode fundamental-mode
(setq font-lock-defaults '(myKeywordsLevel1)))
> Its value is
> (t
> (myKeywordsLevel1)
> (myKeywordsLevel1
> (0 font-lock-keyword-face)))
>
> Local in buffer untitled<3>;
> »
>
> Where did all the extra came from?
The list has been "compiled". The t marks it as such, so it isn't
processed twice. Due to this kind of voodoo, I avoid touching
`font-lock-keywords'. I use `font-lock-add-keywords'.
regards,
Nikolaj Schumacher
next prev parent reply other threads:[~2008-10-09 17:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 18:46 problem understanding font-lock-defaults structure Xah
2008-10-08 21:22 ` Nikolaj Schumacher
[not found] ` <mailman.619.1223500981.25473.help-gnu-emacs@gnu.org>
2008-10-09 0:02 ` Xah
2008-10-09 0:54 ` Lennart Borgman (gmail)
2008-10-09 2:25 ` Kevin Rodgers
[not found] ` <mailman.643.1223519147.25473.help-gnu-emacs@gnu.org>
2008-10-09 21:18 ` Xah
2008-10-09 11:13 ` Nikolaj Schumacher
[not found] ` <mailman.637.1223513718.25473.help-gnu-emacs@gnu.org>
2008-10-09 15:04 ` Xah
2008-10-09 15:26 ` harven
2008-10-09 17:17 ` Nikolaj Schumacher
[not found] ` <mailman.677.1223550826.25473.help-gnu-emacs@gnu.org>
2008-10-09 15:29 ` Xah
2008-10-09 17:16 ` Nikolaj Schumacher [this message]
[not found] ` <mailman.719.1223572620.25473.help-gnu-emacs@gnu.org>
2008-10-09 21:40 ` Xah
2008-10-09 23:27 ` Nikolaj Schumacher
[not found] ` <mailman.739.1223594868.25473.help-gnu-emacs@gnu.org>
2008-10-10 0:20 ` Xah
2008-10-10 0:45 ` Tim X
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=m21vypk7t6.fsf@nschum.de \
--to=me@nschum.de \
--cc=help-gnu-emacs@gnu.org \
--cc=xahlee@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).