https://bugs.winehq.org/show_bug.cgi?id=56114
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #5 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
I have to agree with the user on that one.
I can create a D: drive pointing to the absolute path of the WINEPREFIX directory itself by typing it in the input field, and I can run notepad with: $ wine start 'D:\drive_c\windows\notepad.exe'
The same thing can't be achieved using the Unix browser dialog.
You say that it's on purpose, to avoid a potential recursion issue.
If that recursion issue could only affect the Unix browser dialog itself, and using the WINEPREFIX as a drive path is not at risk, then that Unix browser 'feature' just hinders the selection of the drive path for an unrelated reason, and it should be reworked with a proper fix that would allow selecting a path in the WINEPREFIX while avoiding recursion issues. That would be a valid issue.
If using the WINEPREFIX as a drive path may also result in that recursion issue you want to avoid, then such a path should also be rejected when manually typed into the field, not just in the Unix browser dialog, otherwise the purpose of the Unix browser 'feature' is defeated. That would also be a valid issue.
So, please, clarify: Does the recursion issue that is prevented by the 'feature' only affects the Unix browser dialog itself, or does it potentially affects the use of the WINEPREFIX as the drive path?
Regards.