incompatible with nushell

antfu-collective / ni

💡 Use the right package manager

MIT License

6.16k stars 206 forks source link

incompatible with nushell #153

Open eikaramba opened 1 year ago

eikaramba commented 1 year ago

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 x64

Used Package Manager

npm

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

uxiew commented 1 year ago

maybe rename nu to nux, cuz nu is rarely used.

Lord-Valen commented 1 year ago

maybe rename nu to nux, cuz nu is 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.

vaaski commented 1 year ago

Maybe an option to "blacklist" certain aliases in the config which could then get forwarded to the next best thing in PATH?

HawtinZeng commented 7 months ago

U can alias the command of this tool in the terminal profile or config file.