From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: Chris Feng <chris.w.feng@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: 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?)
Date: Tue, 16 Feb 2016 17:55:19 -0500 [thread overview]
Message-ID: <56C3A8D7.9010207@gmail.com> (raw)
In-Reply-To: <CAP4=87E1er23k++eVm6W_ceSwVw1L6Gb_zZo6zqVW-4wh1cdgA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On 02/16/2016 05:41 PM, Chris Feng wrote:
>> Scaling back on the original intent, then, could we expose to Lisp a way to create a chrome-less frame, presumably in just the same way as the tooltip code does it? Something like `remove_frame_chrome(frame *f)`, which one would call before making a frame visible.
>
> This will definitely work on X. Basically an X window manager takes over a window when it gets mapped (becomes visible). But I'm not sure if the procedure is necessary on other platforms.
>
> I think it'd be better if we can control this directly by feeding `make-frame' a new frame parameter.
Indeed, that would be nice :)
Can we set this parameter after the corresponding X window has been displayed? Or should this new frame parameter only make sense in make-frame calls?
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-02-16 22:55 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 [this message]
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
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=56C3A8D7.9010207@gmail.com \
--to=clement.pit@gmail.com \
--cc=chris.w.feng@gmail.com \
--cc=emacs-devel@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).