Gnus development mailing list
 help / color / mirror / Atom feed
From: "Kai Großjohann" <Kai.Grossjohann@CS.Uni-Dortmund.DE>
Subject: Re: pgnus commandeers emacs to check mail
Date: 20 Jul 1999 00:12:01 +0200	[thread overview]
Message-ID: <vafk8rwcmry.fsf@petty.cs.uni-dortmund.de> (raw)
In-Reply-To: Bill White's message of "19 Jul 1999 16:12:23 -0500"

Bill White <billw@wolfram.com> writes:

> Is there a way to make mail/news checking a completely unobtrusive
> thing? 

Hm.  Since Emacs is not multithreaded (yet), you must delegate the
process of putting mails into folders to some other program.  But
Emacs thinks it owns the ~/Mail directory (horrible things will happen
if you dare write into ~/Mail!), which makes this kinda difficult.

One way to achieve this is to use nnimap and to read mail via IMAP.  I
have configured things such that the Cyrus `deliver' programm
automatically puts mail into the right folder.  That means that, when
you hit `g', Gnus quickly scans all nnimap groups to see whether there
is new mail, and this time does not depend on the amount of new mail,
only on the number of groups.

Another way to possibly achieve it is to write into ~/Mail anyway if
you know exactly what you're doing.  I think you won't have much luck
unless you use the nnmh backend, and that is so slow compared with
nnml that this won't help you either.  And for nnfolder groups, Gnus
has the files in memory.

Btw, wouldn't it be possible to tell Gnus to have a look at the
overview files to see if the in-memory copy is still up to date before
changing anything in them?  This would kind of make it possible to use
nnml, if it weren't for race conditions.  Could some locking mechanism
be added?

kai
-- 
Life is hard and then you die.


  reply	other threads:[~1999-07-19 22:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-19 21:12 Bill White
1999-07-19 22:12 ` Kai Großjohann [this message]
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=vafk8rwcmry.fsf@petty.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).