Backtrace:11;rgb:2323/2626/2727<<<
I like to have gforth start up and run in a window when I log into my
Debian Linux PC. I just put the path to gforth in the KDE Plasma GUI
startup menu and tell it to run in a terminal. Seemed to work fine with
the old 0.7.3 gforth. I recently changed to the latest gforth and most
often (but not always) got wacky output like:
Gforth 0.7.9_20220428
Authors: Anton Ertl, Bernd Paysan, Jens Wilke et al., ...
Copyright © 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later ...
Gforth comes with ABSOLUTELY NO WARRANTY; for details type `license'
Type `help' for basic help
11;rgb:2323/2626/2727
*the terminal*:1:1: error: Undefined word
Backtrace:11;rgb:2323/2626/2727<<<
kernel/int.fs:321:10: 0 $7FBDED6A9430 throw
ok
Changing the startup call from
/usr/bin/gforth
to
/usr/bin/sleep 5 && /usr/bin/gforth
seems to resolve the issue, so it looks like the new gforth is too fast,
or is something else going on?
My guess is that the initialization of the terminal is not complete
when the status line is printed, leading to some hickup in the ANSI
escape sequence processing.
You can test this theory by turning the startup call into
/usr/bin/gforth -e "' noop is status"
This turns off the status line. If you still have the same problem,
the theory is wrong. If the problem is gone, you have an alternative workaround.
*the terminal*:-1:11: error: Undefined word
' noop is >>>status<<<
buzz_mccool <buzz_mccool@yahoo.com> writes:
*the terminal*:-1:11: error: Undefined word
' noop is >>>status<<<
Sorry, my mistake. It should be
/usr/bin/gforth -e "' noop is .status"
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 51:39:14 |
Calls: | 6,712 |
Calls today: | 5 |
Files: | 12,243 |
Messages: | 5,355,038 |
Posted today: | 1 |