search

gkotas / vscode-restore-git-branch-tabs

MIT License
29 stars 10 forks source link

Endless scrolling over opened tabs after switching git branch #22

Open alan6k8 opened 2 years ago

alan6k8 commented 2 years ago

After latest update of VS Code this amazing feature ceased to work right. When I switch branch, endless rotation of opened tabs occures. I have to close them all but one and than it stops.

Is there any chance to have this resolved?

Version: 1.63.0 (system setup) Commit: 7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e Date: 2021-12-07T06:26:56.179Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 6.1.7601

alfreema commented 2 years ago

We are having the same issue. It's the same effect as if someone were just hitting ctrl+tab super fast causing the editor to switch from tab to tab to tab super quickly. When it starts, the only way I have found to get it to stop is to click on the Extensions icon on the left and click any extension. That stops the crazy rotation.

We love this plugin but have to disable it for now.

alfreema commented 2 years ago

I love this plugin and don't want to abandon it, but it has become unusable. Is there another alternative out there?

lgibso34 commented 2 years ago

Experiencing this too. Disabled the extension for now.

fizvlad commented 2 years ago

For anyone looking for alternative take a look at Git Branch-wise Session. It's a bit different, but works for me

ravihlb commented 2 years ago

Also having this problem.

avaly commented 2 years ago

I also ran into this issue earlier this year.

I published a forked extension with other unrelated smaller features added: https://marketplace.visualstudio.com/items?itemName=avaly.restore-git-branch-tabs-improved

While I haven't done anything specifically to counter this bug, I haven't experienced it since I started using the fork. Try it out as well!

avaly commented 2 years ago

I looked into this today in my forked extension and found the issue and pushed a fix there.

It's available in v1.0.1 of the forked extension.

BarkenBark commented 2 years ago

I looked into this today in my forked extension and found the issue and pushed a fix there.

It's available in v1.0.1 of the forked extension.

Great work, thank you! Tried it out and the extension behaves just like the original used to ^^