* [TUHS] Re: shells, Re: Listing of early Unix source code from the Computer History Museum.
[not found] <20250525194505.B4D2618C075@mercury.lcs.mit.edu>
@ 2025-05-26 0:15 ` John Levine
0 siblings, 0 replies; 2+ messages in thread
From: John Levine @ 2025-05-26 0:15 UTC (permalink / raw)
To: tuhs; +Cc: jnc
It appears that Noel Chiappa <jnc@mercury.lcs.mit.edu> said:
>but by V5 it had been re-written in C:
>
> https://minnie.tuhs.org/cgi-bin/utree.pl?file=V5/usr/source/s2/sh.c
I had heard that called the Mashey shell, also according to Wikipedia the PWB shell.
That shell had no flow control but it read its input one character at a time and there
was a "goto" program that rewound the input and scanned forward for a label in a comment. Primitive
but sort of usable.
One of the early usenix tapes has some patches I wrote to add primitive single character shell variables.
R's,
John
^ permalink raw reply [flat|nested] 2+ messages in thread
* [TUHS] Re: shells, Re: Listing of early Unix source code from the Computer History Museum.
@ 2025-05-26 13:28 Noel Chiappa
0 siblings, 0 replies; 2+ messages in thread
From: Noel Chiappa @ 2025-05-26 13:28 UTC (permalink / raw)
To: tuhs; +Cc: jnc
> From: Noel Chiappa
> the PWB shell (which I guess Massey worked on; hence the name)
Someone pointed out to me that I needed to do a:
1,$s/Massey/Mashey/g
The pitfalls of creating replies in editor buffers: typos get replicated!
Noel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-05-26 13:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20250525194505.B4D2618C075@mercury.lcs.mit.edu>
2025-05-26 0:15 ` [TUHS] Re: shells, Re: Listing of early Unix source code from the Computer History Museum John Levine
2025-05-26 13:28 Noel Chiappa
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).