XPost: comp.os.cpm   
      
   In article <692a35e1$1@news.ausics.net>, dxf   wrote:   
   >On 29/11/2025 1:16 am, ECNeilson wrote:   
   >> On Nov 27, 2025 at 11:55:55 PM CST, "dxf"  wrote:   
   >> ...   
   >>>> Is anyone else having problems saving .scr files using the built-in SED   
   >>>> editor?   
   >>>>   
   >>>> Steps to reproduce:   
   >>>> 1. USING HELLO  -> Successfully creates HELLO.SCR   
   >>>> 2. 0 SED  -> Goes to SED editor   
   >>>> 3. Type in some code and hit CTRL-U to save   
   >>>> 4. Back to Forth interactive prompt with "ok"   
   >>>> 5. 0 LIST  ->  Nothing you typed was saved.  Everything is blank.   
   >>>>   
   >>>> This seems to occur on every version of DX-FORTH I've tried, both   
   >CP/M and DOS   
   >>>> versions. Am I doing something wrong?   
   >>>>   
   >>>> Eric N.   
   >>>   
   >>>   
   >>> CTRL-U only exits the editor (you don't want to save any changes)   
   >>>   
   >>> From SED.TXT:   
   >>>   
   >>>   Ctrl-K   Update all changes made to the screen   
   >>>   
   >>> So the procedure is CTRL-K CTRL-U to Save and Exit.  Perhaps there should   
   be   
   >>> a single command ... but it's never occurred to me in over 30 years and I   
   use   
   >>> screens exclusively.   
   >>   
   >> Holy cow! Thank you! That did the trick. I'm old hat with CP/M and software   
   >> development but brand new to FORTH, and DX-FORTH. I couldn't find any   
   >> documentation on using CTRL-K prior to CTRL-U.   
   >>   
   >> You've made my day, and perhaps someone else will find this thread useful   
   one   
   >> day.   
   >   
   >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.   
      
   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.   
      
   UPDATE FLUSH EMPTY-BUFFERS are ISO words.   
      
   >   
   >Thanks for the report.  Writing docs for raw beginners can be a challenge and   
   >feedback like this helps.   
   >   
      
   Groetjes Albert   
   --   
   The Chinese government is satisfied with its military superiority over USA.   
   The next 5 year plan has as primary goal to advance life expectancy   
   over 80 years, like Western Europe.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)