-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Way to disable vcs plugins? #319
Comments
If you just want to get it done for now, check out the I know I did quite an aggressive refactoring lately, but there were a few things that I wanted to change for a long time and.. well, it's happening now. I removed a lot of options because a) http://neugierig.org/software/blog/2018/07/options.html and b) they were introduced before Vim was capable of async execution.
Anyway, I see your issue. But instead of reintroducing Maybe something like:
This gives us more flexibility than we had before, is easy to extend, and reduces the number of options. Would that work for you? |
I suppose something like skipping a filename pattern would work, but I'd end up turning off perforce altogether for basically I understand that adding options requires real justification and easily leads to software bloat. I use tools on a daily basis plagued by options accumulated over decades and now come with literal 10,000 page manuals. However, for something like this where the "default" installation comes with support for multiple VCS, many of which most people won't use concurrently, it seems like having a way to simply limit the supported VCS borders on basic functionality. All that would be needed would be to add another entry in the |
Allow only certain VCS or deny all but the specified ones. Mutual exclusive. This can be used to replace the old g:signify_vcs_list. Examples: let g:signify_skip = {'vcs': { 'allow': ['git'] }} let g:signify_skip = {'vcs': { 'deny': ['perforce'] }} References #319
Okay, so the commit It's not documented yet on purpose, in case we want to change things in the next days. |
Allow only certain VCS or deny all but the specified ones. Mutual exclusive. This can be used to replace the old g:signify_vcs_list. Examples: let g:signify_skip = {'vcs': { 'allow': ['git'] }} let g:signify_skip = {'vcs': { 'deny': ['perforce'] }} References #319
I tested and it works for me!
|
is this still considered undocumented/subject to change? Edit: doesn't appear to work for me, not sure if it was rolled back |
It actually works fine but missing documentation. |
|
I have a situation where I use both
git
andperforce
in the same folder (yeah...), but I only want signify to operate on the git repository.I just updated my plugins today and discovered that my previous way of modifying
g:signify_vcs_list
so that onlygit
was available no longer works, sinceg:signify_vcs_list
doesn't exist anymore (#261). Is there an alternative way to disable individual vcs plugins? Perhaps usingg:signify_vcs_list
was the wrong way to do this in the first place?Here's my existing vimrc:
This XKCD seems applicable here: https://xkcd.com/1172/
The text was updated successfully, but these errors were encountered: