From mboxrd@z Thu Jan 1 00:00:00 1970 From: schily@schily.net (Joerg Schilling) Date: Mon, 27 Jun 2016 16:58:09 +0200 Subject: [TUHS] Origin year of BSD csh? In-Reply-To: <20160627112732.GA8110@autechre4> References: <201606261014.u5QAE1qX015184@skeeve.com> <5770032F.8030306@mhorton.net> <20160626181450.GK26734@mcvoy.com> <18119E4C-CE7E-44BD-B2D2-D7B32850238F@ronnatalie.com> <20160627112732.GA8110@autechre4> Message-ID: <57713f01.okpK5vDdvYLxIaXs%schily@schily.net> Sven Mascheck 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/'