Le 13 nov. 08 à 04:13, Ben Schmidt a écrit :
> >> I'm using a custom-compiled GVim now strictly for this reason, but I >> really do wish that MacVim were set up this way. Why do you guys not >> acknowledge a user's PATH? GVim works otherwise on Windows and Linux. > > Why do people not understand how environment variables work? This is > not > to do with Gvim, but the system. The place to set environment > variables > on the Mac for GUI applications (those started via loginwindow, the > Finder, etc.) is ~/.MacOSX/environment.plist > > http://developer.apple.com/qa/qa2001/qa1067.html > > Just like on Windows you set environment variables in a standard > system > place (System properties) you do the same on the Mac; it's just a > different place. On Linux, it's a different place again: you alter > your > shell startup files, because everything, including the window manager, > usually, is started via a shell. > > However, it seems many people on the Mac don't understand this, but > alter their shell startup files and expect every other app to somehow > magically pick up the variables even though they are not started via a > shell. Because this is the way most Unices do. And setting env variables in the preferences isn't half as flexible as with a shell startup script, which I (and others) are pretty used to editing, pre- or appending stuff to the $PATH and other variables thanks to shell expansion. Not executing a shell by default is a design decision from Apple, but wrt the way Unices behave, and what people expect generally, it might not be the brightest they had. Or did I miss something? David --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
