I'm having a weird issue with gvim on Windows 7 64-bit. I am using gvim 7.2, and the "c:\windows\gvim.bat" is the executable that is first on my path if I just type "gvim" on the powershell command line. Note that I've tried both the gvim.bat file and calling gvim.exe directly.
For some reason, there is a certain directory on my file system which vim does not seem to see or recognize. I can navigate to this directory in cmd, powershell, windows explorer, etc., and I can see the files in the directory. I can also edit the files in notepad or another text editor, but if I try to open any of the files in gvim, it does not open the file, but rather reports "[New DIRECTORY]". If I try to open the folder itself in gvim, it does not open it in the vim directory browser as I would expect, but instead it reports "[New FILE]".
If I open gvim, and do File->Open... and navigate to where the folder should be, it is not visible in the open file dialog.
What would cause a directory (or files) to not be visible or recognized by gvim?
Note that the directory I'm having problems with is the PowerShellCommunityExtensions module. I currently have this installed here: "c:\windows\system32\WindowsPowerShell\v1.0\Modules\Pscx\". The Pscx folder is the one that gvim will not recognize. I have other modules in this Modules folder which gvim can open success开发者_StackOverflowfully.
Apparently GVIM.exe is a 32-bit app that appears to Windows 7 as a legacy app which causes Windows Vista/7 to virtualize access to the file system and registry. Access to C:\Windows\System32 is redirected to C:\Windows\SysWOW4. Writes to C:\Program Files are redirected to C:\ProgramData or C:\Users\\AppData\Local\VirtualStore. And access to the registry node HKLM:\Software is redirected to HKLM:\Software\Wow6432Node. The following MS Support URL explains it a bit further.
精彩评论