Sponsor:

Your company here ā€” click to reach over 10,000 unique daily visitors

mu-remove - Man Page

command to remove messages from the database.

Synopsis

mu [common-options] remove [options] <file> [<files>]

Description

mu remove removes specific messages from the database, each of them specified by their filename. The files do not have to exist in the file system.

Remove Options

--muhome

use a non-default directory to store and read the database, write the logs, etc. By default, mu uses the XDG Base Directory Specification (e.g. on GNU/Linux this defaults to ~/.cache/mu and ~/.config/mu). Earlier versions of mu defaulted to ~/.mu, which now requires --muhome=~/.mu.

The environment variable MUHOME can be used as an alternative to --muhome. The latter has precedence.

Common Options

-d, --debug

makes mu generate extra debug information, useful for debugging the program itself. By default, debug information goes to the log file, ~/.cache/mu/mu.log. It can safely be deleted when mu is not running. When running with --debug option, the log file can grow rather quickly. See the note on logging below.

-q, --quiet

causes mu not to output informational messages and progress information to standard output, but only to the log file. Error messages will still be sent to standard error. Note that mu index is much faster with --quiet, so it is recommended you use this option when using mu from scripts etc.

--log-stderr

causes mu to not output log messages to standard error, in addition to sending them to the log file.

--nocolor

do not use ANSI colors. The environment variable NO_COLOR can be used as an alternative to --nocolor.

-V, --version

prints mu version and copyright information.

-h, --help

lists the various command line options.

Reporting Bugs

Please report bugs at https://github.com/djcb/mu/issues.

Author

Dirk-Jan C. Binnema <djcb@djcbsoftware.nl>

See Also

mu(1), mu-index(1), mu-add(1)

Referenced By

mu(1), mu-add(1).