Do not filter COLORTERM

[equal-l2]

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes? Here's an example.
• Have you successfully run brew style with your changes locally?
• Have you successfully run brew typecheck with your changes locally?
• Have you successfully run brew tests with your changes locally?

---

COLORTERM can be used by editors, which are called by brew edit.

[MikeMcQuaid]

COLORTERM can be used by editors

Which editors? What does it do?

[equal-l2]

In fact, any program can make use of COLORTERM to check if the terminal supports truecolor, like using TERM to check the capability.
I used "editors" as an example because my .vimrc uses the env variable to check the truecolor support and switch features.

[MikeMcQuaid]

In fact, any program can make use of COLORTERM to check if the terminal supports truecolor, like using TERM to check the capability.

Any program can use any arbitrary variable, sure.

I used "editors" as an example because my .vimrc uses the env variable to check the truecolor support and switch features.

So in this case you mean it's actually just your local configuration? If so, set HOMEBREW_COLORTERM and check that instead.

Passing on this, sorry.

[equal-l2]

COLORTERM is a common environmental variable that is automatically set by terminal emulators, and is the de-facto way for programs to check if a terminal supports truecolor support.
https://github.com/termstandard/colors#checking-for-colorterm

Though I use that just for tweaking my editor, that is more potential.