<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Desktop on Tom Meurs</title>
    <link>https://tommeurs.nl/en/tags/desktop/</link>
    <description>Recent content in Desktop on Tom Meurs</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© Tom Meurs</copyright>
    <lastBuildDate>Thu, 11 Jun 2026 20:28:00 +0100</lastBuildDate>
    <atom:link href="https://tommeurs.nl/en/tags/desktop/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux Is for Everyone: Why This Blog Now Welcomes Beginners Too</title>
      <link>https://tommeurs.nl/en/posts/linux-is-for-everyone/</link>
      <pubDate>Thu, 11 Jun 2026 20:28:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/linux-is-for-everyone/</guid>
      <description>&lt;p&gt;My neighbour is 70 years old. He&amp;rsquo;s used Windows his whole life. Last month he asked me: &amp;ldquo;Tom, I keep hearing about Linux. Is that something for me too?&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;He&amp;rsquo;s not the first. Over the past year I&amp;rsquo;ve had the same question from friends, family and colleagues, each in their own shape. &amp;ldquo;I want to get off Windows, but where do I start?&amp;rdquo; &amp;ldquo;Is Linux hard?&amp;rdquo; &amp;ldquo;Can I still use my normal programs?&amp;rdquo; To me these are easy questions. I&amp;rsquo;ve been running Linux since SuSE 6.0, back when you picked your hardware by whether a Linux driver existed for it. If you&amp;rsquo;ve never seen a terminal, they&amp;rsquo;re not easy at all.&lt;/p&gt;</description>
    </item>
    <item>
      <title>KVM/QEMU Scripts and Aliases: Making Virtualization Actually Usable</title>
      <link>https://tommeurs.nl/en/posts/kvm-qemu-scripts-aliases/</link>
      <pubDate>Wed, 03 Jun 2026 21:17:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/kvm-qemu-scripts-aliases/</guid>
      <description>&lt;p&gt;I run VMs all day. A Kubernetes deployment I want to test, a distro I read about, Windows for that one stubborn application, an experiment I&amp;rsquo;d rather not run on my actual machine. KVM/QEMU is the right tool for all of it. It lives in the Linux kernel and runs close to native speed. Nothing in it phones home, and no vendor gets a say in what I do with my own hardware.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Terminal Multiplexing: tmux vs Zellij vs Screen</title>
      <link>https://tommeurs.nl/en/posts/terminal-multiplexing/</link>
      <pubDate>Thu, 14 May 2026 19:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/terminal-multiplexing/</guid>
      <description>&lt;p&gt;The first time it bit me I was halfway through a database migration over SSH. The train went into a tunnel, the WiFi dropped, and the process on the other end died with the connection. I sat looking at a dead prompt, wondering how much of the migration had committed.&lt;/p&gt;&#xA;&lt;p&gt;A multiplexer would have saved me that hour. The process keeps running on the server whether I&amp;rsquo;m attached or not, so a dropped connection costs me a reconnect and nothing else. I reattach and the work is where I left it. That one property is why a multiplexer goes on every machine I touch, before the editor and before the dotfiles.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Arch vs NixOS as a Workstation: Professional and Personal Use</title>
      <link>https://tommeurs.nl/en/posts/arch-vs-nixos-workstation/</link>
      <pubDate>Tue, 03 Mar 2026 21:28:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/arch-vs-nixos-workstation/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; I&amp;rsquo;ve run Arch and NixOS as my daily machine, and today it&amp;rsquo;s Arch on both desktops and NixOS on the servers. Arch&amp;rsquo;s reputation for breaking is mostly a missing snapshot. With btrfs, Snapper, dotfiles in git and a package list, a rollback takes 2 minutes and the fear of updates goes away. NixOS earns its learning curve when several machines have to stay identical, and on a server I wouldn&amp;rsquo;t run anything else.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Learn the Defaults: Why Portability Beats Customization</title>
      <link>https://tommeurs.nl/en/posts/learn-the-defaults/</link>
      <pubDate>Sun, 15 Feb 2026 19:47:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/learn-the-defaults/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; I spent years polishing a vim and tmux setup, then sat useless in front of a stock vim on a production server. So I learned the defaults I&amp;rsquo;d been overriding all along, and moved my customizations on top of them instead of in place of them. What that looks like for vim, tmux and the shell tools, and the four checks I use to find the gaps.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;For years my setup was the thing I was proudest of. A dotfiles repo with commits going back further than some of my jobs, a vim config that pulled in thirty plugins, the tmux prefix moved somewhere comfortable, a prompt that took a weekend to get right. Down to the last keybinding, it was mine. On my laptop I was fast, and I hardly thought about the tools at all. Muscle memory did the work.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dotfile Management with mise and chezmoi: The Perfect Combo</title>
      <link>https://tommeurs.nl/en/posts/dotfile-management-mise-chezmoi/</link>
      <pubDate>Wed, 11 Feb 2026 20:23:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/dotfile-management-mise-chezmoi/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; Six ways of syncing dotfiles later, the one I kept is chezmoi for the files and mise for the tool versions, with the mise config living inside the chezmoi repo. Templates handle the work laptop against the personal desktop, age handles the secrets, and a fresh machine is one command and about five minutes. The walk-through goes from one managed file to the bootstrap I run for real.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;My &lt;code&gt;.zshrc&lt;/code&gt; is older than some of my coworkers&amp;rsquo; careers. Same for my &lt;code&gt;.vimrc&lt;/code&gt; and my tmux config. They&amp;rsquo;ve grown into a setup that does exactly what I want, and I&amp;rsquo;d be lost without them. The catch is that I run more than one machine. A laptop, a desktop, now and then a throwaway VM for testing. For years, keeping those in sync was a pile of hacks I didn&amp;rsquo;t trust.&lt;/p&gt;</description>
    </item>
    <item>
      <title>YubiKey &#43; Pass &#43; GPG &#43; SSH: One Key to Rule Them All</title>
      <link>https://tommeurs.nl/en/posts/yubikey-pass-gpg-ssh/</link>
      <pubDate>Tue, 13 Jan 2026 17:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/yubikey-pass-gpg-ssh/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; One YubiKey carries a GPG key with a signing, an encryption and an authentication subkey. gpg-agent hands the authentication subkey to SSH, git signs with the signing subkey and pass decrypts with the encryption subkey, so one PIN in the morning and a touch per action replace every password I used to type. The SSH part alone is three steps and worth doing on its own.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;Every morning I plug in my YubiKey, type one PIN, and that&amp;rsquo;s the last secret I type until I pull it out again. SSH to a server, no password. Sign a commit, no passphrase. Pull a secret out of pass, touch the key. One thing in a USB port, and the rest of the day my authentication happens without me.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Pass: the Unix password manager that just works</title>
      <link>https://tommeurs.nl/en/posts/pass-password-manager/</link>
      <pubDate>Sat, 10 Jan 2026 12:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/pass-password-manager/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; pass keeps each password as a GPG-encrypted file in a directory, and the directory is the whole data model. &lt;code&gt;pass -c email/gmail&lt;/code&gt; puts a password in your clipboard from any terminal, &lt;code&gt;pass git push&lt;/code&gt; backs the store up, and the fzf script further down is how I look up every password I have. The price is GPG key management, and it&amp;rsquo;s a real price.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;I used KeePass for years. Then 1Password. Then Bitwarden. All decent tools, and every one of them was too much for what I asked of it. Too much UI, too many features, and a password always lived on the other side of an app I had to alt-tab into. A small interruption, and they added up.&lt;/p&gt;</description>
    </item>
    <item>
      <title>GPG explained: from first key to daily use</title>
      <link>https://tommeurs.nl/en/posts/gpg-beginners-guide/</link>
      <pubDate>Tue, 06 Jan 2026 19:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/gpg-beginners-guide/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; GPG encrypts files and signs things, and it sits under pass, under signed git commits and under the checksums maintainers publish. One command gives you a working keypair in five minutes. Subkeys and a YubiKey come later, if ever, and the UX is bad enough that I complain about it at length below.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;GPG is a tool I kept meaning to learn and didn&amp;rsquo;t, for years. The docs are a wall of text, the terminology is its own dialect, and the error messages are cryptic in both senses of the word.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Taskwarrior, Timewarrior and Vit: The Ultimate CLI Productivity Stack</title>
      <link>https://tommeurs.nl/en/posts/taskwarrior-timewarrior-vit-tutorial/</link>
      <pubDate>Sat, 03 Jan 2026 15:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/taskwarrior-timewarrior-vit-tutorial/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; Taskwarrior, timewarrior and vit are my task list, my time tracking and the vim-style screen on top, all in the terminal and all plain text in &lt;code&gt;~/.task&lt;/code&gt;. Two commands get you started. The rest of this post is what I bolted on afterwards, from projects and dependencies to a self-hosted sync server, and you can stop at any section.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;For context on how my brain works, see &lt;a href=&#34;https://tommeurs.nl/en/posts/working-with-audhd-brain/&#34;&gt;Working with an AuDHD Brain&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Working with an AuDHD brain: why I automate everything</title>
      <link>https://tommeurs.nl/en/posts/working-with-audhd-brain/</link>
      <pubDate>Sat, 27 Dec 2025 14:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/working-with-audhd-brain/</guid>
      <description>&lt;p&gt;For a long time I thought the problem was me.&lt;/p&gt;&#xA;&lt;p&gt;I have &lt;span class=&#34;def&#34; tabindex=&#34;0&#34; data-def=&#34;Autism combined with ADHD. The author has the inattentive presentation of ADHD, and writes about what that means for infrastructure work rather than about the diagnosis.&#34;&gt;AuDHD&lt;/span&gt;&#xA;, autism and ADHD together. The ADHD is ADHD-PI, the inattentive kind, without the hyperactivity most people picture when they hear the word. For years I treated the whole thing as a defect I&amp;rsquo;d train away. I bought the planners. I read the productivity books. Every week I told myself that Monday I&amp;rsquo;d finally be disciplined.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
