From: Chong Yidong <cyd@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10835@debbugs.gnu.org
Subject: bug#10835: 24.0.93; bidi-paragraph-direction slows down Shell mode
Date: Sun, 19 Feb 2012 22:07:24 +0800 [thread overview]
Message-ID: <87y5ry29yb.fsf@gnu.org> (raw)
In-Reply-To: <83y5s0v84w.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 18 Feb 2012 10:49:19 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Yes, the overlays together with the long search for paragraph
> beginning probably push the user experience from slightly below the
> annoyance threshold to just above it.
> ...
> How about setting bidi-paragraph-direction in comint buffers to
> left-to-right when the locale indicates that use of bidirectional
> scripts is unlikely? We could use locale-language-names and an
> additional small database of languages that need bidi, to make that
> decision. WDYT?
I'm not keen on bolting on this additional complexity.
I don't see any better way out, so we might as well take the risk and
switch to using text properties for color escape highlighting. I just
committed a patch to do that, limiting the change to Shell mode and
leaving the other users of ansi-color.el unaffected (and still using
overlays).
Thanks for helping with this bug. Hopefully the fix won't turn up any
problems...
next prev parent reply other threads:[~2012-02-19 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 5:41 bug#10835: 24.0.93; bidi-paragraph-direction slows down Shell mode Chong Yidong
2012-02-17 5:48 ` Chong Yidong
2012-02-17 8:21 ` Andreas Schwab
2012-02-17 13:42 ` Chong Yidong
2012-02-17 16:08 ` Eli Zaretskii
2012-02-17 17:39 ` Chong Yidong
2012-02-17 18:27 ` Eli Zaretskii
2012-02-18 2:28 ` Chong Yidong
2012-02-18 3:37 ` Chong Yidong
2012-02-18 8:49 ` Eli Zaretskii
2012-02-18 14:14 ` Eli Zaretskii
2012-02-19 14:07 ` Chong Yidong [this message]
2012-02-18 8:27 ` 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=87y5ry29yb.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=10835@debbugs.gnu.org \
--cc=eliz@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.