lsp-status.nvim VS telescope.nvim

https://github.com/nvim-lua/lsp-status.nvim do not have this issue (I completely disabled it before trying this one to avoid conflicts).

I use lsp-status to show the language server indexing progress

I use https://github.com/nvim-lua/lsp-status.nvim to get LSP diagnostic info for status lines / etc. This might be of interest if only in seeing its inner workings.

[lsp-status](https://github.com/nvim-lua/lsp-status.nvim) that's used by the statusline plugin I use ([bubbly.nvim](https://github.com/datwaft/bubbly.nvim)) to populate lsp diagnostic info in the status bar (ex. 2 errors, 50 warnings, etc). I only added it per suggestion of the plugin, so it's quite possible you wouldn't need it.

lsp-status.nvim - Language Server Protocol statusline integration

I also experience that and this plugins is nice to know what the lsp is doing in the background: https://github.com/nvim-lua/lsp-status.nvim

I use lsp status https://github.com/nvim-lua/lsp-status.nvim

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