From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: font-locked Gnus browse server
Date: Wed, 13 May 2015 23:15:40 +0200 [thread overview]
Message-ID: <874mngfabn.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.2946.1431523050.904.info-gnus-english@gnu.org>
Tassilo Horn <tsdh@gnu.org> writes:
>> Here is a dump [1] of how it could look, and the
>> Elisp [2] that makes it look that way easily
>> enough. Doesn't it look nice and, uhm, colorful?
>> It seems even tho `font-lock-mode' is on, you still
>> have to call `font-lock-fontify-buffer' to get
>> the action.
>
> I think it would be there immediately if you call
> `font-lock-add-keywords' with nil in place of
> 'gnus-browse-mode.
From (describe-function 'font-lock-add-keywords)
MODE should be a symbol, the major mode command
name, such as `c-mode' or nil. If nil,
highlighting keywords are added for the
current buffer.
>> I put it in `gnus-browse-mode-hook' but
>> I don't think you should have to (?).
>
> Or you can put your current `font-lock-add-keywords'
> call into your ~/.gnus. Then it would be evaluated
> before gnus-browse-mode was activated.
It is in an init file and it is evaluated before the
mode is set. For some reason it doesn't kick in
without the explicit call to
`font-lock-fontify-buffer'. That has never been needed
elsewhere in my experience.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2015-05-13 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 23:03 Emanuel Berg
2015-05-13 13:17 ` Tassilo Horn
[not found] ` <mailman.2946.1431523050.904.info-gnus-english@gnu.org>
2015-05-13 21:15 ` Emanuel Berg [this message]
2015-05-15 9:06 ` Tassilo Horn
[not found] ` <mailman.3058.1431680808.904.info-gnus-english@gnu.org>
2015-05-15 14:07 ` Emanuel Berg
2015-05-16 7:33 ` Tassilo Horn
[not found] ` <mailman.3122.1431761615.904.info-gnus-english@gnu.org>
2015-05-16 21:25 ` Emanuel Berg
2015-05-18 11:35 ` Tassilo Horn
2015-05-18 19:58 ` Emanuel Berg
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=874mngfabn.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=info-gnus-english@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.
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 NNTP newsgroup(s).