From: Eli Zaretskii <eliz@gnu.org>
To: Alexis <flexibeast@gmail.com>
Cc: mark@hindley.org.uk, mbork@mbork.pl, 20611@debbugs.gnu.org
Subject: bug#20611: 24.4; mutt slow in ansi-term
Date: Sat, 16 Apr 2016 13:11:07 +0300 [thread overview]
Message-ID: <83y48dc18k.fsf@gnu.org> (raw)
In-Reply-To: <87shynthkt.fsf@gmail.com> (message from Alexis on Fri, 15 Apr 2016 18:13:54 +1000)
> From: Alexis <flexibeast@gmail.com>
> Cc: mark@hindley.org.uk, 20611@debbugs.gnu.org, mbork@mbork.pl
> Date: Fri, 15 Apr 2016 18:13:54 +1000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Can you show a screenshot of a ansi-term display that behaves
> > sluggishly
>
> Attached.
>
> > and also tell how many lines and how many characters are there
> > in the buffer which is in ansi-term mode?
>
> M-x count-lines => "Buffer has 39 lines, 32 words, and 6512
> characters."
What can I say? I'm stumped. Such small buffers should not be
sensitive to dynamic determination of paragraph direction.
But facts are stubborn, so I installed a change to force
bidi-paragraph-direction to the 'left-to-right' value. Please try the
latest emacs-25 branch, and if the problem is fixed, please close the
bug.
Thanks.
next prev parent reply other threads:[~2016-04-16 10:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 7:58 bug#20611: 24.4; mutt slow in ansi-term Mark Hindley
2016-04-08 18:10 ` Marcin Borkowski
2016-04-09 7:39 ` Mark Hindley
2016-04-09 9:38 ` Eli Zaretskii
2016-04-10 9:15 ` Mark Hindley
2016-04-10 17:01 ` Eli Zaretskii
2016-04-10 22:22 ` Alexis
2016-04-11 16:01 ` Eli Zaretskii
2016-04-12 7:59 ` Alexis
2016-04-12 15:27 ` Eli Zaretskii
2016-04-13 0:22 ` Alexis
2016-04-13 1:41 ` Mark Hindley
2016-04-13 2:41 ` Eli Zaretskii
2016-04-13 7:37 ` Mark Hindley
2016-04-13 7:52 ` Alexis
2016-04-13 14:56 ` Eli Zaretskii
2016-04-15 8:13 ` Alexis
2016-04-16 10:11 ` Eli Zaretskii [this message]
2016-06-17 11:04 ` Phil Sainty
2016-06-17 13:27 ` Eli Zaretskii
2016-06-18 1:08 ` Phil Sainty
2016-06-18 8:10 ` Eli Zaretskii
2016-06-19 11:19 ` Phil Sainty
2016-06-26 0:50 ` Phil Sainty
2016-06-26 16:46 ` 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=83y48dc18k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20611@debbugs.gnu.org \
--cc=flexibeast@gmail.com \
--cc=mark@hindley.org.uk \
--cc=mbork@mbork.pl \
/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).