Skip to content
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

Closed
MagicAndre1981 opened this issue Mar 24, 2015 · 8 comments

Comments

@MagicAndre1981
Copy link

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:

Image of clink history issue

The command ends at .man but still shows parts of an earlier command:

PerfView /nogui userCommand DumpRegisteredManifest Microsoft-Windows-DotNETRuntime
@mridgers
Copy link
Owner

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)?

@MagicAndre1981
Copy link
Author

Here is the output:

Status von Gerät CON:
    Zeilen:          9999
    Spalten:         100
    Wiederholrate:   31
    Verzögerungszeit:1
    Codepage:        850

I used the arrow keys on my keyboard to browse for older commands.

@MagicAndre1981
Copy link
Author

Where you able to repro this and do you have any idea how to fix this?

@mridgers
Copy link
Owner

mridgers commented Apr 3, 2015

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.

@MagicAndre1981
Copy link
Author

thanks. Can we please get a new dev version, so that I can test the fix?

@mridgers
Copy link
Owner

mridgers commented Apr 7, 2015

@MagicAndre1981
Copy link
Author

thanks. I've installed that version now and I'll test it.

@MagicAndre1981
Copy link
Author

It looks like the dev version fixed the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants