cuc-lib 0.1.0

Library for working with usage spec and cuc-cli.
Documentation
  • Coverage
  • 0%
    0 out of 97 items documented0 out of 46 items with examples
  • Size
  • Source code size: 33.63 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 5.55 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 31s Average build duration of successful builds.
  • all releases: 31s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Homepage
  • IMXEren/cuc
    1 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • IMXEren

cuc (Clink Usage Completions)

A CLI tool to generate clink argmatcher completions from the usage spec.

Installation

  1. Go to Releases and download the executable to a desired location.

  2. The generated usage.completions.lua requires that you have these modules in your package.path (you can also use !init.lua or .init.lua, to ensure the modules are added to package.path):

  3. For dynamic completion i.e. a usage.spec.kdl that uses complete, you'd need a shell while generating. The complete node in the spec uses run command that require unix shells. As a workaround, you can use git-bash which would work fine (CLI already uses it). So, you'd need to specify when using shell other than git-bash (or if not found) like MSYS2 environment.

  4. For loading completions, you can either provide the spec from a file or by stdin.

load(io.popen("abs/path/cuc.exe generate [OPTIONS] abs/path/usage.kdl"):read("*a"))()
load(io.popen("mycli usage | abs/path/cuc.exe generate [OPTIONS]"):read("*a"))()