From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, 17173@debbugs.gnu.org
Subject: bug#17173: 24.4.50; Emacs partially loses display, and redisplay via `C-l' does not fix it
Date: Sat, 26 Dec 2015 09:29:16 -0800 (PST) [thread overview]
Message-ID: <970cb5d6-b017-4aad-be69-0628c5792fd3@default> (raw)
In-Reply-To: <<83a8oxi2i8.fsf@gnu.org>>
> We (mostly Stefan) made redisplay faster by removing some triggers
> that would redraw windows unnecessarily. Such optimizations always
> leave some fallout that needs to be fixed.
>
> It is impossible to fix these problems without a reproducible recipe.
> The only alternative is to wait for someone else to come up with a bug
> report and a recipe, which will solve this problem as a side effect.
I understand. If there is no way to correlate the source changes
made with the bug report, and so lots of such source changes could
affect this, then the bug report cannot help. Feel free to close
it in that case. Hopefully another report will come along, with
more precise info.
Maybe, when such wholesale optimizations are made in the future,
some debug code can be added, so that symptoms such as I reported
can more easily be traced to particular source changes? Is that
feasible?
My impression is that this is not the only bug report about
failures to redisplay properly in Emacs 25. Seems like we have,
on the one hand, lots of redisplay optimizations implemented
together, or within a short timespan, and a fair number of
redisplay problems reported, and no specific, operational
connections made between the two. If so, that's too bad.
next prev parent reply other threads:[~2015-12-26 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<17026dc9-ee25-4e83-a5c4-86140d37e250@default>
[not found] ` <<83lhvnbrbk.fsf@gnu.org>
2014-04-02 17:19 ` bug#17173: 24.4.50; Emacs partially loses display, and redisplay via `C-l' does not fix it Drew Adams
2015-12-26 14:09 ` Lars Ingebrigtsen
2015-12-26 16:38 ` Drew Adams
2015-12-26 16:43 ` Eli Zaretskii
[not found] ` <<849e9e65-3cc7-45b9-b388-da5993600278@default>
[not found] ` <<87si2pz4gi.fsf@gnus.org>
[not found] ` <<5a3eb48a-6574-41bc-a8c2-37659ec5ebde@default>
[not found] ` <<83a8oxi2i8.fsf@gnu.org>
2015-12-26 17:29 ` Drew Adams [this message]
2015-12-26 18:20 ` Eli Zaretskii
2014-04-02 15:14 Drew Adams
2014-04-02 15:49 ` Daniel Colascione
2014-04-02 15:54 ` Juanma Barranquero
2014-04-02 15:58 ` Daniel Colascione
2014-04-02 16:22 ` Drew Adams
2014-04-02 16:21 ` Drew Adams
2014-04-02 16:59 ` 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=970cb5d6-b017-4aad-be69-0628c5792fd3@default \
--to=drew.adams@oracle.com \
--cc=17173@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).