Irreal

One of the worst things I can imagine in my blogging workflow would be to be unable to use Emacs for writing my posts. Word Press does have an editor for writing posts, of course, but I have never used it. Each and every Irreal post starts life as an org-mode file. Even updates are made to the original source and republished to the blog.

Imagine poor Ben Simon then. Simon has been blogging for a long time and has even appeared in Irreal a few times. A long time ago he wrote a blogging engine to publish his Emacs post to Blogger. Everything was fine until he updated oauth2. That update broke his custom blogging engine and until he rewrote it for the new oauth2 he was forced to use the builtin Blogger editor to write his posts. He didn’t like it. He missed the core Emacs editing, of course, but as we all know, Emacs is so much more. He also missed things like shortcuts, spelling correction, completion, and all the other amenities that he’d grown used to after 30 years of Emacs use. Take a look a Simon’s post for some more details of how he uses Emacs for writing his blog.

It can be easy to forget how central Emacs is to our workflow until we’re forced to do without it for a while. The closest I’ve ever come is when Melpa pushed a broken update to Org. I think I recovered by installing an older version until things got straightened out. I didn’t have to live without Emacs but it scared me anyway.

Update [2025-12-20 Sat 16:04]: Blopgger → Blogger.

Tsoding has an interesting—possibly tongue in cheek—video that argues that Emacs is annoyingly useful. He begins by saying that he doesn’t like Emacs because it is “yanky and hacky”. Part of the problem, he says, is that Emacs has been around for a long time and thousands of people have contributed code to it. The reason it’s so useful, he speculates, is because it’s extensible. He illustrates the point by extending Emacs with a Hello World function and makes it callable with a keypress.

After a lot of thought he’s decided that Emacs’ secret is the buffer, which deals exclusively with text. He illustrates this with Dired. You call Dired and it puts an ls listing into a buffer. This is just text and you can treat it the same way you treat any text buffer. A special feature of Dired is that you can save the edits back to the file system. In particular, you can change the names of a file in a Dired buffer and have those changes take effect in the file system.

Now for the real secret. Dired was written by one developer and the multiple-cursors package was written by another. Neither had the other in mind when they wrote their packages yet it’s easy to compose the two packages because they both deal with text in a buffer. Tsoding illustrates this by bringing up a Dired listing, using multiple-cursors to change the names of a group of files, and then save those changes back to the file system.

He ends the video by warning that if you’re looking for a cool customizable editor, stay away from Emacs because you’ll never be able to get rid of it. It’s too useful.

Update [2025-12-19 Fri 11:32]: Dried → Dired.

Another quickie for those of you who prefer using Emacs in the terminal. The default Emacs action for Ctrl+w is to delete the current region. In most shells, Ctrl+w deletes the previous word.

Srijan Choudhary found this a little disconcerting so he ginned up a bit of Elisp that makes Ctrl+w delete the previous word in Emacs unless the a region is active in which case it deletes the region. That helps ease muscle memory problems between the shell and Emacs.

This is not a problem for me for two reasons. First, I hardly ever use the shell anymore. Almost everything I do is in Emacs. Even when I am in the shell, I hardly ever remember to use Ctrl+w. More importantly, I long ago installed Steve Purcell’s whole-line-or-region, which, among other things, kills the active region if there is one or the current line if not. It’s a great package that I use many times a days. It’s bound to Ctrl+w so I wouldn’t want to change it.

If this is a problem for you, take a look at Choudhary’s post for the Elisp to fix things up.

Just a quickie today. This post addresses a niche need that most readers probably aren’t facing. Joar Alexander Pablo von Arndt’s girlfriend recently bought a Framework 12 laptop and stylus and wanted to use it to take handwritten notes that she could later organize in Org mode.

That’s the type of thing that sounds like it should be doable with Emacs and, of course, it is. The solution they settled on was to use Xournal++ to take the handwritten notes and org-xournalpp to interface it to Emacs.

Sadly, it didn’t work quite right on the Framework 12 so they wrote a bit of Elisp to do the interfacing. It turned out to be pretty easy. See Pablo von Arndt’s post for the details.

This is another nice example of how you can use Emacs to solve problems with just a little investigation into what’s available and perhaps a bit of Elisp.

Update [2025-12-17 Wed 11:28]: Added link to Pablo von Arndt’s post.

For those of you who like to run Emacs in the terminal, Adithya Kumar has some useful advice. One of the problems with using the terminal is that some key presses are not passed on to Emacs. In graphical mode, Emacs receives key presses directly from the OS while in terminal mode the key presses are processed by the terminal software first.

Kumar’s remedy for this is simple and ingenious. It has two stages. In the first stage, he specifies alternate bindings for the problem keys. For example, his terminal doesn’t do the right thing for Ctrl+/ so he rebound the undo command to Ctrl+c c u. By itself, that’s not a very good solution because it breaks your muscle memory. The second stage is to train the OS to send Ctrl+c c u instead of Ctrl+/.

You need a keyboard mapper to do this, of course, and Kumer suggests ones for Linux, macOS, and Windows. I suppose that this solution has the potential to interfere with other applications needing one of the problematic bindings but that strikes me as unlikely and Kumars suggestion seems like a good one to me. Take a look at his post for all the details. If you’re a terminal user, it will be worth your time.

For a long time I have been a huge fan of abo-abo (Oleh Krehel). He wrote the Ivy, Avy, and Swiper packages that are probably my most used Emacs add ins. Eleven years ago I wrote, “When I get tired of blogging I’m going to write some Elisp that everyday will make a post that says, ‘Abo-abo has a great post today. Go read it.’”

A while ago, abo-abo suddenly disappeared. His programs are still being maintained but little has been heard from the man himself. The accepted story was that he had had a son and was devoting his time to being a father.

Now Patient_Chance_3795 over at the Emacs reddit asks what did happen to him? Someone pointed at this comment from abo-abo giving an update on his situation. The TL;DR is that his son is almost 4 years old and that he hopes to get back to maintaining his packages—and presumably writing others—soon.

Along with all his other users, I hope that fatherly duties will allow him to return to full engagement with our community. He is certainly one of our most prolific members and he has been missed. In the mean time, I salute him getting his priorities straight and devoting his time to his son and family.

Álvaro Ramírez is back with a new video in his Bending Emacs series. This time it’s about the super useful and flexible completing read function. The basic idea is that you supply a prompt and a list of possible answers. The user can scroll to select an answer or use fuzzy matching to pick the desired option.

There are, of course, various flags to fine tune its behavior. The most useful is probably a flag to insist that the option be from the list rather than anything the user wants to enter. To me, one of the nicest things about completing-read function is that it can—almost magically—automatically adjust to whatever framework you’re using. Ramírez and I both use the Ivy framework, which provides an nicer interface to the function. There are other frameworks as well and the completing-read function automatically adapts to the one in use. Ramírez demonstrates this by turning off Ivy and completing-read falls back to its default behavior. This is especially nice when you’re developing an application because you can just write to the default and Emacs will automatically adjust to whatever framework is active.

Ramírez covers all this and shows several applications of completing read that he uses on his system. He even shows how to use it for command line utilities.

I use completing-read all the time in my own development and can’t recommend it enough. The list of choices can be calculated on the fly so it’s very flexible and doesn’t depend on your knowing what the choices are in advance. If you aren’t already using it, give it a try.

The video is 17 minutes, 4 seconds long so plan accordingly.