nvim
nvim-conf
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nvim
-
You don't need to `source <venv>/bin/activate` before running neovim for LSP to pick the virtual environment.
I prefer to let this automaticlly handled inside neovim. For pyright, I made my nvim support these python venv: basic virtualenv in workspace (with pyvenv.cfg), pipenv and poetry. see https://github.com/younger-1/nvim/blob/one/lua/young/lang/python.lua
- Run Python venv from nvim
- Python virtual environment pyright
-
Null-LS isn't recognizing my .luacheckrc
Thanks you! Here's my configuration: https://github.com/younger-1/nvim and my choice of modules of plugins https://github.com/younger-1/nvim/blob/b0d4b4ecd185537c2e3e28b55cb8171eef124ad2/lua/young/plugins.lua#L865-L881 The defer usage in your nvim config would definitely help me to try this magic which I failed to make it work in my nvim config when I first saw it in doom-nvim.
-
Packer Initialization
My setup for packer with recompile and carefully design for first time bootstrap https://github.com/younger-1/nvim/blob/42efe08512145323d06c6b5f0877cf9a218f3da7/lua/young/plugin-loader.lua
-
Comparing different approaches to packer
My neovim config: https://github.com/younger-1/nvim
nvim-conf
- Breaking changes inbound (next few weeks) for lspconfig and neovim's language server client lsp
-
Comparing different approaches to packer
My plugin definitions
-
File Structure for Adjusting Plugin Options
I keep plugin configurations in my lua/user/plugin/ directory. If the plugin's options are short, I keep them in a file called misc.lua, otherwise I create a separate file with the name of the plugin. Check out my config to see what I mean.
-
What do you want to know about the process of converting an init.vim to init.lua setup?
Here is my configuration currently, nearly all Lua. Here is what it looked like when it was still VimScript (quite messy).
-
GitHub - b0o/mapx.nvim: A better way to create key mappings in Neovim
Please head over to the README for more examples, or check out my config to see how I actually use Mapx.
What are some alternatives?
neovhy - I had no better name for it I swear
CodeArt - Use NeoVim as general purpose IDE
projectmgr.nvim - Quickly switch between projects and automate startup tasks.
nvim-config - A modern Neovim configuration with full battery for Python, Lua, C++, Markdown, LaTeX, and more...
Neovim-from-scratch - 📚 A Neovim config designed from scratch to be understandable
astro.nvim - Faster Neovim Configuration
project-settings.nvim - Manage project local settings using a json file.
lazy-require.nvim - Require as little as possible. Do as little work as possible. Spend hours shaving off milliseconds
penvim - Project's root directory and documents Indentation detector with project based config loader
mapx.nvim - 🗺 A better way to create key mappings in Neovim
pyenv-virtualenv - a pyenv plugin to manage virtualenv (a.k.a. python-virtualenv)
vim-resize-mode - A Vim mode for easier window resizing