From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] BSD/v8 TCP/IP
Date: Tue, 13 Sep 2016 11:16:57 +0200 [thread overview]
Message-ID: <57d7c409.CAXBeKfBxosryqgB%schily@schily.net> (raw)
In-Reply-To: <CAEoi9W7fp1Wxd=eB6dSAV_y20kKczK1t3z7sGt2jSJjhsuWAGQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
Dan Cross <crossd at gmail.com> wrote:
> All modern shells use such an integrated history editor....
> >
>
> There is considerable difference on the meaning of "modern" with respect to
> this facility in recent shells, but this isn't the place for a holy war.
From what I could read in the net (I was not able to get an old ksh source)
older ksh versions did call "vi" as external program to edit the history.
This is why there still is the idiosyncratic "fc" command in ksh. With this
interface, you could not type ahead as you first need to call "fc" to be able
to edit a command line. Without type aead, there is no character loss with the
original AT&T streams concept.
Jörg
--
EMail:joerg at schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/
next prev parent reply other threads:[~2016-09-13 9:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 21:39 Doug McIlroy
2016-09-12 21:48 ` Dave Horsfall
2016-09-12 21:53 ` Joerg Schilling
2016-09-12 23:49 ` Dan Cross
2016-09-13 9:16 ` Joerg Schilling [this message]
2016-09-13 1:52 ` Lyndon Nerenberg
2016-09-13 2:37 ` Larry McVoy
2016-09-13 8:12 ` Brantley Coile
2016-09-13 9:29 ` Joerg Schilling
2016-09-13 14:35 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2016-09-12 20:16 Doug McIlroy
2016-09-12 20:27 ` Larry McVoy
2016-09-12 20:36 ` Lyndon Nerenberg
2016-09-12 20:42 ` Joerg Schilling
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=57d7c409.CAXBeKfBxosryqgB%schily@schily.net \
--to=schily@schily.net \
/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).