-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
git blame: configurable additional options #400
Comments
The fact that Gitsigns uses the git cli is just an implementation detail and not foundational to the overall design. If lua-git ever becomes production ready, we would plan to use that where possible. So with that said, exposing configuration to append options on to specific git commands doesn't seem like the best idea. Git blame doesn't have a huge amount of options, so first class support for the features we want will be ok. From what I can tell, I propose we add additional options to
For backwards compat, |
I totally agree with you about the abstraction. Adding |
- blame_line() now takes a table as it's first argument (instead of a boolean) with the fields "full" and "ignore_whitespace" - Added config.current_line_blame_opts.ignore_whitespace Resolves #400
- blame_line() now takes a table as it's first argument (instead of a boolean) with the fields "full" and "ignore_whitespace" - Added config.current_line_blame_opts.ignore_whitespace Resolves #400
Is your feature request related to a problem? Please describe.
Please allow extra arguments for
git blame
(forlua require"gitsigns".blame_line(true)
, for example). For example,git blame -w
is a very commonly used command to ignore whitespace changes.Describe the solution you'd like
We could have some configurations like
or the field name as you wish.
Alternativelty, allow additional opts:
(BTW the first argument
full
could be a part of the opts as well)Describe alternatives you've considered
N/A
Additional context
I checked the implementation
lua/gitsigns/git.lua
and there is currently no such feature implemented. For example, git-messenger has this feature vialet g:git_messenger_extra_blame_args
.The text was updated successfully, but these errors were encountered: