From: Paul Moore <gustav@morpheus.demon.co.uk>
Subject: Re: Setting fonts on text directly
Date: Fri, 27 Sep 2002 21:02:27 +0100 [thread overview]
Message-ID: <u1kb5hgs.fsf@morpheus.demon.co.uk> (raw)
In-Reply-To: <vafwup7v2l2.fsf@lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> paul.moore@atosorigin.com (Paul Moore) writes:
>
>> Another approach I could use would be to hook into
>> gnus-summary-highlight-line-function, which is called after all the
>> rest of the work of highlighting is done, but that's harder than it
>> looks, as I have to post-process the formatted line then, rather than
>> working with the raw data. I'd much prefer to get the original
>> approach working...
>
> Maybe gnus-summary-highlight-line should provide for the raw data to
> be available. Is that difficult to do?
I discovered that the most intractable problem is that
gnus-summary-highlight-line-function doesn't get called every time
(effecively, only when nothing in gnus-summary-highlight applies - or
maybe not, I lost track...) so I can't use that to do the
post-processing. I raised a bug report for that.
Gross hacks work:
1. Set a custom property on the text I want to highlight (pfm-font,
say)
2. Write something to go through the current line, setting text font
properties from pfm-font.
3. Hack gnus-summary-highlight - pull out its function definition, and
redefine it as its old definition, followed by the thing from (2).
Of course, if I ever actually wrote something like that, I'd probably
have to shoot myself afterwards :-)
OK, I have a solution. Whether I can actally face using it is another
matter :-)
One of these days I'll work out if I love or hate Lisp for letting me
do that...
Paul.
parent reply other threads:[~2002-09-27 20:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <vafwup7v2l2.fsf@lucy.cs.uni-dortmund.de>]
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=u1kb5hgs.fsf@morpheus.demon.co.uk \
--to=gustav@morpheus.demon.co.uk \
/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).