Garrett Campbell

@v-frankwang My reading of this is that it's a feature request. Thanks.

@v-frankwang @thernstig This sounds like a possible bug and something that we should investigate. Thank you for bringing it to our attention!

@thernstig Thanks for the feedback. We can definitely take a note to update our documentation for the feature. We will continue to track this issue for the issue of adding...

> I think it would instead make sense to inner source this to the VS Code repo instead as a generic "pinned commands" functionality. And that extensions then possibly can...

@Jack-Bie Does this mean that this issue can be closed? Or is there still an underlying issue that we should solve to make this experience easier?

@v-frankwang They have successfully found a workaround, but we still hope to investigate this and make it easier for users. We have this item in our "On Deck" Milestone which...

@punowo @agarny Thanks for your questions, we have it marked for the next milestone and will be investigating it soon, thanks!

@LinHuan86 Looks like this is still a bug that we need to address, but in the meantime, an easy workaround is to construct your own launch.json configuration for debugging. Thanks...

Closing as this behavior is expected.

@bebuch Thanks for your update and your ping on this issue. I took a quick look and unfortunately the fix is not as simple as it might seem. vscode doesn't...