Logging output of a BLISS terminal session
In BLISS I am missing a way of logging sequentially output of a BLISS terminal session to daily changing log files. BLISS terminal outputs disappear when the terminal output buffer is filled or when the session is closed. In SPEC it helps writing the terminal output to a file by using the commands on(logfilename), off(logfilename) and close(logfilename). There, the logfile name is updated with the current date stamp during each resetup. A too verbose output is avoided by not logging movement updates and/or only logging the LAST of identical lines.
Text log files have practical advantages. They facilitate remote support during an experiment
a) by using a terminal with low bandwidth and b) viewing in read-only mode the current terminal output, e.g. by using tail -f .
At this point no graphical interface is needed like GUACAMOLE or VNC.
After the experiment the log files are useful for debugging.
The logfile should contain all output that is sent to the user terminal (stdout, probably even stderr). Ideally, it should have (some) timestamps for searching, either on each line or, at least, from time to time. It would be possible independently by writing a timestamp after each prompt. Long user macros should write timestamps themselves.
It is not necessary and even not desirable visualizing graphical output. This could be done independently, e.g. with flint, running in parallel (!) in a graphical terminal, with pymca or whatever.