From: Eli Zaretskii <eliz@gnu.org>
To: bojohan@gnu.org, 9771@debbugs.gnu.org
Subject: bug#9771: 24.0.90; Redisplay problems with control characters
Date: Mon, 17 Oct 2011 10:18:42 -0400 [thread overview]
Message-ID: <E1RFo1a-00079e-Kw@fencepost.gnu.org> (raw)
In-Reply-To: <E1RFhvv-0002JH-Ql@fencepost.gnu.org> (message from Eli Zaretskii on Mon, 17 Oct 2011 03:48:27 -0400)
> Date: Mon, 17 Oct 2011 03:48:27 -0400
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 9771@debbugs.gnu.org
>
> > 3. Long lines with display vectors make Emacs really slow (with bidi)
>
> It's not the display vectors in general that cause this. It's
> specifically the display of control characters.
The reason for the slowness is the bidirectional property of the
control characters, and a peculiarity of the UBA, the Unicode
Bidirectional Algorithms, regarding the processing of sequences of
characters with that particular property. In the particular case in
point, it causes Emacs to search to the end of the long line, when it
is about to display the first null character.
So now this question becomes very relevant:
> is there some real-life use case behind your recipe?
Depending on the answer, it may or may not be a good idea to look for
some heuristics for this case before 24.1 is released, because AFAICS
the current implementation of the UBA requirements is correct.
next prev parent reply other threads:[~2011-10-17 14:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 22:24 bug#9771: 24.0.90; Redisplay problems with control characters Johan Bockgård
2011-10-17 7:48 ` Eli Zaretskii
2011-10-17 14:18 ` Eli Zaretskii [this message]
2011-10-17 21:04 ` Johan Bockgård
2011-10-18 12:56 ` Eli Zaretskii
2011-10-18 16:58 ` Eli Zaretskii
2011-10-20 12:43 ` Eli Zaretskii
2011-10-19 1:06 ` Johan Bockgård
2011-10-19 11:49 ` Eli Zaretskii
2011-10-17 17:06 ` Eli Zaretskii
2011-10-17 19:16 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1RFo1a-00079e-Kw@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=9771@debbugs.gnu.org \
--cc=bojohan@gnu.org \
/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.