From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 20164@debbugs.gnu.org
Subject: bug#20164: 25.0.50; Do not tell users that `x-show-tip' is internal
Date: Fri, 02 Aug 2019 21:57:39 +0300 [thread overview]
Message-ID: <835znffl98.fsf@gnu.org> (raw)
In-Reply-To: <87imrfphpx.fsf@mouse.gnus.org> (message from Lars Ingebrigtsen on Fri, 02 Aug 2019 20:03:54 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: drew.adams@oracle.com, 20164@debbugs.gnu.org
> Date: Fri, 02 Aug 2019 20:03:54 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> I agree that the calling conventions for `x-show-tip' seems to be much
> >> nicer than `tooltip-show'.
> >
> > If you do, please explain it to me, because the above arguments don't
> > convince me, certainly not that x-show-tip's API is "nicer". Maybe
> > I'm missing something.
>
> I think explicit parameters to a function is almost always to be
> preferred to binding variables and then calling a function that takes no
> parameters. In this case, you're supposed bind `tooltip-{x,y}-offset'
> according to the doc string.
Only if you for some reason don't like the defaults. Which should
happen rarely, if ever.
> > https://lists.gnu.org/archive/html/emacs-pretest-bug/2007-03/msg00261.html
> >
> > The conclusion to take out of that discussion is that whoever uses
> > x-show-tip should know very well what they are doing, which is another
> > way of saying "kids, don't try that at home", a.k.a. "an internal
> > function".
>
> Makes sense to me, and I'm closing this bug report.
Thanks.
next prev parent reply other threads:[~2019-08-02 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 16:40 bug#20164: 25.0.50; Do not tell users that `x-show-tip' is internal Drew Adams
2019-08-02 12:28 ` Lars Ingebrigtsen
2019-08-02 14:20 ` Eli Zaretskii
2019-08-02 18:03 ` Lars Ingebrigtsen
2019-08-02 18:57 ` Eli Zaretskii [this message]
2019-08-02 15:38 ` 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=835znffl98.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20164@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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.