-
Notifications
You must be signed in to change notification settings - Fork 283
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
using the history to show older command doesn't clear output in cmd.exe, so parts of older and longer commands still show in cmd.exe #301
Comments
I've seen this on and off but never been able to get a repro when I'm in a position to investigate it. I really thinks it's dependent on environment like buffer size and cursor position as well as long lines in the history. How did you navigate the history to cause this redraw issue (i.e. what keypresses)? What is the console's buffer size (you can run "mode" to find out)? |
Here is the output:
I used the arrow keys on my keyboard to browse for older commands. |
Where you able to repro this and do you have any idea how to fix this? |
Yes, thanks, I am now able to reproduce this. There's a bug in Clink's handling of termcap requests from Readline, but I'm not sure of the fix yet as I'm getting unexpected values from Readline. |
thanks. Can we please get a new dev version, so that I can test the fix? |
thanks. I've installed that version now and I'll test it. |
It looks like the dev version fixed the issue. |
using the history to show older command doesn't clear output in cmd.exe, so parts of older and longer commands still show in cmd.exe:
The command ends at
.man
but still shows parts of an earlier command:The text was updated successfully, but these errors were encountered: