Hi Jorj:
I think we can probably agree that TSE is a great editor.
And I think wan can probably agree to disagree on the relative value of
paper documentation:  What is very important to me (online help), is of
less value to you than the hardcopy.  Each of us uses the editor in
different ways that contribute to this difference.   I'm sure SemWare
will take your input into consideration in their next release.
JS> Options.  Many places give you the option of buying a printed
JS> manual, or printing your own copy from an on-disk one they ship,
JS> along with the program and its online help.  Since the manual
JS> is 90% or more the same as the online help, it's not like it
JS> requires a huge separate investment to do.
Hmm.  I think this is a good idea, and probably not very hard to do.
JS>MC> Persistent History is absolutely wonderful.
JS> Annoying clutter, I found it, so turned it off.
Once again, reasonable men can agree to disagree reasonably.
JS> I am not so self-abusive as to do anything under Windows that I
JS> can possibly avoid doing.
Actually, I've found a good role for Windows:  It task switches my
DOS tasks quite well (and also provides the platform for solving one
of the needs you have for paper docs:  I frequently have several copies
of TSE running in different windows, so debugging a macro in one while
looking at help in another is much more effective for me than fumbling
with paper.)  In addition, the character generation available with
graphical environments for DOS VDM's is so vastly superior that I much
prefer running my DOS apps under windows:  There I get a very readable
80 x 50 display in a window that leaves plenty of room to manage other
windows.
JS>MC> The source level macro debugger is an
JS>  > accomplishment which simply floors me.
JS> Tried it a couple of times.  Complex beyond understanding.
JS> Maybe someday it will be useful to me, but I doubt it.
Debugging can sometimes be complex.  Since I've specialized in system
level debugging on more systems than I can count (on one hand ), I
suppose its possible that what seems intuitively obvious may not be so.
The SAL macro debugger has enough commonality with the debuggers built
into most Borland languages and with Turbo Debugger, that using it
was like meeting an old friend.  Trust me on this one:  If you write
macros, the debugger will help you.  It's worth taking the time to
learn.
JS>MC> Instant online access to any word contained in the help system.
JS> Making the help searchable was a noted improvement.  It's the
JS> biggest plus of online help over manuals.  At least now I'm no
JS> longer penalized for remembering seeing something in the help,
JS> but not recalling what keyword it was tucked away under.
Whew! Glad we can agree on something!
Paper documentation is obviously very important to you -- much more
so than it is to me.  (To be honest, I haven't seen my TSE manuals in
six months -- about the time Semware released searchable help in beta:
The help system can find the topic I want faster than I can find the
books! )
I do think that your idea of being able to print the docs is a good
one.  Be aware, though, that printing the online would take about 650
pages.  Even with my TSEBOOK macro, this is a lot of paper.
Good luck.
Mike.
---
 þ SLMR 2.1a þ For every vision, there is an equal and opposite revision
--- FidoPCB v1.4 [ff151/a]
---------------