Garrett Campbell

@AlMar-Devel Do you have a repro project? I have tested this for a similar issue #3687 and I wasn't able to reproduce the issue. We add the configure environment, which...

@SimonBoorer This is definitely something that would be nice. I will add this to our backlog. THanks.

Closing, fixed in #3775

@talyz Thanks for posting this issue! I'm glad there is a workaround. We'll add it to the backlog as we agree, it's not the most convenient.

@WittonBell Could you translate into English for us please? That would greatly improve our ability to understand and triage this. Thanks!

@WittonBell Is there any specific project that this reproduces on? Or is this generic to any project using kits?

Hi @danniesim, before reviewing this PR, we'd like to understand more about these scenarios and why setting the `cmake.configureOnOpen` and other types of settings don't already handle this. To my...

@danniesim Curious to have your feedback from the above message. Also, I'm curious about your thoughts on whether this PR #3703 fully solves this issue, or only partially. My initial...

@danniesim I'm revisiting this, and I'm trying to wrap my head around all the cases that you're seeing this happen. From what I can tell, if users set `cmake.configureOnOpen` to...

@danniesim Could you possibly send me a repro project / workspace to test with? I'd love to test this and while I could create miy own, it'd be good to...