http://bugs.winehq.org/show_bug.cgi?id=21513
Summary: Option to not inherit the UNIX environment Product: Wine Version: 1.1.37 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: dima@gmail.com
The Perforce command-line client (p4.exe) breaks because of a few environment variables that Wine inherits from the OS:
PWD: Doesn't even exist in Windows, and yet, p4 reads it and gets confused because it's a UNIX path, not a win32 one. P4EDITOR: I have it set to "nano", which makes sense for the Linux p4, but not the Windows one. P4DIFF: same as above.
p4 breaks the same way in WinXP if I set PWD to a UNIX-like path.
Since just about any UNIX environment variable can potentially break a Windows program, it would be nice to have an option to start programs with just the Windows environment. (While it's possible to run "env -i wine ...", that has some disadvantages: variables such as HOME, PATH, and DISPLAY need to be set, since they're required by Wine; if Wine starts a native program, that program won't get the original UNIX environment.)
Similarly, if Wine starts a native program, that program shouldn't inherit the Windows environment.