@@ -135,7 +135,7 @@ only on the last hyphen when the suffix starts with a digit.
135135Values resolve in this order : ` ${PACKAGE_ROOT}` , `${VERSION}`, `${NAME}`,
136136` ${PATHSEP}` (`:` on Unix / `;` on Windows), `${EXE_SUFFIX}` (`""` on Unix /
137137` ".exe"` on Windows), then any `${VAR}` set by previously resolved packages or
138- the inherited environment, and finally `~/` — which expands at every path
138+ the inherited environment, and finally `~/`, which expands at every path
139139segment, so `~/USD/bin${PATHSEP}~/USD/lib` works as expected. On Windows
140140PowerShell sessions `~/` falls back to `USERPROFILE` when `HOME` is unset.
141141
@@ -147,7 +147,7 @@ through.
147147
148148The `commands` map lets `anvil run` pick a program from the package definition.
149149Values expand the same way as `environment` values, and can include baked in
150- arguments with whitespace or tilde segments — anvil tokenises the value with
150+ arguments with whitespace or tilde segments. Anvil tokenises the value with
151151POSIX shell rules, expands `~/` in every token, then runs the first token
152152with the remaining tokens prepended to whatever the user passes after `--`.
153153
@@ -167,7 +167,7 @@ commands:
167167` ` `
168168
169169` anvil run nukex -- --view` therefore exec's
170- ` ${NUKE_HOME}/Nuke${VERSION} --nukex --view` — packages can ship sane defaults
170+ ` ${NUKE_HOME}/Nuke${VERSION} --nukex --view` . Packages can ship sane defaults
171171for every tool they expose without forcing users to memorise flag soup. Quoted
172172substrings are preserved as a single argv element, so paths with spaces work
173173without escaping the whole value.
0 commit comments