Re: suppressing "E319: * syntax off"

Thank you, Karthick; "if has" is a perfect fit and works flawlessly.

I had spent a good 15 min searching/reading documentation, but didn't find this. Certainly most of the problem lies between my ears, but vim is so well documented that the phrase "drinking from the firehose" comes to mind. :-) Sorry I can't provide more constructive feedback here. Regards...

 

On Thu, 5 Mar 2015 09:11:20 +0530, Karthick Gururaj <karthick.gururaj@gmail.com> wrote:

On Wed, Mar 4, 2015 at 11:38 PM, J.D. Laub <vim@laubster.org> wrote:

Hi.  I've got a standard .vimrc file I keep consistent across multiple machines with rsync.  I dislike syntax highlighting, so in that file I have " :syntax off " .  A problem I'm having is that some of the machines have the full-blown vim, where things work swell, but some of the machines have vim-tiny, and on those I get "E319: Sorry, the command is not available in this version: :syntax off" at start-up of vim.  I start vim many times a day, so this message gets old.

I'm looking for options on hushing the noise; after some thinking, these are the possibilities that come to mind (most of which probably don't exist):

    have vim recognize I'm trying to turn it off, which means I don't really care whether it's there or not, so there's no need for the E319
    put the "syntax off" in an rc file that applies only on full installs and not tiny installs

See :help has()

 

if has("syntax")

   syntax off

endif

 

    put this error msg in some "yes he's seen it before so don't show it again" filter file
    turn on some option to suppress all E319 errors

See :help silent

:silent! syntax off 

should be sufficient

    leave the default alone, but disable syntax highlighting some other way (maybe set up syntax files that effectively disables highlighting)
    eliminate the vimrc entry; instead, query vim at shell start-up, and only if syntax is a supported, then turn it off in my VIMRC environment var

The last I can do without too much hassle, but it feels like a work-around (putting the onus on the user & shell).  Other possibilities I'm missing?  Any other suggestions?

Cheers...

 

 

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.