White-space changes only, exception being the rare insertion of NL before
closing brace (couldn't find the option to disable that behavior).

I excluded some header files (e.g. sbbs.h) since uncrustify seemed to be doing
more harm than good there. I might just end up applying different set of rules
to .h files.

Causing uncrustify (0.80) to assert:

do_source_file: Parsing: execmisc.cpp as language CPP
parse_cleanup(479): pc orig line is 1257, orig col is 55, Text() is ')', type is PAREN_CLOSE
parse_cleanup(485): (frm.top().type + 1) is SQUARE_CLOSE
parse_cleanup(492): File: execmisc.cpp, orig line is 1257, orig col is 55, Error: Unexpected ')' for 'SQUARE_OPEN', which was on line 1257

(e.g. new user)

Similar bug fix as that just made to system.datestr()

Actually use the return value of datestr()

Fixes issue reported by Deuce, regression introduced in commit 490e86fa

To fix jsdoor build

Helpful for scripts that want to know what file types (extensions) are
supported by the Archive class object.

Still need to work out the JSDOC support for this. Similar to the
Socket class object properties, this will have no documentation/description.

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)