Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Authentication-Warning: localhost.localdomain: ronald set sender to blytkerchan@users.sourceforge.net using -f Date: Mon, 29 Sep 2003 11:10:25 +0200 From: Ronald Landheer-Cieslak To: cygwin@cygwin.com Subject: Re: Copying stderr to stdout Message-ID: <20030929091025.GA6877@linux_rln.harvest> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4i X-Disclaimer: I had nothing to do with it - I swear! X-loop: linux_rln.harvest On Fri, Sep 26, 2003 at 05:28:16PM +0200, Øyvind Harboe wrote: > I was having a bit of trouble copying stderr to stdout, e.g. > > $ ls 2>&1 lkajsdflkjasdflkj >ll > ls: lkajsdflkjasdflkj: No such file or directory > > I would have expected the error message to end up in "ll". > > If I place "2>&1" at the end of the line it works. > > Is this the intended behaviour? You're not giving any information that might actually lead to an answer: something as basic as which shell you are using.. If you're using Bash, the behaviour is normal. If you're using any other shell, I don't know. rlc -- To stay youthful, stay useful. -- 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/