prodoc.nvim VS telescope.nvim

Looks simple and clean! Big ups for starts of good screenshots, docs, and quickstart (Docker) instructions.

Regarding the name, "Telescope" is also the name of a Neovim fuzzy finder[0] that dominates the ecosystem there. Other results appear by searching "telescope github".

[0]: https://github.com/nvim-telescope/telescope.nvim

Telescope.nvim is extremely popular for navigating between files in Neovim. But that's not all that it can do! Telescope.nvim comes with dozens of builtins that can be extremely useful. My two favorites are lsp_document_symbols and live_grep.

another solution for fuzzy finding is telescope.nvim https://github.com/nvim-telescope/telescope.nvim

the thing i like the most about it is the amount of plugins you can add (including things like looking at nvim's paste ring).

I personally use Telescope as my fuzzy finder. Again, here's the docs for telescope and here's my config:

For example, telescope.nvim, that is also one of the most popular plugins, has a note in README that describes the way to use with lazy.nvim.

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

I too share your sentiment about VS Code. Its extension API[0] is extensive and approachable, often with examples[1] for each API.

Just a small anecdote: At work, I found it frustrating not being able to quickly locate where views for Django API endpoints were, so I wrote a simple extension that took the output of django-extensions' show_urls, parsed it, and displayed a quick pick list of all API endpoints, upon which selecting an endpoint would open the file and reveal the exact line in which the view for it was defined.

Implementing this did not take much effort (in fact, TypeScript and JSDoc make everything a lot simpler as it's clear to see what each function in the API does and what arguments they accept), and now this is something I use almost every day and greatly improves my satisfaction when navigating the codebase if not my productivity in general.

I have tried looking into implementing something similar in Neovim and came across the API for telescope.nvim[2], but found it a lot less intuitive to use. I do think Vim/Neovim shines when it comes to text manipulation and extensions built around it, but when it comes to more complex UI that often deals a lot more with graphical elements (e.g. tree views, hover text, notifications), it's hard to beat VS Code.

[0]: https://code.visualstudio.com/api/references/vscode-api

[1]: https://github.com/microsoft/vscode-extension-samples

[2]: https://github.com/nvim-telescope/telescope.nvim/blob/master...

This is indeed the main thing I use Spotlight/Alfred for on MacOS: I want to go to the window for this app, regardless of what virtual desktop it's on, and I don't want to hunt for it.

I use that "text-based finder" approach _everywhere_:

- Telescope in NeoVim (https://github.com/nvim-telescope/telescope.nvim)

Quick file nav: telescope