From: adam8157@gmail.com (Adam Lee)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Query on CodingStyle: indentation
Date: Fri, 19 Oct 2012 15:03:28 +0800 [thread overview]
Message-ID: <20121019070328.GA6410@adam-laptop> (raw)
In-Reply-To: <20121019053129.GA2712@gmail.com>
On Thu, Oct 18, 2012 at 10:31:29PM -0700, Kumar amit mehta wrote:
> Hi,
>
> I've a query regarding the coding style for Linux Kernel code. I'm
> reading the CodingStyle under Documentation and what I've understood is
> that I shouldn't be using spaces for indentation purposes and should use
> tabs of width 8 characters. Quoting from the same document:
> "Outside of comments, documentation and except in Kconfig, spaces are
> never used for indentation, and the above example is deliberately broken."
> However, Is it correct to replace each tab stroke by 8 spaces ? I use vim
> editor and I've put following under $HOME/.vimrc file:
> <snip>
> set tabstop=8
> set shiftwidth=8
> set expandtab
> <snip>
>
> In past I've seen that some application have different interpretation of
> tabs and hence sometimes even If I've done proper indentation using tab,
> the code appears unindented, and therefore In order to make sure that I'm
> moving 8 characters upon hitting tab, I've put the above rules under my
> .vimrc file. Please let me know If I should remove these from my .vimrc
> file and rely on tab instead.
No, you should not expand tabs. Tabs in CodingStyle mean _hard_ tabs.
Mine:
<snip>
set tabstop=8
set noexpandtab
set shiftwidth=8
set cinoptions=:0,l1,t0,g0
<snip>
--
Regards,
Adam Lee
http://adam8157.info
next prev parent reply other threads:[~2012-10-19 7:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 5:31 Query on CodingStyle: indentation Kumar amit mehta
2012-10-19 7:03 ` Adam Lee [this message]
2012-10-19 9:00 ` Kumar amit mehta
2012-10-19 15:40 ` Greg Freemyer
2012-10-22 4:36 ` Kumar amit mehta
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=20121019070328.GA6410@adam-laptop \
--to=adam8157@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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 NNTP newsgroup(s).