Systems administrators, testers, and configuration managers will know what I'm talking about.
I know the name of the script that isn't working, now I want to work with it. Where is it?
The old-fashioned way to find a command is this:
$ which oofficeThe shell built-in, type is much faster than which, so I tried converting to this:
$ type -path oofficebut old habits die hard, so I put alias which='type -path' into my ~/.bashrc, and went back to using which.
$ alias which='type -path'To look at the contents, I do this:
$ which ooffice
$ cat $(which ooffice)For editing it, I invoke an editor instead of cat. Take your pick: vi, emacs, gedit, ...