From: Stefan Kangas <stefankangas@gmail.com>
To: David Hedlund <public@beloved.name>, emacs-devel@gnu.org
Subject: Re: Should https://www.gnu.org/software/emacs/manual/html_node/efaq/Fullscreen-mode-on-MS_002dWindows.html be renamed to Maxmize-mode-on-MS_002dWindows.html ?
Date: Sun, 22 Oct 2023 15:24:36 -0700 [thread overview]
Message-ID: <CADwFkm=MOY0=-G69_NWFz4jSB64NDyFiMu5Vw557tMVe1+ehRA@mail.gmail.com> (raw)
In-Reply-To: <4ffcb78e-3735-4c9d-9755-ff3403ca8071@beloved.name>
David Hedlund <public@beloved.name> writes:
> Also, people expect GUIs that can start with a maximized window to not
> gradually expand it. Emacs is the only GUI that behaves this way of all
> the GUIs that I'm currently using.
Right, but taking a step back here: should we consider that as a bug?
IOW, instead of documenting workarounds, why isn't --maximized fixed to
not have the "slightly distracting visual effect"? Is that impractical
for some reason?
next prev parent reply other threads:[~2023-10-22 22:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 21:05 Should https://www.gnu.org/software/emacs/manual/html_node/efaq/Fullscreen-mode-on-MS_002dWindows.html be renamed to Maxmize-mode-on-MS_002dWindows.html ? David Hedlund
2023-09-30 13:57 ` Eli Zaretskii
2023-09-30 18:09 ` chad
2023-09-30 18:36 ` Eli Zaretskii
2023-09-30 19:06 ` David Hedlund
2023-09-30 19:21 ` Eli Zaretskii
2023-10-02 22:40 ` David Hedlund
2023-10-02 23:05 ` Emanuel Berg
2023-10-05 3:56 ` David Hedlund
2023-10-21 9:35 ` Stefan Kangas
2023-10-21 9:52 ` Eli Zaretskii
2023-10-21 10:02 ` Stefan Kangas
2023-10-21 11:18 ` Eli Zaretskii
2023-10-21 20:05 ` chad
2023-10-21 12:55 ` David Hedlund
2023-10-22 22:24 ` Stefan Kangas [this message]
2023-10-23 13:02 ` Eli Zaretskii
2023-10-23 15:25 ` David Hedlund
2023-10-23 15:33 ` Stefan Kangas
2023-10-23 15:58 ` David Hedlund
2023-10-28 17:25 ` Stefan Kangas
2023-10-28 17:34 ` Emanuel Berg
2023-10-28 18:51 ` Eli Zaretskii
2023-10-28 19:39 ` Emanuel Berg
2023-10-28 18:02 ` David Hedlund
2023-10-28 20:03 ` Stefan Kangas
2023-11-04 13:58 ` Stefan Kangas
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='CADwFkm=MOY0=-G69_NWFz4jSB64NDyFiMu5Vw557tMVe1+ehRA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=public@beloved.name \
/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).