It's been decades, but I don't recall running into any KEDIT or Quercus REXX bugs. I liked it, but I had XEDIT macros for structured code entry that really needed something like SET PENDING. Sort of like ISPF models, but automatically dealing with indentation levels and multiple insertion points. E.g., if you requested insertion of an IF then you got blank lines after both the THEN and ELSE, with the blank lines disappearing if you hit ENTER without typing anything.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> on behalf of Mark Boonie <boo...@us.ibm.com> Sent: Thursday, August 28, 2025 2:51 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU <ASSEMBLER-LIST@LISTSERV.UGA.EDU> Subject: Re: Is HLASM efficient WAS: Telum and SpyreWAS: Vector instruction performance External Message: Use Caution In case my previous emails didn't make it obvious, let me add my name to the list of those who think Kedit is an outstanding product. The list of enhancements I'd like to see is short, and the list of buggy, erroneous, or otherwise wrong behavior is even shorter. The conversion of most of my Xedit macros to Kedit was effortless, and only a few required any real rework (and when I did the reworking I gave myself a better infrastructure for future tools as well). - mb > -----Original Message----- > From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> On > Behalf Of Robert Raicer > Sent: Thursday, August 28, 2025 1:59 PM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: [EXTERNAL] Re: Is HLASM efficient WAS: Telum and SpyreWAS: Vector > instruction performance > > 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
