nushell
How about nushell-completions?
There are bash-completion and zsh-completions already. I think it is convenient to regard the present custom-complitions as an individual package to distribute or install.
I am not familiar with nupm but bash-completion and zsh-completions can be installed in many linux distributions with their each internal package manager.
Nupm is our unfinished package manager. https://github.com/nushell/nupm.
We also have to be cross-platform, where would these files go on Windows?
At least, nushell-completions should be an individual package to package, distibute, and install. How to package it does not matter here, and whether to install the package with nupm is up to users, but I wager that Unix users prefer to install the package with the operation system package manager instead. As for Windows users, they can use nupm anyway, if nupm supports it.
on linux, i would still use nupm to install this, which is what i'm doing in my current config, i guess we would just need to make the custom-completion/ directory a package instead of the whole nu_scripts repo :yum:
see the package.nuon file :wink:
right now you can nupm install --path /path/to/nu_scripts/ and have all the nu_scripts installed, but i can imagine doing nupm install --path /path/to/nu_scripts/custom-completions/ instead :smirk:
At least, nushell-completions should be an individual package to package, distibute, and install. How to package it does not matter here, and whether to install the package with nupm is up to users, but I wager that Unix users prefer to install the package with the operation system package manager instead. As for Windows users, they can use nupm anyway, if nupm supports it.
totally agree
