tree | less tree | lessShow me files in this dir:
$ n
Show/hide details for each: .
Filter / search file list: /
Navigate subdirs (or parents) with vim or arrow keys.Cd into sub dirs by typing unique chars from dir names:
ctrl-n
Drop back to shell i started n from but cd into this new dir: ctrl-g
Exit n without cd’ing to the new dir i navigated to: q
https://github.com/craigjperry2/dotfiles/blob/main/dotfiles/...Although for deeply nested targets where i already know what im after, i’ll just:
vim<ctrl+t>
To launch an fzf fuzzy finder on the (.gitignore aware) results of an “fd” (cross platform alternative to gnu and bsd find)It seems like they even have a neovim plugin, you might consider using it.
That said, i don't find myself using that as much. Usually i'm in the shell when i invoke nnn - i might open a file in vim from nnn though.
In vim, i typically lean on fzf.vim more often - usually i know something about the next file i want to open so it just feels more direct.
Edit: That and the speed. And since I am more proficient with Python, hacking on Ranger is easier.
But - if you're happy with ranger, i'm not sure it's worth the switch - they're very similar. nnn is quite a bit faster than ranger but other than that, i think ranger has more community support.
Shameless plug but I'd written my own $SHELL callewd `murex` as I kept running into pain points with Bash as a DevOps engineer. The shell doesn't have `tree` inbuilt but it does have FZF-like navigation built in.
https://github.com/lmorg/murex
I've been using it as my primary shell for a few years now and I'm not going to pretend that it isn't BETA it does work. However it's not POSIX and some of the design decisions might rub people the wrong way (given how opinionated peoples work-flows are). But if you're curious then check it out.