From: Mike McEwan <mike@lotusland.demon.co.uk>
Subject: Re: [BUG] gnus-uu.el attempts to uudecode all articles in a thread?
Date: 31 Mar 1998 19:06:47 +0100 [thread overview]
Message-ID: <m3emzizqdk.fsf@lotusland.demon.co.uk> (raw)
In-Reply-To: Mikael Hedin's message of "31 Mar 1998 12:20:55 +0200"
Mikael Hedin <micce@irf.se> writes:
> The subject lines were probably similar with something like (1/7),
> (2/7), etc in them. Then Gnus thinks it's a splitted uuencoded file
> and collects all pieces before decoding.
No, not the case. I can reproduce the problem by sending a message
to myself with uuencoded content, and then following up to myself.
Both articles are unread, I select the original article to myself,
type `X v u', bum, my followup is also marked read. The subject lines
appear:
A+ 127: 31-Mar 18:50 [Mike McEwan ] gnus-uu.el test
+ 2: 31-Mar 18:52 [Mike McEwan ] Re: gnus-uu.el test
--
Mike.
next prev parent reply other threads:[~1998-03-31 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-30 20:10 Mike McEwan
1998-03-31 10:20 ` Mikael Hedin
1998-03-31 18:06 ` Mike McEwan [this message]
1998-04-01 14:04 ` Lars Magne Ingebrigtsen
1998-04-02 2:16 ` Mike McEwan
1998-04-24 19:26 ` 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=m3emzizqdk.fsf@lotusland.demon.co.uk \
--to=mike@lotusland.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).