Vitalio

Possible solution: ```patch diff --git a/fuzz.c b/fuzz.c index 398cae34..0e6919f9 100644 --- a/fuzz.c +++ b/fuzz.c @@ -255,8 +255,7 @@ static void fuzz_perfFeedback(run_t* run) { size_t tot_exec_per_sec = elapsed_sec ? (curr_exec_cnt /...

Our build system (on ALT) works purely on tmpfs and there is no other disks/filesystems. I currently settled on doing in `%check` script: ``` printf '6.6\n%s\n' $(uname -r) | sort...

Actually, why not let `filtering` in `choose`? Without switching modes by a magic key -- if user just started to type in `choose` it could start behaving like filter (w/o...

> Also, it seems like what you suggested from the comment is `gum filter` without the screen clearing which might be already possible by setting a certain `--height` (iirc), so...

Just to confirm this is still unfixed in `0.13.0`.

Thanks for looking it up! I see that `CLICOLOR_FORCE=1` env could be used to force colors. But, that's pity it does not work by default in 2023.

> Setting `COLORTERM` to an appropriate value (`true` or `truecolor`) would be enough to make it work. Thanks that's also good to know. > Alternatively start using `screen-256color` as your...

Or you meant I could set my `TERM` after `screen` and before script with `gum` run. I will look it up. Thanks! ps. But this will only fix issue for...

IC. Thanks for answer! I will run them with `cargo test ... -- --test-threads=1` (already tested to work OK).

Perhaps `60:69:60:4c:0a:aa` could be confused with a mac address, but this is just a nonce number which does not need to be extremely readable.