From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: let's go shopping.
Date: 08 Sep 1998 21:26:32 +0200 [thread overview]
Message-ID: <m3d896o17b.fsf@sparky.gnus.org> (raw)
In-Reply-To: Jon Kvebaek's message of "08 Sep 1998 09:54:54 +0200"
Jon Kvebaek <jkv@a.sol.no> writes:
> Yup. The question really ought to be "why isn't the message buffer
> encoded when i forward mail?" - but that was obviously too hard for me
> to say ;)
The decoding has to be done earlier.
I've now taken the decoding functions out of gnus-article-display-hook
and created a gnus-article-decode-hook which is run at a much earlier
point. It should now be impossible to get an undecoded article
displayed in the buffer.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-09-08 19:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-07 8:25 Jon Kvebaek
2002-10-20 23:13 ` Lars Magne Ingebrigtsen
1998-09-08 7:54 ` Jon Kvebaek
1998-09-08 19:26 ` Lars Magne Ingebrigtsen [this message]
1998-09-09 8:20 ` let's go mail and post forwarding Jon Kvebaek
1998-09-10 0:26 ` Lars Magne Ingebrigtsen
1998-09-10 7:52 ` Jon Kvebaek
1998-09-11 6:23 ` Lars Magne Ingebrigtsen
1998-09-11 8:36 ` Jon Kvebaek
1998-09-11 9:19 ` 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=m3d896o17b.fsf@sparky.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).