Hot answers tagged

2

Ignoring the default config file can be achieved by using the -f flag to specify the config file, and /dev/null: tmux -f /dev/null


2

You should be able to do: tmux send-keys 'exec myscript' 'C-m' With that, the shell will exec the script (i.e, myscript will replace the shell process instead of getting started as a child). Then, when that process terminates, it'll be the process that tmux ran, so tmux will clean up after it.


1

It was not tmux! I had accidentally pressed ⌘-D and split the macOS Terminal window.


1

Unfortunately there is currently no way to have an empty pane closed when the process piping to it closes its stdout. You need to kill the pane yourself with kill-pane.


1

Assuming your terminal outputs Up as ^[[A: up-line-or-history() { zle .set-local-history -n ${#WIDGET:#*global*} # 0 iff $WIDGET == *global* zle .up-line-or-history } zle -N up-line-or-history-local up-line-or-history zle -N up-line-or-history-global up-line-or-history # Up arrow bindkey '^[[A' up-line-or-history-local # Alt + up arrow bindkey '^[^[[A'...


1

An alternative is to have a reasonably big history and install the tmux logging plugin I like to have logging in all tmux windows turned on by default. I log to a 'tmux_log' directory and have a cron job to delete very old logs.


Only top voted, non community-wiki answers of a minimum length are eligible