mesonbuild / mesonbuild/vscode-meson
[Feature request] Use shell for meson invocation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 138
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Feature description: use default shell for all `meson` invocations (the same way as `ninja` task are currently invoked).
Reasoning:
v1.2.0 added an awesome IDE integration, but it works only with native `meson`. Which means, it can't utilize `meson` that is present only in default shell (e.g. WSL shell).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the extension invokes Meson and compare it with the existing Ninja task invocation, especially the default-shell behavior described in the issue. Done means all Meson invocations use the default shell so Meson available only there can support the IDE integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- build-system, devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100