42bc5a19ad
New stable release 1.12.13. This contains improvements to the build process, the
Guile/Scheme binding ("SCM") and a new experimental "labels" sub-command. Let's
start with that last one.
* Labels
There's a new, experimental feature: *labels*. Labels are similar to the
existing "tags", but better integrated with both mu and mu4e,
You can search for message with a given label using 'label:', e.g
$ mu find label:tupperware
Or add/remove labels, e.g., remove the label "planet" and add the label
"dwarf-planet" to all messages that have "pluto" in their subject:
$ mu labels update "subject:pluto" --labels -planet,+dwarf-planet
Clear all labels from messages with the label "boring":
$ mu labels clear "label:boring"
Labels are only stored in mu's database, and do not write to the message file
themselves. I.e., when you remove your database, your labels are gone. However,
you can use the `mu labels export` and `mu labels import` to save/restore them;
see the mu-labels(1) man-page for details.
In mu4e, you can do the same using `mu4e-headers-mark-for-label` (bound to `l`)
and clearing with `mu4e-headers-mark-for-unlabel` (bound to 'L').
I.e., mark some messages (or the current one by default), and in the
headers-buffer type
l -planet +dwarf-planet RET
This works similar to the other marks.
There's autocompletion as well, both for search (label:) and marking (after +/-)
It's experimental, but it seems quite useful so far. See the man-page for
further details.
* SCM
The SCM/Guile bindings have been improved substantially; some common operations
are much faster (algorithmically). Also, the "glue" was added to interact with
Emacs and the "geiser" package, either with or without mu4e.
For the "plain Emacs" integraticon, see the Mu-SCM documentation, section
`Hooking up with GNU/Emacs and Geiser'.
For the mu4e integration, see the chapter `Using mu's SCM/Guile integration' in
the mu4e reference manual; or check the `mu4e-mu-scm-server' configuration
variable and the `mu4e-mu-scm-repl' command.
Future version will add more, and start answering questions like "Why would I
even want SCM bindings?!" :-)
* Building
- by default, tests are built 'lazily', i.e., only when running tests;
this speeds up the build considerably for people that don't want to run
tests (there's also -Btest=disabled of course)
- when available/found, mu now (by default) uses the system versions of CLI11
and libfmt, rather than mu's "vendored" versions.
You can influence where the build system (i.e., meson) looks through the
`PKG_CONFIG_PATH` environment variable (see the pkg-config/pkgconf man-pages),
and you can disable
#+TITLE:mu
Welcome to mu!
Latest development news: NEWS.org.
With the enormous amounts of e-mail many people gather and the importance of e-mail message in our work-flows, it's essential to quickly deal with all that mail - in particular, to instantly find that one important e-mail you need right now, and quickly file away message for later use.
mu is a set of command-line tools for dealing with e-mail messages stored in the
Maildir-format. mu's goal is to help you to quickly find the messages you need,
view them, extract attachments, create new maildirs, and so on.
After indexing your messages into a Xapian-database, you can search them through a query language. You can use various message fields or words in the body text to find the right messages.
Built on top of mu are some extensions (included in this package):
mu4e: a full-featured e-mail client that runs inside emacsmu-scm: bindings for the Guile/Scheme programming language (version 3.0 and later)
mu is written in C++; mu4e is written in elisp and mu-scm is written in a mix of
C++ and Scheme.
mu is available in many Linux distributions (e.g. Debian/Ubuntu and Fedora)
under the name maildir-utils; apparently because they don't like short names.
All of the code is distributed under the terms of the GNU General Public License
version 3 (or higher).
Versions
mu attempts to balance development speed and stability. For this, every few
months there is a stable version (e.g. 1.12.12); development then continues in
in master, with -dev<n> (e.g. 1.12.13-dev2): -dev-suffixed versions refer to the
current development code, until it is released (and then looses its -dev suffix,
i.e., becomes the 1.12.13 release).
So if you want stability, grab the release; if you are more
adventurous/impatient, git master is there as well.
Installation
Note: building from source is an advanced subject, especially if something goes wrong. The below simple examples are a start, but all tools involved have many options; there are differences between systems, versions etc. So if this is all a bit daunting we recommend to wait for someone else to build it for you, such as a Linux distribution. Many have packages available.
Requirements
To be able to build mu, ensure you have:
- a C++17 compiler (
gccandclangare known to work) - development packages for Xapian and GMime and GLib (see
meson.buildfor the versions) - basic tools such as
make,sed,grep meson
For mu4e, you also need emacs.
Note, support for Windows is very much experimental, that is, it works for some people, but we can't really support it due to lack of the specific expertise. Help is welcome!
Building
$ git clone https://github.com/djcb/mu.git $ cd mu
mu uses meson for building, so you can use that directly, and all the usual
commands apply. You can also use it indirectly through the provided Makefile,
which provides a number of useful targets.
For instance, using the Makefile, you could install mu using:
$ ./autogen.sh && make $ sudo make install
You can of course also run meson directly (see the meson documentation for more
details):
$ meson setup build $ meson compile -C build $ meson install -C build
Contributing
Contributions are welcome! See the Github issue list and IDEAS.org.