http://bugs.winehq.org/show_bug.cgi?id=23319
Jason Edmeades us@edmeades.me.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |us@edmeades.me.uk
--- Comment #2 from Jason Edmeades us@edmeades.me.uk 2010-06-24 09:30:07 --- Interesting testing this with procmon... If the first token is not followed by a whitespace, it will attempt to open a program with that name in the current working directory, then it will check for internal programs with that name,... for example: shift - doesnt look at local file system shift.exe - looks for 'shift.exe' locally, then matches 'shift' internal cd - doesnt look at local file system cd.exe - looks for 'cd.exe' in local dir, then matches 'cd' internal command with parameter ".exe" (eg. mk .exe, cd.exe) fred.exe - searches current dir for fred.exe then goes off on locate searching (eg. for fred.exe.* locally, then searching the path)
So overall, if we match the internal command, and the next token is a not a whitespace, see if there is a <first token> file in the current directory, and if there is then run it otherwise drop into the internal command processind