<<< Date Index >>>     <<< Thread Index >>>

Re: why isn't mutt threaded (logically)



On 03/04/05 09.42, Charles Cazabon wrote:
> Craig Millar <mutt@xxxxxxxxxxxxxxxx> wrote:
> > been using mutt for a couple of weeks and i don't see myself looking back.
> > the only complaint i have is that when it polls a server (i have several 
> > imap
> > accounts) that takes a while to respond, it freezes until it has had a
> > response. why is such a well respected mail client so monolithic and
> > incapable of multitasking?
> 
> Well, applications aren't supposed to "multitask"; your OS already does all
> that already.  So what you do is run mutt, and have getmail retrieving your
> mail in the background as a separate application (i.e., run it as a cronjob or
> whatever).  mutt's built-in POP retrieval is a bit of an anomaly versus the
> rest of its design.

That works reasonably well with pop, but Craig said he uses imap. With
imap it is a lot more reasonable for mutt to talk directly to the
server, and the resulting stalls are real and can be annoying,
especially when one is not on the same lan as the server.

Given mutts userinterface it is reasonable for there to be a bit of a
wait when swithcing folder, since lots of data might need to be
downloaded. But it would be nice if the checking for new mails could
be done in a seperate thread, or otherwise decoupled (I have not
looked into how mutt does it, but it doesn't feel like threads). It
would also bee nice if mutt could continue to talk to the server while
waiting for an external editor or an internal prompt, both has lost me
the connection to the imap server on occasion.

But unless/untill somebody with the time and the know-how to fix this
gets irritated enough...

/dossen
-- 
Common sense is the collection of prejudices acquired by age eighteen.
                -- Albert Einstein

Attachment: pgpJyvyVz4bgv.pgp
Description: PGP signature