Hey all - when I try to run certain programs (frotz) under linux while connect via SyncTERM they crap out with an unknown term error.
I seem to recall that SyncTERM provided a TERMCAP or terminfo file or similar for Linux that could be used to help provide support.
Anybody have the directions handy on how to do that?
Re: SyncTERM TERMCAP/terminfo
By: Deepthaw to All on Sun Nov 01 2020 08:44 pm
Anybody have the directions handy on how to do that?
http://wiki.synchro.net/install:nix?#installing_the_terminfo_file
Re: SyncTERM TERMCAP/terminfo
By: Digital Man to Deepthaw on Sun Nov 01 2020 08:55 pm
Re: SyncTERM TERMCAP/terminfo
By: Deepthaw to All on Sun Nov 01 2020 08:44 pm
Anybody have the directions handy on how to do that?
http://wiki.synchro.net/install:nix?#installing_the_terminfo_file
Thank you!
Re: SyncTERM TERMCAP/terminfo
By: Deepthaw to Digital Man on Sun Nov 01 2020 09:54 pm
Sure. Let us know if it fixes the issue you were having.
Re: SyncTERM TERMCAP/terminfo
By: Digital Man to Deepthaw on Sun Nov 01 2020 09:58 pm
Re: SyncTERM TERMCAP/terminfo
By: Deepthaw to Digital Man on Sun Nov 01 2020 09:54 pm
Sure. Let us know if it fixes the issue you were having.
Sort of. I've been toying with MBSE (in addition to SBBS) and was toying around with running some linux terminal programs as external programs.
When I tried using frotz and a few others, it'd give an unknown terminal type syncterm error.
I was able to import the terminfo file, which added ansi-bbs to my Debian system but programs still gave the same problem.
What I've done is source a brief script that runs before known problem doors which contains:
#!/bin/bash
if [ $TERM = "syncterm" ]; then
export TERM=xterm
fi
and that's fixing it so far. I also notice that while ansi-bbs worked, frotz started to encounter issues when text scrolled up through the status bar at the top - but xterm's been a great workaround.
I'm not clear how your TERM environment variable is getting set to "syncterm" in the first place. In Synchronet, the term environment variable to use for external programs is set in sbbs.ini and by default it is "pc3" for ANSI terminals on Linux. So... is this something that MBSE is doing for you?
If you really want a SyncTERM terminfo entry, you can create one by running "syncterm -t" on Linux. But a more generic "ansi-bbs" compatible t
Re: SyncTERM TERMCAP/terminfo
By: Digital Man to Deepthaw on Sun Nov 01 2020 09:58 pm
Re: SyncTERM TERMCAP/terminfo
By: Deepthaw to Digital Man on Sun Nov 01 2020 09:54 pm
Sure. Let us know if it fixes the issue you were having.
Sort of. I've been toying with MBSE (in addition to SBBS) and was toying around with running some linux terminal programs as external programs.
When I tried using frotz and a few others, it'd give an unknown terminal type syncterm error.
I was able to import the terminfo file, which added ansi-bbs to my Debian system but programs still gave the same problem.
What I've done is source a brief script that runs before known problem doors which contains:
#!/bin/bash
if [ $TERM = "syncterm" ]; then
export TERM=xterm
fi
and that's fixing it so far. I also notice that while ansi-bbs worked, frotz started to encounter issues when text scrolled up through the status bar at the top - but xterm's been a great workaround.
---
??? Synchronet ??? Vertrauen ??? Home of Synchronet ??? [vert/cvs/bbs].synchro.net
Quoting Nelgin to Deepthaw <=-
Have you tried these in your sbbs.ini file?
ExternalTermDumb=dumb
ExternalTermANSI=ansi-bbs
Sysop: | Tandy |
---|---|
Location: | New York, USA |
Users: | 15 |
Nodes: | 13 (0 / 13) |
Uptime: | 01:12:57 |
Calls: | 335 |
Messages: | 113,798 |