[Info-vax] improving EDT

[Henry Crun]

On 16-Nov-2016 13:18, Phillip Helbig (undress to reply) wrote:
> EDT has the nice EDIT/RECOVER feature.  This is good when there is some
> unexpected problem.
>
> I have also defined a key to write a new version of the current file to
> disk, so that I don't have to leave the editor.  This is good when
> writing source code, saving it, compiling the new version, without
> leaving the editor.  It also protects against making some major change
> by mistake; probably, a previous version can be retrieved and used as
> the basis for a new version without the mistake.
>
> What about the two together?  If I use the last feature, and there is an
> unexpected crash, the journal file can't be applied to the highest
> version of the edited file.  If I apply it to the version of the file it
> was created with, should this work in all cases, i.e. EDIT/RECOVER in
> this case would give the same result as the current state of the highest
> version of the file?  (Obviously, if I make a big mistake and go back to
> a previous version for a fresh start, I will leave the editor and the
> journal file will be deleted.)
>

 From my experience, everything (and lots more) that can be done with EDT can be 
done in TPU.
E.g. I use TPU for text eding in 8-bit Hebrew (entering text right-to-left, the 
Learn function has no convenient equivalent in EDT, Spawn, etc. etc.

To use in an Edit/Compile/Test cycle you could try LSE (also based on EVE) which 
has many language-specific constructs (though IIRC it costs...)

-- 
Mike R.
Home: http://alpha.mike-r.com/
QOTD: http://alpha.mike-r.com/qotd.php
No Micro$oft products were used in the URLs above, or in preparing this message.
Recommended reading: http://www.catb.org/~esr/faqs/smart-questions.html#before
                 and: http://alpha.mike-r.com/jargon/T/top-post.html
Missile address: N31.7624/E34.9691