summaryrefslogtreecommitdiffstats
path: root/runtime/doc/os_vms.txt
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2010-01-06 20:52:26 +0100
committerBram Moolenaar <Bram@vim.org>2010-01-06 20:52:26 +0100
commit8f3f58f2c361f1b7241128d9821f88d8a30aa066 (patch)
treebd5827eec39ddf8e6a94919a6a541765882f00d4 /runtime/doc/os_vms.txt
parent28c37959871b83fd5d1d621f70bce29dc3f21ba4 (diff)
Update documentation files.
Diffstat (limited to 'runtime/doc/os_vms.txt')
-rw-r--r--runtime/doc/os_vms.txt40
1 files changed, 20 insertions, 20 deletions
diff --git a/runtime/doc/os_vms.txt b/runtime/doc/os_vms.txt
index 0d75906289..39efcf6460 100644
--- a/runtime/doc/os_vms.txt
+++ b/runtime/doc/os_vms.txt
@@ -1,4 +1,4 @@
-*os_vms.txt* For Vim version 7.2. Last change: 2008 Aug 19
+*os_vms.txt* For Vim version 7.2. Last change: 2009 Oct 28
VIM REFERENCE MANUAL
@@ -139,9 +139,9 @@ Use: >
define/nolog VIMRUNTIME device:[path.vim.vim60]
define/nolog TMP device:[path.tmp]
-to get vim.exe to find its document, filetype, and syntax files, and to
+To get vim.exe to find its document, filetype, and syntax files, and to
specify a directory where temporary files will be located. Copy the "runtime"
-subdirectory of the vim distribution to vimruntime.
+subdirectory of the Vim distribution to vimruntime.
Logicals $VIMRUNTIME and $TMP are optional.
@@ -217,7 +217,7 @@ You just have to define the "whole" path: >
$ define VIM "<server_name>[""user password""]::device:<path>"
$ vi*m :== "mcr VIM:VIM.EXE"
-as for example: >
+As for example: >
$ define VIM "PLUTO::RF10:[UTIL.VIM]"
$ define VIM "PLUTO""ZAY mypass""::RF10:[UTIL.VIM]" ! if passwd required
@@ -234,7 +234,7 @@ then add to the SYS$STARTUP:SYLOGICALS.COM >
$ define/nolog/sys VIM device:<path>
$ define/nolog/sys TMP SYS$SCRATCH
-and to the SYS$STARTUP:SYLOGIN.COM >
+And to the SYS$STARTUP:SYLOGIN.COM >
$ vi*m :== mcr VIM:VIM.EXE
$ gv*im:== spawn/nowait/input=NLA0 mcr VIM:VIM.EXE -g -GEOMETRY 80x40
@@ -396,7 +396,7 @@ It is possible to use Vim as an internode editor.
vi "<server>""username passwd""::<device>:<path><filename>;<version>"
-example: >
+Example: >
vi "pluto""zay passwd""::RF10:<USER.ZAY.WORK>TEST.C;1"
Note: syntax is very important, otherwise VMS will recognize more parameters
@@ -418,7 +418,7 @@ and run the command procedure below: >
$ end:
Note: Never use it in a clustered environment (you do not need it), loading
-could be very-very slow, but even faster then a local Emacs. :-)
+could be very-very slow, but even faster than a local Emacs. :-)
(Zoltan Arpadffy, Vim 5.6)
@@ -575,12 +575,12 @@ boxes that is meant to solve GNU problems on OpenVMS.
8.12 diff-mode
-Vim 6.0 and higher supports vim diff-mode (See |new-diff-mode|, |diff-mode|
+Vim 6.0 and higher supports Vim diff-mode (See |new-diff-mode|, |diff-mode|
and |08.7|). This uses the external program 'diff' and expects a Unix-like
output format from diff. The standard VMS diff has a different output
-format. To use vim on VMS in diff-mode, you need to:
+format. To use Vim on VMS in diff-mode, you need to:
1 Install a Unix-like diff program, e.g. GNU diff
- 2 Tell vim to use the Unix-like diff for diff-mode.
+ 2 Tell Vim to use the Unix-like diff for diff-mode.
You can download GNU diff from the VIM-VMS website, it is one of the GNU
tools in http://www.polarhome.com/vim/files/gnu_tools.zip. I suggest to
@@ -594,7 +594,7 @@ prompt: >
GDIFF :== $GNU:DIFF.EXE
-Now you need to tell vim to use the new diff program. Take the example
+Now you need to tell Vim to use the new diff program. Take the example
settings from |diff-diffexpr| and change the call to the external diff
program to the new diff on VMS. Add this to your .vimrc file: >
@@ -615,7 +615,7 @@ program to the new diff on VMS. Add this to your .vimrc file: >
endfunction
endif
-You can now use vim in diff-mode, e.g. to compare two files in read-only
+You can now use Vim in diff-mode, e.g. to compare two files in read-only
mode: >
$ VIM -D/R <FILE1> <FILE2>
@@ -638,7 +638,7 @@ You can now compare files in 4 ways: >
8.13 Allow '$' in C keywords
DEC C uses many identifiers with '$' in them. This is not allowed in ANSI C,
-and vim recognises the '$' as the end of the identifier. You can change this
+and Vim recognises the '$' as the end of the identifier. You can change this
with the |iskeyword|command.
Add this command to your .vimrc file: >
@@ -667,7 +667,7 @@ start it with: >
8.14 Slow start in console mode issue
-As GUI/GTK Vim works equally well in console mode, many administartors
+As GUI/GTK Vim works equally well in console mode, many administrators
deploy those executables system wide.
Unfortunately, on a remote slow connections GUI/GTK executables behave rather
slow when user wants to run Vim just in the console mode - because of X environment detection timeout.
@@ -680,7 +680,7 @@ both GUI/GTK build and just console build executables, like below: >
|----- syntax
vimrc (system rc files)
gvimrc
- gvim.exe (the remaned GUI or GTK built vim.exe)
+ gvim.exe (the renamed GUI or GTK built vim.exe)
vim.exe (the console only executable)
Define system symbols like below in for ex in LOGIN.COM or SYLOGIN.COM: >
@@ -713,11 +713,11 @@ View of Cluster from system ID 11655 node: TOR
¦ ODIN ¦ VMS V7.3-2 ¦ MEMBER ¦
+---------------------------------+
-It is convinient to have a common VIM directory but execute different
+It is convenient to have a common VIM directory but execute different
executables.
There are more solutions for this problem:
-solution 1. all executables in the same directory with different names
+Solution 1. All executables in the same directory with different names
This is easily done with the following script that can be added
to the login.com or sylogin.com: >
@@ -737,7 +737,7 @@ to the login.com or sylogin.com: >
$ vi*m :== mcr vim:VIM.EXE_IA64
$ endif
-solution 2. different directories: >
+Solution 2. Different directories: >
$ if f$getsyi("NODE_HWTYPE") .eqs. "VAX"
$ then
@@ -757,8 +757,8 @@ solution 2. different directories: >
$! VIMRUNTIME must be defined in order to find runtime files
$ define/nolog VIMRUNTIME RF10:[UTIL.VIM72]
-A good examle for this approach is the [GNU]gnu_tools.com script from GNU_TOOLS.ZIP
-package downloadable from http://www.polarhome.com/vim/
+A good example for this approach is the [GNU]gnu_tools.com script from
+GNU_TOOLS.ZIP package downloadable from http://www.polarhome.com/vim/
(Zoltan Arpadffy, Vim 7.2)