unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: contovob@tcd.ie, 44464@debbugs.gnu.org
Subject: bug#44464: 28.0.50; slow shell output
Date: Thu, 05 Nov 2020 16:22:30 +0200	[thread overview]
Message-ID: <83zh3vano9.fsf@gnu.org> (raw)
In-Reply-To: <eae849fb-be36-35b5-f01c-76accad04af8@orcon.net.nz> (message from Phil Sainty on Fri, 6 Nov 2020 02:54:17 +1300)

> Cc: 44464@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
> From: Phil Sainty <psainty@orcon.net.nz>
> Date: Fri, 6 Nov 2020 02:54:17 +1300
> 
> I can reproduce the issue (in 27.1), and it seems to me that it's
> all about that one paragraph of right-to-left text.
> 
> If I disable `bidi-display-reordering', I see no slow-downs.

I don't see any particularly bad slowdown at all, but maybe I didn't
make all the steps (I don't have 'curl').  Do you see the same
slowdown if you fetch the URL with, say, WGET, and then visit it in
Emacs?  If not, how to reproduce this without 'curl'?

> Eli, I note that setting `bidi-paragraph-direction' in the buffer
> (with bidi-display-reordering enabled) does not seem to have any
> obvious effect.

It normally doesn't.  Only some very special files can benefit from
setting bidi-paragraph-direction non-nil.

> Setting it to `left-to-right', I still see right-to-left movement
> through that portion of the text, and the associated slowness.  Is
> that expected?

Yes.  Paragraph direction doesn't disable reordering, it just
determines whether the text will start at the left or the right edge
of the window.

> I'll add that the line in question is not *especially* long
> (2374 characters); however it does seem to be a significant factor,
> as enabling longlines-mode eliminates the slowness around that text.

I might be able to say something intelligent about this if I have a
recipe for reproducing the slowdown, and have some quantitative idea
of the slowdown (how much time does it take for Emacs to respond to
some specific command).

Thanks.





  reply	other threads:[~2020-11-05 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 10:47 bug#44464: 28.0.50; slow shell output Andreas Röhler
2020-11-05 10:55 ` Basil L. Contovounesios
2020-11-05 13:54   ` Phil Sainty
2020-11-05 14:22     ` Eli Zaretskii [this message]
2020-11-05 14:41       ` Basil L. Contovounesios
2020-11-05 15:54         ` Eli Zaretskii

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=83zh3vano9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=44464@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=psainty@orcon.net.nz \
    /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).