Several weeks ago I wrote about scripting a tmux session’s initialization. At the end of the post I mentioned that while writing it, I had learned about tmuxinator. I even teased that it looked so good, I may switch to it eventually. Well… that didn’t take long. I’ve scrapped my tmux shell scripts, and have converted to using tmuxinator. Here’s how.
I have been using neofetch as my command-line system information tool for a few years now. While browsing /r/unixporn, I noticed that several of the submissions did not have distro logos in their neofetch/screenfetch ascii art. I knew that neofetch was customizable, but have never dug into it myself. So I decided to change that.
A couple months ago I swapped out my dual monitor setup for a single (but massive), 42.5” UHD IPS display. I love it, but admit that sometimes, it has too much workspace. While I still think that the larger display was better choice, I sometimes wish that I had the more limited, but focused workspace of an ultrawide or 1440p monitor. Maybe I still can…
Not too long ago, I updated our home networking equipment to an Ubiqui setup. However, we recently moved into a new house and I switched to a mesh wifi network. No, the switch was not just to increase wifi coverage throughout the entire house. The real motivator (ironically)… was that I needed a better ethernet connection…
I love the terminal multiplexer, tmux. It adds
functionality to the terminal, such as multiple tabs, pane splitting, and the
ability to detach and re-attach everything later (which is amazing when
ssh). I have been utilizing tmux even more at work, and recently
started to script the start up/configuration a tmux session for each project.
The other day, I decided to write a script to spin up a session for working on my
website… and thought it would be a great tutorial!