Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Workflow in tmux

coderwall.com

Post reply on HN
Print view View original

21–30 of 62 posts

Re: Workflow in tmux

#21

Post by joelhooks »

Osiris wrote: post #19

I understand using console window managers when logged into a headless system where you don't otherwise have access to a UI, but I'm baffled by the desire to use console-based window managers within well defined GUI like OS X. In OS X, there are multitudes of tools to allow you to manage windows. Spectacle is a simple one, Slate is extremely customizable. Why not use the built-in OS X window manager to manager variou…

it is lightweight, contained, and excellent if you have a "unix-like" workflow. Typically I'll have a watch script, server, and vim in a given window, and it is super compact. Some cons are probably the learning curve required to see any advantage, and the fundamental lack of any respect for mousing, which can be in the pro column for many.

Re: Workflow in tmux

#22

Post by rogerbinns »

The single most irritating thing about tmux is that viewers have to look at the same window or whatever it is called. My typical usage pattern is to connect twice, have one window where there is a long running task I want to monitor and a second where I am typing commands. But I can't show one in one connection and the other in the other connection.

Note that I use byobu to front end things, and when using screen this can easily be done. I have seen workarounds that involve using multiple copies of tmux talking to each other in various heroic configurations but that is silly.

Re: Workflow in tmux

#23

Post by Osiris »

joelhooks wrote: post #21
Osiris wrote: post #19

I understand using console window managers when logged into a headless system where you don't otherwise have access to a UI, but I'm baffled by the desire to use console-based window managers within well defined GUI like OS X. In OS X, there are multitudes of tools to allow you to manage windows. Spectacle is a simple one, Slate is extremely customizable. Why not use the built-in OS X window manager to manager variou…

it is lightweight, contained, and excellent if you have a "unix-like" workflow. Typically I'll have a watch script, server, and vim in a given window, and it is super compact. Some cons are probably the learning curve required to see any advantage, and the fundamental lack of any respect for mousing, which can be in the pro column for many.

That's interesting. I practically never use the mouse to switch between windows in OS X or Windows.

The biggest problem I have with tmux is vertical splits don't work with native copy-paste because the selection goes across both panes. Using multiple terminal windows, on the other hand, doesn't have that issue.

Re: Workflow in tmux

#24

Post by th »

eridius wrote: post #16
th wrote: post #12

Earlier quoted context omitted.

The status bar with the arrow breadcrumbs is powerline: https://github.com/Lokaltog/powerline There are bindings for tmux, bash, zsh, vim, and ipython (among others).

The status bar with the arrow breadcrumbs _looks like_ powerline. If you read his tmux config, he's not actually using powerline, he just duplicated the appearance.

He is using the vim-powerline bundle for vim, but it looks like you're right about the tmux config.

Re: Workflow in tmux

#25

Post by piinbinary »

rogerbinns wrote: post #22

The single most irritating thing about tmux is that viewers have to look at the same window or whatever it is called. My typical usage pattern is to connect twice, have one window where there is a long running task I want to monitor and a second where I am typing commands. But I can't show one in one connection and the other in the other connection. Note that I use byobu to front end things, and when using screen thi…

I always have two copies of tmux running, for this very reason. Someone out there surely must have a better solution.

Re: Workflow in tmux

#26

Post by asveikau »

Osiris wrote: post #19

I understand using console window managers when logged into a headless system where you don't otherwise have access to a UI, but I'm baffled by the desire to use console-based window managers within well defined GUI like OS X. In OS X, there are multitudes of tools to allow you to manage windows. Spectacle is a simple one, Slate is extremely customizable. Why not use the built-in OS X window manager to manager variou…

One use case I used to do often is switching between headless/remote and local use. Imagine sitting at your desktop, starting something, then detaching, going somewhere else... Then you ssh back to the desktop and resume the same session. Your stuff has been running there the whole time.

Re: Workflow in tmux

#27

Post by d0m »

I started using tmux.. then switched to stumpwm which is too awesome to explain here. Embrace the full power of emacs and your Window Manager.

Re: Workflow in tmux

#28

Post by eridius »

d0m wrote: post #27

I started using tmux.. then switched to stumpwm which is too awesome to explain here. Embrace the full power of emacs and your Window Manager.

stumpwm is a window manager. tmux is a terminal multiplexer. They are not the same thing and using one does not preclude using the other.

Re: Workflow in tmux

#29

Post by pyre »

piinbinary wrote: post #25
rogerbinns wrote: post #22

The single most irritating thing about tmux is that viewers have to look at the same window or whatever it is called. My typical usage pattern is to connect twice, have one window where there is a long running task I want to monitor and a second where I am typing commands. But I can't show one in one connection and the other in the other connection. Note that I use byobu to front end things, and when using screen thi…

I always have two copies of tmux running, for this very reason. Someone out there surely must have a better solution.

I used to do this all of the time in screen, but I haven't done so since switching to tmux (haven't run upon the situation). You've inspired me to look into it.

First, terminology. I know that tmux has: servers, clients, windows, sessions, and panes, but I've never bothered to understand how they fit together.

* server - The server is a process that listens on a unix socket, and accepts connections from clients. Each server manages one or more sessions, which is a grouping of windows.

* client - A terminal connected to the server. Each client connects to a single session on the server.

* session - A collection of windows on a server.

Each session has a single 'active window.' When you connect two clients to a single session, switching the current active window affects what both clients see.

Solution:

Windows can be shared between sessions, and a single window can be present in multiple sessions. This culminates in a tmux feature called "grouped sessions" where multiple sessions are linked and share the same windows. You can use this command:

  tmux new-session -t session-id
source: http://unix.stackexchange.com/questions/24274/attach-to-diff...

Re: Workflow in tmux

#30

Post by barkmadley »

vec wrote: post #3
swah wrote: post #2

OT: Tmux/Screen are a little bit RSI inducing to me, to be used effectively. Any tips?

Remap caps lock to be a ctrl key, then preferably remap your prefix key to a. Caps+a is way easier to type.

I would find Caps+a very difficult to type (since it uses the two weakest fingers). Have you ever tried Caps+d or Caps+f?
Post reply on HN