4 ms·

Author of tmuxp [1], a session manager also in Python. I like the project. I consider it more in the "different" category as opposed to "better". > Other tmux

Author of tmuxp [1], a session manager also in Python. I like the project. I consider it more in the "different" category as opposed to "better". > Other tmux session managers require pages of documentation for basic use, http://tmuxp.readthedocs.org/en/latest/quickstart.html http://tmuxp.readthedocs.org/en/latest/quickstart.html > and define windows using a complicated nesting of pane splits. http://tmuxp.readthedocs.org/en/latest/examples.html http://tmuxp.readthedocs.org/en/latest/examples.html The syntax for tmuxp was heavily inspired by tmuxinator and teamocil. Normally, window layouts in tmux don't get too fancy. > tmuxomatic is so easy that anyone could use it after just one example. I think the idea has potential - already being used to using teamocil/tmuxinator configs, it feel its a tad unorthodox at first. I don't see what benefit it gives over constructing the tmux via your client and saving the layout. The `tmuxp freeze` command exists for this. > Yet tmuxomatic is more flexible and more powerful than other tmux session managers. http://tmuxp.readthedocs.org/en/latest/quickstart_python.html http://tmuxp.readthedocs.org/en/latest/quickstart_python.htm... + http://tmuxp.readthedocs.org/en/latest/api.html http://tmuxp.readthedocs.org/en/latest/api.html You can't get more powerful and flexible than having an API that basically runs at a parity to tmux's data model and commands. That said, anything that spreads the word about tmux and makes it easier for people to use is a good thing. I think the real pain point in CLI is even with modern (neo)vim/emacs, we don't have anything close to an Atom or Intellij suite for "just works" completion. If you've had better luck with completion - I'm happy for you. [1] https://github.com/tony/tmuxp https://github.com/tony/tmuxp

oxidane 11y ago
Hi, author of tmuxomatic here. My personal use of tmux includes windows with 10+ panes. It's not easy to define these layouts using other means, and often making simple modifications is a big hassle. I didn't want to be an expert in tmux to maximize my use of it. I wanted something so simple and intuitive that documentation is virtually unnecessary. For those who only ever use simple 1 or 2 split layouts, a traditional manager may suffice. But even in these cases, tmuxomatic is much easier to deal with. Definitions in tmuxomatic are readable at-a-glance, and the flexibility afforded by windowgrams make layouts clear and unambiguous. As for the tedium of ASCII, there's the Flex command set that's being added to tmuxomatic 2.x. Using a handful of basic commands, virtually any layout is possible without doing any ASCII art at all. I'd say this qualifies as better. Of course it's different, it has to be.

oxidane 11y ago

Hi, author of tmuxomatic here. My personal use of tmux includes windows with 10+ panes. It's not easy to define these layouts using other means, and often making simple modifications is a big hassle. I didn't want to be an expert in tmux to maximize my use of it. I wanted something so simple and intuitive that documentation is virtually unnecessary. For those who only ever use simple 1 or 2 split layouts, a traditional manager may suffice. But even in these cases, tmuxomatic is much easier to deal with. Definitions in tmuxomatic are readable at-a-glance, and the flexibility afforded by windowgrams make layouts clear and unambiguous. As for the tedium of ASCII, there's the Flex command set that's being added to tmuxomatic 2.x. Using a handful of basic commands, virtually any layout is possible without doing any ASCII art at all. I'd say this qualifies as better. Of course it's different, it has to be.