From: akosela@andykosela.com (Andy Kosela)
Subject: [TUHS] Adventure shell / Doug Gwyn
Date: Tue, 27 Jun 2017 18:00:31 -0500 [thread overview]
Message-ID: <CALMnNGh4AsbZWc4phL_KzpwRuTza_usYjsK0DtJNaG7VwCptGg@mail.gmail.com> (raw)
In-Reply-To: <126A55E2-CCEA-44D7-A0F3-574C9F2002CC@kdbarto.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
On Tuesday, June 27, 2017, David <david at kdbarto.org> wrote:
> Does anyone here remember the Adventure Shell?
>
> Doug wrote it back in 83, and I just stumbled across a copy in an RCS
> directory.
>
> Invoked as ‘ash’ it was pretty clever. I’ve lost the instructions and
> help files, however I’ve got the main script.
>
> Back when people did weird things because it was fun.
>
>
There is also the New Adventure Shell project.
http://nadvsh.sourceforge.net/
--Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170627/7cce4003/attachment.html>
next prev parent reply other threads:[~2017-06-27 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 16:19 David
2017-06-27 17:39 ` Chet Ramey
2017-06-27 23:00 ` Andy Kosela [this message]
2017-06-28 0:07 ` 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=CALMnNGh4AsbZWc4phL_KzpwRuTza_usYjsK0DtJNaG7VwCptGg@mail.gmail.com \
--to=akosela@andykosela.com \
/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).