KEDIT

K5SL4.DOC - KEDIT 5.0 Service Level 4 - Fall 1997 This file lists the changes made to KEDIT 5.0 since the original release of KEDIT 5.0 in the Spring of 1992. Changes made in the most recent Service Level are listed first: * KEDIT 5.0 Service Level 4 (released Fall 1997) * KEDIT 5.0 Service Level 3 (released Summer 1994) * KEDIT 5.0 Service Level 2 (released Spring/Summer 1993) * KEDIT 5.0 Service Level 1 (original KEDIT 5.0 Release, Spring 1992) *** Here is a summary of the changes made in KEDIT 5.0 Service Level 4 The Service Level 4 changes involve a few bug fixes, along with some improvements to KEDIT's DIR command, allowing it to display and sort on 4-digit years. * SET DIRFORMAT now accepts a third operand, which determines whether the file dates displayed by KEDIT's DIR command use a 2-digit or 4-digit year. SET DIRFORMAT 8 3 2 is the default under both DOS and OS/2, and yields a 2-digit year such as 97 or 00. SET DIRFORMAT 8 3 4 yields 4-digit years, such as 1997 and 2000. (The first two operands of SET DIRFORMAT control the width set aside for file names and file extensions. With the DOS version of KEDIT, 8 character names and 3 character extensions are the only allowable values, but the OS/2 and Windows versions support long filenames, and hence allow larger values to be specified.) * When a DIR.DIR file is sorted via DIRSORT DATE or DEFSORT DATE, KEDIT will now treat two-digit years from 80 through 99 as 1980 through 1999, and will treat two-digit years from 00 through 79 as 2000 through 2079. * EXTRACT /TIME/, used from within a KEDIT macro, yielded an incorrect value for TIME.3 beginning in the year 2000. TIME.3 now correctly returns the date in the format mm-dd-yy. TIME.5 is now also available; it returns the date in the format yyyy-mm-dd. * Other KEDIT 5.0 changes in Service Level 4: * Fixes affecting only the DOS version of KEDIT: - Mouse was disabled in KEDIT after KEDIT DOS command under NT 4.0 - UNDO could append garbage to lines with > 127 leading blanks * Fixes affecting only the OS/2 version of KEDIT: - WRAP ON was ignored for backward searches, (LOCATE -/string/) - KEDIT could crash after FILE/QUIT from large (>32 meg) file *** Here is a summary of the changes made in KEDIT 5.0 Service Level 3 * Changes affecting both the DOS and OS/2 versions of KEDIT.EXE: - Added CLASSIC() and CUA() Boolean functions - Added MERGE command - Allow KEDIT "fileid", with fileid in quotes, to include parentheses - Autosave alteration count was not reset to 1 after error in autosave - Block coloring on screen was not always updated properly - CANCEL command was quitting file with cursor in modified field - CURLINE.3 was ignoring char in truncation col if TRAILING ON - DEFPROFILE and PROFILE options now allow fileids in quotes - DOS command in mouse macro now forces button up handling - EXTRACT /LASTKEY/ in ASCII macro didn't have latest keystroke - KEDIT crashed after Ctrl-End on cmd line with char in WIDTH column - KEDIT crashed if WORDWRAP, nonblank in margin+1, insert blank past line end - KEDIT gave Improper Cursor Position error if typing on Tof/Eof, after trunc - KEXX function names had a limit of 20 chars, now raised to 80 - LOCATE PARAGRAPH sometimes crashed KEDIT by looking beyond end-of-range line - Memory leak was possible after out-of-memory for KEXX variable - Memory release was delayed with variable numeric +(n) in PARSE template - PREFIX ON RIGHT, col to left of prefix area incorrectly got prefix color - Trailing blanks were not saved properly if TABSOUT ON - Unsuccessful searches with cursor starting on shadow line caused loop * Changes affecting only the DOS version of KEDIT.EXE: - Fix incorrect DIR.DIR files in rare situations due to PROFILE processing - Workaround network error for files with write but not delete access * Changes affecting only the OS/2 version of KEDIT.EXE: - Added MACROSPACE init option; allows execution of macros in REXX macrospace - Alt/Shift/Ctrl key problems between KEDIT and 4OS2 resolved - Improved performance when editing in directory with very many files - KEDIT wasn't correctly determining startup directory - Maximum allowable screen height raised from 80 to 120 - Workaround OS/2 2.1 problem with STDIN/STDOUT handle checking * Further notes on a few of these changes: * We have added two new Boolean functions, CLASSIC() and CUA(). CLASSIC() always returns 1 and CUA() always returns 0. These functions will help some users of the upcoming Windows version of KEDIT write key definitions that work in both the text mode and the Windows versions of KEDIT. * An XEDIT-compatible MERGE command is now available. For a description, see the MANUAL.DOC file or look for the MERGE command in KHELP. *** Here is a summary of the changes made in KEDIT 5.0 Service Level 2 * Changes affecting both the DOS and OS/2 versions of KEDIT.EXE: - When IDLINE is off or overlayed by reserved line, clicking on it with mouse was improperly cycling through files in ring. - With TRAILING ON, lines consisting of one or more trailing blanks were not found by BLANK targets. - With large values for WIDTH option, ISA could become full too easily. - If the cursor was in a prefix area field whose text had been altered, PENDING() function did not reflect the change. - If the cursor was on a line whose text had been altered, LINEFLAG QUERY/EXTRACT value did not reflect the change. - DIRFILEID QUERY/EXTRACT value stopped at first blank in directory names, causing problems for HPFS directory names containing blanks; it will now stop only after two consecutive blanks. - When using debug facility to trace KEXX macros, REXX-style comments containing quotes were sometimes improperly handled. - When using debug facility to trace KEXX macros, INTERPRET instructions in the macro that generated errors were improperly handled. - The maximum length of a macro name was 20, which was shorter than desirable for some mousebar macros; the new limit is 40. - REXX-style comments at the start of KML files should be ignored but were not. - If the profile executed for a MACROS command issued commands that affect the file, the MACROS command did not always function properly. - The cursor could be positioned at an illegal location after DIR or MACROS commands issued with CMDLINE OFF, sometimes crashing KEDIT. - Some default mousebar macros used possibly-uninitialized variables, giving errors if NOVALUE ON was in effect. - Cursor could be positioned improperly after TABL or SCALE prefix commands. - If the profile executed when adding a file to the ring left some other file as the current file when it finished execution, undo handling was not turned on for the added file. - The alteration count was not being properly updated after an UNDO or REDO of a SORT command. - CHDIR improperly did not accept double quotes around its operand. - Errors involving KEXX expressions with extra right parentheses were not properly handled - Ctrl-Break conditions were not reset until the next keystroke, and should also have been reset after the next mouse action - In certain unusual cases KEXX macros could incorrectly get an 'Unexpected or unmatched END' error message - Leading blanks following LF in DIALOG command prompts were incorrectly being removed - DIR command issued with CMDLINE OFF could cause KEDIT crashes - Raised KEXX macro line limit from 500 to 1000 - If the UNDO command removed block marking from another file in the ring, the view on screen of the file wasn't immediately updated to show the change - Made MSGMODE ON the default for all new files, unless NOMSG option used - KEXX TRACE instruction got an error if it ended in trailing blanks - Internal changes have been made to reduce memory fragmentation problems within the FSA - The KEXX POS() function could return incorrect results in some cases when the value of the third parameter was greater than the current WIDTH. * Changes affecting only the DOS version of KEDIT.EXE: - Method used to initialize PC speaker caused conflicts for a few users. - With XMS in use, KEDIT could never sort more than about 2500 lines. Now, if there is sufficient DOS memory, we try to reserve enough to make larger sorts possible. - SET LOCKING ON or LOCK command caused system integrity violation under Windows for Workgroups. - Use of XMS memory on certain Compaq machines could cause KEDIT crashes. - When using the CC macro, Microsoft Resource Compiler (RC) output was incorrectly being included in the CC.TMP file. - Changed method of putting 25-line mode back into effect on exit from KEDIT after using a different height within KEDIT, to make it match KEDIT 4.0's handling and avoid problems for a few users - Improved performance in some situations for FILE and SAVE commands - Fixed performance problem affecting a few users of SORT command under Windows - If you tried to edit a hidden file, the DOS version of KEDIT incorrectly let you edit a new file by that name, with no error until you tried to save it - EMS Save/Restore page frame call used by KEDIT fails on some systems; KEDIT now works around this instead of exiting with an error message - Available memory shown on the status line was incorrect on some systems with memory managers allocating EMS and XMS memory from a shared pool * Changes affecting only the OS/2 version of KEDIT.EXE: - KEDIT would hang if no mouse available, mouse driver not loaded, or bad return codes came back from mouse driver. In particular, if you attempted to use KEDIT when OS/2 was booted from the installation diskette, no mouse driver was available, and KEDIT would hang. - Using KEDIT command with a fully qualified name to move to a file already in the ring caused unnecessary disk I/O. - KEDIT command could not handle HPFS fileids with a file extension but no file name. KEDIT for OS/2 will now treat 'KEDIT .EXT', issued from the KEDIT command line, as a request to edit the file .EXT, rather than as an undocumented shortcut equivalent to 'KEDIT =.EXT'; this shortcut is still allowed in the DOS version of KEDIT. - Could not edit files on CD-ROM drives or certain network file systems. - DIRFILEID with FCASE ASIS was returning information in uppercase; it will now be returned in mixed case. - With FCASE ASIS, KML files that load macros based on the current file's extension improperly made a case-sensitive comparison of extensions. - Attempting to edit a file with Extended Attributes that don't follow the normal conventions could crash KEDIT. - KEDIT was using unnecessary amounts of CPU when tracking mouse movements. - When using the REXXVERSION EXTRACT operand, REXXVERSION.3, which should be set to the null string, was not being set. - SET REXXIO previously took effect only for macros that began execution after it was issued. With IBM's OS/2 REXX, it is possible to have it take effect with the currently-executing macro, so we now do this. - Max supported screen size was 79 by 199, and it should be 80 by 200. - Arg[0] was not being passed properly to the OS/2 command processor when the DOS command was issued with no operands; this had no effect with CMD.EXE, but could affect alternative command processors (and did affect Hamilton C Shell). - QUERY DIRECTORY could crash KEDIT if name of current directory was longer than 100 characters - '*' and '?' were incorrectly being accepted in OS/2 fileid's * Minor changes for KEDIT 5.0 Service Level 2 have also been made to KHELP.EXE (both DOS and OS/2 versions), KMEMTEST.EXE, and the sample macro MANYFILE.KEX. A number of improvements have been made to KREF50.HLP, primarily involving better cross referencing between topics. * Further notes on a few of these changes: - Note that the maximum number of lines in a KEXX macro has been raised from 500 to 1000. - SET MSGMODE has been changed a bit. With REPROFILE OFF, the MSGMODE setting for a new file was formerly set equal to the MSGMODE setting in effect in the file that was previously the current file. Now, MSGMODE ON is always put into effect for all new files, unless the NOMSG option is used on the command that adds the file to the ring. (This helps avoid a problem for macros that use NOMSG KEDIT or NOMSG DIR, with REPROFILE OFF in effect. MSGMODE OFF was sometimes being left in effect for the new file when the NOMSG command completed.) - Since OS/2 HPFS fileids can begin with a period, KEDIT for OS/2 will now treat 'KEDIT .ext', issued from the KEDIT command line, as a request to edit the file .ext, rather than as an undocumented shortcut equivalent to 'KEDIT =.ext'. This shortcut is still allowed in the DOS version of KEDIT. (We recommend against using it, since it may be necessary to disallow it in a future version of KEDIT.) - In the 32-bit OS/2 version of KEDIT, a number of changes have been made to improve performance and to raise or remove internal limits. The higher limits are discussed in the README.DOC file. - In the 32-bit OS/2 version of KEDIT, a slight change has been made to the handling of Extended Attributes. The .LONGNAME Extended Attribute is no longer preserved when a file is written to disk under something other than its original name, when a file is autosaved, or when a .BAK file is created. This avoids a problem where two files (the original file and the newly created file) had identical .LONGNAME Extended Attributes, and therefore appeared in the Workplace Shell as two files with the same name.