Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com X-Authentication-Warning: smtp1.cern.ch: Host IDENT:root@pb-d-137-138-206-44.cern.ch [137.138.206.44] claimed to be skywalker.cern.ch Message-ID: <39C7148F.EAE9F548@cern.ch> Date: Tue, 19 Sep 2000 09:23:59 +0200 From: "Lassi A. Tuura" Organization: Northeastern University, Boston, USA X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: "David M. Karr" CC: cygwin@sourceware.cygnus.com Subject: Re: Link "bash" to "ksh" to be more "portable"? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > 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? IIRC, zsh has a mode to emulate ksh, and will do so automatically if it starts as "ksh"-named process. There have been messages about porting zsh to cygwin on this list, so take a look around to see if you can find the port. Then create a symlink ksh to zsh or just copy the program to ksh. Haven't tried that though. Cheers and hope this helps, //lat -- Of all forms of caution, caution in love is the most fatal. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com