From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Which hook for auto-MIME-decoding?
Date: 01 Dec 1999 19:59:54 +0100 [thread overview]
Message-ID: <m3903e32s5.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <ltk8ncpmka.fsf@asfast.com>
Lloyd Zusman <ljz@asfast.com> writes:
> However, I can't figure out which hook to use for this. Both
> `gnus-article-mode-hook' and `gnus-article-prepare-hook' don't seem to
> be the right places.
I've now made the latter hook be run after the MIME stuff has been
done.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-12-01 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-21 3:09 Lloyd Zusman
1999-12-01 18:59 ` Lars Magne Ingebrigtsen [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=m3903e32s5.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).