From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>,
23246@debbugs.gnu.org, eliz@gnu.org, bruce.connor.am@gmail.com
Subject: bug#23246: 25.0.92; Local face-remapping-alist doesn't affect tooltips
Date: Tue, 12 Apr 2016 07:26:47 -0700 (PDT) [thread overview]
Message-ID: <6a2794c3-f14c-4011-bf15-a2b20f9c0b89@default> (raw)
In-Reply-To: <570CA409.9080308@gmx.at>
> >> `x-show-tip' just might work.
> > You mean, tooltip-functions doesn't?
>
> The doc-string of ‘x-show-tip’ advises that
> This is an internal function; Lisp code should call ‘tooltip-show’.
Yes, and that's misguided, at least for the reason you give.
> but ‘tooltip-show’ overrides any face properties of TEXT via
> (propertize text 'face 'tooltip)
> in a hardcoded fashion. So if you want to display your own face
> attributes, you currently have to call ‘x-show-tip’ directly despite of
> its advice.
Exactly. Plus ‘x-show-tip’ works across Emacs versions.
It is preferable, IMO.
> Obviously, GTK+ (and probably OS X) tooltips override such attributes
> anyway, so changing this might probably never given high priority.
> Still, Emacs tooltip frames provide the possibility so why not use it?
Yes. Just do it.
When Emacs wants to steer users away from X toward Y, especially
because the name X is misleading (e.g. `x-<something'), it had
better make sure that Y is really an adequate replacement for X.
next prev parent reply other threads:[~2016-04-12 14:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 19:22 bug#23246: 25.0.92; Local face-remapping-alist doesn't affect tooltips Artur Malabarba
2016-04-08 19:34 ` Eli Zaretskii
2016-04-08 20:06 ` Artur Malabarba
2016-04-09 9:04 ` martin rudalics
2016-04-09 9:35 ` Eli Zaretskii
2016-04-09 12:50 ` martin rudalics
2016-04-09 13:18 ` Eli Zaretskii
2016-04-11 3:15 ` Artur Malabarba
2016-04-11 15:40 ` Eli Zaretskii
2016-04-12 7:30 ` martin rudalics
2016-04-12 14:26 ` Drew Adams [this message]
2016-04-12 15:14 ` Eli Zaretskii
2016-04-09 9:04 ` martin rudalics
2016-04-09 9:39 ` 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=6a2794c3-f14c-4011-bf15-a2b20f9c0b89@default \
--to=drew.adams@oracle.com \
--cc=23246@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=eliz@gnu.org \
--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).