From 8fea076821f02d95dd15d4b89fda28a2e02c8eb9 Mon Sep 17 00:00:00 2001 From: Thomas Roessler Date: Tue, 16 Jun 1998 18:11:24 +0000 Subject: [PATCH] Have "make install" install manual.txt as well. --- Makefile.in | 15 +- configure | 258 +++++---- configure.in | 18 +- doc/Makefile.in | 32 ++ doc/manual.txt | 1343 ++++++++++++++++++++++++++++++++++++++--------- 5 files changed, 1292 insertions(+), 374 deletions(-) diff --git a/Makefile.in b/Makefile.in index 8bda5d883..d02a7ca5b 100644 --- a/Makefile.in +++ b/Makefile.in @@ -26,6 +26,7 @@ libdir=@libdir@ mandir=@mandir@ sharedir=@sharedir@ srcdir=@srcdir@ +docdir=@docdir@ VPATH=@srcdir@ @SET_MAKE@ @@ -64,12 +65,10 @@ keymap_defs.h: Makefile $(OPS) rm -f keymap_defs.h $(srcdir)/gen_defs $(OPS) > keymap_defs.h -install: mutt +install: mutt install.doc $(srcdir)/mkinstalldirs $(bindir) -mv -f $(bindir)/mutt $(bindir)/mutt.old $(INSTALL) @MUTT_GROUP@ -m @MUTT_PERMISSION@ mutt $(bindir) - $(srcdir)/mkinstalldirs $(mandir)/man1 - $(INSTALL) -m 644 $(srcdir)/doc/mutt.man $(mandir)/man1/mutt.1 -if [ ! -f $(sharedir)/Muttrc ]; then \ $(srcdir)/mkinstalldirs $(sharedir); \ $(INSTALL) -m 644 $(srcdir)/Muttrc $(sharedir); \ @@ -78,8 +77,14 @@ install: mutt $(INSTALL) -m 644 $(srcdir)/mime.types $(sharedir); \ fi -uninstall: - rm -f $(bindir)/mutt $(sharedir)/Muttrc $(mandir)/man1/mutt.1 +install.doc: + make -C $(srcdir)/doc/ install + +uninstall: uninstall.doc + rm -f $(bindir)/mutt $(sharedir)/Muttrc + +uninstall.doc: + make -C $(srcdir)/doc/ uninstall $(srcdir)/configure: $(srcdir)/configure.in autoconf diff --git a/configure b/configure index cc8dca53b..240f6658f 100755 --- a/configure +++ b/configure @@ -23,6 +23,8 @@ ac_help="$ac_help --with-mailpath=DIR directory where spool mailboxes are located" ac_help="$ac_help --with-sharedir=PATH specify where to put arch independent files" +ac_help="$ac_help + --with-docdir=PATH specify where to put the documentation" ac_help="$ac_help --with-domain=DOMAIN Specify your DNS domain name " ac_help="$ac_help @@ -559,7 +561,7 @@ VERSION=0.92.11 SUBVERSION='' echo $ac_n "checking for prefix""... $ac_c" 1>&6 -echo "configure:563: checking for prefix" >&5 +echo "configure:565: checking for prefix" >&5 if test x$prefix = xNONE; then mutt_cv_prefix=$ac_default_prefix else @@ -570,7 +572,7 @@ echo "$ac_t""$mutt_cv_prefix" 1>&6 # Extract the first word of "gcc", so it can be a program name with args. set dummy gcc; ac_word=$2 echo $ac_n "checking for $ac_word""... $ac_c" 1>&6 -echo "configure:574: checking for $ac_word" >&5 +echo "configure:576: checking for $ac_word" >&5 if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -599,7 +601,7 @@ if test -z "$CC"; then # Extract the first word of "cc", so it can be a program name with args. set dummy cc; ac_word=$2 echo $ac_n "checking for $ac_word""... $ac_c" 1>&6 -echo "configure:603: checking for $ac_word" >&5 +echo "configure:605: checking for $ac_word" >&5 if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -647,7 +649,7 @@ fi fi echo $ac_n "checking whether the C compiler ($CC $CFLAGS $LDFLAGS) works""... $ac_c" 1>&6 -echo "configure:651: checking whether the C compiler ($CC $CFLAGS $LDFLAGS) works" >&5 +echo "configure:653: checking whether the C compiler ($CC $CFLAGS $LDFLAGS) works" >&5 ac_ext=c # CFLAGS is not in ac_cpp because -g, -O, etc. are not valid cpp options. @@ -657,11 +659,11 @@ ac_link='${CC-cc} -o conftest $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS cross_compiling=$ac_cv_prog_cc_cross cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:667: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then ac_cv_prog_cc_works=yes # If we can't run a trivial program, we are probably using a cross compiler. if (./conftest; exit) 2>/dev/null; then @@ -681,12 +683,12 @@ if test $ac_cv_prog_cc_works = no; then { echo "configure: error: installation or configuration problem: C compiler cannot create executables." 1>&2; exit 1; } fi echo $ac_n "checking whether the C compiler ($CC $CFLAGS $LDFLAGS) is a cross-compiler""... $ac_c" 1>&6 -echo "configure:685: checking whether the C compiler ($CC $CFLAGS $LDFLAGS) is a cross-compiler" >&5 +echo "configure:687: checking whether the C compiler ($CC $CFLAGS $LDFLAGS) is a cross-compiler" >&5 echo "$ac_t""$ac_cv_prog_cc_cross" 1>&6 cross_compiling=$ac_cv_prog_cc_cross echo $ac_n "checking whether we are using GNU C""... $ac_c" 1>&6 -echo "configure:690: checking whether we are using GNU C" >&5 +echo "configure:692: checking whether we are using GNU C" >&5 if eval "test \"`echo '$''{'ac_cv_prog_gcc'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -695,7 +697,7 @@ else yes; #endif EOF -if { ac_try='${CC-cc} -E conftest.c'; { (eval echo configure:699: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }; } | egrep yes >/dev/null 2>&1; then +if { ac_try='${CC-cc} -E conftest.c'; { (eval echo configure:701: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }; } | egrep yes >/dev/null 2>&1; then ac_cv_prog_gcc=yes else ac_cv_prog_gcc=no @@ -710,7 +712,7 @@ if test $ac_cv_prog_gcc = yes; then ac_save_CFLAGS="$CFLAGS" CFLAGS= echo $ac_n "checking whether ${CC-cc} accepts -g""... $ac_c" 1>&6 -echo "configure:714: checking whether ${CC-cc} accepts -g" >&5 +echo "configure:716: checking whether ${CC-cc} accepts -g" >&5 if eval "test \"`echo '$''{'ac_cv_prog_cc_g'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -738,7 +740,7 @@ else fi echo $ac_n "checking whether ${MAKE-make} sets \${MAKE}""... $ac_c" 1>&6 -echo "configure:742: checking whether ${MAKE-make} sets \${MAKE}" >&5 +echo "configure:744: checking whether ${MAKE-make} sets \${MAKE}" >&5 set dummy ${MAKE-make}; ac_make=`echo "$2" | sed 'y%./+-%__p_%'` if eval "test \"`echo '$''{'ac_cv_prog_make_${ac_make}_set'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 @@ -794,7 +796,7 @@ ac_configure=$ac_aux_dir/configure # This should be Cygnus configure. # SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff" # ./install, which can be erroneously created by make from ./install.sh. echo $ac_n "checking for a BSD compatible install""... $ac_c" 1>&6 -echo "configure:798: checking for a BSD compatible install" >&5 +echo "configure:800: checking for a BSD compatible install" >&5 if test -z "$INSTALL"; then if eval "test \"`echo '$''{'ac_cv_path_install'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 @@ -847,7 +849,7 @@ test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644' # Extract the first word of "sendmail", so it can be a program name with args. set dummy sendmail; ac_word=$2 echo $ac_n "checking for $ac_word""... $ac_c" 1>&6 -echo "configure:851: checking for $ac_word" >&5 +echo "configure:853: checking for $ac_word" >&5 if eval "test \"`echo '$''{'ac_cv_path_SENDMAIL'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -889,7 +891,7 @@ if test -f $srcdir/pgp.c; then # Extract the first word of "gpg", so it can be a program name with args. set dummy gpg; ac_word=$2 echo $ac_n "checking for $ac_word""... $ac_c" 1>&6 -echo "configure:893: checking for $ac_word" >&5 +echo "configure:895: checking for $ac_word" >&5 if eval "test \"`echo '$''{'ac_cv_path_GPG'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -933,7 +935,7 @@ EOF # Extract the first word of "pgpk", so it can be a program name with args. set dummy pgpk; ac_word=$2 echo $ac_n "checking for $ac_word""... $ac_c" 1>&6 -echo "configure:937: checking for $ac_word" >&5 +echo "configure:939: checking for $ac_word" >&5 if eval "test \"`echo '$''{'ac_cv_path_PGPK'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -978,7 +980,7 @@ EOF # Extract the first word of "pgp", so it can be a program name with args. set dummy pgp; ac_word=$2 echo $ac_n "checking for $ac_word""... $ac_c" 1>&6 -echo "configure:982: checking for $ac_word" >&5 +echo "configure:984: checking for $ac_word" >&5 if eval "test \"`echo '$''{'ac_cv_path_PGP'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -1042,7 +1044,7 @@ EOF # Extract the first word of "ispell", so it can be a program name with args. set dummy ispell; ac_word=$2 echo $ac_n "checking for $ac_word""... $ac_c" 1>&6 -echo "configure:1046: checking for $ac_word" >&5 +echo "configure:1048: checking for $ac_word" >&5 if eval "test \"`echo '$''{'ac_cv_path_ISPELL'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -1079,7 +1081,7 @@ EOF fi echo $ac_n "checking how to run the C preprocessor""... $ac_c" 1>&6 -echo "configure:1083: checking how to run the C preprocessor" >&5 +echo "configure:1085: checking how to run the C preprocessor" >&5 # On Suns, sometimes $CPP names a directory. if test -n "$CPP" && test -d "$CPP"; then CPP= @@ -1094,13 +1096,13 @@ else # On the NeXT, cc -E runs the code through the compiler's parser, # not just through cpp. cat > conftest.$ac_ext < Syntax Error EOF ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out" -{ (eval echo configure:1104: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } +{ (eval echo configure:1106: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } ac_err=`grep -v '^ *+' conftest.out` if test -z "$ac_err"; then : @@ -1111,13 +1113,13 @@ else rm -rf conftest* CPP="${CC-cc} -E -traditional-cpp" cat > conftest.$ac_ext < Syntax Error EOF ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out" -{ (eval echo configure:1121: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } +{ (eval echo configure:1123: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } ac_err=`grep -v '^ *+' conftest.out` if test -z "$ac_err"; then : @@ -1143,7 +1145,7 @@ echo "$ac_t""$CPP" 1>&6 if test "${with_slang+set}" = set; then withval="$with_slang" echo $ac_n "checking if -ltermlib is required""... $ac_c" 1>&6 -echo "configure:1147: checking if -ltermlib is required" >&5 +echo "configure:1149: checking if -ltermlib is required" >&5 if eval "test \"`echo '$''{'mutt_cv_bsdish'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -1151,7 +1153,7 @@ else { echo "configure: error: can not run test program while cross compiling" 1>&2; exit 1; } else cat > conftest.$ac_ext < @@ -1164,7 +1166,7 @@ main () #endif } EOF -if { (eval echo configure:1168: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit) 2>/dev/null +if { (eval echo configure:1170: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit) 2>/dev/null then mutt_cv_bsdish=yes else @@ -1181,7 +1183,7 @@ fi echo "$ac_t""$mutt_cv_bsdish" 1>&6 echo $ac_n "checking for S-Lang""... $ac_c" 1>&6 -echo "configure:1185: checking for S-Lang" >&5 +echo "configure:1187: checking for S-Lang" >&5 if test $withval = yes; then if test -d $srcdir/../slang; then mutt_cv_slang=$srcdir/../slang/src @@ -1227,16 +1229,16 @@ EOF echo $ac_n "checking if I can compile a test SLang program""... $ac_c" 1>&6 -echo "configure:1231: checking if I can compile a test SLang program" >&5 +echo "configure:1233: checking if I can compile a test SLang program" >&5 cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:1242: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* echo "$ac_t""yes" 1>&6 else @@ -1264,7 +1266,7 @@ fi echo $ac_n "checking for initscr in -lncurses""... $ac_c" 1>&6 -echo "configure:1268: checking for initscr in -lncurses" >&5 +echo "configure:1270: checking for initscr in -lncurses" >&5 ac_lib_var=`echo ncurses'_'initscr | sed 'y%./+-%__p_%'` if eval "test \"`echo '$''{'ac_cv_lib_$ac_lib_var'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 @@ -1272,7 +1274,7 @@ else ac_save_LIBS="$LIBS" LIBS="-lncurses $LIBS" cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:1289: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_lib_$ac_lib_var=yes" else @@ -1306,17 +1308,17 @@ if eval "test \"`echo '$ac_cv_lib_'$ac_lib_var`\" = yes"; then do ac_safe=`echo "$ac_hdr" | sed 'y%./+-%__p_%'` echo $ac_n "checking for $ac_hdr""... $ac_c" 1>&6 -echo "configure:1310: checking for $ac_hdr" >&5 +echo "configure:1312: checking for $ac_hdr" >&5 if eval "test \"`echo '$''{'ac_cv_header_$ac_safe'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext < EOF ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out" -{ (eval echo configure:1320: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } +{ (eval echo configure:1322: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } ac_err=`grep -v '^ *+' conftest.out` if test -z "$ac_err"; then rm -rf conftest* @@ -1357,12 +1359,12 @@ fi echo $ac_n "checking for start_color""... $ac_c" 1>&6 -echo "configure:1361: checking for start_color" >&5 +echo "configure:1363: checking for start_color" >&5 if eval "test \"`echo '$''{'ac_cv_func_start_color'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:1391: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_func_start_color=yes" else @@ -1410,12 +1412,12 @@ fi for ac_func in typeahead bkgdset curs_set meta use_default_colors do echo $ac_n "checking for $ac_func""... $ac_c" 1>&6 -echo "configure:1414: checking for $ac_func" >&5 +echo "configure:1416: checking for $ac_func" >&5 if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:1444: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_func_$ac_func=yes" else @@ -1465,12 +1467,12 @@ done for ac_func in resizeterm do echo $ac_n "checking for $ac_func""... $ac_c" 1>&6 -echo "configure:1469: checking for $ac_func" >&5 +echo "configure:1471: checking for $ac_func" >&5 if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:1499: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_func_$ac_func=yes" else @@ -1522,12 +1524,12 @@ fi echo $ac_n "checking for ANSI C header files""... $ac_c" 1>&6 -echo "configure:1526: checking for ANSI C header files" >&5 +echo "configure:1528: checking for ANSI C header files" >&5 if eval "test \"`echo '$''{'ac_cv_header_stdc'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext < #include @@ -1535,7 +1537,7 @@ else #include EOF ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out" -{ (eval echo configure:1539: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } +{ (eval echo configure:1541: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } ac_err=`grep -v '^ *+' conftest.out` if test -z "$ac_err"; then rm -rf conftest* @@ -1552,7 +1554,7 @@ rm -f conftest* if test $ac_cv_header_stdc = yes; then # SunOS 4.x string.h does not declare mem*, contrary to ANSI. cat > conftest.$ac_ext < EOF @@ -1570,7 +1572,7 @@ fi if test $ac_cv_header_stdc = yes; then # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI. cat > conftest.$ac_ext < EOF @@ -1591,7 +1593,7 @@ if test "$cross_compiling" = yes; then : else cat > conftest.$ac_ext < #define ISLOWER(c) ('a' <= (c) && (c) <= 'z') @@ -1602,7 +1604,7 @@ if (XOR (islower (i), ISLOWER (i)) || toupper (i) != TOUPPER (i)) exit(2); exit (0); } EOF -if { (eval echo configure:1606: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit) 2>/dev/null +if { (eval echo configure:1608: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit) 2>/dev/null then : else @@ -1630,17 +1632,17 @@ for ac_hdr in stdarg.h sys/ioctl.h do ac_safe=`echo "$ac_hdr" | sed 'y%./+-%__p_%'` echo $ac_n "checking for $ac_hdr""... $ac_c" 1>&6 -echo "configure:1634: checking for $ac_hdr" >&5 +echo "configure:1636: checking for $ac_hdr" >&5 if eval "test \"`echo '$''{'ac_cv_header_$ac_safe'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext < EOF ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out" -{ (eval echo configure:1644: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } +{ (eval echo configure:1646: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; } ac_err=`grep -v '^ *+' conftest.out` if test -z "$ac_err"; then rm -rf conftest* @@ -1668,12 +1670,12 @@ done echo $ac_n "checking return type of signal handlers""... $ac_c" 1>&6 -echo "configure:1672: checking return type of signal handlers" >&5 +echo "configure:1674: checking return type of signal handlers" >&5 if eval "test \"`echo '$''{'ac_cv_type_signal'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext < #include @@ -1690,7 +1692,7 @@ int main() { int i; ; return 0; } EOF -if { (eval echo configure:1694: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then +if { (eval echo configure:1696: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then rm -rf conftest* ac_cv_type_signal=void else @@ -1710,12 +1712,12 @@ EOF echo $ac_n "checking for sys_siglist declaration in signal.h or unistd.h""... $ac_c" 1>&6 -echo "configure:1714: checking for sys_siglist declaration in signal.h or unistd.h" >&5 +echo "configure:1716: checking for sys_siglist declaration in signal.h or unistd.h" >&5 if eval "test \"`echo '$''{'ac_cv_decl_sys_siglist'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext < #include @@ -1727,7 +1729,7 @@ int main() { char *msg = *(sys_siglist + 1); ; return 0; } EOF -if { (eval echo configure:1731: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then +if { (eval echo configure:1733: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then rm -rf conftest* ac_cv_decl_sys_siglist=yes else @@ -1749,7 +1751,7 @@ fi echo $ac_n "checking size of long""... $ac_c" 1>&6 -echo "configure:1753: checking size of long" >&5 +echo "configure:1755: checking size of long" >&5 if eval "test \"`echo '$''{'ac_cv_sizeof_long'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -1757,7 +1759,7 @@ else { echo "configure: error: can not run test program while cross compiling" 1>&2; exit 1; } else cat > conftest.$ac_ext < main() @@ -1768,7 +1770,7 @@ main() exit(0); } EOF -if { (eval echo configure:1772: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit) 2>/dev/null +if { (eval echo configure:1774: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit) 2>/dev/null then ac_cv_sizeof_long=`cat conftestval` else @@ -1789,12 +1791,12 @@ EOF echo $ac_n "checking for pid_t""... $ac_c" 1>&6 -echo "configure:1793: checking for pid_t" >&5 +echo "configure:1795: checking for pid_t" >&5 if eval "test \"`echo '$''{'ac_cv_type_pid_t'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext < #if STDC_HEADERS @@ -1825,12 +1827,12 @@ fi for ac_func in setegid srand48 strerror do echo $ac_n "checking for $ac_func""... $ac_c" 1>&6 -echo "configure:1829: checking for $ac_func" >&5 +echo "configure:1831: checking for $ac_func" >&5 if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:1859: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_func_$ac_func=yes" else @@ -1881,12 +1883,12 @@ done for ac_func in strcasecmp do echo $ac_n "checking for $ac_func""... $ac_c" 1>&6 -echo "configure:1885: checking for $ac_func" >&5 +echo "configure:1887: checking for $ac_func" >&5 if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:1915: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_func_$ac_func=yes" else @@ -1938,12 +1940,12 @@ done mutt_cv_snprintf=no echo $ac_n "checking for snprintf""... $ac_c" 1>&6 -echo "configure:1942: checking for snprintf" >&5 +echo "configure:1944: checking for snprintf" >&5 if eval "test \"`echo '$''{'ac_cv_func_snprintf'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:1972: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_func_snprintf=yes" else @@ -1990,12 +1992,12 @@ mutt_cv_snprintf=yes fi echo $ac_n "checking for vsnprintf""... $ac_c" 1>&6 -echo "configure:1994: checking for vsnprintf" >&5 +echo "configure:1996: checking for vsnprintf" >&5 if eval "test \"`echo '$''{'ac_cv_func_vsnprintf'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:2024: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_func_vsnprintf=yes" else @@ -2048,12 +2050,12 @@ fi for ac_func in ftruncate do echo $ac_n "checking for $ac_func""... $ac_c" 1>&6 -echo "configure:2052: checking for $ac_func" >&5 +echo "configure:2054: checking for $ac_func" >&5 if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:2082: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_func_$ac_func=yes" else @@ -2098,7 +2100,7 @@ EOF else echo "$ac_t""no" 1>&6 echo $ac_n "checking for chsize in -lx""... $ac_c" 1>&6 -echo "configure:2102: checking for chsize in -lx" >&5 +echo "configure:2104: checking for chsize in -lx" >&5 ac_lib_var=`echo x'_'chsize | sed 'y%./+-%__p_%'` if eval "test \"`echo '$''{'ac_cv_lib_$ac_lib_var'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 @@ -2106,7 +2108,7 @@ else ac_save_LIBS="$LIBS" LIBS="-lx $LIBS" cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:2123: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_lib_$ac_lib_var=yes" else @@ -2151,12 +2153,12 @@ done for ac_func in strftime do echo $ac_n "checking for $ac_func""... $ac_c" 1>&6 -echo "configure:2155: checking for $ac_func" >&5 +echo "configure:2157: checking for $ac_func" >&5 if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:2185: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_func_$ac_func=yes" else @@ -2201,7 +2203,7 @@ EOF else echo "$ac_t""no" 1>&6 echo $ac_n "checking for strftime in -lintl""... $ac_c" 1>&6 -echo "configure:2205: checking for strftime in -lintl" >&5 +echo "configure:2207: checking for strftime in -lintl" >&5 ac_lib_var=`echo intl'_'strftime | sed 'y%./+-%__p_%'` if eval "test \"`echo '$''{'ac_cv_lib_$ac_lib_var'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 @@ -2209,7 +2211,7 @@ else ac_save_LIBS="$LIBS" LIBS="-lintl $LIBS" cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:2226: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_lib_$ac_lib_var=yes" else @@ -2273,12 +2275,12 @@ else for ac_func in regcomp do echo $ac_n "checking for $ac_func""... $ac_c" 1>&6 -echo "configure:2277: checking for $ac_func" >&5 +echo "configure:2279: checking for $ac_func" >&5 if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:2307: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_func_$ac_func=yes" else @@ -2372,7 +2374,7 @@ if test "${with_mailpath+set}" = set; then mutt_cv_mailpath=$withval else echo $ac_n "checking where new mail is stored""... $ac_c" 1>&6 -echo "configure:2376: checking where new mail is stored" >&5 +echo "configure:2378: checking where new mail is stored" >&5 if eval "test \"`echo '$''{'mutt_cv_mailpath'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -2401,7 +2403,7 @@ EOF echo $ac_n "checking if $mutt_cv_mailpath is world writable""... $ac_c" 1>&6 -echo "configure:2405: checking if $mutt_cv_mailpath is world writable" >&5 +echo "configure:2407: checking if $mutt_cv_mailpath is world writable" >&5 if eval "test \"`echo '$''{'mutt_cv_worldwrite'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -2409,7 +2411,7 @@ else { echo "configure: error: can not run test program while cross compiling" 1>&2; exit 1; } else cat > conftest.$ac_ext < #include @@ -2423,7 +2425,7 @@ int main (int argc, char **argv) exit (1); } EOF -if { (eval echo configure:2427: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit) 2>/dev/null +if { (eval echo configure:2429: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit) 2>/dev/null then mutt_cv_worldwrite=yes else @@ -2448,7 +2450,7 @@ EOF else echo $ac_n "checking if $mutt_cv_mailpath is group writable""... $ac_c" 1>&6 -echo "configure:2452: checking if $mutt_cv_mailpath is group writable" >&5 +echo "configure:2454: checking if $mutt_cv_mailpath is group writable" >&5 if eval "test \"`echo '$''{'mutt_cv_groupwrite'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -2456,7 +2458,7 @@ else { echo "configure: error: can not run test program while cross compiling" 1>&2; exit 1; } else cat > conftest.$ac_ext < #include @@ -2470,7 +2472,7 @@ int main (int argc, char **argv) exit (1); } EOF -if { (eval echo configure:2474: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit) 2>/dev/null +if { (eval echo configure:2476: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit) 2>/dev/null then mutt_cv_groupwrite=yes else @@ -2506,7 +2508,7 @@ if test "${with_sharedir+set}" = set; then mutt_cv_sharedir=$withval else echo $ac_n "checking where to put architecture-independent data files""... $ac_c" 1>&6 -echo "configure:2510: checking where to put architecture-independent data files" >&5 +echo "configure:2512: checking where to put architecture-independent data files" >&5 if eval "test \"`echo '$''{'mutt_cv_sharedir'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -2534,6 +2536,33 @@ fi sharedir=$mutt_cv_sharedir +# Check whether --with-docdir or --without-docdir was given. +if test "${with_docdir+set}" = set; then + withval="$with_docdir" + mutt_cv_docdir=$withval +else + echo $ac_n "checking where to put the documentation""... $ac_c" 1>&6 +echo "configure:2546: checking where to put the documentation" >&5 +if eval "test \"`echo '$''{'mutt_cv_docdir'+set}'`\" = set"; then + echo $ac_n "(cached) $ac_c" 1>&6 +else + if test x$prefix = xNONE; then + mutt_cv_prefix=$ac_default_prefix + else + mutt_cv_prefix=$prefix + fi + mutt_cv_docdir=$mutt_cv_prefix/doc/mutt +fi + +echo "$ac_t""$mutt_cv_docdir" 1>&6 + +fi + + +docdir=$mutt_cv_docdir + + + if test x$mutt_cv_setgid = xyes; then MUTT_GROUP='-g mail' MUTT_PERMISSION=2755 @@ -2574,7 +2603,7 @@ if test "${enable_pop+set}" = set; then EOF echo $ac_n "checking for socket in -lsocket""... $ac_c" 1>&6 -echo "configure:2578: checking for socket in -lsocket" >&5 +echo "configure:2607: checking for socket in -lsocket" >&5 ac_lib_var=`echo socket'_'socket | sed 'y%./+-%__p_%'` if eval "test \"`echo '$''{'ac_cv_lib_$ac_lib_var'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 @@ -2582,7 +2611,7 @@ else ac_save_LIBS="$LIBS" LIBS="-lsocket $LIBS" cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:2626: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_lib_$ac_lib_var=yes" else @@ -2621,7 +2650,7 @@ else fi echo $ac_n "checking for gethostbyname in -lnsl""... $ac_c" 1>&6 -echo "configure:2625: checking for gethostbyname in -lnsl" >&5 +echo "configure:2654: checking for gethostbyname in -lnsl" >&5 ac_lib_var=`echo nsl'_'gethostbyname | sed 'y%./+-%__p_%'` if eval "test \"`echo '$''{'ac_cv_lib_$ac_lib_var'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 @@ -2629,7 +2658,7 @@ else ac_save_LIBS="$LIBS" LIBS="-lnsl $LIBS" cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:2673: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_lib_$ac_lib_var=yes" else @@ -2680,7 +2709,7 @@ if test "${enable_imap+set}" = set; then EOF echo $ac_n "checking for socket in -lsocket""... $ac_c" 1>&6 -echo "configure:2684: checking for socket in -lsocket" >&5 +echo "configure:2713: checking for socket in -lsocket" >&5 ac_lib_var=`echo socket'_'socket | sed 'y%./+-%__p_%'` if eval "test \"`echo '$''{'ac_cv_lib_$ac_lib_var'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 @@ -2688,7 +2717,7 @@ else ac_save_LIBS="$LIBS" LIBS="-lsocket $LIBS" cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:2732: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_lib_$ac_lib_var=yes" else @@ -2727,7 +2756,7 @@ else fi echo $ac_n "checking for gethostbyname in -lnsl""... $ac_c" 1>&6 -echo "configure:2731: checking for gethostbyname in -lnsl" >&5 +echo "configure:2760: checking for gethostbyname in -lnsl" >&5 ac_lib_var=`echo nsl'_'gethostbyname | sed 'y%./+-%__p_%'` if eval "test \"`echo '$''{'ac_cv_lib_$ac_lib_var'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 @@ -2735,7 +2764,7 @@ else ac_save_LIBS="$LIBS" LIBS="-lnsl $LIBS" cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest; then +if { (eval echo configure:2779: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then rm -rf conftest* eval "ac_cv_lib_$ac_lib_var=yes" else @@ -2980,7 +3009,7 @@ done ac_given_srcdir=$srcdir ac_given_INSTALL="$INSTALL" -trap 'rm -fr `echo "Makefile rx/Makefile Muttrc config.h" | sed "s/:[^ ]*//g"` conftest*; exit 1' 1 2 15 +trap 'rm -fr `echo "Makefile rx/Makefile Muttrc doc/Makefile config.h" | sed "s/:[^ ]*//g"` conftest*; exit 1' 1 2 15 EOF cat >> $CONFIG_STATUS <> $CONFIG_STATUS <> $CONFIG_STATUS <<\EOF for ac_file in .. $CONFIG_FILES; do if test "x$ac_file" != x..; then diff --git a/configure.in b/configure.in index 3ee0a076b..36f065076 100644 --- a/configure.in +++ b/configure.in @@ -307,6 +307,22 @@ AC_ARG_WITH(sharedir, [ --with-sharedir=PATH specify where to put arch in sharedir=$mutt_cv_sharedir AC_SUBST(sharedir) +AC_ARG_WITH(docdir, [ --with-docdir=PATH specify where to put the documentation], + [mutt_cv_docdir=$withval], + [ AC_CACHE_CHECK(where to put the documentation, + mutt_cv_docdir, + [if test x$prefix = xNONE; then + mutt_cv_prefix=$ac_default_prefix + else + mutt_cv_prefix=$prefix + fi + mutt_cv_docdir=$mutt_cv_prefix/doc/mutt]) + ]) + +docdir=$mutt_cv_docdir +AC_SUBST(docdir) + + if test x$mutt_cv_setgid = xyes; then MUTT_GROUP='-g mail' MUTT_PERMISSION=2755 @@ -386,4 +402,4 @@ AC_ARG_ENABLE(exact-address, [ --enable-exact-address enable regeneration o AC_DEFINE(EXACT_ADDRESS) fi]) -AC_OUTPUT(Makefile rx/Makefile Muttrc) +AC_OUTPUT(Makefile rx/Makefile Muttrc doc/Makefile) diff --git a/doc/Makefile.in b/doc/Makefile.in index 7d85b315a..a8f0d9be5 100644 --- a/doc/Makefile.in +++ b/doc/Makefile.in @@ -1,5 +1,37 @@ +SHELL=/bin/sh +VERSION=@VERSION@ + +prefix=@prefix@ +exec_prefix=@exec_prefix@ +bindir=@bindir@ +libdir=@libdir@ +mandir=@mandir@ +sharedir=@sharedir@ +srcdir=@srcdir@ +docdir=@docdir@ +VPATH=@srcdir@/doc +@SET_MAKE@ + +INSTALL=@INSTALL@ +CC=@CC@ +XCPPFLAGS=-I. @CPPFLAGS@ +CFLAGS=@CFLAGS@ -DSHAREDIR=\"$(sharedir)\" $(XCPPFLAGS) +LDFLAGS=@LDFLAGS@ + + all: manual.txt mutt.man manual.html +install: mutt.man manual.txt + ../mkinstalldirs $(mandir)/man1 + $(INSTALL) -m 644 mutt.man $(mandir)/man1/mutt.1 + ../mkinstalldirs $(docdir) + $(INSTALL) -m 644 manual.txt $(docdir) + $(INSTALL) -m 644 PGP-Notes.txt $(docdir) + +uninstall: + -rm -f $(mandir)/man1/mutt.1 $(docdir)/manual.txt \ + $(docdir)/PGP-Notes.txt + manual.txt: manual.sgml sgml2txt manual diff --git a/doc/manual.txt b/doc/manual.txt index 17cdd295b..9dfa57e2f 100644 --- a/doc/manual.txt +++ b/doc/manual.txt @@ -12,16 +12,19 @@ regular expression searches and a powerful pattern matching language for selecting groups of messages. + 11..11.. MMuutttt HHoommee PPaaggee http://www.cs.hmc.edu/~me/mutt/index.html + 11..22.. MMaaiilliinngg LLiissttss To subscribe to one of the following mailing lists, send a message with the word _s_u_b_s_c_r_i_b_e in the subject to list-name_- _r_e_q_u_e_s_t@cs.hmc.edu. + +o mutt-announce@cs.hmc.edu -- low traffic list for announcements +o mutt-users@cs.hmc.edu -- help, bug reports and feature requests @@ -31,19 +34,24 @@ NNoottee:: all messages posted to _m_u_t_t_-_a_n_n_o_u_n_c_e are automatically forwarded to _m_u_t_t_-_u_s_e_r_s, so you do not need to be subscribed to both lists. + 11..33.. SSooffttwwaarree DDiissttrriibbuuttiioonn SSiitteess + +o ftp://ftp.cs.hmc.edu/pub/me/mutt/ + 11..44.. IIRRCC Visit channel _#_m_u_t_t on DALnet (www.dal.net) to chat with other people interested in Mutt. + 11..55.. UUSSEENNEETT See the newsgroup comp.mail.mutt. + 11..66.. CCooppyyrriigghhtt Mutt is Copyright (C) 1996-8 Michael R. Elkins @@ -62,8 +70,10 @@ along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. + 22.. GGeettttiinngg SSttaarrtteedd + This section is intended as a brief overview of how to use Mutt. There are many other features which are described elsewhere in the manual. There is even more information available in the Mutt FAQ and @@ -78,11 +88,15 @@ at the command line. There are various command-line options, see either the mutt man page or the ``reference''. + 22..11.. MMoovviinngg AArroouunndd iinn MMeennuuss + Information is presented in menus, very similar to ELM. Here is a table showing the common keys used to navigate menus in Mutt. + + j or Down next-entry move to the next entry k or Up previous-entry move to the previous entry z or PageDn page-down go to the next page @@ -92,12 +106,30 @@ q quit exit the current menu ? help list all keybindings for the current menu + + + + 22..22.. EEddiittiinngg IInnppuutt FFiieellddss Mutt has a builtin line editor which is used as the primary way to input textual data such as email addresses or filenames. The keys used to move around while editing are very similar to those of Emacs. + + + + + + + + + + + + + + ^A or bol move to the start of the line ^B or backward-char move back one char ^D or delete-char delete the char under the cursor @@ -113,14 +145,19 @@ n/a complete filename (only when prompting for a file) n/a finish editing + + + You can remap the _e_d_i_t_o_r functions using the ``bind'' command. For example, to make the _D_e_l_e_t_e key delete the character in front of the cursor rather than under, you could use bind editor delete backspace + 22..33.. RReeaaddiinngg MMaaiill -- TThhee IInnddeexx aanndd PPaaggeerr + Similar to many other mail clients, there are two modes in which mail is read in Mutt. The first is the index of messages in the mailbox, which is called the ``index'' in Mutt. The second mode is the display @@ -129,8 +166,36 @@ The next few sections describe the functions provided in each of these modes. + 22..33..11.. TThhee MMeessssaaggee IInnddeexx + + + + + + + + + + + + + + + + + + + + + + + + + + + c change to a different mailbox ESC c change to a folder in read-only mode C copy the current message to another mailbox @@ -160,13 +225,21 @@ ^T tag messages matching a pattern ^U undelete messages matching a pattern + + + + 22..33..11..11.. SSttaattuuss FFllaaggss + In addition to who sent the message and the subject, a short summary of the disposition of each message is printed beside the message number. Zero or more of the following ``flags'' may appear, which mean: + + + D message is deleted K contains a PGP public key M requires mailcap to view @@ -178,33 +251,51 @@ ! message is flagged * message is tagged + + + Some of the status flags can be turned on or off using +o sseett--ffllaagg (default: w) +o cclleeaarr--ffllaagg (default: W) + + Furthermore, the following flags reflect who the message is addressed to. They can be customized with the ``$to_chars'' variable. + + + + message is to you and you only T message is to you, but also to or cc'ed to others C message is cc'ed to you F message is from you + + + + 22..33..22.. TThhee PPaaggeerr + By default, Mutt uses its builtin pager to display the body of messages. The pager is very similar to the Unix program _l_e_s_s though not nearly as featureful. + + go down one line display the next page (or next message if at the end of a message) - go back to the previous page n display the next message ? show keybindings / search for a regular expression (pattern) - \ toggle search pattern coloring + \ toggle search pattern coloring + + + In addition, many of the functions from the _i_n_d_e_x are available in the pager, such as _d_e_l_e_t_e_-_m_e_s_s_a_g_e or _c_o_p_y_-_m_e_s_s_a_g_e (this is one advantage @@ -223,6 +314,20 @@ for character attributes. Mutt translates them into the correct color and character settings. The sequences Mutt supports are: + + + + + + + + + + + + + + ESC [ Ps;Ps;Ps;...;Ps m where Ps = 0 All Attributes Off @@ -243,17 +348,23 @@ 6 cyan 7 white + + + Mutt uses these attributes for handling text/enriched messages, and they can also be used by an external ``autoview'' script for highlighting purposes. NNoottee:: If you change the colors for your display, for example by changing the color associated with color2 for your xterm, then that color will be used instead of green. + 22..33..33.. TThhrreeaaddeedd MMooddee When the mailbox is ``sorted'' by _t_h_r_e_a_d_s, there are a few additional functions available in the _i_n_d_e_x and _p_a_g_e_r modes. + + ^D delete-thread delete all messages in the current thread ^U undelete-thread undelete all messages in the current thread ^N next-thread jump to the start of the next thread @@ -266,8 +377,12 @@ ESC r read-subthread mark the current subthread as read ESC t tag-thread toggle the tag on the current thread + + + See also: ``$strict_threads''. + 22..33..44.. MMiisscceellllaanneeoouuss FFuunnccttiioonnss ccrreeaattee--aalliiaass (default: a) @@ -278,11 +393,13 @@ NNoottee:: Specifying an ``$alias_file'' does not add the aliases specified there-in, you must also ``source'' the file. + ddiissppllaayy--hheeaaddeerrss (default: h) Toggles the weeding of message header fields specified by ``ignore'' commands. + eenntteerr--ccoommmmaanndd (default: ``:'') This command is used to execute any command you would normally put in @@ -290,17 +407,20 @@ variables, or in conjunction with ``macros'' to change settings on the fly. + eexxttrraacctt--kkeeyyss (default: ESC k) This command extracts PGP public keys from the current or tagged message(s) and adds them to your ``$pgp_v2_pubring'' or ``$pgp_v5_pubring'' depending on ``$pgp_key_version''. + ffoorrggeett--ppaasssspphhrraassee (default: ^F) This command wipes the PGP passphrase from memory. It is useful, if you misspelled the passphrase. + lliisstt--rreeppllyy (default: L) Reply to the current or tagged message(s) by extracting any addresses @@ -335,11 +455,16 @@ This function will go to the next line of non-quoted text which come after a line of quoted text in the internal pager. + 22..44.. SSeennddiinngg MMaaiill + + The following bindings are available in the _i_n_d_e_x for sending messages. + + m compose compose a new message r reply reply to sender g group-reply reply to all recipients @@ -348,6 +473,9 @@ b bounce bounce (remail) message ESC k mail-key mail a PGP public key to someone + + + Bouncing a message sends the message as is to the recipient you specify. Forwarding a message allows you to add comments or modify the message you are forwarding. Bouncing a message uses the @@ -375,6 +503,8 @@ Once you have finished editing the body of your mail message, you are returned to the _c_o_m_p_o_s_e menu. The following options are available: + + a attach-file attach a file ESC k attach-key attach a PGP public key d edit-description edit description on attachment @@ -391,6 +521,11 @@ i ispell check spelling (if available on your system) ^F forget-passphrase whipe PGP passphrase from memory + + + + + 22..44..11.. EEddiittiinngg tthhee mmeessssaaggee hheeaaddeerr When editing the header of your outgoing message, there are a couple @@ -419,8 +554,10 @@ Also see ``edit_headers''. + 22..55.. PPoossttppoonniinngg MMaaiill + At times it is desirable to delay sending a message that you have already begun to compose. When the _p_o_s_t_p_o_n_e_-_m_e_s_s_a_g_e function is used in the _c_o_m_p_o_s_e menu, the body of your message and attachments are @@ -442,8 +579,10 @@ See also the ``$postpone'' quad-option. + 33.. CCoonnffiigguurraattiioonn + 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 @@ -464,16 +603,32 @@ number is the same which is visible using the ``-v'' ``command line'' switch or using the show-version key (default: V) from the index menu. + 33..11.. SSyynnttaaxx ooff IInniittiiaalliizzaattiioonn FFiilleess - An initialization file consists of a series of ``commands'', each on - its own line. The hash mark, or pound sign (``#''), is used as a - ``comment'' character. You can use it to annotate your initialization - file. All text after the comment character to the end of the line is - ignored. For example, + + An initialization file consists of a series of ``commands''. Each + line of the file may contain one or more commands. When multiple + commands are used, they must be separated by a semicolon (;). + + + set realname='Mutt user' ; ignore x- + + + + + The hash mark, or pound sign (``#''), is used as a ``comment'' charac- + ter. You can use it to annotate your initialization file. All text + after the comment character to the end of the line is ignored. For + example, + + my_hdr X-Disclaimer: Why are you listening to me? # This is a comment + + + Single quotes (') and double quotes (") can be used to quote strings which contain spaces or other special characters. The difference between the two types of quotes is similar to that of many popular @@ -489,8 +644,12 @@ use ``\'' to force the next character to be a literal instead of interpreted character. + set realname="Michael \"MuttDude\" Elkins" + + + ``\\'' means to insert a literal ``\'' into the line. ``\n'' and ``\r'' have their usual C meanings of linefeed and carriage-return, respectively. @@ -503,8 +662,12 @@ initialization file. This is accomplished by enclosing the command in backquotes (``). For example, + my_hdr X-Operating-System: `uname -a` + + + The output of the Unix command ``uname -a'' will be substituted before the line is parsed. Note that since initialization files are line oriented, only the first line of output from the Unix command will be @@ -513,8 +676,10 @@ For a complete list of the commands understood by mutt, see the ``command reference''. + 33..22.. DDeeffiinniinngg//UUssiinngg aalliiaasseess + Usage: alias _k_e_y _a_d_d_r_e_s_s [ , _a_d_d_r_e_s_s, ... ] It's usually very cumbersome to remember or type out the address of @@ -529,9 +694,14 @@ unalias _a_d_d_r [ _a_d_d_r _._._. ] + + alias muttdude me@cs.hmc.edu (Michael Elkins) alias theguys manny, moe, jack + + + Unlike other mailers, Mutt doesn't require aliases to be defined in a special file. The alias command can appear anywhere in a configuration file, as long as this file is ``sourced''. @@ -547,10 +717,13 @@ For example: + + source /usr/local/share/Mutt.aliases source ~/.mail_aliases set alias_file=~/.mail_aliases + To use aliases, you merely use the alias at any place in mutt where mutt prompts for addresses, such as the _T_o_: or _C_c_: prompt. You can also enter aliases in your editor at the appropriate headers if you @@ -567,6 +740,7 @@ _s_e_l_e_c_t_-_e_n_t_r_y key (default: RET), and use the _e_x_i_t key (default: q) to return to the address prompt. + 33..33.. CChhaannggiinngg tthhee ddeeffaauulltt kkeeyy bbiinnddiinnggss Usage: bind _m_a_p _k_e_y _f_u_n_c_t_i_o_n @@ -577,6 +751,7 @@ _m_a_p specifies in which menu the binding belongs. The currently defined maps are: + +o generic +o alias @@ -607,10 +782,18 @@ In addition, _k_e_y may consist of: - \t tab - \r carriage return - \n newline - \e escape + + + + + + + + + \t tab + \r carriage return + \n newline + \e escape up up arrow down down arrow left left arrow @@ -626,6 +809,9 @@ f1 function key 1 f10 function key 10 + + + _k_e_y does not need to be enclosed in quotes unless it contains a space (`` ''). @@ -633,6 +819,7 @@ complete list of functions, see the ``reference''. The special function noop unbinds the specify key sequence. + 33..44.. SSeettttiinngg vvaarriiaabblleess bbaasseedd uuppoonn mmaaiillbbooxx Usage: folder-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d @@ -653,12 +840,20 @@ For example, a command action to perform is to change the sorting method based upon the mailbox being read: + + folder-hook mutt set sort=threads + + + However, the sorting method is not restored to its previous value when reading a different mailbox. To specify a _d_e_f_a_u_l_t command, use the pattern ``.'': + + + folder-hook . set sort=date-sent 33..55.. KKeeyybbooaarrdd mmaaccrrooss @@ -679,9 +874,12 @@ NNoottee:: Macro definitions (if any) listed in the help screen(s), are silently truncated at the screen width, and are not wrapped. + 33..66.. UUssiinngg ccoolloorr aanndd mmoonnoo vviiddeeoo aattttrriibbuutteess Usage: color _o_b_j_e_c_t _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d [ _r_e_g_e_x_p ] + Usage: color index _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d [ _p_a_t_t_e_r_n ] + Usage: uncolor index _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] If your terminal supports color, you can spice up Mutt by creating your own color scheme. To define the color of an object (type of @@ -691,6 +889,7 @@ _o_b_j_e_c_t can be one of: + +o attachment +o body (match _r_e_g_e_x_p in the body of messages) @@ -703,6 +902,8 @@ +o hdrdefault (default color of the message header in the pager) + +o index (match _p_a_t_t_e_r_n in the message index) + +o indicator (arrow or bar used to indicate the current item in a menu) @@ -732,6 +933,7 @@ _f_o_r_e_g_r_o_u_n_d and _b_a_c_k_g_r_o_u_n_d can be one of the following: + +o white +o black @@ -761,12 +963,23 @@ _C_O_L_O_R_F_G_B_G environment variable to the default colors of your terminal for this to work; for example (for Bourne-like shells): + + set COLORFGBG="green;black" export COLORFGBG + + + NNoottee:: The _S_-_L_a_n_g library requires you to use the _l_i_g_h_t_g_r_a_y and _b_r_o_w_n keywords instead of _w_h_i_t_e and _y_e_l_l_o_w when setting this variable. + NNoottee:: The uncolor command can be applied to the index object only. It + removes entries from the list. You mmuusstt specify the same pattern + specified in the color command for it to be removed. The pattern + ``*'' is a special token which means to clear the color index list of + all entries. + Mutt also recognizes the keywords _c_o_l_o_r_0, _c_o_l_o_r_1, ..., _c_o_l_o_rNN--11 (NN being the number of colors supported by your terminal). This is useful when you remap the colors for your display (for example by @@ -775,11 +988,11 @@ If your terminal does not support color, it is still possible change the video attributes through the use of the ``mono'' command: - Usage: mono _<_o_b_j_e_c_t_> _<_a_t_t_r_i_b_u_t_e_> [ _r_e_g_e_x_p ] where _a_t_t_r_i_b_u_t_e is one of the following: + +o none +o bold @@ -790,6 +1003,7 @@ +o standout + 33..77.. IIggnnoorriinngg ((wweeeeddiinngg)) uunnwwaanntteedd mmeessssaaggee hheeaaddeerrss Usage: [un]ignore _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] @@ -812,12 +1026,17 @@ For example: + # Sven's draconian header weeding ignore * unignore from date subject to cc unignore organization organisation x-mailer: x-newsreader: x-mailing-list: unignore posted-to: + + + + 33..88.. MMaaiilliinngg lliissttss Usage: [un]lists _a_d_d_r_e_s_s [ _a_d_d_r_e_s_s ... ] @@ -834,9 +1053,11 @@ Mutt that this is a mailing list, you would add ``lists mutt-users'' to your initialization file. + The ``unlists'' command is to remove a token from the list of mailing- lists. Use ``unlists *'' to remove all tokens. + 33..99.. UUssiinngg MMuullttiippllee ssppooooll mmaaiillbbooxxeess Usage: mbox-hook [!]_p_a_t_t_e_r_n _m_a_i_l_b_o_x @@ -851,6 +1072,7 @@ pattern is used (it is not possible to save read mail in more than a single mailbox). + 33..1100.. DDeeffiinniinngg mmaaiillbbooxxeess wwhhiicchh rreecceeiivvee mmaaiill Usage: mailboxes [!]_f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ] @@ -872,12 +1094,14 @@ which accesses the mailbox might cause Mutt to never detect new mail for that mailbox if they do not properly reset the access time. + NNoottee:: the filenames in the mailboxes command are resolved when the command is executed, so if these names contain ``shortcut characters'' (such as ``='' and ``!''), any variable definition that affect these characters (like ``$folder'' and ``$spool'') should be executed before the mailboxes command. + 33..1111.. UUsseerr ddeeffiinneedd hheeaaddeerrss Usage: @@ -890,8 +1114,10 @@ For example, if you would like to add an ``Organization:'' header field to all of your outgoing messages, you can put the command + my_hdr Organization: A Really Big Company, Anytown, USA + in your .muttrc. NNoottee:: space characters are _n_o_t allowed between the keyword and the @@ -902,13 +1128,17 @@ should either set the ``edit_headers'' variable, or use the _e_d_i_t_- _h_e_a_d_e_r_s function (default: ``E'') in the send-menu so that you can edit the header of your message along with the body. + To remove user defined header fields, use the ``unmy_hdr'' command. You may specify an asterisk (``*'') to remove all header fields, or the fields to remove. For example, to remove all ``To'' and ``Cc'' header fields, you could use: + unmy_hdr to cc + + 33..1122.. DDeeffiinniinngg tthhee oorrddeerr ooff hheeaaddeerrss wwhheenn vviieewwiinngg mmeessssaaggeess Usage: hdr_order _h_e_a_d_e_r_1 _h_e_a_d_e_r_2 _h_e_a_d_e_r_3 @@ -916,8 +1146,14 @@ With this command, you can specify an order in which mutt will attempt to present headers to you when viewing messages. + + hdr_order From Date: From: To: Cc: Subject: + + + + 33..1133.. SSppeecciiffyy ddeeffaauulltt ssaavvee ffiilleennaammee Usage: save-hook [!]_r_e_g_e_x_p _f_i_l_e_n_a_m_e @@ -932,11 +1168,17 @@ Examples: + + save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins save-hook aol\\.com$ +spam + + + Also see the ``fcc-save-hook'' command. + 33..1144.. SSppeecciiffyy ddeeffaauulltt FFcccc:: mmaaiillbbooxx wwhheenn ccoommppoossiinngg Usage: fcc-hook [!]_r_e_g_e_x_p _m_a_i_l_b_o_x @@ -956,6 +1198,7 @@ to the `+spammers' mailbox by default. Also see the ``fcc-save-hook'' command. + 33..1155.. SSppeecciiffyy ddeeffaauulltt ssaavvee ffiilleennaammee aanndd ddeeffaauulltt FFcccc:: mmaaiillbbooxx aatt oonnccee Usage: fcc-save-hook [!]_r_e_g_e_x_p _m_a_i_l_b_o_x @@ -963,6 +1206,7 @@ This command is a shortcut, equivalent to doing both a ``fcc-hook'' and a ``save-hook'' with its arguments. + 33..1166.. CChhaannggee sseettttiinnggss bbaasseedd uuppoonn mmeessssaaggee rreecciippiieennttss Usage: send-hook [!]_r_e_g_e_x_p _c_o_m_m_a_n_d @@ -976,7 +1220,7 @@ See ``matching messages'' for information on the exact format of _r_e_g_e_x_p. - Example: send-hook mutt "set mime_fwd signature=''" + Example: send-hook mutt "set mime_forward signature=''" Another typical use for this command is to change the values of the ``$attribution'', ``$signature'' and ``$locale'' variables in order to @@ -987,6 +1231,7 @@ list of recipients. Adding a recipient after replying or editing the message will NOT cause any send-hook to be executed. + 33..1177.. AAddddiinngg kkeeyy sseeqquueenncceess ttoo tthhee kkeeyybbooaarrdd bbuuffffeerr Usage: push _s_t_r_i_n_g @@ -995,6 +1240,7 @@ use it to automatically run a sequence of commands at startup, or when entering certain folders. + 33..1188.. MMeessssaaggee SSccoorriinngg Usage: score _p_a_t_t_e_r_n _v_a_l_u_e @@ -1013,6 +1259,7 @@ removed. The pattern ``*'' is a special token which means to clear the list of all score entries. + 33..1199.. SSeettttiinngg vvaarriiaabblleess Usage: set [no|inv]_v_a_r_i_a_b_l_e[=_v_a_l_u_e] [ _v_a_r_i_a_b_l_e ... ] @@ -1055,8 +1302,13 @@ value of a variable by prefixing the name of the variable with a question mark: + + set ?allow_8bit + + + The question mark is actually only required for boolean variables. The reset command resets all given variables to the compile time @@ -1066,7 +1318,6 @@ With the reset command there exists the special variable ``all'', which allows you to reset all variables to their system defaults. - 33..2200.. RReeaaddiinngg iinniittiiaalliizzaattiioonn ccoommmmaannddss ffrroomm aannootthheerr ffiillee Usage: source _f_i_l_e_n_a_m_e @@ -1079,6 +1330,11 @@ If the filename begins with a tilde (``~''), it will be expanded to the path of your home directory. + If the filename ends with a vertical bar (|), then _f_i_l_e_n_a_m_e is + considered to be an executable program from which to read input (eg. + source ~bin/myscript|/. + + 44.. AAddvvaanncceedd UUssaaggee 44..11.. SSeeaarrcchhiinngg aanndd RReegguullaarr EExxpprreessssiioonnss @@ -1095,6 +1351,7 @@ command: ``\\''. For more information, see the section on ``searching'' below. + 44..11..11.. RReegguullaarr EExxpprreessssiioonnss A regular expression is a pattern that describes a set of strings. @@ -1179,6 +1436,7 @@ character, as well as several characters that are equivalent for collating or sorting purposes: + CCoollllaattiinngg SSyymmbboollss A collating symbols is a multi-character collating element enclosed in ``[.'' and ``.]''. For example, if ``ch'' is a @@ -1192,10 +1450,10 @@ and ``=]''. For example, the name ``e'' might be used to represent all of ``e'' ``e'' and ``e''. In this case, [[[[==ee==]]]] is a regexp that matches any of ``e'', ``e'' and ``e''. - A regular expression matching a single character may be followed by one of several repetition operators: + ?? The preceding item is optional and matched at most once. ** The preceding item will be matched zero or more times. @@ -1230,6 +1488,7 @@ NNoottee:: If you compile Mutt with the GNU _r_x package, the following operators may also be used in regular expressions: + \\yy Matches the empty string at either the beginning or the end of a word. @@ -1252,51 +1511,64 @@ they may or may not be available in stock libraries on various systems. + 44..11..22.. SSeeaarrcchhiinngg Many of Mutt's commands allow you to specify a pattern to match (limit, tag-pattern, delete-pattern, etc.). There are several ways to select messages: - ~A all messages - ~b PATTERN messages which contain PATTERN in the message body - ~c USER messages carbon-copied to USER - ~C PATTERN message is either to: or cc: PATTERN - ~D deleted messages - ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range - ~E expired messages - ~e PATTERN message which contains PATTERN in the ``Sender'' field - ~F flagged messages - ~f USER messages originating from USER - ~h PATTERN messages which contain PATTERN in the message header - ~i ID message which match ID in the ``Message-ID'' field - ~L PATTERN message is either originated or recieved by PATTERN - ~l message is addressed to a known mailing list - ~m [MIN]-[MAX] message in the range MIN to MAX - ~n [MIN]-[MAX] messages with a score in the range MIN to MAX - ~N new messages - ~O old messages - ~p message is addressed to you (consults $alternates) - ~P message is from you (consults $alternates) - ~Q messages which have been replied to - ~R read messages - ~r [MIN]-[MAX] messages with ``date-received'' in a Date range - ~S superseded messages - ~s SUBJECT messages having SUBJECT in the ``Subject'' field. - ~T tagged messages - ~t USER messages addressed to USER - ~U unread messages - ~x PATTERN messages which contain PATTERN in the `References' field - Where PATTERN, USER, ID, and SUBJECT are ``regular expressions''. - 44..11..33.. CCoommpplleexx SSeeaarrcchheess + ~A all messages + ~b PATTERN messages which contain PATTERN in the message body + ~c USER messages carbon-copied to USER + ~C PATTERN message is either to: or cc: PATTERN + ~D deleted messages + ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range + ~E expired messages + ~e PATTERN message which contains PATTERN in the ``Sender'' field + ~F flagged messages + ~f USER messages originating from USER + ~h PATTERN messages which contain PATTERN in the message header + ~i ID message which match ID in the ``Message-ID'' field + ~L PATTERN message is either originated or received by PATTERN + ~l message is addressed to a known mailing list + ~m [MIN]-[MAX] message in the range MIN to MAX + ~n [MIN]-[MAX] messages with a score in the range MIN to MAX + ~N new messages + ~O old messages + ~p message is addressed to you (consults $alternates) + ~P message is from you (consults $alternates) + ~Q messages which have been replied to + ~R read messages + ~r [MIN]-[MAX] messages with ``date-received'' in a Date range + ~S superseded messages + ~s SUBJECT messages having SUBJECT in the ``Subject'' field. + ~T tagged messages + ~t USER messages addressed to USER + ~U unread messages + ~x PATTERN messages which contain PATTERN in the `References' field + + + + + Where PATTERN, USER, ID, and SUBJECT are ``regular expressions''. + + + 44..11..33.. CCoommpplleexx SSeeaarrcchheess + + + Logical AND is performed by specifying more than one criterion. For + example: + - Logical AND is performed by specifying more than one criterion. For - example: ~t mutt ~f elkins + + + would select messages which contain the word ``mutt'' in the list of recipients aanndd that have the word ``elkins'' in the ``From'' header field. @@ -1304,17 +1576,26 @@ Mutt also recognizes the following operators to create more complex search patterns: + +o ! -- logical NOT operator +o | -- logical OR operator + +o () -- logical grouping operator Here is an example illustrating a complex search pattern. This pattern will select all messages which do not contain ``mutt'' in the ``To'' or ``Cc'' field and which are from ``elkins''. + + + !(~t mutt|~c mutt) ~f elkins + + + + 44..11..44.. SSeeaarrcchhiinngg bbyy DDaattee Mutt supports two types of dates, _a_b_s_o_l_u_t_e and _r_e_l_a_t_i_v_e. @@ -1323,8 +1604,13 @@ optional, defaulting to the current month and year). An example of a valid range of dates is: + + Limit to messages matching: ~d 20/1/95-31/10 + + + If you omit the minimum (first) date, and just specify ``-DD/MM/YY'', all messages _b_e_f_o_r_e the given date will be selected. If you omit the maximum (second) date, and specify ``DD/MM/YY-'', all messages _a_f_t_e_r @@ -1348,17 +1634,23 @@ w weeks d days + + Example: to select messages less than 1 month old, you would use + Limit to messages matching: ~d <1m + + + NNoottee:: all dates used when searching are relative to the llooccaall time - zone, so unless you change the setting of your ``$header_format'' to + zone, so unless you change the setting of your ``$index_format'' to include a %[...] format, these are nnoott the dates shown in the main index. - 44..22.. UUssiinngg TTaaggss + Sometimes it is desirable to perform an operation on a group of messages all at once rather than one at a time. An example might be to save messages to a mailing list to a separate folder, or to delete @@ -1376,6 +1668,7 @@ applies to the tagged messages automatically, without requiring the ``tag-prefix''. + 44..33.. UUssiinngg HHooookkss A _h_o_o_k is a concept borrowed from the EMACS editor which allows you to @@ -1399,6 +1692,7 @@ for specific details on each type of _h_o_o_k available. + 44..33..11.. MMeessssaaggee MMaattcchhiinngg iinn HHooookkss Hooks that act upon messages (send-hook, save-hook, fcc-hook) are @@ -1416,8 +1710,10 @@ For example, if you wanted to set your return address based upon sending mail to a specific address, you could do something like: + send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User ' + which would execute the given command when sending mail to _m_e_@_c_s_._h_m_c_._e_d_u. @@ -1429,6 +1725,7 @@ time the hook is declared, so the value of ``$dfault_hook'' that is in effect at that time will be used. + 44..44.. EExxtteerrnnaall AAddddrreessss QQuueerriieess Mutt supports connecting to external directory databases such as LDAP, @@ -1436,8 +1733,13 @@ using a simple interface. Using the ``$query_command'' variable, you specify the wrapper command to use. For example: + + set query_command = "mutt_ldap_query.pl '%s'" + + + The wrapper script should accept the query on the command-line. It should return a one line message, than each matching response on a single line, each line containing a tab separated address then name @@ -1447,11 +1749,15 @@ An example multiple response output: + Searching database ... 20 entries ... 3 matching: me@cs.hmc.edu Michael Elkins mutt dude blong@fiction.net Brandon Long mutt and more roessler@guug.de Thomas Roessler mutt pgp + + + There are two mechanisms for accessing the query function of mutt. One is to do a query from the index menu using the query function (default: Q). This will prompt for a query, then bring up the query @@ -1470,6 +1776,10 @@ will activate the query menu. At the query menu, you can select one or more addresses to be added to the prompt. + + + + 44..55.. MMaaiillbbooxx FFoorrmmaattss Mutt supports reading and writing of four different mailbox formats: @@ -1482,8 +1792,13 @@ messages are stored in a single file. Each message has a line of the form: + + From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST + + + to denote the start of a new message (this is often referred to as the ``From_'' line). @@ -1506,12 +1821,14 @@ programs are writing the mailbox over NFS, which means that no file locking is needed. + 44..66.. MMaaiillbbooxx SShhoorrttccuuttss There are a number of built in shortcuts which refer to specific mailboxes. These shortcuts can be used anywhere you are prompted for a file or mailbox path. + +o ! -- refers to your ``$spool'' (incoming) mailbox +o > -- refers to your ``$mbox'' file @@ -1524,8 +1841,11 @@ +o = or + -- refers to your ``$folder'' directory + 44..77.. HHaannddlliinngg MMaaiilliinngg LLiissttss + + Mutt has a few configuration options that make dealing with large amounts of mail easier. The first thing you must do is to let Mutt know what addresses you consider to be mailing lists (technically this @@ -1536,11 +1856,10 @@ Now that Mutt knows what your mailing lists are, it can do several things, the first of which is the ability to show the list name in the _i_n_d_e_x menu display. This is useful to distinguish between personal - and list mail in the same mailbox. In the ``$header_format'' - variable, the escape ``%L'' will return the string ``To '' when - ``list'' appears in the ``To'' field, and ``Cc '' when it - appears in the ``Cc'' field (otherwise it returns the name of the - author). + and list mail in the same mailbox. In the ``$index_format'' variable, + the escape ``%L'' will return the string ``To '' when ``list'' + appears in the ``To'' field, and ``Cc '' when it appears in the + ``Cc'' field (otherwise it returns the name of the author). Often times the ``To'' and ``Cc'' fields in mailing list messages tend to get quite large. Most people do not bother to remove the author of @@ -1569,6 +1888,7 @@ dealing with large volume mailing lists easier because you can easily delete uninteresting threads and quickly find topics of value. + 44..88.. DDeelliivveerryy SSttaattuuss NNoottiiffiiccaattiioonn ((DDSSNN)) SSuuppppoorrtt RFC1894 defines a set of MIME content types for relaying information @@ -1583,8 +1903,10 @@ message should be returned with the receipt (headers or full message). Refer to the man page on sendmail for more details on DSN. + 44..99.. PPOOPP33 SSuuppppoorrtt ((OOPPTTIIOONNAALL)) + If Mutt was compiled with POP3 support (by running the _c_o_n_f_i_g_u_r_e script with the _-_-_e_n_a_b_l_e_-_p_o_p flag), it has the ability to fetch your mail from a remote server for local browsing. When you invoke the @@ -1596,10 +1918,12 @@ Once you have been authenticated, Mutt will fetch all your new mail and place it in the local ``spoolfile''. After this point, Mutt runs exactly as if the mail had always been local. + NNoottee:: The POP3 support is there only for convenience, and it's rather limited. If you need more functionality you should consider using a specialized program, such as fetchmail + 55.. MMuutttt''ss MMIIMMEE SSuuppppoorrtt Quite a bit of effort has been made to make Mutt the premier text-mode @@ -1611,12 +1935,14 @@ IANA MIME types. The other is the mailcap file, which specifies the external commands to use for handling specific MIME types. + 55..11.. UUssiinngg MMIIMMEE iinn MMuutttt There are three areas/menus in Mutt which deal with MIME, they are the pager (while viewing a message), the attachment menu and the compose menu. + 55..11..11.. VViieewwiinngg MMIIMMEE mmeessssaaggeess iinn tthhee ppaaggeerr When you select a message from the index and view it in the pager, @@ -1629,17 +1955,29 @@ Mutt will denote attachments with a couple lines describing them. These lines are of the form: + [-- Attachment #1: Description --] [-- Type: text/plain, Encoding: 7bit, Size: 10000 --] + + + Where the Description is the description or filename given for the attachment, and the Encoding is one of 7bit/8bit/quoted-print- able/base64/binary. If Mutt cannot deal with a MIME type, it will display a message like: + [-- image/gif is unsupported (use 'v' to view this part) --] + + + + + + + 55..11..22.. TThhee AAttttaacchhmmeenntt MMeennuu The default binding for view-attachments is `v', which displays the @@ -1654,6 +1992,7 @@ viewer definition. See the help on the attachment menu for more information. + 55..11..33.. TThhee CCoommppoossee MMeennuu The compose menu is the menu you see before you send a message. It @@ -1669,6 +2008,8 @@ - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz + + The '-' denotes that Mutt will delete the file after sending the message. It can be toggled with the toggle-unlink command (default: u). The next field is the MIME content-type, and can be changed with @@ -1681,7 +2022,8 @@ final field is the description of the attachment, and can be changed with the edit-description command (default: d). - 55..22.. MMIIMMEE TTyyppee ccoonnffiigguurraattiioonn wwiitthh mime.types + + 55..22.. MMIIMMEE TTyyppee ccoonnffiigguurraattiioonn wwiitthh mmiimmee..ttyyppeess When you add an attachment to your mail message, Mutt searches your personal mime.types file at ${HOME}/.mime.types, and then the system @@ -1692,13 +2034,16 @@ The mime.types file consist of lines containing a MIME type and a space separated list of extensions. For example: + application/postscript ps eps application/pgp pgp audio/x-aiff aif aifc aiff + + + A sample mime.types file comes with the Mutt distribution, and should contain most of the MIME types you are likely to use. - If Mutt can not determine the mime type by the extension of the file you attach, it will look at the file. If the file is free of binary information, Mutt will assume that the file is plain text, and mark it @@ -1710,7 +2055,8 @@ text, image, video, or audio. If you attempt to use a different major type, Mutt will abort the change. - 55..33.. MMIIMMEE VViieewweerr ccoonnffiigguurraattiioonn wwiitthh mailcap + + 55..33.. MMIIMMEE VViieewweerr ccoonnffiigguurraattiioonn wwiitthh mmaaiillccaapp Mutt supports RFC 1524 MIME Configuration, in particular the Unix specific format specified in Appendix A of RFC 1524. This file format @@ -1724,8 +2070,12 @@ find an external handler. The default search string for these files is a colon delimited list set to + ${HOME}/.mailcap:SHAREDIR/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap + + + where $HOME is your home directory and SHAREDIR is the shared direc- tory defined at compile time (visible from mutt -v). @@ -1733,6 +2083,7 @@ usually as /usr/local/etc/mailcap, which contains some baseline entries. + 55..33..11.. TThhee BBaassiiccss ooff tthhee mmaaiillccaapp ffiillee A mailcap file consists of a series of lines which are comments, @@ -1767,17 +2118,29 @@ So, in the simplest form, you can send a text/plain message to the external pager more on stdin: - text/plain; more + + text/plain; more + + + Or, you could send the message as a file: + text/plain; more %s + + + Perhaps you would like to use lynx to interactively view a text/html message: + text/html; lynx "%s" + + + In this case, lynx does not support viewing a file from stdin, so you must use the %s syntax. NNoottee:: _S_o_m_e _o_l_d_e_r _v_e_r_s_i_o_n_s _o_f _l_y_n_x _c_o_n_t_a_i_n _a _b_u_g _w_h_e_r_e _t_h_e_y _w_i_l_l _c_h_e_c_k _t_h_e _m_a_i_l_c_a_p _f_i_l_e _f_o_r _a _v_i_e_w_e_r _f_o_r _t_e_x_t_/_h_t_m_l_. @@ -1788,18 +2151,31 @@ just want to have it convert the text/html to text/plain, then you can use: + text/html; lynx -dump "%s" | more + + + Perhaps you wish to use lynx to view text/html files, and a pager on all other text formats, then you would use the following: + text/html; lynx "%s" text/*; more + + + This is the simplest form of a mailcap file. + 55..33..22.. AAddvvaanncceedd mmaaiillccaapp UUssaaggee + + + + 55..33..22..11.. OOppttiioonnaall FFiieellddss In addition to the required content-type and view command fields, you @@ -1815,8 +2191,12 @@ use this to replace the pipe to more in the lynx -dump example in the Basic section: + text/html; lynx -dump %s ; copiousoutput + + + This will cause lynx to format the text/html output as text/plain and Mutt will use your standard pager to display the results. @@ -1861,7 +2241,11 @@ file ends in .html. So, you would specify lynx as a text/html viewer with a line in the mailcap file like: - text/html; lynx %s; nametemplate=%s.html + + text/html; lynx %s; nametemplate=%s.html + + + tteesstt==<> This field specifies a command to run to test whether this @@ -1873,9 +2257,13 @@ _c_o_n_t_e_n_t_-_t_y_p_e _m_u_s_t _m_a_t_c_h _b_e_f_o_r_e _M_u_t_t _p_e_r_f_o_r_m_s _t_h_e _t_e_s_t_. For example: + text/html; netscape -remote 'openURL(%s)' ; test=RunningX text/html; lynx %s + + + In this example, Mutt will run the program RunningX which will return 0 if the X Window manager is running, and non-zero if it isn't. If RunningX returns 0, then Mutt will call netscape to dis- @@ -1883,6 +2271,7 @@ will go on to the next entry and use lynx to display the text/html object. + 55..33..22..22.. SSeeaarrcchh OOrrddeerr When searching for an entry in the mailcap file, Mutt will search for @@ -1891,10 +2280,14 @@ in your mailcap file, Mutt will search for an entry with the print command: + image/*; xv %s image/gif; ; print= anytopnm %s | pnmtops | lpr; \ nametemplate=%s.gif + + + Mutt will skip the image/* entry and use the image/gif entry with the print command. @@ -1904,15 +2297,20 @@ can then use the test feature to determine which viewer to use interactively depending on your environment. + text/html; netscape -remote 'openURL(%s)' ; test=RunningX text/html; lynx %s; nametemplate=%s.html text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput + + + For ``Autoview'', Mutt will choose the third entry because of the copiousoutput tag. For interactive viewing, Mutt will run the program - RunningX to determine if it should use the first entry. If the pro- - gram returns non-zero, Mutt will use the second entry for interactive - viewing. + RunningX to determine if it should use the first entry. If the + program returns non-zero, Mutt will use the second entry for interac- + tive viewing. + 55..33..22..33.. CCoommmmaanndd EExxppaannssiioonn @@ -1937,18 +2335,23 @@ from the Content-Type: line of the mail message. For instance, if Your mail message contains: + Content-Type: text/plain; charset=iso-8859-1 + + + then Mutt will expand %{charset} to iso-8859-1. The default meta- mail mailcap file uses this feature to test the charset to spawn an xterm using the right charset to view the message. - \\%% This will be replaced by a % + %% This will be replaced by a % Mutt does not currently support the %F and %n keywords specified in RFC 1524. The main purpose of these parameters is for multipart mes- sages, which is handled internally by Mutt. + 55..33..33.. EExxaammppllee mmaaiillccaapp ffiilleess This mailcap file is fairly simple and standard: @@ -1962,8 +2365,15 @@ text/html; netscape -remote 'openURL(%s)' ______________________________________________________________________ + + This mailcap file shows quite a number of examples: + + + + + ______________________________________________________________________ # Use xanim to view all videos Xanim produces a header on startup, # send that to /dev/null so I don't see it @@ -2006,6 +2416,9 @@ application/ms-excel; open.pl %s ______________________________________________________________________ + + + 55..44.. MMIIMMEE AAuuttoovviieeww In addition to explicitly telling Mutt to view an attachment with the @@ -2022,11 +2435,15 @@ For instance, if you set auto_view to: + auto_view text/html text/enriched application/x-gunzip application/postscript image/gif application/x-tar-gz + + Mutt could use the following mailcap entries to automatically view attachments of these types. + text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html text/enriched; enriched.sh ; copiousoutput image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput @@ -2034,6 +2451,9 @@ application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput application/postscript; ps2ascii %s; copiousoutput + + + 55..55.. MMIIMMEE MMuullttiippaarrtt//AAlltteerrnnaattiivvee Mutt has some heuristics for determining which attachment of a @@ -2043,13 +2463,18 @@ mimetypes in order, including support for implicit and explicit wildcards, for example: + alternative_order text/enriched text/plain text application/postscript image/* + + + Next, mutt will check if any of the types have a defined ``auto_view'', and use that. Failing that, Mutt will look for any text type. As a last attempt, mutt will look for any type it knows how to handle. + 66.. RReeffeerreennccee 66..11.. CCoommmmaanndd lliinnee ooppttiioonnss @@ -2058,6 +2483,8 @@ spool mailbox. However, it is possible to read other mailboxes and to send messages from the command line as well. + + -a attach a file to a message -c specify a carbon-copy (Cc) address -e specify a config command to be run after initilization files are read @@ -2077,6 +2504,8 @@ -z exit immediately if there are no messages in the mailbox -Z open the first folder with new message,exit immediately if none + + To read messages in a mailbox mutt [ -nz ] [ -F _m_u_t_t_r_c ] [ -m _t_y_p_e ] [ -f _m_a_i_l_b_o_x ] @@ -2095,10 +2524,12 @@ subject of ``data set for run #2''. In the body of the message will be the contents of the file ``~/run2.dat''. + 66..22.. CCoonnffiigguurraattiioonn CCoommmmaannddss The following are the commands understood by mutt. + +o ``alias'' _k_e_y _a_d_d_r_e_s_s [ , _a_d_d_r_e_s_s, ... ] +o ``unalias'' _k_e_y _a_d_d_r_e_s_s [ , _a_d_d_r_e_s_s, ... ] @@ -2149,8 +2580,11 @@ +o ``source'' _f_i_l_e_n_a_m_e + 66..33.. CCoonnffiigguurraattiioonn vvaarriiaabblleess + + 66..33..11.. aabboorrtt__nnoossuubbjjeecctt Type: quadoption @@ -2161,6 +2595,7 @@ messages with no subject given at the subject prompt will never be aborted. + 66..33..22.. aabboorrtt__uunnmmooddiiffiieedd Type: quadoption @@ -2171,6 +2606,7 @@ happens after the _f_i_r_s_t edit of the file). When set to _n_o, composition will never be aborted. + 66..33..33.. aalliiaass__ffiillee Type: string @@ -2182,6 +2618,7 @@ NNoottee:: Mutt will not automatically source this file; you must explicitly use the ``source'' command for it to be executed. + 66..33..44.. aalliiaass__ffoorrmmaatt Type: string @@ -2190,11 +2627,17 @@ Specifies the format of the data displayed for the `alias' menu. The following printf(3)-style sequences are available. + %a alias name %n index number %r address which alias expands to %t character which indicates if the alias is tagged for inclusion (*/ ) + + + + + 66..33..55.. aallllooww__88bbiitt Type: boolean @@ -2203,6 +2646,7 @@ Controls whether 8-bit data is converted to 7-bit using either Quoted- Printable or Base64 encoding when sending mail. + 66..33..66.. aalltteerrnnaatteess Type: string @@ -2212,6 +2656,7 @@ receive mail. This affects Mutt's idea about messages from you and addressed to you. + 66..33..77.. aarrrrooww__ccuurrssoorr Type: boolean @@ -2223,6 +2668,7 @@ be redrawn on the screen when moving to the next or previous entries in the menu. + 66..33..88.. aasscciiii__cchhaarrss Type: boolean @@ -2231,6 +2677,7 @@ If set, Mutt will use plain ASCII characters when displaying thread and attachment trees, instead of the default _A_C_S characters. + 66..33..99.. aasskkbbcccc Type: boolean @@ -2239,6 +2686,7 @@ If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients before editing an outgoing message. + 66..33..1100.. aasskkcccc Type: boolean @@ -2247,37 +2695,16 @@ If set, Mutt will prompt you for carbon-copy (Cc) recipients before editing the body of an outgoing message. - 66..33..1111.. aattttaacchh__sseepp - - Type: string - Default: newline - - The separator to add between attachments when piping or saving a list - of tagged attachments to an external Unix command. - - 66..33..1122.. aattttaacchh__sspplliitt - - Type: boolean - Default: set - - Used in connection with the _p_i_p_e_-_e_n_t_r_y and _s_a_v_e_-_e_n_t_r_y commands and the - ``tag-prefix'' operator in the ``attachment'' menu. If this variable - is unset, when piping or saving a list of tagged attachments Mutt will - concatenate the attachments and will pipe or save them as a single - file. The ``attach_sep'' separator will be added after each message. - When set, Mutt will pipe or save the messages one by one. In both - cases the the messages are processed in the displayed order. - 66..33..1133.. aattttrriibbuuttiioonn + 66..33..1111.. aattttrriibbuuttiioonn Type: format string Default: "On %d, %n wrote:" This is the string that will precede a message which has been included in a reply. For a full listing of defined escape sequences see the - section on ``$header_format''. - - 66..33..1144.. aauuttooeeddiitt + section on ``$index_format''. + 66..33..1122.. aauuttooeeddiitt Type: boolean Default: unset @@ -2290,7 +2717,8 @@ If the ``$edit_headers'' variable is also set, the initial prompts in the send-menu are always skipped, even when composing a new message. - 66..33..1155.. aauuttoo__ttaagg + + 66..33..1133.. aauuttoo__ttaagg Type: boolean Default: unset @@ -2300,14 +2728,16 @@ must first use the tag-prefix function (default: ";") to make the next function apply to all tagged messages. - 66..33..1166.. bbeeeepp + + 66..33..1144.. bbeeeepp Type: boolean Default: set When this variable is set, mutt will beep when an error occurs. - 66..33..1177.. bbeeeepp__nneeww + + 66..33..1155.. bbeeeepp__nneeww Type boolean Default: unset @@ -2316,7 +2746,8 @@ notifying you of new mail. This is independent of the setting of the ``beep'' variable. - 66..33..1188.. cchhaarrsseett + + 66..33..1166.. cchhaarrsseett Type: string Default: iso-8859-1 @@ -2326,7 +2757,8 @@ contain 8-bit characters so that receiving parties can display your messages in the correct character set. - 66..33..1199.. cchheecckk__nneeww + + 66..33..1177.. cchheecckk__nneeww Type: boolean Default: set @@ -2338,8 +2770,7 @@ some time since it involves scanning the directory and checking each file to see if it has already been looked at. If _c_h_e_c_k___n_e_w is _u_n_s_e_t, no check for new mail is performed while the mailbox is open. - - 66..33..2200.. ccoonnffiirrmmaappppeenndd + 66..33..1188.. ccoonnffiirrmmaappppeenndd Type: boolean Default: set @@ -2347,7 +2778,8 @@ When set, Mutt will prompt for confirmation when appending messages to an existing mailbox. - 66..33..2211.. ccoonnffiirrmmccrreeaattee + + 66..33..1199.. ccoonnffiirrmmccrreeaattee Type: boolean Default: set @@ -2355,7 +2787,8 @@ When set, Mutt will prompt for confirmation when saving messages to a mailbox which does not yet exist before creating it. - 66..33..2222.. ccooppyy + + 66..33..2200.. ccooppyy Type: quadoption Default: yes @@ -2364,14 +2797,15 @@ will be saved for later references. Also see ``record'', ``save_name'', ``force_name'' and ``fcc-hook''. - 66..33..2233.. ddaattee__ffoorrmmaatt + + 66..33..2211.. ddaattee__ffoorrmmaatt Type: string Default: "!%a, %b %d, %Y at %I:%M:%S%p %Z" This variable controls the format of the date printed by the ``%d'' - sequence in ``$header_format''. This is passed to the _s_t_r_f_t_i_m_e call - to process the date. See the man page for _s_t_r_f_t_i_m_e_(_3_) for the proper + sequence in ``$index_format''. This is passed to the _s_t_r_f_t_i_m_e call to + process the date. See the man page for _s_t_r_f_t_i_m_e_(_3_) for the proper syntax. Unless the first character in the string is a bang (``!''), the month @@ -2381,7 +2815,8 @@ rest of the string are expanded in the _C locale (that is in US English). - 66..33..2244.. ddeeffaauulltt__hhooookk + + 66..33..2222.. ddeeffaauulltt__hhooookk Type: string Default: "~f %s | (~P (~c %s | ~t %s))" @@ -2396,26 +2831,28 @@ ``alternates'') and is to or cc'ed to a user matching the given regular expression. - 66..33..2255.. ddeelleettee + + 66..33..2233.. ddeelleettee Type: quadoption Default: ask-yes - Controls whether or not messages are really deleted when closing or synchronizing a mailbox. If set to _y_e_s, messages marked for deleting will automatically be purged without prompting. If set to _n_o, messages marked for deletion will be kept in the mailbox. - 66..33..2266.. ddeelleettee__ffoorrmmaatt + + 66..33..2244.. ddeelleettee__ffoorrmmaatt Type: string Default: "[-- Attachment from %u deleted on %<%D> --]" This variable controls the format of the message used to replace an attachment when the attachment is deleted. It uses the same format - sequences as the ``$header_format'' variable. + sequences as the ``$index_format'' variable. - 66..33..2277.. ddssnn__nnoottiiffyy + + 66..33..2255.. ddssnn__nnoottiiffyy Type: string Default: none @@ -2431,7 +2868,8 @@ Example: set dsn_notify="failure,delay" - 66..33..2288.. ddssnn__rreettuurrnn + + 66..33..2266.. ddssnn__rreettuurrnn Type: string Default: none @@ -2444,7 +2882,8 @@ Example: set dsn_return=hdrs - 66..33..2299.. eeddiitt__hheeaaddeerrss + + 66..33..2277.. eeddiitt__hheeaaddeerrss Type: boolean Default: unset @@ -2452,21 +2891,35 @@ This option allows you to edit the header of your outgoing messages along with the body of your message. - 66..33..3300.. eeddiittoorr + + 66..33..2288.. eeddiittoorr Type: String Default: value of environment variable $VISUAL, $EDITOR, or "vi" This variable specifies which editor to use when composing messages. - 66..33..3311.. eessccaappee + + + + 66..33..2299.. eemmppttyy__ttoo + + Type: string + Default: undisclosed-recipients + + Specifies the text Mutt inserts in the To: header of a message you're + sending, if the To: and Cc: fields are empty. + + + 66..33..3300.. eessccaappee Type: string Default: ~ Escape character to use for functions in the builtin editor. - 66..33..3322.. ffaasstt__rreeppllyy + + 66..33..3311.. ffaasstt__rreeppllyy Type: boolean Default: unset @@ -2478,7 +2931,8 @@ NNoottee:: this variable has no effect when the ``$autoedit'' variable is set. - 66..33..3333.. ffcccc__aattttaacchh + + 66..33..3322.. ffcccc__aattttaacchh Type: boolean Default: set @@ -2486,7 +2940,8 @@ This variable controls whether or not attachments on outgoing messages are saved along with the main body of your message. - 66..33..3344.. ffoollddeerr + + 66..33..3333.. ffoollddeerr Type: String Default: ~/Mail @@ -2498,7 +2953,8 @@ `+' or `=' for any other variables since expansion takes place during the `set' command. - 66..33..3355.. ffoolllloowwuupp__ttoo + + 66..33..3344.. ffoolllloowwuupp__ttoo Type: boolean Default: set @@ -2512,8 +2968,7 @@ will receive a copy of the message if it is addressed to the mailing list (and thus there is no need to also include your address in a group reply). - - 66..33..3366.. ffoorrccee__nnaammee + 66..33..3355.. ffoorrccee__nnaammee Type: boolean Default: unset @@ -2524,27 +2979,28 @@ Also see the ``$record'' variable. - 66..33..3377.. ffoorrwwaarrdd__ddeeccooddee + + 66..33..3366.. ffoorrwwaarrdd__ddeeccooddee Type: boolean - Default: unset + Default: set Controls the decoding of complex MIME messages into text/plain when - forwarding a message. If ``mime_forward'' is _u_n_s_e_t, then the message - header is also RFC2047 decoded (this cannot be done when forwarding a - message as a message/rfc822 attachment because it would violate the - MIME spec, which states that you must only use US-ASCII in the - header). + forwarding a message and the message header is also RFC2047 decoded. + This variable is only used, if ``mime_forward'' is _u_n_s_e_t, otherwise + ``mime_forward_decode'' is used instead. - 66..33..3388.. ffoorrwwaarrdd__ffoorrmmaatt + + 66..33..3377.. ffoorrwwaarrdd__ffoorrmmaatt Type: format string Default: "[%a: %s]" This variable controls the default subject when forwarding a message. - It uses the same format sequences as the ``$header_format'' variable. + It uses the same format sequences as the ``$index_format'' variable. + - 66..33..3399.. ffoorrwwaarrdd__qquuoottee + 66..33..3388.. ffoorrwwaarrdd__qquuoottee Type: boolean Default: unset @@ -2553,7 +3009,8 @@ (when ``mime_forward'' is _u_n_s_e_t) will be quoted using ``indent_string''. - 66..33..4400.. hheeaaddeerr__ffoorrmmaatt + + 66..33..3399.. iinnddeexx__ffoorrmmaatt Type: format string Default: "%4C %Z %{%b %d} %-15.15L (%4l) %s" @@ -2565,70 +3022,88 @@ function printf to format output (see the man page for more detail). The following sequences are defined in Mutt: - %a address of the author - %b filename of the original message folder (think mailBox) - %B the list to which the letter was sent, or else the folder - name (%b). - %c number of characters (bytes) in the message - %C current message number - %d date and time of the message in the format specified by - ``date_format'' - %f entire From: line (address + real name) - %F author name, or recipient name if the message is from you - %i message-id of the current message - %l number of lines in the message - %L list-from function - %m total number of message in the mailbox - %N message score - %n author's real name (or address if missing) - %O (_O_riginal save folder) Where mutt would formerly have - stashed the message: list name or recipient name if no list - %s subject of the message - %S status of the message (N/D/d/!/*/r) - %t `to:' field (recipients) - %T the appropriate character from the $to_chars string - %u user (login) name of the author - %Z message status flags - - %{fmt} the date and time of the message is converted to sender's - time zone, and ``fmt'' is expanded by the system call - ``strftime''; a leading bang disables locales - %[fmt] the date and time of the message is converted to the local - time zone, and ``fmt'' is expanded by the system call - ``strftime''; a leading bang disables locales - %(fmt) the local date and time when the message was received. - ``fmt'' is expanded by the system call ``strftime''; - a leading bang disables locales - % the current local time. ``fmt'' is expanded by the system - call ``strftime''; a leading bang disables locales. - - %>X right justify the rest of the string and pad with character "X" - %|X pad to the end of the line with character "X" - See also: ``$to_chars''. - 66..33..4411.. hhddrrss - Type: boolean - Default: set - When unset, the header fields normally added by the ``my_hdr'' command - are not created. This variable _m_u_s_t be unset before composing a new - message or replying in order to take effect. If set, the user defined - header fields are added to every new message. - 66..33..4422.. hheeaaddeerr - Type: boolean - Default: unset - When set, this variable causes Mutt to include the _f_u_l_l header of the - message you are replying to into the edit buffer. - 66..33..4433.. hheellpp - Type: boolean - Default: set + + + + %a address of the author + %b filename of the original message folder (think mailBox) + %B the list to which the letter was sent, or else the folder name (%b). + %c number of characters (bytes) in the message + %C current message number + %d date and time of the message in the format specified by + ``date_format'' + %f entire From: line (address + real name) + %F author name, or recipient name if the message is from you + %i message-id of the current message + %l number of lines in the message + %L list-from function + %m total number of message in the mailbox + %N message score + %n author's real name (or address if missing) + %O (_O_riginal save folder) Where mutt would formerly have stashed the + message: list name or recipient name if no list + %s subject of the message + %S status of the message (N/D/d/!/*/r) + %t `to:' field (recipients) + %T the appropriate character from the $to_chars string + %u user (login) name of the author + %Z message status flags + + %{fmt} the date and time of the message is converted to sender's + time zone, and ``fmt'' is expanded by the system call + ``strftime''; a leading bang disables locales + %[fmt] the date and time of the message is converted to the local + time zone, and ``fmt'' is expanded by the system call + ``strftime''; a leading bang disables locales + %(fmt) the local date and time when the message was received. + ``fmt'' is expanded by the system call ``strftime''; + a leading bang disables locales + % the current local time. ``fmt'' is expanded by the system + call ``strftime''; a leading bang disables locales. + + %>X right justify the rest of the string and pad with character "X" + %|X pad to the end of the line with character "X" + + + + + See also: ``$to_chars''. + + + 66..33..4400.. hhddrrss + + Type: boolean + Default: set + + When unset, the header fields normally added by the ``my_hdr'' command + are not created. This variable _m_u_s_t be unset before composing a new + message or replying in order to take effect. If set, the user defined + header fields are added to every new message. + + + 66..33..4411.. hheeaaddeerr + + Type: boolean + Default: unset + + When set, this variable causes Mutt to include the _f_u_l_l header of the + message you are replying to into the edit buffer. + + + + 66..33..4422.. hheellpp + + Type: boolean + Default: set When set, help lines describing the bindings for the major functions provided by each menu are displayed on the first line of the screen. @@ -2639,7 +3114,8 @@ Since this variable is primarily aimed at new users, neither of these should present a major problem. - 66..33..4444.. hhiissttoorryy + + 66..33..4433.. hhiissttoorryy Type: number Default: 10 @@ -2648,7 +3124,8 @@ the string history buffer. The buffer is cleared each time the variable is set. - 66..33..4455.. hhoossttnnaammee + + 66..33..4444.. hhoossttnnaammee Type: string Default: varies @@ -2657,7 +3134,8 @@ addresses. This overrides the compile time definition obtained from /etc/resolv.conf. - 66..33..4466.. iiggnnoorree__lliisstt__rreeppllyy__ttoo + + 66..33..4455.. iiggnnoorree__lliisstt__rreeppllyy__ttoo Type: boolean Default: unset @@ -2670,24 +3148,25 @@ list when this option is set, use the _l_i_s_t_-_r_e_p_l_y function; _g_r_o_u_p_-_r_e_p_l_y will reply to both the sender and the list. - 66..33..4477.. iinn__rreeppllyy__ttoo + + 66..33..4466.. iinn__rreeppllyy__ttoo Type: format string Default: "%i; from \"%n\" on %{!%a, %b %d, %Y at %I:%M:%S%p}" This specifies the format of the In-Reply-To: header field added when replying to a message. For a full listing of defined escape sequences - see the section on ``$header_format''. + see the section on ``$index_format''. + - 66..33..4488.. iinncclluuddee + 66..33..4477.. iinncclluuddee Type: quadoption Default: ask-yes Controls whether or not a copy of the message(s) you are replying to is included in your reply. - - 66..33..4499.. iinnddeenntt__ssttrriinngg + 66..33..4488.. iinnddeenntt__ssttrriinngg Type: format string Default: "> " @@ -2696,14 +3175,16 @@ message to which you are replying. You are strongly encouraged not to change this value, as it tends to agitate the more fanatical netizens. - 66..33..5500.. iissppeellll + + 66..33..4499.. iissppeellll Type: string Default: "ispell" How to invoke ispell (GNU's spell-checking software). - 66..33..5511.. llooccaallee + + 66..33..5500.. llooccaallee Type: string Default: "C" @@ -2711,7 +3192,8 @@ The locale used by _s_t_r_f_t_i_m_e_(_3_) to format dates. Legal values are the strings your system accepts for the locale variable _L_C___T_I_M_E. - 66..33..5522.. mmaaiillccaapp__ppaatthh + + 66..33..5511.. mmaaiillccaapp__ppaatthh Type: string Default: $MAILCAPS or @@ -2720,7 +3202,8 @@ This variable specifies which files to consult when attempting to display MIME bodies not directly supported by Mutt. - 66..33..5533.. mmaarrkk__oolldd + + 66..33..5522.. mmaarrkk__oolldd Type: Boolean Default: set @@ -2733,7 +3216,8 @@ make Mutt treat all unread messages as new only, you can unset this variable. - 66..33..5544.. mmaarrkkeerrss + + 66..33..5533.. mmaarrkkeerrss Type: boolean Default: set @@ -2742,7 +3226,8 @@ ``+'' marker is displayed at the beginning of wrapped lines. Also see the ``$smart_wrap'' variable. - 66..33..5555.. mmaasskk + + 66..33..5544.. mmaasskk Type: string Default: "^(\.\.$|[^.])" @@ -2750,7 +3235,8 @@ A regular expression used in the file browser. Files whose names don't match this mask will not be shown. - 66..33..5566.. mmbbooxx + + 66..33..5555.. mmbbooxx Type: String Default: +inbox @@ -2758,7 +3244,8 @@ This specifies the folder into which read mail in your ``spoolfile'' folder will be appended. - 66..33..5577.. mmbbooxx__ttyyppee + + 66..33..5566.. mmbbooxx__ttyyppee Type: String Default: mbox @@ -2766,7 +3253,8 @@ The default mailbox type used when creating new folders. May be any of mbox, MMDF, MH and Maildir. - 66..33..5588.. mmeettoooo + + 66..33..5577.. mmeettoooo Type: boolean Default: unset @@ -2776,7 +3264,8 @@ you, Mutt will also assume that you want to reply to the recipients of that message rather than to yourself. - 66..33..5599.. mmeennuu__ssccrroollll + + 66..33..5588.. mmeennuu__ssccrroollll Type: boolean Default: unset @@ -2786,7 +3275,8 @@ the next or previous page of the menu is displayed (useful for slow links to avoid many redraws). - 66..33..6600.. mmeettaa__kkeeyy + + 66..33..5599.. mmeettaa__kkeeyy Type: Boolean Default: unset @@ -2798,7 +3288,9 @@ pressed ESC then ``x''. This is because the result of removing the high bit from ``0xf4'' is ``0x74'', which is the ASCII character ``x''. - 66..33..6611.. mmiimmee__ffoorrwwaarrdd + + + 66..33..6600.. mmiimmee__ffoorrwwaarrdd Type: boolean Default: unset @@ -2808,7 +3300,18 @@ message. This is useful for forwarding MIME messages so the receiver can properly view the message as it was delivered to you. - Also see ``forward_decode''. + Also see ``forward_decode'' and ``mime_forward_decode''. + + + 66..33..6611.. mmiimmee__ffoorrwwaarrdd__ddeeccooddee + + Type: boolean + Default: unset + + Controls the decoding of complex MIME messages into text/plain when + forwarding a message while ``mime_forward'' is _s_e_t. Otherwise + ``forward_decode'' is used instead. + 66..33..6622.. mmoovvee @@ -2819,6 +3322,7 @@ from your spool mailbox to your ``$mbox'' mailbox, or as a result of a ``mbox-hook'' command. + 66..33..6633.. mmeessssaaggee__ffoorrmmaatt Type: string @@ -2826,7 +3330,8 @@ This is the string displayed in the ``attachment'' menu for attachments of type _m_e_s_s_a_g_e_/_r_f_c_8_2_2. For a full listing of defined - escape sequences see the section on ``header_format''. + escape sequences see the section on ``index_format''. + 66..33..6644.. ppaaggeerr @@ -2838,6 +3343,7 @@ variable should specify the pathname of the external pager you would like to use. + 66..33..6655.. ppaaggeerr__ccoonntteexxtt Type: number @@ -2848,6 +3354,7 @@ default, Mutt will display the line after the last one on the screen at the top of the next page (0 lines of context). + 66..33..6666.. ppaaggeerr__ffoorrmmaatt Type: format string @@ -2855,9 +3362,8 @@ This variable controls the format of the one-line message ``status'' displayed before each message in either the internal or an external - pager. The valid sequences are listed in the ``header_format'' + pager. The valid sequences are listed in the ``index_format'' section. - 66..33..6677.. ppaaggeerr__iinnddeexx__lliinneess Type: number @@ -2875,6 +3381,7 @@ less than _p_a_g_e_r___i_n_d_e_x___l_i_n_e_s, then the index will only use as many lines as it needs. + 66..33..6688.. ppaaggeerr__ssttoopp Type: boolean @@ -2883,6 +3390,7 @@ When set, the internal-pager will nnoott move to the next message when you are at the end of a message and invoke the _n_e_x_t_-_p_a_g_e function. + 66..33..6699.. ppggpp__aauuttooeennccrryypptt Type: boolean @@ -2893,6 +3401,7 @@ to the _s_e_n_d_-_h_o_o_k command. It can be overridden by use of the _p_g_p_- _m_e_n_u, when encryption is not required or signing is requested as well. + 66..33..7700.. ppggpp__aauuttoossiiggnn Type: boolean @@ -2902,6 +3411,7 @@ sign outgoing messages. This can be overridden by use of the _p_g_p_- _m_e_n_u, when signing is not required or encryption is requested as well. + 66..33..7711.. ppggpp__ddeeffaauulltt__vveerrssiioonn Type: string @@ -2912,6 +3422,7 @@ is the default for the variables ``$pgp_receive_version'', ``$pgp_send_version'', and ``$pgp_key_version''. + 66..33..7722.. ppggpp__eennccrryyppttsseellff Type: boolean @@ -2930,6 +3441,7 @@ ``$pgp_default_version'' is used. Set this to pgp2 (PGP 2.*), or pgp5 (PGP 5.*) if you want a different PGP version for key operations. + 66..33..7744.. ppggpp__lloonngg__iiddss Type: boolean @@ -2937,6 +3449,7 @@ If set, use 64 bit PGP key IDs. Unset uses the normal 32 bit Key IDs. + 66..33..7755.. ppggpp__rreecceeiivvee__vveerrssiioonn Type: string @@ -2948,6 +3461,7 @@ pgp2 (PGP 2.*), or pgp5 (PGP 5.*) if you want a different PGP version for receiving operations. + 66..33..7766.. ppggpp__rreeppllyyeennccrryypptt Type: boolean @@ -2956,6 +3470,7 @@ If set, automatically PGP encrypt replies to messages which are encrypted. + 66..33..7777.. ppggpp__rreeppllyyssiiggnn Type: boolean @@ -2965,6 +3480,7 @@ NNoottee:: this does not work on messages, that are encrypted aanndd signed! + 66..33..7788.. ppggpp__sseenndd__vveerrssiioonn Type: string @@ -2976,6 +3492,10 @@ pgp2 (PGP 2.*), or pgp5 (PGP 5.*) if you want a different PGP version for sending operations. + + + + 66..33..7799.. ppggpp__ssiiggnn__aass Type: string @@ -2985,6 +3505,7 @@ which of your private keys to use. It is recommended that you use the keyid form to specify your key (e.g., ``0xABCDEFGH''). + 66..33..8800.. ppggpp__ssiiggnn__mmiiccaallgg Type: string @@ -3001,6 +3522,7 @@ here. The value of this variable will show up in the micalg parameter of MIME headers when creating RFC 2015 signatures. + 66..33..8811.. ppggpp__ssttrriicctt__eenncc Type: boolean @@ -3011,6 +3533,7 @@ to problems with non-verifyable PGP signatures, so only change this if you know what you are doing. + 66..33..8822.. ppggpp__ttiimmeeoouutt Type: number @@ -3019,6 +3542,7 @@ The number of seconds after which a cached passphrase will expire if not used. + 66..33..8833.. ppggpp__vv22 Type: string @@ -3027,6 +3551,7 @@ This variable allows you to override the compile time definition of where the PGP 2.* binary resides on your system. + 66..33..8844.. ppggpp__vv22__llaanngguuaaggee Type: string @@ -3036,6 +3561,7 @@ from the mutt doc directory, you can try the languages "mutt" (English) or "muttde" (German) to reduce the noise produced by pgp. + 66..33..8855.. ppggpp__vv22__ppuubbrriinngg Type: string @@ -3044,6 +3570,7 @@ Points to the PGP 2.* public keyring. + 66..33..8866.. ppggpp__vv22__sseeccrriinngg Type: string @@ -3052,6 +3579,7 @@ Points to the PGP 2.* secret keyring. + 66..33..8877.. ppggpp__vv55 Type: string @@ -3060,6 +3588,7 @@ This variable allows you to override the compile time definition of where the PGP 5.* binary resides on your system. + 66..33..8888.. ppggpp__vv55__llaanngguuaaggee Type: string @@ -3069,6 +3598,7 @@ from the mutt doc directory, you can try the languages "mutt" (English) to reduce the noise produced by pgp. + 66..33..8899.. ppggpp__vv55__ppuubbrriinngg Type: string @@ -3077,6 +3607,7 @@ Points to the PGP 5.* public keyring. + 66..33..9900.. ppggpp__vv55__sseeccrriinngg Type: string @@ -3085,6 +3616,7 @@ Points to the PGP 5.* secret keyring. + 66..33..9911.. ppiippee__ddeeccooddee Type: boolean @@ -3094,6 +3626,8 @@ will pipe the messages without any preprocessing. When set, Mutt will weed headers and will attempt to PGP/MIME decode the messages first. + + 66..33..9922.. ppiippee__sseepp Type: string @@ -3102,6 +3636,7 @@ The separator to add between messages when piping a list of tagged messages to an external Unix command. + 66..33..9933.. ppiippee__sspplliitt Type: boolean @@ -3114,6 +3649,7 @@ In both cases the the messages are piped in the current sorted order, and the ``$pipe_sep'' separator is added after each message. + 66..33..9944.. ppoopp__ddeelleettee Type: boolean @@ -3123,6 +3659,7 @@ server when using the fetch-mail function. When unset, Mutt will download messages but also leave them on the POP server. + 66..33..9955.. ppoopp__hhoosstt Type: string @@ -3130,6 +3667,7 @@ The name or address of your POP3 server. + 66..33..9966.. ppoopp__ppaassss Type: string @@ -3141,6 +3679,7 @@ secure machine, because the superuser can read your muttrc even if you are the only one who can read the file. + 66..33..9977.. ppoopp__ppoorrtt Type: number @@ -3148,13 +3687,16 @@ This variable specifies which port your POP server is listening on. + 66..33..9988.. ppoopp__uusseerr Type: string Default: login name on local system + Your login name on the POP3 server. + 66..33..9999.. ppoosstt__iinnddeenntt__ssttrriinngg Type: format string @@ -3163,6 +3705,7 @@ Similar to the ``$attribution'' variable, Mutt will append this string after the inclusion of a message which is being replied to. + 66..33..110000.. ppoossttppoonnee Type: quadoption @@ -3171,6 +3714,7 @@ Controls whether or not messages are saved in the ``$postponed'' mailbox when you elect not to send immediately. + 66..33..110011.. ppoossttppoonneedd Type: string @@ -3181,6 +3725,7 @@ in the folder specified by this variable. Also see the ``$postpone'' variable. + 66..33..110022.. pprriinntt Type: quadoption @@ -3189,6 +3734,7 @@ Controls whether or not Mutt asks for confirmation before printing. This is useful for people (like me) who accidentally hit ``p'' often. + 66..33..110033.. pprriinntt__ccoommmmaanndd Type: string @@ -3196,6 +3742,7 @@ This specifies the command pipe that should be used to print messages. + 66..33..110044.. pprroommpptt__aafftteerr Type: boolean @@ -3206,17 +3753,31 @@ returning to the index menu. If unset, Mutt will return to the index menu when the external pager exits. + 66..33..110055.. qquueerryy__ccoommmmaanndd Type: string Default: null + This specifies the command that mutt will use to make external address queries. The string should contain a %s, which will be substituted with the query string the user types. See ``query'' for more information. - 66..33..110066.. qquuoottee__rreeggeexxpp + + 66..33..110066.. qquuiitt + + Type: quadoption + Default: yes + + This variable controls whether ``quit'' and ``exit'' actually quit + from mutt. If it set to yes, they do quit, if it is set to no, they + have no effect, and if it is set to ask-yes or ask-no, you are + prompted for confirmation when you try to quit. + + + 66..33..110077.. qquuoottee__rreeggeexxpp Type: string Default: "^([ \t]*[>|#:}])+" @@ -3228,7 +3789,8 @@ need to set this to a regular expression that matches _e_x_a_c_t_l_y the quote characters at the beginning of quoted lines. - 66..33..110077.. rreeaadd__iinncc + + 66..33..110088.. rreeaadd__iinncc Type: number Default: 10 @@ -3245,14 +3807,16 @@ Also see the ``$write_inc'' variable. - 66..33..110088.. rreeaadd__oonnllyy + + 66..33..110099.. rreeaadd__oonnllyy Type: boolean Default: unset If set, all folders are opened in read-only mode. - 66..33..110099.. rreeaallnnaammee + + 66..33..111100.. rreeaallnnaammee Type: string Default: GCOS field from /etc/passwd @@ -3260,7 +3824,9 @@ This variable specifies what "real" or "personal" name should be used when sending messages. - 66..33..111100.. rreeccaallll + + + 66..33..111111.. rreeccaallll Type: quadoption Default: ask-yes @@ -3268,7 +3834,8 @@ Controls whether or not you are prompted to recall postponed messages when composing a new message. Also see ``postponed'' - 66..33..111111.. rreeccoorrdd + + 66..33..111122.. rreeccoorrdd Type: string Default: none @@ -3281,7 +3848,8 @@ The value of _$_r_e_c_o_r_d is overridden by the ``$force_name'' and ``$save_name'' variables, and the ``fcc-hook'' command. - 66..33..111122.. rreeppllyy__rreeggeexxpp + + 66..33..111133.. rreeppllyy__rreeggeexxpp Type: string Default: "^(re|aw):[ \t]*" @@ -3290,7 +3858,8 @@ and replying. The default value corresponds to the English "Re:" and the German "Aw:". - 66..33..111133.. rreeppllyy__ttoo + + 66..33..111144.. rreeppllyy__ttoo Type: quadoption Default: ask-yes @@ -3302,7 +3871,8 @@ header field to the list address and you want to send a private message to the author of a message. - 66..33..111144.. rreessoollvvee + + 66..33..111155.. rreessoollvvee Type: boolean Default: set @@ -3311,7 +3881,8 @@ (possibly undeleted) message whenever a command that modifies the current message is executed. - 66..33..111155.. rreevveerrssee__aalliiaass + + 66..33..111166.. rreevveerrssee__aalliiaass Type: boolean Default: unset @@ -3323,15 +3894,24 @@ alias juser abd30425@somewhere.net (Joe User) + + + and then you receive mail which contains the following header: + + From: abd30425@somewhere.net + + + It would be displayed in the index menu as ``Joe User'' instead of ``abd30425@somewhere.net.'' This is useful when the person's e-mail address is not human friendly (like Compu$erve addresses). - 66..33..111166.. rreevveerrssee__nnaammee + + 66..33..111177.. rreevveerrssee__nnaammee Type: boolean Default: unset @@ -3343,7 +3923,8 @@ messages you are replying to. If the variable is unset, the _F_r_o_m_: line will use your address on the current machine. - 66..33..111177.. ssaavvee__aaddddrreessss + + 66..33..111188.. ssaavvee__aaddddrreessss Type: boolean Default: unset @@ -3352,7 +3933,8 @@ default folder for saving a mail. If ``save_name'' or ``force_name'' is set too, the selection of the fcc folder will be changed as well. - 66..33..111188.. ssaavvee__eemmppttyy + + 66..33..111199.. ssaavvee__eemmppttyy Type: boolean Default: set @@ -3364,7 +3946,8 @@ NNoottee:: This only applies to mbox and MMDF folders, Mutt does not delete MH and Maildir directories. - 66..33..111199.. ssaavvee__nnaammee + + 66..33..112200.. ssaavvee__nnaammee Type: boolean Default: unset @@ -3379,15 +3962,18 @@ Also see the ``$force_name'' variable. - 66..33..112200.. sseennddmmaaiill + + 66..33..112211.. sseennddmmaaiill Type: string Default: /usr/lib/sendmail -oi -oem + Specifies the program and arguments used to deliver mail sent by Mutt. Mutt expects that the specified program will read the message header for recipients. - 66..33..112211.. sseennddmmaaiill__wwaaiitt + + 66..33..112222.. sseennddmmaaiill__wwaaiitt Type: number Default: 0 @@ -3401,18 +3987,22 @@ 0 wait forever for sendmail to finish <0 always put sendmail in the background without waiting + + Note that if you specify a value other than 0, the output of the child process will be put in a temporary file. If there is some error, you will be informed as to where to find the output. - 66..33..112222.. sshheellll + + 66..33..112233.. sshheellll Type: string Default: retrieved from passwd file Command to use when spawning a subshell. - 66..33..112233.. ssiigg__ddaasshheess + + 66..33..112244.. ssiigg__ddaasshheess Type: boolean Default: set @@ -3424,7 +4014,8 @@ detect your signature. For example, Mutt has the ability to highlight the signature in a different color in the builtin pager. - 66..33..112244.. ssiiggnnaattuurree + + 66..33..112255.. ssiiggnnaattuurree Type: string Default: ~/.signature @@ -3433,8 +4024,7 @@ outgoing messages. If the filename ends with a pipe (``|''), it is assumed that filename is a shell command and input should be read from its stdout. - - 66..33..112255.. ssiimmppllee__sseeaarrcchh + 66..33..112266.. ssiimmppllee__sseeaarrcchh Type: string Default: "~f %s | ~s %s" @@ -3442,13 +4032,15 @@ Specifies how Mutt should expand a simple search into a real search pattern. A simple search is one that does not contain any of the ~ operators. See ``searching'' for more information on search patterns. + For example, if you simply type joe at a search or limit prompt, Mutt will automatically expand it to the value specified by this variable. For the default value it would be: ~f joe | ~s joe - 66..33..112266.. ssmmaarrtt__wwrraapp + + 66..33..112277.. ssmmaarrtt__wwrraapp Type: boolean Default: set @@ -3458,13 +4050,15 @@ unset, lines are simply wrapped at the screen edge. Also see the ``$markers'' variable. - 66..33..112277.. ssoorrtt + + 66..33..112288.. ssoorrtt Type: string Default: date-sent Specifies how to sort messages in the _i_n_d_e_x menu. Valid values are + +o date-sent +o date-received @@ -3484,7 +4078,8 @@ You may optionally use the reverse- prefix to specify reverse sorting order (example: set sort=reverse-date-sent). - 66..33..112288.. ssoorrtt__aalliiaass + + 66..33..112299.. ssoorrtt__aalliiaass Type: string Default: alias @@ -3492,11 +4087,17 @@ Specifies how the entries in the `alias' menu are sorted. The following are legal values: + + + alias sort alphabetically by alias name address sort alphabetically by email address unsorted leave in order specified in .muttrc - 66..33..112299.. ssoorrtt__aauuxx + + + + 66..33..113300.. ssoorrtt__aauuxx Type: string Default: date-sent @@ -3513,13 +4114,15 @@ thread, that thread becomes the last one displayed (or the first, if you have set sort=reverse-threads.) - 66..33..113300.. ssoorrtt__bbrroowwsseerr + + 66..33..113311.. ssoorrtt__bbrroowwsseerr Type: string Specifies how to sort entries in the file browser. By default, the entries are sorted alphabetically. Valid values: + +o date +o alpha (alphabetically) @@ -3527,7 +4130,8 @@ You may optionally use the reverse- prefix to specify reverse sorting order (example: set sort_browser=reverse-date). - 66..33..113311.. ssppoooollffiillee + + 66..33..113322.. ssppoooollffiillee Type: string Default: most likely /var/mail/$USER or /usr/spool/mail/$USER @@ -3537,7 +4141,8 @@ automatically set this variable to the value of the environment variable $MAIL if it is not set. - 66..33..113322.. ssoorrtt__rree + + 66..33..113333.. ssoorrtt__rree Type: boolean Default: set @@ -3550,7 +4155,8 @@ message whether or not this is the case, as long as the non-``reply_regexp'' parts of both messages are identical. - 66..33..113333.. ssttaattuuss__cchhaarrss + + 66..33..113344.. ssttaattuuss__cchhaarrss Type: string Default: "-*%" @@ -3562,7 +4168,9 @@ read-only mode, or if the mailbox will not be written when exiting that mailbox (You can toggle whether to write changes to a mailbox with the toggle-write operation, bound by default to "%"). - 66..33..113344.. ssttaattuuss__ffoorrmmaatt + + + 66..33..113355.. ssttaattuuss__ffoorrmmaatt Type: string Default: "-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? @@ -3570,9 +4178,11 @@ %l?]---(%s/%S)-%>-(%P)---" Controls the format of the status line displayed in the _i_n_d_e_x menu. - This string is similar to ``$header_format'', but has its own set of + This string is similar to ``$index_format'', but has its own set of printf()-like sequences: + + %b number of mailboxes with new mail * %d number of deleted messages * %h local hostname @@ -3592,18 +4202,24 @@ %t number of tagged messages * %u number of unread messages * %v Mutt version string + %V currently active limit pattern, if any * %>X right justify the rest of the string and pad with "X" %|X pad to the end of the line with "X" * = can be optionally printed if nonzero + + + Some of the above sequences can be used to optionally print a string if their value is nonzero. For example, you may only want to see the number of flagged messages if such messages exist, since zero is not particularly meaningful. To optionally print a string based upon one of the above sequences, the following construct is used + + %??? where _s_e_q_u_e_n_c_e___c_h_a_r is a character from the table above, and @@ -3614,9 +4230,15 @@ Here is an example illustrating how to optionally print the number of new messages in a mailbox: + + %?n?%n new messages.? - 66..33..113355.. ssttaattuuss__oonn__ttoopp + + + + + 66..33..113366.. ssttaattuuss__oonn__ttoopp Type: boolean Default: unset @@ -3624,7 +4246,8 @@ Setting this variable causes the ``status bar'' to be displayed on the first line of the screen rather than near the bottom. - 66..33..113366.. ssttrriicctt__tthhrreeaaddss + + 66..33..113377.. ssttrriicctt__tthhrreeaaddss Type: boolean Default: unset @@ -3636,7 +4259,8 @@ personal mailbox where you might have several unrelated messages with the subject ``hi'' which will get grouped together. - 66..33..113377.. ssuussppeenndd + + 66..33..113388.. ssuussppeenndd Type: boolean Default: set @@ -3645,7 +4269,8 @@ key, usually ``control-Z''. This is useful if you run mutt inside an xterm using a command like xterm -e mutt. - 66..33..113388.. tthhoorroouugghh__sseeaarrcchh + + 66..33..113399.. tthhoorroouugghh__sseeaarrcchh Type: boolean Default: unset @@ -3655,15 +4280,15 @@ to be searched are decoded before searching. If unset, messages are searched as they appear in the folder. - 66..33..113399.. ttiillddee + + 66..33..114400.. ttiillddee Type: boolean Default: unset When set, the internal-pager will pad blank lines to the bottom of the screen with a tilde (~). - - 66..33..114400.. ttiimmeeoouutt + 66..33..114411.. ttiimmeeoouutt Type: number Default: 600 @@ -3672,14 +4297,17 @@ to be pressed in the main menu before timing out and checking for new mail. A value of zero or less will cause Mutt not to ever time out. - 66..33..114411.. ttmmppddiirr + + 66..33..114422.. ttmmppddiirr Type: string Default: /tmp + This variable allows you to specify where Mutt will place its temporary files needed for displaying and composing messages. - 66..33..114422.. ttoo__cchhaarrss + + 66..33..114433.. ttoo__cchhaarrss Type: string Default: " +TCF" @@ -3694,7 +4322,8 @@ recipient. The fifth character is used to indicate mail that was sent by _y_o_u. - 66..33..114433.. uussee__88bbiittmmiimmee + + 66..33..114444.. uussee__88bbiittmmiimmee Type: boolean Default: unset @@ -3706,7 +4335,8 @@ When _s_e_t, Mutt will invoke ``$sendmail'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP negotiation. - 66..33..114444.. uussee__ddoommaaiinn + + 66..33..114455.. uussee__ddoommaaiinn Type: boolean Default: set @@ -3715,7 +4345,8 @@ @host portion) with the value of ``$hostname''. If _u_n_s_e_t, no addresses will be qualified. - 66..33..114455.. uussee__ffrroomm + + 66..33..114466.. uussee__ffrroomm Type: boolean Default: set @@ -3723,8 +4354,7 @@ When _s_e_t, Mutt will generate the `From:' header field when sending messages. If _u_n_s_e_t, no `From:' header field will be generated unless the user explicitly sets one using the ``my_hdr'' command. - - 66..33..114466.. uussee__mmaaiillccaapp + 66..33..114477.. uussee__mmaaiillccaapp Type: quad-option Default: ask @@ -3741,7 +4371,8 @@ space) for which the corresponding mailcap entries will be used to display MIME parts without prompting the user for confirmation. - 66..33..114477.. ppggpp__vveerriiffyy__ssiigg + + 66..33..114488.. ppggpp__vveerriiffyy__ssiigg Type: quad-option Default: yes @@ -3750,7 +4381,8 @@ ask whether or not to verify the signature. If ``no'', never attempt to verify PGP/MIME signatures. - 66..33..114488.. vviissuuaall + + 66..33..114499.. vviissuuaall Type: string Default: $VISUAL @@ -3758,7 +4390,8 @@ Specifies the visual editor to invoke when the _~_v command is given in the builtin editor. - 66..33..114499.. wwaaiitt__kkeeyy + + 66..33..115500.. wwaaiitt__kkeeyy Type: boolean Default: set @@ -3773,7 +4406,21 @@ When set, Mutt will always ask for a key. When unset, Mutt will wait for a key only if the external command returned a non-zero status. - 66..33..115500.. wwrriittee__iinncc + + 66..33..115511.. wwrraapp__sseeaarrcchh + + Type: boolean + Default: set + + Controls whether searches wrap around the end of the mailbox. + + When set, searches will wrap around the first (or last) message. When + unset, searches will not wrap. + + + + + 66..33..115522.. wwrriittee__iinncc Type: number Default: 10 @@ -3784,6 +4431,7 @@ Also see the ``$read_inc'' variable. + 66..44.. FFuunnccttiioonnss The following is the list of available functions listed by the mapping @@ -3791,13 +4439,16 @@ explanation of what the function does. The key bindings of these functions can be changed with the ``bind'' command. + 66..44..11.. ggeenneerriicc + The _g_e_n_e_r_i_c menu is not a real menu, but specifies common functions (such as movement) available in all menus except for _p_a_g_e_r and _e_d_i_t_o_r. Changing settings for this menu will affect the default bindings for all menus (except as noted). + bottom-page L move to the bottom of the page current-bottom not bound move current entry to bottom of page current-middle not bound move current entry to middle of page @@ -3828,8 +4479,13 @@ tag-prefix ; apply next command to tagged entries top-page H move to the top of the page + + 66..44..22.. iinnddeexx + + + bounce-message b remail a message to another user change-folder c open a different folder change-folder-readonly ESC c open a different folder in read only mode @@ -3878,6 +4534,7 @@ save-message s save message/attachment to a file set-flag w set a status flag on a message show-version V show the Mutt version number and date + show-limit ESC l show currently active limit pattern, if any sort-mailbox o sort messages sort-reverse O sort messages in reverse order sync-mailbox $ save changes to mailbox @@ -3892,8 +4549,75 @@ untag-pattern ^T untag messages matching a pattern view-attachments v show MIME attachments + + + 66..44..33.. ppaaggeerr + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + bottom $ jump to the bottom of the message bounce-message b remail a message to another user change-folder c open a different folder @@ -3962,14 +4686,20 @@ undelete-thread ^U undelete all messages in thread view-attachments v show MIME attachments + + 66..44..44.. aalliiaass + search / search for a regular expression search-next n search for next match search-reverse ESC / search backwards for a regular expression + + 66..44..55.. qquueerryy + create-alias a create an alias from a message sender mail m compose a new mail message query Q query external program for addresses @@ -3979,8 +4709,11 @@ search-opposite not bound search for next match in opposite direction search-reverse ESC / search backwards for a regular expression + + 66..44..66.. aattttaacchh + bounce-message b remail a message to another user decode-copy ESC C decode a message and copy it to a file/mailbox decode-save ESC s decode a message and save it to a file/mailbox @@ -3999,8 +4732,24 @@ view-mailcap m force viewing of attachment using mailcap view-text T view attachment as text + + 66..44..77.. ccoommppoossee + + + + + + + + + + + + + + attach-file a attach a file(s) to this message attach-key ESC k attach a PGP public key copy-file C save message/attachment to a file @@ -4033,13 +4782,19 @@ toggle-unlink u toggle whether to delete file after sending it view-attach RET view attachment using mailcap entry if necessary + + 66..44..88.. ppoossttppoonneedd + delete-entry d delete the current entry undelete-entry u undelete the current entry + + 66..44..99.. bbrroowwsseerr + change-dir c change directories check-new TAB check mailboxes for new mail enter-mask m enter a file mask @@ -4050,13 +4805,20 @@ sort o sort messages sort-reverse O sort messages in reverse order + + 66..44..1100.. ppggpp + view-name % view the key's user id verify-key c verify a PGP public key + + + 66..44..1111.. eeddiittoorr + backspace BackSpace delete the char in front of the cursor backward-char ^B move the cursor one character to the left bol ^A jump to the beginning of the line @@ -4073,8 +4835,13 @@ kill-word ^W delete the word in front of the cursor quote-char ^V quote the next typed key + + + 77.. MMiisscceellllaannyy + + 77..11.. AAcckknnoowwlleeddggeemmeennttss Kari Hurrta co-developed the original MIME @@ -4108,8 +4875,76 @@ Allain Thivillon , Ken Weinert + 77..22.. AAbboouutt tthhiiss ddooccuummeenntt This document was written in SGML, and then rendered using the sgml- tools package. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + -- 2.40.0