From: Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de>
Cc: ding@ifi.uio.no
Subject: Re: highlight-problem
Date: 21 May 1996 16:53:32 +0200 [thread overview]
Message-ID: <vaf689qhyc3.fsf@ls6.informatik.uni-dortmund.de> (raw)
In-Reply-To: Stefan Janke's message of Tue, 21 May 1996 13:58:34 +0200
>>>>> On Tue, 21 May 1996 13:58:34 +0200, Stefan Janke
>>>>> <gonzo@burg.studfb.unibw-muenchen.de> said:
Stefan> I do use the hl-319 for highlighting and it works very good
Stefan> with most modes, but with the sgnus-packet I dont get such a
Stefan> good result as with the Gnus-5.1 from emacs-19.30. [...]
Gnus has built-in highlighting. The best approach to highlighting
with Gnus would be to do away with font-lock or hilit and use the
built-in way. It's not all that complicated, really, if you know
about faces.
The general idea is that you have a description of what groups should
be printed with which faces, and you assign properties (like bold,
underline, background color, foreground color) to these faces.
Here's how you make a face and change its properties:
(make-face 'my-small-group-face)
(make-face-bold 'my-small-group-face)
(set-face-foreground 'my-small-group-face "green")
Here's how you create a description that sez groups with less than 20
unread articles should be printed with my-small-group-face:
(setq gnus-group-highlight
(list
'( (< unread 20) . my-small-group-face )
;; add more lines here at your leisure
)
)
Type M-x apropos RET face RET to get a list of functions that deal
with faces. Type C-h v gnus-group-highlight RET to get a description
of what parameters you can use to define the faces for the groups.
For a good description of what gnus-group-highlight can do, go to the
node `Group Highlighting' in the SGnus manual.
hth,
kai
--
Life is hard and then you die.
prev parent reply other threads:[~1996-05-21 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-21 11:58 highlight-problem Stefan Janke
1996-05-21 13:57 ` highlight-problem Lars Magne Ingebrigtsen
1996-05-21 14:53 ` Kai Grossjohann [this message]
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=vaf689qhyc3.fsf@ls6.informatik.uni-dortmund.de \
--to=grossjoh@charly.informatik.uni-dortmund.de \
--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).