Despite using tmux for years, even having written scripts for nested sessions that I use each day, I hadn't noticed the CLI was missing long options. Kind of crazy.
An area I don't know about is -C (control mode). libtmux could technically use it to get live updates rather than inefficiently and possibly needlessly querying session/window/pane info to keep objects up to date. Apparently iterm2's tmux integration uses it.
I use Tmux for starting 4 Bhyve VM's on FreeBSD via rc.local.
It really like it better than screen or daemon processes.
Nice for large compiling jobs on remote machines too.
Nice, I had no idea you could script tmux like that! Reminds me of "expect", which I've used to automate interactive SSH sessions with network devices.
I started using tmux in 2009. There was no -p option when capturep command was first added. Old scripts that keep working tend not to get updated. I have updated it now. Thank you.
Just this night I was thinking if whether tmux scripting could be abused to get it to work like zmodem. Sending files from the system with the tmux session to whatever machine one had sshd into (and ideally the other direction as well).
Tmux has pipe-pane, and it has -I and -O to go both directions.
It does require some gyrations to get around the fact that it logs everything (the command itself, terminal control, etc), and not just what's output by the command. Here's a quick and dirty example:
a) Start a tmux session to a remote host
b) On the local host, run this (assuming session 0):
19 comments
[ 5.9 ms ] story [ 51.7 ms ] threadIn the backend, it's all tmux CLI commands.
tmuxp (https://tmuxp.git-pull.com), similar to tmuxinator, uses libtmux under the hood to build workspaces from a yaml/json file: https://github.com/tmux-python/tmuxp/blob/master/tmuxp/works...
Despite that, I've found some people prefer just using plain tmux scripting (https://twitter.com/bitprophet/status/561356905843392514). Aside: That's Jeff Forcier, creator of fabric (http://www.fabfile.org/)
Through tmux's formats (http://man7.org/linux/man-pages/man1/tmux.1.html#FORMATS), you can about any info you'd like on your workspace.
An area I don't know about is -C (control mode). libtmux could technically use it to get live updates rather than inefficiently and possibly needlessly querying session/window/pane info to keep objects up to date. Apparently iterm2's tmux integration uses it.
which-key on vim has been great in making sure, I use new features, I add to my config file.
Not utterly comfortable, but helps most of the time.
I started using tmux in 2009. There was no -p option when capturep command was first added. Old scripts that keep working tend not to get updated. I have updated it now. Thank you.
[Quine]: https://en.wikipedia.org/wiki/Quine_%28computing%29
Anyone know of this or a better approach?
It does require some gyrations to get around the fact that it logs everything (the command itself, terminal control, etc), and not just what's output by the command. Here's a quick and dirty example:
a) Start a tmux session to a remote host
b) On the local host, run this (assuming session 0):
$ tmux pipe-pane -o -t0 "tail -n +2 | col -b | base64 -d > ~/output"
$ tmux send-keys -t0 "base64 /some/file && read" Enter
$ tmux pipe-pane -t0
$ tmux send-keys -t0 Enter
You should now have ~/output on the local host, which is identical to /some/file on the remote.