Bill Arlofski wrote in a message to Jack Stein:
JS> I would have suspected that TSE for OS/2 would have sold well, since a
JS> large number of "power users", those most likely to use a powerful
JS> text editor, switched to OS/2 long ago.
 BA> Very good point.
JS> WIN may have lots of users, but the majority of them don't likely know
JS> what to do with a text editor, let alone a programable one such as
JS> TSE.
 BA> I think you mentioned Boxer in a post a few messages back...
 BA> Anywhere one can grab a copy, and is it still being
 BA> suppported? 
I don't know what versions its up to now, nor do I know if its still 
supported.
I have 2 versions here that you can fre'q:
BOXOS2_6.ZIP   BOXER Text Editor for OS2!(Sysop Recommended)
BOXOS2_7.ZIP   BOXER Text Editor Ver.7A for OS/2.
I use the .6 version, have never bothered with the .7 version as I haven't 
registered it yet for the same reasons you list here:
 BA> I really hate to give up on Qedit/TSE-Pro, but I
 BA> m trying to convert to ALL 32-bit (NON-MS) apps, Heck, I
 BA> don't even have DOS 6.xx on my machine anymore. I'd really
 BA> like to have a native OS/2 "text" (80x25) editor (NOT
 BA> E.exe!) so I can do this:
I still have DOS support installed in OS/2 since my BBS is OPUS, but I rarely 
use any other DOS apps or utilities, including QEDIT and TSE.  I like TSE a 
great deal, but its not worth running DOS for.  I still use QEDIT for OS/2 
sometimes, but I guess it appears I might as well give up on Semware ever 
releasing TSE for OS/2.  Can't say I blame them, but can't say I don't 
question their not coming out with one long ago.  I've been using BOXER too 
long now not to register it anyway, so I guess I will if its still supported. 
 
The one I use has 1 bug and one nat in it that I can live with while not 
registered.  One is the undo you mention, it moves the curser to different 
lines when used, I think that was fixed in .7, and the other is a little more 
serious, which is if your are writing a REXX script with keyboard input, and 
shell out to test the script, BOXER doesn't read the correct shell or 
something, and never sees the input and just keeps on waiting.  The work 
around is to test the app in another session, which I don't mind doing 
anyway.  I would hope that would be fixed in newer versions, and would be 
something for semware to watch out for if they ever get around to TSE for 
OS/2.
C:\ > Edit "F:\Temorary download directory\readme.long-filename.txt"
 BA> Can't do that with TSE pro in a VDM :)
Boxer does.
 BA> Also, I think I remember you mentioning support for context
 BA> color coding (or something)  If I am not mistaken, doesn't
 BA> TSE for DOS offer that as well as proper indenting etc for
 BA> different programming languages? I don't particularly care
 BA> for stuff like that, but if I get back into programming, I
 BA> am betting it might be more of a help rather than the
 BA> distraction that I perceive it to be.  
Once you use it, you can't do without it.  Thats the primary reason I run 
BOXER now, rather than QEDIT for OS/2.  BOXER is a bit better than TSE in 
this area I think, but don't recall exactly why I think that.  My only gripe 
about TSE is it's for DOS.  Syntax highlighting is the ONLY way to go when 
programing, or even just editing a config file.  
 BA>  See my Win95 tagline. Bound to catch hell for that 
 BA> someday. hehe 
Not from me you won't:-)
                                              Jack 
--- timEd/2-B11
---------------