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

41–50 of 62 posts

Re: Workflow in tmux

#41

Post by mackwic »

emidln wrote: post #32
Osiris wrote: post #23

Earlier quoted context omitted.

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.

Native copy/paste typically requires a mouse. using tmux's copy-mode and pasting doesn't require a mouse an still stays inside panes.

But the tmux copy paste is horribly inefficient.

Re: Workflow in tmux

#42

Post by pimeys »

d0m wrote: post #31
eridius wrote: post #28

Earlier quoted context omitted.

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.

*Started using tmux, then realized for my needs stumpwm was better. Obviously these are two different beasts. I still often use tmux on remote server for instance. However, if you use tmux locally, then a tiling manager might be better.

Exactly. I've been using xmonad for years now and I've tried to start using tmux for several occasions. I've never found any advantage of it compared to my different xmonad layouts: tabbed, tall, tall mirrored and grid.

Re: Workflow in tmux

#43

Post by cturner »

mackwic wrote: post #41
emidln wrote: post #32

Earlier quoted context omitted.

Native copy/paste typically requires a mouse. using tmux's copy-mode and pasting doesn't require a mouse an still stays inside panes.

But the tmux copy paste is horribly inefficient.

Less efficient than reaching for the mouse? :)

Re: Workflow in tmux

#44

Post by cturner »

rogerbinns wrote: post #38
pyre wrote: post #29

Earlier quoted context omitted.

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…

This is so much more complicated! When using byobu I use F3 and F4 to cycle to previous and next window. I can't understand why they think that by default I want all of the viewers to switch at once.

Having the viewers switch by default is useful for demos, when you are showing something to someone. And it's the simplest behaviour for their data structure. So I can see some logic to why they designed it that way.

I'm glad you raised this issue because I've only recently moved to tmux and would have been stung by it.

Could you abstract it away behind a shell alias? I used this:

   alias tmuxc='tmux new-session -t 0'

Re: Workflow in tmux

#45

Post by rane »

base698 wrote: post #9

To get copy/paste to play nice in OSX you have to go through some Herculean tasks. I made it work with netcat yesterday. I was running an http server to do it :) https://github.com/base698/tmux-copy-paste-mac-osx

bind C-y run-shell "reattach-to-user-namespace -l zsh -c 'tmux saveb - | pbcopy'"

works for me.

Re: Workflow in tmux

#47

Post by jasonlotito »

emidln wrote: post #32
Osiris wrote: post #23

Earlier quoted context omitted.

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.

Native copy/paste typically requires a mouse. using tmux's copy-mode and pasting doesn't require a mouse an still stays inside panes.

Using a mouse, you can use tmux's new (in 1.8) pane expansion. prefix + z causes the current pane to take up the entire window. prefix + z again and it goes back to normal. Essentially, it's a maximized/restore capability.

Re: Workflow in tmux

#48

Post by blaabjerg »

d0m wrote: post #31
eridius wrote: post #28

Earlier quoted context omitted.

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.

*Started using tmux, then realized for my needs stumpwm was better. Obviously these are two different beasts. I still often use tmux on remote server for instance. However, if you use tmux locally, then a tiling manager might be better.

Why not both? If you use tmux for your terminals you get persistence in case you need to restart X, or when you log in remotely.

Re: Workflow in tmux

#49

Post by jaredmcateer »

sathish316 wrote: post #39
th wrote: post #24

Earlier quoted context omitted.

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

tmux has its own powerline: https://github.com/erikw/tmux-powerline

Actually that's been deprecated in favour of the one powerline to rule them all that "th" posted above.

Re: Workflow in tmux

#50

Post by s00pcan »

base698 wrote: post #9

To get copy/paste to play nice in OSX you have to go through some Herculean tasks. I made it work with netcat yesterday. I was running an http server to do it :) https://github.com/base698/tmux-copy-paste-mac-osx

This is basically what I was doing except with redis instead of netcat. I was happy to see copy-pipe in v1.8.
Post reply on HN