Binary name in the desktop file
Jerome Leclanche
adys.wh at gmail.com
Sat Dec 28 15:06:13 PST 2013
IDEs are a good example of binaries that take their arguments
differently based on the file type, or whether there is a file at all
(eg. an ide normally expects a project file, but some will have a
command line switch to open files in a new project.
That's an excellent example of a type of intent that takes file
arguments: "Open a code file in a new development project".
J. Leclanche
On Sat, Dec 28, 2013 at 10:45 PM, Jasper St. Pierre
<jstpierre at mecheye.net> wrote:
> It seems the use case is "I want to launch an app whose Exec line takes
> filenames or URIs but don't want to pass it any arguments". In the case of
> the Wine example, it's not the "env" line that's the problem, it's that the
> "/ProgIDOpen" won't work unless there are more files after it. I'd perhaps
> argue that you shouldn't build your apps like that, and apps have been built
> this way for 12 years without major troubles, and DBus activation is right
> around the corner, but maybe it's worth speccing in a "BareExec" key.
>
> Keep in mind, this is very, very different from "get the binary name".
>
>
> On Sat, Dec 28, 2013 at 5:39 PM, Thiago Macieira <thiago at kde.org> wrote:
>>
>> On quinta-feira, 26 de dezembro de 2013 21:15:49, Jerome Leclanche wrote:
>> > For the exact same reason menus and any kind of application runners
>> > do. That is to say, not that much. It's needed for the rarer case
>> > where the application accepts different parameters/different command
>> > line depending on whether it has input args or not.
>> > What bothers me here is that the concensus seems to be "Nobody has
>> > needed it so far", but this is clearly false; there just seems to be
>> > pressure not to need it, and call applications needing it "a bug".
>>
>> Jerome, the problem is that no one here understands why you need to know
>> the
>> binary name.
>>
>> Forget the environment. That was a side-effect of your using the wine file
>> as an
>> example. Maybe we need to add EnvironmentNNN entries to set environment
>> variables before launching an executable. But that's a *separate*
>> discussion.
>>
>> --
>> Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
>> Software Architect - Intel Open Source Technology Center
>> PGP/GPG: 0x6EF45358; fingerprint:
>> E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
>>
>> _______________________________________________
>> xdg mailing list
>> xdg at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/xdg
>>
>
>
>
> --
> Jasper
>
> _______________________________________________
> xdg mailing list
> xdg at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xdg
>
More information about the xdg
mailing list