From: Yury Gribov <y.gribov@samsung.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Laurynas Biveinis <laurynas.biveinis@gmail.com>,
Jeff Law <law@redhat.com>
Subject: Re: Vimrc config with GNU formatting
Date: Fri, 05 Sep 2014 15:04:00 -0000 [thread overview]
Message-ID: <5409D0EA.2050709@samsung.com> (raw)
In-Reply-To: <CAFiYyc3j-enc0mtotgeMLC=n2ShgBLrLQtNLdXNp35_+1dVmzQ@mail.gmail.com>
On 09/04/2014 05:22 PM, Richard Biener wrote:
> For some reason I use
>
> set shiftwidth=4
> set tabstop=8
> set autoindent
> set cinoptions={.5s,g0,p5,t0,(0,^-0.5s,n-0.5s
>
> I note some differences to your
>
> + setlocal cinoptions=>4,n-2,{2,^-2,:2,=2,g0,h2,p5,t0,+2,(0,u0,w1,m1
Ah, the vimfu.
So the differences seem to boil down to
1) your config uses autoindent (mine does cindent)
2) my (well, Laurynas's) cinoptions additionally include
>4,:2,=2,h2,+2,u0,w1,m1
3) your config sets tabstop whereas mine uses softtabstop
4) formatoptions cause autowrapping of comments at 80-th column
I'm not sure about 1), but 2) allows:
* case labels start under parent {
* correct indent on line break (should be 2, not 4)
which seem to match current GCC style.
Also due to 3) issuing a tab expands to 2 spaces
instead of real tab which is probably a Good Thing.
Your settings beat mine at m1 though - it should be removed
to allow vim to match closing ) with opening.
So I'd say that in general proposed patch handles more cases (with
removed m1).
-Y
next prev parent reply other threads:[~2014-09-05 15:04 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
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 [this message]
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=5409D0EA.2050709@samsung.com \
--to=y.gribov@samsung.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=laurynas.biveinis@gmail.com \
--cc=law@redhat.com \
--cc=richard.guenther@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).