mirror of
https://github.com/nushell/nu_scripts.git
synced 2024-08-16 17:00:32 +03:00
e4dbec663b
TL;DR: The "simple" example from https://www.gnu.org/software/make/manual/html_node/Simple-Makefile.html is currently not compatible with the custom completion script found in `custom-completions/make/make-completions.nu`. This PR tries to fix that. As I was working on `nur` (https://github.com/ddanier/nur) and the `nurify` script to convert to `nur` from different task runners (https://github.com/ddanier/nur/blob/main/scripts/nurify.nu) I wanted to create a good way to convert from using `make`. So I thought the `make` completion would for sure implement a good way to get a list of all possible `make` targets. Hence I started looking at `custom-completions/make/make-completions.nu`. Then I searched for a good documentation for how `Makefile`s work, as the last time I was using this myself is about 5 to 10 years ago. If you for example look at the documentation on gnu.org you may find examples of `Makefile`s not working with the current autocompletion. See https://www.gnu.org/software/make/manual/html_node/Simple-Makefile.html for example, the "simple" example they provide. The reason for this not working is that the targets use some whitespace after the target name. This is somehow allowed and thus valid. See https://www.gnu.org/software/make/manual/html_node/Rule-Introduction.html for a quick overview about how the `Makefile`s syntax works. I quickly checked this to ensure `make` actually parses this correctly, it really does. This means that the current `make` completion does miss support for the "simple" example provided my `make` itself. So I went on to fix this. My suggested solution is: * Filter all lines by regex `'^[\w\.-]+\s*:'` to ensure possible targets - start with some word (also allowing `.` and `-`) - may have some whitespaces after the word - has ":" after this * Split by the ":" * Use first column * Trim the remaining target name to remove those nasty whitespaces * Use result for completion For me this did fix the issue with the "simple" `Makefile`, allowing me to put this into my `nurify` script. Would be nice to get this "backported" to nu scripts as well. Might help others 😉 |
||
|---|---|---|
| .. | ||
| ack | ||
| adb | ||
| ani-cli | ||
| as | ||
| auto-generate | ||
| bat | ||
| bend | ||
| bitwarden-cli | ||
| btm | ||
| cargo | ||
| cargo-make | ||
| composer | ||
| curl | ||
| fastboot | ||
| flutter | ||
| fsharpc | ||
| fsharpi | ||
| gh | ||
| git | ||
| glow | ||
| godoc | ||
| gradlew | ||
| just | ||
| less | ||
| make | ||
| man | ||
| mask | ||
| mix | ||
| mvn | ||
| mysql | ||
| nano | ||
| nix | ||
| npm | ||
| op | ||
| pass | ||
| pdm | ||
| pixi | ||
| pnpm | ||
| poetry | ||
| reflector | ||
| rg | ||
| rustup | ||
| rye | ||
| scoop | ||
| tar | ||
| tcpdump | ||
| tealdeer | ||
| toipe | ||
| typst | ||
| virsh | ||
| vscode | ||
| winget | ||
| xgettext | ||
| yarn | ||
| zef | ||
| 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