From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Cc: ding@gnus.org
Subject: Re: does .newsrc merging still work?
Date: Fri, 28 May 2004 19:45:49 +0200 [thread overview]
Message-ID: <m34qq0cunm.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <m3brk8cuvt.fsf@merlin.emma.line.org> (Matthias Andree's message of "Fri, 28 May 2004 19:40:54 +0200")
Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:
>> I think it's supposed to work. Shot in the dark: It might be related
>> to the new nntp marks code. Does it help to set `nntp-marks-is-evil'
>> to t? Of course this is no solution, but maybe it helps to find the
>> bug.
>
> Doesn't appear to help (I placed it in .gnus and pressed R, for restart
> Gnus).
What's worse, it twisted my .newsrc so that tin showed already read news
as unread...
I also updated to the latest CVS just in case.
--
Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95
prev parent reply other threads:[~2004-05-28 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 19:51 Matthias Andree
2004-05-27 11:58 ` Reiner Steib
2004-05-28 17:40 ` Matthias Andree
2004-05-28 17:45 ` Matthias Andree [this message]
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=m34qq0cunm.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).