Problems with input()::read_line() on version 5.1 about crossterm HOT 9 CLOSED

Thanis for letting me know I'll be one it...

from crossterm.

I have the same problem though, so it is not a problem you only have. One thing to note is that when using git bash on windows the output was correct. However, when using cmd I had the same problems.

from crossterm.

Oke, I solved part of the problem. However I need to do some more work to make it work correctly. I would suggest to use the std::io::Stdin::read_line() instead of crossterm readline. I will be working on this and have the fixes released a soon as possible.

from crossterm.

If you are not able to replicate this issues (it may be localized thing) let me know and I'll send you some screen recordings.

from crossterm.

@GarkGarcia Did you enable with crossterm raw modes for your terminal? And could you provide some code that reproduces this?

from crossterm.

Sure, here's my code:

extern crate crossterm;

use crossterm::{terminal::{terminal, Terminal}, input};

fn main() {
    let prompt = terminal();
    read_input(&prompt);
}

fn read_input(prompt: &Terminal) {
    match input().read_line() {
        Ok(input) => { /* Do some stuff */ },
        Err(_) => prompt.write("Bad stuff")
    }
    read_input(&prompt);
}

I didn't enabled raw modes, in fact I don't even know what they are... Am I messing something up?

from crossterm.

Is this fixed then, or will the fixes come out in version 5.2?

from crossterm.

Sorry, it took this long to fix this issue, I had some other crates to maintain. I will release a new version as soon as possible and put my priority on it. Version 0.6 will be the next one. I also have some other changes for the new feature so 5 or 6 days should everything be finished.

Does this issue have priority for you? You might want to fork the master branch and use that as a dependency since it has the fixes of this issue.

from crossterm.

Yeah sounds fine.

from crossterm.