all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
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, 26 Jun 2016 12:35:40 +1200	[thread overview]
Message-ID: <576F235C.8070409@orcon.net.nz> (raw)
In-Reply-To: <83shw5452e.fsf@gnu.org>

On 23/06/16 03:27, Eli Zaretskii wrote:
> Thanks for testing.  So I think this bug can be closed.

Yes, agreed.


Bug #20611 can potentially be closed as well, with the caveat
that there was a workaround commit made for that one, and it
is presumably important to ensure that the workaround will not
get merged to master later on, being unnecessary in that branch.

(Although I'd still be inclined to shift that workaround to act
in term-mode-hook rather than in ansi-term. I'll follow up in
that bug, though.)


 > We are still debating whether 25.2 will be produced from the
 > master branch or from emacs-25.

Ok. Either way, if we have the workaround in effect in emacs-25,
and the real fix in master, this problem is dealt with for the
upcoming releases.


thanks,
-Phil





  reply	other threads:[~2016-06-26  0:35 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
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 [this message]
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=576F235C.8070409@orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=23801@debbugs.gnu.org \
    --cc=eliz@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.