Hi, all -- I'm running Leap 15.x on various computers davidtg@jpo:~> for H in jpo diskfarm gezebel ; do echo $H ; ssh $H " egrep '^(NAME|VERSION)' /etc/os-release " ; echo '' ; done jpo NAME="openSUSE Leap" VERSION="15.2" VERSION_ID="15.2" diskfarm NAME="openSUSE Leap" VERSION="15.2" VERSION_ID="15.2" gezebel NAME="openSUSE Leap" VERSION="15.1" VERSION_ID="15.1" (yes, I'm planning to update soon; see my recent update-and-migrate thread) and have finally gotten tired enough of stupid syntax highlighting, especially when vim complains No Syntax items defined for this buffer on startup, to dig into it. I find that the SuSE vimrc turns it on by default: davidtg@jpo:~> grep syn /usr/share/vim/vim80/*vimrc* /usr/share/vim/vim80/gvimrc_example.vim: " Switch on syntax highlighting if it wasn't on yet. /usr/share/vim/vim80/gvimrc_example.vim: if !exists("syntax_on") /usr/share/vim/vim80/gvimrc_example.vim: syntax on /usr/share/vim/vim80/suse.vimrc:" enable syntax highlighting /usr/share/vim/vim80/suse.vimrc: syntax on /usr/share/vim/vim80/vimrc_example.vim:if has('syntax') && has('eval') GAAAH! No wonder I'm seein' this thing all of the time ... Of course, I turn it off davidtg@jpo:~> cat .vimrc source $HOME/.exrc syntax=off in my own .vimrc file, but that doesn't seem to matter ... This concept has come up before for default aliases, too. I tried a few ways to permanently stomp on some /etc/profile.d/* files, but anything that promises to be permanent also breaks updates, so I'm stuck making the same changes again and again. I foresee the same thing with syntax settings *sigh* So what's the best way to step on a setting or file that is placed by default but should be able to be overridden -- just once, and thus forevermore -- by the admin? TIA & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt