From: norman@oclsc.org (Norman Wilson)
To: tuhs@tuhs.org
Subject: Re: [TUHS] ksh88 source code?
Date: Wed, 22 Dec 2021 09:40:56 -0500 (EST) [thread overview]
Message-ID: <5D8BA976A496FD8E3AEFB6C9153250F0.for-standards-violators@oclsc.org> (raw)
Thomas Paulsen:
bash is clearly more advanced. ksh is retro computing.
====
Shell wars are, in the end, no more interesting than editor wars.
I use bash on Linux systems because it's the least-poorly
supported of the Bourne-family shells, besides which bash
is there by default. Ksh isn't.
I use ksh on OpenBSD systems because it's the least-poorly
supported of the Bourne-family shells, besides which kh
is there by default. Bash isn't.
I don't actually care for most of the extra crap in either
of those shells. I don't want my shell to do line editing
or auto-completion, and I find the csh-derived history
mechanisms more annoying than useful so I turn them off
too. To my mind, the Research 10/e sh had it about right,
including the simple way functions were exported and the
whatis built-in that told you whether something was a
variable or a shell function or an external executable,
and printed the first two in forms easily edited on the
screen and re-used.
Terminal programs that don't let you easily edit input
or output from the screen and re-send it, and programs
that abet them by spouting gratuitous ANSI control
sequences: now THAT's what I call retro-computing.
Probably further discussion of any of this belongs in
COFF.
Norman Wilson
Toronto ON
next reply other threads:[~2021-12-22 14:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 14:40 Norman Wilson [this message]
2021-12-23 17:23 ` John Cowan
2021-12-23 20:08 ` silas poulson
-- strict thread matches above, loose matches on Subject: below --
2021-12-23 19:10 Norman Wilson
2020-12-22 22:43 Warren Toomey
2020-12-22 23:01 ` Clem Cole
2020-12-23 1:29 ` John P. Linderman
2020-12-23 22:57 ` Warren Toomey
2020-12-23 3:30 ` Rico Pajarola
2020-12-23 9:03 ` Thomas Paulsen
2020-12-23 9:14 ` Rico Pajarola
2020-12-23 5:46 ` Scot Jenkins via TUHS
2020-12-23 7:19 ` Efton Collins
2021-12-21 13:55 ` Cyrille Lefevre via TUHS
2021-12-21 16:21 ` Larry McVoy
2021-12-21 16:27 ` Warner Losh
2021-12-21 17:15 ` Grant Taylor via TUHS
2021-12-21 17:31 ` Boyd Lynn Gerber
2021-12-21 19:09 ` Richard Salz
2021-12-22 6:23 ` jason-tuhs
2021-12-24 22:51 ` Grant Taylor via TUHS
2021-12-24 23:15 ` Richard Salz
2021-12-24 23:34 ` Michael Huff
2021-12-21 16:42 ` John Cowan
2021-12-21 16:47 ` Chet Ramey
2021-12-21 17:09 ` John Cowan
2021-12-22 11:11 ` Cyrille Lefevre via TUHS
2021-12-21 22:15 ` Thomas Paulsen
2021-12-22 7:44 ` arnold
2021-12-22 14:35 ` Cyrille Lefevre via TUHS
2021-12-22 14:36 ` Chet Ramey
2020-12-23 6:56 ` arnold
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=5D8BA976A496FD8E3AEFB6C9153250F0.for-standards-violators@oclsc.org \
--to=norman@oclsc.org \
--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).