vim9jit
impatient.nvim
vim9jit | impatient.nvim | |
---|---|---|
14 | 31 | |
498 | 1,230 | |
- | - | |
6.0 | 5.9 | |
about 2 months ago | 12 months ago | |
Rust | 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.
vim9jit
-
Vim-writegood: nothing, but a simple Vim9 wrapper around write-good.
That's not happening any time soon, but there's this project by one of Neovim's contributers that transpiles Vim9 script into Lua.
-
Introducing neovim config written in C
Probably feasible with https://github.com/tjdevries/vim9jit actually
-
Has anyone migrated their vimrc to vim9script ?
There's https://github.com/tjdevries/vim9jit. It has reportedly been used to port Vim9script runtime files to Neovim.
- Vim9jit: A vim9script to Lua transpiler written in Rust
-
What does emacs and elisp has as an advantage over nvim and lua?
Neovim is going to use a transpiler that covers vim9script code to lua code using the nvim api in the future (https://github.com/tjdevries/vim9jit)
-
Any Vimscript to Lua transpilers?
I didn’t watch the streams because I wasn’t totally sure what he was even doing, but maybe this will take some of it off your hands: https://github.com/tjdevries/vim9jit
-
I am done with vim (ThePrimeagen)
It could (rightly) be argued that neovim could just merge in vim9script, but I think this probably isn't the best more. I'm personally more in favor of getting a vim9 cross-compiler working, that way there's an easy way to support both. But that's my ignorant two cents on the matter.
-
So, is your main editor Vim or Neovim?
A core contributor to Neovim is toying with a Vim9Script to Lua convertor.
-
Vim 9.0 Was Released
That's not necessarily true.
Core maintainer of the Neovim Tjdevries is working on a compatibility layer that would allow vim9 to not only run in Neovim, but likely faster.
Source: https://github.com/tjdevries/vim9jit
-
Vim 9 has been released
My understanding was the neovim folks decided this wasn't work the hassle. TJ already has https://github.com/tjdevries/vim9jit, which transpiles vim9scripts to lua, and that is much more likely the way things will go.
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?
What are some alternatives?
vim-startuptime - A plugin for profiling Vim and Neovim startup time.
trouble.nvim - 🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing.
lua-languages - Languages that compile to Lua
barbar.nvim - The neovim tabline plugin.
vim9 - An experimental fork of Vim, exploring ways to make Vim script faster and better.
indent-blankline.nvim - Indent guides for Neovim
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
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
neovim - Vim-fork focused on extensibility and usability
vim-settings - My Vim Settings and a script to auto setup them
nvim - My own NVIM (>=NVIM v0.10.0-dev-2993+gc81b7849a) lua config