Appended very important trailing linefeed.

The biggest difference is that you can combine all files from multiple dirs
into a single sorted list and you can sort on any property (field) value.

The byte/credit format is very customizeable, the output format is completely
customizeable.

By default, just the filenames are output, but either use '-ext' or one or
more '-v' values to add more fields. Use -p=list to specify a comma-separated
list of properties to print.

Instead, return the fractional size in KB's with 2 digits of precision.

Fixed up some of the variable names.

Returns a floating-point formatted size estimate more in-line with my
preference (e.g. 17.0G instead of 17,000M).

Fix bseen calculation and saving
Only save seen data after all repsonses have been sent
Stop processing when the socket has been closed

Can find duplicate files in your file bases by name and/or hash sum - fast!
Can output simple text or JSON format.
Run 'jsexec dupefind' to search just for duplicate files by hash (SHA-1)
or run 'jsexec dupefind -help' for the various usage options.

For Nelgin, to reduce log spam.

- Add a unique number to event names for each request
  Prevents responses from being acepted by multiple queries
- Don't set Socket.dnsObject for synchronous lookups
- OPcode of 2 is used for status replies (ie: NXDOMAIN)
- Be more careful construct result array in request()

Also, have handle_response() return errors.

Like the -d option for ADDFILES.

For Al (TRMB)

Also, check that the opcode and response flag are correct when
parsing responses.

When handling a resolve call, ensure no errors occured.

This won't impact Synchronet as it has a separate signal handling
thread, but we still need to behave properly for processes that
don't.  I'm also saying that ENOMEM does not indicate a disconnection,
though it may be better to pretend it was disconnected...

The DNS_blocking class supports the same API as the DNS class, but
does not use events, so any method will complete before returning.
As such, the callback argument is optional.

Sheesh.

SRV, NAPTR, and URI

Thus appears to have been the root cause of the infinite loop/memory
issue.  Basically, line was never replaced if it didn't match
^{[0-9]+}$ and didn't result in a number when passed to parseInt()
This resulted in an infinite loop that kept pushing zero-length
strings into an array.

Implicated in possible infinite loop/OOM problems.

(console.screen_rows).

This appears to work and the event handler *should* work on other
event types already.

Note, this is *nix-only due to the use of poll().  select() will
need to be used for Windows to keep XP compatability.

Autoformatted via prettier with settings below, this is so additional polyfill matches can be used to match formatting in future PRs for polyfills, as well as full formatting tooling for .js files.

```yaml
tabWidth: 4
useTabs: true
singleQuote: true
trailingComma: "es5"
```

If true, and if this is our first input, and if the users types
something that would otherwise have been appended to the default
text, then the default text is deleted first.

While they both delete a character, delete at the end of a line will
move the next line up instead of moving this line up.

Fixes #243

Just in case it was read as a string (e.g. had a ; comment following the value)

Also check bbs.online for sbbs input.

First look for a linked node matching the node address string as passed,
then look for a match using the normalized address (removing .0 and @domain).
The "ALL" wildcard should not be used for password lookups.

This should fix reported issue 240.

1) user.number immediately after login() remains zero, but changes
   "sometime" after.  Avoid using user.number right after login()
   call to generate filename.  All data/user/0000.imap files can
   be deleted after this change.
2) Saving Seen data would modify the object storing it when binary
   seen values were used.  Use JSON.parse(JSON.stringify() to make
   a copy before saving and restore it afterward.  Should fix issue
   reported by nickshanks1 over IRC.

Don't include the obsolete unstructured regex in abs.unstrctured,
and use the abnf.unstructured for parsing headers.

This fixes an issue seen running the IMAP server on gratuitously
spammy messages.