From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>,
Stephen Berman <stephen.berman@gmx.net>,
30399@debbugs.gnu.org
Subject: bug#30399: 27.0.50; tooltips are broken
Date: Fri, 9 Feb 2018 07:41:55 -0800 (PST) [thread overview]
Message-ID: <f17939d0-7eda-4f64-856a-0811f3e6338b@default> (raw)
In-Reply-To: <5A7D6F9A.1010504@gmx.at>
> This is due to a rather silly omission which should have already
> defeated a feature in Emacs 26 when calling 'x-show-tip' (you've
> been warned - Lisp code should call 'tooltip-show').
That warning sounds very bad to me. It's vague, however,
so forgive me if I'm overreacting.
I have 4 libraries that will presumably break completely
if `x-show-tip' is defeated or is no longer available.
`tooltip-show' does NOT do the same thing and will not
work (AFAICT) for what I use `x-show-tip' for.
The libraries are `pp+.el', `apu.el', `modeline-char.el',
and `showkey.el'. They are all available on Emacs Wiki,
Elisp Area.
https://www.emacswiki.org/emacs?action=elisp-area;context=0
`tooltip-show' constrains its call of `x-show-tip' to
only one particular behavior/appearance, etc. Replacing
the latter function with just the former would be like
replacing the general function `goto-char' a limited one
such as `beginning-of-line'. `x-show-tip' is much more
general than `tooltip-show'.
Here's a typical call:
(x-show-tip (propertize
cmd-desc
'face
`(:foreground "red"
:height ,showkey-tooltip-height))
nil
nil
showkey-tooltip-timeout)
next prev parent reply other threads:[~2018-02-09 15:41 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 [this message]
2018-02-10 9:47 ` martin rudalics
2018-02-10 16:39 ` Drew Adams
2018-02-11 9:36 ` martin rudalics
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=f17939d0-7eda-4f64-856a-0811f3e6338b@default \
--to=drew.adams@oracle.com \
--cc=30399@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--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.