From: Samuel Tardieu <sam@inf.enst.fr>
Subject: Lost mails because of bogus newsrc.eld :/
Date: 18 Apr 1996 14:00:03 +0200 [thread overview]
Message-ID: <qw67mvdpwsc.fsf@gargantua.enst.fr> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
This mail is for Lars, but maybe some people here will have done the
work already.
Due to some experimentations I made, I ended up with a mail group
whose active highest number was 30 and the highest news number read in
this group was 9000. This made that even while mails were entered into
this group (and active incremented) I didn't see any of them because
September Gnus told me there were none.
Would it be possible for Gnus to warn the user with a message such as:
"Warning, xxx mails read while there is only yyy in group, adjust (Y/n) ?"
This group was not very important and people didn't get too upset that I
didn't answer, but I'm afraid this arrives again with a very critical
workgroup which will make me look like an arrogant people which
doesn't even answers his mail :/
I just noticed this; I've lost 2 weeks of mails in this group
(because the bogus file was created 3 weeks ago and I only keep 1 week
history). This is my fault and only mine, but it would be a good idea
IMHO to warn users about this probable incoherency.
And if it happens to users unaware of the .newsrc.eld/active
structure... this could bring them into deep troubles...
Wouldn't it worth adding this check in the current Gnus release ? (I
mean before 5.2 gets released)
Sam
- --
"La cervelle des petits enfants, ca doit avoir comme un petit gout de noisette"
Charles Baudelaire
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQCVAgUBMXYuvYFdzKExeYBpAQFGZAP+My5yl9edWyTh53H8NLdaiiFb7EZLJWvG
Vr4MuXrb8GVozUEHCJvDaZCiekS71yDkZR8vu+HZlxh1wA2xDOVUqJx9392Gn8VI
U3zHyS9v87ZikVkAm4L8UV4KVEwcaGsA9rptNq5ka8jsZDpOtbdySsLAAOjZk5Yo
CfsD2eY8rRY=
=DO9l
-----END PGP SIGNATURE-----
reply other threads:[~1996-04-18 12:00 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=qw67mvdpwsc.fsf@gargantua.enst.fr \
--to=sam@inf.enst.fr \
/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).