In a previous post I talked about XMonad.Prompt.OrgMode, an xmonad module to rapidly capture thoughts and ideas into an Org file. The functionality that the module provides has proven to be extremely useful to me, and really I couldn’t be happier with it. However, a user recently contacted me by email and told me that they’re missing but one feature: the ability to immediately refile notes.
Motivation§If you don’t know, refiling is the act of moving an entry
A headline, possibly with an attached body.below another heading; i.e., such that it becomes a subheading there. This can be useful for structuring todos into separate categories: one might have projects called “work”, “life”, “xmonad”, and so on, where all related tasks live. Quite convenient! So far, X.P.OrgMode just dumped the created note at the end of the specified file, leaving you to pick up the pieces. This aligns with my personal workflow—while I extensively use refiling, I only do so at the end of the day after reviewing all tasks that have accumulated. However, it is conceivable that someone might want to refile certain tasks straight away when it’s pretty clear that (i) they’ll be kept, and (ii) they can be unambiguously assigned to a certain heading (e.g., an already scheduled work meeting with X).
Showcase§Long story short, this is now built into X.P.OrgMode. There are two new functions:
The former takes the same arguments as orgPrompt (which see), and is for popping up another prompt that asks for a heading. The latter refiles everything under the specified (as the second argument) heading. The way
orgPromptRefile :: XPConfig -> String -> FilePath -> X () orgPromptRefileTo :: XPConfig -> String -> String -> FilePath -> X ()
orgPromptRefileworks is that, after querying for a todo, it always inserts the note into the file and then possibly refiles it to another heading. This way, you don’t need to worry about losing notes when you abort the refiling prompt or enter a non-existent heading. Note: Refiling is (near) instant; the delay you are seeing above is due to
Some gory details§All of the refiling is actually directly done by Emacs itself! More precisely, the edsl that XMonad.Util.Run defines—which I’ve also written about—shells out to Emacs. This might intuitively feel horrible, but that’s just another reason to share it:
This—as you probably guessed already—just executes the following elisp snippet in Emacs’s batch mode:
refile :: String -> FilePath -> X () refile (asString -> parent) (asString -> fp) = proc $ inEmacs >-> asBatch >-> eval (progn [ "find-file" <> fp , "end-of-buffer" , "org-refile nil nil" <> list [ parent, fp, "nil" , saveExcursion ["org-find-exact-headline-in-buffer" <> parent] ] , "save-buffer" ])
I know this seems insane, but letting Emacs do this work is actually much less brittle than the alternative. The Org maintainers certainly know best what refiling means, and thus also what it entails—if all of this logic is already written, why not take advantage of it? Plus, I now don’t have to keep track of subtle changes in newer versions of Org.
(progn (find-file «fp») (end-of-buffer) (org-refile nil nil (list «parent» «fp» nil (save-excursion (org-find-exact-headline-in-buffer «parent»)))) (save-buffer))
Closing thoughts§Writing this was actually a lot of fun, and a great opportunity to play with the edsl that X.U.Run exposes. I reckon there are a few places in my own xmonad configuration in which I could use these kinds of “Emacs scripts” to great effect! One other idea I’ve had is to integrate this into the language that plain old
orgPromptaccepts. It could be prefixed by something like “
ref:”, followed by a unique substring with which to identity a heading. This would have the disadvantage that—without the second prompt—one would not get any suggestions for headings. However, if you want to refile something you probably know where you want to put it; plus, it would not involve a possibly distracting second prompt. Actually, this sounds like a good first pull request: contributions welcome!