So it all begins

After several hours work, I’ve got my muse+pyblosxom setuped. So now it’s my start of my blog.
The first thing I’ll need to do is to go through my planner pages and get the notes somewhat like a blog into this blog system.
I’ll write most of my blog in English, as a practice and more “world […]

export notes to pyblosxom

well I decide to give this up.
The main reason is that muse-blosxom-new-entry makes the file name from blog title. I think it’s a good idea. But that make me harder, if possible, to keep the planner notes sync with blog entries.
What’s more, I might use different sub-set of muse features on planner and blog. Like […]

OK, I’ll go with the official hardcodedates.py

And this will save some confusing about versions. I can give time 00:00 for notes without a note taken timestamp. Anyway this is what Michael give for blog files with only date in the timestamps file.

Share This

I can use unison to sync the comments

unison can sync two directories, which are changing on both side. It updates that do not conflict are propagated automatically. Conflicting updates are detected and displayed.
This is perfet for the comments back and force of planner-pyblosxom: people can comment on the blog via web interface, and I can reply comments within Emacs, even off-line. And […]

new idea: planner-pyblosxom

After playing with muse-blosxom.el, (emacs-wiki-)blosxom.el, remember-blosxom.el and pyblosxom, I found it’s pretty wired that I’m writting everything in my planner page, while I’d have to write something again for my blog. Also that means I’d have to keep a seperate set of data, and it’s not an easy work to keep them synced.
The ideal thing […]

Close
E-mail It