Skip to content

Whole file highlighted as changed #164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
basil-gray opened this issue Aug 7, 2018 · 2 comments
Closed

Whole file highlighted as changed #164

basil-gray opened this issue Aug 7, 2018 · 2 comments

Comments

@basil-gray
Copy link

VS 2017 15.7.4

The margin of the entire file is highlighted in blue as soon as any change is made to the file, even if it's just adding a space. In some files, only parts of the file will be highlighted in blue though I haven't been able to identify a pattern with this.

2018-08-07_17-12-43

Hitting backspace and saving the file doesn't get rid of the blue highlight, though CTRL+Z does.

The below example shows a file where it doesn't highlight the whole file as changed (see the scroll bar on the right)

2018-08-07_17-14-49

Using the Visual Studio diff tool only highlights those areas as expected. I've tried resetting VS to default settings, reinstalling the extension as well as switching between branches. Any advice on what could be causing this?

Thanks!

@laurentkempe
Copy link
Owner

Thanks for the report @ambiguousrocket

Could you check if something the following issue #82 is the same problem?

@basil-gray
Copy link
Author

Sorry for the late response!

I found out that the issue was only affecting certain branches. The line endings weren't being normalised. It was that the .gitattributes file in those branches had lind endings set to auto hence differences being flagged between the origin and the current file. Thanks for the help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants