Skip to content
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

The extension should not ask for a cmake file on projects that are not C++ #2254

Closed
danielo515 opened this issue Nov 18, 2021 · 4 comments
Closed
Labels
duplicate a duplicate of an already present issue upstream Bugs related to issues in an upstream project

Comments

@danielo515
Copy link

Issue Type: Bug

I work with a lot of codebases, and just a very few of them are C/C++
However, this extension keeps asking me to create Cmake files on every project I open. Ideally the extension should detect the project language and don't bother me with it unless it is an obvious C/C++ project.

Extension version: 1.7.1
VS Code version: Code 1.61.2 (6cba118ac49a1b88332f312a8f67186f7f3c1643, 2021-10-19T15:49:28.381Z)
OS version: Darwin x64 20.6.0
Restricted Mode: No

System Info
Item Value
CPUs Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (12 x 2900)
GPU Status 2d_canvas: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 34, 34, 17
Memory (System) 32.00GB (0.09GB free)
Process Argv --crash-reporter-id 3bf10e6d-54c9-4df4-8aaa-781f2b9fc1b9
Screen Reader no
VM 0%
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30384385
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
dockerwalkthru:30377721
bridge0723:30353136
pythonrunftest32:30373476
pythonf5test824:30373475
javagetstartedt:30391933
pythonvspyt187:30373474
vsqsis200:30402016
vsaa593:30376534
vssld246:30401890
vscexrecpromptt3:30400063

@bobbrow
Copy link
Member

bobbrow commented Nov 18, 2021

Unfortunately, the problem is that VS Code activates our extension against our declared intentions and doesn't tell us that or give us a way to know that it happened. This issue would give us the information we need to not bother you: microsoft/vscode#44711.

Related: #2127

@bobbrow bobbrow added duplicate a duplicate of an already present issue upstream Bugs related to issues in an upstream project labels Nov 18, 2021
@bobbrow
Copy link
Member

bobbrow commented Nov 19, 2021

The VS Code team just made a change to stop activating extensions when the search for CMakeLists.txt times out. It should appear in the next VS Code Insiders build.

microsoft/vscode#135673 (comment)

@bobbrow bobbrow closed this as completed Nov 19, 2021
@danielo515
Copy link
Author

Thanks for the quick fix! Even if it takes a couple of days to release 😄

@bobbrow
Copy link
Member

bobbrow commented Nov 19, 2021

Today's Insiders build might already have it. I'm not sure when the next stable build will release. I assume early December.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate a duplicate of an already present issue upstream Bugs related to issues in an upstream project
Projects
None yet
Development

No branches or pull requests

2 participants