Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Adam Thornton <>
To: Computer Old Farts Followers <>
Subject: Re: [COFF] [TUHS] ksh88 source code?
Date: Wed, 22 Dec 2021 07:51:34 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1.1: Type: text/plain, Size: 2239 bytes --]

MacOS finally pushed me to zsh.  So I went all the way and installed
oh-my-zsh.  It makes me feel very dirty, and I have a two-line prompt (!!),
but I can't deny it's convenient.

tickets/DM-32983 ✗

(and in my terminal, the X glyph next to my git branch showing the status
is dirty is red while the branch name is green)

and if something doesn't exit with rc=0...

adam@m1-wired:~/git/jenkins-dm-jobs$ fart
zsh: command not found: fart
tickets/DM-32983 ✗127 ⚠️

Then I also get the little warning glyph and the rc of the last command in
my prompt.

But then I'm also now using Fira Code with ligatures in my terminal, so
I've pretty much gone full Red Lightsaber.


On Wed, Dec 22, 2021 at 7:41 AM Norman Wilson <> wrote:

> 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
> Norman Wilson
> Toronto ON

[-- Attachment #1.2: Type: text/html, Size: 2919 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

COFF mailing list

       reply	other threads:[~2021-12-22 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-12-22 14:51 ` Adam Thornton [this message]
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <>
     [not found]       ` <>
     [not found]         ` <>
     [not found]           ` <>
     [not found]             ` <>
2021-12-23 16:14               ` John Cowan
2021-12-23 17:33                 ` Warner Losh
2021-12-23 17:44                   ` Larry McVoy
2021-12-23 18:18                     ` John Cowan
2021-12-24  3:46 Rudi Blom

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \
    --subject='Re: [COFF] [TUHS] ksh88 source code?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).