1. 30 Mar, 2022 1 commit
  2. 29 Mar, 2022 13 commits
  3. 28 Mar, 2022 9 commits
  4. 27 Mar, 2022 8 commits
  5. 25 Mar, 2022 8 commits
    • Rob Swindell's avatar
      Uh, increment the pointer in globi() · 30cf70e9
      Rob Swindell authored
      Fixes crash reported in #381.
      30cf70e9
    • Rob Swindell's avatar
      Remove the hard-coded ".msg" extension from data/subs/*.msg display file · 1f0d53ca
      Rob Swindell authored
      And data/dirs/*.msg display file. Now you can have any supported menu file in this location if you wish.
      1f0d53ca
    • Rob Swindell's avatar
      Detect/display menu files, even if only a .ans version exists · 9ac7335f
      Rob Swindell authored
      I'm so tired of this 30 year old frequently asked question.
      
      If a sysop really wants their Synchronet BBS to only work correctly for ANSI users, I suppose that should be their prerogative.
      
      I always felt that by not detecting/displaying menu files when the minimum set of files was not present, I was helping sysops to identify an issue with their system (which would not work correctly for non-ANSI users). *And* I always felt that having a single menu/display file that correctly supported both ANSI and non-ANSI users was a nice convenience (who really wants to maintain multiple versions of their menu files?). But I'm so tired of answering this question, I just give up.
      
      Hopefully this doesn't break anything for anyone. <shrug>
      9ac7335f
    • Rob Swindell's avatar
      Revert to *.XXcol.* being an exact column width, add *.cXX.* support · e3ba2427
      Rob Swindell authored
      That previous commit made all *.40col.msg files display for 80 column users. Not my intention.
      
      So revert to the previous behavior of *.XXcol.* display files. I didn't want to go renaming a bunch of menu files as a result of the previous commit and I didn't want a bunch of sysops with *.XXcol.* files to be suddenly surprised at their new BBS behavior.
      
      And introduce a new file naming convention, *.cXX.* (where XX is a MINIMUM column width). This is the same naming convention used by Mystic, which also treats it is as a minimum terminal width, not a required exact width.
      e3ba2427
    • Rob Swindell's avatar
      Merge branch 'dd_msg_reader_bbs_edit_msg' into 'master' · d897d430
      Rob Swindell authored
      DDMsgReader: Now calls bbs.edit_msg() to edit an existing message.
      
      See merge request !167
      d897d430
    • Rob Swindell's avatar
      Use text/menu/*.###col.* display files for even-wider terminals · a8db694b
      Rob Swindell authored
      e.g. display basename.132col.msg even if the terminal is 133+ columns wide.
      
      Fixes issue #380.
      a8db694b
    • Rob Swindell's avatar
      Introduce case-insensitive version of glob(): globi() · ce74d0e0
      Rob Swindell authored
      glob() is case-insensitive on Windows already, so create a work-alike for *nix.
      ce74d0e0
    • Rob Swindell's avatar
      De-dupe random menu filenames by truncating at first dot, rather than last. · 479bd24c
      Rob Swindell authored
      Fix for one of the problems described in issue #380.
      
      bbs.menu("random*"); would display column-width-specific files (e.g.
      random.132col.msg) even when they weren't appropriate for the current
      user terminal width.
      
      This is fixed by truncating the filenames matching the requested pattern at
      their first-dot rather than the last.
      
      The downside is, you can't have a set of random.#.* files, where # is the
      unique part of the filename and * is the file-type extension. Just use
      the naming pattern "random-#.*" instead (or something similar) instead.
      479bd24c
  6. 24 Mar, 2022 1 commit