Re: Danger! Marks for nntp.el

[Kai Grossjohann <kai@emptydomain.de>]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

>>>>>> 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

Okay.  Another try...

>>>>>> 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':

I've now removed the call to nntp-possibly-change-group.  Better?

I'll test more when I'm back at home.  Sorry for all the trouble.

Kai