targets.vim VS telescope.nvim

targets is nice too.

The thing that has the biggest impact on me is ci”, ca”, da”, etc.. so I suggested getting used to using those.. and then you can get more pedantic with it using https://github.com/wellle/targets.vim

I do recommend getting, targets.vim https://github.com/wellle/targets.vim .. which unlocks the n(ext) and l(ast) verbs(?) ..ahhhh it’s REALLY REALLY good, I use 2in” like a lot

In fact, as /u/Chillbrosaurus_Rex points out, there's a plugin, targets.vim, that expands on Vim's built-in text objects, and one of the things it does is to provide this kind of forward and reverse direction functionality.

Hey, I use targets.vim, how does it compare with that?

You might benefit from targets.vim, it works well with your thought process. It adds a bunch of new really useful editing targets (which should be builtin imo).

https://github.com/wellle/targets.vim

Thanks for the through explanation. I has seen that and considered using it in the past. Can I ask how it compares to https://github.com/wellle/targets.vim? Would you consider mini.ai a replacement or complementary?

This is provided by targets.vim, along with a bunch of other useful text objects.

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