Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kevin.greiner@vignette.com>
Subject: Re: Gnus losing information about what has been read
Date: Tue, 21 Sep 2004 22:12:54 -0500	[thread overview]
Message-ID: <ubrfzknd5.fsf@vignette.com> (raw)
In-Reply-To: <cioq0q$b0t$1@sea.gmane.org>

Ralf Angeli <dev.null@iwi.uni-sb.de> writes:

> * Jan Rychter (2004-09-21) writes:
>
>> [Quoting my post from about 2 weeks ago...]
>>>>>>> "Jan" == Jan Rychter <jan@rychter.com> writes:
>>  Jan> Ok. My Gnus has just forgotten which articles I have read in some
>>  Jan> groups. Again. I have long had the impression that it does that
>>  Jan> behind my back sometimes, but I was never sure enough. This time
>>  Jan> I'm quite sure, because it has forgotten about roughly 1k
>>  Jan> articles.
>>
>>  Jan> This seems to happen for me in agentized groups that I read while
>>  Jan> unplugged -- after I go online again, the articles are visible as
>>  Jan> "unread", again.
>>
>>  Jan> I'm using No Gnus 0.3, updated from CVS on Aug 5, under XEmacs --
>>  Jan> but I'm quite sure the problem has been there for quite some time.
>>
>>  Jan> Any ideas?
>>
>> I am rather alarmed by the number of responses to this report -- namely:
>> zero.
>>
>> Am I the only one who sees that?
>
> I don't know exactly if it is the same problem, but for me Gnus
> forgets marks with the following usage pattern:
>
> When being online, start Gnus in "Plugged" state (`emacs -f gnus').
> Download new (nntp) articles with `J s' into the agent.  Go into
> "Unplugged" state with `J j'.  Read the new articles or mark them as
> read, e.g. with `c y'.  Close Gnus with `q y' and close Emacs.  Start
> Emacs/Gnus again in "Plugged" state.  The read articles will be marked
> unread again.  (If it doesn't "work" the first time, maybe try the
> pattern once again.)  One can distinguish read articles which are not
> marked as read from really new articles.  The latter have an unseen
> mark (`.') in the summary buffer.
>
> Those problems started with the introduction of marks for nntp.

These problems occur because you are not sync'ing the marks that were
cached in the agent (while unplugged) when you next plug in.  What you
have to do is press 'J Y' in the group buffer BEFORE opening a summary
buffer.

If you don't want to do the 'J Y', update to "No Gnus 0.3, Sept 21".
I just checked in the patch to always bypass the agent when writing
nntp marks.

Kevin



  reply	other threads:[~2004-09-22  3:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-04 16:18 Jan Rychter
2004-09-20 23:18 ` Jan Rychter
2004-09-21  6:39   ` Jonas Steverud
2004-09-22 17:20     ` Jan Rychter
2004-09-23  6:32       ` Xavier Maillard
2004-09-21  8:52   ` Ralf Angeli
2004-09-22  3:12     ` Kevin Greiner [this message]
2004-09-22 13:21       ` Ralf Angeli
2004-09-23  0:59         ` Kevin Greiner
2004-09-23  7:59           ` Ralf Angeli
2004-09-23 13:28             ` Kevin Greiner
2004-09-23 14:00               ` Ralf Angeli
2004-09-24  3:52                 ` Kevin Greiner
2004-09-24  7:43                   ` Ralf Angeli
2004-09-24 12:22                     ` Kevin Greiner
2004-09-24 12:32                       ` Ralf Angeli
2004-09-24 13:41                         ` Kevin Greiner
2004-09-24 16:29                           ` Kevin Greiner
2004-09-24 16:30                           ` Ralf Angeli
2004-09-23 20:07           ` Jan Rychter
2004-09-24  3:58             ` Kevin Greiner
2004-10-11 20:22               ` Jan Rychter
2004-10-13  3:01                 ` Kevin Greiner
2004-10-15  1:12                   ` Jan Rychter
2004-09-22 17:13       ` Jan Rychter
2004-09-22 16:29   ` Xavier Maillard

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=ubrfzknd5.fsf@vignette.com \
    --to=kevin.greiner@vignette.com \
    /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).