From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] 80 columns ...
Date: Wed, 8 Nov 2017 16:18:16 -0500 (EST) [thread overview]
Message-ID: <alpine.BSF.2.02.1711081613201.44242@frieza.hoshinet.org> (raw)
In-Reply-To: <20171108210645.33E9F156E7D8@mail.bitblocks.com>
On Wed, 8 Nov 2017, Bakul Shah wrote:
> It is this spellingThingsOutInExcruciatingDetail that I find
> hard to read. Whether you use 80 columns or 800. Why not
> think a bit harder and come up with shorter name? Fix that
> and you don't need wide columns.
This is how I operate too - I use a lot of abbreviations (one particularly
hairy program I have has "havesnddrv", "iielc", "dblgrx" (have sound
driver, IIe language card, double resolution graphics respectively)).
Of course anyone familiar with the domain of what the program is doing
(it's an Apple ][ emulator) will probably understand the terminology.
-uso.
next prev parent reply other threads:[~2017-11-08 21:18 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 20:52 ron minnich
2017-11-08 21:02 ` Larry McVoy
2017-11-08 21:19 ` Dan Cross
2017-11-08 21:24 ` Larry McVoy
2017-11-08 21:28 ` Steve Nickolas
2017-11-08 21:48 ` [TUHS] (cassette) tape coming back [was " Charles H Sauer
2017-11-08 22:46 ` Don Hopkins
2017-11-08 23:28 ` [TUHS] " Dave Horsfall
2017-11-08 23:35 ` Ron Natalie
2017-11-08 23:39 ` Dave Horsfall
2017-11-08 21:34 ` Dan Cross
2017-11-08 21:40 ` Dan Cross
2017-11-08 21:40 ` Larry McVoy
2017-11-08 21:43 ` Dan Cross
2017-11-09 1:00 ` Theodore Ts'o
2017-11-08 23:46 ` Steffen Nurpmeso
2017-11-09 6:52 ` Otto Moerbeek
2017-11-08 21:06 ` Bakul Shah
2017-11-08 21:18 ` Steve Nickolas [this message]
2017-11-08 22:17 ` Grant Taylor
2017-11-08 22:30 ` Arthur Krewat
2017-11-08 23:07 ` Andy Kosela
2017-11-08 23:15 ` Arthur Krewat
2017-11-08 23:15 ` Warner Losh
2017-11-08 23:49 ` Arthur Krewat
2017-11-09 0:04 ` Dave Horsfall
2017-11-08 23:24 ` Andy Kosela
2017-11-09 7:24 ` Lars Brinkhoff
2017-11-09 15:02 ` Don Hopkins
2017-11-09 19:14 ` Ron Natalie
2017-11-10 16:18 ` Nemo
2017-11-10 19:05 ` Jon Steinhart
2017-11-10 20:36 ` Toby Thain
2017-11-10 20:39 ` Larry McVoy
2017-11-10 20:46 ` Warner Losh
2017-11-10 20:59 ` Larry McVoy
2017-11-11 9:24 ` David Arnold
2017-11-10 20:43 ` Jon Steinhart
2017-11-10 20:58 ` Larry McVoy
2017-11-10 21:02 ` Jon Steinhart
2017-11-10 21:09 ` Larry McVoy
2017-11-10 21:12 ` Jon Steinhart
2017-11-10 21:34 ` William Corcoran
2017-11-10 21:50 ` Jon Steinhart
2017-11-10 22:58 ` Dave Horsfall
2017-11-10 23:05 ` Jon Steinhart
2017-11-10 23:52 ` Toby Thain
2017-11-11 0:24 ` Larry McVoy
2017-11-11 16:40 ` Ian Zimmerman
2017-11-11 16:47 ` Larry McVoy
2017-11-11 17:23 ` Jon Steinhart
2017-11-11 17:38 ` Ralph Corderoy
2017-11-10 22:46 ` Toby Thain
2017-11-10 22:59 ` Jon Steinhart
2017-11-11 14:33 ` Andy Kosela
2017-11-11 17:19 ` Jon Steinhart
2017-11-11 17:24 ` Larry McVoy
2017-11-11 17:25 ` Jon Steinhart
2017-11-10 23:59 ` Don Hopkins
2017-11-10 22:10 ` Dave Horsfall
2017-11-09 20:46 ` Lars Brinkhoff
2017-11-10 17:21 Norman Wilson
2017-11-10 17:56 ` Larry McVoy
2017-11-11 17:04 ` Ian Zimmerman
2017-11-11 17:30 ` Random832
2017-11-11 18:05 ` Ian Zimmerman
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=alpine.BSF.2.02.1711081613201.44242@frieza.hoshinet.org \
--to=usotsuki@buric.co \
/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).