atty VS fzf.vim

That said, there's a recent question about maintenance status and a fork with some changes, so you could switch to that if you're worried.

Maybe start with the atty crate? Ultimately this is an OS question more than a Rust question, and it depends on what you mean by "any stdout was piped". For example, do you want to be able to tell the difference between

That likely only works on a Windows console. For tools like this, you also want to handle cygwin, and that requires crazy hacks: https://github.com/softprops/atty/blob/7b5df17888997d57c2c1c8f91da1db5691f49953/src/lib.rs#L116-L154

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.