MU-INFO(1)

🌸 MU INFO(1) β€” the general commands manual, section 1, bestie 🌸

okay so real quick before we dive in: this page lives in section 1 of the manual (the general commands manual), and it's all about mu info. yes, that mu. πŸ’–


✨ NAME ✨

mu-info β€” show information πŸ™ˆ


πŸ“œ SYNOPSIS πŸ“œ

mu [COMMON OPTIONS] info [TOPIC]

πŸ’… DESCRIPTION πŸ’…

mu info is the mu command you hit up when you need the tea about all kinds of topics. here's the lineup, no cap:

  • mu: general mu build information. this is the default one, so if you don't say a topic, this is what you get 🫢
  • store: information about the message store ✨
  • fields: a table with all the query fields and flags πŸ“‹
  • maildirs: list all maildirs under the store's root-maildir πŸ“
⚠️ heads up bestie: while you're running stuff (think mu4e), some of the store information can be delayed because of database caching. it's not broken, it's just ✨fashionably late✨. πŸ’€

πŸŽ€ COMMON OPTIONS πŸŽ€

  • -d, --debug β€” makes mu generate extra debug information, which is lowkey so useful when you're debugging the program itself. all that debug info goes to the standard logging location β€” go peek at mu(1) for the deets πŸ›
  • -q, --quiet β€” makes mu stop printing informational messages and progress info to standard output, and sends them to the log file only. error messages still go to standard error though, we're not hiding those πŸ™…β€β™€οΈ. also: mu index is much faster with --quiet, so if you're calling mu from scripts etc., this is the move. periodt. πŸ”₯
  • --log-stderr β€” causes mu to not output log messages to standard error, in addition to sending them to the standard logging location πŸͺ΅
  • --nocolor β€” do not use ANSI colors 🎨. the environment variable NO_COLOR can be used as an alternative to --nocolor, iykyk
  • -V, --version β€” prints mu version and copyright information πŸ‘‘
  • -h, --help β€” lists the various command line options πŸ™‹β€β™€οΈ

πŸ’€ EXIT CODE πŸ’€

this command returns 0 when it completes successfully, or a non-zero exit code otherwise. vibe check time:

  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. they want to hear from you fr fr 🫢


πŸ‘‘ AUTHOR πŸ‘‘

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


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.

no warranty bestie, we said what we said πŸ’…

πŸ¦‹ SEE ALSO πŸ¦‹

mu(1)


and that's the whole page, gorgeous πŸ’– written for mu version 1.14.2 β€” go forth and info, you ate ⭐🧚

πŸ“¦ where this page comes from