From: Van Ly via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: eliz@gnu.org, 74496@debbugs.gnu.org
Subject: bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts
Date: Sat, 30 Nov 2024 19:25:41 +0000 [thread overview]
Message-ID: <dcsldx05xsa.fsf@SDF.ORG> (raw)
In-Reply-To: <8529cd17-7c52-44fc-a8fa-0521b2f26474@gmx.at> (message from martin rudalics on Sat, 30 Nov 2024 20:01:24 +0100)
martin rudalics <rudalics@gmx.at> writes:
> I'm completely lost. I nowhere see the frame size change - a fullscreen
> frame stays at 1920x1080 a maximized one at 1914x1074 and the positions
> remain the same too. OTOH the value of the fullscreen parameter is
> reset to nil in both cases. Can you run xwininfo to check the sizes
> before and after restarting CTWM.
An emacs session that never uses CTWM's `toggle zoom' to "maximize" the
frame with border decorations showing to full frame on screen will have
the following result.
Line 7 has the frame size change.
1 ;; A. F11 fullscreen before
2 (frame-geometry)
3 ((outer-position -3 . -3) (outer-size 1920 . 1080) (external-border-size -3 . -3) (outer-border-width . 0) (title-bar-size 0 . 6) (menu-bar-external . t) (menu-bar-size 0 . 0) (tab-bar-size 1918 . 14) (tool-bar-external) (tool-bar-position . top) (tool-bar-size 0 . 0) (internal-border-width . 1))
4
5 ;; Z. F11 fullscreen after
6 (frame-geometry)
=> 7 ((outer-position -3 . -3) (outer-size 1920 . 1072) (external-border-size -3 . -3) (outer-border-width . 0) (title-bar-size 0 . 6) (menu-bar-external . t) (menu-bar-size 0 . 0) (tab-bar-size 1918 . 14) (tool-bar-external) (tool-bar-position . top) (tool-bar-size 0 . 0) (internal-border-width . 1))
8
9 ;; A. F11 fullscreen before
10 (frame-parameter nil 'fullscreen) ; => fullboth
11
12 ;; Z. F11 fullscreen after
13 (frame-parameter nil 'fullscreen) ;=> nil
Using CTWM's `toggle zoom' to "maximize" allows the F11 fullscreen to
persist across CTWM restart.
Hope that helps.
--
vl
prev parent reply other threads:[~2024-11-30 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 18:28 bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 10:23 ` Eli Zaretskii
2024-11-30 10:36 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 13:03 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 16:53 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 18:21 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 19:01 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 19:25 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=dcsldx05xsa.fsf@SDF.ORG \
--to=bug-gnu-emacs@gnu.org \
--cc=74496@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rudalics@gmx.at \
--cc=van.ly@SDF.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).