Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

`quarto.path` is not used directly when it points to a launcher/trampoline executable

未关闭
#1,000 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
52/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
typescript, vscode

调研方向

Start by tracing how the configured quarto.path is handled for command execution and integrated-terminal PATH changes, using the Pixi launcher reproduction as the failing case. Done means commands use /home/***/.pixi/bin/quarto without bypassing its runtime setup, or an option prevents the automatic terminal PATH modification.

由索引模型根据 Issue 内容生成。

描述

bug vscode
Bug description

When quarto.path is explicitly configured, I expect the VS Code extension to invoke that executable, or at least preserve it as the effective Quarto command used by the extension and the integrated terminal.

However, the extension appears to use the configured executable only for discovery. It then resolves the underlying Quarto installation path, likely from quarto --paths, and prepends the resolved internal bin directory to the integrated terminal PATH.

This breaks installations where the configured Quarto executable is a launcher or trampoline, such as Quarto installed through pixi. In this setup, the launcher is not just a path alias: it is responsible for setting up the runtime environment required by Quarto. The internal Quarto script inside the Pixi environment is not intended to be executed directly.

Therefore, the issue is that quarto.path is not treated as the authoritative executable path. Instead, the extension rewrites the terminal environment in a way that bypasses the configured launcher.

Configuration
{
  "quarto.usePipQuarto": false,
  "quarto.path": "/home/***/.pixi/bin/quarto"
}
Steps to reproduce
  1. Install Quarto through Pixi, for example with:
pixi global install quarto
  1. Configure the VS Code extension to use the Pixi launcher:
{
  "quarto.usePipQuarto": false,
  "quarto.path": "/home/***/.pixi/bin/quarto"
}
  1. Open VS Code / VS Code Remote with the Quarto extension enabled.

  2. Check the integrated terminal PATH.

The extension prepends:

/home/***/.pixi/envs/quarto/bin
  1. Run:
which quarto
quarto check
Actual behavior

quarto resolves to:

/home/***/.pixi/envs/quarto/bin/quarto

Running quarto check then fails with:

/home/***/.pixi/envs/quarto/bin/quarto: line 208:
/home/***/.pixi/envs/quarto/bin/tools/x86_64/deno: No such file or directory

This happens because the command bypasses the Pixi launcher at:

/home/***/.pixi/bin/quarto
Expected behavior

When quarto.path is configured, the extension should treat that path as the authoritative Quarto executable.

In this case, commands should use:

/home/***/.pixi/bin/quarto

rather than resolving and prepending the internal Quarto installation directory.

At minimum, the extension should provide an option to disable automatic modification of the integrated terminal PATH.

主要语言
TypeScript
星标
652
派生
64
平均合并
8 小时 45 分钟
30 天内合并 PR
36

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

quarto-dev/quarto 的其他 Issue

查看 quarto-dev/quarto 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。