https://gitlab.synchro.net/main/sbbs/-/commit/6135284f950b9bfc6ac3d58b
Modified Files:
src/sbbs3/con_out.cpp
Log Message:
The progress reports (e.g. "[ Done 100.0% ]") should never go to logs
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/4728536ae5fc6bd4de2e0907
Modified Files:
src/sbbs3/con_out.cpp
Log Message:
Fix off-by-one error in sbbs_t::cleartoeol() for non-ANSI terminals

This was evident by logging in with PETSCII/64col mode and the last ']' of the "Loading message pointers..." progress indicator was left in the first right column of the screen.
--- SBBSecho 3.23-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/a79988ca5e6919a7c2b15a74
Modified Files:
src/sbbs3/con_out.cpp
Log Message:
Propagate the non-auto user terminal dimensions to the runtime values, always

Previously, if either of the user terminal dimensions was set to a auto (0) then we wouldn't propagate the other specific (non-zero) value to the runtime console dimension. Usually a user will set either both values (cols and rows) to 0/auto or neither. So this isn't a oft-used configuration combo.
--- SBBSecho 3.23-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/c7fda9ff39acd9818cbc7f2f
Modified Files:
src/sbbs3/con_out.cpp
Log Message:
Remove broken security check for text.dat strings w/@-codes in bputs()

As Deuce pointed out, the text[] pointers are malloc()'d so they're not necessarily sequential/in-order addresses. Definitely not after
any text replacements have been made.
--- SBBSecho 3.23-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/b55f86216976f0e90d2e4b6d
Modified Files:
src/sbbs3/con_out.cpp
Log Message:
Fix test in last commit
--- SBBSecho 3.24-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/0fe2d71cc32d96ce83269f25
Modified Files:
src/sbbs3/con_out.cpp
Log Message:
Output multiple inverted question marks for > 1 width UNICODE characters

... for non-UTF8 terminals

This insures that the printed string length matches the output of
bstrlen(..., P_AUTO_UTF8)
on non-UTF8 terminals.

This should address the DDLightbarMenu issue described by Nightfox in merge request #569
--- SBBSecho 3.29-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: src/sbbs3/con_out.cpp
By: Rob Swindell (on Debian Linux) to Git commit to main/sbbs/master on Sat Sep 06 2025 07:00 pm

Modified Files:
src/sbbs3/con_out.cpp
Log Message:
Output multiple inverted question marks for > 1 width UNICODE characters

... for non-UTF8 terminals

This insures that the printed string length matches the output of bstrlen(..., P_AUTO_UTF8)
on non-UTF8 terminals.

This should address the DDLightbarMenu issue described by Nightfox in merge request #569

This helps, and things look good now. Thanks!

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/5fa5d6844af16b77bd320b77
Modified Files:
src/sbbs3/con_out.cpp
Log Message:
Display a trailing space after full-width UNICODE chars are printed as CP437

... if successfully converted to CP437 or not. This also means that full-width UNICODE chars that were previously (as of commit 0fe2d71cc32d96ce83269f25cdc) displayed as multiple upside-down question marks are now just displayed as a single upside-down question mark, followed by one or more spaces.

This fix is related to merge request (MR) !569 by Nightfox
--- SBBSecho 3.29-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/be4b8fe9756c70572bda8f8c
Modified Files:
src/sbbs3/con_out.cpp
Log Message:
Fix pausing in doors correctly.

The issue appears to have been that cp437_out() would call outchar()
for tabs. Since outchar is a higher level function, this would cause
weird stuff.

Just call term_out() and the problem is solved.
--- SBBSecho 3.30-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/ccd2d07571b185459ce51bf3
Modified Files:
src/sbbs3/con_out.cpp
Log Message:
Use nested if to help debugging (setting break-points)

No functional change.
--- SBBSecho 3.32-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/5227728dfd71cfe524ea5966
Modified Files:
src/sbbs3/con_out.cpp
Log Message:
Skip the UTF-8 BOM when auto-detected by auto_utf8()

I think this was the intention of this function always (hence why it returns
a char*).
--- SBBSecho 3.33-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/a9c51e9408ff05cdfc9c8918
Modified Files:
src/sbbs3/con_out.cpp
Log Message:
Add comment about curious legacy behavior when sending a FF via outchar()

Cosmetically, the blank line before the screen clear often looks good/best, except when it doesn't. But I'm pretty sure this was originally added to avoid a pause prompt being displayed near the right edge of the screen and possibly wrapping.
--- SBBSecho 3.34-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/15fde4bd32f361dd5a887f08
Modified Files:
src/sbbs3/con_out.cpp
Log Message:
Fix infinite loop in cp437_out() TAB expansion

cp437_out() expands TAB (0x09) by calling term_out(' ') in a loop,
polling term->column to determine when to stop. When the ANSI parser (parse_output) is mid-sequence — e.g. because binary data containing
ESC was passed through rputs()/console.write() — the space is consumed
by the parser without advancing term->column, causing an infinite loop
that sends spaces forever and pegs the CPU at 100%.

Prior to the Terminal class refactor (374282bf81), TAB expansion lived
in outchar() and used outcom(' ') with manual column++ tracking,
which was immune to ANSI parser state. The refactor moved it to
cp437_out() and switched to term_out(), introducing the dependency on parse_output() advancing the column.

Fix: compute the target column and space count upfront from the current
column and tabstop, then loop a fixed number of iterations regardless
of whether term->column actually advances. Also guard against
tabstop == 0 (would be division by zero in the original modulo check).

Found by ANSI fuzz testing (termtest.js) sending random byte streams
containing ESC followed by TAB.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/2686d621c9e2fa15e40dcd3b
Modified Files:
src/sbbs3/con_out.cpp
Log Message:
Add typecasts to address new GCC warnings
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)