vim already recognizes many file types by default. Most of them work by file extensions, but in a case like this, vim will also analyze the content of the file to guess the correct type. vim sets the filetype for specific file names like .bashrc, .tcshrc, etc. automatically. But a file with a .sh extension … Read more
The cterm in ctermbg is short for “color terminal”. It is used to define the background color when Vim runs in a terminal emulator and can only accept named colors like grey or cyan or color numbers like 7. Hexadecimal values only work in GVim/MacVim and must be used with guibg/guifg like that: hi Folded … Read more
Let’s finally solve this issue once and for all! I mailed Charles E. Campbell, the maintainer of tex.vim, suggesting he’d add highlighting rules for the listings package. However it turns out lacking support for the listings package in tex.vim is actually intentional. The reasoning can be found :h tex-package. In short, you’re supposed to create … Read more
This may get you started. Is that more like what you’re looking for? Just had a quick search – it looks like there are a few different sorts of assembly syntax highlighting built in. Which one are you using? Copy-pasted from :help syntax Currently these syntax files are included: asm GNU assembly (the default) asm68k … Read more
What was missing from ~/.vimrc is a specification of where to find the plugin, i.e., Plugin ‘leafgarland/typescript-vim’ Highlighting works now.
You might like to try this improved Javascript syntax highlighter rather than the one that ships with VIMRUNTIME.
You need to have following settings in .vimrc file as per arch linux documentation filetype plugin on syntax on
UPDATE: Go 1.4 Release Notes Miscellany The standard repository’s top-level misc directory used to contain Go support for editors and IDEs: plugins, initialization scripts and so on. Maintaining these was becoming time-consuming and needed external help because many of the editors listed were not used by members of the core team. It also required us … Read more
I had this very same problem when I started using vim. The solution is simple, you just have to edit the c syntax file used by vim, here’s how to do it: When you start editing a C or C++ file, vim reads the default c syntax file located in $VIMRUNTIME/syntax/c.vim (Where $VIMRUNTIME is where … Read more
Are you correctly giving the shell script a .sh extension? Vim’s automatic syntax selection is almost completely based on file name (extension) detection. If a file doesn’t have a syntax set (or is the wrong syntax), Vim won’t automatically change to the correct syntax just because you started typing a script in a given language. … Read more