re: start.exe: New feature allowing to specify the shell operation name
The new /O[peration] command line option allows to specify a shell operation other than "open". This is very valuable for testing or implementing actions from shell scripts.
Hmm. I don't see that option in the Win XP documentation: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-... There's already one clash (/l) between wine's start and Windows'. I hesitate to say that adding another extension is a good idea. I'd feel better if the help mentioned that this is a Wine-specific extension. - Dan
On Tue, 26 Sep 2006, Dan Kegel wrote:
The new /O[peration] command line option allows to specify a shell operation other than "open". This is very valuable for testing or implementing actions from shell scripts.
Hmm. I don't see that option in the Win XP documentation: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-...
There's already one clash (/l) between wine's start and Windows'. I hesitate to say that adding another extension is a good idea. I'd feel better if the help mentioned that this is a Wine-specific extension. - Dan
There's more than one clash - /r[estored] vs. /realtime - but at least I used something currently unallocated. Should both be marked wine specific in usage? Paul Chitescu
On 9/26/06, Paul Chitescu <paulc(a)voip.null.ro> wrote:
On Tue, 26 Sep 2006, Dan Kegel wrote:
The new /O[peration] command line option allows to specify a shell operation other than "open". Hmm. I don't see that option in the Win XP documentation: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-...
There's already one clash (/l) between wine's start and Windows'.
There's more than one clash - /r[estored] vs. /realtime - but at least I used something currently unallocated.
Should both be marked wine specific in usage?
Yes, we should rename the currently clashing ones to not clash, and mark them as wine specific. - Dan
participants (2)
-
Dan Kegel -
Paul Chitescu