Vim-blueplanet Alternatives
Similar projects and alternatives to vim-blueplanet
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
vim-gitgutter
A Vim plugin which shows git diff markers in the sign column and stages/previews/undoes hunks and partial hunks.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
material.nvim
:trident: Material colorscheme for NeoVim written in Lua with built-in support for native LSP, TreeSitter and many more plugins
-
focus.nvim
Auto-Focusing and Auto-Resizing Splits/Windows for Neovim written in Lua. A full suite of window management enhancements. Vim splits on steroids!
-
vim-textobj-variable-segment
A text object to turn foo_bar_baz into foo_baz *and* quuxSpamEggs into quuxEggs *and* shine your shoes
-
nvim
Simple and ready configuration for neovim(nvim) with LSP. Inited with rust and go support (by xoac)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
vim-blueplanet reviews and mentions
-
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.
Stats
The primary programming language of vim-blueplanet is Lua.
Popular Comparisons
Sponsored