Humour, comics, tech, law, software, reviews, essays, articles and HOWTOs intermingled with random philosophy now and then
Tutorials and HOWTOs by
Today I made a momentous decision; at least in terms of my personal history with Linux and switched to the Gnome desktop completely. While the migration story including my reasons for dropping KDE is another topic (and will most likely be covered in a future entry) I wanted to explain a very annoying problem which most former KDE users are likely to face when using Gnome. And that is how to set the working path for any executable for which you create a desktop launcher. This is a useful, and occasionally important setting which are required by some programs.
The Gnome launcher creation tool provides no way to specify a working directory as you can see. I searched the web for numerous solutions, all of which were quite unsatisfactory and didn't work. All I needed was a simple solution to the problem. While I hope the Gnome developers will fix this somewhat annoying issue in the future, I have devised a reasonable workaround for the problem. After a bit of thought I merely used a
Posted on Wed, Jul 22, 2009 at 22:40 IST (last updated: Wed, Jul 22, 2009 @ 22:52 IST)
gnome-terminal to wrap around the executable program/script. Seems a very obvious ploy on hindsight, but it took me a while to hit upon the solution.
Here's the necessary command for the launcher window:
gnome-terminal --working-directory /path/to/working/dir/ -e /path/to/executable
Just replace the
/peth/to/executable with your own and you're set. Hope you find it useful.