Premise

So I had a Linux laptop for a bit now. On my main desktop workstation I used to have Arch, but to help my wife's recent 3d endevours I installed PopOS instead, which is more user friendly, and most importantly, is somewhat officially supported by Autodesk. Where by "officially supported" I mean: there's a 13 steps guide on their website documenting the commands to run to get it to work, including setting up correctly their beautiful Licensing tools (something that I tried to on Arch without success, mostly due to the horrible error messages spit out by the AdskLicensingHelper CLI).

Due to this loss, the amount of tinkering I feel the need to do on my laptop has grown exponentially. Which eventually lead me into the beautiful 🐇 hole of tiling window managers..

Disclaimer: Everything I write comes from those tiny funny neurons firing in my own brain. Nobody (especially my employer) told me what to write in this article.

A quick note on how I install (doom) emacs on a new computer. For a guide on how to use Doom once it's installed, see my doom-emacs-handbook article instead.

In thoughts-on-ai-art (which is from 2018, in the midst of my Computational Art studies), I wrote the beginning of a never-to-be-completed draft about the role of AI as a mean to generate artworks. As somebody deeply interested in coding rules, patterns, cellular automata by hand the Weltanschauung around using AI to generate the final product always left me with a sense of.. unfullfiment.

Since I might never finish that article, and I've decided to keep that as-is, I can least re-share an article that I found to share some of my same internal doubts about this new world we've somehow decided to build: https://drewdevault.com/2023/08/29/2023-08-29-AI-crap.html (which I got from https://mckayla.blog/posts/recommended-reading-2023.html).

Disclaimer: Everything I write comes from those tiny funny neurons firing in my own brain. Nobody (neither my employer nor Framework) told me what to write in this article.

A new adventure

I've been wanting a just-for-my-own-enjoyment Linux laptop for a looong time. Probably it all started from my time in Framestore, when CentOS was the main OS at work, and I could see the Linux Jedi there perform all kind of (useful) one-line shell trickeries. You could tell those kind of things came from running Linux as a daily driver at home, not just at your $dayjob.

When I was young I went through my period of fascination with Zen. I still hold some Zen teachings dear to my heart, but these days I wouldn't be able to you what Mahāyāna Buddhism is really about and what Tenets there are, if any.

During that period, I remember wanting to study Zen officially, but the only school close to me was in Rome, and travelling there from my place was a bit of a commitment. Despite that, one day I gathered all my motivation, took the car and decided to drive all of way there. After fighting through late-evening traffic in Rome I managed to find a parking spot close enough to the place and I finally got at the Zen school, only 5 minutes late. I think it was 5 past 8, which is why taking the train was not a possibility, given the last train home used to have been at 10:30pm and I imagine this would be at least a 2 hour affair.

Disclaimer: everything that follows is the result of what I think and is in no way connected or endorsed by my employer.

It's no secret that I've been enjoying working in Doom Emacs for the better half of the past year (I wrote about it here: /doom-emacs-handbook/). So it shouldn't come as too big of a surprise that I decided to pay homage to the programmable text editor for martian hackers with a small 3d asset inspired by the cute cacodemon icon created by jaidetree in their popular repo: https://github.com/jaidetree/doom-icon .

This^ cacodemon is coming for you

Disclaimer: everything that follows is the result of what I think and is in no way connected or endorsed by my employer.

I have started my personal Rust journey a few years ago but I really didn't venture into trying to put it in production at $dayjob until a year or so ago.. and since then I have learned a few things that I think are worth sharing. Most of what follows should be read in the context of writing code supporting a Computer Graphics / Visual Effects pipeline (one of those places where the software is only relevant if it helps produce better pixels).

For many years, I have been guilty of always recreating an ssh-agent instead of reusing the previous one. I know, it's an atrocity and a waste of CPU cycles and registers. It had to stop.

Every time I would try to use a ssh-key via ssh-add, I'd see the dreaded

Could not open a connection to your authentication agent.

message and I would just mindlessly run eval $(ssh-agent). With time, this would leave an army of ssh-agent processes behind my back..

Image under Public Domain, but original credits go to Reddit user Anenome5

Tell me why

First of all, why would you still use a programming language first designed in 1960, using an implementation (SBCL) that has been around since at least 1984?

If you do the math and compare it to the pace of web development, it's like sticking with a tool that was written 126 JavaScript frameworks ago (according to this SO article). Imagine doing web development today using something that came before jquery!

AKA: how to use Doom Emacs as my main text editor for note-taking and software development.

But what is Doom Emacs ?

An Emacs framework for the stubborn martian hacker

The TL;DR is that Doom Emacs offers sane defaults for most stuff, and uses SPACE as your leader key. The killer feature for me is using the beautifully lisp-y Emacs ecosystem of packages together with the insanely practical vim keybindings (if you like being evil ).

NOTE: Everything I write is tested against my own config, which you can find in my dotfiles repo: https://github.com/vvzen/dotfiles

For more info on Doom Emacs itself, have a look at https://github.com/doomemacs/doomemacs

Buffer and File Navigation

• SPACE + . -> Find a file to open in a new buffer

This^ uses dired, so you will be able to fuzzy match, etc.

• SPACE + SPACE -> Find a file in the current project (also uses fuzzy find, but leverages projectile)

• CTRL + x + d -> Edit the dired directory for the current buffer (and more)

• SPACE + b + i -> Open a buffer listing all buffers (via ibuffer)