I’ve been using Xonsh, a shell that combines a shell REPL with a Python REPL, for years now. I’ve also been using Emacs for years, but I was never able to marry the two in a satisfactory way. But finally, after being frustrated for long enough, I solved the puzzle. This article is written to help like one or two other people on this world who use both Emacs and Xonsh.
I recently changed up my blog’s theme. I previously used beautifulhugo, and now I use hugo-pure. The whole thing’s a touch more basic, but I’ve not lost any important features. Multi-language supports works (although it has been ages since I posted in Esperanto), and posts display just fine.
The most important thing I changed from the hugo-pure theme is the text colour: my black text is #000 instead of some dark grey.
Yesterday I released v3.1.0a1 of the REUSE tool. It is an alpha release for the soon-to-be-released REUSE Specification v3.2, which can be found in its current state at this link.
The biggest change is the introduction of REUSE.toml, a configuration file that replaces the soft-deprecated .reuse/dep5. This configuration file allows you to declare the copyright and licensing of files (and globs of files) relative to the file. The important distinctions from .
On-and-off over the past few months I wrote a new tool called Protokolo. I wrote earlier about how I implemented internationalisation for this project. This blog post is a simple and short introduction to the tool.
Protokolo—Esperanto for ‘report’ or ‘minutes’—is a change log generator. It solves a very simple (albeit annoying) problem space at the intersection of change logs and version control systems:
Different merge requests all edit the same area in CHANGELOG, inevitably resulting in merge conflicts.
TL;DR—look at Protokolo and do exactly what it does.
This is a short article because I am lazy but do want to be helpful. The sections are the steps you should take. All code presented in this article is licensed CC0-1.0.
Use gettext As a first step, you should use gettext. This effectively means wrapping all string literals in _() calls. This article won’t waste a lot of time on how to do this or how gettext works.
I recently happened upon an article1 that argued against the four freedoms as defined by the Free Software Foundation. I don’t actually want to link to the article—its tone is rather rude and unsavoury, and I do not want to end up in a kerfuffle—but I’ll include an obfuscated link at the end of the article for the sake of integrity.
The article—in spite of how much I disagree with its conclusions—inspired me to reflect on idealism and the inadequacy of things.
I recently switched to Fedora Silverblue for my development machine. I want to document approximately how I do this (and why it’s awesome!).
Fedora Silverblue This article is not an introduction to Fedora Silverblue, but a short summary is well-placed: Fedora Silverblue is an immutable operating system that upgrades atomically. Effectively, the root filesystem is mounted read-only, with the exception of /var, /home, and /etc. The system is upgraded by mounting a new read-only snapshot as the root filesystem.
I like to read GNU/Linux hobbyist forums from time to time. Partially to keep up with all the changes that are constantly happening within the lovely world of Free Software, but mostly because I’m just very excited about GNU/Linux. It is quite possibly the world’s biggest international collaborative effort, and that’s just mind-bogglingly cool—the idea that people from all over the world come together to make this amazing tool for everyone to freely use.
This weekend, I attended CopyCamp in Warsaw. I arrived in a hurry and on a whim, because I was substituting for someone who could not attend last-minute.
Erik Da Silva and I together held a talk on the FSFE’s latest campaign, «Public Money, Public Code». It is a campaign that postulates that software used or created by public institutions ought become Free Software and available to the public that paid for it.
There are a lot of conscious choices and efforts I make when it comes to how I do my computing. I list them here for me to review once in a while, or for your entertainment.
Devices I have five devices that I use at least semi-regularly. In order of use:
Thinkpad T470.
A self-built desktop computer (A10-7850k, R9 380).
Some Kobo e-reader.
Moto G (I believe it’s the 2015 model, but I’m not too sure).