# Config for git-blame flags -w, -M, and -C? 3 messages from 2016-05-07 to 2016-05-08. Participants: Joe Lencioni, Junio C Hamano. Thread: https://gitlist.dev/t/42258 ## Joe Lencioni, 2016-05-07 17:03 Subject: Config for git-blame flags -w, -M, and -C? Message-ID: URL: https://gitlist.dev/e/CAJzkHHf-B0FK%3DOw%3DB49GjSWyHJ6%2BfdnSvyGphDrEdkCGy1TOAg%40mail.gmail.com ``` 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 ``` ## Junio C Hamano, 2016-05-08 18:23 Subject: Re: Config for git-blame flags -w, -M, and -C? Message-ID: URL: https://gitlist.dev/e/xmqqk2j4z9wm.fsf%40gitster.mtv.corp.google.com In-Reply-To: ``` Joe Lencioni 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. ``` ## Joe Lencioni, 2016-05-08 18:39 Subject: Re: Config for git-blame flags -w, -M, and -C? Message-ID: URL: https://gitlist.dev/e/CAJzkHHfVK%2BUtEEx0d%2BT_ga3v6SiW0%3D2VhYFcMuMndzy0k9sK7Q%40mail.gmail.com In-Reply-To: ``` > 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. ```