tmuxinator: Unable to successfully run tmuxinator on macOS Sonoma 14.4.1

Describe the bug A couple of weeks ago I was able to run a number of projects with tmuxinator on my Mac Book Pro without problem, as I have been doing for a number of years now. Today, however, running tmuxinator as I’ve always done simply opens any configured panes and runs the first command associated with each pane and then stops.

To Reproduce I appear to be unable run any of my existing projects, or any new projects with tmuxinator. The problem is that all expected panes open open start (good), but all commands are simply echoed at the top of each pane, and then only the first command appears to be executed. All subsequent commands are ignored.

Expected behavior I expect each pane to open, and for the commands not to be echoed as a single block at the top of the pane, and for each command to be executed in sequence.

Environment

  • tmuxinator Version: tmuxinator 3.1.2
  • tmux Version: tmux 3.4
  • Ruby Version: ruby 2.5.5p157 (2019-03-15 revision 67260) [-darwin21]
  • OS: macOS Sonoma 14.4.1

Additional information Running this project will simply list the files in each ~/tmp/tmuxbuginator directory, but will not cat the contents of the two files:

name: tp-experiment
root: ~/tmp/tmuxbuginator

# Optional tmux socket
# socket_name: foo

# Note that the pre and post options have been deprecated and will be replaced by
# project hooks.

# Project hooks
# Runs on project start, always
# on_project_start: command
# Run on project start, the first time
# on_project_first_start: command
# Run on project start, after the first time
# on_project_restart: command
# Run on project exit ( detaching from tmux session )
# on_project_exit: command
# on_project_exit: tmux -CC attach
# Run on project stop
# on_project_stop: command

# Runs in each window and pane before window/pane specific commands. Useful for setting up interpreter versions.
# pre_window: rbenv shell 2.0.0-p247

# Pass command line options to tmux. Useful for specifying a different tmux.conf.
# tmux_options: -f ~/.tmux.mac.conf
# tmux_options: -f ~/.tmux.conf

# Change the command to call tmux.  This can be used by derivatives/wrappers like byobu.
# tmux_command: byobu

# Specifies (by name or index) which window will be selected on project startup. If not set, the first window is used.
# startup_window: editor

# Specifies (by index) which pane of the specified window will be selected on project startup. If not set, the first pane is used.
# startup_pane: 1

# Controls whether the tmux session should be attached to automatically. Defaults to true.
# attach: false


windows:
  - main:
      layout: even-vertical
      panes:
        - core:
          - ls -al
          - cat core.txt
        - other:
          - ls -al
          - cat other.txt

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 33 (17 by maintainers)

Most upvoted comments

@akofink Interesting reply, thanks.

I tried a bunch of things related to your comments above, and found the following:

Running the debug output with bash, from zsh

Without changing anything else, I tried running the debug output with bash. That is, starting bash (version 5.2, from brew) from a zsh shell, with my ~/.zshrc file in play.

Ran: bash s5b.sh.

Result: Opened two panes, printed all of the command in the respective panes. Ran all of the commands in the first pane. Only ran the first command in the second pane. (fail)

Running the debug output with bash, from zsh (without ~/.zshrc)

I tried running the debug output with bash. That is, starting bash (version 5.2, from brew) from a zsh shell, started without my ~/.zshrc file in play: exec zsh -i -f -d

Ran: bash s5b.sh.

Result: Opened two panes, printed all of the command in the respective panes. Ran all of the commands in the first pane. Only ran the first command in the second pane. (fail - same as above)

Running with bash set as the default shell in tmux, from zsh

Set the following configuration in ~/.tmux.conf:

set-option -g default-shell /opt/homebrew/bin/bash

Ran the following command from zsh, without ~/.zshrc in play.

Ran: tmuxinator experiment

Result: Displays two panels. Prints out the commands to be run at the top of each respective panel. Displays the command prompt (in the correct directory) in each panel. Does NOT run any of the commands.

However, activating each panel in turn, and typing the ENTER key in each panel causes all of the respective commands for that panel to run in that panel. ¯_(ツ)_/¯

Closing this issue

It appears that I’m the only person experiencing this issue. I have seen the commands run as they should once during all of these changes, giving me a kind of false hope, but it is non-deterministic - for me. I’m going to stop consuming everybody’s time on this issue (my issue) now, including my own, and close this issue now.

Thank you to all who responded. I really, really appreciate the extended effort that was made in looking for a solution.

Just tried the recent version of tmuxinator, via brew: it’s still broken for me in the same way; unfortunately unusable. 😞

The configuration is:

  • macOS: Sonoma 14.5
  • ruby: ruby 3.0.4p208 (2022-04-12 revision 3fa771dded) [arm64-darwin21]
  • tmux: 3.4
  • tmuxinator: 3.2.1

The behavior you were seeing seems fairly similar to https://github.com/tmuxinator/tmuxinator/issues/856

@akofink : Thanks for the new release 3.2.0. @augustelalande : Thanks for your continued assistance.

I’ve installed the new release via brew and rerun the same example configurations against the new version.

  • macOS: Sonoma 14.4.1
  • ruby: 3.0.4p208 (2022-04-12 revision 3fa771dded) [arm64-darwin21]
  • tmux: 3.4
  • tmuxinator: 3.2.0

The original list version still exhibits the bug, whereby it only executes the first command of the command list.

The modified array version (shown below) runs all of the commands, as expected.

2024-04-19-tmuxinator-bug

I’ve been suspicious of the yaml processing throughout this investigation. I will attempt the bisect over the weekend and see if I can narrow down the commit that introduced the change.

As a complete aside: I don’t recall the commands being echoed at the top of each pane in the past, but maybe I just wasn’t paying attention - and also that’s prolly related to tmux, and not to tmuxinator.

@akofink could you make a new release so we can see if the problem still exists with the few changes that were made?