The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Greg A. Woods" <woods@robohack.ca>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] tabs vs spaces - entab, detab
Date: Fri, 05 Mar 2021 11:29:15 -0800	[thread overview]
Message-ID: <m1lIG8S-0036urC@more.local> (raw)
In-Reply-To: <CAKH6PiU58Fp=KQohX9M-qryQPsYd3aT=0YeT3YvBKiMowEdzyA@mail.gmail.com>

At Fri, 5 Mar 2021 11:44:49 -0500, M Douglas McIlroy <m.douglas.mcilroy@dartmouth.edu> wrote:
Subject: [TUHS] tabs vs spaces - entab, detab
> 
> > The reason to use tab was file size for one
> 
> This is urban legend. The percentage of 512-byte blocks that
> tabs would save was never significant.

Using tabs to save space was definitely more than an urban legend for
some of us!  (but there is a caveat below)

When I started at UofCalgary we had a PDP-11/60 running 7th Edition
(with about 16 terminals).  It had an RX-02 mounted into the terminal
room wall (the computer room was of course on the other side of the
wall, with a nice big window so we could see the blinken lights (which
are of course very few on an 11/60, but enough to tell when it was most
busy churning the disks).

Students were strongly encouraged to buy 8-1/2" disks at the books store
and off-load anything they were not directly working on at any given
time.  (And when we upgraded to a VAX 11/780 with BSD, disk quotas were
implemented as soon as possible.)

Some of us found that we could fit considerably more data on those disks
if we made sure we used tabs everywhere possible.  We also obviously
learned to have a "clean" target in our makefiles and to be sure to use
it before we archived anything!

However I think we were probably using tar, not a filesystem, on the
floppies so that would of course have been what allowed for greater
savings.  I don't remember many of the details, though I do remember
there was a program to reserve and "lock" the drive, and I think it
changed the ownership of the device file(s) to the user requesting the
reservation.

As for the size of tabs, well I seem to recall students also traded
tabstop setup files for various kinds of terminals so that each could
see code indentations at their own preferred size.  (Maybe this was done
more on the Multics system though, and/or it was in the pre-Vi days when
we used a custom full-screen editor called Fred.)

-- 
					Greg A. Woods <gwoods@acm.org>

Kelowna, BC     +1 250 762-7675           RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>     Avoncote Farms <woods@avoncote.ca>

  reply	other threads:[~2021-03-05 19:30 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 16:44 M Douglas McIlroy
2021-03-05 19:29 ` Greg A. Woods [this message]
2021-03-06 23:21   ` Steffen Nurpmeso
  -- strict thread matches above, loose matches on Subject: below --
2021-03-07  2:53 Nelson H. F. Beebe
2021-03-05 22:50 Norman Wilson
2021-03-04 16:52 Will Senn
2021-03-04 16:59 ` Clem Cole
2021-03-04 18:31   ` arnold
2021-03-04 19:23     ` Nemo Nusquam
2021-03-04 19:37       ` Steve Nickolas
2021-03-04 19:50         ` Rob Pike
2021-03-04 21:20           ` Robert Clausecker
2021-03-04 21:25           ` Will Senn
2021-03-05  9:58             ` John Gilmore
2021-03-06 21:31               ` Dave Horsfall
2021-03-06 21:38                 ` Larry McVoy
2021-03-06 22:05                   ` Clem Cole
2021-03-15  3:02                     ` John Cowan
2021-03-15 18:15                       ` Steffen Nurpmeso
2021-03-15 21:19                         ` Bakul Shah
2021-03-15 23:47                           ` Steffen Nurpmeso
2021-03-16  3:10                             ` Earl Baugh
2021-03-15 21:08                       ` Dave Horsfall
2021-03-15 21:12                         ` Steve Nickolas
2021-03-15 21:24                           ` Dave Horsfall
2021-03-15 22:06                             ` Adam Thornton
2021-03-16 13:25                             ` arnold
2021-03-17  5:10                       ` Greg 'groggy' Lehey
2021-03-06 21:40                 ` Steve Nickolas
2021-03-04 18:48   ` emanuel stiebler
2021-03-05  0:44     ` John Cowan
2021-03-05  0:55       ` Larry McVoy
2021-03-05  1:09         ` George Michaelson
2021-03-05  1:21           ` Larry McVoy
2021-03-05  1:29             ` Richard Salz
2021-03-04 18:33 ` John P. Linderman
2021-03-04 21:24 ` Greg 'groggy' Lehey
2021-03-04 21:27   ` Will Senn
2021-03-04 21:29     ` Greg 'groggy' Lehey
2021-03-04 21:42       ` Will Senn
2021-03-04 21:48       ` John P. Linderman
2021-03-04 22:08         ` Andy Kosela
2021-03-04 22:12           ` Greg 'groggy' Lehey
2021-03-05 14:13             ` Steffen Nurpmeso
2021-03-05 20:24               ` John Cowan
2021-03-05 21:51                 ` Bakul Shah
2021-03-06 23:43                 ` Steffen Nurpmeso
2021-03-05  0:15           ` Jon Steinhart
2021-03-06 21:22           ` Dave Horsfall
2021-03-06 23:58             ` Bakul Shah
2021-03-07  0:03               ` Jon Steinhart
2021-03-07  0:25               ` Steve Nickolas
2021-03-07  9:16               ` Brantley Coile
2021-03-04 22:10     ` Greg A. Woods
2021-03-05  1:41 ` alan
2021-03-05  1:55 ` alan
2021-03-05  2:06   ` Will Senn
2021-03-05 17:08     ` Clem Cole
2021-03-05 17:19       ` Richard Salz
2021-03-05 19:39         ` Lawrence Stewart
2021-03-05 19:51           ` Dan Halbert
2021-03-08  1:52       ` Will Senn
2021-03-05 16:43 ` Scot Jenkins via TUHS
2021-03-05 22:23   ` Bakul Shah
2021-03-06 20:51 ` Dave Horsfall
2021-03-06 21:01   ` Jon Steinhart
2021-03-06 21:19     ` Larry McVoy
2021-03-06 22:01       ` Clem Cole

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=m1lIG8S-0036urC@more.local \
    --to=woods@robohack.ca \
    --cc=tuhs@tuhs.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).