From: Lennart Borgman <lennart.borgman@gmail.com>
To: Emacs-Devel devel <emacs-devel@gnu.org>
Cc: "Zoltán Nagy" <abesto0@gmail.com>
Subject: Re: font-lock-add-keywords: should font-lock-mode be turned off/on after that
Date: Fri, 29 May 2009 19:56:16 +0200 [thread overview]
Message-ID: <e01d8a50905291056q55b75cdbyfa9067074503cc8c@mail.gmail.com> (raw)
In-Reply-To: <e01d8a50905291050ldcc286ava66170d7dfd5b5a2@mail.gmail.com>
After sending this I got an idea that there might be a bug in
font-lock-add-keywords when mode is nil. It seems to be so. Setting
(font-lock-add-keywords 'php-mode doxymacs-doxygen-keywords)
make it works and then it works in mumamo too.
On Fri, May 29, 2009 at 7:50 PM, Lennart Borgman
<lennart.borgman@gmail.com> wrote:
> If you add keywords
>
> (font-lock-add-keywords nil doxymacs-doxygen-keywords)
>
> Do you have to do
>
> (font-lock-mode -1)
> (font-lock-mode 1)
>
> after that? It looks to me from the code like it is not necessary, but
> I in the case above font-lock did not work without turning off/on
> font-lock. Actually after
>
> (defun my-doxymacs-font-lock ()
> (require 'doxymacs)
> (message "before (doxymacs-font-lock)")
> (doxymacs-font-lock)
> (message "after (doxymacs-font-lock)"))
> (add-hook 'php-mode-hook 'my-doxymacs-font-lock)
>
> and doing
>
> M-x php-mode
>
> there was no fontification at all until font-lock was turned off/on
> and then the keywords worked too.
>
> It looks to me that there can be some kind of problem with
> doxymacs-doxygen-keywords. Is there some way of checking that? Or is
> it something with font-lock-add-keywords?
>
next prev parent reply other threads:[~2009-05-29 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 17:50 font-lock-add-keywords: should font-lock-mode be turned off/on after that Lennart Borgman
2009-05-29 17:56 ` Lennart Borgman [this message]
2009-05-30 20:28 ` 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=e01d8a50905291056q55b75cdbyfa9067074503cc8c@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=abesto0@gmail.com \
--cc=emacs-devel@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.