From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Ted Ts'o" <tytso@mit.edu>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Dimitrios Apostolou <jimis@gmx.net>,
linux-kernel@vger.kernel.org, Dan Nicolaescu <dann@gnu.org>
Subject: Re: emacs and "linux" coding style
Date: Sun, 18 Jul 2010 11:05:02 +0200 [thread overview]
Message-ID: <m3zkxpf9dt.fsf@intrepid.localdomain> (raw)
In-Reply-To: <20100718071552.GB4684@thunk.org> (Ted Ts'o's message of "Sun, 18 Jul 2010 03:15:52 -0400")
Ted Ts'o <tytso@mit.edu> writes:
> Actually, what my code use is tabs with a tab stop of 8 followed by
> enough spaces (< 7) to align function parameters and to align
> open/close parenthesis in C expression line wrap.
To be honest, I do precisely the same, though I think it's far from
perfect. It's just emacs which can't do better (or I don't know how to
make it do better).
> The main problem seems to be that Chapter 9 in
> Documentation/CodingStyle is written by someone who feels that since
> vi makes it easy to only align parameters using tabs, that everybody
> should do it the same way as vi. I'm simply challenging Chapter 9 as
> being canon. I certainly ignore it, and as a maintainer I tend to
> accept either vi or emacs-style indentations with respect to
> parameters and C expressions.
Fully agreed.
--
Krzysztof Halasa
next prev parent reply other threads:[~2010-07-18 9:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 14:00 Dimitrios Apostolou
2010-07-13 22:19 ` Randy Dunlap
2010-07-14 6:12 ` Theodore Tso
2010-07-15 11:46 ` Dimitrios Apostolou
2010-07-17 9:21 ` Krzysztof Halasa
2010-07-17 13:51 ` Randy Dunlap
2010-07-17 23:18 ` Krzysztof Halasa
2010-07-18 7:15 ` Ted Ts'o
2010-07-18 9:05 ` Krzysztof Halasa [this message]
2010-07-18 9:10 ` Dimitrios Apostolou
2010-07-18 9:21 ` Ted Ts'o
2010-07-18 21:53 ` Krzysztof Halasa
2010-07-18 9:37 ` Artem Bityutskiy
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=m3zkxpf9dt.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=dann@gnu.org \
--cc=jimis@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®