Message-Id: <200107151951.PAA08908@delorie.com> Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Apparently-From: From: Joerg Fischer To: CC: Date: Sun, 15 Jul 2001 21:52:03 +0200 X-Mailer: Vivian Mail [320.0104170] R Subject: Re: Problem with shell commands Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id PAA08908 Hello, sorry, I didn't pay enough attention, I just copied from the original message ;-) So yes, now I don't get an invalid null command message. But strangely enough it still does not work. What I/O descriptors can be open that NEdit sees? Are stdin, stdout or stderr always open? Joerg ----------------- >On Sun, 15 Jul 2001, Joerg Fischer wrote: > >> > you should write (csh) >> > view % & < /dev/null >& /dev/null >.... >> The above /dev/null trick doesn't work for Cygwin (invalid null command). >> > >I am very surprised that this works anywhere else. The correct is > >view % < /dev/null >& /dev/null & > >& is command separator, just as newline or ; so your example is >interpreted as two commands, the second one with just redirections (that's >about null command). > >-andrej _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/