A big driver of improvements in software are the users. I’m very lucky to have a community of users who provide well-thought-out suggestions, and when they report bugs it is usually easy to determine what the underlying cause is.
Hot on the heels of 2026.11 comes 2026.11.1 with some bug fixes.
The first fix I worked on for this release, was where the home screen widget was ignoring the sort hints when provided with the new search syntax. For example, /state:TODO AND tag:work sort:priority wasn’t being sorted by priority. This bug has been fixed.
Next I came to a user who was having trouble getting beorg to decrypt content they’d encrypted from within Emacs. Recently I had updated some of the code around encryption, and I was failing to handle different encodings of passwords.
The final fix for this release was around timezones and timers. If you’ve ever worked on software you know that timezones can be a head scratcher. This particular bug was where a timer had a CLOCKLINE with a time that didn’t exist in the current timezone. 01:17 on 30th March 2025 is perfectly valid if you are in New York, less so if you are in London! In London on that date the clocks went forward at 1am, straight to 2am - anything in-between doesn’t exist! New York (EDT) had its change on the 9th of March. Some recent updates I’d made to how beorg failed to account for this.
As always, thanks to everyone who gets in touch. If you’ve ever reported a bug and don’t see it fixed after a couple of releases, please give me another prod!