eFTE/2 text editor & FTE text editor

02 Mar 2008 This package combines Alfredo Fernandez Diaz's IPF/HTML configuration updates and Spanish language support with Michael Greene's change including open watcom support (see below). In addition it now uses wrc.exe which was updated by Steven Levine and should be part of Open Watcom 1.8 It can currently be found here http://svn.netlabs.org/fm2/ticket/131. In addition the latest code from the CVS has been incorporated. I have made some minor changes to the menu structure. I also fixed several problems with search and replace in the PM version. It was built with open watcom 1.7a It now has the Norton color scheme as the default (blue backgraoud). 26 Jan 2006 Other than a couple small changes, the major reason for this version is the release of OpenWatcom 1.4 GA which I use to compile. So, this upload includes binary and source. To build: cd into SRC directory wmake [owos2 or owclean] the owos2 option will build console and pm version Oh, if you use the console version of NT/XP you can build it with OW14GA on a Win machine - sorry OS/2 only peoples. Also... sorry about the white background Doodle. Changes: 1. Still doing little changes in dialogs 2. Patched with Sergey Pinigin's svn changes, guess this works the same as FTE cvs, but I don't know - feedback?

Menus, Keybindings, and Macros for FTE REXX Mode March 19, 2001 DISCLAIMER Using this stuff is completely up to you. I'm not responsible for any problems your use of these files may create, no matter how great or small those problems may prove to be. INTRODUCTION Even though FTE is still a beta, it's an excellent text editor. I won't bother with a commercial for it here, though. You can get it on Hobbes or visit the FTE website hosted on SourceForge. http://fte.sourceforge.net One of the challenges to using FTE is the fact that the menus, keybindings, and macros for the various modes it supports are unfinished. Another challenge is that the documentation for these is barely there. I wanted better support for REXX in FTE, and in the spirit of the open source movement I opened the source and put together what I wanted... more or less. I am not a programmer; I can barely program in REXX. What I've done works, but it is probably ungainly. I welcome your improvements and suggestions. WHAT IT IS * Key combinations which automatically create complete loop constructs; * Extensive menu for REXX keywords, contructs, functions, and libraries; * Ability to recognize REXX files with the extension REX and REXX. INSTALLATION It is very important that you back up your FTE configuration files. 1. Add the following line to your UI file (default is fte\config\ui_fte.fte): include 'menu/m_rexx.fte'; 2. Add the following line to your MAIN.FTE in the appropriate place (there are similar lines in the default file): include 'ab_rexx.fte'; 3. Back up the following files, in case you'd prefer to go back to the old configuration some time: fte/config/kbd/k_rexx.fte fte/config/M_REXX.FTE 4. Place the enclosed FTERXMNU.ZIP in the same directory as FTE.EXE and unzip FTERXMNU.ZIP, assuring that directories are recreated. InfoZip's UNZIP will re-create directories by default; PKUnzip requires a command-line parameter which slips my mind at the moment. 5. If you want REXXUtil, RxFTP, and/or RxSock libraries available on your pull-down menus, open fte/config/menu/m_rexx.fte (in the FTE editor, of course <g>) and uncomment the appropriate lines in the beginning of the file. REXXUtil is already uncommented because I like it that way on my setup. 6. Compile the new CNF file by executing CFTE CONFIG\MAIN.FTE and rename the resulting FTE-NEW.CNF to FTE.CNF or FTEPM.CNF, depending on the executable you prefer to use. 7. Set an environment variable named USER denoting your name or an alias, using your perferred method under your operating environment. I use "SET USER=Michael DeBusk" (without the quotes, of course) in my OS/2 CONFIG.SYS and in Windows/DOS AUTOEXEC.BAT. This environment variable is used in the macro that creates your REXX header comment; the contents of the variable are inserted after the word "Author:". HISTORY March 19, 2001 Added an abbrev file and eliminated many of the Ctrl-E keystroke combinations at the suggestion of developer Darin McBride. I like it better and it's easier to use. Type a short string followed by a space and whole constructs appear. The abbreviations are as follows: headx : REXX program header comment utilx : Adds RexxUtil support sockx : Adds RexxSock support ftpx : Adds RxFTP support dox : Constructs a DO loop dux : Constructs a DO UNTIL loop dwx : Constructs a DO WHILE loop dfx : Constructs a DO FOREVER loop ifx : Constructs an IF-THEN-ELSE structure selx : Constructs a SELECT-WHEN structure I simply commented out the key combinations in case someone out there actually prefers them. Delete the "#" to uncomment. March 2, 2001 Added syntax highlighting for Object Rexx keywords and expanded the existing NetRexx highlighting; I haven't added menu selections for them yet. Also realized that not everybody would want all libraries in their menus, so added conditional statements there. Haven't figured out how to make macros and keybindings conditional, but they aren't that big. February 15, 2001 Corrected two bugs that should have never made it out of initial testing. I had neglected to put the necessary "InsertString" command before two statements in the CALL menu. February 9, 2001 I've made some minor improvements, including correction of a mistake in this document. I also decided to include the keyboard file instead of asking the user to edit it; no sense making it more complex than it has to be, right? STILL TO DO I would like feedback of any type before submitting these to the maintainers of FTE. I know it can be better. If you improve it, please send me your changes so I can distribute them in the next "version" and so I can enjoy them as well. Send messages to debu4335@eclipsetel.com with the subject "REXX FTE". Thanks.

Included are mode files for FTE Text Editor to edit CONFIG.* in either OS/2 or DOS and to edit batch files under DOS COMMAND.COM or any JP Software command processor (4DOS, 4OS2, Take Command, and so on.) Since last distribution: fixed a typo in M_CNFGS.FTE and updated it to include new keywords for CONFIG.SYS of MS-DOS 7 for Windows 95. Note that if anything happens as a result of your use of these files, you bear total responsibility for it. M_CNFGS.FTE will recognize any file with the name CONFIG, regardless of extension. (How did I get 33 CONFIG.* files in C:\ anyway?) M_BATCH.FTE will recognize files with the extension BAT or BTM. To use these files: 1. Place the enclosed CNFGBAT.ZIP in the same directory as your FTE executable file(s) and unzip it in a way that re-creates directories (Info-Zip's UNZIP does this by default, PKUnzip does not); 2. Edit CONFIG/MAIN.FTE to add the following lines (examination of the file should tell you the appropriate place): include 'm_batch.fte'; include 'm_cnfgs.fte'; 3. Recompile your FTE configuration file. 4. E-mail me at debu4335@eclipsetel.com and let me know how you like them. If you improve these files, please send me your changes so I can enjoy them as well as add them to a subsequent upload. If everyone is pleased, I'll send these to the maintainers of FTE for their evaluation and possible inclusion in an FTE distribution. Thank you.