From: Eli Zaretskii <eliz@gnu.org>
To: Herman@debbugs.gnu.org, Géza <geza.herman@gmail.com>
Cc: 44007@debbugs.gnu.org
Subject: bug#44007: 26.3; Strange shell mode performance
Date: Fri, 16 Oct 2020 13:55:02 +0300 [thread overview]
Message-ID: <831rhywid5.fsf@gnu.org> (raw)
In-Reply-To: <3ed7855d-9c95-b56f-7abd-db2c6bd9647b@gmail.com> (Herman@debbugs.gnu.org)
> From: Herman@debbugs.gnu.org, Géza <geza.herman@gmail.com>
> Date: Fri, 16 Oct 2020 12:44:32 +0200
>
> It reproduces for me, both 26.3 and 28.0.50. And both for the X and
> console version (by console version, I mean the usual version, but with
> DISPLAY unset).
>
> I attached a text file (hopefully it gets through).
>
> cat-ing this file takes ~18 sec. But with enter, it takes just ~3 sec
> (these measurements are done with the console version). It behaves like
> this 100% of the time (it's a more reliable test than the "seq" test).
Does it help to play with the value of process-adaptive-read-buffering?
Or with read-process-output-max?
next prev parent reply other threads:[~2020-10-16 10:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 9:53 bug#44007: 26.3; Strange shell mode performance Herman, Géza
2020-10-15 14:10 ` Eli Zaretskii
2020-10-15 14:34 ` Herman, Geza
2020-10-16 8:25 ` Andreas Röhler
2022-01-28 15:26 ` Lars Ingebrigtsen
2022-01-28 22:33 ` Herman, Géza
2022-01-29 6:52 ` Eli Zaretskii
2022-01-29 14:38 ` Lars Ingebrigtsen
2022-01-29 16:10 ` Herman, Géza
2023-11-05 16:46 ` Herman, Géza
2023-11-06 12:08 ` Eli Zaretskii
2023-11-06 12:28 ` Herman, Géza
2023-11-06 13:22 ` Eli Zaretskii
2023-11-06 13:37 ` Herman, Géza
2023-11-06 14:40 ` Eli Zaretskii
2023-11-06 15:00 ` Herman, Géza
2023-11-06 16:52 ` Eli Zaretskii
2023-11-06 17:25 ` Herman, Géza
2023-11-06 22:47 ` Dmitry Gutov
2020-10-16 10:44 ` Herman, Géza
2020-10-16 10:55 ` Eli Zaretskii [this message]
2020-10-16 12:23 ` Herman, Géza
2020-10-17 12:48 ` Herman, Géza
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=831rhywid5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44007@debbugs.gnu.org \
--cc=Herman@debbugs.gnu.org \
--cc=geza.herman@gmail.com \
/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.