Irreal

Hooray. Journelly, which I think of as an iOS front end for Emacs’ Org mode, has been officially released. For those of you who have been waiting for an official release to try it out, your time has come.

I’ve been using this app everyday for the last month and even though I was working with a beta, it has been rock solid. I really, really like this app and recommend that everyone try it out. It’s $14.99 but let me assure you that it’s worth every penny.

One of the things that I haven’t mentioned in my posts about it is that there’s seamless syncing of your data. No third party apps or difficult configuration. You simply specify that you want to sync your data to iCloud and it’s instantly available to Org mode on your Mac and the rest of your iOS devices. Exactly what we expect, but seldom get from apps that interface between iOS and Emacs. Ramírez says that exporting to Markdown is on his todo list so even if you aren’t—for some reason—an Org mode user, he’s got you covered.

This is the first app that I’ve bought for a long time but I’m happy to spend the money. Journelly has become an important part of my workflow.

The Emacs mode line contains a wealth of information, much of which I depend on daily. Some of that information is what the major mode is and what minor modes are active. Again, that’s often useful information. Still, there are plenty of minor modes that I don’t care about, either because they’re always enabled or because they simply don’t matter to my workflow.

For a long time, the standard way of dealing with that was the diminish command that would prevent a given minor mode from appearing on the mode line. The problem was that it sometimes didn’t work and, at least in my experience, every update of a package would reset the diminish function to off for that mode.

Relief is finally—or at least will be—here. Coming in Emacs 31 is mode-line-collapse-minor-modes. The idea is that you will list in a single variable those minor modes you don’t want to appear on the mode line or, optionally, those you do. By default those modes excluded are represented by a single ... on the mode line. You can click on that to see a list of the hidden modes.

As I’ve said before, I usually have two side-by-side windows in a single Emacs frame. That means that there’s not a lot of room on my mode line so getting rid of less important information is essential to me. Diminish has worked reasonably well for that but I’ll be glad to have a simpler way of handling the problem. Emacs 31 is still sometime away but it’s something to look forward to.

It’s been about a month since JTR (over at TAONAW) and I started using Journelly. Although it’s still in beta—but approaching its release date—I’ve nevertheless come to rely on it for my memo book. It’s smooth integration with Org mode and Emacs makes it a natural iOS front end for Org and a perfect fit for my memo book. Keeping its file in Org format and syncing it to my Mac make it really easy to integrate it into my Emacs workflow.

JTR has a post reporting on his own experience with using Journelly over the last month. Like me, he’s settled into using Journelly as part of his day-to-day work and depends on it even though it’s still beta software. As I discussed the last time I wrote about JTR and his use of Journelly, he uses it as a staging area for his other Org files. That appears to be working well for him and he’s been refining his workflow as he gains experience with the app.

One of his major concerns is dealing with the photos that he adds to the entries. He likes to tweak them in various ways such as reducing their resolution and sometimes even editing the photo itself. Happily, I don’t have those problems. I suppose it might happen that I need to work on a photo for some reason or another but I can do that from the comfort of my Mac.
If you’re dealing with the Journelly photos a lot, you might want to read about how JTR deals with the fact that Journelly names them with unique IDs that give no clue as to what the photo is of. The TL;DR is that he uses Dired thumbnails to see what each picture is about. The photos are kept in a separate file so it’s easy to display the thumbnails in Dired.

As I’ve said before, Journelly can adapt itself to a variety of workflows so it’s worth your while to read about as many of them as you can. Take a look at JTR’s post to see one of those workflows.

Update [2025-04-29 Tue 13:06]: In a subsequent post JTR writes a bit more about how he handles pictures in Journelly.

Charles Choi has posted a tip mostly, he says, as a reminder to his future self. It’s about how to sort strings on a single Emacs line. At first blush that may not seem all that useful but a moment’s thought will bring to mind all sorts of situations where it’s just what you need.

The secret sauce is sort-regexp-fields, which actually sorts a region whether or not it’s on a single line. When called interactively, you will need to supply two regexes. The first is used to identify the record and the second to identify the key of that record.

If you specify a match field in the record regex, you can use a match number (\n) for the key regex. If the key is the whole field, you can use \&.

Choi has an example that shows how to sort quote-delimited strings on a single line and the documentation has an example of sorting lines by the first word that starts with f. The documentation example shows how powerful the method really is.

In any event, this post is partially a reminder to future me and you should bookmark Choi’s post to remind yourself how to do it. It’s another one of those things that you don’t need very often but when you do, you’ll be really glad to have a reminder of how to do it.

Christian Tietze has an informative post that tells us how to keep an Org file sorted. Your first question should be, “What do you mean by sorted?” Your second question should be, “What does ‘keep sorted’ mean?”

Tietze answers both these questions. The answer to the second question is easier. By “keep sorted” he means that after adding an entry to the file, it will automatically be inserted into its proper “sorted” place without the user having to do anything special.

The answer to the first question is “it depends”. Not very helpful, I know. The precise answer is “whatever sorting order you can describe with org-sort-entries.” Take a look at its documentation to see how many possibilities that entails. You can also provide your own comparison and data extraction functions so the practical answer is “just about any order you desire.”

There is, of course, a bit of configuration that you have to do to have all this take place. Tietze’s post explains how to set things up. The org-sort-entries function is so flexible that it will cover most cases out of the box but there is, as I said, an escape hatch for special needs.

This is another example of how much flexibility is built into Emacs and Org. Most users probably don’t need and aren’t even aware of the functionality that Tietze writes about but it’s there for those who do need it.

As I and others keep telling you, it’s not an editor, it’s a Lisp instance with built in editing commands. You can make just about anything you need happen, usually pretty easily.

The Emacs Cat has a post on an Emacs feature that I use but had mostly forgotten about. It concerns the Emacs time stamp that lets you record in a file when it was last modified. I use it at the top of my init.el to record when it was last changed.

It’s pretty simple to use. You just add a Time-stamp: string somewhere in the first few lines of the file, do a tiny bit of Emacs configuration, and Emacs will add a time stamp whenever the file is saved. My impression is that it’s mostly used in init.el files but it can be used in any file that you edit with Emacs. The Cat’s post give some examples of using it with an Elisp file, an Org file, and a C++ file.

Usually you have to have the Time-stamp: as part of a comment but in some cases, as shown in the Org file, it can be part of the actual file data. Almost everything is configurable. You can specify how many lines from the top of the file to look for the Time-stamp, and you can specify what the time stamp itself with look like.

Take a look at the Cat’s post or the documentation for the details

Well, actually on any Mac but I couldn’t resist the symmetry. You’re probably wondering what this post is all about. It turns out that Apple computers are inclined to autocomplete “Emacs” to “eMacs”. That, apparently, is because Apple once sold a computer—mostly to the educational market—named the “eMac”.

Over at the Emacs subreddit, uamplifier explains this and provides a link to a Wikipedia article that gives the history of the eMac. All this may be marginally interesting to Emacs users on Macs but the comments provide an additional aspect.

The rest of this post is a sort of PSA for Emacs users on the Mac. The comments to uamplifier’s post explain how to eliminate this antisocial behavior. The first thing you can do is replace the Emacs → eMacs completion. That solves the problem but you can also just disable the Apple dictionary in settings. See the comments to uamplifier’s post for the details.

I’ve never had this problem, probably because I don’t use completion very much and never autocompletion. Nevertheless, I’m happy to see a solution because—due to my sensitive nature—I really hate seeing “eMacs” in posts. It always makes me think that the poster has been lobotomized by the eThis and eThat nonsense that is so endemic in our industry. Perhaps it’s Apple and not these people’s brain that are to blame. Regardless, if you’re using Emacs on the Mac and are having Emacs turned into eMacs, take a look at uamplifier’s post to see how to fix it.

Here at Irreal and in many other venues, you hear a lot about staying in Emacs. The hardcore among us treat having to leave Emacs as a fail. To outsiders, it can seem a little obsessive but it all goes back to having a uniform interface for dealing with text.

Here’s a delightful meme that expresses that impulse. As usual, the comments are really interesting. For a bit of context—as one of the commenters explains—with CUA the Ctrl+a Ctrl+x Ctrl+s selects everything, deletes it, and saves the file; definitely not what you get from Emacs.

It’s astounding how many of the commenters say that they’ve fallen victim to the same sort of thing. Others complain of deleting browser tabs with Ctrl+w. One said that he had moved even browsing into Emacs despite its being suboptimal. At least the key bindings do what you expect them to.

There’s nothing really profound in the post but it is amusing and, as I said, the comments are interesting. They show that those of us who would prefer to stay in Emacs are not alone.