quarto-dev / quarto-dev/quarto-cli
Add a way to configure quarto to look for a non-default TinyTeX installation
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
This comes from discussion at https://github.com/conda-forge/quarto-feedstock/pull/24#issuecomment-1648045509
There was a bug in the conda feedstock because it was trying to make TinyTeX install and available at another place than where Quarto is looking for.
Currently we only check the default installation for determining if this is TinyTeX
https://github.com/quarto-dev/quarto-cli/blob/49f1bd16e341f59087b346481756be50281419da/src/tools/impl/tinytex-info.ts#L23-L34
it could be interesting to have a way to configure this in case of a non default installation. It could be as simple as an environment variable that we would use if set.
@dragonstyle opening this to discuss before doing anything.
Contributor guide
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 with src/tools/impl/tinytex-info.ts at the referenced detection logic, then review the linked conda-forge discussion for the non-default installation problem. Define and implement a configuration path for locating TinyTeX while preserving the default behavior; done means Quarto can detect a non-default installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- latex, typescript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100