Skip to content
Snippets Groups Projects
  1. Sep 01, 2011
  2. Aug 31, 2011
  3. Aug 30, 2011
  4. Aug 27, 2011
  5. Aug 26, 2011
  6. Aug 25, 2011
  7. Aug 12, 2011
  8. Aug 11, 2011
  9. Aug 10, 2011
  10. Aug 06, 2011
  11. Jul 29, 2011
    • deuce's avatar
      Add Amiga fonts: · 12b09ed8
      deuce authored
       37 - P0T NOoDLE (Amiga)
       38 - mO'sOul (Amiga)
       39 - MicroKnight (Amiga)
       40 - Topaz (Amiga)
      
      As a reminder, to select a font, send the sequence "\e[0;40 D" where \e is
      ESC and that space IS THERE.
      12b09ed8
    • deuce's avatar
      Add Amiga fonts. · d8295b8f
      deuce authored
      d8295b8f
  12. Jul 21, 2011
    • rswindell's avatar
      028045a5
    • rswindell's avatar
      Complete QWKE support (using MultiMail for testing): · c9f6aaa5
      rswindell authored
      Create and include in packet TOREADER.EXT if QWKEsupport is enabled
      (MultiMail keys of this file for QWKE support, so without, no QWKE features are
      enabled in MultiMail).
      Parse TODOOR.EXT if included in REP packets (for adding/dropping subs or
      setting/resetting pointers).
      Parse To:, From:, and Subject: QWKE kludge lines and use if/when appropriate
      (e.g. to defeat QWK 25-char header field limits).
      Create To:, From:, and Subject: QWKE kludge lines in QWK/REP packets when
      QWKE support is enabled and those fields exceed QWK limits (25 chars).
      Also, legacy SyncQNET kludge lines (@VIA, @TZ, etc.) may now exist in the
      top of the message body in any order.
      Note: current versions of MultiMail do not support "To" fields > 25 chars, even
      in QWKE mode (though I have a patch pending) and do not (yet) support
      Synchronet HEADERS.DAT file (rendering QWKE kludges unnecessary).
      These are major changes in the QWK/REP creation/parsing code, so testing
      (especially with QWKE-compliant offline readers) and bug reports are welcome!
      c9f6aaa5
    • rswindell's avatar
      Enhancement: most question-type text.dat entries are now optional. · 77a2cda0
      rswindell authored
      That is, if any of the following text.dat entries are set to a blank/emtpy
      string (by editing ctrl/text.dat or via run-time script modification), the
      question will not be asked of the user allowing greater sysop-customization
      of hard-coded processes (e.g. new user application):
      ClearUploadQueueQ
      ClearDownloadQueueQ
      HangUpAfterXferQ
      ChatWithGuruInsteadQ
      ForwardMailQ
      DownloadBatchQ
      LogOffQ
      DeleteErrorLogQ
      ClearErrCounter
      DeleteGuruLogQ
      AutoTerminalQ
      AnsiTerminalQ
      ColorTerminalQ
      ExAsciiTerminalQ
      CallingFromNorthAmericaQ
      ReadYourMailNowQ
      NScanAllGrpsQ
      SScanAllGrpsQ
      NewPasswordQ
      ContinueQ
      EnterYourPhoneNumber
      UserInfoCorrectQ
      UseExternalEditorQ
      DownloadAttachedFileQ
      AddSubToNewScanQ (new)
      RemoveFromNewScanQ
      DisplaySubjectsOnlyQ
      Post
      SearchExtendedQ
      ViewSysInfoFileQ
      ViewLogonMsgQ
      WithLineNumbersQ
      77a2cda0
    • rswindell's avatar
      8491e813
Loading