It’s been a long time, Octopress is slow and painful to setup, after the death of my silly hard drive, I’m too lazy so I give up setting a Octopress environment, even writing new posts.

Eventually, I’m levaing, heading for Hexo.

What’s Hexo?

Hexo is a fast, simple and powerful blog framework. It parses your posts with Markdown or other render engine and generates static files with the beautiful theme. All of these just take seconds.

Why?

• Painless installing
• Cleaner documentation
• Simple configuration
• Fast generating, deploying
• Easy customization
• Actively maintained

\begin{align} \theta = \arccos({ \frac {1} {\sqrt{ \tan^2{\alpha} + \tan^2{\beta} + 1 }} }) \end{align}

Prologue

With the release of OmniMarkupPreviewer v1.6, you can embed $\LaTeX$ and MathML equations directly into your Markdown documents. Equations are handled with the excellent MathJax library.

For a long time, I didn’t know a way to do directory comparison using git difftool command, extdiff extension from Mercurial did perform much more superior than Git.

Though it may be a bit out of date, I just found that after v1.7.11, Git now supports directory comparison through --dir-diff option, fantastic!

UPDATE 12/11/2012: You will need v1.8.0 version of msysgit installed, as noted by Scooter Software (Reference).

So here is a list of steps for me to make Beyond Compare 3 and Git directory comparison work under Windows.

First of all, Execute following commands in the Git Bash shell (or just modify your .gitconfig directly). You may need to change the folder where BCompare.exe resides.

NOTE: Instead of bcomp.exe, use BCompare.exe, because I’ve found bcomp.exe returns too early, which will cause errors like this:

Then make an alias for difftool:

Now, you can use git dt to open Beyond Compare 3 for directory comparison in git repositories.

It’s weird, while importing some .pyd modules, like pyexpat, unicodedata in Windows version of Sublime Text 2, you will get ImportError, for example:

Will result in:

However, since standard pyd modules are not missing, reside correctly in the same folder as sublime_text.exe, we can add that folder to sys.path in order to allow embedded python interpreter to load these modules:

After that, you can import these standard python modules without pain, I hope it’s useful for Sublime Text 2 packages developers who met the same problem before.