#imag #information #personal #management #pim

bin+lib imag-log

Part of the imag core distribution: imag-log command

13 releases

Uses old Rust 2015

0.10.1 Feb 29, 2020
0.10.0 Dec 24, 2019
0.9.3 May 23, 2019
0.9.1 Feb 17, 2019
0.6.4 Mar 25, 2018

#52 in #imag


Used in imag

LGPL-2.1

245KB
4.5K SLoC

imag - imag-pim.org

imag is a commandline personal information management suite.

This application is in early development. There are some things that work, but we do not consider anything stable or usable at this moment. Feel free to play around anyways.

Mission statement

Our (long-term) goal is to

Create a fast, scriptable, commandline first, plain-text-only suite of tools to cover all aspects of personal information management.

Yes, imag is a rather ambitious project as it tries to reimplement functionality for several "personal information management aspects". We try to use standards like vcard, icalendar and others wherever possible.

Have a look at the documentation for some more words on this.

Building/Running

Here is how to try imag out.

imag is a suite/collection of tools (like git, for example) and you can build each "module" individually.

Building

Building all crates works with cargo build --all, building individual crates by specifying the --manifest-path flag to cargo. The crates in ./bin are the actual commandline tools, ./bin/core contains a core set of imag commands ("plumbing" in git-speak) and ./bin/domain contains domain-specific imag commands, for example a todo tool or a bookmark tool.

Running

After you build the module you want to play with, you can simply call the binary itself with the --help flag, to get some help what the module is capable of.

If you installed the module, you can either call imag-<modulename> (if the install-directory is in your $PATH), or install the imag binary to call imag <modulename> (also if everything is in your $PATH). Call imag --help to see which modules are found and can be used. Call imag --versions to print the versions of all modules.

Example usage

As imag is a big and complex project, we cannot show all tools of the suite here. But to give you some idea, here's an example:

# Lets initialize imag
imag init

# Recursively import vcf files
imag contact import /home/user/contacts

# Create a contact (vcf) in the private collection
imag contact create --file /home/user/contacts/private

# Add a diary entry
imag diary -p private create

# Uh, I forgot something in a diary entry, select one (or multiple) and edit it
# use the `fzf` tool here (not a part of imag) to select from the IDs
imag diary -p private list | fzf -m | imag edit

# Link a contact to the diary entry
imag link diary/private/2018/01/01/00:00:00 contact/bc222298-casf-40a4-bda1-50aa980a68c9

# Annotate a contact with some notes
imag annotate add contact/bc222298-casf-40a4-bda1-50aa980a68c9 contact-notes

# Write down some notes named "pineapple"
imag notes create "pineapple"

# Where was that contact again?
imag grep Eva # also possible with `imag contact find Eva`

# Okay, we need to add some imag-internal notes to that contact
imag grep Eva -l | imag edit

# Now save our work
imag git add . # "imag-git" simply calls git in the imag store
imag git commit -m 'Commit message'

Staying up-to-date

We have a official website for imag, where I post release notes and monthly(ish) updates what's happening in the source tree (RSS here).

We also have a mailinglist where I post updates and where discussion and questions are encouraged.

Documentation

We have some documentation in the ./doc subtree which can be compiled to PDF or a website using pandoc. It might not be up to date, though. Developer documentation for the last release is available on docs.rs.

Please contribute!

We are looking for contributors! Feel free to open issues (by writing to the mailinglist) for asking questions, suggesting features or other things!

Also have a look at the CONTRIBUTING.md file!

Contact

Feel free to join our new IRC channel at freenode: #imag or our mailinglist.

License

We chose to distribute this software under terms of GNU LGPLv2.1.

Dependencies

~15–29MB
~466K SLoC