Follow-up Comment #6, bug #65804 (group findutils):
[comment #5 comment #5:]
> Wasn't aware that "~/bin" is not posix conform... it was just shorter :)
It's the quoting that's the problem. In a POSIX-conforming shell you can use ~
in PATH assignments, as long as you don't quote it. Then the
Follow-up Comment #5, bug #65804 (group findutils):
Thanks for all the answers.
The "~/bin" served me well the last 8 years, but I have to admit that I only
used bash ;)
Changed it to "$HOME/bin" and up to now nothing broke.
So fine for me as well, to close this ticket.
Wasn't aware that
Follow-up Comment #4, bug #65804 (group findutils):
[comment #2 comment #2:]
> It does appear that Bash performs tilde expansion on $PATH entries while
execvp (which is what the env program uses) does not:
This is one of the places where bash does not conform to POSIX by default.
> $ env -u
