Rose Thatcher

I really like the option to block or warn on invalid input! Would it be reasonable to set a behavior flag, like `m.textInput.Warning()', and let the validator logic flip it...

Does this issue still occur? Testing post- #324 seems to show no problems.

It seems that since `termenv` is detecting the pipe, it's getting rid of the ansi sequences to avoid spitting out trash to `tee`. There are ~two ways to fix this...

It looks like this is a limitation of the `termenv` package, which doesn't support querying the `screen` colorspace as it can be hooked up to multiple terminals with different color...

Pardon the dust! Adding a distinction is definitely useful, I'd love to get this updated soon but a few questions still remain. Currently spin is supposed to show both the...

So the ideal behavior is (correct me if I'm wrong): `--show-error` will output the accumulated buffer if the program doesn't end on `0`. (`stderr`) `--show-output` will display the accumulated buffer...

Was this a problem with version > 6.0, or just 7.1? Do you have a repo with at least your `View`? Does this happen on a fresh Kitty install?