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
When running examples/autocompletion.py, if I attempt to complete an animal starting with 't', the options are 'turkey' and 'turtle'. In this instance, I would expect 'tur' to be filled in before I start tabbing through the options, but instead it cycles immediately to 'turkey', then 'turtle', then back to 't'.
It's unclear to me what the intended behavior of this is. There appears to be code to do this in interface.py (insert_common_part), and it looks like this variable is getting set to True, but the code that does the insertion never seems to get hit.
For reference, I'm using Python 2.7 on Windows 10.
The text was updated successfully, but these errors were encountered:
I just took another look at this. The problem seems to be that pushing 't' immediately brings up the completions menu, so the first tab starts cycling through it. If I push another letter then backspace, the completion box goes away, and pushing tab fills in the common prefix as expected (but again shows the completion box immediately, counter to the description in the module docstring for examples/autocompletion.py).
When running
examples/autocompletion.py
, if I attempt to complete an animal starting with 't', the options are 'turkey' and 'turtle'. In this instance, I would expect 'tur' to be filled in before I start tabbing through the options, but instead it cycles immediately to 'turkey', then 'turtle', then back to 't'.It's unclear to me what the intended behavior of this is. There appears to be code to do this in interface.py (
insert_common_part
), and it looks like this variable is getting set to True, but the code that does the insertion never seems to get hit.For reference, I'm using Python 2.7 on Windows 10.
The text was updated successfully, but these errors were encountered: