impatient.nvim
DISCONTINUED
dots
DISCONTINUED
Our great sponsors
impatient.nvim | dots | |
---|---|---|
31 | 4 | |
1,230 | 46 | |
- | - | |
5.9 | 5.7 | |
11 months ago | over 1 year 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.
impatient.nvim
-
Reduce Neovim startup time with plugins
You could use impatient.nvim or the new vim.loader module if you’re on nightly. Both work really well. I used impatient for a long time and it reduced my startup time by half. I’m using vim.loader now and it reduces it by about the same amount
-
Optimizing my startup time
The 20-30 ms promise depends on your hardware. In my case, vanilla Neovim takes about 18 ms to startup, so a realistic good startup time for my config is around 50-60 ms. Lines of code isn’t a great reference either because you could just lazy load a bunch of plugins and have more LoC but still better startup times. What I would recommend is using lazy.nvim or if you wanna stick with packer, then pairing it with impatient.nvim .
-
lazy.nvim is amazing!
automatically caches all startup code before :h VimEnter or :h BufReadPre (basically what impatient.nvim does)
-
fzf is so powerful when you use it well ! code/files/tags/git history
there is an amazing plugin called impatient.nvim that cache a lot of stuff and make other pluggins go so fast !
-
neovim startup optimization
Try installing https://github.com/lewis6991/impatient.nvim first.
-
Guide: Structuring Lua plugins
:lua vim.pretty_print(vim.mpack.decode(vim.mpack.encode({some = { thing = false }}))) used by impatient.nvim
- Can neovim config be baked in to make neovim blazingly fast?
-
Default mappings override user mappings in Rust ( [[ and ]] mappings )
Did you defined your [[ and ]] mappings in that file or just created it? the after directory runs at the end of your config so you can override this kind of settings. Maybe you are using impatient.nvim? From their README:
-
what is your startup time like?
Are you using impatient.nvim? It caches lua modules. My startuptime with 72 plugins (including it) and zero lazy loading is 600ms.
dots
-
Documentation for neovim lua api in nvim-cmp?
Here is my dotfile: .config/nvim
-
How can I reduce the loading time of init.lua?
If anything you can see my config for inspiration on how to achieve fast loading time.
-
Neovim is not smooth when writing and bad startup time.
My config load in 12ms with 43 plugins (lazy load basically everything), maybe you can learn a thing or two from it: ~/.config/nvim
What are some alternatives?
trouble.nvim - 🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing.
barbar.nvim - The neovim tabline plugin.
indent-blankline.nvim - Indent guides for Neovim
vim-startuptime - A plugin for profiling Vim and Neovim startup time.
neovim - Vim-fork focused on extensibility and usability
nvim - My own NVIM (>=NVIM v0.10.0-dev-2355+g1c7b0b9d5) lua config
filetype.nvim - A faster version of filetype.vim
nvimdots - A well configured and structured Neovim.
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
nvim - Straightforward and pure Lua based Neovim configuration for my work as DevOps/Cloud Engineer with batteries included for Python, Golang, and, of course, YAML
nvim-jdtls - Extensions for the built-in LSP support in Neovim for eclipse.jdt.ls
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config