Hacker News new | ask | show | jobs
by jan6 2112 days ago
which "$(echo $0)" should work no matter the invokation ;p if full path, it still returns full path, if just "bash" or such it finds it from $PATH, badoom!
6 comments
xorcist 2112 days ago
The only reason anyone would want to say "$($echo $0)", echoing the variable through a subshell and substituting it with itself, is to rely on the subshell parameter splitting to remove duplicate field separators from the variable.

That is likely not the case there, and any such file names are unlikely to exist. Just say: which "$0"

link
aidenn0 2112 days ago
Which is not guaranteed to be present. 'command -v' should work on any posix shell though.
link
em500 2112 days ago
As the author notes in the 2nd section, that will return the location of the shell binary in the user path, which is not necessarily the one that is currently running.
link
contingencies 2112 days ago
Nah.

  $ which "$(echo $0)"
  which: illegal option -- b
  usage: which [-as] program ...

  $ echo $0
  -bash
OSX. True story.
link
SAI_Peregrinus 2112 days ago
Only for POSIX shells.

fish: $(...) is not supported. In fish, please use '(echo)'. which "$(echo $0)" ^

;)

link
0x0 2112 days ago
But you might have customized your PATH after your shell was executed? So this does not seem accurate.
link