22:14:02 andyf: hi, just noticed that vim and less (at least) are misbehaving after updating to latest bloody with TERM of xterm*, screen*; was there an ncurses update that could affect it? 22:15:34 not since Jan 4th when it went to 6.4 22:16:28 vim got an update though, so did tmux, 22:17:15 (I don't know what you ran before, but I just did `git diff --name-only '@{last week}'`) 22:20:16 I installed from the latest available ISO, 20230127, doing `man man` over ssh with TERM=xterm256-color seems to work fine; did `pkg update`, it's now omnios-r151047, doing `man man` with the same settings shows nothing (less misbehaves) 22:21:02 that's definitely not the case on omnios-master-e925d4a8679 22:21:13 which is a couple weeks old 22:21:27 assuming that TERM is actually correct for your terminal and whatnot 22:22:17 ; awk -F= '$1 == "BUILD_ID"' /etc/os-release 22:22:17 BUILD_ID=151047.0.2023.06.09 22:22:21 if that helps you pin it down more 22:24:40 BUILD_ID=151047.0.2023.06.30 22:26:16 it's some unstable bug, it seems to display fine if i run tmux and quit it 22:27:03 vim always seem to think term size is 80x25 22:28:57 how big does stty think it is? 22:29:13 rows = 29; columns = 120; 22:29:24 while vim is still broken? 22:29:27 that's weird 22:29:37 I don't have ideas :( 22:29:45 and I think andy is going to be very busy for at least a few more days. 22:29:56 yep, both in (screen-256color) and out of (xterm-256color) tmux 22:30:37 it could be windows terminal, but seems to be the same with iterm2 22:31:25 but if you are not seeing it, then it must be me somehow :) 22:31:58 or it broke between june 9th and 30th 22:32:36 if this image build works (it's 50/50) I can try it on something newer, otherwise it'll be a bit (until I can fix the image build) 22:44:53 yeah, it'll be a bit sorry, I botched this build. 22:46:48 no worries, i'm trying to understand what i did wrong :D and thank you 23:08:49 this reminds me of weird behavior in tmux that i was seeing quite some time ago where it would sometimes (often) get incorrect window size on startup (80x25?); less seems to have the same problem for me now (it would work 1 of 20 times it seems)