From: Kevin Greiner <kevin.greiner@vignette.com>
Subject: Re: Gnus losing information about what has been read
Date: Fri, 24 Sep 2004 07:22:33 -0500 [thread overview]
Message-ID: <ullezn9fa.fsf@vignette.com> (raw)
In-Reply-To: <cj0j39$9mb$1@sea.gmane.org>
Ralf Angeli <dev.null@iwi.uni-sb.de> writes:
> * Kevin Greiner (2004-09-24) writes:
>
>> I'm trying an entirely different aproach now as it turned out that the
>> nntp implementation required the server to be open for
>> nntp-marks-file-name to be correct.
>>
>> It appears that the agent's synchronization function could actually
>> try to write the flags back to itself. Then, having done so, delete
>> the flags file so that all of the flags were lost. I've added some
>> additional checks. Please give it a try.
>
> After a fresh CVS checkout I don't get the error related to
> `nntp-marks-file-name' being nil anymore. I noticed a message in the
> echo area upon leaving a group in unplugged state with e.g. `q':
>
> Added to /home/angeli/News/agent/nntp/news.gmane.org/agent.lib/flags
>
> While there are no errors anymore, the marks are forgotten again.
> Tested this by starting Emacs/Gnus in plugged state, downloading new
> articles into the agent with `J s', switching to unplugged state with
> `J j', reading the articles, shutting down Gnus in unplugged state
> with `q y' and restarting Emacs and Gnus in plugged state.
Have you customized gnus-agent-synchronize-flags? If it is null,
automatic synchronization will be completely turned off.
From this description, the unplugged flags are being saved but never
sync'ed. In the last step, when you restart emacs and gnus in a
plugged state, do you automatically perform a fetch session ('J s')?
Kevin
next prev parent reply other threads:[~2004-09-24 12:22 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
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 [this message]
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=ullezn9fa.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).