1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
|
-------------------
Running vile on VMS
-------------------
vile can be built using either the VAXC or DECC compiler. use vmsbuild.com
as the build script, which accepts this syntax:
$ @vmsbuild [vile [<compiler> [<bldtarget>]]] ! builds vile
$ @vmsbuild xvile [<compiler> [<bldtarget>]] ! builds xvile
where:
<compiler> :== { decc | vaxc }
<target> :== build target, generally used by developers
the default compiler on VAX hosts is vaxc, else decc (Alpha hosts).
when choosing a compiler, carefully read the "warning" section below. if
building _both_ vile and xvile from the _same_ directory, refer to the
"Configuration Note" at the top of vmsbuild.com.
Tested systems
--------------
VMS system version 5.4-2
VAX-C version 3.2
and
VMS system version 6.1, 6.2
DEC C version 5.0, 5.2
and
VMS/VAX system version V7.1
DEC C V5.6-003
+++++++++++++++++++++++++++
warning warning warning
+++++++++++++++++++++++++++
when selecting a target compiler, beware of this problem:
on a VAX, the DEC-C compiler and/or its run-time library cause
vile to change the "Revised time" of every file the editor _reads_.
you won't like this when using mms or a make clone. the VAXC
compiler does not suffer from this problem.
configuration where problem was observed:
DEC C V5.6-003 on OpenVMS VAX V7.1
General installation instructions
---------------------------------
installation of vile's components is the responsibility of the end user.
after the build, copy all resultant executables (except mktbls.exe) and the
file vile.hlp to a directory of your choice. finally, create a foreign
symbol that invokes the editor from the installation directory. ex:
vile :== $install_disk:[install_dir]vile.exe
Creating a startup file
-----------------------
most users will configure the editor. this is accomplished by creating a
startup file, called "vile.rc", and adding various settings and macros as
described in vile.hlp . vile searches for the startup file in these
locations (and in the order listed):
current working directory
the directory specified by the symbol HOME
the vile executable directory [this often does not work]
if the symbol VILE_STARTUP_PATH exists then
search each comma-delimited directory specified in this symbol
else search
sys$login
sys$device:[vmstools]
sys$library
end if
sys$system
sys$library
VMS-specific features
---------------------
vile includes several useful vms-specific modes, which are described in
vile.hlp in the section entitled "VMS specifics".
|
