From: Maciek Pasternacki <maciekp@japhy.fnord.org>
Subject: Re: No Gnus don't get new articles after server change.
Date: Tue, 04 Oct 2005 01:52:50 +0200 [thread overview]
Message-ID: <87slvi88fh.fsf@lizard.focus.digimer.pl> (raw)
In-Reply-To: <87irwfdvic.fsf@tuxtanker.mwolson.org>
On Sweetmorn, Bureaucracy 57, 3171 YOLD, Michael Olson wrote:
> Maciek Pasternacki <maciekp@japhy.fnord.org> writes:
>
> I've had similar problems lately, using a CVS snapshot from
> 2005.10.02. I wiped my hard drive and reinstalled everything, saving
> everything important from my homedir first, especially ~/News. After
> doing so, none of my gmane groups were showing new messages as unread,
> though I could still browse them.
>
> Adding (nntp-marks-is-evil t) to the options for gnus-select-method
> seems to make things work. I had tried moving my ~/News/marks folder
> somewhere else, but this caused Gnus to throw the following error when
> starting up.
Thanks, it helped -- I didn't think of moving marks away. After
investigating contents of .marks files I managed to clear them all:
$ echo '((read))' > foo ; find ~/News/marks/news.task.gda.pl -name .marks -exec dd if=foo of={} \; -print
(news.task.gda.pl is name of my server).
Shouldn't gnus-group-clear-data clear marks files too?
--
__ Maciek Pasternacki <maciekp@japhy.fnord.org> [ http://japhy.fnord.org/ ]
`| _ |_\ / { The question is: what is a Mahnamahna?
,|{-}|}| }\/ The question is: who cares? }
\/ |____/ ( The Muppets ) -><-
next prev parent reply other threads:[~2005-10-03 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 8:59 Maciek Pasternacki
2005-10-03 5:23 ` Michael Olson
2005-10-03 23:52 ` Maciek Pasternacki [this message]
2005-10-09 22:00 ` Marks files and gnus-group-clear-data (was: No Gnus don't get new articles after server change.) Reiner Steib
2005-10-03 18:03 ` No Gnus don't get new articles after server change Michael Olson
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=87slvi88fh.fsf@lizard.focus.digimer.pl \
--to=maciekp@japhy.fnord.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).