Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Link "bash" to "ksh" to be more "portable"?
From:	dkarr AT tcsi DOT com (David M. Karr)
Date:	18 Sep 2000 14:33:56 -0700
Message-ID:	<uyn1h5qta3.fsf@tcsi.com>
Lines:	20
User-Agent:	Gnus/5.0807 (Gnus v5.8.7) Emacs/20.6
MIME-Version:	1.0

I often see Java libraries/packages that provide pairs of scripts, as
a "bat" file and a Korn shell script.  It's sort of annoying when I
see that I can't use either of them directly from a Bash shell.

Is it reasonable to link "bash.exe" to "ksh.exe" in the Cygwin
distribution?  Is there any feature in Korn shell that is NOT in Bash,
or any other reason why this might be a bad thing to do?

I guess one other annoyance is the "whence" subcommand in Korn shell.
That apparently isn't present in Bash.  It should be easy enough to
write a script for it, but that's just another thing to take care of.

I'm aware of the recently mentioned incantation to run a ".bat" file
from Cygwin.  I would guess that a very simple "cygrunbat" script
could encapsulate this.

-- 
===============================================================================
David M. Karr     ; dkarr AT tcsi DOT com  ; w:(425)487-8312 ; TCSI & Best Consulting
Software Engineer ; Unix/Java/C++/X ; BrainBench CJ12P (#12004)


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -