From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: 34502@debbugs.gnu.org
Subject: bug#34502: Ask yourself, am I generating a NEW .overview file?
Date: Sun, 17 Feb 2019 03:26:37 +0800 [thread overview]
Message-ID: <8736onzg9e.fsf@jidanni.org> (raw)
nnml bug:
1. exit emacs
2. remove an .overview file. (Say it was corrupted. Or mom didn't like
it, whatever. State secrets, you know.)
3. start emacs and gnus. etc. All is OK.
1. exit emacs
2. remove an .overview file.
3. send yourself a mail
4. start emacs and gnus... upon entering the group,
the new overview file is generated only *containing only that new mail*.
The user is shocked to see all his other mail is "lost forever" there
is the *Summary* buffer.
Workaroud: first
"you should regenerate them by entering the server buffer using ‘^’, and then ‘g’ on the
appropriate mail server (e.g., nnml) to cause regeneration."
So, bug: when gnus regenerates overview files on its own, if it finds a
new mail, it only uses that, not noticing all the existing mails.
It first needs to ask itself: "am I, ho-hum, appending to an existing .overview
file, or gosh-once-in-a-lifetime fresh generating it for the first time?" So it should look
first, if it finds no .overview file, it had better regenerate it
first before incorporating any new mail! Thanks!
What's worse about this bug is gnus will work great for days, months, with no
.overview file for that group. Until one fateful day, when the user
receives a new mail. And "KABAM", all his messages except that new mail
are suddenly gone. No ESC 99999 RET entering the group will retrieve
them back into the *Summary* buffer etc.
Sure, you could say it is his own "fault" for removing the .overview
file without asking grandma, and (seemingly) losing all his mails is
proper "punishment" for the crime, case closed.
But you could simply always check first: does the .overview file I am
about to cheerily append to exist in the first place?
Gnus v5.13
GNU Emacs 26.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.4)
of 2019-02-03, modified by Debian
next reply other threads:[~2019-02-16 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 19:26 積丹尼 Dan Jacobson [this message]
2019-07-09 16:39 ` bug#34502: Ask yourself, am I generating a NEW .overview file? Lars Ingebrigtsen
2019-07-13 22:57 ` 積丹尼 Dan Jacobson
2019-07-14 11:58 ` Lars Ingebrigtsen
2019-07-15 11:12 ` 積丹尼 Dan Jacobson
2019-07-15 11:36 ` Lars Ingebrigtsen
2019-07-15 12:16 ` 積丹尼 Dan Jacobson
2019-07-15 12:20 ` Lars Ingebrigtsen
2019-07-15 12:56 ` 積丹尼 Dan Jacobson
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736onzg9e.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=34502@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).