Euphoria
Ticket #999:
8.3.5.11 free_console
-
Reported by
irv
Sep 23, 2019
WINDOWS:
Euphoria will create a console text window for your program the first time that your program prints something to the screen, reads something from the keyboard, or in some way needs a console. This window will automatically disappear when your program terminates, but you can call free_console to make it disappear sooner.
After freeing the console window, you can create a new console window by printing something to the screen, calling clear_screen, position, or any other routine that needs a console.
UNIX:
When running in pure text mode (no window manager), the text mode terminal is always there. Text output and keyboard input will appear there.
When running from an xterm, the terminal will remain open after your program ends, and a new prompt will be presented. Any text output or keyboard input will be seen on the xterm.
When running without an xterm, Euphoria will not open a text window, any printing to the screen will be sent to dev/NULL, and keyboard input will go directly to your Euphoria program.
Details
1. Comment by ChrisB
Nov 27, 2022
Not sure this is important enough to be fixed, awaiting the argument to the contrary
2. Comment by jimcbrown
Jan 25, 2023
This seems more like a feature request than a bug. On nix we don't really have the same concept of consoles or console applications, and the builtin xterm integration seems like a lot.
On most GNU/Linux desktop environments I've seen that there are options to run an application in a given xterm (whether the original xterm, urxvt, Konsole, or something else) and to even make that the default. E.g. to run /usr/bin/bc (a simple calculator). Since OE behaves like bc on the respective platforms, I think that's good enough.
GitHub