From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: cyd@gnu.org, 7464-done@debbugs.gnu.org
Subject: bug#7464: 24.0.50; mouse highlighting vanishes upon unsplitting window
Date: Sat, 31 Mar 2012 21:12:39 +0300 [thread overview]
Message-ID: <83hax4k5bc.fsf@gnu.org> (raw)
In-Reply-To: <87k420amz4.fsf@escher.home>
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: cyd@gnu.org, 7464@debbugs.gnu.org
> Date: Sat, 31 Mar 2012 16:01:19 +0200
>
> On Sat, 31 Mar 2012 08:56:00 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Can you show a backtrace in a few instances when the breakpoint inside
> > cancel_mouse_face breaks? I think these calls are those that keep the
> > highlighting from being wiped out in the GTK build.
>
> I've attached two backtraces. The first backtrace was produced
> immediately after typing `r -q', with execution breaking before the
> frame appeared. The second backtrace was produced after the second
> break, when the frame appeared with the menu and tool bars but no scroll
> bar or text. This backtrace and subsequent (essentially identical) ones
> included no Lisp backtrace. At the third break, the scroll bar
> appeared; the backtrace is the same as the second one. Continuing after
> that, the splash screen appeared and execution reverted to the command
> loop. I then typed C-x 2 and execution broke four times to split the
> window and redisplay the scroll bars. Then C-x 1 with the mouse pointer
> over a link text, showing highlighting (which remained after
> continuing), the execution breaking once. Each of these breaks produced
> the same backtrace, essentially like the second one, but without the
> call to x_scroll_bar_create and with a much larger level_stack in the
> redisplay_window frame.
Thanks. So I think the issue is now completely clear, and with
Stefan's permission I installed the fix for this bug (as trunk
revision 107713).
I'm therefore closing the bug.
next prev parent reply other threads:[~2012-03-31 18:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 14:57 bug#7464: 24.0.50; mouse highlighting vanishes upon unsplitting window Stephen Berman
2010-11-22 17:54 ` Eli Zaretskii
2010-11-22 19:17 ` Eli Zaretskii
2012-03-21 16:29 ` Chong Yidong
2012-03-21 17:52 ` Stephen Berman
2012-03-21 22:41 ` Stephen Berman
2012-03-22 3:55 ` Eli Zaretskii
2012-03-22 14:51 ` Stefan Monnier
2012-03-22 17:01 ` Stephen Berman
2012-03-22 17:05 ` Eli Zaretskii
2012-03-24 18:32 ` Eli Zaretskii
2012-03-24 21:46 ` Stephen Berman
2012-03-25 3:55 ` Eli Zaretskii
2012-03-25 12:57 ` Stephen Berman
2012-03-28 18:56 ` Eli Zaretskii
2012-03-29 7:57 ` Stephen Berman
2012-03-29 18:47 ` Eli Zaretskii
2012-03-29 22:56 ` Stephen Berman
2012-03-30 6:35 ` Eli Zaretskii
2012-03-30 8:44 ` Stephen Berman
2012-03-30 9:10 ` Eli Zaretskii
2012-03-30 11:08 ` Stephen Berman
2012-03-30 12:06 ` Eli Zaretskii
2012-03-30 19:35 ` Stephen Berman
2012-03-30 20:41 ` Eli Zaretskii
2012-03-30 23:09 ` Stephen Berman
2012-03-31 5:56 ` Eli Zaretskii
2012-03-31 14:01 ` Stephen Berman
2012-03-31 18:12 ` Eli Zaretskii [this message]
2012-03-30 7:43 ` Jan D.
2012-03-30 8:00 ` Eli Zaretskii
2012-03-30 8:45 ` Stephen Berman
2012-03-30 8:57 ` Eli Zaretskii
2012-03-30 12:20 ` Jan Djärv
2012-03-30 12:37 ` Stefan Monnier
2012-03-25 12:56 ` martin rudalics
2012-03-21 18:54 ` 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=83hax4k5bc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7464-done@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=stephen.berman@gmx.net \
/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).