Fwd: Re: RFC: Autostart spec, first draft

Matthias Welwarsky matze at stud.fbi.fh-darmstadt.de
Fri Jul 8 08:44:43 BST 2005

Hi Waldo,

originally sent to xdg-list, but it's subscriber only and the list manager 
didn't approve it (yet).

----------  Forwarded Message  ----------

Subject: Re: RFC: Autostart spec, first draft
Date: Thursday 07 July 2005 14:33
From: Matthias Welwarsky <matze at brucherseifer.net>
To: xdg at lists.freedesktop.org


I, too, think that the 'x' bit should not be abused here. Of course it's a
simple trick to enable/disable autostart, but it's far more obvious to add a
key (EnableAutorun) to the .desktop file.

The section titled "Hidden Key" is unclear. Is it supposed to disambiguate
autostart files in different directory trees? It's much saner IMHO to ignore
autostart files in less important directories alltogether instead of making
an exception for certain keys. You probably cannot merge the contents of
autostart files across all directories anyway.

TryExec: the differentiation between "absolute" and "relative" paths is
unclear with regards to handling PATH. A relative path is commonly understood
as "any path not starting with /". Does this mean you can have
TryExec=somedir/somexec and this will be matched against each component of
PATH by concatenation of TryExec with each component of PATH? Or is
"relative" actually meant to be "name of executable"?



From the 'Handbook of Corporate Slang':

- to protect prior investment (phrase):
    describes the inability to revert a wrong decision made
    in the past, expresses willingness of throwing 
    good money after bad. (q.v. Fiorina, C.)

More information about the kde-core-devel mailing list