From: Sudish Joseph <sj@eng.mindspring.net>
Subject: Re: I am an idiot.
Date: 29 Mar 2000 15:12:50 -0500 [thread overview]
Message-ID: <yvia66u5cz7h.fsf@ra.eng.mindspring.net> (raw)
In-Reply-To: Alan Shutko's message of "29 Mar 2000 13:17:14 -0500"
Alan Shutko writes:
> Quitting immediately is always the best bet. When it looks like
> you've lost lots of groups because you hit C-g, you probably haven't
> lost them, just interrupted it while it was building the list, so you
> can safely save and quit. I only use Q when I really think lots has
> gone wrong.
I use Q out of the *Group* buffer quite frequently, mostly when I hit
c by mistake when exiting a group. Or for typos in multi-key
sequences, such as for scoring, where the wrong prefix key can land up
with a lot of groups getting messed up. I then edit the dribble file
and remove the junk transformations on newsrc.eld.
This is what I would've done in Miguel's situation. (Fwiw, there're
other cases where Gnus can get confused when C-g is hit at the wrong
moment during group article update. Sometimes this can lead to groups
having totally bogus article counts. I do a quick visual scan of the
group buffer after hitting C-g when Gnus is updating article counts.)
I've often thought it'd be cool to have an "undo" mode buffer, where
one could edit the dribble file in a user-friendly fashion. However,
C-xC-f .newsrc-dribble combined with C-k works well enough for me at
the moment.
> (I also save all the time, so hitting Q wouldn't be so bad.)
I haven't used "q" in years now and instead bind "z" in the group
buffer to gnus-group-suspend. I then have the suspend hook write out
.newsrc.eld:
(add-hook 'gnus-suspend-gnus-hook 'gnus-group-save-newsrc)
Works very well for me, since a suspended Gnus has faster startup for
scanning new news than M-x gnus.
--
Sudish Joseph
next prev parent reply other threads:[~2000-03-29 20:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-29 10:24 Miguel de Icaza
2000-03-29 15:49 ` Kai Großjohann
2000-03-29 17:49 ` D. Michael McFarland
2000-03-29 18:17 ` Alan Shutko
2000-03-29 20:12 ` Sudish Joseph [this message]
2000-03-29 20:43 ` Colin Rafferty
2000-03-30 5:42 ` Sudish Joseph
2000-03-30 6:20 ` Arcady Genkin
2000-03-30 6:59 ` .newsrc.eld backups (was: I am an idiot.) Mike Fabian
2000-03-30 18:39 ` Florian Weimer
2000-03-30 22:42 ` Mike Fabian
2000-06-13 15:08 ` Andreas Schwab
2000-06-16 10:40 ` Mike Fabian
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=yvia66u5cz7h.fsf@ra.eng.mindspring.net \
--to=sj@eng.mindspring.net \
/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).