From: Jiri Slaby <jirislaby@gmail.com>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Li Yang-r58472 <LeoLi@freescale.com>,
linux-kernel@vger.kernel.org
Subject: Re: Lindent and coding style
Date: Mon, 20 Mar 2006 17:20:15 +0059 [thread overview]
Message-ID: <441ED656.7050005@gmail.com> (raw)
In-Reply-To: <1142871150.22772.351.camel@capoeira>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Xavier Bestel napsal(a):
> On Mon, 2006-03-20 at 15:51, Jiri Slaby wrote:
>>> It should produce suitable output. Do you have examples of where it
>>> produces space indentation and you expect tabs ?
>> As far as I know, it produces:
>> <tab> if (very long condition &&
>> <tab> ssss2nd condition)...
>> where ssss are four spaces. Maybe this is considered as well formed at all, but
>> I indent 3 tabs in this case.
>
> Does that mean your tabs are 2-chars wide ? I think Linus stated that
> tabs should be 8-chars wide, that should be somewhere in the
> CodingStyle.
Nope, you maybe misunderstood me. Tab is 8 chars wide, but lindent do 4 spaces
on line after `if' if the condition continues on the next line. Then, I wrote I
do 2 tabs (16 chars) instead of 4-lindent spaces.
regards,
- --
Jiri Slaby www.fi.muni.cz/~xslaby
\_.-^-._ jirislaby@gmail.com _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFEHtZWMsxVwznUen4RAv5gAJ9Q14Us1CCO3k+FoNWWgfDNYRzY4gCgt7jg
HKphoxhtCeUYU/l2mNg4TIY=
=P1Gq
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-03-20 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 11:32 Lindent and coding style Li Yang-r58472
2006-03-20 14:36 ` Alan Cox
2006-03-20 14:51 ` Jiri Slaby
2006-03-20 16:12 ` Xavier Bestel
2006-03-20 16:21 ` Jiri Slaby [this message]
2006-03-20 16:28 ` Xavier Bestel
-- strict thread matches above, loose matches on Subject: below --
2006-03-21 2:55 Li Yang-r58472
2006-03-21 10:22 ` Alan Cox
2006-03-21 2:58 Li Yang-r58472
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=441ED656.7050005@gmail.com \
--to=jirislaby@gmail.com \
--cc=LeoLi@freescale.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=xavier.bestel@free.fr \
/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