Ctrl-x not function to leave console

When attempting to make local calls in the console, pressing ctrl-x merely prints ^x rather than leaving the console. At this point, the only way out is to kill pudb. An interesting behavior is that this only happens after issuing a command in the console; ctrl-x works fine until then.

Details:
pudb version: 2015.4.1
installed with pip
running in osx 10.11.2 in iTerm2, Terminal, and Neovim's terminal mode

[inducer]

I can't reproduce this, so this likely has something to do with your setup. On Linux, with vte (gnome terminal), konsole, and xterm, this works just fine for me.

Can you try through both display drivers (raw/curses) in the pref screen and see if that helps?

Changing to curses seems to have fixed it. Thanks.

[nedbat]

I have the same reported behavior on Mac. I am using iTerm2.
^X gets me into the console, and another ^X will get me out of it. But if I type '1' to see the value 1 in the console, then ^X just echoes ^X, and I can't figure out a way to do anything but kill pudb.

[nedbat]

Switching to curses doesn't improve the console, and makes other things bad :(

[inducer]

^X used to have some flow control behavior. Can you turn that off in iTerm2?

[inducer]

(I think. Actually not 100% sure about that.)

[nedbat]

That doesn't sound right to me. The first ^X would have that effect then, but it doesn't. And the second ^X doesn't stop the flow, it just echoes ^X, and you can still type into the console window.

[inducer]

@asmeurer, you use (used?) iTerm2, I recall. Any clues?

[asmeurer]

It is working for me, but I am using the iTerm2 nightly build. But it also works for me in Terminal.app. What version of urwid are you guys using? I have 1.3.1.

[nedbat]

Full freeze output (only some of which is for pudb):

-e hg+ssh://hg@bitbucket.org/ned/coveragepy@f4001cd0cd5210e67ba8ba2e15c9bc362a001e2e#egg=coverage
covtestegg1==0.0.0
decorator==4.0.9
eventlet==0.19.0
gevent==1.1.1
greenlet==0.4.9
mock==2.0.0
nose==1.3.7
pbr==1.10.0
pudb==2016.2
PyContracts==1.7.9
Pygments==2.1.3
pyparsing==2.1.4
six==1.10.0
unittest-mixins==1.0
urwid==1.3.1

[nedbat]

BTW, I tested using the Mac Terminal app also, and it behaves the same for me as in iTerm2.

[asmeurer]

Yeah me too, that is, it works in both.

In fact, I just tried using the guest user account on my Mac to install pudb fresh, using Terminal.app, so that everything is default settings, and I still can't reproduce this. Any guesses as to what might be causing it. I also tried fiddling with different $TERM settings, but it doesn't seem to matter.

[inducer]

@nedbat, whats your $TERM?

[nedbat]

xterm-256color

[inducer]

Is that what you have, @asmeurer?