From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: 27647@debbugs.gnu.org, Alex <agrambot@gmail.com>
Subject: bug#27647: 26.0.50; Line numbers implemented natively disappear momentarily when frame out of focus
Date: Thu, 09 Nov 2017 19:38:30 -0500 [thread overview]
Message-ID: <87h8u33r3t.fsf@users.sourceforge.net> (raw)
In-Reply-To: <CAFyQvY0AFQrYD6RQHiatfFP7wPmVuF=aMSZaqhRKqJVWz3thTQ@mail.gmail.com> (Kaushal Modi's message of "Thu, 09 Nov 2017 13:34:27 +0000")
Kaushal Modi <kaushal.modi@gmail.com> writes:
> Thanks for spending time to debug this and come up with that crucial
> fix. Did any of the within-emacs debug tactics help you figure this
> out? Or was it putting breakpoints and catching them in gdb? Or did
> you go the final hard way, and review the code manually?
So glad you asked, now I can relive the glory of the hunt :D
The first thing I tried was the 'watch Vdisplay_line_numbers', but this
gave me no hits except for some spurious stuff related to buffer-local
variables; after changing to (setq-default display-line-numbers t) I got
no hits at all. So it was fairly clear that the problem lay below the
lisp level.
Then I considered putting a breakpoint into the display code, which is a
bit tricky because I needed to drag the mouse to trigger the problem,
but if a breakpoint is hit before that Emacs is frozen and can't
register the mouse drag. I tried to reduce the recipe to some lisp code
to be evaluated based on mouse-drag-and-drop-region, but I didn't
manage to come up with something that worked.
Then I looked a bit through the display code to figure if a breakpoint
conditioned on mouse dragging could work, and I noticed the
should_produce_line_number function, so I just put a breakpoint on every
place which returned false. Bang, success!
Except I then had to check the values of WINDOW_FRAME (it->w) to make
sure I hadn't actually hit the case where the code *correctly* skips
line numbers for tooltips. A quick grep for tip_frame soon turned up
x_hide_tooltip which had the comment that explained what was going on.
> Also thanks to everyone who helped figure out a recipe, which is
> equally important :).
Most definitely, I could not have done anything without a simple way to
reproduce the problem.
next prev parent reply other threads:[~2017-11-10 0:38 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 20:52 bug#27647: 26.0.50; Line numbers implemented natively disappear momentarily when frame out of focus Kaushal Modi
2017-07-11 2:38 ` Eli Zaretskii
2017-07-11 3:43 ` Kaushal Modi
2017-07-11 14:31 ` Eli Zaretskii
2017-07-11 14:38 ` Kaushal Modi
2017-07-11 20:08 ` Kaushal Modi
2017-07-12 14:44 ` Eli Zaretskii
2017-07-19 15:13 ` Kaushal Modi
2017-07-19 17:34 ` Eli Zaretskii
2017-07-19 17:52 ` Noam Postavsky
2017-07-19 18:09 ` Eli Zaretskii
2017-10-05 12:40 ` Kaushal Modi
2017-10-05 13:03 ` jonas
2017-10-05 13:10 ` Eli Zaretskii
2017-10-05 13:39 ` Eli Zaretskii
2017-10-05 22:17 ` Romanos Skiadas
2017-10-06 8:57 ` Eli Zaretskii
2017-10-11 20:32 ` Romanos Skiadas
2017-10-12 8:29 ` Eli Zaretskii
2017-10-12 19:30 ` Romanos Skiadas
2017-10-13 8:33 ` Eli Zaretskii
2017-10-13 18:14 ` Romanos Skiadas
2017-10-14 7:47 ` Eli Zaretskii
2017-10-15 15:05 ` Romanos Skiadas
2017-10-14 8:36 ` martin rudalics
2017-10-14 10:12 ` Eli Zaretskii
2017-10-15 9:39 ` martin rudalics
2017-10-15 13:25 ` Kaushal Modi
2017-10-16 21:46 ` Kaushal Modi
2017-10-17 8:59 ` martin rudalics
2017-10-17 14:47 ` Eli Zaretskii
2017-10-17 15:07 ` Kaushal Modi
2017-10-17 15:13 ` Kaushal Modi
2017-10-17 16:48 ` Eli Zaretskii
2017-10-15 14:29 ` Eli Zaretskii
2017-11-08 20:08 ` Alex
2017-11-08 20:14 ` Alex
2017-11-09 2:49 ` Noam Postavsky
2017-11-09 7:28 ` martin rudalics
2017-11-09 15:57 ` Eli Zaretskii
2017-11-09 18:10 ` martin rudalics
2017-11-09 20:53 ` Eli Zaretskii
2017-11-12 10:08 ` martin rudalics
2017-11-12 11:36 ` Eli Zaretskii
2017-11-13 18:45 ` martin rudalics
2017-11-13 19:12 ` Eli Zaretskii
2017-11-14 9:52 ` martin rudalics
2017-11-14 15:47 ` Eli Zaretskii
2017-11-14 18:29 ` martin rudalics
2017-11-14 19:02 ` Eli Zaretskii
2017-11-15 9:22 ` martin rudalics
2017-11-15 10:05 ` martin rudalics
2017-11-18 11:42 ` Eli Zaretskii
2017-11-18 18:25 ` martin rudalics
2017-11-09 13:34 ` Kaushal Modi
2017-11-10 0:38 ` Noam Postavsky [this message]
2017-11-09 16:12 ` Eli Zaretskii
2017-11-09 18:14 ` Romanos Skiadas
2017-11-09 20:27 ` Eli Zaretskii
2017-11-10 0:11 ` Noam Postavsky
2017-11-10 8:37 ` Eli Zaretskii
2017-07-21 17:49 ` bug#27647: 26.0.50; Line numbers implemented natively disappear momentarily when, " jonas
2017-07-21 18:57 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8u33r3t.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=27647@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=kaushal.modi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).