feat: cleanup with respect to core
Build, test, deploy / site (push) Failing after 1m37s

This commit is contained in:
alexm committed 2026-10-06 10:30:36 -04:00
1 parent e525f1d26f
commit ce45d30cc7
10 files changed
+24 -24

No files matched your search

+2 -2
View File
@@ -157,14 +157,14 @@ In a format other than HTML (a PDF, a Word file), a rendered view becomes Markdo
Or arrange it in the playground itself and paste the result: **Share** → *embed which view* → **Quarto** gives a `{{< pplus-playground state="…" >}}` or `{{< pplus-embed state="…" view="…" >}}` shortcode for exactly what you see, layout and step included.
### A Mojo program from `core/mojo/local/`, with its assembly
### A Mojo program from `core/library/mojo/local/`, with its assembly
```bash
pixi run --manifest-path core/pixi.toml play demo # verify it, and store the compiler's listing
pixi run quarto-export demo ../site/programmingplus/demo
```
This writes `demo.mojo`, `demo.asm` (the x86-64 pane's program) and `demo.setup` next to the page, and prints the shortcode that embeds them. The `# origin:`/`# probe:`/... header of a `core/mojo/local/` file is left out of the pane and the listing. Its `# expect-stdout:` lines count as `EXPECT` lines.
This writes `demo.mojo`, `demo.asm` (the x86-64 pane's program) and `demo.setup` next to the page, and prints the shortcode that embeds them. The `# origin:`/`# probe:`/... header of a `core/library/mojo/local/` file is left out of the pane and the listing. Its `# expect-stdout:` lines count as `EXPECT` lines.
## The machine