Git shows every line has been altered.
jackjameshoward opened this issue · 6 comments
Prerequisites
- Put an X between the brackets on this line if you have done all of the following:
- Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
- Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
- Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
- Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
- Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages (I didn't see this as being relivent)
Description
Whenever I clone a repo and make an edit to any file, git-diff shows that every line in the file has been delete and an equal number of lines has been replaced. If I git add/commit/push/pull/fetch/merge the result is always the same in atom; if I change anything in atom it decects every line has been altered.
Curiosly if I check what was commited via git, it will accurate show that only one line has changed.
Steps to Reproduce
- git clone a repo
- open Atom
- add Project Folder (Ctrl+Shift+A), add cloned repo folder.
- open any file from repo - for example index.html
- change anything one a single line in file and save file
- bottom right corner states +200, -200 lines (for example)
- git add and git commit
- git commit reads +1, -1 line chaged
- atom now reads up to date.
- repeat steps 5 to 10 and the outcome never changes
Expected behavior: Atom should read +1, -1 lines changed
Actual behavior: Atom shows all lines in file removed and an equal number replaced.
Reproduces how often: This occurs on a freash install of Atom and a newly cloned repo.
Versions
I have done a fresh install using the atom-x64-windows.zip package.
It was install on a USB drive on a pc with Windows 7. I have followed the flight manual for converting to portable mode e.g. move the .atom folder to the correct location.
There are no user installed packages.
atom --version
Atom : 1.14.4
Electron: 1.3.13
Chrome : 52.0.2743.82
Node : 6.5.0
apm --verison
apm 1.15.3
npm 3.10.5
node 4.4.5 x64
This is most likely because of your core.autocrlf settings in Git. Try setting it to false and see if that changes anything.
That seemed to do the trick. Thanks @50Wliu
Awesome, glad it worked!
@50Wliu
Heyyy, it's not a solution, it's a workaround!
I expect the plugin to show diff line just the same as git diff command does, why is it still not a thing?
Please reopen the issue.
Heyyy, it's not a solution, it's a workaround!
I expect the plugin to show diff just as git diff command does, why is it still not a thing?
@qwemaze It does work, and what you are referring to is not a workaround...
If you can reliably reproduce, then open a new issue with a detailed list of steps required to reproduce the problem, and also full details such as Atom version, output of git --version etc. It's practically impossible for us to help you based on your comment.
This is still happening to me, even with autocrlf set to false.
Correction: it works if i set autocrlf to false, delete the repo and clone once more.
This really does feel like a workaround and not a fix. Especially considering that the treeview detects changes just fine. Any chance to get this fixed?