-
-
Notifications
You must be signed in to change notification settings - Fork 465
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
Can't change user shell #1209
Comments
What terminal are you using? Have you added yourself to |
Tried both alacritty and apple's terminal program. I am not currently using |
Yes, you want to add your own user to |
Gotcha thanks, can I ask why it says not to add admin users to knownUsers in the docs? I assumed I shouldn't add my account because it's the only account on the computer and is an admin. Running the path for zsh will run it fine |
Ah, I forgot to update that, basically it’s because adding a user to Have you tried restarting your computer? |
I added myself to |
Are you setting the |
Nope |
Have you tried quitting Terminal.app and opening it fresh? |
Yeah I killed the tmux session too, no change |
In the menus there should be a New Command option and if you use that and put |
What happens if you change that back to |
Thanks for the help, the issue has to do with something in my tmux config - just rebuilt without tmux and it's fine. Didn't notice that earlier because every shell auto attaches to tmux |
Looks like tmux just doesn't use my shell when I start it up |
I have no |
|
According to this commit, Maybe you can just override it with |
Looks like there's a pull request to fix this: tmux-plugins/tmux-sensible#75 |
It looks like So you can make sure the package is not installed and you don't need to set anything else |
Thanks for the help! |
Both dscl and $SHELL show the correct shell but any time I open a new shell it uses apple bash. Any idea why this could be happening? I'm using
programs.zsh
and haveusers.users.ted.shell = pkgs.zsh
.chsh
also doesn't do anything because it's already set to the correct shell but running the wrong oneThe text was updated successfully, but these errors were encountered: