aboutsummaryrefslogtreecommitdiffstats
path: root/init/Mathias.itermcolors
diff options
context:
space:
mode:
authorLuveen Rupchand Wadhwani <luveenw@gmail.com>2014-03-04 23:22:29 -0800
committerMathias Bynens <mathias@qiwi.be>2014-03-05 08:37:45 +0100
commitc62ff1628bc3bb08aebb77d97dac026c8f17cf4f (patch)
tree720f174ea0a7c9940cb7811155cd882d6fe19af6 /init/Mathias.itermcolors
parentd4cfb804fceb3e6c22ea581b3d89d04522c8e503 (diff)
downloaddotfiles-c62ff1628bc3bb08aebb77d97dac026c8f17cf4f.tar.gz
dotfiles-c62ff1628bc3bb08aebb77d97dac026c8f17cf4f.tar.bz2
dotfiles-c62ff1628bc3bb08aebb77d97dac026c8f17cf4f.zip
.gitconfig: Explicitly disable `indent-with-non-tab`
Don’t use `indent-with-non-tab`. This config flag is PERNICIOUS. If turned on, Git won’t tell you that you indented your code incorrectly. Instead, when it is pushing your changes to your remote repo, Git will silently convert any consecutive 8-space strings it sees into tab characters. This can be highly undesirable, especially if you collaborate with a team that expects the code to be indented using spaces instead of tabs. At the very least, the comment above this line should very clearly explain the fact that `indent-with-non-tab` does more than advertised in the `git-config man page (https://www.kernel.org/pub/software/scm/git/docs/git-config.html). Closes #351.
Diffstat (limited to 'init/Mathias.itermcolors')
0 files changed, 0 insertions, 0 deletions