From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Why call font-lock-add-keywords in a mode hook?
Date: Mon, 25 Jan 2016 15:49:56 +0100 [thread overview]
Message-ID: <87si1lpvcb.fsf@web.de> (raw)
In-Reply-To: 878u3ec6xk.fsf@mbork.pl
Marcin Borkowski <mbork@mbork.pl> writes:
> Hi list,
>
> this I found in the manual:
>
> -- Function: font-lock-add-keywords mode keywords &optional how
> This function adds highlighting KEYWORDS, for the current buffer or
> for major mode MODE. The argument KEYWORDS should be a list with
> the same format as the variable ‘font-lock-keywords’.
>
> If MODE is a symbol which is a major mode command name, such as
> ‘c-mode’, the effect is that enabling Font Lock mode in MODE will
> add KEYWORDS to ‘font-lock-keywords’. Calling with a non-‘nil’
> value of MODE is correct only in your ‘~/.emacs’ file.
>
> If MODE is ‘nil’, this function adds KEYWORDS to
> ‘font-lock-keywords’ in the current buffer. This way of calling
> ‘font-lock-add-keywords’ is usually used in mode hook functions.
>
> My question: why would I want to call this function in a hook if I can
> specify the mode in its invocation? (Assuming that I use it in my
> init.el, of course.)
I can think of two reasons at least:
(1) If MODE has not yet "been initialized", the HOW argument would not
have any effect. In particular, if you want to append your keywords to
the generic ones, this will only work before the mode had been defined.
(2) With MODE -> nil, using the function in a hook is a common use
case, I think.
Regards,
Michael.
next prev parent reply other threads:[~2016-01-25 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 10:03 Why call font-lock-add-keywords in a mode hook? Marcin Borkowski
2016-01-25 14:49 ` Michael Heerdegen [this message]
2016-01-26 4:14 ` Stefan Monnier
2016-01-26 8:51 ` Marcin Borkowski
2016-01-26 13:04 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87si1lpvcb.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.