When reading an mh folder mutt 1.0.1 apparently loads every message,
and, when you quit, writes every message back to disk. (Is that true
for maildir too?) That's surely a bug, right? The whole point of
one-file-per-message formats is that you only touch the data you need
to, and leave the rest
On 2000-03-14 15:51:08 -0500, Scott Schwartz wrote:
> In my experience mh works well enough, but mutt makes
> some incorrect assumptions that have painful
> consequences.
Please look at the unstable branch (i.e., the
just-released 1.1.9). It should behave much better.
However, you may wish to
Scott Schwartz <[EMAIL PROTECTED]> wrote:
> When reading an mh folder mutt 1.0.1 apparently loads every message,
> and, when you quit, writes every message back to disk.
Well, the files have to be at least renamed, because mh requires the filenames
be contiguous integers. IIRC, the message flags
| Well, the files have to be at least renamed, because mh requires the filenames
| be contiguous integers.
No it doesn't. They usually are not.
| IIRC, the message flags are also stored inside the
| files, so mutt would have to rewrite the files to change the read, replied,
| etc flags.
It s
Thomas writes:
| However, you may wish to notice that there is still a
| problem with message flags. From the mh point of view (as
| far as I understand it), these flags should be stored in
| the .mh_sequences file - which is in paricular true for
| the unseen sequence. However, there doesn't see
On 2000-03-15 15:25:56 -0500,
[EMAIL PROTECTED] wrote:
> Yes, mh has a problem with that. The simple solution
> is just to avoid any form of concurrent access to
> folders. If you only use mh commands from the shell
> (i.e. no rcvstore), that's the case. Mutt can't be
> faulted by mh users for
Thomas Roessler writes:
| > In my experience mh works well enough, but mutt makes
| > some incorrect assumptions that have painful
| > consequences.
|
| Please look at the unstable branch (i.e., the
| just-released 1.1.9). It should behave much better.
Actually 1.1.11 behaves very badly. If yo
