-
Notifications
You must be signed in to change notification settings - Fork 184
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
Moving the cursor wipes out next lines #48
Comments
Ok, |
@gwenn yes, I think that is the right strategy. Even better might be to take a rectangle or bounding box as a parameter. I also don't think that the prompt should write anything to output. This can be done by application code and separates concerns. |
What I mean about writing to stdout is to not write the prefix or the line ending. That gives a lot more flexibility to the code consuming the library. For example if I want to have "\r\n" rather "\n" as the EOL. |
Just so I fully understand, you want the following line to be removed: println!(""); ? |
@gwenn yes, I think that line should either be removed, or the readline function should at least take an argument to allow for cross platform line endings. Thank you for your help. |
Are you sure |
And do not ignorespace by default. And do not panic when the history is empty
And do not ignorespace by default. And do not panic when the history is empty
No. I am more concerned with how it inter-operates with termion. I am going to open source the project I am using rustyline in, so I can give a link after I update the license. Also, I can open a new ticket to discuss line terminators if it makes sense to. |
The associated patch has been merged in master. |
Thanks! |
The library calls refresh in the cursor movement functions causing future lines to be wiped out. This is causing issues for a game I embedded the line editor in, because the bottom portion of the screen gets wiped if the user moves the cursor while entering a command.
The text was updated successfully, but these errors were encountered: