Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: Proposed code to cleanup gnus on Emacs exit
Date: Thu, 06 Oct 2011 23:00:27 -0400	[thread overview]
Message-ID: <m2aa9dld4k.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <m3wrchda3l.fsf@stories.gnus.org>


on Thu Oct 06 2011, Lars Magne Ingebrigtsen <larsi-AT-gnus.org> wrote:

> Dave Abrahams <dave@boostpro.com> writes:
>
>> But then you get an alarming message and a prompt the next time you
>> start up gnus.
>
> I don't think it's particularly alarming.

Of course not.  Can't we at least read the dribble file unconditionally?
IIRC Gnus can become hopelessly borked if you answer "no" to that
prompt.  In fact, I seem to remember you telling me years ago to just
answer yes always.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com




  parent reply	other threads:[~2011-10-07  3:00 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 [this message]
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
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=m2aa9dld4k.fsf@pluto.luannocracy.com \
    --to=dave@boostpro.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).