Garrett Campbell

@malsyned I think I like option 2 as it's more generic, and as you said, it might be more future-proof, thanks!

@bebuch @Amy-Li03 Thank you for your patience. I would expect this to be a "medium" feature. It should be relatively easy to follow the pattern of the `CMake: Build Target`...

@bebuch We would encourage you to upvote the original issue as we often use the amount of upvotes from the community to assess priority. Thanks!

@jaegerj-curtis @BenFrantzDale This is correct, we have not updated to Presetsv10 yet. However, you can enable the `cmake.allowUnsupportedPresetsVersions` setting. We hope to implement v10 soon

Implemented in pre-release, closing.

@borjamunozf @Amy-Li03 Thanks for the investigation! We have been notified of this before and have it on our backlog to investigate: #4283. However, the possible bad performance location in the...

@JVApen If I'm understanding your issue correctly, I think the easiest way to fix this is to disable the automatic configure using the `cmake.configureOnEdit` setting.

I believe that it should be able to be cancelled, often times I have to click the notifications button in the bottom bar of the screen in order to show...

@JVApen I'm not sure I understand. What exactly isn't working for you? I believe there was confirmation that the `cmake.configureOnEdit` setting makes it so that the automatic configuration doesn't happen,...

@JVApen OH, are you saying that, in the event that a user has the `cmake.configureOnEdit` enabled, slightly modify the behavior of the automatic configure to kill the currently running configure...