From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel 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 21:36:19 +0300 Message-ID: <837co7a4po.fsf@gnu.org> References: <83o7hjahlw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28969"; mail-complaints-to="usenet@ciao.gmane.io" Cc: public@beloved.name, Emacs-devel@gnu.org To: chad Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 30 20:37:10 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qmepx-0007GO-FC for ged-emacs-devel@m.gmane-mx.org; Sat, 30 Sep 2023 20:37:09 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qmepX-0002mL-Nu; Sat, 30 Sep 2023 14:36:43 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qmepV-0002m5-4H for Emacs-devel@gnu.org; Sat, 30 Sep 2023 14:36:41 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qmepR-0005lW-NM; Sat, 30 Sep 2023 14:36:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=Meuz9ciBH1W84j6ZzwExmZSbswTq07H0j2Yq8Lv2xWo=; b=eVqTGlJ207QlKowoAnWJ vAnFSS1bvbtqia0/d6ETvieRKuYsRuDENNPvKND0wRO2N8Hn1OPPqNNzQ1Phyu8QvnI0beWrs0FSe Ar0ZEQ5Ii3M54Ijqu9p7FB6F68hZ7O1dsHnkhw6y2M/7l7AZ/xgbDdUWfWkRUGPnnCVgEGPlZD4+5 z3pG4JruHaVBR3oEWtPeJVL8qujBDlLv3R/XJsqPfcYMlb+7eHvxX1GCcs2KbYnW9oT9iqqbu6yNk vaQNQbLzdOdlaXv/VgevzNscIE3wabi01DyRDgq7BEZOTFXjszyGTXcatVPngatmFiXXuduk23N2W fDz3zKynnPgNeQ==; In-Reply-To: (message from chad on Sat, 30 Sep 2023 14:09:22 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:311214 Archived-At: > From: chad > Date: Sat, 30 Sep 2023 14:09:22 -0400 > Cc: David Hedlund , Emacs-devel@gnu.org > > I'm trying to catch up here, as David Hedlund asked me if I could help > out (as English is not his most comfortable language), and the > conversation has splintered somewhat. I myself joined the conversation > a bit late, so I might be confused myself. > > The issue that DH has raised, as I understand it, surrounds the FAQ > entry in the Emacs manual titled "Fullscreen mode on MS-Windows". This > FAQ covers a few different ways to adjust the emacs frame under > MS-Windows, including older versions of emacs that predate the emacs > function toggle-frame-maximized (or perhaps predate it functioning > under MS-Windows). He also prefers to avoid the situation where Emacs > maps a "normal" window and then resizes it later (perhaps because it's > distracting, because it seems to take longer, or some other reason). > > The FAQ entry in the most recent release talks about avoiding this > "distracting visual effect" by setting ersatz X Resources via the > Windows registry or a short set of emacs commands. IIUC, DH was > searching for a solution that would cause emacs to start with a > fullscreen window (rather than start and quickly grow to fullscreen), > and that would work across platforms. This is where I jumped in. > > The solution I proposed was: add this line to the early-init.el file: > > (push '(fullscreen . maximized) default-frame-alist) > > There is a variant of this solution that instead uses: > > (push '(fullscreen . maximized) initial-frame-alist) > > to effect only the initial window. > > With that as the background, I think the proposal is: > > In the efaq node "Fullscreen mode on MS-Windows", replace the > following text: > > >Beginning with Emacs 24.4 either run Emacs with the ‘--maximized’ > >command-line option or put the following form in your init file (*note > >Setting up a customization file::): > > > > (add-hook 'emacs-startup-hook 'toggle-frame-maximized) > > With something like this: > > >Beginning with Emacs 24.4 either run Emacs with the ‘--maximized’ > >command-line option or put the following form in your early-init file > >(*note*note (emacs)Early Init File::): > > > > (push '(fullscreen . maximized) default-frame-alist) Thanks. Unfortunately, this just increases the confusion in this thread. Let me explain why. First, that section in the FAQ is specifically about MS-Windows. So looking for a portable solution is okay, but is out of scope of the question that section tries to answer. Second, I don't understand what is wrong with what the FAQ says already, viz.: Beginning with Emacs 24.4 either run Emacs with the ‘--maximized’ command-line option or put the following form in your init file (*note Setting up a customization file::): (add-hook 'emacs-startup-hook 'toggle-frame-maximized) [...] Alternatively, you can avoid the visual effect of Emacs changing its frame size entirely in your init file (i.e., without using the Registry), like this: @lisp (setq frame-resize-pixelwise t) (set-frame-position nil 0 0) (set-frame-size nil (display-pixel-width) (display-pixel-height) t) @end lisp 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). 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. To summarize: . if what we have in the FAQ is incorrect or not good enough, please someone explain what and why . if it _is_ correct, why replace it?