I was creating a custom launcher on the Mate panel on CentOS 7. I created and placed my script in /home/ken. I pointed the launcher to ~/myscript.sh but it does not launch. I have tested the script from a terminal by typing ~/myscript.sh or /home/ken/myscript.sh or changing to the directory /home/ken and entering ./myscript.sh. All of these work. If I spell out the complete path in the launcher it also works. I am wondering why the launcher does not treat ~/ in the way that Unix and Linux have done for the past hundred year or so?

This also happens with Ubuntu Mate 14.04 and with gnome 2 on CentOS 6 so I do not think it is a Mate issue. Perhaps an artifact from gnome? Any ideas?

TIA,

Ken

ls -l <the-script> ?

1 members found this post helpful.

As far as I know - I've always had to call out the whole path in a "launcher" command (or setting the working directory). /home/user/blah.sh instead of ~/blah.sh BECAUSE the environment variable HOME (or current working directory) is not set in a launcher by default. You can probably see this by making a launcher with the command "/usr/bin/env > /home/user/env.out" and looking at the output to find the variables that are set. If HOME is not set correctly, then "~/" would not work.

1 members found this post helpful.

Thanks c0wb0y, I know the script is where it is supposed to be, is executable and works.And thank you szboardstretcher, That makes sense. I generally would have put the script in a more public location if other users needed to access it and then addressed it by its full path. In this case the only users are me, myself and I So I decided to be lazy and use ~/

Ken

glad you got it sorted.