The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] Origin year of BSD csh?
Date: Mon, 27 Jun 2016 16:58:09 +0200	[thread overview]
Message-ID: <57713f01.okpK5vDdvYLxIaXs%schily@schily.net> (raw)
In-Reply-To: <20160627112732.GA8110@autechre4>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

Sven Mascheck <mascheck at in-ulm.de> wrote:

>   "Originally the idea of adding command line editing to ksh was
>    rejected in the hope that line editing would move into the terminal
>    driver. However, when it became clear that this was not likely to
>    happen soon, both line editing modes were integrated into ksh and
>    made optional so that they could be disabled on systems that provided
>    editing as part of the terminal interface."
>
> I believe it's a real pity that it hasn't been implemented in terminal
> drivers in general.
>
> Or do I overlook possible disadvantages?  What could be downsides,
> apart from possibly inconsistent behaviour across systems?

It was in the terminal driver from VMS ;-)

In Summer 1984, I noticed that this feature worked in a similar way as my test 
implementation from 1982 and then worked on an integrated implementation for 
"bsh" at H. Berthold AG. The person that helped me in 1984 was Peter Teuchert.

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/'


  parent reply	other threads:[~2016-06-27 14:58 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-26 10:14 Aharon Robbins
2016-06-26 16:30 ` Mary Ann Horton
2016-06-26 18:14   ` Larry McVoy
2016-06-26 18:32     ` Ronald Natalie
2016-06-26 20:43       ` John Cowan
2016-06-27  0:59         ` Larry McVoy
2016-06-27  1:11           ` John Cowan
2016-06-27 11:27       ` Sven Mascheck
2016-06-27 12:47         ` Steve Nickolas
2016-06-27 14:58         ` Joerg Schilling [this message]
2016-06-27 15:29           ` Ronald Natalie
2016-06-27 16:22         ` John Cowan
2016-06-27 16:35           ` Steve Nickolas
2016-06-27 20:00         ` Dave Horsfall
2016-06-27 20:33         ` Ronald Natalie
2016-06-27 20:44           ` Clem Cole
2016-06-27 21:02           ` Steve Nickolas
2016-06-27 21:15             ` Ronald Natalie
2016-06-27 21:20           ` John Cowan
2016-06-27 21:28             ` Ronald Natalie
2016-06-27 21:45               ` John Cowan
2016-06-28  6:49               ` Peter Jeremy
2016-06-28  7:51                 ` arnold
2016-06-27 21:29           ` Random832
2016-06-28 14:47         ` Tony Finch
2016-06-26 19:41     ` Clem Cole
2016-06-27 10:31       ` Joerg Schilling
2016-06-27 13:01         ` Ronald Natalie
2016-06-27 13:15           ` Steffen Nurpmeso
2016-06-27 15:17           ` Joerg Schilling
2016-06-27 13:39         ` [TUHS] Bizarre job control, was csh Warren Toomey
2016-06-27 15:00           ` Steve Nickolas
2016-06-27 15:13             ` Joerg Schilling
2016-06-27 15:23               ` Steve Nickolas
2016-06-26 20:58     ` [TUHS] Origin year of BSD csh? Steve Nickolas
2016-06-27 10:03 ` 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=57713f01.okpK5vDdvYLxIaXs%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).