This is the 34th iteration on what happened in the last four weeks in the imag project, the text based personal information management suite for the commandline.
Besides that, we had 45 merges since the last blog article. I’m not listing all of them, but only the most important ones:
- 7bbc379b changed “imag” to list the commands alphabetically now.
aliased the “show” subcommand to “list” in the
- 7f4cdced changed all binaries to not print “Ok” on successfull execution.
- d5e0c234 added a license-header-checker script to the CI. Our CI jobs fail now if a file does not have the license at its top.
fixed a severe bug where
imag-initcreated the git repository in the imag runtimepath rather for the imag runtime path.
added a check in
imag-linkso that an entry cannot be linked to itself (or rather: it made the error much clearer).
- 1d46004d refactored the complete error handling.
added a feature whether the imag version is now built from
git describeif compiling in debug mode.
- 97e863f8 fixed a bug where piping imag output to an external tool resulted in broken pipe errors.
libimagentryrefand its usage.
added the “plumbing module”
imag idsand removed the same functionality from
libimagentrylistwhich was basically unused.
libimagdiaryto use the header-type marker functionality (
libimagentryutil::isa::Is) which it did not before.
rewrote the entry parsing in
libimagstoreand fixed a bug in it.
added a “unlink” functionality in
libimagentrylinkfor conveniently removing all links from an entry.
- ef3b60ee updated “uuid” and “task-hookrs” (thanks Dylan-DPC)!
- 7cd3bb05 fixed a severe bug which was introduced by 1521005e.
imagto not instantiate a
Runtimeobject, which is not necessary in this context.
added “daily” support in
refactored all usage of
libimagrtprovides access to IO resources now. That’s the first step towards an easy command-chaining approach where
libimagrtholds all resources for interactive functionality and IO resources.
What will happen
I’m currently working more on the “command chaining” thing than on the
I hope I can get
imag-wiki ready before April, but I
cannot promise anything.
I’m also thinking a lot about how to simplify contributions. Writing new modules for imag is not hard, but it is too hard for a person not knowing the imag code infrastructure and all the nice abstractions and tools we have around.