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

How can I get the cursor position #201

Open
ShadowySpirits opened this issue Jan 22, 2024 · 1 comment
Open

How can I get the cursor position #201

ShadowySpirits opened this issue Jan 22, 2024 · 1 comment

Comments

@ShadowySpirits
Copy link

I found issue #38, but it only adds the function to move the cursor. Could someone help me with this?

@Joedang
Copy link

Joedang commented Jul 4, 2024

Well, I have a partial solution. Maybe someone who's more familiar with this library can get it across the finish line.

Partial solution

use console::Term;

fn main() {
    let term = Term::stdout();
    print!("\nsome filler text... please hit enter \x1b[6n");
    let response = term.read_line().expect("failed to read response");
    assert_eq!(response, ";38R"); // should be something like "\x1b[10;38R"
                                  // not sure why row info is being cut off

    term.clear_screen().expect("failed to clear screen");
    print!("\nsome filler text... please hit enter \x1b[6n");
    let response = term.read_line().expect("failed to read response");
    assert_eq!(response, "38R"); // not sure why clearing the screen matters
}

Explanation

Printing the escape sequence \x1b[6n requests the cursor position, and the terminal should respond by writing \x1b[Y;XR, where Y and X are the row and column.

As stated in man 4 console_codes:

ESC [ 6 n
       Cursor position report (CPR): Answer is ESC [ y ; x R, where x,y is the cursor location.

So, I would expect my partial solution to get a response like \x1b[10;38R. (Of course, the row would depend on the cursor position when print!() was called.) The row info is getting cut off and I'm not sure why. It also cuts off the ; if the screen is cleared before-hand, which is very confusing. (I tried throwing in some calls to term.flush(), figuring there was some race-condition going on between the terminal and the Rust program, but it didn't make a difference.)

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