How do I set Vim's syntax highlighting to treat a file extension as an HTML file?
I'm using ez template, so the file's extension is .ezt. But a lot of it is normal HTML code.
You can also put this into your .vimrc:
au BufReadPost *.ezt set syntax=html
.myspecialdotfile. It needs a star in it somewhere to work, even if it's theoretically not necessary..vimrc file for Dockerfiles that have extensions for different purposes. autocmd BufNewFile,BufRead Dockerfile* set filetype=docker Just using Dockerfile* prevents syntax highlighting from working when using vi Dockerfile - adding the backslash allows it to work for Dockerfile / Dockerfile.something and DockerfilesomethingTo make it automatic, add this line to your ~/.vimrc:
autocmd BufNewFile,BufRead *.ezt set filetype=html
If you want to just do it for the current file, then type:
:set filetype=html
You could also substitute syntax instead of filetype, but filetype affects more things than syntax (including syntax highlighting, indenting rules, and plugins), so generally you should use filetype unless you only want to affect syntax.
Take a look at this Vim wikia topic. Some useful tips:
As other answers have mentioned, you can use the vim set command to set syntax. :set syntax=<type> where <type> is something like perl, html, php, etc.
There is another mechanism that can be used to control syntax highlighting called filetype, or ft for short. Similar to syntax, you give it a type like this: :set filetype=html. Other filetypes are perl, php, etc.
Sometimes vim "forgets" what syntax to use, especially if you're mixing things like php and html together. Use the keyboard shortcut Ctrl+L (<C-L>) to get vim to refresh the highlighting.
In a .php file (or a html file), you could use a Vim Modeline to force certain commands or settings:
1 /* vim: syntax=javascript
2 *
3 * .submit_norefresh()
~
~
au ... settings in my ~/.vimrc get ignored for certain files (presumably due to modified metadata?). Other than copying that file content to a fresh file, setting a modeline at the top of that file works. E.g., for a BASH script, adding a second line, # vim: syntax=sh after the shebang (first line: #!/bin/bash) seems to work, reliably. Since it's basically a "comment", I just include both lines in my sbb ("shebang bash") snippet.# vim:ft=dosini or # vim:ft=sh as the first line works for me as well. Especially useful if it's a config file with no file extension.