From: doug@cs.dartmouth.edu (Doug McIlroy)
Subject: [TUHS] TECO was: Re: basic tools / Universal Unix
Date: Thu, 16 Nov 2017 18:15:00 -0500 [thread overview]
Message-ID: <201711162315.vAGNF0r7003992@coolidge.cs.Dartmouth.EDU> (raw)
>Speaking of which, am I the only one annoyed by Penguin/OS' silly coloured
"ls" output?
Syntax coloring, of which IDE's seem to be enamored, always
looks to me like a ransom note. For folks who like colorized
text, Writers Workbench had a tool that can be harnessed to
do a bang-up job of syntax colorizing for English: "parts"
did a remarkable job of inferring parts of spechc in running
text.
Doug
next reply other threads:[~2017-11-16 23:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 23:15 Doug McIlroy [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-30 14:16 [TUHS] " Noel Chiappa
2017-10-30 20:56 ` Dave Horsfall
2017-10-31 10:50 ` Ronald Natalie
2017-11-01 3:23 ` Dave Horsfall
2017-11-15 1:25 ` Nemo
2017-11-15 2:10 ` Will Senn
2017-11-15 2:16 ` Larry McVoy
2017-11-15 2:37 ` Warner Losh
2017-11-15 3:07 ` Will Senn
2017-11-15 16:13 ` Arthur Krewat
2017-11-15 16:23 ` Arthur Krewat
2017-11-15 16:48 ` Clem Cole
2017-11-15 18:13 ` Bakul Shah
2017-11-15 19:01 ` Clem Cole
2017-11-15 19:52 ` [TUHS] TECO was: " Arthur Krewat
2017-11-15 20:19 ` Clem Cole
2017-11-15 20:25 ` Arthur Krewat
2017-11-15 22:18 ` Ralph Corderoy
2017-11-16 4:34 ` Dave Horsfall
2017-11-16 4:36 ` Jim Capp
2017-11-16 8:42 ` Pete Turnbull
2017-11-18 14:39 ` Ralph Corderoy
2017-11-16 9:19 ` arnold
2017-11-16 21:59 ` Dave Horsfall
2017-11-16 22:58 ` Andy Kosela
2017-11-17 2:17 ` Steve Johnson
2017-11-17 2:38 ` George Michaelson
2017-11-17 3:56 ` Ian Zimmerman
2017-11-17 4:07 ` Steve Nickolas
2017-11-17 8:44 ` Michael Kjörling
2017-11-17 3:50 ` Lyndon Nerenberg
2017-11-17 6:51 ` Andy Kosela
2017-11-17 1:18 ` Greg 'groggy' Lehey
2017-11-16 0:29 ` Grant Taylor
2017-11-16 0:35 ` Grant Taylor
2017-11-16 0:52 ` Warner Losh
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=201711162315.vAGNF0r7003992@coolidge.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.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).