Tmuxinator iterm2 windows how to#
Tmuxinator iterm2 windows manual#
Tmuxinator iterm2 windows full#
Tmuxinator iterm2 windows free#

Tmuxinator iterm2 windows manual#

When you think about “Am I going to use the terminal – if I’m gonna base my workflow around the keyboard or around a mouse”, the arguments around the keyboard and a terminal versus GUIs, which usually require a mouse or another input device beyond just the keyboard, the factors are… Somewhat context switching, but I think it’s speed of moving your hand off or on the keyboard, to the mouse, which is slower once you’re there, but then it’s fast, but that transition back and forth slows you down… And then also the idea of customizability or malleability… I think a lot of the modern text editors are catching up in the malleability category, if you look at just the way you can trick out VS Code or Sublime Text to the hilt, at this point… And so many things are built-in – or not built-in, but available to be added, removed and customized.īut if you had to think about what was the most important thing – you seem to be focusing a little bit on the speed, because you say you feel like you’re a little bit closer to the metal, so to speak… Maybe there’s an analogy with driving a car, an enthusiast likes a manual transmission regular people like automatic transmission.

Tmuxinator iterm2 windows full#

I feel like I’m in full control, and if anything goes wrong, I know what the CLI tool or what the terminal is telling me… Because you get used to the terminology, you get used to how things fail, instead of just cryptic error messages, or just pop-ups or errors being hidden, or anything like that. I’m not just pressing buttons and expecting things to happen, and not really knowing what’s going on in the background. Once I moved to Vim and I just started using my terminal all the time, I feel like I know what my machine is doing it’s not as if I was handing that to an IDE. I think that made things harder to understand. I think it gets a bit confusing for people, especially people that are new, what are the things that are related to their development environment and what are the things related to the toolchain they’re using. That was alright at the time, but one of the things I struggled the most - and I even talk about it in the post - is that, especially for people that are starting out, I think it’s hard to figure out what’s the limit of the IDE, where does the IDE stop and where does the language toolchain start. When I started out in college, we were using Eclipse. I tried some IDEs, but it’s just not the same thing, even with Vim mode.

Tmuxinator iterm2 windows how to#

And now that I started using CLI tools more often, all I know how to do, all my workflow revolves around CLI tools. But after a month, I was just so much faster, and my workflow got so much more comfortable that I just couldn’t quit. In the beginning, I’ve gotta say, it was very frustrating. If I had used Vim during work, and stuff, I think I wouldn’t have been productive enough, but after a month – I just persisted I just kept trying…

Tmuxinator iterm2 windows free#

He was using Vim, and I was like, “Hey, how do you do things so fast?” And then he showed me his dotfiles, and the explained how the whole Vim code works… So then I just started trying it out in my free time, because at the time I was doing an internship. I remember we were sitting next to each other in college.

I was just impressed by how things were happening. So at the beginning I was more impressed than I actually – it was not as if I had made any formal decision. It’s been a few years now… I remember when I started, to be honest, I’d seen a friend of mine using it, and it looked so cool, and he was super-fast with it.