Le samedi 24 mars 2007, à 11:53, Brian J. Tarricone a écrit : > > I don't think it's needed to specify that field codes, quoting & > > escaping rules don't apply to TryExec: this part doesn't look > > ambiguous to me in the spec. But if you feel it's still ambiguous in > > the spec, then we should fix in some way. > > No, you're right. Since only Exec has further explanation of how to > interpret it and TryExec doesn't, TryExec should be interpreted just > like any other key of the same string type. Though I would still > appreciate the addition to the functional interpretation (regarding > PATH, etc.) you propose above.
Agree. Here's the patch for this. Is there any objection to this patch? Vincent -- Les gens heureux ne sont pas pressés.
Index: desktop-entry-spec/desktop-entry-spec.xml =================================================================== --- desktop-entry-spec.orig/desktop-entry-spec.xml 2007-03-26 00:53:22.000000000 +0200 +++ desktop-entry-spec/desktop-entry-spec.xml 2007-03-26 00:54:58.000000000 +0200 @@ -469,9 +469,11 @@ <row> <entry id="key-tryexec"><varname>TryExec</varname></entry> <entry> - File name of a binary on disk used to determine if the - program is actually installed. If not, entry may not - show in menus, etc. + Path to an executable file on disk used to determine if the program + is actually installed. If the path is not an absolute path, the file + is looked up in the $PATH environment variable. If the file is not + present or if it is not executable, the entry may be ignored (not be + used in menus, for example). </entry> <entry>string</entry> <entry>NO</entry>
_______________________________________________ xdg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xdg
