From: Mark Plaksin <happy@mcplaksin.org>
Subject: Re: nnrss often hangs recent CVS Emacs
Date: Fri, 07 Jan 2005 12:07:03 -0500 [thread overview]
Message-ID: <m3brc12mo8.fsf@water.tss.usg.edu> (raw)
In-Reply-To: <87pt0hyzdv.fsf@mid.packer.its.vanderbilt.edu>
"Andrew A. Raines" <aaraines@pobox.com> writes:
> I switched a few days ago to Emacs 21.3.50 from 21.3.1.
> Gnus seems to like the newer environment. Things seem
> much smoother and updates to the group buffer when
> fetching mail and news are quicker.
>
> nnrss, however, works intermittently. Often when updating
> a group, Emacs will hang indefinitely. I mean _really_
> hang -- if I have an external process going in the
> background (like mplayer through EMMS), the track will
> pause, and if I let Gnus run through its course (something
> eventually times out I guess), my erc sessions get
> disconnected.
A while back I traced this problem to make-network-process. But I'm not
sure that's the problem any more. nnrss uses the url package which uses
make-network-process. Unless you give it the nowait option (which the url
package doesn't), make-network-process blocks until it makes a connection
or a timeout occurs. That seemed to explian it.
Recently I tried to reproduce the problem (by calling make-network-process
directly) and C-g always interrupted it. So maybe the problem is gone in
the latest CVS Emacs. I'm running on Linux; it might be a different story
on Windows.
If you happen to be using the multi-tty branch, C-g only interrupts
make-network-stream when you're in the initial Emacs window. For some
reason it doesn't interrupt it in subsequent windows.
next prev parent reply other threads:[~2005-01-07 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 16:31 Andrew A. Raines
2005-01-07 17:07 ` Mark Plaksin [this message]
2005-01-07 22:37 ` Adam Duck
2005-01-08 21:39 ` Dan Christensen
2005-01-10 19:32 ` Andrew A. Raines
2005-01-11 6:21 ` Katsumi Yamaoka
2005-01-11 15:47 ` Adam Duck
2005-01-12 11:31 ` Katsumi Yamaoka
2005-01-11 17:00 ` Andrew A. Raines
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=m3brc12mo8.fsf@water.tss.usg.edu \
--to=happy@mcplaksin.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).