![]() This makes it easier to distinguishĬode blocks introduced by different commits. īlame-options now includes in its man page: -color-linesĬolor line annotations in the default format differently if they come from While both options are mentioned in usage help, they aren't documented in git-blame(1). (Merged by Junio C Hamano - gitster - in commit 871e42e, ) blame: document -color-* optionsĬommit cdc2d5f (" builtin/blame: dim uninteresting metadata lines",, Git v2.18.0-rc0 - merge listed in batch #7) and 25d5f52 (" builtin/blame: highlight recently changed lines",, Git v2.18.0-rc0 - merge listed in batch #7) introduce -color-lines and -color-by-age options to git blame ( man), respectively. See commit 8c32856 (), and commit 38c356a () by Bagas Sanjaya ( bagasme). Note: The " -color-lines" and " -color-by-age" options of " git blame" ( man) have been missing, which are now documented with Git 2.34 (Q4 2021). Setting the config option doesn't imply that repeated lines are colored. Repeated lines, and the config option ' ' is The command line option ' -color-lines' will trigger the coloring of ![]() Traditionally, we use CYAN for lines that are less interesting than others (e.g. When using git-blame, lots of lines contain redundant information, forĮxample in hunks that consist of multiple lines, the metadata (commitĪ reader may not be interested in those, so offer an option to color the information that is repeated from the previous line differently. One year old are kept white, and lines introduced within the last month areīuiltin/blame: dim uninteresting metadata lines It defaults to ' blue,12 month ago,white,1 month ago,red', which colorsĮverything older than one year blue, recent changes between one month and Instead of an absolute timestamp relative timestamps work as well, e.g.Ģ.weeks.ago is valid to address anything older than 2 weeks. The metadata will be colored given the colors if the the line was introducedīefore the given timestamp, overwriting older timestamped colors. This setting should be set to a comma-separated list of color and date settings, starting and ending with a color, the dates should be set from oldest to newest. This can be used to color the metadata of a blame line depending on age of the line. ' -color-by-age' to enable this mode and the config option ![]() Similarly to the previous patch, this offers the command line option It can be ' repeatedLines', ' highlightRecent', or ' none' which is the default.īuiltin/blame: highlight recently changed linesĬhoose a different color for dates and imitate a 'temperature cool down' This determines the coloring scheme to be applied to blame output. The command line still takes precedence over the configuration. (Merged by Junio C Hamano - gitster - in commit 3d24129, ) builtin/blame: add new coloring scheme configĪdd a config option that allows selecting the default color scheme forīlame. See commit 0dc95a4, commit 25d5f52, commit cdc2d5f () by Stefan Beller ( stefanbeller). Update Git 2.18 (Q2 2018): " git blame" learns to unhighlight uninteresting metadata from the originating commit on lines that are the same as the previous one, and also paint lines in different colors depending on the age of ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |