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.
...
> 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
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
On 8/27/17 6:54 AM, Neven Sajko wrote:
> Bash Version: 4.4
> Patch Level: 12
> Release Status: release
>
> Description:
>
> Some bash features (history expansions ...?) prevent executing
> commands with the same name.
I am not sure what you think Posix mode should do here. Since Posix doesn't
s
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale'
