-
Notifications
You must be signed in to change notification settings - Fork 0
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
How should terminal metadata be exposed? #9
Comments
Regarding I'm definitely against names |
a boolean flag for if color is supported ignores that some terminals support different amounts of color detail. for example, the npm package |
Terminal metadata idea from this #1 comment.
CLI.terminal.noColor
) or bare in the namespace (egCLI.noColor
)?CLI.terminal.noColor()
) or getters (egCLI.terminal.noColor
)?interactive
,isInteractive
,interactivity
,nonInteractive
,notInteractive
,tty
,isTty
,isTTY
,terminal
,isTerminal
,inTerminal
isatty(...)
function, but now is moving toisTerminal
.noColor
,color
,colorful
,hasColor
,shouldColor
noColor
as it is essentially an opt-out preference;color
could imply the user wants color which could not be true (rather thanNO_COLOR
stating the user explicitly does not want color). Also, this would then share the name of the environment variable "standard".Deno.noColor
) afaik, other runtimes you have to handle it yourself (eg!!process.env.NO_COLOR
).The text was updated successfully, but these errors were encountered: