4 ms·
I'll be honest. I use tmux everyday as an integral part of my workflow, but I find this whole idea of Windows and panes extremely cumbersome and complex. I just
by whack 9y ago
I'll be honest. I use tmux everyday as an integral part of my workflow, but I find this whole idea of Windows and panes extremely cumbersome and complex. I just stick to a one-server-one-window/pane model, and create a new server for every new "window" that I want. I then connect to these multiple servers using multiple tabs on my terminal app, which I can then freely drag-drop-resize to my heart's content. If someone's looking for an entry-drug into screen/tmux, this is the easiest way to get started.
- jamesbvaughan 9y agoThis is exactly what I did for a long time, but after seeing so many friends and coworkers using panes effectively, I decided to finally jump in and commit some time to learning and customizing all the keybindings, and it has definitely paid off. Using panes and windows has become an integral part of my workflow. I would encourage you to give them a serious shot. You might be surprised!
- 43224gg252 9y agoYou can even enable the mouse to resize splits and switch between tabs in tmux/byobu: https://gfycat.com/SmallComplexGreatargus https://gfycat.com/SmallComplexGreatargus
- pthreads 9y agoNow, that is quite useful! I am going to try tmux just for that. Have been a screen user so far.
- mdaniel 9y agoIf you haven't already found a system you like, you may enjoy Teamocil https://github.com/remiprev/teamocil#examples https://github.com/remiprev/teamocil#examples I use it for tailing the logs of multiple servers in the same window, which is especially nice because ctrl-b,space will rotate the layouts if I need to see more horizontal or vertical for a second, and ctrl-b,z will full-window a pane enabling complete drill-down on one server A related project is tmuxinator https://github.com/tmuxinator/tmuxinator#tmuxinator https://github.com/tmuxinator/tmuxinator#tmuxinator but it didn't work exactly right for my use-case (I don't recall the specifics without being in front of my work machine)
- pavel_lishin 9y agoHere's my current workflow: http://i.imgur.com/qeUfXuI.png http://i.imgur.com/qeUfXuI.png Top pane is for git stuff. Bottom left is where webpack/npm/react stuff runs - if I save and see errors, I know something is wrong. Bottom right is an ssh tunnel to a server the local dev environment depends on. (Or I can run that dependency locally, too, but meh.) For me, it's pretty intuitive - splitting, switching panes, etc. I know it's effectively the same, but I can't imagine going to back to one-tab-per-process. If nothing else, the ability to see multiple logs scrolling by in a single window is A+.
- cryptonector 9y agoMe too. Also, I nest sessions. 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.