This is the 30th iteration on what happened in the last four weeks in the imag project, the text based personal information management suite for the commandline.
imag is a personal information management suite for the commandline. Its target audience are commandline- and power-users. It does not reimplement personal information management (PIM) aspects, but re-uses existing tools and standards to be an addition to an existing workflow, so one does not have to learn a new tool before beeing productive again. Some simple PIM aspects are implemented as imag modules, though. It gives the user the power to connect data from different existing tools and add meta-information to these connections, so one can do data-mining on PIM data.
Because we had 25 merges (as of 23820e322e) since the last blog post, here only the most relevant ones.
imag-viewgot positional args, finally.
- 75a8041c0e made the runtime able to write to a logging file
- 0a3f7d9e49 updated some dependencies.
Resolved a conflict in the architecture where
libimagentryannotationwas build upon
libimagnotes, which is problematic.
fixed an error in the
Store::entries()function which returned directories as
was the initial PR for
added partial hash support in
- 212ff3945e added some documentation
- e7aa5af9be removed CLI options to override logging formats. This can be done via the canonical config-override functionality.
refactored config stuff in the
fixed another flaw in the architecture where the
imag-storewas implemented in
- 23820e322e added a functionality where the runtimepath of imag can be specified via an environment variable.
imag-contactwith basic contact management functionality.
What will happen
Well, not much anymore before the 0.5.0 release.
Right now there are only a few things open
in the milestone.
imag-habit will be a thing in 0.5.0 - that’s the last big step before we
release the next version of imag.
I always thought we would get
imag-calendar in there as well, though we did
not include it in the milestone and I will not include it anymore, as the
milestone is already “frozen” right now.
After that, I will tackle the 0.6.0 milestone of course, which will be another
big step forward - though there is not much planned by now, only some changes
If we continue developing at the current speed, imag 0.5.0 will happen before Christmas and 0.6.0 should then be alive around February. But because I have my lessons learned: I cannot guarantee that, of course!