Skip to content
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

Current line annotations are hidden when debugging #382

hejianghu opened this Issue May 25, 2018 · 3 comments


None yet
3 participants
Copy link

commented May 25, 2018

  • GitLens Version: 8.3.2
  • VSCode Version: 1.23.1
  • OS Version: macOS 10.13.2

Steps to Reproduce:

  1. open the debug mode of VSCode
  2. focus any line of a git repository file
  3. the change information of this line could not appear
  4. close the VSCode's debug mode and the information shows up

It's not a big problem, but a little frustrating...


This comment has been minimized.

Copy link

commented May 25, 2018

This is by design because the vscode debugging experience can also add decorations to the end of the lines (variables, etc) and GitLens can conflict with them. You can manually toggle them back on during a debugging session by using the Gitlens: Toggle Line Blame Annotations command from the command palette.

Please let me know if that work-around isn't enough, and I can probably add a setting to stop turning off the annotations when debugging.

@eamodio eamodio changed the title the change info will be hidden when I use the debug mode of VSCode Current line annotations are hidden when debugging May 26, 2018


This comment has been minimized.

Copy link

commented Jun 4, 2018

@eamodio ok, thank you a lot!

@hejianghu hejianghu closed this Jun 4, 2018


This comment has been minimized.

Copy link

commented Mar 21, 2019

That workaround is fine, but it would be a lot more convenient to have a setting that won't stop line annotations when in debug mode rather than having to do that everytime. Not sure how easy that would be for you to add, and also sorry for commenting on this closed issue.

Let me know if that's at all possible or if you'd like some help.

@eamodio eamodio reopened this Apr 1, 2019

@eamodio eamodio self-assigned this Apr 1, 2019

@eamodio eamodio added this to the Soon™ milestone Apr 1, 2019

@eamodio eamodio closed this in fa9f119 Apr 8, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.