SUB and DIR have long had this bug, but I just noticed while playing with the
new USER keyword capabilities (specifying user numbers and/or names).

If you switched between numeric and alpha/string parameters, without restating
the ARS keyword, the keyword would could end up wrong in the parsed byte array.

Caveat: the name parameter cannot contain a space, so excludes spaces or
replace them with '.' or '_': the user's alias will match.

This fixes issue #748

Previously, if either of the user terminal dimensions was set to a auto (0)
then we wouldn't propagate the other specific (non-zero) value to the runtime
console dimension. Usually a user will set either both values (cols and rows)
to 0/auto or neither. So this isn't a oft-used configuration combo.

e.g. [can|is]_subject_something() is now named subject_[can|is]_something()

No functional change.

temp_cmd() should've been called first on any sane platform. <shrug>

Borland doesn't need this, and making the new feature work with it
would be immensely painful, so just disable the files in Borland.

Also, now the JS format()/printf()/etc. can use field specifiers.

like datestr() does.

Eliminate use of strcpy() and sprintf() in this file

... and download events.

The "Native Program List" was a hack left over from the transition from
MS-DOS to OS/2 and now with extensible configuration files, like we have now,
there's no reason not to add more fields and make it easier to specify which
of these programs (most/all of them nowadays) are actually native to the
host OS.

The defaults (e.g. when creating a new file type) are unchanged for now.

Shorten the native_opt from "Native Executable/Script" to just
"Native Executable" to make it usable in opt lists with narrower option name
columns.

... sometimes the generated command-line is different depenending on the
external() mode flags (e.g. EX_NATIVE).

No need to load/modify messages that already have DELETE attribute flag set

Log a debug-level message after loading messages upon POP3 login.

Optimization:
No need to read and re-write headers that already have the DELETE attribute.

Fix:
Forced permanent removal of deleted messages (e.g. when creating a new user
that's reusing an existing user number), didn't work unless SCFG->Message
Options->Purge Delete E-mail was set to "Immediately" (not the default).

Add/use new print mode flag: P_ATCODES for use with trusted format params

Renamed text.dat strings (to better support translation/localization):
- Deleted -> DeletedUser
- Inactive -> InactiveUser

New text.dat strings:
- Deleting
- DoneDeleting
- Deleted
- DeletedNumberItems
- E_Mail
- E_Mails

As reported by Accession in #synchronet at irc.synchro.net

If this menu file exists, it'll be used to display file information (e.g.
when using 'E'xtended info or 'D'ownload commands) instead of the Fi* text.dat
strings.

Allowing more customization options for file information displays.

datestr() will return this string when passed a time_t value of 0.

FILE_DESC didn't handle blank/no file description correctly

The @-codes that need file size or date needed to call the proper filedat
functions to get those values or else risk them being 0.

I received 6853 duplicate FastCGI error emails today (sent in a 2 minute
time span). I wish I already had this in place. :-(

Caught by Coverity: CID 529977:  Incorrect expression  (SIZEOF_MISMATCH)

Converting the path to UPPER case and then comparing against a lowercase
string would never work.

Bug introduced in commit 6edc0270, reported by xbit (XBITBBS)

New:
- FILE_COST, file's credit value or "FREE" when applicable
  (see also FILE_CREDITS - the file's credit value or 0 when free download)
- FILE_AUTHOR - file's author (e.g. from SAUCE record) or blank if N/A
- FILE_GROUP - file's author group (e.g. from SAUCE record) or blank if N/A
- FILE_BYTES - file's size in bytes (previously, would use FILE_SIZE for this)
- FILE_CRC32 - 8 hex digits or blank if N/A
- FILE_MD5 - 32 hex digits or blank if N/A
- FILE_SHA1 - 40 hex digits or blank if N/A
- FILE_TIME_TO_DL - estimated time ("HH:MM:SS") to download file at current CPS

Changed:
FILE_SIZE is now the file size estimated in KB, MB, GB, etc., not the exact
file size in bytes.

from text.dat.

Also change the alignment of the Fi* (File Information) text.dat strings to
allow more space for the data fields, allowing better support for adding URLs
(for sysops that want to do so, e.g. by setting FiFilename in text.ini).

This reverts commit 269875be.

There are plenty of existing text.dat strings where URL @-codes can be added.
I had good/better results by changing the FiFilename string.
So let's not add a new/blank text.dat string for now good reason.

This is an optional (default: blank) string that can be used to display a
file's URL(s) (e.g. FTP and/or Web URLs, using @-codes) when viewing extended
file information. I currently have this string output before the file
description.

The idea is that a sysop could set this string (e.g in their ctrl/text.ini)
instead of or in-addition-to their text/menu/download.msg file and then the
file URL(s) would be more readily displayed (not just went prompting for a
download protocol to send said file).

As an alternative to directory aliases configured in ftpalias.cfg and/or
web_alias.ini, a sysop can specify a shortcut (virtual directory name) per
directory in SCFG->File Areas. These shortcuts will appears as top/root level
directories in the FTP and Web servers for quick user access to important
directories.

The advantages (over ftpalias.cfg / web_alias.ini) are:
- one place to configure
- FILE_FTP_PATH and FILE_WEB_PATH @-codes will use the shortcut
  (usually a shorter, preferred virtual path to the directory)

* New JS file_area.dir[].vshortcut property

This appears to have been the original intention (otherwise, why call ultoa?),
but was never done. Just a usability/convenience thing, but an apparent bug.

Again, not exhaustive, just the places I found quickly.

If ESC is pressed, clears the UIFC_XF_QUIT and aborts the exit.
Otherwise, continues exiting.

Not sure if there's anywhere else that needs the ATEXIT change to
avoid infinite exit loopage.

On JS TLS sockets, sends over 16384 bytes would be truncated to
the next multiple of 8192 higher than half the buffer length.

This was triggered because we send chunks of 8192 bytes at a time,
and decrement the length each time through the loop.  We return
"success" when the total sent so far is higher than the length
remaining.

Fixes bug reported in #Synchronet by Accession.

Since "FreeBSD" is longer than "Win32" or "Linux", we can't use
a fixed position/length here or the version number will get chopped
off.