-
```
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…
-
On crashes we show stack traces. They are quite unreadable.
We can make them better using:
https://github.com/erlang-lager/lager#exception-pretty-printing
And maybe colored output:
https://gi…
-
For .js files (with `allowJs: true`) glint is emitting exports like `export const foo: Foo`, instead of `export declare const foo: Foo` (which you have test coverage for), that causes jscodeshift to t…
-
```
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…