[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: Wine FAQ edits
From:       Vitaliy <vitaliy () kievinfo ! com>
Date:       2011-01-29 21:36:45
Message-ID: 4D44886D.3030905 () kievinfo ! com
[Download RAW message or body]

On 01/29/2011 12:21 PM, Dan Kegel wrote:
> Hi Albert,
> http://wiki.winehq.org/FAQ?action=diff&rev2=384&rev1=383 looks
> like it was a pretty big edit.
>
> Try smaller ones, and try to do just one kind of change per edit.

That, and the fact that some changes where questionable, and broken:

> -cd ~/.wine/drive_c/Program\ Files
> +cd .wine/drive_c/Program\ Files
This will break if current directory is not $HOME.

> - You can also use double quotes, but you need two backslashes instead of one:
> -
> -{{{
> -wine start "C:\\Games\\Tron\\tron.exe"
> -}}}
Backslashes still have special meaning inside double quotes. So they should 
be escaped.

> -/bin/sh -c glxgears
> +/usr/bin/env glxgears
What advantage does "env" has over full featured shell? This is unnecessary.

> -@="/bin/sh run_linx_program acroread \"%1\""
> +@="/bin/sh -c \"acroread `wine winepath -u '%1'`\""
Have you actually tested this? This won't work for paths with spaces. If it 
will work at all.

Vitaliy


[prev in list] [next in list] [prev in thread] [next in thread]