2012-01-23 07:42:11 +04:00
" 'set exrc' in ~/.vimrc will read .vimrc from the current directory
2015-11-23 21:31:00 +03:00
" Warning: Enabling exrc is dangerous! You can do nearly everything from a
" vimrc configuration file, including write operations and shell execution.
" You should consider setting 'set secure' as well, which is highly
" recommended!
2016-02-10 14:27:35 +03:00
2018-12-06 17:45:19 +03:00
" Note that we set a line width of 109 for .c and XML files, but for everything
2016-02-10 14:27:35 +03:00
" else (such as journal catalog files, unit files, README files) we stick to a
" more conservative 79 characters.
" NOTE: If you update this file make sure to update .dir-locals.el and
" .editorconfig, too.
2012-01-23 07:42:11 +04:00
set tabstop = 8
set shiftwidth = 8
set expandtab
2013-10-20 06:27:30 +04:00
set makeprg = GCC_COLORS = \ make
2016-02-10 14:27:35 +03:00
set tw = 79
2018-12-06 17:45:19 +03:00
au BufRead , BufNewFile *.xml set tw = 109 shiftwidth = 2 smarttab
scripts: use 4 space indentation
We had all kinds of indentation: 2 sp, 3 sp, 4 sp, 8 sp, and mixed.
4 sp was the most common, in particular the majority of scripts under test/
used that. Let's standarize on 4 sp, because many commandlines are long and
there's a lot of nesting, and with 8sp indentation less stuff fits. 4 sp
also seems to be the default indentation, so this will make it less likely
that people will mess up if they don't load the editor config. (I think people
often use vi, and vi has no support to load project-wide configuration
automatically. We distribute a .vimrc file, but it is not loaded by default,
and even the instructions in it seem to discourage its use for security
reasons.)
Also remove the few vim config lines that were left. We should either have them
on all files, or none.
Also remove some strange stuff like '#!/bin/env bash', yikes.
2019-04-04 15:10:42 +03:00
au FileType sh set tw = 80 shiftwidth = 4 smarttab
2018-12-06 17:45:19 +03:00
au FileType c set tw = 109