vim-blueplanet
nvim
vim-blueplanet | nvim | |
---|---|---|
2 | 4 | |
10 | 12 | |
- | - | |
9.2 | 0.0 | |
about 2 months ago | over 2 years ago | |
Lua | Lua | |
- | - |
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.
vim-blueplanet
-
FAVOURITE PLUGINS
To my knowledge vim-test has no out-of-the-box configuration for TypeScript. I forgot why. Anyway here is my configuration that adds mocha and jest as testers for TypeScript. Though it is mostly based on the existing JavaScript support of vim-test it adds some extra support for Vue testing and project local binaries. Finally ensure you enabled these testers in the vim-test configuration (g:test#custom_runners).
-
Do you use a single init.lua/.vim file or an organized directory structure? Just curious :)
You could take a look here at my configuration. Not sure if that is helpful. You should first read up native packages as it has been linked above. I don't explain the little sneaks and features here. But in its core I put file and directory structure above everything else. I barely import anything manually but fully rely on automated mechanisms. I use lazy loading heavily. I use a mix of .vim and .lua files depending on its content and which language is easier (e.g. mappings are simpler in VimL. In result I have hundreds of files in my configuration. My everything follows a structure. With tools like fzf or telescope it is too easy to open the file you search for. It's basically no overhead. It would be more work to find what I search for if I would have less files. Finally this keeps everything incredibly independent. I can add, change and especially remove thing very easily as most things are very separated and independent. I want to remove a plugin, all its config, mappings, highlights, signs, ... I just remove one directory. Nothing more and nothing less. Clean cut. If I want a plugin and everything around it (copy-paste from above) to be lazy loaded it just works out-of-the-box. It's very simple and elegant. In my opinion. Though you can easily dislike it if you don't agree that strong with the approach it's fundamental arguments.
nvim
-
Do you use a single init.lua/.vim file or an organized directory structure? Just curious :)
I am trying to create rule: one file one plugin but it's a little bit difficult since not all plugins like setups in many files. My config is here: https://github.com/xoac/nvim
-
My different approach for nvim configuration (easier for beginners and simpler to maintain)
Now I can see the difference between spaces and tabs Now I use spaces instead of tabs
What are some alternatives?
material.nvim - :trident: Material colorscheme for NeoVim written in Lua with built-in support for native LSP, TreeSitter and many more plugins
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
octo.nvim - Edit and review GitHub issues and pull requests from the comfort of your favorite editor
dotfiles - Personal configuration files, scripts, etc.
vim-gitgutter - A Vim plugin which shows git diff markers in the sign column and stages/previews/undoes hunks and partial hunks.
dotfiles - ❄️ My dotfiles for NixOS and macOS as a Nix flake. Neovim, Fish shell, Wezterm, etc.
nvim-dap - Debug Adapter Protocol client implementation for Neovim
NeoHub - Instance manager for Neovide
neovim.config - WIP: My new configuration for Neovim 0.5+