You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lines inside the fenced blocks may either start with `#` (as in the example), be plain TOML, or be wrapped in multi-line comment delimiters `#= ... =#`:
425
-
426
-
```julia
427
-
#!project begin
428
-
#=
429
-
name = "HelloApp"
430
-
uuid = "9c5fa7d8-7220-48e8-b2f7-0042191c5f6d"
431
-
version = "0.1.0"
432
-
[deps]
433
-
Markdown = "d6f4376e-aef5-505a-96c1-9c027394607a"
434
-
=#
435
-
#!project end
436
422
```
437
423
424
+
Lines inside the fenced blocks should be commented with `#` (as in the example) or be plain TOML lines. The `#!project` section must come first in the file (after an optional shebang and empty lines). If a `#!manifest` section is present, it must come after the `#!project` section, and no Julia code is allowed after the `#!manifest end` delimiter.
438
425
439
426
Running `julia hello.jl` automatically activates the embedded project. The script path becomes the active project entry in `LOAD_PATH`, so package loading works exactly as if `Project.toml` and `Manifest.toml` lived next to the script. The `--project=@script` flag also expands to the script itself when no on-disk project exists but inline metadata is present.
0 commit comments