From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: 10835@debbugs.gnu.org
Subject: bug#10835: 24.0.93; bidi-paragraph-direction slows down Shell mode
Date: Fri, 17 Feb 2012 18:08:47 +0200 [thread overview]
Message-ID: <837gzlwigg.fsf@gnu.org> (raw)
In-Reply-To: <8762f6dn85.fsf@gnu.org>
> From: Chong Yidong <cyd@gnu.org>
> Date: Fri, 17 Feb 2012 13:48:26 +0800
>
> It happens on both GUI sessions and TTY, run locally on an Intel i7
> processor; Emacs was compiled without optimizations.
On an i7, I'd expect no slowdown at all.
How much time does it take `ls' to produce that 2K-line listing on
your machine, outside of Emacs and with a warm cache?
Also, can you put a printf after this line from xdisp.c:
else if (it->bidi_it.charpos == bob
|| (!string_p
&& (FETCH_CHAR (it->bidi_it.bytepos - 1) == '\n'
|| FETCH_CHAR (it->bidi_it.bytepos) == '\n')))
{
/* If we are at the beginning of a line/string, we can produce
the next element right away. */
bidi_paragraph_init (it->paragraph_embedding, &it->bidi_it, 1); <<<<<<
and tell me once in how many characters or lines of input from `ls' is
bidi_paragraph_init called here? E.g., to see the character count,
print it->bidi_it.charpos just before that line. (You could do the
same from breakpoint commands, but I'm afraid that doing so will
change the timing of how frequently the process output is read by
Emacs, and will therefore produce a biased estimation.)
TIA
next prev parent reply other threads:[~2012-02-17 16:08 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 [this message]
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
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
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=837gzlwigg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10835@debbugs.gnu.org \
--cc=cyd@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 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).