||2 years ago|
|.github||2 years ago|
|bin||2 years ago|
|doc||2 years ago|
|etc||3 years ago|
|lib||2 years ago|
|scripts||2 years ago|
|tests||2 years ago|
|.editorconfig||4 years ago|
|.gitignore||3 years ago|
|.travis.yml||2 years ago|
|CHANGELOG.md||4 years ago|
|CONTRIBUTING.md||4 years ago|
|Cargo.toml||2 years ago|
|LICENSE||6 years ago|
|README.md||2 years ago|
|default.nix||2 years ago|
|imagrc.toml||2 years ago|
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.
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.
Here is how to try
imag is a suite/collection of tools (like git, for example) and you can
build each "module" individually.
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.
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
imag --help to see which modules are found and can be used.
imag --versions to print the versions of all modules.
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'
We also have a mailinglist where I post updates and where discussion and questions are encouraged.
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.
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!
Feel free to join our new IRC channel at freenode: #imag or our mailinglist.
We chose to distribute this software under terms of GNU LGPLv2.1.