From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16736@debbugs.gnu.org
Subject: bug#16736: Compiling a Lisp file causes display to flash off and on
Date: Sun, 16 Feb 2014 18:14:43 +0100 [thread overview]
Message-ID: <5300F203.1070108@gmx.at> (raw)
In-Reply-To: <83vbwf9f9h.fsf@gnu.org>
> Btw, the bug was about non-toolkit builds, but at least one of the
> hunks affects toolkit builds as well. Not sure if that was intended.
It was intended. A related bug showed up also on the Windows build.
I then checked the border behavior on all builds I made.
Basically, the changes should only clear areas where display artifacts
show up. It does that somewhat brute forcish (similar to the Gtk build)
but I can't yet imagine that these could screw up redisplay that much.
martin
next prev parent reply other threads:[~2014-02-16 17:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 2:25 bug#16736: Compiling a Lisp file causes display to flash off and on Glenn Morris
2014-02-14 6:42 ` Glenn Morris
2014-02-14 7:29 ` Eli Zaretskii
2014-02-14 7:48 ` Glenn Morris
2014-02-15 8:24 ` Eli Zaretskii
2014-02-15 8:34 ` Eli Zaretskii
2014-02-15 21:28 ` Glenn Morris
2014-02-15 22:07 ` Glenn Morris
2014-02-16 10:31 ` martin rudalics
2014-02-16 16:46 ` Eli Zaretskii
2014-02-16 17:14 ` martin rudalics [this message]
2014-02-17 0:53 ` Glenn Morris
2014-02-16 16:22 ` Eli Zaretskii
2014-02-17 0:58 ` Glenn Morris
2014-02-17 5:14 ` Eli Zaretskii
2014-02-17 7:45 ` Glenn Morris
2014-02-17 15:42 ` Eli Zaretskii
2014-02-17 16:23 ` martin rudalics
2014-02-17 16:50 ` Eli Zaretskii
2014-02-17 17:16 ` martin rudalics
2014-02-17 17:27 ` Eli Zaretskii
2014-02-17 17:58 ` martin rudalics
2014-02-17 18:56 ` Eli Zaretskii
2014-02-18 11:02 ` martin rudalics
2014-02-18 18:08 ` Eli Zaretskii
2014-02-19 10:02 ` martin rudalics
2014-02-18 18:19 ` Glenn Morris
2014-02-17 18:19 ` Glenn Morris
2014-02-17 18:47 ` Eli Zaretskii
2014-02-18 11:03 ` martin rudalics
2014-02-16 16:17 ` Eli Zaretskii
2014-02-16 19:48 ` Glenn Morris
2014-02-16 21:04 ` Eli Zaretskii
2014-02-17 1:18 ` Glenn Morris
2014-02-17 5:15 ` 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=5300F203.1070108@gmx.at \
--to=rudalics@gmx.at \
--cc=16736@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 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).