You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i add one line in ipdb main.py _get_debugger_cls to use command vi mode when debug ipdb.set_trace, and this work good in linux
def_get_debugger_cls():
shell=get_ipython()
#shell=NoneifshellisNone:
# Not inside IPython# Build a terminal app in order to force ipython to load the# configurationipapp=TerminalIPythonApp()
# Avoid output (banner, prints)ipapp.interact=Falseipapp.initialize(["--no-term-title"])
shell=ipapp.shell######################add lineshell.editing_mode='vi'else:
but when i do same thing in windows , vi mode prompt broke, and print some char like ?[6 qipdb> list?[2 q?[2 ?[2 q
it look like some cursor control escape char i think....
and this both happen in cmd and powershell , but when create cmd in ConEmu , ipdb vi mode work great
is there some config i set wrong ?
or other nomal way to config vi mode in ipdb?
The text was updated successfully, but these errors were encountered:
i add one line in ipdb main.py
_get_debugger_cls
to use command vi mode when debug ipdb.set_trace, and this work good in linuxbut when i do same thing in windows , vi mode prompt broke, and print some char like
?[6 qipdb> list?[2 q?[2 ?[2 q
it look like some cursor control escape char i think....
and this both happen in cmd and powershell , but when create cmd in ConEmu , ipdb vi mode work great
is there some config i set wrong ?
or other nomal way to config vi mode in ipdb?
The text was updated successfully, but these errors were encountered: