Gnus development mailing list
 help / color / mirror / Atom feed
From: Mike McEwan <mike@lotusland.demon.co.uk>
Subject: [BUG] gnus-uu.el attempts to uudecode all articles in a thread?
Date: 30 Mar 1998 21:10:36 +0100	[thread overview]
Message-ID: <m3pvj4c537.fsf@lotusland.demon.co.uk> (raw)


  I just typed `X v u' to view the uuencoded contents of an
article. Gnus proceeded to issue:

Getting article 16585...
Getting article 16614...
Getting article 16618...
Getting article 16620...
Getting article 16635...
Getting article 16649...
Getting article 16657...
Getting article 16703...
Getting article 16704...
Getting article 16722...
Getting article 16731...
Getting article 16732...
Getting article 16736...
Getting article 16640...
Getting article 16581...
End of message

  All the articles in the thread were subsequently marked read, even
though I only wanted to uudecode the contents of article 16581 and
hadn't yet read the rest of the thread! This is surely not the desired
behaviour.

-- 
Mike.


             reply	other threads:[~1998-03-30 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-30 20:10 Mike McEwan [this message]
1998-03-31 10:20 ` Mikael Hedin
1998-03-31 18:06   ` Mike McEwan
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=m3pvj4c537.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).