10. Building and installing JED requires that you also have the S-Lang library
2   to link to.  Build it first.
3
41. Pick some place for JED.
5   JED is distributed in a TREE structure:
6
7     JED_ROOT:
8     JED_ROOT:[src]
9     JED_ROOT:[info]
10     JED_ROOT:[doc]
11     JED_ROOT:[lib]
12     JED_ROOT:[bin.vms]
13
14   Here JED_ROOT can be anything.  Its value is up to you.  It should be a
15   concealed logical.  For example, suppose that JED is unpacked in a
16   directory
17
18       dev$source:[editors.jed]
19
20   You CANNOT simply define JED_ROOT to be this value.  Instead, it must be a
21   concealed logical defined as:
22
23     $ define/job/trans=(concealed) jed_root dev$source:[editors.jed.]
24
25   It is important to note the final `.' after jed.  This logical must be
26   placed in the job table; system managers may put it in the system table
27   instead.
28
29   Instead of the above, I recommend something like:
30
31     $ jedroot = f$logical("DEV$SOURCE") - "]" + "EDITORS.JED.]"
32     $ define/job/trans=(concealed) jed_root 'jedroot'
33
34   It is best to put the definition in the appropriate startup file
35   (systartup.com, sylogin.com, login.com).
36
37   Note: If are currently using a very old version of JED and and you have
38   JED_LIBRARY defined as a logical, please remove it.
39
402. Build the jed.exe executable file: After you have properly setup the
41   JED_ROOT logical, change to the directory 'jed_root:[src]'.  You should
42   now edit the 'vmsmake.com' file to indicate the location of the S-Lang
43   library constructed in step 0. Directions are included in VMSMAKE.COM.
44
45   Currently the file is structured such that typing `@VMSMAKE' at the VMS
46   DCL prompt will make jed.exe for systems which have DEC's VMS C compiler.
47   For systems that use GCC, `@vmsmake gcc' might also work.  That is:
48
49     $ @vmsmake          ! VMS CC, DEC C
50     $ @vmsmake gcc      ! GNU GCC
51
52   After building the JED.EXE and XJED.EXE images, copy them into the
53   JED_ROOT:[BIN.VMS] directory, giving them architecture-specific
54   names such as JED.VAX_EXE or JED.ALPHA_EXE.
55
564. Put one of the following in either your sylogin.com for all users
57   or in login.com.  Note that JED_ROOT must be defined!
58
59     $ @JED_ROOT:[bin.vms]init_jed.com  0 0 ! no kept editor/no mail
60     $ @JED_ROOT:[bin.vms]init_jed.com  0 1 ! no kept editor/ use for mail
61     $ @JED_ROOT:[bin.vms]init_jed.com  1 0 ! kept editor/ no mail (most systems)
62     $ @JED_ROOT:[bin.vms]init_jed.com  1 1 ! kept editor/use for mail
63
64   The first flag indicates whether jed should be installed as a standalone
65   executable or as a kept editor.  Use 1 for kepteditor or 0 for standalone.
66   The second flag indicates whether or not mail$edit logical should be
67   defined to point to jed.  If it is set to 1, vms mail will call jed to
68   edit the mail message.  If JED is run as a kept editor, mail will simply
69   attach to JED for editing.   Most systems will probably use the 3rd
70   choice above.
71
725. The file JED_ROOT:[lib]jed.rc contains some default settings for
73   users that do not have a jed.rc file in SYS$LOGIN.  If
74   SYS$LOGIN:jed.rc exists, then it will be used instead.  By default,
75   jed starts up with EMACS keybindings. You may want to specify some
76   other emulation, such as the Borland IDE emulation or even EDT
77   emulation.  It is not necessary for every user to have a copy of
78   this file.
79
806. It may be necessary to edit site.sl if you have an info directory where
81   info files are kept.  If you do not understand this statement, then you
82   do not have info.
83
847. Make sure all users who will be using JED have permission to do so.  The
85   easiest way to do this is to type:
86
87     $ set file/protection=(w:re) jed_root:[000000...]
88
898. Optional but highly recommended.  Preparse the S-Lang files.  This
90   is done by running JED as:
91
92         $ jed -batch -n -l preparse
93
94   This creates pre-parsed *.slc files that load quicker than *.sl files.
95   It is also a convenient test to see if JED has been installed properly.
96
97   Once you do this, make sure that you give the WORLD read permission on
98   the files.  Do:
99
100         $ set file/protection=(W:RE) JED_ROOT:[lib]*.slc
101
102     !!! Do not use *.*.   Use *.slc.
103
1049. It is possible that you have the PC distribution.  This distribution
105   truncates filenames to 8+3 style names.  If you have
106   JED_ROOT:[LIB]VMS_SHEL.COM, rename it to VMS_SHELL.COM.  Also make sure
107   that JED_ROOT:[INFO] contains dir.info and not dir.inf.
108
10910. Read the bit about defaults.sl in install.all for customizing your
110    distribution.
111
11211. Please email bugs, installation problems, or hints about how to better
113    install JED to `davis@space.mit.edu'.
114