I’m using split panes in tmux – one being vim, the other being a shell. Sometimes, around once a day, vim freezes. I can move between panes, perform any tmux commands, just vim doesn’t react to anything. This happens only with tmux. My only solution for now is to kill that pane and create a new one.
You might have hit Ctrl+S, which turns off flow control in terminals and stops the terminal from accepting input. It is reenabled by pressing Ctrl+Q.
-
6When you're just starting to use vim/terminal editors as your main editor, this is a very common problem. Later on, you'll end up having :wq spread throughout all your documents (or ZZ, I don't judge) and feel silly. – Rob Jul 29 '13 at 15:14
-
14Amazing how you correctly guessed the problem from such such a vague description. Thanks! – DBedrenko May 30 '14 at 8:00
-
7Holy ...! I've been having this issue for years, and never actually searched for a solution. This answer was the first solution I found, and it literally took me 3 seconds... All those hours wasted, and you had the solution just a couple of seconds away. I wish I could upvote you more (and downvote myself). Thanks! – simendsjo Oct 10 '14 at 21:29
-
Another time you might have this issue is when you're switching between editors (emacs and vim, for instance). They have different "save" commands, muscle memory confuses and hence the freezing. – Utkarsh Sinha Nov 11 '14 at 14:26
-
5and if it happens to be twice unlucky (a remote tmux session with C-q as prefix): Type
Cltr-q
, then:
, and enter in tmux:send-keys C-q
! – Paschalis Apr 14 '16 at 20:24
For me, this turned out to be a gpm problem. Run:
sudo service gym restart
See here for the related bug.
My story involved following
alias doodle='(f=$(mktemp); vim $f; echo $f)' # alias to quick edit a new file with whatever name
Now that I use this alias diff -u $(doodle) $(doodle)
vim said Vim: Warning: Output is not to a terminal
.
After that the terminal froze. Usual keys wouldn't help, e.g. Ctrl+Q, Ctrl-C, etc.
Pressing ZQ helped. It would exit the vim that you stuck in, but whos UI you can't see.
I guess vim
needs some flag (not figured out yet which) to show itself on screen when being executed from bach mode.
I hope it helps someone.
^
z
to put vim into the background too quickly afterwards. – svenper Jun 8 '17 at 14:56