From: On Behalf Of Ben Fritz
> Any ideas here what might be going on? I was able to get Vim to use
> chcp.com only by copying it from the System32 directory into
> $VIMRUNTIME. I think this is NOT a good way to fix the problem. As
> soon as Vim 7.4 or 8.0 comes out the workaround will stop working.
>
> Yes, my $PATH contains the system32 directory.
>
> C:\eclim-git\eclim>dir C:\WINDOWS\system32\*.com
> Volume in drive C is Local Disk
> Volume Serial Number is EA9A-15F2
>
> Directory of C:\WINDOWS\system32
>
> 02/18/2007 06:00 AM 9,216 chcp.com
> 02/18/2007 06:00 AM 12,288 diskcomp.com
> 02/18/2007 06:00 AM 9,728 diskcopy.com
> 02/18/2007 06:00 AM 30,720 format.com
> 02/18/2007 06:00 AM 43,008 mode.com
> 02/18/2007 06:00 AM 25,088 more.com
> 02/18/2007 06:00 AM 17,408 tree.com
> 7 File(s) 147,456 bytes
> 0 Dir(s) 181,770,612,736 bytes free
>
> C:\eclim-git\eclim>"C:\Program Files (x86)\vim\vim73\vim.exe" -N -u
^^^^^^^^^^^^^^^^^^^
64-bit Windows versions (Win 7) contain a bunch of filesystem
redirections so that 32 bit apps can believe they are on a 32 OS and
be happy, and 64 bit apps get the same treatment. What you are seeing
is almost certainly a result of those redirections, as vim is a 32-bit
app.
I'm not a Windows programmer, but I understand there are special new
windows calls that will give the raw situation if the app really wants
it.
A couple of quick links:
http://msdn.microsoft.com/en-us/library/aa384187(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365743(v=vs.85).aspx
...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
