From: "Paul D. Smith" <psmith@BayNetworks.com>
Cc: Gnus 5 Mailing List <ding@ifi.uio.no>
Subject: Re: [5.2.2] proper highlighting setup?
Date: Wed, 29 May 96 13:57:37 EDT [thread overview]
Message-ID: <9605291757.AA18690@lemming.engeast> (raw)
In-Reply-To: <fawn32rmmc7.fsf@mordor.rsn.hp.com>
%% Shane Holder <holder@mailhost.rsn.hp.com> writes:
sh> As of 19.31 you can delete fontification hooks, assuming the mode
sh> supports font-lock-mode.
sh> (global-font-lock-mode t)
I have this. This turns on/off font-lock, but to control _what_ gets
font-locked you have to modify these hooks. GNUS fontification is too
complex to be controlled with a simple font-lock-maximum-decoration
variable.
See the docs for gnus-article-maybe-highlight and
gnus-article-highlight, and try them yourself to see the difference.
Come to think of it, though, it'd be _really_ nice if there was a
mapping in gnus-article-maybe-highlight between
font-lock-maximum-decoration and the various article fontification
options for articles; then you could leave the hook function as
gnus-article-maybe-highlight and raise the font-lock-maximum-decoration
levels to get more fontification in articles.
-------------------------------------------------------------------------------
Paul D. Smith <psmith@baynetworks.com> Network Management Development
Senior Software Engineer Bay Networks, Inc.
-----------------------------------------------==<http://www.baynetworks.com/>-
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions--Bay Networks takes no responsibility for them.
next prev parent reply other threads:[~1996-05-29 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-29 15:12 Paul D. Smith
1996-05-29 17:16 ` Shane Holder
1996-05-29 17:57 ` Paul D. Smith [this message]
1996-05-29 21:24 ` Lars Magne Ingebrigtsen
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=9605291757.AA18690@lemming.engeast \
--to=psmith@baynetworks.com \
--cc=ding@ifi.uio.no \
/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).