lux-cli-debug-toolchains(1)

πŸ“¦ version 0.48.0, in nixpkgs unstable

okay so welcome to lux-cli-debug-toolchains(1), bestie β€” straight out of the General Commands Manual ✨ this page is the toolchains check and it’s gonna show you how to see what toolchains are available πŸ’…

πŸŽ€ NAME πŸŽ€

lux-cli-debug-toolchains β€” Check for available toolchains. That’s the whole main-character job fr fr.

✨ SYNOPSIS ✨

Run it like this, exactly:

lux-cli debug toolchains [--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]

πŸ¦‹ DESCRIPTION πŸ¦‹

Check for available toolchains. Yup β€” this command is literally a vibe check for toolchains, no cap. πŸ‘‘

πŸ’– OPTIONS πŸ’–

okay here’s every flag, one by one, no skipping 🫢

  • --output-format <OUTPUT_FORMAT> [default: text] β€” the output format you want, bestie. Possible values:
    • json
    • text
  • --server <server> β€” Fetch rocks/rockspecs from this server (takes priority over config file). priority queen behavior πŸ‘‘
  • --extra-servers <extra-server> β€” Fetch rocks/rockspecs from these servers in addition to the main server{n} (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.{n} Valid versions are: '5.1', '5.2', '5.3', '5.4', '5.5', 'jit' and 'jit52'.{n} If not set, Lux will attempt to detect the Lua version:{n}
    • From the current project, if it has an exact Lua version requirement.{n}
    • From the Lua installation that is available on the PATH.
  • --tree <tree> β€” Which tree to operate on.{n} 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,{n} in which the default user install tree resides{n} (e.g. ~/.local/share/lux).
  • --variables <variable> β€” Override config variables.{n} Example: lx -v "LUA=/path/to/lua" ...
  • --profile <profile> β€” The build profile to use when compiling packages.{n} Default: release. Possible values:
    • release
    • dev
  • --verbose β€” Display verbose output of commands executed, enabling DEBUG logs.{n} To enable TRACE logs, set RUST_LOG=trace.
  • --no-progress β€” Don’t print any progress bars or spinners. clean output era ✨
  • --no-prompt <NO_PROMPT> β€” Skip prompts, selecting the default option.{n} Prompting is enabled by default in terminal/TTY environments. Possible values:
    • true
    • false
  • --preset <preset> β€” Configure Lux for a specific environment.{n} Valid presets are: 'nvim'. Possible values:
    • nvim: Configure Lux for Neovim plugins
  • --nvim [DEPRECATED] β€” Configure lux for installing Neovim packages.{n} Use --preset nvim instead. deprecated bestie, we’re moving on πŸ’…
  • --no-tfa β€” Disable prompts for two-factor authentication (2FA) codes.{n} It is strongly recommended to enable 2FA instead see (https://luarocks.org/settings/two-factor-auth).
  • --timeout <seconds> β€” Timeout on network operations, in seconds.{n} 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{n} 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').

okay that’s the whole page, bestie πŸ’– source/version footer vibes: toolchains and lux-cli-debug-toolchains(1) β€” and there’s no date line in the footer, so we’re not making one up, periodt 🫢✨

πŸ“¦ where this page comes from