nvim
project-settings.nvim
nvim | project-settings.nvim | |
---|---|---|
6 | 5 | |
22 | 16 | |
- | - | |
9.1 | 0.0 | |
about 1 month ago | almost 2 years ago | |
Lua | Lua | |
- | MIT License |
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
project-settings.nvim
-
I didn't know before that having multiple Neovim instances is bad
That command actually uses project-settings.nvim to setup all the things, not just lsp.
- Run Python venv from nvim
-
Some questions about Lua plugin development
If it helps, you can take a look at this little plugin I made: project-settings.nvim.
-
Using project-settings.nvim to call language servers
project-settings.nvim is a plugin I created to handle some unique scenarios I faced in a couple of projects. It allows you to reuse a lua function across multiple projects, and pass arguments to it using a json file. (I know one could just use an exrc file, but I don't like them).
-
How do y'all feel about handling project local settings using a json file?
Once again I found myself turning a piece of my config into a plugin. This time around it is the project local settings: project-settings.nvim
What are some alternatives?
neovhy - I had no better name for it I swear
workspaces.nvim - a simple plugin to manage workspace directories in neovim
projectmgr.nvim - Quickly switch between projects and automate startup tasks.
nvim-config-local - Secure load local config files for neovim
Neovim-from-scratch - 📚 A Neovim config designed from scratch to be understandable
editorconfig-vim - EditorConfig plugin for Vim
penvim - Project's root directory and documents Indentation detector with project based config loader
plugin-template.nvim - A template to create Neovim plugins written in Lua
pyenv-virtualenv - a pyenv plugin to manage virtualenv (a.k.a. python-virtualenv)
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
flow.nvim - A neovim plugin that lets you build custom commands to automate parts of your development workflow