-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Ignore commits that move a file #123
Comments
Oh, hi!
Could you expand a bit on this one?
Yeah, this seems to make sense initially. |
I am interested in this feature too.
All the information that I have is from an article on Git Butler, but in resume, The -C option ignores code movements between files or lines when using the git blame command. It only shows changes to the code itself, rather than movements. Example where in the first command uses a normal here the article: |
I think that for the plugin, a nice feature will be to add the parameters that we want to add to the git blame command. For example: let g:gitblame_parameters = ['-w', '-C', '-C', '-C'] and then this should run as: git blame -w -C -C -C |
Thanks @marcelarie, I also got this tip from a very similar source, in a recent talk by the Scott from git butler: I think a setting could be nice but maybe also the ability to pass flags to eg
or similar. Not sure exactly how that should interact with default options though? |
Yes that sounds amazing. |
Thanks for the explanation @marcelarie!
Yup, I agree it would be nice! However, for this particular one, I'd also like it to be a setting so that people can see that they can do this :)
I don't mind having that but don't think it's as important :) |
i would love to have this too as it is how i have fugitive configured! |
I recently learned about the
-C
flag ofgit blame
which can be added 0 to 3 times and make eg commits that just move away to be ignored. This is usually what I actually want to see and I was wondering if it could make sense to expose that as a configuration option or an option to the command directly?The text was updated successfully, but these errors were encountered: