[ 2803s]   = note: /usr/lib64/gcc/x86_64-suse-linux/12/../../../../x86_64-suse-linux/bin/ld: final link failed: No space left on device
[ 2803s]           collect2: error: ld returned 1 exit status

Seems like a _constraints might be needed

In wezterm.spec:

%build
# export CFLAGS="%%optflags"
# export CXXFLAGS="%%optflags"
%if 0%{?suse_version} > 1500
%{cargo_build} --all-features
%else
export CARGO_FEATURE_VENDORED=1
export RUSTFLAGS='%{rustflags}'
cargo build --offline --release --all-features
%endif

Building with --all-features enables dhat-heap/dhat-ad-hoc, which may cause slowdown and not suitable for production use: https://github.com/wez/wezterm/blob/ede7e846f483d189d26c62c674fd391bb63ce3d7/wezterm-gui/Cargo.toml#L25

Soc Virnyl Estela (uncomfyhalomacro) - 9 months ago

maintainer

thanks for pointing that out. i will update this soon

Soc Virnyl Estela (uncomfyhalomacro) - 9 months ago

maintainer

FIXED!

Disabled AutoSubmit. I will wait for unpinned openSSL crate release

I notice wezterm-terminfo was removed in flavor of the one provided by ncurses since r108, but it seems causes glitches for neovim.

The wezterm terminfo from terminfo-6.4.20240224-32.1 inherits xterm-256color, and falsely reports smg*, which wezterm does not support, as seen in their offical terminfo. Neovim uses smg* to optimize scrolling, only when the terminfo indicates the revelant capabilities. This optimization is now falsely enabled with ncurses-provided wezterm terminfo.

infocmp -A /usr/share/terminfo/ wezterm | grep smg
# smg* are reported, but should not

TERM=wezterm nvim /a/long/file +vs
# move the cursor to the right window and press J,
# rendering will be broken when scrolling

TERM=xterm-256color does not have this issue because the neovim guys aware people set this no matter what terminal emulator they are using, and have a workaround for this.