Skip to content

CTRL+SHIFT+B no longer gives the option to set up a build task when a cpp file is open #3674

Description

@dunhor

Type: LanguageService
When I do the key combo 'CTRL+SHIFT+B' on a new directory (not configured for any build task), it would previously prompt me to set up a new task. This was wonderful since I likely wanted to invoke cmake/ninja/etc. It is now, however, only presenting me the option to invoke cl.exe on the active file. While I can still go in and manually set up a new build task, it was very convenient to do everything the old way. This could also be an editor change unrelated to the extension, but it's still annoying nonetheless. FWIW if the active file is not a C++ file, then it presents me with the old experience, so I suppose at least I still have that

Describe the bug

  • OS and Version: Windows Insiders (but hit this on 1803 machine at home)
  • VS Code Version: 1.35.0-insider
  • C/C++ Extension Version: 0.23.1

Activity

  1. sean-mcmanus commented on May 21, 2019

    @sean-mcmanus
    Contributor

    Yeah, we recently changed it to add those default build tasks -- maybe we can add the "default" that was previously shown to the list as well, so the previous behavior is still obtainable.

  2. added this to the 1.0.0 milestone on Sep 24, 2019
  3. removed
    fixedCheck the Milestone for the release in which the fix is or will be available.
    on Jul 29, 2020
  4. locked and limited conversation to collaborators on Dec 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugfixedCheck the Milestone for the release in which the fix is or will be available.regressionA bug that didn't exist in a previous releasetasks/build/debugAn issue relating to tasks.json (e.g. build issues)verifiedBug has been reproduced

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions