This is interesting, but I like neither the TUI nor the fact that it's written in Python, lol. My idea was to have namespaced wrappers for the commands which w

This is interesting, but I like neither the TUI nor the fact that it's written in Python, lol. My idea was to have namespaced wrappers for the commands which were designed to generate output as JSON and/or accept input as JSON. So for example "ls" would have a wrapper "qls" (queryable ls) or maybe "jsls" (json LS), etc. But in thinking about it, many questions remain- Would some of the structs or struct elements have types, like "file_path" or "file_name" for example? Like for example they do: > $ jc dig example.com | jq -r '.[].answer[].data' and my API would be more like: > $ jsdig example.com -- '.[].answer[].data' (which would then pass those additional arguments to "jq -r" without having to pipe) The core idea is that you can have seamless integration of structured pipe data with regular piped data without having to change shells.