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: Mon, 12 Feb 2018 06:43:57 -0800 (PST) [thread overview]
Message-ID: <28591819-f037-4517-b9b1-210b3f103114@default> (raw)
In-Reply-To: <5A815DD0.9090205@gmx.at>
> > 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.
That's good to hear. That was not clear to me.
> > 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.
I certainly got the wrong impression from what you
wrote, then. Thanks for clarifying.
> > 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.
Very good to hear. Glad I asked for clarification,
and thank you for clarifying. None of what you say now
was clear (to me) from your previous msgs in this thread.
Sorry, if the misunderstanding was my fault here.
And thanks for fixing the `x-show-tip' bug.
prev parent reply other threads:[~2018-02-12 14:43 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
2018-02-12 14:43 ` Drew Adams [this message]
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=28591819-f037-4517-b9b1-210b3f103114@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 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).