From: martin rudalics <rudalics@gmx.at>
To: "Clément Pit--Claudel" <clement.pitclaudel@live.com>,
"Eli Zaretskii" <eliz@gnu.org>
Cc: 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: Tue, 26 Apr 2016 08:35:00 +0200 [thread overview]
Message-ID: <571F0C14.8070404@gmx.at> (raw)
In-Reply-To: <571CF48D.7010207@live.com>
> Hence "(or of a new similar variable)" :)
I suppose that most clients of ‘x-show-tip’ peruse this function for
showing a frame that displays more persistent information - hence the
need for customizing this delay independently from ‘tooltip-hide-delay’.
I'm currently trying to implement something like tip-like frames which
should allow applications to display an arbitrary number of such frames
and a strategy for hiding and moving such frames (the latter being the
more problematic part). I hope that as soon as these frames can be
used, the need for a "new similar variable" will be moot ;-)
martin
next prev parent reply other threads:[~2016-04-26 6:35 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
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 [this message]
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
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=571F0C14.8070404@gmx.at \
--to=rudalics@gmx.at \
--cc=23341@debbugs.gnu.org \
--cc=clement.pitclaudel@live.com \
--cc=eliz@gnu.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 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).