Is there a reason for my local pytest run to die right after I Ctrl-b z? Is there a signal that is sent and not catched by the tmux server and thus, somehow killing my pytest? (I think running the pytest in a non-tmux terminal, Ctrl-b z won't do a thing though I couldn't confirm that yet)

The same happens when trying to resize a pane (i.e. Ctrl-b Press-Down-Arrow)


When tmux resizes it will ask the kernel to send SIGWINCH to the processes in the pane, it sounds like your application is not handling it correctly and is crashing or exiting.

  • I'm testing it right now. Is there a way to envelop my pytest run (i.e. my application) in a 'ignore sigwinch' closure? – CIsForCookies May 27 '19 at 15:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.