Recent Changes

Here is the list of recent changes at this site.


Updates in the last 30 days

1 | 3 | 7 | 30 | 90 days
List all changes Include rollbacks Include minor changes
List later changes RSS RSS with pages RSS with pages and diff

2025-11-17

  • 20:07 UTC (new) (history) 2025-11-17 Showing size of Org mode subtrees . . . . mbork I’ve been using Org mode for way over 10 years now, and some of my Org files grew to a considerable size. My largest Org files are over 3 megabytes, which means that working with them tends to be a bit slow. I’d like to be able to check which parts of the Org file are the largest and which are smaller. With files on the disk, the classical tool to achieve this is du, along with its interactive counterparts like ncdu or the insanely fast gdu. I hoped for the existence of some kind of org-du which would do a similar thing with Org files. In fact, a tool with that name (written by the famous Karl Voit!) does exist, but it has three disadvantages which pretty much disqualify it for me: it counts lines instead of bytes, it is not working inside Emacs, and it is written in Python. Let’s write an org-du command which would work a bit like org-clock-display, that is, it would show the size of each subtree next to it using overlays.

2025-11-10

2025-11-03

  • 18:57 UTC (new) (history) 2025-11-03 Beeminder Org timer . . . . mbork Once I wrote about what I called “Org mode burst timer”, another idea occurred to me. That code is good, and may be useful for some people – if it is for you, feel free to use it! But I can do something better for me. Instead of requiring myself to set the burst property manually, I could tie this code to my Emacs Beeminder client. When a clock is started on a beeminded task, it could retrieve the necessary data about the goal associated with the current headline and notify me when I work on it enough.

2025-10-27

  • 15:20 UTC (new) (history) 2025-10-27 Org mode burst timer . . . . mbork Preview: Org mode has two built-in timers – the “relative timer” (which is basically a stopwatch – it starts with 0 and counts up), useful for taking meeting minutes with an indication of when things were discussed, and a “countdown timer” (which is, well, a countdown timer – you tell it a duration, it counts down from it, and rings a bell when it gets to zero). What I sometimes miss is the following feature. I’d like to have some kind of timer which would tell me when a given amount of time passed, but then it would keep running. For instance, let’s assume that I want to write this blog post for at least 25 minutes, but also measure the time I spend doing it even if I keep writing for longer.
  • 15:20 UTC (new) (history) 2025-10-20 Org mode burst timer . . . . mbork Deleted 2025-10-20_Org_mode_burst_timer

More...

Filters