On Mon, May 13, 2013 at 10:36:07AM +0200, Vladimir Marek wrote:
Since I'm usually using several mail clients (from phone, old
mutt,
mutt-kz) it happens quite often that mutt complains.
rename: No such file or directory (errno = 2)
and the only thing I can do about it is to kill whole mutt. What I
believe is happening is that if I view unread mail, mutt remembers that
it has to move the mail once it leaves current inbox. But before that,
someone else touches the mail (probably moving the message from 'new'
directory to 'cur'. After that mutt-kz can't find the original file and
complains with the error message.
This is reason why I don't use 'notmuch new' or something like this
from crontab. All I have is notmuch-deliver which cares about one new
email only and does not try to sync whole DB.
It's really bad idea to modify on-disk data (maildirs) if you're not
able to sync in-memory cached data (mutt).
This seems to be problem in the mutt maildir handling rather than in
the
notmuch addon, still I wonder if you saw that or even better have some
plans on tackling that :)
I see this problem very very rarely (usually when I have more one
running mutts that modify the same virtual folder).
Maybe it would be possible to improve nm_sync() to read the message
path from notmuch DB before it call mh_sync_mailbox_message(). Now
the code blindly follows cached path (from nm_header_get_fullpath()).
Karel
--
Karel Zak <kzak(a)redhat.com>
http://karelzak.blogspot.com