From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>,
Stephen Berman <stephen.berman@gmx.net>,
30399@debbugs.gnu.org
Subject: bug#30399: 27.0.50; tooltips are broken
Date: Mon, 12 Feb 2018 10:26:40 +0100 [thread overview]
Message-ID: <5A815DD0.9090205@gmx.at> (raw)
In-Reply-To: <d6a81063-3cb0-4486-9402-ad9e415e4628@default>
>> That when the behavior of 'x-show-tip' changes,
>> applications will have to adapt.
>
> That's even more vague - not a clarification at all.
> What is the behavior change? What kind of adaptation
> are you hinting at?
That if for some reason the behavior of that function must be changed,
its callers may have to change too.
>> Currently there are no plans to replace 'x-show-tip' AFAICT.
>
> Let's not quibble over the word "replace", please.
>
> You imply that "the behavior of 'x-show-tip'" will
> change. That's what I'm asking about, in talking
> about "replacement".
'x-show-tip' had a bug that has been hopefully fixed. I did not imply
anything else.
> You also said that we should not use 'x-show-tip'
> but should use only `tooltip-show', which is much
> more limited - not a substitute for 'x-show-tip'
> at all.
I'm using 'x-show-tip' in my private code, so why should I say such a
thing.
> The question is, if `x-tool-tip' is not expected
> to be replaced, but it is expected to change, just
> _how_ is it expected to change?
>
> Will we be able to do with the "new" `x-show-tip',
> what we can do with it now, even if we must "adapt"
> in some way to be able to do that?
Hopefully so.
> You are being quite vague, it seems. You make a
> pronouncement that we should not use the function,
> but also that it will change - somehow.
I did neither the former nor the latter.
> The real question is not the words to name the
> impending change or replacement that you warn us
> about.
>
> The question is how, after the change/replacement,
> to get done everything we can do now with that
> function.
Let's see to that when we're there.
martin
next prev parent reply other threads:[~2018-02-12 9:26 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
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 [this message]
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=5A815DD0.9090205@gmx.at \
--to=rudalics@gmx.at \
--cc=30399@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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.