> Using a full or relative path for a command or file is just an alternative to chdir'ing around the file system.
Well, no it isn't, otherwise you wouldn't have needed a chdir immediately before the comskip command in your example!
The point is, nobody uses a full path to reference a file in the current working directory on a linux system unless there is some specific reason, and if so that reason needs to be explained. So writing it with no explanation just raises hackles.
> Having spent the last 28 years as a professional Unix systems administrator
Well, good for you. I spent 42 years as a professional developer, mostly on Unix and Linux, starting with the first commercial Unix system in the UK in 1979. TIMTOWTDI indeed.
> Regards Comskip documentation, I am not going to Google that for you.
Ooh, you are awful :) And then you have the nerve to post a link to your article a second time! And of course, that article doesn't contain a link either - I did already look there.
And I already looked at the forum, which you do link to, and the github site, which you don't though you do provide a hint to the address. And neither of those provide a link to the documentation that I found. So I lost the will to live and decided to ask somebody who says they came 'to offer a little assistance/clarification'.
But since that person wasn't actually willing to do what they say, I was provoked into searching again and this time I did find
https://www.comskip.org/ (for the benefit of anybody else reading this illuminating discussion). It seems there's some rather poor, out of date, Windows-only documentation there.
