http://bugs.winehq.org/show_bug.cgi?id=26243
--- Comment #5 from Kim Jensen kjensen@devnull.dk 2011-02-25 16:24:59 CST --- I apologize that I have not been thorough enough in my test. Regarding ~ it is obviously my fault - I was too quick on the trigger so to speak.
The second error - regarding pipe and sed - is still weird. It is true that sed and pipe do nothing, but if I unplug it, then I can not open files with spaces. This is probably a configuration error / misunderstanding by me. At least I think so because I have found out that there is a difference whether the command ends with a space or not: >$1 "`wine winepath -u "$2"`"
However my open command looks different from that described in the FAQ (but I could not get that to work). Therefore my looks like this: /bin/sh /home/kjensen/bin/run_linx_program ooffice "% 1"
I'm not sure why, but it works for me now but it is not due to "sed".
Sincerely, Kim Jensen