impatient.nvim
DISCONTINUED
packer.nvim
Our great sponsors
impatient.nvim | packer.nvim | |
---|---|---|
31 | 180 | |
1,230 | 7,541 | |
- | - | |
5.9 | 3.4 | |
11 months ago | 24 days ago | |
Lua | Lua | |
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.
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.
packer.nvim
-
thethethe.nvim - neovim friendly autocorrect plugin
packer
-
Editing init.lua with lua_ls on gives "Undefined global : vim" ?
require('packer').startup(function(use) use 'https://github.com/wbthomason/packer.nvim' use 'https://github.com/neovim/nvim-lspconfig' end)
- error message whenever I write a file
-
[Help] Packer.nvim
git clone --depth 1 https://github.com/wbthomason/packer.nvim\ ~/.local/share/nvim/site/pack/packer/start/packer.nvim
-
Pyright Won't Let me Quit Python Files
``` vim.g.maplocalleader = " " vim.g.mapleader = " " local ensure_packer = function() local fn = vim.fn local install_path = fn.stdpath("data") .. "/site/pack/packer/start/packer.nvim" if fn.empty(fn.glob(install_path)) > 0 then fn.system({ "git", "clone", "--depth", "1", "https://github.com/wbthomason/packer.nvim", install_path }) vim.cmd([[packadd packer.nvim]]) return true end return false end
- [Neovim] Gestionnaire de packages basé à Lua
-
Introducing tsc.nvim: Project-Wide Asynchronous TypeScript Type-Checking & Diagnostics
To get started, simply install the plugin using your favorite plugin manager, such as vim-plug or packer.nvim. You can find detailed installation instructions in the README.
-
Why do I get a 'can't assign string to parameter fun()' error?
Is there a particular reason why you would want to use vim plug in Lua? If you're new to neovim, I would highly recommend that you pick one of the popular Lua-based package managers (Lazy and Packer) and use those. Perhaps also check out TJ's kickstart.nvim if you want a slightly less barebones initial setup.
-
Boost Your Neovim Experience with These Essential Plugins
Snapshot provides the same functionality but is much harder to use IMHO, see https://github.com/wbthomason/packer.nvim/issues/1009 they describe what people expect from a lock file and how it's integrated in a way that is developer friendly and it's still open.
What are some alternatives?
vim-plug - :hibiscus: Minimalist Vim Plugin Manager
lazy.nvim - 💤 A modern plugin manager for Neovim
trouble.nvim - 🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing.
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
nvim-lspconfig - Quickstart configs for Nvim LSP
paq-nvim - 🌚 Neovim package manager
gruvbox.nvim - Lua port of the most famous vim colorscheme
nvim-lua-guide - A guide to using Lua in Neovim
nvim-tree.lua - A file explorer tree for neovim written in lua
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
mason-lspconfig.nvim - Extension to mason.nvim that makes it easier to use lspconfig with mason.nvim.
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.