loading words...

Aug 15, 2019 22:32:18

Tmux

by @craigpetterson PATRON | 328 words | 294🔥 | 296💌

Craig Petterson

Current day streak: 294🔥
Total posts: 296💌
Total words: 82294 (329 pages 📄)

I started using Vim a while ago. I actually first learnt how to program in Ruby on Rails using Vim, but then after a job changed, this went away and I started using more UI focused IDEs before sticking to Sublime. I never paid for it, so I get the periodic pop-ups after you to pay for the optional Pro service. I never did. I remember a colleague said to me once: "You didn't even see that pop up did you?". I hadn't. It had become so habitual to dismiss it.

I'm back on Vim now.

I have some custom bindings but I've been intrigued by Tmux. It was always sold to me as windows and tabs, but inside Vim! So, I never bothered, because I like the default terminal tabbing system. I would create tabs using `CTRL+SHIFT+T` for my server, another for any background processes and another for Vim itself. Then I would tab between them as needed with `ALT+<tab number>`.

After installing Tmux, this uses a similar system, but with `CTRL+b` as the lead command. After tinkering for a bit, it was still a glorified tabbing system, but now I have it set up so that I can browse the terminal history to copy and paste! This was the whole reason I wanted to use it!

This means I can now use Tmux to copy git tag, failed test file names and merge conflict file names super easily. Goodbye mouse.

My dotfiles are publicly available, if you wanted to have a tinker.

Tomorrow, I'm going to look at setting up shortcuts to find these items and perform a set action with them in simple, one-button commands.

In pseudo code, for a merge conflict, that would be like so:

  1. Open the Vim process within Tmux
  2. Find the words "Both merged:"
  3. Copy the file path immediately following it
  4. Open a new window
  5. Open the file in the new window

contact: email - twitter / Terms / Privacy