New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Up arrow key history search gets stuck in QTConsole #2943
Comments
Can you provide specific reproduction steps? The relevant change is almost certainly #2819.
Not surprising, since there isn't a line of code in common wrt the input history (terminal is 100% readline, qtconsole doesn't involve readline). |
I think I figured it out. Try #2946. |
I just replaced the file from your commit but now actually up arrow only go up one history and then I'm stuck. |
I'm sorry, actually it might have caused by some left over files from previous installation of ipython. Let me remove them and try again. |
Again - the new commit only gives one previous history. Also when I delete everything and reinstall ipython from current master 48b63c1, the up arrow history did work as expected. I am afraid that it was caused by my mistake in the first place. I'm very sorry for wasting your time. |
I grabbed the wrong cursor object, try #2946 again. |
It is working well now :) |
@minrk Thanks a lot for this. |
EndOfLine may or may not mean the end of a full line when the line is longer than the window. This commit uses the same logic to check as the actual move, so it should be consistent. closes ipython#2943
With the ipython installed with with commit 50a5838, going through history with up arrow key in qtconsole works without any problem. But in current commit 48b63c1, in qtconsole, it gets "stuck" after several items - pressing up arrow key does not do anything. It seems to be happening when the currently showing history is longer than the qtconsole width.
Since there are more than 120 commits in between, I haven't tried to identify what was the commit which caused this.
Also, in terminal this does not happen.
The text was updated successfully, but these errors were encountered: