<Deuce> Yes.
<mcmlxxix> :|
<mcmlxxix> you took that as an or statement
<mcmlxxix> i hate you so much sometimes

Renamed the menuTitle property to topBorderText.  Added a bottomBorderText property, for text to be displayed in the bottom border.

Version 1.22: If the message score is 0, with upvotes and total_votes both 0, then don't show the score when using the default header ANSI.  This is what was intended, but the 0 score started showing up in more recent builds of Synchronet.

Fixed a bug that somehow crept in: Tthe check mark for selections in multi-select mode was being displayed in the wrong place when using a menu border.

Now supports a title in the top border line: Added a new property for the DDLightbarMenu object, menuTitle, which is a string that specifies the title text to write in the top border (if the border is being displayed).  It defaults to an empty string (for no title).  Synchronet attribute codes are supported.

smb_freemsgmem():
bounce() is using a strange method of copying a message header in memory
(not using smb_copymsgmem) and when it frees the message, ends up with a
double-free of the 2 new smbmsg_t members (not header fields): text_subtype
and text_charset.

Send failure emails with high-prioirty.
Use require() instead of load().

enable bright-background support (and disable blink).
Use require() instead of load(), where applicable.

- P_NOERROR
- P_PETSCII
- P_WRAP

bright-background (iCE color) support in SyncTERM/CTerm ANSI terminals.

- PetTerminalDetected (renamed from PetTermDetected)
- PetTerminalQ
- TerminalAutoDetect
- TerminalColumns
- TerminalRows
- TerminalMonochrome
- TerminalColor
- TerminalIceColor
- IceColorTerminalQ
This also moved the MsgCarbonCopyList definition to the end of the file

on PETSCII terminals.

Replaced embedded ^A chars with \x01.
Use bright-background (\x01e) for selected answer, much more readable on
PETSCII terminals.

New text.dat strings:
- PetTerminalDetected (renamed from PetTermDetected)
- PetTerminalQ
- TerminalAutoDetect
- TerminalColumns
- TerminalRows
- TerminalMonochrome
- TerminalColor
- TerminalIceColor
- IceColorTerminalQ
This also moved the MsgCarbonCopyList definition to the end of the file
for now.

- for PETSCII, this is automatic and you don't lose blink, but you do lose
  colored foreground when enabling a bright background ("reverse video")
- for ANSI, this mode is typically referred to as "iCE colors" and disables
  blinking-text support
- Ctrl-AE (^AE) is the new attribute code to enable bright-background
  (will have no effect on ANSI terminals that are not iCE color enabled)
  "E" is now valid in the ctrl/attr.cfg file and string values for JS
  console.attributes assignments, as well
- Ctrl-AI (^AI) - blink - now does nothing for ANSI/ICE color terminals
  (blinking is not supported in combination with bright-background)
- Using a new/non-standard CGA attribute bit-flag to indicate the selection of
  bright-background colors (BG_BRIGHT, bit 10), separate from BLINK.
  This change required all/most char/uchar attribute representations to be
  converted to int/uint.

New text.dat strings:
- PetTerminalDetected (renamed from PetTermDetected)
- PetTerminalQ
- TerminalAutoDetect
- TerminalColumns
- TerminalRows
- TerminalMonochrome
- TerminalColor
- TerminalIceColor
- IceColorTerminalQ
This also moved the MsgCarbonCopyList definition to the end of the file
for now.

PETSCII reverse-video attribute fix:
When a CR is sent to the terminal, the reverse-video attibute is auto-disabled
so update our "current attribute" (curatr) value to match the remote.

Support new printfile/putmsg mode flag: P_WRAP to force an ungraceful
line-wrap (splitting) to the specified column width. If no column width is
specified (0), then this mode will force an ungraceful wrap before the last
terminal column where some terminals *may* auto-wrap.

JS console.printfile() and printtail() methods now support an optional
"orig_columns" argument, similar to console.putmsg(). Must specify P_WORDWRAP
or P_WRAP for this argument to have any effect.

Much improved terminal-type selection/configuration in the user defaults
menu and abort (^C) at any of the yes/no prompts is now detected/handled much
better (to answers to the prompted questions are not saved to the user
settings).

passesd filename is not found - function reports the symbol was not
defined rather than file not found or something similar.

return an error value (-33, it's the magic number).

Borland Implib Version 3.0.22 Copyright (c) 1991, 2000 Inprise Corporation
and MSVC-generated DLLs with exported functions using _cdecl calling convention
... sometimes or with some verisons of some DLLs, implib won't add the
underscore prefix to the exported function name which caused the build error:
Error: Unresolved external '_total_users' ...

Using coff2omf instead to convert the MSVC-generated import library (sbbs.lib)
to the Borland/OMF flavor works, however. I'd seen this issue before but it
went away when the number of symbols in the source DLL changes. Newer versions
of implib appear to *not* have this issue so when we upgrade to a newer
C++Builder, this work-around will no longer be necessary.

 -clear        Clear the screen (if possible) before list
 -home       Home the cursor (if possible) before list
 -loop [n]    Loop the list, delaying n seconds (default: 2.0 seconds)

When the command is MLST, fp is NULL, so should not be passed to ftell().

F

backspace/delete key prompt, set the PETSCII flag in the autoterm *and* the
user's setting. If a CBM/PETSCII user actually got that prompt, that means
they were probably connecting to the wrong TCP port in the first place, so
relying on auto-terminal won't work for them on subsequent connections. We
probably should have a way to manually turn off/on PETSCII support, when
needed. <sigh>

^U, ^P, ^T, ^K, etc. and not 0. This allows a CBM/PETSCII terminal user
to actual hit their Backspace/Delete key (^T) in response to the new new-user
prompt

- turn off the user.misc PETSCII flag (too)
- don't copy the current autoterm flags into user.misc - this should no longer
  be necessary since the correct way to detect current terminal capabiilites
  is via calls to term_supports().

Removed note re 'platform' line from readme.txt
Some of you were using this feature (as intended) to advertise that the
client was running on some other/fake/amusing BBS package and OS.  I'm
told that this is not okay and may break things in the future.  (If you
update mrc-connector.js, the fact that you're running Synchronet and on
Linux or Windows i386, i686, x86_64 will be shared with the MRC server.)

You're now running SYNCHRONET and whatever (system.platform + '_' + system.architecture) resolves to.

- "lsaquo" and "rsaquo" (angled versions of "lsquo" and "rsquo")
- "zwj" and "znnj" (zero-width joiner / non-joiner)

So replace some strstr() calls with either (new local function) strStartWith_i()
or strcasestr(), depending.
strStartWith_i() return length of the matched word, so no need to sprinkle
about magic numeric constants everywhere. The extra calls to strlen() are worth
the code clarity / reliability, methinks.
TODO: find out if there's a way to calculate the length of string-constants at
compile-time (?).