## compare_shells: bash dash mksh zsh

#### ~ expansion in assignment
HOME=/home/bob
a=~/src
echo $a
## STDOUT:
/home/bob/src
## END
## BUG bash STDOUT:
## END

#### ~ expansion in readonly assignment
# dash fails here!
# http://stackoverflow.com/questions/8441473/tilde-expansion-doesnt-work-when-i-logged-into-gui
HOME=/home/bob
readonly const=~/src
echo $const
## stdout: /home/bob/src
## BUG dash stdout: ~/src

#### No ~ expansion in dynamic assignment
HOME=/home/bob
binding='const=~/src'
readonly "$binding"
echo $const
## stdout: ~/src

#### No tilde expansion in word that looks like assignment but isn't
# bash and mksh mistakenly expand here!
# bash fixes this in POSIX mode (gah).
# http://lists.gnu.org/archive/html/bug-bash/2016-06/msg00001.html
HOME=/home/bob
echo x=~
## stdout: x=~
## BUG bash/mksh stdout: x=/home/bob

#### tilde expansion of word after redirect
HOME=$TMP
echo hi > ~/tilde1.txt
cat $HOME/tilde1.txt | wc -c
## STDOUT:
3
## END
## status: 0
## BUG bash STDOUT:
## END
## BUG bash STDERR:
## END

#### No assignment-like tilde expansion in redirect target
HOME=/home/bob
echo hi > $TMP/x=~
cat "$TMP/x=~"
## STDOUT:
hi
## END

#### other user
echo ~nonexistent
## stdout: ~nonexistent
# zsh doesn't like nonexistent
## OK zsh stdout-json: ""
## OK zsh status: 1

#### ${undef:-~}
HOME=/home/bar
echo ${undef:-~}
echo ${HOME:+~/z}
echo "${undef:-~}"
echo ${undef:-"~"}
## STDOUT:
/home/bar
/home/bar/z
~
~
## END
## BUG bash STDOUT:
## END

#### ${x//~/~root}
HOME=/home/bar
x=~
echo ${x//~/~root}

# gah there is some expansion, what the hell
echo ${HOME//~/~root}

x=[$HOME]
echo ${x//~/~root}

## STDOUT:
/root
/root
[/root]
## END
## BUG bash STDOUT:
## END
## N-I dash status: 2
## N-I dash stdout-json: ""

#### x=foo:~ has tilde expansion
HOME=/home/bar
x=foo:~
echo $x
echo "$x"  # quotes don't matter, the expansion happens on assignment?
x='foo:~'
echo $x

x=foo:~,  # comma ruins it, must be /
echo $x

x=~:foo
echo $x

# no tilde expansion here
echo foo:~
## STDOUT:
foo:/home/bar
foo:/home/bar
foo:~
foo:~,
/home/bar:foo
foo:~
## END
## BUG bash STDOUT:
## END

#### a[x]=foo:~ has tilde expansion
case $SH in dash|zsh) exit ;; esac

HOME=/home/bar
declare -a a
a[0]=foo:~
echo ${a[0]}

declare -A A
A['x']=foo:~
echo ${A['x']}

## STDOUT:
foo:/home/bar
foo:/home/bar
## END
## BUG bash STDOUT:
## END
## N-I dash/zsh stdout-json: ""

#### tilde expansion an assignment keyword
HOME=/home/bar
f() {
  local x=foo:~
  echo $x
}
f
## STDOUT:
foo:/home/bar
## END
## BUG bash STDOUT:
## END
## BUG dash STDOUT:
foo:~
## END

#### x=${undef-~:~}
HOME=/home/bar

x=~:${undef-~:~}
echo $x

# Most shells agree on a different behavior, but with the OSH parsing model,
# it's easier to agree with yash.  bash disagrees in a different way

## STDOUT:
/home/bar:/home/bar:/home/bar
## END
## BUG bash STDOUT:
## END
## OK osh/yash STDOUT:
/home/bar:~:~
## END

#### strict tilde
echo ~nonexistent

echo ~nonexistent

echo status=$?
## status: 1
## STDOUT:
~nonexistent
## END
## N-I bash/dash/mksh status: 0
## N-I bash/dash/mksh STDOUT:
~nonexistent
~nonexistent
status=0
## END
## OK zsh stdout-json: ""

#### temp assignment x=~ env

HOME=/home/bar

xx=~ env | grep xx=

# Does it respect the colon rule too?
xx=~root:~:~ env | grep xx=

## STDOUT:
xx=/home/bar
xx=/root:/home/bar:/home/bar
## END
