From unknown Mon Jun 23 02:23:27 2025 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) Content-Type: text/plain; charset=utf-8 From: bug#16736 <16736@debbugs.gnu.org> To: bug#16736 <16736@debbugs.gnu.org> Subject: Status: Compiling a Lisp file causes display to flash off and on Reply-To: bug#16736 <16736@debbugs.gnu.org> Date: Mon, 23 Jun 2025 09:23:27 +0000 retitle 16736 Compiling a Lisp file causes display to flash off and on reassign 16736 emacs submitter 16736 Glenn Morris severity 16736 important thanks From debbugs-submit-bounces@debbugs.gnu.org Wed Feb 12 21:25:14 2014 Received: (at submit) by debbugs.gnu.org; 13 Feb 2014 02:25:14 +0000 Received: from localhost ([127.0.0.1]:49760 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WDlzF-0001Y5-H2 for submit@debbugs.gnu.org; Wed, 12 Feb 2014 21:25:13 -0500 Received: from fencepost.gnu.org ([208.118.235.10]:56588 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WDlzB-0001Xu-RZ for submit@debbugs.gnu.org; Wed, 12 Feb 2014 21:25:10 -0500 Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1WDlzB-00053b-3v; Wed, 12 Feb 2014 21:25:09 -0500 From: Glenn Morris To: submit@debbugs.gnu.org Subject: Compiling a Lisp file causes display to flash off and on X-Spook: cypherpunk Clinton condor insurgency 2600 Magazine Bush X-Ran: GLvq5P8mDE_cF_~t|SO}3\1k!2ZR$]UIuHC+v!2[|rcYWjia3&Q+vPv User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: -5.7 (-----) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.7 (-----) Package: emacs Version: 24.3.50 Current trunk on x86_64 GNU/Linux, Lucid toolkit. Visit some non-trivial file that compiles with no warnings: emacs -Q some-file.el M-x byte-compile-file RET RET During the resulting compilation, at some point it looks like the Emacs display goes completely blank. It happens a bit fast, so it is hard to say exactly. It does not look to me as if it is switching to another buffer (Compile-Log) and back again. It's like the display flashes off and on. The tool-bar, mode line also disappear. This effect does not happen with 24.3. From debbugs-submit-bounces@debbugs.gnu.org Fri Feb 14 01:42:33 2014 Received: (at 16736) by debbugs.gnu.org; 14 Feb 2014 06:42:33 +0000 Received: from localhost ([127.0.0.1]:51495 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WECTp-0005e6-Cn for submit@debbugs.gnu.org; Fri, 14 Feb 2014 01:42:33 -0500 Received: from fencepost.gnu.org ([208.118.235.10]:55693 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WECTm-0005dw-GT for 16736@debbugs.gnu.org; Fri, 14 Feb 2014 01:42:31 -0500 Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1WECTl-00012v-Gr; Fri, 14 Feb 2014 01:42:29 -0500 From: Glenn Morris To: 16736@debbugs.gnu.org Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> X-Spook: undercover Etacs Adriatic e-cash ANZUS explosion Juiliett X-Ran: #IWv[|X%[^rzy02+4NLB3~ZC9_A})cpMCpAxS?zCc@\@N~qEH&J=u+?'P(erKS@S0RWVL@ X-Hue: blue X-Attribution: GM Date: Fri, 14 Feb 2014 01:42:29 -0500 In-Reply-To: <96vbwj696i.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 12 Feb 2014 21:25:09 -0500") Message-ID: User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: -5.7 (-----) X-Debbugs-Envelope-To: 16736 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.7 (-----) I'm noticing display flashes in other situations too. Eg with simply emacs -Q, then repeating C-x 2, C-x 1 in sequence, I notice the toolbar flashing quickly off and on. Not every time, but often. It's rather distracting. I do not observe this with 24.3. From debbugs-submit-bounces@debbugs.gnu.org Fri Feb 14 02:29:58 2014 Received: (at 16736) by debbugs.gnu.org; 14 Feb 2014 07:29:58 +0000 Received: from localhost ([127.0.0.1]:51542 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEDDh-00070h-Jq for submit@debbugs.gnu.org; Fri, 14 Feb 2014 02:29:58 -0500 Received: from mtaout25.012.net.il ([80.179.55.181]:47960) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEDDd-00070K-NP for 16736@debbugs.gnu.org; Fri, 14 Feb 2014 02:29:54 -0500 Received: from conversion-daemon.mtaout25.012.net.il by mtaout25.012.net.il (HyperSendmail v2007.08) id <0N0Z00B005XIWG00@mtaout25.012.net.il> for 16736@debbugs.gnu.org; Fri, 14 Feb 2014 09:28:45 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout25.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N0Z00BCH63XBK10@mtaout25.012.net.il>; Fri, 14 Feb 2014 09:28:45 +0200 (IST) Date: Fri, 14 Feb 2014 09:29:43 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: X-012-Sender: halo1@inter.net.il To: Glenn Morris Message-id: <83lhxecftk.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > From: Glenn Morris > Date: Fri, 14 Feb 2014 01:42:29 -0500 > > > I'm noticing display flashes in other situations too. Eg with simply > emacs -Q, then repeating C-x 2, C-x 1 in sequence, I notice the toolbar > flashing quickly off and on. Not every time, but often. It's rather > distracting. I do not observe this with 24.3. I tried to reproduce your original report, but couldn't, perhaps because I couldn't find a large enough Lisp file that compiles without warnings. Can you tell which file did you use? As for toolbar flickering with repeated "C-x 2" and "C-x 1", I don't see it here. Is this with a configuration where Emacs draws the toolbar, or is the toolbar drawn by the toolkit? From debbugs-submit-bounces@debbugs.gnu.org Fri Feb 14 02:48:36 2014 Received: (at 16736) by debbugs.gnu.org; 14 Feb 2014 07:48:36 +0000 Received: from localhost ([127.0.0.1]:51564 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEDVj-0007b8-U4 for submit@debbugs.gnu.org; Fri, 14 Feb 2014 02:48:36 -0500 Received: from fencepost.gnu.org ([208.118.235.10]:56661 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEDVg-0007ax-IM for 16736@debbugs.gnu.org; Fri, 14 Feb 2014 02:48:33 -0500 Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1WEDVf-0001nH-9g; Fri, 14 Feb 2014 02:48:31 -0500 From: Glenn Morris To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> X-Spook: passwd afsatcom JSOFC3IP Roswell ASLET Downing Street X-Ran: [*!qDHXp-gfM)szK3p=bZw8K@I8uR|p%{8X{'H^c'(&]g&$]};ok,7(j)Lned1sgcK:KL1 X-Hue: red X-Debbugs-No-Ack: yes X-Attribution: GM Date: Fri, 14 Feb 2014 02:48:31 -0500 In-Reply-To: <83lhxecftk.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 14 Feb 2014 09:29:43 +0200") Message-ID: <2smwhurv74.fsf@fencepost.gnu.org> User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: -5.7 (-----) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.7 (-----) Eli Zaretskii wrote: > I tried to reproduce your original report, but couldn't, perhaps > because I couldn't find a large enough Lisp file that compiles without > warnings. Can you tell which file did you use? I think I randomly used progmodes/scheme.el, but added (require 'gnus) (require 'org) at the start, and deleted gnus/*.elc and org/*.elc to slow things down. Basically make the slowest compilation you can, so long as there are no warnings. It seems to be right at the end of the compilation that the flash occurs. > As for toolbar flickering with repeated "C-x 2" and "C-x 1", I don't > see it here. Is this with a configuration where Emacs draws the > toolbar, or is the toolbar drawn by the toolkit? --with-x-toolkit=athena --without-toolkit-scroll-bars From debbugs-submit-bounces@debbugs.gnu.org Sat Feb 15 03:24:57 2014 Received: (at 16736) by debbugs.gnu.org; 15 Feb 2014 08:24:57 +0000 Received: from localhost ([127.0.0.1]:52924 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEaYS-0006tq-J0 for submit@debbugs.gnu.org; Sat, 15 Feb 2014 03:24:57 -0500 Received: from mtaout24.012.net.il ([80.179.55.180]:40561) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEaYO-0006tV-Hn for 16736@debbugs.gnu.org; Sat, 15 Feb 2014 03:24:54 -0500 Received: from conversion-daemon.mtaout24.012.net.il by mtaout24.012.net.il (HyperSendmail v2007.08) id <0N1100C0034EDS00@mtaout24.012.net.il> for 16736@debbugs.gnu.org; Sat, 15 Feb 2014 10:23:41 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout24.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N11006S43BHL080@mtaout24.012.net.il>; Sat, 15 Feb 2014 10:23:41 +0200 (IST) Date: Sat, 15 Feb 2014 10:24:44 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: <2smwhurv74.fsf@fencepost.gnu.org> X-012-Sender: halo1@inter.net.il To: Glenn Morris Message-id: <83iosgbx6b.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > From: Glenn Morris > Cc: 16736@debbugs.gnu.org > Date: Fri, 14 Feb 2014 02:48:31 -0500 > > Eli Zaretskii wrote: > > > I tried to reproduce your original report, but couldn't, perhaps > > because I couldn't find a large enough Lisp file that compiles without > > warnings. Can you tell which file did you use? > > I think I randomly used progmodes/scheme.el, but added > > (require 'gnus) > (require 'org) > > at the start, and deleted gnus/*.elc and org/*.elc to slow things down. > > Basically make the slowest compilation you can, so long as there are no > warnings. It seems to be right at the end of the compilation that the > flash occurs. I don't see any flash here. What you describe, viz.: > During the resulting compilation, at some point it looks like the Emacs > display goes completely blank. It happens a bit fast, so it is hard to > say exactly. It does not look to me as if it is switching to another > buffer (Compile-Log) and back again. It's like the display flashes off > and on. The tool-bar, mode line also disappear. 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. > > As for toolbar flickering with repeated "C-x 2" and "C-x 1", I don't > > see it here. Is this with a configuration where Emacs draws the > > toolbar, or is the toolbar drawn by the toolkit? > > --with-x-toolkit=athena --without-toolkit-scroll-bars These symptoms seem to indicate that the tool bar is redrawn, whereas it shouldn't be, because its content is unchanged by "C-x 2". I don't see any flickering here, so please step with GDB through the affected code, as described below, and tell what you see. I also tried this recipe: (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? To find out why does the tool-bar flicker, please step into the portion of redisplay that redraws the tool bar. Its entry point is in update_frame, like this: #if defined (HAVE_WINDOW_SYSTEM) && ! defined (USE_GTK) && ! defined (HAVE_NS) /* Update the tool-bar window, if present. */ if (WINDOWP (f->tool_bar_window)) { struct window *w = XWINDOW (f->tool_bar_window); /* Update tool-bar window. */ if (w->must_be_updated_p) { Lisp_Object tem; update_window (w, 1); w->must_be_updated_p = false; /* Swap tool-bar strings. We swap because we want to reuse strings. */ tem = f->current_tool_bar_string; fset_current_tool_bar_string (f, f->desired_tool_bar_string); fset_desired_tool_bar_string (f, tem); } } #endif Please step into the update_window call above. There you should see that we perform this loop: /* Update the rest of the lines. */ for (; row < end && (force_p || !input_pending); ++row) /* scrolling_window resets the enabled_p flag of the rows it reuses from current_matrix. */ if (row->enabled_p) { Then step into update_window_line call in that loop. The glyph rows of the tool-bar window don't have marginal areas, so when the loop calls update_window_line, only update_text_area is called from update_window_line. There's call in update_text_area that compares the glyph row of the current glyph matrix (which reflects what is on the screen) and the desired glyph matrix (which says what should be on the screen). The comparison code starts with this: stop = min (current_row->used[TEXT_AREA], desired_stop_pos); i = 0; x = desired_row->x; /* Loop over glyphs that current and desired row may have in common. */ while (i < stop) { In my case, current_row and desired_row are exactly equal, so the tool bar is never redrawn. Please see if things are different in your case, and why. You can display the contents of the glyph row with the pgrowx command (defined on src/.gdbinit), like this: (gdb) pgrowx current_row TEXT: 13 glyphs 0 0: IMAGE[10] str=0x3a9f394[0] w=35 a+d=14+21 face=3 MB [ slice=0,0,24,24 1 35: IMAGE[11] str=0x3a9f394[1] w=34 a+d=14+21 face=3 MB slice=0,0,24,24 2 69: IMAGE[12] str=0x3a9f394[2] w=29 a+d=14+21 face=3 MB slice=0,0,19,24 3 98: IMAGE[13] str=0x3a9f394[3] w=34 a+d=14+21 face=3 MB slice=0,0,24,24 4 132: IMAGE[14] str=0x3a9f394[4] w=34 a+d=14+21 face=3 MB slice=0,0,24,24 5 166: IMAGE[15] str=0x3a9f394[5] w=12 a+d=14+21 face=3 MB slice=0,0,2,24 6 178: IMAGE[16] str=0x3a9f394[6] w=34 a+d=14+21 face=3 MB slice=0,0,24,24 7 212: IMAGE[15] str=0x3a9f394[7] w=12 a+d=14+21 face=3 MB slice=0,0,2,24 8 224: IMAGE[17] str=0x3a9f394[8] w=34 a+d=14+21 face=3 MB slice=0,0,24,24 9 258: IMAGE[18] str=0x3a9f394[9] w=34 a+d=14+21 face=3 MB slice=0,0,24,24 10 292: IMAGE[19] str=0x3a9f394[10] w=34 a+d=14+21 face=3 MB slice=0,0,24,24 11 326: IMAGE[15] str=0x3a9f394[11] w=12 a+d=14+21 face=3 MB slice=0,0,2,24 12 338: IMAGE[20] str=0x3a9f394[12] w=34 a+d=14+21 face=3 MB ] slice=0,0,24,24 Thanks. From debbugs-submit-bounces@debbugs.gnu.org Sat Feb 15 03:34:19 2014 Received: (at 16736) by debbugs.gnu.org; 15 Feb 2014 08:34:19 +0000 Received: from localhost ([127.0.0.1]:52928 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEahX-0007DM-1G for submit@debbugs.gnu.org; Sat, 15 Feb 2014 03:34:19 -0500 Received: from mtaout25.012.net.il ([80.179.55.181]:36866) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEahU-0007D5-AU for 16736@debbugs.gnu.org; Sat, 15 Feb 2014 03:34:17 -0500 Received: from conversion-daemon.mtaout25.012.net.il by mtaout25.012.net.il (HyperSendmail v2007.08) id <0N1100F0030OLY00@mtaout25.012.net.il> for 16736@debbugs.gnu.org; Sat, 15 Feb 2014 10:33:05 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout25.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N1100CXU3R5RL60@mtaout25.012.net.il>; Sat, 15 Feb 2014 10:33:05 +0200 (IST) Date: Sat, 15 Feb 2014 10:34:08 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: <83iosgbx6b.fsf@gnu.org> X-012-Sender: halo1@inter.net.il To: rgm@gnu.org Message-id: <83ha80bwqn.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> X-Spam-Score: 1.2 (+) X-Spam-Report: Spam detection software, running on the system "debbugs.gnu.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: > Date: Sat, 15 Feb 2014 10:24:44 +0200 > From: Eli Zaretskii > Cc: 16736@debbugs.gnu.org > > Then step into update_window_line call in that loop. The glyph rows > of the tool-bar window don't have marginal areas, so when the loop > calls update_window_line, only update_text_area is called from > update_window_line. There's call in update_text_area that compares ^^^^ This should have been "code", sorry. [...] Content analysis details: (1.2 points, 10.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 1.0 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail) 0.2 BODY_URI_ONLY Message body is only a URI in one line of text or for an image X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.2 (+) X-Spam-Report: Spam detection software, running on the system "debbugs.gnu.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: > Date: Sat, 15 Feb 2014 10:24:44 +0200 > From: Eli Zaretskii > Cc: 16736@debbugs.gnu.org > > Then step into update_window_line call in that loop. The glyph rows > of the tool-bar window don't have marginal areas, so when the loop > calls update_window_line, only update_text_area is called from > update_window_line. There's call in update_text_area that compares ^^^^ This should have been "code", sorry. [...] Content analysis details: (1.2 points, 10.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 1.0 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail) 0.2 BODY_URI_ONLY Message body is only a URI in one line of text or for an image > Date: Sat, 15 Feb 2014 10:24:44 +0200 > From: Eli Zaretskii > Cc: 16736@debbugs.gnu.org > > Then step into update_window_line call in that loop. The glyph rows > of the tool-bar window don't have marginal areas, so when the loop > calls update_window_line, only update_text_area is called from > update_window_line. There's call in update_text_area that compares ^^^^ This should have been "code", sorry. From debbugs-submit-bounces@debbugs.gnu.org Sat Feb 15 16:28:19 2014 Received: (at 16736) by debbugs.gnu.org; 15 Feb 2014 21:28:19 +0000 Received: from localhost ([127.0.0.1]:53827 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEmmY-0005En-Li for submit@debbugs.gnu.org; Sat, 15 Feb 2014 16:28:19 -0500 Received: from fencepost.gnu.org ([208.118.235.10]:52533 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEmmV-0005Ef-Ts for 16736@debbugs.gnu.org; Sat, 15 Feb 2014 16:28:16 -0500 Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1WEmmT-0000Cj-OS; Sat, 15 Feb 2014 16:28:13 -0500 From: Glenn Morris To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> X-Spook: Kennedy oil SAPO HAMASMOIS number key spy arrangements X-Ran: Fu,;P0:He7?TshnR,;{7~2&|J+$6OWuSS9E{v]ggn{Si2AM+cPsM[geVCHexU!/$Nz".S" X-Hue: red X-Debbugs-No-Ack: yes X-Attribution: GM Date: Sat, 15 Feb 2014 16:28:13 -0500 Message-ID: User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: -5.7 (-----) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.7 (-----) 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 From debbugs-submit-bounces@debbugs.gnu.org Sat Feb 15 17:07:41 2014 Received: (at 16736) by debbugs.gnu.org; 15 Feb 2014 22:07:42 +0000 Received: from localhost ([127.0.0.1]:53865 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEnOf-0006MM-Mi for submit@debbugs.gnu.org; Sat, 15 Feb 2014 17:07:41 -0500 Received: from fencepost.gnu.org ([208.118.235.10]:53144 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEnOd-0006MC-LN for 16736@debbugs.gnu.org; Sat, 15 Feb 2014 17:07:40 -0500 Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1WEnOc-0004f5-OS; Sat, 15 Feb 2014 17:07:38 -0500 From: Glenn Morris To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> X-Spook: Montenegro Lexis-Nexis militia munitions Bruxelles Putin X-Ran: ~_6k>@E>T&RJ'KjGv*8^V*c,S+SKJL-~y1~hnR;kotL~8,?H5MIk*k|5O2Kq\(*7*Tzj^K X-Hue: cyan X-Debbugs-No-Ack: yes X-Attribution: GM Date: Sat, 15 Feb 2014 17:07:38 -0500 Message-ID: User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: -5.7 (-----) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, martin rudalics X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.7 (-----) 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 branch nick: trunk timestamp: Sat 2014-01-11 10:31:09 +0100 message: Fix handling of internal borders (Bug#16348). From debbugs-submit-bounces@debbugs.gnu.org Sun Feb 16 05:31:44 2014 Received: (at 16736) by debbugs.gnu.org; 16 Feb 2014 10:31:44 +0000 Received: from localhost ([127.0.0.1]:54286 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEz0h-0004st-Hx for submit@debbugs.gnu.org; Sun, 16 Feb 2014 05:31:43 -0500 Received: from mout.gmx.net ([212.227.17.22]:50385) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WEz0e-0004sd-Jn for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 05:31:41 -0500 Received: from [62.47.47.61] ([62.47.47.61]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0Lhwgc-1X1o6J2jje-00nDBr for <16736@debbugs.gnu.org>; Sun, 16 Feb 2014 11:31:33 +0100 Message-ID: <53009381.6020800@gmx.at> Date: Sun, 16 Feb 2014 11:31:29 +0100 From: martin rudalics MIME-Version: 1.0 To: Glenn Morris Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:CLkfrPg34o89LBZSJjCVWShcCLlO9ZDsWefdx59r/oL0+ZVugCK FxGOq8/EphjgVq/bqRr6uAojdf1VfsbIFPDMzNEKLKNGaZ9sXP4GBBY7hzT2XPtmjjxjIE3 ZSD0L6CFbbHtDqdTq36/p46ZjoMruxJ+8znLf+4OgcVrX1okh7hMK9BQk42BzasmfSX7zhb EJFkx9sDwAcQ6SpbwRGHQ== X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, Eli Zaretskii X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) > Bisected to: > > revno: 115971 > committer: martin rudalics > branch nick: trunk > timestamp: Sat 2014-01-11 10:31:09 +0100 > message: > Fix handling of internal borders (Bug#16348). Does anything change when you set the frame's internal border width to zero? Does anything change when you disable the calls to x_clear_under_internal_border? If so, can you spot one of these calls as the offending one? I'm yet too silly to understand what's going on here. Thanks, martin From debbugs-submit-bounces@debbugs.gnu.org Sun Feb 16 11:17:41 2014 Received: (at 16736) by debbugs.gnu.org; 16 Feb 2014 16:17:42 +0000 Received: from localhost ([127.0.0.1]:54922 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WF4PU-0007gj-FB for submit@debbugs.gnu.org; Sun, 16 Feb 2014 11:17:41 -0500 Received: from mtaout23.012.net.il ([80.179.55.175]:54925) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WF4PQ-0007gL-E8 for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 11:17:38 -0500 Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0N1300C00JVECO00@a-mtaout23.012.net.il> for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 18:17:29 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N1300C8YJX5AF50@a-mtaout23.012.net.il>; Sun, 16 Feb 2014 18:17:29 +0200 (IST) Date: Sun, 16 Feb 2014 18:17:32 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: X-012-Sender: halo1@inter.net.il To: Glenn Morris Message-id: <83zjlr9gmb.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > From: Glenn Morris > Cc: 16736@debbugs.gnu.org > Date: Sat, 15 Feb 2014 16:28:13 -0500 > > > 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. Can you show a backtrace from that breakpoint? > 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'm interested in seeing what happens the first time this breakpoint breaks after you type "C-x 2" in *scratch*. (On my system, this is the only time it breaks after "C-x 2"; do you see something different?) > 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 These look identical to me. Are you saying that tracing into update_window_line and then update_text_area for these two, you see that the loop which starts at line 3598 ends with i's value smaller than desired_row->used[TEXT_AREA], and you see these 3 lines (3696 to 3698) being executed: output_cursor_to (w, vpos, start_hpos, desired_row->y, start_x); rif->write_glyphs (w, updated_row, start, TEXT_AREA, i - start_hpos); changed_p = 1; Again, please trace all this upon the first time the breakpoint on line 3045 breaks after "C-x 2". > I'll try again later, but frankly I don't know what I'm doing, even > with your detailed instructions. Thanks. Feel free to ask questions about things you'd like to understand. In a nutshell, this is part of the code that updates the window after Emacs has determined that some window(s) need to be updated, in this case, due to "C-x 2" that created a new window and made the old one smaller. The code I pointed to updates the tool-bar window when anything on the tool bar changes, or refrains from updating it if the tool bar did not change at all (which should happen in this case). From debbugs-submit-bounces@debbugs.gnu.org Sun Feb 16 11:22:44 2014 Received: (at 16736) by debbugs.gnu.org; 16 Feb 2014 16:22:44 +0000 Received: from localhost ([127.0.0.1]:54926 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WF4UN-0007pJ-9a for submit@debbugs.gnu.org; Sun, 16 Feb 2014 11:22:43 -0500 Received: from mtaout27.012.net.il ([80.179.55.183]:54636) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WF4UL-0007p3-8z for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 11:22:42 -0500 Received: from conversion-daemon.mtaout27.012.net.il by mtaout27.012.net.il (HyperSendmail v2007.08) id <0N1300C00JPYJJ00@mtaout27.012.net.il> for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 18:21:01 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout27.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N13007EXK31QC70@mtaout27.012.net.il>; Sun, 16 Feb 2014 18:21:01 +0200 (IST) Date: Sun, 16 Feb 2014 18:22:38 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: X-012-Sender: halo1@inter.net.il To: Glenn Morris Message-id: <83y51b9gdt.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rudalics@gmx.at X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > From: Glenn Morris > Cc: 16736@debbugs.gnu.org, martin rudalics > 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 > 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) From debbugs-submit-bounces@debbugs.gnu.org Sun Feb 16 11:46:58 2014 Received: (at 16736) by debbugs.gnu.org; 16 Feb 2014 16:46:58 +0000 Received: from localhost ([127.0.0.1]:54932 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WF4rp-0008S4-RA for submit@debbugs.gnu.org; Sun, 16 Feb 2014 11:46:58 -0500 Received: from mtaout20.012.net.il ([80.179.55.166]:42053) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WF4rm-0008Rl-NT for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 11:46:55 -0500 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0N1300900L68GI00@a-mtaout20.012.net.il> for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 18:46:47 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N13009UZL9Z7770@a-mtaout20.012.net.il>; Sun, 16 Feb 2014 18:46:47 +0200 (IST) Date: Sun, 16 Feb 2014 18:46:50 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: <53009381.6020800@gmx.at> X-012-Sender: halo1@inter.net.il To: martin rudalics Message-id: <83vbwf9f9h.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <53009381.6020800@gmx.at> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > Date: Sun, 16 Feb 2014 11:31:29 +0100 > From: martin rudalics > CC: Eli Zaretskii , 16736@debbugs.gnu.org > > > Bisected to: > > > > revno: 115971 > > committer: martin rudalics > > branch nick: trunk > > timestamp: Sat 2014-01-11 10:31:09 +0100 > > message: > > Fix handling of internal borders (Bug#16348). > > Does anything change when you set the frame's internal border width to > zero? Does anything change when you disable the calls to > x_clear_under_internal_border? If so, can you spot one of these calls > as the offending one? I'm yet too silly to understand what's going on > here. 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. From debbugs-submit-bounces@debbugs.gnu.org Sun Feb 16 12:14:59 2014 Received: (at 16736) by debbugs.gnu.org; 16 Feb 2014 17:14:59 +0000 Received: from localhost ([127.0.0.1]:54953 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WF5Iw-0001tj-NE for submit@debbugs.gnu.org; Sun, 16 Feb 2014 12:14:59 -0500 Received: from mout.gmx.net ([212.227.15.19]:60641) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WF5It-0001tQ-Qk for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 12:14:56 -0500 Received: from [62.47.43.37] ([62.47.43.37]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0Lt2BW-1XHCHi0ess-012bio for <16736@debbugs.gnu.org>; Sun, 16 Feb 2014 18:14:48 +0100 Message-ID: <5300F203.1070108@gmx.at> Date: Sun, 16 Feb 2014 18:14:43 +0100 From: martin rudalics MIME-Version: 1.0 To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <53009381.6020800@gmx.at> <83vbwf9f9h.fsf@gnu.org> In-Reply-To: <83vbwf9f9h.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:YEPRXv2z8hVfzq7QPd+5kgCOOmZ/9nzSutAgH1mmrpGe4AgypJ5 fxdB0+Dvr8O4+NX44RONeyCujlHX0NKnpG2G80v6xzFceGLGTnDf7PX4Rl3L3F4huK8i/sw BIhamLApWUJ62arL8oxGyTAO6OUnbfSPJQ4s11fKOLbdBVswj8VaUtwPRPfk96xfwut47x4 tnqLkXXdB0VCThOE3b7Jw== X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) > 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 From debbugs-submit-bounces@debbugs.gnu.org Sun Feb 16 14:48:14 2014 Received: (at 16736) by debbugs.gnu.org; 16 Feb 2014 19:48:14 +0000 Received: from localhost ([127.0.0.1]:55007 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WF7hF-0005x1-P6 for submit@debbugs.gnu.org; Sun, 16 Feb 2014 14:48:14 -0500 Received: from fencepost.gnu.org ([208.118.235.10]:40964 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WF7hD-0005wr-PQ for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 14:48:12 -0500 Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1WF7hC-0007Pn-Qq; Sun, 16 Feb 2014 14:48:10 -0500 From: Glenn Morris To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83zjlr9gmb.fsf@gnu.org> X-Spook: Sears Tower Albright lynch Europol Semtex Armani Kh-11 X-Ran: 4Hu.XDy.kS.Faxy>t%Qu/x| (Eli Zaretskii's message of "Sun, 16 Feb 2014 18:17:32 +0200") Message-ID: User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: -5.6 (-----) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.6 (-----) Eli Zaretskii wrote: >> I put a break on x_clear_frame, and with emacs -Q, byte-compile-file on >> scheme.el triggers it. > > Can you show a backtrace from that breakpoint? Easy enough. #0 x_clear_frame (f=0x11cd8b8) at xterm.c:2909 #1 0x00000000004ece00 in clear_frame (f=0x11cd8b8) at terminal.c:140 #2 0x0000000000417f8f in redraw_frame (f=0x11cd8b8) at dispnew.c:2955 #3 0x0000000000448e4d in clear_garbaged_frames () at xdisp.c:10935 #4 0x0000000000448fb9 in echo_area_display (update_frame_p=1) at xdisp.c:10979 #5 0x000000000044703a in message3_nolog (m=14191025) at xdisp.c:9987 #6 0x0000000000446de9 in message3 (m=14191025) at xdisp.c:9929 #7 0x00000000005b560f in Fmessage (nargs=3, args=0x7fffffff8338) at editfns.c:3452 #8 0x00000000005c0e83 in Ffuncall (nargs=4, args=0x7fffffff8330) at eval.c:2796 #9 0x0000000000600e44 in exec_byte_code (bytestr=13161473, vector=19239277, maxdepth=72, args_template=5140, nargs=5, args=0x7fffffff88d8) at bytecode.c:919 #10 0x00000000005c16b2 in funcall_lambda (fun=18472445, nargs=5, arg_vector=0x7fffffff88b0) at eval.c:2983 #11 0x00000000005c11a7 in Ffuncall (nargs=6, args=0x7fffffff88a8) at eval.c:2864 #12 0x0000000000600e44 in exec_byte_code (bytestr=14003153, vector=18902205, maxdepth=32, args_template=2056, nargs=2, args=0x7fffffff8e68) at bytecode.c:919 #13 0x00000000005c16b2 in funcall_lambda (fun=18951917, nargs=2, arg_vector=0x7fffffff8e58) at eval.c:2983 #14 0x00000000005c11a7 in Ffuncall (nargs=3, args=0x7fffffff8e50) at eval.c:2864 #15 0x0000000000600e44 in exec_byte_code (bytestr=14003009, vector=18997205, maxdepth=64, args_template=6168, nargs=6, args=0x7fffffff9420) at bytecode.c:919 #16 0x00000000005c16b2 in funcall_lambda (fun=18997301, nargs=6, arg_vector=0x7fffffff93f0) at eval.c:2983 #17 0x00000000005c11a7 in Ffuncall (nargs=7, args=0x7fffffff93e8) at eval.c:2864 #18 0x0000000000600e44 in exec_byte_code (bytestr=14002977, vector=18073693, maxdepth=68, args_template=5140, nargs=5, args=0x7fffffff99e8) at bytecode.c:919 #19 0x00000000005c16b2 in funcall_lambda (fun=18997349, nargs=5, arg_vector=0x7fffffff99c0) at eval.c:2983 #20 0x00000000005c11a7 in Ffuncall (nargs=6, args=0x7fffffff99b8) at eval.c:2864 #21 0x0000000000600e44 in exec_byte_code (bytestr=14002785, vector=18997397, maxdepth=120, args_template=1028, nargs=1, args=0x7fffffff9f68) at bytecode.c:919 #22 0x00000000005c16b2 in funcall_lambda (fun=18997477, nargs=1, arg_vector=0x7fffffff9f60) at eval.c:2983 #23 0x00000000005c11a7 in Ffuncall (nargs=2, args=0x7fffffff9f58) at eval.c:2864 #24 0x0000000000600e44 in exec_byte_code (bytestr=21918129, vector=17903693, maxdepth=16, args_template=1028, nargs=1, args=0x7fffffffa4a0) at bytecode.c:919 #25 0x00000000005c16b2 in funcall_lambda (fun=17919557, nargs=1, arg_vector=0x7fffffffa498) at eval.c:2983 #26 0x00000000005c11a7 in Ffuncall (nargs=2, args=0x7fffffffa490) at eval.c:2864 #27 0x0000000000600e44 in exec_byte_code (bytestr=21918449, vector=17903597, maxdepth=20, args_template=1028, nargs=1, args=0x7fffffffa9e0) at bytecode.c:919 #28 0x00000000005c16b2 in funcall_lambda (fun=17903645, nargs=1, arg_vector=0x7fffffffa9d8) at eval.c:2983 #29 0x00000000005c11a7 in Ffuncall (nargs=2, args=0x7fffffffa9d0) at eval.c:2864 #30 0x0000000000600e44 in exec_byte_code (bytestr=14339425, vector=19017693, maxdepth=16, args_template=0, nargs=0, args=0x7fffffffaf10) at bytecode.c:919 #31 0x00000000005c16b2 in funcall_lambda (fun=19017861, nargs=0, arg_vector=0x7fffffffaf10) at eval.c:2983 #32 0x00000000005c11a7 in Ffuncall (nargs=1, args=0x7fffffffaf08) at eval.c:2864 #33 0x0000000000600e44 in exec_byte_code (bytestr=14364257, vector=19207309, maxdepth=4, args_template=0, nargs=0, args=0x7fffffffb438) at bytecode.c:919 #34 0x00000000005c16b2 in funcall_lambda (fun=19308733, nargs=0, arg_vector=0x7fffffffb438) at eval.c:2983 #35 0x00000000005c11a7 in Ffuncall (nargs=1, args=0x7fffffffb430) at eval.c:2864 #36 0x00000000005bfa48 in eval_sub (form=13338950) at eval.c:2157 #37 0x00000000005bdd6a in internal_lisp_condition_case (var=14018162, bodyform=13338950, handlers=13339046) at eval.c:1323 #38 0x0000000000601ff5 in exec_byte_code (bytestr=21623585, vector=19198157, maxdepth=64, args_template=1028, nargs=1, args=0x7fffffffbc48) at bytecode.c:1169 #39 0x00000000005c16b2 in funcall_lambda (fun=16683157, nargs=1, arg_vector=0x7fffffffbc40) at eval.c:2983 #40 0x00000000005c11a7 in Ffuncall (nargs=2, args=0x7fffffffbc38) at eval.c:2864 #41 0x0000000000600e44 in exec_byte_code (bytestr=21665569, vector=18963773, maxdepth=68, args_template=2052, nargs=1, args=0x7fffffffc1a8) at bytecode.c:919 #42 0x00000000005c16b2 in funcall_lambda (fun=16684125, nargs=1, arg_vector=0x7fffffffc1a0) at eval.c:2983 #43 0x00000000005c11a7 in Ffuncall (nargs=2, args=0x7fffffffc198) at eval.c:2864 #44 0x0000000000600e44 in exec_byte_code (bytestr=10789089, vector=10789125, maxdepth=8, args_template=0, nargs=0, args=0x7fffffffc6d0) at bytecode.c:919 #45 0x00000000005c16b2 in funcall_lambda (fun=10789037, nargs=0, arg_vector=0x7fffffffc6d0) at eval.c:2983 #46 0x00000000005c11a7 in Ffuncall (nargs=1, args=0x7fffffffc6c8) at eval.c:2864 #47 0x00000000005c08c7 in apply1 (fn=20569570, arg=12757298) at eval.c:2581 #48 0x00000000005b9cd3 in Fcall_interactively (function=20569570, record_flag=12757298, keys=12792317) at callint.c:378 #49 0x00000000005c1014 in Ffuncall (nargs=4, args=0x7fffffffc9f8) at eval.c:2822 #50 0x0000000000600e44 in exec_byte_code (bytestr=10183985, vector=10184021, maxdepth=52, args_template=4100, nargs=1, args=0x7fffffffcf60) at bytecode.c:919 #51 0x00000000005c16b2 in funcall_lambda (fun=10183941, nargs=1, arg_vector=0x7fffffffcf58) at eval.c:2983 #52 0x00000000005c11a7 in Ffuncall (nargs=2, args=0x7fffffffcf50) at eval.c:2864 #53 0x00000000005c096c in call1 (fn=12801186, arg1=20569570) at eval.c:2614 #54 0x0000000000531592 in command_loop_1 () at keyboard.c:1556 #55 0x00000000005bdecd in internal_condition_case ( bfun=0x530eab , handlers=12808898, hfun=0x5307bd ) at eval.c:1354 #56 0x0000000000530c05 in command_loop_2 (ignore=12757298) at keyboard.c:1174 #57 0x00000000005bd6df in internal_catch (tag=12804834, func=0x530bdf , arg=12757298) at eval.c:1118 #58 0x0000000000530bb3 in command_loop () at keyboard.c:1153 #59 0x00000000005303b8 in recursive_edit_1 () at keyboard.c:777 #60 0x0000000000530525 in Frecursive_edit () at keyboard.c:845 #61 0x000000000052e550 in main (argc=3, argv=0x7fffffffd438) at emacs.c:1643 Lisp Backtrace: "message" (0xffff8338) "byte-compile-file-form-defmumble" (0xffff88b0) 0x1212ee8 PVEC_COMPILED 0x121e030 PVEC_COMPILED 0x121e060 PVEC_COMPILED "byte-compile-file-form-defalias" (0xffff9f60) "byte-compile-file-form" (0xffffa498) "byte-compile-toplevel-file-form" (0xffffa9d8) 0x1223080 PVEC_COMPILED 0x126a0b8 PVEC_COMPILED "funcall" (0xffffb430) "byte-compile-from-buffer" (0xffffbc40) "byte-compile-file" (0xffffc1a0) "emacs-lisp-byte-compile" (0xffffc6d0) "call-interactively" (0xffffca00) "command-execute" (0xffffcf58) I don't have time to look into the rest of the things you asked right now. From debbugs-submit-bounces@debbugs.gnu.org Sun Feb 16 16:04:25 2014 Received: (at 16736) by debbugs.gnu.org; 16 Feb 2014 21:04:25 +0000 Received: from localhost ([127.0.0.1]:55046 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WF8sy-000862-GM for submit@debbugs.gnu.org; Sun, 16 Feb 2014 16:04:24 -0500 Received: from mtaout25.012.net.il ([80.179.55.181]:49058) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WF8su-00085k-Mk for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 16:04:22 -0500 Received: from conversion-daemon.mtaout25.012.net.il by mtaout25.012.net.il (HyperSendmail v2007.08) id <0N1300N00X2W6S00@mtaout25.012.net.il> for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 23:03:06 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout25.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N1300JSFX56X630@mtaout25.012.net.il>; Sun, 16 Feb 2014 23:03:06 +0200 (IST) Date: Sun, 16 Feb 2014 23:04:18 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: X-012-Sender: halo1@inter.net.il To: Glenn Morris Message-id: <83lhxaahwt.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83zjlr9gmb.fsf@gnu.org> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > From: Glenn Morris > Cc: 16736@debbugs.gnu.org > Date: Sun, 16 Feb 2014 14:48:10 -0500 > > Eli Zaretskii wrote: > > >> I put a break on x_clear_frame, and with emacs -Q, byte-compile-file on > >> scheme.el triggers it. > > > > Can you show a backtrace from that breakpoint? > > Easy enough. > > #0 x_clear_frame (f=0x11cd8b8) at xterm.c:2909 > #1 0x00000000004ece00 in clear_frame (f=0x11cd8b8) at terminal.c:140 > #2 0x0000000000417f8f in redraw_frame (f=0x11cd8b8) at dispnew.c:2955 > #3 0x0000000000448e4d in clear_garbaged_frames () at xdisp.c:10935 > #4 0x0000000000448fb9 in echo_area_display (update_frame_p=1) at xdisp.c:10979 > #5 0x000000000044703a in message3_nolog (m=14191025) at xdisp.c:9987 > #6 0x0000000000446de9 in message3 (m=14191025) at xdisp.c:9929 > #7 0x00000000005b560f in Fmessage (nargs=3, args=0x7fffffff8338) > at editfns.c:3452 Thanks. This clearly shows that the frame was marked as "garbaged", which naturally requires its complete redrawing. The question now becomes why it is marked garbaged. It's possible that the change in change_frame_size_1 is the reason, because the code in that function does just that. > I don't have time to look into the rest of the things you asked right > now. I hope you will some time soon, as I think we are zeroing in on the culprit. Thanks. From debbugs-submit-bounces@debbugs.gnu.org Sun Feb 16 19:53:09 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 00:53:09 +0000 Received: from localhost ([127.0.0.1]:55182 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFCSL-0005mn-Ay for submit@debbugs.gnu.org; Sun, 16 Feb 2014 19:53:09 -0500 Received: from fencepost.gnu.org ([208.118.235.10]:45208 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFCSJ-0005mf-3a for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 19:53:07 -0500 Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1WFCSI-0007Ml-73; Sun, 16 Feb 2014 19:53:06 -0500 From: Glenn Morris To: martin rudalics Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <53009381.6020800@gmx.at> X-Spook: ASIO NSA spies warfare Islam Abduganievich Karimov X-Ran: \R;K",;tYLIvlL(o)E4\C.*3+cgfL@]8T+N{OO-=Bk\^d[0*QKzpR$"vBM6'+?V~](r$8& X-Hue: white X-Debbugs-No-Ack: yes X-Attribution: GM Date: Sun, 16 Feb 2014 19:53:06 -0500 In-Reply-To: <53009381.6020800@gmx.at> (martin rudalics's message of "Sun, 16 Feb 2014 11:31:29 +0100") Message-ID: <82wqguo8zx.fsf@fencepost.gnu.org> User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: -5.6 (-----) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, Eli Zaretskii X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.6 (-----) martin rudalics wrote: > Does anything change when you set the frame's internal border width to > zero? emacs -Q -ib 0 seems the same. > Does anything change when you disable the calls to > x_clear_under_internal_border? AFAICS, that function is not defined for me, since USE_X_TOOLKIT = 1. From debbugs-submit-bounces@debbugs.gnu.org Sun Feb 16 19:58:21 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 00:58:21 +0000 Received: from localhost ([127.0.0.1]:55188 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFCXN-0005v6-7d for submit@debbugs.gnu.org; Sun, 16 Feb 2014 19:58:21 -0500 Received: from fencepost.gnu.org ([208.118.235.10]:45309 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFCXL-0005uq-K6 for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 19:58:19 -0500 Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1WFCXF-0001S0-Q0; Sun, 16 Feb 2014 19:58:13 -0500 From: Glenn Morris To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> X-Spook: Qaddafi kilo class CIDA illuminati Indigo Croatian IDEA X-Ran: Cd^aSQ6,(;W!i)AT/L|6#_+(;F_LS}JXkG3;DNeaxsO$vwTyV+}~Ap%)ZW?.\VXRrx#4GK X-Hue: cyan X-Debbugs-No-Ack: yes X-Attribution: GM Date: Sun, 16 Feb 2014 19:58:13 -0500 In-Reply-To: <83y51b9gdt.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 16 Feb 2014 18:22:38 +0200") Message-ID: <0ssirio8re.fsf@fencepost.gnu.org> User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: -5.6 (-----) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rudalics@gmx.at X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.6 (-----) Eli Zaretskii wrote: > 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*? Yes, it does. > 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) 640 640 672 672 674 1 From debbugs-submit-bounces@debbugs.gnu.org Sun Feb 16 20:18:43 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 01:18:43 +0000 Received: from localhost ([127.0.0.1]:55194 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFCr5-0006US-5S for submit@debbugs.gnu.org; Sun, 16 Feb 2014 20:18:43 -0500 Received: from fencepost.gnu.org ([208.118.235.10]:45696 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFCr3-0006UG-2F for 16736@debbugs.gnu.org; Sun, 16 Feb 2014 20:18:41 -0500 Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1WFCr1-0007WH-UV; Sun, 16 Feb 2014 20:18:39 -0500 From: Glenn Morris To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83zjlr9gmb.fsf@gnu.org> X-Spook: ISEC CID bullion Al Jazeera SDI rs9512c NATO clones X-Ran: [SGo<_*WBreb;{V7Z]?iB-,P7=)k3]2{]m(X#tJ]h_y75vh3MDY~ck:pDt{K"W61k9R$-E X-Hue: yellow X-Debbugs-No-Ack: yes X-Attribution: GM Date: Sun, 16 Feb 2014 20:18:39 -0500 Message-ID: User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: -5.6 (-----) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.6 (-----) Eli Zaretskii wrote: >> In an attempt to follow your instructions, I put a break on dispnew.c:3045. [...] > I'm interested in seeing what happens the first time this breakpoint > breaks after you type "C-x 2" in *scratch*. (On my system, this is > the only time it breaks after "C-x 2"; do you see something > different?) I do gdb> run -Q and continue a few times until Emacs starts up. If I then select the Emacs window with the mouse, it breaks twice, so I have to reselect the gdb window to get it to continue, and then when I select the Emacs window... Anyway, I can get around that by alt-tabbing back into Emacs. > Are you saying that tracing into update_window_line and then > update_text_area for these two, you see that the loop which starts at > line 3598 ends with i's value smaller than > desired_row->used[TEXT_AREA], and you see these 3 lines (3696 to 3698) > being executed: That does not seem to happen, no. I have i = stop = 13 = desired_row->used[TEXT_AREA]. > Again, please trace all this upon the first time the breakpoint on > line 3045 breaks after "C-x 2". From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 17 00:14:17 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 05:14:17 +0000 Received: from localhost ([127.0.0.1]:55551 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFGX3-0004ir-6q for submit@debbugs.gnu.org; Mon, 17 Feb 2014 00:14:17 -0500 Received: from mtaout23.012.net.il ([80.179.55.175]:42198) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFGX0-0004id-WE for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 00:14:15 -0500 Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0N1400E00JHBF500@a-mtaout23.012.net.il> for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 07:14:08 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N1400ESLJVKEB30@a-mtaout23.012.net.il>; Mon, 17 Feb 2014 07:14:08 +0200 (IST) Date: Mon, 17 Feb 2014 07:14:13 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: <0ssirio8re.fsf@fencepost.gnu.org> X-012-Sender: halo1@inter.net.il To: Glenn Morris Message-id: <83eh329v8a.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rudalics@gmx.at X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > From: Glenn Morris > Cc: 16736@debbugs.gnu.org, rudalics@gmx.at > Date: Sun, 16 Feb 2014 19:58:13 -0500 > > Eli Zaretskii wrote: > > > 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*? > > Yes, it does. > > > 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) > > 640 > 640 > 672 > 672 > 674 > 1 OK, then that's the root cause, right there: this function continues to do this: adjust_frame_glyphs (f); calculate_costs (f); SET_FRAME_GARBAGED (f); f->resized_p = 1; which marks the frame "garbaged" and requires its complete redisplay, that starts with clearing it (as you have demonstrated in your backtrace a few messages ago), and continues by redrawing the tool bar. Martin, any ideas why this happens in a toolkit build? I don't understand how come this condition: if (new_text_height == FRAME_TEXT_HEIGHT (f) && new_text_width == FRAME_TEXT_WIDTH (f) && new_root_width == old_root_width && (FRAME_PIXEL_HEIGHT (f) == FRAME_TEXT_TO_PIXEL_HEIGHT (f, new_text_height)) && (FRAME_PIXEL_WIDTH (f) == FRAME_TEXT_TO_PIXEL_WIDTH (f, new_text_width))) return; fails to cause the function to return. The reason must be in the 2 last conditions, which you added in revision 115971. Glenn, can you show the values of FRAME_PIXEL_HEIGHT (f) and FRAME_PIXEL_WIDTH (f) in this scenario? From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 17 00:15:23 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 05:15:23 +0000 Received: from localhost ([127.0.0.1]:55555 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFGY6-0004l5-W2 for submit@debbugs.gnu.org; Mon, 17 Feb 2014 00:15:23 -0500 Received: from mtaout23.012.net.il ([80.179.55.175]:42242) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFGY4-0004kp-NO for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 00:15:21 -0500 Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0N1400E00JHBF500@a-mtaout23.012.net.il> for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 07:15:15 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N1400E19JXEEB40@a-mtaout23.012.net.il>; Mon, 17 Feb 2014 07:15:15 +0200 (IST) Date: Mon, 17 Feb 2014 07:15:19 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: X-012-Sender: halo1@inter.net.il To: Glenn Morris Message-id: <83d2im9v6g.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83zjlr9gmb.fsf@gnu.org> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > From: Glenn Morris > Cc: 16736@debbugs.gnu.org > Date: Sun, 16 Feb 2014 20:18:39 -0500 > > > Are you saying that tracing into update_window_line and then > > update_text_area for these two, you see that the loop which starts at > > line 3598 ends with i's value smaller than > > desired_row->used[TEXT_AREA], and you see these 3 lines (3696 to 3698) > > being executed: > > That does not seem to happen, no. > I have i = stop = 13 = desired_row->used[TEXT_AREA]. That figures: the problem is not that the rows differ, the problem is that Emacs thinks the frame is garbaged, and redraws it unconditionally. From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 17 02:45:46 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 07:45:46 +0000 Received: from localhost ([127.0.0.1]:55698 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFItd-0000jn-E4 for submit@debbugs.gnu.org; Mon, 17 Feb 2014 02:45:45 -0500 Received: from fencepost.gnu.org ([208.118.235.10]:52030 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFItb-0000jd-4a for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 02:45:43 -0500 Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1WFItY-0003LD-KY; Mon, 17 Feb 2014 02:45:40 -0500 From: Glenn Morris To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> X-Spook: Arnett smuggle USDOJ SCUD missile fundamentalist genetic X-Ran: %6RS0$-u9@SU}/#0oAf/d0T@Y/7my@:$uN9Umnj1oP%<<{-`Eaj[z{Z+MQyPIkLYZOR!V5 X-Hue: red X-Debbugs-No-Ack: yes X-Attribution: GM Date: Mon, 17 Feb 2014 02:45:40 -0500 In-Reply-To: <83eh329v8a.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 17 Feb 2014 07:14:13 +0200") Message-ID: <0nlhxa18t7.fsf@fencepost.gnu.org> User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: -5.6 (-----) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rudalics@gmx.at X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.6 (-----) Eli Zaretskii wrote: > if (new_text_height == FRAME_TEXT_HEIGHT (f) > && new_text_width == FRAME_TEXT_WIDTH (f) > && new_root_width == old_root_width > && (FRAME_PIXEL_HEIGHT (f) == > FRAME_TEXT_TO_PIXEL_HEIGHT (f, new_text_height)) > && (FRAME_PIXEL_WIDTH (f) == > FRAME_TEXT_TO_PIXEL_WIDTH (f, new_text_width))) > return; new_text_height = 570 = FRAME_TEXT_HEIGHT (f) new_text_width = 640 = FRAME_TEXT_WIDTH (f) new_root_width = 672 = old_root_width FRAME_PIXEL_HEIGHT (f) = 605 FRAME_TEXT_TO_PIXEL_HEIGHT (f, new_text_height) = 572 new_text_height = 570 FRAME_PIXEL_WIDTH (f) = 674 = FRAME_TEXT_TO_PIXEL_WIDTH (f, new_text_width) new_text_width = 640 From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 17 10:42:49 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 15:42:49 +0000 Received: from localhost ([127.0.0.1]:56672 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFQLJ-0000mE-1P for submit@debbugs.gnu.org; Mon, 17 Feb 2014 10:42:49 -0500 Received: from mtaout26.012.net.il ([80.179.55.182]:59054) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFQLF-0000ly-NU for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 10:42:47 -0500 Received: from conversion-daemon.mtaout26.012.net.il by mtaout26.012.net.il (HyperSendmail v2007.08) id <0N1500K00CN4D400@mtaout26.012.net.il> for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 17:41:03 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout26.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N1500E6BCWFU070@mtaout26.012.net.il>; Mon, 17 Feb 2014 17:41:03 +0200 (IST) Date: Mon, 17 Feb 2014 17:42:45 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: <0nlhxa18t7.fsf@fencepost.gnu.org> X-012-Sender: halo1@inter.net.il To: Glenn Morris Message-id: <83wqgt924q.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rudalics@gmx.at X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > From: Glenn Morris > Cc: 16736@debbugs.gnu.org, rudalics@gmx.at > Date: Mon, 17 Feb 2014 02:45:40 -0500 > > Eli Zaretskii wrote: > > > if (new_text_height == FRAME_TEXT_HEIGHT (f) > > && new_text_width == FRAME_TEXT_WIDTH (f) > > && new_root_width == old_root_width > > && (FRAME_PIXEL_HEIGHT (f) == > > FRAME_TEXT_TO_PIXEL_HEIGHT (f, new_text_height)) > > && (FRAME_PIXEL_WIDTH (f) == > > FRAME_TEXT_TO_PIXEL_WIDTH (f, new_text_width))) > > return; > > new_text_height = 570 = FRAME_TEXT_HEIGHT (f) > new_text_width = 640 = FRAME_TEXT_WIDTH (f) > new_root_width = 672 = old_root_width > > FRAME_PIXEL_HEIGHT (f) = 605 > FRAME_TEXT_TO_PIXEL_HEIGHT (f, new_text_height) = 572 > new_text_height = 570 Looks like FRAME_PIXEL_HEIGHT includes the tool bar, and is thus 33 pixels larger than we expect. (What is f->tool_bar_height?) But I cannot find the place where we assign any value to FRAME_PIXEL_HEIGHT, except in this very function, so I'm unsure where do those extra 33 pixels come from. Glenn, if you put a breakpoint in change_frame_size_1 and then just "run -Q", can you show all the calls you see until Emacs starts up, including the arguments we pass to that function? Here's what I see on Windows: (gdb) break change_frame_size_1 Breakpoint 3 at 0x100d809: file dispnew.c, line 5467. (gdb) r -Q Starting program: D:\gnu\bzr\emacs\trunk\src\emacs.exe -Q [New Thread 2272.0x13c0] [New Thread 2272.0x1790] [New Thread 2272.0x324] Breakpoint 3, change_frame_size_1 (f=0x394a9d8, new_width=80, new_height=160, pretend=true, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); (gdb) c Continuing. Breakpoint 3, change_frame_size_1 (f=0x394a9d8, new_width=640, new_height=608, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); (gdb) Continuing. Breakpoint 3, change_frame_size_1 (f=0x394a9d8, new_width=640, new_height=608, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); (gdb) Continuing. Breakpoint 3, change_frame_size_1 (f=0x394a9d8, new_width=640, new_height=608, pretend=false, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); (gdb) Continuing. Breakpoint 3, change_frame_size_1 (f=0x394a9d8, new_width=0, new_height=0, pretend=false, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); (gdb) Continuing. Breakpoint 3, change_frame_size_1 (f=0x394a9d8, new_width=640, new_height=608, pretend=true, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); (gdb) Continuing. (The 640x608 size corresponds to the 80x35 text size I get (35 includes the mode line and the echo area), plus the equivalent of 3 text lines used for the tool bar.) From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 17 11:23:41 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 16:23:41 +0000 Received: from localhost ([127.0.0.1]:56791 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFQyr-0001yS-3V for submit@debbugs.gnu.org; Mon, 17 Feb 2014 11:23:41 -0500 Received: from mout.gmx.net ([212.227.17.21]:53753) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFQyo-0001yF-Ec for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 11:23:39 -0500 Received: from [62.47.56.45] ([62.47.56.45]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0LaXEN-1X0YmK2inn-00mNM8 for <16736@debbugs.gnu.org>; Mon, 17 Feb 2014 17:23:31 +0100 Message-ID: <5302377D.3070007@gmx.at> Date: Mon, 17 Feb 2014 17:23:25 +0100 From: martin rudalics MIME-Version: 1.0 To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> <83wqgt924q.fsf@gnu.org> In-Reply-To: <83wqgt924q.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:8W3HLx0vnx1+PKD6qLOR7VsnxS482g0CgOcIf05v57eVORV/fcB xQdFJKSVe3CB/s/XfE8MzwXhLSIOEuSejYqs3rgTkJyyQJy0bqDT4JIJAJOB/hWo3Sa0cII 6AQXN15AyYaLNBcW/cy2F1rQmK+z46lqYs6pHhdH8FvtSABfodonX+2Mo2PRqq1w9q7Li+o Fc4dthDvgbqhK4y6IGUlA== X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, Glenn Morris X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) > Looks like FRAME_PIXEL_HEIGHT includes the tool bar, and is thus 33 > pixels larger than we expect. (What is f->tool_bar_height?) But I > cannot find the place where we assign any value to FRAME_PIXEL_HEIGHT, > except in this very function, so I'm unsure where do those extra 33 > pixels come from. It's from update_various_frame_slots in widget.c. If you comment that out, the problem disappears. But I don't know yet whether it's needed elsewhere ... martin From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 17 11:50:43 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 16:50:43 +0000 Received: from localhost ([127.0.0.1]:56819 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFRP1-0002gv-7w for submit@debbugs.gnu.org; Mon, 17 Feb 2014 11:50:43 -0500 Received: from mtaout23.012.net.il ([80.179.55.175]:58225) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFROy-0002gd-UJ for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 11:50:41 -0500 Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0N1500H00FXV8U00@a-mtaout23.012.net.il> for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 18:50:34 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N1500HO6G4A8X00@a-mtaout23.012.net.il>; Mon, 17 Feb 2014 18:50:34 +0200 (IST) Date: Mon, 17 Feb 2014 18:50:40 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: <5302377D.3070007@gmx.at> X-012-Sender: halo1@inter.net.il To: martin rudalics Message-id: <83iosd8yzj.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> <83wqgt924q.fsf@gnu.org> <5302377D.3070007@gmx.at> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > Date: Mon, 17 Feb 2014 17:23:25 +0100 > From: martin rudalics > CC: Glenn Morris , 16736@debbugs.gnu.org > > > Looks like FRAME_PIXEL_HEIGHT includes the tool bar, and is thus 33 > > pixels larger than we expect. (What is f->tool_bar_height?) But I > > cannot find the place where we assign any value to FRAME_PIXEL_HEIGHT, > > except in this very function, so I'm unsure where do those extra 33 > > pixels come from. > > It's from update_various_frame_slots in widget.c. If you comment that > out, the problem disappears. But I don't know yet whether it's needed > elsewhere ... If you mean this: FRAME_PIXEL_HEIGHT (f) = ew->core.height + x->menubar_height; then does it mean that menubar_height is 33 pixels? Sounds too much to me. From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 17 12:17:02 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 17:17:02 +0000 Received: from localhost ([127.0.0.1]:56850 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFRoT-0003Oq-Ra for submit@debbugs.gnu.org; Mon, 17 Feb 2014 12:17:02 -0500 Received: from mout.gmx.net ([212.227.17.22]:54865) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFRoR-0003OF-J5 for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 12:17:00 -0500 Received: from [62.47.56.45] ([62.47.56.45]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0LaaVn-1X0eL51vO3-00mKIn for <16736@debbugs.gnu.org>; Mon, 17 Feb 2014 18:16:52 +0100 Message-ID: <530243FE.8050108@gmx.at> Date: Mon, 17 Feb 2014 18:16:46 +0100 From: martin rudalics MIME-Version: 1.0 To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> <83wqgt924q.fsf@gnu.org> <5302377D.3070007@gmx.at> <83iosd8yzj.fsf@gnu.org> In-Reply-To: <83iosd8yzj.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:afFeiNjAa3LkPyv4RsLYp6iBbFQyhmeZ4Dx/3amoMQUmQmxkiXt y8WuCP+Bps211di7Y9+AWfaaHC4PVgBfdJexFZBk1HRbUTK/s19b1VSDZCrDG2pX2BQjHX9 AMsvWpClE/cbVQcCMyoXAT7JrFtgAPjJMdAqxcjw5gnZ4x/ZYfRQXLQnBwFJoGH84zH7lU6 KVBTg0QwYMAXqG0I8RgTw== X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) > If you mean this: > > FRAME_PIXEL_HEIGHT (f) = ew->core.height + x->menubar_height; > > then does it mean that menubar_height is 33 pixels? Sounds too much > to me. In change_frame_size I here have a FRAME_PIXEL_HEIGHT of 697 and a new_text_height of 667. f->output_data.x->menubar_height equals 28 and there are two pixels to add for the default internal border. martin From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 17 12:27:27 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 17:27:28 +0000 Received: from localhost ([127.0.0.1]:56859 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFRyY-0003fw-Hj for submit@debbugs.gnu.org; Mon, 17 Feb 2014 12:27:27 -0500 Received: from mtaout26.012.net.il ([80.179.55.182]:34481) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFRyV-0003fd-68 for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 12:27:24 -0500 Received: from conversion-daemon.mtaout26.012.net.il by mtaout26.012.net.il (HyperSendmail v2007.08) id <0N1500O00HO6JV00@mtaout26.012.net.il> for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 19:25:41 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout26.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N1500GU1HQS6B80@mtaout26.012.net.il>; Mon, 17 Feb 2014 19:25:41 +0200 (IST) Date: Mon, 17 Feb 2014 19:27:22 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: <530243FE.8050108@gmx.at> X-012-Sender: halo1@inter.net.il To: martin rudalics Message-id: <83eh318xad.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> <83wqgt924q.fsf@gnu.org> <5302377D.3070007@gmx.at> <83iosd8yzj.fsf@gnu.org> <530243FE.8050108@gmx.at> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > Date: Mon, 17 Feb 2014 18:16:46 +0100 > From: martin rudalics > CC: rgm@gnu.org, 16736@debbugs.gnu.org > > > If you mean this: > > > > FRAME_PIXEL_HEIGHT (f) = ew->core.height + x->menubar_height; > > > > then does it mean that menubar_height is 33 pixels? Sounds too much > > to me. > > In change_frame_size I here have a FRAME_PIXEL_HEIGHT of 697 and a > new_text_height of 667. f->output_data.x->menubar_height equals 28 and > there are two pixels to add for the default internal border. OK, so it sounds like we need to make change_frame_size_1 consistent with widget.c code. From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 17 12:59:00 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 17:59:00 +0000 Received: from localhost ([127.0.0.1]:56913 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFST6-0004bW-23 for submit@debbugs.gnu.org; Mon, 17 Feb 2014 12:59:00 -0500 Received: from mout.gmx.net ([212.227.17.22]:59175) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFST3-0004bG-Ue for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 12:58:58 -0500 Received: from [62.47.56.45] ([62.47.56.45]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0Lm7MT-1Wp4CR2w6r-00ZejX for <16736@debbugs.gnu.org>; Mon, 17 Feb 2014 18:58:50 +0100 Message-ID: <53024DD2.2020900@gmx.at> Date: Mon, 17 Feb 2014 18:58:42 +0100 From: martin rudalics MIME-Version: 1.0 To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> <83wqgt924q.fsf@gnu.org> <5302377D.3070007@gmx.at> <83iosd8yzj.fsf@gnu.org> <530243FE.8050108@gmx.at> <83eh318xad.fsf@gnu.org> In-Reply-To: <83eh318xad.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:6sxbwJlEyPwer8eBssK888J3BSgvqAHpU199biba+iBmnkjt8IA XT9sXv7I84zqsonQOwKzuWft76G+vAHogsTKD5mm6eztym4ZZw3oVG890SAY+xaCUOFEIlS JtZfdMLtvMzaLr7MJJ4FVI6qM5D6JWWsGmYdT6WA7fQALfflqp9caU9HSm25kE8MSxfdfTV cbANf0oofF1nNMsXr/Aiw== X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) > OK, so it sounds like we need to make change_frame_size_1 consistent > with widget.c code. IMO the widget.c code is inherently absurd. EmacsFrameResize processes a resize request by calculating a text size from ew->core.height. Then it sets FRAME_PIXEL_HEIGHT (f) = ew->core.height + x->menubar_height; and update_from_various_frame_slots inversely processes ew->core.height = FRAME_PIXEL_HEIGHT (f) - x->menubar_height; where update_from_various_frame_slots is called only by EmacsFrameInitialize. Does anyone understand what this is good for? martin From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 17 13:19:58 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 18:19:58 +0000 Received: from localhost ([127.0.0.1]:56926 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFSnN-0005Bp-FT for submit@debbugs.gnu.org; Mon, 17 Feb 2014 13:19:58 -0500 Received: from fencepost.gnu.org ([208.118.235.10]:36759 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFSnL-0005Bi-Pg for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 13:19:56 -0500 Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1WFSnK-0006Fq-J2; Mon, 17 Feb 2014 13:19:54 -0500 From: Glenn Morris To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> <83wqgt924q.fsf@gnu.org> X-Spook: Aladdin IDEA virus Capricorn SSL ASO Compsec SAPO X-Ran: 1et+j"Oyx-$JD!H+>s3UkiMa,S\/iyHkuy^)(fV{7rNt1Jt@uuj!oH0*t;}[!g (Eli Zaretskii's message of "Mon, 17 Feb 2014 17:42:45 +0200") Message-ID: User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: -5.6 (-----) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rudalics@gmx.at X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.6 (-----) Eli Zaretskii wrote: > (What is f->tool_bar_height?) 45 > Glenn, if you put a breakpoint in change_frame_size_1 and then just > "run -Q", can you show all the calls you see until Emacs starts up, > including the arguments we pass to that function? Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=80, new_height=150, pretend=true, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=0, new_height=0, pretend=false, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=true, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=537, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=537, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=80, new_height=38, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=537, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=537, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=571, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=571, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=false, safe=true, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=false, safe=true, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, pretend=false, delay=false, safe=true, pixelwise=true) at dispnew.c:5467 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); Continuing. From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 17 13:48:01 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 18:48:01 +0000 Received: from localhost ([127.0.0.1]:56960 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFTEW-0005yB-BT for submit@debbugs.gnu.org; Mon, 17 Feb 2014 13:48:01 -0500 Received: from mtaout23.012.net.il ([80.179.55.175]:63415) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFTES-0005xm-Q7 for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 13:47:58 -0500 Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0N1500H00L6XKC00@a-mtaout23.012.net.il> for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 20:47:50 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N1500HEULJPKE10@a-mtaout23.012.net.il>; Mon, 17 Feb 2014 20:47:50 +0200 (IST) Date: Mon, 17 Feb 2014 20:47:55 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: X-012-Sender: halo1@inter.net.il To: Glenn Morris Message-id: <83d2il8tk4.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> <83wqgt924q.fsf@gnu.org> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rudalics@gmx.at X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > From: Glenn Morris > Cc: 16736@debbugs.gnu.org, rudalics@gmx.at > Date: Mon, 17 Feb 2014 13:19:54 -0500 > > Eli Zaretskii wrote: > > > (What is f->tool_bar_height?) > > 45 > > > Glenn, if you put a breakpoint in change_frame_size_1 and then just > > "run -Q", can you show all the calls you see until Emacs starts up, > > including the arguments we pass to that function? > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=80, new_height=150, > pretend=true, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=0, new_height=0, > pretend=false, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=true, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=537, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=537, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=80, new_height=38, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=537, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=537, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=571, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=571, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=false, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=false, safe=true, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=false, safe=true, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=true, safe=false, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. > > Breakpoint 3, change_frame_size_1 (f=0x11cd8b8, new_width=640, new_height=570, > pretend=false, delay=false, safe=true, pixelwise=true) at dispnew.c:5467 > 5467 int old_root_width = WINDOW_PIXEL_WIDTH (XWINDOW (FRAME_ROOT_WINDOW (f))); > Continuing. Thanks. Martin, any idea what this dance with 570/537/571/570 sizes is about? From debbugs-submit-bounces@debbugs.gnu.org Mon Feb 17 13:56:56 2014 Received: (at 16736) by debbugs.gnu.org; 17 Feb 2014 18:56:56 +0000 Received: from localhost ([127.0.0.1]:56965 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFTN9-0006EE-Rq for submit@debbugs.gnu.org; Mon, 17 Feb 2014 13:56:56 -0500 Received: from mtaout20.012.net.il ([80.179.55.166]:33783) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFTN6-0006Dv-Hm for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 13:56:53 -0500 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0N1500100LN0U400@a-mtaout20.012.net.il> for 16736@debbugs.gnu.org; Mon, 17 Feb 2014 20:56:46 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N15001H0LYLMK60@a-mtaout20.012.net.il>; Mon, 17 Feb 2014 20:56:46 +0200 (IST) Date: Mon, 17 Feb 2014 20:56:51 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: <53024DD2.2020900@gmx.at> X-012-Sender: halo1@inter.net.il To: martin rudalics Message-id: <83bny58t58.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> <83wqgt924q.fsf@gnu.org> <5302377D.3070007@gmx.at> <83iosd8yzj.fsf@gnu.org> <530243FE.8050108@gmx.at> <83eh318xad.fsf@gnu.org> <53024DD2.2020900@gmx.at> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > Date: Mon, 17 Feb 2014 18:58:42 +0100 > From: martin rudalics > CC: rgm@gnu.org, 16736@debbugs.gnu.org > > > OK, so it sounds like we need to make change_frame_size_1 consistent > > with widget.c code. > > IMO the widget.c code is inherently absurd. EmacsFrameResize processes > a resize request by calculating a text size from ew->core.height. Then > it sets > > FRAME_PIXEL_HEIGHT (f) = ew->core.height + x->menubar_height; > > and update_from_various_frame_slots inversely processes > > ew->core.height = FRAME_PIXEL_HEIGHT (f) - x->menubar_height; > > where update_from_various_frame_slots is called only by > EmacsFrameInitialize. Does anyone understand what this is good for? The latter part is not important, I think, because ew->core is not used anywhere. So the only important part here is setting FRAME_PIXEL_HEIGHT and other fields of the frame struct. widget.c is compiled only for X toolkits, right? So I think making update_various_frame_slots consistent with change_frame_size_1 when USE_X_TOOLKIT will fix the problem. From debbugs-submit-bounces@debbugs.gnu.org Tue Feb 18 06:02:59 2014 Received: (at 16736) by debbugs.gnu.org; 18 Feb 2014 11:02:59 +0000 Received: from localhost ([127.0.0.1]:57675 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFiS2-0002LA-Pu for submit@debbugs.gnu.org; Tue, 18 Feb 2014 06:02:59 -0500 Received: from mout.gmx.net ([212.227.15.18]:52117) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFiS0-0002Km-5d for 16736@debbugs.gnu.org; Tue, 18 Feb 2014 06:02:57 -0500 Received: from [62.47.58.23] ([62.47.58.23]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MEWxh-1WUmLQ0ntZ-00FkBq for <16736@debbugs.gnu.org>; Tue, 18 Feb 2014 12:02:49 +0100 Message-ID: <53033DD1.6050005@gmx.at> Date: Tue, 18 Feb 2014 12:02:41 +0100 From: martin rudalics MIME-Version: 1.0 To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> <83wqgt924q.fsf@gnu.org> <5302377D.3070007@gmx.at> <83iosd8yzj.fsf@gnu.org> <530243FE.8050108@gmx.at> <83eh318xad.fsf@gnu.org> <53024DD2.2020900@gmx.at> <83bny58t58.fsf@gnu.org> In-Reply-To: <83bny58t58.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:kxlzD51+o7V/Bs8YkY2C5w+3At3lL6aAYZsHjCMCROvaTtJ253A lhw/usKWvBIschZmge4dSdvjl6y2sCXu++KrA6yoUIgpfSGRKK+anwHibaAj4x4UiBMsfPa b6Sp6tBWsWBDvfmkVIi8kHjSb8LXFukr46VipjOqYbDVxQxpeIUKQsTBdEJKC6V7hxiZPBZ S1l3bgMwh8Mdz+HJKbtiQ== X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) > So the only important part here is setting FRAME_PIXEL_HEIGHT and > other fields of the frame struct. > > widget.c is compiled only for X toolkits, right? So I think making > update_various_frame_slots consistent with change_frame_size_1 when > USE_X_TOOLKIT will fix the problem. I defined out the assignments in update_various_frame_slots. I saw no other way because FRAME_PIXEL_HEIGHT inherently records the "old" internal border width (that's all it does IIUC). When the border width changes, the text height remains unaltered, and I see no alternate means to detect the change and redraw the frame appropriately. martin From debbugs-submit-bounces@debbugs.gnu.org Tue Feb 18 06:03:22 2014 Received: (at 16736) by debbugs.gnu.org; 18 Feb 2014 11:03:23 +0000 Received: from localhost ([127.0.0.1]:57679 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFiSQ-0002MM-Ke for submit@debbugs.gnu.org; Tue, 18 Feb 2014 06:03:22 -0500 Received: from mout.gmx.net ([212.227.15.19]:63646) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFiSP-0002MA-B4 for 16736@debbugs.gnu.org; Tue, 18 Feb 2014 06:03:21 -0500 Received: from [62.47.58.23] ([62.47.58.23]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0Lk81O-1Wqh6O2ZP0-00cCwE for <16736@debbugs.gnu.org>; Tue, 18 Feb 2014 12:03:14 +0100 Message-ID: <53033DEA.8060602@gmx.at> Date: Tue, 18 Feb 2014 12:03:06 +0100 From: martin rudalics MIME-Version: 1.0 To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> <83wqgt924q.fsf@gnu.org> <83d2il8tk4.fsf@gnu.org> In-Reply-To: <83d2il8tk4.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:6rKLafmBQ2I2XDDeyqaCsD01FwpNDSV79DmJ3IbAprrmN8EUg0O PpW5Mr83+nW3yoRlB5ezjCQLjjn8ecNYg5vc6d9MnWjFc1Uh9tt0IAUNhBPrny5lrao4I/G iz5FT0bK9N4AY9XaY6zBTExBk5Vu0tYf+JqJy/9kPOwm2V3U9SITSNcma8m9ARX/K3YjHVM 9MeyRqMaRI8ixg46bT+ZQ== X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, Glenn Morris X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) > Martin, any idea what this dance with 570/537/571/570 sizes is about? The 570 ~> 537 seem caused by the 33 difference of Glenn's frame pixel height w and w/o menubar + internal borders. The 571 one is a mystery to me. Most of these changes seem caused by frequent calls of resize_cb whose frequency is a mystery to me as well. I also recall having seen tooltip frames in here. martin From debbugs-submit-bounces@debbugs.gnu.org Tue Feb 18 13:08:16 2014 Received: (at 16736) by debbugs.gnu.org; 18 Feb 2014 18:08:16 +0000 Received: from localhost ([127.0.0.1]:58785 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFp5b-0007UW-VL for submit@debbugs.gnu.org; Tue, 18 Feb 2014 13:08:16 -0500 Received: from mtaout29.012.net.il ([80.179.55.185]:50419) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFp5Z-0007UG-E4 for 16736@debbugs.gnu.org; Tue, 18 Feb 2014 13:08:14 -0500 Received: from conversion-daemon.mtaout29.012.net.il by mtaout29.012.net.il (HyperSendmail v2007.08) id <0N1700E00E2ED500@mtaout29.012.net.il> for 16736@debbugs.gnu.org; Tue, 18 Feb 2014 20:10:37 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout29.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N1700693EHOMJ20@mtaout29.012.net.il>; Tue, 18 Feb 2014 20:10:36 +0200 (IST) Date: Tue, 18 Feb 2014 20:08:16 +0200 From: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on In-reply-to: <53033DD1.6050005@gmx.at> X-012-Sender: halo1@inter.net.il To: martin rudalics Message-id: <83zjlo5m5r.fsf@gnu.org> References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> <83wqgt924q.fsf@gnu.org> <5302377D.3070007@gmx.at> <83iosd8yzj.fsf@gnu.org> <530243FE.8050108@gmx.at> <83eh318xad.fsf@gnu.org> <53024DD2.2020900@gmx.at> <83bny58t58.fsf@gnu.org> <53033DD1.6050005@gmx.at> X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Eli Zaretskii List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) > Date: Tue, 18 Feb 2014 12:02:41 +0100 > From: martin rudalics > CC: rgm@gnu.org, 16736@debbugs.gnu.org > > > So the only important part here is setting FRAME_PIXEL_HEIGHT and > > other fields of the frame struct. > > > > widget.c is compiled only for X toolkits, right? So I think making > > update_various_frame_slots consistent with change_frame_size_1 when > > USE_X_TOOLKIT will fix the problem. > > I defined out the assignments in update_various_frame_slots. I saw no > other way because FRAME_PIXEL_HEIGHT inherently records the "old" > internal border width (that's all it does IIUC). When the border width > changes, the text height remains unaltered, and I see no alternate means > to detect the change and redraw the frame appropriately. Thanks. I see no problem with your changes. From debbugs-submit-bounces@debbugs.gnu.org Tue Feb 18 13:19:25 2014 Received: (at 16736) by debbugs.gnu.org; 18 Feb 2014 18:19:25 +0000 Received: from localhost ([127.0.0.1]:58816 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFpGP-0007rT-2K for submit@debbugs.gnu.org; Tue, 18 Feb 2014 13:19:25 -0500 Received: from fencepost.gnu.org ([208.118.235.10]:38864 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFpGN-0007rL-6L for 16736@debbugs.gnu.org; Tue, 18 Feb 2014 13:19:23 -0500 Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1WFpGL-00087P-U3; Tue, 18 Feb 2014 13:19:22 -0500 From: Glenn Morris To: martin rudalics Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> <83wqgt924q.fsf@gnu.org> <5302377D.3070007@gmx.at> <83iosd8yzj.fsf@gnu.org> <530243FE.8050108@gmx.at> <83eh318xad.fsf@gnu.org> <53024DD2.2020900@gmx.at> <83bny58t58.fsf@gnu.org> <53033DD1.6050005@gmx.at> X-Spook: Cocaine benelux anthrax UNSCOM infowar Al-Qaeda INSCOM X-Ran: ]:W.v'57nWd2G+'=-E\8<1Rl_ZyA{e\gYM`k$NDv`I?{6?e[5Vmr?H]hqxzLX$q^f{XF2[ X-Hue: black X-Debbugs-No-Ack: yes X-Attribution: GM Date: Tue, 18 Feb 2014 13:19:21 -0500 Message-ID: <3mzjlo707q.fsf@fencepost.gnu.org> User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: -5.6 (-----) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, Eli Zaretskii X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.6 (-----) martin rudalics wrote: > I defined out the assignments in update_various_frame_slots. Thanks, it doesn't flash now, so I'll close this. (Please reopen, or open a new report, if you still think there are issues.) From debbugs-submit-bounces@debbugs.gnu.org Tue Feb 18 13:19:30 2014 Received: (at control) by debbugs.gnu.org; 18 Feb 2014 18:19:30 +0000 Received: from localhost ([127.0.0.1]:58819 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFpGU-0007rm-AY for submit@debbugs.gnu.org; Tue, 18 Feb 2014 13:19:30 -0500 Received: from fencepost.gnu.org ([208.118.235.10]:38868 ident=Debian-exim) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WFpGT-0007rf-CQ for control@debbugs.gnu.org; Tue, 18 Feb 2014 13:19:29 -0500 Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1WFpGT-00007Z-1u for control@debbugs.gnu.org; Tue, 18 Feb 2014 13:19:29 -0500 Date: Tue, 18 Feb 2014 13:19:29 -0500 Message-Id: Subject: control message for bug 16736 To: X-Mailer: mail (GNU Mailutils 2.1) From: Glenn Morris X-Spam-Score: -5.6 (-----) X-Debbugs-Envelope-To: control X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -5.6 (-----) close 16736 24.4 From debbugs-submit-bounces@debbugs.gnu.org Wed Feb 19 05:02:37 2014 Received: (at 16736) by debbugs.gnu.org; 19 Feb 2014 10:02:37 +0000 Received: from localhost ([127.0.0.1]:59495 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WG3zA-00060A-Os for submit@debbugs.gnu.org; Wed, 19 Feb 2014 05:02:37 -0500 Received: from mout.gmx.net ([212.227.17.22]:50246) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WG3z7-0005zj-PX for 16736@debbugs.gnu.org; Wed, 19 Feb 2014 05:02:35 -0500 Received: from [62.47.41.228] ([62.47.41.228]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MOkQc-1WJw842vws-00665H for <16736@debbugs.gnu.org>; Wed, 19 Feb 2014 11:02:26 +0100 Message-ID: <53048129.5070906@gmx.at> Date: Wed, 19 Feb 2014 11:02:17 +0100 From: martin rudalics MIME-Version: 1.0 To: Eli Zaretskii Subject: Re: bug#16736: Compiling a Lisp file causes display to flash off and on References: <96vbwj696i.fsf@fencepost.gnu.org> <83lhxecftk.fsf@gnu.org> <2smwhurv74.fsf@fencepost.gnu.org> <83iosgbx6b.fsf@gnu.org> <83y51b9gdt.fsf@gnu.org> <0ssirio8re.fsf@fencepost.gnu.org> <83eh329v8a.fsf@gnu.org> <0nlhxa18t7.fsf@fencepost.gnu.org> <83wqgt924q.fsf@gnu.org> <5302377D.3070007@gmx.at> <83iosd8yzj.fsf@gnu.org> <530243FE.8050108@gmx.at> <83eh318xad.fsf@gnu.org> <53024DD2.2020900@gmx.at> <83bny58t58.fsf@gnu.org> <53033DD1.6050005@gmx.at> <83zjlo5m5r.fsf@gnu.org> In-Reply-To: <83zjlo5m5r.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:ylwQ27XO/mbIRrcvA8Y1f0/ny80SIgvegfOIBFw46uI/uV0H1O9 nXggMOUHcdi4Pu3qAzL4Vp7evQjH3rMcCmBY7op9XBdDoI5HifOpz0P4O9BqBKbSkItuDtR JXjG+tdGIL+NwN90QA246K9Vs9xNt2zZVGdySBfx6RF0Q//UIKpZgKNJdT+Oin5MyA3ClI0 eMeCOPBsjXSOtdCZ3I9Xg== X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 16736 Cc: 16736@debbugs.gnu.org, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) > Thanks. I see no problem with your changes. Thanks to you and Glenn for the forensics. martin From unknown Mon Jun 23 02:23:27 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Wed, 19 Mar 2014 11:24:03 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator