colorize VS Tmuxinator

In Ruby, this is possible using a gem like Colorize or Rainbow.

Add the colorize gem to your project by including the code below in your Gemfile.

So you want to add color to your terminal app? Since you're a programmer, the first thing you do is go straight to Google. This generally leads people to two ideas. One is the popular Colorize gem, which is an easy and super convenient way to get color functionality into your app. You just install the gem, require it into whatever file(s) you wish to use it in, and then you'll have several color utility functions added onto the String class. Other things people often run into are Stack Overflow posts like this one, which essentially peel back the curtain on how the Colorize gem works. When we want to add colors to a string, we wrap the string in an ANSI escape code that signals how your terminal emulator should style the text.

Before I start going into more detail, here's the code for the rake task. The dependencies for the rake task are a running ngrok instance, the twilio-ruby gem (I'm using v5.67.1), and if you'd like a pop of color in your terminal to make things easier to spot, the colorize gem

The next thing I used on my project is the Colorize gem

The named colors available through the colorize gem are defined in Colorize::ClassMethods#color_codes, L61-73. You'll notice the colors are organized into two columns of 8 colors, plus default. Any basic color terminal will support 8 colors. The next level of support is 16 colors, and finally 265 colors. IRB does something similar in Colorize::DEFAULTS on L29-L34. Note that these two classes share a name, but they're entirely different and unrelated.

Well, I now use tmux and tmuxinator. I have had many failed tmux attempts over the years, but I'm firmly bedded in now.

I once bought a 32 core ThreadRipper and tried to get along with using a cheap £200 Windows 10 laptop to remote into the threadripper while in coffee shops and use the ThreadRipper to do my work.

The £200 Windows 10 laptop wasn't powerful enough, it was too laggy. Even on Wifi.

I love the idea of the X11 protocol. And I still love the idea of a web desktop. Something that is supremely well integrated and allows me to move workloads between client and server seamlessly. This idea I really like. The ability to outsource computation and storage seamlessly. A process can be moved between machines seamlessly.

This could be modelled in Javascript and promises that can be sent around. Microservices in the desktop environment.

I looked at tools that would bring up tmux sessions with everything preloaded. (https://github.com/tmuxinator/tmuxinator)

ScrapScript has very good ideas in this area of distributing dependencies and storage. (https://scrapscript.org/) There is also val town.

I never use KDE Plasma widgets or the sidebar widgets that Mac provided.

There is so many exciting ideas that could be tried out but I worry they're all too big ideas to be implemented.

tmuxinator

I use https://github.com/tmuxinator/tmuxinator for my workspaces. Doesn't save ad-hoc layouts, but usually I find one layout that works per project, then create a tmuxinator config for it, so after reboot, it's a short "tmuxinator start $my-project" away to get back to how I want it to be.

you might be interested in: https://github.com/tmuxinator/tmuxinator

I’ve become a huge fan of tmuxinator. Incredible tool for defining templates for tmux.

https://github.com/tmuxinator/tmuxinator

I doubt that would be possible with tmux's built-in zoom functionality (if it is, I'm not aware). You can use tools such as tmuxinator to create cusotm layouts, but I think "zoom" in tmux means "cover the whole window"

mprocs looks pretty cool. In the past I've used Tmuxinator or Tmuxp configs for stuff like that.