Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ctrl+F5 shortcut does not work the same as manually clicking Debug -> Start Without Debugging #81195

Closed
DanTup opened this issue Sep 19, 2019 · 4 comments · Fixed by microsoft/azuredatastudio#7356
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded

Comments

@DanTup
Copy link
Contributor

DanTup commented Sep 19, 2019

If you have multiple debug configurations, this works:

  • Select first debug config on the debug side bar
  • Click Debug -> Start Without Debugging
  • Select second debug config on the debug side bar
  • Click Debug -> Start Without Debugging

Against the Start Without Debugging menu entry, it says the shortcut key is Ctrl+F5. Yet if you perform the same steps above using F5, the second debug configuration will not launch.

I think this is because the keybind has !inDebugMode as a condition, but I think this is confusing and unwanted. If a menu entry is enabled, and shows a shortcut key, that shortcut key should do the same thing as clicking on the menu entry.

@vscodebot
Copy link

vscodebot bot commented Sep 19, 2019

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@isidorn isidorn added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues labels Sep 20, 2019
@isidorn isidorn added this to the September 2019 milestone Sep 20, 2019
@isidorn
Copy link
Contributor

isidorn commented Sep 20, 2019

@DanTup good catch, thanks for reporting. You can try it out with Monday's vscode insiders and let us know if this gets fixed for you.

@DanTup
Copy link
Contributor Author

DanTup commented Sep 30, 2019

LGTM, thanks!

@isidorn
Copy link
Contributor

isidorn commented Oct 1, 2019

Thanks, adding verified label.

@isidorn isidorn added the verified Verification succeeded label Oct 1, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants