kule path
Print where a task's copy is on disk, or a file in it.
Synopsis
kule path [OPTIONS] <TASK> [FILE]
Description
The copy lives inside Kule's home, at <home>/tasks/<id>/w/<folder name>.
kule path prints that path, or the path of one file or folder in the copy,
so you can cd there, open it in an editor, or use it in a script.
FILE is a path inside the copy, relative to its top. Kule never follows a
link to get there, and refuses .., so the printed path is always inside
the copy.
Like kule shell, kule path warns on stderr when the task has
changed the copy's git config or hooks: git in that folder would run them
outside the sandbox. It still prints the path (a path alone runs nothing),
but take the warning seriously before you run git or open an editor there.
Only stdout holds the path, so command substitution works even with the warning.
Arguments
| Name | Required | Meaning |
|---|---|---|
TASK | yes | The task's full id. See Naming a task. |
FILE | no | A file or folder inside the copy, like src/main.rs. Without it, the copy itself. |
Options
| Option | Value | Default | Meaning |
|---|---|---|---|
--home | path | ~/.kule | Kule's home (also KULE_HOME). See global options. |
Examples
The copy:
$ kule path 3422f830
/Users/me/.kule/tasks/3422f830/w/app
Go there:
cd "$(kule path 3422f830)"
Open the copy in your editor:
code "$(kule path 3422f830)"
One file:
$ kule path 3422f830 src/main.rs
/Users/me/.kule/tasks/3422f830/w/app/src/main.rs
Compare a file with the workspace's:
diff ~/code/app/src/main.rs "$(kule path 3422f830 src/main.rs)"
The warning after a git config change:
$ kule path 3422f830
kule: careful in there: the copy's git config changed, and git there would run it outside the sandbox; review it, then commit or roll it back before opening a terminal
/Users/me/.kule/tasks/3422f830/w/app
Output
One absolute path on stdout. A warning, if any, on stderr starting with
kule: careful in there:.
Errors and fixes
| Message | What to do |
|---|---|
kule: <file>: No such file or directory (os error 2) | The file is not in the copy. Paths are relative to the copy's top. |
kule: <file>: a path inside the copy, without .. | Do not use .. or an absolute path. |
An editor runs things by itself from a folder: tasks, settings, recommended extensions, git hooks. If an agent worked in the copy, open it in VS Code's Restricted Mode (answer no when it asks whether you trust the authors). The app's Open the copy in your editor explains this the first time.
In the app
Copy path (⌥⌘C on macOS, Ctrl+Alt+C on Linux) on a file in Files, and Open the copy in your editor in the task's ⋮ menu. See Files and Preview.