Message scans must be set off by ddoc, for ddoc only users

[dgets]

In case users select things wrong in the initial configuration, it is imperative that ddoc, when selected as a shell, needs to save the previous settings and set new message scan and new un-read messages to user scan off, as they will not call routines from the appropriate ddoc shell interface.

[dgets]

Now that the scanSub() crap has been completed, I've finally posted a request for how to do this in the appropriate forum for the developers. We'll see what they've got to say!

[dgets]

The flags that I changed ended up having lots of bogus effects. This is going to take some more research...

[dgets]

Fixed this as per 4c7de71, I believe.

[dgets]

Okay so ^= is the only one that is fixing this, but only 50% of the time, as it toggles. The other operators, that are supposed to work, are breaking everything from ANSI to high ascii. I could add a conditional text on whether or not to XOR things here, but that seems remarkably foolish. I'll come up with a solution for this when my brain isn't so fogged, if @ntwitch doesn't beat me to it. ;)

[dgets]

This has been fixed in 6d075a5.