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

[martin rudalics]

> 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