vim-textobj-entire VS telescope.nvim

I agree that ggVG is fine but not with the custom leader to copy to clipboard part. If you're gonna have to remember something might as well use a text object instead, that way you get the full range of actions and not just the hardcoded mapping. I use kana/vim-textobj-entire that provides e for entire buffer, so copying would be yie and life is smooth. There's a bunch of text object plugins, just get one or write it yourself would be my advice.

I like the entire document text object: https://github.com/kana/vim-textobj-entire

You should make your life easier and get the entire text object plugin. This is the easiest way to act one the entire buffer with no surprises, although it still does change the cusror position sometimes, but I still recommend it.

kana/vim-textobj-entire - Make entire buffer available as a text object

I now use entire text object for this with vie, which is more mentally coherent, for me, than ggVG.

kana/vim-textobj-entire adds e as text object for entire buffer

die (delete in entire) with the plugin vim-textobj-entire

I would suggest adding the text object "entire", either by making your own omap, or using a plugin like vim-textobj-entire.

for telescope.nvim (optional) live grep: ripgrep find files: fd

Here we have a configuration for telescope.nvim, a very popular fuzzy finder.

EDIT: I found what I was looking for https://github.com/nvim-telescope/telescope.nvim and https://github.com/nvim-telescope/telescope-file-browser.nvim

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

Just landed on Telescope.nvim: https://github.com/nvim-telescope/telescope.nvim/pull/2572

This extension allows you to use the power of ast-grep to find code patterns in your editor, using the familiar and awesome interface of telescope.nvim.

telescope.nvim

My solution is using telescope.nvim with lsp extension, and map the vim.lsp.buf.definition keybinding to telescope one https://github.com/nvim-telescope/telescope.nvim