I’ve once again changed the design of the site to make it cleaner, more simple and above all, less bloated. I’ve removed a bunch of javascript code (for instance, MathJax is no longer loaded by the main template but by the actual pages that really need it). Also, I’ve simplified the color palette settling on a black on white scheme with green for links and titles.
Old (left) and new (right) design side-by-side. The new design is cleaner and more pleasant to the eye.
The new design also looks better on mobile screens, as I took some care of adapting the templates for pocket devices. Finally, I changed the home page from the blog summary listing to an introduction and welcome page, and added a full blog listing page containing a list of all blog post titles sorted by date.
Description of my daily Linux setup as of October 2019
Updated:
8 minute read
Edit (2020-10-02):
change termite to kitty due to font ligatures support. Edit (2020-06-01):
change urxvt to termite, update info on qutebrowser with tor.*
Overview
In this post I’m documenting the current (March 2019) system setup I use in my development machines. This has been converging for a long time already, and It will surely evolve in the future. However, right now, it works well for me.
I use the machines mostly for development work (Gaia Sky, Gaia First Look, Ph.D., etc.). I also use my personal computers for the occasional light gaming session (Terraria, C&C remastered, or whatever I feel like at the moment) and as all-around computing devices to manage stuff.
During the last months I have been working on a QOL improvement for Gaia Sky video production. Currently, Gaia Sky offers a couple of ways to persist and reproduce camera behaviours: scripting and camera paths.
Scripting offers a high level API which allows for the interaction and manipulation of the internal state. Conceptually, a running script is no different from a regular user. A script runs in its own thread and, like a user, interacts with Gaia Sky’s core through the event manager, a message-passing entity which encapsulates the core functionality.
A couple of days ago I sumbled upon this video by Luke Smith where he presented a couple of scripts to display CPU, memory and temperature information in i3blocks. Since I use polybar due to it working much better in tandem with my dual-monitor setup with different DPIs, I decided I’d adapt and change the scripts to work in polybar. Polybar already comes with memory, CPU and temperature modules by default, but they don’t include a popup showing the top-consuming processes, which is a nice feature to have.
This is just a quick post to share my .dotfiles project. It contains the configuration files for most of the essential utils and tools I use in all my machines. These include the tiling window manager i3wm, the info bar polybar, the awesome qutebrowser, the text editor vim or the file manager ranger. Also, in the bin/ folder there are lots of scripts (most of them hacked together quickly) to do various tasks, like converting garimin fit files to the open gpx format or switching off the monitor in systems without a hardware switch.
