vim: runtime/doc/os_vms.txt comparison

comparison runtime/doc/os_vms.txt @ 2033:de5a43c5eedc

Update documentation files.

author	Bram Moolenaar <bram@zimbu.org>
date	Wed, 06 Jan 2010 20:52:26 +0100
parents	71eaeb69efe4
children	7c8c7c95a865

comparison

equal deleted inserted replaced

-:592032e9e167
+:de5a43c5eedc
-*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
 	define/nolog VIM	device:[path.vim]
 	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.
 If $VIMRUNTIME is not set, Vim will guess and try to set up automatically.
 Read more about it at :help runtime
 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
 You can also use the $VIMRUNTIME logical to point to the proper version of Vim
 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
 It is possible to use Vim as an internode editor.
 1. Edit some file from remote node: >
 	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
 instead of one (resulting with: file not found)
 	$ write sys$output " Please enter username and password as a parameter."
 	$ write sys$output " Example: @SETVIM.COM username passwd"
 	$ 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)
 8.6 Terminal problems
 ( Zoltan Arpadffy, Vim 6.1)
 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
 unpack it in a separate directory "GNU" and create a logical GNU: that
 points to that directory, e.g: >
 You may also want to define a symbol GDIFF, to use the GNU diff from the DCL
 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: >
 " Set up vimdiff options
 if v:version >= 600
 	   silent execute "!mc GNU:diff.exe -a " . opt . v:fname_in . " " .  v:fname_new .
 		\  " > " . v:fname_out
 	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>
 You can also define new symbols for vimdiff, e.g.: >
 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: >
 autocmd FileType c,cpp,cs  set iskeyword+=$
 (Thomas.R.Wyant III, Vim 6.1)
 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.
 Luckily, there is a simple solution for that. Administrators need to deploy
 |- vim72
 |----- doc
 |----- 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: >
 	$ define/nolog VIM RF10:[UTIL.VIM72] ! where you VIM directory is
 � TOR    � VMS V7.3-2   � MEMBER  �
 � TITAN2 � VMS V8.3     � MEMBER  �
 � 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: >
 	$ if f$getsyi("NODE_HWTYPE") .eqs. "VAX"
 	$ then
 	$ then
 	$      say "IA64 platform"
 	$      vi*m :== mcr vim:VIM.EXE_IA64
 	$ endif
-solution 2. different directories: >
+Solution 2.  Different directories: >
 	$ if f$getsyi("NODE_HWTYPE") .eqs. "VAX"
 	$ then
 	$       say "VAX platform"
 	$       define/nolog VIM RF10:[UTIL.VAX_EXE] ! VAX executables
 	$      define/nolog VIM RF10:[UTIL.IA64_EXE] ! IA64 executables
 	$ endif
 $! 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
+A good example for this approach is the [GNU]gnu_tools.com script from
-package downloadable from http://www.polarhome.com/vim/
+GNU_TOOLS.ZIP package downloadable from http://www.polarhome.com/vim/
 (Zoltan Arpadffy, Vim 7.2)
 ==============================================================================

Mercurial > vim

comparison runtime/doc/os_vms.txt @ 2033:de5a43c5eedc