This repository has been archived by the owner. It is now read-only.

Doesn't show changes in gutter when there is a symlink in path to git repository on Windows 10 #91

hron opened this Issue Mar 9, 2016 · 4 comments


None yet
6 participants
Copy link

hron commented Mar 9, 2016

Let's say we have a git repo in E:\src\project and there is a symlink to src in home folder C:\Users\aleks\src -> E:\src.

git-diff works without problems when Atom opens target directory E:\src\project, but when Atom tries to open this project using the symlink, i.e. C:\Users\aleks\src\project git-diff doesn't show changes in the gutter.

However, tree-view always shows the changes. Atom also shows branch name in the status bar in both cases.

@50Wliu 50Wliu added the bug label Mar 9, 2016


This comment has been minimized.

Copy link

florianb commented May 26, 2016

This bug seems to be OS unspecific - i am using Mac OS X:

Error getting line diffs for /Users/florianb/github/linter-javac/spec/sym-fixtures/sub-directory/ function) @ /Users/florianb/github/atom/node_modules/git-diff/lib/
Error: the path 'sym-fixtures' exists but is not a tree(…)(anonymous function) @ /Users/florianb/github/atom/node_modules/git-diff/lib/

apm  1.9.2
npm  2.13.3
node 0.10.40
python 2.7.10
git 2.7.4

This comment has been minimized.

Copy link

rk-development commented Jul 19, 2016

I can confirm.
When i open the project through the orginal path everything seems to work fine, but when i use my path with junction folder in it, it doesn't show the changed file and/or changed lines.

I also found that if we focus another window (instead of atom) and we get back to atom again, we will get changes in file list (coloured names), but still no indicator in lines.

Windows 10 PRO
Atom 1.8.0

@Mouvedia Mouvedia referenced this issue Sep 17, 2016


Does not work #85


This comment has been minimized.

Copy link

steve2507 commented Nov 12, 2016

I have the same issue with drive mappings to a Windows share. Not sure if I should open a new issue for that, as it may very well be related.


This comment has been minimized.

Copy link

maxbrunsfeld commented Sep 7, 2018

A lot has changed since we've heard about this, and I can't reproduce it on mac os. So the issue may have been fixed. If not, please feel free to open a new issue on the main Atom repository, as we have moved this code there. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.