"J. Lewis Muir" writes:
> On 11/12, Austin Clements wrote:
>> Quoth David Bremner on Nov 04 at 1:26 pm:
>> > I agree it looks like a race condition. inotify sounds a bit
>> > overcomplicated and perhaps non-portable? It should probably just
>> > tolerate disappearing files better, consider that
On 11/12, Austin Clements wrote:
> Quoth David Bremner on Nov 04 at 1:26 pm:
> > I agree it looks like a race condition. inotify sounds a bit
> > overcomplicated and perhaps non-portable? It should probably just
> > tolerate disappearing files better, consider that a warning.
>
> Inotify really *
Quoth David Bremner on Nov 04 at 1:26 pm:
>
> Paul Wise wrote:
>
> > Last night I got this errorĀ from my `notmuch new --quiet` cron job. The
> > file that the error message complains about is now in the cur directory
> > of the maildir at the following path.
> >
> > /path/to/mail/cur/1478190211.
On Fri, 2016-11-04 at 20:47 +0200, Jani Nikula wrote:
> Do you have some other software modifying your mail store while
> you're running notmuch new?
The folder in question has my laptop's exim4 service writing to it when
my cron jobs generate email.
On Fri, 2016-11-04 at 13:26 -0300, David Brem
On Fri, 04 Nov 2016, David Bremner wrote:
> I wonder if this some kind of race condition in `notmuch new`
> processing.
Do you have some other software modifying your mail store while you're
running notmuch new?
BR,
Jani.
___
notmuch mailing list
notmu
Paul Wise wrote:
> Last night I got this errorĀ from my `notmuch new --quiet` cron job. The
> file that the error message complains about is now in the cur directory
> of the maildir at the following path.
>
> /path/to/mail/cur/1478190211.H80553P18378.chianamo:2,
>
> I wonder if this some kind of