@alexgorbatchev/dotfiles 0.0.4 → 0.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/cli.js +107 -107
- package/cli.js.map +8 -8
- package/package.json +1 -1
- package/skill/references/shell-and-hooks.md +7 -0
package/package.json
CHANGED
|
@@ -396,6 +396,11 @@ Tab completions are configured per-shell using `.completions()`:
|
|
|
396
396
|
> **Lifecycle**: All completions are generated only after `dotfiles install <tool>` succeeds,
|
|
397
397
|
> not during `dotfiles generate`. This ensures cmd-based completions can execute the installed
|
|
398
398
|
> binary and callbacks receive the actual installed version in `ctx.version`.
|
|
399
|
+
>
|
|
400
|
+
> **URL completions and hooks**: URL-based completion assets are downloaded or extracted during
|
|
401
|
+
> installation before `after-install` hooks run. This means `after-install` hooks can patch or
|
|
402
|
+
> sanitize those files in `ctx.installedDir` / `ctx.currentDir` before the completion symlink is
|
|
403
|
+
> emitted into the generated shell scripts directory.
|
|
399
404
|
|
|
400
405
|
## Configuration Options
|
|
401
406
|
|
|
@@ -493,6 +498,8 @@ The callback receives `ctx` with:
|
|
|
493
498
|
|
|
494
499
|
URL-based completions are downloaded to `ctx.currentDir`. For archives, they are automatically extracted and `source` specifies the path to the completion file within.
|
|
495
500
|
|
|
501
|
+
Because the download/extract step happens before `after-install`, hook code can modify the downloaded file in place before the generated shell completion symlink points at it.
|
|
502
|
+
|
|
496
503
|
**Supported archive formats**: `.tar.gz`, `.tar.xz`, `.tar.bz2`, `.zip`, `.tar`, `.tar.lzma`, `.7z`
|
|
497
504
|
|
|
498
505
|
## Dynamic Completions (cmd)
|