1. Forum
  2. FidoNet
  3. SYNC PROGRAMMING

  • src/sbbs3/node.c

    From Deucе@1:103/705 to Git commit to main/sbbs/master on Sun Oct 12 02:48:24 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/6030d8d90356d177c4aeea41
    Modified Files:
    src/sbbs3/node.c
    Log Message:
    Fix options parsing

    -debug, -loop, -pause, and -v[key] have printed usage and exited
    since e1ac8374d9.
    --- SBBSecho 3.30-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to Git commit to main/sbbs/master on Sun Oct 12 03:22:15 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/12faae1503722c8ee3ee0c87
    Modified Files:
    src/sbbs3/node.c
    Log Message:
    Print a message describing why usage() is being called

    The only way to get help without a message is to not specify any
    arguments at all.
    --- SBBSecho 3.30-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to Git commit to main/sbbs/master on Sun Oct 12 03:28:39 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/20285cda7d935d7071c4b631
    Modified Files:
    src/sbbs3/node.c
    Log Message:
    Actually, multiple actions and options is documented

    Sorta... it's not really clear that/if options are supposed to be
    able to be specified later, but since they could, they can.
    --- SBBSecho 3.30-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)