OK millert@, kn@, ian@, sthen@

These PATH helpers failed to quote their input properly leading to shell
code execution. Noone noticed since import (over 21 years ago), so wipe it.
OK tb rpe

prodded by Raf Czlonka
OK tb@

From Raf Czlonka.
ok halex

parameter expansion instead of basename(1). From Raf Czlonka
ok rpe

OK halex

Found by landry
OK deraadt

While here, convert `` to $().
OK halex

OK halex

OK halex, krw

Based on a diff from Anthony Coulter.
OK krw, halex

OK tb

- comments relevant to other brands of UNIX
- the no-op KSH_VERSION case-block, we only have pdksh
- the case-block for setting aliases based on UNIX brand
together with a comment that falsely encourages to modify this
file instead of putting stuff in $HOME/.kshrc
OK krw@ halex@

to maintain. The eval's must stay to make the aliases expand at run
time instead of at parse time.
ok krw@

eval seems to be needed for reaching the aliases which otherwise aren't
available from within functions...

Eval'ing constant expressions is not such a case.
"...fine with me" krw@

assignments function calls are not surprisingly polluting your shell environment
"makes sense" krw@, ok tedu@ guenther@

urls with spaces work.  ok sthen@

and now that the behaviour of -g has changed to be more in line
with posix, we get group ID by default anyway;
kick started by PR 5784 from Jacek Masiulaniec;
discussed with otto and sobrado;
ok deraadt millert

they do this by sending to stdout. commands like: 'ftp -o - ftp://blah/foo>foo'
do not like having data added to the output stream.
since we only define these two functions in an environment where /dev/tty
exists, send output to /dev/tty to make sure it does not corrupt the output
stream of commands.

xterm or equivalent