all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 40047@debbugs.gnu.org, stephen.berman@gmx.net, dlacewell@gmail.com
Subject: bug#40047: 26.2; Images in tooltip-mode tooltips broken on Linux and OSX
Date: Sat, 14 Mar 2020 12:11:48 +0200	[thread overview]
Message-ID: <83a74jckkb.fsf@gnu.org> (raw)
In-Reply-To: <ad8456d1-a397-9d95-04de-8182d4ae7309@gmx.at> (message from martin rudalics on Sat, 14 Mar 2020 09:49:24 +0100)

> Cc: 40047@debbugs.gnu.org, dlacewell@gmail.com
> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 14 Mar 2020 09:49:24 +0100
> 
> The native case is neither broken nor can it be fixed.  Tooltips like
> those provided by GTK, Windows or many desktops are supposed to provide
> a uniform look across all sorts of applications that use them so that
> the user can easily recognize tooltips as what they are.  That's why they
> usually have customizable backgrounds, fonts and borders.  Applications
> are not supposed to meddle with them.

So you are saying the native tooltips cannot usefully display images?
I'd be surprised, but if that is indeed so, we should at least
document that, so users who do want images in tooltips could switch to
our tooltips.





  reply	other threads:[~2020-03-14 10:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12 21:54 bug#40047: 26.2; Images in tooltip-mode tooltips broken on Linux and OSX Dustin Lacewell
2020-03-13  8:18 ` Eli Zaretskii
2020-03-13 12:11   ` Stephen Berman
2020-03-13 14:24     ` Eli Zaretskii
2020-03-13 15:00       ` Dustin Lacewell
2020-03-14  8:49       ` martin rudalics
2020-03-14 10:11         ` Eli Zaretskii [this message]
2020-03-13 15:17 ` Alan Third
2020-03-13 15:57   ` Eli Zaretskii
2020-03-13 23:17     ` Alan Third
2020-03-14  8:12       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83a74jckkb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=40047@debbugs.gnu.org \
    --cc=dlacewell@gmail.com \
    --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.