delorie.com/archives/browse.cgi | search |
From: | "Mark E." <snowball3 AT bigfoot DOT com> |
To: | djgpp-workers AT delorie DOT com |
Date: | Wed, 31 May 2000 14:41:26 -0400 |
MIME-Version: | 1.0 |
Subject: | Re: Bash 2.04 beta 5 released |
Message-ID: | <39352496.3503.7FBBAC@localhost> |
References: | <39351666 DOT 10362 DOT 88549E AT localhost> |
In-reply-to: | <Pine.GSO.4.10.10005311122350.19453-100000@orion.ac.hmc.edu> |
X-mailer: | Pegasus Mail for Win32 (v3.12c) |
Reply-To: | djgpp-workers AT delorie DOT com |
> I think this is because when you invoke bash as `sh', it goes into > POSIX-compatibility mode. It may well be that >& is not specified by > POSIX. > The Bash docs confirm this: When invoked as `sh', Bash enters POSIX mode after the startup files are read. Then in the Posix mode section, it says: 2. The `>&' redirection does not redirect stdout and stderr.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |