Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Output tab cannot be pinned to the second column
See original GitHub issueDescription:
When running a query in the VsCode (using Shift+Enter in MacOs), the output tab opens in the second column, when rerunning the same query for the second time the output tab opens in the first column.
https://user-images.githubusercontent.com/4527650/148527967-3879508d-b59b-4f0f-ac6b-3afae32dfd18.mov
Expected outcome
Every time a query is run the output tab must open in the column it was opened before, instead of opening the tab in the first column.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This is fixed with the nightly vscode 1.64 build via microsoft/vscode#138914 via 57e2ed6.
I can replicate this…
The problem comes from a
editor.reveal()call that is used to focus the existing query result window to the foreground of it’s respective panel in case it isn’t already visible.This used to work fine, the recent vscode update I think changed something.
Even though it’s being called to reveal in the same ViewColumn it’s already in it appears to be switching, which I agree is highly annoying.
Still investigating, but this may be an issue with vscode and not the extension.