> Sounds like you reinvented it

Tmux comes with the ability to script it, intentionally and by design, and it’s very straightforward and simple to open several windows that launch commands in them. Tmuxinator doesn’t reinvent that, and it does add another dependency, and another layer of options and flags and project syntax to learn.

The suggestion to check it out is great, but saying that people who don’t use it are reinventing it is a tad heavy handed. There are good reasons and legitimate scenarios to keep it simple with tmux scripting alone.

Absolutely. I think it depends on ruby, too, which is unusual. It’s anyway got some good ideas - declarative config files, etc.

Not the OP, but I did riff off of tmuxinator recently. tmuxed talks to tmux directly out-of-band to avoid running over user input and supports things like "wait before sending more input" for cases where `sleep` isn't desirable. I envisioned it being an orchestrator layer over tmux rather than a "new thing" to learn; while it's largely finished for my normal use cases I've been thinking about how sometimes it'd be awfully useful to be able to orchestrate tmux commands and not just send-keys.

Single binary, too, so no Ruby dependency. I really should get it into Homebrew one of these days...

https://github.com/eropple/tmuxed

I have not! I'll have to investigate more, because my little shell script is pretty basic (like 20 lines total, most of which was done for readability).

https://github.com/tmuxinator/tmuxinator