Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Cook <michael@waxrat.com>
To: ding@gnus.org
Subject: Re: Proposed code to cleanup gnus on Emacs exit
Date: Fri, 07 Oct 2011 16:48:02 -0400	[thread overview]
Message-ID: <87wrcgwmt9.fsf@waxrat.com> (raw)
In-Reply-To: <8762k0k2gz.fsf@uwo.ca> (Dan Christensen's message of "Fri, 07 Oct 2011 15:48:12 -0400")

Dan Christensen <jdc@uwo.ca> writes:

> Dave Abrahams <dave@boostpro.com> writes:
>
>> Can't we at least read the dribble file unconditionally?
>
> Please, no.  If I accidentally catch up a group or something else gets
> messed up, then what I do is exit emacs *without* saving the .newsrc.eld
> and then start Gnus without reading the dribble file.  You are proposing
> removing both of those options, which would get rid of that safety net.

Your safety net could be to remove the dribble file before
restarting gnus.  After all, you knew something had gone wrong
before you decided to exit without saving.

Michael



  parent reply	other threads:[~2011-10-07 20:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23 17:12 John Wiegley
2011-09-10 22:20 ` Lars Magne Ingebrigtsen
2011-09-11  0:42   ` John Wiegley
2011-09-11  1:09     ` Richard Riley
2011-09-29  8:32     ` Ted Zlatanov
2011-09-29 21:55       ` John Wiegley
2011-10-06 21:23       ` Lars Magne Ingebrigtsen
2011-10-06 22:26         ` Dave Abrahams
2011-10-06 22:33           ` Lars Magne Ingebrigtsen
2011-10-06 23:54             ` John Wiegley
2011-10-07  3:00             ` Dave Abrahams
2011-10-07 19:48               ` Dan Christensen
2011-10-07 20:22                 ` Dave Abrahams
2011-10-08  6:14                   ` Steinar Bang
2011-10-07 20:48                 ` Michael Cook [this message]
2011-10-07 23:19                 ` Richard Riley
2011-10-07  1:10           ` Dan Christensen
2011-10-08  9:59       ` Reiner Steib

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=87wrcgwmt9.fsf@waxrat.com \
    --to=michael@waxrat.com \
    --cc=ding@gnus.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.
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).