-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
bug: tmux with 'sensibleOnTop' option no longer uses the correct shell #5952
Comments
I'm also experiencing the same issue. The notes for tmux 3.5a here tmux/tmux#4162 say the following: "Note that a fix in 3.5 and 3.5a to correctly set SHELL for run-shell and if-shell reveals a bug in the tmux-sensible script, causing it to set default-shell to /bin/sh. This can be worked around by adding this to .tmux.conf after the tmux-sensible script is invoked:" - system: `"aarch64-darwin"`
- host os: `Darwin 24.0.0, macOS 15.0.1`
- multi-user?: `yes`
- sandbox: `no`
- version: `nix-env (Nix) 2.18.8`
- channels(root): `"nixpkgs"`
- nixpkgs: `/nix/store/60sn02zhawl3kwn0r515zff3h6hg6ydz-source` EDIT: Using the following in
|
Same here. Having EDIT: using |
enable again when nix-community/home-manager#5952 is fixed
tmux sensible uses this if it's found and this causes problems with default-command being set to sh instead of zsh see: tmux/tmux#4162 and nix-community/home-manager#5952 which provided the correct workaround of setting default-command to $SHELL
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/tmux-use-bash-instead-defined-zsh-in-home-manager/54763/2 |
tmux now calls run-shell with /bin/sh, which causes tmux-sensible use it instead of my shell here: https://github.com/tmux-plugins/tmux-sensible/blob/master/sensible.tmux#L103 Hardcode `/bin/zsh` instead of `$SHELL` there, since I know what I want to use. Issues: home-manager: nix-community/home-manager#5952 tmux: tmux/tmux#4162
Quick and (very) dirty workaround for this:
It hardcodes |
This solved the root problem, but after running tmux I got another issue: After pressing the 'Enter' key:
And I don't know how to fix it |
|
I encountered the same issue, and at that time, I noticed that home-manager's tmux automatically loads the sensible plugin. |
It's supposed to be a sensible default, hence the name ;) |
This is simply the origin of the plugin’s name. Regardless of the name, it’s still just a plugin. Who would expect that setting tmux.enable = true would also load an additional tmux plugin? |
And unfortunately, it seems that tmux-sensible is no longer being maintained... |
…ll in new sessions Issue: nix-community/home-manager#5952
I don't disagree, was mostly joking. Yeah, considering the last commit was over 2 years ago - could be worth considering changing the default. |
Are there any problems in creating the PR on this? I think a bit more discussion is needed, but it is inconvenient to discuss in this thread. |
Good to note that the default-command |
There's a bug between current tmux 3.5a and tmux-sensible@25cb91f that makes it always use sh instead of correct $SHELL https://discourse.nixos.org/t/tmux-use-bash-instead-defined-zsh-in-home-manager/54763/2 nix-community/home-manager#5952 will need fix here: - tmux-plugins/tmux-sensible#75 but I may not actually need sensible at all with home-manager tmux config
Are you following the right branch?
Is there an existing issue for this?
Issue description
The upstream version of
tmux
was updated last week to 3.5a (commit). One of the changes in this version (from 3.5) is that/bin/sh
is used for run-shell.With this version of tmux, all panes/windows/etc use
sh
instead of the configured default shell (in my case,zsh
).My rough guess is that this change in tmux has introduced some ordering issues when
sensibleOnTop
is set, asrun-shell
will now usesh
regardless of how tmux's default-shell is set.The problem goes away if I do:
or if I set
sensibleOnTop = false;
Maintainer CC
@jorsn @rycee (cc based on a7cdfaa).
System information
The text was updated successfully, but these errors were encountered: