Skip to content
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

Terminal metadata: Exposition #13

Closed
CanadaHonk opened this issue Feb 7, 2024 · 1 comment
Closed

Terminal metadata: Exposition #13

CanadaHonk opened this issue Feb 7, 2024 · 1 comment

Comments

@CanadaHonk
Copy link
Member

  • Should we have a parent object (eg CLI.terminal.noColor) or bare in the namespace (eg CLI.noColor)?
  • Functions (eg CLI.terminal.noColor()) or getters (eg CLI.terminal.noColor)?
  • Interactivity:
    • Potential names: interactive, isInteractive, interactivity, nonInteractive, notInteractive, tty, isTty, isTTY, terminal, isTerminal, inTerminal
    • Deno used to have a isatty() function, but now is moving to isTerminal.
  • No color:
    • Potential names: noColor, color, colorful, hasColor, shouldColor
    • We should probably just use noColor as it is essentially an opt-out preference; color could imply the user wants color which could not be true (rather than NO_COLOR stating the user explicitly does not want color). Also, this would then share the name of the environment variable "standard".
@CanadaHonk
Copy link
Member Author

Duplicate of #9 🙈

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant