Joined: July 2004
||Posted: April 21 2006,14:44
|Quote (ZoOp @ April 21 2006,03:30)|
|After using the 'run program' option quiet a lot, I would like to suggest a systematization of input commands to give in the run program. |
F.ex.: in order to run firefox, I just have to tipe
It is the same for Emelfm or dillo (just examples). But, as Robert kindly teaches me, I have to tipe
in order to run rdesktop. Tipping rdesktop only won't work.
It would be great to harmonize all input commands in order for users to only tipe names of apps, and not sometimes names, sometimes full extensions. Thank you so much for keeping up the great work.
The "run program" dialog is grun, which is the same as fbrun, which is the same as every other run dialog. It's merely a "friendly" alternative to a terminal, when you don't need to run a program interactively and don't need bash-specific functionality. As such, it utilizes the basic principle of running a command according to its filename, and with or without its full path depending on its location.
In the case of rdesktop, this behavior is necessary because rdesktop requires commandline parameters in order to work. You cannot start it in any system with only "rdesktop" unless you create an alias or symlink. The rdesktop.lua script is there as a convenience, to give you an interface for setting the commandline parameters.
You can still start rdesktop from the run dialog by using "rdesktop <server>".