5 ms·
Nice, using similar workflow for my blog, emacs export + some post-processing [0]. Even with high quality parsing libraries, when you dip into the most advance
by karlicoss 6y ago
Nice, using similar workflow for my blog, emacs export + some post-processing [0].
Even with high quality parsing libraries, when you dip into the most advanced features of org-mode (like literate programming via babel), you end up needing emacs anyway. And it's much more pleasant to tweak existing export code, than figuring out how to reimplement it from scratch.
[0] https://github.com/karlicoss/beepb00p/blob/master/src/compile_org.py https://github.com/karlicoss/beepb00p/blob/master/src/compil...
- dpbriggs 6y agoI checked out your articles and I like your writing style! I thought about doing batch export but ended up being too lazy to integrate it in my release flow. My compromise is to use this snippet: (defun make-blogging-mode () (interactive) (toggle-word-wrap) (toggle-truncate-lines) (flycheck-mode) (flycheck-vale-toggle-enabled) (add-hook 'after-save-hook 'org-mode-export-hook) ) And this find-file hook in my blog template: # -*- find-file-hook: make-blogging-mode -*- My new computer is beefy enough that I barely notice the export on save. I wouldn't recommend this on slower boxes as it freezes emacs for a bit.