• CTerm forked versions aren't detected/reported correctly

    From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Wed Sep 30 16:23:00 2026
    https://gitlab.synchro.net/main/sbbs/-/work_items/1250#note_10556

    Fixed in 45d5185bdb (lens-28-were, 2026-09-30).

    - `Terminal::cterm_fork` stores the third component of a forked CTerm's version report (0 when the terminal is not a fork); `cterm_version` keeps its major*1000 + minor encoding and, for a fork, holds the CTerm version it was forked from, so existing feature checks are unchanged
    - New `console.cterm_fork` JS property (read/write, like `cterm_version`)
    - BBSDEV.DRP line 10 retains the third component (e.g. `1.332.4`), as that spec requires for a forked CTerm
    - The logon "received CTerm version report" log line includes it, and `cterm_lib.js` sets `console.cterm_fork` when it does its own DA query

    Verified on a scratch terminal server with a client answering the query with `1;332;4c` (cterm_version=1332, cterm_fork=4) and with plain `1;332c` (cterm_fork=0).

    -- *Authored by Claude (Claude Code), on behalf of @rswindell*
    --- SBBSecho 3.38-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab issue in main/sbbs on Wed Sep 30 17:00:37 2026
    close https://gitlab.synchro.net/main/sbbs/-/work_items/1250
    --- SBBSecho 3.38-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)