The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: John Cowan <cowan@ccil.org>
To: Norman Wilson <norman@oclsc.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] ksh88 source code?
Date: Thu, 23 Dec 2021 12:23:35 -0500	[thread overview]
Message-ID: <CAD2gp_R+9PdVgvg0=tjWqxcfyrfBTpTqbSRDmmS8e5fZNQN3fw@mail.gmail.com> (raw)
In-Reply-To: <5D8BA976A496FD8E3AEFB6C9153250F0.for-standards-violators@oclsc.org>

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

On Wed, Dec 22, 2021 at 9:41 AM Norman Wilson <norman@oclsc.org> wrote:


> Shell wars are, in the end, no more interesting than editor wars.
>

+1.  One person's "fully-featured software" is another person's "ten pounds
of crap in a five-pound bag".

> Bourne-family shells


All of which, considered as programming languages, are badly designed, in
the usual way of sofa beds and other allegedly dual-purpose pieces of
furniture.  Scsh is a shell that's a high-quality programming language
(namely Scheme), and I have just discovered xonsh, which is like scsh for
Python.  I have some ideas for a shell based on rc and Lua.

> To my mind, the Research 10/e sh had it about right,
>

Unfortunately, approximately nobody except you has access to its man page.
Can you post or email it?

[-- Attachment #2: Type: text/html, Size: 2157 bytes --]

  reply	other threads:[~2021-12-23 17:24 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22 14:40 Norman Wilson
2021-12-23 17:23 ` John Cowan [this message]
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='CAD2gp_R+9PdVgvg0=tjWqxcfyrfBTpTqbSRDmmS8e5fZNQN3fw@mail.gmail.com' \
    --to=cowan@ccil.org \
    --cc=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).