跳至主要内容

博文

目前显示的是标签为“good old days”的博文

org2jeklly is changing... excerpt: Some change breaks my current workflow, and the workaround

publish failure in org2jeklly 0.25 Some time ago, I started using org2jeklly to publish my blogs. All went well until someday I did a package upgrade for all my emacs packages… My publishing start to fail, there's no markdown file produced after I run `M-x org2jeklly-publish`… There's `org-export-process exited abnorml` message in Message buffer. org-export-process exited abnormally issue Several hours of debug show that the "org-export-process" related issue was caused by there's no correct org asynchronous export setting. To fix it, add the following snippet to .emacs: (custom-set-variables '(org-export-async-init-file "~/.emacs.d/org-async-init.el" )) And create a "~/.emacs.d/org-async-init.el" with following contents: ( require ' package ) ( setq package-enable-at-startup nil) (package-initialize) ( require ' org ) ( require ' ox ) ( setq org-export-async-debug t) no markdown genera...

using org2jekyll for blog publishing

switch to org2jekyll package from homegrown solution For some time, I was using the `autoinsert’ function to prepare Jekyll post. I have the following auto-insert define in my .emacs, so whenever I create a new markdown file in Jekyll ` post ` directory it prompts me for the Jekyll header. (define-auto-insert '("\\.markdown" . "Jekyll Markdown Post") '("TITLE: " "---\nlayout: post\ntitle: " str "\ndate: " (format-time-string "%Y-%m-%d %H:%m:%S %z") "\ncategories: " ("CATEGORY: " str " ") -1 "\n---\n" _ "\n") t) It turns out the procedure is too error prone. I got into various error (filename convention, markdown syntax, etc.) many times when trying to publish my post. Today I have the org2jekyll setted up, all steps need to publish a jekyll post is now simplified to: M-x org2jekyll-create-draft Anwser the questions as usual for Jekyl...