Brian Salter-Duke <[EMAIL PROTECTED]> wrote:
>
> Does mutt use TMPDIR? I have TMPDIR set to /var/tmp but it writes
> messages into /tmp. I do not know about the mailbox as above.
Mutt also has a "tmpdir" variable setting, which is supposed to be
initially set to $TMPDIR, but you can set it else
On Mon, Sep 20, 1999 at 05:33:04PM -0500, David DeSimone wrote:
> Brian Butler <[EMAIL PROTECTED]> wrote:
> >
> > In this case, though, something is definitely not going right because
> > the length of the mailbox file does not change and the messages which
> > were flagged deleted are still liste
Brian Butler <[EMAIL PROTECTED]> wrote:
>
> In this case, though, something is definitely not going right because
> the length of the mailbox file does not change and the messages which
> were flagged deleted are still listed and available in the same
> mailbox.
>
> Also, when the request is to '
David DeSimone <[EMAIL PROTECTED]> wrote:
> Are you certain that the mailbox is not getting fully written? Mutt has
> an optimization that makes it only update messages in the folder,
> starting from the first one that has *changed status*. That means that,
> if you only modify a message in the
Brian Butler <[EMAIL PROTECTED]> wrote:
>
> It gets to about 55% now (recently it was 73%), sits there and
> says "Writing messages... 3178 (55%)" then quits doing that and
> awaits a command. Everything seems to work like it always has,
> except the completion of the 'save' directive.
A
[attempting resend; I was rejected as a nonsubscriber from this address...]
Hello. Have had good times with mutt for years now.
Recently, with my disgustingly large /var/spool/mail box, mutt has not
completely written my mailbox after changes are made. I recognize that
the massive mailbo
