Allow for a Breakpoint to be Enabled when breakpoints are deactivated

[JohanssonDaniel]

• VSCode Version: 1.31.0-insider (user setup)
• OS Version: Windows_NT x64 10.0.17134

Steps to Reproduce:

1. Create a breakpoint
2. Deactivate all breakpoints in the debug view
3. Try to enable one breakpoint
4. The context menu shows Disable Breakpoint
5. Clicking this option correctly switches it to Enable Breakpoint. However, since breakpoints are deactivated, the breakpoint is still not used.

Expected Behavior

The context menu shows Enable Breakpoint which would allow for a quick way to disable all breakpoints except one.

Does this issue occur when all extensions are disabled?: Yes

[vscodebot]

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

• Conditional breakpoints: up/down to navigate through condition history (#50412)
• Breakpoints not visible in gutter and editor (#64117)
• Expose the Id in the base Breakpoint class (#48722)
• After removing breakpoint, its still stopping the iteration flow (#64072)
• Breakpoint set but not yet bound when opening a folder via symlink since 1.28.0 (#63855)

[JohanssonDaniel]

I have been looking to try to solve this myself, however, the main problem seems to be that the debug view deactivates all breakpoints instead of disabling them. If I could continue to work on this, I think I need to know more about the main reason as to why both deactivating and disabling is used.

[isidorn]

Leaving this open as a feature request for now.
Not convinced we need it.
I would prefer that enabling any breakpoint activates all breakpoints, and as that I would treat this as a bug.
Chrome dev tools behaves just like that for example

[vscodebot]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!