path inconsistencies for config files
vincent at vinc17.org
Thu May 9 10:45:28 UTC 2019
In the Mutt manual, one has:
1. Location of Initialization Files
While the default configuration (or "preferences") make Mutt usable
right out of the box, it is often desirable to tailor Mutt to suit
your own tastes. When Mutt is first invoked, it will attempt to read
the "system" configuration file (defaults set by your local system
administrator), unless the "-n" command line option is specified.
This file is typically /usr/local/share/mutt/Muttrc or /etc/Muttrc.
Example 3.7. Configuring external alias files
When you add an attachment to your mail message, Mutt searches your
personal mime.types file at $HOME/.mime.types, and then the system
mime.types file at /usr/local/share/mutt/mime.types or /etc/mime.types
To enable "classic mode", ensure GPGME is disabled and use the gpg.rc
or smime.rc files that come with mutt. These are typically installed
under /usr/share/doc/mutt/samples/. Source them, either directly or by
copying them to your .mutt directory and sourcing them. Sourcing them
directly from /usr/share/doc/mutt/samples/ has the benefit of
automatically using fixes and security improvements to the command
invocations, and is recommended.
/usr/local/share is used in the first 3 parts, but just /usr/share
in the 4th one.
Also, I don't understand why /usr/local/share/mutt/mime.types
is hardcoded (if still valid). Moreover, it seems that Mutt
installs Muttrc and mime.types in $prefix/etc, and the manual
is inconsistent with that.
IMHO, all these should be relative to the install directory ($prefix).
There should be a Mutt variable, e.g. $installdir, to express this.
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
More information about the Mutt-dev