telescope-repo.nvim VS dirbuf.nvim

For the cases you describe: To move between "projects", take a look at telescope-repo or project.

If you really need to keep a list of editable files, I don't think there's a built-in for that. You could either try: - making your own picker (maybe telescope-repo could serve as an inspiration); - maintain a list of symlinked files into a directory and find_files from there.

GitHub prohibits embedding arbitrary scripts for security reason. But what if you want to embed an asciinema player on your project homepage, so that users can play the asciicast as they would a standard video? You can have a placeholder with the link on GitHub as asciinema documentation advises and then use RISS to replace it with the full player on your website. You will find how to do that in the documentation. Plus, here is an example README this one doing this (and the corresponding website, look for the asciicast that autoplays).

For me I think it’s the best at what it does (with mini.files coming in a close second. It would probably be my first, but I prefer the whole buffer approach over the floating popups.) I’ve tried dirbuf.nvim as well, but I didn’t like that I couldn’t copy/move files.

Big fan of https://github.com/elihunter173/dirbuf.nvim

Shout-out to dirbuf.nvim as it is one of my favorite plugins I cannot live without, but I see it rarely mentioned. It allows you to do file management by editing a file, so you can do anything you would do to edit any regular file. There are no new keymaps to learn, you just use any regular motion, :s, :g, or anything you can think of. Great for bulk renaming!

While I do use file managers often (ranger and dolphin are pretty nice overall), within Neovim my file management is fairly reduced. I use dirbuf when I need to browse through files (for refactors or something), and since it's dired-like its a lot more built into the "vim-as-a-language" mindset. Not to say I do a whole lot in it, but it is quicker than having to do shell stuff within Neovim. I think file-tree plugins tend to just miss the concept for me, as I never found them to be anything more than just "look and see" due to disconnect from the aforementioned "vim-as-a-language"

https://github.com/elihunter173/dirbuf.nvim, it's basically netrw done right.

https://github.com/elihunter173/dirbuf.nvim might just be the thing. In terms of navigating it's as minimal as it can be:

I use fish shell with z plugin to quickly jump to directories and nnn file manager mainly to select files for deletion. I also use dirbuf plugin for neovim when working inside this editor.

dirbuf.nvim!

dirbuf mostly. Anything really advanced and I'll just open a new ranger session

dirbuf doesn't get enough attention. It's a robust, simple, yet featureful replacement for the netrw plugin built into Vim/NeoVim. It allows directories to be treated somewhat like files - edit a directory, and you get a directory listing. That listing can be modified - add files, edit files, delete files, and the result ends up on disk. A much simpler and more-Vimy alternative to tree plugins like NeoTree, in my view.