Summary of Changes in KEDIT 5.0 Service Level 2
Here is a list of the changes made to KEDIT 5.0 in Service Level 2,
which was released in mid-1993.
All of the changes listed here are also included in KEDIT 5.0 Service Level 3 and in KEDIT 5.0 Service Level 4.
KEDIT 5.0 was originally released, as KEDIT 5.0 Service Level 1, in
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
- 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
- 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
- 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
- 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
- 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
Changes affecting only the OS/2 version of KEDIT.EXE:
- 16-bit OS/2 module replaced by 32-bit module in July 1993.
- 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 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 fileids
- Minor changes for KEDIT 5.0 Service Level 2 were also made to
KHELP.EXE (both DOS and OS/2 versions), KMEMTEST.EXE, and the sample
macro MANYFILE.KEX. A number of improvements were made to
KREF50.HLP, primarily involving better cross referencing between topics.
- 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.
- 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
KEDIT Home Page
KEDIT Overview |
Download Libraries |
Demo Version |
Technical Support |
KEDIT for Windows 1.6.1 Upgrade |
KEDIT Mailing List
Copyright © 1996-2012 Mansfield Software Group, Inc.