Where is vim syntax directory

Here are a couple of quick examples. With syntax highlighting turned on, a vim editor session can give you some nice syntax highlighting, as shown in this image:.

Conversely, if you want to turn syntax highlighting off in your current vim editor session, just issue this command:. When you turn vim syntax highlighting off, the same file in your vim editor will now look like this:. If you want syntax highlighting enabled by default when you open your vim editor, just add this command to your vimrc configuration file:. Just open the file as shown, then add the syntax on statement somewhere in the file.

These of course are guidelines. In this example, there are no statements or pre-processor commands, however celBlockCmd has been set to use Statement highlighting, and celHip will use Type highlighting. You can view more options in Vim with :help syntax. You may need to create the. You can see what directories to use by entering commands like the following in Vim:.

Using the directory specified above means the syntax file will be available to you, but not to other users. If you want the syntax file to be available to all users, do not save the file under your home directory; instead, copy the file under your Vim system directory. You can see the full path name of the required file by entering the following in Vim:. Another procedure to show the base directories which can be used is to enter either of the following commands in Vim the first displays the value of the 'runtimepath' option, and the second inserts that value into the current buffer :.

By default, the first item in runtimepath is the base directory for your personal Vim files, and the second item is the base directory for system-wide Vim files. Place the syntax subdirectory under either of these directories; doing that means your syntax file will not be overwritten when you next upgrade Vim.

Now we have to make sure Vim knows how to interpret your file. There are a few methods to add filetype detection for files of this new type. See :help new-filetype for full details, but the basics are here. In this file place a single line to set the filetype on buffer read or creation:.

Add filetype detection to filetype. This is so that Vim does not override any previously detected filetypes while running this script. Details :help :setfiletype. This method does not apply in our example case, but some filetypes can only be detected by examining buffer contents. Details at :help new-filetype-scripts.

Basically you just add tests using getline , search , etc. Add filetype detection to vimrc in this case the Vim script is named cel. I have removed the following advice for MacVim on Mac OS but will keep this for a while as an explanation :. While I have no knowledge of MacVim, I have found confirmation that the above is the directory containing Vim's syntax files i.

It is always a mistake to make changes in a distribution directory because updating Vim may and one day will cause your changes to be lost. Vim Tips Wiki Explore. Main Page All Pages Community. Community portal. To do. Explore Wikis Community Central. Register Don't have an account? Creating your own syntax files. Edit source History Talk 0. The runtimepath option contains a list of paths, separated by commas, where vim looks for plugins, syntax files, etc.

This folder is where you should put add-ons when you want them available to every user. This tells vim where to find and load add-ons which came bundled with that particular version of Vim. The other advantage of this setup is that you can always download the latest versions of the default bundled plugins without overriding any custom plugins you may have added.

You should be able to find that folder by executing. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 12 years, 2 months ago. Active 5 years ago. Viewed 47k times. Keith Pinson 7, 6 6 gold badges 55 55 silver badges 98 98 bronze badges.

Add a comment.