[neomutt-users] Irritating "Unable to write" errors in neomutt

[Vikas Rawal]

Thanks for confirming the problem.

It is not possible to restart neomutt everytime you want to check mail.
That would be such a waste of time. Restarting neomutt everytime I face
this problem is the only thing one can do. It means whatever changes you
might have done, to notmuch tags for example, are lost, and one has to wait
for the new instance of neomutt to start.

This is just too bad!!

Vikas

On Sat, 22 Feb 2020 at 03:20, Greg Anders <greg at gpanders.com> wrote:

> On Fri, 21 Feb 2020 at 09:03 AM, Adrian Petrescu wrote:
> >On 02/21 11:01AM, Vikas Rawal wrote:
> >>Is this a known problem? How do people handle this?
> >
> >Yup, I've had the exact symptoms you've described since forever,
> >basically (though I use lieer instead of mbsync, it operates on the same
> >principles).
> >
> >I just restart neomutt when that happens, which is relatively rarely.
> >
> >
> >--
> >Adrian
>
> I have experienced the exact same thing. I've recently adopted the habit
> of only opening neomutt when I'm actually checking mail instead of
> leaving it open full-time, which helps with this problem.
>
> Not that that's particularly helpful to you -- just wanted to chime in
> and say that I've noticed this as well.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.neomutt.org/pipermail/neomutt-users-neomutt.org/attachments/20200222/8517de3f/attachment.html>