Re: extension of file-test primitives?

2017-08-24 Thread Chet Ramey
On 8/23/17 3:57 PM, Eric Blake wrote: >>> EXPR1 -a EXPR2 True if both expr1 AND expr2 are true. >>> EXPR1 -o EXPR2 True if either expr1 OR expr2 is true. >> >> Why update the help documentation? Bash supports it. It's just deprecated >> in the posix standard. > > Not just deprecated,

aliases not supported by default in non-interactive mode...but POSIX required?

2017-08-24 Thread L A Walsh
I was directed to the POSIX section on aliases and it doesn't say they are only to be enabled during interactive mode, but seem to be a required compatibility feature even when running non-interactively: = 2.3.1 Alias Substitution ^[UP XSI ] [Option Start] The processing of aliases

Re: aliases not supported by default in non-interactive mode...but POSIX required?

2017-08-24 Thread Chet Ramey
On 8/24/17 9:49 PM, L A Walsh wrote: > However, in testing posix and non-posix modesĀ  in bash 4.4.12, I don't > see aliases being enabled in scripts. > > To be POSIX conformant, wouldn't they have to be on? They are: $ ../bash-4.4-patched/bash --version GNU bash, version 4.4.12(4)-release (x86_

Re: aliases not supported by default in non-interactive mode...but POSIX required?

2017-08-24 Thread Eric Blake
On 08/24/2017 08:49 PM, L A Walsh wrote: > > However, in testing posix and non-posix modes in bash 4.4.12, I don't > see aliases being enabled in scripts. That's what happens when you run your script in bash mode, rather than POSIX mode. > > To be POSIX conformant, wouldn't they have to be on?

Re: aliases not supported by default in non-interactive mode...but POSIX required?

2017-08-24 Thread L A Walsh
Eric Blake wrote: On 08/24/2017 08:49 PM, L A Walsh wrote: However, in testing posix and non-posix modes in bash 4.4.12, I don't see aliases being enabled in scripts. That's what happens when you run your script in bash mode, rather than POSIX mode. My scripts were: #!/bin/sh s