-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
tty detection for mintty #10
Comments
Absolutely! It never amazes me how complicated windows makes solving this seemingly simple problem |
BurntSushi
added a commit
to BurntSushi/atty
that referenced
this issue
Jan 8, 2017
This improves the tty detection in MSYS terminal environments on Windows. Specifically, it uses heuristics to determine whether a standard handle is a pipe or a tty. Behavior in normal Windows consoles remains unchanged. Fixes softprops#10
BurntSushi
added a commit
to BurntSushi/atty
that referenced
this issue
Jan 14, 2017
This improves the tty detection in MSYS terminal environments on Windows. Specifically, it uses heuristics to determine whether a standard handle is a pipe or a tty. Behavior in normal Windows consoles remains unchanged. Fixes softprops#10
BurntSushi
added a commit
to BurntSushi/atty
that referenced
this issue
Jan 14, 2017
This improves the tty detection in MSYS terminal environments on Windows. Specifically, it uses heuristics to determine whether a standard handle is a pipe or a tty. Behavior in normal Windows consoles remains unchanged. Fixes softprops#10
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Over time, ripgrep has grown its own tty detection code which includes a hack for (seemingly reliably) detecting the presence of a tty on Windows inside mintty. Would you be interested in a PR that brings it to this crate?
There isn't much code, but you can see it all here: https://github.com/BurntSushi/ripgrep/blob/master/src/atty.rs
There is a pretty long issue on the topic of mintty detection here, which includes the provenance of the hack: BurntSushi/ripgrep#94 --- Spoiler alert: it's what
git
does.The text was updated successfully, but these errors were encountered: