From: dxforth@gmail.com   
      
   On 29/11/2025 10:17 pm, albert@spenarnc.xs4all.nl wrote:   
   > In article <692a35e1$1@news.ausics.net>, dxf   wrote:   
   >> ...   
   >> I've updated SED.TXT in the DX-Forth distribution to read:   
   >>   
   >> Ctrl-K   Update all changes made to the current screen.  Note:   
   >>         This must be done before moving to another screen or   
   >>         exiting the editor else the changes will be lost.   
   >   
   > The tradition with screens was that you keep screens in cache,   
   > because writing all the time was too expensive.   
   > If you handle too much at once, the oldest screen was written to   
   > disk. My MSDOS editor copies a screen to video memory, and   
   > after finishing I do an UPDATE from the screen, marking it as to-be-written.   
   > (another screen is about to be copied to video memory)   
   >   
   > With fast disk mass storage you can implement UPDATE as write   
   > immediately. FLUSH then becomes the same as EMPTY-BUFFERS.   
      
   My intention was to use blocks only for forth source files, so   
   everything was kept rudimentary.   
      
   > So I don't think ^K is sensible. It is too easy to forget.   
   > Instead have e.g. ESCAPE-Q that abandons the edits and ESCAPE-X to   
   > normal exit.   
      
   Using ESC would be more complicated than CTRL.  Besides the CTRL keys   
   are all muscle memory now and I barely need to think what keys I'm   
   pressing.   
      
   On that last point I now see what Eric was getting at.  CTRL-U (exit)   
   offers up (S)ave or (Q)uit.  The implication being S saves the changes.   
   I had become so used to doing CTRL-K that I never noticed (S) doesn't   
   actually save.  I'll need to look into this further...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)