From: martin rudalics <rudalics@gmx.at>
To: "Clément Pit--Claudel" <clement.pitclaudel@live.com>,
23341@debbugs.gnu.org
Subject: bug#23341: x-show-tip does not respect the value of tooltip-hide-delay, and the default tooltip timeout isn't configurable
Date: Sun, 24 Apr 2016 10:40:20 +0200 [thread overview]
Message-ID: <571C8674.5050702@gmx.at> (raw)
In-Reply-To: <571BB03F.5000906@live.com>
> Isn't that one more burden that we impose on package developers for
> essentially no good reason? Also. what do you mean by "use the value
> by default"? Do you mean to initialize a defcustom? That won't work:
> changing the value of tooltip-hied-delay would not update that of the
> corresponding defcustom. Or do you mean that all packages using
> tooltips should explicitly pass a hide-delay argument to pos-tip or
> tooltip or x-show-tip, with that argument being (or
> package-local-delay tooltip-hide-delay)? That sounds cumbersome and
> error prone: if that's how we want things done, why is the delay
> argument optional?
Package ‘foo’ would evaluate the value of ‘foo-tooltip-hide-delay’
which, by default, should yield the value ‘tooltip-hide-delay’ evaluates
to unless the user has customized ‘foo-tooltip-hide-delay’. That value
should be passed by ‘foo’ to ‘x-show-tip’. If you can think of a better
solution with less surprising results for the user please tell me.
> In any case, do we gain anything from hardcoding 5 as the default?
As Eli expained elsewhere this is an internal value which, ideally, is
never used. And I fully share everything Eli said on this subject.
martin
next prev parent reply other threads:[~2016-04-24 8:40 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 2:47 bug#23341: x-show-tip does not respect the value of tooltip-hide-delay, and the default tooltip timeout isn't configurable Clément Pit--Claudel
2016-04-23 6:53 ` Eli Zaretskii
2016-04-23 14:22 ` Clément Pit--Claudel
2016-04-23 14:36 ` Eli Zaretskii
2016-04-23 15:26 ` Clément Pit--Claudel
2016-04-23 17:54 ` Eli Zaretskii
2016-04-23 22:33 ` Clément Pit--Claudel
2016-04-24 6:08 ` Eli Zaretskii
2016-04-24 14:43 ` Clément Pit--Claudel
2016-04-24 15:59 ` Eli Zaretskii
2016-04-23 8:13 ` martin rudalics
2016-04-23 14:27 ` Clément Pit--Claudel
2016-04-23 17:08 ` martin rudalics
2016-04-23 17:26 ` Clément Pit--Claudel
2016-04-24 8:40 ` martin rudalics [this message]
2016-04-24 14:40 ` Clément Pit--Claudel
2016-04-24 15:57 ` Eli Zaretskii
2016-04-24 16:30 ` Clément Pit--Claudel
2016-04-26 6:35 ` martin rudalics
2016-04-26 11:25 ` Dmitry Gutov
2022-04-30 15:10 ` Lars Ingebrigtsen
2022-04-30 15:30 ` Eli Zaretskii
2022-04-30 15:38 ` Lars Ingebrigtsen
2022-04-30 16:01 ` Eli Zaretskii
2022-04-30 16:22 ` Lars Ingebrigtsen
2022-04-30 16:50 ` Eli Zaretskii
2022-05-01 0:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-01 8:37 ` Lars Ingebrigtsen
2022-05-01 9:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-01 9:53 ` Lars Ingebrigtsen
2022-05-01 10:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-01 10:39 ` Lars Ingebrigtsen
2022-05-01 11:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-01 11:42 ` Lars Ingebrigtsen
2022-05-01 12:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-01 16:19 ` Drew Adams
2022-05-02 0:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-02 2:19 ` Drew Adams
2022-05-02 2:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-02 14:53 ` Drew Adams
2022-05-03 0:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-03 1:32 ` Drew Adams
2022-05-03 2:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-03 4:16 ` Drew Adams
2022-05-03 4:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=571C8674.5050702@gmx.at \
--to=rudalics@gmx.at \
--cc=23341@debbugs.gnu.org \
--cc=clement.pitclaudel@live.com \
/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.