vim-rooter VS fzf.vim

This or users may have monorepo style projects and vim-rooter to auto-set cwd to specific directories within the project based on certain file markers (e.g. makefile, package.json, ...etc), to accomplish something like :e dir1/file.go | make would run make and then :e dir2/file2.ts | make would run npm.

maybe you are already doing this and you want to access files outside the project directory but if not I use vim-rooter to set the root dir of the project automatically when I open vim

The airblade/vim-rooter plugin is an essential part of my Neovim workflow. It automatically changes current directory (:h current-directory) for every buffer to a more natural one (like to path of its Git repository). For me this has the following benefits:

It depends where you open vim. If you are in home and open a file (even in sub directories) like nvim directory/file.txt, uour vim's current working directory (aka cwd) will be home. A way to make this automatic I think is the built in autocd (or something like that) and plugins like vim-rooter.

An alternative would be using a plugin like vim-rooter : https://github.com/airblade/vim-rooter

I just use rooter and avoid thinking about it...

There's vim-rooter, which is great.

No, it doesn't change current directory. For that, use sessions or airblade/vim-rooter (or wait around couple of months for planned 'mini.root' :) ). And, of course, you can create custom items which will change current directory.

Fuzzy Finder: fzf.vim (for its speed) along with telescope.nvim (for its ecosystem)

https://github.com/junegunn/fzf.vim

And added my keyboard shortcuts.

There are two plugins allowing us to use fzf in Vim: the native fzf plugin directly installed with fzf, and fzf.vim. The second plugin is built on the first one.

You might be interested in installing the fzf-vim plugin [0]. It has a user-defined command :Maps which can be used to search through all keybindings (you can also do this with just :nmap in vim, but the fzf interface is much nicer). It also provides :Commands. This behaves remarkably like VSCode's command palette.

[0] https://github.com/junegunn/fzf.vim

You'll also need https://github.com/junegunn/fzf.vim (which is imo the only vim plugin that's a must).

I do all my file operations from the command line. But to open and search files I use fzf

Regarding plugins , I am using https://github.com/Donaldttt/fuzzyy because it works in windows, unlike https://github.com/junegunn/fzf.vim

There's a :Buffers command in fzf.vim that I use extensively. It opens a fuzzy-find window with all open buffers in a MRU list.

Thanks to fzf.vim and fzf-lua, everything I learned and copied is from them.

they're likely referring to fzf.vim, the vimscript plugin from the original fzf author that wraps around fzf. there's also fzf-lua nowadays.