From: Alan Third <alan@idiocy.org>
To: martin rudalics <rudalics@gmx.at>
Cc: Aaron Jensen <aaronjensen@gmail.com>, 28872@debbugs.gnu.org
Subject: bug#28872: 26.0.90; non-native-fullscreen does not play well with ns-transparent-titlebar on macOS
Date: Sat, 28 Oct 2017 14:11:27 +0100 [thread overview]
Message-ID: <20171028131127.GA70513@breton.holly.idiocy.org> (raw)
In-Reply-To: <59F19531.8060408@gmx.at>
On Thu, Oct 26, 2017 at 09:56:33AM +0200, martin rudalics wrote:
> > In order to use lisp to do the fullscreen thing we’d need to keep
> > track of various ‘windowed’ frame parameters, ie. undecorated, width,
> > height, origin, maybe others. I assume it would be OK to stick them
> > into the frame-parameters alist under a special key, so we know where
> > they are when we want to switch back.
>
> We might need the 'original-width' and 'original-height' values for
> other platforms as well. I'm still not happy about our current
> implementation of fullscreen. But what is the 'origin' parameter?
The top and left parameters. I couldn’t remember what they were
called.
What are original-width and original-height used for?
--
Alan Third
next prev parent reply other threads:[~2017-10-28 13:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 3:00 bug#28872: 26.0.90; non-native-fullscreen does not play well with ns-transparent-titlebar on macOS Aaron Jensen
2017-10-17 14:25 ` Alan Third
2017-10-19 1:08 ` Aaron Jensen
2017-10-19 11:17 ` Alan Third
[not found] ` <CAHyO48y5jy7L7E+BZTtTAtd5eGcUb-W54FQXhfEh444WPx4j3A@mail.gmail.com>
2017-10-25 13:38 ` Alan Third
2017-10-25 15:15 ` Aaron Jensen
2017-10-28 13:19 ` Alan Third
2017-10-28 17:15 ` Aaron Jensen
2017-10-28 17:17 ` Aaron Jensen
2017-11-05 18:59 ` Alan Third
2017-10-26 7:56 ` martin rudalics
2017-10-28 13:11 ` Alan Third [this message]
2017-10-31 8:40 ` martin rudalics
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=20171028131127.GA70513@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=28872@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--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 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.