From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: gnus-sync: `gnus-newsrc-alist' modifications don't survive `M-g'
Date: Sun, 08 Jan 2012 11:47:09 +0100 [thread overview]
Message-ID: <8762gmpj2q.fsf@dod.no> (raw)
In-Reply-To: <m3zke058rn.fsf@stories.gnus.org>
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
> Ted Zlatanov <tzz@lifelogs.com> writes:
LMI> The variable that controls this is... er... `gnus-propagate-marks'?
>>
>> Sorry, it's nil for me.
> D'oh! I'm running with `nntp-marks-is-evil' set to t. Gah. I thought
> I had cleared out all customisations in this area...
> There's a fundamental difference between the marks stored in IMAP and
> the marks stored on the nntp backend. The former is useful. The
> latter just duplicates the information in the .newsrc.eld file
> locally, and isn't particularly.
Interesting. I also (not unexpectedly) have the .marks files in all of
my gnusen. These are possibly the cause for gnus-sync's (both the old
and the new) problems: ie. sometimes it updates the marks correctly,
sometimes it doesn't.
It could maybe also be the cause of gnus agent's obscure errors...? But
if it is, it points to a potential issue: As you say, storing marks in
the backend is the right thing to do for nnimap. And nnimap is also the
backend that would benefit the most from a working agent (at least for
me).
next prev parent reply other threads:[~2012-01-08 10:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 12:42 Ted Zlatanov
2011-11-03 22:36 ` Lars Magne Ingebrigtsen
2011-11-04 12:21 ` Ted Zlatanov
2012-01-03 23:08 ` Lars Magne Ingebrigtsen
2012-01-07 1:36 ` Ted Zlatanov
2012-01-07 1:40 ` Lars Magne Ingebrigtsen
2012-01-07 2:18 ` Ted Zlatanov
2012-01-07 2:23 ` Ted Zlatanov
2012-01-07 2:30 ` Lars Magne Ingebrigtsen
2012-01-07 2:36 ` Ted Zlatanov
2012-01-07 6:25 ` Lars Magne Ingebrigtsen
2012-01-08 10:47 ` Steinar Bang [this message]
2012-01-16 18:46 ` Steinar Bang
2012-01-26 18:56 ` Lars Ingebrigtsen
2012-01-26 21:20 ` Steinar Bang
2012-01-26 22:08 ` Lars Ingebrigtsen
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=8762gmpj2q.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.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).