From: Bill White <billw@wolfram.com>
Subject: pgnus commandeers emacs to check mail
Date: 19 Jul 1999 16:12:23 -0500 [thread overview]
Message-ID: <ruozp0s739k.fsf@g.wolfram.com> (raw)
Sounds like a newspaper headline.
This is about my only continuing gripe with gnus:
When pgnus checks for new mail/news, I can't do anything in that
invocation of emacs until pgnus finishes. Keyboard input is
accumulated until then. When our news server is slow or if there's a
boatload of email to download, emacs can be useless for quite a while.
This happens with 'g' in the *Group* buffer, and also with the
automatic "check mail/news and update *Group* buffer" function in
.gnus:
; Posted to ding or gnu.emacs.gnus long ago...
; The catch with gnus-demon-scanmail seems to be that the Group buffer
; doesn't get updated when the mail is fetched (so nothing actually
; appears to happen). I do this instead:
(gnus-demon-add-handler (lambda () (gnus-group-get-new-news t)) 10 nil)
Is there a way to make mail/news checking a completely unobtrusive
thing?
Pterodactyl Gnus v0.95, GNU Emacs 20.4.1 (i586-pc-linux-gnu, X
toolkit) of Fri Jul 16 1999 on g.wolfram.com
This was also seen in Emacs 20.3 and all the 20.4 prereleases.
Thanks -
bw
--
Bill White . billw@wolfram.com . http://members.wri.com/billw
next reply other threads:[~1999-07-19 21:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-19 21:12 Bill White [this message]
1999-07-19 22:12 ` Kai Großjohann
1999-07-21 20:32 ` Greg Stark
1999-07-22 10:07 ` Hrvoje Niksic
1999-07-22 11:57 ` Michael Sperber [Mr. Preprocessor]
1999-07-20 0:19 ` Stainless Steel Rat
1999-07-20 0:49 ` Bill White
1999-07-20 17:16 ` Rajesh Godbole
1999-07-20 18:02 ` Kai Großjohann
1999-07-21 10:50 ` Hrvoje Niksic
1999-07-21 11:11 ` Kai Großjohann
1999-07-21 11:35 ` Didier Verna
1999-07-28 12:27 ` Robert Bihlmeyer
1999-07-22 10:09 ` Hrvoje Niksic
1999-07-20 19:07 ` Olivier Galibert
1999-07-20 23:31 ` Rajesh Godbole
1999-07-21 6:18 ` Michael Sperber [Mr. Preprocessor]
1999-07-21 15:06 ` Karl M. Hegbloom
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=ruozp0s739k.fsf@g.wolfram.com \
--to=billw@wolfram.com \
/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).