Path: utzoo!utgpu!attcan!uunet!peregrine!elroy!ames!mailrus!tut.cis.ohio-state.edu!husc6!spdcc!gnosys!gst
From: gst@gnosys.UUCP (Gary S. Trujillo)
Newsgroups: comp.sys.att
Subject: Re: Questions from a new user (SUMMARY)
Summary: RTFM :-)
Keywords: ksh history
Message-ID: <54@gnosys.UUCP>
Date: 12 Aug 88 15:29:00 GMT
References: <620@gvgspd.GVG.TEK.COM> <752@rush.cts.com> <219@ssbn.WLK.COM> <318@anumb.UUCP> <5609@ihlpf.ATT.COM>
Reply-To: gst@gnosys.UUCP (Gary S. Trujillo)
Distribution: na
Organization: gst's 3B1 - Somerville, Massachusetts
Lines: 22

In article <5609@ihlpf.ATT.COM> gmark@ihlpf.ATT.COM (Stewart) writes:
>In article <318@anumb.UUCP>, adh@anumb.UUCP (a.d.hay) writes:
>> actually, it's <esc>/string and ksh finds the most recent command
>> containing the string -anywhere- within it.
>
>Oh, and remember to tell 'im that successive presses of "/" and "cret"
>will give him the rest of the commands that contain the string.

Am I the only one losing interest in this discussion?  The behavior of
ksh under these circumstances is governed by that of either the EMACS
or vi editor commands, so whatever one needs to know can be gleaned from
the appropriate reference.  Further, in the case cited (which is true
only if one has ksh configured to use vi mode (which can be done by
setting the EDITOR environment variable to the path of the vi editor
on your system - and I think there's another way also)), you needn't
use "/<CR>" to get the indicated behavior.  Just use "n", as in vi!

Please - enough already!  :-)

-- 
Gary S. Trujillo			{ihnp4,linus,bbn,m2c}!spdcc!gnosys!gst
Somerville, Massachusetts		     {cirl,ima,stech,wjh12}!gnosys!gst