-
Notifications
You must be signed in to change notification settings - Fork 519
Add separate page for setting Nu as default shell #754
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Adds instructions to add Nu to your terminal - Advises against setting Nu as login shell Heavily inspired by https://elv.sh/get/#using-elvish-as-your-default-shell
I like the changes except that the part that says "We do not recommend setting your login shell to Nu.". I use it as my login shell in WSL2 every weekday without issue. I can understand that we may need to say something but I don't want to deter people from using nushell, just the opposite. I think it's ok to have a warning but I think we should use different words. Perhaps like "Warning, Nu is still in development and is not intended to be POSIX compliant. If you need strict POSIX compliance at login time, you should consider using a alternate login shell." Maybe not those exact words, but something less like "Don't use nushell" 😆 |
I understand what you are saying, and I also want people to use nushell.
Unfortunately, that's not something you can choose. Some friends noticed that also with some vscode extensions, so that problem probably also occurs on WSL and macOS. If you still want me to weaken the message or add alternative "default methods" (see https://wiki.archlinux.org/title/Fish), I am happy to. |
Yes, it needs to be similar to what I suggested please. I don't want to discourage use. |
Updated it to:
How do you like that one? |
Much better. Thank you. |
One last thing, Do you think the |
Thanks for improving the docs! |
These are the changes after running nu_deps
Heavily inspired by
https://elv.sh/get/#using-elvish-as-your-default-shell