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

[BUG] Readline history + Ctrl+C behaves differently than bash #135

Open
itislu opened this issue Jan 31, 2024 · 0 comments
Open

[BUG] Readline history + Ctrl+C behaves differently than bash #135

itislu opened this issue Jan 31, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@itislu
Copy link
Collaborator

itislu commented Jan 31, 2024

If you go back more than one input line in the readline history and then hit Ctrl+C, the initial behavior is correct.
However, if you then press the DOWN arrow key, the input line that appears is the one below where you hit Ctrl+C.

It means you are still in the same position in the readline history, even after pressing Ctrl+C.

Maybe this can be fixed with one of the terminal manipulation functions.
It might be interesting to learn more about them in the process.

@itislu itislu added the bug Something isn't working label Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant