Skip to content

Migrating to Org2Blog

WordPress is a powerful and satisfying writing and publishing platform. After learning Org-Mode, I wanted to use Org-Mode for writing and WordPress for publishing. Org2Blog makes that easy.

WordPress easily exports your posts to XML. Org2Blog-Importers converts them to Org-Mode via Pandoc. Tonight I converted them here. Any future modifications belong in these documents with publishing to WordPress.

I tested both publishing new posts and modifying and re-publishing old posts and both worked correctly.

Additional Org2Blog Configuration

Hello, world.

(+ 1 2 3)

Org2Blog Setup

Content goes here.

(+ 1 2 3)

How to reintegrate changes for Word back into Org-Mode


Original: Your Org source
A: Org -> DOCX for co-authors (using pandoc)
B: Org -> DOCX -> Org (using pandoc).
C: A -> Org (using pandoc and --accept-all-changes)
D: B-Original

The difference between B and Original are pandoc-introduced changes that you do
not want. Ignore/remove these changes from C, call it D and then the difference
between D and the Original are your co-author comments. Now your authors can
edit DOCX with Track Changes and you can work on those edits with Emacs ediff.

Generating autoloads and Compiling Org without make

Here is how to do it.

Search for the heading “Generating autoloads and Compiling Org without make”.

This is very helpful for non-developer Org-Mode users who want to run Org-Mode from source via Git.

Link Roundup


Uniquely Name Source-Blocks and Headline IDs in Org-Mode

Always name all of your Source-Blocks and uniquely ID Headlines in Org-Mode. It is the only way to make Literate Programming pleasant and predictable. At the very least you will understand what is happening during tangling.

Life Is Simple @tgtext


digraph graphviz {
subgraph cluster {
ayh [label="Happy with things?", shape=ellipse];
no [label="No.", shape=Mdiamond];
yes [label="Yes.", shape=Mdiamond];
ayh -> no;
ayh -> yes;
no -> ayh [label="Change them."];
yes -> ayh [label="Keep doing them."];
label="Life is simple:\nAttribution: @tgtext";


Org-Mode Release 8.3

Org 8.3 is now out.

Addendum: 2015-08-16


  • org-show-context-detail
  • Markdown export supports switches in source blocks
  • ASCII export additions
  • Export inline source blocks
  • ascii plot
  • date macro parms
  • mathjax cdn
  • viewport for html mobile
  • remotely edit footnote definition
  • texinfo image support
  • Removed option org-koma-letter-use-title
  • Three slash URI links
  • Footnotes in included files are now local to the file
  • When exporting, throw an error on unresolved id/fuzzy links and code refs

(use-package smartparens-config :ensure smartparens)

If you utilize use-package to install smartparens and require smartparens-config then do it like this:

(use-package smartparens-config :ensure smartparens)

This week I migrated to use-package and configured it incorrectly with something like this:

(use-package smartparens :ensure t :config (require 'smartparens-config))

Big giveaway: single-quote and backtick don’t work correctly in strict mode! There are a lot of explanations of how to “fix this issue”. It isn’t an issue with smartparens. This is how I got it wrong; very easy mistake to make.