mirror of
https://github.com/nushell/nu_scripts.git
synced 2024-09-11 13:45:56 +03:00
Hi! I found another bug, if you write ```bash $ gh repo create ``` it leads you to a series of prompts, but the current nu script throws an error. I fixed that and `gh repo fork` too, in which you don't necessarily need an argument. |
||
---|---|---|
.. | ||
ani-cli | ||
auto-generate | ||
bitwarden-cli | ||
btm | ||
cargo | ||
gh | ||
git | ||
glow | ||
just | ||
make | ||
man | ||
mask | ||
nano | ||
nix | ||
npm | ||
pass | ||
pdm | ||
pixi | ||
pnpm | ||
poetry | ||
reflector | ||
rustup | ||
scoop | ||
tealdeer | ||
toipe | ||
typst | ||
vscode | ||
winget | ||
yarn | ||
zellij | ||
README.md |
Custom completions
This current directory provides custom completions. They can be used by importing their exported commands via:
use path/to/<command>/<command>-completions.nu *
# or
source path/to/<command>/<command>-completions.nu
# without the `*` at the end
With path/to/<command>
being either the relative path of the file to your current working directory or its absolute path.
Bear in mind that if you import the use <path> *
, it is important that you don't name a function with the same name of the file
# file: rustup.nu
export extern rustup [
...args
]
use ./rustup.nu *
won't work here