Need to work on how interactive mode is handled when the tab or window focus is changed and then back to the active window/tab, some odd output going on.

Working on input tracking for interactive mode, will track the number of keystroke & on carriage return (enter) we will clear the tracking. This will allow us to prevent the backspace, or cursor movement for interactive mode trying to go beyond where the input should let it.

Tested in a branch merged with #70 and worked well so far.

Still to fix:

• up/down arrow to move through text, needs to update the character tracking so we know how far the cursor can move.
• Somehow track how far up you can scroll through past input, as it gets angry if you go too far.

Have added an intercept of the bell command at the screen level which I am hopeful will avoid having to emulate too much of the readline for interactive commands in our multiplexer.

The addition of the handling the bell sequent, as mentioned yesterday, actually does handle the issues caused by the command running in the screen process, which means all that emulation of the readline history state at the top level is not needed.

Will just add tests & is ready to merge, will fix interactivity.

I also want to look into adding a ESC[?25h (make cursor visible) sequence, if a command is interactive, so we know where the cursor is (currently hidden by default)