home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-387-Vol-3of3.iso
/
e
/
epmtex12.zip
/
INSTALL.DOC
< prev
next >
Wrap
Text File
|
1993-02-19
|
15KB
|
355 lines
TeX Macro Enhancements for EPM 5.51
Version 1.2c
Jon Hacker
Feb 17, 1993
Introduction:
~~~~~~~~~~~~
The E macro file tex.e when compiled with the IBM enhanced Editor translator
ETPM.EXE will add a TeX pull down menu to the EPM menu bar to files with
extensions .tex*, .sty, or .bbl. A custom TeX extension can also be
specified by defining MY_TEX_FILE_TYPE in the user's mycnf.e file.
Menu items in the TeX pull down menu allow the user to TeX (or LaTeX), preview
(portrait and landscape), and print (portrait and landscape) the TeX file
currently active in EPM. A custom 'user' mode may also be defined for special
needs unique to the user.
The E macro file texkeys.e when compiled with the IBM enhanced Editor translator
ETPM.EXE will add TeX syntax assist and TeX accelerator keys to files with
extensions .tex*, .sty, or .bbl. A custom TeX extension can also be specified
by defining MY_TEX_FILE_TYPE in the user's mycnf.e file.
German users are advised to read the section 'Support for German Users' at the
end of this document. Other languages can be added in a similar way.
Requirements:
~~~~~~~~~~~~
The TeX E macro package supplied with this package needs to be compiled before
it can be incorporated into EPM. You will need to obtain the complete EPM 5.51
package from IBM to do this.
The EPM package is available for free from the following Internet sites:
software.watson.ibm.com /pub/os2/epm
ftp-os2.nmsu.edu /pub/os2/ibm/epm
It should also be available from major OS/2 BBS services.
Installation of EPM 5.51:
~~~~~~~~~~~~~~~~~~~~~~~~
If you are not already familiar with compiling EPM macros on your machine, read
this section for additional help.
The installation of the EPM 5.51 package is sufficiently confusing that I will
try to give some hints to get you going as fast as possible.
The EPM package includes two hypertext files; the EPM User's Manual, and the EPM
Technical Reference. Both of these manuals provide a wealth of information on
EPM. It is highly recommended that you spend some time becoming familiar with
EPM, and the E macro language by reading through them.
1) Decide on a location for your EPM files. I suggest something like
\os2\epm or \epm. I would avoid using the \os2\apps directory
where the binaries for EPM 5.50 are placed in the GA release of OS/2 2.0.
There's just too much other crap in there already.
2) Unzip the EPM 5.51 files. You will want to take care where you put
everything. I recommend the following directory structure as suggested in
the EPMBBS.TXT file in the EPM package from IBM.
EPMAPP.ZIP - Unzip into your epm directory (eg \os2\epm)
EPM.EXE - The 5.51 version of the editor
ETPM.EXE - The 5.51 version of the macro compiler
PMMORE.EXE - Useful for debugging Rexx macros; entering RXSHELL from
EPM will start PMMORE and redirect STDOUT to this window.
SAY and TRACE output will be displayed there.
*.EX - the 5.51 version of the compiled macros
EPMHELP.QHL - the updated "quick help" file
EPMTECH.NDX - An index file for getting macro programmer help.
EPMBK.ZIP - Unpack into a directory in your BOOKSHELF path
EPMUSERS.INF - The EPM User's Guide
EPMTECH.INF - The EPM Macro Programmer's Technical Reference
EPMDLL.ZIP - Unpack into \os2\apps\dll or a directory in your LIBPATH. Delete
the obsolete ETK*550.DLL files leftover from EPM 5.50.
ETK*551.DLL - The E Toolkit DLLs.
EPMMAC.ZIP - Create a subdirectory under EPM called E_MACROS and unzip into it.
*.e - contains the macro files used to build the standard
*.ex files.
EPMHLP.ZIP - Updated EPM.HLP; unpack into \os2\help
EMPSMP.ZIP - Create a subdirectory under EPM called sampmacs and unzip this file
into it.
*.e - Sample E macro code; includes both useful programs and
building blocks that you can use in writing your own code.
3) Edit your config.sys file and make sure that your new epm directory
is included in you PATH statement. If you have IBM's TCP/IP networking
package, make sure your epm directory comes before \tcpip\bin in your PATH,
or delete the redundant EPM files as outlined in step (6).
4) Edit your config.sys file and make sure that the e_macros and sampmacs
subdirectories are included in your EPMPATH. EPMPATH is used by the ETPM
compiler to find macro files that are not in your current directory.
5) Use a file finding utility to hunt down all *.ex files. These are
the compiled E macros that EPM executes. The GA release of OS/2 puts them
in \os2\apps. Delete all redundant or older *.ex files on your system. You
only need them in your EPM directory. Having multiple copies of the *.ex
files may result in unpredictable behaviour from EPM.
----- OPTIONAL -------------------------------------------------------------
6) If you have IBM's TCP/IP networking package, there will be some more *.ex
files in \tcpip\bin. You can delete most of these files, or, if you prefer,
just make sure your your epm directory comes before \tcpip\bin in your PATH,
WARNING: LEAVE THE FOLLOWING UNIQUE TO LAMAIL *.EX FILES IN \TCPIP\BIN
~~~~~~
EPMLIST.EX
LAMEXTRA.EX
MAILLIST.EX
-----------------------------------------------------------------------------
7) Find all copies of EPM.EXE (v 5.50) and delete them. Likely hiding places
are \os2\apps and \tcpip\bin. You only need the one copy of epm.exe and it
should be in your epm directory. As long as it is in your PATH lamail will
find it.
8) Find all copies of ETK*550.DLL (v 5.50 dll's) and delete them. Likely
hiding places are \os2\apps\dll and \tcpip\dll. You only need the v5.51
dll's and they should be put somewhere in your LIBPATH (\os2\apps\dll is as
good as any) As long as it is in your LIBPATH lamail will find it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTE: Unfortunately, when you apply a CSD or Service Pack, copies of
EPM will again be placed in \os2\apps or \tcpip\bin and you will need
to do some housekeeping to get things back in order.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
9) I advise you get the spell checker option EPM_SPEL.ZIP for EPM. It is a
nice thing to have and is available from the following INTERNET source.
ftp-os2.nmsu.edu /pub/os2/2.0/editors
You will need to put the location of the dictionary (us.dct file) in the
paths section of the EPM preferences notebook. I put mine in
\os2\dictionary.
10) Copy the contents of the EPMTeX macro package to the e_macros subdirectory.
11) You should now be ready to compile your E macros. First, though, reboot
if you made any changes to config.sys.
COMPILING E MACROS;
~~~~~~~~~~~~~~~~~~
1) Read the section in the EPM user's manual 'Changing the default
configuration' to understand the use of EPM's configuration constants and
what they can do. The binaries included with the EPM package were compiled
with the constants defined in epmgcnf.smp in your e_macros subdirectory. If
these are OK with you, copy epmgcnf.smp to a file called mycnf.e in your
e_macros directory.
As an alternative, there is a file called jonscnf.e that is included with
my tex macro. If you would like to try it instead, copy it to a file called
mycnf.e in your e_macros directory. Even better, make up your own to setup
EPM as YOU want it.
2) Edit tex.e to point to your TeX applications. You will need to edit the
following lines: (the lines in there already are for a version of EMTEX on
my system. Yours will probably be different.)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTE: For reasons of speed, I do not load the command processor in spawned
shells by specifying the /n option in the start command. This means that
batch files will not run ( ie. TEX_EXEC=d:\mytex\texit.cmd ) since there
is no interpreter!
If you want to specify a batch file as the executable in a *.EXEC
variable, then change the corresponding *_IS_CMD variable to 1.
ie. TEX_EXEC = 'd:\texit.cmd'
TEX_IS_CMD = 1
Do not use the ^&plain or ^&lplain argument in the start command when
using batch files as the arguments will not make it through to the
command.
ie. if you specify TEX_EXEC = 'd:\texit.cmd ^&lplain' then texit.cmd
will not receive any arguments. But, TEX_EXEC = 'd:\texit.cmd' works
fine!
I have no explanation for this weirdness! Ask someone smarter.
If you want to run a previewer that is not a PM application, add the
switch /win or /fs as appropriate in the start commands in the command
procedure 'texvw'.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- TEX_EXEC points to your plain TeX compiler. The current TeX filename loaded
-- into EPM will be appended to it.
eg. TEX_EXEC = 'd:\emtex\bin\tex386.exe ^&plain'
TEX_IS_CMD = 1
-- LATEX_EXEC points to your LaTeX compiler. The current TeX filename loaded
-- into EPM will be appended to it.
eg. LATEX_EXEC = 'd:\emtex\bin\tex386.exe ^&lplain'
LATEX_IS_CMD = 1
-- TEX_VIEW_EXEC points to your TeX portrait previewer. The dvi file
-- associated with the TeX file loaded into EPM will be appended to it.
eg. TEX_VIEW_EXEC = 'd:\emtex\dviscr\dvipm7.exe @d:\emtex\dviscr\dvipm.cnf'
TEX_VIEW_IS_CMD = 0
-- TEX_VIEWLA_EXEC points to your TeX landscape previewer. The dvi file
-- associated with the TeX file loaded into EPM will be appended to it.
eg. TEX_VIEWLA_EXEC = 'd:\emtex\dviscr\dvipm7.exe @d:\emtex\dviscr\dvipmla.cnf'
TEX_VIEWLA_IS_CMD = 0
-- TEX_PRINT_EXEC points to your TeX portrait dvi driver. The dvi
-- file associated with the TeX file loaded into EPM will be appended to it.
eg. TEX_PRINT_EXEC = 'd:\emtex\dvidrv\dvihplj7.exe @d:\emtex\dvidrv\lj.cnf'
TEX_PRINT_IS_CMD = 0
-- TEX_PRINTLA_EXEC points to your TeX landscape dvi driver. The dvi
-- file associated with the TeX file loaded into EPM will be appended to it.
eg. TEX_PRINTLA_EXEC = 'd:\emtex\dvidrv\dvihplj7.exe @d:\emtex\dvidrv\lj.cnf /tr1'
TEX_PRINTLA_IS_CMD = 0
OPTIONAL:
You can define a special mode (German, AMS, Bibtex, ?) that will appear on
the TeX menu here. To do this, define TEX_USER_MENU_TEXT with the desired
label to appear on the menu. When this mode is selected, the following
variables will be used when TeXing
Put the label that will show up on the TeX pulldown menu here (use '' to disable
the user mode completely). Use a ~ to specify the accelerator letter.
eg. TEX_USER_MENU_TEXT = '~BibTeX'
These point to the executables you wish to run when user mode is on and you TeX
the document. The current TeX filename loaded into EPM will be appended to it.
TEX_USER_EXEC = 'd:\emtex\bibtex.cmd'
TEX_USER_IS_CMD = 1
LATEX_USER_EXEC = 'd:\emtex\bibtex.cmd'
LATEX_USER_IS_CMD = 1
3) If you already have a mystuff.e file in your e_macros directory, simply
add the following line to the end of it
include 'tex.e'
If you don't have a mystuff.e file (maybe because this is your first
stab at compiling E macros) then copy tex.e to mystuff.e.
4) Make sure mymnuini.e exists in your e_macros directory. It is possible that
you may already have an existing mymnuini.e file if you have made other
modifications to EPM's menu bar already. If so, you will need to append the
mymnuini.e file from this package to your existing mymnuini.e file.
5) To be safe, make backup copies of your epm.ex and extra.ex files in your
epm directory. Then if things go awry you can get back to the original
epm configuration.
6) Make the epm directory your current directory, and type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
etpm epm
The etpm compiler will execute and compile your epm.e macro. The TeX stuff
in mystuff.e and mymnuini.e and your config switches in mycnf.e will
automatically be included. If etpm complains it can't find a file, you
probably have your EPMPATH incorrectly defined. It should point to all
directories containing E macro files (*.e).
7) If that goes well then type
etpm extra
This will compile the extra stuff that wouldn't all fit in the epm.ex
file and generate a new extra.ex file.
8) Verify that new epm.ex and extra.ex files are in your epm directory. If
they are, fire up epm with a TeX file (files with extensions .tex*, .sty,
or .bbl) and you should get the TeX submenu added to the EPM menu
bar.
9) Read the epmtex.doc file for information on using the various TeX commands
added with the EPMTeX package. During the installation, it may be helpful
to turn the 'debug mode' feature on as explained in the epmtex.doc file.
OPTIONAL STUFF:
~~~~~~~~~~~~~~
I have included an optional E source file epmlex.tex that is a modified version
of epmlex.e, the E source code for EPM's spelling checker and thesaurus. Using
this version of epmlex will cause the EPM spell checker to ignore words starting
with the TeX escape character '\' (most of the time, it's not perfect) . To use
this modified version you will need to recompile as follows. In the interest of
speed, it also disables script file support, which shouldn't matter to most
people outside of IBM,
1) Backup the original epmlex.e file in your e_macros directory.
2) Copy epmlex.tex to a file called epmlex.e.
3) Make the epm directory your current directory, and type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
etpm epmlex
Support for German Users:
~~~~~~~~~~~~~~~~~~~~~~~~
German users who wish to add a german language mode to the pulldown menu will
want to rename the following file prior to compiling the macros.
rename gtex.e to tex.e
The german language mode can be used to optionally specify the use of plaing or
lplaing formats when TeXing a document. This is an example of using using the
tex.e 'user' mode for a special purpose.
You will also need to edit the following lines:
-- TEX_USER_EXEC points to your german plaing TeX compiler. The current TeX filename loaded
-- into EPM will be appended to it.
eg. TEX_USER_EXEC = 'e=d:\emtex\tex386.exe ^&plaing'
TEX_USER_IS_CMD =0
-- LATEX_USER_EXEC points to your german LaTeX compiler. The current TeX filename loaded
-- into EPM will be appended to it.
eg. LATEX_USER_EXEC = 'd:\emtex\tex386.exe ^&lplaing'
LATEX_USER_IS_CMD =0