1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • DDMsgReader: Fix for "go to message" in lightbar mode (correctly...

    From Craig Hendricks@1:103/705 to GitLab note in main/sbbs on Wed Feb 4 09:01:37 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/c26a0702f2b8ad9d09429ffba75be6da8c65dabc#note_8204

    Regarding the "Replaced arrow keys in the key help lines since some terminals can't display them" change, is this something that could be decided by the terminal type considering Synchronet has detection for ANSI & CP437? Or maybe configurable by the sysop?
    --- SBBSecho 3.36-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Eric Oulashin@1:103/705 to GitLab note in main/sbbs on Wed Feb 4 09:42:34 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/c26a0702f2b8ad9d09429ffba75be6da8c65dabc#note_8205

    @codefenix I'm not sure. Even if a terminal can display CP437, it might or might not display those characters as arrows. The problem is those characters are actually control characters, not CP437 characters - The up arrow is ASCII 24 (cancel) and the down arrow is ASCII 25 (end of medium). While SyncTerm displays those as arrow characters, other terminal software doesn't. I can't really think of a way to detect what terminal software the user is using (in order to display those or not).
    --- SBBSecho 3.36-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Thu Feb 5 15:01:20 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/c26a0702f2b8ad9d09429ffba75be6da8c65dabc#note_8210

    There probably is a way to auto-detect if the terminal can render those characters using ANSI cursor position request. If you send the character to the terminal while the cursor is in say x/y of 1,1 and then request the cursor position and the response says the cursor is still in 1,1, then you can assume the terminal can't/won't render that code value. Synchronet doesn't do any of this kind of autodetection today and we really just try to stay clear of sending characters that we aren't totally confident will be universally rendered (e.g. commit 6e9684ff2).
    --- SBBSecho 3.36-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)