Gnus development mailing list
 help / color / mirror / Atom feed
From: gsstark@MIT.EDU (Greg Stark)
Subject: Old marking with fetch-old-headers in big groups
Date: 15 Jan 1996 03:30:12 -0500	[thread overview]
Message-ID: <ycq7mytuagb.fsf@fierce-bad-rabbit.MIT.EDU> (raw)



I have gnus-fetch-old-headers to t.

When I enter a group that has a lot of unread posts it asks me how many posts
to read.  If I only ask for some of them then it fetches only those plus the
extra old ones it needs to complete the threads.  It marks the extra ones as
O, old.  It also marks the read articles it fetched for the same reason as
old.  That's a problem.

I would like it not to treat these as the same.  I would like to read the old
unread articles, but not the old read articles.  I think what I want it to do
is to not mark the old unread articles at all.   If it is going to mark them
then I want them distinguishable from old read articles and I want some way to
tell the reading commands, N, P, and SPC to go to them.

Then if I ask for the last 10 or 20 posts I get the whole of any threads that
are still live.  It might also be interesting to be able to give a date in
answer to that prompt and have Gnus get articles back to that date.  Then we
could even have a variable to set to the default answer to that question,
ie. I can set it to by default get one days worth of posts plus
fetch-old-headers whenever I enter a big group I don't normally read.


--
greg


                 reply	other threads:[~1996-01-15  8:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ycq7mytuagb.fsf@fierce-bad-rabbit.MIT.EDU \
    --to=gsstark@mit.edu \
    /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).