3

How to change Vim behaviour using single .vimrc file (without ftplugin) in elegant way ?

What do I mean is ... if I run many commends for C/C++ file , e.g.:

set nu
set cin
set ai
set mouse=a
color elflord

and another bunch of commends for AsciiDoc files, e.g.:

set syntax=asciidoc
set nocin
set spell spl=en

Not mentioning about Python, LaTeX etc....

There is solution presented https://stackoverflow.com/a/159065/544721 for putting autocommand before every custom command.

Is there a nice way to group them for autocommand without using ftplugin - in order to keep everything in single .vimrc file (better for moving around many machines, etc.) ? Something equivalent to if statement with brackets {} ?

Community
  • 1
  • 1
Grzegorz Wierzowiecki
  • 10,545
  • 9
  • 50
  • 88
  • See: http://stackoverflow.com/questions/2889766/best-way-to-organize-filetype-settings-in-vim-and-vimrc – pb2q Aug 02 '12 at 20:41

2 Answers2

3

You can use the following:

if has("autocmd")
    augroup LISP
        au!
        au BufReadPost *.cl :set lisp
        au BufReadPost *.cl :set showmatch
        au BufReadPost *.cl :set cpoptions-=m
        au BufReadPost *.cl :set autoindent
    augroup END
    augroup C
        au!
        autocmd BufNewFile,BufRead *.cpp set formatprg=c:\\AStyle\\bin\\AStyle.exe\ -A4Sm0pHUk3s4
        autocmd BufNewFile,BufRead *.c set formatprg=c:\\AStyle\\bin\\AStyle.exe\ -A4Sm0pHUk3s4
        autocmd BufNewFile,BufRead *.h set formatprg=c:\\AStyle\\bin\\AStyle.exe\ -A4Sm0pHUk3s4
        autocmd BufNewFile,BufRead *.cpp set tw=80
        autocmd BufNewFile,BufRead *.c set tw=80
        autocmd BufNewFile,BufRead *.h set tw=80
    augroup END
endif

This created grouping of commands depending on the type of file that is opened, which is specified in the autocmd section. You still need to specify autocmd or au before each one, but they are nicely grouped.

Derek
  • 3,087
  • 1
  • 21
  • 23
3

I'd probably do per-filetype functions to do the setup for me. Shamelessly ripping off @Derek...

function! SetUpLispBuffer()
    set lisp
    set showmatch
    set cpoptions-=m
    set autoindent
endfunction

function! SetUpCBuffer()
    set formatprg=c:\\AStyle\\bin\\AStyle.exe\ -A4Sm0pHUk3s4
    set tw=80
endfunction

if has("autocmd")
    augroup LISP
        au!
        au BufReadPost *.cl call SetUpLispBuffer()
    augroup END
    augroup C
        au!
        autocmd BufNewFile,BufRead *.{cpp,c,h} call SetUpCBuffer
    augroup END
endif

A lot less to change when you want to make changes and much less cut&paste too.

dash-tom-bang
  • 17,383
  • 5
  • 46
  • 62
  • I'm a bit newb... I seem to read "au!" removes autocommands for this filetype group. Why do we do this? Could this interfere with other vim plugins? Thanks :) – aikeru Sep 10 '14 at 13:42
  • 1
    `au!` removes autocommands in the containing augroup, so just name them something that you think won't conflict with plugins. (E.g. my augroups are often named things like TomsFileCleanups etc.) – dash-tom-bang Sep 24 '14 at 00:37