From: Stephen Berman via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 69385@debbugs.gnu.org
Subject: bug#69385: 30.0.50; Long lines with bidi text slow down Emacs
Date: Mon, 26 Feb 2024 16:17:38 +0100 [thread overview]
Message-ID: <87sf1ffe5p.fsf@gmx.net> (raw)
In-Reply-To: <86v86bux3w.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 26 Feb 2024 16:19:15 +0200")
On Mon, 26 Feb 2024 16:19:15 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: 69385@debbugs.gnu.org
>> Date: Mon, 26 Feb 2024 15:13:38 +0100
>>
>> On Mon, 26 Feb 2024 14:33:18 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
[...]
>> > If, after starting Emacs, you set all the entries of Arabic characters
>> > in composition-function-table to nil (e.g., using
>> > set-char-table-range), do you see significant speedup?
>>
>> Yes, there is a noticeable speedup when M-> and C-v, M-v, and even
>> holding down C-n and C-p is faster, though they still freeze after a few
>> seconds, but the freeze doesn't last as long as when it happens with the
>> shaped Arabic script. Also, probably unsurprisingly, the speed after
>> disabling shaping is still much slower than keeping shaping enabled but
>> setting bidi-display-reordering to nil.
>
> Is this with text from HELLO, or with some other Arabic text? The
> prominent effect of bidi-display-reordering is actually surprising,
> and not what I see here, with or without shaping. Very strange.
All my tests in this thread have been with the Arabic example text in
HELLO, though the file with which I first noticed the slowdown contains
much more and different Arabic text, as well as ASCII and non-ASCII
characters without shaping. Here, the speed difference, when executing
movement and other commands in a buffer with a long line of
bidirectional text containing shaped Arabic, between
bidi-display-reordering t and nil is like night and day. If it's not
that way for you I can only assume it's due to another factor
distinguishing our systems that hasn't yet been identified.
Steve Berman
prev parent reply other threads:[~2024-02-26 15:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 16:23 bug#69385: 30.0.50; Long lines with bidi text slow down Emacs Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-25 17:06 ` Eli Zaretskii
2024-02-25 18:03 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-25 19:31 ` Eli Zaretskii
2024-02-25 20:36 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-26 12:33 ` Eli Zaretskii
2024-02-26 14:13 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-26 14:19 ` Eli Zaretskii
2024-02-26 14:22 ` Eli Zaretskii
2024-02-26 15:17 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-26 15:52 ` Eli Zaretskii
2024-02-26 15:59 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-26 16:36 ` Eli Zaretskii
2024-02-26 17:12 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-26 19:18 ` Eli Zaretskii
2024-02-26 21:47 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-27 8:52 ` Eli Zaretskii
2024-02-27 10:13 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-03 15:18 ` Eli Zaretskii
2024-03-04 13:28 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-04 14:43 ` Eli Zaretskii
2024-03-07 11:12 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 11:25 ` Eli Zaretskii
2024-03-21 8:29 ` Eli Zaretskii
2024-03-21 15:08 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-26 15:17 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=87sf1ffe5p.fsf@gmx.net \
--to=bug-gnu-emacs@gnu.org \
--cc=69385@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stephen.berman@gmx.net \
/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).