We used KEDIT for developing an Ada application, I wrote key bindings in KEXX and wrote edit macros in Quercus REXX. It was a nice editor, but I missed the full power of XEDIT.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Robert Raicer <[email protected]> Sent: Thursday, August 28, 2025 1:58 PM To: [email protected] <[email protected]> Subject: Re: Is HLASM efficient WAS: Telum and SpyreWAS: Vector instruction performance External Message: Use Caution Around 1986 (I don't remember the exact date) I met Kevin Kearney, the founder of the Mansfield Software Group and the developer of Kedit for DOS (that's PC DOS) at a SHARE conference. To cut to the chase, I was intrigued at the prospect of having an XEDIT-like text editor on a PC. I bought a copy of Kedit as well as Quercus Rexx (which was developed by another fellow and friend of Kevin Kearney, Charles Daney). Quercus Rexx was used as the macro language for Kedit. Eventually, a subset of Rexx was implemented by Mansfield and it became the integrated macro processor for Kedit; the macros have a file type of KEX and a macro library is supported as a file type of KML. Over the years I had the opportunity to be one of the beta testers for Kedit for Windows. Kedit for Windows is still supported by Mansfield, although there has been no new development on the product for quite some time. I still use Kedit nearly every day for all kinds of things. It has definitely been one of the most reliable PC products I've ever used. While I was working as a developer at IBM I wrote many macros for Kedit for Windows. A colleague of mine at IBM put together an elaborate set of Kedit macros and OO Rexx code to produce a very nice development environment for mainframe assembler as well as PL/X programming (assemblies/compiles could be submitted directly from the Kedit environment, the assembly/compilation listings would be made available directly in the environment as separate Kedit sessions with highlighting used for flagged warnings and errors, there was the capability to run IBM's internal source level debugger, and so on). I wrote some PL/X code to use the JES SAPI to access the listings on the JES Spool. And YES, virtually all of the modules we were developing for OS components were written in mixed case, with upper casing performed as appropriate (or necessary) by the Kedit macros. This environment allowed us to perform a significant amount of our code development work on Windows. I've been retired from IBM for almost a decade and I have no idea what has become of that code. Bob
