9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Gordon Hogan <dhog@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Sam question
Date: Fri, 17 Aug 2001 12:32:11 -0400	[thread overview]
Message-ID: <20010817163211.D4650199E9@mail.cse.psu.edu> (raw)

> I carry around a utility I originally developed at Geotronics
> (early 1980s) called "retab" that transforms from one set of
> tabs stops to another in one pass; it can turn all tabs to an
> appropriate number of spaces by specifying -o +1.  The manual
> page could be improved, but here it is:

I am SO sick of C programs that are indented using spaces,
eg the GNU code which seems to have standardized on 2
space indent.  In the variable width font that I use, 2 spaces
is not a lot of indent, and the code is totally unreadable (as
opposed to being mostly unreadable, as it would be if it were
at least formatted correctly).

Real programmers indent with tabs.

Maybe the C preprocessor should reject any line that
starts with a space :-)



             reply	other threads:[~2001-08-17 16:32 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17 16:32 David Gordon Hogan [this message]
2001-08-17 16:55 ` Lucio De Re
2001-08-17 17:08   ` Boyd Roberts
2001-08-17 17:28   ` Louis Beleos
2001-08-17 17:45     ` Lucio De Re
2001-08-17 17:04 ` Boyd Roberts
2001-08-17 17:04 ` Steve Kilbane
2001-08-18  1:36   ` Boyd Roberts
2001-08-19  6:31     ` Lucio De Re
  -- strict thread matches above, loose matches on Subject: below --
2008-07-17 22:56 [9fans] sam question Skip Tavakkolian
2008-07-18  0:28 ` erik quanstrom
2008-07-18  0:45   ` Pietro Gagliardi
2008-07-18 10:01     ` roger peppe
2008-07-18 13:22       ` Russ Cox
2001-08-20 12:06 [9fans] Sam question bwc
2001-08-19 18:06 rob pike
2001-08-19 15:05 bwc
2001-08-19 15:59 ` Boyd Roberts
2001-08-19 12:44 rob pike
2001-08-18  7:38 nigel
2001-08-18  8:31 ` Steve Kilbane
2001-08-20  8:57   ` Luis Fernandes
2001-08-20 11:10     ` Boyd Roberts
2001-08-18 11:06 ` Boyd Roberts
2001-08-19  6:57 ` Lucio De Re
2001-08-19 10:54   ` Boyd Roberts
2001-08-19 11:13     ` Lucio De Re
2001-08-19 12:02       ` Boyd Roberts
2001-08-19 12:23         ` Lucio De Re
2001-08-19 16:17           ` Steve Kilbane
2001-08-19 20:57 ` Dan Cross
2001-08-17 22:35 David Gordon Hogan
2001-08-18  4:47 ` Rick Hohensee
2001-08-19  6:29 ` Lucio De Re
2001-08-17 22:22 geoff
2001-08-17 17:00 rob pike
2001-08-17 14:22 rob pike
2001-08-17 14:15 rob pike
2001-08-17 16:58 ` Boyd Roberts
2001-08-20  8:56 ` Douglas A. Gwyn
2001-08-14 12:41 rob pike
2001-08-08 10:45 [9fans] ls -R rog
2001-08-08 17:08 ` [9fans] Sam question gene garbutt
2001-08-14  9:44   ` Douglas A. Gwyn
2001-08-16 21:07     ` Boyd Roberts
2001-08-17  8:50       ` Douglas A. Gwyn
2001-08-17 12:14         ` Boyd Roberts
2001-08-20  8:56           ` Douglas A. Gwyn
2001-08-20 11:11             ` Boyd Roberts
2001-08-20 16:25             ` Sam Ducksworth
2001-08-20 15:11               ` Boyd Roberts
2001-08-21  8:37                 ` Ozan Yigit
2001-08-21  9:31                   ` Boyd Roberts
2001-08-22  2:52                     ` Donald Brownlee

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=20010817163211.D4650199E9@mail.cse.psu.edu \
    --to=dhog@plan9.bell-labs.com \
    --cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).