Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@justresearch.com>
Subject: multipart uuencoded articles are not all marked read
Date: 12 Jan 2000 10:27:08 -0500	[thread overview]
Message-ID: <vxkya9vwbsj.fsf@beaver.jprc.com> (raw)

If one has a summary showing e.g...

   [ 500: some guy            ] some-large-file.ext (1/5)
   [ 500: some guy            ] some-large-file.ext (2/5)
   [ 500: some guy            ] some-large-file.ext (3/5)
   [ 500: some guy            ] some-large-file.ext (4/5)
   [ 397: some guy            ] some-large-file.ext (5/5)

...and one extracts some-large-file.ext using `X u', the five
component articles are correctly obtained and some-large-file.ext is
reconstructed and left available for viewing as a pseudoarticle.
However, only the (5/5) article is marked read when this is done.  The
other four (x/5) articles are still marked unread.

I have no idea when this broke, as I don't use things like `X u' very
often.  I used it today for probably the first time in 6 months.



             reply	other threads:[~2000-01-12 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-12 15:27 Karl Kleinpaste [this message]
2000-04-21 13:24 ` Lars Magne Ingebrigtsen
2000-04-25 13:43   ` Karl Kleinpaste

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=vxkya9vwbsj.fsf@beaver.jprc.com \
    --to=karl@justresearch.com \
    /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).