If I read the config page correctly, there are two things to be set
(just searched through the 10 occurrences of 'highlight'
diff.wsErrorHighlight
(says 'all' is valid)
color.diff.<slot>
(I think you want whitespace slot)
says you can set the various colours. Not sure about what the default
colours would be.
Beyond that, not sure. but check for any residual white space at the end
of lines in the config file.(s) ;-) !
Philip
On 26/06/2019 20:20, Elemental wrote:
Hi,
Changing the line so that there is no trailing comment did not fix the
problem.
# Shows removed whitespace in diffs
wsErrorHighlight = all
On Wednesday, June 26, 2019 at 5:48:00 AM UTC-4, Philip Oakley wrote:
While blank lines are acceptable, as are comment lines that start
with
the comment character, IIRC there are no trailing comments allowed
for
parameter values.
The parameter values can contain arbitrary characters (except /n
and /0,
and likely /r on Windows etc)
Philip
On 26/06/2019 00:49, Elemental wrote:
>
> If I do
> git config diff.wsErrorHighlight all
>
> (from
>
https://stackoverflow.com/questions/5257553/coloring-white-space-in-git-diffs-output
<https://stackoverflow.com/questions/5257553/coloring-white-space-in-git-diffs-output>.)
> , then my `git diff` shows whitespace highlighted in red.
> But, for some reason, if I modify my ~/.gitconfig file, to be:
>
> [diff]
> # Automatically detect renames/moves of files in git diffs
> # Shows actual changes between files
> renames =true
>
>
> wsErrorHighlight =all # Shows removed whitespace in diffs
>
>
> then doing a `git diff` doesn't show the whitespace highlighted
in red.
>
>
>
> Shouldn't these two ways produce the same output?
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from
it, send
> an email to git-...@googlegroups.com <javascript:>
> <mailto:git-...@googlegroups.com <javascript:>>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/git-users/9ea37888-db7c-4355-b0c2-802ab8179174%40googlegroups.com
<https://groups.google.com/d/msgid/git-users/9ea37888-db7c-4355-b0c2-802ab8179174%40googlegroups.com>
>
<https://groups.google.com/d/msgid/git-users/9ea37888-db7c-4355-b0c2-802ab8179174%40googlegroups.com?utm_medium=email&utm_source=footer
<https://groups.google.com/d/msgid/git-users/9ea37888-db7c-4355-b0c2-802ab8179174%40googlegroups.com?utm_medium=email&utm_source=footer>>.
> For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to the Google
Groups "Git for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to git-users+unsubscr...@googlegroups.com
<mailto:git-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/git-users/e4637712-27e5-4799-9016-cc749b5b8656%40googlegroups.com
<https://groups.google.com/d/msgid/git-users/e4637712-27e5-4799-9016-cc749b5b8656%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/git-users/be8a58e2-124e-457f-6a7c-37ec7613c161%40iee.org.
For more options, visit https://groups.google.com/d/optout.
