Config for git-blame flags -w, -M, and -C?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Config for git-blame flags -w, -M, and -C?

Joe Lencioni
git-blame has a few options are useful when working with commits that
only modify whitespace (-w), move code within the file (-M), or move
code between files (-C). It would be nice if there was a way to
configure git so these options could be enabled by default when
running `git blame`.

I suppose this would also require the addition of the inverse options,
or perhaps arguments for the options, to disable them if needed.

Thoughts?

/Joe
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Reply | Threaded
Open this post in threaded view
|

Re: Config for git-blame flags -w, -M, and -C?

Junio C Hamano
Joe Lencioni <[hidden email]> writes:

> Thoughts?

For end-user facing commands that are expected to be used by human
typing on the keyboard, I'd recommend

        git config alias.bl "blame -w -M -C"

instead.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Reply | Threaded
Open this post in threaded view
|

Re: Config for git-blame flags -w, -M, and -C?

Joe Lencioni
> git config alias.bl "blame -w -M -C"

Indeed, that would do the trick when interacting with git directly.
However, I am interested in something that would provide a consistent
git blame across all tools that integrate with git, such as GUI tools
and editor integrations like Fugitive.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html