Open wonderbeyond opened 6 years ago
In some shells Ctrl+s
and Ctrl+q
pause and resume input and output so if the shell gets the keystroke instead of pymux
it will stop sending anything to the foreground process and this may cause the failure you are seeing.
I used to run into this frequently while working in vim
because switching between files in splits uses Ctrl+w
which is right between Ctrl+s
and Ctrl+q
.
I do some keystrokes I cant remember, then pymux stops responding.
After a minute, I killed the process. I can see a crash log: