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
History reversed with older prompt_toolkit #13634
Comments
I think this is related to #13631 (or it is the same issue). I don't think the prompt-toolkit versions mattered there though. |
I've had a similar issue where the command history would appear in reverse order, from oldest to newest. Likewise, it started with the latest update to IPython 8.2.0, and upgrading prompt_toolkit seems to have solved the issue. |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
Same here with 8.4.0. Upgrading |
Also have a similar issue. Using python 3.8.6, ipython 8.4.0 in windows 10. I have prompt_toolkit version '3.0.29'. I see two problems
Downgrading to v8.0.0 also resolves it for me |
Same problem and no solution :\
|
I've had a similar issue and it was fixed after I updated prompt-toolkit: version 3.0.30 and version of ipython 8.4.0 |
When using an older version of
prompt-toolkit
(3.0.7), history does not work correctly.Upon opening ipython, both when scrolling with the arrow keys and searching, a second copy of it appears, in reversed order. This does not affect the actual history file, only how it looks in this environment.
Example:
real history
apparent history
Then upon entering another command the first half vanishes, leaving only the reversed, with no new entries being added
apparent history
The new history is added to the file as usual, but not displayed.
Environment:
prompt-toolkit
version: 3.0.7The issue is not present with the latest
prompt-toolkit
: version 3.0.29, or with versions ofipython
before 8.2.0If bumping the dependency version is viable, it seems like the easiest fix.
The text was updated successfully, but these errors were encountered: