-
Notifications
You must be signed in to change notification settings - Fork 18k
x/term: Why IsTerminal reports true
on redirected stdout
? [unrelated]
#42003
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
Comments
Your program doesn't compile:
When I fix that, the program behaves as I expect:
Show us a way to reproduce the problem. |
Updated |
Really. I am on Darwin macOs in a Zsh shell. There it happens. |
I will provide more infos! |
@gabyx I am using darwin with zsh, I cannot reproduce your findings
|
Thx for that report. I will investigate later in 2 days
Von meinem iPhone gesendet
… Am 16.10.2020 um 08:10 schrieb Dave Cheney ***@***.***>:
@gabyx I am using darwin with zsh, I cannot reproduce your findings
(~/src) % go build term.go && ./term | tee log.out
(~/src) % cat log.out
(~/src) % go build term.go && ./term > log.out
(~/src) % cat log.out
(~/src) %
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sorry for your precious time. I mistakenly used the compiled code under a hook invoked by This works fine. |
true
on redirected stdout
?true
on redirected stdout
? [unrelated]
What version of Go are you using (
go version
)?1.15.2
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
and run it with
./run 1> Log.txt
.What did you expect to see?
No output in Log.txt because
stdout
is redirected?What did you see instead?
Is Terminal
in Log.txtThe text was updated successfully, but these errors were encountered: