Groups | Search | Server Info | Login | Register


Groups > comp.lang.forth > #134439

Re: ANN: DX-Forth 4.62

Date 2025-11-30 02:25 +1100
Subject Re: ANN: DX-Forth 4.62
Newsgroups comp.lang.forth
References <68dccfaa$1@news.ausics.net> <6929396b$1@news.ausics.net> <10gcas3$2fjih$1@dont-email.me> <692a35e1$1@news.ausics.net> <nnd$468d8292$6f4237e5@4bd21ec83a4edaf9>
From dxf <dxforth@gmail.com>
Message-ID <692b1057@news.ausics.net> (permalink)
Organization Ausics - https://newsgroups.ausics.net

Show all headers | View raw


On 29/11/2025 10:17 pm, albert@spenarnc.xs4all.nl wrote:
> In article <692a35e1$1@news.ausics.net>, dxf  <dxforth@gmail.com> 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...

Back to comp.lang.forth | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

ANN: DX-Forth 4.62 dxf <dxforth@gmail.com> - 2025-10-01 16:52 +1000
  Re: ANN: DX-Forth 4.62 John <john@somewhere> - 2025-10-01 06:58 -0500
    Re: ANN: DX-Forth 4.62 Hans Bezemer <the.beez.speaks@gmail.com> - 2025-10-01 17:13 +0200
      Re: ANN: DX-Forth 4.62 ECNeilson <eric@neilsonhart.com> - 2025-11-28 04:09 +0000
        Re: ANN: DX-Forth 4.62 dxf <dxforth@gmail.com> - 2025-11-28 16:55 +1100
          Re: ANN: DX-Forth 4.62 ECNeilson <eric@neilsonhart.com> - 2025-11-28 14:16 +0000
            Re: ANN: DX-Forth 4.62 dxf <dxforth@gmail.com> - 2025-11-29 10:53 +1100
              Re: ANN: DX-Forth 4.62 albert@spenarnc.xs4all.nl - 2025-11-29 12:17 +0100
                Re: ANN: DX-Forth 4.62 dxf <dxforth@gmail.com> - 2025-11-30 02:25 +1100
                ANN: DX-Forth 4.63 dxf <dxforth@gmail.com> - 2025-11-30 12:49 +1100

csiph-web