From: Adam Thornton <athornton@gmail.com>
To: chet.ramey@case.edu
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] sh: cmd | >file
Date: Mon, 6 Jan 2020 17:50:18 -0700 [thread overview]
Message-ID: <572C7C41-0B92-461C-88F9-5EC5436A66F5@gmail.com> (raw)
In-Reply-To: <bee504b9-75c9-1c03-e7f4-18d75b31d687@case.edu>
> On Jan 6, 2020, at 2:55 PM, Chet Ramey <chet.ramey@case.edu> wrote:
>
> On 1/6/20 4:29 PM, Dave Horsfall wrote:
>> On Mon, 6 Jan 2020, arnold@skeeve.com wrote:
>>> Would anyone who uses Bash regularly, both interactively and
>>> for scripting, really want to go back to using the V7 sh
>>> for production work?
>> I have never used all the fancy stuff in BASH such as the arithmetic
>> functions; I still use "expr" etc for portability.
>
> Portability to what? The POSIX $((...)) arithmetic expansion is widely
> implemented and near-universally available.
>
> Some of the other things are more esoteric, but you should be able to
> increase your expectation to POSIX features and still be sufficiently
> portable.
>
Portability to v7, of course!
I mean, I’m joking, but also not.
I felt like v7 might be enough of a daily driver that I could port some fun stuff to it, but…damn, even ex/vi 3.x is huge, jove will take a lot of work, and I can’t find a minimalist screen editor in K&R C. The best I’ve managed is TE but although there is presumably a Unix port, I couldn’t find it. Porting termcap and curses was easy, but….the whole reason I want them, initially, is so that I don’t have to use ed. If anyone knows of a small screen editor that will build easily on v7 I want to know about it.
This is in contrast to 2.11BSD, where, yeah, it’s just Unix, and especially with a TCP/IP stack, is completely usable. The PDP-11’s 64K address space is constraining and (as it turned out) influences the way I write programs—for my menu front end for ZIP, I started with my usual technique of making a struct with all the fields I’d want for my menu structure, and a linked list of those things, but that turned out to be a hog and a simple **char plus some utility functions to index the elements ended up being completely adequate.
Adam
next prev parent reply other threads:[~2020-01-07 0:50 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 2:58 Doug McIlroy
2020-01-04 10:07 ` markus schnalke
2020-01-04 11:47 ` Robert Clausecker
2020-01-04 22:31 ` Chet Ramey
2020-01-04 21:02 ` Dave Horsfall
2020-01-04 21:06 ` Jon Steinhart
2020-01-05 0:03 ` Eric Allman
2020-01-05 1:49 ` Adam Thornton
2020-01-05 2:44 ` Chet Ramey
2020-01-05 8:15 ` Brantley Coile
2020-01-05 15:16 ` Chet Ramey
2020-01-04 21:11 ` Dave Horsfall
2020-01-04 21:39 ` Warner Losh
2020-01-04 22:19 ` Terry Jones
2020-01-04 22:33 ` Chet Ramey
2020-01-04 23:53 ` Dave Horsfall
2020-01-05 0:04 ` Andreas Kusalananda Kähäri
2020-01-05 2:41 ` Chet Ramey
2020-01-05 13:45 ` Sven Mascheck via TUHS
2020-01-05 15:18 ` Chet Ramey
2020-01-05 21:21 ` Dave Horsfall
2020-01-06 13:53 ` Chet Ramey
2020-01-06 15:42 ` Brantley Coile
2020-01-06 15:46 ` arnold
2020-01-06 16:13 ` Clem Cole
2020-01-06 20:44 ` arnold
2020-01-06 20:51 ` Steve Nickolas
2020-01-06 21:32 ` Clem Cole
2020-01-06 21:39 ` Brad Spencer
2020-01-06 21:29 ` Dave Horsfall
2020-01-06 21:55 ` Chet Ramey
2020-01-06 22:22 ` Dave Horsfall
2020-01-06 22:52 ` Dan Cross
2020-01-07 0:50 ` Adam Thornton [this message]
2020-01-06 22:10 ` Bakul Shah
2020-01-04 22:44 ` markus schnalke
2020-01-04 23:01 ` Terry Jones
2020-01-04 22:22 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2020-01-07 5:03 Brian Walden
2020-01-07 4:49 Brian Walden
2020-01-06 19:47 Doug McIlroy
2020-01-06 16:11 Brian Walden
2020-01-06 16:33 ` Clem Cole
2020-01-06 3:24 Brian Walden
2020-01-06 15:42 ` Richard Salz
2020-01-06 15:45 ` Brantley Coile
2020-01-03 12:45 markus schnalke
2020-01-03 14:00 ` Steffen Nurpmeso
2020-01-03 17:03 ` Brian Zick
2020-01-03 17:18 ` markus schnalke
2020-01-04 0:53 ` Sven Mascheck via TUHS
2020-01-04 20:41 ` Steffen Nurpmeso
2020-01-03 19:38 ` markus schnalke
2020-01-03 19:44 ` Warner Losh
2020-01-03 22:49 ` Michael Parson
2020-01-03 23:32 ` Dave Horsfall
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=572C7C41-0B92-461C-88F9-5EC5436A66F5@gmail.com \
--to=athornton@gmail.com \
--cc=chet.ramey@case.edu \
--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).