As I explained, I recently decided to switch from GNU Screen to tmux. Well, I ran into a couple of minor gotchas that I mamanaged to work around. First of all, the threads in mutt got somehow distorted after a while and I had to constantly refresh the screen to fix it. In the end, I realized that I just had to switch the value of the $TERM variable to "xterm" to get things working correctly. However, as it tends to happen, doing that introduced another problem elsewhere: all of a sudden, vim lost the functionality to copy to the clipboard, which is key to my workflow. As it turned out, I just had to set the default $TERM to "linux" in that case to get things working. {link to this entry}

I finally decided to bite the bullet, and switch from GNU Sreen to tmux as my default terminal multiplexer. To be honest, nothing in particular brought about this change. In spite of its age, GNU Screen was behaving fine. It's a stable application that does what it's supposed to do, and it does it well. I know there are many articles out there comparing these two apps (for example, this one, or this other one), and they tend to prefer tmux. But, again, being totally honest, GNU Screen was working fine for me. So, what convinced me to switch? Well, first of all, precisely because GNU Screen is much older, it does look as if it's not so actively maintainted as tmux. Also, for the same reason, I assume (but, truly, it's just an assumption) that it may not be so fast to adapt to new developments out there (again, I'm not sure what; the switch to Wayland that should happen sooner or later, perhaps?). But, most importantly, I recently wanted to automate the two or three GNU Screen sessions that I use on a daily basis, so that I could just automatically open several windows on each one of them, name them a specific way, and even run some commands by default. The reality is that, although I searched around for information on how to accomplish this, and there was plenty of info for both, GNU Screen and tmux, it was much easier to configure in the latter. So, in the end, I thought it was about time to start using tmux. Let's see how it goes from here. In case someone is also considering to switch, here is the link to a complete tutorial for beginners, and another one to an article on tmux scripting. {link to this entry}

This one came via Lobsters. It's a list of C functions banned to the git developers because they are not deemed safe. Good to review. Also, it looks like a good idea to add that header file to all projects. {link to this entry}