avr@mtgzz.UUCP (XMRP50000[jcm]-a.v.reed) (05/20/88)
In article <2199@quacky.mips.COM>, dce@mips.COM (David Elliott) writes:
< 2. Having used the csh history mechanism for nearly 8 years, I'm used
< to being able to do things like
<
< % foo bar
< ...
< % ^oo^ob^ # change first foo to foob
< fob bar
< ...
< % mv foo.c foo.c.old
< % !!:gs/foo/bar/ # change all foo to bar
< mv bar.c bar.c.old
<
< I was told once that there was a ksh with a complete csh-style history
< machanism. Is this true?
Yes. What's beautiful is that you can use it with the command set of
your favorite editor, whether vi or emacs; there is no need to learn
another set of editing commands just for the shell.
Adam Reed (mtgzz!avr)andrew@frip.gwd.tek.com (Andrew Klossner) (05/24/88)
[]
"What's beautiful is that you can use it with the command set
of your favorite editor, whether vi or emacs; there is no need
to learn another set of editing commands just for the shell."
Not strictly true; my favorite editor is neither vi nor emacs, so to
learn the ksh history would require me to "learn another set of editing
commands just for the shell." I haven't vigorously pursued switching
to ksh, in part for this reason.
-=- Andrew Klossner (decvax!tektronix!tekecs!andrew) [UUCP]
(andrew%tekecs.tek.com@relay.cs.net) [ARPA]ked@garnet.berkeley.edu (Charles Faulhaber) (05/24/88)
>Not strictly true; my favorite editor is neither vi nor emacs, so to >learn the ksh history would require me to "learn another set of editing >commands just for the shell." I haven't vigorously pursued switching >to ksh, in part for this reason. The MKS Toolkit version of ksh for MSDOS allows you to specify the editor to be used for command editing. Earl H. Kinmonth History Department University of California, Davis Davis, California 95616 916-752-1636/0776 Disclaimer: This is AmeriKa! Who needs a disclaimer! Internet: ehkinmonth@ucdavis.edu cck@deneb.ucdavis.edu BITNET: ehkinmonth@ucdavis UUCP: {ucbvax, lll-crg}!ucdavis!ehkinmonth {ucbvax, lll-crg}!ucdavis!deneb!cck Direct: 916-752-1636 (0000-0700 PDT, not guaranteed), login with password BAKA. Kanji: NEC kanji, shift JIS, JIS80, shin-JIS, kyu-JIS by prior arrangement.
mikep@ism780c.UUCP (Michael A. Petonic) (05/24/88)
In article <10012@tekecs.TEK.COM> andrew@frip.gwd.tek.com (Andrew Klossner) writes: > > "What's beautiful is that you can use it with the command set > of your favorite editor, whether vi or emacs; there is no need > to learn another set of editing commands just for the shell." > >Not strictly true; my favorite editor is neither vi nor emacs, so to >learn the ksh history would require me to "learn another set of editing >commands just for the shell." I haven't vigorously pursued switching >to ksh, in part for this reason. Unfortunately, implementing ed as a command line editor for use in the ksh was seen as pretty redundant to the c-shell. :-) -MikeP
wnp@dcs.UUCP (Wolf N. Paul) (05/24/88)
ked@garnet.berkeley.edu (Charles Faulhaber) writes: >>Not strictly true; my favorite editor is neither vi nor emacs, so to >>learn the ksh history would require me to "learn another set of editing >>commands just for the shell." I haven't vigorously pursued switching >>to ksh, in part for this reason. > >The MKS Toolkit version of ksh for MSDOS allows you to specify >the editor to be used for command editing. > That is not the same as the standard command editing capability, which is built in and can be defined as either emacs or vi. The user-defined editor actually puts a line from history into a tmp file, edits it, and then submits it to the shell: this is MUCH slower than either the emacs or vi editing MODES of the shell. -- Wolf N. Paul * 3387 Sam Rayburn Run * Carrollton TX 75007 * (214) 306-9101 UUCP: ihnp4!killer!dcs!wnp ESL: 62832882 INTERNET: wnp@DESEES.DAS.NET or wnp@dcs.UUCP TLX: 910-280-0585 EES PLANO UD
lvc@tut.cis.ohio-state.edu (Lawrence V. Cipriani) (05/25/88)
In article <10249@agate.BERKELEY.EDU> ked@garnet.berkeley.edu (Charles Faulhaber) writes: >The MKS Toolkit version of ksh for MSDOS allows you to specify >the editor to be used for command editing. The *command line* editing capabilities are either vi or emacs. The *command* editing can be be defined with $FCEDIT. Didn't the original question had to do with *command line* editing? -- Larry Cipriani, AT&T Network Systems and Ohio State University Domain: lvc@tut.cis.ohio-state.edu Path: ...!cbosgd!osu-cis!tut.cis.ohio-state.edu!lvc (weird but right)
ked@garnet.berkeley.edu (Charles Faulhaber) (05/25/88)
In article <14120@tut.cis.ohio-state.edu> lvc@tut.cis.ohio-state.edu (Lawrence V. Cipriani) writes: >In article <10249@agate.BERKELEY.EDU> ked@garnet.berkeley.edu (Earl H. Kinmonth) writes: >>The MKS Toolkit version of ksh for MSDOS allows you to specify >>the editor to be used for command editing. > >The *command line* editing capabilities are either vi or emacs. >The *command* editing can be be defined with $FCEDIT. >Didn't the original question had to do with *command line* editing? Probably. I'm new to the korn shell. After Bourne shell with no history, I was in hog heaven to find ANY command editing. :) Now, if someone would provide an inexpensive Japanese language version.... Earl H. Kinmonth History Department University of California, Davis Davis, California 95616 916-752-1636/0776 Disclaimer: This is AmeriKa! Who needs a disclaimer! Internet: ehkinmonth@ucdavis.edu cck@deneb.ucdavis.edu BITNET: ehkinmonth@ucdavis UUCP: {ucbvax, lll-crg}!ucdavis!ehkinmonth {ucbvax, lll-crg}!ucdavis!deneb!cck Direct: 916-752-1636 (0000-0700 PDT, not guaranteed), login with password BAKA. Kanji: NEC kanji, shift JIS, JIS80, shin-JIS, kyu-JIS by prior arrangement.