vim-signify significantly slow down vim in terminal

[mhinz]

vim-signify significantly slow down vim in terminal

[mhinz]

Exactly when does it happen? Everytime the signs get updated?

[kossnocorp]

Yeah, even if I jumping between splits. Give me time to play with it and I will write more explanation what is actually going on.

btw I'm running my vim inside of tmux.

[mhinz]

Let's assume you have 2 splits open. If you switch to a window that contains actual changes it's quick. But when the buffer was not modified since the last commit, it's slow.

Is that right?

[adarsh]

I find it's slow on save. I assume it's waiting on git diff?

[mhinz]

On a VCS-controlled file?

[adarsh]

Yes, under git.

[mhinz]

The signs will be updated every time the file gets saved && was modified. If a VCS was already detected, git in this case, it will automatically used from now on. Then yes, it's only processing the output of 'git diff'.

As a general rule for gaining better performance with this plugin:

1. set g:signify_vcs_list to only the VCS you use. Only these will be checked for when a new file gets opened.

2. set g:signify_update_on_bufenter to 0, if you often switch between buffers.

3. If you're working in a file with LOTS of changes, you're free to disable signify temporary using <leader>gt

Otherwise it's really just processing the diff output of an external tool. There's not much to make it a lot faster.

Some things are planned for the 2.0 release, though.

[kossnocorp]

Hey, sorry for delay, I finally found case when it becoming slow. When I switching between untracked (I'm using git) files every jump takes about 2-3 seconds. I don't know why maybe something wrong with my repo.

[kossnocorp]

btw thank you for so awesome plugin! It's really great work!

[mhinz]

Well, it sounds exactly like what is described in :h signify-options. You want to set signify_vcs_list. :-)

And thanks!

[kossnocorp]

Thanks! I guess this issue can be closed then :-).

[positron]

May I suggest adding the information about g:signify_vcs_list to the README? When I type "vim signi" in google one of the first suggestions is "vim signify slow". This indicates that a lot of people have this problem and it deserves a more prominent place in the documentation.

Thanks for the awesome plugin!

[mhinz]

Well, it's because nobody googles something if it's working blazing fast for him. ;-) And it's one of the very first things in the documentation (read: help file). The README is usually not meant for documentation purposes, at least not for Vim plugins.

But yes, I guess I can throw in anoher sentence. Thanks for the feedback!

EDIT: I stressed the use of g:signify_vcs_list in the README now.