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.
dotfiles
-
neovim and angularls
Works fine for me, haven't done anything particular either. Feel free to check config if you want: https://github.com/jemag/dotfiles/blob/3fc3fb4855955d0ab21d0c0856e6f3175f61dc57/neovim/.config/nvim/lua/lsp/lsp-installer.lua . Otherwise, you may want to double check that angular ls attaches properly with ":LspInfo" and check your lsp logs.
-
File Structure for Adjusting Plugin Options
There are numerous way you could go about it, I like to have the configuration of each plugin in its own file and invoke that in my packer startup, for example this would be my plugin configs files: https://github.com/jemag/dotfiles/tree/master/neovim/.config/nvim/lua/plugin-configs , each being invoked from packer : https://github.com/jemag/dotfiles/blob/master/neovim/.config/nvim/lua/plugins.lua
-
Unable to use nvim-jdtls
Don't have much time to investigate right now, but it does work for me. I can jump to definition and it does work also for Spring annotations. Feel free to check my config if you want, mostly https://github.com/jemag/dotfiles/blob/master/neovim/.config/nvim/lua/lsp/configs/jdtls-conf.lua and https://github.com/jemag/dotfiles/blob/master/bin/bin/java-lsp.sh
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?
.dotfiles - Personal dotfiles
CodeArt - Use NeoVim as general purpose IDE
nvim-config - A modern Neovim configuration with full battery for Python, Lua, C++, Markdown, LaTeX, and more...
astro.nvim - Faster Neovim Configuration
lazy-require.nvim - Require as little as possible. Do as little work as possible. Spend hours shaving off milliseconds
mapx.nvim - 🗺 A better way to create key mappings in Neovim
vim-resize-mode - A Vim mode for easier window resizing
dotfiles - 👨🏻💻 My dotfiles including Neovim Lua config, ZSH with zinit plugin manager & powerlevel10k prompt
dotfiles - wave Welcome to my dotfiles repository! This is where I store my personalized desktop configuration. desktop_computer
curso-neovim
nvim - The Ultimate NeoVim Config for Colemak Users
lsp-format.nvim - A wrapper around Neovims native LSP formatting.