From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Danger! Marks for nntp.el
Date: Fri, 14 May 2004 19:34:25 +0900 [thread overview]
Message-ID: <b9yk6zfnvpq.fsf@jpl.org> (raw)
In-Reply-To: <87wu3fbc07.fsf@emptyhost.emptydomain.de>
>>>>> In <871xlncql9.fsf@emptyhost.emptydomain.de>
>>>>> Kai Grossjohann <kai@emptydomain.de> wrote:
> Okay, now it's committed. Better now?
Thanks. However, it still warned as:
>> While compiling nntp-marks-changed-p in file /Work/gnus/lisp/nntp.el:
>> ** reference to free variable server
>>>>> In <87wu3fbc07.fsf@emptyhost.emptydomain.de>
>>>>> Kai Grossjohann <kai@emptydomain.de> wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> Even if I set nntp-marks-is-evil as t, it takes a long time to
>> fetch new mails. I'm using nnml and subscribing to a lot of
>> nntp groups. I haven't investigated yet what is wrong. Sorry.
> Whee. I'm somewhat surprised that nntp-marks affects nnml.
There is no problem if there is no nntp groups (i.e., using
gnus-no-server) or all nntp connections are open and active.
However, if one or more connections are closed (because of
server's timeout), Gnus seems to try to open those connections.
Here is a backtrace gotten when I typed C-g while getting new
mails using `1 g':
Debugger entered--Lisp error: (quit)
signal(quit nil)
[...]
nntp-open-connection(#<buffer *nntpd*>)
[...]
nntp-possibly-change-group("gnus.ding" "quimby")
nntp-request-update-info("gnus.ding" ("nntp+quimby:gnus.ding" 4 ((1 . 52959))...
gnus-get-unread-articles(1)
gnus-group-get-new-news(1)
call-interactively(gnus-group-get-new-news)
The group level for all the nntp+quimby newsgroups is 4.
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2004-05-14 10:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 17:57 Kai Grossjohann
2004-05-13 22:25 ` Katsumi Yamaoka
2004-05-14 3:07 ` Katsumi Yamaoka
2004-05-14 9:20 ` Kai Grossjohann
2004-05-14 10:34 ` Katsumi Yamaoka [this message]
2004-05-14 11:52 ` Kai Grossjohann
2004-05-14 12:18 ` Katsumi Yamaoka
2004-05-19 1:00 ` Katsumi Yamaoka
2004-05-20 23:50 ` Katsumi Yamaoka
2004-05-21 0:34 ` Katsumi Yamaoka
2004-05-14 9:20 ` Kai Grossjohann
2004-05-18 13:15 ` Reiner Steib
2004-05-18 13:54 ` Kai Grossjohann
2004-05-18 14:35 ` Reiner Steib
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=b9yk6zfnvpq.fsf@jpl.org \
--to=yamaoka@jpl.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).