IPE leads to it failing
to report that the IMAP connection had closed and it can sit unresponsive to
user input for many seconds, when instead it should be able to report closed
connections earlier from SIGPIPE. I did not run this down, and presumably
closed connections will be much more rare in my l
ng that without
putting low-level signal code around relatively high-level stuff in
mutt_view_attachment, or complicating the abstraction further, but I have no
objection if you can come up with something better.
Certainly I'm not in any rush -- having suffered for the better part of a year
and with a fix for the big problem in my config file and the small problem in
my build tree, I'm happy to wait :)
--jh...@mit.edu
John Hawkinson
the "Press any key to continue..." prompt for more than the
IMAP timeout.
IMAP connection times out. I guess the problem is mutt_any_key_to_continue().
I wonder how many of these problems there are :(
--jh...@mit.edu
John Hawkinson
Kevin J. McCarthy wrote on Mon, 17 Sep
utt needs to worry about overmuch.
> Cameron (or anyone else on MacOS), can you confirm ':' is allowed for files
> on your system, especially those created from a shell or launched by Mutt
> via mailcap?
Confirmed.
And this is not a recent change. It has been ever thus since
mutt development
commits closely enough so maybe I'm being unreasonable to expect documentation
at the same time as a feature is committed.
--
jh...@alum.mit.edu
John Hawkinson
Vincent Lefevre wrote on Thu, 13 Jan 2022
at 21:31:27 EST in <20220114023127.gc131...@zira.vinc17.org>:
other affects critical message metadata that is often
displayed in abbreviated form. And for a given message, many more people read
(or try to read the parsed version of) the Subject: than the body.
But I don't feel as strongly as Vincent, I just think the argument should be a
bit more...grounded.
--
jh...@alum.mit.edu
John Hawkinson
