shell open fails with some folder names

[leniviy]

Please, can someone try it?
Create 2 empty text files:
"c:\test\aaa.txt"
"c:\test aaa\aaa.txt"

Now open wine explorer, go to "c:\test aaa" and doubleclick aaa.txt. It should open another explorer window instead of opening the file in notepad.

Looks like existence of "c:\test\" somehow prevents normal shell open in other folders in "C:\" which start with "test ".

wine-1.1.35

[vitamin]

Now open wine explorer, go to "c:\test aaa" and doubleclick aaa.txt. It should open another explorer window instead of opening the file in notepad.

It's a known problem - Wine's "start.exe" doesn't handle files with spaces in their names.

[trycage]

Hi All

This problem is indicated as solved in the release 1.1.20
By the fact applications (e.g. Msword) can browse, reach the file and open it using the dialog windows (Wine version 1.1.41). However I tested version 1.1.41, and it is quite annoying that by click on my NTFS volume each folder or name with spaces in it cannot be opened.

If someone as a valid workaround (not just changing the file name) isvery welcome.
Personally (as many other people), I have many windows-originated contents with spaces in files and path and I would really appreciate a smart solution

Thanks

Best Regards

Marco

[leniviy]

trycage, specifically, your description of the problem is incomplete.
For most users paths with spaces work well. That's why they haven't fixed it yet. There're, however, some problems with msoffice file associations.


I'm currently waiting for coments on the related patch
http://www.winehq.org/pipermail/wine-pa ... 86009.html

[trycage]

Sorry Lenivity,

I understand I may gave you a wrong impression.
I didn't want to cut short on the problem. Actually proper path addressing in msoffice is very important to me.

I just wanted to report that GUI access to files (from MsWord) seems to work, but indeed the problem is there and it is still to solve.

Trycahe

[dimesio]

I just wanted to report that GUI access to files (from MsWord) seems to work, but indeed the problem is there and it is still to solve.

The place to report that something is still a problem is in the relevant bug report. http://bugs.winehq.org/show_bug.cgi?id=19385