From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: "Johan Bockgård" <bojohan@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>,
Dmitry Gutov <dgutov@yandex.ru>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Could x-show-tip be reimplemented in Elisp? How does one create borderless frames from Elisp?
Date: Tue, 16 Feb 2016 17:18:24 -0500 [thread overview]
Message-ID: <56C3A030.8000506@gmail.com> (raw)
In-Reply-To: <87lh6kl4r1.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
On 02/16/2016 04:33 PM, Johan Bockgård wrote:
> Clément Pit--Claudel <clement.pit@gmail.com> writes:
>
>> Indeed, that's what I'd like. x-show-tip works perfectly for me (it
>> supports fonts, faces, etc. properly), expect for the fact that
>> updating the tooltip text causes it to be closed and reopened.
>
> Try this: ...
Thanks; this is a very clever trick :) Do you think there's a way to work around the other issue that I pointed out in the very first email of this thread?
> (...) there can be at most one tooltip displayed at any
> time; this means that we'd break other packages that display
> tooltips while completion is ongoing. Examples include
> company-quickhelp, which displays documentation for the currently
> selected entry next to completion candidates.
Cheers,
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-02-16 22:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 15:01 Could x-show-tip be reimplemented in Elisp? How does one create borderless frames from Elisp? Clément Pit--Claudel
2016-02-13 2:15 ` Chris Feng
2016-02-13 3:35 ` Clément Pit--Claudel
2016-02-13 3:57 ` Chris Feng
2016-02-16 20:12 ` Creating a "borderless" frame (without WM chrome) (was Re: Could x-show-tip be reimplemented in Elisp? How does one create borderless frames from Elisp?) Clément Pit--Claudel
2016-02-16 22:41 ` Chris Feng
2016-02-16 22:55 ` Clément Pit--Claudel
2016-02-16 23:14 ` Chris Feng
2016-02-16 23:46 ` Clément Pit--Claudel
2016-02-17 9:13 ` martin rudalics
2016-02-17 13:49 ` Chris Feng
2016-02-17 14:55 ` Clément Pit--Claudel
2016-02-18 1:28 ` Chris Feng
2016-02-17 14:57 ` Clément Pit--Claudel
2016-02-18 10:51 ` martin rudalics
2016-02-14 14:05 ` Could x-show-tip be reimplemented in Elisp? How does one create borderless frames from Elisp? Stefan Monnier
2016-02-14 16:44 ` Eli Zaretskii
2016-02-14 17:19 ` Stefan Monnier
2016-02-14 18:00 ` Eli Zaretskii
2016-02-16 20:06 ` Clément Pit--Claudel
2016-02-15 10:57 ` martin rudalics
2016-02-15 13:31 ` Stefan Monnier
2016-02-16 20:06 ` Clément Pit--Claudel
2016-02-16 20:05 ` Clément Pit--Claudel
2016-02-16 21:33 ` Johan Bockgård
2016-02-16 22:18 ` Clément Pit--Claudel [this message]
2016-02-17 9:12 ` martin rudalics
2016-02-17 14:26 ` Clément Pit--Claudel
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=56C3A030.8000506@gmail.com \
--to=clement.pit@gmail.com \
--cc=bojohan@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
/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).