public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Yury Gribov <tetra2005@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Vimrc config with GNU formatting
Date: Sat, 06 Sep 2014 19:35:00 -0000	[thread overview]
Message-ID: <20140906193507.GA31921@gate.crashing.org> (raw)
In-Reply-To: <loom.20140906T173551-992@post.gmane.org>

On Sat, Sep 06, 2014 at 03:38:31PM +0000, Yury Gribov wrote:
> Segher Boessenkool <segher <at> kernel.crashing.org> writes:
> > On Fri, Sep 05, 2014 at 07:10:02PM +0400, Yury Gribov wrote:
> > > Now I don't quite like the idea of plugin:
> > 
> > Anything that will make this enabled automatically will meet a lot of
> > resistance.  Make something nice for contrib/ instead?
> 
> Hm, isn't it already enabled by default for Emacs (in .dirs-local.el)?

That may well be.  But Vim is not Emacs.

> 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.  Because
I will bloody well type four spaces anyway.  Etc.  Not to mention the horrors
it will do in a machine description file.

This all should be opt-in.  As it already is.  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.


Segher

p.s.  At least you're not forcing syntax hilighting on ;-)

  parent reply	other threads:[~2014-09-06 19:35 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 13:06 Yury Gribov
2014-09-04 13:22 ` Richard Biener
2014-09-04 20:23   ` Bernhard Reutner-Fischer
2014-09-05 15:10     ` Yury Gribov
2014-09-05 16:46       ` Bernhard Reutner-Fischer
2014-09-06 16:33         ` Yury Gribov
2014-09-05 17:35       ` Segher Boessenkool
2014-09-06 15:40         ` Yury Gribov
2014-09-06 18:21           ` Trevor Saunders
2014-09-06 19:35           ` Segher Boessenkool [this message]
2014-09-07  4:18             ` Yuri Gribov
2014-09-07  4:48               ` Yuri Gribov
2014-09-07 13:33               ` Segher Boessenkool
2014-09-05 15:04   ` Yury Gribov
2014-09-10  8:09 ` [PATCHv2] " Yury Gribov
2014-09-10  8:17   ` Yury Gribov
2014-09-10 19:17   ` Segher Boessenkool
2014-09-11  4:47     ` Yury Gribov
2014-09-11  9:14       ` pinskia
2014-09-11  9:35         ` Yury Gribov
2014-09-11  9:06   ` Richard Biener
2014-09-11  9:18     ` Richard Biener
2014-09-11 10:10       ` Yury Gribov
2014-09-11 16:07         ` Yury Gribov
2014-09-14 10:32           ` Alexander Monakov
2014-09-15  9:54             ` Yury Gribov
2014-09-16 16:38   ` [PATCHv3] " Yury Gribov
2014-09-16 21:59     ` Trevor Saunders
2014-09-17 13:02       ` Segher Boessenkool
2014-09-17 14:05         ` Yury Gribov
2014-09-17 14:10           ` Yury Gribov
2014-09-17 17:08     ` [PATCHv4] " Yury Gribov
2014-09-18  3:54       ` Segher Boessenkool
2014-09-18  8:39         ` Yury Gribov
2014-09-18 15:37           ` Mike Stump
2014-09-18 17:20           ` Segher Boessenkool
2014-09-19  4:17             ` Yury Gribov
2014-09-19 11:11               ` Segher Boessenkool
2014-10-02 17:14       ` [PATCHv5] " Yury Gribov
2014-10-13 10:33         ` [PATCHv5][PING] " Yury Gribov
2014-10-21 15:24           ` [PATCHv5][PING^2] " Yury Gribov
2014-11-06 10:31             ` [PATCHv5][PING^3] " Yury Gribov
2014-11-28 18:00               ` [PATCHv5][PING^4] " Yury Gribov
2014-12-08 21:46                 ` Jeff Law

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140906193507.GA31921@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tetra2005@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).