From: Neil Crellin <neilc@cadabra.com>
Subject: online vs offline available articles conflict resolution
Date: 01 Sep 1999 14:54:21 -0700 [thread overview]
Message-ID: <vb6so4y5mcy.fsf@webtile.wallaby.cc> (raw)
I've just been burnt both ways by this and am wondering if there can't
be some sort of optional warning to prevent it or at least make it
less painful.
Online beating offline: If I haven't done a "J s" recently enough and
accidentally enter a group for which I've seen article numbers online
I've not read, gnus treats them as if already expired I guess, and I
have a devil of a time finding which articles I hadn't already read
next time I'm online.
Offline beating online: This can cause the same problem in reverse.
Having diligently loaded the Agent for several weeks but having no
time to catch up in fa.linux.kernel, I could pleasantly read through
the last 10k articles offline at my leisure. Today I entered the
group while online, and the server only has 1.5k articles and gnus
updated my number of unread articles due to the articles expired on
the server. Presumably I can still go back and read them offline
after some pain, but I wish I didn't have to keep getting caught in
one or other of these contortions.
Is there some way of making this less painful? Perhaps if visiting
groups while offline there were some metadatum kept regarding the last
known to be downloaded article the Agent grabbed, and not killing
anything in a range past that? What about the other way? When there
are unread articles available in the Agent but not on the server, it
seems a crime to mark those as expired and unavailable.
--
Neil Crellin <neilc@wallaby.cc>
next reply other threads:[~1999-09-01 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-01 21:54 Neil Crellin [this message]
1999-09-25 7:57 ` 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=vb6so4y5mcy.fsf@webtile.wallaby.cc \
--to=neilc@cadabra.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).