Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: read messages becoming unread in nnml
Date: Tue, 12 Aug 2014 00:48:47 +0200	[thread overview]
Message-ID: <87r40mtzg0.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87wqaer8rj.fsf@debian.uxu>

Emanuel Berg <embe8573@student.uu.se> writes:

>> Do you quit Gnus before stopping Emacs?

> No, I always assumed Emacs would tell Gnus to save and terminate.

It doesn't.

> Man, come to think of it, I don't even stop Emacs, I run a shell
> command from Emacs (shutdown) to shut down the whole system. Perhaps
> that's why!

It most probably will cause you problems from time to time, yes.

I think we can rule out that your problems and Julien's problems have
the same cause.

>>> I would think it best for the .newsrc.eld be saved every time there
>>> is a change

>> (If you want to maximize disk-I/O :-))

> Yeah, but that's cool, I don't do that many things with that many
> posts anyway. And computers including the lowest-level hardware are
> quick these days.

So why did you turn off the dribble-file, which conceptually does what
you are saying you want?

>> You have explicitly turned off Gnus' defence against crashes and
>> unforseen events!

> I know, we discussed this already. My Debian is like a Swiss watch

Yeah, but you are pulling the rug out under Gnus, like, every time you
turn your computer off.

So, the unforseen event in this case is located around 40 cm's from the
screen. Or some meters from the projection on your wall.

In summary:

 a) Always quit Gnus before closing down Emacs

 b) Don't turn off the dribble-file, unless you have a really, really
    good reason (i.e. don't)


  Best regards,

    Adam

-- 
 "I'm so indie my shirt don't fit"                            Adam Sjøgren
                                                         asjo@koldfront.dk


_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2014-08-11 22:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.6902.1407653531.1147.info-gnus-english@gnu.org>
2014-08-10 20:52 ` Emanuel Berg
2014-08-11  9:17   ` Adam Sjøgren
2014-08-11 10:54     ` Julien Cubizolles
2014-08-11 10:51   ` Julien Cubizolles
2014-09-17  9:15     ` Julien Cubizolles
     [not found]   ` <mailman.6960.1407748672.1147.info-gnus-english@gnu.org>
2014-08-11 21:55     ` Emanuel Berg
2014-08-11 22:48       ` Adam Sjøgren [this message]
     [not found]       ` <mailman.6989.1407797356.1147.info-gnus-english@gnu.org>
2014-08-11 23:16         ` Emanuel Berg
2014-08-12 10:33           ` Adam Sjøgren
     [not found]           ` <mailman.7007.1407839648.1147.info-gnus-english@gnu.org>
2014-08-12 17:15             ` Emanuel Berg
2014-08-12 17:32               ` Adam Sjøgren
2014-08-12 17:32               ` Adam Sjøgren
     [not found]               ` <mailman.7028.1407864763.1147.info-gnus-english@gnu.org>
2014-08-12 17:59                 ` Emanuel Berg
2014-08-12 20:17                   ` Adam Sjøgren
     [not found]                   ` <mailman.7035.1407874665.1147.info-gnus-english@gnu.org>
2014-08-13 20:02                     ` Emanuel Berg
     [not found]               ` <mailman.7029.1407864916.1147.info-gnus-english@gnu.org>
2014-08-12 18:07                 ` Emanuel Berg
2014-08-12 17:21         ` Carlos Pita
2014-08-12 17:20           ` Emanuel Berg
2014-08-10  6:51 Julien Cubizolles

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=87r40mtzg0.fsf@topper.koldfront.dk \
    --to=asjo@koldfront.dk \
    --cc=info-gnus-english@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.
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).