lux-cli-search(1)

πŸ“¦ version 0.48.0, in nixpkgs unstable

✨ NAME ✨

okay so bestie, this is lux-cli-search β€” from the General Commands Manual, with the page title lux-cli-search(1) folded in right here at the top. πŸ’–

lux-cli-search β€” Query the luarocks servers. That’s the whole vibe. periodt. πŸ’…


πŸ› οΈ SYNOPSIS πŸ› οΈ

lux-cli search [--output-format] [--server] [--extra-servers]
[--namespace] [--lua-dir] [--lua-version] [--tree] [--cache-dir]
[--data-dir] [--variables] [--profile] [--verbose] [--no-progress]
[--no-prompt] [--preset] [--nvim] [--no-tfa] [--timeout] [--max-jobs]
[--no-luarc] [--no-wrap-bin] [--user-agent] [-h|--help]
<LUA_PACKAGE_REQ>

πŸ’¬ DESCRIPTION πŸ’¬

Query the luarocks servers. That’s literally the description, and honestly? iconic minimalism. ✨


πŸŽ€ OPTIONS πŸŽ€

  • --output-format <OUTPUT_FORMAT> β€” the output format, with [default: text]. possible values are:
    • json
    • text
  • --server <server> β€” Fetch rocks/rockspecs from this server (takes priority over config file). πŸ‘‘
  • --extra-servers <extra-server> β€” Fetch rocks/rockspecs from these servers in addition to the main server (overrides any entries in the config file). πŸ¦‹
  • --namespace <namespace> β€” Specify the luarocks server namespace to use. πŸŽ€
  • --lua-dir <prefix> β€” Specify the directory in which to install Lua if not found. 🧚
  • --lua-version <ver> β€” Which Lua installation to use. Valid versions are: '5.1', '5.2', '5.3', '5.4', '5.5', 'jit' and 'jit52'. If not set, Lux will attempt to detect the Lua version:
    • From the current project, if it has an exact Lua version requirement.
    • From the Lua installation that is available on the PATH.
  • --tree <tree> β€” Which tree to operate on. In a workspace, this can be used to specify a detached workspace tree. 🌈
  • --cache-dir <cache-dir> β€” Specifies the cache directory, e.g. for luarocks manifests. πŸ“
  • --data-dir <data-dir> β€” Specifies the data directory, in which the default user install tree resides (e.g. ~/.local/share/lux). πŸ’œ
  • --variables <variable> β€” Override config variables. Example: lx -v "LUA=/path/to/lua" ... ✨
  • --profile <profile> β€” The build profile to use when compiling packages. Default: release. possible values are:
    • release
    • dev
  • --verbose β€” Display verbose output of commands executed, enabling DEBUG logs. To enable TRACE logs, set RUST_LOG=trace. πŸ”₯
  • --no-progress β€” Don’t print any progress bars or spinners. no cap, sometimes you just want silence. πŸ’€
  • --no-prompt <NO_PROMPT> β€” Skip prompts, selecting the default option. Prompting is enabled by default in terminal/TTY environments. possible values are:
    • true
    • false
  • --preset <preset> β€” Configure Lux for a specific environment. Valid presets are: 'nvim'. possible values are:
    • nvim: Configure Lux for Neovim plugins. πŸ’–
  • --nvim β€” [DEPRECATED] Configure lux for installing Neovim packages. Use --preset nvim instead. bestie, this one’s giving legacy energy β€” use the preset. πŸ™ˆ
  • --no-tfa β€” Disable prompts for two-factor authentication (2FA) codes. It is strongly recommended to enable 2FA instead see (https://luarocks.org/settings/two-factor-auth). 🫢
  • --timeout <seconds> β€” Timeout on network operations, in seconds. 0 means no timeout (wait forever). Default is 30. ⏳
  • --max-jobs <MAX_JOBS> β€” Maximum buffer size for parallel jobs, such as downloading rockspecs and installing rocks. 0 means no limit. Default is 0. πŸš€
  • --no-luarc β€” Do not generate or update a .luarc.json file when building a project. πŸŽ€
  • --no-wrap-bin β€” Do not wrap Lua bin scripts. πŸ¦‹
  • --user-agent <USER_AGENT> β€” The user agent to set when making web requests. Default is "lux/<version>". 🌸
  • -h, --help β€” Print help (see a summary with -h). πŸ’…
  • <LUA_PACKAGE_REQ> β€” the required positional argument placeholder; the original doesn’t add a separate description here. ✨

okay that’s the whole page, bestie. cute little sign-off: this is lux-cli-search(1) from the General Commands Manual, footer reading search and lux-cli-search(1) β€” and there’s no separate date/version string in the supplied footer, so I’m not inventing one. πŸ«ΆπŸ’–πŸŽ€

πŸ“¦ where this page comes from