unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 38213@debbugs.gnu.org, juri@linkov.net
Subject: bug#38213: 27.0.50; add tooltip move-frame handling to mouse-avoidance-mode
Date: Fri, 15 Nov 2019 11:50:10 +0200	[thread overview]
Message-ID: <83o8xd31v1.fsf@gnu.org> (raw)
In-Reply-To: <81c4863b-1f8d-4d2f-96f2-f44c96db003c@gmx.at> (message from martin rudalics on Fri, 15 Nov 2019 09:53:37 +0100)

> Cc: 38213@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Fri, 15 Nov 2019 09:53:37 +0100
> 
>  > Shouldn't we instead avoid emitting this event when a tooltip frame is
>  > positioned?  Otherwise, we will have to make such adaptations in many
>  > places.
> 
> Doesn't the tooltip frame get removed because 'mouse-avoidance-mode'
> reacts to a movement of the normal frame that "hosts" the tooltip
> frame.

But the normal frame which hosts the tooltip is not moved in this
scenario.  To reproduce, turn on mouse-avoidance-mode (I used 'jump'
as the avoidance technique), then start Dired, and move the mouse to
the file name under cursor.  Here, the tooltip appears and immediately
disappears, and I see no movement of the "hosting" frame anywhere.





  reply	other threads:[~2019-11-15  9:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14 23:32 bug#38213: 27.0.50; add tooltip move-frame handling to mouse-avoidance-mode Juri Linkov
2019-11-15  8:13 ` martin rudalics
2019-11-15  8:26 ` Eli Zaretskii
2019-11-15  8:53   ` martin rudalics
2019-11-15  9:50     ` Eli Zaretskii [this message]
2019-11-15 16:35       ` martin rudalics
2019-11-15 16:57         ` Eli Zaretskii
2019-11-16  8:19           ` martin rudalics
2019-11-21 21:31             ` Juri Linkov
2019-11-22  8:09               ` martin rudalics
2019-11-26 22:12                 ` Juri Linkov

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=83o8xd31v1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=38213@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=rudalics@gmx.at \
    /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).