[19:25] OvenWerks: You should be able to test for the location of a command in $PATH using "command -v". Don't use 'which', it's being depricated. [19:29] Eickmeyer: I was already assuming python has a better way to do this :) [19:32] Oh, yeah, I don't know about that, but I know you can query python for the output of a command. [19:32] Eickmeyer: you will never guess what the python method is... shutil.which() [19:32] LMAO That's hilarious. [19:32] Long Live Which [19:32] :) [19:33] Yeah, but I doubt it's using the actual "which" command as a backend. [19:33] why people would depricate something simple like which to something no one has heard of sounds dumb. [19:35] command should be changed so that if parameter 0 is which it acts that way. [19:35] (ie. a link called which that points to command should just work... otherwise bug [19:37] basic unix commands should always continue to work [19:41] Right, not sure why it's depricated, but probably because it was duplicating the work of "command -v". [19:42] except any book that teaches unix commands teaches which [19:43] Yeah, again, I have no idea why, but remember, GNU's Not Unix (tm). [19:44] no but gnu has created almost all the commandline tools unix depends on. The gnu commandline tools are effectively the standard commandline tools. [19:46] I mean, I agree, but which in 22.04 was giving the error that it was being depricated in favor of "command -v". The release team reverted that for now since it's an LTS and nobody wants that going bad yet. [19:48] command is a part of bash it seems. [19:49] does sh include command as well? seems to... except I think our sh->bash :P [19:50] one wonders about ash and csh too. [19:51] or for that matter any shell script that is not run from bash. [20:00] Yeah, no clue. I just know it was saying "This version of which is depricated. Use 'command -v' instead in scripts." [20:12] Anyway, python has which ;) [20:14] :)