Skip to content

Commit

Permalink
add new quarto check output, julia guidance (#1403)
Browse files Browse the repository at this point in the history
  • Loading branch information
cscheid authored Oct 23, 2024
1 parent a3d12da commit 139d5f7
Showing 1 changed file with 13 additions and 6 deletions.
19 changes: 13 additions & 6 deletions docs/troubleshooting/index.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -13,16 +13,18 @@ but this page might help you get up and running quickly.
You can check the version of Quarto and its dependencies by running `quarto check`. Here's an example of the output it generates:

```
Quarto 1.5.42
Quarto 1.6.30
[✓] Checking environment information...
Quarto cache location: /Users/cscheid/Library/Caches/quarto
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.2.0: OK
Pandoc version 3.4.0: OK
Dart Sass version 1.70.0: OK
Deno version 1.41.0: OK
Deno version 1.46.3: OK
Typst version 0.11.0: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 1.5.42
Path: /Applications/quarto/bin
Version: 1.6.30
Path: /Users/cscheid/repos/github/cscheid/quarto-regress/releases/v1.6.30/binQuarto 1.5.42
[✓] Checking tools....................OK
TinyTeX: v2024.03.13
Expand Down Expand Up @@ -154,7 +156,7 @@ issues with rendering to PDF, make sure you have an up-to-date installation of `

One common source of tricky problems is the presence of multiple installations of R and Python in a system. Quarto will attempt to find an R or Python installation, and sometimes your shell environment is pointing to a different one.

### knitr
### `knitr`

If you suspect that quarto is finding the wrong version of an R installation, you can obtain information about the R installation that Quarto sees by running the following .qmd file:

Expand Down Expand Up @@ -182,6 +184,11 @@ can ask for a difference between the outputs more directly:
sessioninfo:::session_diff(new = "quarto-session-info-output.txt")
```

### `julia`

One potential source of trouble in Julia execution and installationwith both the `jupyter` and `julia` engines are stale library versions in caches.
In those situations, consider removing the contents of the directory described under `Quarto cache location` in `quarto check`.

## Advanced

### Debugging Jupyter engine issues
Expand Down

0 comments on commit 139d5f7

Please sign in to comment.