dotfiles VS telescope.nvim

I have never used lsp-zero nor mason. I crafted my own LSP setup from back in the Neovim 0.5 days, see config here if interested.

Very simple, as noted here

My Diagnostic config: https://github.com/bluz71/dotfiles/blob/master/nvim/after/plugin/diagnostic.lua

My Neovim dotfiles.

init.lua and nvim directory

Most of mine is in Vimscript except for any modern Neovim plugin, I configure all of those in Lua. You can so I sprinkle Lua lightly within my configuration.

[Tip 3] Do not use the vim-rails plugin, it really slows down startup A LOT. I have switched over to Tim Pope's other project navigation plugin projectionist which can be configured to provide most of the functionality of vim-rails (but not all). For those interested here are my projectionist mappings. The stuff I miss out on, such as opening view files under the cursor just via :Eview, I can live without.

You can look around my dotfiles to get a feel for this hybrid Neovim / Vim compatibility mode.

This is what it looks like for me and this is my indent-blankline configuration, the most important of which is this:

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