From: Eli Zaretskii <eliz@gnu.org>
To: 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 20:20:12 +0200 [thread overview]
Message-ID: <834mf5hy1v.fsf@gnu.org> (raw)
In-Reply-To: <970cb5d6-b017-4aad-be69-0628c5792fd3@default> (message from Drew Adams on Sat, 26 Dec 2015 09:29:16 -0800 (PST))
> Date: Sat, 26 Dec 2015 09:29:16 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: larsi@gnus.org, 17173@debbugs.gnu.org
>
> 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?
We have the debug code. I myself use it all the time, and several
times asked people who reported bugs to enable it and show the output.
But it produces a lot of output, so it is only feasible to turn it on
when running a reproducible recipe. Which we don't have in this case.
> 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.
There were indeed several reports about redisplay problems, related to
those changes. They were all fixed, AFAICT, because each one
eventually succeeded to find a recipe for reproducing the problem.
next prev parent reply other threads:[~2015-12-26 18:20 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
2015-12-26 18:20 ` Eli Zaretskii [this message]
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=834mf5hy1v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17173@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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).