Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 17 Dec 2004 11:36:37 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Piping output from sqlplus Message-ID: <20041217163637.GC765@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <407DF7D68DD30440B5CEB70ED234D1CF053F6C65 AT excuswa100 DOT americas DOT unity> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Fri, Dec 17, 2004 at 11:26:15AM -0500, Chuck wrote: >Bakken, Luke wrote: >>>Why would ksh behave differently under Cygwin than under Solaris? >> >> >>cygwin ksh is pdksh. The specific set of code you gave does not work in >>pdksh. Read about it here: >>http://web.cs.mun.ca/~michael/pdksh/ >> >>"Its weak points are that there are still a few differences from ksh88 >>(the major one is that `echo hi | read x' does not set x in the current >>shell - the read is done in a separate process). See the NOTES file in >>the distribution for more details." >> >>You can get a Cygwin ksh from www.kornshell.com >> > >This is working just perfectly thanks. I would like to note (for the >archives) that this ksh does not support the -l option. If you want to >use it for a login shell so that it runs /etc/profile and $HOME/.profile >automatically, make a copy of it named -ksh and run that from your >windows batch file. I tried just creating a symlink named -ksh first, >but Windows didn't like it. I'd like to note for the archives also that I'd like to get the real version of ksh into the cygwin distribution. This comes up from time to time. The first time it happened someone was insisting that they needed to change the Cygwin DLL for this to happen and I had reservations about the licensing status of some of the changes since the person had also seen U/WIN sources. Then, somehow, ksh was built without the need to change cygwin and a cygwin ksh package was going to show up any second now. Well, years later, we still don't have a ksh. Anyone want to take the plunge? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/