Mercurial > vim
annotate runtime/doc/os_vms.txt @ 18687:81d34044450f v8.1.2335
patch 8.1.2335: error message for function arguments may use NULL pointer
Commit: https://github.com/vim/vim/commit/2118a302957dea352174722bf355376901f49b9b
Author: Bram Moolenaar <Bram@vim.org>
Date: Fri Nov 22 19:29:45 2019 +0100
patch 8.1.2335: error message for function arguments may use NULL pointer
Problem: Error message for function arguments may use NULL pointer.
(Coverity)
Solution: Use the original function name.
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Fri, 22 Nov 2019 19:30:05 +0100 |
| parents | fe57e4f0eac1 |
| children | af69c9335223 |
| rev | line source |
|---|---|
| 15729 | 1 *os_vms.txt* For Vim version 8.1. Last change: 2019 Jan 29 |
| 7 | 2 |
| 3 | |
| 4 VIM REFERENCE MANUAL | |
| 5 | |
| 6 | |
| 7 *VMS* *vms* | |
| 8 This file contains the particularities for the VMS version of Vim. | |
| 9 You can reach this information file by typing :help VMS in Vim command | |
| 10 prompt. | |
| 11 | |
| 12 1. Getting started |vms-started| | |
| 13 2. Download files |vms-download| | |
| 14 3. Compiling |vms-compiling| | |
| 15 4. Problems |vms-problems| | |
| 16 5. Deploy |vms-deploy| | |
| 17 6. Practical usage |vms-usage| | |
| 18 7. GUI mode questions |vms-gui| | |
| 19 8. Useful notes |vms-notes| | |
| 20 9. VMS related changes |vms-changes| | |
| 21 10. Authors |vms-authors| | |
| 22 | |
| 23 ============================================================================== | |
| 24 | |
| 25 1. Getting started *vms-started* | |
| 26 | |
| 5340 | 27 Vim (Vi IMproved) is a Vi-compatible text editor that runs on nearly every |
| 7 | 28 operating system known to humanity. Now use Vim on OpenVMS too, in character |
| 29 or X/Motif environment. It is fully featured and absolutely compatible with | |
| 30 Vim on other operating systems. | |
| 31 | |
| 32 ============================================================================== | |
| 33 | |
| 34 2. Download files *vms-download* | |
| 35 | |
| 36 You can download the Vim source code by ftp from the official Vim site: | |
| 37 ftp://ftp.vim.org/pub/vim/ | |
| 38 Or use one of the mirrors: | |
| 39 ftp://ftp.vim.org/pub/vim/MIRRORS | |
| 40 | |
| 41 You can download precompiled executables from: | |
| 42 http://www.polarhome.com/vim/ | |
| 43 ftp://ftp.polarhome.com/pub/vim/ | |
| 44 | |
| 45 To use the precompiled binary version, you need one of these archives: | |
| 46 | |
| 412 | 47 vim-XX-exe-ia64-gui.zip IA64 GUI/Motif executables |
| 48 vim-XX-exe-ia64-gtk.zip IA64 GUI/GTK executables | |
| 49 vim-XX-exe-ia64-term.zip IA64 console executables | |
| 856 | 50 vim-XX-exe-axp-gui.zip Alpha GUI/Motif executables |
| 51 vim-XX-exe-axp-gtk.zip Alpha GUI/GTK executables | |
| 412 | 52 vim-XX-exe-axp-term.zip Alpha console executables |
| 7 | 53 vim-XX-exe-vax-gui.zip VAX GUI executables |
| 54 vim-XX-exe-vax-term.zip VAX console executables | |
| 55 | |
| 701 | 56 and of course (optional) |
| 7 | 57 vim-XX-runtime.zip runtime files |
| 58 | |
| 412 | 59 The binary archives contain: vim.exe, ctags.exe, xxd.exe files. |
| 7 | 60 |
| 856 | 61 For GTK executables you will need GTKLIB that is available for |
| 701 | 62 Alpha and IA64 platform. |
| 63 | |
| 7 | 64 ============================================================================== |
| 65 | |
| 66 3. Compiling *vms-compiling* | |
| 67 | |
| 68 See the file [.SRC]INSTALLVMS.TXT. | |
| 69 | |
| 70 ============================================================================== | |
| 71 | |
| 72 4. Problems *vms-problems* | |
| 73 | |
| 412 | 74 The code has been tested under Open VMS 6.2 - 8.2 on Alpha, VAX and IA64 |
| 3082 | 75 platforms with the DEC C compiler. It should work without big problems. |
| 236 | 76 If your system does not have some include libraries you can tune up in |
| 77 OS_VMS_CONF.H file. | |
| 7 | 78 |
| 79 If you decided to build Vim with +perl, +python, etc. options, first you need | |
| 236 | 80 to download OpenVMS distributions of Perl and Python. Build and deploy the |
| 81 libraries and change adequate lines in MAKE_VMS.MMS file. There should not be | |
| 82 a problem from Vim side. | |
| 7 | 83 |
| 412 | 84 Also GTK, XPM library paths should be configured in MAKE_VMS.MMS |
| 85 | |
| 236 | 86 Note: Under VAX it should work with the DEC C compiler without problems. The |
| 87 VAX C compiler is not fully ANSI C compatible in pre-processor directives | |
| 3082 | 88 semantics, therefore you have to use a converter program that will do the lion |
| 236 | 89 part of the job. For detailed instructions read file INSTALLvms.txt |
| 7 | 90 |
| 3082 | 91 MMS_VIM.EXE is build together with VIM.EXE, but for XXD.EXE you should |
| 92 change to a subdirectory and build it separately. | |
| 7 | 93 |
| 236 | 94 CTAGS is not part of the Vim source distribution anymore, however the OpenVMS |
| 95 specific source might contain CTAGS source files as described above. | |
| 7 | 96 You can find more information about CTAGS on VMS at |
| 97 http://www.polarhome.com/ctags/ | |
| 98 | |
|
2207
b17bbfa96fa0
Add the settabvar() and gettabvar() functions.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
99 Advanced users may try some acrobatics in FEATURE.H file as well. |
| 7 | 100 |
| 101 It is possible to compile with +xfontset +xim options too, but then you have | |
| 236 | 102 to set up GUI fonts etc. correctly. See :help xim from Vim command prompt. |
| 7 | 103 |
| 104 You may want to use GUI with GTK icons, then you have to download and install | |
| 105 GTK for OpenVMS or at least runtime shareable images - LIBGTK from | |
| 106 polarhome.com | |
| 15640 | 107 Post 7.2 Vim uses GTK2+ while the last GTK on OpenVMS is 1.2.10, therefore |
| 15729 | 108 the GTK build is no longer available. |
| 7 | 109 |
| 110 For more advanced questions, please send your problem to Vim on VMS mailing | |
| 111 list <vim-vms@polarhome.com> | |
| 112 More about the vim-vms list can be found at: | |
| 113 http://www.polarhome.com/mailman/listinfo/vim-vms | |
| 114 | |
| 115 ============================================================================== | |
| 116 | |
| 117 5. Deploy *vms-deploy* | |
| 118 | |
| 119 Vim uses a special directory structure to hold the document and runtime files: | |
| 120 | |
| 121 vim (or wherever) | |
| 122 |- tmp | |
| 123 |- vim57 | |
| 124 |----- doc | |
| 125 |----- syntax | |
| 701 | 126 |- vim62 |
| 7 | 127 |----- doc |
| 128 |----- syntax | |
| 701 | 129 |- vim64 |
| 7 | 130 |----- doc |
| 131 |----- syntax | |
| 132 vimrc (system rc files) | |
| 133 gvimrc | |
| 134 | |
| 135 Use: > | |
| 136 | |
| 137 define/nolog VIM device:[path.vim] | |
| 138 define/nolog VIMRUNTIME device:[path.vim.vim60] | |
| 139 define/nolog TMP device:[path.tmp] | |
| 140 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
141 To get vim.exe to find its document, filetype, and syntax files, and to |
| 236 | 142 specify a directory where temporary files will be located. Copy the "runtime" |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
143 subdirectory of the Vim distribution to vimruntime. |
| 7 | 144 |
| 145 Logicals $VIMRUNTIME and $TMP are optional. | |
| 146 | |
| 147 If $VIMRUNTIME is not set, Vim will guess and try to set up automatically. | |
| 236 | 148 Read more about it at :help runtime |
| 7 | 149 |
| 150 If $TMP is not set, you will not be able to use some functions as CTAGS, | |
| 151 XXD, printing etc. that use temporary directory for normal operation. | |
| 236 | 152 The $TMP directory should be readable and writable by the user(s). |
| 153 The easiest way to set up $TMP is to define a logical: > | |
| 7 | 154 |
| 155 define/nolog TMP SYS$SCRATCH | |
| 156 or as: > | |
| 157 define/nolog TMP SYS$LOGIN | |
| 158 | |
| 159 ============================================================================== | |
| 160 | |
| 161 6. Practical usage *vms-usage* | |
| 162 | |
| 163 Usually, you want to run just one version of Vim on your system, therefore | |
| 164 it is enough to dedicate one directory for Vim. | |
| 236 | 165 Copy the whole Vim runtime directory structure to the deployment position. |
| 7 | 166 Add the following lines to your LOGIN.COM (in SYS$LOGIN directory). |
| 236 | 167 Set up the logical $VIM as: > |
| 7 | 168 |
| 169 $ define VIM device:<path> | |
| 170 | |
| 171 Set up some symbols: > | |
| 172 | |
| 173 $ ! vi starts Vim in chr. mode. | |
| 174 $ vi*m :== mcr VIM:VIM.EXE | |
| 175 | |
| 176 $ !gvi starts Vim in GUI mode. | |
| 177 $ gv*im :== spawn/nowait mcr VIM:VIM.EXE -g | |
| 178 | |
| 179 Please, check the notes for customization and configuration of symbols. | |
| 180 | |
| 181 You may want to create .vimrc and .gvimrc files in your home directory | |
| 182 (SYS$LOGIN) to overwrite default settings. | |
| 183 | |
| 236 | 184 The easiest way is just rename example files. You may leave the menu file |
| 185 (MENU.VIM) and files vimrc and gvimrc in the original $VIM directory. It will | |
| 3082 | 186 be the default setup for all users, and for users it is enough to just have |
| 187 their own additions or resetting in their home directory in files .vimrc and | |
| 188 .gvimrc. It should work without problems. | |
| 7 | 189 |
| 236 | 190 Note: Remember, system rc files (default for all users) don't have a leading |
| 191 ".". So, system rc files are: > | |
| 7 | 192 |
| 193 $VIM:vimrc | |
| 194 $VIM:gvimrc | |
| 195 $VIM:menu.vim | |
| 196 | |
| 236 | 197 and user customized rc files are: > |
| 7 | 198 |
| 199 sys$login:.vimrc | |
| 200 sys$login:.gvimrc | |
| 201 | |
| 3082 | 202 You can check that everything is at the right place with the :version command. |
| 7 | 203 |
| 204 Example LOGIN.COM: > | |
| 205 | |
|
15533
08604d82fc9e
patch 8.1.0774: VMS build is missing the blob file
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
206 $ define/nolog VIM DKA0:[UTIL.VIM81] |
| 7 | 207 $ vi*m :== mcr VIM:VIM.EXE |
| 208 $ gv*im:== spawn/nowait/input=NLA0 mcr VIM:VIM.EXE -g -GEOMETRY 80x40 | |
|
15533
08604d82fc9e
patch 8.1.0774: VMS build is missing the blob file
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
209 $ set disp/create/node=192.168.10.202/trans=tcpip |
| 7 | 210 |
| 3082 | 211 Note: This set-up should be enough, if you are working on a standalone server or |
| 212 clustered environment, but if you want to use Vim as an internode editor in | |
| 236 | 213 DECNET environment, it will satisfy as well. |
| 7 | 214 You just have to define the "whole" path: > |
| 215 | |
| 216 $ define VIM "<server_name>[""user password""]::device:<path>" | |
| 217 $ vi*m :== "mcr VIM:VIM.EXE" | |
| 218 | |
| 3082 | 219 For example: > |
| 7 | 220 |
| 221 $ define VIM "PLUTO::RF10:[UTIL.VIM]" | |
| 222 $ define VIM "PLUTO""ZAY mypass""::RF10:[UTIL.VIM]" ! if passwd required | |
| 223 | |
| 236 | 224 You can also use the $VIMRUNTIME logical to point to the proper version of Vim |
| 225 if you have installed more versions at the same time. If $VIMRUNTIME is not | |
| 226 defined Vim will borrow its value from the $VIM logical. You can find more | |
| 227 information about the $VIMRUNTIME logical by typing :help runtime as a Vim | |
| 228 command. | |
| 7 | 229 |
| 230 System administrators might want to set up a system wide Vim installation, | |
| 231 then add to the SYS$STARTUP:SYLOGICALS.COM > | |
| 232 | |
| 233 $ define/nolog/sys VIM device:<path> | |
| 234 $ define/nolog/sys TMP SYS$SCRATCH | |
| 235 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
236 And to the SYS$STARTUP:SYLOGIN.COM > |
| 7 | 237 |
| 238 $ vi*m :== mcr VIM:VIM.EXE | |
| 239 $ gv*im:== spawn/nowait/input=NLA0 mcr VIM:VIM.EXE -g -GEOMETRY 80x40 | |
| 240 | |
| 241 | |
| 236 | 242 It will set up a normal Vim work environment for every user on the system. |
| 7 | 243 |
| 701 | 244 IMPORTANT: Vim on OpenVMS (and on other case insensitive system) command line |
| 1120 | 245 parameters are assumed to be lowercase. In order to indicate that a command |
| 701 | 246 line parameter is uppercase "/" sign must be used. |
| 247 | |
| 248 Examples: | |
| 249 > | |
| 250 vim -R filename ! means: -r List swap files and exit | |
| 856 | 251 vim -/r filename ! means: -R Readonly mode (like "view") |
| 252 vim -u <vimrc> ! means: -u Use <vimrc> instead of any .vimrc | |
| 253 vim -/u <gvimrc> ! means: -U Use <gvimrc> instead of any .gvimrc | |
| 254 | |
| 7 | 255 ============================================================================== |
| 256 | |
| 257 7. GUI mode questions *vms-gui* | |
| 258 | |
| 236 | 259 OpenVMS is a real mainframe OS, therefore even if it has a GUI console, most |
| 260 of the users do not use a native X/Window environment during normal operation. | |
| 261 It is not possible to start Vim in GUI mode "just like that". But anyhow it | |
| 262 is not too complicated either. | |
| 7 | 263 |
| 236 | 264 First of all: you will need an executable that is built with the GUI enabled. |
| 7 | 265 |
| 266 Second: you need to have installed DECW/Motif on your VMS server, otherwise | |
| 267 you will get errors that some shareable libraries are missing. | |
| 268 | |
| 236 | 269 Third: If you choose to run Vim with extra features such as GUI/GTK then you |
| 270 need a GTK installation too or at least a GTK runtime environment (LIBGTK | |
| 412 | 271 can be downloaded from http://www.polarhome.com/vim/). |
| 7 | 272 |
| 273 1) If you are working on the VMS X/Motif console: | |
| 274 Start Vim with the command: > | |
| 275 | |
| 276 $ mc device:<path>VIM.EXE -g | |
| 277 < | |
| 236 | 278 or type :gui as a command to the Vim command prompt. For more info :help |
| 279 gui | |
| 7 | 280 |
| 236 | 281 2) If you are working on some other X/Window environment like Unix or a remote |
| 282 X VMS console. Set up display to your host with: > | |
| 7 | 283 |
| 284 $ set disp/create/node=<your IP address>/trans=<transport-name> | |
| 285 < | |
| 236 | 286 and start Vim as in point 1. You can find more help in VMS documentation or |
| 7 | 287 type: help set disp in VMS prompt. |
| 288 Examples: > | |
| 289 | |
| 290 $ set disp/create/node=192.168.5.159 ! default trans is DECnet | |
| 291 $ set disp/create/node=192.168.5.159/trans=tcpip ! TCP/IP network | |
| 292 $ set disp/create/node=192.168.5.159/trans=local ! display on the same node | |
| 293 | |
| 294 Note: you should define just one of these. | |
| 295 For more information type $help set disp in VMS prompt. | |
| 296 | |
| 297 3) Another elegant solution is XDM if you have installed on OpenVMS box. | |
| 298 It is possible to work from XDM client as from GUI console. | |
| 299 | |
| 236 | 300 4) If you are working on MS-Windows or some other non X/Window environment |
| 301 you need to set up one X server and run Vim as in point 2. | |
| 3082 | 302 For MS-Windows there are available free X servers as MIX, Omni X etc., |
| 7 | 303 as well as excellent commercial products as eXcursion or ReflectionX with |
| 236 | 304 built-in DEC support. |
| 7 | 305 |
| 306 Please note, that executables without GUI are slightly faster during startup | |
| 3082 | 307 than with enabled GUI in character mode. Therefore, if you do not use GUI |
| 7 | 308 features, it is worth to choose non GUI executables. |
| 309 | |
| 310 ============================================================================== | |
| 311 | |
| 312 8. Useful notes *vms-notes* | |
| 313 | |
| 1709 | 314 8.1 Backspace/delete |
| 7 | 315 8.2 Filters |
| 316 8.3 VMS file version numbers | |
| 317 8.4 Directory conversion | |
| 318 8.5 Remote host invocation | |
| 319 8.6 Terminal problems | |
| 320 8.7 Hex-editing and other external tools | |
| 321 8.8 Sourcing vimrc and gvimrc | |
| 322 8.9 Printing from Vim | |
| 323 8.10 Setting up the symbols | |
| 324 8.11 diff and other GNU programs | |
| 325 8.12 diff-mode | |
| 326 8.13 Allow '$' in C keywords | |
| 327 8.14 VIMTUTOR for beginners | |
| 3082 | 328 8.15 Slow start in console mode issue |
| 329 8.16 Common VIM directory - different architectures | |
| 7 | 330 |
| 1709 | 331 8.1 Backspace/delete |
| 7 | 332 |
| 333 There are backspace/delete key inconsistencies with VMS. | |
| 334 :fixdel doesn't do the trick, but the solution is: > | |
| 335 | |
| 336 :inoremap ^? ^H " for terminal mode | |
| 337 :inoremap <Del> ^H " for gui mode | |
| 338 | |
| 339 Read more in ch: 8.6 (Terminal problems). | |
| 340 (Bruce Hunsaker <BNHunsaker@chq.byu.edu> Vim 5.3) | |
| 341 | |
| 342 | |
| 343 8.2 Filters | |
| 344 | |
| 236 | 345 Vim supports filters, i.e., if you have a sort program that can handle |
| 7 | 346 input/output redirection like Unix (<infile >outfile), you could use > |
| 347 | |
| 348 :map \s 0!'aqsort<CR> | |
| 349 | |
| 350 (Charles E. Campbell, Jr. <cec@gryphon.gsfc.nasa.gov> Vim 5.4) | |
| 351 | |
| 352 | |
| 353 8.3 VMS file version numbers | |
| 354 | |
| 355 Vim is saving files into a new file with the next higher file version | |
| 356 number, try these settings. > | |
| 357 | |
| 358 :set nobackup " does not create *.*_ backup files | |
| 236 | 359 :set nowritebackup " does not have any purpose on VMS. It's the |
| 856 | 360 " default. |
| 7 | 361 |
| 3082 | 362 Recovery is working perfectly as well from the default swap file. |
| 7 | 363 Read more with :help swapfile |
| 364 | |
| 365 (Claude Marinier <ClaudeMarinier@xwavesolutions.com> Vim 5.5, Zoltan Arpadffy | |
| 236 | 366 Vim 5.6) |
| 7 | 367 |
| 368 | |
| 369 8.4 Directory conversion | |
| 370 | |
| 371 Vim will internally convert any unix-style paths and even mixed unix/VMS | |
| 236 | 372 paths into VMS style paths. Some typical conversions resemble: |
| 7 | 373 |
| 374 /abc/def/ghi -> abc:[def]ghi. | |
| 375 /abc/def/ghi.j -> abc:[def]ghi.j | |
| 376 /abc/def/ghi.j;2 -> abc:[def]ghi.j;2 | |
| 377 /abc/def/ghi/jkl/mno -> abc:[def.ghi.jkl]mno. | |
| 378 abc:[def.ghi]jkl/mno -> abc:[def.ghi.jkl]mno. | |
| 379 ./ -> current directory | |
| 380 ../ -> relative parent directory | |
| 381 [.def.ghi] -> relative child directory | |
| 382 ./def/ghi -> relative child directory | |
| 383 | |
| 384 Note: You may use <,> brackets as well (device:<path>file.ext;version) as | |
| 385 rf10:<user.zay.work>test.c;1 | |
| 386 | |
| 387 (David Elins <delins@foliage.com>, Jerome Lauret | |
| 3082 | 388 <JLAURET@mail.chem.sunysb.edu> Vim 5.6) |
| 7 | 389 |
| 390 | |
| 391 8.5 Remote host invocation | |
| 392 | |
| 393 It is possible to use Vim as an internode editor. | |
| 394 1. Edit some file from remote node: > | |
| 395 | |
| 396 vi "<server>""username passwd""::<device>:<path><filename>;<version>" | |
| 397 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
398 Example: > |
| 7 | 399 vi "pluto""zay passwd""::RF10:<USER.ZAY.WORK>TEST.C;1" |
| 400 | |
| 401 Note: syntax is very important, otherwise VMS will recognize more parameters | |
| 402 instead of one (resulting with: file not found) | |
| 403 | |
| 236 | 404 2. Set up Vim as your internode editor. If Vim is not installed on your |
| 405 host, just set up your IP address, the full Vim path including the server name | |
| 406 and run the command procedure below: > | |
| 7 | 407 |
| 408 $ if (p1 .eqs. "") .OR. (p2 .eqs. "") then goto usage | |
| 409 $ set disp/create/node=<your_IP_here>/trans=tcpip | |
| 410 $ define "VIM "<vim_server>""''p1' ''p2'""::<device>:<vim_path>" | |
| 411 $ vi*m :== "mcr VIM:VIM.EXE" | |
| 412 $ gv*im :== "spawn/nowait mcr VIM:VIM.EXE -g" | |
| 413 $ goto end | |
| 414 $ usage: | |
| 415 $ write sys$output " Please enter username and password as a parameter." | |
| 416 $ write sys$output " Example: @SETVIM.COM username passwd" | |
| 417 $ end: | |
| 418 | |
| 236 | 419 Note: Never use it in a clustered environment (you do not need it), loading |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
420 could be very-very slow, but even faster than a local Emacs. :-) |
| 7 | 421 |
| 422 (Zoltan Arpadffy, Vim 5.6) | |
| 423 | |
| 424 | |
| 425 8.6 Terminal problems | |
| 426 | |
| 427 If your terminal name is not known to Vim and it is trying to find the default | |
| 428 one you will get the following message during start-up: | |
| 429 --- | |
| 430 Terminal entry not found in termcap | |
| 236 | 431 'unknown-terminal' not known. Available built-in terminals are: |
| 7 | 432 builtin_gui |
| 433 builtin_riscos | |
| 434 builtin_amiga | |
| 435 builtin_beos-ansi | |
| 436 builtin_ansi | |
| 437 builtin_vt320 | |
| 438 builtin_vt52 | |
| 439 builtin_pcansi | |
| 440 builtin_win32 | |
| 441 builtin_xterm | |
| 442 builtin_iris-ansi | |
| 443 builtin_debug | |
| 444 builtin_dumb | |
| 445 defaulting to 'vt320' | |
| 446 --- | |
| 3082 | 447 The solution is to define the default terminal name: > |
| 7 | 448 |
| 236 | 449 $ ! unknown terminal name. Let us use vt320 or ansi instead. |
| 7 | 450 $ ! Note: it's case sensitive |
| 451 $ define term "vt320" | |
| 452 | |
| 3082 | 453 Terminals from VT100 to VT320 (as V300, VT220, VT200) do not need any extra |
| 454 keyboard mappings. They should work perfectly as they are, including arrows, | |
| 236 | 455 Ins, Del buttons etc., except Backspace in GUI mode. To solve it, add to |
| 7 | 456 .gvimrc: > |
| 457 | |
| 458 inoremap <Del> <BS> | |
| 459 | |
| 460 Vim will also recognize that they are fast terminals. | |
| 461 | |
| 462 If you have some annoying line jumping on the screen between windows add to | |
| 463 your .vimrc file: > | |
| 464 | |
| 465 set ttyfast " set fast terminal | |
| 466 | |
| 3082 | 467 Note: if you're using Vim on remote host or through a very slow connection, it's |
| 468 recommended to avoid the fast terminal option with: > | |
| 7 | 469 |
| 470 set nottyfast " set terminal to slow mode | |
| 471 | |
| 472 (Zoltan Arpadffy, Vim 5.6) | |
| 473 | |
| 474 | |
| 475 8.7 Hex-editing and other external tools | |
| 476 | |
| 477 A very important difference between OpenVMS and other systems is that VMS uses | |
| 478 special commands to execute executables: > | |
| 479 | |
| 480 RUN <path>filename | |
| 481 MCR <path>filename <parameters> | |
| 482 | |
| 483 OpenVMS users always have to be aware that the Vim command :! "just" drop them | |
| 236 | 484 to DCL prompt. This feature is possible to use without any problem with all |
| 3082 | 485 DCL commands, but if we want to execute some programs such as XXD, CTAGS, JTAGS, |
| 486 etc. we're running into trouble if we follow the Vim documentation (see: help | |
| 7 | 487 xxd). |
| 488 | |
| 489 Solution: Execute with the MC command and add the full path to the executable. | |
| 490 Example: Instead of :%!xxd command use: > | |
| 491 | |
| 492 :%!mc vim:xxd | |
| 493 | |
| 494 ... or in general: > | |
| 495 :!mc <path>filename <parameters> | |
| 496 | |
| 236 | 497 Note: You can use XXD and CTAGS from GUI menu. |
| 7 | 498 |
| 236 | 499 To customize ctags it is possible to define the logical $CTAGS with standard |
| 7 | 500 parameters as: > |
| 501 | |
| 502 define/nolog CTAGS "--totals -o sys$login:tags" | |
| 503 | |
| 504 For additional information, please read :help tagsearch and CTAGS | |
| 505 documentation at http://ctags.sourceforge.net/ctags.html. | |
| 506 | |
| 507 (Zoltan Arpadffy, Vim 5.6-70) | |
| 508 | |
| 509 | |
| 510 8.8 Sourcing vimrc and gvimrc | |
| 511 | |
| 512 If you want to use your .vimrc and .gvimrc from other platforms (e.g. Windows) | |
| 513 you can get in trouble if you ftp that file(s): VMS has different end-of-line | |
| 514 indication. | |
| 236 | 515 The symptom is that Vim is not sourcing your .vimrc/.gvimrc, even if you say: |
| 7 | 516 > |
| 517 :so sys$login:.vimrc | |
| 518 | |
| 519 One trick is to compress (e.g. zip) the files on the other platform and | |
| 520 uncompress it on VMS; if you have the same symptom, try to create the files | |
| 521 with copy-paste (for this you need both op. systems reachable from one | |
| 522 machine, e.g. an Xterm on Windows or telnet to Windows from VMS). | |
| 523 | |
| 524 (Sandor Kopanyi, <sandor.kopanyi@mailbox.hu> Vim 6.0a) | |
| 525 | |
| 526 | |
| 527 8.9 Printing from Vim | |
| 528 | |
| 529 To be able to print from Vim (running in GUI mode) under VMS you have to set | |
| 530 up $TMP logical which should point to some temporary directory and logical | |
| 531 SYS$PRINT to your default print queue. | |
| 532 Example: > | |
| 533 | |
| 534 $define SYS$PRINT HP5ANSI | |
| 535 | |
| 3082 | 536 You can print out the whole buffer or just the marked area. |
| 7 | 537 More info under :help hardcopy |
| 538 | |
| 539 (Zoltan Arpadffy, Vim 6.0c) | |
| 540 | |
| 541 | |
| 542 8.10 Setting up the symbols | |
| 543 | |
| 11473 | 544 When I use gvim this way and press CTRL-Y in the parent terminal, gvim exits. |
| 7 | 545 I now use a different symbol that seems to work OK and fixes the problem. |
| 546 I suggest this instead: > | |
| 547 | |
| 548 $ GV*IM:==SPAWN/NOWAIT/INPUT=NLA0: MCR VIM:VIM.EXE -G -GEOMETRY 80X40 | |
| 549 | |
| 550 The /INPUT=NLA0: separates the standard input of the gvim process from the | |
| 551 parent terminal, to block signals from the parent window. | |
| 11473 | 552 Without the -GEOMETRY, the gvim window size will be minimal and the menu |
| 7 | 553 will be confused after a window-resize. |
| 554 | |
| 555 (Carlo Mekenkamp, Coen Engelbarts, Vim 6.0ac) | |
| 556 | |
| 557 | |
| 558 8.11 diff and other GNU programs | |
| 559 | |
| 560 From 6.0 diff functionality has been implemented, but OpenVMS does not use | |
| 561 GNU/Unix like diff therefore built in diff does not work. | |
| 236 | 562 There is a simple solution to solve this anomaly. Install a Unix like diff |
| 3082 | 563 and Vim will work perfectly in diff mode too. You just have to redefine your |
| 7 | 564 diff program as: > |
| 565 | |
| 566 define /nolog diff <GNU_PATH>diff.exe | |
| 567 | |
| 568 Another, more sophisticated solution is described below (8.12 diff-mode) | |
| 3082 | 569 There are other programs such as patch, make etc that may cause the same |
| 570 problems. At www.polarhome.com is possible to download an GNU package for | |
| 571 Alpha and VAX boxes that is meant to solve GNU problems on OpenVMS. | |
| 572 (Zoltan Arpadffy, Vim 6.1) | |
| 7 | 573 |
| 574 | |
| 575 8.12 diff-mode | |
| 576 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
577 Vim 6.0 and higher supports Vim diff-mode (See |new-diff-mode|, |diff-mode| |
| 236 | 578 and |08.7|). This uses the external program 'diff' and expects a Unix-like |
| 579 output format from diff. The standard VMS diff has a different output | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
580 format. To use Vim on VMS in diff-mode, you need to: |
| 7 | 581 1 Install a Unix-like diff program, e.g. GNU diff |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
582 2 Tell Vim to use the Unix-like diff for diff-mode. |
| 7 | 583 |
| 584 You can download GNU diff from the VIM-VMS website, it is one of the GNU | |
| 236 | 585 tools in http://www.polarhome.com/vim/files/gnu_tools.zip. I suggest to |
| 7 | 586 unpack it in a separate directory "GNU" and create a logical GNU: that |
| 236 | 587 points to that directory, e.g: > |
| 7 | 588 |
| 589 DEFINE GNU <DISK>:[<DIRECTORY>.BIN.GNU] | |
| 590 | |
| 591 You may also want to define a symbol GDIFF, to use the GNU diff from the DCL | |
| 592 prompt: > | |
| 593 | |
| 594 GDIFF :== $GNU:DIFF.EXE | |
| 595 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
596 Now you need to tell Vim to use the new diff program. Take the example |
| 7 | 597 settings from |diff-diffexpr| and change the call to the external diff |
| 236 | 598 program to the new diff on VMS. Add this to your .vimrc file: > |
| 7 | 599 |
| 600 " Set up vimdiff options | |
| 601 if v:version >= 600 | |
| 602 " Use GNU diff on VMS | |
| 603 set diffexpr=MyDiff() | |
| 604 function MyDiff() | |
| 605 let opt = "" | |
| 606 if &diffopt =~ "icase" | |
| 607 let opt = opt . "-i " | |
| 608 endif | |
| 609 if &diffopt =~ "iwhite" | |
| 610 let opt = opt . "-b " | |
| 611 endif | |
| 612 silent execute "!mc GNU:diff.exe -a " . opt . v:fname_in . " " . v:fname_new . | |
| 613 \ " > " . v:fname_out | |
| 614 endfunction | |
| 615 endif | |
| 616 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
617 You can now use Vim in diff-mode, e.g. to compare two files in read-only |
| 7 | 618 mode: > |
| 619 | |
| 620 $ VIM -D/R <FILE1> <FILE2> | |
| 621 | |
| 622 You can also define new symbols for vimdiff, e.g.: > | |
| 623 | |
| 624 $ VIMDIFF :== 'VIM' -D/R | |
| 625 $ GVIMDIFF :== 'GVIM' -D/R | |
| 626 | |
| 627 You can now compare files in 4 ways: > | |
| 628 | |
| 629 1. VMS diff: $ DIFF <FILE1> <FILE2> | |
| 630 2. GNU diff: $ GDIFF <FILE1> <FILE2> | |
| 631 3. VIM diff: $ VIMDIFF <FILE1> <FILE2> | |
| 632 4. GVIM diff: $ GVIMDIFF <FILE1> <FILE2> | |
| 633 | |
| 3082 | 634 (Coen Engelbarts, Vim 6.1) |
| 7 | 635 |
| 636 | |
| 637 8.13 Allow '$' in C keywords | |
| 638 | |
| 236 | 639 DEC C uses many identifiers with '$' in them. This is not allowed in ANSI C, |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
640 and Vim recognises the '$' as the end of the identifier. You can change this |
|
2324
0a258a67051d
In Visual mode with 'showcmd' display the number of bytes and characters.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
641 with the 'iskeyword' option. |
| 7 | 642 Add this command to your .vimrc file: > |
| 643 | |
| 644 autocmd FileType c,cpp,cs set iskeyword+=$ | |
| 645 | |
| 646 You can also create the file(s) $VIM/FTPLUGIN/C.VIM (and/or CPP.VIM and | |
| 647 CS.VIM) and add this command: > | |
| 648 | |
| 649 set iskeyword+=$ | |
| 650 | |
| 651 Now word-based commands, e.g. the '*'-search-command and the CTRL-] | |
| 236 | 652 tag-lookup, work on the whole identifier. (Ctags on VMS also supports '$' in |
| 7 | 653 C keywords since ctags version 5.1.) |
| 654 | |
| 3082 | 655 (Coen Engelbarts, Vim 6.1) |
| 7 | 656 |
| 657 8.14 VIMTUTOR for beginners | |
| 658 | |
| 3082 | 659 The VIMTUTOR.COM DCL script can help Vim beginners to learn/make their first |
| 660 steps with Vim on OpenVMS. Depending of binary distribution you may start it | |
| 661 with: > | |
| 7 | 662 |
| 663 @vim:vimtutor | |
| 664 | |
| 665 (Thomas.R.Wyant III, Vim 6.1) | |
| 666 | |
| 3082 | 667 8.16 Slow start in console mode issue |
| 1709 | 668 |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
669 As GUI/GTK Vim works equally well in console mode, many administrators |
| 1709 | 670 deploy those executables system wide. |
| 671 Unfortunately, on a remote slow connections GUI/GTK executables behave rather | |
| 3082 | 672 slow when user wants to run Vim just in the console mode - because of X |
| 673 environment detection timeout. | |
| 1709 | 674 |
| 675 Luckily, there is a simple solution for that. Administrators need to deploy | |
| 676 both GUI/GTK build and just console build executables, like below: > | |
| 677 | |
| 2581 | 678 |- vim73 |
| 1709 | 679 |----- doc |
| 3082 | 680 |----- syntax |
| 1709 | 681 vimrc (system rc files) |
| 682 gvimrc | |
| 3082 | 683 gvim.exe (the renamed GUI or GTK built vim.exe) |
| 684 vim.exe (the console only executable) | |
| 1709 | 685 |
| 686 Define system symbols like below in for ex in LOGIN.COM or SYLOGIN.COM: > | |
| 687 | |
| 2581 | 688 $ define/nolog VIM RF10:[UTIL.VIM73] ! where you VIM directory is |
| 1709 | 689 $ vi*m :== mcr VIM:VIM.EXE |
| 690 $ gvi*m :== mcr VIM:GVIM.EXE | |
| 691 $ ! or you can try to spawn with | |
| 692 $ gv*im :== spawn/nowait/input=NLA0 mcr VIM:GVIM.EXE -g -GEOMETRY 80x40 | |
| 693 | |
| 694 | |
| 3082 | 695 Like this, users that do not have X environment and want to use Vim just in |
| 1709 | 696 console mode can avoid performance problems. |
| 697 | |
| 698 (Zoltan Arpadffy, Vim 7.2) | |
| 699 | |
| 700 8.15 Common VIM directory - different architectures | |
| 701 | |
| 702 In a cluster that contains nodes with different architectures like below: | |
| 703 | |
| 704 $show cluster | |
| 705 View of Cluster from system ID 11655 node: TOR 18-AUG-2008 11:58:31 | |
| 706 +---------------------------------+ | |
| 13857 | 707 | SYSTEMS | MEMBERS | |
| 708 +-----------------------+---------| | |
| 709 | NODE | SOFTWARE | STATUS | | |
| 710 +--------+--------------+---------| | |
| 711 | TOR | VMS V7.3-2 | MEMBER | | |
| 712 | TITAN2 | VMS V8.3 | MEMBER | | |
| 713 | ODIN | VMS V7.3-2 | MEMBER | | |
| 1709 | 714 +---------------------------------+ |
| 715 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
716 It is convenient to have a common VIM directory but execute different |
| 3082 | 717 executables. |
| 718 There are several solutions for this problem: | |
| 1709 | 719 |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
720 Solution 1. All executables in the same directory with different names |
| 1709 | 721 This is easily done with the following script that can be added |
| 722 to the login.com or sylogin.com: > | |
| 723 | |
| 724 $ if f$getsyi("NODE_HWTYPE") .eqs. "VAX" | |
| 725 $ then | |
| 726 $ say "VAX platform" | |
| 727 $ vi*m:== mcr vim:VIM.EXE_VAX | |
| 728 $ endif | |
| 729 $ if f$getsyi("NODE_HWTYPE") .eqs. "ALPH" | |
| 730 $ then | |
| 731 $ say "ALPHA platform" | |
| 732 $ vi*m :== mcr vim:VIM.EXE_AXP | |
| 733 $ endif | |
| 734 $ if f$getsyi("ARCH_NAME") .eqs. "IA64" | |
| 735 $ then | |
| 736 $ say "IA64 platform" | |
| 737 $ vi*m :== mcr vim:VIM.EXE_IA64 | |
| 738 $ endif | |
| 739 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
740 Solution 2. Different directories: > |
| 1709 | 741 |
| 742 $ if f$getsyi("NODE_HWTYPE") .eqs. "VAX" | |
| 743 $ then | |
| 744 $ say "VAX platform" | |
| 745 $ define/nolog VIM RF10:[UTIL.VAX_EXE] ! VAX executables | |
| 746 $ endif | |
| 747 $ if f$getsyi("NODE_HWTYPE") .eqs. "ALPH" | |
| 748 $ then | |
| 749 $ say "ALPHA platform" | |
| 750 $ define/nolog VIM RF10:[UTIL.AXP_EXE] ! AXP executables | |
| 751 $ endif | |
| 752 $ if f$getsyi("ARCH_NAME") .eqs. "IA64" | |
| 753 $ then | |
| 754 $ say "IA64 platform" | |
| 755 $ define/nolog VIM RF10:[UTIL.IA64_EXE] ! IA64 executables | |
| 756 $ endif | |
| 757 $! VIMRUNTIME must be defined in order to find runtime files | |
| 2581 | 758 $ define/nolog VIMRUNTIME RF10:[UTIL.VIM73] |
| 1709 | 759 |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
760 A good example for this approach is the [GNU]gnu_tools.com script from |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1709
diff
changeset
|
761 GNU_TOOLS.ZIP package downloadable from http://www.polarhome.com/vim/ |
| 1709 | 762 |
| 763 (Zoltan Arpadffy, Vim 7.2) | |
| 764 | |
| 7 | 765 ============================================================================== |
| 766 | |
| 767 9. VMS related changes *vms-changes* | |
| 768 | |
|
15533
08604d82fc9e
patch 8.1.0774: VMS build is missing the blob file
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
769 Version 8.1 |
|
08604d82fc9e
patch 8.1.0774: VMS build is missing the blob file
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
770 - make necessary changes to build v8.1 on VMS |
|
08604d82fc9e
patch 8.1.0774: VMS build is missing the blob file
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
771 |
|
08604d82fc9e
patch 8.1.0774: VMS build is missing the blob file
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
772 Version 8.0 |
|
08604d82fc9e
patch 8.1.0774: VMS build is missing the blob file
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
773 - solve the 100% cpu usage issue while waiting for a keystroke |
|
08604d82fc9e
patch 8.1.0774: VMS build is missing the blob file
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
774 - correct the VMS warnings and errors around handling the INFINITY (used in json.c) |
| 15729 | 775 - minor VMS port related changes |
| 776 - correct the make_vms.mms file for 8.0 | |
| 777 - fix [.TESTDIR]make_vms.mms for 8.0 | |
|
15533
08604d82fc9e
patch 8.1.0774: VMS build is missing the blob file
Bram Moolenaar <Bram@vim.org>
parents:
14421
diff
changeset
|
778 |
| 11473 | 779 Version 7.4 |
| 780 - Undo: VMS can not handle more than one dot in the filenames use "dir/name" -> "dir/_un_name" | |
| 5704 | 781 add _un_ at the beginning to keep the extension |
| 782 - correct swap file name wildcard handling | |
| 783 - handle iconv usage correctly | |
| 784 - do not optimize on vax - otherwise it hangs compiling crypto files | |
| 785 - fileio.c fix the comment | |
| 11473 | 786 - correct RealWaitForChar |
| 5704 | 787 - after 7.4-119 use different functions lib$cvtf_to_internal_time because Alpha and VAX have |
| 788 G_FLOAT but IA64 uses IEEE float otherwise Vim crashes | |
| 6180 | 789 - guard against crashes that are caused by mixed filenames |
| 5704 | 790 - [TESTDIR]make_vms.mms changed to see the output files |
| 791 - Improve tests, update known issues | |
| 792 - minor compiler warnings fixed | |
| 793 - CTAGS 5.8 +regex included | |
| 794 | |
|
2428
33148c37f3c9
Changes for VMS. Mostly by Zoltan Arpadffy.
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
795 Version 7.3 |
|
33148c37f3c9
Changes for VMS. Mostly by Zoltan Arpadffy.
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
796 - CTAGS 5.8 included |
|
33148c37f3c9
Changes for VMS. Mostly by Zoltan Arpadffy.
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
797 - VMS compile warnings fixed - floating-point overflow warning corrected on VAX |
| 3082 | 798 - filepath completion corrected - too many chars were escaped in filename |
|
2428
33148c37f3c9
Changes for VMS. Mostly by Zoltan Arpadffy.
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
799 and shell commands |
|
33148c37f3c9
Changes for VMS. Mostly by Zoltan Arpadffy.
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
800 - the following plugins are included into VMS runtime: |
|
33148c37f3c9
Changes for VMS. Mostly by Zoltan Arpadffy.
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
801 genutils 2.4, multiselect 2.2, multvals 3.1, selectbuf 4.3, |
|
33148c37f3c9
Changes for VMS. Mostly by Zoltan Arpadffy.
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
802 bufexplorer 7.1.7, taglist 4.5 |
|
33148c37f3c9
Changes for VMS. Mostly by Zoltan Arpadffy.
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
803 - minor changes in vimrc (just in VMS runtime) |
| 1709 | 804 - make_vms.mms - HUGE model is the default |
| 805 - [TESTDIR]make_vms.mms include as many tests possible | |
| 806 - modify test30 and test54 for VMS | |
| 807 - enable FLOAT feature in VMS port | |
|
2428
33148c37f3c9
Changes for VMS. Mostly by Zoltan Arpadffy.
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
808 - os_vms.txt updated |
| 1709 | 809 |
| 810 Version 7.2 (2008 Aug 9) | |
| 811 - VCF files write corrected | |
| 812 - CTAGS 5.7 included | |
| 3082 | 813 - corrected make_vms.mms (on VAX gave syntax error) |
| 1709 | 814 |
| 815 Version 7.1 (2007 Jun 15) | |
| 3082 | 816 - create TAGS file from menu |
| 1709 | 817 |
| 818 Version 7 (2006 May 8) | |
| 701 | 819 - Improved low level char input (affects just console mode) |
| 1709 | 820 - Fixed plugin bug |
| 821 - CTAGS 5.6 included | |
| 701 | 822 |
| 823 Version 6.4 (2005 Oct 15) | |
| 412 | 824 - GTKLIB and Vim build on IA64 |
| 825 - colors in terminal mode | |
| 826 - syntax highlighting in terminal mode | |
| 827 - write problem fixed (extra CR) | |
| 828 - ESC and ESC sequence recognition in terminal mode | |
| 829 - make file changed to support new MMS version | |
| 830 - env variable expansion in path corrected | |
| 831 - printing problems corrected | |
| 832 - help text added for case insensitive arguments | |
| 833 | |
| 7 | 834 Version 6.3 (2004 May 10) |
| 835 - Improved vms_read function | |
| 836 - CTAGS v5.5.4 included | |
| 837 - Documentation corrected and updated | |
| 838 | |
| 839 Version 6.2 (2003 May 7) | |
| 840 - Corrected VMS system call results | |
| 841 - Low level character input is rewritten | |
| 842 - Correction in tag and quickfix handling | |
| 843 - First GTK build | |
| 844 - Make file changes | |
| 845 - GTK feature added | |
| 846 - Define for OLD_VMS | |
| 847 - OpenVMS version 6.2 or older | |
| 848 - Documentation updated with GTK features | |
| 849 - CTAGS v5.5 included | |
| 850 - VMS VIM tutor created | |
| 851 | |
| 852 Version 6.1 (2002 Mar 25) | |
| 853 - TCL init_tcl() problem fixed | |
| 854 - CTAGS v5.4 included | |
| 855 - GNU tools binaries for OpenVMS | |
| 856 - Make file changes | |
| 857 - PERL, PYTHON and TCL support improved | |
| 858 - InstallVMS.txt has a detailed description HOWTO build | |
| 859 - VMS/Unix file handling rewritten | |
| 860 - Minor casting and bug fixes | |
| 861 | |
| 862 Version 6.0 (2001 Sep 28) | |
| 863 - Unix and VMS code has been merged | |
| 864 - separated "really" VMS related code | |
| 865 - included all possible Unix functionality | |
| 866 - simplified or deleted the configuration files | |
| 867 - makefile MAKE_VMS.MMS reviewed | |
| 868 - menu changes (fixed printing, CTAGS and XXD usage) | |
| 869 - fixed variable RMS record format handling anomaly | |
| 870 - corrected syntax, ftplugin etc files load | |
| 871 - changed expand_wildcards and expandpath functions to work more general | |
| 872 - created OS_VMS_FILTER.COM - DECC->VAXC pre-processor directive convert | |
| 873 script. | |
| 874 - Improved code's VAXC and new DECC compilers compatibility | |
| 875 - changed quickfix parameters: | |
| 876 - errormessage format to suite DECC | |
| 877 - search, make and other commands to suite VMS system | |
| 878 - updated and renamed MMS make files for Vim and CTAGS. | |
| 879 - CTAGS has been removed from source distribution of Vim but it will remain | |
| 880 in OpenVMS binary distributions. | |
| 881 - simplified build/configuration procedure | |
| 882 - created INSTALLvms.txt - detailed compiling instructions under VMS. | |
| 883 - updated test scripts. | |
| 884 | |
| 885 Version 5.8 (2001 Jun 1) | |
| 886 - OS_VMS.TXT updated with new features. | |
| 887 - other minor fixes. | |
| 888 - documentation updated | |
| 889 - this version had been tested much more than any other OpenVMS version | |
| 890 earlier | |
| 891 | |
| 892 Version 5.7 (2000 Jun 24) | |
| 893 - New CTAGS v5.0 in distribution | |
| 894 - Documentation updated | |
| 895 | |
| 896 Version 5.6 (2000 Jan 17) | |
| 897 - VMS filename related changes: | |
| 898 - version handling (open everything, save to new version) | |
| 899 - correct file extension matching for syntax (version problem) | |
| 900 - handle <,> characters and passwords in directory definition | |
| 901 - handle internode/remote invocation and editing with passwords | |
| 902 - OpenVMS files will be treated case insensitive from now | |
| 903 - corrected response of expand("%:.") etc path related functions | |
| 904 (in one word: VMS directory handling internally) | |
| 905 - version command | |
| 906 - corrected (+,-) information data | |
| 907 - added compiler and OS version | |
| 908 - added user and host information | |
| 909 - resolving $VIM and $VIMRUNTIME logicals | |
| 910 - VMS port is in MAX_FEAT (maximum features) club with Unix, Win32 and OS/2. | |
| 911 - enabled farsi, rightleft etc. features | |
| 912 - undo level raised up to 1000 | |
| 913 - Updated OS_VMS.MMS file. | |
| 914 - maximum features ON is default | |
| 915 - Vim is compilable with +perl, +python and +tcl features. | |
| 916 - improved MMK compatibility | |
| 917 - Created MAKEFILE_VMS.MMS, makefile for testing Vim during development. | |
| 918 - Defined DEC terminal VT320 | |
| 919 - compatibility for VT3*0, VT2*0 and VT1*0 - ANSI terminals | |
| 920 backwards, but not VT340 and newer with colour capability. | |
| 921 - VT320 is default terminal for OpenVMS | |
| 922 - these new terminals are also fast ttys (default for OpenVMS). | |
| 923 - allowed dec_mouse ttym | |
| 924 - Updated files vimrc and gvimrc with VMS specific suggestions. | |
| 925 - OS_VMS.TXT updated with new features. | |
| 926 | |
| 927 Version 5.5 (1999 Dec 3) | |
| 928 - Popup menu line crash corrected. | |
| 929 - Handle full file names with version numbers. | |
| 930 - Directory handling (CD command etc.) | |
| 931 - Corrected file name conversion VMS to Unix and v.v. | |
| 932 - Correct response of expand wildcards | |
| 933 - Recovery is working from this version under VMS as well. | |
| 934 - Improved terminal and signal handing. | |
| 935 - Improved OS_VMS.TXT | |
| 936 | |
| 937 Version 5.4 (1999 Sep 9) | |
| 938 - Cut and paste mismatch corrected. | |
| 939 - Motif directories during open and save are corrected. | |
| 940 | |
| 941 Version 5.3 (1998 Oct 12) | |
| 942 - Minor changes in the code | |
| 943 - Standard distribution with +GUI option | |
| 944 | |
| 945 Version 5.1 (1998 Apr 21) | |
| 946 - Syntax and DEC C changes in the code | |
| 947 - Fixing problems with the /doc subdirectory | |
| 948 - Improve OS_VMS.MMS | |
| 949 | |
| 950 Version 4.5 (1996 Dec 16) | |
| 951 - First VMS port by Henk Elbers <henk@xs4all.nl> | |
| 952 | |
| 953 ============================================================================== | |
| 954 | |
| 955 10. Authors *vms-authors* | |
| 956 | |
| 957 OpenVMS documentation and executables are maintained by: | |
| 958 Zoltan Arpadffy <arpadffy@polarhome.com> | |
| 1709 | 959 OpenVMS Vim page: http://www.polarhome.com/vim/ |
| 7 | 960 |
| 961 This document uses parts and remarks from earlier authors and contributors | |
| 962 of OS_VMS.TXT: | |
| 963 Charles E. Campbell, Jr. <cec@gryphon.gsfc.nasa.gov> | |
| 964 Bruce Hunsaker <BNHunsaker@chq.byu.edu> | |
| 965 Sandor Kopanyi <sandor.kopanyi@mailbox.hu> | |
| 966 | |
| 14421 | 967 vim:tw=78:ts=8:noet:ft=help:norl: |