fzf VS tinytestlib

I first used jethrokuan/fzf: Ef-🐟-ient fish keybindings for fzf (github.com) jethrokuan/fzf for some time, but while it does the job done at offering a fuzzy frontend to the fish completion engine, it's not very flexible and does not allow you to extend/add completion logic.

I wrote something like this but in Bash https://github.com/pmarreck/tinytestlib but since this accomplishes my own design goals of being able to assert on all 3 things at once (stdout, stderr, return/exit code), and since I have a thing for Awk, and since you can also embed this in a Markdown, I kind of like this better

I actually used a variation on that stackoverflow answer to implement a simple as possible bash testing library where you can assert on stdout, stderr and returncodes (which all had to be gathered from 1 command invocation)

I've been trying to learn Nix, NixOS (incl. writing my own derivations), play with Phoenix's LiveView (which has already been out for a while), play with Elixir's Nx library for machine learning stuff, play with https://livebook.dev/ which now has ML hooks, come up with a use case for GraphQL so I can at least stick it on a resume (I understand it in principle but not in practice), make Bash saner by writing my own testing library for it which still needs polishing so it is incredibly easy to include in another bash script https://github.com/pmarreck/tinytestlib, code a Discord bot to DJ my cross-country gaming sessions with a best friend (I have one working but I need to hack on it more), learn more about ZFS and tuning it (I boot off it), stay on top of Linux developments, stay on top of Postgresql developments (perhaps investigating immutable-data/event-log schemes that play nice with it to maybe work with a security audit requirement in an app I'm responsible for)...

AND THAT'S JUST OFF THE TOP OF MY HEAD. ;)

I made the mistake last year of falling in love with xs-shell, talking to its maintainer (who recently put xs out to pasture, as it were) who is now moving all his stuff to es-shell, switching my romance to es-shell, merging in 2 forks of it to my own version https://github.com/pmarreck/es-shell/ aaaand having a kid and basically running out of time.

This shell makes a ton more sense to my brain than the usual bash/zsh/fish rigmarole, it just needs some love.

The last thing I was working on was a way to capture all of stdout, stderr and return code from a single run of a command, for testing purposes, because the OTHER thing es-shell desperately needs is a proper test suite. I figured one out for bash https://github.com/pmarreck/tinytestlib but not one for es yet.