From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: set-frame-parameter
Date: Thu, 10 Dec 2020 18:26:21 +0100 [thread overview]
Message-ID: <875z59fu82.fsf@web.de> (raw)
In-Reply-To: d44b01aa-1b17-42fa-9d2a-2b571928aaba@default
Drew Adams <drew.adams@oracle.com> writes:
> Do we know whether it was explicitly by design
> that you can't change the frame size when it's
> fullscreen without first turning off fullscreen?
>
> That seems odd to me, but perhaps it is by design
> and there's a good reason for it. If not, maybe
> it should be fixed...
With the X window system, that's the behavior for any maximized window,
in all window managers I used. Dunno if Emacs has a choice here, since
resizing and moving are X things.
How is the behavior in other `window-system's?
Michael.
next prev parent reply other threads:[~2020-12-10 17:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 22:24 set-frame-parameter steve-humphreys
2020-12-09 22:58 ` set-frame-parameter Stephen Berman
2020-12-09 23:04 ` set-frame-parameter steve-humphreys
2020-12-09 23:13 ` set-frame-parameter Stephen Berman
2020-12-09 23:19 ` set-frame-parameter steve-humphreys
2020-12-09 23:26 ` set-frame-parameter Stephen Berman
2020-12-09 23:29 ` set-frame-parameter Stephen Berman
2020-12-09 23:39 ` set-frame-parameter steve-humphreys
2020-12-09 23:46 ` set-frame-parameter Stephen Berman
2020-12-09 23:49 ` set-frame-parameter steve-humphreys
2020-12-09 23:43 ` set-frame-parameter steve-humphreys
2020-12-09 23:47 ` set-frame-parameter Stephen Berman
2020-12-09 23:50 ` set-frame-parameter steve-humphreys
2020-12-10 0:19 ` set-frame-parameter Michael Heerdegen
2020-12-10 0:38 ` set-frame-parameter Michael Heerdegen
2020-12-10 2:13 ` set-frame-parameter steve-humphreys
2020-12-10 2:33 ` set-frame-parameter steve-humphreys
2020-12-10 3:01 ` set-frame-parameter Michael Heerdegen
2020-12-10 3:08 ` set-frame-parameter steve-humphreys
2020-12-10 3:55 ` set-frame-parameter Michael Heerdegen
2020-12-10 4:09 ` set-frame-parameter steve-humphreys
2020-12-10 3:17 ` set-frame-parameter steve-humphreys
2020-12-10 3:42 ` set-frame-parameter steve-humphreys
2020-12-10 3:59 ` set-frame-parameter Michael Heerdegen
2020-12-10 4:11 ` set-frame-parameter steve-humphreys
2020-12-10 16:13 ` set-frame-parameter Drew Adams
2020-12-10 17:26 ` Michael Heerdegen [this message]
2020-12-10 18:31 ` set-frame-parameter Drew Adams
2020-12-10 18:45 ` set-frame-parameter Pankaj Jangid
2020-12-10 18:51 ` set-frame-parameter Drew Adams
2020-12-10 19:03 ` set-frame-parameter steve-humphreys
2020-12-10 20:44 ` set-frame-parameter Stephen Berman
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=875z59fu82.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@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.
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).