From: martin rudalics <rudalics@gmx.at>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>, 24579@debbugs.gnu.org
Subject: bug#24579: [PATCH] borderless windows on OS X
Date: Sun, 02 Oct 2016 10:30:26 +0200 [thread overview]
Message-ID: <57F0C5A2.1060206@gmx.at> (raw)
In-Reply-To: <496bdc1e-b673-228c-d253-b0eef6e08c21@gmail.com>
> This looks good indeed, but we don't have the same thing exposed to
> ELisp for GNU/Linux, do we?
We do: Emacs' native tooltip frames with a ‘border-width’ of zero should
accomplish precisely that.
> (https://emacs.stackexchange.com/questions/20167/how-do-i-create-a-borderless-frame
> was about this).
The recipes there don't work: The ‘border-width’ parameter is usually
ignored by the window manager for "normal" frames and replaced by the
standard border. You have to create a CWOverrideRedirect window - a
frame that is _not_ handled by the window manager.
> Isn't that a prerequisite before merging this
> feature?
It would be. But in fact the patch has NS still lag behind slightly
because it doesn't allow to set the border width.
martin
next prev parent reply other threads:[~2016-10-02 8:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 1:31 bug#24579: [PATCH] borderless windows on OS X Jay McCarthy
2016-10-01 8:44 ` martin rudalics
2016-10-01 11:53 ` Jay McCarthy
2016-10-01 13:41 ` martin rudalics
2016-10-01 20:18 ` Jay McCarthy
2016-10-02 8:29 ` martin rudalics
2016-10-13 17:56 ` Jay McCarthy
2016-10-13 18:36 ` martin rudalics
2016-10-13 22:27 ` Jay McCarthy
2016-10-01 21:26 ` Alan Third
2016-10-01 22:18 ` Jay McCarthy
2016-10-01 23:04 ` Alan Third
2016-10-02 0:49 ` Clément Pit--Claudel
2016-10-02 8:30 ` martin rudalics [this message]
2016-10-02 15:07 ` Alan Third
2016-10-02 16:39 ` martin rudalics
2016-10-02 16:49 ` Alan Third
2016-10-02 18:10 ` martin rudalics
2016-10-02 18:31 ` Clément Pit--Claudel
2016-10-02 15:18 ` Clément Pit--Claudel
2016-10-02 16:39 ` martin rudalics
2016-10-02 16:50 ` Clément Pit--Claudel
2016-10-02 18:09 ` martin rudalics
2017-04-21 19:49 ` Alan Third
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=57F0C5A2.1060206@gmx.at \
--to=rudalics@gmx.at \
--cc=24579@debbugs.gnu.org \
--cc=clement.pit@gmail.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.