When oh-my-zsh tmux plugin is enabled, the 'tmux' alias will cause my oh-my-tmux .tmux.conf.local to be ignored

[mayersj1]

Describe the bug

I'm using both .oh-my-zsh and .oh-my-tmux. Without the zsh tmux plugin enabled, all works fine for tmux to parse my .tmux.conf.local from oh-my-tmux. When I have the zsh tmux plugin enabled, the configuration from .tmux.conf.local is completely ignored UNLESS I have ZSH_TMUX_AUTOSTART=true in my .zshrc. Disabling the zsh tmux plugin make everything work as expected.

I did verify that with the tmux plugin enabled if I path to the tmux binary or use any of the aliases that are defined by the tmux EXCEPT for 'tmux', then all works as expected.

Steps to reproduce

1. Don't the 'tmux' plugin.
2. Install oh-my-tmux
3. cp the .tmux/.tmux.conf.local file to the home directory and enable the theme
4. Exit the shell
5. Start the shell (just to get everything loaded properly)
6. Type 'tmux' to start tmux, you should see the theme that is configured in .tmux.conf.local
7. Enable the oh-my-zsh 'tmux' plugin
8. source / restart your shell
9. Type 'tmux' and you'll see that instead of getting the theme as configured in the .tmux.conf.local, you are getting the default green status bar of tmux.
10. type 'ts' to start with a session and all seems okay.
11. type 'ta' to attach to the session and all seems okay. Just the 'tmux' command that appears to be broken.

NOTE: If I have ZSH_TMUX_AUTOSTART=true in my .zshrc, then the proper theme is loaded from the .tmux.conf.local file as well.

Expected behavior

use of oh-my-tmux should be unaffected by the zsh tmux plugin

Screenshots and recordings

No response

OS / Linux distribution

MacOS Sonoma

Zsh version

5.9

Oh My Zsh version

master (0008534)

Terminal emulator

kitty, iTerm2

If using WSL on Windows, which version of WSL

None

Additional context

No response

[carlosala]

I'm not sure I can follow what's going on here. ZSH_TMUX_AUTOSTART just executes the tmux alias at startup, which shouldn't be different than executing it manually right after.
Could you make sure that you have the exact configuration that https://github.com/gpakosz/.tmux proposes?

[carlosala]

Hi! Is it still reproducible?
friendly ping @mayersj1 :)

[mayersj1]

Yes, still reproducible. Thanks! Steve Mayer ***@***.***

…

On 9 Apr 2024, at 15:26, Carlo Sala wrote: Hi! Is it still reproducible? friendly ping @mayersj1 :) -- Reply to this email directly or view it on GitHub: #12247 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[carlosala]

I'm not sure I can follow what's going on here. ZSH_TMUX_AUTOSTART just executes the tmux alias at startup, which shouldn't be different than executing it manually right after.
Could you make sure that you have the exact configuration that https://github.com/gpakosz/.tmux proposes?

Could you check this?

[mayersj1]

So, the configuration is exactly as noted in the .tmux link provided above.

With ZSH_TMUX_AUTOSTART (which I have disabled as it was causing other, unrelated issues) all seemed to load fine. That doesn't negate the fact that now, if I have the tmux plugin enabled, launching 'tmux' causes the .tmux.conf.local to be completely ignored. If I use the 'tmux' command (which is an alias at this point: _zsh_tmux_plugin_run) it skips the .tmux.conf.local.

If I directly call the tmux executable or use a function that wraps tmux, all works properly (such as 'ts'):

 which ts
ts () {
        if [[ -z $1 ]] || [[ ${1:0:1} == '-' ]]
        then
                tmux new-session "$@"
        else
                tmux new-session -s "$@"
        fi
}

executing 'tmux' with any argument works properly of course. It's just the bare 'tmux' execution that seems to launch the tmux session without parsing the .tmux.conf.local file.