跳至主要内容

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 Jekyll headers
  • type type type for the blog body
  • M-x org2jekyll-publish
  • git commit and push to github.io

org2jekyll configuration

Instead of using the org2jekyll example configuration, I am using the `org-md-pubish-to-md’ function for blog publish

'(org-publish-project-alist
   (quote
    (("default" :base-directory "~/workspace/blog/" :base-extension "org" :publishing-directory "~/workspace/fktpp.github.io/" :publishing-function org-md-publish-to-md :headline-levels 4 :section-numbers nil :with-toc nil :body-only t)
     ("post" :base-directory "~/workspace/blog/" :base-extension "org" :publishing-directory "~/workspace/fktpp.github.io/_posts" :publishing-function org-md-publish-to-md :headline-levels 4 :section-numbers nil :with-toc nil :body-only t)
     ("images" :base-directory "~/workspace/blog/img" :base-extension "jpg\\|gif\\|png" :publishing-directory "~/workspace/fktpp.github.io/img" :publishing-function org-publish-attachment :recursive t)
     ("js" :base-directory "~/workspace/blog/js" :base-extension "js" :publishing-directory "~/workspace/fktpp.github.io/js" :publishing-function org-publish-attachment :recursive t)
     ("css" :base-directory "~/workspace/blog/css" :base-extension "css\\|el" :publishing-directory "~/workspace/fktpp.github.io/css" :publishing-function org-publish-attachment :recursive t)
     ("web" :components
      ("images" "js" "css")))))

评论

此博客中的热门博文

Use MobaDiff with git difftool

Recently there's an activity in IT that forces the deletion of all unauthorized softwares from all work machines. Unfortunately, kdiff3 is one in the list. As it is generally okay to use vimdiff as an alternative for kdiff3, A gui tool is better suited for desktop workflows. Known that MobaXterm is shipping a gui diff tool named MobaDiff. But it only appears in the windows right click context menu. Find the real application name takes me some time to search in the windows registry. "MobaRTE.exe", which is the one invoked by HKCR\*\shell\MobaDiff. And it was invoked with "-contextdiff" switch to show MobaDiff UI, while when the switch is "-contextedit" it shows MobaTextEditor. Too bad that the "-contextdiff" switch do not support pre-image post-image as other diff tool did, which effectively made it unable to be used as a command line diff utility. Also MobaTech did not mention anything in their document of this Mob...

Emacs 26.2 windows Hunspell setup

 Hunspell failed with default setup With my shining new emacs26.2 setup, I am happy until trying to `M-$’ on a word. I got following error message, it used to be work by just set ispell program to hunspell. Starting new Ispell process hunspell with default dictionary... split-string: Wrong type argument: stringp, nil After some check in my customization setting. nothing found. install a copy of hunspell dictionary At first I think it was caused by no hunspell dictionary. I downloaded en US and en CA hunspell dictionary from wordlist.sf.net project. After put the .aff and .dic files into C:directory I’ve also made a symbolic link from en US ones by running the `mklink’ tool: mklink default.aff en_US.aff mklink default.dic en_US.dic Err… hunspell does not work, still. Time to read code Dig into ispell.el I suprisingly find there’re lots of hunspell specific logic. Originally I was thinking hunspell support involves no elisp work. Acturally ispell did many work to de...

XEmacs 21.5 beta 35 "kohlrabi" has been released.

If you are an old XEmacs user, you may feel happy to see this from https://www.xemacs.org/.    After ten years, XEmacs released a new version 21.5. So there's still many people cares about XEmacs. The XEmacs' source repo have been moved from altassian Bitbucket to https://heptapod.net/. As Bitbucket have been dropped Mercurial support many years ago.