On Tue, 26 Aug 2008 14:01:12 +0100 "Jan Minář" <[EMAIL PROTECTED]> wrote:
> Let me ask: What are the commands you (would) > put in that .vimrc? What are the problems you are trying to fix? I find it's usually stylistic issues. Quite often I'll be changing things like shiftwidth, expandtabs, some of the comment/formatting options. I did consider some stripped-down way of specifying just a few known-safe settings. But I'm not sure I like that as a solution. I'm a big fan of the /etc/default/ way of configuring system services, where the settings are the environment variables left by "source"ing a shell script. This gives full Turing-completeness to any settings. There was a time I ran a mixed Linux 2.4 / 2.6 setup, where sometimes I'd boot different kernels. I had a weird bug in a service that needed different config on each kernel. This made it trivial source /etc/default/fooservice.`uname -r` Similarly, I like to allow the possibility of arbitrary code in such .vimrc files. Perhaps my company's style guides require 4 space indents in code written on Tuesday, and 3 every other day? Silly I know; but if you can allow that sort of behaviour, then you should be able to account for any -sensible- one :) -- Paul "LeoNerd" Evans [EMAIL PROTECTED] ICQ# 4135350 | Registered Linux# 179460 http://www.leonerd.org.uk/
signature.asc
Description: PGP signature
