• docs/v322_new.md exec/loa

    From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Sun Jun 7 18:41:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/6033e9d61dad951da5d36309
    Modified Files:
    docs/v322_new.md exec/load/binkp.js
    Log Message:
    BinkIT: don't record successful binkp/1.1 callouts as failures

    The JSBinkP session loop only breaks out on *receiving* a final M_EOB,
    but in binkp/1.1's two-M_EOB handshake the completed state is usually
    reached by *sending* the last EOB. After sending it, the peer closes
    the connection, and the next loop iteration attempts one more M_EOB on
    the now-closed socket; that send fails and (since b795cf6a3d) marked the
    whole session as failed -- even though all files had already been sent
    and acknowledged. binkit.js then wrote "[callout failure]" to data/binkstats.ini with the sent file(s) listed.

    binkp/1.0 peers (Mystic, mbcico) exchange a single M_EOB each and break immediately on receipt, so they were recorded correctly; the bug hit
    binkp/1.1 peers (Synchronet/BinkIT, binkd) -- the vast majority of
    sessions -- producing huge "failed_callouts" counts despite mail
    flowing fine. Reported in DOVE-Net's sync_sysops by Khronos and Gamgee.

    Fix: a failed closing M_EOB send is benign once our sent files have all
    been acknowledged (pending_ack empty); break the loop without failing
    the session in that case. Only fail when files remain unacknowledged.
    The on-wire behavior is unchanged. Bumped JSBinkP revision to 6 so the
    fix is identifiable via the vers= field in binkstats.ini.

    Validated with a two-process TCP loopback harness: binkp/1.1 callout
    flips from false to true (file transferred either way); binkp/1.0 and
    no-files polls unchanged; a peer that drops mid-transfer still fails.

    Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Fri Jun 26 01:24:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/c00526fb8f7f91aa16e28eee
    Modified Files:
    docs/v322_new.md exec/load/salib.js exec/spamc.js
    Log Message:
    spamc.js/salib.js: let SpamAssassin see the originating relay IP

    Enable the synthetic Received-header injection (set msg.hello_name from
    the mailproc hello_name global) so spamd can identify the connecting
    client and run sender-IP DNSBLs (Spamhaus, etc.) and SPF -- previously
    every message scored with NO_RELAYS/NO_RECEIVED, neutering those checks.

    Strip the synthetic Received from the re-written message so the stored
    mail doesn't duplicate the Received the mail server adds at delivery
    (the duplicate that caused this to be disabled in f886a41 / only-3-strip). Strip it on its own: SA consumes the injected Return-Path, so a combined
    match never hit.

    Validated live: NO_RELAYS/NO_RECEIVED gone, SPF_PASS + RCVD_IN_* now
    firing, stored messages carry exactly one Received header.

    Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
    (cherry picked from commit 567c45486b2cb958d70a2fabe2bd9f29e2c8ade0)

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sat Aug 1 01:20:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/63844fa110647fc2660da61b
    Modified Files:
    docs/v322_new.md exec/load/ircd/core.js unregistered.js
    Log Message:
    ircd: serialize manual CONNECT, and stop answering ERROR with a numeric

    IRCClient_do_connect() declined to start when Outbound_Connect_in_Progress
    was set but never set it itself, so for the duration of an operator's
    /CONNECT the flag stayed clear and a scheduled Automatic_Server_Connect()
    could dial a second server concurrently -- the case 0b4056bbcf (2024-06-19) added the flag to prevent. It also meant every manual /CONNECT logged "Outbound connection while !Outbound_Connect_in_Progress" when the socket callback found the flag already false.

    Unregistered_Commands() had no case for ERROR, so a server refusing our handshake -- which reports why with ERROR just before dropping the link --
    was answered with 461 "You have not registered", and the reason went no
    further than the raw protocol log. Log it and notify routing opers
    instead. Outbound links are named by their configured server name, since
    an unregistered client's hostname defaults to the socket's peer address,
    which is not yet resolvable at that point in the connect callback.

    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Fri Sep 18 23:15:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/45e2c6c9e5b64ac90f4b2728
    Modified Files:
    docs/v322_new.md exec/load/sbbsdefs.js src/sbbs3/logon.cpp newuser.cpp sbbsdefs.h src/sbbs3/scfg/scfg.c scfg.h scfgindex.h scfgnode.c scfgxtrn.c src/sbbs3/xtrn_sec.cpp
    Log Message:
    Add a "clear screen before execution" option for external programs

    Some external programs clear or overwrite the user's terminal as soon as
    they start. Run from a logon event, such a program can wipe text the user
    has not yet read. The new XTRN_CLS online program option clears the
    screen before the program is executed, using the BBS's own clear-screen
    (cls), which first prompts the user to continue if there is unread
    output on the screen. GitLab #1243.

    The screen is cleared once the program is sure to run (all early-return
    checks done) and before the drop file is written and the node status,
    start time, inactivity timeout, and MQTT exec event are set, so a long
    pause at the prompt affects none of them.

    Logon and New User fixed events get the same option (FEVENT_CLS), along
    with a pause-after-execution option (FEVENT_PAUSE). A fixed event's
    settings are external() mode bits, so these use bits that external()
    ignores. The other fixed events run offline and don't offer them.

    In SCFG, the online program "Pause After Execution" option becomes
    "Terminal Control" (None, Clear, Pause, or "Clear, Pause"), which prompts
    for both settings; ESC at the first prompt skips the second. The Logon
    and New User fixed event menus offer the same option. toggle_flag() now
    returns the list selection so a caller can detect an abort. The fixed
    event copy of the option is kept out of the search index, which cannot
    tell which fixed events offer it.

    scfgindex.h is regenerated, which also picks up the Msg/File Total
    Interval option added in 875357a01a (2026-08-17).

    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sun Sep 20 12:07:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/5de72e09952321c0bfffb38d
    Modified Files:
    docs/v322_new.md exec/load/filecontents_lib.js src/sbbs3/filedat.c ftpsrvr.cpp js_system.cpp mailsrvr.cpp sbbsecho.c services.cpp src/xpdev/genwrap.c genwrap.h
    Log Message:
    Run external commands without flashing a console window on Windows

    C's system() runs its command through cmd.exe, and when the calling
    process has no console of its own -- a Windows service, sbbsctrl.exe, or anything spawned by them -- cmd.exe allocates one, flashing a window onto
    the sysop's desktop. The web server made this obvious: every archive a
    web client peeks into with ?view= runs lsar.

    New in xpdev:

    xp_system() - system(), except that a console-less process spawns
    %COMSPEC% /S /C "..." with CREATE_NO_WINDOW instead. A caller that does
    have a console still goes through system(), so console output is
    unchanged there. Standard handles and handle inheritance are passed
    along as system() does (services.cpp hands a native service its socket
    that way).

    xp_popen() - popen(cmd, "r"), read to EOF, with the captured lines
    appended to a str_list_t. On Windows it builds the pipe with
    CreateProcess() rather than _popen(), which requires the calling process
    to have a console and so has never worked inside a server.

    system.popen() consequently works on Windows now and is no longer
    documented as UNIX-only, and system.exec() no longer flashes a window.
    Given the same treatment: the mail server's external mail processors, the Services' native services, SBBSecho's external programs, and the file-extraction command run for DIZ files. FTP's SITE EXEC loses its
    #ifdef and returns the command's output to the client on Windows too.

    filecontents_lib.js drops the temp-file redirect it was using to keep
    lsar off system.popen() (043587351c9) and captures the output directly.

    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sun Sep 20 12:43:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/9e9b6659281839c23872e22c
    Modified Files:
    docs/v322_new.md exec/load/filecontents_lib.js exec/webfileindex.ssjs Log Message:
    View self-extracting .exe archives in the web file index

    libarchive already reads the Zip or 7-Zip payload inside an SFX stub --
    it locates the archive's signature rather than insisting the file start
    with one -- so nothing but an extension gate stood in the way. Verified against both a 7-Zip SFX and an .exe with a Zip appended; a plain
    program still fails to extract and is stored as the negative verdict it
    is.

    webfileindex.ssjs kept its own list of archive extensions, a shorter one
    than the library's, so 'arj', 'zoo', 'tar', 'gz' and 'bz2' were listable
    but never offered. It now asks contents.is_archive(), leaving one list
    to maintain, and 'exe' is added to it.

    extract_external(): an empty lsarContents with a non-zero lsarError is a failure rather than an empty archive. lsar recognizes a self-extracting
    Zip whose stub offsets it won't follow and says exactly that; storing it
    as a zero-entry listing misreported the file (043587351c9).

    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Mon Sep 21 22:21:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/c265ffd0d3b4c794510c39b5
    Modified Files:
    docs/v322_new.md exec/load/822header.js newsutil.js src/smblib/smbtxt.c Log Message:
    Don't claim RFC-3676 format=flowed for message text that isn't

    newsutil.js (NNTP) and 822header.js (IMAP) synthesize a Content-Type
    header field for a message that has none stored, and asserted
    format=flowed whenever MSG_FIXED_FORMAT was clear. That flag is only
    ever set by an explicit "fixed" - a MIME format= parameter, a QWK
    "Format = fixed" header, an FTN \1FORMAT: kludge, or a local post made
    in raw-input mode - so a message that simply never said anything was
    reported as flowed.

    An omitted format parameter already means fixed (RFC 3676 4.1), so omit
    it rather than assert a wire format the text does not use: Synchronet
    message text is hard-wrapped and carries no trailing space on a soft
    break, and a conforming flowed reader also space-stuffs each line and
    reflows leading '>' quote blocks. The synthesized field is only
    generated when no Content-Type was stored, so a message that did arrive
    flowed keeps its own header field verbatim and is unaffected.

    Reported on DOVE-Net by ant: messages relayed over QWK with MIME
    excluded were served by NNTP as "charset=IBM437; format=flowed" with no trailing spaces anywhere in the body.

    mime_getpart() extracted the selected part's charset but passed NULL for auxattr, so only a single-part message's format= parameter could reach MSG_FIXED_FORMAT. Thread it through, so that - together with the
    preceding ";format=" typo fix in smb_parse_content_type() - a multi-part message whose text part declares format=fixed now round-trips.

    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Wed Sep 30 19:08:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/9c59990042def81b2d6beb76
    Modified Files:
    docs/v322_new.md exec/load/sbbsdefs.js exec/msglist.js src/doors/termgfx/CMakeLists.txt audio_mgr.c src/sbbs3/getmsg.cpp putmsg.cpp sbbsdefs.h
    Log Message:
    Strip terminal commands (APC strings) from displayed message text

    Fixes #1254

    putmsg() strips a fixed list of terminal *queries* from everything it
    displays (so a reply never lands in the user's input), but passed every state-changing sequence through, and made no distinction between a sysop's display file and a message body. SyncTERM's C;S (store file) APC in a
    message therefore wrote a file into the SyncTERM cache of everyone who read
    it, persistently, under any name the poster chose.

    Add a P_NOAPC mode (and the matching sbbsdefs.js constant) under which
    putmsg() strips every APC string (ESC _ ... ESC \), and set it where
    message text is shown: show_msg() for the sub-board and mail readers, and
    the msglist.js lightbar reader. Display files keep full pass-through, since sysops embed fonts and images in them.

    The one shipped consumer that trusted a cached file by name alone,
    termgfx's door audio manager, now plays a client-cached track only when
    the MD5 the C;L listing reports for it matches the door's own copy, as syncterm_cache.js and the zmachine already require; without a door-side
    copy to check against, the client's file is not trusted and the track is uploaded as before. md5.c joins fnv1a.c as a hash-lib source compiled
    straight into termgfx.

    Verified on a scratch terminal server with a post and a mail carrying a
    C;S APC followed by a colored line: both readers show the text, the C++
    reader keeps the SGR color code, and neither emits the APC. Every termgfx
    door rebuilds.

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sun Oct 25 13:37:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/3109381166a8f58a85d97ab2
    Modified Files:
    docs/v322_new.md exec/load/ircd/core.js src/sbbs3/js_console.cpp js_internal.cpp js_socket.cpp js_socket.h sbbs.h
    Log Message:
    js: report asynchronous connect failures and keep callbacks alive

    Socket.connect() with a callback ran the resolve and connect on a thread
    and sent the result over a socket pair that the callback engine never
    read: it set is_connected the moment the thread started and invoked the callback regardless. A refused connect, or a hostname that did not
    resolve (that path sent nothing at all), reached the callback looking
    connected with no peer address. The IRC daemon then sent its server
    handshake into dead links to unreachable hubs and, since outbound
    connects are serialized, delayed its reconnect to a reachable one.

    The thread now reports {error, gai} on every path and the engine reads it before the callback, setting is_connected, error and error_str. The
    socket is not marked connected while the connect is pending.

    Every stored event callback (js.setTimeout/setInterval/setImmediate/ addEventListener, Socket.on/once/connect, console.on/once) was a bare JSFunction* with no GC root, and JS_ValueToFunction() returns the shared function behind a closure, dropping its scope. A callback that captured
    a variable crashed in the interpreter when invoked. Store and root the
    function object that was passed, and call it with JS_CallFunctionValue().

    Windows select() was given a negative timeval when no timer was pending
    and empty descriptor sets when only timers were pending, so connect-only scripts exited with "Timeout with no event" and timer-only scripts with
    "poll() returned with error 22". Pass NULL for an infinite wait and sleep
    when there is nothing to select on.

    All three date from the callback engine's introduction in 1928973941 (2021-04-02) and 06ec7d4148 (2021-04-13). The ircd's connect-failure
    notice now includes the error text.

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sat Oct 31 15:29:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/e79b7e95b76d02e5eb516ef0
    Modified Files:
    docs/v322_new.md exec/load/dorkit.js src/sbbs3/exec.cpp xtrn/gttrivia/gttrivia.js
    Log Message:
    Scope a script's js.auto_terminate/terminate_on_disconnect change to itself

    sbbs_t::js_callback is one struct per node, shared by every script that js_execfile() runs during the session. dorkit.js (since 5a4e103ff3d, and terminate_on_disconnect since fc82a6d9116) clears both flags at load and
    only sets them again in its own disconnect-timeout path, so after a normal
    exit from a dorkit door (e.g. LORD) every later script on the node ran with
    the disconnect abort and the recycle abort disabled.

    Seen on vert: a caller played LORD, then Good Time Trivia, then dropped the connection. The node stayed "in use" for 20+ hours, its thread rereading
    the trivia question files in a loop, ignoring the disconnect; only the JavaScriptTimeLimit counter would eventually have ended it.

    - js_execfile() saves the two flags before executing a script and restores
    them afterward, so a script's change can't leak into the next one.
    - dorkit.js restores the caller's values via js.on_exit() as well.
    - gttrivia.js: console.getkeys() returns a number (not a string) on abort
    or when the caller is offline; doMainMenu() converted that to "0" and
    fell through to its ACTION_PLAY default forever. Treat a non-string or
    empty result, or an offline caller, as Quit.

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Wed Nov 11 22:14:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/1a255ae94520c1632ef0acd7
    Modified Files:
    docs/v322_new.md exec/load/msgutils.js
    Log Message:
    msgutils.js: getMessageThreads(sub, max) reads the newest max messages

    With a non-zero max, getMessageThreads() looked up every number from
    last_msg - max to last_msg. get_msg_header() returns null for a missing
    or deleted number, and the loop then threw "TypeError: header is null".
    When it didn't throw, it stored each header under header.num, which is not
    a header property, so every header landed under the key "undefined" and
    only the last one survived: a limit of 100 returned one message. On
    sparsely numbered subs the number window also held fewer than max
    messages.

    Take the newest max index records that are neither deleted nor votes,
    and read those headers by offset. Callers that pass no limit (ecReader by default) still read every header with get_all_msg_headers().

    Part of #1340.

    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sat Nov 14 17:08:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/4e0745220bebd5438c87dd71
    Modified Files:
    docs/v322_new.md exec/load/menubar.js src/sbbs3/js_console.cpp putmsg.cpp terminal.cpp terminal.h
    Log Message:
    @BARATTR: optional second attribute, for a lightbar's command key

    @BARATTR:<attr>:<key-attr>@ names, after the selected-item attribute, a foreground color for the command key of each lightbar item, so that a
    menu whose items are whole words in one color (which makes the entire
    word, first letter included, one selectable and clickable region) can
    still show which letter is the key. @BARATTR::<key-attr>@ sets the key
    color alone.

    As with the selected-item attribute, the Terminal Server only records
    the value, exposed to JavaScript as console.bar_hot_attr; menubar.js
    does the drawing. It redisplays each unselected item with the first
    occurrence of its command in the key color, over the item's own
    background, when the menu is first displayed and whenever an item is deselected. A selected item is drawn entirely in the selected-item
    attribute. Only single-character commands are colored.

    Also: US spelling in two menubar.js comments.

    Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sat Nov 14 20:05:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/0a130d7a0dd0706247f2e9d4
    Modified Files:
    docs/v322_new.md exec/load/menubar.js exec/tests/atcodes/lightbars.js src/sbbs3/js_console.cpp putmsg.cpp terminal.cpp terminal.h
    Log Message:
    @BARDEFAULT:cmd@: let a display file name its first-highlighted item

    A lightbar menu always started on the first item in file order unless
    the script displaying it passed a command to MenuBar(), so a sysop
    editing only the menu file had no say in it.

    The new code displays nothing and is reported to scripts as the
    read-only console.bar_default (an empty string when the file has none).
    It takes the same C-escapes as @BAR:cmd@ and is forgotten with the
    other lightbar state when the hot-spots are cleared.

    load/menubar.js uses it only when the script gave MenuBar() no starting
    item: the user's last selection and an explicit argument (including
    false, for no highlight) still take precedence, and a command matching
    no item leaves the first one highlighted.

    Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sat Nov 14 22:39:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/511a76aaddef0ab84fd6a0e3
    Modified Files:
    docs/v322_new.md exec/load/select_item.js exec/xtrn_sec.js
    Log Message:
    select_item.js: lightbar navigation of a menu file's @BAR items

    When the menu file displayed in place of a list (the 'menu' option, e.g.
    the xtrn_sec, xtrn<n>, text_sec and text<n> menus) has lightbar items
    (@BAR codes), the arrow, Home and End keys now move the bar among them
    and Enter chooses the highlighted one, via load/menubar.js. An item
    returns what the user could type instead: an item number, the quit key
    or one of the caller's command keys. Typed numbers and keys, and so
    mouse clicks, are read at the prompt as before.

    The bar starts on the item for the caller's default (opts.current), else
    on the one the file names with @BARDEFAULT, else on its first item.

    xtrn_sec.js passes the section or program last chosen as that default,
    so the bar returns to it when a menu is redisplayed. Enter at a section
    menu file with lightbar items enters the highlighted section; without
    them it still quits.

    Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sat Nov 14 23:31:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/8d732cb540b7879d7c976f0e
    Modified Files:
    docs/v322_new.md exec/load/select_item.js shell_lib.js exec/text_sec.js uselect.js xtrn_sec.js
    Log Message:
    Find in the select_item.js lists: search by name with boolean terms

    A caller of select_item() that passes the new 'search' option (a
    function returning the text of an item) gets a Find command (issue
    #1345):

    - '/' or 'F' prompts, on the prompt's line, for a boolean search
    expression (see bool_search()), using the SearchStringPrompt text and
    defaulting to the previous search; '?' displays the textsrch help menu
    and a syntax error is reported with InvalidSearchExpression, each
    followed by the prompt again.
    - 'N' and 'P' repeat the search forward and backward, once there has
    been one.
    - Each moves the selected item to the next (or previous) match, wrapping
    around and changing page as needed; FindStringNotFound is displayed
    when nothing matches.

    The keys are named above the prompt: "/=Find" and, after a search,
    "/=Find, Next, Prev", following the "more" indicator or, when the list
    isn't paged, on the prompt's leading blank line. Those are gettext()
    strings (keys find_hint and find_next_hint) displayed as mnemonics, the
    command keys in the normal attribute and the rest in dark gray. A key
    that is one of the caller's own command keys is left out.

    Find is not offered in a list without a selected item (no_default), for
    a menu file displayed in place of a list, or when bool_search() isn't available.

    What is searched:
    - area selection lists (shell_lib.js): description, name and, for
    sub-boards and directories, internal code
    - uselect.js: the item name
    - text_sec.js: section name; file description and filename
    - xtrn_sec.js: section or program name and internal code

    Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sat Nov 14 23:56:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/d24c7188639f42e1bb3e8769
    Modified Files:
    docs/v322_new.md exec/load/select_item.js
    Log Message:
    select_item.js: name the Find keys in the prompt; N and P page the list

    Changes to the Find command of the select_item() lists (issue #1345):

    - The keys are named in the list's own prompt rather than on a line
    above it: "Find, " and, once there has been a search, "Next, Prev, "
    are inserted ahead of the prompt's first command key (e.g. "Which,
    Find, Quit, or [3]: "), and a prompt of the form "Which or Quit: "
    becomes "Which, Find, or Quit: ". They are displayed as part of the
    prompt's mnemonics, so 'F', 'N' and 'P' are its highlighted keys.
    The gettext() strings (find_hint, find_slash_hint, find_next_hint)
    use the @Find@, @Next@ and @Previous@ text.
    - 'F' is the key named ('/' remains an alias, and is the one named only
    where 'F' is the caller's own command key).
    - 'N' and 'P' repeat a search only when one has been made in the list as
    currently displayed. Otherwise, and in lists without Find, they page
    the list as PgDn and PgUp do, unless they are the caller's own keys.
    The previous expression is still the default of the next search.

    Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sun Nov 15 15:13:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/bdb36a0dea4ec77f44dd01bc
    Modified Files:
    docs/v322_new.md exec/load/menubar.js select_item.js
    Log Message:
    select_item.js, menubar.js: Backspace, Left and Right arrow keys

    In the lists of select_item.js (area selection, uselect.js, text_sec.js, xtrn_sec.js, scancfg.js), Backspace now leaves the list as the quit key
    does. In a single-column list so does the Left arrow key, and the Right
    arrow key chooses the default item, as Enter does. In a multi-column
    list those two keys still move between the columns. A key that's one of
    the caller's own command keys is still returned to the caller.

    MenuBar.move() now returns whether there was an item to move to, and MenuBar.handle() uses that for the Left and Right arrow keys of a menu
    whose items are all in one column: Right returns the current item's
    command (as Enter does) and Left is returned unchanged, which
    select_item.js takes as the quit key for a menu file displayed in place
    of one of its lists.

    Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net