Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!ukma!rutgers!att!ihlpb!gregg
From: gregg@ihlpb.ATT.COM (Wonderly)
Newsgroups: comp.sources.d
Subject: Re: Bourne Again Shell?
Message-ID: <9845@ihlpb.ATT.COM>
Date: 13 Mar 89 15:00:24 GMT
References: <10659@stb.UUCP>
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 27

From article <10659@stb.UUCP>, by michael@stb.UUCP (Michael):
> ...
>
> Now, my turn: How do you combine multiple commands in the KSH history
> mode? My copy of ksh does not implement vi's yank feature, so I cannot
> combine parts from command 32 with command 35.
> 

since ksh's history file is essentially read only, you can use 'dw' or
whatever to delete the words that you want from one line and insert them
into another with 'p' or 'P' (or the equivalent, if it works, in emacs mode)...

> Also, ksh's vi mode has the /'s and ?'s backwards, as well as G (which
> goes to the first command, not the last command).
> 
> (I know what you'll say, think of editing a file where the new lines go at
> the top. But then why can't I say 1G, and why are the numbers on the lines
> backwards?)

The answer is that the normal thing is to search backwards through history,
so that is the easiest (no shift key).  Certainly complexity of operation
is an issue when designing the interface for a tool.  Here, David did the
correct thing!

-- 
Gregg Wonderly                             DOMAIN: gregg@ihlpb.att.com
AT&T Bell Laboratories                     UUCP:   att!ihlpb!gregg