Hi,
* Kyle Wheeler wrote:
> What I do is simply allow interrupts during socket reads. It's
> clunky, because it aborts the connection, but it gets the job done
> (see attachment).
Well, this doesn't seem too unreasonable. In case errno=EINTR, why not
make the socket functions return -1 in genera
On Friday, July 10 at 08:21 AM, quoth b a:
I understand that you enclose as much calls as you can inside
mutt_allow_interrupts(1); ... mutt_allow_interrupts(0);
How does that translate later on , how does it help ncurses or any
other code that's supposed to run run ? Your code doesn't have any
I understand that you enclose as much calls as you can inside
mutt_allow_interrupts(1); ... mutt_allow_interrupts(0);
How does that translate later on , how does it help ncurses or any
other code that's supposed to run run ?
Your code doesn't have any specific code written to exit that loop ,
it j
On Friday, July 10 at 05:24 AM, quoth b a:
When pressing to view an email with a big attachement mutt
becomes unresponsive until the message is fetched.
I've had the same complaint.
I don't like this and I will fix it in the next few days by binding
the escape key to break the loop on lines
Hi,
I came here because I have a problem with mutt and I will fix it.
When pressing to view an email with a big attachement mutt
becomes unresponsive until the message is fetched.
I don't like this and I will fix it in the next few days by binding
the escape key to break the loop on lines 463 -
