[Bug 26243] New: WineFAQ: 7.5. I want to associate a native program with a file type in Wine
http://bugs.winehq.org/show_bug.cgi?id=26243 Summary: WineFAQ: 7.5. I want to associate a native program with a file type in Wine Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kjensen(a)devnull.dk Hi, I have submitted a change to the WineFAQ but it seems like you don't like it - as it keeps getting reverted... I'll try to explain the change here (as a last attempt) In section 7.5. "I want to associate a native program with a file type in Wine" If the argument to the program contains spaces it will not work - so I have added sed to change " " (spaces) to "\ " like: #!/bin/sh $1 "`wine winepath -u "$2"`" | sed 's/ /\\ /' I.e. you try to open a .doc file named "my document.doc" then without sed, openoffice will not be able to open the file. With sed added it will. I'm sure that I'm not the only one with this problem. Another minor thing: I believe most people will find it easier to understand if you use ~ as the reference to home instead of telling them to: "make sure that $HOME/bin directory is in your $PATH." But that's just my two cents Sincerely, Kim Jensen -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=26243 Juan Lang <juan_lang(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID --- Comment #1 from Juan Lang <juan_lang(a)yahoo.com> 2011-02-25 10:44:36 CST --- This isn't a Wine bug. It's also not an appropriate forum to discuss such things, please do so on the mailing list. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=26243 Juan Lang <juan_lang(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #2 from Juan Lang <juan_lang(a)yahoo.com> 2011-02-25 10:44:50 CST --- Closing invalid. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=26243 --- Comment #3 from Kim Jensen <kjensen(a)devnull.dk> 2011-02-25 12:38:44 CST --- I was just trying to help - but that is a difficult task I see, and that's shame. I was not allowed to do so using the wiki It is not a "real" bug, so I can't use Bugzilla Well perhaps some mailing list will accept my request otherwise I give up. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=26243 --- Comment #4 from Alexandre Julliard <julliard(a)winehq.org> 2011-02-25 12:41:17 CST --- http://www.winehq.org/pipermail/wine-devel/2011-February/089031.html -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=26243 --- Comment #5 from Kim Jensen <kjensen(a)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 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org