Xref: utzoo comp.unix.amiga:1065 comp.unix.shell:2490 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!cs.umn.edu!atc!cimcor!hawkmoon!det From: det@hawkmoon.MN.ORG (Derek E. Terveer) Newsgroups: comp.unix.amiga,comp.unix.shell Subject: Re: ksh vs csh (was Re: SVR4 /bin/sh BUG) Message-ID: <1991Jun21.230114.16071@hawkmoon.MN.ORG> Date: 21 Jun 91 23:01:14 GMT Article-I.D.: hawkmoon.1991Jun21.230114.16071 References: <109310@becker.UUCP> <1991Jun14.042736.28910@metapro.DIALix.oz.au> <1991Jun15.014909.1562@menudo.uh.edu> <1991Jun15.141609.848@ckctpa.UUCP> <1991Jun17.234824.20461@jato.jpl.nasa.gov> <1991Jun18.023211.25558@msuinfo.cl.msu.edu> The GNU shell, bash, supports >both command line and history editing (ala ksh) _and_ the csh history >recall syntax. Since bash sources are available via FTP, you can place >this shell on every machine you use. Unfortunately, bash does have a few features that are in itself irritating to a ksh user. For example, no support for the ksh "r pattern" command to repeat a command starting with "pattern". The kill character is *hardcoded* to be ^U! Why this is, i haven't the foggiest. There are other nuances that seem rather minor and could be easily fixed, but aren't. I'll stick to ksh. -- Derek "Tigger" Terveer det@hawkmoon.MN.ORG -- U of MN Women's Lax I am the way and the truth and the light, I know all the answers; don't need your advice. -- "I am the way and the truth and the light" -- The Legendary Pink Dots