Windows causes a problem due to expecting Carriage Return+Line Feed at the end of lines (CRLF):
Git can take care of this by adding a note to .gitattributes :
which instructs it to automatically use Git's core.autocrlf
which does this when checking out of Windows:
git config --global core.autocrlf input
and this when checkign out of Linux/Mac:
git config --global core.autocrlf true
- Run dos2unix TheViolenceLayerManager.py once on your Linux machine to fix the current ^M errors.
- Add the .gitattributes file to the repo.
- Commit.
- Windows users will get the file with correct line endings automatically. They won't see any difference in functionality.
Not urgent because there is no included py files yet.
Windows causes a problem due to expecting Carriage Return+Line Feed at the end of lines (CRLF):
Git can take care of this by adding a note to .gitattributes :
which instructs it to automatically use Git's core.autocrlf
which does this when checking out of Windows:
and this when checkign out of Linux/Mac:
Not urgent because there is no included py files yet.