all the time.
Also, I've recently switched to excflags.

poor vim users don't have :set ts

tired of regenerating this manually.  :-)

  would crash the IRCd.  Thanks to Invizix of doopal.synchro.net for finding
  this one.

COM0:STDIO <- Indicates that stdio should be used.
COM0:SOCKET### <- Indicates socket I/O should be used with socket handle ###
COM0:HANDLE### <- Indicates Win32 COM should be used with COM handle ###

executables.
If "Intercept Standard I/O" is enabled, Line1 becomes:
COM0:STDIO
If not, Line1 becomes:
COM0:SOCKET<Socket Handle>
ie:
COM0:SOCKET54

Currently, this is #ifdef'ed out since I'd like DMs approval before I do
this.

within a lightbar getval() call.

functionality)

  attached to the receiving server (as opposed to the server string itself)
  would crash the IRCd.
* Beginnings of Dreamforge support.

  socket problem, but then not empty the queue before sending current data
  after the connection cleared up.  This would lead to severe
  desynchronization in some circumstances.  All Sysops are encouraged to
  upgrade to this version of the IRCd as soon as possible.

SSH.  Passing a socket isn't very likely to be helpfull, and a local socket
pair seems like a kludge (That will, of course, be supported for "old-style"
32-bit doors)

  Thanks to Tracker1 and RuneMaster for pointing this one out.

When asked to clear lines beyond the lbshell_bg size, clear to LBShell_Attr

Re-enable combined attributes.

[wildmat] arguments (only * and ?, not complete WILDMAT pattern syntax).