From: Bakul Shah <bakul@bitblocks.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] V9 shell [was Re: Warner's Early Unix Presentation]
Date: Mon, 10 Feb 2020 10:59:14 -0800 [thread overview]
Message-ID: <20200210185921.E6328156E40E@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Tue, 11 Feb 2020 05:39:26 +1100." <CAKzdPgw9zVVo-QzpA3Paminq-YrAEO89nUBKAw4f6-TrxvAffg@mail.gmail.com>
On Tue, 11 Feb 2020 05:39:26 +1100 Rob Pike <robpike@gmail.com> wrote:
>
> Readline and job control were less compelling when you had multiple command
> windows of editable typescript, which we all had with the Blit.
^Z is still useful, to stop forward progress temporarily.
Analogous to what ^S/^Q does for output stream.
As for editable typescript, I like how Dyalog's APL console
app works. You can edit any previous expression but when you
run it, the original expression is restored and the edited
expression appears on a new line. This way you can see the
real history of what you did, as opposed to in acme or rio,
for example, where the original content of edited lines in an
rc shell window is lost.
next prev parent reply other threads:[~2020-02-10 18:59 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 22:25 [TUHS] Warner's Early Unix Presentation Warren Toomey
2020-02-07 23:57 ` Rob Pike
2020-02-08 0:43 ` Warren Toomey
2020-02-08 3:37 ` Warner Losh
2020-02-08 15:15 ` Warner Losh
2020-02-08 21:50 ` Rob Pike
2020-02-08 22:29 ` Chet Ramey
2020-02-08 22:54 ` Rob Pike
2020-02-08 23:02 ` Chet Ramey
2020-02-08 23:11 ` Rob Pike
2020-02-08 23:13 ` Rob Pike
2020-02-08 23:21 ` Kurt H Maier
2020-02-08 23:26 ` Rob Pike
2020-02-08 23:28 ` Chet Ramey
2020-02-08 23:26 ` Chet Ramey
2020-02-08 23:29 ` Rob Pike
2020-02-08 23:35 ` Warner Losh
2020-02-08 23:36 ` Chet Ramey
2020-02-08 23:54 ` Rob Pike
2020-02-09 0:11 ` Chet Ramey
2020-02-09 0:19 ` Larry McVoy
2020-02-08 22:31 ` Richard Salz
2020-02-10 13:18 ` Tony Finch
2020-02-10 15:05 ` Dan Cross
2020-02-10 15:46 ` [TUHS] V9 shell [was Re: Warner's Early Unix Presentation] arnold
2020-02-10 18:39 ` Rob Pike
2020-02-10 18:59 ` Bakul Shah [this message]
2020-02-10 19:58 ` Angelo Papenhoff
2020-02-10 20:11 ` Chet Ramey
2020-02-11 9:33 ` arnold
2020-02-11 9:47 ` Noel Hunt
2020-02-11 9:47 ` Rob Pike
2020-02-11 9:59 ` Rob Pike
2020-02-11 17:05 ` Steffen Nurpmeso
2020-02-11 17:18 ` Arthur Krewat
2020-02-11 18:22 ` Kurt H Maier
2020-02-16 21:34 ` Wesley Parish
2020-02-11 18:26 ` Jon Steinhart
2020-02-11 23:56 ` Steffen Nurpmeso
2020-02-12 0:12 ` Jon Steinhart
2020-02-12 1:03 ` [TUHS] V9 shell Warren Toomey
2020-02-12 5:54 ` [TUHS] V9 shell [was Re: Warner's Early Unix Presentation] Rob Pike
2020-02-11 17:36 ` Dan Cross
2020-02-11 18:35 ` Christopher Browne
2020-02-11 18:54 ` Rob Pike
2020-02-11 21:36 ` Harald Arnesen
2020-02-11 3:32 Doug McIlroy
2020-02-11 3:53 ` Larry McVoy
2020-02-11 11:24 ` Ralph Corderoy
2020-02-11 15:51 ` Larry McVoy
2020-02-11 4:46 ` Warren Toomey
2020-02-11 5:12 ` Steve Nickolas
2020-02-11 6:33 ` Rob Pike
2020-02-11 9:40 ` arnold
2020-02-11 15:06 ` Chet Ramey
2020-02-11 14:36 ` Clem Cole
2020-02-11 15:29 ` Mike Markowski
2020-02-11 16:03 ` Bakul Shah
2020-02-11 17:12 ` Clem Cole
2020-02-11 17:17 ` Steve Nickolas
2020-02-11 17:21 ` Dan Cross
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=20200210185921.E6328156E40E@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--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).