[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] Future directions for nmh

From: Paul Vixie
Subject: Re: [Nmh-workers] Future directions for nmh
Date: Wed, 16 Mar 2016 18:10:23 -0700
User-agent: Postbox 4.0.8 (Windows/20151105)

Conrad Hughes wrote:
Ken>  it makes it WORSE; each nmh command starts with a brand-new scan of a
Ken>  folder, so messages added or removed between commands work out fine.
Ken>  But a FUSE interface would have no idea when an nmh command is starting
Ken>  or stopping, so you'd have to do a lot of caching or a new IMAP session
Ken>  for each file access.

Arguably this is a problem already: all the time I have to keep in my
head that I must be careful about changing nmh state among my (usual)
four terminal windows: I'm reading one email in one folder, see
something arrive in another folder, look at that in another window, go
back to the first window, decide the original message is irrelevant and
rmm it — except now I'm rmm'ing something else in another folder because
I switched context in the other window.

i make liberal use of -nochangecur in all my non-interactive use of MH, so that my interactive use won't produce the result you're describing.

P Vixie

reply via email to

[Prev in Thread] Current Thread [Next in Thread]