Gnus development mailing list
 help / color / mirror / Atom feed
From: Burkhard Perkens-Golomb <burkhard.perkens-golomb.NOSP@M.web.de>
Subject: Re: Gnus forgets marks if switching from unplugged to plugged - SOLUTION (?)
Date: Fri, 13 May 2005 12:47:05 +0200	[thread overview]
Message-ID: <uy8ajmmhi.fsf_-_@M.web.de> (raw)
In-Reply-To: <uhdhh8ucv.fsf@M.web.de>

On 5 Mai 2005, Burkhard Perkens-Golomb wrote:

> On 5 Mai 2005, Kevin Greiner wrote:
>
>> Burkhard Perkens-Golomb <burkhard.perkens-golomb@web.de> writes:
>>
>>> Hi!
>>>
>>> The problem:
>>>
>>> I download articles while Gnus is in plugged state. I switch to
>>> unplugged state, read and mark articles while Gnus is unplugged. I
>>> switch back to plugged and press "g" in the group buffer. I see
>>> some messages "Updating marks for <groupname>...done" in the
>>> minibuffer. When the updating is finished all marks (read, ticked,
>>> dormant) I did in the unplugged state are lost :-( .
>>>
>>> I'm working with No Gnus 0.3 and GNU Emacs 21.3.1
>>> (i386-mingw-nt5.1.2600).
>>
>> What backend are you using? nntp, nnimap?
>
> I'm using nntp.
>
> By the way marks done in plugged state stay forever, only marks done
> in unplugged state get lost.

I've found a simple way to get the expected behaviour: I've set the
variable gnus-agent-synchronize-flags to t (previously it was
nil). From the docs I expected the variable to be relevant for
agentized IMAP groups only. But gnus-agent-synchronize-flags seems to
be used for nntp groups too. Was it changed sometime ago? If so the
docs should be changed.

        Burkhard



  reply	other threads:[~2005-05-13 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04 17:30 Gnus forgets marks if switching from unplugged to plugged Burkhard Perkens-Golomb
2005-05-05  3:26 ` Kevin Greiner
2005-05-05 17:18   ` Burkhard Perkens-Golomb
2005-05-13 10:47     ` Burkhard Perkens-Golomb [this message]
2005-05-14 18:25       ` Gnus forgets marks if switching from unplugged to plugged - SOLUTION (?) Kevin Greiner

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=uy8ajmmhi.fsf_-_@M.web.de \
    --to=burkhard.perkens-golomb.nosp@m.web.de \
    /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).