Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom DPI in config is ignored after first window resize #5453

Open
ashleysommer opened this issue May 22, 2024 · 2 comments
Open

Custom DPI in config is ignored after first window resize #5453

ashleysommer opened this issue May 22, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@ashleysommer
Copy link

ashleysommer commented May 22, 2024

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

Linux X11

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

KDE Plasma 6.0.2

WezTerm version

Nightly 20240520-135708-b8f94c47

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

I just switched from the old release 20240203-110809-5046fc22 to latest nightly 20240520-135708-b8f94c47 and I'm seeing this new behaviour.

When wezterm window opens, the scaling matches the custom config.dpi value I have in my wezterm.lua file.

But as soon as the window is resized, the DPI reverts back to an automatically-calculated version and ignores my custom set DPI value.

To Reproduce

Simply add config.dpi = 110 in wezterm.lua, launch wezterm and resize the window by dragging a corner.
See the DPI in the window immediately change.

Configuration

I have config.dpi = 110 in my wezterm.lua file.

I do this because I find the UI is too small with the auto-calculated DPI, so I like to set it manually.

Expected Behavior

In previous builds, rezising the window did not mess with the scaling, and did not ignore the config.dpi custom value in the config.

Logs

No response

Anything else?

This is loosely related to #4806
In #4806 @wez says that setting a DPI manually is not recommended, and to use font-size instead to make text more readable.
I suppose its the same for this issue. So should the config.dpi option be removed?

@ashleysommer ashleysommer added the bug Something isn't working label May 22, 2024
@ashleysommer
Copy link
Author

Note, clarifying the running environment. I'm suing Plasma 6.0.2 in Wayland mode, but wezterm is configured with config.enable_wayland = false so I guess its running in XWayland mode?

@sgon00
Copy link

sgon00 commented Jan 8, 2025

Dear @ashleysommer, I am having the same issue. I just installed wezterm and new to this terminal. I am running Xubuntu 24.04, XFCE4, X11 environment. I surprised that there is no comments after more than a half year. Do you have any workaround on this issue? I can NOT use wezterm with my 4k monitor. Thanks a lot.

Updated:

In order to use WezTerm, I had to switch to KDE (X11).

My original problem was that XFCE4's scaling setup only works with GTK apps, so I had to use config.dpi. However, due to this GitHub resize issue, I am unable to use config.dpi.

After switching to KDE (X11), things changed. Although the resize issue with config.dpi still exists in KDE (X11), WezTerm now honors KDE's system scaling setup, so I can use it on my 4K monitor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants