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

Benefits of using tmux – streamlining your development environment

blog.bugsnag.com

Post reply on HN
Print view View original

41–50 of 172 posts

Re: Benefits of using tmux – streamlining your development environment

#41

Post by clarry »

joatmon-snoo wrote: post #25

When I was first introduced to tmux, I was really excited by having a terminal session I could reattach to. I was never able to get very deep into it though: (1) a lot of the time a single script would get me up to speed, (2) the extra layer of abstraction broke some stuff I was doing, and (3) I couldn't make heads or tails of a lot of the tmux documentation. I'll definitely take a second look at a lot of the things…

I think you should give the man page & built in documentation another chance. It's not that long (maybe 40-50 pages printed) and you can skip a few sections that you'll know to look up if you need them. You can also skip the detailed descriptions of most commands and options. Just having the important shortcuts memorized and having a general idea of what commands you have and what they do is all you need. Don't forget to read the examples.

Re: Benefits of using tmux – streamlining your development environment

#42

Post by greenshackle2 »

pfranz wrote: post #20
nextos wrote: post #9

Does anyone run tmux with a tiling window manager for local development? If so, what are the advantages? I know automating sessions is one of them, as explained in the article. I am more interested in hearing about interactions with the terminal. You already get good mouse-less window management with something like i3 or xmonad. How about copy & paste? I use urxvt plugin for this, but I often find myself using the mo…

Similar to that, I've seen a lot of blog posts about Tmux and Vim, but I've been itching to see one where they talk about day-to-day. When do they use vim-split versus tmux pane, vim buffers versus tmux windows? I use both, but aren't very systematic...there's a bit of cognitive load when remembering which I'm using and using the different commands to navigate. You can't do diffs with panes and it's nice to use vim b…

I use a tiling WM with tmux and vim. I have three levels of windows/tabs. It's probably not optimal but I've gotten used to it.

I basically always run all my terminals in a single tmux'd window, and run a single instance of vim. I use vim windows when I edit multiple files at a time.

Re: Benefits of using tmux – streamlining your development environment

#43

Post by minhajuddin »

positr0n wrote: post #37
minhajuddin wrote: post #19

I use a tool called tummy ( https://github.com/minhajuddin/tummy full disclosure: built by me) which allows me to create a Tmuxfile per project. A typical file looks like this: session "liveform" directory "/home/minhajuddin/r/liveform/frontend" window "src", [ pane("vim TODO"), ] window "server-pry", [ pane("puma --port 3000 --config

I used to use tools like that (tummy, teamocil, etc) but I've since discovered tmux-resurrect. It persists tmux sessions, windows, panes, and a whitelist of non-destructive commands like vim and top across reboots. Now my tmux sessions just organically grow and shrink as necessary and I never worry about having to recreate them. Of course I can see the case for combining both tools. If you have a lot of projects, and…

I've tried tmux resurrect. Wasn't for me. With a predefined script I can close and open many windows with abandon. Also, creating the initial script is simple enough. I guess different strokes for different folks :)

Re: Benefits of using tmux – streamlining your development environment

#45

Post by Artemis2 »

godmodus wrote: post #36
parzivalm wrote: post #29

Earlier quoted context omitted.

I think they are trying to say screen is better since it uses less code.

not sure he says screen is better. screen is much older, but it's interesting to see the code comparison. i doubt this says anything about code quality - i expect a lot of non OOP code in screen and more in tmux. despite having fewer lines of code, screen's tar gz is at ~1mb, while tmux is at ~470k. overall, interesting.

There is a bit more code in tmux but it's split in many more files than in screen, and there are significantly more blank lines and comments. tmux seems better in my opinion, but it's certainly difficult to tell without looking at the actual code.

Re: Benefits of using tmux – streamlining your development environment

#48

Post by nicwest »

beefsack wrote: post #44

I started writing a terminal multiplexer in Rust, partially because I wanted to fix clearing ANSI escape codes to EOL, but also because I wanted to try and come up with a multiplexer that had very similar shortcuts and commands to Vim.

How did it go?

Re: Benefits of using tmux – streamlining your development environment

#50

Post by julian_1 »

nextos wrote: post #9

Does anyone run tmux with a tiling window manager for local development? If so, what are the advantages? I know automating sessions is one of them, as explained in the article. I am more interested in hearing about interactions with the terminal. You already get good mouse-less window management with something like i3 or xmonad. How about copy & paste? I use urxvt plugin for this, but I often find myself using the mo…

I use screen (like tmux) and xmonad.

The tiling window-manager is used for longer running GUI apps - webbrowser, pdf/email viewer, CAD etc and for apps that I don't context switch as quickly. Also for handling the dual monitor setup.

I use screen for managing a consistent cli environment - that could be anywhere - on my dev machine, or sshd to a dev container or cloud box. I also tend to context switch screen environments much more quickly - eg. between edit (vim), compile and run turnaround.

Post reply on HN