current column is > 0, it'll maintain that same margin on the right-edge of the
screen (shortening the fill length).
This allows you to create nice dynamic horizontal lines/dividers with margins.

states, and there's no other threads around to change those states.

The SDL wiki lists KMOD_MODE as AltGR... if that flag is flying in a
keypress, do not block text input.

checking.

the net-attributes header fields.

and clear the "IN-TRANSIT" net-attribute of the original message, even if we're
flagging it for deletion (the delete attribute could always be toggled off).

Now, the window() is set to the curr coordinates.
Use generic functions for implicit and relative movement.
Make the scrolling region behave much more like the DEC source.

"terminal nodes".

is deeply impacted by the vt glitch, and I'm not dealing with that.

If either localtime_r() or mktime() return a error result, don't use use the
non-sensical time.
Nelgin has reported that under some conditions, he sees:
Your time has been reduced due to an upcoming event on Wed Dec 31 1969 18:00:00
when using Ctrl-T (time info hot key).
I don't have an explanation for this, but if either of those function calls
failed in getnextevent(), something like this could happen. <shrug>

Don't add another tear-line (---) if one already exists, when creating
netmail (.msg) stored messages.

flag set.
Allow robot configurations in sbbsecho.in to include attribute values to
add (or-into) the message header, thus allowing for robot-netmail messages
that remain in SMB and are handled by robots (e.g. tickfix.js). Without
the in-transit attribute flag set, the messages will be subsequently
exported out to netmail/*.msg files for potential processing by other
FTN utils.

imported for robots actually have a 'to' index value of 0.

Fix gcc warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'long unsigned int'

only (e.g. areamgr requests or whatever). In the future, they could be extended
to echomail areas too, if that's desirable.

For now, it's really intended for ticket-FileFix.

Anyway, NetMail can be received for the robot-name@<your-ftn-address> and
the mail message will be stored in the Synchronet "mail" base. The recipient
extension will be absent since there is no valid user account associated with
the robot. Robot names supercede other user names/aliases for received netmail.
If one or more netmail messages were imported for a robot and that robot has
a semaphore path/filename specified (e.g. to trigger a timed event), then that
semaphore will be "touched" before SBBSecho exits.
One weird anomly with this is if attached files are received for robots, those
files will be stored in data/user/0000.in. The altnerative is to just ignore
file attachments sent to robots.

The echofg supprot for robots is still yet to be added. In the mean time, you
can add robots to your sbbsecho.ini like so:
[robot:<name>]
semfile=/path/to/semfile

Incremented version to 3.11.

Also converts Ctrl-A chars to '@", so behaves similar to fmsgdump now.
SEEN-BY's and AREA lines aren't dumped with -c because they don't begin with
a Ctrl-A.

(from stored messages in .msg files into packets), the origin net/node within
the  *packed message* header would be set to the local system's address
net/node (for the destination zone), always. This is the appropriate action
when packing EchoMail, but not for NetMail.

Now, there are lot of other header fields in the packed message that contain
the source/origin address (e.g. @FMPT, @INTL kludges) and those would reflect
the original origin address still. And these fields take precedence over the
orign net/node fields of the packed message header. So I'm not sure this bug
would actually cause any problems anywhere, but it was a bug all the same.

letter).
Also, REALNAME is now an alias for COMPANY and MEMO2. Man these legacy
@-code names are terrible.

to not work if the second byte of a stack-allocated but unintiallized variable
(str) was non-zero. This was only observable on Win32-Release builds
(in debug builds, stack variables are initialized to non-zero). Reported by
Sneaky (Ian) who was patient and kept with me through the remote debugging
effort. Thanks!

change the window size and it should work out alright.

into any other files.