Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL So 19.05.2024 00:00:03 192.109 -3 8.728.541 45,4 Mastodon 4.3.0... 500 Sa 18.05.2024 00:00:03 192.112 -5 8.720.153 45,4 Mastodon 4.3.0... 500 Fr 17.05.2024 00:00:03 192.117 -1 8.710.099 45,3 Mastodon 4.3.0... 500 Do 16.05.2024 00:00:02 192.118 -1 8.707.027 45,3 Mastodon 4.3.0... 500 Mi 15.05.2024 00:00:02 192.119 -2 8.697.532 45,3 Mastodon 4.3.0... 500 Di 14.05.2024 00:00:03 192.121 -4 8.689.581 45,2 Mastodon 4.3.0... 500 Mo 13.05.2024 00:00:06 192.125 -4 8.681.677 45,2 Mastodon 4.3.0... 500 So 12.05.2024 00:00:03 192.129 0 8.674.347 45,1 Mastodon 4.3.0... 500 Sa 11.05.2024 00:00:03 192.129 -2 8.665.940 45,1 Mastodon 4.3.0... 500 Fr 10.05.2024 00:00:03 192.131 0 8.657.514 45,1 Mastodon 4.3.0... 500
Brian Ward (@brianward) · 04/2022 · Tröts: 529 · Folger: 236
So 19.05.2024 00:06
So I updated to the latest version of iTerm2 this morning and all of a sudden vim is ignoring the t_Co setting as specified in my .vimrc file. I have it set to 16 colors to enforce terminal colors only. After loading vim, if I run :set t_Co? it reports 256. If I run :set t_Co=16 in vim everything works again. If I run echo $TERM, it reports xterm-256color, which is the same value it was before I upgraded. Something has changed in iTerm2 to alter the way this works. Anybody have ideas?
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0 · via Web