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
It would add significant dependencies, which is unfortunate. Perhaps we should instead provide easily copy/paste-able code that does it? Or maybe with lazy module loading in 1.17 it is enough to put terminal detection in its own package?
The text was updated successfully, but these errors were encountered:
I think deciding when to output color is going to vary between each downstream application. For example: What should the default be? Should they obey TERM=dumb and NO_COLOR? Should they have a flag to force color on? Should they also hook up a flag for any of this, like --color?
My vote goes for having a ready to use example people can copy from. We could perhaps make it a runnable example if we mock term.IsTerminal, and instead just link to pkg.go.dev in a comment.
Should we do terminal detection automatically? See e.g. tailscale/depaware#11.
It would add significant dependencies, which is unfortunate. Perhaps we should instead provide easily copy/paste-able code that does it? Or maybe with lazy module loading in 1.17 it is enough to put terminal detection in its own package?
The text was updated successfully, but these errors were encountered: