Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site allegra.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!alan From: alan@allegra.UUCP (Alan S. Driscoll) Newsgroups: net.unix Subject: Re: editing history list in ksh Message-ID: <2524@allegra.UUCP> Date: Sat, 9-Jun-84 19:39:36 EDT Article-I.D.: allegra.2524 Posted: Sat Jun 9 19:39:36 1984 Date-Received: Sun, 10-Jun-84 01:49:01 EDT References: <174@ucbopal.CC.Berkeley.ARPA> Organization: AT&T Bell Laboratories, Murray Hill Lines: 14 > Does the Korn shell spawn a new vi or emacs process every time you want > to edit some command in the history list? This strikes me as inefficient, > particularly on architectures where forking is slow. Or does ksh have > a subset of vi built in? No forking is done. Instead, a subset of 'emacs' is built into the ksh. (There is also a subset of 'vi' for the masochist.) The command line is treated as a one line window into the history list. In emacs mode, typing ^P replaces the current command line with the previous command, typing ^R allows a reverse search through the history list, and so on. -- Alan S. Driscoll AT&T Bell Laboratories