On 1999-03-31 11:07:13 -0800, Andrew Bell [4036] wrote:
> I noticed that if one's current dir does not exist (ie. remove an
> interactive shell's CWD in another shell), mutt will only open the
> user's mailbox(es) read-only -- regardless of the directory in
> question. Why would this be the case if '.' is not a meaningful
> dir to mutt?
This is related to the inner workings of mutt's dotlocking code. To
avoid some possible race conditions, mutt has to chdir() into the
directory in which the file to be locked resides. Afterwards, mutt
tries to use fchdir() to the directory it started from.
For this to work, mutt has to open the current directory (".") at
some point. If this fails, dotlocking will fail which leads to the
effect you observed.
To work around this, try forcing the use of an external dotlock
program. In unstable, we have an --enable-external-dotlock
configure option. I'm not sure if it's also in stable - don't have
access to the stable source and to the CVS right now.
tlr
--
http://home.pages.de/~roessler/
