Why hard coded executable paths?

[borg1622]

I've noticed that some of the executables used in the script are called by their absolute paths, e.g. /usr/bin/xsel, /usr/bin/cat, etc. Some of these paths are different in Ubuntu, so I had to adjust texpander to my environment.

Is this really necessary? I guess just calling xsel, cat or sleep would be sufficent?! If you expect that these commands are not in the scope of PATH it would be better to retrieve the system specific absolute paths with which rather than using hard coded paths.

In case of the latter I could create a PR.

[Oatelaus]

@itc-ger as far as I know, which searches using PATH.

https://linux.die.net/man/1/which

It does this by searching for an executable or script in the directories listed in the environment variable PATH using the same algorithm as bash(1).