Mercurial > vim
comparison runtime/doc/os_vms.txt @ 7:3fc0f57ecb91 v7.0001
updated for version 7.0001
author | vimboss |
---|---|
date | Sun, 13 Jun 2004 20:20:40 +0000 |
parents | |
children | 4102fb4ea781 |
comparison
equal
deleted
inserted
replaced
6:c2daee826b8f | 7:3fc0f57ecb91 |
---|---|
1 *os_vms.txt* For Vim version 7.0aa. Last change: 2004 May 16 | |
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 | |
27 Vim (Vi IMproved) is a vi-compatible text editor that runs on nearly every | |
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 will need both the Unix and Extra archives to build vim.exe for VMS. | |
42 For using Vim's full power you will need the runtime files as well. | |
43 | |
44 You can download precompiled executables from: | |
45 http://www.polarhome.com/vim/ | |
46 ftp://ftp.polarhome.com/pub/vim/ | |
47 | |
48 To use the precompiled binary version, you need one of these archives: | |
49 | |
50 vim-XX-exe-alpha-gui.zip Alpha GUI/Motif executables | |
51 vim-XX-exe-alpha-gtk.zip Alpha GUI/GTK executables | |
52 vim-XX-exe-alpha-term.zip Alpha console executables | |
53 vim-XX-exe-vax-gui.zip VAX GUI executables | |
54 vim-XX-exe-vax-term.zip VAX console executables | |
55 | |
56 and of course | |
57 vim-XX-runtime.zip runtime files | |
58 | |
59 The binary archives contain: vim.exe, ctags.exe, xxd.exe, mms_vim.exe files. | |
60 | |
61 ============================================================================== | |
62 | |
63 3. Compiling *vms-compiling* | |
64 | |
65 See the file [.SRC]INSTALLVMS.TXT. | |
66 | |
67 ============================================================================== | |
68 | |
69 4. Problems *vms-problems* | |
70 | |
71 The code has been tested under Open VMS 6.2 - 7.3 on Alpha and VAX platforms | |
72 with the DECC compiler. It should work without bigger problems. | |
73 If it happened that your system does not have some include libraries you can | |
74 tune up in OS_VMS_CONF.H file. | |
75 | |
76 If you decided to build Vim with +perl, +python, etc. options, first you need | |
77 to download OpenVMS distributions of Perl and Python. Build and deploy the | |
78 libraries and change adequate lines in MAKE_VMS.MMS file. There should not be | |
79 problem from Vim side. | |
80 | |
81 Note: Under VAX it should work with DEC C compiler without problem. VAXC | |
82 compiler is not fully ANSI C compatible in pre-processor directives | |
83 semantics, therefore you have to use a converter program what will do the | |
84 lion part of the job. For detailed instruction read file INSTALLvms.txt | |
85 | |
86 MMS_VIM.EXE is building together with VIM.EXE, but for XD.EXE you should | |
87 change to subdirectory and build it separately. | |
88 | |
89 CTAGS is not part of Vim source distribution any more, however the OpenVMS | |
90 specific source might contain CTAGS source files as it is described above. | |
91 You can find more information about CTAGS on VMS at | |
92 http://www.polarhome.com/ctags/ | |
93 | |
94 Advanced users may try some acrobatics in FEATURE.H file also. | |
95 | |
96 It is possible to compile with +xfontset +xim options too, but then you have | |
97 to set up GUI fonts etc. correctly. See. :help xim from Vim command prompt. | |
98 | |
99 You may want to use GUI with GTK icons, then you have to download and install | |
100 GTK for OpenVMS or at least runtime shareable images - LIBGTK from | |
101 polarhome.com | |
102 | |
103 For more advanced questions, please send your problem to Vim on VMS mailing | |
104 list <vim-vms@polarhome.com> | |
105 More about the vim-vms list can be found at: | |
106 http://www.polarhome.com/mailman/listinfo/vim-vms | |
107 | |
108 ============================================================================== | |
109 | |
110 5. Deploy *vms-deploy* | |
111 | |
112 Vim uses a special directory structure to hold the document and runtime files: | |
113 | |
114 vim (or wherever) | |
115 |- tmp | |
116 |- vim57 | |
117 |----- doc | |
118 |----- syntax | |
119 |- vim60 | |
120 |----- doc | |
121 |----- syntax | |
122 |- vim61 | |
123 |----- doc | |
124 |----- syntax | |
125 vimrc (system rc files) | |
126 gvimrc | |
127 | |
128 Use: > | |
129 | |
130 define/nolog VIM device:[path.vim] | |
131 define/nolog VIMRUNTIME device:[path.vim.vim60] | |
132 define/nolog TMP device:[path.tmp] | |
133 | |
134 to get vim.exe to find its document, filetype, and syntax files, and to | |
135 specify a directory where temporary files will be located. Copy the "runtime" | |
136 subdirectory of the vim distribution to vimruntime. | |
137 | |
138 Logicals $VIMRUNTIME and $TMP are optional. | |
139 | |
140 If $VIMRUNTIME is not set, Vim will guess and try to set up automatically. | |
141 Read more about at :help runtime | |
142 | |
143 If $TMP is not set, you will not be able to use some functions as CTAGS, | |
144 XXD, printing etc. that use temporary directory for normal operation. | |
145 $TMP directory should be readable and writable by the user(s). | |
146 The easiest way to set up $TMP is to define logical: > | |
147 | |
148 define/nolog TMP SYS$SCRATCH | |
149 or as: > | |
150 define/nolog TMP SYS$LOGIN | |
151 | |
152 ============================================================================== | |
153 | |
154 6. Practical usage *vms-usage* | |
155 | |
156 Usually, you want to run just one version of Vim on your system, therefore | |
157 it is enough to dedicate one directory for Vim. | |
158 Copy all Vim runtime directory structure to the deployment position. | |
159 Add the following lines to your LOGIN.COM (in SYS$LOGIN directory). | |
160 Set up logical $VIM as: > | |
161 | |
162 $ define VIM device:<path> | |
163 | |
164 Set up some symbols: > | |
165 | |
166 $ ! vi starts Vim in chr. mode. | |
167 $ vi*m :== mcr VIM:VIM.EXE | |
168 | |
169 $ !gvi starts Vim in GUI mode. | |
170 $ gv*im :== spawn/nowait mcr VIM:VIM.EXE -g | |
171 | |
172 Please, check the notes for customization and configuration of symbols. | |
173 | |
174 You may want to create .vimrc and .gvimrc files in your home directory | |
175 (SYS$LOGIN) to overwrite default settings. | |
176 | |
177 The easiest way is just rename example files. You may leave the menu file | |
178 (MENU.VIM) and files vimrc and gvimrc in the original $VIM directory. It will | |
179 be default setup for all users, and for users is enough just to have their | |
180 own additions or resetting in home directory in files .vimrc and .gvimrc. | |
181 It should work without problems. | |
182 | |
183 Note: Remember, system rc files (default for all users) does not have leading | |
184 "." So, system rc files are: > | |
185 | |
186 $VIM:vimrc | |
187 $VIM:gvimrc | |
188 $VIM:menu.vim | |
189 | |
190 and user's customized rc files are: > | |
191 | |
192 sys$login:.vimrc | |
193 sys$login:.gvimrc | |
194 | |
195 You can check that everything is on the right place with the :version command. | |
196 | |
197 Example LOGIN.COM: > | |
198 | |
199 $ define/nolog VIM RF10:[UTIL.VIM] | |
200 $ vi*m :== mcr VIM:VIM.EXE | |
201 $ gv*im:== spawn/nowait/input=NLA0 mcr VIM:VIM.EXE -g -GEOMETRY 80x40 | |
202 $ set disp/create/node=192.168.5.223/trans=tcpip | |
203 | |
204 Note: This set-up should be enough, if you are working on standalone server or | |
205 clustered environment, but if you want to use Vim as internode editor in | |
206 DECNET environment, it will satisfy you as well. | |
207 You just have to define the "whole" path: > | |
208 | |
209 $ define VIM "<server_name>[""user password""]::device:<path>" | |
210 $ vi*m :== "mcr VIM:VIM.EXE" | |
211 | |
212 as for example: > | |
213 | |
214 $ define VIM "PLUTO::RF10:[UTIL.VIM]" | |
215 $ define VIM "PLUTO""ZAY mypass""::RF10:[UTIL.VIM]" ! if passwd required | |
216 | |
217 You can also use $VIMRUNTIME logical to point to proper version of Vim if you | |
218 have installed more versions in the same time. If $VIMRUNTIME is not defined | |
219 Vim will borrow value from $VIM logical. You can find more information about | |
220 $VIMRUNTIME logical by typing :help runtime as a Vim command. | |
221 | |
222 System administrators might want to set up a system wide Vim installation, | |
223 then add to the SYS$STARTUP:SYLOGICALS.COM > | |
224 | |
225 $ define/nolog/sys VIM device:<path> | |
226 $ define/nolog/sys TMP SYS$SCRATCH | |
227 | |
228 and to the SYS$STARTUP:SYLOGIN.COM > | |
229 | |
230 $ vi*m :== mcr VIM:VIM.EXE | |
231 $ gv*im:== spawn/nowait/input=NLA0 mcr VIM:VIM.EXE -g -GEOMETRY 80x40 | |
232 | |
233 | |
234 It will set up normal Vim work environment for every user on the system. | |
235 | |
236 ============================================================================== | |
237 | |
238 7. GUI mode questions *vms-gui* | |
239 | |
240 OpenVMS in a real mainframe OS, therefore even if it has a GUI console, most of | |
241 the users does not use a native X/Window environment during normal operation. | |
242 It is not possible to start Vim in GUI mode "just like that". But anyhow it is | |
243 not too complicate either. | |
244 | |
245 First of all: you will need an executable that is built with enabled GUI. | |
246 | |
247 Second: you need to have installed DECW/Motif on your VMS server, otherwise | |
248 you will get errors that some shareable libraries are missing. | |
249 | |
250 Third: If you choose to run Vim with extra feature as GUI/GTK then you need | |
251 GTK installation too or at least GTK runtime environment (LIBGTK etc.) | |
252 | |
253 1) If you are working on the VMS X/Motif console: | |
254 Start Vim with the command: > | |
255 | |
256 $ mc device:<path>VIM.EXE -g | |
257 < | |
258 or type :gui as a command to the Vim command prompt. For more info :help gui | |
259 | |
260 2) If you are working on other X/Window environment as Unix or some remote X | |
261 VMS console. Set up display to your host with: > | |
262 | |
263 $ set disp/create/node=<your IP address>/trans=<transport-name> | |
264 < | |
265 and start Vim as in point 1. You can find more help in VMS documentation or | |
266 type: help set disp in VMS prompt. | |
267 Examples: > | |
268 | |
269 $ set disp/create/node=192.168.5.159 ! default trans is DECnet | |
270 $ set disp/create/node=192.168.5.159/trans=tcpip ! TCP/IP network | |
271 $ set disp/create/node=192.168.5.159/trans=local ! display on the same node | |
272 | |
273 Note: you should define just one of these. | |
274 For more information type $help set disp in VMS prompt. | |
275 | |
276 3) Another elegant solution is XDM if you have installed on OpenVMS box. | |
277 It is possible to work from XDM client as from GUI console. | |
278 | |
279 4) If you are working on MS Windows or other non X/Window environment | |
280 You need to set up one X server and run Vim as in point 2. | |
281 For MS Windows there are available free X servers as MIX , Omni X etc. | |
282 as well as excellent commercial products as eXcursion or ReflectionX with | |
283 buit in DEC support. | |
284 | |
285 Please note, that executables without GUI are slightly faster during startup | |
286 then with enabled GUI in character mode. Therefore, if you do not use GUI | |
287 features, it is worth to choose non GUI executables. | |
288 | |
289 ============================================================================== | |
290 | |
291 8. Useful notes *vms-notes* | |
292 | |
293 8.1 backspace/delete | |
294 8.2 Filters | |
295 8.3 VMS file version numbers | |
296 8.4 Directory conversion | |
297 8.5 Remote host invocation | |
298 8.6 Terminal problems | |
299 8.7 Hex-editing and other external tools | |
300 8.8 Sourcing vimrc and gvimrc | |
301 8.9 Printing from Vim | |
302 8.10 Setting up the symbols | |
303 8.11 diff and other GNU programs | |
304 8.12 diff-mode | |
305 8.13 Allow '$' in C keywords | |
306 8.14 VIMTUTOR for beginners | |
307 | |
308 8.1 backspace/delete | |
309 | |
310 There are backspace/delete key inconsistencies with VMS. | |
311 :fixdel doesn't do the trick, but the solution is: > | |
312 | |
313 :inoremap ^? ^H " for terminal mode | |
314 :inoremap <Del> ^H " for gui mode | |
315 | |
316 Read more in ch: 8.6 (Terminal problems). | |
317 (Bruce Hunsaker <BNHunsaker@chq.byu.edu> Vim 5.3) | |
318 | |
319 | |
320 8.2 Filters | |
321 | |
322 Vim supports filters; ie. if you have a sort program that can handle | |
323 input/output redirection like Unix (<infile >outfile), you could use > | |
324 | |
325 :map \s 0!'aqsort<CR> | |
326 | |
327 (Charles E. Campbell, Jr. <cec@gryphon.gsfc.nasa.gov> Vim 5.4) | |
328 | |
329 | |
330 8.3 VMS file version numbers | |
331 | |
332 Vim is saving files into a new file with the next higher file version | |
333 number, try these settings. > | |
334 | |
335 :set nobackup " does not create *.*_ backup files | |
336 :set nowritebackup " does not have any purpose on VMS. It's default. | |
337 | |
338 Recovery is working perfect as well from the default swap file. | |
339 Read more with :help swapfile | |
340 | |
341 (Claude Marinier <ClaudeMarinier@xwavesolutions.com> Vim 5.5, Zoltan Arpadffy | |
342 Vim 5.6 ) | |
343 | |
344 | |
345 8.4 Directory conversion | |
346 | |
347 Vim will internally convert any unix-style paths and even mixed unix/VMS | |
348 paths into VMS style paths. Some typical conversions resemble: | |
349 | |
350 /abc/def/ghi -> abc:[def]ghi. | |
351 /abc/def/ghi.j -> abc:[def]ghi.j | |
352 /abc/def/ghi.j;2 -> abc:[def]ghi.j;2 | |
353 /abc/def/ghi/jkl/mno -> abc:[def.ghi.jkl]mno. | |
354 abc:[def.ghi]jkl/mno -> abc:[def.ghi.jkl]mno. | |
355 ./ -> current directory | |
356 ../ -> relative parent directory | |
357 [.def.ghi] -> relative child directory | |
358 ./def/ghi -> relative child directory | |
359 | |
360 Note: You may use <,> brackets as well (device:<path>file.ext;version) as | |
361 rf10:<user.zay.work>test.c;1 | |
362 | |
363 (David Elins <delins@foliage.com>, Jerome Lauret | |
364 <JLAURET@mail.chem.sunysb.edu> Vim 5.6 ) | |
365 | |
366 | |
367 8.5 Remote host invocation | |
368 | |
369 It is possible to use Vim as an internode editor. | |
370 1. Edit some file from remote node: > | |
371 | |
372 vi "<server>""username passwd""::<device>:<path><filename>;<version>" | |
373 | |
374 example: > | |
375 vi "pluto""zay passwd""::RF10:<USER.ZAY.WORK>TEST.C;1" | |
376 | |
377 Note: syntax is very important, otherwise VMS will recognize more parameters | |
378 instead of one (resulting with: file not found) | |
379 | |
380 2. Set up Vim as your internode editor. If Vim is not installed on your host, | |
381 just set up your IP address, full Vim path including the server name and run | |
382 the command procedure below: > | |
383 | |
384 $ if (p1 .eqs. "") .OR. (p2 .eqs. "") then goto usage | |
385 $ set disp/create/node=<your_IP_here>/trans=tcpip | |
386 $ define "VIM "<vim_server>""''p1' ''p2'""::<device>:<vim_path>" | |
387 $ vi*m :== "mcr VIM:VIM.EXE" | |
388 $ gv*im :== "spawn/nowait mcr VIM:VIM.EXE -g" | |
389 $ goto end | |
390 $ usage: | |
391 $ write sys$output " Please enter username and password as a parameter." | |
392 $ write sys$output " Example: @SETVIM.COM username passwd" | |
393 $ end: | |
394 | |
395 Note: Never use it in clustered environment (you do not need it), and load could | |
396 be very-very slow, but even faster then a local Emacs. :-) | |
397 | |
398 (Zoltan Arpadffy, Vim 5.6) | |
399 | |
400 | |
401 8.6 Terminal problems | |
402 | |
403 If your terminal name is not known to Vim and it is trying to find the default | |
404 one you will get the following message during start-up: | |
405 --- | |
406 Terminal entry not found in termcap | |
407 'unknown-terminal' not known. Available built-in terminals are: | |
408 builtin_gui | |
409 builtin_riscos | |
410 builtin_amiga | |
411 builtin_beos-ansi | |
412 builtin_ansi | |
413 builtin_vt320 | |
414 builtin_vt52 | |
415 builtin_pcansi | |
416 builtin_win32 | |
417 builtin_xterm | |
418 builtin_iris-ansi | |
419 builtin_debug | |
420 builtin_dumb | |
421 defaulting to 'vt320' | |
422 --- | |
423 The solution is to define default terminal name: > | |
424 | |
425 $ ! unknown terminal name. let us use vt320 or ansi instead. | |
426 $ ! Note: it's case sensitive | |
427 $ define term "vt320" | |
428 | |
429 Terminals from VT100 to VT320 (as V300, VT220, VT200 ) do not need any extra | |
430 keyboard mappings. They should work perfect as they are, including arrows, | |
431 Ins, Del buttons etc. Except Backspace in GUI mode. To solve it, add to | |
432 .gvimrc: > | |
433 | |
434 inoremap <Del> <BS> | |
435 | |
436 Vim will also recognize that they are fast terminals. | |
437 | |
438 If you have some annoying line jumping on the screen between windows add to | |
439 your .vimrc file: > | |
440 | |
441 set ttyfast " set fast terminal | |
442 | |
443 Note: if you're using Vim on remote host or through very slow connection, it's | |
444 recommended to avoid fast terminal option with: > | |
445 | |
446 set nottyfast " set terminal to slow mode | |
447 | |
448 (Zoltan Arpadffy, Vim 5.6) | |
449 | |
450 | |
451 8.7 Hex-editing and other external tools | |
452 | |
453 A very important difference between OpenVMS and other systems is that VMS uses | |
454 special commands to execute executables: > | |
455 | |
456 RUN <path>filename | |
457 MCR <path>filename <parameters> | |
458 | |
459 OpenVMS users always have to be aware that the Vim command :! "just" drop them | |
460 to DCL prompt. This feature is possible to use without any problem with all | |
461 DCL commands, but if we want to execute some program as XXD, CTAGS, JTAGS etc. | |
462 we're running into trouble if we following the Vim documentation (see: help | |
463 xxd). | |
464 | |
465 Solution: Execute with the MC command and add the full path to the executable. | |
466 Example: Instead of :%!xxd command use: > | |
467 | |
468 :%!mc vim:xxd | |
469 | |
470 ... or in general: > | |
471 :!mc <path>filename <parameters> | |
472 | |
473 Note: You can use XXD, and CTAGS from GUI menu. | |
474 | |
475 To customize ctags it is possible to define logical $CTAGS with standard | |
476 parameters as: > | |
477 | |
478 define/nolog CTAGS "--totals -o sys$login:tags" | |
479 | |
480 For additional information, please read :help tagsearch and CTAGS | |
481 documentation at http://ctags.sourceforge.net/ctags.html. | |
482 | |
483 (Zoltan Arpadffy, Vim 5.6-70) | |
484 | |
485 | |
486 8.8 Sourcing vimrc and gvimrc | |
487 | |
488 If you want to use your .vimrc and .gvimrc from other platforms (e.g. Windows) | |
489 you can get in trouble if you ftp that file(s): VMS has different end-of-line | |
490 indication. | |
491 The symptom is that ViM is not sourcing your .vimrc/.gvimrc, even if you say: | |
492 > | |
493 :so sys$login:.vimrc | |
494 | |
495 One trick is to compress (e.g. zip) the files on the other platform and | |
496 uncompress it on VMS; if you have the same symptom, try to create the files | |
497 with copy-paste (for this you need both op. systems reachable from one | |
498 machine, e.g. an Xterm on Windows or telnet to Windows from VMS). | |
499 | |
500 (Sandor Kopanyi, <sandor.kopanyi@mailbox.hu> Vim 6.0a) | |
501 | |
502 | |
503 8.9 Printing from Vim | |
504 | |
505 To be able to print from Vim (running in GUI mode) under VMS you have to set | |
506 up $TMP logical which should point to some temporary directory and logical | |
507 SYS$PRINT to your default print queue. | |
508 Example: > | |
509 | |
510 $define SYS$PRINT HP5ANSI | |
511 | |
512 You can print out whole buffer or just the marked area. | |
513 More info under :help hardcopy | |
514 | |
515 (Zoltan Arpadffy, Vim 6.0c) | |
516 | |
517 | |
518 8.10 Setting up the symbols | |
519 | |
520 When I use GVIM this way and press CTRL-Y in the parent terminal, gvim exits. | |
521 I now use a different symbol that seems to work OK and fixes the problem. | |
522 I suggest this instead: > | |
523 | |
524 $ GV*IM:==SPAWN/NOWAIT/INPUT=NLA0: MCR VIM:VIM.EXE -G -GEOMETRY 80X40 | |
525 | |
526 The /INPUT=NLA0: separates the standard input of the gvim process from the | |
527 parent terminal, to block signals from the parent window. | |
528 Without the -GEOMETRY, the GVIM window size will be minimal and the menu | |
529 will be confused after a window-resize. | |
530 | |
531 (Carlo Mekenkamp, Coen Engelbarts, Vim 6.0ac) | |
532 | |
533 | |
534 8.11 diff and other GNU programs | |
535 | |
536 From 6.0 diff functionality has been implemented, but OpenVMS does not use | |
537 GNU/Unix like diff therefore built in diff does not work. | |
538 There is a simple solution to solve this anomaly. Install an Unix like diff | |
539 and Vim will work perfect in diff mode too. You just have to redefine your | |
540 diff program as: > | |
541 | |
542 define /nolog diff <GNU_PATH>diff.exe | |
543 | |
544 Another, more sophisticated solution is described below (8.12 diff-mode) | |
545 There are some other programs as patch, make etc that may cause same problems. | |
546 At www.polarhome.com is possible to download an GNU package for Alpha and VAX | |
547 boxes that is meant to solve GNU problems on OpenVMS. | |
548 ( Zoltan Arpadffy, Vim 6.1) | |
549 | |
550 | |
551 8.12 diff-mode | |
552 | |
553 Vim 6.0 and higher supports vim diff-mode (See |new-diff-mode|, |diff-mode| | |
554 and |08.7|). This uses the external program 'diff' and expects a Unix-like | |
555 output format from diff. The standard VMS diff has a different output | |
556 format. To use vim on VMS in diff-mode, you need to: | |
557 1 Install a Unix-like diff program, e.g. GNU diff | |
558 2 Tell vim to use the Unix-like diff for diff-mode. | |
559 | |
560 You can download GNU diff from the VIM-VMS website, it is one of the GNU | |
561 tools in http://www.polarhome.com/vim/files/gnu_tools.zip. I suggest to | |
562 unpack it in a separate directory "GNU" and create a logical GNU: that | |
563 points to that directory. e.g: > | |
564 | |
565 DEFINE GNU <DISK>:[<DIRECTORY>.BIN.GNU] | |
566 | |
567 You may also want to define a symbol GDIFF, to use the GNU diff from the DCL | |
568 prompt: > | |
569 | |
570 GDIFF :== $GNU:DIFF.EXE | |
571 | |
572 Now you need to tell vim to use the new diff program. Take the example | |
573 settings from |diff-diffexpr| and change the call to the external diff | |
574 program to the new diff on VMS. Add this to your .vimrc file: > | |
575 | |
576 " Set up vimdiff options | |
577 if v:version >= 600 | |
578 " Use GNU diff on VMS | |
579 set diffexpr=MyDiff() | |
580 function MyDiff() | |
581 let opt = "" | |
582 if &diffopt =~ "icase" | |
583 let opt = opt . "-i " | |
584 endif | |
585 if &diffopt =~ "iwhite" | |
586 let opt = opt . "-b " | |
587 endif | |
588 silent execute "!mc GNU:diff.exe -a " . opt . v:fname_in . " " . v:fname_new . | |
589 \ " > " . v:fname_out | |
590 endfunction | |
591 endif | |
592 | |
593 You can now use vim in diff-mode, e.g. to compare two files in read-only | |
594 mode: > | |
595 | |
596 $ VIM -D/R <FILE1> <FILE2> | |
597 | |
598 You can also define new symbols for vimdiff, e.g.: > | |
599 | |
600 $ VIMDIFF :== 'VIM' -D/R | |
601 $ GVIMDIFF :== 'GVIM' -D/R | |
602 | |
603 You can now compare files in 4 ways: > | |
604 | |
605 1. VMS diff: $ DIFF <FILE1> <FILE2> | |
606 2. GNU diff: $ GDIFF <FILE1> <FILE2> | |
607 3. VIM diff: $ VIMDIFF <FILE1> <FILE2> | |
608 4. GVIM diff: $ GVIMDIFF <FILE1> <FILE2> | |
609 | |
610 ( Coen Engelbarts, Vim 6.1) | |
611 | |
612 | |
613 8.13 Allow '$' in C keywords | |
614 | |
615 DEC C uses many identifiers with '$' in them. This is not allowed in ANSI C, | |
616 and vim recognises the '$' as the end of the identifier. You can change this | |
617 with the |iskeyword|command. | |
618 Add this command to your .vimrc file: > | |
619 | |
620 autocmd FileType c,cpp,cs set iskeyword+=$ | |
621 | |
622 You can also create the file(s) $VIM/FTPLUGIN/C.VIM (and/or CPP.VIM and | |
623 CS.VIM) and add this command: > | |
624 | |
625 set iskeyword+=$ | |
626 | |
627 Now word-based commands, e.g. the '*'-search-command and the CTRL-] | |
628 tag-lookup, work on the whole identifier. (Ctags on VMS also supports '$' in | |
629 C keywords since ctags version 5.1.) | |
630 | |
631 ( Coen Engelbarts, Vim 6.1) | |
632 | |
633 8.14 VIMTUTOR for beginners | |
634 | |
635 It exits VIMTUTOR.COM DCL script that can help Vim beginners to learn/make | |
636 first steps with Vim on OpenVMS. Depending of binary distribution you may start | |
637 it with: > | |
638 | |
639 @vim:vimtutor | |
640 | |
641 (Thomas.R.Wyant III, Vim 6.1) | |
642 | |
643 ============================================================================== | |
644 | |
645 9. VMS related changes *vms-changes* | |
646 | |
647 Version 6.3 (2004 May 10) | |
648 - Improved vms_read function | |
649 - CTAGS v5.5.4 included | |
650 - Documentation corrected and updated | |
651 | |
652 Version 6.2 (2003 May 7) | |
653 - Corrected VMS system call results | |
654 - Low level character input is rewritten | |
655 - Correction in tag and quickfix handling | |
656 - First GTK build | |
657 - Make file changes | |
658 - GTK feature added | |
659 - Define for OLD_VMS | |
660 - OpenVMS version 6.2 or older | |
661 - Documentation updated with GTK features | |
662 - CTAGS v5.5 included | |
663 - VMS VIM tutor created | |
664 | |
665 Version 6.1 (2002 Mar 25) | |
666 - TCL init_tcl() problem fixed | |
667 - CTAGS v5.4 included | |
668 - GNU tools binaries for OpenVMS | |
669 - Make file changes | |
670 - PERL, PYTHON and TCL support improved | |
671 - InstallVMS.txt has a detailed description HOWTO build | |
672 - VMS/Unix file handling rewritten | |
673 - Minor casting and bug fixes | |
674 | |
675 Version 6.0 (2001 Sep 28) | |
676 - Unix and VMS code has been merged | |
677 - separated "really" VMS related code | |
678 - included all possible Unix functionality | |
679 - simplified or deleted the configuration files | |
680 - makefile MAKE_VMS.MMS reviewed | |
681 - menu changes (fixed printing, CTAGS and XXD usage) | |
682 - fixed variable RMS record format handling anomaly | |
683 - corrected syntax, ftplugin etc files load | |
684 - changed expand_wildcards and expandpath functions to work more general | |
685 - created OS_VMS_FILTER.COM - DECC->VAXC pre-processor directive convert | |
686 script. | |
687 - Improved code's VAXC and new DECC compilers compatibility | |
688 - changed quickfix parameters: | |
689 - errormessage format to suite DECC | |
690 - search, make and other commands to suite VMS system | |
691 - updated and renamed MMS make files for Vim and CTAGS. | |
692 - CTAGS has been removed from source distribution of Vim but it will remain | |
693 in OpenVMS binary distributions. | |
694 - simplified build/configuration procedure | |
695 - created INSTALLvms.txt - detailed compiling instructions under VMS. | |
696 - updated test scripts. | |
697 | |
698 Version 5.8 (2001 Jun 1) | |
699 - OS_VMS.TXT updated with new features. | |
700 - other minor fixes. | |
701 - documentation updated | |
702 - this version had been tested much more than any other OpenVMS version | |
703 earlier | |
704 | |
705 Version 5.7 (2000 Jun 24) | |
706 - New CTAGS v5.0 in distribution | |
707 - Documentation updated | |
708 | |
709 Version 5.6 (2000 Jan 17) | |
710 - VMS filename related changes: | |
711 - version handling (open everything, save to new version) | |
712 - correct file extension matching for syntax (version problem) | |
713 - handle <,> characters and passwords in directory definition | |
714 - handle internode/remote invocation and editing with passwords | |
715 - OpenVMS files will be treated case insensitive from now | |
716 - corrected response of expand("%:.") etc path related functions | |
717 (in one word: VMS directory handling internally) | |
718 - version command | |
719 - corrected (+,-) information data | |
720 - added compiler and OS version | |
721 - added user and host information | |
722 - resolving $VIM and $VIMRUNTIME logicals | |
723 - VMS port is in MAX_FEAT (maximum features) club with Unix, Win32 and OS/2. | |
724 - enabled farsi, rightleft etc. features | |
725 - undo level raised up to 1000 | |
726 - Updated OS_VMS.MMS file. | |
727 - maximum features ON is default | |
728 - Vim is compilable with +perl, +python and +tcl features. | |
729 - improved MMK compatibility | |
730 - Created MAKEFILE_VMS.MMS, makefile for testing Vim during development. | |
731 - Defined DEC terminal VT320 | |
732 - compatibility for VT3*0, VT2*0 and VT1*0 - ANSI terminals | |
733 backwards, but not VT340 and newer with colour capability. | |
734 - VT320 is default terminal for OpenVMS | |
735 - these new terminals are also fast ttys (default for OpenVMS). | |
736 - allowed dec_mouse ttym | |
737 - Updated files vimrc and gvimrc with VMS specific suggestions. | |
738 - OS_VMS.TXT updated with new features. | |
739 | |
740 Version 5.5 (1999 Dec 3) | |
741 - Popup menu line crash corrected. | |
742 - Handle full file names with version numbers. | |
743 - Directory handling (CD command etc.) | |
744 - Corrected file name conversion VMS to Unix and v.v. | |
745 - Correct response of expand wildcards | |
746 - Recovery is working from this version under VMS as well. | |
747 - Improved terminal and signal handing. | |
748 - Improved OS_VMS.TXT | |
749 | |
750 Version 5.4 (1999 Sep 9) | |
751 - Cut and paste mismatch corrected. | |
752 - Motif directories during open and save are corrected. | |
753 | |
754 Version 5.3 (1998 Oct 12) | |
755 - Minor changes in the code | |
756 - Standard distribution with +GUI option | |
757 | |
758 Version 5.1 (1998 Apr 21) | |
759 - Syntax and DEC C changes in the code | |
760 - Fixing problems with the /doc subdirectory | |
761 - Improve OS_VMS.MMS | |
762 | |
763 Version 4.5 (1996 Dec 16) | |
764 - First VMS port by Henk Elbers <henk@xs4all.nl> | |
765 | |
766 ============================================================================== | |
767 | |
768 10. Authors *vms-authors* | |
769 | |
770 OpenVMS documentation and executables are maintained by: | |
771 Zoltan Arpadffy <arpadffy@polarhome.com> | |
772 | |
773 This document uses parts and remarks from earlier authors and contributors | |
774 of OS_VMS.TXT: | |
775 Charles E. Campbell, Jr. <cec@gryphon.gsfc.nasa.gov> | |
776 Bruce Hunsaker <BNHunsaker@chq.byu.edu> | |
777 Sandor Kopanyi <sandor.kopanyi@mailbox.hu> | |
778 | |
779 vim:tw=78:ts=8:ft=help:norl: |