Wine FAQ edits
trisk at forkgnu.org
Tue Feb 1 22:47:29 CST 2011
On Sat, Jan 29, 2011 at 4:36 PM, Vitaliy <vitaliy at kievinfo.com> wrote:
> 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.
'cd' immediately precedes this.
>> - You can also use double quotes, but you need two backslashes instead of
>> -wine start "C:\\Games\\Tron\\tron.exe"
> Backslashes still have special meaning inside double quotes. So they should
> be escaped.
Yes, I'll fix this.
>> -/bin/sh -c glxgears
>> +/usr/bin/env glxgears
> What advantage does "env" has over full featured shell? This is unnecessary.
Why do you need a full shell to run a single external program? It
complicates e.g. argument passing if you used this as a template.
>> -@="/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.
Not with spaces, I'll fix this as well.
More information about the wine-devel