From: dc@panix.com
Cc: ding@ifi.uio.no
Subject: Re: Outstanding bugs?
Date: Wed, 22 May 1996 01:21:43 -0700 (PDT) [thread overview]
Message-ID: <199605220821.BAA22267@infinity.c2.org> (raw)
In-Reply-To: <x6hgtao06h.fsf@eyesore.no> from "Lars Magne Ingebrigtsen" at May 21, 96 11:17:10 am
Suppose my unix shell session dies when I'm in Gnus, and
does so after having done enough stuff for long enough in Gnus such
that there's an auto save .newsrc*whatever that's more
current than the official .newsrc*whateve files.
The next time I launch Gnus I may see a prompt like:
Auto save file is newer; use it y/n ?
If I see this in the newsgroups buffer I can actually
select the autosave file, and typically the autosave file
is current up to the second to last group I read.
However, sometimes I see after leaving the newsgroups buffer
and before entering the summary buffer a message:
Auto save file is newer; consider M-x recover-file
and there is no way to back out and M-x recover-file short of
opening another shell and killing Gnus.
So the bug is that an option (M-x recover-file)
is presented which is unselectable as and where
it's presented. (in between newsgroups and summary buffer).
How to recreate the bug:
Do s for save in newsgroups buffer.
In the newsgroups buffer,
select a group and many articles from that group[1]
eg select 50,000 articles from control, and have a
killfile (not scorefile) that kills on a low priority
header, eg keyword.
This should take a few hours and gives the autosave timer a good
chance to save something and gives the modem a good chance to
drop the line.
After the session is lost, open a new session, and select the
group that you selected in [1], and choose many articles.
David W. Crawford <dc@panix.com>
> If you're seeing any bugs that you haven't reported -- please do so
> now. Even if it's just a teensy-weensy little thing that you imagine
> everybody has seen and decided to live with, report it anyway.
>
> I'll do a few more nineties releases, and then it's Gnus 5.2 time.
>
> --
> "Yes. The journey through the human heart
> would have to wait until some other time."
>
next prev parent reply other threads:[~1996-05-22 8:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-21 9:17 Lars Magne Ingebrigtsen
1996-05-21 16:50 ` Steven L Baur
1996-05-21 17:04 ` Lars Magne Ingebrigtsen
1996-05-21 19:26 ` Steven L Baur
1996-05-21 19:33 ` Lars Magne Ingebrigtsen
1996-05-21 20:07 ` William Perry
1996-05-22 8:21 ` dc [this message]
1996-05-22 12:28 ` Yair Friedman
1996-05-22 17:45 ` Mark Eichin
1996-05-22 18:46 ` Lars Magne Ingebrigtsen
1996-05-24 3:49 ` stend+ding
1996-05-24 15:22 ` Lars Magne Ingebrigtsen
1996-06-04 20:18 ` St. Suika Roberts
1996-06-04 20:39 ` Scott Byer
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=199605220821.BAA22267@infinity.c2.org \
--to=dc@panix.com \
--cc=ding@ifi.uio.no \
/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).