From: Glenn Morris <rgm@gnu.org>
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: Sat, 15 Feb 2014 16:28:13 -0500 [thread overview]
Message-ID: <x17g8w3w2a.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <96vbwj696i.fsf@fencepost.gnu.org>
Eli Zaretskii wrote:
> sounds like the frame is cleared and completely redrawn, which I won't
> expect during byte-compile, which only redisplays the echo area. If I
> put a breakpoint in clear_frame, it is never hit during your recipe.
I put a break on x_clear_frame, and with emacs -Q, byte-compile-file on
scheme.el triggers it.
> (while t
> (split-window-below)
> (sit-for 0.05)
> (delete-other-windows)
> (sit-for 0.05))
>
> Typing "C-x C-e" at the right paren of this in *scratch*, I see no
> flickering in the tool bar. Do you?
Oh yes. It looks awful!
In an attempt to follow your instructions, I put a break on dispnew.c:3045.
So far I don't think I am getting any useful information out of this,
because it seems to trigger a lot, and I'm not sure I'm catching it at
the right time. I'll try again later, but frankly I don't know what I'm
doing, even with your detailed instructions.
Here's current_row and desired_row in update_text_area one time.
TEXT: 13 glyphs
0 0: IMAGE[10] str=0x13fb5c8[0] w=35 a+d=14+21 face=3 MB [ slice=0,0,24,24
1 35: IMAGE[11] str=0x13fb5c8[1] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
2 69: IMAGE[12] str=0x13fb5c8[2] w=29 a+d=14+21 face=3 MB slice=0,0,19,24
3 98: IMAGE[13] str=0x13fb5c8[3] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
4 132: IMAGE[14] str=0x13fb5c8[4] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
5 166: IMAGE[15] str=0x13fb5c8[5] w=12 a+d=14+21 face=3 MB slice=0,0,2,24
6 178: IMAGE[16] str=0x13fb5c8[6] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
7 212: IMAGE[15] str=0x13fb5c8[7] w=12 a+d=14+21 face=3 MB slice=0,0,2,24
8 224: IMAGE[17] str=0x13fb5c8[8] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
9 258: IMAGE[18] str=0x13fb5c8[9] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
10 292: IMAGE[19] str=0x13fb5c8[10] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
11 326: IMAGE[15] str=0x13fb5c8[11] w=12 a+d=14+21 face=3 MB slice=0,0,2,24
12 338: IMAGE[20] str=0x13fb5c8[12] w=34 a+d=14+21 face=3 MB ] slice=0,0,24,24
TEXT: 13 glyphs
0 0: IMAGE[10] str=0x13fbe90[0] w=35 a+d=14+21 face=3 MB [ slice=0,0,24,24
1 35: IMAGE[11] str=0x13fbe90[1] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
2 69: IMAGE[12] str=0x13fbe90[2] w=29 a+d=14+21 face=3 MB slice=0,0,19,24
3 98: IMAGE[13] str=0x13fbe90[3] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
4 132: IMAGE[14] str=0x13fbe90[4] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
5 166: IMAGE[15] str=0x13fbe90[5] w=12 a+d=14+21 face=3 MB slice=0,0,2,24
6 178: IMAGE[16] str=0x13fbe90[6] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
7 212: IMAGE[15] str=0x13fbe90[7] w=12 a+d=14+21 face=3 MB slice=0,0,2,24
8 224: IMAGE[17] str=0x13fbe90[8] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
9 258: IMAGE[18] str=0x13fbe90[9] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
10 292: IMAGE[19] str=0x13fbe90[10] w=34 a+d=14+21 face=3 MB slice=0,0,24,24
11 326: IMAGE[15] str=0x13fbe90[11] w=12 a+d=14+21 face=3 MB slice=0,0,2,24
12 338: IMAGE[20] str=0x13fbe90[12] w=34 a+d=14+21 face=3 MB ] slice=0,0,24,24
next prev parent reply other threads:[~2014-02-15 21:28 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 [this message]
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
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=x17g8w3w2a.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--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).