Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Add CSS3 syntax support to vim's built-in `syntax/css.vim`.

branch: master
README.md

vim-css3-syntax

Add CSS3 syntax support to Vim's built-in syntax/css.vim.

INSTALLATION

I strongly recommend to install this plugin on Vim 7.4 or higher with default runtime files.

Manual Installation

Download from GitHub, extract vim-css3-syntax.tar.gz, and copy the contents to your ~/.vim directory.

Installing with Git and pathogen

$ cd ~/.vim/bundle
$ git clone https://github.com/hail2u/vim-css3-syntax.git

NOTES

Highlighting problems on: vertical-align, box-shadow, and others

Some properties do not highlight correctly by default. This is a limitation of Vim's highlight priority mechanism. To fix this problems, put following lines in your ~/.vim/after/css.vim:

setlocal iskeyword+=-

Or in your ~/.vimrc:

augroup VimCSS3Syntax
  autocmd!

  autocmd FileType css setlocal iskeyword+=-
augroup END

This setting have side effects, so use it at your own risk.

Vendor Prefixes

I do not plan to support CSS3 properties (or functions) with vendor prefixes, such as -webkit- or -moz-, etc. These are hard to maintain because they are:

  • Added frequently
  • Changed unexpectedly
  • Removed silently

These must be supported by separate syntax plugins (Vim 7.4's default CSS syntax file supports this). If you want to highlight prefixed properties or functions manually, :highlight and :match would help:

:highlight VendorPrefix guifg=#00ffff gui=bold
:match VendorPrefix /-\(moz\|webkit\|o\|ms\)-[a-zA-Z-]\+/

These commands highlight vendor prefixed properties and functions instantly with cyan and bold (on gVim).

CSS Preprocessors: Sass, LESS, and Stylus

vim-css3-syntax supports Sass's SCSS syntax only. If you want use this plugin with LESS, install VIM-LESS. Sass's indent synatx and Stylus are not supported.

AUTHOR

Kyo Namegashima kyo@hail2u.net

LICENSE

MIT: http://hail2u.mit-license.org/2011

Something went wrong with that request. Please try again.