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]
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   If you are installing jed on an ALPHA system, use DECCmake.com instead of
46   VMSmake.com.
47
48   Currently the file is structured such that typing `@vmsmake' at the VMS
49   DCL prompt will make jed.exe for systems which have DEC's VMS C compiler.
50   For systems that use GCC, `@vmsmake gcc' might also work.  That is:
51
52     $ @vmsmake          ! VMS CC
53     $ @vmsmake gcc      ! GNU GCC
54     $ @deccmake         ! ALPHA/AXP systems with DEC C.
55
56   Although descrip.mms files are included for use with `mms', I cannot
57   guarantee them to work on ALPHA/AXP systems.  Use `deccmake.com' instead.
58
59   After building the JED.EXE and XJED.EXE images, copy them into the
60   JED_ROOT:[BIN] directory, giving them architecture-specific names such as
61   JED.VAX_EXE or JED.ALPHA_EXE.
62
634. Put one of the following in either your sylogin.com for all users
64   or in login.com.  Note that JED_ROOT must be defined!
65
66     $ @JED_ROOT:[bin]init_jed.com  0 0     ! no kept editor/no mail
67     $ @JED_ROOT:[bin]init_jed.com  0 1     ! no kept editor/ use for mail
68     $ @JED_ROOT:[bin]init_jed.com  1 0     ! kept editor/ no mail (most systems)
69     $ @JED_ROOT:[bin]init_jed.com  1 1     ! kept editor/use for mail
70
71   The first flag indicates whether jed should be installed as a standalone
72   executable or as a kept editor.  Use 1 for kepteditor or 0 for standalone.
73   The second flag indicates whether or not mail$edit logical should be
74   defined to point to jed.  If it is set to 1, vms mail will call jed to
75   edit the mail message.  If JED is run as a kept editor, mail will simply
76   attach to JED for editing.   Most systems will probably use the 3rd
77   choice above.
78
795. The file jed.rc contains the default keysettings for most users.  On VMS
80   this means users will get both edt and emacs keybindings.  It is not
81   necessary for every user to have a copy of this file.  JED will search
82   for jed.rc in sys$login first and if not found, it will load jed.rc from
83   JED_ROOT:[LIB].
84
856. It may be necessary to edit site.sl if you have an info directory where
86   info files are kept.  If you do not understand this statement, then you
87   do not have info.
88
897. Make sure all users who will be using JED have permission to do so.  The
90   easiest way to do this is to type:
91
92     $ set file/protection=(w:re) jed_root:[000000...]
93
948. Optional but highly recommended.  Preparse the S-Lang files.  This
95   is done by running JED as:
96
97         $ jed -batch -n -l preparse
98
99   This creates pre-parsed *.slc files that load quicker than *.sl files.
100   It is also a convenient test to see if JED has been installed properly.
101
102   Once you do this, make sure that you give the WORLD read permission on
103   the files.  Do:
104
105         $ set file/protection=(W:RE) JED_ROOT:[lib]*.slc
106
107     !!! Do not use *.*.   Use *.slc.
108
1099. It is possible that you have the PC distribution.  This distribution
110   truncates filenames to 8+3 style names.  If you have
111   JED_ROOT:[LIB]VMS_SHEL.COM, rename it to VMS_SHELL.COM.  Also make sure
112   that JED_ROOT:[INFO] contains dir.info and not dir.inf.
113
11410. Read the bit about defaults.sl in install.all for customizing your
115    distribution.
116
11711. Please email bugs, installation problems, or hints about how to better
118    install JED to `davis@space.mit.edu'.
119