Hello again @brianp 👋

Been using muxed constantly for the past few years and continue to love it! 💜

I was looking to revamp some of my tmux stuff recently and was getting annoyed with my sed hacks to get newline delimited results out of list 😆

So here is proper support for tty detection, as well as an option to force one item per line (following lss -1 options)

I was going to look into adding some test cases for that, but realized the first road block is that we don't have a great way to capture stdout in the tests, which makes it hard to write good tests for this list sub-command.

I've used assert_cmd for this in the past, but not sure if there are better options or ways of doing this. Another option I found is maybe extracting out the writing to stdout. Maybe by passing in a writer that can write to stdout for the binary and a buffer for tests? (https://users.rust-lang.org/t/how-to-test-output-to-stdout/4877/3)

My Example with assert_cmd: https://github.com/coreyja/devicon-lookup/blob/master/tests/strip_ansi.rs (Uses a 1.x version it looks like, just FYI)
Crate Docs: https://docs.rs/assert_cmd/2.0.2/assert_cmd/

Do you have thoughts on how you would like to do testing?

Fixes #53