You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chances are that when I'm using GitDiffMargin, I won't want the build in 'Track changes' enabled. Having both bars is confusing and cluttered.
The problem is, it isn't necessarily obvious how to disable to built in 'Track changes' option. Even though I know the option exists, I still sometimes forget where to look. 😕
It would be nice if there was an option to disable it on the GitDiffMargin menu (that's only visible when the option is enabled). Eg. here:
That would make it easy to get Visual Studio into the state the user probably wants (even if they don't know it 😉). It would still be a user initiated action, so it wouldn't be automatically disabling built in functionality.
The text was updated successfully, but these errors were encountered:
It might be nice if this was just mentioned in the README somewhere. I had no idea what the option was called so I didn't really know where to look. Luckily I found this issue :) Thanks!
Thanks for the feedback @MarlonGamez
I updated both README for GitHub and VS Marketplace. You can already see the change on GitHub and on VS Marketplace it will be available with next release.
Chances are that when I'm using GitDiffMargin, I won't want the build in 'Track changes' enabled. Having both bars is confusing and cluttered.
The problem is, it isn't necessarily obvious how to disable to built in 'Track changes' option. Even though I know the option exists, I still sometimes forget where to look. 😕
It would be nice if there was an option to disable it on the GitDiffMargin menu (that's only visible when the option is enabled). Eg. here:

That would make it easy to get Visual Studio into the state the user probably wants (even if they don't know it 😉). It would still be a user initiated action, so it wouldn't be automatically disabling built in functionality.
The text was updated successfully, but these errors were encountered: