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: Mon, 11 Aug 2014 11:17:24 +0200	[thread overview]
Message-ID: <878umvv10b.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87y4uw5aok.fsf@debian.uxu>

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

> Julien Cubizolles <j.cubizolles@free.fr> writes:

>> For years now I've experienced this strange behaviour: running
>> gnus-group-get-new-news or restarting gnus changes the status of read
>> messages in nnml groups: some read messages become unread. It doesn't
>> happen in the nntp and nnimap groups I'm using.

> Yeah, I've experienced things like that many times, I haven't been
> able to deduct if it has happened exclusively for nnml though.

Weird, I never see that. I wonder what the difference is. The only
"weird" thing I can think of in my setup is that I don't use the agent.

Can either of you reproduce the problem?

> I always thought that happened because the .newsrc.eld file wasn't
> saved, so sometimes the changes would vanish when you terminate Emacs.

Do you quit Gnus before stopping Emacs?

> 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 :-))

[...]

> (setq gnus-use-dribble-file nil)

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


  Best regards,

    Adam

-- 
 "I went for the fireengines                                  Adam Sjøgren
  But they were all upside down"                         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  9:17 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 [this message]
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
     [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=878umvv10b.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).