Display bug on Alma Linux in TMUX 3.2a

[ConorMurphy21]

lnav version
v0.12.4 installed from lnav-0.12.4-linux-musl-x86_64.zip

Describe the bug
x's on either side of logs, some of the the x's on the left are also m's and l's

To Reproduce
For me just running lnav 0.12.4 on Alma Linux

I've also tried compiling from sources but since the switch to notcurses I think the configure step may be outdated. I had to get libunistring-devel and when I ran it crashed when I hit down arrow.

[tstack]

Looks like the altcharset is not working, hmm…. What TERM do you have set?

[tstack]

Thanks for the heads up about the crash. I managed to replicate a crash that seems to have been caused by a call to isprint() with a large value. I've pushed a change for that.

I haven't been able to replicate the display issue. But, I've just been testing with an Alma install using OrbStack on my mac. What terminal are you using?

[ConorMurphy21]

Oh nice, I assumed the crash was just due to some missing dependency or smthn, glad it helped.
Ok interesting, sorry I didn't test all of the cases. This only happens inside my tmux session. $TERM = tmux-256color inside my tmux session and xterm-256color outside my tmux session. I'm running the default gnome terminal on ubuntu and then sshing into an Alma linux server, but it seems like TMUX is the issue.

[ConorMurphy21]

I realized my tmux version is 3.2a so that may be why this issue is different from #1390

[ConorMurphy21]

Updated to https://github.com/tstack/lnav/actions/runs/13463172327, and still seeing this display bug on tmux 3.2a

[tstack]

Strange goings on... The smacs setting (used to switch to alt char set) for tmux-256color is ^N, which is different from xterm-256color where it's \E(0. Setting TERM to xterm-256color within tmux will get it displaying things correctly. Running an old lnav that uses ncurses works and then the new one works too...

[ConorMurphy21]

Setting TERM to xterm-256color within tmux will get it displaying things correctly.

I assume this was for debugging purposes and not an intended workaround? I don't know too much about the TERM variable but when I looked into doing this it seems like it is bad practice (I don't know if there are consequences lol)?

I guess I can just alias lnav to TERM=xterm-256color lnav for now so the scope is small.