From: Chong Yidong <cyd@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Setting bidi-paragraph-direction in comint modes
Date: Wed, 15 Feb 2012 14:24:11 +0800 [thread overview]
Message-ID: <87k43ovcl0.fsf@gnu.org> (raw)
In-Reply-To: <83zkckwxrg.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 15 Feb 2012 06:01:23 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Chong Yidong <cyd@gnu.org>
>> Cc: emacs-devel@gnu.org
>> Date: Wed, 15 Feb 2012 08:49:18 +0800
>>
>> Like I said, it's simply `ls /usr/share/doc'.
>
> You mean, the insertion of the next chunk of text that arrives from
> `ls'?
Yep.
> I didn't look at the insertion itself, I tried the various cursor
> motion commands _after_ the output from `ls' was already in the
> buffer. Do you see the "crawl" there as well?
Yep. After inserting about 7000 lines into the *shell* buffer, as
described, press and hold down M-v (or PageUp) for several seconds.
Redisplay freezes, not updating until about two seconds after the key is
released. Then it updates the screen with the new cursor position. But
if bidi-paragraph-direction is set to 'left-to-right, the display
updates in real time as I press and hold M-v.
> Can you quantify it? Like, how much time it takes to insert the first
> 2000 lines vs the last?
Not easily, but it is definitely not my imagination. You can't
reproduce the problem at all?
next prev parent reply other threads:[~2012-02-15 6:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 6:35 Setting bidi-paragraph-direction in comint modes Chong Yidong
2012-02-14 17:52 ` Stefan Monnier
2012-02-14 17:55 ` Eli Zaretskii
2012-02-15 0:49 ` Chong Yidong
2012-02-15 4:01 ` Eli Zaretskii
2012-02-15 6:24 ` Chong Yidong [this message]
2012-02-15 17:01 ` Eli Zaretskii
2012-02-17 5:44 ` Chong Yidong
2012-02-15 17:46 ` Johan Bockgård
2012-02-15 18:33 ` 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=87k43ovcl0.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.