unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Jan D." <jan.h.d@swipnet.se>
Cc: stephen.berman@gmx.net, 7464@debbugs.gnu.org, cyd@gnu.org
Subject: bug#7464: 24.0.50; mouse highlighting vanishes upon unsplitting window
Date: Fri, 30 Mar 2012 11:00:49 +0300	[thread overview]
Message-ID: <83bone1pse.fsf@gnu.org> (raw)
In-Reply-To: <4F756438.7050503@swipnet.se>

> Date: Fri, 30 Mar 2012 09:43:52 +0200
> From: "Jan D." <jan.h.d@swipnet.se>
> CC: Stephen Berman <stephen.berman@gmx.net>, cyd@gnu.org, 
>  7464@debbugs.gnu.org
> 
> It probably has something to do with the fact that Gtk+ scrollbars 
> aren't handeled by the display engine and we therefore have to force a 
> redraw of the scroll bars at certain points so the scrollbars look ok. 
> Presumably one of these redraws does something that triggers a redraw of 
> mouse highlight?  It might be that a redraw of the scroll bar generates 
> some X expose/configuration event that in turn invokes the display 
> engine.  I'm just speculating.

I think your speculation is exactly right.  Perhaps Stephen or someone
else who has access to a GTK build could confirm that an extra
redraw of mouse highlight is triggered at some point in this scenario.

Anyway, I think it is not important (however interesting and exciting)
to determine the exact reason which causes the bug not to appear in
the GTK build.  It suffices to say that any non-GTK build suffers from
this bug, and suffered in the past (Emacs 23 at least) as well.  I
think this information, and the patch that cures the bug I posted
earlier, is enough for Chong and Stefan to make the decision whether
to install the change now or defer it until after v24.1.





  reply	other threads:[~2012-03-30  8:00 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
2012-03-30  7:43                       ` Jan D.
2012-03-30  8:00                         ` Eli Zaretskii [this message]
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=83bone1pse.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=7464@debbugs.gnu.org \
    --cc=cyd@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --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).