You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As observed, for the first 6-7s, state 1 occurs; the window is set to its minimum dimensions. Afterwards, we see an instance of the intended state 3, followed by the flickering of state 2.
I have confirmed the issue is not present with other floating windows on sway, including other terminal emulators, though I have not tested on other compositors / window managers.
for_window [app_id="my_float"] floating enable, resize set 400 400
Note
It's not strictly necessary to set specific dimensions through sway. The behavior of "fighting" for dimensions is present nonetheless. It does make it easier to determine if sway is attempting to set window dimensions though. Hence setting to a square.
Open a new wezterm window with
wezterm start --class my_float fzf
Easier when bound to a key. Can test repeatedly and quickly. Same reason I was running fzf. Trivial to press <esc> to close and try again.
Configuration
return {}
Expected Behavior
wezterm should open as a floating window, and resize either to
the dimensions set by sway (if applicable), or
the dimensions specified by initial_cols / initial_rows.
Logs
No debug lines in all 3 of the cases described above.
Debug Overlay
wezterm version: 20240203-110809-5046fc22 x86_64-unknown-linux-gnu
Window Environment: Wayland
Lua Version: Lua 5.4
OpenGL: Mesa Intel(R) Graphics (MTL) 4.6 (Compatibility Profile) Mesa 24.2.7-arch1.1
Enter lua statements or expressions and hit Enter.
Press ESC or CTRL-D to exit
>
Anything else?
No response
The text was updated successfully, but these errors were encountered:
What Operating System(s) are you seeing this problem on?
Linux Wayland
Which Wayland compositor or X11 Window manager(s) are you using?
Sway
WezTerm version
20241205-083533-6f375e29
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
Spawning a new
wezterm
window, and setting an initial size viasway
configuration, results in flickering & inconsistent window dimensions.1 of 3 states will occur:
Screencast
https://github.com/user-attachments/assets/b62fb587-0a55-4c7d-b007-058aa95742a8
In this video, I have a key bound to...
...which I am repeatedly launching.
As observed, for the first 6-7s, state 1 occurs; the window is set to its minimum dimensions. Afterwards, we see an instance of the intended state 3, followed by the flickering of state 2.
I have confirmed the issue is not present with other floating windows on
sway
, including other terminal emulators, though I have not tested on other compositors / window managers.To Reproduce
Run
Wayland
, downloadsway
, use the default configuration, append this:Note
It's not strictly necessary to set specific dimensions through
sway
. The behavior of "fighting" for dimensions is present nonetheless. It does make it easier to determine if sway is attempting to set window dimensions though. Hence setting to a square.Open a new
wezterm
window withEasier when bound to a key. Can test repeatedly and quickly. Same reason I was running
fzf
. Trivial to press<esc>
to close and try again.Configuration
return {}
Expected Behavior
wezterm
should open as a floating window, and resize either tosway
(if applicable), orinitial_cols
/initial_rows
.Logs
No debug lines in all 3 of the cases described above.
Anything else?
No response
The text was updated successfully, but these errors were encountered: