The VTEDIT Editing Interface for VAXTPU The Video Terminal Editor VTEDIT is an editing interface for the VAX Text Processing Utility VAXTPU available under VAX/VMS. The VTEDIT interface is an efficient, keypad driven editor allowing multi window editing and providing semi automatic, context dependent text formatting. VTEDIT is based on the VTEDIT.TEC keyboard interface that is a part of the TECO distribution kit. This new version of VTEDIT implements nearly all of the functions of the original VTEDIT.TEC in a compatible way, and has been greatly extended to include many new features of VAXTPU, and optionally VAX LSE, such as: - support for multi file and multi buffer editing; - support for split screen editing using an optional second window into the same or another text buffer; - selection of insert and overstrike mode of editing; - selection of free and bound cursor movement; - many additional editor functions, like: + (search and) replace operations, + rectangular cut, paste, and delete operations, + operations to remember and retrieve buffer positions, + insertion of date, time, file and buffer names, + case and position control for searches, + case conversion and capitalization of words, + center line and fill paragraph operations, + control of tabulator setting, + operations to replace Tabs with spaces and vice versa, + deletion of trailing blanks, + sorting of buffers and ranges, + wildcard filename search and selection, + selection of user and system buffers from a list; - recognition of all TECO match control constructs and access to VAXTPU pattern building constructs; - journaling the editing session in order to protect against loss of work in case of a crash; - access to the VMS operating system via DCL, Spawn and Attach commands; - access to VAXTPU with possiblities to extend the VTEDIT editing interface; - optional semi automatic, context dependent text formatting providing the following functions: + case conversion / automatic case control, + automatic indentation, + manual correction of indentation, + automatic word wrap, + automatic line justification, + optional automatic insertion of closing parentheses and string delimiters, + optional highlighting of the matching opening parenthesis and string delimiter;  - no (practical) restrictions as to the maximum size of texts to be edited; - extensive online help; - optional access to the features of the Language-Sensitive Editor VAX LSE, providing operations to: + fill and align program comments, + specify a directory search list, + retrieve sources from a CMS library, + protect buffers against modification, + move to and/or delete placeholders, + expand tokens, routines, placeholders, and aliases, + define aliases for use in later expansions, + compile sources and review errors, + locate errors and retrieve the corresponding source text, + load language definitions and environments at run time, + access the LSE command interpreter directly; - optional access to the features of the Source Code Analyzer VAX SCA, providing operations to: + find declarations of symbols, + list positions of variable declarations and/or references, + retrieve corresponding sources, + access the SCA command interpreter directly. Installation of VTEDIT VTEDIT is installed via the standard VMSINSTAL procedure using the savesets VTEDIT045.A, VTEDIT045.B, and VTEDIT045.C. If you copied these savesets to the directory '[mydir]' on device 'mydisk:', you can install VTEDIT using the command: $ @SYS$UPDATE:VMSINSTAL VTEDIT mydisk:[mydir] The installation will take less than 5 minutes on a not too heavily loaded machine. To install VTEDIT, you need about 1600 free blocks on your system disk, and, if you select the option of getting the reference manual, this will need an additional 1400 blocks on your system disk. If you have the Language-Sensitive Editor VAX LSE on your system, the installation procedure will ask whether you wish LSE support. Selecting this option will require additional 800 blocks. You must have either SETPRV privilege or all of the following privileges: CMKRNL, SYSNAM, SYSPRV to install VTEDIT. If VTEDIT has been installed without support for the Language-Sensitive Editor and if such support is required at a later time - probably because VAX LSE was installed after the installation of VTEDIT -, support for the Language-Sensitive Editor can be made available by re-installaing VTEDIT. (Re-installation of VTEDIT is the recommended procedure for adding LSE support to native VTEDIT.)  The installation copies the environment file VTEDIT.ENV into the directory SYS$LIBRARY, if VTEDIT is installed with LSE support. This environment file contains an extensive definition of the language "Runoff" and some basic definitions for the languages "DCL", "Datatrieve", "Help" (for Help texts), and "VAXTPU", as well as some changes to the language "Fortran". You may wish to include some of these changes, or all of them, into your system environment file. The installation procedure will copy a short guide, contained in the file VTEDIT.DOC, to the directory SYS$EXAMPLES. If you have enough disk space, the procedure will ask if you want the user manual, too. If you respond with 'yes' to this question, the installation procedure will copy the two files VTEDIT.LNI (the reference manual, suitable for printing on an LN03 laser printer), and VTEDIT.RNO (the Runoff source for the .LNI file) to SYS$EXAMPLES. These two files are contained in the saveset VTEDIT045.C; if you do not select to get the reference manual, this saveset will not be read at all by the installation procedure. In any case, complete Help information will be provided in the help library SYS$HELP:VTEDIT.HLB. Side Effects The installation of VTEDIT will define the system-wide logical name TPU$CALL_USER to point to the file SYS$LIBRARY:TPUCALL.EXE. If you have VAXTPU interfaces using a system-wide call_user-routine, you will have to decide which file TPU$CALL_USER should point to. The standard VAXTPU interfaces provided by VMS do not use this mechanism and thus are not affected by the definition of this logical name. For further information about providing call_user-exits for VAXTPU, see the appropriate chapters of the VAXTPU documentation. Suggestions for enhancements, and reports on errors or problems should be sent to: Dr. G. Weck Infodas GmbH Rhonestr. 2 D-5000 Köln 71 West Germany