impatient.nvim
nvim-lua-guide
Our great sponsors
impatient.nvim | nvim-lua-guide | |
---|---|---|
31 | 152 | |
1,230 | 4,992 | |
- | - | |
5.9 | 6.3 | |
12 months ago | over 1 year ago | |
Lua | sed | |
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.
- Why do Neovim users actively seek out lua rewrites?
nvim-lua-guide
-
Any guide to start writing plugins?
Nvim Lua guide
- I'm fairly new to Neovim, and I want to configure my neovim setup.
-
Advice/Resources for creating/debugging a Neovim Plugin?
My main struggles beyond a simple problem are just the inability to find a way to easily debug things and the general process for setting up a plugin. I mostly work with Python/Jupyter, some C and Lua/Bash scripts, and usually you can either write tests/print debug for smaller scale things or get some stack trace if you have an error. With Neovim development, it just feels like there's nothing more besides update plugin, try on neovim, fail, bash head against wall, and repeat, and that doesn't quite seem efficient or correct - I'm sure there's something out there that should make the process easier. I tried looking online but I haven't found many that really fit my needs (most of the resources here seem more targeted towards creating your own init.lua, and Luadev plugin's commands are all broken (:Luadev-RunLine and any other command keeps telling me I got some trailing space). I'm really just looking to see how to make a snippet library, but there doesn't seem to be much that helps me. If someone could let me know how they debug their plugin or point me to any external resources, please let me know!
-
[help] use neovim to edit files at remote - server?
I have no guidance for the first point. For the second, checkout the neovim lua guide or : lua-guide
- Is there a vim/neovim equivalent to something like "Mastering Emacs"?
- [Neovim] Puis-je obtenir un guide sur la façon d’installer Packer pour les nuls absolus ?
- New to NeoVim, looking to learn
- Where to learn about Neovim and it's plugins? (Deeply)
-
Where would be a good place to start trying to learn lua with no previous programming experience. Trying to learn it as it’s the main language used in a project I’m apart of and want to help out
A quick google search turned up this codeacademy class on learning to program in Javascript. I didn't vet the whole thing, but it appears to assume you know nothing, which is what you need. If you go through that, you can then consume one of the resources that /u/luascriptdev post to equate that back to Lua. Again, the concepts translate.
- how to understand lua config
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.
kickstart.nvim - A launch point for your personal nvim configuration
barbar.nvim - The neovim tabline plugin.
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
indent-blankline.nvim - Indent guides for Neovim
vim-test - Run your tests at the speed of thought
vim-startuptime - A plugin for profiling Vim and Neovim startup time.
plenary.nvim - plenary: full; complete; entire; absolute; unqualified. All the lua functions I don't want to write twice.
neovim - Vim-fork focused on extensibility and usability
tree-sitter-svelte - Tree sitter grammar for Svelte
nvim - My own NVIM (>=NVIM v0.10.0-dev-2355+g1c7b0b9d5) lua config
which-key.nvim - 💥 Create key bindings that stick. WhichKey is a lua plugin for Neovim 0.5 that displays a popup with possible keybindings of the command you started typing.