From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: nnrss often hangs recent CVS Emacs
Date: Wed, 12 Jan 2005 20:31:03 +0900 [thread overview]
Message-ID: <b9ywtuiyjd4.fsf@jpl.org> (raw)
In-Reply-To: <864qho9de1.fsf@oumu.localdomain>
>>>>> In <864qho9de1.fsf@oumu.localdomain> Adam Duck wrote:
> Ah, that's very good, this fixes the bug. Although I can't possibly
> think of a _why_ this is happening -- which, sort of, explains "for
> unexplained reasons"... And you really don't see it when you mark
> multiple rss-feeds and press "M-g"? When I have only one feed to
> update, I don't see it either.
Hm, there's no problem when I press M-g after marking a couple
of nnrss groups.
> But, I think I said it before: when emacs loses focus it doesn't
> output this much (meaning a name of a feed stays in the minibuffer
> while gnus is already updating other feeds).
I'm inexperienced in such a phenomenon but I guess it is caused
by the timer processes (which mm-url.el uses) or the asynchronous
operations of the url ELisp package. Unfortunately, I'm not
familiar with those any.
>> Another solution is not to use the url ELisp package. To do
>> that, use the following:
>>
>> (setq mm-url-use-external t)
> Yes, it's faster, too. But:
> 1) I don't get any output which states which feed gnus is
> updating (minor one).
> 2) If a feed doesn't succeed, gnus stops (bad). Is there an option
> for this?
I have no idea, sorry. Anyway, I've ticked this thread. I'll
inform whatever I notice.
BTW, I am, so to speak, a new nnrss user and need to gain
experiences. Now I'm trying it only in the office (behind the
proxy server), but I will have to do it in home (no proxy) as
well.
next prev parent reply other threads:[~2005-01-12 11:31 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
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 [this message]
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=b9ywtuiyjd4.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).