May 23

Many people in the Emacs community use orgmode. Quite a few of them use the org-babel system to write and maintain their emacs configuration, and so am I. I find the biggest advantage to be able to document my thought process as well as the configuration details. Emacs configuration can get pretty big and maintaining it becomes a lot easier for me if I can read back what I was thinking 6 months ago.

The system borrows from literate programming concepts where you write code and documentation in one document and let tools tangle the code and documentation into separate documents.

The default way to publish an Emacs configuration with that system would be to let org-mode export the configuration document to html and publish that somewhere. What I wanted to do was to use the in-place org-mode converter I am using with Jekyll. In short, the ideal would be that jekyll fetches the authoritative version of my emacs configuration in org-mode syntax and treats that as /normal/ content and publish it.

I started off by defining a collection, a new feature of jekyll, which gave me a chance to use it. The collection is defined in the _config.yml file:

# Emacs collection contains emacs 'generated' documents
    # Render them, i.e. convert them to html. 
    output: true

This will render source files in the _emacs folder as if they were pages. The url generated for them will be prefixed by /emacs/.

In this folder I placed a file with the following contents

layout: orgmode

[... text left out  ..]

{% include extern/ %}

That includes the file <root>/_includes/extern/ from the jekyll installation and renders its content. The only correction I had to make was to insert a raw...endraw block around some org-mode settings.

You can view the result of the rendering in /emacs/config.html

Nov 16

Most of my notetaking and task management is in org-mode so it makes sense to use that as the basic format of my postings too. This is usually done by publishing a project from org-mode into the location where jekyll keeps its files and let jekyll convert that into something publishable. I’m using a slightly different setup which is more effective for blog posting.

Publishing with org-mode turned out harder than I thought. The publish process is pretty demanding in org-mode and you only end up with raw documents that still need to be processed by jekyll. It occurred to me that has the ability to render org-mode documents directly and perhaps that library could be used to turn it into a jekyll plugin so I could use the org-mode format directly.

Turns out there was a recent commit which mentioned an org-mode converter plugin; long story short: installed it and never looked back. Having jekyll convert org-mode files directly saves the whole publishing configuration step in Emacs which would otherwise be needed from within org-mode.

The converter is simple; it uses an org-ruby call to convert the org-file to html and that’s it really:

module Jekyll
  # Convert org-mode files.
  require 'org-ruby'
  class OrgConverter < Converter
    safe true

    def setup
      # No-op

    def matches(ext)
      ext =~ /org$/i

    def output_ext(ext)

    def convert(content)

I can now just write org-mode files with a frontmatter and they’ll end up automatically as blog postings. As yaml frontmatter needs to come first in the file to make jekyll happy this can’t be hidden in an org-mode construct like a comment block or something else that org-mode itself ignores. This makes it harder to use the blog postings for anything else than jekyll because the frontmatter will get in the way; exporting the file to PDF for example. There is obviously room for improvement, but this simple plugin directly gives a workable system.

To have a reference document for writing I created a test org-mode file, with the rendered result here. This file helps to check what org-mode constructs render into something useful and verifying visual layout of them. Not everything worked as I had hoped, but given the amount of complexity that got eliminated I’m quite happy with it.

Issues that I found in the rendering:

  • the headers start at level 1 which is probably 1 or 2 levels too high for my purpose; I haven’t found a way to correct this yet. I probably should file a feature request for this;
  • footnotes do not work, which I would use to keep links nicely at the bottom of an article.
  • some rendering is ugly (blockquotes for example), but that’s probably not a direct consequence of the org-mode converter
  • there are only a couple of org-mode environments supported;
  • the use of liquid tags that jekyll uses is somewhat cumbersome.

I was pleasantly surprised by the code highlighting though, which worked out of the box for me.

The next step is finding or making some helper functions in emacs lisp to support working with drafts and publishing.

Aug 30
Jun 03

Many people got attracted to bitcoin the last couple of months. This explosion of interest probably caused the monetary value of bitcoins to show the same shape as the google trend-line chart pictured below.

Feb 23

I’m probably not the typical user of social networks. I join them not for social reasons, i.e. interact with friends, but because i’m interested in the phenomena and the techniques involved. Many of my status updates are about those techniques itself and probably not very interesting reading material for my friends, i.e. the ones I normally interact with socially. I bet most of them just ignore my updates. I have at times considered splitting my (online) personality into ’ich geek’ and ’ich normal’ (cfr. Schachnovelle, Stefan Zweig) and have the people I know follow the one or the other, but to date I haven’t found a good way to deal with that.