-
Notifications
You must be signed in to change notification settings - Fork 29.3k
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
Clicking F11 while not in debug mode turns on debug instead of going full screen #141157
Comments
It seems these are both the defaults in 1.66.2.
So, for example, F11 starts debugging in a Node project but toggles full screen in other projects. |
Yes, it is unfortunate that F11 is the shortcut for |
Is there no way of having it go into "Start Debugging" mode when a specific condition is met? Something like Another option is to have F11 start debugging if the user is in the Debug tab of the sidebar. Just ideas, not something that is really needed, sense it isn't causing any urgent issues. |
Ultimately this will still cause a conflict for users who both want to toggle fullscreen and do use debugging. So we should relocate or specify one keybinding or the other... |
Reviewing this, looks like we have both "F10" and "F11" as keybindings. Unfortunately we don't have a way to differentiate which keybinding triggered entering debug mode in our telemetry, and a sizable number of users (>10K) have used one of these keybindings recently, so I don't just want to boot one of those off. I like the compromise of only running the command on F11 when the debug view is the active viewlet. |
Verified that F11 only starts debugging if the debug view is visible (also if not active) |
Have a few configurations (mine were javascript client/server attach) for the debugging and click F11, while not in debug mode, and have
Auto Attach
turned on withWith Flag
as the option.Once clicking F11, it tries to turn on debugging for a few seconds, and then stops:
This is the Output from the Log (Window) error that appears:
The text was updated successfully, but these errors were encountered: