From Newsgroup: comp.lang.forth

DX-Forth is a Forth language compiler and development system
for MS-DOS and CP/M-80 operating systems. It is intended to
be a complete, easy to use, programming tool for the creation
of turnkey applications.

What's new:

+ added - removed * fixed ! changed = updated

v4.62 2025-10-01

+ CPMEOF
! Buffer requirements for READ-LINE
! Revert to original f/p output functions
= Documentation updates
= Filesys: SFILE BFILE QFILE
= NEWAPP: interactive testing enhancements

Downloads:

DXCPM462.ZIP (CP/M-80)
DXDOS462.ZIP (MS-DOS)

https://drive.google.com/drive/folders/1kh2WcPUc3hQpLcz7TQ-YQiowrozvxfGw

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

Thanks, appreciate the work!
-J
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

Congratulations!
BTW, I'm close behind ;-)

Hans Bezemer
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

On Oct 1, 2025 at 9:13:00 AM CDT, "Hans Bezemer" <the.beez.speaks@gmail.com> wrote:

Congratulations!
BTW, I'm close behind ;-)

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.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

On 28/11/2025 3:09 pm, ECNeilson wrote:

On Oct 1, 2025 at 9:13:00 AM CDT, "Hans Bezemer" <the.beez.speaks@gmail.com>
wrote:

Congratulations!
BTW, I'm close behind ;-)

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.


--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

On Nov 27, 2025 at 11:55:55 PM CST, "dxf" <dxforth@gmail.com> wrote:

On 28/11/2025 3:09 pm, ECNeilson wrote:

On Oct 1, 2025 at 9:13:00 AM CDT, "Hans Bezemer" <the.beez.speaks@gmail.com>
wrote:

Congratulations!
BTW, I'm close behind ;-)

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.

Eric N.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

On 29/11/2025 1:16 am, ECNeilson wrote:

On Nov 27, 2025 at 11:55:55 PM CST, "dxf" <dxforth@gmail.com> 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.

Thanks for the report. Writing docs for raw beginners can be a challenge and feedback like this helps.

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

In article <692a35e1$1@news.ausics.net>, dxf <dxforth@gmail.com> wrote:

On 29/11/2025 1:16 am, ECNeilson wrote:

On Nov 27, 2025 at 11:55:55 PM CST, "dxf" <dxforth@gmail.com> 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.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

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...

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.lang.forth

On 30/11/2025 2:25 am, dxf wrote:

..
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...

I've corrected the screen editor CTRL-U (S)ave function such that it
properly updates the current screen and flushes to disk. See entries
Ctrl-K Ctrl-U in SED.TXT for further details.

Download:

DXCPM463.ZIP (CP/M-80)
DXDOS463.ZIP (MS-DOS)

https://drive.google.com/drive/folders/1kh2WcPUc3hQpLcz7TQ-YQiowrozvxfGw

Cross-posted to comp.lang.forth and comp.os.cpm

--- Synchronet 3.21a-Linux NewsLink 1.2