All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Felix Domke <tmbinc@elitedvb.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Indention - why spaces?
Date: Mon, 30 Dec 2002 11:28:08 +0000	[thread overview]
Message-ID: <20021230112808.A26934@infradead.org> (raw)
In-Reply-To: <3E0FAF70.5040006@elitedvb.net>; from tmbinc@elitedvb.net on Mon, Dec 30, 2002 at 03:29:04AM +0100

On Mon, Dec 30, 2002 at 03:29:04AM +0100, Felix Domke wrote:
> Hi kernel hackers,
> 
> yes, i know http://www.purists.org/linux/#indent .
> 
> my question is just: what's the matter of NOT using tabs instead of 
> spaces? i think there must be one, otherwise everybody would use tabs.
> 
> I know the thing about "more than 3 levels of indention *suck*" (but i'm 
> not sure if i have really understand this yet in my coding style, but 
> who cares..), but i like tab characters more than spaces, simply because 
> it removes all the discussion about the best indention width. some 
> people use ~180 character-consoles, some use 80 ones.Whats the reason of 
> not giving the freedom to choose whatever he likes?
> 
> i don't want to change anything, i just like to know WHY people use 
> spaces. are they somehow unportable? (i don't think so)

spaces are a workaround for broken editors.  But Linux developers have a
"use the best tool for your job" approach so we don't care :)

As someone pointed to a paper by a mozilla hacker in this thread here's
another advice:  don't use mozilla to send non mime-encoded patches, they
even implemented their brain-dead tab expansion policy in their mailer.

*sigh*


  reply	other threads:[~2002-12-30 11:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-30  2:29 Indention - why spaces? Felix Domke
2002-12-30 11:28 ` Christoph Hellwig [this message]
2002-12-31  8:55   ` Tomas Szepe
     [not found] <fa.f9m4suv.e6ubgf@ifi.uio.no>
2002-12-30  3:33 ` Russ Allbery
2002-12-30  3:43   ` Larry McVoy
2002-12-30  3:47     ` john slee
2002-12-30  4:26     ` Russ Allbery
2002-12-30 23:20     ` Mark Mielke
2002-12-30 12:28   ` Wichert Akkerman
2002-12-30 12:49     ` John Bradford
2002-12-30 12:57       ` Wichert Akkerman
2002-12-30 13:12       ` Rik van Riel
2002-12-30 13:16       ` Russell King
2002-12-30 13:17       ` Dave Jones
2002-12-30 18:53         ` Emiliano Gabrielli
2002-12-30 19:00           ` Arnaldo Carvalho de Melo
2002-12-30 19:30             ` Herman Oosthuysen
2002-12-30  9:42               ` Zac Hansen
2002-12-30 20:43               ` Felix Domke
2002-12-30 23:26                 ` Mark Mielke
2002-12-31  1:02                   ` Wichert Akkerman
2002-12-30 23:55                 ` Herman Oosthuysen
2002-12-31  2:20               ` Anthony J. Breeds-Taurima
2002-12-31  9:47                 ` Christoph Hellwig
     [not found]         ` <mailman.1041274740.23755.linux-kernel2news@redhat.com>
2002-12-31  5:28           ` Pete Zaitcev
2002-12-31  6:04             ` Larry McVoy
2002-12-30 16:12     ` Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2002-12-31 17:21 Roberto Peon
2002-12-31 22:43 Heater, Daniel (IndSys, GEFanuc, VMIC)

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=20021230112808.A26934@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmbinc@elitedvb.net \
    /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.