From: On Behalf Of Ingo Karkat > On 16-Feb-2012 16:15, MacDonald, Stuart wrote: > > I say an option is the correct way; make 32-bit vim operate "normally" > > but allow it to see past the redirection if that's needed. > > From http://www.vim.org/download.php#pc: > > > Native 64-bit binaries for MS-Windows can be found at > > http://code.google.com/p/vim-win3264/. The Win32 binaries should run > > too, but the 64 bit version has a few minor advantages (see the web > page > > at the link).
And at the link you find that there are a few disadvantages too: - Command-line installer - Not supported; not well tested. Also, I prefer to get official vim.org releases. > I guess avoiding the file system redirection is one of the "few minor > advantages" the text hints at. I've been using the 64-bit version on Possibly. It's not clear to me if 64-bit native apps see the whole raw filesystem on 64-bit Windows, or if they see the 64-bit view of the filesystem. > Windows 7 > without problems. To me, this is too little of an issue (and, as this Vim has many features, and I could say that all the ones I don't use are too little of an issue to have been implemented. Nevertheless they were. Ultimately, it's Bram's call. However, 32-bit vim cannot interact with parts of the Win 64-bit filesystem without this. That makes it worthwhile all by itself IMHO. ...Stu -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
