HP_DECset_for_OpenVMS_______________________________ Language-Sensitive Editor for OpenVMS Release Notes August 2003 These release notes describe important general information, new and changed features, current restrictions, and documentation notes that pertain to the Language-Sensitive Editor Version 4.8 for OpenVMS software. Operating System Version: HP OpenVMS VAX Version 6.2, 7.2, or 7.3 HP OpenVMS Alpha Version 6.2, 7.2-2, or 7.3-1 Software Version: HP DECset Version 12.5 for OpenVMS Language-Sensitive Editor Version 4.8 for OpenVMS Hewlett-Packard Company Palo Alto, California ________________________________________________________________ © 2003 Hewlett-Packard Development Company, L.P. Microsoft, Windows, Windows NT, and Visual C++ are U.S. registered trademarks of Microsoft Corporation. Motif is a trademark of The Open Group in the United States and other countries. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendors standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. _________________________________________________________________ Contents Preface................................................... v 1 General Information 1.1 Introduction..................................... 1-1 1.2 Associated Documents............................. 1-1 1.3 Using LSE with DECwindows Motif.................. 1-2 1.4 Installation Requirements........................ 1-2 1.5 Compatibility Issues............................. 1-3 2 New Features 3 New Features in Version 4.7 3.1 Box Commands..................................... 3-1 3.2 Command to Delete Overview Information........... 3-3 3.3 COBOL Language Template.......................... 3-3 3.4 Example Language Extensions...................... 3-3 3.5 TPU Pattern Style................................ 3-4 3.5.1 User Interface ................................ 3-5 3.5.2 Partial Pattern Assignment Variables .......... 3-5 3.5.3 New Line ...................................... 3-6 3.5.4 Errors ........................................ 3-7 3.5.5 Global Variables .............................. 3-8 3.5.6 Pattern Variables ............................. 3-8 3.5.7 Use for Developing DTM User Filters ........... 3-8 iii 4 Problems Fixed 5 Known Problems 5.1 General.......................................... 5-1 5.2 Documentation.................................... 5-6 6 Restrictions iv _________________________________________________________________ Preface These release notes characterize the Language-Sensitive Editor Version 4.8 for OpenVMS (LSE) software. These notes contain information that either supplements or supersedes the information in the HP DECset Version 12.5 for OpenVMS (DECset) documentation set. Intended Audience These release notes are intended for users and system managers who need information about LSE on either of the OpenVMS operating system platforms (VAX or Alpha). Document Structure These release notes are organized as follows. o Chapter 1 contains general information about this release. o Chapter 2 contains a description of the new features. o Chapter 3 contains a description of the new features added in Version 4.7. o Chapter 4 describes all problems resolved by the current release. o Chapter 5 describes all outstanding issues in the current release. o Chapter 6 describes all restrictions. v Related Documents For additional information about OpenVMS or DECset products and services, visit the following web site: http://www.hp.com/go/openvms Reader's Comments HP welcomes your comments on these release notes. Please send comments to either of the following addresses: Internet openvmsdoc@hp.com Mail Hewlett-Packard Company OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 How To Order Additional Documentation For information about how to order additional documentation, visit the following World Wide Web address: http://www.hp.com/go/openvms/doc/ Conventions The following conventions are used in these notes. ___________________________________________________________ Convention__________Description____________________________ $ A dollar sign ($) represents the OpenVMS DCL system prompt. Ctrl/x The key combination Ctrl/x indicates that you must hold down the key labeled Ctrl while you press another key, for example, Ctrl/Y or Ctrl/Z or a pointing device button. boldface text Boldface text represents the introduction of a new term. monospace boldface Boldface monospace text represents user text input in interactive examples. vi ___________________________________________________________ Convention__________Description____________________________ italic text Italic text represents book titles, parameters, arguments, and information that can vary in system messages (for example, Internal error number). UPPERCASE Uppercase indicates the name of a command, routine, the name of a file, the name of a file protection code, or the abbreviation of a system privilege. lowercase Lowercase in examples indicates that you are to substitute a word or value ____________________of_your_choice.________________________ vii 1 _________________________________________________________________ General Information The information in these release notes pertains to the Language-Sensitive Editor Version 4.8 for OpenVMS (LSE) software. HP suggests that you upgrade your environment incrementally with each new release, but there is no technical requirement to do so. It is recommended that you review the release notes for each version because they capture important release-oriented information and advise you of changes between versions. 1.1 Introduction LSE Version 4.8 is a minor release. 1.2 Associated Documents The following documents contain information related to LSE. Note however, that for the HP DECset Version 12.5 for OpenVMS release, only the software product descriptions and component product release notes have been updated. The documents associated with LSE are: o Guide to DIGITAL Language-Sensitive Editor for OpenVMS Systems o DIGITAL Language-Sensitive Editor/Source Code Analyzer for OpenVMS Reference Manual Also applicable are the general DECset documents: o Compaq DECset for OpenVMS Installation Guide o HP DECset for OpenVMS Alpha Software Product Description o HP DECset for OpenVMS VAX Software Product Description o Guide to Detailed Program Design for OpenVMS Systems o Using DECset for OpenVMS Systems General Information 1-1 o Guide to DIGITAL Source Code Analyzer for OpenVMS Systems In addition to the base LSE documentation, the DECset engineering team has also provided the HP DECset for OpenVMS Cookbook for an Integrated Product Development Environment. This document comprises a series of technical articles that describe how each of the component applications can be used in different programming environments. This document is available in PostScript (.PS), HTML (.HTML), and ASCII text (.TXT) formats from the following location: SYS$SYSROOT:[SYSHLP.EXAMPLES.DECSET]DECSET_COOKBOOK.*" 1.3 Using LSE with DECwindows Motif To use LSE with the DECwindows Motif interface, one of the following must be installed: o HP DECwindows Motif for OpenVMS Alpha Version 1.2-5, 1.2-6, or 1.3 o HP DECwindows Motif for OpenVMS VAX Version 1.2-5 or 1.2-6 1.4 Installation Requirements For a new installation of LSE the following is required: For HP OpenVMS Alpha Systems Global Pages 10000 Global Sections 15 Disk Blocks 45000 For HP OpenVMS VAX Systems Global Pages 6000 Global Sections 15 Disk Blocks 40000 1-2 General Information 1.5 Compatibility Issues In versions of LSE prior to V4.3 the UNDO command is implemented to reverse the effect of the last ENTER COMMENT command. This effect can still be achieved if the user specifies the following format: UNDO ENTER [COMMENT] General Information 1-3 2 _________________________________________________________________ New Features No new enhancements have been added to LSE Version 4.8. New Features 2-1 3 _________________________________________________________________ New Features in Version 4.7 The following enhancements were added to LSE Version 4.7. 3.1 Box Commands Commands that operate on a selected box have been added. The commands have OpenVMS and portable command language forms and they are also available from a new top level menu named Box. BOX commands operate on a selected range. The standard methods of selecting a range are used. The top left corner of the box is given by the first character in the selection and the bottom right corner is given by the last character in the selection. If, for the example shown below, a selection that includes all the upper case letters is made, then for a BOX command the selected box is the area containing the letter B. eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee eeeeeeeeBBBBBBBBBBBBBBBBBBIIIIIIIIII IIIIIIIIBBBBBBBBBBBBBBBBBBIIIIIIIIII IIIIIIIIBBBBBBBBBBBBBBBBBBIIIIIIIIII IIIIIIIIBBBBBBBBBBBBBBBBBBeeeeeeeeee eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee If the BOX DRAW command is issued for the selection described above the result is: eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee eeeeeeee+----------------+IIIIIIIIII IIIIIIII|BBBBBBBBBBBBBBBB|IIIIIIIIII IIIIIIII|BBBBBBBBBBBBBBBB|IIIIIIIIII IIIIIIII+----------------+eeeeeeeeee eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee New Features in Version 4.7 3-1 Box operations are performed by the following commands: ___________________________________________________________ OpenVMS_Command_______Portable_Command_____________________ BOX COPY BOX COPY BOX CUT BOX CUT BOX CUT/PAD BOX CUT PAD BOX PASTE BOX PASTE BOX DRAW BOX DRAW BOX PASTE/OVERSTRIKE BOX PASTE OVERSTRIKE BOX LOWERCASE BOX LOWERCASE BOX_UPPERCASE_________BOX_UPPERCASE________________________ The BOX COPY command copies the currently selected box to the default location (the DECwindows clipboard or the paste buffer). The BOX CUT command moves the currently selected box to the default location. The BOX CUT/PAD command moves the currently selected box to the default location and the box is replaced by spaces. The BOX PASTE command copies the contents of the default location to a box with its top left hand corner at the current position. The BOX PASTE/OVERSTRIKE command copies the contents of the default location to a box with its top left hand corner at the current position. The contents are copied in overstrike mode. The BOX DRAW command draws a box in overstrike mode. The box is drawn using the plus sign (+) for the corners, the vertical bar (|) for the sides and a hyphen (-) for the top and bottom. The BOX LOWERCASE command changes the case of the text in the selected box to lowercase. The BOX UPPERCASE command changes the case of the text in the selected box to upper case. 3-2 New Features in Version 4.7 The following restrictions apply: o A box operation is not allowed if there is overview information in the records that make up the box. o If a box operation is performed for which the total size of the records containing the box before or after the operation is greater than 65535 characters then undo information is reset. o Auto erase is switched off during a box paste operation. o Tabs in the records containing the box are converted to spaces and the records may be extended with spaces. 3.2 Command to Delete Overview Information This command gets rid of all the overview lines in the current buffer and makes all the real lines in the buffer visible. ___________________________________________________________ OpenVMS_______________Equivalent_Portable__________________ DELETE_OVERVIEW_______DELETE_BUFFER_OVERVIEW_______________ The portable command clashes with the portable command to delete a buffer with name OVERVIEW. The problem can be avoided by enclosing OVERVIEW in quotes when it is the name of a buffer. 3.3 COBOL Language Template A new version of the COBOL Language Template has been added to LSE. 3.4 Example Language Extensions Language template files for Java (JAVA.LSE) and Perl (PERL.LSE) have been added to the examples directory (LSE$EXAMPLE). New Features in Version 4.7 3-3 3.5 TPU Pattern Style A new pattern style TPU has been added to the existing pattern styles, VMS and ULTRIX. For full details of TPU patterns see the DEC Text Processing Utility Reference Manual. Pattern styles are used in: o SEARCH/PATTERN command (VMS command language) o SUBSTITUTE/PATTERN command (VMS command language) o PATTERN SEARCH command (Portable command language) o PATTERN SUBSTITUTE command (Portable command language) o PATTERN EXACT SUBSTITUTE command (Portable command language) o Search dialog box (Search / Search ...) o Substitute dialog box (Search / Substitute ...) The new TPU pattern style is used in a similar way to the existing styles. The main advantages of the new style are: o Direct access to the powerful TPU pattern facility (the existing pattern styles use the facility indirectly). o The ability to make a substitution that is a function of the pattern found. o The ability to develop Digital Test Manager Version 4.1 for OpenVMS (DTM) user defined filters interactively. Most of the examples in the following sections are given using the VMS command language and assume that the search options are set to the TPU pattern style and case insensitive searching. The search direction is assumed to be forward and the cursor is assumed to be positioned before the example text. The search and replace parameters in the VMS command language examples can be used unchanged in the equivalent Portable command language commands. 3-4 New Features in Version 4.7 3.5.1 User Interface The TPU pattern style is selected in one of three ways: SET SEARCH PATTERN=TPU (vms command language ) SET SEARCH PATTERN TPU (portable command language) Select TPU pattern on the Search Attributes window (Options/Search Attributes...) The only other user interface change is the form of the search and replace string parameters when the TPU pattern style is selected for a pattern search or substitution. The search string parameter is a TPU expression that must evaluate to a TPU pattern and the replace string parameter is a TPU expression that must evaluate to a TPU string. The following examples are given in both command languages. The first two examples search for abc or def and the last two examples substitute all occurrences of abc or def by ghi: SEARCH/PATTERN "'abc' | 'def'" PATTERN SEARCH "'abc' | 'def'" SUBSTITUTE/PATTERN/ALL "'abc' | 'def'" "'ghi'" PATTERN SUBSTITUTE "'abc' | 'def'" "'ghi'" ALL In the above examples 'abc', 'def' and 'ghi' are TPU strings and | is the TPU pattern alternation operator. The outermost quotes in the above example must be omitted if the parameters are prompted for or if a dialog box is used. 3.5.2 Partial Pattern Assignment Variables Partial pattern assignment variables allow a substitution to be a function of the found pattern. For example, the following command replaces a date of the form yyyy/mm/dd with one of the form dd/mm/yyyy: SUBSTITUTE/PATTERN - "(_year@_v1)+'/'+(_month@_v2)+'/'+(_day@_v3)" - "str(_v3)+'/'+str(_v2)+'/'+ str(_v1)" when applied to: 1998/04/21 generates: 21/04/1998 New Features in Version 4.7 3-5 In the above example _year, _month and _day are TPU variables holding patterns that match the year, month and day parts of a date, for details of how to set up these variables, see Section 3.5.6. In addition, @ is the TPU partial pattern assignment operator, and _v1, _v2 and _v3 are partial pattern assignment variables that are set to the found year, date and day. A partial pattern assignment variable holds a TPU range and when used in the replacement string must be converted to a string using the TPU procedure STR. For example, the following command prefixes any lines that start with any three characters from ABCDEFGHI with XYZ_ : SUBSTITUTE/PATTERN/ALL - "LINE_BEGIN + (ANY('ABCDEFGHI',3)@_v1)" - "'XYZ_'+ str(_v1)" when applied to: abc generates: XYZ_abc 012 012 defghi XYZ_defghi In the above example LINE_BEGIN is a TPU keyword that matches the beginning of a line and ANY is a TPU pattern procedure that matches a specified number of characters from a specified set of characters. 3.5.3 New Line A new line is generated for each line feed character in the replacement string, a line feed character can be introduced by means of the TPU procedure ASCII with the value 10 as a parameter. For example, to replace any numbers at the end of lines with the string 'xxx' (a line feed is necessary because the search pattern includes the end of the line): SUBSTITUTE/PATTERN/ALL - "_n + LINE_END" - "'xxx' + ASCII(10)" when applied to: 123 456 generates: 123 xxx 789 xxx 3-6 New Features in Version 4.7 In the above example, LINE_END is a TPU keyword that matches the end of a line and _n is TPU variable holding a pattern that matches a number. When a partial pattern assignment variable is converted to a string by the TPU procedure STR an optional second parameter can be set to ASCII(10) to cause any end of lines in the range described by the variable to be converted to line feed characters (without the parameter they are represented by the null string). For example: SUBSTITUTE/PATTERN/ALL - "(LINE_BEGIN + _n + LINE_END + _n + LINE_END)@_v1" - "STR(_v1, ASCII(10)) + STR(_v1, ASCII(10))" when applied to: 123 generates: 123 456 456 123 456 Carriage return characters adjacent to line feed characters in the replacement string are ignored. 3.5.4 Errors The search and replace strings are TPU expressions which have to be evaluated and may generate various TPU compilation / evaluation error messages. Two new error messages have been added for invalid search or replace parameters: Error in search pattern Error in replacement string These messages are normally preceded by various TPU error messages. For example, the search string "'aaa' + bbb" results in the following error messages: Undefined procedure call BBB Operand combination STRING + INTEGER unsupported Error in search pattern New Features in Version 4.7 3-7 3.5.5 Global Variables Partial pattern assignment variables and pattern variables (such as _year in an earlier example) need to be global and must not clash with any TPU global variables used by LSE. This can be achieved by starting any such variable names with an underscore character. 3.5.6 Pattern Variables Any complicated search or substitution is likely to need various pattern variables to have already been set up. This can be achieved in various ways. The definitions can be set up by issuing DO/TPU commands, for example: DO/TPU "_digits:='0123456789'" DO/TPU "_digit:=any(_digits)" DO/TPU "_year:=any(_digits,4)" DO/TPU "_month:=any('01',1)+_digit" DO/TPU "_day:=any('0123',1)+_digit" DO/TPU "_n:=span(_digits)" The file LSE$PATTERNS.TPU in the LSE$EXAMPLE directory contains some examples of patterns which can be added to LSE by means of the following commands: GOTO FILE LSE$EXAMPLE:LSE$PATTERNS.TPU EXTEND * DO/TPU "LSE$PATTERNS_MODULE_INIT" 3.5.7 Use for Developing DTM User Filters The user defined filters global replace feature introduced in DTM Version 4.0 can be simulated using the SUBSTITUTE/PATTERN/ALL command. This allows DTM user defined filters to be developed interactively using LSE. For example, to replace any numbers at the end of lines with the string 'xxx': 3-8 New Features in Version 4.7 global_replace( _n + LINE_END, 'xxx' + ASCII(10), NO_EXACT, OFF, ON); The LSE equivalent (assuming that the current search attributes are equivalent to NO_EXACT) is: SUBSTITUTE/PATTERN/ALL - "_n + LINE_END" - "'xxx' + ASCII(1O)" The LSE equivalent of the pattern to replace parameter (first parameter of the global_replace routine) is the same except that the parameter has to be in quotes. The LSE equivalent of the replacement string parameter (second parameter) is the same if the evaluate replacement parameter (fourth parameter) is set to ON. If the evaluate replacement parameter is set to OFF the parameter must be in quotes. The LSE equivalent of the search mode parameter (third parameter) is the setting of the search options (set by the SET SEARCH command). LSE does not have equivalents of the evaluate replacement parameter (fourth parameter) or the convert linefeeds parameter (fifth parameter). It always evaluates the replacement string parameter and it always converts linefeed characters (and ignores adjacent carriage return characters). New Features in Version 4.7 3-9 4 _________________________________________________________________ Problems Fixed The following problems were fixed and restrictions removed in LSE Version 4.8: o ID:2225 - A very long portable command language command now produces the error message 'Command too long' and does not produce inappropriate errors such as 'Compilation aborted'. o ID:2282 - Modifying the buffer attributes of the buffer for a file opened from a different directory than the default can no longer result in the file being incorrectly saved to the default directory. o ID:2283 - The LSE version is no longer missing from Alpha LSE trace back information. o ID:2284 - In DECwindows mode a trace back is no longer generated if the display cannot be opened. o ID:2285 - An error that could cause LSE in DECwindows mode to fail with an access violation on exit has been fixed. o ID:2286 - A fault that could result in a CUT/REPLACE (PF1 KP9 key sequence) failing with an internal error /stack dump has been fixed. o ID:2290 - A fault introduced in LSE 4.7-3 that could result in the window attributes (height and width) not being saved to a command file has been fixed. o ID:2291 - An error is now always reported when a parameter is specified for a portable syntax command that has no arguments. o ID:2292 - The bad formatting of the TAKESONLY error has been corrected. Problems Fixed 4-1 o ID:2293 - Collapse All on the View menu now works correctly. o ID:2294 - Various minor problems with error trace back information have been fixed. 4-2 Problems Fixed 5 _________________________________________________________________ Known Problems 5.1 General The following known problems exist in LSE Version 4.8: o ID:2155 - Internal error compiling a DECforms for OpenVMS program after a Ada program. LSE will crash with an internal error when attempting to follow the compilation of an Ada program with the compilation of DECforms source. The source of the two programs appears to be unimportant. The workaround is to compile the DECforms source first. o ID:2156 - SCA LOAD and ANALYZE command parameters do not default to current buffer. The file-spec[,..] parameter cannot be defaulted, the HELP information incorrectly says the default is the current buffer. o ID:2158 - Cannot define an ALT key sequence as the Gold key. LSE cannot accept an ALT key sequence as the Gold key. When an attempt is made, LSE accepts the key definition without errors, but does not recognize the ALT key sequence as the Gold key (this definition does however disable PF1 as the Gold key), however if you show the key definitions the newly defined key has the correct definition. Different results are apparent depending on whether the DECwindows interface to LSE is used or if the character- cell mode interface to LSE is used. For example, in the DECwindows mode, ALT/G can be defined as the Gold key. LSE accepts the key definition, but ALT/G is not recognized as the Gold key. However, if SHIFT/ALT/G is pressed then LSE recognizes it as the Gold key. In Known Problems 5-1 the character-cell interface not even SHIFT/ALT/G is recognized. Again, LSE accepts the definition of ALT/G as the Gold key without errors. The workaround is to define the key via TPU: LSE> do/tpu "set(shift_key,key_name('g',alt_modified) o ID:2164 - TPU$_WINDNOTMAPPED error reading TPU procedure into DECwindows LSE. DECwindows LSE may report the following error when trying to read in and compile a TPU procedure at start up: The window is not mapped to a buffer (TPU$_WINDNOTMAPPED). When this problem occurs, LSE will display an invalid window format (one that does not have a status line). The errors themselves will not be visible unless you display the contents of the message buffer. For example: DO LSE> GOTO BUFFER $MESSAGES ! a normal window is display for buffer $MAIN DO LSE> GOTO BUFFER $MESSAGES The workaround is to start LSE with the command LSE /COMMAND=DE_TAB.TPU and add the following line at the bottom of the DE_TAB.TPU procedure: LSE_NEW_KEY( "TAB", "TPU REM_TABS" ); This will automatically read in the TPU procedure, compile it, and define an LSE key to run it. o ID:2165 - DECwindows SET DEFAULT does not change the default disk after OPEN FILE. In the LSE DECwindows interface, the SET DEFAULT command does not change the default device when issued after using the OPEN FILE command. It correctly changes the default directory but not the device. Prior to calling OPEN FILE, SET DEFAULT works as required. When you exit LSE your default device is changed. 5-2 Known Problems The workaround is to perform the SET DEFAULT command before opening any files in the DECwindows interface or specify the default directory as the filter specification in the open file window. o ID:2174 - Cursor positioning across split screens. When splitting a file into two or more screens, the cursor correctly maintains its position when going back and forth between the windows. However, using the up or down arrows can cause the cursor to change column position to the same position in the other screen. This problem occurs only when moving up or down or the last operation is an up/down motion. For example, moving up in the top screen in column 30, then switching to the bottom screen and trying to move up in column 10: the cursor jumps to column 30. If you first move the cursor left/right or perform any other action, the cursor stays in the column expected. The problem only occurs when using the portable command language interface. o ID:2198 - Cannot access help text after using ENABLE VMS INTEGRATION. After issuing the ENABLE VMS INTEGRATION command, a HELP FIND returns "No help available for the topic specified". HELP GOTO DECLARATION has the same problem. The ENABLE VMS INTEGRATION command enables two additional command prefixes VMSCMS_ and VMSSCA_. The error occurs because there is a FIND routine associated with the VMSSCA_ prefix for which there is no help. The FIND routine associated with the VMSSCA_ prefix hides the standard FIND routine (associated with the default prefix LSE_). The help for the standard FIND routine can still be displayed if part of it's second key is also given as this makes it unique and stops it from being hidden (such as FIND OCCURRENCES). The real error is that there is no help for any of the VMSCMS_ or VMSSCA_ prefix commands. o ID:2216 - SET DIRECTORY DEFAULT not propagated to current compile sub-process. Known Problems 5-3 LSE's portable command language does not propagate changes in the default directory to an already existing compile sub-process; causing the next COMPILE REVIEW command to fail with "Error opening ". o ID:2220 - UNDO access violation changing lines using keys bound to TPU procedures. The fault can occur if user written TPU code is associated with a key. The fault can occur in the setting up of information required to support undo/redo processing for user written TPU code associated with a key. When the key is used the call of the associated code is not jacketed by any LSE code and cannot be protected against undo/redo problems. Four possible workarounds are: 1. Disabling undo/redo processing by means of the SET MODE UNDO (SET UNDO portable) command. 2. Setting the value of MAX_UNDO to zero for each buffer being edited; this may be done via a key definition: For example: LSE Command> DEFINE KEY "F17" "SET MAX_UNDO 0" 3. Defining all your keys using the LSE "DEFINE KEY" or "NEW KEY" commands. For example: LSE Command> DEFINE KEY _Key: "GOLD-Z" _String: "do/tpu """"" or: LSE> NEW KEY Key Name: GOLD-Z LSE Command: tpu "" 4. Making the TPU code to be executed by the defined key a parameter of the routine lse_tpu. This routine protects against undo/redo problems by deleting the undo/redo information for all buffers and inhibiting the setting up of any undo/redo information during the execution of the TPU code associated with the key. 5-4 Known Problems For example:- define_key("lse_tpu('position(buffer_begin)')", key_name("x",shift_key)) o ID:2228 - LSE may fail when executing user's TPU code via a pull-down menu or a user command language. This is similar to ID:2220. o ID:2229 - A spurious error message may be produced when the help command is issued for a long non-existent topic. For example: LSE> HELP Nonexistent_topic Error opening LSE$HELP as input No help available for the topic specified o ID:2231 - If a buffer which has been reviewed is deleted using the DELETE BUFFER command the REVIEW information associated with the buffer is not cleaned up. For example, following the deletion, the END REVIEW command does not produce the error "NO REVIEW IN PROGRESS". o ID:2243 - CTRL/C may not be correctly handled if issued while a DO command is processing a buffer. o ID:2245 - The VMS and portable syntax commands are not consistent in their generation of brief or full information. The /FULL qualifier does not always result in a full display and the /BRIEF qualifier does not always produce a brief display. o ID:2247 - Command mode prompt problem. The 'LSE>' prompt is at times improperly displayed when the 'LSE Command>' prompt for single command mode is expected. o ID:2254 - Unavailable SCA commands. The SCA commands IMPORT, SAVE QUERY and @file-spec are not available from LSE. o ID:2273 - Undo LF and CR character problem. Known Problems 5-5 Undo may not work correctly when applied to the deletion of a line feed, for example: aa Using pattern substitution replace a*a by bbb bbb Undo a The line feed character is lost and the a two a's are in different lines. Any carriage return characters adjacent to the line feed character would also be lost. o ID:2287 - Inclusion of a large file using the INCLUDE command can be very slow. The performance can be improved by switching off journaling or by using the similar READ command if this is appropriate (VMS command language only). o ID:2288 - There is no Portable Command Language equivalent of the VMS Command Language READ command. o ID:2295 - Use of DECwindows help can be slow. The poor performance is most noticeable after large help items have been displayed. The display of a large help item can also affect the time taken to exit from LSE. An example of a large help item is the 'Command Definitions' topic which is approximately 1500 lines long. 5.2 Documentation The following documentation problems exist for LSE Version 4.8: o ID:2266 - Incorrect Language Definition Example The example in Section 4.1.1 of the Guide to DIGITAL Language-Sensitive Editor for OpenVMS Systems is incorrect, it contains: PLSE SET LANGUAGE FILE TYPES ".MEMO .FOO" ADD memo This should be: PLSE SET LANGUAGE FILE TYPES ".MEMO" ADD memo PLSE SET LANGUAGE FILE TYPES ".FOO" ADD memo 5-6 Known Problems This problem replaces ID:2196 which was raised against an incorrect use of the SET LANGUAGE FILE TYPES command. o ID:2276 - Missing documentation of LSE$$SOURCE Internally LSE uses the logical LSE$$SOURCE for source directories. LSE$$SOURCE is initialized from LSE$SOURCE. LSE$SOURCE is not updated when LSE$$SOURCE changes. Known Problems 5-7 6 _________________________________________________________________ Restrictions The following restrictions apply to LSE Version 4.8: o LSE does not support VT500 series terminals. A VT500 series terminal should be set to emulate a supported terminal such as a VT300 series terminal. o The UNDO operation has no effect for the LSE FOCUS command. When the FOCUS command is executed, the UNDO buffers will be reset. No previous operations can be undone. o No UNDO support for TPU commands. For example : TPU "erase (current_buffer)" (Portable) DO/TPU "erase (current_buffer)" (OpenVMS) When a TPU command is executed, the undo buffers will be reset. No previous operations can be undone. o UNDO and REDO commands are disabled in OVERSTRIKE mode. If the buffer is in OVERSTRIKE mode (not insert), initiating the UNDO or REDO command will have no effect. When the mode is changed to INSERT, undoing and redoing is possible again. o UNDO and REDO commands are disabled following a command that generates overview information. They can be re-enabled by deleting overview information, see Section 3.2. o Fortran for OpenVMS Systems - Fortran 90 Language Support. Automatic generation of continuation lines is not supported. o DECnet/OSI Phase V support. Restrictions 6-1 When using portable syntax commands, file names that start with a quote must be enclosed in quotes (single or double). Inner quotes of the same type as the enclosing quotes must be doubled up. For example: LSE> NEW FILE '"A&=BCD"::B.C' LSE> NEW FILE """AAAAAAAAAAAAAAA""::B.C" 6-2 Restrictions