Re: bash pollutes namespace it shouldn't touch when emulating sh

2017-08-30 Thread Neven Sajko
Another note: it's not even necessary to disable such features in POSIX mode, just give them least precedence in the command search path so they wouldn't conflict with executables on the system.

Re: bash pollutes namespace it shouldn't touch when emulating sh

2017-08-30 Thread Neven Sajko
... > order of special builtins, regular builtins, and shell functions. That > section doesn't even list all of the regular builtins the various shells And, that list in POSIX that I linked too defines commands whose invocation gives unspecified results, thus making them appropriate for use as im

Re: bash pollutes namespace it shouldn't touch when emulating sh

2017-08-30 Thread Neven Sajko
On 28 August 2017 at 17:54, Neven Sajko wrote: > On 28 August 2017 at 15:05, Chet Ramey wrote: >> On 8/28/17 3:42 AM, Neven Sajko wrote: I am not sure what you think Posix mode should do here. Since Posix doesn't standardize the behavior of `^', Bash is free to use it as part of history