"Vincent Povirk" madewokherd+d41d@gmail.com writes:
My last attempt created a new winelib program; apparently this functionality fits in explorer.
start.exe is probably more appropriate. Either way you are trying to make it too smart; it should take a straight Unix path, and not try to guess anything.
My understanding is that start.exe will not work because it must be compatible with the windows version of start. In any case, I don't think I could usefully share code with the rest of start.
Attempting to guess between unix and windows paths is not necessary (I saw no reason not to do it, but I can remove it).
I would like to keep the distinction between .exe and other files so that bug 5368 can be fixed.
On Wed, Mar 26, 2008 at 8:50 AM, Alexandre Julliard julliard@winehq.org wrote:
"Vincent Povirk" madewokherd+d41d@gmail.com writes:
My last attempt created a new winelib program; apparently this functionality fits in explorer.
start.exe is probably more appropriate. Either way you are trying to make it too smart; it should take a straight Unix path, and not try to guess anything.
-- Alexandre Julliard julliard@winehq.org
"Vincent Povirk" madewokherd+d41d@gmail.com writes:
My understanding is that start.exe will not work because it must be compatible with the windows version of start. In any case, I don't think I could usefully share code with the rest of start.
It has to be compatible, but adding new options that don't exist on Windows shouldn't be a problem. That's what you'd have to do in explorer too anyway.
I would like to keep the distinction between .exe and other files so that bug 5368 can be fixed.
I'm not sure I understand why you need that for 5368.
On Wed, Mar 26, 2008 at 10:04 AM, Alexandre Julliard julliard@winehq.org wrote:
"Vincent Povirk" madewokherd+d41d@gmail.com writes:
My understanding is that start.exe will not work because it must be compatible with the windows version of start. In any case, I don't think I could usefully share code with the rest of start.
It has to be compatible, but adding new options that don't exist on Windows shouldn't be a problem. That's what you'd have to do in explorer too anyway.
Ok, I'll have to look at this in more detail when I am at home.
I would like to keep the distinction between .exe and other files so that bug 5368 can be fixed.
I'm not sure I understand why you need that for 5368.
It's more the combination of 5224 and 5368.
5224 requires quotes around the exe filename in the command line, even if the filename contains no spaces. ShellExecuteEx does not let me put in the quotes. I think I tested start.exe on windows and it also did not let me add quotes, but I will check again.
5368 isn't very clear (someone apparently wants to make windows file associations somehow work like those on Linux), but it seems like it could be partially solved by having something that users can open non-exe files with in nautilus to start it with the file association in wine. I think it makes sense from a user perspective to do this by starting them with "wine". For that to work, nautilus needs to be able to start them with the same method as exe files.
I don't think starting non-exe files should be considered a separate feature. wine.desktop really should do what windows explorer would do, and that's the problem I want to solve here.