Re: rewriting local apps menu code
Vagrant Cascadian <[email protected]>
| Newsgroups | gmane.linux.terminal-server.devel |
|---|---|
| Message-ID | <[email protected]> |
On Sun, Feb 01, 2009 at 09:20:18AM +0200, Άλκης Γεωργόπουλος wrote:
> I don't think command line parameters aren supposed to be included in
> the "TryExec" line of .desktop files.
> "TryExec" in the .desktop files are what the DE should look for in order
> to show or not this menu item. Meaning, if a .desktop file contains
> "TryExec=myapp", then gnome looks for "myapp" in the path, and if it's
> not there, it doesn't display the menu.
in my brief experience with the LOCAL_APPS_MENU code, this hasn't actually
caused anything to not show up on the menu. is that just because gnome menus
doen't use TryExec, and other things do?
> So, TryExec should either
> * be removed completely from the resulting .desktop file,
> * or modified to "TryExec=xprop" without parameters,
> * or even better, if the exact application path is known, to
> "TryExec=/opt/ltsp/<arch>/path/to/bin", not involving xprop at all.
> (this would require finding out the chroot directory _and_ the chroot
> PATH and looking for the application in it - I don't think it's worth
> the trouble)
one of the first two would be best, as the application server may not have
access to the LTSP chroot.
live well,
vagrant
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_____________________________________________________________________
Ltsp-developer mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help, try #ltsp channel on irc.freenode.net