dotnvim
startuptime.vim
dotnvim | startuptime.vim | |
---|---|---|
6 | 5 | |
121 | 283 | |
- | - | |
0.0 | 0.0 | |
8 months ago | over 1 year ago | |
Lua | Vim Script | |
MIT License | 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.
dotnvim
- Running Neovim server in docker container
-
Lua
I have WIP java implementation if you are interested: dotnvim. It's similar to nvim-jdtls but calls are more organized and promisified.
-
coq.nvim now supports fast as fuck modular lua sources (third party plugins too!)
This is my dotfiles. May not be the best but way better than yours.
-
Fix for diagnostics not updating issue
I have my configuration on GitHub if anyone wants to check it out.
- unfinished string near '<eof>'
-
My first (neo)vim plugin
Vim script is readable I agree with that. But just uncommon syntax throw me off. I would create a API wrapper than using vim script. I have done it here.
startuptime.vim
-
How can I profile neovim plugins for a specific file?
You could use https://github.com/tweekmonster/startuptime.vim. Then you can run :StartupTime -- big-file.txt
-
Lua
tweekmonster/startuptime.vim is inaccurate. I think it doesn't take Lua into account. Don't use this plugin.
-
moonfly & nightfly colorschemes, now with faster startup
I recently had a look at startup performance. Using the startuptime plugin both moonfly & nightfly were taking around 4.5ms to load on my quad-core Linux desktop (not too bad for traditional Vimscript-based colorschemes). Some profiling did indicate that clearing highlights and resetting syntax are actually quite expensive. We really don't need to do either when loading a colorscheme at Vim start time; it is only really needed when changing colorschemes within an existing edit session. Putting in a simple guard results in moonfly & nightfly now taking only 2.5ms to startup (on my machine).
-
moonfly & nightfly colorschemes, now with expanded Neovim ecosystem support (and faster startup)
Lastly, I also had a look at startup performance. Using the startuptime plugin both moonfly & nightfly were taking around 4.5ms to load on my quad-core Linux desktop (not too bad for Vimscript-based colorschemes). Some profiling did indicate that clearing highlights and resetting syntax are actually quite expensive. We really don't need to do either when loading a colorscheme at Neovim start time; it is only really needed when changing colorschemes within an existing edit session. Putting in a simple guard results in moonfly & nightfly now taking only 2.5ms to startup (on my machine). That is quite similar to some of the nice new Lua-based Neovim colorschemes now available. A win, albeit a small one.
-
Why my config has gotten so slow?
Using the :StartupTime provided by https://github.com/tweekmonster/startuptime.vim ...
What are some alternatives?
luavim - Luavim is a simple neovim configuration written in lua, aiming to provide a base config.
lightspeed.nvim - deprecated in favor of leap.nvim
vim-startuptime - A plugin for profiling Vim and Neovim startup time.
NvimSetup - A NVIM setup I'm working on. Moving from IDE to PDE.
barbar.nvim - The neovim tabline plugin.
dotfiles - -
neovim - Vim-fork focused on extensibility and usability
CosmicNvim - CosmicNvim is a lightweight and opinionated Neovim config for web development, specifically designed to provide a 💫 COSMIC programming experience! [Moved to: https://github.com/CosmicNvim/CosmicNvim]
hop.nvim - Neovim motions on speed!
impatient.nvim - Improve startup time for Neovim
nvim-tree.lua - A file explorer tree for neovim written in lua