RGBCube/nu_scripts
1
Fork 0
mirror of https://github.com/RGBCube/nu_scripts synced 2025-08-02 15:17:47 +00:00
Code Issues Activity

🐛 Fix rustup use completions and modify README (#696)

Browse source 
Hey, it's me, I finally fixed this `use` vs `source` script.nu 😄 

Also, I added a few lines of the `custom-completions/README.md` to
explain what happened in my case
This commit is contained in:
Auca Coyan 2023-12-13 19:43:19 -03:00 • committed by GitHub
parent 9700391563
commit af92dca520
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 16 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

14
custom-completions/README.md
View file

@ -4,6 +4,20 @@ This current directory provides custom completions. They can be used by importin
```nushell ```nushell
use path/to/<command>/<command>-completions.nu * 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. 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
```nu
# file: rustup.nu
export extern rustup [
...args
]
```
`use ./rustup.nu *` won't work here

0
custom-completions/rustup/rustup.nu → custom-completions/rustup/rustup-completions.nu
View file