From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Cc: ding@gnus.org
Subject: Re: NNTP marks code breaks .newsrc
Date: Fri, 09 Jul 2004 14:10:35 +0200 [thread overview]
Message-ID: <m3d6359y9w.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <ilu3c4179mv.fsf@latte.josefsson.org> (Simon Josefsson's message of "Fri, 09 Jul 2004 12:33:28 +0200")
Simon Josefsson <jas@extundo.com> writes:
>> Any help will be appreciated,
>
> Does (setq gnus-agent-synchronize-flags 'ask) help?
It does indeed help.
I wonder however why a binary search across Gnus versions let me end up
with Kai's nntp-marks diff though and how the nntp-marks code relates to
gnus-agent synchronization stuff.
> I have now reverted the default from nil to 'ask in CVS, seems like
> many people have reported this problem, and as far as I can tell,
> nobody explained why nil is better.
Thanks a bunch.
--
Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred)
next prev parent reply other threads:[~2004-07-09 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 9:53 Matthias Andree
2004-07-09 10:33 ` Simon Josefsson
2004-07-09 12:10 ` Matthias Andree [this message]
2004-07-09 12:43 ` Simon Josefsson
2004-07-12 9:54 ` Matthias Andree
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=m3d6359y9w.fsf@merlin.emma.line.org \
--to=ma@dt.e-technik.uni-dortmund.de \
--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).