From: Leo <sdl.web@gmail.com>
Cc: ding@gnus.org
Subject: Re: gnus makes emacs lose response
Date: Tue, 26 Sep 2006 20:20:43 +0100 [thread overview]
Message-ID: <m3mz8migdw.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: <87mz8mfqkr.fsf@stupidchicken.com>
On Tue, 09/26/2006 19:08 +0100, Chong Yidong wrote:
> Leo <sdl.web@gmail.com> writes:
>
>> The ChangeLog says it's fixed. But I can't see the actually
>> fix. gnus-demon.el has not been changed for 7 month.
>
> Hmm, I could have sworn I checked it in; oh well. I really did check
> it in this time.
Thanks.
I can see the change now.
--
Leo
next prev parent reply other threads:[~2006-09-26 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-23 18:18 Chong Yidong
2006-09-23 23:42 ` Luc Teirlinck
2006-09-26 17:26 ` Leo
2006-09-26 18:08 ` Chong Yidong
2006-09-26 19:20 ` Leo [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-06 20:41 Dave Love
2006-03-29 23:02 [sdl.web@gmail.com: gnus makes emacs lose response] Richard Stallman
2006-04-05 18:30 ` Dave Love
2006-04-06 15:37 ` Richard Stallman
2006-04-06 16:43 ` gnus makes emacs lose response 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=m3mz8migdw.fsf@sl392.st-edmunds.cam.ac.uk \
--to=sdl.web@gmail.com \
--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).