Strange rendering artifact

[dracan]

On my work machine a particular file is rendering a strange vertical line to the left of the editor window ...

I've seen this happen to two different files. It doesn't seem to be the file itself, as if I copy the file to another folder it fixes it. So something must be remembering the absolute path to this file. I've even tried deleting all the folders in the C:\Users\dan.clarke\AppData\Roaming\Caret that have the name cache, to see if something was being cached there, but it doesn't fix the issue. I can't find any way of removing these rendering artifacts.

[astoilkov]

This is supposed to be a Git indication showing that the file has changed. Is the folder where file is a Git project?

[dracan]

Oh, I see! I didn't realise Caret did that. Yes, it is in Git - however, there are no pending changes against that file. It still shows that line for the whole file.

[astoilkov]

What is true for the file:

• it is pushed to the public repository and there are no local changes to the file
• there is a local commit for the file but it is not pushed to the public repository
• the file is completely new and it is work in progress

[dracan]

"it is pushed to the public repository and there are no local changes to the file"

[astoilkov]

Do you experience the same problem for other files in the same repository?

[astoilkov]

Is this a public repo that we can clone so we can test this?

[dracan]

Yep, just tried another file, and it does the same. Unfortunately, it's a not a public repo. I can try it this evening on a public repo though. I'll just create a temporary github repo to test.

[dracan]

Sounds very much line a line-ending issue to me. I'm on Windows - so perhaps a CR/LF thing?

[dracan]

My Git config is set to have this core.autocrlf=true.

[astoilkov]

Yes. This sounds possible. We will test different configurations tomorrow. Thanks a lot for the detailed and helpful information.

[dracan]

No problem! Thanks a lot for such an awesome app! Also, for the Git integration! That's very cool - I didn't know Caret did that :)

[astoilkov]

We replicated the problem and fixed it. We will release a new version of Caret tomorrow.

[dracan]

Great work! :) Thank you for such a very fast response and resolution! :)

[astoilkov]

This is now fixed in the latest 3.2.2 Caret release.

Closing this issue.