Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!ukc!warwick!cudcv
From: cudcv@warwick.ac.uk (Rob McMahon)
Newsgroups: comp.unix.shell
Subject: Re: Questions concerning BaSH
Keywords: Bash, question
Message-ID: <1991Jan14.173508.22224@warwick.ac.uk>
Date: 14 Jan 91 17:35:08 GMT
References: <71792@bu.edu.bu.edu> <1991Jan8.163518.24894@cs.utk.edu> <1991Jan9.140124.22689@odin.diku.dk>
Sender: news@warwick.ac.uk (Network news)
Organization: Computing Services, Warwick University, UK
Lines: 27

In article <1991Jan9.140124.22689@odin.diku.dk> kimcm@diku.dk (Kim Christian Madsen) writes:
>>Pros/Cons vs. TCSH
>
>+Has emacs like i-search and reverse-i-search.
>
>This is a great help, for finding old commands in just a few strokes, instead
>of C-p-C-p-C-p ad nauseam.

But note that tcsh has ESC-p to search for previous commands that began with a
certain string, which is usually all you need.  Also I find tcsh's ESC-s for
spell-word, ESC-$ for spell-line, and `set correct = all' for automatic
typo correction invaluable.

I have tried bash out a bit, but it was too flakey at 1.05 for me to use.  A
beta version of 1.06 was around for a bit and seemed much better, but was
branded unofficial.  The problem with bash is that the bash newsgroup/mailing
list is full of `I have problem X' ... `S'OK, that was fixed 6 months ago',
which gets very frustrating.  Where are these fixes ?

I'm sure bash is great for Brian and Chet, and one of these years might be
good for the rest of us, but for now I'll stick to tcsh.

Rob
--
UUCP:   ...!mcsun!ukc!warwick!cudcv	PHONE:  +44 203 523037
JANET:  cudcv@uk.ac.warwick             INET:   cudcv@warwick.ac.uk
Rob McMahon, Computing Services, Warwick University, Coventry CV4 7AL, England