4.11.4 Assigning copy and paste actions to clipboards.4.11.2 ‘Shift overrides application's use of mouse’.4.11.1 Changing the actions of the mouse buttons.4.10.6 Combining VT100 line-drawing with UTF-8.4.10.5 Controlling copy and paste of line drawing characters.4.10.4 Controlling display of line-drawing characters.4.10.3 ‘Caps Lock acts as Cyrillic switch’.4.10.2 ‘Treat CJK ambiguous characters as wide’.4.10.1 Controlling character set translation.4.9.5 ‘System menu appears on Alt alone’.4.9.4 ‘System menu appears on ALT-Space’.4.8.3 ‘Hide mouse pointer when typing in window’.4.8.2 Controlling the font used in the terminal window.4.8.1 Controlling the appearance of the cursor.4.7.4 ‘Push erased text into scrollback’.4.7.2 What to do when the window is resized.4.7.1 Setting the size of the PuTTY window.4.6.11 Disabling bidirectional text display.4.6.9 Disabling remote character set configuration.4.6.7 Disabling remote scrollback clearing.4.6.6 Response to remote window title querying.4.6.5 Disabling remote window title changing.4.6.4 Disabling switching to the alternate screen.4.6.3 Disabling remote terminal resizing.4.6.2 Disabling xterm-style mouse reporting.4.6.1 Disabling application keypad and cursor keys.4.5.3 ‘Control the bell overload behaviour’.4.5.2 ‘Taskbar/caption indication on bell’.4.4.9 ‘Control-Alt is different from AltGr’.4.4.6 Controlling Application Keypad mode.4.4.5 Controlling Application Cursor Keys mode.4.4.4 Changing the action of the shifted arrow keys.4.4.3 Changing the action of the function keys and keypad.4.4.2 Changing the action of the Home and End keys.4.4.1 Changing the action of the Backspace key.4.3.5 ‘Use background colour to erase screen’.4.2.5 Options specific to SSH packet logging.4.2.2 ‘What to do if the log file already exists’.4.1.2 Loading and storing saved sessions.You simply need to log back in via SSH then screen -ls and screen -x back into your session. If your network drops out your operations won't be lost! Since screen is running on the server. A great thing about this and something I've dealt with a lot as a System Administrator - network connectivity. You can't use your scroll bar in Screen you have to use buffer controls to roll back, however the above is enough to get you started to see if this is a viable option. There are a whole slew of options available for Screen you should pour over the man file for more. Lastly to list all windows open you can type Ctrl + A then ". Finally you can close tabs by using Ctrl + A then k which will kill that tab (if it locks up) but typically you can just type exit as if you were in a terminal and it will close that tab. If you want to exit screen but keep it running use Ctrl + A then d which will detach your session. You can open a maximum of 60 tabs per screen session.
You'll notice the footer has (LOAD) 0-$ bash 1$* bash which shows that there is another tab open and the active tab is number 1. All commands are started with this combination. Type something then Press this Key Combination: Ctrl + A release, then press c. Which is the servers load and a list of all open "terminal tabs". screenrc file) You'll see the following along the bottom: Once you're in a Screen (and you've employed my sample. Screen -x - This will resume a Detached screen session, IE: screen -x 16467 Yes you can have multiple terminals inside multiple screens. Screen -ls - List all active screen sessions.
Next install screen on the remote machine ( sudo apt-get install screen) Next you'll want to fire it up here are some commands for "firing up screen": screenrc save it on the remote server in your users home folder. You've got a lot of learning of commands to setup a successful Screen environment. GNU Screen is the answer you've been looking for - but it's a lot like Vi.