From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: raeburn@permabit.com, 11822@debbugs.gnu.org
Subject: bug#11822: 24.1; emacsclient terminal mode captures escape characters as text
Date: Fri, 11 Sep 2015 08:56:58 -0400 [thread overview]
Message-ID: <jwvzj0t7s29.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83vbbi409g.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 10 Sep 2015 21:06:35 +0300")
>> > /* Contrary to expectations, a value of "false" can be detrimental to
>> > responsiveness since aborting a redisplay throws away some of the
>> > work already performed.
>> But that's because the effect was different from what is being
>> discussed here (at least in theory): interrupting redisplay between
>> windows wouldn't throw away work, AFAIK.
> What Ken suggests is not an interruption between windows, it's
> interruption in the middle of recomputing faces. That's much worse.
I think he suggests several things.
One of them is to redisplay frame-by-frame, starting with the selected
frame and checking for pending input between each frame.
Another is to do decompose the redisplay of a given window into
chunks (e.g. cut at those points where we're waiting for a reply from
the X server) that can be interrupted. IIUC by "interrupted" he doesn't
mean to abort what we're doing, but only to suspend it.
What we need to remember from redisplay-dont-pause is that we need to
avoid doing work and throwing it away before the result is shown on
the display. In the case of redisplay-dont-pause, the reason it's
thrown away is that by the time we got back, the work we'd done
(refreshing the matrices) often/usually needed to be redone.
If we only interrupt after refreshing the display of a window and before
starting to recompute the glyph matrices of the next, then I think we
avoid this risk.
Stefan
next prev parent reply other threads:[~2015-09-11 12:56 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 0:08 bug#11822: 24.1; emacsclient terminal mode captures escape characters as text Ken Raeburn
2012-06-30 5:55 ` Eli Zaretskii
2012-07-31 21:06 ` Ken Raeburn
2012-08-08 3:13 ` Ken Raeburn
2012-08-08 4:52 ` Dan Nicolaescu
2012-08-08 9:26 ` Ken Raeburn
2012-08-09 21:12 ` Ken Raeburn
2012-08-10 6:16 ` Eli Zaretskii
2012-08-10 7:27 ` Ken Raeburn
2012-08-10 7:46 ` Eli Zaretskii
2012-08-10 8:08 ` Eli Zaretskii
2015-09-07 21:09 ` Ken Raeburn
2015-09-08 1:29 ` Stefan Monnier
2015-09-08 4:29 ` Eli Zaretskii
2015-09-08 6:53 ` Ken Raeburn
2015-09-08 13:03 ` Stefan Monnier
2015-09-08 13:11 ` Stefan Monnier
2015-09-08 17:21 ` Eli Zaretskii
2015-09-08 4:48 ` Eli Zaretskii
2015-09-08 10:15 ` Ken Raeburn
2015-09-08 13:35 ` Stefan Monnier
2015-09-08 17:33 ` Eli Zaretskii
2015-09-08 19:54 ` Ken Raeburn
2015-09-09 14:16 ` Eli Zaretskii
2015-09-10 6:59 ` Ken Raeburn
2015-09-10 15:36 ` Eli Zaretskii
2015-09-10 17:56 ` Stefan Monnier
2015-09-10 18:06 ` Eli Zaretskii
2015-09-11 12:56 ` Stefan Monnier [this message]
2015-09-11 13:53 ` Eli Zaretskii
2015-09-11 16:53 ` Stefan Monnier
2015-09-11 6:54 ` Ken Raeburn
2015-09-11 7:22 ` Eli Zaretskii
2015-09-11 23:11 ` Ken Raeburn
2015-09-12 0:51 ` Stefan Monnier
2015-09-12 1:34 ` Ken Raeburn
2015-09-15 14:29 ` Eli Zaretskii
2015-09-15 16:14 ` Stefan Monnier
2015-09-18 14:19 ` Eli Zaretskii
2015-09-21 9:23 ` Ken Raeburn
2015-09-21 9:44 ` Eli Zaretskii
2015-09-23 17:27 ` Ken Raeburn
2015-09-23 18:04 ` martin rudalics
2015-09-23 20:59 ` Ken Raeburn
2015-09-23 19:17 ` Eli Zaretskii
2015-09-24 8:52 ` Ken Raeburn
2015-09-24 18:46 ` Eli Zaretskii
2015-09-24 20:08 ` Ken Raeburn
2015-09-25 6:49 ` Eli Zaretskii
2015-09-25 12:07 ` Stefan Monnier
2015-09-26 7:01 ` Eli Zaretskii
2015-09-25 6:50 ` Eli Zaretskii
2015-09-25 12:09 ` Stefan Monnier
2015-09-25 13:29 ` Eli Zaretskii
2015-09-25 15:18 ` Stefan Monnier
2015-09-12 7:30 ` Eli Zaretskii
2015-09-11 13:39 ` Stefan Monnier
2015-09-11 14:01 ` Eli Zaretskii
2015-09-08 13:22 ` Stefan Monnier
2015-09-08 17:25 ` Eli Zaretskii
2015-09-08 18:52 ` Stefan Monnier
2015-09-08 19:08 ` Eli Zaretskii
2015-09-08 20:37 ` Stefan Monnier
2015-09-08 17:36 ` 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=jwvzj0t7s29.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11822@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=raeburn@permabit.com \
/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).