Supported platforms
===================
-Mutt has been reported to compile and run under the following Unix operating
+Mutt-ng has been reported to compile and run under the following Unix operating
systems:
AIX
S-Lang, ftp://space.mit.edu/pub/davis/slang/
-- Mutt needs an implementation of the iconv API for character set
+- Mutt-ng needs an implementation of the iconv API for character set
conversions. A free one can be found under the following URL:
http://www.gnu.org/software/libiconv/
Installation
============
-Installing Mutt is rather painless through the use of the GNU
-autoconf package. Simply untar the Mutt distribution, and run the
+Installing Mutt-ng is rather painless through the use of the GNU
+autoconf package. Simply untar the Mutt-ng distribution, and run the
``configure'' script. If you have obtained the distribution from
the CVS repository, run the ``prepare'' script with the same command
-line parameters you would pass to configure. It will set up mutt's
+line parameters you would pass to configure. It will set up Mutt-ng's
build environment and add the files which are present in the tar
balls, but not in the CVS repository.
to ``configure'' to help it out, or change the default behavior:
--prefix=DIR
- install Mutt in DIR instead of /usr/local
+ install Mutt-ng in DIR instead of /usr/local
--with-curses=DIR
use the curses lib in DIR/lib. If you have ncurses, ``configure''
use the S-Lang library instead of ncurses. This library seems to
work better for some people because it is less picky about proper
termcap entries than ncurses. It is recommended that you use at
- *least* version 0.99-38 with Mutt.
+ *least* version 0.99-38 with Mutt-ng.
--with-mailpath=DIR
specify where the spool mailboxes are located on your system
Use the Cyrus SASL library for IMAP or POP authentication. This
library provides generic support for several authentication methods,
and more may be added by the system administrator without recompiling
- mutt. SASL may also be able to encrypt your mail session even if
+ Mutt-ng. SASL may also be able to encrypt your mail session even if
SSL is not available.
--disable-nls
- This switch disables mutt's native language support.
+ This switch disables Mutt-ng's native language support.
--with-included-gettext
- Mutt will be built using the GNU gettext library included in
+ Mutt-ng will be built using the GNU gettext library included in
the intl/ sub-directory. You may need to use this switch if
your machine has something which looks like gettext to the
- configure script, but isn't able to cope with mutt's catalog
+ configure script, but isn't able to cope with Mutt-ng's catalog
files.
--with-regex
use flock() to lock files.
--disable-fcntl
- by default, Mutt uses fcntl() to lock files. Over NFS this can
+ by default, Mutt-ng uses fcntl() to lock files. Over NFS this can
result in poor performance on read/write. Note that using this
option could be dangerous if dotlocking is also disabled.
--enable-nfs-fix
some implementations of NFS do not always write the
- atime/mtime of small files. This means that Mutt's ``mailboxes''
+ atime/mtime of small files. This means that Mutt-ng's ``mailboxes''
feature does not always work properly, as it uses these
attributes to work out whether the file has new mail. This
option enables a workaround to this bug.
--enable-locales-fix
on some systems, the result of isprint() can't be used reliably
to decide which characters are printable, even if you set the
- LANG environment variable. If you set this option, Mutt will
+ LANG environment variable. If you set this option, Mutt-ng will
assume all characters in the ISO-8859-* range are printable. If
- you leave it unset, Mutt will attempt to use isprint() if either
+ you leave it unset, Mutt-ng will attempt to use isprint() if either
of the environment variables LANG, LC_ALL or LC_CTYPE is set,
and will revert to the ISO-8859-* range if they aren't.
If you need --enable-locales-fix then you will probably need
LC_ALL or LC_CTYPE instead).
--without-wc-funcs
- by default Mutt uses the functions mbrtowc(), wctomb() and
+ by default Mutt-ng uses the functions mbrtowc(), wctomb() and
wcwidth() provided by the system, when they are available.
- With this option Mutt will use its own version of those
+ With this option Mutt-ng will use its own version of those
functions, which should work with 8-bit display charsets, UTF-8,
euc-jp or shift_jis, even if the system doesn't normally support
those multibyte charsets.
- If you find Mutt is displaying non-ascii characters as octal
+ If you find Mutt-ng is displaying non-ascii characters as octal
escape sequences (e.g. \243), even though you have set LANG and
LC_CTYPE correctly, then you might find you can solve the problem
with either or both of --enable-locales-fix and --without-wc-funcs.
--with-exec-shell=SHELL
on some versions of unix, /bin/sh has a bug that makes using emacs
- with mutt very difficult. If you have the problem that whenever
- you press control-G in emacs, mutt and emacs become very confused,
+ with Mutt-ng very difficult. If you have the problem that whenever
+ you press control-G in emacs, Mutt-ng and emacs become very confused,
you may want to try using a Bourne-derived shell other than
/bin/sh here. Some shells that may work are bash, zsh, and ksh.
C shells such as csh and tcsh will amost certainly not work right.
- Note that this option is unrelated to what shell mutt gives you
+ Note that this option is unrelated to what shell Mutt-ng gives you
when you press '!'. Only use this option to solve the above problem,
and only specify one of the above shells as its argument.
(If you encounter this problem with your platform's native
- Bourne shell, please send a short report to mutt-dev@mutt.org,
+ Bourne shell, please send a short report to mutt-ng-devel@lists.berlios.de,
so a short note on this topic can be added to the Platform notes
section below.)
--enable-exact-address
- By default, Mutt will rewrite all addresses in the form
+ By default, Mutt-ng will rewrite all addresses in the form
Personal Name <user@host.domain>
- regardless of the input. By enabling this option, Mutt will write
+ regardless of the input. By enabling this option, Mutt-ng will write
addresses in the same form they are parsed. NOTE: this requires
significantly more memory.
Once ``configure'' has completed, simply type ``make install.''
-Mutt should compile cleanly (without errors) and you should end up with a
-binary called ``mutt.'' If you get errors about undefined symbols like
+Mutt-ng should compile cleanly (without errors) and you should end up with a
+binary called ``muttng.'' If you get errors about undefined symbols like
A_NORMAL or KEY_MIN, then you probably don't have a SysV compliant curses
library. You should install either ncurses or S-Lang (see above), and then
run the ``configure'' script again.
Character set support
=====================
-Mutt no longer contains functions for doing character set conversion.
+Mutt-ng no longer contains functions for doing character set conversion.
Instead, it expects the iconv functions (iconv_open, iconv,
iconv_close) to be provided. Most up-to-date systems provide these
-functions, often as part of the C library. If you are installing Mutt
+functions, often as part of the C library. If you are installing Mutt-ng
on a system which does not have them, it is recommended that you
install Bruno Haible's portable libiconv library, which you can obtain
from:
If you decide to use your system's iconv implementation, you may
-need to tell mutt about implementation-defined names for some
+need to tell Mutt-ng about implementation-defined names for some
character sets. Sample configuration files for various systems can
be found in the directory contrib/iconv/ in this source
distribution, and will be installed in the samples/iconv directory
-as part of mutt's documentation.
+as part of Mutt-ng's documentation.
In order to use these sample configuration files, just put a line
like
- source /usr/local/doc/mutt/samples/iconv/iconv.osf1-4.0d.rc
+ source /usr/local/doc/muttng/samples/iconv/iconv.osf1-4.0d.rc
into your system's global Muttrc, which normally resides in /etc or
/usr/local/etc.
-If you really want to, you can configure Mutt --disable-iconv, but
+If you really want to, you can configure Mutt-ng --disable-iconv, but
there will then be no character set conversion.
All platforms
There is a bug in most (if not all) S-Lang versions which
- prevents the Meta key from working with mutt. A patch can
+ prevents the Meta key from working with Mutt-ng. A patch can
be found in the file contrib/patch.slang-1.2.2.keypad.1 in
- this mutt distribution.
+ this Mutt-ng distribution.
Solaris 2.4
The system regcomp() and regexec() routines are very badly
broken. This should be automatically detected by the
configure script. If not, use the --with-regex switch when
- configuring mutt.
+ configuring Mutt-ng.
We are also hearing reports that Solaris 2.4's NLS libraries
- dump core with mutt when using a locale different from "C".
+ dump core with Mutt-ng when using a locale different from "C".
Use the --with-included-gettext configuration switch if you
experience this problem.
Solaris 2.6
- There are reports that mutt behaves strangely when linked with
+ There are reports that Mutt-ng behaves strangely when linked with
the system regexp library. Please use the --with-regex switch
when configuring on this platform.
Sparc Linux
Redhat 4.2 Sparc users reported problems with some system
- include files when building mutt. Configuring mutt with the
+ include files when building Mutt-ng. Configuring Mutt-ng with the
--disable-warnings switch is said to help against this problem.