From: Robert Pluim <rpluim@gmail.com>
To: Jean Louis <bugs@gnu.support>
Cc: Emacs Developers <emacs-devel@gnu.org>,
"Tyler Dodge" <tyler@tdodge.consulting>
Subject: Re: limitation in how emacs processes subprocess output, maybe belongs to mainstream
Date: Wed, 25 May 2022 18:23:55 +0200 [thread overview]
Message-ID: <875yltzilg.fsf@gmail.com> (raw)
In-Reply-To: <courier.00000000628E1CE9.000058D8@stw1.rcdrun.com> (Jean Louis's message of "Wed, 25 May 2022 15:10:55 +0300")
>>>>> 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
--
next prev parent reply other threads:[~2022-05-25 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 12:10 limitation in how emacs processes subprocess output, maybe belongs to mainstream Jean Louis
2022-05-25 16:23 ` Robert Pluim [this message]
2022-05-25 20:18 ` Tyler Dodge
2022-05-26 5:36 ` Eli Zaretskii
2022-06-03 9:44 ` Robert Pluim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yltzilg.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=tyler@tdodge.consulting \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.