Mercurial > vim

comparison runtime/doc/os_win32.txt @ 10048:43efa4f5a8ea

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
commit https://github.com/vim/vim/commit/89bcfda6834aba724d12554a34b9ed49f5789fd5 Author: Bram Moolenaar <Bram@vim.org> Date: Tue Aug 30 23:26:57 2016 +0200 Updated runtime files. Remove version checks for Vim older than 6.0.
author Christian Brabandt <cb@256bit.org>
date Tue, 30 Aug 2016 23:30:09 +0200
parents 4c6ad81d41fe
children 9f48eab77d62
comparison
equal deleted inserted replaced
10047:a62862410ca1 10048:43efa4f5a8ea
1 *os_win32.txt* For Vim version 7.4. Last change: 2016 Mar 05 1 *os_win32.txt* For Vim version 7.4. Last change: 2016 Aug 28
2 2
3 3
4 VIM REFERENCE MANUAL by George Reilly 4 VIM REFERENCE MANUAL by George Reilly
5 5
6 6
142 142
143 ============================================================================== 143 ==============================================================================
144 5. Running under Windows 3.1 *win32-win3.1* 144 5. Running under Windows 3.1 *win32-win3.1*
145 145
146 *win32s* *windows-3.1* 146 *win32s* *windows-3.1*
147 There is a special version of Gvim that runs under Windows 3.1 and 3.11. You 147 There was a special version of Gvim that runs under Windows 3.1 and 3.11.
148 need the gvim.exe that was compiled with Visual C++ 4.1. 148 Support was removed in patch 7.4.1363.
149
150 To run the Win32 version under Windows 3.1, you need to install Win32s. You
151 might have it already from another Win32 application which you have installed.
152 If Vim doesn't seem to be running properly, get the latest version: 1.30c.
153 You can find it at:
154
155 http://support.microsoft.com/download/support/mslfiles/pw1118.exe
156
157 (Microsoft moved it again, we don't know where it is now :-( ).
158
159 The reason for having two versions of gvim.exe is that the Win32s version was
160 compiled with VC++ 4.1. This is the last version of VC++ that supports Win32s
161 programs. VC++ 5.0 is better, so that one was used for the Win32 version.
162 Apart from that, there is no difference between the programs. If you are in a
163 mixed environment, you can use the gvim.exe for Win32s on both.
164
165 The Win32s version works the same way as the Win32 version under 95/NT. When
166 running under Win32s the following differences apply:
167 - You cannot use long file names, because Windows 3.1 doesn't support them!
168 - When executing an external command, it doesn't return an exit code. After
169 doing ":make" you have to do ":cn" yourself.
170 149
171 ============================================================================== 150 ==============================================================================
172 6. Win32 mini FAQ *win32-faq* 151 6. Win32 mini FAQ *win32-faq*
173 152
174 Q. Why does the Win32 version of Vim update the screen so slowly on Windows 95? 153 Q. Why does the Win32 version of Vim update the screen so slowly on Windows 95?