startuptime.vim
vim9jit
startuptime.vim | vim9jit | |
---|---|---|
5 | 14 | |
283 | 501 | |
- | - | |
0.0 | 6.0 | |
over 1 year ago | 2 months ago | |
Vim Script | Rust | |
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.
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 ...
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.
What are some alternatives?
lightspeed.nvim - deprecated in favor of leap.nvim
vim-startuptime - A plugin for profiling Vim and Neovim startup time.
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.
neovim - Vim-fork focused on extensibility and usability
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
hop.nvim - Neovim motions on speed!
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
dotnvim - Neovim Lua configuration pre-configured for Java, JavaScript, Typescript etc...
impatient.nvim - Improve startup time for Neovim