unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Alan Third <alan@idiocy.org>
Cc: martin rudalics <rudalics@gmx.at>, emacs-devel <emacs-devel@gnu.org>
Subject: RE: Fix some tooltip related problems
Date: Wed, 10 Jan 2018 13:02:42 -0800 (PST)	[thread overview]
Message-ID: <329fad14-bed5-409a-828c-facec2e4be35@default> (raw)
In-Reply-To: <20180110191755.GA79229@breton.holly.idiocy.org>

> > (x-show-tip (propertize "abc" 'face '(:foreground "gray")))
> >
> > What's different here from what you are talking about?
> > OK, I'm using MS Windows.  But does this not work also
> > on GNU/Linux and Mac?
> 
> This doesn’t work on the NS port. Tooltips on that platform are
> neither system tooltips nor fully‐fledged frames. I think it also
> doesn’t work with certain X toolkits (GTK?) where they use system
> tooltips.

I see.

> > And if that doesn't work on such platforms, can't we use
> > a ("normal") Emacs frame where such things do work?  Just
> > what is it that makes it impossible for Emacs to dim the
> > text in a tooltip?  Sorry, but this is not clear to me.
> 
> It’s beyond me why you’d want to dim a tooltip. Dimming of menu items
> is standard behaviour on many platforms whereas dimming a tooltip is,
> afaik, a completely novel behaviour and as a result would just be
> confusing.

1. The ability to use different Emacs faces in a tooltip
   frame is much more general than the use of that ability
   to dim the text in a tooltip.  It's a general feature.

   I didn't realize that Emacs was so limited in this regard
   on other platforms.  Thank goodness it works without a
   problem on at least some platforms (e.g. Windows).

   Given that limitation, I repeat the question: Can't we
   use a ("normal") Emacs frame, where things such as faces
   do work, to implement tooltips?

2. Wrt dimming a tooltip to show that its text, or some of it,
   applies generally, or at least in some contexts, but does
   not apply currently:

   The argument that we shouldn't do it because that would be
   "novel" isn't a good argument.  That a feature is "novel" is
   an argument neither for nor against its being added to Emacs.

   Emacs has, from the beginning, done things that weren't
   mainstream or even, yes, that were completely novel.
   There are some Emacs features that are still not found
   outside Emacs even though they've been in Emacs for decades.

   Ask yourself: How did dimming of menu items become standard
   behavior?  How did that feature ever get added to anything?
   Certainly not by someone who argued that it shouldn't be
   added because it is "novel" or is not yet standard.

   Did someone have to explain to you what a dimmed menu item
   is all about?  Is that inherently confusing the first time
   someone sees it?  I think not.  A tooltip with dimmed text
   is no more confusing.



  reply	other threads:[~2018-01-10 21:02 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08  9:53 Fix some tooltip related problems martin rudalics
2018-01-08 14:41 ` Drew Adams
2018-01-08 18:19   ` martin rudalics
2018-01-08 18:50     ` Drew Adams
2018-01-09  9:42       ` martin rudalics
2018-01-09 15:08         ` Drew Adams
2018-01-10 10:20           ` martin rudalics
2018-01-10 15:55             ` Drew Adams
2018-01-10 19:17               ` Alan Third
2018-01-10 21:02                 ` Drew Adams [this message]
2018-01-10 23:04                   ` Alan Third
2018-01-10 23:26                     ` Drew Adams
2018-01-11  3:39                   ` Eli Zaretskii
2018-01-11  7:03                 ` Yuri Khan
2018-01-11 14:32                   ` Drew Adams
2018-01-11 10:56               ` martin rudalics
2018-01-11 14:42                 ` Drew Adams
2018-01-11 17:06                   ` martin rudalics
2018-01-11 17:19                     ` Robert Pluim
2018-01-11 17:59                       ` Eli Zaretskii
2018-01-11 18:20                         ` martin rudalics
2018-01-11 23:33                         ` Daniele Nicolodi
2018-01-12  8:38                           ` Eli Zaretskii
2018-01-12  8:40                         ` Robert Pluim
2018-01-12  9:55                           ` Eli Zaretskii
2018-01-12 13:57                             ` Robert Pluim
2018-01-12 14:15                               ` Philipp Stephani
2018-01-11 19:54                       ` Richard Stallman
2018-01-11 23:26                       ` Stefan Monnier
2018-01-12  8:48                         ` Robert Pluim
2018-01-11 18:09                     ` Drew Adams
2018-01-11 18:54                       ` martin rudalics
2018-01-11 19:50                         ` Drew Adams
2018-01-12  8:47                           ` martin rudalics
2018-01-12 16:43                             ` Drew Adams
2018-01-08 18:47 ` Eli Zaretskii
2018-01-08 19:06   ` martin rudalics
2018-01-08 19:22     ` Eli Zaretskii
2018-01-09  9:42       ` martin rudalics
2018-01-19 18:54 ` martin rudalics

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=329fad14-bed5-409a-828c-facec2e4be35@default \
    --to=drew.adams@oracle.com \
    --cc=alan@idiocy.org \
    --cc=emacs-devel@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).