Aaron Meurer

Since, as I noted, you can't actually see the result of stdout/stderr unless the step takes a long time, would it be reasonable to just not switch screens until quit...

Ah, so stdout doesn't work unless the buffer is active. I wasn't sure. So we would have to buffer it.

And we're back full circle :) I guess my thought that we could never switch at all was based on the thought that you could write to stdout without switching...

Let me see if I can reproduce it.

I don't remember if I did more, but the place in the code that does this is at https://github.com/inducer/pudb/blob/master/pudb/debugger.py#L1342. I'm not sure why it uses an integer instead of a...

Might we have more control over the situation when PuDB is run on a script (as opposed to a `set_trace`)? We could then run everything through `subprocess` for example.

Interesting. For me, the flashing is really bad in iTerm2 and Terminal.app, but when using tmux in Terminal.app, it's not bad (basically doesn't happen at all unless something is printed...

I sent an [email to the iTerm2 mailing list](https://groups.google.com/forum/#!topic/iterm2-discuss/quYia5K_-ZA).

I believe Terminal has a setting regarding sending backspace as Ctrl-H. No idea about the rest of tmux. You'll have to look that up.

Thanks to @gnachman, this is no longer an issue in iTerm2 https://gitlab.com/gnachman/iterm2/issues/4123 (and there's no need to use tmux). As long as the code run for each step is fast,...