-
```
Currently gtest determines whether to use colored output by checking the TERM
variable against a short list of known-good terminals. This list does not
include rxvt-unicode [1], so users of this…
-
```
Currently gtest determines whether to use colored output by checking the TERM
variable against a short list of known-good terminals. This list does not
include rxvt-unicode [1], so users of this…
-
```
Currently gtest determines whether to use colored output by checking the TERM
variable against a short list of known-good terminals. This list does not
include rxvt-unicode [1], so users of this…
-
```
Currently gtest determines whether to use colored output by checking the TERM
variable against a short list of known-good terminals. This list does not
include rxvt-unicode [1], so users of this…
-
```
Currently gtest determines whether to use colored output by checking the TERM
variable against a short list of known-good terminals. This list does not
include rxvt-unicode [1], so users of this…
-
```
Currently gtest determines whether to use colored output by checking the TERM
variable against a short list of known-good terminals. This list does not
include rxvt-unicode [1], so users of this…
-
```
Currently gtest determines whether to use colored output by checking the TERM
variable against a short list of known-good terminals. This list does not
include rxvt-unicode [1], so users of this…
-
```
Currently gtest determines whether to use colored output by checking the TERM
variable against a short list of known-good terminals. This list does not
include rxvt-unicode [1], so users of this…
-
https://no-color.org/
`NO_COLOR` is a standard for disabling color in terminal applications.
> By adopting this standard, users that prefer to have plain, non-colored text output can export NO_…
-
I usually have hooks on commit and push actions. When committing, lazygit ui hides, and shows only the output of the hook (linting process etc.) only, and if it gives an error you can see it clearly.
…