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: Mon, 20 Dec 2004 11:44:24 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Piping output from sqlplus Message-ID: <20041220164424.GL1175@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <407DF7D68DD30440B5CEB70ED234D1CF053F6C6F 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 Mon, Dec 20, 2004 at 10:02:22AM -0500, Chuck wrote: >Bakken, Luke wrote: >>>I need a korn shell that will handle the windows-like path names >>>(pdksh), and where "read" executes in the same shell that called it >>>(ksh '93). >> >>Keep wishing. There are other ways of doing what you need to do with >>sqlplus without using a pipe and read. > >I have dozen's of ksh scripts already written and running on other >platforms. I'm not going to change them all just to accomodate a >weakness in Cygwin, or more precisely pdksh. So you've got dozens of ksh scripts and your method of getting them working on cygwin is to wish real hard that something changes? You must not want to get things working on windows very much then. -- 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/