bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts

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]

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]


Hello,

When the ctwm window manager is restarted, the emacs fullscreen frame,
set with `F11' key, shifts up by approximately 50 pixels and shows the
desktop background.  The right edge of the frame shifts a little to the
left.  Expect the fullscreen frame to remain unchanged.

To demonstrate,

 1. start, `emacs -Q'
 2. enlarge frame to fullscreen, `F11'
 3. call, `Restart CTWM' from window manager menu on X
 4. see the fullscreen frame bottom edge is shifted up 50 pixels approximately

 X. expect to see no change to fullscreen frame when ctwm restarts
    for comparison, a fullscreen xterm frame remains unchanged when ctwm restarts

=> http://sdf.org/~van.ly/img/emacs-fullscreen-frame-0.webp .
=> http://sdf.org/~van.ly/img/emacs-fullscreen-frame-1-shifts-up.webp .

=> http://mail-index.netbsd.org/netbsd-users/2024/11/23/msg031998.html discussion about shifted fullscreen frame behavior


[-- Attachment #2: gnu emacs bug diagnostics --]
[-- Type: application/octet-stream, Size: 4482 bytes --]

From: xxx@xxx.mail-host-address-is-not-set
To: bug-gnu-emacs@gnu.org
Subject: 30.0.91; x
X-Debbugs-Cc: 
--text follows this line--




In GNU Emacs 30.0.91 (build 2, x86_64--netbsd, X toolkit, cairo version
 1.18.0) of 2024-09-27 built on xxx
Windowing system distributor 'The X.Org Foundation', version 11.0.12101014
System Description: NetBSD xxx 10.0_STABLE NetBSD 10.0_STABLE (GENERIC) #1: Thu Nov  7 15:18:42 AEDT 2024  xxx@xxx:/u/o/n10/amd64/sys/arch/amd64/compile/GENERIC amd64

Configured using:
 'configure --srcdir=/u/xxx/src/emacs/30.0.91 --localstatedir=/var
 --disable-autodepend --with-native-compilation --without-ns --with-rsvg
 --without-imagemagick --without-xaw3d --without-toolkit-scroll-bars
 --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib
 --with-x-toolkit=lu --prefix=/usr/local --build=x86_64--netbsd
 --host=x86_64--netbsd --infodir=/usr/pkg/info --mandir=/usr/pkg/man
 --enable-option-checking=yes 'CFLAGS=-O2 -I/usr/pkg/include/cairo
 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2
 -I/usr/pkg/include/glib-2.0 -I/usr/pkg/include/gio-unix-2.0
 -I/usr/pkg/lib/glib-2.0/include -I/usr/X11R7/include
 -I/usr/pkg/include/harfbuzz -I/usr/X11R7/include/libdrm'
 'CPPFLAGS=-DTERMINFO -I/usr/pkg/include -I/usr/include
 -I/usr/pkg/include/freetype2 -I/usr/pkg/include/glib-2.0
 -I/usr/pkg/include/gio-unix-2.0 -I/usr/pkg/lib/glib-2.0/include
 -I/usr/X11R7/include -I/usr/pkg/include/harfbuzz
 -I/usr/X11R7/include/libdrm' 'LDFLAGS=-Wl,-R/usr/pkg/gcc13/lib
 -Wl,-zrelro -L/usr/pkg/lib -lcairo -L/usr/lib -Wl,-R/usr/lib
 -Wl,-R/usr/pkg/lib -L/usr/X11R7/lib -Wl,-R/usr/X11R7/lib
 -Wl,-R/usr/pkg/lib -L/usr/pkg/lib -lgnutls''

Configured features:
ACL CAIRO DBUS FREETYPE GIF GLIB GNUTLS GSETTINGS HARFBUZZ JPEG LCMS2
LIBOTF LIBXML2 MODULES NATIVE_COMP NOTIFY KQUEUE PDUMPER PNG RSVG SOUND
SQLITE3 THREADS TIFF TREE_SITTER WEBP X11 XDBE XIM XINPUT2 XPM LUCID
ZLIB

Important settings:
  value of $LC_COLLATE: en_AU.UTF-8
  value of $LC_CTYPE: en_AU.UTF-8
  value of $LC_MESSAGES: en_AU.UTF-8
  value of $LC_MONETARY: en_AU.UTF-8
  value of $LC_NUMERIC: en_AU.UTF-8
  value of $LC_TIME: en_AU.UTF-8
  value of $LANG: en_AU.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  global-eldoc-mode: t
  eldoc-mode: t
  show-paren-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  minibuffer-regexp-mode: t
  line-number-mode: t
  indent-tabs-mode: t
  transient-mark-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message mailcap yank-media puny dired
dired-loaddefs rfc822 mml mml-sec password-cache epa derived epg rfc6068
epg-config gnus-util text-property-search time-date subr-x mm-decode
mm-bodies mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader
cl-loaddefs cl-lib sendmail rfc2047 rfc2045 ietf-drums mm-util
mail-prsvr mail-utils rmc iso-transl tooltip cconv eldoc paren electric
uniquify ediff-hook vc-hooks lisp-float-type elisp-mode mwheel
term/x-win x-win term/common-win x-dnd touch-screen tool-bar dnd fontset
image regexp-opt fringe tabulated-list replace newcomment text-mode
lisp-mode prog-mode register page tab-bar menu-bar rfn-eshadow isearch
easymenu timer select scroll-bar mouse jit-lock font-lock syntax
font-core term/tty-colors frame minibuffer nadvice seq simple cl-generic
indonesian philippine cham georgian utf-8-lang misc-lang vietnamese
tibetan thai tai-viet lao korean japanese eucjp-ms cp51932 hebrew greek
romanian slovak czech european ethiopic indian cyrillic chinese
composite emoji-zwj charscript charprop case-table epa-hook
jka-cmpr-hook help abbrev obarray oclosure cl-preloaded button loaddefs
theme-loaddefs faces cus-face macroexp files window text-properties
overlay sha1 md5 base64 format env code-pages mule custom widget keymap
hashtable-print-readable backquote threads dbusbind kqueue lcms2
dynamic-setting system-font-setting font-render-setting cairo x-toolkit
xinput2 x multi-tty move-toolbar make-network-process native-compile
emacs)

Memory information:
((conses 16 49491 9439) (symbols 48 5360 0) (strings 32 14355 2416)
 (string-bytes 1 402093) (vectors 16 8999)
 (vector-slots 8 125392 10454) (floats 8 24 2) (intervals 56 330 0)
 (buffers 992 10))

[-- Attachment #3: Type: text/plain, Size: 9 bytes --]



-- 
vl

bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts

[Eli Zaretskii]

> Date: Sat, 23 Nov 2024 18:28:16 +0000
> From:  Van Ly via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> When the ctwm window manager is restarted, the emacs fullscreen frame,
> set with `F11' key, shifts up by approximately 50 pixels and shows the
> desktop background.  The right edge of the frame shifts a little to the
> left.  Expect the fullscreen frame to remain unchanged.
> 
> To demonstrate,
> 
>  1. start, `emacs -Q'
>  2. enlarge frame to fullscreen, `F11'
>  3. call, `Restart CTWM' from window manager menu on X
>  4. see the fullscreen frame bottom edge is shifted up 50 pixels approximately
> 
>  X. expect to see no change to fullscreen frame when ctwm restarts
>     for comparison, a fullscreen xterm frame remains unchanged when ctwm restarts
> 
> => http://sdf.org/~van.ly/img/emacs-fullscreen-frame-0.webp .
> => http://sdf.org/~van.ly/img/emacs-fullscreen-frame-1-shifts-up.webp .
> 
> => http://mail-index.netbsd.org/netbsd-users/2024/11/23/msg031998.html discussion about shifted fullscreen frame behavior

Martin, any suggestions?

bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts

[martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors]

 > Martin, any suggestions?

Maybe setting ‘frame-resize-pixelwise’ to t could help.  Some window
managers respect size hint increments even for fullscreen frames.

martin

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]

> Maybe setting ‘frame-resize-pixelwise’ to t could help.

Setting that variable to t had no change on persisting the fullscreen frame.

-- 
vl

bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts

[martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors]

 > Setting that variable to t had no change on persisting the fullscreen frame.

What does (frame-geometry) evaluate to before and after restarting CTWM?
What does (frame-parameter nil 'fullscreen) evaluate to before and after
restarting CTWM?  Does a maximized frame change too?

Thanks, martin

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]

>
> What does (frame-geometry) evaluate to before and after restarting CTWM?
> What does (frame-parameter nil 'fullscreen) evaluate to before and after
> restarting CTWM?  Does a maximized frame change too?
>

Having the ctwm maximized zoom frame lets both kinds of full frames
persist across ctwm restart.  Then, only having full frames be of the
F11 fullscreen type lets the fullscreen persist across ctwm restart.

The result on Line 27 below seems to be key.

Thanks.

   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 . 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))
   8
   9
  10  ;; A. F11 fullscreen before
  11  (frame-parameter nil 'fullscreen) ; => fullboth
  12
  13
  14  ;; Z. F11 fullscreen after
  15  (frame-parameter nil 'fullscreen) ; => nil
  16
  17
  18  ;; A. ctwm max zoom before
  19  (frame-geometry)
  20  ((outer-position 0 . 0) (outer-size 1914 . 1074) (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 1912 . 14) (tool-bar-external) (tool-bar-position . top) (tool-bar-size 0 . 0) (internal-border-width . 1))
  21
  22  ;; Z. ctwm max zoom after
  23  (frame-geometry)
  24  ((outer-position 0 . 0) (outer-size 1914 . 1074) (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 1912 . 14) (tool-bar-external) (tool-bar-position . top) (tool-bar-size 0 . 0) (internal-border-width . 1))
  25
  26  ;; A. ctwm max zoom before
=>27  (frame-parameter nil 'fullscreen) ; => maximized
  28
  29  ;; Z. ctwm max zoom after
  30  (frame-parameter nil 'fullscreen) ; => nil


-- 
vl

bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts

[martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors]

 >> What does (frame-geometry) evaluate to before and after restarting CTWM?
 >> What does (frame-parameter nil 'fullscreen) evaluate to before and after
 >> restarting CTWM?  Does a maximized frame change too?
 >>
 >
 > Having the ctwm maximized zoom frame lets both kinds of full frames
 > persist across ctwm restart.  Then, only having full frames be of the
 > F11 fullscreen type lets the fullscreen persist across ctwm restart.
 >
 > The result on Line 27 below seems to be key.

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.

martin

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]

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

bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts

[martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors]

 > An emacs session that never uses CTWM's `toggle zoom' to "maximize"

Could you please explain how that toggle works and how an emacs session
can use it?  IIUC without it you see the problem below.  With it you
don't see the problem.  Does it have any detrimental side-effects to set
that toggle?

 > 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))

But this is a difference of 8 pixels and nowhere near the 50 pixels you
mentioned earlier.

 >     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.

Not really IIUC.  The 'fullscreen' status is reset in either case.

martin

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]

martin rudalics <rudalics@gmx.at> writes:

>  > An emacs session that never uses CTWM's `toggle zoom' to "maximize"
>
> Could you please explain how that toggle works and how an emacs session
> can use it?  IIUC without it you see the problem below.  With it you
> don't see the problem.  Does it have any detrimental side-effects to set
> that toggle?
>

I use a CTWM keyboard shortcut that pops up a `Window' context menu over
the emacs frame.  Included is a section that lists

 Window
 - Zoom
 - Zoom-V
 - Zoom-H

Using `Window, Zoom' effects the `maximize' operation on the frame, the
frame border shows while the frame occupies all of the screen.  When
this maximized frame is in a CTWM virtual workspace and has as neighbors
that are F11 invoked fullscreen frames, CTWM restart does not cause the
shift at the bottom frame edge upwards by a few pixels.

>  >     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))
>
> But this is a difference of 8 pixels and nowhere near the 50 pixels you
> mentioned earlier.
>

The 50 pixels was my rough guess estimate.  The measured value is 8 pixels.

>  >     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.
>
> Not really IIUC.  The 'fullscreen' status is reset in either case.
>

In an emacs session, I arrange for 3 CTWM virtual workspaces to each
display an emacs frame fullscreen invoked by F11.  CTWM restart causes
the bottom edge to shift upwards by 8 pixels.  Undesired behavior.

In a new, quit and start again, emacs session, I arrange for 3 CTWM
virtual workspaces to display 2 emacs frames fullscreen invoked by F11
and 1 emacs frame `maximized' full screen with border edges showing.
CTWM restart does not change how the frames are displayed.  Desired behavior.

Using CTWM's `Window, zoom' that sees the following result lets the F11
fullscreen and `maximized' full screen with border edges persist across
CTWM restart.  Desired behavior.

    =>27  (frame-parameter nil 'fullscreen) ; => maximized

The puzzle is why having only F11 `fullboth' fullscreens will shift the
bottom edge up by 8 pixels on CTWM restart.

Hope that helps.

-- 
vl

bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts

[martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors]

 > The puzzle is why having only F11 `fullboth' fullscreens will shift the
 > bottom edge up by 8 pixels on CTWM restart.

So I see two problems we have to investigate:

- The fullscreen parameters are reset when restarting CWTM regardless of
   whether the frame was maximized or fullboth.  This means that when you
   do F11, restart CWTM and do F11 again the frame will become fullscreen
   again.  Right?

- The size of fullscreen frames shrinks by 8 pixels unless there is a
   maximized frame present.

IIUC you are using Lucid.  Now in xterm.c there are three instances of

store_frame_param (f, Qfullscreen, lval);

Can you put a breakpoint on each of them, ideally conditioned on lval
equaling Qnil, restart CWTM and post a backtrace of whatever happens.
I'd like to find out what kind of event makes us reset the parameter.

martin

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]

>
> - The fullscreen parameters are reset when restarting CWTM regardless of
>    whether the frame was maximized or fullboth.  This means that when you
>    do F11, restart CWTM and do F11 again the frame will become fullscreen
>    again.  Right?

Yes.

> - The size of fullscreen frames shrinks by 8 pixels unless there is a
>    maximized frame present.
>
> IIUC you are using Lucid.  Now in xterm.c there are three instances of

I use Lucid or Xaw, the bug diagnostics report will show it.

>
> store_frame_param (f, Qfullscreen, lval);
>
> Can you put a breakpoint on each of them, ideally conditioned on lval
> equaling Qnil, restart CWTM and post a backtrace of whatever happens.
> I'd like to find out what kind of event makes us reset the parameter.

I'll need to find and read documentation to figure out how that is to be
done.

Meanwhile, some more observations.  Inside xterm or uxterm the keychord
`fn RET' or `meta RET' will fullscreen and persist across CTWM restart.

Now unrelated to CTWM restart, the following is observed when zooming.

Using the `Window' context menu zoom from CTWM on xterm or uxterm
choosing any of the options `Zoom, Zoom-V, Zoom-H' leaves a 

 - gap at the right and bottom edge for `Zoom',
 - gap at bottom edge for `Zoom-V' and
 - gap at the right edge for `Zoom-H'.

The above suggests CTWM has issues calculating the height and width
dimensions for fullscreen on u/xterm.

Also, from a normal 80x24 u/xterm, when I `Window, Zoom' that results in
the gap at right and bottom edge, then when I keychord `meta RET' the
first time, I get the borderless fullscreen, keychord the second time
and u/xterm returns to a normal 80x24 dimension.

-- 
vl

bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts

[martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors]

 > Meanwhile, some more observations.  Inside xterm or uxterm the keychord
 > `fn RET' or `meta RET' will fullscreen and persist across CTWM restart.

What does `fn RET' do in an Emacs window?  Or in any other window but
the terminal windows you cite above?

 > Now unrelated to CTWM restart, the following is observed when zooming.

What is zooming?  Just maximizing the window or more?

 > Using the `Window' context menu zoom from CTWM on xterm or uxterm
 > choosing any of the options `Zoom, Zoom-V, Zoom-H' leaves a
 >
 >   - gap at the right and bottom edge for `Zoom',
 >   - gap at bottom edge for `Zoom-V' and
 >   - gap at the right edge for `Zoom-H'.
 >
 > The above suggests CTWM has issues calculating the height and width
 > dimensions for fullscreen on u/xterm.

Usually, terminal windows cannot be really maximized.  They want the
window height be a multiple of their font height + line spacing.

 > Also, from a normal 80x24 u/xterm, when I `Window, Zoom' that results in
 > the gap at right and bottom edge, then when I keychord `meta RET' the
 > first time, I get the borderless fullscreen, keychord the second time
 > and u/xterm returns to a normal 80x24 dimension.

I doubt that a fullscreen terminal can display half a line at the
bottom.  So your borderless fullscreen is likely an artefact.

martin

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]

martin rudalics <rudalics@gmx.at> writes:

>  > Meanwhile, some more observations.  Inside xterm or uxterm the keychord
>  > `fn RET' or `meta RET' will fullscreen and persist across CTWM restart.
>
> What does `fn RET' do in an Emacs window?  Or in any other window but
> the terminal windows you cite above?

`meta RET' will fullscreen the xterm.

`fn RET' will run overwrite-mode, I mislabelled the left hand keychord
which is also `meta RET'.

>  > Now unrelated to CTWM restart, the following is observed when zooming.
>
> What is zooming?  Just maximizing the window or more?

Yes, zooming maximizes fullboth, vertical or horizontal dimensions.

>  > Using the `Window' context menu zoom from CTWM on xterm or uxterm
>  > choosing any of the options `Zoom, Zoom-V, Zoom-H' leaves a
>  >
>  >   - gap at the right and bottom edge for `Zoom',
>  >   - gap at bottom edge for `Zoom-V' and
>  >   - gap at the right edge for `Zoom-H'.
>  >
>  > The above suggests CTWM has issues calculating the height and width
>  > dimensions for fullscreen on u/xterm.
>
> Usually, terminal windows cannot be really maximized.  They want the
> window height be a multiple of their font height + line spacing.
>
>  > Also, from a normal 80x24 u/xterm, when I `Window, Zoom' that results in
>  > the gap at right and bottom edge, then when I keychord `meta RET' the
>  > first time, I get the borderless fullscreen, keychord the second time
>  > and u/xterm returns to a normal 80x24 dimension.
>
> I doubt that a fullscreen terminal can display half a line at the
> bottom.  So your borderless fullscreen is likely an artefact.

This is how emacsclient looks inside a borderless fullscreen xterm.

    http://sdf.org/~van.ly/img/emacs-30-0-91-inside-fullscreen-xterm.webp

The minibuffer area looks stretched more than one line.

-- 
vl

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]

martin rudalics <rudalics@gmx.at> writes:

>  > The puzzle is why having only F11 `fullboth' fullscreens will shift the
>  > bottom edge up by 8 pixels on CTWM restart.
>
> So I see two problems we have to investigate:
>
> - The fullscreen parameters are reset when restarting CWTM regardless of
>    whether the frame was maximized or fullboth.  This means that when you
>    do F11, restart CWTM and do F11 again the frame will become fullscreen
>    again.  Right?

Yes.

> - The size of fullscreen frames shrinks by 8 pixels unless there is a
>    maximized frame present.

That was the case when I was evaluating those expressions.  But, now
fullboth and maximized frames will adjust up the bottom edge by 8
pixels.

> IIUC you are using Lucid.  Now in xterm.c there are three instances of
>
> store_frame_param (f, Qfullscreen, lval);
>
> Can you put a breakpoint on each of them, ideally conditioned on lval
> equaling Qnil, restart CWTM and post a backtrace of whatever happens.
> I'd like to find out what kind of event makes us reset the parameter.

I pieced together the following steps to make emacs debuggable.  I'll
need pointers to info pages to make progress.



  a.  make distclean
  b.  configure ... 'CFLAGS=-g3 -ggdb -Og ...'
  c.  make



  i.  start, emacs -Q
  ii. use, M-x gdb



   1  For help, type "help".
   2  Type "apropos word" to search for commands related to "word"...
   3  "0x7f7fff604da0s": not in executable format: file format not recognized
   4  No symbol table is loaded.  Use the "file" command.
   5  Breakpoint 1 (xterm.c:18044) pending.
   6  No symbol table is loaded.  Use the "file" command.
   7  Breakpoint 2 (xterm.c:28275) pending.
   8  No symbol table is loaded.  Use the "file" command.
   9  Breakpoint 3 (xterm.c:28343) pending.
  10  (gdb) run
  11  The target does not support running in non-stop mode.



-- 
vl

bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts

[Eli Zaretskii]

> From: Van Ly <van.ly@SDF.ORG>
> Cc: eliz@gnu.org, 74496@debbugs.gnu.org
> Date: Mon, 02 Dec 2024 15:47:35 +0000
> 
> I pieced together the following steps to make emacs debuggable.  I'll
> need pointers to info pages to make progress.
> 
> 
> 
>   a.  make distclean
>   b.  configure ... 'CFLAGS=-g3 -ggdb -Og ...'
>   c.  make
> 
> 
> 
>   i.  start, emacs -Q
>   ii. use, M-x gdb
> 

At this point, you should see a prompt in the minibuffer saysing
something like

 Run gdb (like this): gdb -i=mi SOMETHING

Edit the last part so it says /path/to/emacs instead of SOMETHING, and
then press RET.

>    1  For help, type "help".
>    2  Type "apropos word" to search for commands related to "word"...
>    3  "0x7f7fff604da0s": not in executable format: file format not recognized
>    4  No symbol table is loaded.  Use the "file" command.
>    5  Breakpoint 1 (xterm.c:18044) pending.
>    6  No symbol table is loaded.  Use the "file" command.
>    7  Breakpoint 2 (xterm.c:28275) pending.
>    8  No symbol table is loaded.  Use the "file" command.
>    9  Breakpoint 3 (xterm.c:28343) pending.
>   10  (gdb) run
>   11  The target does not support running in non-stop mode.

This is because you didn't give GDB the executable (emacs) to work on
and run.  If you do it like above, then "run" should start Emacs.