From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>,
Stephen Berman <stephen.berman@gmx.net>,
30399@debbugs.gnu.org
Subject: bug#30399: 27.0.50; tooltips are broken
Date: Sun, 11 Feb 2018 10:36:15 +0100 [thread overview]
Message-ID: <5A800E8F.60706@gmx.at> (raw)
In-Reply-To: <0f060af6-d348-4d38-806e-a0d6d9f194ff@default>
> Can you clarify the warning, please?
That when the behavior of 'x-show-tip' changes, applications will
have to adapt.
> If there is a reason to replace `x-show-tip', can you not
> replace it with something that is just as general? Why
> would we take away something that lets you specify the
> appearance and behavior, replacing it by something that
> just hard-codes properties etc.?
Currently there are no plans to replace 'x-show-tip' AFAICT.
>> Make sure to use (selected-frame) as second argument for
>> Emacs < 27. nil is broken but you might not notice it.
>
> Thank you. I didn't know that. And you're right that
> I haven't noticed it, so far.
>
> Can you please say what the brokenness is? Is there
> a bug # for that, so we can learn about the brokenness
> that we might not notice? Thx.
Internally, Emacs tries to not delete/recreate a tooltip frame when
the text of the tooltip remains the same and only its position
changes. This optimization may get broken when using nil as the
second argument. As mentioned, you probably won't notice it.
martin
next prev parent reply other threads:[~2018-02-11 9:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 22:26 bug#30399: 27.0.50; tooltips are broken Stephen Berman
2018-02-09 9:53 ` martin rudalics
2018-02-09 10:49 ` Stephen Berman
2018-02-10 9:47 ` martin rudalics
2018-02-09 15:41 ` Drew Adams
2018-02-10 9:47 ` martin rudalics
2018-02-10 16:39 ` Drew Adams
2018-02-11 9:36 ` martin rudalics [this message]
2018-02-11 17:23 ` Drew Adams
2018-02-12 9:26 ` martin rudalics
2018-02-12 14:43 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5A800E8F.60706@gmx.at \
--to=rudalics@gmx.at \
--cc=30399@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.