nvim VS telescope.nvim

I read the installation documentation and the problem is that it is very general. https://github.com/catppuccin/nvim

catppuccin

I prefer https://github.com/catppuccin/nvim

I have consulted the catpuccin website and the github and followed their instructions but I feel like I'm missing something as I neovim still can't find the theme.

Im using lazy.nvim to load my colorscheme as plugin. This works as intended as long as i load the standard version of the colorscheme. In my example its catppuccin which translates to catppuccin-mocha. I cant get it to work with a variant of the colorscheme, for example catppuccin-latte. This is how my current plugins/colorscheme.lua:

I like Catppuccin (I use it for everything I can) personally

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)

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

{"level":"info","time":"2023-05-08T08:09:43.047Z","pid":920874,"host":"fedora","reqId":"req-1","req":{"method":"POST","url":"/shorten","hostname":"localhost:3000","remoteAddress":"127.0.0.1","remotePort":60582},"msg":"incoming request"} {"level":"debug","time":"2023-05-08T08:09:43.058Z","pid":920874,"host":"fedora","msg":"https://github.com/nvim-telescope/telescope.nvim#themes shortened to mB5Ke86"} {"level":"info","time":"2023-05-08T08:09:43.060Z","pid":920874,"host":"fedora","reqId":"req-1","res":{"statusCode":200},"responseTime":12.570792019367218,"msg":"request completed"}

lsp_workspace_symbols returns results only from the current workspace, whereas lsp_dynamic_workspace_symbols returns results from all the workspaces. Also, lsp_workspace_symbols returns an error of no results from workspace if the query is empty. So you need to also append a valid query to get back results. lsp_dynamic_workspace_symbols does not appear to have such a problem, but there have been some worries regarding its performance on large workspaces. I don't know the internal intricancies of LSP myself, but I found myself getting an error when using pyright with lsp_workspace_symbols so I transitioned to lsp_dynamic_workspace_symbols which solves this problem. There is an issue on telescope repo, which also discussed this problem, so you might want to read it through to get a better understanding.