From: Eli Zaretskii <eliz@gnu.org>
To: David Hedlund <public@beloved.name>
Cc: 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: Sat, 30 Sep 2023 16:57:47 +0300 [thread overview]
Message-ID: <83o7hjahlw.fsf@gnu.org> (raw)
In-Reply-To: <be90c5de-f7fe-4759-b91f-d99173179aea@beloved.name> (message from David Hedlund on Fri, 29 Sep 2023 23:05:23 +0200)
> Date: Fri, 29 Sep 2023 23:05:23 +0200
> From: David Hedlund <public@beloved.name>
>
> Shouldn't
>
> https://www.gnu.org/software/emacs/manual/html_node/efaq/Fullscreen-mode-on-MS_002dWindows.html
> be renamed to
>
> https://www.gnu.org/software/emacs/manual/html_node/efaq/Maxmize-mode-on-MS_002dWindows.html
> ?
>
> Since it's about maximize mode, not full screen mode.
"Fullscreen" is widely accepted terminology for what is discussed
there. Moreover, typing "i maximized RET" and "i fullscreen RET" in
both the ELisp and the Emacs user manuals brings you to the same text,
so we already have the two equivalent terms covered, and renaming the
node is not necessary IMO.
> This will also help confusion with the ongoing discussion in the mailing-list with subject: "Solution to a
> proposed FAQ, how to maximize emacs quickly (like `emacs --maximize`) for GNU/Linux"
What confusion is that? (It's a long discussion, with several
participants, so it is hard to tell to what confusion you are alluding
here.)
next prev parent reply other threads:[~2023-09-30 13:57 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o7hjahlw.fsf@gnu.org \
--to=eliz@gnu.org \
--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 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.