A major VS Code extension (which comes installed with VS Code) isn't working for me. I've read bug reports for the behavior I'm seeing and the resolution isn't working for me either.
I want to use Extension Bisect to troubleshoot which other extension is inhibiting this one. However, it seems that Extension Bisect's first step is to disable all extensions and then ask me if the problem is still there. Yes, the problem is 'still' there because it disabled the extension with the feature I'm trying to troubleshoot.
Q: How can I tell Extension Bisect to not disable the specific extension with the feature I'm troubleshooting?
It's counter-intuitive, but you can actually keep an extension enabled during bisection by disabling it before starting the bisect, then manually re-enabling it after the bisect has calculated its todo-list.
extension.bisect.start);