Re: limitation in how emacs processes subprocess output, maybe belongs to mainstream

[Tyler Dodge <tyler@tdodge.consulting>]

Hi Robert,

Thanks for reaching out. I’d love to sign over the copyright for this. Please let me know what you all need from my end to facilitate that.

Tyler Dodge

> On May 25, 2022, at 9:23 AM, Robert Pluim <rpluim@gmail.com> wrote:
> 
> 
>> 
>>>>>> On Wed, 25 May 2022 15:10:55 +0300, Jean Louis <bugs@gnu.support> said:
> 
>    Jean> I have read in Emacs News by Sacha Chua, about this Eshell speed up:
>    Jean> From 70 Seconds To 3 Seconds
>    Jean> https://tdodge.consulting/blog/eshell/background-output-thread
> 
>    Jean> and the fork of Emacs is here:
> 
>    Jean> GitHub - tyler-dodge/emacs: Fork of emacs mirror Emacs. Has a
>    Jean> background thread optimization for getting past the 1024 byte
>    Jean> bottleneck on MacOS
>    Jean> https://github.com/tyler-dodge/emacs
> 
>    Jean> Where author writes:
> 
>>> In a change that I made to my fork of emacs, I added a background
>>> thread that continuously handles buffering subprocess output. This
>>> has the benefit of ensuring that the subprocess output is consumed
>>> as soon as it is available in STDOUT, which minimizes the amount of
>>> time that the subprocess blocks waiting for emacs to consume its
>>> output. This also makes it so that the strings passed to the
>>> subprocess filter can be larger than 1024 bytes because multiple
>>> reads can happen in the time between event loop evaluations.
> 
>    Jean> Maybe developers and author may find it useful to implement author's
>    Jean> feature in the main stream Emacs?
> 
> Maybe. What's the copyright status of those changes?
> 
> Thanks
> 
> Robert
> --