From: Eli Zaretskii <eliz@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 34819@debbugs.gnu.org
Subject: bug#34819: 26.1; Blank help-echo tooltips for mode line menus
Date: Tue, 12 Mar 2019 17:45:59 +0200 [thread overview]
Message-ID: <83ftrs3xl4.fsf@gnu.org> (raw)
In-Reply-To: <02f4973ceec5cc3520ad14614c3a329b@webmail.orcon.net.nz> (message from Phil Sainty on Tue, 12 Mar 2019 12:45:58 +1300)
> Date: Tue, 12 Mar 2019 12:45:58 +1300
> From: Phil Sainty <psainty@orcon.net.nz>
>
> Recipe from emacs -Q (and --with-x-toolkit=lucid)
>
> * M-x text-mode
> * Mouse 1 click on "Text" in the mode line to open the menu
> * Hover over any of the menu items until the tooltip appears
>
> For me, this produces tooltips of the appropriate dimensions, but the
> text itself is not visible.
I can only suggest to step with a debugger through x-show-tip and see
what's going on there. It's hard to understand how come the frame is
shown, but the text produced by the same function is invisible. Maybe
we are missing some X wizardry in that function.
next prev parent reply other threads:[~2019-03-12 15:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 23:45 bug#34819: 26.1; Blank help-echo tooltips for mode line menus Phil Sainty
2019-03-12 6:28 ` Phil Sainty
2019-03-12 15:56 ` Eli Zaretskii
2019-03-12 17:21 ` Eli Zaretskii
2019-03-12 20:20 ` Phil Sainty
2019-03-12 15:45 ` Eli Zaretskii [this message]
2019-03-12 21:06 ` Glenn Morris
2019-03-13 3:34 ` Eli Zaretskii
2019-03-13 5:03 ` Phil Sainty
2019-03-13 6:37 ` Phil Sainty
2019-03-13 10:31 ` Eli Zaretskii
2019-03-13 11:52 ` Phil Sainty
2019-03-13 15:25 ` Eli Zaretskii
2019-03-13 15:34 ` dancol
2019-03-30 9:27 ` Eli Zaretskii
2019-03-14 5:57 ` Glenn Morris
2019-03-14 6:06 ` Eli Zaretskii
2019-04-02 0:26 ` Noam Postavsky
2019-04-23 9:21 ` martin rudalics
2019-04-23 10:57 ` Noam Postavsky
2019-06-20 5:01 ` YAMAMOTO Mitsuharu
2019-06-20 9:17 ` YAMAMOTO Mitsuharu
2019-06-20 11:04 ` mituharu
2019-06-26 12:56 ` Phil Sainty
2019-06-30 6:31 ` YAMAMOTO Mitsuharu
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=83ftrs3xl4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34819@debbugs.gnu.org \
--cc=psainty@orcon.net.nz \
/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).