From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@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:22:38 +0200 [thread overview]
Message-ID: <83y51b9gdt.fsf@gnu.org> (raw)
In-Reply-To: <v6vbwgf2s5.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Cc: 16736@debbugs.gnu.org, martin rudalics <rudalics@gmx.at>
> Date: Sat, 15 Feb 2014 17:07:38 -0500
>
> Glenn Morris wrote:
>
> >> (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!
>
> Bisected to:
>
> revno: 115971
> committer: martin rudalics <rudalics@gmx.at>
> branch nick: trunk
> timestamp: Sat 2014-01-11 10:31:09 +0100
> message:
> Fix handling of internal borders (Bug#16348).
Thanks, but I think we still need more info to find what caused this,
as most of that commit is for non-toolkit builds.
Can you put a breakpoint in change_frame_size_1, on line 5564:
SET_FRAME_COLS (f, new_cols); <<<<<<<<<<<<<<<<
FRAME_LINES (f) = new_lines;
FRAME_TEXT_WIDTH (f) = new_text_width;
and see if that breakpoint breaks when you type "C-x 2" in *scratch*?
If it does break, can you show the values of these:
new_text_width
FRAME_TEXT_WIDTH (f)
new_root_width
old_root_width
FRAME_TEXT_TO_PIXEL_WIDTH (f, new_text_width)
FRAME_INTERNAL_BORDER_WIDTH (f)
next prev parent reply other threads:[~2014-02-16 16:22 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
2014-02-17 0:53 ` Glenn Morris
2014-02-16 16:22 ` Eli Zaretskii [this message]
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=83y51b9gdt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16736@debbugs.gnu.org \
--cc=rgm@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).