Subject: bug#79367: 31.0.50; magit-commit sometimes doesn't work if diff-hl-update-async is t

From: Eli Zaretskii <[email-masked]>
Date: Wed, 03 Sep 2025 14:57:13 +0300

> Date: Wed, 3 Sep 2025 00:21:09 +0300
> From: Dmitry Gutov <[email-masked]>
> Cc: [email-masked], [email-masked], [email-masked]
> 
> On 02/09/2025 22:45, Dmitry Gutov wrote:
> > We need a fuller scenario. If not with code, then a full use case 
> > described in English.
> 
> Maybe to start something, do we expect some Comint functionality to be 
> broken when background threads exist and perhaps call 
> 'accept-process-output' with nil, in a loop?
> 
> Such as comint-redirect-results-list-from-process or comint-proc-query, 
> for example.

If the process is locked to the thread which runs
comint-redirect-results-list-from-process, I wouldn't expect problems
there.  But it would be good for someone to look into this, sure.

> Or among third party code, inf-ruby-completions. All of these call 
> 'accept-process-output' with their own process object.

Same, I think.