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

Update typst.qmd #1407

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 36 additions & 0 deletions docs/output-formats/typst.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -315,3 +315,39 @@ format:
- text: |
#show heading: set text(navy)
```
## Custom Typst Configuration

By default, Quarto uses its built-in version of Typst to ensure compatibility and stable behavior. However, for advanced users who need to use features from newer Typst versions, Quarto can be configured to use an external Typst installation through the `QUARTO_TYPST` environment variable.

For example:

```bash
# Unix/macOS
export QUARTO_TYPST=/path/to/typst

# Windows PowerShell
$env:QUARTO_TYPST = "C:\path\to\typst"
```

:::caution
Using a custom Typst installation is considered experimental and may lead to unexpected behavior. Quarto makes no guarantees about compatibility when using versions of Typst other than the built-in version. Use this configuration at your own risk.
:::

The custom Typst binary can be installed through various package managers, including homebrew, cargo, Nix, and more.

```bash
# Homebrew (macOS/Linux)
brew install typst

# Cargo (Cross-platform)
cargo install typst

# Nix (Cross-platform)
nix-env -iA nixpkgs.typst
```

After setting `QUARTO_TYPST` and refreshing your shell, verify the configuration by checking which version of Typst Quarto is using:

```bash
quarto typst --version
```