From: Eli Zaretskii <eliz@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 23801@debbugs.gnu.org
Subject: bug#23801: 25.0.95; term.el redraws extremely slow with bidi support enabled, and large buffers
Date: Sun, 19 Jun 2016 19:26:18 +0300 [thread overview]
Message-ID: <83pord87rp.fsf@gnu.org> (raw)
In-Reply-To: <57666E36.6030809@orcon.net.nz> (message from Phil Sainty on Sun, 19 Jun 2016 22:04:38 +1200)
> From: Phil Sainty <psainty@orcon.net.nz>
> Cc: Eli Zaretskii <eliz@gnu.org>
> Date: Sun, 19 Jun 2016 22:04:38 +1200
>
> This is a spin-off from bug#20611: 24.4; mutt slow in ansi-term.
>
> I'm logging a new bug report by request, although it seems to me that
> this is still the same bug (and 20611 is still open), so I suggest that
> they can both be closed together once a fix is committed?
>
> I've experimented further with this issue since my comments in 20611,
> and my current observations follow...
Thanks.
My problem is that I don't see these slow redraws. I tried in a TTY
session on a GNU/Linux system, using "ls ~" as the command inside
term-mode (my home directory on that system produces a 1500-line list
of files). I don't see slow redraws, and don't see any perceptible
speed-up when I set bidi-paragraph-direction to left-to-right.
Can you reproduce the problem using 'ls'?
next prev parent reply other threads:[~2016-06-19 16:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 10:04 bug#23801: 25.0.95; term.el redraws extremely slow with bidi support enabled, and large buffers Phil Sainty
2016-06-19 16:26 ` Eli Zaretskii [this message]
2016-06-19 23:41 ` Phil Sainty
2016-06-20 0:00 ` Phil Sainty
2016-06-20 14:35 ` Phil Sainty
2016-06-20 15:05 ` Eli Zaretskii
2016-06-21 18:47 ` Eli Zaretskii
2016-06-22 13:13 ` Phil Sainty
2016-06-22 15:27 ` Eli Zaretskii
2016-06-26 0:35 ` Phil Sainty
2016-06-26 16:45 ` Eli Zaretskii
2016-06-26 16:45 ` Eli Zaretskii
2016-06-20 14:28 ` Eli Zaretskii
2016-06-20 15:07 ` Phil Sainty
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=83pord87rp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23801@debbugs.gnu.org \
--cc=psainty@orcon.net.nz \
/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.