From: Aaron Jensen <aaronjensen@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: 28512@debbugs.gnu.org
Subject: bug#28512: 26.0.60; undecorated frames on macOS 10.13 do not resize properly
Date: Mon, 16 Oct 2017 08:49:07 -0400 [thread overview]
Message-ID: <CAHyO48y5PaXHaXXsX15jEanxP2C6FS8cFYb1b=x0FpxFKW_BMw@mail.gmail.com> (raw)
In-Reply-To: <20171016100119.GA41757@breton.holly.idiocy.org>
On October 16, 2017 at 3:01:14 AM, Alan Third
(alan@idiocy.org(mailto:alan@idiocy.org)) wrote:
> On Sat, Oct 14, 2017 at 02:47:41PM -0700, Aaron Jensen wrote:
> > I was able to get some information from the author of iTerm2. The
> > problem is definitely that Emacs changes the window style to
> > resizable. If the NSWindow is recreated as resizable then it works
> > fine.
>
> I don’t understand, we’re not changing the resizable attribute.
I’m sorry, I miswrote. I meant that the borderless attribute is changed.
> > So that leaves a couple of questions:
> >
> > 1. Is it possible to create the first frame with undecorated set?
>
> So create the window undecorated, then immediately switch it to
> decorated?
What I meant was how do I start emacs while telling it to create its
initial frame undecorated if that’s my desire. Setting
`initial-display-alist` to include `(undecorated . t)` in `init.el`
seems to be insufficient, because the frame appears to be created
prior to `init.el` being eval’d.
> > 2. Would it be difficult to recreate the NSWindow housing the frame
> > when that frame parameter is changed?
>
> I’m not sure. I’ll have to go and have a look.
Thanks.
Aaron
next prev parent reply other threads:[~2017-10-16 12:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 15:10 bug#28512: 26.0.60; undecorated frames on macOS 10.13 do not resize properly Aaron Jensen
2017-09-19 15:35 ` Aaron Jensen
2017-09-19 21:34 ` Alan Third
2017-09-19 21:44 ` Aaron Jensen
2017-09-23 14:31 ` Aaron Jensen
2017-09-23 19:11 ` Alan Third
2017-09-23 21:35 ` Aaron Jensen
2017-09-24 11:27 ` Alan Third
2017-09-24 15:43 ` Aaron Jensen
2017-09-24 21:05 ` Alan Third
2017-09-25 0:39 ` Aaron Jensen
2017-09-25 10:13 ` Alan Third
2017-09-25 15:18 ` Aaron Jensen
2017-09-25 16:33 ` Alan Third
2017-09-25 17:02 ` Aaron Jensen
2017-10-14 21:47 ` Aaron Jensen
2017-10-16 10:01 ` Alan Third
2017-10-16 12:49 ` Aaron Jensen [this message]
2017-10-16 20:46 ` Alan Third
2017-10-17 2:50 ` Aaron Jensen
2017-10-17 8:58 ` Alan Third
2017-10-18 16:08 ` Aaron Jensen
2017-10-18 16:12 ` Aaron Jensen
2017-10-18 19:32 ` Alan Third
2017-10-18 19:50 ` Alan Third
2017-10-19 1:00 ` Aaron Jensen
2021-07-25 11:17 ` Alan Third
2021-07-25 17:06 ` Aaron Jensen
2021-12-22 20:52 ` Alan Third
2021-12-23 15:20 ` Aaron Jensen
2021-12-23 16:09 ` Alan Third
2021-12-23 18:19 ` Aaron Jensen
2021-12-28 11:43 ` Alan Third
2021-12-28 16:18 ` Aaron Jensen
2022-01-04 10:58 ` Alan Third
2017-10-17 8:59 ` martin rudalics
2017-10-17 16:06 ` Aaron Jensen
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='CAHyO48y5PaXHaXXsX15jEanxP2C6FS8cFYb1b=x0FpxFKW_BMw@mail.gmail.com' \
--to=aaronjensen@gmail.com \
--cc=28512@debbugs.gnu.org \
--cc=alan@idiocy.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).