The ansi protocols seem to not work well on Linux, compared to Xterm. I'm wondering if I am missing a font, or setting are incorrect. Also it crashes when trying to do font management.
Reading symbols from ./syncterm...
(gdb) run
Starting program: /home/lumni/syncterm
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff796f640 (LWP 4103)]
[Thread 0x7ffff796f640 (LWP 4103) exited]
[New Thread 0x7ffff7fbb640 (LWP 4104)]
[New Thread 0x7ffff6e60640 (LWP 4105)]
[New Thread 0x7ffff7f95640 (LWP 4106)]
[New Thread 0x7ffff60b7640 (LWP 4107)]
Thread 1 "syncterm" received signal SIGSEGV, Segmentation fault.
truncspctrl (str=0x628eca " ") at uifc32.c:625
/usr/lib64/python3.9/site-packages/pygments/plugin.py:45: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
import pkg_resources
625 str[c] = 0;
I've tried different switches to fix the ansi problem. It makes them worse
Anonymous
A few things I notice here:
It sounds like you turned off CP437 support in your BBS user account.
I'm sorry. It is X11. And it is on every BBS I go to. When I try to go to font management and do an insert, it crashes.
That did it with the ansi part.
When you do an insert, are you leaving the name blank and pressing enter? Where exactly does it crash? Are you connected to a BBS when you're doing it?
I may have fixed the bug, but I still don't have a clear understand of what's happening, so I can't debug it. You can download the latest build from http://syncterm.bbsdev.net/ and try it out.
I'll download it tomorrow. Anything I enter into the font config causes it to crash.
Moving to pending... will likely end up timing out. :(