incompatible with nushell
eikaramba opened this issue · comments
Describe the bug
with nushell, nu is already starting the nushell. i am not sure how this can be fixed. i tried the same powershell command just replaced it with nu, but this did not help.
Reproduction
install https://www.nushell.sh and type nu
System Info
windows x64Used Package Manager
npm
Validations
- Follow our Code of Conduct
- Read the Contributing Guide.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
- The provided reproduction is a minimal reproducible of the bug.
maybe rename nu to nux, cuz nu is rarely used.
maybe rename
nutonux, cuznuis rarely used.
Wouldn't nup be more obvious?
Even better would be to just not hyper-abbreviate commands and leave that to user aliases instead so as to avoid current and future name conflicts. Subcommands would be a good idea since we could then provide just one bin (less surface area means less chance for conflict). Hell, with subcommands we can keep the hyper-abbreviated commands e.g. n i, n u, n un etc. and users could alias these to ni, nu, nun and such.
Maybe an option to "blacklist" certain aliases in the config which could then get forwarded to the next best thing in PATH?
U can alias the command of this tool in the terminal profile or config file.