跳至主要内容

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...

Winget: From Quirky Underdog to Stable Champion

Remember winget, the Windows Package Manager that started as a playful experiment? Well, prepare to be surprised – it's grown into a powerful and highly stable tool for managing your software, including in environments with network restrictions . Gone are the days of unreliable installs and limited functionality. The developers have diligently transformed winget into a reliable contender in the package manager arena. Updates arrive regularly, bringing stability, enhanced features, and wider app support . Here's why you should give winget another look: Unified experience: Manage all your apps from a single command line , ditching the scattered hunt for individual installers and downloads. Security focus: Winget verifies package integrity and signatures, ensuring you get authentic and secure software . Efficiency: Say goodbye to manual downloads and updates. Winget automates the process, saving you time and effort. Customization: Configure installation options and choose s...

Eglot and before/after-save-hook and use-package

In Emacs, when you try to automate some actions during every save action, you will surely get to the before-save-hook and the after-save-hook. Simply adding something like gofmt-before-save to before-save-hook will save you tons of time to do the go-fmt. And then, I meet eglot, and gopls will also save me tons of time doing googling and api documentation navigation. But eglot-ensure is not very friendly to the good old ways of how after-save-hooks were designed to work. It makes the before/after-save-hook a buffer local variable and it does not inherit the variable's global value. So, to make before/after-save-hook work again, experts start to adding hooks to major mode specific hooks like this: emacs.md - Go (opensource.google) """ ;; Optional: install eglot-format-buffer as a save hook. ;; The depth of -10 places this before eglot's willSave notification, ;; so that that notification reports the actual contents that will be saved. (defu...