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

C++ documentation regarding wildcards in tasks #12050

Closed
RuddeK opened this issue Mar 1, 2024 · 1 comment
Closed

C++ documentation regarding wildcards in tasks #12050

RuddeK opened this issue Mar 1, 2024 · 1 comment
Assignees

Comments

@RuddeK
Copy link

RuddeK commented Mar 1, 2024

The documentation for GCC for Linux and GCC for WSL mention the possibility of using Linux wildcards in paths (see section "modifying tasks.json"). However, when I modify the args to include a wildcard, the task wraps the path inside 'single quotes' and single quotes prevent wildcard expansion (this also happens when there are spaces in the path).
I found that the workaround should be to create an object that specifies a weak quoting mode. Unfortunately, the task fails silently when I change "${fileDirname}/*.c" to {"value": "${fileDirname}/*.c", "quoting": "weak"} with no indication for what the problem is. By failing silently I mean that nothing happens when I press the run button or CTRL+SHIFT+P > C/C++: Run C/C++ File.
I'm not interested in what the workaround is, but that the documentation includes a working example of selecting all files ending with .c from a folder.
Attachments: tasks.json

Thank you in advance!

Edit: Note that "${fileDirname}/main.c" works, but targets only a single file. For targeting multiple files I have to add them all manually to the tasks.json.

@ntrogh ntrogh transferred this issue from microsoft/vscode-docs Mar 2, 2024
@Colengms
Copy link
Contributor

Colengms commented Mar 4, 2024

This is a duplicate of #12001 and not a doc issue. This is addressed in 1.19.5, pending release shortly. Closing this as a duplicate.

@Colengms Colengms closed this as not planned Won't fix, can't repro, duplicate, stale Mar 4, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Apr 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants