Binary name in the desktop file

[Dominique Michel]

Le Thu, 26 Dec 2013 20:54:18 +0000,
Jerome Leclanche <adys.wh at gmail.com> a écrit :

> I never implied the spec was wrong...
> 
> I seem to be talking into the wind here, it's quite frustrating, so
> I'm just going to leave this alone. If someone wishes to go forward
> with adding an Environment key to the desktop file though that still
> seems like an excellent idea.
> 
> J. Leclanche

I am like you here, I have no power at all to decide whatever regarding
this list or the spec. But reading the spec for the Exec key, and after
you remembering me env is a command, I see no reason why your
Exec key generated by wine will not work. How I understand the spec, it
must work.

That imply this is not a limitation in the spec or a bug in the desktop
file, that no Environment key is needed, but the implementation of the
spec in your system need to be fixed.

I try a desktop file with the following Exec key into plain fvwm using
fvwm-menu-directory and a nested session:

Exec=env TESTENV="eng" urxvt

and it worked fine. If I do an echo $TESTENV in that term, I get eng.
That imply your issue is elsewhere that in the spec, but in its
implementation in your system or in the quoting in your desktop file
(I didn't tested it).

Dominique

> 
> 
> On Thu, Dec 26, 2013 at 9:06 PM, Dominique Michel
> <dominique.michel at vtxnet.ch> wrote:
> > Le Thu, 26 Dec 2013 20:37:56 +0000,
> > Jerome Leclanche <adys.wh at gmail.com> a écrit :
> >
> >> On Thu, Dec 26, 2013 at 8:33 PM, Liam R E Quin <liam at holoweb.net>
> >> wrote:
> >> > On Thu, 2013-12-26 at 10:56 +0000, Jerome Leclanche wrote:
> >> >> I'd really like to be able to get the binary name from desktop
> >> >> files
> >> >
> >> > What if there's no binary, e.g. a shell script or a python-based
> >> > program with a UI?
> >> >
> >> > What about a Java program,
> >> > java -cp .... -jar ...
> >> > ?
> >> > If you just run "java" you won't see much.
> >> >
> >> >> (eg a way to "start without any argument"). Current
> >> >> implementations rely on getting the first word of the Exec key
> >> >> OR replace %f etc by nothing, but that fails for things such as
> >> >> these:
> >> >>
> >> >> Exec=env
> >> >> WINEPREFIX="/home/adys/.local/share/wineprefixes/default" wine
> >> >> start /ProgIDOpen chm.file %f
> >> >
> >> > What exactly fails here?
> >> >
> >> > Like others I've no idea about "runners" or "intents", but maybe
> >> > that's because I don't run KDE? I'm not sure that a cross-desktop
> >> > environment facility should hard-code environment-specific ideas.
> >> > But if it's a concept useful elsewhere then it may make sense.
> >> >
> >> > I *think* you might really be asking for a way to run a program
> >> > without opening a specific file, is that right? It's not about
> >> > having no arguments such as "-c"...
> >> >
> >> > If so, that might be a good idea, and should indeed be a separate
> >> > entry. But doesn't the menu entry already give you this?
> >>
> >> See a couple of posts above; the menu entry suffers from the same
> >> issue. Either way, I can just do the same thing as menus/launchers
> >> do without arguments but as I said, some apps will still be broken.
> >> I dislike the philosophy of "it's on the app developer to fix it";
> >> this is a pretty obvious shortcoming of the spec.
> >
> > Not sure. The spec said the Exec key must be an executable followed
> > by arguments. In your case, env is the executable, and all that
> > follow are arguments to that executable. At least according to 'man
> > env'.
> >
> > That imply the spec is right, but its implementation doesn't work in
> > such cases.
> >
> > Dominique
> >
> >>
> >> >
> >> > Liam
> >> >
> >> > --
> >> > Liam Quin - XML Activity Lead, W3C,
> >> > http://www.w3.org/People/Quin/ Pictures from old books:
> >> > http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org
> >> > freenode/#xml
> >> >
> >>
> >>
> >>
> >> J. Leclanche
> >> _______________________________________________
> >> xdg mailing list
> >> xdg at lists.freedesktop.org
> >> http://lists.freedesktop.org/mailman/listinfo/xdg
> > _______________________________________________
> > xdg mailing list
> > xdg at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/xdg