OS/2 Shareware BBS: 5 Edit

home *** CD-ROM | disk | FTP | other *** search

/ OS/2 Shareware BBS: 5 Edit / 05-Edit.zip / epmtex31.zip / EPMTEX.HLP (.txt) < prev next >

Wrap

OS/2 Help File | 1995-09-26 | 61KB | 1,672 lines

ΓòÉΓòÉΓòÉ 1. Table of Contents ΓòÉΓòÉΓòÉ TeX Macro Enhancements for EPM 5.51a and EPM 6.0x Version 3.1 Installation/User Manual Jon Hacker Rodney Korte September 1995 Table of Contents 1. Frequently Asked Questions 2. License Agreement 3. Introduction 4. Installation Instructions 5. Using the Macros with TeX 6. Settings Notebook Page 7. Startup Notebook page 8. Executables Notebook Pages 9. Formats Notebook Page 10. User Menu Notebook Pages ΓòÉΓòÉΓòÉ 2. Frequently Asked Questions ΓòÉΓòÉΓòÉ Frequently Asked Questions 1. Where is the official EPMTeX archive site. Currently sharkbait.arl.psu.edu is the official site. You can use anonymous ftp or a Web browser to download from this site. Another primary site is hobbes.nmsu.edu in /pub/os2/unix/tex. 2. Why can't I enable the REXX profile support in EPM v6. Make sure you have WANT_PROFILE = 'SWITCH' defined in your mycnf.e file before compiling epm.e. 3. Syntax highlighting doesn't seem to work. Syntax highlighting is only available with EPM v6. If you are using v5.51a, then this feature is not available. 4. How do I setup the syntax highlighting feature with EPM v6. You need to have epmkwds.tex defined in your *.ex directory. Refer to the information in the header of epmkwds.e for further details on configuring the highlighting keywords and colors. 5. After installing EPMTeX standard version some of my custom EPM features for EPM 5.51a stopped working. Do to a limitation in EPM 5.51a, custom features defined in defload and defselect routines may be overwritten when you link in tex.e. We suggest you install the EPMTeX Pro version if you experience problems of this nature. This problem does not exist with EPM v6. 6. The two page icons in the upper right hand corner of the EPM window have become transparent after installing EPMTeX Pro. The versions of epm.exe, epm.hlp, and the etk*551.dll files supplied with the compiler package are incompatible with Warp. You need to use selective install to reinstall the newer Warp copies of the above files that were overwritten. Table of Contents ΓòÉΓòÉΓòÉ 3. License Agreement ΓòÉΓòÉΓòÉ License Agreement for EPMTeX Enhancements v3.1 IF YOU DOWNLOAD OR USE THIS PROGRAM YOU AGREE TO THESE TERMS. I grant you a license to use the Program only in the country where you acquired it. The Program is copyrighted and licensed (not sold). I do not transfer title to the Program to you. You obtain no rights other than those granted you under this license. Under this license, you may: 1. use the Program on one or more machines at a time; 2. make copies of the Program for use or backup purposes within your Enterprise; 3. make copies of the original file you downloaded and distribute it, provided that you transfer a copy of this license to the other party. The other party agrees to these terms by its first use of the Program. 4. modify the source code provided that you change the name of the package source code files and give credit where credit is due. You must reproduce the copyright notice and any other legend of ownership on each copy or partial copy, of the Program. You may NOT: 1. sublicense, rent, lease, or assign the Program; Under no circumstances am I liable for any of the following: 1. third-party claims against you for losses or damages; 2. loss of, or damage to, your records or data; or 3. economic consequential damages (including lost profits or savings) or incidental damages, even if I are informed of their possibility. Some jurisdictions do not allow these limitations or exclusions, so they may not apply to you. I do not warrant uninterrupted or error free operation of the Program. I have no obligation to provide service, defect correction, or any maintenance for the Program. I have no obligation to supply any Program updates or enhancements to you even if such are or later become available. IF YOU DOWNLOAD OR USE THIS PROGRAM YOU AGREE TO THESE TERMS. THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. You may terminate this license at any time. I may terminate this license if you fail to comply with any of its terms. In either event, you must destroy all your copies of the Program. You are responsible for the payment of any taxes resulting from this license. You may not sell, transfer, assign, or subcontract any of your rights or obligations under this license. Any attempt to do so is void. Neither of us may bring a legal action more than two years after the cause of action arose. If you acquired the Program in the United States, this license is governed by the laws of the State of New York. If you acquired the Program in Canada, this license is governed by the laws of the Province of British Columbia. Otherwise, this license is governed by the laws of the country in which you acquired the Program. 9/1995 Jon Hacker Bellcore INTERNET: hacker@patagonia.bellcore.com Rodney Korte Penn State, State College, PA INTERNET: korte@sabine.psu.edu Table of Contents ΓòÉΓòÉΓòÉ 4. Introduction ΓòÉΓòÉΓòÉ Introduction. EPMTeX is a sophisticated free macro package that integrates the TeX typesetting system with the IBM enhanced editor EPM for OS/2. The EPMTeX macro suite adds a TeX pull down menu to the EPM menu bar, and includes a PM style notebook program for configuration of the package. Menu items in the TeX pull down menu allow the user to TeX (with any format, e.g. LATeX), jump to errors in the TeX source, preview (portrait and landscape), and print (portrait and landscape) the TeX file currently active in EPM. Custom 'user' modes may also be defined for special needs unique to the user. Due to popular demand, the standard edition of EPMTeX now comes precompiled. The version of EPM shipped with OS/2 is all that is required to run EPMTeX. It is no longer necessary to obtain the EPM macro compiler from IBM to add the core EPMTeX features. Consequently, installation is now greatly simplified. EPMTeX Pro... what is this? EPMTeX was substantially rewritten to allow it to be distributed precompiled. In the process, some existing features were removed due to limitations in what can be done with a precompiled EPM macro. Users of earlier versions of EPMTeX may not wish to give up these features, particularly if they are comfortable compiling macros for EPM. For this reason, a Pro version of the macro package is also provided. The Pro version does not come precompiled and is not recommended for novice users. Its installation is complicated, requires the complete EPM macro compiler from IBM, and does not offer much more than the standard version anyway. It is provided solely as a comfort to our longtime EPMTeX users. The Pro version offers the following (minor) extra things over the standard version: 1. The format and orientation can be chosen from either the settings notebook (as per the standard version) or from the TeX menu in EPM. 2. The TeX menu items in EPM get enabled/disabled (greyed out) as appropriate. For example, if the dvi file does not exist, the preview and print functions will be greyed out in the menu. 3. Access to the macro source code should you wish to dabble in a little customization of the package. If you wish to use EPMTeX Pro, unzip the file TeXpro.zip included with EPMTeX 3.1 and follow the installation instructions contained in the file readme.pro. Table of Contents ΓòÉΓòÉΓòÉ 5. Installation ΓòÉΓòÉΓòÉ Installation Procedures 1. Standard Version (Easy) 2. Pro Version (Complicated) Table of Contents ΓòÉΓòÉΓòÉ 5.1. Standard Version ΓòÉΓòÉΓòÉ Easy Installation Procedure (Standard version) NOTE: Users of older versions of EPMTeX will first have to purge the old EPMTeX files before installing the new version. Refer to Appendix A for further instructions. 1. Unzip the EPMTeX files into a convenient directory. 2. Copy tex.ex and profile.erx to a directory that is specified in either EPMPATH or PATH so that EPM can find them. Most *.EX files are in the \OS2\APPS directory. Make sure there are no other older copies of tex.ex in your PATH that could override your newer version. NOTE: For people using EPM version 6, you need to unzip the tex.ex file from v60x.zip to replace the tex.ex that is the default (v5.51a). 3. Copy bpmcc.dll to any directory in your LIBPATH. Copy epmtex.exe and epmtex.hlp anywhere to your liking, it doesn't matter where, but keep them together. 4. Run epmtex.exe and fill in the notebook to describe your local TeX environment. Refer to the on-line help for further information. 5. Now you are ready to use the new EPMTeX. There are a couple of ways to tell EPM to load the tex.ex file (see also Appendix B). The simplest is to use the REXX profile file 'profile.erx' supplied with EPMTeX. EPM will automatically 'run' this file when it starts creating a way to customize EPM without recompiling the epm macro files. Start EPM. If the TeX menu is not visible, then you need to enable the REXX profile support. Type ctrl-i to open the EPM command window. Execute the command 'profile on' (no quotes). Then select the 'Save Options' command in the pull-down menu. NOTE: For people using EPM version 6, enable REXX profile support by opening the EPM settings notebook and check the 'REXX profile' option on the Misc page. 6. Exit EPM and restart. The TeX menu should be visible now. Load a TeX file and test it out! Table of Contents ΓòÉΓòÉΓòÉ 5.2. APPENDIX A: ΓòÉΓòÉΓòÉ APPENDIX A: Removing a Previous EPMTeX Version To install over a previous version of EPMTeX you will need to first purge the old EPMTeX files from your system. 1. Remove the old EPMTeX version from your epm files: a) Delete the EPMTeX part of Mymnuini.e b) Delete the EPMTeX part of Mykeyset.e (if any) c) Delete the EPMTeX part of Mykeys.e (if any) d) Delete the EPMTeX part of Mystuff.e (if any) e) Delete the EPMTeX constants from Mycnf.e (step e. is optional but the constants are no longer used) 2. Recompile (version 6 users can skip the extra.e recompile) etpm epm etpm extra Now you should have a plain version of EPM, like it was before you installed EPMTeX. Try running EPM and make sure the TeX menu is gone. Table of Contents ΓòÉΓòÉΓòÉ 5.3. APPENDIX B ΓòÉΓòÉΓòÉ APPENDIX B: Compiling in the EPMTeX Macros Another way to link in the tex.ex file is to edit your mystuff.e file. This is more work because it requires recompiling your EPM macros. In fact, if you're going to go to this much bother, you might as well just install the full blown EPMTeX Pro version. But for those people who want to do it anyway, add the following lines to mystuff.e definit 'linkverify tex' Now recompile epm.e and extra.e (version 6 users can skip the extra.e recompile) etpm epm etpm extra This will cause tex.ex to be linked in automatically whenever you start EPM. You can delete the EPMTeX portion of your profile.erx file if you use this method since it is no longer needed. Table of Contents ΓòÉΓòÉΓòÉ 5.4. Pro Version ΓòÉΓòÉΓòÉ EPMTeX 3.1 (Pro version) 1. Express Installation (terse installation instructions for EPM experts) 2. Long-Winded Installation (full installation instructions for novices) Table of Contents ΓòÉΓòÉΓòÉ 5.4.1. Express Installation ΓòÉΓòÉΓòÉ Express Installation Procedure (Pro version) NOTE: Users of older versions of EPMTeX will first have to purge the old EPMTeX files before installing the new version. Refer to Appendix A for further instructions. 1. Create the subdirectory EPMTEX in the EPM directory. Copy the contents of the EPMTeX Pro macro package (including the files contained in TEXPRO.ZIP) into it. Add this directory to your EPMPATH environment variable. (You could also copy them to the e_macros subdirectory of epm, but this makes things more confusing with all the other files in there already.) Reboot if you made any changes to config.sys. 2. Append mymnuini.add to your existing mymnuini.e file, or if you don't have one, copy mymnuini.add to mymnuini.e and put the file in a directory specified in your PATH or EPMPATH environment variables. 3. Append mystuff.add to your existing mystuff.e file, or if you don't have one, copy mystuff.add to mystuff.e and put the file in a directory specified in your PATH or EPMPATH environment variables. CAUTION: We recommend you backup the original epm.ex and extra.ex in case you have problems and wish to get back to the original configuration. Recompile (version 6 users can skip the extra.e recompile) etpm epm etpm extra etpm tex Make sure the resulting epm.ex, extra.ex, and tex.ex files are located in a directory specified in your PATH or EPMPATH environment variables. Also, make sure there are no other older copies of epm.ex, extra.ex, and tex.ex in your PATH that could override your newer versions. 4. Copy bpmcc.dll to any directory in your LIBPATH. Copy epmtex.exe and epmtex.hlp anywhere to your liking, it doesn't matter where, but keep them together. 5. Run epmtex.exe and fill in the notebook to describe your local TeX environment. Refer to the on-line help for further information. 6. Start EPM. The TeX menu should be visible. Load a TeX file and test it out! Table of Contents ΓòÉΓòÉΓòÉ 5.4.2. Long-Winded Installation ΓòÉΓòÉΓòÉ Long-Winded Installation Procedure (Pro version) NOTE: Users of older versions of EPMTeX will first have to purge the old EPMTeX files before installing the new version. Refer to Appendix A for further instructions. Requirements The EPMTeX Pro macros supplied with this package need to be compiled before they can be incorporated into EPM. You will need to obtain the complete EPM 5.51a package from IBM to do this. Alternatively, the package can also be used with the new 32 bit version 6 of EPM. WARNING: There are several versions of epm 5.51. Make sure you get the latest version. It should say 5.51a in the Product Information dialog box under the Help menu. The EPM package is available for free from the following Internet sites: 1. software.watson.ibm.com /pub/os2/epm (do not use the version in /pub/os2/os2fixes as it an older version) 2. ftp-os2.cdrom.com /pub/os2/ibm/epm It should also be available from major OS/2 BBS services. Installation of EPM 5.51a 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.51a 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.51 are placed by default during the the installation of OS/2. There's just too much other crap in there already. 2. Unzip the EPM 5.51a 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. WARNING: If you are using Warp v3.0, it is recommended you keep the original Warp versions of epm.exe, epm.hlp, and the etk*551.dll files as they are newer than the versions supplied with the IBM EPM compiler package. EPMAPP.ZIP - Unzip into your epm directory (eg. \os2\epm) EPM.EXE - The 5.51a version of the editor (see Warp warning above) ETPM.EXE - The 5.51a 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.51a 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. (see Warp warning above) 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 (see Warp warning above) 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. EPMREX.ZIP - Create a subdirectory under EPM called EREXX, unzip this file into it and add it to your EPMPATH. *.erx - contains some sample EPM / Rexx macros. EPMASI.ZIP - Create a subdirectory under EPM called myassist, unzip this file into it and add it to your EPMPATH. An alternative approach to syntax-assisted editing; makes it easy to add your own expansions. Includes sample files for OS/2 and PM APIs, C, and Bookmaster. EPMATR.ZIP - Create a subdirectory under EPM called epmattr, unzip this file into it and add it to your EPMPATH. Sample code for doing things with EPM's attribute support. 3. Edit your config.sys file and make sure that your new epm directory is included in your PATH statement. If you have IBM's TCP/IP v2.0 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, sampmacs, erexx, myassist, and epmattr 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 OS/2 installation 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 unexpected behaviour from EPM. 6. OPTIONAL: If you have IBM's TCP/IP v2.0 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 other copies EPM.EXE 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. For Warp users, move the existing EPM.EXE from \os2\apps to your epm directory as it is newer than the one supplied with the compiler package. 8. Find any 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.51a dll's and they should be put somewhere in your LIBPATH (\os2\apps\dll is as good as any). For Warp users, keep the existing ETK*551.DLL files in \os2\apps\dll as they are newer than the ones supplied with the compiler package. 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.cdrom.com /pub/os2/2_x/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 \epm\lexam. 10. You should now be ready to compile your E macros. First, though, reboot if you made any changes to config.sys. COMPILING THE EPMTeX Pro MACROS 1. Create the subdirectory EPMTEX in the EPM directory. Copy the contents of the EPMTeX Pro macro package (including the files contained in TEXPRO.ZIP) into it. Add this directory to your EPMPATH environment variable. (You could also copy them to the e_macros subdirectory of epm, but this makes things more confusing with all the other files in there already. Reboot if you made any changes to config.sys. 2. Delete the file TEX.EX that comes with the standard version of EPMTeX. You will compile your own copy of this file during the installation procedure. 3. 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. Alternatively, read the EPM documentation on compiler options and build your own custom mycnf.e file to suit your taste. We would suggest that in your MYCNF.E file you enable the ring by including the following: MY_RING_ENABLED = 1 RING_OPTIONAL = 0 4. If you don't have a mystuff.e file in your e_macros directory, (maybe because this is your first stab at compiling E macros) then copy mystuff.add to mystuff.e. If you already have a mystuff.e file in your e_macros directory, then append the contents of mystuff.add to the end of it. 5. If you don't have a mymnuini.e file in your e_macros directory, then copy mymnuini.add to mymnuini.e. If you already have a mymnuini.e file 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), then append the contents of mymnuini.add to it. 6. CAUTION: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. 7. 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, 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). 8. If that goes well, 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. (Note: this step is unnecessary with EPM version 6.) 9. If that goes well, type: etpm tex This will compile the actual TeX support. 10. Make sure the files epm.ex, extra.ex, and tex.ex created above are located in a directory specified in your PATH or EPMPATH environment variables. Also, make sure there are no other older copies of epm.ex, extra.ex, and tex.ex in your PATH that could override your newer versions. 11. Copy bpmcc.dll to any directory in your LIBPATH. Put epmtex.exe and epmtex.hlp anywhere to your liking, it doesn't matter where, but keep them together. 12. Run epmtex.exe and fill in the notebook to describe your local TeX environment. Refer to the on-line help for further information. 13. Start EPM. The TeX menu should be visible. Load a TeX file and test it out! Table of Contents ΓòÉΓòÉΓòÉ 6. Using the Macros with TeX ΓòÉΓòÉΓòÉ Overview The E macro file tex.ex, when linked into the IBM enhanced Editor, will add a TeX drop down menu to the EPM menu bar. Menu items in the TeX drop down menu allow the user to TeX (with any format, e.g. LATeX), jump to errors in the TeX source, preview (portrait and landscape), and print (portrait and landscape) the TeX file currently active in EPM. Four custom user modes may also be defined for special needs unique to the user. TeX can be forced to use one of four formats (all user-definable) when TeXing source code. However, a general automatic mechanism is provided so that any format can be specified in the first line of the TeX file. This is the same method used in texit.cmd by Eberhard Mattes. For large projects, a Master file scheme is supported, using a method similar to the automatic format selection method. This allows the user to break a large document into many smaller, more manageable ones with fewer hassles. Paper orientation for viewing and printing also can be defined in the first line of the TeX file, or selected through the TeX notebook. TeX syntax assist and TeX accelerator keys can be enabled for files with extensions .tex, .sty, .aux, or .log, plus any other extensions defined by by the user. Sample TeX files are included in the EXAMPLES directory to demonstrate the EPMTeX package. See the file EXAMPLES\T-MAIN.TEX to get started. For additional information refer to the following sections: The Master File Concept Drop Down Menu Overview TeX Document Locate Next Error View LOG File Preview Document Print Document User Defined Commands Delete LOG File Delete DVI File Format Selection Orientation Selection About ΓòÉΓòÉΓòÉ 6.1. Using the EPM Drop Down Menu for TeX: ΓòÉΓòÉΓòÉ This is a description of the menu items that appear on the TeX sub-menu after installing EPMTeX. The TeX menu will be greyed out for non-Tex files. (TeX files are defined as having extensions .tex, .log, .aux and .sty. You can also specify extensions of your own choice using the EPMTeX notebook (See User File Types) **A double asterisk following the menu choice below signifies that determination of the "Master" file is the first thing that is done after this choice is made. If a "Master" file specification is found, EPM changes the default directory to that directory (so that log files, etc., end up in that directory) and executes the command associated with that menu item on the Master file, not the current file. The Master file can be specified in any of the following ways (the master file is MYMAIN.TEX): % Master: mymain % master: mymain % Master mymain % master mymain Any number of spaces can be used between any of the elements in the line. All Master and Slave (those input from the master) files are assumed to be in the same directory. However, they can be placed in different directories if they are always referenced with a fully qualified pathname (no relative path specifications). Forward or back slashes can be used in the Master specification above, but remember to use forward slashes in \input lines since TeX will interpret backslashes as command sequences. If a master file is specified but does not actually exist, EPMTeX will ask if you want to stop processing or continue as if the Master directive was not issued. This has the (nifty) side-effect that you can do something like: % Format: lplain Master : mymain Orientation:Landscape for the first line of a file. If you want to TeX only the current file, simply modify mymain to something like mymain1 and then TeX the current file. Note that you would then have a .log and .dvi (and maybe other) files lying around that you won't want later! Note that this question will pop up for any of the operations below that check for a master file name. Two other First line directives are defined: Format and Orientation. Note that they can appear in any order on the first line of the file. To reiterate, the Master directive is processed first. If a master file is defined and exists, the Format and Orientation directives in the current file are ignored. But if a master file is defined but does not exist, they will be used. (Hang on, it does make sense!) For additional information refer to the following sections: The Master File Concept TeX Document Locate Next Error View LOG File Preview Document Print Document User Defined Commands Delete LOG File Delete DVI File Format Selection Orientation Selection About ΓòÉΓòÉΓòÉ 6.2. TeX Document ** ΓòÉΓòÉΓòÉ Calls the version of TeX specified on the TeX|Exec notebook page with the format to be used and the name of the current (or Master) file appended. Note that the appended filename is specified with UNIX type directory delimiters (ie. '/') so that TeX will not barf. The format to be used is selected on the Settings notebook page. If Automatic is not chosen (one of the other ones is) the format defined on the TeX|Formats notebook page for that format will be used. If Automatic is chosen, an attempt is made to determine the format from the first line of the current (or Master) file. The format can be specified in any of the following ways (lplain is the format used here): % Format: lplain % format: lplain % Format lplain % format lplain % Format:lplain % format : lplain % format :lplain etc... Any number of spaces can be used between any of the elements in the line. If the format is not specified but Automatic is chosen, EPMTeX will issue a warning and continue with the format defined for Plain. Note that the format specification only need be placed in the Master file, not the slave files. Note that the format you specify does not have to correspond to any format defined in the Format notebook page. If you specify a format that doesn't exist, EPMTeX won't care, but TeX will- you'll get a 'Sorry, I can't find that format; will try PLAIN' error. If the AutoSave option is checked on the TeX Settings notebook page, the current file will first be saved to disk if the version in EPM memory has been modified. If a Master file is defined, EPM loads the Master file and scans it for "\input file_name" commands, and checks to see if file_name is in the ring. If it is, and has been modified, EPM will save the file. If AutoSave is not checked, EPM will ask you if you wish to save the file before TeXing. This action also resets the Error Locating routine to the beginning of the LOG file. ΓòÉΓòÉΓòÉ 6.3. Locate Next Error ** ΓòÉΓòÉΓòÉ If the LOG file for the current (or Master) file exists, this action will load the log file, determine the TeX source file in which the first error resides, load that file, position the cursor at the error, and print the error message on the message line. Subsequent selection of this action will cause a search for the next error until all errors have been located. Selecting either the View LOG File or TeX Document menu options resets the search to the beginning of the LOG file. Note that if you are using a Master file and include a slave file that does not have the Master specification in the first line, and EPMTeX locates an error in this file, you will have to switch to a file in the ring that does have the master file defined to locate subsequent errors. This is due to the fact that the error routine will look for a LOG file associated with the slave file, not the master, to locate the next error. In most cases, it will not exist, so the menu item will be greyed out. BE AWARE: if it does exist, you may have some trouble since the error routine will be looking in the wrong LOG file for the next error! ΓòÉΓòÉΓòÉ 6.4. View LOG File ** ΓòÉΓòÉΓòÉ If the LOG file exists, this command will load the associated LOG file for the current (or Master) TeX file into the EPM file ring. If there is a LOG file currently in the ring, it is removed before the new LOG file is loaded. This action also resets the Error Locating routine to the beginning of the LOG file. ΓòÉΓòÉΓòÉ 6.5. Preview Document ** ΓòÉΓòÉΓòÉ Calls the TeX previewer specified on the Previewer|Portrait notebook page (or Previewer|Landscape if landscape orientations is selected) with the name of the associated DVI file for the current (or Master) file loaded in EPM appended. The TeX previewer specified on the Previewer|Portrait notebook page should be the previewer used for portrait orientation. The TeX previewer specified on the Previewer|Landscape notebook page should be the previewer used for landscape orientation. If the Auto LOG Delete option is checked in the Settings notebook page, the associated LOG file for the current (or Master) file will be automatically deleted if it exists. ΓòÉΓòÉΓòÉ 6.6. Print Document ** ΓòÉΓòÉΓòÉ Calls the TeX dvi printer driver specified on the Printer|Portrait notebook page (or Printer|Landscape if landscape orientation is selected) with the name of the associated DVI file for the current (or Master) file loaded in EPM appended. The TeX printer driver specified should be on the Printer|Portrait notebook page the printer driver used for portrait orientation. The TeX printer driver specified on the Printer|Landscape notebook page should be the printer driver used for landscape orientation. If the Auto LOG Delete option is checked in the Settings notebook page, the associated LOG file for the current (or Master) file will be automatically deleted if it exists. ΓòÉΓòÉΓòÉ 6.7. User Defined Command ** ΓòÉΓòÉΓòÉ You can define up to four user defined commands. The commands are specified on the User X|Portrait notebook pages (or User X|Landscape notebook pages if landscape orientation is chosen) will be executed. ΓòÉΓòÉΓòÉ 6.8. Delete LOG File ** ΓòÉΓòÉΓòÉ If the LOG file exists, this command will delete the associated LOG file for the current (or Master) file loaded in EPM. It also removes this LOG file from the ring if it exists. ΓòÉΓòÉΓòÉ 6.9. Delete DVI File ** ΓòÉΓòÉΓòÉ If the DVI file exists, this command will delete the associated DVI file for the current (or Master) file loaded in EPM. ΓòÉΓòÉΓòÉ 6.10. Format ΓòÉΓòÉΓòÉ CAUTION: This menu item is only availabe on the Pro version of the EPMTeX package. Use the Settings notebook page instead if using the standard version. The chosen format will have a checkmark beside it. If Automatic is chosen, EPMTeX will attempt to determine the format to be used from the first line of the current (or Master) file. If no format is specified on the first line, the format defined by Plain will be used. If one of the other formats is selected, EPMTeX will explicitly call the format associated with this selection when TeX Document is selected. There is no specific German mode in this release. Rather, alternate language support is included as part of this more general format selection method. The German versions of the plain and LATeX formats can be defined on the TeX|Formats notebook page. ΓòÉΓòÉΓòÉ 6.11. Orientation ΓòÉΓòÉΓòÉ CAUTION: This menu item is only availabe on the Pro version of the EPMTeX package. Use the Settings notebook page instead if using the standard version. The chosen paper orientation will have a checkmark beside it. If Automatic is chosen, EPMTeX will attempt to determine the orientation to be used from the first line of the current (or Master) file. If no orientation is specified on the first line, Portrait will be used. If Portrait or Landscape is chosen, the orientation specified on the first line of the file will be overridden. The orientation is specified on the first line of the TeX file in a manner similar to that of the Format specification, except there are only two possible orientations, Landscape and Portrait. Some example specifications are shown below: % Orientation: Landscape % Orientation: Portrait % Format: lplain Orientation: Landscape % Format: TeXsis Orientation: Portrait % Orientation: Landscape Format: MyFormat etc... If Portrait or Landscape is selected, the orientation specified on the first line of the file, if it exists, will be ignored and the selected orientation will always be used. If the orientation is determined to be landscape, the landscape versions of the TeX previewer and printer driver (and the four user-defined commands) are used as specified by the Landscape pages of the EPMTeX notebook. Otherwise, the portrait versions specified by the Portrait pages of the EPMTeX notebook are used. ΓòÉΓòÉΓòÉ 6.12. About ΓòÉΓòÉΓòÉ Self-explanatory? Table of Contents ΓòÉΓòÉΓòÉ 7. EPMTeX Settings Page ΓòÉΓòÉΓòÉ The settings page controls those configurations that have an immediate affect on the operation of the EPMTeX macro package. The following settings can be controlled: Auto Log Delete Auto Save Master File Debug Level Format Orientation OK Cancel Table of Contents ΓòÉΓòÉΓòÉ 7.1. EPMTeX Automatic Log File Delete ΓòÉΓòÉΓòÉ If this option is checked, the log file for the active TeX file in the editor window will be automatically deleted when previewing or printing the associated dvi file. This feature can be handy to avoid leaving behind a clutter of log files after using TeX. ΓòÉΓòÉΓòÉ 7.2. EPMTeX Smart File Save ΓòÉΓòÉΓòÉ If this option is checked, TeX files that have been modified will be saved to disk automatically before TeX is called. TeX files checked for modification include the current TeX file in the editor window, any TeX files included in the current file using the \input and \include{} commands, and any other files linked to the current file by a common Master file. Since TeX operates on the file saved to disk and not on the file in editor memory, it is usually desirable to have this option selected. If this option is not checked, and there are modified files in the editor, then you will be reminded by a dialog box that there are modified files in the editor whenever TeX is run. The dialog box reminder will give you the opportunity to have the modified files saved to disk before TeX is run. ΓòÉΓòÉΓòÉ 7.3. Master File System ΓòÉΓòÉΓòÉ If this option is checked, the Master File system will be enabled. The Master File Concept It is useful to break a large document into smaller, more manageable parts. The idea is to create a small file, which contains initialization commands, special definitions, etc., and then includes other files which have the actual text of the document. This small file is the "Master" file. For example we might have the following Master file, NOISE.TEX %Format: TeXsis % Use the TeXsis format \paper % Set page layout \TrueDoubleSpacing % Set doublespacing \draft % Put into draft mode \input NOISE-REFS % References \input NOISE-INTRO % Introduction \input NOISE-SEC1 % Section 1 \input NOISE-SEC2 % Section 2 \input NOISE-SEC3 % Section 3 \input NOISE-CONC % Conclusion \ListReferences % List all References \end The first line will tell EPMTeX (and Eberhard Mattes' texit.cmd) that the TeXsis format should be used when TeXing this file. Any valid format can be used here as long as the corresponding *.fmt file exists. Lines 2-4 are TeXsis commands that set the page layout and other things that apply to the entire document. The references, as well as each of the 5 sections of the paper, are in a separate files which are read in one after another. The second-to-last line then prints out the references and finally the document ends. This scheme is useful since not only is the document well organized, but now sections of the paper can be worked on individually by simply commenting out those sections which need not be compiled. When everything is working, just uncomment all the sections and recompile. A simple example of the Master File system is provided with EPMTeX in the \examples directory created when you first unzip the EPMTeX package. ΓòÉΓòÉΓòÉ 7.4. Debug Level ΓòÉΓòÉΓòÉ For the purpose of debugging a new installation, EPMTeX has some built in support for runtime debugging. The spinbutton allows the debug level to be changed from OFF, the default state, through level 3. If debug level 1 is selected, the contents of the command line sent to the OS/2 shell when TeX, Preview, Print, etc., are selected will be displayed on the EPM message line. This can be useful when setting up and debugging the various TeX commands during the installation of EPMTeX. Note that a list of recent messages can be retrieved in EPM under the menu options|messages. Debug levels 2 and 3 provide increasing detail about the operation of the EPMTeX macros. However, such detail is unlikely to be of much use unless you are developing enhancements to the EPMTeX macro package. ΓòÉΓòÉΓòÉ 7.5. Format Selection ΓòÉΓòÉΓòÉ The desired TeX format is selected using the available radio buttons. If Auto is chosen, EPMTeX will attempt to determine the format to use by looking at the first line of the current (or Master) file. If no format is specified on the first line, the format defined by Plain will be used by default. The format to use is specified in the first line of the file. Some example specifications are shown below: % Format: plain % Format: lplain % Format: MyFormat etc. If a specific format radio button is selected, EPMTeX will use the format associated with this selection as specified in the Format page of the EPMTeX notebook. Should it exist, the format specified on the first line of the file will be ignored and the selected format will always be used. There are provisions to support two User formats as well as the more common Plain and LaTeX formats. In practise, however, any TeX format can be associated with any radiobutton selection by appropriately defining it in the Format page of the EPMTeX notebook. Note that any format can be specified in the Tex file using the %Format: directive. The format need not be first defined on this page to be used. Provided the Auto setting is selected the specified format will be passed to TeX. The only requirement is that the corresponding *.fmt file exist. ΓòÉΓòÉΓòÉ 7.6. Orientation Selection ΓòÉΓòÉΓòÉ The desired TeX paper orientation is selected using the available radio buttons. If Auto is chosen, EPMTeX will attempt to determine the orientation to use by looking at the first line of the current (or Master) file. If no orientation is specified on the first line, Portrait will be used by default. The orientation is specified on the first line of the TeX file in a manner similar to that of the Format specification, except there are only two possible orientations, Landscape and Portrait. Some example specifications are shown below: % Orientation: Landscape % Orientation: Portrait % Format: lplain Orientation: Landscape % Format: TeXsis Orientation: Portrait % Orientation: Landscape Format: MyFormat etc. If Portrait or Landscape is selected, the orientation specified on the first line of the file, if it exists, will be ignored and the selected orientation will always be used. If the orientation is determined to be landscape, the landscape versions of the TeX previewer and printer driver (and the four user-defined commands) are used as specified by the Landscape pages of the EPMTeX notebook. Otherwise, the portrait versions specified by the Portrait pages of the EPMTeX notebook are used. The same holds true for the four user-defined commands. ΓòÉΓòÉΓòÉ 7.7. OK Button ΓòÉΓòÉΓòÉ Pressing OK causes the notebook to close with its current state saved in the epm.ini file. ΓòÉΓòÉΓòÉ 7.8. Cancel Button ΓòÉΓòÉΓòÉ Pressing Cancel causes the notebook to be closed without saving any changes made to the currently visible page of the notebook. CAUTION: Please note that changes made previously to other pages in the notebook will not be undone. Once a new page in the notebook is selected, it is equivalent to having selected the OK button, and any changes made to the page are permanently saved and cannot be undone. The Cancel button's scope only applies to the page that is visible when the Cancel button is pressed. So, don't change the notebook page until you are happy with the changes you have made. ΓòÉΓòÉΓòÉ 8. EPMTeX StartUp Page ΓòÉΓòÉΓòÉ The startup page controls those configuration options that only affect the operation of the EPMTeX macro package the next time EPM is started. Hence, any changes made to these settings will not have any immediate affect on the current EPM editing session. The following settings can be controlled. TeX Tabs Quick Keys Menu On Syntax Assist TeX Margins Additional file extensions to associate with TeX OK Cancel Table of Contents ΓòÉΓòÉΓòÉ 8.1. EPMTeX TeX Tabs ΓòÉΓòÉΓòÉ Tab stops specific only to TeX files can be defined in the Tab Stops entry box, and enabled by clicking in the Enable check box. In the Tab Stops entry box, you can type either a single number to be used as an increment, or a series of numbers separated by a space that will be used as column spacings. In both cases column one is used as a starting point. A TeX file, for the purposes of defining tab scope, is defined to be any file with an extension of tex, sty, aux, and log. In addition, custom file extensions can be specified in the Additional file extensions to associate with TeX entry box on the Startup page. ΓòÉΓòÉΓòÉ 8.2. EPMTeX Quick keys ΓòÉΓòÉΓòÉ If the Quick Keys setting is checked, the key Shift+F11 is defined to execute the TeX Document menu item, and the key Shift+F12 is defined to execute the Locate Next Error menu item. ΓòÉΓòÉΓòÉ 8.3. EPMTeX Menu Always On ΓòÉΓòÉΓòÉ If the Menu Always On setting is checked, access to the TeX submenu is always possible, even if a non-TeX file is loaded. If unchecked, the TeX menu will be greyed out when the current file in EPM is not a TeX file. A TeX file is defined to be any file with an extension of tex, sty, aux, and log. In addition, custom file extensions can be specified in the Additional file extensions to associate with TeX entry box on the Startup page. ΓòÉΓòÉΓòÉ 8.4. EPMTeX Syntax Assist ΓòÉΓòÉΓòÉ A number of syntactical aids are available with the EPMTeX macros to help the user with typing and debugging TeX commands. The following features can be independently controlled: Syntax Highlighting (EPM v6 only) Syntax Expansion TeX Accelerator Keys ΓòÉΓòÉΓòÉ 8.4.1. Syntax Highlighting ΓòÉΓòÉΓòÉ If the Highlighting setting is checked and you are using EPM version 6 or later, then EPM's built-in TeX syntax highlighting will be enabled. Various TeX commands will be highlighted in user defined colors based on entries in the epmkwds.tex file. This file should be consulted for further information on customizing the TeX syntax highlighting feature. ΓòÉΓòÉΓòÉ 8.4.2. Syntax Expansion ΓòÉΓòÉΓòÉ If the Expansion setting is checked, then the built-in TeX syntax expansions will be enabled. The TeX syntax expansion provided with EPMTeX was developed by Jo Koenen. If you have suggestions, or better yet source code, that will expand the functionality of this section we would love to hear from you. This is a brief description of the syntax expansion features defined in EPMTeX: Loading a file into EPM with the extension .tex, .sty, .aux, or .log (plus any user defined extensions added using the Additional file extensions to associate with TeX entrybox) enables the following enhancements: (the vertical bar | denotes the cursor position) 1. \be (including the blank after \be !!) will be expanded to \begin{|} now you can enter a TeX-word like itemize \begin{itemize} press enter and you get \begin{itemize} | \end{itemize} 2. \it (including the blank) will be expanded to \item | 3. \ci (including the blank) will be expanded to \cite{|} That's all I (Jo) have done so far, but it is all source code, therefore it's expandable. Every suggestion is welcome. ΓòÉΓòÉΓòÉ 8.4.3. TeX Accelerator Keys ΓòÉΓòÉΓòÉ If the Accelerator keys setting is checked, then the built-in TeX accelerator keys will be defined. Note: You cannot enable the TeX accelerator keys without also enabling the TeX syntax expansion. Key assignments (the vertical bar | marks the cursor position) are shown below: alt-a:=eqnarray| alt-b:=\begin{|} alt-c:=\cite{|} alt-d:=description| alt-e:=equation| alt-f:=\frac{|}{} alt-h:=\hspace*{|} alt-i:=\item| alt-j:=itemize| alt-k:=tabular| alt-l:=\label{|} alt-m:=\mbox{|} alt-n:=enumerate| alt-q:=equation| alt-r:=\ref{|} alt-s:=\sqrt{|} alt-v:=\vspace*{|} alt-w:=verbatim| { :={|} $ :=$|$ ΓòÉΓòÉΓòÉ 8.5. EPMTeX TeX Margins ΓòÉΓòÉΓòÉ Margins specific only to TeX files can be defined in the Left, Right, and Paragraph entry boxes, and enabled by clicking in the Enable check box. The left and right margins control where the cursor is positioned when typing text. If you type beyond the right margin , the word you are typing is moved to a new line starting at the left margin. When you reformat a paragraph, it is justified so that all lines are between the left margin and the right margin, except the first line, which starts at the paragraph margin. A TeX file, for the purposes of defining margin scope, is defined to be any file with an extension of tex, sty, aux, and log. In addition, custom file extensions can be specified in the Additional file extensions to associate with TeX entry box on the Startup page. ΓòÉΓòÉΓòÉ 8.6. TeX User File Types ΓòÉΓòÉΓòÉ Many EPMTeX functions such as the TeX menu, syntax assist and accelerator keys are disabled for non-TeX files. For example, the TeX menu will be greyed out for non-Tex files (unless Menu Always On is checked). By default, a TeX file is defined to be any file with an extension of tex, sty, aux, and log. You can also specify additional extensions of your own choice by entering them in the Additional file extensions to associate with TeX entry box. The file types do not need to be separated with spaces, although this can be done for ease of reading. The extensions need not be limited to 3 characters if you are using the HPFS file system. For example, suppose you want to define additional files with file names of *.fgl, *.tbl, *.ref, *.cnt, and *.toc to be recognized as TeX files. Either of the following entries would accomplish this, although the first is arguably easier to read. Furthermore, the second entry would also match other permutations of file extensions such as *.fgltbl and so on: FGL TBL REF CNT TOC FGLtbLREFcnttoc ΓòÉΓòÉΓòÉ 9. EPMTeX Executable Page ΓòÉΓòÉΓòÉ The executable notebook page allows the specification of an external executable program or REXX file to be launched for a given task such as TeXing, previewing, and printing. It also allows configuration of the parameters that control how EPMTeX will start the program and pass parameters. There are many of these pages in the EPMTeX notebook, each describing a different executable program whose function will be self evident from the description on the notebook tab. A basic setup will require specification of programs or REXX files to TeX, preview and print. Four additional User tabs are provided, with no fixed purpose, to suit the individual needs of each user. Typically they might be used to launch FAX routines, envelope printing, and other TeX related applications, that are not a part of the core TeX, preview, and print functions. The following controls are available on the page: Executable File Name Program Type Start Condition Parameter Path Executable Type Start In OK Cancel Table of Contents ΓòÉΓòÉΓòÉ 9.1. EPMTeX Executable File Name ΓòÉΓòÉΓòÉ Enter your executable path\filename and args here. EPMTeX will automatically append the fully qualified TeX filename of the TeX or *.dvi file (as appropriate) to the end of the line. The format will also be appended in the case of the TeX executable. The use of environment variables in the filename is supported. The syntax follows that of emtex, with a $ preceding the variable name, and a : following. If you have correctly defined the EMTEXDIR environment variable during the emtex installation, then the default entries in the EPMTeX notebook pages should work without change for your installation. An example showing the use of an environment variable for the Printer notebook page is shown below: $EMTEXDIR:\bin\dvihplj.exe @lj.cnf Additional detailed information about the filename entry for the following notebook pages is available: TeX Previewer Printer User ΓòÉΓòÉΓòÉ 9.1.1. TeX File Name Entry ΓòÉΓòÉΓòÉ The name of the TeX executable is entered here. The default entry should work properly for the standard setup of emtex v3.14159 or later. In addition to having the fully qualified TeX filename of the TeX file automatically appended to the end of the line, EPMTeX will also append the selected format to the line as specified with the Format setting. The format is appended before the TeX filename. EPMTeX automatically inserts the characters & before the format, and encloses the format and file name in quotes so that the & symbol will not interfere with the command processor. For example, if $EMTEXDIR:\bin\tex386.exe -mp40000 is entered in the TeX notebook page, the format plain is selected, and the file being edited is called x:\mypath\foo.tex, then EPMTeX will launch TeX with the following line: start x:\TheEmtexDir\bin\tex386.exe -mp40000 "&plain x:/mypath/foo.tex" ΓòÉΓòÉΓòÉ 9.1.2. Previewer File Name Entry ΓòÉΓòÉΓòÉ The name of the Previewer executable is entered here. Two different pages are defined, to allow different previewers to be specified for Portrait and Landscape orientation. The default entry should work properly for the standard setup of emtex dvipm v1.5 or later. Note that EPMTeX does nothing different for the Portrait and Landscape orientations other than calling the executable specified on the respective notebook page. It is up to the user to make sure that the corresponding entry correctly invokes the appropriate orientation. For example, for dvipm, adding the command line switch /tr1 is usually all that is necessary to get landscape orientation. ΓòÉΓòÉΓòÉ 9.1.3. Printer File Name Entry ΓòÉΓòÉΓòÉ The name of the Printer executable is entered here. Two different pages are defined, to allow different printers to be specified for Portrait and Landscape orientation. The default entry should work properly for the standard setup of emtex dvihplj v1.5 or later. Note that EPMTeX does nothing different for the Portrait and Landscape orientations other than calling the executable specified on the respective notebook page. It is up to the user to make sure that the corresponding entry correctly invokes the appropriate orientation. For example, for dvihplj, adding the command line switch /tr1 is usually all that is necessary to get landscape orientation. ΓòÉΓòÉΓòÉ 9.1.4. Userx File Name Entry ΓòÉΓòÉΓòÉ The name of any user defined executable is entered here. The corresponding description specified on the menu page will then show up in the EPMTeX pull down menu. Two different pages are defined, to allow different executables to be specified for Portrait and Landscape orientation. If nothing is specified, the entry will not show up in the EPMTeX pulldown menu in EPM. Selecting a user command from the menu will cause the corresponding command specified in the executable file name entry box to be run. The name of the current file in the editor (without extension) will be appended to the command unless an extension is specified in the corresponding Menu notebook page. If an extension is specified, then the extension will be appended to the filename before executing the command provided the file exists. Note that EPMTeX does nothing different for the Portrait and Landscape orientations other than calling the executable specified on the respective notebook page. It is up to the user to make sure that the corresponding entry correctly invokes the appropriate orientation. If you want to use the user-definable commands to run TeX then there are some caveats. For example, you cannot specify: c:\emtex\texit.cmd ^&myplain with a Command File executable type as texit.cmd will not receive any arguments. You can, however, (at least with 4OS/2) specify: c:\emtex\texit.cmd &myplain Also, since the filename passed to TeX must not have backslashes in it (TeX will interpret them as control sequences), if you configure to run TeX, you must specify the UNIX Style Parameter Path so that the filename passed will use UNIX style directory delimiters. ΓòÉΓòÉΓòÉ 9.2. Program Type ΓòÉΓòÉΓòÉ Choose the selection that matches the program type entered, or choose Automatic to have OS/2 choose. PM specifies that the program is a Presentation Manager application Windowed specifies an OS/2 application that runs within an OS/2 or DOS window Full Screen specifies a full screen OS/2 or DOS application that must run in a separate session independent of Presentation Manager ΓòÉΓòÉΓòÉ 9.3. Start Condition ΓòÉΓòÉΓòÉ Specifies the starting condition for the program. Choose Default to start the application in the normal state (neither maximized nor minimized.) Maximized specifies that the program is to start in the maximized state. It has no effect for a Full Screen application. A PM application may choose not to honour the request. Minimized specifies that the program is to start in the minimized (icon) state. It has no effect for a Full Screen application. A PM application may choose not to honour the request. ΓòÉΓòÉΓòÉ 9.4. Parameter Path ΓòÉΓòÉΓòÉ Specifies whether the fully-qualified name of the current file in the editor (without extension) appended to the command uses UNIX Style (/) or PC Style (\) type directory delimiters. Most PC programs and REXX files will expect to see PC Style delimiters. The one big exception is TeX itself, which interprets PC Style delimiters as control sequences (an inheritance from its UNIX origin). Hence, if you are specifying tex.exe as the executable, then you must also specify UNIX Style path delimiters. If you are running TeX through a REXX file, then you probably want to use PC Style, but check the REXX file for further information. ΓòÉΓòÉΓòÉ 9.5. Executable Type ΓòÉΓòÉΓòÉ Choose the selection that matches the program type entered. If the program is directly executable (*.exe), then select EXE File. This is equivalent to the /N parameter in the OS/2 start command, and has the effect of starting the program directly without the command processor (cmd.exe). If the program is a REXX or batch file (*.cmd), or an internal OS/2 command, then select Command File. This is equivalent to the /C parameter in the OS/2 start command, and has the effect of starting the program indirectly using the command processor (cmd.exe). Warning: Do not choose Command File for an *.exe program as inconsistent results may occur. In particular, choosing Command File in conjunction with tex.exe will result in TeX not starting properly because the format control sequence (^&plain) will not be passed properly through the command processor (cmd.exe). The typical symptom of this is an idle window being created whenever the TeX Document command on the TeX menu is selected. ΓòÉΓòÉΓòÉ 9.6. Start In ΓòÉΓòÉΓòÉ Choose the appropriate selection to start the program either in the foreground or background session. ΓòÉΓòÉΓòÉ 10. Formats ΓòÉΓòÉΓòÉ The formats page of the EPMTeX notebook allows the specification of up to four different TeX formats. The four formats are named Plain, Latex, User1 and User2. Typically, most people will set up Plain and Latex to load the plain and lplain formats, but this can be easily changed if desired. Likewise, User1 and User2 can refer to any additional formats such as the TeXsis format for example. The following controls are available on the page: Select To Edit Format File Name Menu Name Help Prompt OK Cancel Table of Contents ΓòÉΓòÉΓòÉ 10.1. Select To Edit ΓòÉΓòÉΓòÉ Use the radio buttons to select which of the four Formats to edit. The contents of the entry boxes on the page will change to reflect the selected format. The actual format that is used when you select the TeX Document menu item in EPM is chosen from the list of formats defined on this page. For information on selecting formats when using TeX, refer to Selecting the Format on the Settings page. If the User1 or User2 format entry boxes are blank then that format will be disabled. If you try to select a disabled format when running TeX on a document, the Plain format will be substituted instead by default. ΓòÉΓòÉΓòÉ 10.2. Format File Name ΓòÉΓòÉΓòÉ This is the name passed to TeX to specify which format to load. For example, to specify the english plain format, you would enter plain in the Format File Name entry box. You do not need to specify the .fmt extension of the format file. The format file specified must exist in the btexfmts directory or TeX will complain that it can't find the format. (or the texfmts directory if you are not using tex386.exe). ΓòÉΓòÉΓòÉ 10.3. Menu Name ΓòÉΓòÉΓòÉ This is the name of the menu item that will appear on the EPM TeX pulldown menu to select this format. The menu name should be kept short to avoid making the drop down TeX menu excessively wide. A ~ placed before any letter in the name will make that letter the hotkey for the command. The letter will be underlined in the drop down menu as a reminder. Be sure not to choose a hotkey letter that is already in use by another menu item. CAUTION: This entry does nothing with the precompiled version of EPMTeX because the format cannot be set directly from the EPM TeX menu. You will need to get the EPMTeX Pro version for this entry to have any affect. EPMTeX Pro is considerably more complicated to install as it requires recompiling the EPM *.ex files. EPMTeX Pro should be available wherever the standard version of EPMTeX is archived. ΓòÉΓòÉΓòÉ 10.4. Help Prompt ΓòÉΓòÉΓòÉ This is the help prompt that will appear in the messages line of EPM for the corresponding format item in the TeX pulldown menu. CAUTION: This entry does nothing with the precompiled version of EPMTeX because the format cannot be set directly from the EPM TeX menu. You will need to get the EPMTeX Pro version for this entry to have any affect. EPMTeX Pro is considerably more complicated to install as it requires recompiling the EPM *.ex files. EPMTeX Pro should be available wherever the standard version of EPMTeX is archived. ΓòÉΓòÉΓòÉ 11. User Menus ΓòÉΓòÉΓòÉ The User Menu page of the EPMTeX notebook allows the specification of the description and activation of the four optional User command menu items on the TeX pull down menu. The following controls are available on the page: Menu Name File Extension to Activate Help Prompt OK Cancel Table of Contents ΓòÉΓòÉΓòÉ 11.1. User Menu Name ΓòÉΓòÉΓòÉ This is the name of the menu item that will appear on the EPM TeX pulldown menu to select this User command. The menu name should be kept short to avoid making the drop down TeX menu excessively wide. A ~ placed before any letter in the name will make that letter the hotkey for the command. The letter will be underlined in the drop down menu as a reminder. Be sure not to choose a hotkey letter that is already in use by another menu item. ΓòÉΓòÉΓòÉ 11.2. File Extension to Activate ΓòÉΓòÉΓòÉ Enter the extension of the file name that this User command applies to. EPMTeX will make sure the file exists before the command will execute. For example, suppose you have entered dvi in the entry box, If you have the file myfile.tex loaded in EPM and select the user command, EPMTeX will check to make sure the file myfile.dvi exists before it will execute the command. The file myfile.dvi will be appended to the command when it is executed. Refer to Userx File Name Entry for further details. Enter a checkmark in the All Files check box if you wish the command to be executed for all files. Or, equivalently, you can leave the entry box blank which will accomplish the same thing. ΓòÉΓòÉΓòÉ 11.3. User Help Prompt ΓòÉΓòÉΓòÉ This is the help prompt that will appear in the messages line of EPM for the corresponding command in the TeX pulldown menu. The message will appear when the menu item is selected with the mouse or keyboard.