Each window in the top-level session runs tmux anew-session or attach-session. Window names correspond to session names.
My top-level session is the default session and uses ^T as the prefix. All others use ^A.
I also have a $CSCOPE_EDITOR that runs the real $EDITOR in new window (named after the basename of the file to be edited) in the same session and then exits, letting cscope get control back. I strongly recommend this.
I also have a pid2mux script that takes a pid and tells me which window of which session has that process (if it has a controlling tty).
I live as much as possible in a tmux world. Though I still use screen keybindings as much as possible also.
Each window in the top-level session runs tmux anew-session or attach-session. Window names correspond to session names.
My top-level session is the default session and uses ^T as the prefix. All others use ^A.
I also have a $CSCOPE_EDITOR that runs the real $EDITOR in new window (named after the basename of the file to be edited) in the same session and then exits, letting cscope get control back. I strongly recommend this.
I also have a pid2mux script that takes a pid and tells me which window of which session has that process (if it has a controlling tty).
I live as much as possible in a tmux world. Though I still use screen keybindings as much as possible also.