From: Michael Olson <mwolson@member.fsf.org>
Subject: Re: No Gnus don't get new articles after server change.
Date: Mon, 03 Oct 2005 13:03:10 -0500 [thread overview]
Message-ID: <871x32wk9t.fsf@tuxtanker.mwolson.org> (raw)
In-Reply-To: <87psqsqmfk.fsf@lizard.king> (Maciek Pasternacki's message of "Thu, 29 Sep 2005 10:59:27 +0200")
[-- Attachment #1: Type: text/plain, Size: 2201 bytes --]
Maciek Pasternacki <maciekp@japhy.fnord.org> writes:
> I use No Gnus (CVS checkout now from a few days ago) on GNU Emacs 22
> (fresh checkout too). Some time ago my primary Usenet server
> crashed and was reinstalled, and article numbers were lost. From
> that time on whatever I do with Gnus to rehash article numbers, it
> doesn't see new articles when offline. I.e. I start up Gnus, see all
> groups on native server caught up (no new articles) (on other NNTP
> servers I do see other articles, so do I get mail via nnmail). When
> after some time I hit `g', Gnus gets new articles -- but only those
> that were sent after Gnus was started. I can use groups normally
> while Gnus is on; then I quit Emacs and when I start Gnus again,
> there are no unread articles on all native groups (even if I left
> some unread ones when quitting Gnus -- those are caught-up too).
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.
Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
time-less-p((17205 37218) nil)
nntp-marks-changed-p("gmane.emacs.xtla.devel" "localhost")
nntp-request-update-info("gmane.emacs.xtla.devel" ("gmane.emacs.xtla.devel" 3 ((1 . 31)) ((seen ...))) "localhost")
gnus-get-unread-articles(nil)
gnus-setup-news(nil nil nil)
byte-code("[snip]")
gnus-1(nil nil nil)
gnus(nil)
call-interactively(gnus)
execute-extended-command(nil)
call-interactively(execute-extended-command)
--
Michael Olson -- FSF Associate Member #652 -- http://www.mwolson.org/
Interests: anime, Debian, XHTML, wiki, Emacs Lisp
/` |\ | | | IRC: mwolson on freenode.net: #hcoop, #muse, #PurdueLUG
|_] | \| |_| Jabber: mwolson_at_hcoop.net
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2005-10-03 18:03 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
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 ` Michael Olson [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=871x32wk9t.fsf@tuxtanker.mwolson.org \
--to=mwolson@member.fsf.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).