https://bugs.winehq.org/show_bug.cgi?id=38468
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |fgouget@codeweavers.com Ever confirmed|0 |1
--- Comment #1 from François Gouget fgouget@codeweavers.com --- I have collected some data on this.
/run/user/<UID>/smb-share:server=hostname,share=sharename/
In the path below '/run/user/<UID>' is the gvfs mount point and 'smb-share:server=hostname,share=sharename' is a virtual directory created by gvfs when one 'mounts' the corresponding Samba share.
So I'm not sure Wine would get a notification when the 'smb-share:...' directory gets created. Still the gvfs documentation says that it uses UDisks2 and the source code does contain quite a few references to UDisks2. So there's hope that Wine can turn these into drive letters and thus 'hide' the colon in the path.
Another point has to do with the error one gets when double-clicking on a filename containing a colon in the File -> Open dialog. It comes from a check in the first lines of FILEDLG95_ValidatePathAction() in dlls/comdlg32/filedlg.c. Removing that check makes it possible to open a filenames containing a colon in Wine's notepad application. But Excel 2000 still refuses to open such filenames. So either there are other checks elsewhere, or Excel itself does not deal well with such filenames. So it seems there's no single-line hack that would workaround this issue for most applications.
Any 'path mangling' approach would obviously have to be done at a much lower level. Maybe it could leverage the short vs. long filename support but that's not clear.