startuptime.vim
gitsigns.nvim
startuptime.vim | gitsigns.nvim | |
---|---|---|
5 | 80 | |
283 | 4,445 | |
- | - | |
0.0 | 9.2 | |
over 1 year ago | 7 days ago | |
Vim Script | 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.
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 ...
gitsigns.nvim
-
Please, help with highlights.
those are gitsigns. read :h gitsigns-highlight-groups. i think the first 3 ones (gitsignsadd, gitsignschange, gitsignsdelete) would need their background cleared.
-
Gitsigns thinks that new lines in Windows are differences
I have installed Gitsigns in a Windows machine and when I execute the method diffthis it thinks that the new lines are differences.
-
Algebraic data types in Lua (Almost) post
Lack of tooling/LSP support compared to Lua. A rather popular neovim plugin, gitsigns, recently switched from teal to regular lua for (among other reasons) the tooling.
https://github.com/lewis6991/gitsigns.nvim/commit/4d63d996b0...
-
Benchmarking some of my favourite neovim plugins over time
gitsigns.nvim
-
Introducing multicursors.nvim plugin
The closest one would be gitsigns
-
How to use Git?
you can use gitsigns
-
Your favourite Neovim plugins?
https://github.com/lewis6991/satellite.nvim absolutely amazing choices, visual economy, integration with gitsigns and builtin vim features (marks).
-
Hacky way to return to original window after using gitsign's `diffthis`. There must be a better way to do this.
It's also nice to ask him directly.
-
Async module in Lua for Nvim
For a long time, I have been searching for solutions for asynchrony in Neovim, but what interested me the most was the one provided by gitsigns.nvim. Therefore, I decided to turn it into a separate module to make it easier to use async in Neovim. I have already created some usage examples.
-
[New plugin] deadcolumn.nvim -- gradually show you colorcolumn as you type
Oh, the symbols are provided by gitsigns.nvim and I have set :h statuscolumn so that they appear to the right of the line numbers. The settings are done in plugin/statuscolumn.lua. I put custom single-file scripts under plugin and ftplugin, where they serve as light-weighted mini plugins, you can even find the prototype of deadcolumn.nvim there :)
What are some alternatives?
lightspeed.nvim - deprecated in favor of leap.nvim
vim-fugitive - fugitive.vim: A Git wrapper so awesome, it should be illegal
vim-startuptime - A plugin for profiling Vim and Neovim startup time.
vim-gitgutter - A Vim plugin which shows git diff markers in the sign column and stages/previews/undoes hunks and partial hunks.
barbar.nvim - The neovim tabline plugin.
neogit - An interactive and powerful Git interface for Neovim, inspired by Magit
neovim - Vim-fork focused on extensibility and usability
lualine.nvim - A blazing fast and easy to configure neovim statusline plugin written in pure lua.
hop.nvim - Neovim motions on speed!
gitui - Blazing 💥 fast terminal-ui for git written in rust 🦀
dotnvim - Neovim Lua configuration pre-configured for Java, JavaScript, Typescript etc...
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.