Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Windows: `quarto.path` pointing at a `.cmd`-only dev binary is detected as a file but silently falls back to PATH

Abierto
  • ¿Algo no está bien?
#981 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
70/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
typescript
Área
devtools

Línea de trabajo

Start in packages/quarto-core/src/context.ts, reading detectUserSpecifiedQuarto, detectQuarto, readQuartoInfo, and the useCmd handling around the referenced lines. Reproduce the Windows setup with package/dist/bin/quarto.cmd and the quarto.path setting, then verify that the configured .cmd binary is version-probed and selected rather than silently falling back to PATH.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug vscode

When the user sets quarto.path to an absolute path of a Quarto build that ships only quarto.cmd on Windows (typical for the in-repo dev binary at package/dist/bin/quarto.cmd after ./configure.cmd), the extension's existence check passes but the subsequent version probe fails. The extension then silently falls back to the system PATH, so the user-specified dev binary is never actually used.

Mechanism

detectUserSpecifiedQuarto validates the file exists and is a file (passes for quarto.cmd), then calls detectQuarto(quartoPath):

https://github.com/quarto-dev/quarto/blob/dec89b21972b16fc3da2807d51206cd7c165006c/packages/quarto-core/src/context.ts#L194-L211

readQuartoInfo calls execProgram(quartoPath, ["--version"]). On Windows, child_process spawn on an absolute path to a .cmd file fails without shell: true because Windows requires cmd.exe to interpret .cmd files. The catch block retries with quartoPath + ".cmd" — but when the user already passed …\quarto.cmd, the retry becomes …\quarto.cmd.cmd, which does not exist. Both attempts fail, detectQuarto returns undefined, and the extension falls through to the PATH branch.

There is no warning surfaced — detectUserSpecifiedQuarto only warns when fs.existsSync or isFile checks fail, not when the version probe silently fails:

https://github.com/quarto-dev/quarto/blob/dec89b21972b16fc3da2807d51206cd7c165006c/packages/quarto-core/src/context.ts#L224-L248

The useCmd flag only adjusts the execution-time path; it does not help at detection time:

https://github.com/quarto-dev/quarto/blob/dec89b21972b16fc3da2807d51206cd7c165006c/packages/quarto-core/src/context.ts#L138

Reproduction

On Windows:

  1. Clone quarto-dev/quarto-cli, run ./configure.cmd. This produces package/dist/bin/quarto.cmd with no quarto.exe sibling.
  2. In Positron/VS Code settings, set quarto.path to the absolute path of that quarto.cmd.
  3. Reload the window.
  4. Open a .qmd and run any Quarto extension command (Preview, Verify Installation, render).

Observed: the dev binary is not used. The extension picks up whatever quarto is on PATH (in my case, a quarto-prerelease install from Scoop).

Quarto output channel log 
[info] Activating Quarto extension.
[info] Searching for Quarto CLI...
[info]   Checking quarto.path setting: C:/Users/chris/Documents/DEV_R/quarto-cli.worktrees/issue-14533/package/dist/bin/quarto.cmd
[info]   Checking system PATH...
[info]   Found Quarto 1.10.3 on system PATH
[info] Using Quarto 1.10.3 from C:\Users\chris\scoop\apps\quarto-prerelease\current\bin (found on system PATH)
[info] Activated Quarto extension.

Note: no warning between the quarto.path check and the PATH fallback. The user has no diagnostic indicating their setting was discarded.

Suggestion

We could either:

  • Detect a trailing .cmd on quartoPath at detection time and spawn with shell: true (or wrap in cmd /c).
  • Or trim the trailing .cmd from quartoPath before passing to readQuartoInfo, so the fallback at L208 can append .cmd cleanly without producing quarto.cmd.cmd.
  • Or at minimum, surface a warning when the existence check passes but the version probe fails, so users get a clear diagnostic instead of silent fallback.

This blocks testing dev binaries against the extension end-to-end on Windows, which is what I hit while validating a quarto-cli fix that surfaces only when the extension is the client. Related to #352, which describes a different mechanism (terminal env-var prepend race on non-bash shells) producing the same user-visible symptom ("quarto.path is ignored").

Lenguaje dominante
TypeScript
Estrellas
652
Forks
64
Merge medio
8 h 45 min
PR fusionados (30 d)
36

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de quarto-dev/quarto

Todos los issues de quarto-dev/quarto

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.