Sometime init windows size wrong

[Kurt-Shiwz]

What Operating System(s) are you seeing this problem on?

macOS

Which Wayland compositor or X11 Window manager(s) are you using?

No response

WezTerm version

20230712-072601-f4abf8fd

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

First, the focus of my mouse is on the internal screen of my Mac. Sometimes when I open wezterm, the window opens on the Dell monitor but the size of the window is incorrect. When I exit the wezterm. app and reopen it, it opens normally on the internal screen.

To Reproduce

No response

Configuration

confing:

    initial_rows = 40,
    initial_cols = 120,

Expected Behavior

No response

Logs

No response

Anything else?

No response

[wez]

Likely a duplicate of:

• Moving a WezTerm window between monitors causes erratic jumping and resizing of the window #1983
• dragging window between monitors on macos is glitchy/laggy #3396
• Font rendering on external monitor is not correct (macOS) #3575

[snobb]

I've done a simple workaround of this issue by adding the code below into the conifg:

wezterm.on('gui-startup', function()
    local tab, pane, window = wezterm.mux.spawn_window(cmd or {})
    window:gui_window():maximize()
end)

Unfortunately that does not solve the window size after unlocking the screen or moving the terminal window between the screens (Mac Retina and Acer, which is bigger but with smaller resolution).

[wez]

Please try the latest nightly build and let me know if this is still an issue!

[github-actions]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.