Austin English <[email protected]> writes: >> diff --git a/en/wineusr-running.sgml b/en/wineusr-running.sgml >> index f36383f..106be37 100644 >> --- a/en/wineusr-running.sgml >> +++ b/en/wineusr-running.sgml >> @@ -90,8 +90,8 @@ Usage: wine PROGRAM [ARGUMENTS...] Run the specified >> program >> in the <parameter>Path</parameter> environment variable, you can >> simply give the executable file name. However, if the executable >> is not in <parameter>Path</parameter>, you must give the full path to >> - the executable (in Windows format, not UNIX format!). For >> - example, given a <parameter>Path</parameter> of the following: >> + the executable. For example, given a <parameter>Path</parameter> >> + of the following: >> </para> >> <screen> >> Path="c:\windows;c:\windows\system;e:\;e:\test;f:\" >> @@ -112,7 +112,11 @@ Path="c:\windows;c:\windows\system;e:\;e:\test;f:\" >> </screen> >> <para> >> (note the backslash-escaped "\" !) >> + or: >> </para> >> + <screen> >> +<prompt>$</prompt> <userinput>wine >> ~/.wine/drive_c/myapps/foo.exe</userinput> >> + </screen> >> <para> >> For details on running text mode (CUI) executables, read the >> <link linkend="CUI-programs">section</link> below. >> -- > > A lot of programs break when using Unix paths. I don't think we should > encourage it.
There's no difference between specifying the path in Windows or Unix format. The current directory may be an issue, but that's true in both cases. -- Alexandre Julliard [email protected]
