From: Damien Collard <damien.collard@distfp.net>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: info-gnus-english@gnu.org
Subject: Re: Way to detect "raw" display of article?
Date: Sun, 17 Mar 2019 09:54:45 +0100 [thread overview]
Message-ID: <m28sxddgoa.fsf@gandi.net> (raw)
In-Reply-To: <87zhpu6wwf.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 16 Mar 2019 19:46:08 -0700")
On Sam, mar 16 2019, Eric Abrahamsen wrote:
> I think the "appropriate" way of doing this would be to make this a
> washing function that does this on command, then a corresponding
> `gnus-treat-FOO' variable, then allow people to set that as they like.
This works very well, thank you!
And it's cleaner than my abusing of `fontification-functions` previously
(for which I had to make sure the prettification was only performed
once).
Now to see if I can avoid using `fontification-functions` in
message-mode...
--
Damien Collard
next prev parent reply other threads:[~2019-03-17 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 21:52 Damien Collard
2019-03-17 2:46 ` Eric Abrahamsen
2019-03-17 8:54 ` Damien Collard [this message]
2019-03-17 21:34 ` Damien Collard
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=m28sxddgoa.fsf@gandi.net \
--to=damien.collard@distfp.net \
--cc=eric@ericabrahamsen.net \
--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).