Hot answers tagged


He was probably using Byobu:


Your assessment is correct, the program running within the scrollback-mode window is stopping because its output buffer is full and it is suspended waiting to write. This behavior is both correct and desirable; the user entered scrollback mode to view the screen contents but as you have noticed, this is not convenient nor obvious when the session is detached....


You have a couple of options... You can pass the ctrl-a through to vim by pressing ctrl-a then a again. You can switch byobu to use what we call emacs mode, where ctrl-a is not used as an escape (instead, the F12 is your escape). You can do this by running byobu-ctrl-a emacs You can change byobu's escape sequence entirely using F9 and selecting 'Change ...


When using tmux, you can write a setup script using shell, like this: byobu-tmux new-session -d vim byobu-tmux new-window bc byobu-tmux new-window bash byobu-tmux new-window sh The new session will be run in the background. If you want to attach to the new session right after it was created, add byobu-tmux attach in the end. You can even add these ...


You could open up a second connection to an other tty. Then you could use Ctrl+a,k to kill the screen window you are trapped in. To prevent this from happening for consecutive sessions you can define the escape character to e.g. Ctrl+e: # lxc-console -e '^e' -n containername

Only top voted, non community-wiki answers of a minimum length are eligible