From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: redisplay-dont-pause
Date: Fri, 16 Sep 2011 20:45:15 +0300 [thread overview]
Message-ID: <83aaa4v0t0.fsf@gnu.org> (raw)
In-Reply-To: <E1R4cEQ-0000jX-Td@fencepost.gnu.org>
> Date: Fri, 16 Sep 2011 13:29:42 -0400
> From: Richard Stallman <rms@gnu.org>
> CC: emacs-devel@gnu.org
>
> Because the optimizations rely on the display being up to date, which
> cannot be assured if redisplay was aborted half way through.
>
> There is no reason in principle that it can't be assured.
> The display code I wrote assured the integrity of the records,
> even when it stopped having updated only some of the lines.
> And the multi-font display code in Emacs 19 did so too.
Perhaps if you describe the design of how the old display engine kept
records about up-to-dateness of display portions, we could see if the
same design principles can be used with the current display engine,
and maybe implement such a feature.
next prev parent reply other threads:[~2011-09-16 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 15:36 redisplay-dont-pause Eli Zaretskii
2011-09-14 15:38 ` redisplay-dont-pause Juanma Barranquero
2011-09-14 16:12 ` redisplay-dont-pause Leo
2011-09-14 17:09 ` redisplay-dont-pause Eli Zaretskii
2011-09-15 4:12 ` redisplay-dont-pause Richard Stallman
2011-09-15 5:24 ` redisplay-dont-pause Eli Zaretskii
2011-09-15 2:10 ` redisplay-dont-pause Christoph Scholtes
2011-09-15 3:03 ` redisplay-dont-pause Eli Zaretskii
2011-09-15 4:12 ` redisplay-dont-pause Richard Stallman
2011-09-15 4:59 ` redisplay-dont-pause Eli Zaretskii
2011-09-15 22:02 ` redisplay-dont-pause Richard Stallman
2011-09-16 7:23 ` redisplay-dont-pause Eli Zaretskii
2011-09-16 17:29 ` redisplay-dont-pause Richard Stallman
2011-09-16 17:45 ` Eli Zaretskii [this message]
2011-09-17 0:36 ` redisplay-dont-pause Richard Stallman
2011-09-17 8:13 ` redisplay-dont-pause Eli Zaretskii
2011-09-17 19:43 ` redisplay-dont-pause Chong Yidong
2011-09-24 14:39 ` redisplay-dont-pause Eli Zaretskii
2011-09-17 21:30 ` redisplay-dont-pause Stefan Monnier
2011-09-18 11:07 ` redisplay-dont-pause Juanma Barranquero
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=83aaa4v0t0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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).