unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Sat, 18 Feb 2012 10:27:18 +0200	[thread overview]
Message-ID: <83zkcgv95l.fsf@gnu.org> (raw)
In-Reply-To: <87y5s0yiwz.fsf@gnu.org>

> From: Chong Yidong <cyd@gnu.org>
> Cc: 10835@debbugs.gnu.org
> Date: Sat, 18 Feb 2012 10:28:12 +0800
> 
> Times are below.  Another observation: with `time ls /usr/share/doc'
> (which does use color highlighting), scrolling through the Shell buffer
> is no longer sluggish.  I think the output of `time' helps by providing
> a paragraph break.

Of course.  That makes each 2000-line output a separate paragraph, as
far as bidi is concerned.  So you never get to the 7500-line limit of
searching for paragraph beginning.

When I tried to reproduce the problem on Windows, I manually edited
away these empty lines (which are inserted in my case because the
shell prompt on Windows always starts with a newline).

> If I do plain `ls' (no `time'), then go back and edit the Shell buffer
> manually by adding a C-q C-j line break after each prompt, that also
> makes the scrolling sluggishness go away.

Of course, for the same reasons.

> In the Emacs 24 shell buffer, after 10 invocations:
> 
> real	0m1.969s
> user	0m0.008s
> sys	0m0.004s

Is this with the empty lines between invocations, or without?

If the former, do the 2 seconds match your impression of sluggishness,
i.e., do you indeed see Emacs take about 2 sec to insert the 10th
listing into the shell buffer?  Or does the insertion take much
longer?  (Timing with second-resolution can be done by just looking at
your wallclock time.)





      parent reply	other threads:[~2012-02-18  8:27 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
2012-02-18  8:27           ` Eli Zaretskii [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=83zkcgv95l.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).