Don't ident; commands.js will trust localhost instead. Should rid us of the 'incorrect password' log message, and another bug recently reported on DOVE-Net.

than sprinkling the mapping around the source files.
Also, disable the message thread nav keys (arrow keys, home, end) when not
in Thread View Mode - too confusing.

Removed some unused constant definitions/macros.
Updated copyright date (to 2016).

along with the standard Control Character 'Symbol" for each in a comment.

incoming mail): it turns out, stripping tabs (ctrl-i) is breaks many folded
header fields (e.g. MIME-encoded messages).
So, just strip bare carriage returns instead, as that was the original problem.

While "fixing" compiler warnings, a bug was introduced that would cause an
infinite loop while inserting File Libraries. This is possibly the same
problem reported by KK4QBN.

or Areas.BBS will all be found/opened successfully if "areas.bbs" is used.

Make sure pause ([Hit a key]) prompt doesn't appear on the same line as the
Reading prompt.
The '?' command now turns off "Thread View Mode".
Backspace is now treated the same as '-' (move backwards through sub).
When in Thread View mode, moving backwards now first searches for a thread
with a lower thread ID and if that fails, look for any thread with a different ID.
New Thread Nav command: Home (move to first msg in thread) and End (move
to last message in thread). Last in this context means the last reply to last
reply to the original message (not necessarily the newest reply). This is most
obvious how this works when in Thread View mode.
Moving forward through the sub (+ or <CR>) while in Thread View Mode now
searches first for a thread with a higher thread ID, and if that fails, then
any thread with a different ID.

I experimented with not clearing the screen (homing the cursor and using clear
to end of screen to remove old data), to avoid the "flash" while browing a
thread, but both Netrunner and mTelnet appear to not support the <ESC>[J
terminal escape sequence (clear to end of screen) correctly.

is not auto-detected. These hacking bots and scripts don't support ANSI.

- smb_next_in_thread
- smb_last_in_branch
- smb_last_in_thread

no longer ignores Ctrl-Z characters (CP/M EOF) by default. If you want the
old behavior (Ctrl-Z characters not displayed, just skipped), specify the
P_CPM_EOF mode flag.

HOME - homes cursor (to upper left, 1:1)
CLRLINE - clears current line (cursor to column 1)
CLR2EOL - clears to end-of-current-line (doesn't move cursor)
CLR2EOS - clears to end of screen (doesn't move cursor)

'J' - Clear to End-of-Screen, for ANSI users sends <ESC>[J, nothing otherwise
'`' - Home Cursor, for ANSI users sends <ESC>[H, form feed otherwise

Any alpha-char command or entering a message number will exit thread view
mode. If the entire thread fits on the screen, then the arrow keys can be used
to move about the thread (up, down, left, and right). The old thread-ID keys
( and ) still work, but a little differently. And while in Thread View  Mode,
ENTER  and - keys now move forward and backward by thread.

I meant to do this a long time ago and really should have (all the underlying
thread support was there). It really highlights all the network nodes that
don't support REPLY-IDs. :-(

them back to the client.

oldest *existing* message in the thread referenced by the specified msg.

Version 1.17 beta 16: Used js.gc(true) to force garbage collection at the beginning of the sub-board scan loops to ensure enough memory is available to continue doing the newscan.  This solved an issue where a "malloc failed" error was being returned.  I just saw that for the first time when doing a newscan with my reader today.

Version 1.17 beta 15: When deleting a message, any vote response messages that may exist for that message are also deleted.  Also, added a check in the GetMsgIdx() method that should (hopefully) avoid a 'msgNum not a number' error (as reported by Ragnarok).

function where the error is being reported from. So the WHERE macro now
contains the __FUNCTION__ "macro" and the various js*.c files that use the
WHERE macro to report errors had to be updated too.
This fixes the SCFG build errors related to "errormsg"

begin with a newline sequence (\r\n), since this would effectively waste a line
on the user's terminal.

uploads).

displays the 20 highest ranked messages in the sub-board based on up/downvotes
and replies.

function where the error is being reported from. So the WHERE macro now
contains the __FUNCTION__ "macro" and the various js*.c files that use the
WHERE macro to report errors had to be updated too.
Also, the 'access' argument is now being passed as a signed long rather than
unsigned long. Status/return values are often passed in here (e.g. from smblib)
and may be negative. This argument was being displayed with %ld but wasn't
being passed in as a signed value, so on 64-bit long systems, negative numbers
were just printed as large (4M+) numbers.
Also, no need to call getfname() in errormsg() since this is embedded in the
WHERE macro (since 2009).

SPAMMERS insert these either intentionally or mistakenly and they can defeat
security checks (like mailauth.js).

as errors.

there's no ftn_domains.ini file.

cause problems elsewhere (reading, viewing, exporting), so that'll need to be
tested.

Version 1.17 beta 14: Fixed a UI issue when displaying voting errors in the scrolling reader interface.

GCC (worked fine in MSVC) :-(

Set smb.last_error strings in new voting/polling functions on failure.