User Tools

Site Tools


git_whitespace

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
git_whitespace [2018/06/11 11:10]
rpjday [git merge]
git_whitespace [2019/03/05 18:15] (current)
rpjday [git blame]
Line 1: Line 1:
 ===== Overview ===== ===== Overview =====
  
- A moderately (dis)organized list of features related to dealing with whitespace issues in Git, in no particular order.+ A moderately (dis)organized list of features related to dealing with whitespace issues in Git, in no particular order. ​It's a matter of some debate whether EOL standardization is simply a subet of whitespace issues, or whether it deserves its own page. 
 + 
 +===== config options ===== 
 + 
 +==== apply.ignoreWhitespace ==== 
 +==== apply.whitespace ==== 
 +==== core.whitespace ==== 
 + 
 +<​code>​ 
 +$ git config --global core.whitespace \ 
 +    trailing-space,​-space-before-tab,​indent-with-non-tab,​tab-in-indent,​cr-at-eol 
 +</​code>​ 
 +==== core.eol ==== 
 +==== core.safecrlf ==== 
 +==== core.autocrlf ==== 
 + 
 +Setting this variable to "​true"​ is the same as setting the text attribute to "​auto"​ on all files and core.eol to "​crlf"​. Set to true if you want to have CRLF line endings in your working directory and the repository has LF line endings. This variable can be set to input, in which case no output conversion is performed. 
 + 
 +===== git apply ===== 
 + 
 +TO DO. 
 + 
  
 ===== git diff ===== ===== git diff =====
Line 9: Line 31:
 <​code>​ <​code>​
 $ git diff --check $ git diff --check
 +</​code>​
 +
 +based on:
 +
 +<​code>​
 +--check
 +    Warn if changes introduce conflict markers or whitespace errors. What are
 +    considered whitespace errors is controlled by core.whitespace configuration.
 +    By default, trailing whitespaces (including lines that solely consist of
 +    whitespaces) and a space character that is immediately followed by a tab
 +    character inside the initial indent of the line are considered whitespace
 +    errors. Exits with non-zero status if problems are found. Not compatible with
 +    --exit-code.
 +
 +--ws-error-highlight=<​kind>​
 +    Highlight whitespace errors in the context, old or new lines of the diff.
 +    Multiple values are separated by comma, none resets previous values, default
 +    reset the list to new and all is a shorthand for old,​new,​context. When this
 +    option is not given, and the configuration variable diff.wsErrorHighlight is
 +    not set, only whitespace errors in new lines are highlighted. The whitespace
 +    errors are colored whith color.diff.whitespace.
 </​code>​ </​code>​
  
Line 95: Line 138:
     ·   ​error-all is similar to error but shows all errors.     ·   ​error-all is similar to error but shows all errors.
 </​code>​ </​code>​
 +
 +===== git blame =====
 +
 +<​code>​
 +-w
 +    Ignore whitespace when comparing the parent’s version and the child’s to find
 +    where the lines came from.
 +</​code>​
 +
 +===== git stripspace =====
 +
 +<​code>​
 +$ man git-stripspace
 +</​code>​
 +
git_whitespace.1528715431.txt.gz · Last modified: 2018/06/11 11:10 by rpjday