wez / wezterm

A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
https://wezfurlong.org/wezterm/
Other
16.77k stars 751 forks source link

Flicker on M1 Mac #4664

Open kentprimrose opened 9 months ago

kentprimrose commented 9 months ago

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

wezterm 20230712-072601-f4abf8fd

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

No, and I'll explain why below

Describe the bug

This seems to be the same issue as https://github.com/wez/wezterm/issues/965 (now closed). I am able to reproduce, editing an extremely large file and paging down. I then implemented the suggestion in 965 ("copying the dylibs from https://github.com/wez/wezterm/tree/main/assets/macos/WezTerm.app into the same directory as the wezterm-gui executable and then re-launching wezterm") and the issue WAS resolved.

To Reproduce

Paging a large file.

Configuration

local wt = require 'wezterm';

local my_scheme = wt.get_builtin_color_schemes()['Thayer Bright'] my_scheme.background = "080808" my_scheme.foreground = "ffffff"

local settings = { warn_about_missing_glyphs = false, initial_rows = 40, initial_cols = 100, hide_tab_bar_if_only_one_tab = true,

color_schemes = { ['mine'] = my_scheme, }, color_scheme = 'mine',

font = wt.font("FiraCode Nerd Font Mono"), font_size = 16.0, default_prog = { "/opt/homebrew/bin/tmux" }, }

return settings

Expected Behavior

No response

Logs

No response

Anything else?

Note that I am running TMux - but that the flicker DOES show before copying libraries and DOES NOT after. In the past I have verified that flicker persists WITHOUT TMux, and am happy to do that again if desired.

kentprimrose commented 8 months ago

Update: This issue has re-surfaced. I still have the approach recommended in https://github.com/wez/wezterm/issues/965 implemented ("copying the dylibs from https://github.com/wez/wezterm/tree/main/assets/macos/WezTerm.app into the same directory as the wezterm-gui executable and then re-launching wezterm"), but while this initially corrected the issue, it has recurred. I'm just noticing this today, so I'm not sure whether it was re-introduced by any recent updates to WezTerm.