From: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org
Subject: Re: "Async fetch" failing in current CVS
Date: 13 Jul 2000 15:07:22 +0200 [thread overview]
Message-ID: <iluwviqxjp1.fsf@localhost.localdomain> (raw)
In-Reply-To: Ulrich Schwarz's message of "Tue, 11 Jul 2000 21:44:43 +0200"
Ulrich Schwarz <uschwarz@gmx.net> writes:
> > - (nntp-handle-authinfo nntp-process-to-buffer)
> > + (nntp-handle-authinfo process)
>
> It doesn't help for me (running Linux).
> Despite applying the patch I still get frequently error messages like:
>
> Signaling: (error "Buffer *Async Prefetch Article* has no process")
> process-send-string(#<buffer " *Async Prefetch Article*"> "ARTICLE 77379
> \n")
> nntp-handle-authinfo(#<buffer " *Async Prefetch Article*">)
> nntp-async-trigger(#<network connection "nntpd<1>" ("nntp" . "news.cis.dfn.de") state:run>)
> nntp-after-change-function(1 80 0)
It doesn't look like the patch was used, make sure you've recompiled
and/or reloaded nntp.el.
By the backtrace, it looks like it used to -- the patch make
`nntp-async-trigger' pass it's first argument to
`nntp-handle-authinfo' instead of a buffer, but it looks like you
still have the old behaviour.
> Apart from that, pgnus sometimes waits eternally for an article to
> be fetched asynchroneously - you have to press Control-G to free Gnus again.
Perhaps the asynchronous support should be disabled then, unless
someone is able to debug this and come up with a patch.
prev parent reply other threads:[~2000-07-13 13:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-10 22:46 Dan McGuirk
2000-07-11 8:48 ` Simon Josefsson
2000-07-11 9:11 ` Michael Klingbeil
2000-07-11 10:32 ` Simon Josefsson
2000-07-11 11:17 ` Michael Klingbeil
2000-07-11 12:46 ` Simon Josefsson
2000-07-11 15:05 ` Dan McGuirk
2000-07-11 19:44 ` Ulrich Schwarz
2000-07-12 8:27 ` Wolfgang Schludi
2000-07-13 13:07 ` Simon Josefsson [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=iluwviqxjp1.fsf@localhost.localdomain \
--to=simon@josefsson.org \
--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).