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

Backspace behavior is incorrect on Windows in cooked mode #9

Open
alexrp opened this issue Mar 17, 2020 · 2 comments
Open

Backspace behavior is incorrect on Windows in cooked mode #9

alexrp opened this issue Mar 17, 2020 · 2 comments
Labels
area: drivers Issues related to the terminal drivers. area: interaction Issues related to user interaction. os: windows Issues that are specific to Windows (10, 11, etc). state: blocked Issues that are blocked on some other issue or work.
Milestone

Comments

@alexrp
Copy link
Member

alexrp commented Mar 17, 2020

When switching to virtual terminal mode, it seems that the behaviors of Backspace and Ctrl-Backspace are swapped.

More details in: microsoft/terminal#4949

@alexrp alexrp self-assigned this Mar 17, 2020
@alexrp alexrp added os: windows Issues that are specific to Windows (10, 11, etc). state: confirmed Bugs that have been confirmed and are reproducible. type: bug labels Mar 21, 2020
@alexrp alexrp added area: interaction Issues related to user interaction. state: blocked Issues that are blocked on some other issue or work. area: drivers Issues related to the terminal drivers. and removed state: confirmed Bugs that have been confirmed and are reproducible. labels Jun 15, 2021
@alexrp alexrp changed the title Backspace behavior is incorrect on Windows Backspace behavior is incorrect on Windows in cooked mode Nov 24, 2021
@alexrp alexrp added this to the v2.0 milestone Dec 20, 2021
@xoofx
Copy link

xoofx commented Dec 30, 2021

Hey,
Just discovered your library and it's greatly designed!

I found one issue probably related to this issue. While trying this program:

Terminal.OutLine("Type some text:");
while (true)
{
    var line = Terminal.ReadLine();
    if (line == null) break;
    Terminal.OutLine(line);
}

In CMD, the input seems to not always work on enter, sometimes it happens straight, sometimes it happens after the first inputted line.

Could be that ENABLE_VIRTUAL_TERMINAL_INPUT is also messing around for that case, I haven't investigated what's exactly received by ReadLine.

@alexrp
Copy link
Member Author

alexrp commented Dec 30, 2021

That's most likely unrelated and could be related to the recently-added cancellation support.

Would you mind filing a separate issue with more info? (Library version, Windows version, etc.)

@alexrp alexrp modified the milestones: v2.0, v3.0 Oct 28, 2022
@alexrp alexrp modified the milestones: v3.0, Future Jan 1, 2024
@alexrp alexrp removed their assignment Jan 27, 2024
@alexrp alexrp removed the type: bug label Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: drivers Issues related to the terminal drivers. area: interaction Issues related to user interaction. os: windows Issues that are specific to Windows (10, 11, etc). state: blocked Issues that are blocked on some other issue or work.
Development

No branches or pull requests

2 participants