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

[Bug]: 8.16.0 does not respect --no-color option #6589

Closed
1 task done
rasa opened this issue Nov 26, 2024 · 4 comments · Fixed by #6594
Closed
1 task done

[Bug]: 8.16.0 does not respect --no-color option #6589

rasa opened this issue Nov 26, 2024 · 4 comments · Fixed by #6594
Labels

Comments

@rasa
Copy link
Contributor

rasa commented Nov 26, 2024

Kind of Issue

Runtime - command-line tools

Tool or Library

cspell

Version

8.16.0

Supporting Library

No response

OS

Linux

OS Version

Ubuntu 24.04

Description

$ node --version
v22.11.0
$ cspell --no-color --no-default-configuration --config empty.json
Still see color
even tried
export NO_COLOR=1
and it's still in color. See https://no-color.org/

Also, the dark red is unreadable. Can this be bright red instead? Or some other readable color?

Steps to Reproduce

$ cspell --no-color --no-default-configuration --config empty.json ...

Expected Behavior

Non-colored output.

Additional Information

Tried other versions of node, and cspell. They all appear broken.

cspell.json

{
  "$schema": "https://raw.githubusercontent.com/streetsidesoftware/cspell/main/cspell.schema.json",
  "version": "0.2"
}

cspell.config.yaml

none

Example Repository

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@rasa rasa changed the title [Bug]: [Bug]: 8.16.0 does not respect --no-color option Nov 26, 2024
@Jason3S
Copy link
Collaborator

Jason3S commented Nov 26, 2024

@rasa,

Thank you. That had been working. I'll find out why it stopped.

@rasa
Copy link
Contributor Author

rasa commented Nov 26, 2024

@Jason3S Thanks for the quick fix! Much appreciated.

@Jason3S
Copy link
Collaborator

Jason3S commented Nov 26, 2024

@rasa,

No problem. It was a regression.

Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants