This should teach anyone that tackling something that's considered "the basics" is not a bad idea. It is astounding how these really simple things can still be enhanced (or even revolutionised ;)) in 2020.
Can you please elaborate? Is that specifically because nnn[1] doesn't show a complete overview of the filesystem or some other features are missing?
One of the guiding principles of nnn is to generate minimum disk IOs.
Reading through a complete volume on a stuffed microSD or SD card attached to a RaspberryPi to list the filesystem (even if compacted) and then supporting filesystem changes dynamically is resource-intensive. nnn development is driven by minimum resource availability and usage.
It simplifies a lot of workflows and reduces the number of keys.
disclaimer: my definition of "devops" is sitting in a remote terminal for where I run docker and chasing down which files take up all my precious space, or not remembering where I put something, which makes the tree overview very useful. I know I could achieve this via many other means also (and did before Broot), but Broot is also very pretty, so I quite like that, too :)
It's the keybind "S" with nnn (or "A" for apparent usage). You can also use the same option ("-S") to open nnn in du mode.
> the overview of multiple directories at once
I explained the nnn design strategy in my other response
> the gitignore handling
This can be added but it changes the current generic way of handling directory entries
> There might be more, but I would have to spend more time with it
That would actually be a constructive data to improve nnn as well.
Thanks for the notes!
I like how 'on the ball' you are with this though, it's that kind of passion that makes projects like nnn so strong!