Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack Internal I happened to have the variable POSIXLY_CORRECT set as I had earlier run set -o posix.
It was in my list of variables as POSIXLY_CORRECT=y but it did not occur to me at fistfirst sight that this could be the cause. (I was rather searching for any interference with the names of the commands).)
Resetting using set +o posix solved the problem.
I happened to have the variable POSIXLY_CORRECT set as I had earlier run set -o posix.
It was in my list of variables as POSIXLY_CORRECT=y but it did not occur to me at fist sight that this could be the cause (I was rather searching for any interference with the names of the commands).
Resetting using set +o posix solved the problem.
I happened to have the variable POSIXLY_CORRECT set as I had earlier run set -o posix.
It was in my list of variables as POSIXLY_CORRECT=y but it did not occur to me at first sight that this could be the cause. (I was rather searching for any interference with the names of the commands.)
Resetting using set +o posix solved the problem.
I happened to have the variable POSIXLY_CORRECT set as I had earlier run set -o posix.
It was in my list of variables as POSIXLY_CORRECT=y but it did not occur to me at fist sight that this could be the cause (I was rather searching for any interference with the names of the commands).
Resetting using set +o posix solved the problem.
