neoconf.nvim VS neovim

Maybe https://github.com/folke/neoconf.nvim

One suggestion: It looks like your plugin's config makes assumptions about all projects (e.g. main branch name). It might be a good idea to support something like neoconf.nvim to configure the plugin on a per-project basis.

I think this is actually because of neoconf?

I have this working in a way that's comparable to how you would configure the VSCode extension.First, you need to install folke/neoconf.nvim and call it's setup function before you setup mason or your lsp-config.

A limited class of settings can be managed per-project with folke/neoconf.nvim with a primary emphasis on LSP settings, so definitely give it a look. I think it's the cleanest approach until the exrc-replacement lands in stable.

If you don’t mind adding a plug-in, neoconf.nvim will let you manage project local lsp settings in a JSON file.

Try https://github.com/folke/neoconf.nvim

There's neoconf by the almighty folke, I am not sure if it is what you are after.

You can find all the details at https://github.com/folke/neoconf.nvim

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.