You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now on to my issue: I'm using stable Rust (stable-x86_64-pc-windows-msvc + rustc 1.14.0) and installed ripgrep using cargo install.
When running a basic rg --type cpp <pattern> and pressing Ctrl-C in the middle, cmd's foreground stays red/purple/whatever color was last printed. I haven't tried on Linux to see if this is really platform specific.
The text was updated successfully, but these errors were encountered:
TL;DR - There are significant trade offs for doing ^C handling, and IMO, screwing up the colors in the terminal (which is easy to fix by running echo -ne "\033[0m" or color on Windows I believe) is the least worst choice.
BurntSushi
added
doc
An issue with or an improvement to documentation.
and removed
wontfix
A feature or bug that is unlikely to be implemented or fixed.
labels
Feb 3, 2017
BurntSushi
changed the title
Keyboard interrupt doesn't restore the termcolor on Windows
document that keyboard interrupt doesn't restore the termcolor on Windows
Feb 3, 2017
Hi everyone,
First of all, great job on this. 👍
Now on to my issue: I'm using stable Rust (stable-x86_64-pc-windows-msvc + rustc 1.14.0) and installed ripgrep using
cargo install
.When running a basic
rg --type cpp <pattern>
and pressing Ctrl-C in the middle, cmd's foreground stays red/purple/whatever color was last printed. I haven't tried on Linux to see if this is really platform specific.The text was updated successfully, but these errors were encountered: