This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Vimrc config with GNU formatting
- From: Yuri Gribov <tetra2005 at gmail dot com>
- To: Segher Boessenkool <segher at kernel dot crashing dot org>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Sun, 7 Sep 2014 08:18:39 +0400
- Subject: Re: Vimrc config with GNU formatting
- Authentication-results: sourceware.org; auth=none
- References: <540863C1 dot 4000909 at samsung dot com> <CAFiYyc3j-enc0mtotgeMLC=n2ShgBLrLQtNLdXNp35_+1dVmzQ at mail dot gmail dot com> <20140904202254 dot GA24681 at nbbrfq dot cc dot univie dot ac dot at> <5409D24A dot 2040805 at samsung dot com> <20140905173512 dot GA29810 at gate dot crashing dot org> <loom dot 20140906T173551-992 at post dot gmane dot org> <20140906193507 dot GA31921 at gate dot crashing dot org>
Replying to all this time.
On Sat, Sep 6, 2014 at 11:35 PM, Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>> Hm, isn't it already enabled by default for Emacs (in .dirs-local.el)?
>
> That may well be. But Vim is not Emacs.
Why is Vim special? As a developer I'd prefer the unified approach:
either nuke both or move them to contrib or make them default.
>> Also
>> GNU coding style is a requirement for GCC so resisting it may not make
>> sense...
>
> I'm not resisting GNU coding style. I am resisting scripts and/or other
> configuration things that make my editor do something else than what I tell
> it to do. If I type enter in insert mode, the cursor should go to column
> one in a newly opened line, not "helpfully" to e.g. four spaces in.
Two spaces in GNU standard.
> Because
> I will bloody well type four spaces anyway.
Well, good luck with a deeply nested constructs where GNU wants a
weird mix of tabs and spaces which developers get wrong every time
(unless they remember to run sed on their patches which they normally
don't).
> Etc. Not to mention the horrors
> it will do in a machine description file.
Indenting is only enabled for C, C++ and Java and .def. Md's and other
stuff is untouched (hmm, .md is interesting).
> This all should be opt-in. As it already is.
Not for other editors...
> If you can give some suggested
> config for other users, that's marvellous, it will probably be helpful to
> some. Changing the config for everyone is quite the opposite of helpful.
Let's see what other hackers say.
> p.s. At least you're not forcing syntax hilighting on ;-)
Noo, this is too personal.