Subj : Re: screen & Mystic issues: UPDATE
To   : MeaTLoTioN
From : acn
Date : Sun Jun 27 2021 12:09:00

Am 27.06.21 schrieb MeaTLoTioN@1337:1/101 in TQW_LINUX:

Hallo Meatlotion,

M> Here's why;
M> without screen;
M>   $ echo $TERM
M>   xterm-256color
M> with screen;
M>   $ echo $TERM
M>   screen.xterm-256color

M> Possible solution (from inside screen);

M>   $ TERM=xterm-256color && ./mis server

M> Untested, but should work (maybe?)

I thought about something like this, too.

Considering your command:
I would prefer either
 $ export TERM=xterm-256color && ./mis server
or
 $ TERM=xterm-256color ./mis server

I don't know instantly if in your solution the variable will be kept for  
the part after &&, hence my "export" idea.
Without using &&, the TERM variable will be set for the ./mis process.

M> Don't use screen, use daemon instead, and learn using the log files to
M> your advantage, you get more info out of them.

Isn't there "nodespy" or something like this in Mystic which should give  
you some insight into your running BBS?

Regards,
Anna

--- OpenXP 5.0.50
 * Origin: Imzadi Box Point (1337:1/108.1)

.