On Sun, Jan 01, 2023 at 05:53:22PM -0500, Thomas Dickey wrote: > On Sun, Jan 01, 2023 at 08:02:31PM +0000, Chris Green wrote: > > On Sun, Jan 01, 2023 at 06:13:07PM +0000, Chris Green wrote: > > > The eternal problem.... > > > > > > On just *some* of my several Linux systems colour syntax higlighting > > > isn't working. It always used to work but I really can't see what I > > > might have changed on *some* systems to break it. > > > > > > The systems and versions and 'working or not' are:- > > > > > > backup xubuntu 22.10 vile 9.8w colour OK > > > bison Android 11 vile 9.8w colour OK > > > caracal Debian 10 vile 9.8 no colour syntax > > > cheddar Debian 10 vile 9.8t colour OK > > > esprimo xubuntu 22.04 vile 9.8u no colour syntax > > > isbd Ubuntu 20.04 vile 9.8t colour OK > > > odin Debian 9 vile 9.8s colour OK > > > pimedia Debian 11 vile 9.8u colour OK > > > t470 xubuntu 22.10 vile 9.8w colour OK > > > tsohost very old vile 9.8 no colour syntax > > > > > > Since esprimo is my main desktop system it's a bit annoying that > > > syntax colouring isn't working there. > > > > > > On all systems 'show-colors' in vile works fine, so they're all > > > *capable* of colour. The two systems showing just vile 9.8 are ones > > > where I have built vile myself, so they have pretty recent code. > > > > > > All systems have the same .vilerc and it runs with no errors. So they > > > all execute:- > > > > > > source filters.rc > > > setv $autocolor-hook HighlightFilter > > > setv $read-hook HighlightFilter > > > set autocolor=500 > > > set bcolor=default > > > > > > I'm stumped! Can anyone point me at some way to diagnose what's > > > wrong? Could it (possibly) be something to do with built-in or > > > external filters? If so, how do I tell whether vile was built with > > > 'built-in' or not? > > > > > Just to add to the fun if I run xvile remotely across an 'ssh -Y' > > connection to esprimo the syntax highlighting works OK. (that's > > running xvile on esprimo from t470) > > > > This suggests to me that it's something to do with how vile was built > > (it's the version from the repositories). > > vile's running in a terminal. I'd check if the terminal is configured for > color: disregarding hard-coded stuff, the value of $TERM is used to select > a terminal description. If it's "vt100" on some machines, that would explain. > > Running this from the command-line will show colors only if the terminal is > configured: > > #!/bin/sh > tput blink > tput bold > tput setab 1 > tput setaf 4 > printf "Hello-" > tput setaf 1 > tput setab 4 > echo "world" > tput sgr0 > read aa > Above script outputs blinking text on coloured background so I think my terminal setting is OK.
I'm beginning to suspect that it's how vile is built that's affecting my syntax highlighting. I'm not only seeing no syntax highlighting on some systems but I'm also seeing two different versions of syntax highlighting in vilemode. In fact vilemode seems to confuse the syntax highlighting somewhat, shmode and and pymode seem to be fine in all cases (when syntax highlighting is working that is). -- Chris Green
