On 2016-04-07, frantisek holop wrote:
> but why set posix mode and then expect the opposite?
Because different shells disagree about which behavior actually
complies with POSIX. For instance, bash in POSIX mode behaves like
our ksh in non-POSIX mode.
--
Christian "naddy" Weisgerber
Christian Weisgerber, 07 Apr 2016 15:41:
> As ksh(1) explains under "POSIX mode":
>
> o Occurrences of \" inside double quoted `..` command substitutions.
> In POSIX mode, the \" is interpreted when the command is interpreted;
> in non-POSIX mode, the backslash is stripped before the
On 2016-04-06, frantisek holop wrote:
> i am trying to track down some fgrep errors that show
> up in vim's configure run.
>
> 5733 if test "X`echo \"$LDFLAGS\" | $FGREP -e \"$perlldflags\"`" =
> "X"; then
Ah, yes. We've run into this before.
As ksh(1) explains under "POSIX mode":
i am trying to track down some fgrep errors that show
up in vim's configure run. despite the error, the result
happens to be the expected one, but still...
/usr/ports/editors/vim$ FLAVOR="gtk2 perl python ruby" make configure
...
checking for perl... /usr/bin/perl
checking Perl version... OK
che
