environment-modules Lmod VS telescope.nvim

In the HPC cluster I manage for more than 5 years, I have all the application variables like PATH and LD_LIBRARY_PATH export via Lmod (or Environment Modules). Each application will have its own modulefile to load when needed and the modulefile are only available on the nodes that are intended to run the application. Users will just need to load the module using module load command to have the variable exported.

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

nvim-telescope/telescope.nvim: Highly extendable fuzzy finder over lists.

Fzf is good, but as I said above, Neovim offers a lot of new plugins with new implementations. And among them, a supercharged fzf: Telescope! It allows you to search for files, and even text patterns, while offering an interface with file previews! A must have , quite simply.

I don't think many Neovim users could live without Telescope. Maintained by TJ DeVries, this is a fuzzy find, LSP integrator, and so many other things. I use it constantly to find open buffers, grep my codebase, look through Git logs, and pull up references. The image below shows how I'm using it to find Workspace Symbols.

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

Here we have a configuration for telescope.nvim, a very popular fuzzy finder.