Johannes Schindelin wrote:
> ---color-words::
> +--color-words[=regex]::
> Show colored word diff, i.e. color words which have changed.
> ++
> +Optionally, you can pass a regular expression that tells Git what the
> +words are that you are looking for; The default is to interpret any
> +stretch of non-whitespace as a word.
Perhaps you could resurrect the documentation from my series, adjusted
for the different newline rule:
--color-words[=<regex>]::
Show colored word diff, i.e., color words which have changed.
By default, a new word only starts at whitespace, so that a
'word' is defined as a maximal sequence of non-whitespace
characters. The optional argument <regex> can be used to
configure this. It can also be set via a diff driver, see
linkgit:gitattributes[1]; if a <regex> is given explicitly, it
overrides any diff driver setting.
+
The <regex> must be an (extended) regular expression. When set, every
non-overlapping match of the <regex> is considered a word. Anything
between these matches is considered whitespace and ignored for the
purposes of finding differences. You may want to append
`|[^[:space:]]` to your regular expression to make sure that it
matches all non-whitespace characters. A match that contains a
newline is silently truncated at the newline.
--
Thomas Rast
trast@{inf,student}.ethz.ch
Attachment:
signature.asc
Description: This is a digitally signed message part.
