tmcd wrote:
On Thu, 7 Aug 2008, Larry Hall (Cygwin)
But leaving that aside for the moment, perhaps you have a a
corrupted '/bin/[.exe'. Yes, it's just a WAG that really shouldn't
be an issue but given your unique environment, maybe it's worth
checking.
I don't have the original note handy, but I thought it was of the form
if [ ... ]
As the subject line noted, [ is a shell builtin in bash (and I think
even in sh of recent decades), so I don't see how it could be affected
by corruption of anything other than /bin/bash.exe.
If the original code was
if /bin/test ...
or
if /bin/[ ... ]
then it would be likelier.
No argument here. I also doubt that it has anything to do with [.exe
but since the behavior reported doesn't make allot of sense, I thought of
it as a pathological case that's easy to check. I still suspect that it
has more to do with the environment than with bash/Cygwin.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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/
