1. 11 Oct, 2020 4 commits
  2. 10 Oct, 2020 1 commit
    • Rob Swindell's avatar
      Fix NDX file creation when votes are included in QWK packets · 2bc1d73f
      Rob Swindell authored
      When both Indexes (NDX files) and vote messages are included in a QWK packet (an unexpected, but valid combination), the "Record number" stored in NDX files for subs with votes would be incorrect as it did not increment when a vote message (with no body text) was added to the messages.dat file.
      
      Reported by user that was trying to use MultiMail to read a QWK packet that included both votes and indexes and "IgnoreNDX: No" in their .mmailrc file.
      2bc1d73f
  3. 09 Oct, 2020 4 commits
    • Rob Swindell's avatar
      Don't pass-through ANSI Device Attributes (DA) requests · 9919c23e
      Rob Swindell authored
      putmsg(), used to display messages and display/menu files, will no longer pass-through the ANSI sequence ESC[c (found in some corrupted ANSI posts to fsxNet->FSX_BOT echo) to the client terminal since this will stimulate a (unwanted) response from the client.
      
      I do wonder if the outchar_esc value check should be == here instead of >=, but I'm not familiar with the string and SOS states. I wonder if any display files sent from the BBS would ever include those sequences.
      9919c23e
    • Rob Swindell's avatar
      Use an enum for ANSI output state · f26b296b
      Rob Swindell authored
      No functional change with regard to the ANSI output state, just making the code easier to read.
      
      Removed the conversion of `[ and \xFA[ to \x1b[ in putmsg(). This unexplained output translation has been supported since at least v2.xx and I have no recollection of exactly why it was added. If I recall correctly, some BBS software at some point in time sent ANSI-encoded messages into message networks by translating the ESC (\x1b) character in the ANSI sequences to either ` or \xFA in the process. This "feature" seems like it would still work, but it's completely undocumented and I have no idea why it was added (and seriously doubt anyone relies on this behavior), so I'm removing it. If anyone misses this feature, I'll happily add it back, but I'm skeptical that'll happen.
      f26b296b
    • Rob Swindell's avatar
    • Rob Swindell's avatar
      Replace ESC chars with '.' when viewing messages, support '-<count>' with 'r'. · c4c9902d
      Rob Swindell authored
      When reading messages, circumvent ANSI-encoded messages by replacing the ESC
      character (ASCII 27) with '.'. This could be made an optional behavior if
      someone really wants ANSI-encoded messages to be read via smbutil.
      
      Also, allow continuous reading of 1 or more consecutive messages using the
      -<digit> option (no prompting).
      c4c9902d
  4. 08 Oct, 2020 14 commits
  5. 07 Oct, 2020 6 commits
  6. 06 Oct, 2020 1 commit
  7. 05 Oct, 2020 4 commits
  8. 04 Oct, 2020 6 commits