Q on Bash's self-documented POSIX compliance...

I noted on the bash man page that it says it will start in posix compliance mode when started as 'sh' (/bin/sh). What does that mean about bash extensions like arrays and use of [[]]? Those are currently not-POSIX (but due to both Bash and Ksh having them, some think that such features are part

Re: |& in bash?

Bob Proulx wrote: And therefore they don't know how to write other directory traversal tasks either. find . -type f -exec sed -n '/PATTERN/s/THIS/THAT/gp' {} + --- You mean I can't: "sed -Rn '...'" ? Drat. OB.bash: bash -c 'while (($#)); do [[ -f $1 ]] && sed -n "/PATTERN/s/THIS/THA

Re: Q on Bash's self-documented POSIX compliance...

On Sat, Jan 26, 2013 at 1:27 PM, Linda Walsh wrote: > I noted on the bash man page that it says it will start in posix > compliance mode when started as 'sh' (/bin/sh). > > What does that mean about bash extensions like arrays and > use of [[]]? > > Those are currently not-POSIX (but due to both

Re: Q on Bash's self-documented POSIX compliance...

Am 27.01.2013 01:37, schrieb Clark WANG: > On Sat, Jan 26, 2013 at 1:27 PM, Linda Walsh wrote: > >> I noted on the bash man page that it says it will start in posix >> compliance mode when started as 'sh' (/bin/sh). >> >> What does that mean about bash extensions like arrays and >> use of [[]]? >>