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.)
, 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-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/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>.
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/8d2a98ac-a76f-4f00-deb9-52fa16a25062%40iee.org.
For more options, visit https://groups.google.com/d/optout.
