Threading IO manager

It is not done in default. Default is the simple user at the keyboard, he only advanage to reading the io manager is that the user can see the command bufer, some other process or command still has the machine.  It is like stalling the scroll cursor on a clogged web,useful, signal and not armful. Rule is, if you don't echo, it is control c  time.

The world of pros is working on the multi threaded io manager, the case for enterprises. Defalt io manager owns the default, start up, bot syntax, standard example, position in the market.  Mouse and keyboard and xcb poll;  get it in any color as long as its RGB.

So, this is wrapping it up, I add the code as needed as I go along here.  In singlet hreaded mode, IO manager will call tokenize then exec command directly. Normally, to redirect console loop, one should open an fd and talk to it like an input string of linux commands. The latter method is what is done in the threaded case. The default case is the short path, and the change in io manager is not noticeable as one just changes the call back entry point. Each loadable is delivered the console loop call back, exec command. In he multi threaded case we give it a Write_console_fd, and the console loop reads like normal. If you're careful with these snippets, the call back on command processing, which is recursive, allows you to redirect s data return path. We get gated entry and exit, single points making thread control a breeze with mutex at the gates.