diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2008-09-04 10:25:54 +0100 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2008-09-06 08:11:33 +0100 |
| commit | 0cadd4ab027c3196c8bfa3361f2507ceb62c7876 (patch) | |
| tree | 74a8f2e514c997f665f6b3200947595890b03d40 /CODING_STYLE | |
| parent | 22de0f6b8d3d680f29d781e1d71cf35a29cd26a9 (diff) | |
[CODING_STYLE] Add vim modeline
Add my vim recipe that most closely matches the coding style. If you can
improve it, please do so!
Diffstat (limited to 'CODING_STYLE')
| -rw-r--r-- | CODING_STYLE | 16 |
1 files changed, 15 insertions, 1 deletions
diff --git a/CODING_STYLE b/CODING_STYLE index 92536a44..95ceac04 100644 --- a/CODING_STYLE +++ b/CODING_STYLE @@ -269,9 +269,23 @@ In general, be wary of performing any arithmetic operations in an argument to malloc. You should explicitly check for integer overflow yourself in any more complex situations. +Mode lines +---------- + +So given the rules above, what is the best way to simplify one's life as +a code monkey? Get your editor to do most of the tedious work of +beautifying your code! + +As a reward for reading this far, here are some mode lines for the more +popular editors: +/* + * vim:sw=4:sts=4:ts=8:tw=78:fo=tcroq:cindent:cino=\:0,(0 + * vim:isk=a-z,A-Z,48-57,_,.,-,> + */ + TODO ---- Write rules for common editors to use this style. Also cleanup/unify -the modlines in the source files. +the modelines in the source files. |