unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Herman@debbugs.gnu.org, Géza <geza.herman@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44007@debbugs.gnu.org, "Herman Géza" <geza.herman@gmail.com>
Subject: bug#44007: 26.3; Strange shell mode performance
Date: Mon, 06 Nov 2023 13:28:15 +0100	[thread overview]
Message-ID: <87bkc73uk4.fsf@gmail.com> (raw)
In-Reply-To: <83v8af2iey.fsf@gnu.org>


Eli Zaretskii <eliz@gnu.org> writes:

> I'm not sure what exactly are we trying to do here.  AFAIU, at 
> least 2
> variables were discovered that can speed up this example, so 
> what else
> has to be done?  Is there any bug here, and if so, what is the 
> bug?

The bug is that if echo is enabled, emacs 'shell' gives a much 
worse performance.  And it has no apparent reason why it should be 
the case.

Also, there is weird behavior around event handling (why does a 
RET speed up I/O?).  I think that this behavior suggests that 
there is some bug in Emacs.  At least I don't consider this a 
normal behavior.

I don't think that the solution is that zsh users should set these 
variables.  It makes much more sense to fix Emacs so this doesn't 
happen in the first place.

I'd like to also mention that my hacky solution not just fixes the 
problem, but also improves shell's performance, even with the 
mentioned variables set.  As far as I know POSIX programming, 
read() should always be called in a loop, if one wants to read N 
bytes (even in the successful case).  Emacs doesn't have this in 
emacs_intr_read, that causes the problem.





  reply	other threads:[~2023-11-06 12:28 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bkc73uk4.fsf@gmail.com \
    --to=herman@debbugs.gnu.org \
    --cc=44007@debbugs.gnu.org \
    --cc=eliz@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).