I disabled all the extension and none of the problems occurred. I then enabled every extension one by one each time to check which extension is causing this issue. I found gitlens extension when enable, cause this problem.
I then disabled all the extension and enabled only gitlens to confirm if this is causing the issue and was right.
Please fix this issue.
Your extension is very helpful and I love using it. Nice work.
Thanks.
Unfortunately I can't see how this could possibly happen outside of a corrupted vscode install or bugs within vscode itself. Vscode provides extensions a very limited api to work with, and GitLens cannot control when menus are shown or not -- all I can do is tell vscode (statically in my package.json) that GitLens wants a set of menu items added to a set of named menus and a condition for when.
Are you running any other extensions or things that modify the base vscode install? You might also want to try setting "window.titleBarStyle": "native" to see if that has any affect on the issues you are seeing.
Currently, I am not running any other extensions or things that modify the base vscode install.
I am not facing the above issue after I uninstalled GitLens extension.
Let me install it again and tell you if the problem returned.
Thanks.
After installing it again, I can confirm that the issue returned. I don't know why is this happening !!
Have you tried setting "window.titleBarStyle": "native" and then restart vscode?
As suggested by you, I tried setting "window.titleBarStyle": "native" and found the issue no longer persist.
the editor is functioning normally without any problem.
Probably the problem is with VS code custom title bar. But why did the problem occurred only when gitlens was installed? Is it related to this extension also?
Hrm, definitely a vscode bug -- something that GitLens must expose (though I fail to understand how). I would recommend opening an issue with the vscode repo and reference this issue. Hopefully they can get to the bottom of the issue.
Alright, I'm opening this issue in the vscode repo referencing this issue.
Thanks for the help.
@eamodio The above issue was due to this https://github.com/Microsoft/vscode/issues/57399
It is now fixed in the latest build of VS code i.e. v1.28
Thanks :)
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.