MU-ADD(1)

πŸ’– NAME πŸ’–

okay so mu-add β€” it adds one or more messages to the database. that's it, that's the whole vibe ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

mu [COMMON-OPTIONS] add [OPTIONS] FILE...

🌸 DESCRIPTION 🌸

so mu add is literally the command for adding specific message files to your database, bestie. but heads up β€” every single file has to be specified with an absolute path. no relative paths, no shortcuts, no "but it's right there in my cwd" energy. absolute. path. periodt πŸ’…


πŸŽ€ ADD OPTIONS πŸŽ€

  • --muhome β€” use a non-default directory to store and read the database, write the logs, whatever else needs a home. by default mu follows the XDG Base Directory Specification (so like, on GNU/Linux it defaults to ~/.cache/mu and ~/.config/mu). earlier versions of mu defaulted to ~/.mu, which now means you gotta say --muhome=~/.mu if that's still your thing πŸ™ˆ

the environment variable MUHOME can be used as an alternative to --muhome. and the latter has precedence β€” so --muhome wins the vibe check if they ever disagree πŸ‘‘


✨ COMMON OPTIONS ✨

  • -d, --debug β€” makes mu generate extra debug information, which is useful for debugging the program itself. where does it go? to the standard logging location; peep mu(1) for that 🫢
  • -q, --quiet β€” causes mu to not output informational messages and progress information to standard output, but only to the log file. error messages will still be sent to standard error, so don't worry, you won't be totally ghosted. also note that mu index is much faster with --quiet, so it's recommended you use this option when using mu from scripts etc. scripts girlies rise up πŸ”₯
  • --log-stderr β€” causes mu to not output log messages to standard error, in addition to sending them to the standard logging location. yes, that's the actual wording, read it twice, it's giving double negative πŸ’€
  • --nocolor β€” do not use ANSI colors. the environment variable NO_COLOR can be used as an alternative to --nocolor. monochrome era, we respect it 🌈
  • -V, --version β€” prints mu version and copyright information. the receipts, basically.
  • -h, --help β€” lists the various command line options. your bestie when you forget everything.

πŸ‘‘ EXIT CODE πŸ‘‘

this command returns 0 upon successful completion, or a non-zero exit code otherwise. here's the whole roster, no gatekeeping:

  1. 0 β€” success πŸŽ‰
  2. 2 β€” no matches found. try a different query 😭
  3. 11 β€” database schema mismatch. you need to re-initialize mu, see mu-init(1) πŸ’€
  4. 19 β€” failed to acquire lock. some other program has exclusive access to the mu database πŸ™ˆ
  5. 99 β€” caught an exception ⚠️

πŸ’œ REPORTING BUGS πŸ’œ

please report bugs at https://github.com/djcb/mu/issues. we love a bug report, fr fr πŸ›


🌟 AUTHOR 🌟

Dirk-Jan C. Binnema <djcb@djcbsoftware.nl> β€” king behavior, no cap πŸ‘‘


this manpage is part of mu 1.14.2.

Copyright Β© 2008-2026 Dirk-Jan C. Binnema. License GPLv3+: GNU GPL version 3 or later https://gnu.org/licenses/gpl.html. this is free software: you are free to change and redistribute it. there is NO WARRANTY, to the extent permitted by law.


🌈 SEE ALSO 🌈

mu(1), mu-index(1), mu-remove(1)


and that's the whole page babes 🫢 this one's MU ADD(1) from the General Commands Manual, serving mu 1.14.2 realness β€” go forth and add your messages to that database, you absolute icon πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from