Add post: Whats coming up in imag (35)

1 files changed, 94 insertions, 0 deletions

diff --git a/content/blog/2018-04-09-what-s-coming-up-in-imag-35.md b/content/blog/2018-04-09-what-s-coming-up-in-imag-35.md
new file mode 100644
index 0000000..342f649
--- /dev/null
+++ b/content/blog/2018-04-09-what-s-coming-up-in-imag-35.md
@@ -0,0 +1,94 @@
+---
+title: "What's coming up in imag (35)"
+date: "2018-04-08T11:59:40"
+tags: [ "linux", " open source", " programming", " rust", " software", " tools", " imag" ]
+---
+
+This is the
+35th
+iteration on what happened in the last four weeks in the
+[imag project, the text based personal information management suite for the commandline](http://imag-pim.org).
+
+<!-- more -->
+
+# What happenend?
+
+<!--
+git log a0b989ef..master --oneline --merges --format="* [%h](http://git.imag-pim.org/imag/commit/?id=%H) %s" | tac
+-->
+
+In the last few weeks, we had great progress. Here are the most important
+changes:
+
+* [d3b38b5a](http://git.imag-pim.org/imag/commit/?id=d3b38b5a90792d87037ec48382312c9e6c4bf6dd)
+  introduced "pipe magic" - this prepares `libimagrt`
+  to be able to pipe the imag store from one imag command (or external
+  command) to the next one.
+* [b374f21d](http://git.imag-pim.org/imag/commit/?id=b374f21d7cecd786948092ae89f0f50113d1b422)
+  changed `imag-contact` to list emails comma seperated.
+* [6ec50970](http://git.imag-pim.org/imag/commit/?id=6ec509709dc1d8af444ffbb537a8e5f260e31977)
+  added the `find` command to `imag-contact`.
+* [5609651f](http://git.imag-pim.org/imag/commit/?id=5609651f118389a4904224efce74252c909e139f)
+  added functionality so that `imag-contact` can output the contact data in
+  JSON. This is helpful when invoking `imag-contact` from an external program
+  (like mutt) and reading the output into that program.
+* [dfb706b3](http://git.imag-pim.org/imag/commit/?id=dfb706b3c1727e62fa538f64ad7c6ca7fcd4f43f)
+  changed `imag-edit` to be able to receive store ids on stdin.
+  This makes `imag ids | fzf | imag edit -I` possible.
+* [ee72e61b](http://git.imag-pim.org/imag/commit/?id=ee72e61b444d5c75967447d18f7cb8108fc12fb7)
+  rewrote the CLI of `imag-tag`.
+* [c5154e83](http://git.imag-pim.org/imag/commit/?id=c5154e8363373d6f0f347097cee9cf47cf88fa45)
+  changed `libimagrt` so that the `rt.editor` setting was considered for
+  building the editor command.
+* [1d3994d1](http://git.imag-pim.org/imag/commit/?id=1d3994d1086587e12c697839642df55f9ad178e3)
+  changed `imag ids` to not print the full filepath by default.
+* [cc9c746c](http://git.imag-pim.org/imag/commit/?id=cc9c746cb423ed082be1552f4384a7556640c5ee)
+  removed a great deal of outdated documentation.
+* [58f50ac2](http://git.imag-pim.org/imag/commit/?id=58f50ac2f908635d8738026ac2777d185470fb4e)
+  changed `imag-habit` so that already done habits can be shown.
+* [c39a1f82](http://git.imag-pim.org/imag/commit/?id=c39a1f82e26be1b6f414e634d451ea2a490e5e4d)
+  changed `libimagstore::store::Store::create()` so that it fails if the entry
+  already exists. This was not done before (which was a bug) so that `create`
+  was the same as `retrieve`.
+* [fd91662e](http://git.imag-pim.org/imag/commit/?id=fd91662ed9fb9e087cc063f8f2d0ff1bd105b912)
+  fixed `imag-init` to create the store directory as well.
+* [96b6beff](http://git.imag-pim.org/imag/commit/?id=96b6beff5d721a65385f9e9242fe083043f5965c)
+  added header edit support in `imag-edit` and `libimagentryedit`.
+* [7907ed96](http://git.imag-pim.org/imag/commit/?id=7907ed96c72d8fe52b9e6bf281ddaeccf0f6d70e)
+  changed `imag-link` so that it uses an ascii table for output by default.
+* [ec2f87af](http://git.imag-pim.org/imag/commit/?id=ec2f87afaded5f05ba57e450df626eb8b6541765)
+  fixed `libimagrt` to pass `/dev/tty` to the editor command, so that vim does
+  not trash the terminal.
+* [8492f149](http://git.imag-pim.org/imag/commit/?id=8492f149be4f452b015f0681b1ece50781878057)
+  added a feature in `libimagrt` to handle unknown subcommands. With this, a
+  user is able to write an executable `imag-store-dosomething` which gets
+  automatically invoked by `imag-store` if the `dosomething` subcommand does
+  not exists.
+* [1d5171d7](http://git.imag-pim.org/imag/commit/?id=1d5171d77018b6e07a880db6826b5ccd690ed6f9)
+  added support for viewing multiple entries with one invocation of the
+  command in `imag-view`.
+* [a14ab7b6](http://git.imag-pim.org/imag/commit/?id=a14ab7b6354e3916ac15f1e3b63d2b540db5d7d8)
+  added support in `imag-contact find` for printing the store id / file path
+  instead of showing the contact.
+* [2f47bece](http://git.imag-pim.org/imag/commit/?id=2f47becef4aec3cf4d06d2531b94536f8f1e81b0)
+  added support for reading the store ids for the entries to view from stdin
+  in `imag-view`.
+
+# What will happen
+
+I had a glance at the changelog file in the repository before writing this
+post and I found, that the changelog is _huge_ already.
+Because of that I will release imag 0.7.0 early, and without the "wiki",
+"calendar" and "flashcard" module I initially planned for this release.
+
+I think I won't be able to get imag-calendar ready until May (my
+[journey](https://beyermatthias.de/traveling/north-america/) starts in May and
+I won't be able to work on imag very much from May until early 2019, sadly).
+Thus, I rather release 0.7.0 early and without imag-calendar rather than not
+at all.
+
+Maybe I get imag-wiki ready until May, which would be really cool and result
+in imag 0.8.0, but I'm not sure I will make it.
+
+So... be prepared for the next imag release in the next few days!
+