From: steve-humphreys@gmx.com
To: Drew Adams <drew.adams@oracle.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
help-gnu-emacs@gnu.org, Pankaj Jangid <pankaj@codeisgreat.org>
Subject: Re: RE: set-frame-parameter
Date: Thu, 10 Dec 2020 20:03:25 +0100 [thread overview]
Message-ID: <trinity-20468e4a-30fb-46b3-8a07-6996bd5b1317-1607627005004@3c-app-mailcom-bs13> (raw)
In-Reply-To: <95b9b0cd-77e0-4bff-aca5-d8ebd7129c92@default>
> Sent: Thursday, December 10, 2020 at 7:51 PM
> From: "Drew Adams" <drew.adams@oracle.com>
> To: "Pankaj Jangid" <pankaj@codeisgreat.org>
> Cc: "Michael Heerdegen" <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org, steve-humphreys@gmx.com
> Subject: RE: set-frame-parameter
>
> > Perhaps you want (toggle-frame-maximized) instead of
> > (toggle-frame-fullscreen)
> >
> > As Michael pointed out, fullscreen things are ‘window-system’
> > things. Whereas a maximised window can be resized.
>
> Whichever is preventing frame-size changes.
> That's the point. If a user can work around
> this inconvenience with an extra sexp then
> Emacs itself could presumably make that
> workaround unnecessary by doing it automatically.
It was a big stumbling block for me. In addition, the proper procedure for resizing was confusing
(set-frame-parameter, set-frame-size). Can one use either, both and mhich should be called first.
next prev parent reply other threads:[~2020-12-10 19:03 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 ` set-frame-parameter Michael Heerdegen
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 ` steve-humphreys [this message]
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=trinity-20468e4a-30fb-46b3-8a07-6996bd5b1317-1607627005004@3c-app-mailcom-bs13 \
--to=steve-humphreys@gmx.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=pankaj@codeisgreat.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).