os_vms.txt

MSYS在windows下模拟了一个类unix的终端

*os_vms.txt*    For Vim version 5.8   Last change: 2001 May 18


		  VIM REFERENCE MANUAL


							*VMS* *vms*
This file contains the particularities for the VMS version of Vim.
You can reach this information file by typing :help VMS in Vim command
prompt.

 1. Getting started	|vms-started|
 2. Download files	|vms-download|
 3. Compiling		|vms-compiling|
 4. Problems		|vms-problems|
 5. Deploy		|vms-deploy|
 6. Practical usage	|vms-usage|
 7. GUI mode questions	|vms-gui|
 8. Useful notes	|vms-notes|
 9. Changes		|vms-changes|
10. Authors		|vms-authors|

==============================================================================

1. Getting started					*vms-started*

Vim (Vi IMproved) is a vi-compatible text editor that runs on nearly every
operating system known to humanity.  Now use Vim on OpenVMS too, in character
or X/Motif environment.  It is fully featured and absolutely compatible with
Vim on other operating systems.

==============================================================================

2. Download files					*vms-download*

You can download the Vim source code by ftp from the official Vim site:
	ftp://ftp.vim.org/pub/vim/
Or use one of the mirrors:
	ftp://ftp.vim.org/pub/vim/MIRRORS

You will need both the Unix and Extra archives to build vim.exe for VMS.
For using Vim's full power you will need the runtime files as well.

You can download precompiled executables from:
	http://www.polarfox.com/vim/

==============================================================================

3. Compiling						*vms-compiling*

Unpack the Unix and Extra archives together into one directory.  In the <.SRC>
subdirectory you should find the make file OS_VMS.MMS.  By editing this file
you may choose between building the character, GUI and debug version. There
are also additional options for Perl, Python and Tcl support.

You will need either the DECSET mms utility or the freely available clone of
it called mmk (VMS has no make utility in the standard distribution). You can
download mmk from http://www.openvms.digital.com/freeware/MMK/

If you have MSS on your system, the command

>	mms /descrip=os_vms.mms

will start building your own customised version of Vim.
The adequate command for mmk is:

>	mmk /descrip=os_vms.mms

==============================================================================

4. Problems						*vms-problems*

The code has been tested under Open VMS 6.2 - 7.1 on Alpha and VAX platforms
with the DECC compiler. It should work without bigger problems.
If it happened that your system does not have some include libraries you can
tune up in OS_VMS_CONF.H or GUI_VMS_CONF.H files.

If you decided to build Vim with +perl, +python, etc. options, first you need
to download OpenVMS distributions of Perl and Python. Build and deploy the
libraries and change adequate lines in OS_VMS.MMS file. There should not be
problem from Vim side.

Note: Under VAX it should work with DEC C compiler without problem, but the
code is not compilable with the old VAX C compiler.

MMS_VIM.EXE is building together with VIM.EXE, but for CTAGS.EXE and XXD.EXE
you should change to subdirectory <.CTAGS> or <.XXD> and build them
separately. You have to be prepared that the CTAGS and XXD make files are not
always up to date.

Advanced users may try some acrobatics in FEATURE.H file also.

It is possible to compile with +xfontset +xim options too, but then you have
to set up GUI fonts etc. correctly. See. :help xim from Vim command prompt.

==============================================================================

5. Deploy						*vms-deploy*

Vim uses a special directory structure to hold the document and runtime files:

   vim (or wherever)
    |- tmp
    |- vim55
    |----- doc
    |----- syntax
    |- vim56
    |----- doc
    |----- syntax
    vimrc    (system rc files)
    gvimrc

Use:

>	define/nolog device:[leading-path-here.vim]       vim
>	define/nolog device:[leading-path-here.vim.vim56] vimruntime
>	define/nolog device:[leading-path-here.tmp]       tmp

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.

Note: Logicals $VIMRUNTIME and $TMP are optional. Read more at :help runtime

==============================================================================

6. Practical usage					*vms-usage*

Usually you want to run just one version of Vim on your system, therefore
it is enough to dedicate one directory for Vim.
Copy all Vim runtime directory structure to the deployment position.
Add the following lines to your LOGIN.COM (in SYS$LOGIN directory).
Set up logical $VIM as:

>	$ define VIM device:<path>

Set up some symbols:

>	$ ! vi starts Vim in chr. mode.
>	$ vi*m  :== mcr device:<path>VIM.EXE

>	$ !gvi starts Vim in GUI mode.
>	$ gv*im :== spawn/nowait mcr device:<path>VIM.EXE -g

Create .vimrc and .gvimrc files in your home directory (SYS$LOGIN).

The easiest way is just rename example files. You may leave the menu file
(MENU.VIM) and files vimrc and gvimrc in the original $VIM directory. It will
be default setup for all users, and for users is enough just to have their
own additions or resetting in home directory in files .vimrc and .gvimrc.
It should work without problems.

Note: Remember, system rc files (default for all users) does not have leading
"." So, system rc files are:

>	VIM$:vimrc
>	VIM$:gvimrc
>	VIM$:menu.vim

and user's customised rc files are:

>	sys$login:.vimrc
>	sys$login:.gvimrc

You can check that everything is on the right place with the :version command.

Example LOGIN.COM:

>	$ define/nolog VIM RF10:[UTIL.VIM]
>	$ vi*m  :== mcr VIM:VIM.EXE
>	$ gv*im :== spawn/nowait mcr VIM:VIM.EXE -g
>	$ set disp/create/node=192.168.5.223/trans=tcpip

Note: This set-up should be enough, if you are working on standalone server or
clustered environment, but if you want to use Vim as internode editor, it
will satiate you as well. 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:

>	$ define VIM "PLUTO::RF10:[UTIL.VIM]"
>	$ define VIM "PLUTO""ZAY mypass""::RF10:[UTIL.VIM]" ! if passwd required

You can also use $VIMRUNTIME logical to point to proper version of Vim if you
have installed more versions in the same time. If $VIMRUNTIME is not defined
Vim will borrow value from $VIM logical. You can find more information about
$VIMRUNTIME logical by typing :help runtime as a Vim command.

==============================================================================

7. GUI mode questions					*vms-gui*

VMS is not a native X window environment, so you can not start Vim in GUI mode
"just like that". But anyhow it is not too complicate to get a running Vim.

1) If you are working on the VMS X console:
   Start Vim with the command:

>	$ mc device:<path>VIM.EXE -g

   or type :gui as a command to the Vim command prompt. For more info :help gui

2) If you are working on other X window environment as Unix or some remote X
   VMS console. Set up display to your host with:

>	$ set disp/create/node=<your IP address>/trans=<transport-name>

   and start Vim as in point 1. You can find more help in VMS documentation or
   type: help set disp in VMS prompt.
   Examples:

>	$ set disp/create/node=192.168.5.159             ! default trans is DECnet
>	$ set disp/create/node=192.168.5.159/trans=tcpip ! TCP/IP network
>	$ set disp/create/node=192.168.5.159/trans=local ! display on the same node

Note: you should define just one of these.
For more information type $help set disp in VMS prompt.

3) If you are working on MS Windows or other non X window environment
   You need to set up one X server and run Vim as in point 2.
   For MS Windows there are available free X servers as MIX , Omni X etc.

==============================================================================