Andreas Klöckner

Thanks for following up. Maybe we can just steal spyder's approach given that it seems to allow stepping in and out of generators even when pdb does not. [Here](https://github.com/spyder-ide/spyder/blob/a282a4fdf79b85e769f2c5850b22f436ca04d774/external-deps/spyder-kernels/spyder_kernels/customize/spyderpdb.py) is...

The "o" key for "view output" should probably just be disabled during remote/telnet debugging (since you're already seeing the program output somewhere else).

Are you meaning to use remote debugging at all? It seems like you're confused. Try `from pudb import set_trace`.

You could stat the config file.

I was more suggesting noticing a non-writable config file in $HOME and warning about it.

The capability doesn't currently exist. As a matter of personal need, it's not something that I would use a lot, but I wouldn't object to a PR.

I'd be happy to consider a PR. One question is whether this should switch the whole config directory, which also stores histories, breakpoints and such.

I should preface this by saying that getting terminal sizes for remote pudb is not an actually solvable problem, AFAICT. All that we have is heuristics. This is the current...

Yep, that's the assumption. The idea behind the heuristic is that you have both running in two tabs of the same terminal.

Thanks for the report! With Py2 less than a month from EOL, I'm happy to take a patch, but I probably won't go debug myself.