From: David Hedlund <public@beloved.name>
To: 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: Tue, 3 Oct 2023 00:40:49 +0200 [thread overview]
Message-ID: <2d4fcd29-6b93-4e8f-9a43-80d950255687@beloved.name> (raw)
In-Reply-To: <8334yva2m8.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2523 bytes --]
On 9/30/23 21:21, Eli Zaretskii wrote:
>> Date: Sat, 30 Sep 2023 21:06:52 +0200
>> From: David Hedlund<public@beloved.name>
>>
>> Do these two methods not work, or have some downside? If they do
>> work, then we could perhaps _add_ an alternative solution, but I don't
>> see why we should _replace_ the existing one(s).
>>
>> I agree that it should be added (not replaced).
> OK.
>
>> Next, the alternative solution does have a drawback, albeit a minor
>> one: it uses early-init.el, something that is explicitly NOT
>> recommended for display-related customizations. It evidently works in
>> this case, but advertising this in the FAQ flies in the face of our
>> general recommendation not to do this kind of stuff there.
> Specifically, the Emacs user manual says:
>
> We do not recommend that you move into ‘early-init.el’ customizations
> that can be left in the normal init files. That is because the early
> init file is read before the GUI is initialized, so customizations
> related to GUI features will not work reliably in ‘early-init.el’. By
> contrast, the normal init files are read after the GUI is initialized.
> If you must have customizations in the early init file that rely on GUI
> features, make them run off hooks provided by the Emacs startup, such as
> ‘window-setup-hook’ or ‘tty-setup-hook’. *Note Hooks::.
>
> So I wonder whether we should advertise the suggested addition for
> early-init file. Stefan, WDYT?
>
>> While we're speaking about this, this is a relevant question regarding the issue for GNU/Linux: So
>> even "(push '(fullscreen . maximized) default-frame-alist)" to ~/.emacs.d/early-init.el is the only
>> solution to automatically maximize emacs without the visually distracting effect in GNU/Linux, should
>> it not be added to the FAQ to a new section, say
>> https://www.gnu.org/software/emacs/manual/html_node/efaq/Fullscreen-mode-on-GNU-Linux.htm?
>> Just "(add-hook 'emacs-startup-hook 'toggle-frame-maximized)" to the top ~/.emacs file if it has a
>> common size (say 100 lines), will cause it to maximize the windows but not without the visually
>> distracting effect.
> Is this indeed a "frequently-asked" question, about GNU/Linux?
Yes.
> If it
> is, I'm okay with adding such a section, or even rewriting this
> section (and renaming it) to make it not Windows-specific. But we do
> not usually add here answers for questions just because they _could_
> be asked. Again, I'd like to hear Stefan's opinion on this.
>
[-- Attachment #2: Type: text/html, Size: 3598 bytes --]
next prev parent reply other threads:[~2023-10-02 22:40 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 [this message]
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
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=2d4fcd29-6b93-4e8f-9a43-80d950255687@beloved.name \
--to=public@beloved.name \
--cc=emacs-devel@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.
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).