This is the story of how I moved from Vim to Emacs and then back again. It’s a story of modes, plugins, stock configs, mobile devices and eBooks. Why switch to Emacs? My initial interest for Emacs was triggered by a blog post about org-mode. Org mode looked like the plain text productivity solution I had been looking for for a long time. Apart from everything being plain text based, the functionality offered covered most of my bases.
Manually sending emails on ticket updates and keeping git mirrors of the code for FDroid building and on Github was starting to take too much of my time. As a result I have decided to move the issues to Redmine and use git instead of fossil. Even though I love the one file approach of fossil, git just integrates better with tools like Redmine. Visit the source and tracker here.
The latest version of Simpletask adds a new feature that was pending for quite some time. It’s now finally possible to archive only selected tasks. This way you can archive your tasks in stages. The new archive menu is available in the overflow menu when you have selected one or more tasks. Additionally you can edit more than one task at a time by selecting multiple tasks and clicking the pen icon.
The site has been moved to Pelican for several reasons, but the most important one is that I can now keep my blog postings in the open and future proof reStructuredText format instead of having it all hidden in a database. I initially moved to octopress, but after a single day of use, the lack of documentation was already annoying. In contrast, Pelican seems to have excellent documentation. I have also decided to move towards reStructuredText (reST) because: In contrast to Markdown, it has a proper standard.
After doing a bit more reading on the subject, it turns out that not only Sublime Text (ST) is closed, it is also very expensive and might disappear any time. I am not willing to build my workflow around tools like that. A sentiment Astrid user should appreciate. However I do think Sublime text has some very nice features. Below I will discuss several ways to transfer these items to vim.
I was reading the site http://plaintext-productivity.net/ and saw some very good feedback on the Sublime Text editor. Curious to try it out. I downloaded it and tried the following steps: Project->Add Folder to Project->My Documents And then Ctrl-P just worked. If you consider the time it took me to make this work in VIM, I think I am sold.
Note to self Focus on the process not on the tools!! Process Ubiquitous capture Open formats I do not want my stuff ending up in some closed database or format which is not easily transferable to something else. This means that for instance Evernote is not the best match. Instead I use plain text files as much as possible. Todo file: todo.txt plain text format Minutes and documents: Markdown syntax For the actual next action list, the plain text open format requirement is less stringent.
When developing for Android, using the provided emulators can be an exercise in frustration. The emulator startup time is quite long and the applications run very slowly. Fortunately there is now a way to run the emulator with decent performance on x86 hardware. The steps to configure this are explained at https://www.virag.si/2012/10/speeding-up-android-emulator/. See section 2 to make your emulator rip. Finally I can do testing on an emulator instead of on my personal phone.
To build fossil for Android, the easiest way is to use the Android NDK. The changes needed to build fossil on a Linux machine can be found at http://mpcjanssen.nl/fossil/fossil/timeline?r=build-android After running the build.sh script, the Android fossil binary can be found in the obj subdirectory. This fossil binary works on Android and even allows you to host fossil repos from your Android device. A prebuilt binary can be downloaded from
Fossil will now be used to do source code management for Simpletask. The repository is at http://mpcjanssen.nl/fossil/simpletask