You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Manos Pitsidianakis 0ebad39b50
Bumb version to 0.5.1
7 months ago
benches melib: remove BackendOpGenerator 1 year ago
debian Bumb version to 0.5.1 7 months ago
melib melib/jmap: fix macro path 7 months ago
scripts Add pre-push git hook 9 months ago
src meli: add invalid flag combo check 7 months ago
testing Remove text_processing 7 months ago
tests Remove ui crate 7 months ago
.gdbinit small fixes 10 months ago
.gitignore Plugins WIP #2 8 months ago
COPYING mailbox: add threads 1 year ago
Cargo.lock Bumb version to 0.5.1 7 months ago
Cargo.toml Bumb version to 0.5.1 7 months ago
Makefile Makefile: don't emit timestamps with gzip 7 months ago Convert README to Markdown 7 months ago use `man` binary if mandoc missing in cli-docs 7 months ago
meli-themes.5 meli-themes.5: split tables into pages 7 months ago
meli.1 Correct mdoc lint warnings 7 months ago
meli.conf.5 ui/conf: replace include macro with m4 include macro 7 months ago
rustfmt.toml Run rustfmt 1 year ago
sample-config ui/conf: replace include macro with m4 include macro 7 months ago


For a quick start, build and install locally:

 PREFIX=~/.local make install

Available subcommands:

  • meli (builds meli with optimizations in $CARGO_TARGET_DIR)
  • install (installs binary in $BINDIR and documentation to $MANDIR)
  • uninstall Secondary subcommands:
  • clean (cleans build artifacts)
  • check-deps (checks dependencies)
  • install-bin (installs binary to $BINDIR)
  • install-doc (installs manpages to $MANDIR)
  • help (prints this information)
  • dist (creates release tarball named meli-VERSION.tar.gz in this directory)
  • deb-dist (builds debian package in the parent directory)
  • distclean (cleans distribution build artifacts)

The Makefile should be portable and not require a specific make version.


After installing meli, see meli(1) and meli.conf(5) for documentation.


meli requires rust 1.39 and rust’s package manager, Cargo. Information on how to get it on your system can be found here:

With Cargo available, the project can be built with

make meli

The resulting binary will then be found under target/release/meli


make install

to install the binary and man pages. This requires root, so I suggest you override the default paths and install it in your $HOME:

make PREFIX=$HOME/.local install

See meli(1) and meli.conf(5) for documentation.

You can build and run meli with one command:

cargo run --release

While the project is in early development, meli will only be developed for the linux kernel and respected linux distributions. Support for more UNIX-like OSes is on the roadmap.

Building in Debian

Building with Debian’s packaged cargo might require the installation of these two packages: librust-openssl-sys-dev librust-libdbus-sys-dev

A *.deb package can be built with make deb-dist

Building with notmuch

To use the optional notmuch backend feature, you must have libnotmuch installed in your system. In Debian-like systems, install the libnotmuch5 libnotmuch-dev packages.

To build with notmuch support, prepend the environment variable MELI_FEATURES='notmuch' to your make invocation:

MELI_FEATURES="notmuch" make

or if building directly with cargo, use the flag `--features="notmuch”'.

Building with JMAP

To build with JMAP support, prepend the environment variable MELI_FEATURES='jmap' to your make invocation:

MELI_FEATURES="jmap" make

or if building directly with cargo, use the flag `--features="jmap”'.


Development builds can be built and/or run with

cargo build
cargo run

There is a debug/tracing log feature that can be enabled by using the flag --feature debug-tracing after uncommenting the features in Cargo.toml. The logs are printed in stderr, thus you can run meli with a redirection (i.e 2> log)

Code style follows the default rustfmt profile.


meli by default looks for a configuration file in this location: $XDG_CONFIG_HOME/meli/config.toml

You can run meli with arbitrary configuration files by setting the $MELI_CONFIG environment variable to their locations, ie:

MELI_CONFIG=./test_config cargo run


How to run specific tests:

cargo test -p {melib, meli} (-- --nocapture) (--test test_name)


perf record -g target/debug/bin
perf script | stackcollapse-perf | rust-unmangle | flamegraph > perf.svg