All of lore.kernel.org
 help / color / mirror / Atom feed
From: DervishD <lkml@dervishd.net>
To: Benny Halevy <bhalevy@panasas.com>
Cc: James Courtier-Dutton <James@superbug.co.uk>,
	Xavier Bestel <xavier.bestel@free.fr>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Coding Style: indenting with tabs vs. spaces
Date: Mon, 12 Nov 2007 17:30:16 +0100	[thread overview]
Message-ID: <20071112163016.GC1073@DervishD> (raw)
In-Reply-To: <47380B14.3010604@panasas.com>

    Hi Benny :)

 * Benny Halevy <bhalevy@panasas.com> dixit:
> Using only spaces as DervishD suggested works around that using brute
> force by forcing the user to the author's preference which is
> legitimate but may not be the most productive way.

I admit it.

> I think that my proposal of using tabs as logical indents only (as Xav
> put it) and spaces for decorative alignment provides the best of both
> worlds.

Yes, you're right, and it is the only "mix" of tabs and spaces that
won't cause headaches. I still don't like tabs for indenting but that's
a matter of personal taste. Sometimes I use tabs for indenting when I
have to share code.

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
We are waiting for 13 Feb 2009 23:31:30 +0000 ...

  parent reply	other threads:[~2007-11-12 16:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 10:36 Coding Style: indenting with tabs vs. spaces Benny Halevy
2007-11-08 15:58 ` Chris Snook
2007-11-12  8:17   ` Benny Halevy
2007-11-10 12:04 ` DervishD
2007-11-10 12:27   ` Xavier Bestel
2007-11-10 16:50     ` DervishD
2007-11-11  9:23       ` James Courtier-Dutton
2007-11-12  8:13         ` Benny Halevy
2007-11-12 15:38           ` J. Bruce Fields
2007-11-12 16:30           ` DervishD [this message]
2007-11-11  8:57     ` Benny Halevy

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=20071112163016.GC1073@DervishD \
    --to=lkml@dervishd.net \
    --cc=James@superbug.co.uk \
    --cc=bhalevy@panasas.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.