From 647ac5444d022537a1f0854dd309494c511dfe07 Mon Sep 17 00:00:00 2001 From: Antonio Radici Date: Sun, 14 Jun 2009 20:50:40 +0100 Subject: [PATCH] Imported Upstream version 1.5.20 --- .gitignore | 34 + .pc/.version | 1 + ChangeLog | 965 +- Makefile.in | 305 +- OPS | 2 +- UPDATING | 19 + VERSION | 2 +- aclocal.m4 | 323 +- addrbook.c | 2 +- alias.c | 9 +- attach.c | 34 +- bcache.c | 8 + browser.c | 17 +- buffy.c | 112 +- buffy.h | 6 +- color.c | 31 +- commands.c | 50 +- compose.c | 4 +- config.guess | 32 +- config.h.in | 70 +- config.sub | 16 +- configure | 11665 +++++++------ configure.ac | 32 +- contrib/Makefile.in | 55 +- copy.c | 28 +- copy.h | 1 + crypt-gpgme.c | 35 +- crypt.c | 6 +- curs_lib.c | 5 +- curs_main.c | 189 +- debian/stamp-patched | 0 doc/Makefile.am | 14 +- doc/Makefile.in | 98 +- doc/Muttrc | 2764 ++-- doc/advancedusage.html | 368 +- doc/configuration.html | 802 +- doc/dotlock.man | 2 +- doc/gen-map-doc | 12 +- doc/gettingstarted.html | 414 +- doc/index.html | 22 +- doc/intro.html | 37 +- doc/makedoc.c | 31 +- doc/manual.html | 4493 ++--- doc/manual.txt | 6387 +++---- doc/manual.xml.head | 2576 ++- doc/manual.xml.tail | 2 +- doc/mbox.man | 6 +- doc/mimesupport.html | 203 +- doc/miscellany.html | 22 +- doc/mmdf.man | 3 +- doc/mutt.css | 14 +- doc/mutt.man | 58 +- doc/muttrc.man.head | 7 +- doc/optionalfeatures.html | 267 +- doc/reference.html | 2368 +-- doc/security.html | 90 + doc/tuning.html | 55 +- edit.c | 5 +- editmsg.c | 2 +- functions.h | 2 + globals.h | 1 + gnupgparse.c | 107 +- group.c | 2 +- handler.c | 154 +- hash.c | 38 +- hash.h | 11 +- hcache.c | 12 +- hdrline.c | 2 + headers.c | 48 +- help.c | 6 +- history.c | 16 +- hook.c | 13 + imap/Makefile.in | 85 +- imap/auth.c | 2 +- imap/browse.c | 8 +- imap/imap.c | 108 +- imap/imap_private.h | 2 +- imap/message.c | 98 +- imap/util.c | 73 +- init.c | 25 +- init.h | 1690 +- lib.c | 68 +- lib.h | 16 +- m4/Makefile.in | 55 +- m4/libgnutls.m4 | 162 - mailbox.h | 3 + main.c | 20 +- mbox.c | 73 +- mbyte.h | 6 + menu.c | 26 +- mh.c | 135 +- mkdtemp.c | 42 + mutt.h | 13 +- mutt_idna.c | 6 +- mutt_sasl.c | 1 + mutt_ssl.c | 150 +- mutt_ssl_gnutls.c | 321 +- muttlib.c | 19 +- mx.c | 76 +- obj-i486-linux-gnu-patched/Makefile | 1115 ++ obj-i486-linux-gnu-patched/account.o | Bin 0 -> 10648 bytes obj-i486-linux-gnu-patched/addrbook.o | Bin 0 -> 25864 bytes obj-i486-linux-gnu-patched/alias.o | Bin 0 -> 31952 bytes obj-i486-linux-gnu-patched/ascii.o | Bin 0 -> 6812 bytes obj-i486-linux-gnu-patched/attach.o | Bin 0 -> 53904 bytes obj-i486-linux-gnu-patched/base64.o | Bin 0 -> 6284 bytes obj-i486-linux-gnu-patched/bcache.o | Bin 0 -> 16084 bytes obj-i486-linux-gnu-patched/browser.o | Bin 0 -> 68332 bytes obj-i486-linux-gnu-patched/buffy.o | Bin 0 -> 33256 bytes obj-i486-linux-gnu-patched/build-stamp | 0 obj-i486-linux-gnu-patched/charset.o | Bin 0 -> 33076 bytes obj-i486-linux-gnu-patched/color.o | Bin 0 -> 40464 bytes obj-i486-linux-gnu-patched/commands.o | Bin 0 -> 56068 bytes obj-i486-linux-gnu-patched/complete.o | Bin 0 -> 10740 bytes obj-i486-linux-gnu-patched/compose.o | Bin 0 -> 68308 bytes obj-i486-linux-gnu-patched/compress.o | Bin 0 -> 37880 bytes obj-i486-linux-gnu-patched/config.h | 718 + obj-i486-linux-gnu-patched/config.log | 3993 +++++ obj-i486-linux-gnu-patched/config.status | 1443 ++ obj-i486-linux-gnu-patched/contrib/Makefile | 400 + obj-i486-linux-gnu-patched/copy.o | Bin 0 -> 44032 bytes obj-i486-linux-gnu-patched/crypt-gpgme.o | Bin 0 -> 168252 bytes .../crypt-mod-pgp-classic.o | Bin 0 -> 17660 bytes .../crypt-mod-pgp-gpgme.o | Bin 0 -> 16768 bytes .../crypt-mod-smime-classic.o | Bin 0 -> 16248 bytes .../crypt-mod-smime-gpgme.o | Bin 0 -> 15816 bytes obj-i486-linux-gnu-patched/crypt-mod.o | Bin 0 -> 13184 bytes obj-i486-linux-gnu-patched/crypt.o | Bin 0 -> 39912 bytes obj-i486-linux-gnu-patched/cryptglue.o | Bin 0 -> 36548 bytes obj-i486-linux-gnu-patched/curs_lib.o | Bin 0 -> 71852 bytes obj-i486-linux-gnu-patched/curs_main.o | Bin 0 -> 103944 bytes obj-i486-linux-gnu-patched/date.o | Bin 0 -> 8132 bytes obj-i486-linux-gnu-patched/doc/Makefile | 624 + obj-i486-linux-gnu-patched/doc/Muttrc | 4811 ++++++ .../doc/advancedusage.html | 609 + .../doc/configuration.html | 1282 ++ .../doc/gettingstarted.html | 553 + obj-i486-linux-gnu-patched/doc/index.html | 178 + obj-i486-linux-gnu-patched/doc/instdoc.sh | 25 + obj-i486-linux-gnu-patched/doc/intro.html | 108 + obj-i486-linux-gnu-patched/doc/makedoc | Bin 0 -> 38798 bytes obj-i486-linux-gnu-patched/doc/makedoc.o | Bin 0 -> 40272 bytes obj-i486-linux-gnu-patched/doc/manual.html | 6459 ++++++++ obj-i486-linux-gnu-patched/doc/manual.txt | 11584 +++++++++++++ obj-i486-linux-gnu-patched/doc/manual.xml | 13788 ++++++++++++++++ .../doc/mimesupport.html | 590 + .../doc/miscellany.html | 32 + obj-i486-linux-gnu-patched/doc/mutt.1 | 234 + obj-i486-linux-gnu-patched/doc/muttrc.man | 5940 +++++++ .../doc/optionalfeatures.html | 309 + obj-i486-linux-gnu-patched/doc/reference.html | 2927 ++++ obj-i486-linux-gnu-patched/doc/smime_keys.1 | 67 + .../doc/stamp-doc-chunked | 0 obj-i486-linux-gnu-patched/doc/stamp-doc-rc | 0 obj-i486-linux-gnu-patched/doc/stamp-doc-xml | 0 obj-i486-linux-gnu-patched/doc/tuning.html | 88 + obj-i486-linux-gnu-patched/edit.o | Bin 0 -> 37668 bytes obj-i486-linux-gnu-patched/editmsg.o | Bin 0 -> 26412 bytes obj-i486-linux-gnu-patched/enter.o | Bin 0 -> 39124 bytes obj-i486-linux-gnu-patched/extlib.o | Bin 0 -> 4316 bytes obj-i486-linux-gnu-patched/filter.o | Bin 0 -> 7620 bytes obj-i486-linux-gnu-patched/flags.o | Bin 0 -> 28756 bytes obj-i486-linux-gnu-patched/flea | 347 + obj-i486-linux-gnu-patched/from.o | Bin 0 -> 8984 bytes obj-i486-linux-gnu-patched/getdomain.o | Bin 0 -> 6216 bytes obj-i486-linux-gnu-patched/gnupgparse.o | Bin 0 -> 20104 bytes obj-i486-linux-gnu-patched/group.o | Bin 0 -> 10568 bytes obj-i486-linux-gnu-patched/handler.o | Bin 0 -> 70768 bytes obj-i486-linux-gnu-patched/hash.o | Bin 0 -> 8740 bytes obj-i486-linux-gnu-patched/hcache.o | Bin 0 -> 35036 bytes obj-i486-linux-gnu-patched/hcachever.sh | 89 + obj-i486-linux-gnu-patched/hcversion.h | 10 + obj-i486-linux-gnu-patched/hdrline.o | Bin 0 -> 39532 bytes obj-i486-linux-gnu-patched/headers.o | Bin 0 -> 17548 bytes obj-i486-linux-gnu-patched/help.o | Bin 0 -> 39100 bytes obj-i486-linux-gnu-patched/history.o | Bin 0 -> 13040 bytes obj-i486-linux-gnu-patched/hook.o | Bin 0 -> 32560 bytes obj-i486-linux-gnu-patched/imap/Makefile | 487 + obj-i486-linux-gnu-patched/imap/auth.o | Bin 0 -> 17616 bytes obj-i486-linux-gnu-patched/imap/auth_gss.o | Bin 0 -> 24784 bytes obj-i486-linux-gnu-patched/imap/auth_login.o | Bin 0 -> 17144 bytes obj-i486-linux-gnu-patched/imap/auth_sasl.o | Bin 0 -> 20940 bytes obj-i486-linux-gnu-patched/imap/browse.o | Bin 0 -> 35000 bytes obj-i486-linux-gnu-patched/imap/command.o | Bin 0 -> 48740 bytes obj-i486-linux-gnu-patched/imap/imap.o | Bin 0 -> 78304 bytes obj-i486-linux-gnu-patched/imap/libimap.a | Bin 0 -> 359628 bytes obj-i486-linux-gnu-patched/imap/message.o | Bin 0 -> 56724 bytes obj-i486-linux-gnu-patched/imap/utf7.o | Bin 0 -> 10420 bytes obj-i486-linux-gnu-patched/imap/util.o | Bin 0 -> 47560 bytes obj-i486-linux-gnu-patched/init.o | Bin 0 -> 146564 bytes obj-i486-linux-gnu-patched/intl/Makefile | 314 + obj-i486-linux-gnu-patched/keymap.o | Bin 0 -> 61580 bytes obj-i486-linux-gnu-patched/keymap_defs.h | 419 + obj-i486-linux-gnu-patched/lib.o | Bin 0 -> 39532 bytes obj-i486-linux-gnu-patched/m4/Makefile | 369 + obj-i486-linux-gnu-patched/main.o | Bin 0 -> 63712 bytes obj-i486-linux-gnu-patched/mbox.o | Bin 0 -> 44408 bytes obj-i486-linux-gnu-patched/mbyte.o | Bin 0 -> 11932 bytes obj-i486-linux-gnu-patched/md5.o | Bin 0 -> 13588 bytes obj-i486-linux-gnu-patched/menu.o | Bin 0 -> 54904 bytes obj-i486-linux-gnu-patched/mh.o | Bin 0 -> 78568 bytes obj-i486-linux-gnu-patched/mutt | Bin 0 -> 2463272 bytes obj-i486-linux-gnu-patched/mutt_dotlock | Bin 0 -> 20882 bytes obj-i486-linux-gnu-patched/mutt_dotlock.o | Bin 0 -> 16888 bytes obj-i486-linux-gnu-patched/mutt_idna.o | Bin 0 -> 18716 bytes obj-i486-linux-gnu-patched/mutt_md5 | Bin 0 -> 17906 bytes obj-i486-linux-gnu-patched/mutt_md5-md5.o | Bin 0 -> 14428 bytes obj-i486-linux-gnu-patched/mutt_sasl.o | Bin 0 -> 25056 bytes obj-i486-linux-gnu-patched/mutt_socket.o | Bin 0 -> 27900 bytes obj-i486-linux-gnu-patched/mutt_ssl_gnutls.o | Bin 0 -> 49904 bytes obj-i486-linux-gnu-patched/mutt_tunnel.o | Bin 0 -> 11032 bytes obj-i486-linux-gnu-patched/muttbug.sh | 347 + obj-i486-linux-gnu-patched/muttlib.o | Bin 0 -> 80252 bytes obj-i486-linux-gnu-patched/mx.o | Bin 0 -> 70160 bytes obj-i486-linux-gnu-patched/pager.o | Bin 0 -> 105020 bytes obj-i486-linux-gnu-patched/parse.o | Bin 0 -> 58796 bytes obj-i486-linux-gnu-patched/patchlist.c | 14 + obj-i486-linux-gnu-patched/patchlist.o | Bin 0 -> 4348 bytes obj-i486-linux-gnu-patched/pattern.o | Bin 0 -> 68492 bytes obj-i486-linux-gnu-patched/pgp.o | Bin 0 -> 66140 bytes obj-i486-linux-gnu-patched/pgpewrap | Bin 0 -> 10075 bytes obj-i486-linux-gnu-patched/pgpewrap.o | Bin 0 -> 5764 bytes obj-i486-linux-gnu-patched/pgpinvoke.o | Bin 0 -> 19776 bytes obj-i486-linux-gnu-patched/pgpkey.o | Bin 0 -> 56132 bytes obj-i486-linux-gnu-patched/pgplib.o | Bin 0 -> 10448 bytes obj-i486-linux-gnu-patched/pgpmicalg.o | Bin 0 -> 10740 bytes obj-i486-linux-gnu-patched/pgppacket.o | Bin 0 -> 7928 bytes obj-i486-linux-gnu-patched/pgppubring.o | Bin 0 -> 29432 bytes obj-i486-linux-gnu-patched/pgpring | Bin 0 -> 100483 bytes obj-i486-linux-gnu-patched/po/Makefile | 278 + obj-i486-linux-gnu-patched/po/Makefile.in | 205 + obj-i486-linux-gnu-patched/po/POTFILES | 73 + obj-i486-linux-gnu-patched/po/bg.gmo | Bin 0 -> 71617 bytes obj-i486-linux-gnu-patched/po/ca.gmo | Bin 0 -> 101097 bytes obj-i486-linux-gnu-patched/po/cs.gmo | Bin 0 -> 100507 bytes obj-i486-linux-gnu-patched/po/da.gmo | Bin 0 -> 69698 bytes obj-i486-linux-gnu-patched/po/de.gmo | Bin 0 -> 96610 bytes obj-i486-linux-gnu-patched/po/el.gmo | Bin 0 -> 76185 bytes obj-i486-linux-gnu-patched/po/eo.gmo | Bin 0 -> 92063 bytes obj-i486-linux-gnu-patched/po/es.gmo | Bin 0 -> 60489 bytes obj-i486-linux-gnu-patched/po/et.gmo | Bin 0 -> 64373 bytes obj-i486-linux-gnu-patched/po/eu.gmo | Bin 0 -> 92238 bytes obj-i486-linux-gnu-patched/po/fr.gmo | Bin 0 -> 101994 bytes obj-i486-linux-gnu-patched/po/ga.gmo | Bin 0 -> 92580 bytes obj-i486-linux-gnu-patched/po/gl.gmo | Bin 0 -> 59112 bytes obj-i486-linux-gnu-patched/po/hu.gmo | Bin 0 -> 68838 bytes obj-i486-linux-gnu-patched/po/id.gmo | Bin 0 -> 91095 bytes obj-i486-linux-gnu-patched/po/it.gmo | Bin 0 -> 71358 bytes obj-i486-linux-gnu-patched/po/ja.gmo | Bin 0 -> 91670 bytes obj-i486-linux-gnu-patched/po/ko.gmo | Bin 0 -> 63148 bytes obj-i486-linux-gnu-patched/po/lt.gmo | Bin 0 -> 55993 bytes obj-i486-linux-gnu-patched/po/nl.gmo | Bin 0 -> 94791 bytes obj-i486-linux-gnu-patched/po/pl.gmo | Bin 0 -> 93689 bytes obj-i486-linux-gnu-patched/po/pt_BR.gmo | Bin 0 -> 53099 bytes obj-i486-linux-gnu-patched/po/ru.gmo | Bin 0 -> 95565 bytes obj-i486-linux-gnu-patched/po/sk.gmo | Bin 0 -> 41596 bytes obj-i486-linux-gnu-patched/po/sv.gmo | Bin 0 -> 93590 bytes obj-i486-linux-gnu-patched/po/tr.gmo | Bin 0 -> 90978 bytes obj-i486-linux-gnu-patched/po/uk.gmo | Bin 0 -> 61069 bytes obj-i486-linux-gnu-patched/po/zh_CN.gmo | Bin 0 -> 40545 bytes obj-i486-linux-gnu-patched/po/zh_TW.gmo | Bin 0 -> 58368 bytes obj-i486-linux-gnu-patched/pop.o | Bin 0 -> 45320 bytes obj-i486-linux-gnu-patched/pop_auth.o | Bin 0 -> 22636 bytes obj-i486-linux-gnu-patched/pop_lib.o | Bin 0 -> 36368 bytes obj-i486-linux-gnu-patched/postpone.o | Bin 0 -> 48076 bytes obj-i486-linux-gnu-patched/query.o | Bin 0 -> 42928 bytes obj-i486-linux-gnu-patched/recvattach.o | Bin 0 -> 70652 bytes obj-i486-linux-gnu-patched/recvcmd.o | Bin 0 -> 46676 bytes obj-i486-linux-gnu-patched/reldate.h | 1 + obj-i486-linux-gnu-patched/remailer.o | Bin 0 -> 45716 bytes obj-i486-linux-gnu-patched/resize.o | Bin 0 -> 5512 bytes obj-i486-linux-gnu-patched/rfc1524.o | Bin 0 -> 32060 bytes obj-i486-linux-gnu-patched/rfc2047.o | Bin 0 -> 37092 bytes obj-i486-linux-gnu-patched/rfc2231.o | Bin 0 -> 19668 bytes obj-i486-linux-gnu-patched/rfc3676.o | Bin 0 -> 18780 bytes obj-i486-linux-gnu-patched/rfc822.o | Bin 0 -> 24232 bytes obj-i486-linux-gnu-patched/score.o | Bin 0 -> 24324 bytes obj-i486-linux-gnu-patched/send.o | Bin 0 -> 70736 bytes obj-i486-linux-gnu-patched/sendlib.o | Bin 0 -> 95280 bytes obj-i486-linux-gnu-patched/sha1.o | Bin 0 -> 12588 bytes obj-i486-linux-gnu-patched/sidebar.o | Bin 0 -> 38856 bytes obj-i486-linux-gnu-patched/signal.o | Bin 0 -> 18004 bytes obj-i486-linux-gnu-patched/smime.o | Bin 0 -> 82656 bytes obj-i486-linux-gnu-patched/smime_keys | 973 ++ obj-i486-linux-gnu-patched/smtp.o | Bin 0 -> 29660 bytes obj-i486-linux-gnu-patched/sort.o | Bin 0 -> 29248 bytes obj-i486-linux-gnu-patched/stamp-h1 | 1 + obj-i486-linux-gnu-patched/status.o | Bin 0 -> 28160 bytes obj-i486-linux-gnu-patched/system.o | Bin 0 -> 7768 bytes obj-i486-linux-gnu-patched/thread.o | Bin 0 -> 50964 bytes obj-i486-linux-gnu-patched/url.o | Bin 0 -> 14316 bytes obj-i486-linux-gnu/Makefile | 1113 ++ obj-i486-linux-gnu/account.o | Bin 0 -> 10640 bytes obj-i486-linux-gnu/addrbook.o | Bin 0 -> 25664 bytes obj-i486-linux-gnu/alias.o | Bin 0 -> 31916 bytes obj-i486-linux-gnu/ascii.o | Bin 0 -> 6804 bytes obj-i486-linux-gnu/attach.o | Bin 0 -> 53804 bytes obj-i486-linux-gnu/base64.o | Bin 0 -> 6276 bytes obj-i486-linux-gnu/bcache.o | Bin 0 -> 16076 bytes obj-i486-linux-gnu/browser.o | Bin 0 -> 67920 bytes obj-i486-linux-gnu/buffy.o | Bin 0 -> 31188 bytes obj-i486-linux-gnu/build-stamp | 0 obj-i486-linux-gnu/charset.o | Bin 0 -> 33068 bytes obj-i486-linux-gnu/color.o | Bin 0 -> 40232 bytes obj-i486-linux-gnu/commands.o | Bin 0 -> 55828 bytes obj-i486-linux-gnu/complete.o | Bin 0 -> 10732 bytes obj-i486-linux-gnu/compose.o | Bin 0 -> 67452 bytes obj-i486-linux-gnu/compress.o | Bin 0 -> 37780 bytes obj-i486-linux-gnu/config.h | 718 + obj-i486-linux-gnu/config.log | 3993 +++++ obj-i486-linux-gnu/config.status | 1443 ++ obj-i486-linux-gnu/contrib/Makefile | 400 + obj-i486-linux-gnu/copy.o | Bin 0 -> 43932 bytes obj-i486-linux-gnu/crypt-gpgme.o | Bin 0 -> 168044 bytes obj-i486-linux-gnu/crypt-mod-pgp-classic.o | Bin 0 -> 17652 bytes obj-i486-linux-gnu/crypt-mod-pgp-gpgme.o | Bin 0 -> 16760 bytes obj-i486-linux-gnu/crypt-mod-smime-classic.o | Bin 0 -> 16240 bytes obj-i486-linux-gnu/crypt-mod-smime-gpgme.o | Bin 0 -> 15808 bytes obj-i486-linux-gnu/crypt-mod.o | Bin 0 -> 13176 bytes obj-i486-linux-gnu/crypt.o | Bin 0 -> 39828 bytes obj-i486-linux-gnu/cryptglue.o | Bin 0 -> 36516 bytes obj-i486-linux-gnu/curs_lib.o | Bin 0 -> 71496 bytes obj-i486-linux-gnu/curs_main.o | Bin 0 -> 102272 bytes obj-i486-linux-gnu/date.o | Bin 0 -> 8124 bytes obj-i486-linux-gnu/doc/Makefile | 624 + obj-i486-linux-gnu/doc/Muttrc | 4780 ++++++ obj-i486-linux-gnu/doc/advancedusage.html | 609 + obj-i486-linux-gnu/doc/configuration.html | 1282 ++ obj-i486-linux-gnu/doc/gettingstarted.html | 553 + obj-i486-linux-gnu/doc/index.html | 178 + obj-i486-linux-gnu/doc/instdoc | 25 + obj-i486-linux-gnu/doc/instdoc.sh | 25 + obj-i486-linux-gnu/doc/intro.html | 108 + obj-i486-linux-gnu/doc/makedoc | Bin 0 -> 38790 bytes obj-i486-linux-gnu/doc/makedoc.o | Bin 0 -> 40264 bytes obj-i486-linux-gnu/doc/manual.html | 6449 ++++++++ obj-i486-linux-gnu/doc/manual.txt | 11526 +++++++++++++ obj-i486-linux-gnu/doc/manual.xml | 13747 +++++++++++++++ obj-i486-linux-gnu/doc/mimesupport.html | 590 + obj-i486-linux-gnu/doc/miscellany.html | 32 + obj-i486-linux-gnu/doc/mutt.1 | 234 + obj-i486-linux-gnu/doc/muttrc.man | 5909 +++++++ obj-i486-linux-gnu/doc/optionalfeatures.html | 309 + obj-i486-linux-gnu/doc/reference.html | 2917 ++++ obj-i486-linux-gnu/doc/smime_keys.1 | 67 + obj-i486-linux-gnu/doc/stamp-doc-chunked | 0 obj-i486-linux-gnu/doc/stamp-doc-rc | 0 obj-i486-linux-gnu/doc/stamp-doc-xml | 0 obj-i486-linux-gnu/doc/tuning.html | 88 + obj-i486-linux-gnu/edit.o | Bin 0 -> 37564 bytes obj-i486-linux-gnu/editmsg.o | Bin 0 -> 26316 bytes obj-i486-linux-gnu/enter.o | Bin 0 -> 38920 bytes obj-i486-linux-gnu/extlib.o | Bin 0 -> 4308 bytes obj-i486-linux-gnu/filter.o | Bin 0 -> 7612 bytes obj-i486-linux-gnu/flags.o | Bin 0 -> 28708 bytes obj-i486-linux-gnu/flea | 347 + obj-i486-linux-gnu/from.o | Bin 0 -> 8976 bytes obj-i486-linux-gnu/getdomain.o | Bin 0 -> 6208 bytes obj-i486-linux-gnu/gnupgparse.o | Bin 0 -> 20076 bytes obj-i486-linux-gnu/group.o | Bin 0 -> 10560 bytes obj-i486-linux-gnu/handler.o | Bin 0 -> 70576 bytes obj-i486-linux-gnu/hash.o | Bin 0 -> 8732 bytes obj-i486-linux-gnu/hcache.o | Bin 0 -> 35028 bytes obj-i486-linux-gnu/hcachever.sh | 89 + obj-i486-linux-gnu/hcversion.h | 10 + obj-i486-linux-gnu/hdrline.o | Bin 0 -> 39432 bytes obj-i486-linux-gnu/headers.o | Bin 0 -> 17540 bytes obj-i486-linux-gnu/help.o | Bin 0 -> 38696 bytes obj-i486-linux-gnu/history.o | Bin 0 -> 13032 bytes obj-i486-linux-gnu/hook.o | Bin 0 -> 32464 bytes obj-i486-linux-gnu/imap/Makefile | 487 + obj-i486-linux-gnu/imap/auth.o | Bin 0 -> 17544 bytes obj-i486-linux-gnu/imap/auth_gss.o | Bin 0 -> 24712 bytes obj-i486-linux-gnu/imap/auth_login.o | Bin 0 -> 17068 bytes obj-i486-linux-gnu/imap/auth_sasl.o | Bin 0 -> 20864 bytes obj-i486-linux-gnu/imap/browse.o | Bin 0 -> 34904 bytes obj-i486-linux-gnu/imap/command.o | Bin 0 -> 48484 bytes obj-i486-linux-gnu/imap/imap.o | Bin 0 -> 78060 bytes obj-i486-linux-gnu/imap/libimap.a | Bin 0 -> 358528 bytes obj-i486-linux-gnu/imap/message.o | Bin 0 -> 56624 bytes obj-i486-linux-gnu/imap/utf7.o | Bin 0 -> 10412 bytes obj-i486-linux-gnu/imap/util.o | Bin 0 -> 47460 bytes obj-i486-linux-gnu/init.o | Bin 0 -> 146196 bytes obj-i486-linux-gnu/intl/Makefile | 314 + obj-i486-linux-gnu/keymap.o | Bin 0 -> 61092 bytes obj-i486-linux-gnu/keymap_defs.h | 409 + obj-i486-linux-gnu/lib.o | Bin 0 -> 39524 bytes obj-i486-linux-gnu/m4/Makefile | 369 + obj-i486-linux-gnu/main.o | Bin 0 -> 63056 bytes obj-i486-linux-gnu/mbox.o | Bin 0 -> 44320 bytes obj-i486-linux-gnu/mbyte.o | Bin 0 -> 11896 bytes obj-i486-linux-gnu/md5.o | Bin 0 -> 13580 bytes obj-i486-linux-gnu/menu.o | Bin 0 -> 54240 bytes obj-i486-linux-gnu/mh.o | Bin 0 -> 78468 bytes obj-i486-linux-gnu/mutt | Bin 0 -> 2436439 bytes obj-i486-linux-gnu/mutt_dotlock | Bin 0 -> 20874 bytes obj-i486-linux-gnu/mutt_dotlock.o | Bin 0 -> 16880 bytes obj-i486-linux-gnu/mutt_idna.o | Bin 0 -> 18692 bytes obj-i486-linux-gnu/mutt_md5 | Bin 0 -> 17898 bytes obj-i486-linux-gnu/mutt_md5-md5.o | Bin 0 -> 14420 bytes obj-i486-linux-gnu/mutt_sasl.o | Bin 0 -> 25048 bytes obj-i486-linux-gnu/mutt_socket.o | Bin 0 -> 27864 bytes obj-i486-linux-gnu/mutt_ssl_gnutls.o | Bin 0 -> 49704 bytes obj-i486-linux-gnu/mutt_tunnel.o | Bin 0 -> 11024 bytes obj-i486-linux-gnu/muttbug.sh | 347 + obj-i486-linux-gnu/muttlib.o | Bin 0 -> 79052 bytes obj-i486-linux-gnu/mx.o | Bin 0 -> 69616 bytes obj-i486-linux-gnu/pager.o | Bin 0 -> 102980 bytes obj-i486-linux-gnu/parse.o | Bin 0 -> 58700 bytes obj-i486-linux-gnu/patchlist.c | 13 + obj-i486-linux-gnu/patchlist.o | Bin 0 -> 4204 bytes obj-i486-linux-gnu/pattern.o | Bin 0 -> 68384 bytes obj-i486-linux-gnu/pgp.o | Bin 0 -> 66068 bytes obj-i486-linux-gnu/pgpewrap | Bin 0 -> 10067 bytes obj-i486-linux-gnu/pgpewrap.o | Bin 0 -> 5756 bytes obj-i486-linux-gnu/pgpinvoke.o | Bin 0 -> 19768 bytes obj-i486-linux-gnu/pgpkey.o | Bin 0 -> 55932 bytes obj-i486-linux-gnu/pgplib.o | Bin 0 -> 10440 bytes obj-i486-linux-gnu/pgpmicalg.o | Bin 0 -> 10732 bytes obj-i486-linux-gnu/pgppacket.o | Bin 0 -> 7920 bytes obj-i486-linux-gnu/pgppubring.o | Bin 0 -> 29424 bytes obj-i486-linux-gnu/pgpring | Bin 0 -> 100475 bytes obj-i486-linux-gnu/po/Makefile | 278 + obj-i486-linux-gnu/po/Makefile.in | 205 + obj-i486-linux-gnu/po/POTFILES | 73 + obj-i486-linux-gnu/po/bg.gmo | Bin 0 -> 71617 bytes obj-i486-linux-gnu/po/ca.gmo | Bin 0 -> 101097 bytes obj-i486-linux-gnu/po/cs.gmo | Bin 0 -> 100507 bytes obj-i486-linux-gnu/po/da.gmo | Bin 0 -> 69698 bytes obj-i486-linux-gnu/po/de.gmo | Bin 0 -> 96610 bytes obj-i486-linux-gnu/po/el.gmo | Bin 0 -> 76185 bytes obj-i486-linux-gnu/po/eo.gmo | Bin 0 -> 92063 bytes obj-i486-linux-gnu/po/es.gmo | Bin 0 -> 60489 bytes obj-i486-linux-gnu/po/et.gmo | Bin 0 -> 64373 bytes obj-i486-linux-gnu/po/eu.gmo | Bin 0 -> 92238 bytes obj-i486-linux-gnu/po/fr.gmo | Bin 0 -> 101994 bytes obj-i486-linux-gnu/po/ga.gmo | Bin 0 -> 92580 bytes obj-i486-linux-gnu/po/gl.gmo | Bin 0 -> 59112 bytes obj-i486-linux-gnu/po/hu.gmo | Bin 0 -> 68838 bytes obj-i486-linux-gnu/po/id.gmo | Bin 0 -> 91095 bytes obj-i486-linux-gnu/po/it.gmo | Bin 0 -> 71358 bytes obj-i486-linux-gnu/po/ja.gmo | Bin 0 -> 91670 bytes obj-i486-linux-gnu/po/ko.gmo | Bin 0 -> 63148 bytes obj-i486-linux-gnu/po/lt.gmo | Bin 0 -> 55993 bytes obj-i486-linux-gnu/po/nl.gmo | Bin 0 -> 94791 bytes obj-i486-linux-gnu/po/pl.gmo | Bin 0 -> 93689 bytes obj-i486-linux-gnu/po/pt_BR.gmo | Bin 0 -> 53099 bytes obj-i486-linux-gnu/po/ru.gmo | Bin 0 -> 95565 bytes obj-i486-linux-gnu/po/sk.gmo | Bin 0 -> 41596 bytes obj-i486-linux-gnu/po/sv.gmo | Bin 0 -> 93590 bytes obj-i486-linux-gnu/po/tr.gmo | Bin 0 -> 90978 bytes obj-i486-linux-gnu/po/uk.gmo | Bin 0 -> 61069 bytes obj-i486-linux-gnu/po/zh_CN.gmo | Bin 0 -> 40545 bytes obj-i486-linux-gnu/po/zh_TW.gmo | Bin 0 -> 58368 bytes obj-i486-linux-gnu/pop.o | Bin 0 -> 45240 bytes obj-i486-linux-gnu/pop_auth.o | Bin 0 -> 22600 bytes obj-i486-linux-gnu/pop_lib.o | Bin 0 -> 36268 bytes obj-i486-linux-gnu/postpone.o | Bin 0 -> 47796 bytes obj-i486-linux-gnu/query.o | Bin 0 -> 42664 bytes obj-i486-linux-gnu/recvattach.o | Bin 0 -> 70260 bytes obj-i486-linux-gnu/recvcmd.o | Bin 0 -> 46572 bytes obj-i486-linux-gnu/reldate.h | 1 + obj-i486-linux-gnu/remailer.o | Bin 0 -> 45456 bytes obj-i486-linux-gnu/resize.o | Bin 0 -> 5504 bytes obj-i486-linux-gnu/rfc1524.o | Bin 0 -> 32024 bytes obj-i486-linux-gnu/rfc2047.o | Bin 0 -> 37056 bytes obj-i486-linux-gnu/rfc2231.o | Bin 0 -> 19632 bytes obj-i486-linux-gnu/rfc3676.o | Bin 0 -> 18772 bytes obj-i486-linux-gnu/rfc822.o | Bin 0 -> 24224 bytes obj-i486-linux-gnu/score.o | Bin 0 -> 24156 bytes obj-i486-linux-gnu/send.o | Bin 0 -> 70708 bytes obj-i486-linux-gnu/sendlib.o | Bin 0 -> 95252 bytes obj-i486-linux-gnu/sha1.o | Bin 0 -> 12580 bytes obj-i486-linux-gnu/signal.o | Bin 0 -> 17964 bytes obj-i486-linux-gnu/smime.o | Bin 0 -> 82388 bytes obj-i486-linux-gnu/smime_keys | 973 ++ obj-i486-linux-gnu/smtp.o | Bin 0 -> 29624 bytes obj-i486-linux-gnu/sort.o | Bin 0 -> 28860 bytes obj-i486-linux-gnu/stamp-h1 | 1 + obj-i486-linux-gnu/status.o | Bin 0 -> 28064 bytes obj-i486-linux-gnu/system.o | Bin 0 -> 7760 bytes obj-i486-linux-gnu/thread.o | Bin 0 -> 50868 bytes obj-i486-linux-gnu/url.o | Bin 0 -> 14308 bytes pager.c | 150 +- parse.c | 16 +- pattern.c | 33 +- pgp.c | 104 +- pgpkey.c | 90 +- pgppubring.c | 2 +- po/bg.gmo | Bin 71617 -> 71271 bytes po/bg.po | 1180 +- po/ca.gmo | Bin 101097 -> 103870 bytes po/ca.po | 1274 +- po/cs.gmo | Bin 100507 -> 100815 bytes po/cs.po | 1192 +- po/da.gmo | Bin 69698 -> 69383 bytes po/da.po | 1179 +- po/de.gmo | Bin 95823 -> 95475 bytes po/de.po | 1180 +- po/el.gmo | Bin 76185 -> 75781 bytes po/el.po | 1191 +- po/eo.gmo | Bin 92063 -> 91716 bytes po/eo.po | 1179 +- po/es.gmo | Bin 60489 -> 60123 bytes po/es.po | 1179 +- po/et.gmo | Bin 64373 -> 64019 bytes po/et.po | 1179 +- po/eu.gmo | Bin 92238 -> 91835 bytes po/eu.po | 1179 +- po/fr.gmo | Bin 101994 -> 102602 bytes po/fr.po | 1196 +- po/ga.gmo | Bin 92580 -> 92192 bytes po/ga.po | 1181 +- po/gl.gmo | Bin 59112 -> 58749 bytes po/gl.po | 1179 +- po/hu.gmo | Bin 68838 -> 68510 bytes po/hu.po | 1180 +- po/id.gmo | Bin 91095 -> 90755 bytes po/id.po | 1179 +- po/it.gmo | Bin 71358 -> 71020 bytes po/it.po | 1179 +- po/ja.gmo | Bin 91670 -> 91270 bytes po/ja.po | 1179 +- po/ko.gmo | Bin 63148 -> 62841 bytes po/ko.po | 1179 +- po/lt.gmo | Bin 55993 -> 55663 bytes po/lt.po | 1179 +- po/mutt.pot | 1164 +- po/nl.gmo | Bin 94791 -> 99225 bytes po/nl.po | 1264 +- po/pl.gmo | Bin 93689 -> 93296 bytes po/pl.po | 1179 +- po/pt_BR.gmo | Bin 53099 -> 52752 bytes po/pt_BR.po | 1179 +- po/ru.gmo | Bin 95565 -> 98258 bytes po/ru.po | 1261 +- po/sk.gmo | Bin 41596 -> 41241 bytes po/sk.po | 1179 +- po/sv.gmo | Bin 93590 -> 93215 bytes po/sv.po | 1179 +- po/tr.gmo | Bin 90978 -> 90654 bytes po/tr.po | 1179 +- po/uk.gmo | Bin 61069 -> 60700 bytes po/uk.po | 1179 +- po/zh_CN.gmo | Bin 40545 -> 40226 bytes po/zh_CN.po | 1179 +- po/zh_TW.gmo | Bin 58368 -> 58053 bytes po/zh_TW.po | 1179 +- pop.c | 32 +- pop_auth.c | 2 +- pop_lib.c | 30 +- postpone.c | 106 +- protos.h | 13 +- query.c | 12 +- recvattach.c | 19 +- recvcmd.c | 40 +- regex.c | 13 +- remailer.c | 2 +- resize.c | 10 +- rfc1524.c | 10 +- rfc3676.c | 139 +- rfc822.c | 16 +- rfc822.h | 4 +- score.c | 7 +- send.c | 77 +- sendlib.c | 632 +- smime.c | 135 +- smtp.c | 59 +- strcasestr.c | 48 + thread.c | 12 +- url.c | 6 +- wcscasecmp.c | 45 + 572 files changed, 165920 insertions(+), 33922 deletions(-) create mode 100644 .gitignore create mode 100644 .pc/.version create mode 100644 debian/stamp-patched create mode 100644 doc/security.html delete mode 100644 m4/libgnutls.m4 create mode 100644 mkdtemp.c create mode 100644 obj-i486-linux-gnu-patched/Makefile create mode 100644 obj-i486-linux-gnu-patched/account.o create mode 100644 obj-i486-linux-gnu-patched/addrbook.o create mode 100644 obj-i486-linux-gnu-patched/alias.o create mode 100644 obj-i486-linux-gnu-patched/ascii.o create mode 100644 obj-i486-linux-gnu-patched/attach.o create mode 100644 obj-i486-linux-gnu-patched/base64.o create mode 100644 obj-i486-linux-gnu-patched/bcache.o create mode 100644 obj-i486-linux-gnu-patched/browser.o create mode 100644 obj-i486-linux-gnu-patched/buffy.o create mode 100644 obj-i486-linux-gnu-patched/build-stamp create mode 100644 obj-i486-linux-gnu-patched/charset.o create mode 100644 obj-i486-linux-gnu-patched/color.o create mode 100644 obj-i486-linux-gnu-patched/commands.o create mode 100644 obj-i486-linux-gnu-patched/complete.o create mode 100644 obj-i486-linux-gnu-patched/compose.o create mode 100644 obj-i486-linux-gnu-patched/compress.o create mode 100644 obj-i486-linux-gnu-patched/config.h create mode 100644 obj-i486-linux-gnu-patched/config.log create mode 100755 obj-i486-linux-gnu-patched/config.status create mode 100644 obj-i486-linux-gnu-patched/contrib/Makefile create mode 100644 obj-i486-linux-gnu-patched/copy.o create mode 100644 obj-i486-linux-gnu-patched/crypt-gpgme.o create mode 100644 obj-i486-linux-gnu-patched/crypt-mod-pgp-classic.o create mode 100644 obj-i486-linux-gnu-patched/crypt-mod-pgp-gpgme.o create mode 100644 obj-i486-linux-gnu-patched/crypt-mod-smime-classic.o create mode 100644 obj-i486-linux-gnu-patched/crypt-mod-smime-gpgme.o create mode 100644 obj-i486-linux-gnu-patched/crypt-mod.o create mode 100644 obj-i486-linux-gnu-patched/crypt.o create mode 100644 obj-i486-linux-gnu-patched/cryptglue.o create mode 100644 obj-i486-linux-gnu-patched/curs_lib.o create mode 100644 obj-i486-linux-gnu-patched/curs_main.o create mode 100644 obj-i486-linux-gnu-patched/date.o create mode 100644 obj-i486-linux-gnu-patched/doc/Makefile create mode 100644 obj-i486-linux-gnu-patched/doc/Muttrc create mode 100644 obj-i486-linux-gnu-patched/doc/advancedusage.html create mode 100644 obj-i486-linux-gnu-patched/doc/configuration.html create mode 100644 obj-i486-linux-gnu-patched/doc/gettingstarted.html create mode 100644 obj-i486-linux-gnu-patched/doc/index.html create mode 100644 obj-i486-linux-gnu-patched/doc/instdoc.sh create mode 100644 obj-i486-linux-gnu-patched/doc/intro.html create mode 100755 obj-i486-linux-gnu-patched/doc/makedoc create mode 100644 obj-i486-linux-gnu-patched/doc/makedoc.o create mode 100644 obj-i486-linux-gnu-patched/doc/manual.html create mode 100644 obj-i486-linux-gnu-patched/doc/manual.txt create mode 100644 obj-i486-linux-gnu-patched/doc/manual.xml create mode 100644 obj-i486-linux-gnu-patched/doc/mimesupport.html create mode 100644 obj-i486-linux-gnu-patched/doc/miscellany.html create mode 100644 obj-i486-linux-gnu-patched/doc/mutt.1 create mode 100644 obj-i486-linux-gnu-patched/doc/muttrc.man create mode 100644 obj-i486-linux-gnu-patched/doc/optionalfeatures.html create mode 100644 obj-i486-linux-gnu-patched/doc/reference.html create mode 100644 obj-i486-linux-gnu-patched/doc/smime_keys.1 create mode 100644 obj-i486-linux-gnu-patched/doc/stamp-doc-chunked create mode 100644 obj-i486-linux-gnu-patched/doc/stamp-doc-rc create mode 100644 obj-i486-linux-gnu-patched/doc/stamp-doc-xml create mode 100644 obj-i486-linux-gnu-patched/doc/tuning.html create mode 100644 obj-i486-linux-gnu-patched/edit.o create mode 100644 obj-i486-linux-gnu-patched/editmsg.o create mode 100644 obj-i486-linux-gnu-patched/enter.o create mode 100644 obj-i486-linux-gnu-patched/extlib.o create mode 100644 obj-i486-linux-gnu-patched/filter.o create mode 100644 obj-i486-linux-gnu-patched/flags.o create mode 100755 obj-i486-linux-gnu-patched/flea create mode 100644 obj-i486-linux-gnu-patched/from.o create mode 100644 obj-i486-linux-gnu-patched/getdomain.o create mode 100644 obj-i486-linux-gnu-patched/gnupgparse.o create mode 100644 obj-i486-linux-gnu-patched/group.o create mode 100644 obj-i486-linux-gnu-patched/handler.o create mode 100644 obj-i486-linux-gnu-patched/hash.o create mode 100644 obj-i486-linux-gnu-patched/hcache.o create mode 100644 obj-i486-linux-gnu-patched/hcachever.sh create mode 100644 obj-i486-linux-gnu-patched/hcversion.h create mode 100644 obj-i486-linux-gnu-patched/hdrline.o create mode 100644 obj-i486-linux-gnu-patched/headers.o create mode 100644 obj-i486-linux-gnu-patched/help.o create mode 100644 obj-i486-linux-gnu-patched/history.o create mode 100644 obj-i486-linux-gnu-patched/hook.o create mode 100644 obj-i486-linux-gnu-patched/imap/Makefile create mode 100644 obj-i486-linux-gnu-patched/imap/auth.o create mode 100644 obj-i486-linux-gnu-patched/imap/auth_gss.o create mode 100644 obj-i486-linux-gnu-patched/imap/auth_login.o create mode 100644 obj-i486-linux-gnu-patched/imap/auth_sasl.o create mode 100644 obj-i486-linux-gnu-patched/imap/browse.o create mode 100644 obj-i486-linux-gnu-patched/imap/command.o create mode 100644 obj-i486-linux-gnu-patched/imap/imap.o create mode 100644 obj-i486-linux-gnu-patched/imap/libimap.a create mode 100644 obj-i486-linux-gnu-patched/imap/message.o create mode 100644 obj-i486-linux-gnu-patched/imap/utf7.o create mode 100644 obj-i486-linux-gnu-patched/imap/util.o create mode 100644 obj-i486-linux-gnu-patched/init.o create mode 100644 obj-i486-linux-gnu-patched/intl/Makefile create mode 100644 obj-i486-linux-gnu-patched/keymap.o create mode 100644 obj-i486-linux-gnu-patched/keymap_defs.h create mode 100644 obj-i486-linux-gnu-patched/lib.o create mode 100644 obj-i486-linux-gnu-patched/m4/Makefile create mode 100644 obj-i486-linux-gnu-patched/main.o create mode 100644 obj-i486-linux-gnu-patched/mbox.o create mode 100644 obj-i486-linux-gnu-patched/mbyte.o create mode 100644 obj-i486-linux-gnu-patched/md5.o create mode 100644 obj-i486-linux-gnu-patched/menu.o create mode 100644 obj-i486-linux-gnu-patched/mh.o create mode 100755 obj-i486-linux-gnu-patched/mutt create mode 100755 obj-i486-linux-gnu-patched/mutt_dotlock create mode 100644 obj-i486-linux-gnu-patched/mutt_dotlock.o create mode 100644 obj-i486-linux-gnu-patched/mutt_idna.o create mode 100755 obj-i486-linux-gnu-patched/mutt_md5 create mode 100644 obj-i486-linux-gnu-patched/mutt_md5-md5.o create mode 100644 obj-i486-linux-gnu-patched/mutt_sasl.o create mode 100644 obj-i486-linux-gnu-patched/mutt_socket.o create mode 100644 obj-i486-linux-gnu-patched/mutt_ssl_gnutls.o create mode 100644 obj-i486-linux-gnu-patched/mutt_tunnel.o create mode 100644 obj-i486-linux-gnu-patched/muttbug.sh create mode 100644 obj-i486-linux-gnu-patched/muttlib.o create mode 100644 obj-i486-linux-gnu-patched/mx.o create mode 100644 obj-i486-linux-gnu-patched/pager.o create mode 100644 obj-i486-linux-gnu-patched/parse.o create mode 100644 obj-i486-linux-gnu-patched/patchlist.c create mode 100644 obj-i486-linux-gnu-patched/patchlist.o create mode 100644 obj-i486-linux-gnu-patched/pattern.o create mode 100644 obj-i486-linux-gnu-patched/pgp.o create mode 100755 obj-i486-linux-gnu-patched/pgpewrap create mode 100644 obj-i486-linux-gnu-patched/pgpewrap.o create mode 100644 obj-i486-linux-gnu-patched/pgpinvoke.o create mode 100644 obj-i486-linux-gnu-patched/pgpkey.o create mode 100644 obj-i486-linux-gnu-patched/pgplib.o create mode 100644 obj-i486-linux-gnu-patched/pgpmicalg.o create mode 100644 obj-i486-linux-gnu-patched/pgppacket.o create mode 100644 obj-i486-linux-gnu-patched/pgppubring.o create mode 100755 obj-i486-linux-gnu-patched/pgpring create mode 100644 obj-i486-linux-gnu-patched/po/Makefile create mode 100644 obj-i486-linux-gnu-patched/po/Makefile.in create mode 100644 obj-i486-linux-gnu-patched/po/POTFILES create mode 100644 obj-i486-linux-gnu-patched/po/bg.gmo create mode 100644 obj-i486-linux-gnu-patched/po/ca.gmo create mode 100644 obj-i486-linux-gnu-patched/po/cs.gmo create mode 100644 obj-i486-linux-gnu-patched/po/da.gmo create mode 100644 obj-i486-linux-gnu-patched/po/de.gmo create mode 100644 obj-i486-linux-gnu-patched/po/el.gmo create mode 100644 obj-i486-linux-gnu-patched/po/eo.gmo create mode 100644 obj-i486-linux-gnu-patched/po/es.gmo create mode 100644 obj-i486-linux-gnu-patched/po/et.gmo create mode 100644 obj-i486-linux-gnu-patched/po/eu.gmo create mode 100644 obj-i486-linux-gnu-patched/po/fr.gmo create mode 100644 obj-i486-linux-gnu-patched/po/ga.gmo create mode 100644 obj-i486-linux-gnu-patched/po/gl.gmo create mode 100644 obj-i486-linux-gnu-patched/po/hu.gmo create mode 100644 obj-i486-linux-gnu-patched/po/id.gmo create mode 100644 obj-i486-linux-gnu-patched/po/it.gmo create mode 100644 obj-i486-linux-gnu-patched/po/ja.gmo create mode 100644 obj-i486-linux-gnu-patched/po/ko.gmo create mode 100644 obj-i486-linux-gnu-patched/po/lt.gmo create mode 100644 obj-i486-linux-gnu-patched/po/nl.gmo create mode 100644 obj-i486-linux-gnu-patched/po/pl.gmo create mode 100644 obj-i486-linux-gnu-patched/po/pt_BR.gmo create mode 100644 obj-i486-linux-gnu-patched/po/ru.gmo create mode 100644 obj-i486-linux-gnu-patched/po/sk.gmo create mode 100644 obj-i486-linux-gnu-patched/po/sv.gmo create mode 100644 obj-i486-linux-gnu-patched/po/tr.gmo create mode 100644 obj-i486-linux-gnu-patched/po/uk.gmo create mode 100644 obj-i486-linux-gnu-patched/po/zh_CN.gmo create mode 100644 obj-i486-linux-gnu-patched/po/zh_TW.gmo create mode 100644 obj-i486-linux-gnu-patched/pop.o create mode 100644 obj-i486-linux-gnu-patched/pop_auth.o create mode 100644 obj-i486-linux-gnu-patched/pop_lib.o create mode 100644 obj-i486-linux-gnu-patched/postpone.o create mode 100644 obj-i486-linux-gnu-patched/query.o create mode 100644 obj-i486-linux-gnu-patched/recvattach.o create mode 100644 obj-i486-linux-gnu-patched/recvcmd.o create mode 100644 obj-i486-linux-gnu-patched/reldate.h create mode 100644 obj-i486-linux-gnu-patched/remailer.o create mode 100644 obj-i486-linux-gnu-patched/resize.o create mode 100644 obj-i486-linux-gnu-patched/rfc1524.o create mode 100644 obj-i486-linux-gnu-patched/rfc2047.o create mode 100644 obj-i486-linux-gnu-patched/rfc2231.o create mode 100644 obj-i486-linux-gnu-patched/rfc3676.o create mode 100644 obj-i486-linux-gnu-patched/rfc822.o create mode 100644 obj-i486-linux-gnu-patched/score.o create mode 100644 obj-i486-linux-gnu-patched/send.o create mode 100644 obj-i486-linux-gnu-patched/sendlib.o create mode 100644 obj-i486-linux-gnu-patched/sha1.o create mode 100644 obj-i486-linux-gnu-patched/sidebar.o create mode 100644 obj-i486-linux-gnu-patched/signal.o create mode 100644 obj-i486-linux-gnu-patched/smime.o create mode 100755 obj-i486-linux-gnu-patched/smime_keys create mode 100644 obj-i486-linux-gnu-patched/smtp.o create mode 100644 obj-i486-linux-gnu-patched/sort.o create mode 100644 obj-i486-linux-gnu-patched/stamp-h1 create mode 100644 obj-i486-linux-gnu-patched/status.o create mode 100644 obj-i486-linux-gnu-patched/system.o create mode 100644 obj-i486-linux-gnu-patched/thread.o create mode 100644 obj-i486-linux-gnu-patched/url.o create mode 100644 obj-i486-linux-gnu/Makefile create mode 100644 obj-i486-linux-gnu/account.o create mode 100644 obj-i486-linux-gnu/addrbook.o create mode 100644 obj-i486-linux-gnu/alias.o create mode 100644 obj-i486-linux-gnu/ascii.o create mode 100644 obj-i486-linux-gnu/attach.o create mode 100644 obj-i486-linux-gnu/base64.o create mode 100644 obj-i486-linux-gnu/bcache.o create mode 100644 obj-i486-linux-gnu/browser.o create mode 100644 obj-i486-linux-gnu/buffy.o create mode 100644 obj-i486-linux-gnu/build-stamp create mode 100644 obj-i486-linux-gnu/charset.o create mode 100644 obj-i486-linux-gnu/color.o create mode 100644 obj-i486-linux-gnu/commands.o create mode 100644 obj-i486-linux-gnu/complete.o create mode 100644 obj-i486-linux-gnu/compose.o create mode 100644 obj-i486-linux-gnu/compress.o create mode 100644 obj-i486-linux-gnu/config.h create mode 100644 obj-i486-linux-gnu/config.log create mode 100755 obj-i486-linux-gnu/config.status create mode 100644 obj-i486-linux-gnu/contrib/Makefile create mode 100644 obj-i486-linux-gnu/copy.o create mode 100644 obj-i486-linux-gnu/crypt-gpgme.o create mode 100644 obj-i486-linux-gnu/crypt-mod-pgp-classic.o create mode 100644 obj-i486-linux-gnu/crypt-mod-pgp-gpgme.o create mode 100644 obj-i486-linux-gnu/crypt-mod-smime-classic.o create mode 100644 obj-i486-linux-gnu/crypt-mod-smime-gpgme.o create mode 100644 obj-i486-linux-gnu/crypt-mod.o create mode 100644 obj-i486-linux-gnu/crypt.o create mode 100644 obj-i486-linux-gnu/cryptglue.o create mode 100644 obj-i486-linux-gnu/curs_lib.o create mode 100644 obj-i486-linux-gnu/curs_main.o create mode 100644 obj-i486-linux-gnu/date.o create mode 100644 obj-i486-linux-gnu/doc/Makefile create mode 100644 obj-i486-linux-gnu/doc/Muttrc create mode 100644 obj-i486-linux-gnu/doc/advancedusage.html create mode 100644 obj-i486-linux-gnu/doc/configuration.html create mode 100644 obj-i486-linux-gnu/doc/gettingstarted.html create mode 100644 obj-i486-linux-gnu/doc/index.html create mode 100755 obj-i486-linux-gnu/doc/instdoc create mode 100644 obj-i486-linux-gnu/doc/instdoc.sh create mode 100644 obj-i486-linux-gnu/doc/intro.html create mode 100755 obj-i486-linux-gnu/doc/makedoc create mode 100644 obj-i486-linux-gnu/doc/makedoc.o create mode 100644 obj-i486-linux-gnu/doc/manual.html create mode 100644 obj-i486-linux-gnu/doc/manual.txt create mode 100644 obj-i486-linux-gnu/doc/manual.xml create mode 100644 obj-i486-linux-gnu/doc/mimesupport.html create mode 100644 obj-i486-linux-gnu/doc/miscellany.html create mode 100644 obj-i486-linux-gnu/doc/mutt.1 create mode 100644 obj-i486-linux-gnu/doc/muttrc.man create mode 100644 obj-i486-linux-gnu/doc/optionalfeatures.html create mode 100644 obj-i486-linux-gnu/doc/reference.html create mode 100644 obj-i486-linux-gnu/doc/smime_keys.1 create mode 100644 obj-i486-linux-gnu/doc/stamp-doc-chunked create mode 100644 obj-i486-linux-gnu/doc/stamp-doc-rc create mode 100644 obj-i486-linux-gnu/doc/stamp-doc-xml create mode 100644 obj-i486-linux-gnu/doc/tuning.html create mode 100644 obj-i486-linux-gnu/edit.o create mode 100644 obj-i486-linux-gnu/editmsg.o create mode 100644 obj-i486-linux-gnu/enter.o create mode 100644 obj-i486-linux-gnu/extlib.o create mode 100644 obj-i486-linux-gnu/filter.o create mode 100644 obj-i486-linux-gnu/flags.o create mode 100755 obj-i486-linux-gnu/flea create mode 100644 obj-i486-linux-gnu/from.o create mode 100644 obj-i486-linux-gnu/getdomain.o create mode 100644 obj-i486-linux-gnu/gnupgparse.o create mode 100644 obj-i486-linux-gnu/group.o create mode 100644 obj-i486-linux-gnu/handler.o create mode 100644 obj-i486-linux-gnu/hash.o create mode 100644 obj-i486-linux-gnu/hcache.o create mode 100644 obj-i486-linux-gnu/hcachever.sh create mode 100644 obj-i486-linux-gnu/hcversion.h create mode 100644 obj-i486-linux-gnu/hdrline.o create mode 100644 obj-i486-linux-gnu/headers.o create mode 100644 obj-i486-linux-gnu/help.o create mode 100644 obj-i486-linux-gnu/history.o create mode 100644 obj-i486-linux-gnu/hook.o create mode 100644 obj-i486-linux-gnu/imap/Makefile create mode 100644 obj-i486-linux-gnu/imap/auth.o create mode 100644 obj-i486-linux-gnu/imap/auth_gss.o create mode 100644 obj-i486-linux-gnu/imap/auth_login.o create mode 100644 obj-i486-linux-gnu/imap/auth_sasl.o create mode 100644 obj-i486-linux-gnu/imap/browse.o create mode 100644 obj-i486-linux-gnu/imap/command.o create mode 100644 obj-i486-linux-gnu/imap/imap.o create mode 100644 obj-i486-linux-gnu/imap/libimap.a create mode 100644 obj-i486-linux-gnu/imap/message.o create mode 100644 obj-i486-linux-gnu/imap/utf7.o create mode 100644 obj-i486-linux-gnu/imap/util.o create mode 100644 obj-i486-linux-gnu/init.o create mode 100644 obj-i486-linux-gnu/intl/Makefile create mode 100644 obj-i486-linux-gnu/keymap.o create mode 100644 obj-i486-linux-gnu/keymap_defs.h create mode 100644 obj-i486-linux-gnu/lib.o create mode 100644 obj-i486-linux-gnu/m4/Makefile create mode 100644 obj-i486-linux-gnu/main.o create mode 100644 obj-i486-linux-gnu/mbox.o create mode 100644 obj-i486-linux-gnu/mbyte.o create mode 100644 obj-i486-linux-gnu/md5.o create mode 100644 obj-i486-linux-gnu/menu.o create mode 100644 obj-i486-linux-gnu/mh.o create mode 100755 obj-i486-linux-gnu/mutt create mode 100755 obj-i486-linux-gnu/mutt_dotlock create mode 100644 obj-i486-linux-gnu/mutt_dotlock.o create mode 100644 obj-i486-linux-gnu/mutt_idna.o create mode 100755 obj-i486-linux-gnu/mutt_md5 create mode 100644 obj-i486-linux-gnu/mutt_md5-md5.o create mode 100644 obj-i486-linux-gnu/mutt_sasl.o create mode 100644 obj-i486-linux-gnu/mutt_socket.o create mode 100644 obj-i486-linux-gnu/mutt_ssl_gnutls.o create mode 100644 obj-i486-linux-gnu/mutt_tunnel.o create mode 100644 obj-i486-linux-gnu/muttbug.sh create mode 100644 obj-i486-linux-gnu/muttlib.o create mode 100644 obj-i486-linux-gnu/mx.o create mode 100644 obj-i486-linux-gnu/pager.o create mode 100644 obj-i486-linux-gnu/parse.o create mode 100644 obj-i486-linux-gnu/patchlist.c create mode 100644 obj-i486-linux-gnu/patchlist.o create mode 100644 obj-i486-linux-gnu/pattern.o create mode 100644 obj-i486-linux-gnu/pgp.o create mode 100755 obj-i486-linux-gnu/pgpewrap create mode 100644 obj-i486-linux-gnu/pgpewrap.o create mode 100644 obj-i486-linux-gnu/pgpinvoke.o create mode 100644 obj-i486-linux-gnu/pgpkey.o create mode 100644 obj-i486-linux-gnu/pgplib.o create mode 100644 obj-i486-linux-gnu/pgpmicalg.o create mode 100644 obj-i486-linux-gnu/pgppacket.o create mode 100644 obj-i486-linux-gnu/pgppubring.o create mode 100755 obj-i486-linux-gnu/pgpring create mode 100644 obj-i486-linux-gnu/po/Makefile create mode 100644 obj-i486-linux-gnu/po/Makefile.in create mode 100644 obj-i486-linux-gnu/po/POTFILES create mode 100644 obj-i486-linux-gnu/po/bg.gmo create mode 100644 obj-i486-linux-gnu/po/ca.gmo create mode 100644 obj-i486-linux-gnu/po/cs.gmo create mode 100644 obj-i486-linux-gnu/po/da.gmo create mode 100644 obj-i486-linux-gnu/po/de.gmo create mode 100644 obj-i486-linux-gnu/po/el.gmo create mode 100644 obj-i486-linux-gnu/po/eo.gmo create mode 100644 obj-i486-linux-gnu/po/es.gmo create mode 100644 obj-i486-linux-gnu/po/et.gmo create mode 100644 obj-i486-linux-gnu/po/eu.gmo create mode 100644 obj-i486-linux-gnu/po/fr.gmo create mode 100644 obj-i486-linux-gnu/po/ga.gmo create mode 100644 obj-i486-linux-gnu/po/gl.gmo create mode 100644 obj-i486-linux-gnu/po/hu.gmo create mode 100644 obj-i486-linux-gnu/po/id.gmo create mode 100644 obj-i486-linux-gnu/po/it.gmo create mode 100644 obj-i486-linux-gnu/po/ja.gmo create mode 100644 obj-i486-linux-gnu/po/ko.gmo create mode 100644 obj-i486-linux-gnu/po/lt.gmo create mode 100644 obj-i486-linux-gnu/po/nl.gmo create mode 100644 obj-i486-linux-gnu/po/pl.gmo create mode 100644 obj-i486-linux-gnu/po/pt_BR.gmo create mode 100644 obj-i486-linux-gnu/po/ru.gmo create mode 100644 obj-i486-linux-gnu/po/sk.gmo create mode 100644 obj-i486-linux-gnu/po/sv.gmo create mode 100644 obj-i486-linux-gnu/po/tr.gmo create mode 100644 obj-i486-linux-gnu/po/uk.gmo create mode 100644 obj-i486-linux-gnu/po/zh_CN.gmo create mode 100644 obj-i486-linux-gnu/po/zh_TW.gmo create mode 100644 obj-i486-linux-gnu/pop.o create mode 100644 obj-i486-linux-gnu/pop_auth.o create mode 100644 obj-i486-linux-gnu/pop_lib.o create mode 100644 obj-i486-linux-gnu/postpone.o create mode 100644 obj-i486-linux-gnu/query.o create mode 100644 obj-i486-linux-gnu/recvattach.o create mode 100644 obj-i486-linux-gnu/recvcmd.o create mode 100644 obj-i486-linux-gnu/reldate.h create mode 100644 obj-i486-linux-gnu/remailer.o create mode 100644 obj-i486-linux-gnu/resize.o create mode 100644 obj-i486-linux-gnu/rfc1524.o create mode 100644 obj-i486-linux-gnu/rfc2047.o create mode 100644 obj-i486-linux-gnu/rfc2231.o create mode 100644 obj-i486-linux-gnu/rfc3676.o create mode 100644 obj-i486-linux-gnu/rfc822.o create mode 100644 obj-i486-linux-gnu/score.o create mode 100644 obj-i486-linux-gnu/send.o create mode 100644 obj-i486-linux-gnu/sendlib.o create mode 100644 obj-i486-linux-gnu/sha1.o create mode 100644 obj-i486-linux-gnu/signal.o create mode 100644 obj-i486-linux-gnu/smime.o create mode 100755 obj-i486-linux-gnu/smime_keys create mode 100644 obj-i486-linux-gnu/smtp.o create mode 100644 obj-i486-linux-gnu/sort.o create mode 100644 obj-i486-linux-gnu/stamp-h1 create mode 100644 obj-i486-linux-gnu/status.o create mode 100644 obj-i486-linux-gnu/system.o create mode 100644 obj-i486-linux-gnu/thread.o create mode 100644 obj-i486-linux-gnu/url.o create mode 100644 strcasestr.c create mode 100644 wcscasecmp.c diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..4400ec4 --- /dev/null +++ b/.gitignore @@ -0,0 +1,34 @@ +.deps/ +.pc/ +Makefile +Makefile.in +aclocal.m4 +autom4te.cache/ +config.h +config.h.in +config.h.in~ +config.log +config.status +configure +contrib/Makefile +contrib/Makefile.in +doc/.deps/ +doc/Makefile +doc/Makefile.in +doc/instdoc.sh +hcachever.sh +imap/.deps/ +imap/Makefile +imap/Makefile.in +intl/Makefile +m4/Makefile +m4/Makefile.in +muttbug.sh +po/Makefile +po/Makefile.in +po/POTFILES +stamp-h1 +.gitignore +debian/stamp-patched +obj-i486-linux-gnu-patched/ +obj-i486-linux-gnu/ diff --git a/.pc/.version b/.pc/.version new file mode 100644 index 0000000..0cfbf08 --- /dev/null +++ b/.pc/.version @@ -0,0 +1 @@ +2 diff --git a/ChangeLog b/ChangeLog index dd135e4..3d0ed82 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,4 +1,967 @@ -2009-01-05 16:35 -0800 Brendan Cully (a170f93fc5b1) +2009-06-14 10:43 -0700 Brendan Cully (a18e286f4365) + + * imap/imap.c: Save a dereference, and close #3226 with voodoo. + + * sendlib.c: Initialize pointer before use under -d4 + +2009-06-13 19:52 -0700 Brendan Cully (83ffb5593bc6) + + * curs_main.c: Adjust menu position after sync more + carefully. Closes #3092. + + * init.h: Force status to redraw when $postponed changes. + + * postpone.c: Fix check for changed $postponed. The pointer-based + check fails when the new $postponed string is stored in the same + location. + +2009-06-13 01:08 +0200 Rocco Rutte (536771b4e085) + + * commands.c, copy.c, copy.h, handler.c, protos.h, send.c, sendlib.c: + Rewrite header folding + + We now distinct between sending and display case. For display, we + always use tabs for folding for readability; for sending we now + correctly fold using whitespace found in the header. + + Closes #2995. Closes #3080. + +2009-06-12 23:10 +0200 Rocco Rutte (23de0e3c81f8) + + * UPDATING, init.h, mutt.h, send.c: Turn $fcc_attach into a + quadoption. Closes #2528. + + * handler.c: Don't insert Content-Description/form name into reply. + Closes #3164. + + * pgpkey.c: Allow ! suffix for pgp keys via $pgp_sign_as and + prompt. Closes #1928. + + * commands.c, recvcmd.c: Warn before bouncing messages without + From: header. Closes #3180. + + * smtp.c: SMTP: don't block but print CRLF for last line if it's + not terminated + +2009-06-11 18:34 +0200 Rocco Rutte (f60eb41ef63c) + + * UPDATING: Mention maildir mtime use in browser + + * send.c: Don't allow setting Return-Path: header via my_hdr + + Mutt has use_envelope_from/envelope_from_address for that purpose. + Closes #1840. + + * browser.c: Use only latest mtime of new/cur for browser, not whole + stat() info + + * copy.c: Don't reformat Return-Path (angle brackets are not + optional). Closes #1702. + +2009-06-10 17:44 +0200 Rocco Rutte (0721c3f6320d) + + * mbox.c, mx.c: Only print messages about CONTEXT when quiet flag not + set + +2009-06-09 22:09 -0700 Brendan Cully (dc9ec900c657) + + * mutt_ssl.c: Improve host checking for SSL with intermediate + certificates. + + * mutt_ssl.c: Whitespace. + + * imap/imap.c: Skip comparison against current mailbox for idle + connections. Closes #3216. + + * imap/util.c: Revert accidental change + + * imap/util.c: Remove trailing whitespace. + +2009-06-08 23:55 -0700 Brendan Cully (15c662a95b91) + + * configure.ac, m4/libgnutls.m4: Test for libgnutls by hand rather + than relying on deprecated libgnutls-config script. Closes #3239. + +2009-06-07 10:55 -0700 Brendan Cully (9831d4c2c3f9) + + * imap/message.c: Do not display error message when user declines + to create target mailbox. + + * imap/message.c: Minor cleanup in imap_copy_messages. + +2009-06-07 08:14 +0200 Miroslav Lichvar (16592f0dfdaf) + + * configure.ac, mutt_ssl_gnutls.c: Disable checking certificate + activation/expiration times in gnutls as we do the checks ourselves. + +2009-06-06 22:31 -0700 Brendan Cully (e5c2befbf0f5) + + * imap/message.c: Do not treat already-seen headers as if they are + new. See #2935. + +2009-06-07 02:09 +0200 Rocco Rutte (a786b0e8627c) + + * doc/dotlock.man, doc/makedoc.c, doc/mbox.man, doc/mmdf.man, + doc/mutt.man, init.h: Fix hyphens in manpages. Closes #1937 + +2009-06-04 17:07 +0200 Rocco Rutte (4f1ceaae93dc) + + * rfc3676.c: Fix pretty quoting for f=f by resetting space count when + flushing paragraph + +2009-06-03 22:35 +0200 Rocco Rutte (386f2ce6b872) + + * rfc3676.c: Fix several f=f bugs + + It fixes problems with space-handling in general (trailing spaces + for display, un-space-stuffing), fixes quote prefix for replies and + lowers FLOWED_MAX so we don't run into line length trouble too + early. + + * UPDATING, globals.h, init.h, pager.c: Don't abuse $pager_context for + searches, add $search_context. See #976. + + * pattern.c: Fix compiler warning + +2009-06-02 20:25 +0200 Miroslav Lichvar (d1d0481d1ca1) + + * mutt_ssl_gnutls.c: Add support for GNUTLS_CERT_INSECURE_ALGORITHM + error code + + * mutt_ssl_gnutls.c: Don't ignore certificate verification errors on + saved signer certs + +2009-06-02 10:18 -0700 René Clerc (761bc678b23e) + + * po/nl.po: Updated Dutch translation. + +2009-06-02 17:24 +0200 Rocco Rutte (8b2af5b64981) + + * buffy.c: Fix duplicate mailbox detection for remote + folders + + * smtp.c: Fix array size + + * buffy.c: Thoroughly check for duplicates when parsing + 'mailboxes' command. Closes #1428. + +2009-06-01 14:50 +0200 Rocco Rutte (7a277ba306c9) + + * gnupgparse.c: Use mutt_atoi() when parsing GnuPG output. Closes + #3145 + + * hcache.c, mh.c: More atoi() fixes + + * smtp.c: SMTP: Use mutt_atoi() to parse server responses + + * curs_main.c, edit.c, init.c, main.c, menu.c, mh.c, parse.c, + resize.c, score.c, url.c: Use strtol() wrappers for most atoi() + calls + + * lib.c, lib.h: Add mutt_atos(), mutt_atoi() and + mutt_atol() (strtol() wrappers) + + * send.c: Treat address groups as no recipients + + When sending with Sendmail or SMTP we exclude address groups anyway, + so treat these addresses as not present when checking for valid + recipients before sending in the compose menu. + + * smtp.c: Weed out address groups for SMTP the same way we + do for sendmail + +2009-05-31 19:19 -0700 Brendan Cully (0024860ab03e) + + * doc/Makefile.am: Allow chunked and unchunked manuals to build in + parallel. + + * mutt_ssl_gnutls.c: Remove trailing whitespace + +2009-05-31 14:46 +0200 Rocco Rutte (8e591e80cd48) + + * smtp.c: SMTP: Don't send "undisclosed-recipients" in RCPT TO + + This happened for Bcc only messages. "undisclosed-recipients" is + added in To: as guard against MTAs that leak BCCs if no To:/Cc: + header is given. See Debian #529090. + + * init.h: Document that $pager_context affects searching, too + + * UPDATING: Update UPDATING + + * handler.c: Turn trailing \r\n to \n for qp-encoded messages. + + RFC2045 (sect. 6.7, (1) general 8bit representation) states that + neither CR nor LF of the trailing CRLF may be qp-encoded. So we + ignore trailing qp-encoded CRs. + + See #2898 though this is a partial fix only. + + * pager.c: Give $pager_context lines of context when searching + page-based menus. Closes #976. + + * handler.c, init.h, rfc3676.c: f=f: Strip trailing spaces for + interoperability. Closes #3001. + + If we make a fixed reply to a flowed message we remove trailing + spaces and can now safely allow $indent_string to be used which is + what users expect. + + Second, if we make a flowed reply to a fixed message we also strip + trailing spaces since from format=fixed we assume all lines are + fixed (i.e. we don't want to errorneously make fixed lines flowed). + + * handler.c, init.h, mutt.h: Add $honor_disposition to not display + attachments inline. Closes #3170. + + Previously all MIME parts were displayed inline regardless of the + Content-Disposition header (if present). With $honor_disposition + set, only inline parts are displayed inline, attachments can only be + viewed from the attachments menu. + +2009-04-25 01:56 -0400 Dan Loewenherz (c1b947f60ea6) + + * init.h: Disables the insecure SSLv2 protocol. Closes #3192. + +2009-05-30 19:37 +0200 Rocco Rutte (b080ae086a62) + + * ChangeLog, mbox.c: Keep new mail flag for mbox/mmdf folders after + closing. Closes #1362. + +2009-05-30 10:23 -0700 Vincent Lefevre (be7b3d349725) + + * po/fr.po: Updated French translation. + +2009-05-30 00:24 +0200 Rocco Rutte (f65a1eb8abce) + + * smtp.c: Fix logic in f260f5836284 + +2009-05-29 21:33 +0200 Rocco Rutte (c4d86d4ea260) + + * pager.c: Drop modified version of and use mutt_read_line() in pager, + too + + * history.c, init.c, lib.c, lib.h, mh.c, mutt_ssl_gnutls.c, pgp.c, + query.c, rfc1524.c, smime.c: Add flags to mutt_read_line() for + EOL-stripping and continuation support + + We use these to stop supporting EOL-escaping with \ which was wrong + in most cases (e.g. $history_file), support is kept for reading + config and mailcap files. + + Leaving CRLF in will be used for the pager. + + * menu.c, pager.c, pattern.c: Fall back to search if no query exists + for search-(next|opposite) + + The pager had the fall-through to search, so for consistency do that + in other menues as well. + + * pager.c: Fix pager search prompt for reverse search + + When doing a reverse search for the first time after switching to + the pager, SearchBack is always 0 and thus gave the wrong prompt, + change to using op directly. While I'm at it, unify search prompts. + + * doc/manual.xml.head: Manual: Fix markup of environment variables + +2009-05-28 16:37 +0200 Rocco Rutte (f260f5836284) + + * smtp.c: SMTP: don't interactively authenticate without a + password in batch/mailx mode + + Otherwise, if we don't have a password and curses is not running, + the SASL authentication callback will crash mutt. We now abort if + the password wasn't given in $smtp_url. + + * doc/mutt.css: Manual: vertical-align table cells at the top + + * doc/manual.xml.head, doc/mutt.css: Manual: Wrap muttrc commands + in + +2009-05-27 23:14 -0700 Brendan Cully (5502fb790bab) + + * mutt_ssl_gnutls.c: gnutls: do not ignore certificate problems. + Specifically, do not allow revoked certificates or those signed by + non-CAs unless they have been explicitly stored in the trusted + certificate file. Thanks to Miroslav Lichvar. + +2009-05-27 22:55 -0700 Miroslav Lichvar (85f41efec6bf) + + * ChangeLog, mutt_ssl_gnutls.c: Don't prompt to save certificates that + are already saved but invalid. + +2009-05-27 22:52 -0700 Brendan Cully (90ef283c103e) + + * mutt_ssl_gnutls.c: Don't leak gnutls certs on preauth validation + failure. Thanks to Miroslav Lichvar. + + * mutt_ssl.c: Fix TLS certificate chain validation for + openssl. + +2009-05-25 17:31 -0700 Brendan Cully (8f11dd00c770) + + * mutt_ssl_gnutls.c: Fix a serious oversight validating TLS + certificates. If any certificate in a chain presented by a server + was accepted, the connection was allowed without verifying that the + presented certificate was actually signed by the certificate in the + chain. + +2009-05-27 22:13 -0700 Petr Písař (05bc65d6ae70) + + * po/cs.po: Updated Czech translation. + +2009-05-27 10:13 +0200 Rocco Rutte (97305eeb91ce) + + * doc/manual.xml.head, doc/mutt.man: Document that -- is always + mandatory after -a. Closes #3235. + + * init.h: Mention account-hook in the docs for $tunnel. Closes + #3237. + +2009-05-26 17:57 +0200 Rocco Rutte (392e945dfba7) + + * attach.c: Use charset parameter to view text attachments using + . Closes #3234. + +2009-05-25 15:57 +0200 Rocco Rutte (3f0963dd9257) + + * pager.c: pager: print progress percentage for attachments, too + + * attach.c: Mark strings for translation + +2009-05-18 20:48 -0700 Vincent Lefevre (6d810c5cf4fc) + + * po/fr.po: Updated French translation. + +2009-05-15 15:03 +0200 Takahashi Tamotsu (c665bdf5ff5f) + + * pop.c: POP: Notify user when messages are lost. Closes #2226. + + * pop.c: POP: Ignore already-deleted messages while + syncing. Closes #2225. + +2009-05-13 18:03 +0200 Rocco Rutte (0563c88ad6f0) + + * attach.c, recvattach.c: Don't loose error message when attachment + saving fails. Closes #3156. + +2009-05-15 12:46 +0200 Seth Arnold (1cea1ecf9f79) + + * UPDATING, color.c, doc/manual.xml.head: Make "uncolor" also work + header and body objects. Closes #1046. + +2009-05-13 14:20 +0200 Rocco Rutte (f96a176bb14c) + + * send.c: Don't set 'replied' flag if user changes + References/IRT. Closes #2044. + + * mutt.h, muttlib.c: Add mutt_find_list() to lookup data in lists + + * alias.c, crypt-gpgme.c, group.c, mbox.c, pgp.c, query.c, + rfc822.c, rfc822.h, send.c, smime.c: Prune empty address groups + when preparing replies. Closes #2875. + + * mbox.c: Actually reopen mbox/mmdf files in case we find + modifications. Closes #2725. + + Since the file is changed while we have it open in ctx->fp, we + likely get wrong information when parsing the mailbox. Now we + explicitely close and (re)open it. + +2009-05-12 16:26 +0200 Rocco Rutte (06e318bfe8f2) + + * mbox.c: Backout errorneously commited mbox atime fix + + * OPS, mbox.c: Fix description for + +2009-04-29 14:49 +0200 Rocco Rutte (335e6f782862) + + * browser.c: Fix maildir times in mailboxes browser. Closes #626. + + Instead of using the (pointless) mtime of the top-level maildir + folder, use the latest mtime of the "new" and "cur" subdirectories. + Maildir folders in the mailboxes list can now be properly sorted by + date. This does not affect the directory browser. Also see #2421. + + * mailbox.h, mh.c, mx.c: Move Maildir/MH folder detection from + mx.c to mh.c + +2009-04-28 15:12 +0200 Rocco Rutte (4d9685be5987) + + * sendlib.c: Fold References: header so we never run into line length + problems + + * headers.c: Fix comment typo + +2009-04-28 14:18 +0200 Bertram Felgenhauer (6b20a3545f03) + + * doc/manual.xml.head, headers.c: Drop References header if In-Reply- + To is modified by user. Closes #3221. + +2009-04-28 13:05 +0200 Rocco Rutte (a13d8fd40094) + + * send.c: Don't generate References: for reply to multiple + messages + + All parent Message-Ids are present in In-Reply-To already. Also, + RfC2822, section 3.6.4 discourages its generation. + + * sendlib.c: Don't trim In-Reply-To with $edit_headers set + + In case of a tagged reply to several messages, we want In-Reply-To + to contain all parent Message-Ids. + + * imap/imap.c: Only sync changed messages back to hcache on + mailbox sync + + * doc/manual.xml.head: For spam detection, mention $imap_headers. + Closes #3223. + + * doc/manual.xml.head: Manual: Fix typo and reword paragraph + +2009-04-26 21:09 +0200 Rocco Rutte (9fa4a3e74355) + + * UPDATING, doc/manual.xml.head, pop.c: POP: Support hcache updating, + too. + + This also allows us to use hcache to manage "flagged" and "replied" + message flags. + + * imap/imap.c, mh.c: Sync header to hcache when synching + MH/Maildir/IMAP folders. Closes #2942. + + * pager.c: Use dynamic buffer for displaying pager lines. Closes + #3162. + + With too small fixed-size buffers we can't color/find certain words + that span buffers. This needs to duplicate mutt_read_line with the + adjustment to leave line termination in and not support breaking + long lines using \ at EOL. Other callers may want to use this one + instead, too as we support \-escaping in too many places. + + * init.h: Document suffixes for %f in $folder_format + +2009-04-22 23:29 +0200 Bertram Felgenhauer (0aa313a3bf20) + + * headers.c: Fix memory leak in mutt_edit_headers(). Closes #3220. + +2009-04-25 10:51 +0200 Thomas Wiegner (8da22400a48d) + + * configure.ac, mkdtemp.c, protos.h: Add mkdtemp() from xfce to + unbreak gpgme build on Solaris. Closes #3217. + +2009-04-25 10:35 +0200 Rocco Rutte (c6de4f51b8c7) + + * ChangeLog, configure.ac, protos.h, strcasestr.c: Add strcasestr() + from uclibc to unbreak (Open)Solaris build. Closes #3222. + +2009-04-21 15:10 -0400 Aron Griffis (3d89eddb2d9a) + + * buffy.c: Equivalent mutt_buffy, but readable code + + * buffy.c, buffy.h: Call mutt_expand_path() from mutt_buffy to fix + imap separator. Closes #3208 and #3218 + + * buffy.c: Use slen instead of assuming _POSIX_PATH_MAX + +2009-04-23 12:51 -0700 Vincent Lefevre (b5b4e652e4b1) + + * ChangeLog, po/fr.po: Updated French translation. + +2009-04-20 18:36 +0200 Christoph Berg (39fee3a9d034) + + * doc/manual.xml.head, init.h: Better document that some send-hooks + can't work with $autoedit. Closes #1834. + +2009-04-20 18:26 +0200 Rocco Rutte (6cc887ccd229) + + * init.h: Fix typo for $imap_pass + +2009-04-17 18:05 +0200 Rocco Rutte (7d44a83efcc6) + + * pgp.c: Support the Charset: armor header for inline PGP. Closes + #3039. + + The header is defined as optional by RfC4880. + + This is based on patch-1.5.9.tamo.pgp_charsetchack.1. We only + support reading this header and, if present, recode the PGP output + from the given charset to $charset if we find it valid; otherwise + fall back to UTF-8. Certain clients make use of the header when + sending mail, so mutt should respect it because some messages are + otherwise unreadable. + + The sending side is not touched, we unconditionally send UTF-8. + +2009-04-17 15:45 +0200 Michael Elkins (61a0c67ed727) + + * sendlib.c: Make sure Recent-From: consults $realname. Closes + #1721. + +2009-04-17 15:37 +0200 Rocco Rutte (3a7ecc3f8aeb) + + * UPDATING, functions.h, pager.c: Make and + work in the pager, too. Closes #3212. + + * pager.c: Don't consider \n part of a line for body + coloring. Closes #2363. + + * attach.c: Enlarge buffer size for parsing mailcap files + + We really need code for dynamic buffers which would solve a few + other bugs, too. Closes #2205. + +2009-04-16 19:23 +0200 Rocco Rutte (a4f66ae72dc5) + + * ChangeLog, pop_lib.c: POP: Default to using getservbyname() as we do + for IMAP and SMTP + + * doc/manual.xml.head: Manual: Improve docs on URL syntax, add + examples + + * doc/manual.xml.head: Manual: Add user-defined variables to variable + types + +2009-04-11 10:35 +0200 Rocco Rutte (7d7976cd4fc4) + + * ChangeLog, buffy.c, buffy.h, commands.c, sendlib.c: Don't raise new + mail flag on mbox/mmdf Fcc mailboxes. Closes #1896. + +2009-04-08 16:25 +0200 Rocco Rutte (5b631ee33281) + + * hdrline.c: For %F, display Bcc recipient if no other recipients + found. Closes #3157. + + * UPDATING, doc/manual.xml.head, doc/muttrc.man.head, pattern.c: + Make ~x match In-Reply-To, too. Closes #771. + +2009-04-07 19:57 +0200 Rocco Rutte (667b0006b586) + + * sendlib.c: Fix b5cbd0dab863, closes #3215. + + Still valgrind reports 'fromcode' as leaking. + +2009-04-07 11:32 +0200 Erik Hovland (d344c6429a48) + + * sendlib.c: Try to correct usage of tempfile and *tempfile + + Since tempfile is a double pointer checking for tempfile and then + dereferencing with *tempfile is not correct. + +2009-04-06 22:05 +0200 Rocco Rutte (d639baaf57fb) + + * doc/manual.xml.head: Manual: Fix typo + +2009-04-06 19:10 +0200 Erik Hovland (4fe35e9984ba) + + * sendlib.c: mutt_message_to_7bit(): Only close file + pointer if we opened it + + The pointer is to be managed outside the function and provided. Only + close it we opened it ourself using fopen(). + +2009-04-06 19:07 +0200 Erik Hovland (b5cbd0dab863) + + * sendlib.c: Plug memory leaks in sendlib.c + +2009-04-05 13:41 +0200 Rocco Rutte (5d393e716c51) + + * init.h, sendlib.c: Backed out changeset 23c7b469ff20 + + This requires more thought: if the user has -- in $sendmail, we need + to add our arguments for 8BITMIME/DSN/etc. before it and not after. + See #3168. + + * doc/manual.xml.head: Manual: Make sure every rc command has a + synopsis in its describing section + + * doc/manual.xml.head: Manual: Fold consecutive + into just one + + This make it visually easier to spot what belongs together. + + * doc/manual.xml.head: Manual: More entities and as + appropriate + +2009-04-04 16:23 +0200 Rocco Rutte (a4b635e96b30) + + * doc/Makefile.am: Manual: Improve 'sortcheck' target + + Don't call up diff+pager if all is sorted and remove the temp files + for diffing we created. + + * doc/gen-map-doc, doc/manual.xml.head, doc/manual.xml.tail: Manual: + Capitalize headlines + + * doc/manual.xml.head: Manual: Move section on mixmaster support to + Optional Features + + * doc/manual.xml.head: Manual: Remove duplicate section on mailcap use + from security chapter + + We already have a more detailed section on secure mailcap usage, so + link to it. + + * doc/manual.xml.head: Manual: Minor improvements and fixes + + * doc/Makefile.am, doc/manual.xml.head: Manual: Add a short chapter + summarizing security considerations + + * doc/manual.xml.head: Manual: Use — in text rather than -- + + * doc/manual.xml.head: Manual: Add section on padding for format + strings + + * doc/manual.xml.head: Manual: Mention reply types in "Sending Mail" + section + + * doc/manual.xml.head: Manual: Add table with navigation keys for + page-based menus + + * doc/mutt.css: mutt.css: Add left+right margins to screen, note and + examples + + * doc/manual.xml.head: Manual: Add section on screens and menus with + short descriptions. + + Mostly stolen from old mutt-ng docs with adjustments. + +2009-04-02 13:11 +0200 Steve Kemp (23c7b469ff20) + + * init.h, sendlib.c: Only append -- to $sendmail if not + present. Closes #3168. + + This allows users to add custom recipients via $sendmail. + +2009-04-02 12:57 +0200 Rocco Rutte (bfb12cf02417) + + * init.h: Clarify what $attach_charset does, closes #3165. + + * doc/Makefile.am: Add 'sortcheck' target to doc/Makefile.am + + This should be used from time to time to check if vars are sorted. + + Closes #3191. + + * init.h: Sort $pgp_* and $crypt_* vars, see #3191. + + * init.h: Sort $smime_* vars, see #3191. + +2009-04-01 14:33 +0200 Miroslav Lichvar (8205a12329d3) + + * hcache.c, muttlib.c: Use PATH_MAX for buffers passed to realpath(3) + as we're supposed to + +2009-04-01 13:16 +0200 Rocco Rutte (47c64fd9ac70) + + * doc/gen-map-doc, doc/manual.xml.head: Manual: Fix openjade + warnings + + * doc/makedoc.c, doc/mutt.css: makedoc: Render description lists as + + + This looks better and is more compact (except missing column + headers.) + +2009-03-31 16:03 +0200 Rocco Rutte (22f21b558f57) + + * doc/manual.xml.head: Manual: Add an example of how to manage + multiple accounts using folder-hook + + * UPDATING, doc/manual.xml.head, mutt.h, pattern.c: Perform case + insensitive string search if pattern is lower case + + ...since we do that for regex patterns already. It doesn't work for + IMAP server-side searches. + + * doc/manual.xml.head: Manual: Fix markup of ".muttrc" + + * doc/manual.xml.head: Manual: Always spell mutt as "Mutt" + + * doc/manual.xml.head: Manual: Replace netscape with firefox + + * doc/manual.xml.head: Manual: use instead of " quotes + + * doc/manual.xml.head: Manual: Lots of minor improvements + (markup consistency, wording) + +2009-03-30 14:58 +0200 Rocco Rutte (318748f3962b) + + * doc/manual.xml.head: For mailbox formats, add some more verbose pros + and cons + + * doc/manual.xml.head: Manual: Add section about zeroprinting format + strings to format string section + +2009-03-28 22:37 +0100 Thomas Roessler (be9fb07730c6) + + * mutt_idna.c: Make IDNA code more readable + +2009-03-28 16:11 +0100 Rocco Rutte (77cfe8016930) + + * doc/manual.xml.head: Manual: Add section roughly explaining config + option types + + * doc/makedoc.c: makedoc: make output slightly more readable + + Add + using HTML which save lots of vertical space. Also, drop + the newline before to save some space. + +2009-03-27 18:02 +0100 Rocco Rutte (a06a2a4c5ebc) + + * rfc3676.c: f=f: Fix debug messages + +2009-03-19 17:19 +0100 Rocco Rutte (754ea0f091fc) + + * doc/manual.xml.head: Improve section on patterns + + * curs_lib.c: Fix progress update debug message + + * doc/manual.xml.head, doc/muttrc.man.head: Document kilo and mega + suffixes for range patterns + + Document it only for ~z (message size) as they don't make much sense + for other patterns like message score or number of attachments. + +2009-03-18 17:40 +0100 Rocco Rutte (8528b8e715da) + + * init.h: Properly initialize more structs + +2009-03-19 13:38 +0100 Erik Hovland (a802b5127f09) + + * pgp.c: Remove unused variable + +2009-03-19 10:36 +0100 Roman Kraevskiy (6fac57b97bf1) + + * mutt_sasl.c: Restore connection polling callback when + closing SASL connection. Closes #3206. + +2009-03-18 14:48 +0100 Erik Hovland (17d770ae41e4) + + * smime.c: S/MIME: Don't leak intermediate cert key + + * buffy.c: Properly initialize struct stats in buffy check + +2009-03-17 20:04 +0100 Rocco Rutte (903b3cee5485) + + * addrbook.c, browser.c, compose.c, curs_main.c, imap/auth.c, mx.c, + pattern.c, pop_auth.c, postpone.c, query.c, recvattach.c, + remailer.c: Fix some warnings with -W about missing initializers in + structs + +2009-03-17 16:44 +0100 Todd Zullinger (bb9b845800f6) + + * pgp.c: Ensure display is redrawn for application/pgp + + When using gpg-agent, a hard redraw is needed after the pinentry + program is called. Otherwise, the screen is garbled and key + bindings are screwed up. + + Closes #3196. + +2009-03-15 16:44 +0100 Rocco Rutte (bc7c64ff3e48) + + * configure.ac, protos.h, wcscasecmp.c: Add wcscasecmp() compatibility + function (for OS X) + + * doc/mutt.man: mutt.1: Mention that -a should be last in option + list. Closes #3202 + + * alias.c: Only define min() if not present. Closes #3199 + +2009-03-15 14:25 +0100 Erik Hovland (3c154fcdad4c) + + * rfc822.c: The assigned value of dom is never used. Remove + assignment + + * alias.c: The file handle will leak if fread fails + +2009-03-12 15:16 -0700 Erik Hovland (53bea026a2a2) + + * curs_main.c: resort_index will use menu->current as a index into an + array. If menu->current is negative, bad things can happen. So check + it before calling resort_index + + * recvcmd.c: 'last' is assigned but never used. Remove assignment. + +2009-03-15 13:46 +0100 Rocco Rutte (1238dff54a15) + + * alias.c, attach.c, buffy.c, check_sec.sh, commands.c, compose.c, + copy.c, crypt-gpgme.c, crypt.c, edit.c, editmsg.c, gnupgparse.c, + handler.c, headers.c, help.c, history.c, imap/message.c, init.c, + lib.c, main.c, mbox.c, mh.c, mutt_ssl.c, mutt_ssl_gnutls.c, + muttlib.c, pager.c, pattern.c, pgp.c, pgpkey.c, pgppubring.c, + pop.c, postpone.c, query.c, recvattach.c, recvcmd.c, rfc1524.c, + rfc3676.c, send.c, sendlib.c, smime.c, smtp.c: Use safe_fclose() + instead of fclose(), add fclose() to check_sec.sh + +2009-03-10 18:39 +0100 NONAKA Kimihiro (cc6fede605d4) + + * mh.c: Fix crashes with 64bit time_t. Closes #3184. + +2009-03-09 12:04 +0100 Vincent Lefevre (4ce562b7f5d7) + + * mbyte.h: Unbreak compilation on OS X with --with-regex/--without-wc- + funcs. Closes #3149. + +2009-03-09 11:58 +0100 Rocco Rutte (f3a33b77dc90) + + * mutt.h, regex.c: Unbreak compilation with --without-wc- funcs on + OS X 10.5.*, see #3149. + + * init.h: Fix 11cd72da743a + + * init.h: Sort SSL-related variables, see #3191. + + * hash.c, hash.h, init.c, mh.c, thread.c: Restore $reverse_alias + feature by using case-insensitive hash keys + + The fix is implemented as callbacks in the hash table so we can + avoid working with copies of the mailbox keys but work on the + originals instead and don't pollute the code with lower-case + conversions all over the place. + + While I'm at it, turn int hashes into unsigned values since the hash + function returns unsigned values now, too. + + Closes #3185. + +2009-03-07 13:49 +0100 Rocco Rutte (ff1906f70b1b) + + * init.h: Sort most variables (except crypto), see #3191. + + * doc/manual.xml.head: Fix typo, see #2430. + +2009-02-20 22:14 +0100 Rocco Rutte (35fbea209c6e) + + * doc/manual.xml.head: Manual: verbosely document how the + initial folder is determined, see #3189. + + * doc/manual.xml.head: Document address normalization. Closes #2430. + + * headers.c: Simplify and fix Attach: header parsing + + With ee5e696a9d08 we would skip beyond the filename to look for a + description. This changeset fixes it. + + * main.c: Set magic from -m before processing queries (-Q) or dumping + variables (-D) + + * doc/mutt.man, init.h: Better document how the initial folder is + determined. Closes #3189. + +2009-02-15 16:09 +0100 Rocco Rutte (ee5e696a9d08) + + * doc/manual.xml.head, headers.c: Support spaces in Attach: + pseudoheader. Closes #3179. + +2009-02-10 13:05 +0100 Rocco Rutte (a21f8bf84149) + + * init.h: Fix documentation typos. Closes #3178. + +2009-01-27 12:58 -0800 Brendan Cully (7ddf1d1cc490) + + * imap/imap.c: Move socket close into imap_logout from imap_logout_all + + * imap/imap.c: IMAP: only close socket when not already + disconnected. + +2009-01-27 18:48 +0100 Rocco Rutte (d7e44862a08a) + + * help.c, main.c, mh.c: Update copyright years + + * help.c: Fix help alignment for escape sequences at screen + boundary. Closes #3146. + + * mh.c: Unconditionally inode-sort Maildir and MH folders. Closes + #3166. + +2009-01-26 12:32 -0800 Brendan Cully (da94a92c3ba0) + + * bcache.c: Remove old bcache tmpfile before trying to create new + one. Closes #3163. + +2009-01-20 12:34 -0800 René Clerc (2006526d1d26) + + * po/nl.po: Updated Dutch translation + +2009-01-19 20:39 -0800 Ivan Vilata i Balaguer (038f1e5cdaea) + + * po/ca.po: Updated Catalan translation + +2009-01-14 20:04 +0000 Emanuele Giaquinta (ddf48761aacf) + + * imap/browse.c: Use imap_utf7_encode instead of + imap_munge_mbox_name+imap_unquote_string. + +2009-01-14 11:45 -0800 Brendan Cully (cd0b17c80372) + + * doc/manual.xml.head: Add missing hooks to manual section 4 + +2009-01-13 06:51 -0800 Brendan Cully (10e224e86f0b) + + * hook.c: Do not allow a command in an account-hook to trigger another + account-hook. Recent changes in the IMAP path canonifier mean that + account-hooks that set variables to URLs (eg folder, spoolfile) can + trigger a recursive account-hook. Now we just bail out of account- + hook early if we are called recursively, but perhaps we should warn + the user to use a folder-hook instead. Thanks to Kyle Wheeler for + finding this one. + +2009-01-12 10:27 -0800 Brendan Cully (6976aca75d04) + + * init.h: Correct defaults for new ssl options (fixes manual + generation) + +2009-01-11 21:47 -0800 Brendan Cully (ff74e612f790) + + * mutt_ssl_gnutls.c: GNUTLS: check all available certs + noninteractively before presenting any menus + + * UPDATING, init.h, mutt.h, mutt_ssl.c, mutt_ssl_gnutls.c: Add + $ssl_verify_dates option to relax certificate date validation + + * UPDATING, init.h, mutt.h, mutt_ssl.c, mutt_ssl_gnutls.c: Add + $ssl_verify_host to allow skipping host name validation + +2009-01-10 22:09 -0800 Brendan Cully (db3a61fcde35) + + * imap/util.c: Assume INBOX for ""/NULL in imap_mxcmp + + * imap/util.c: Use known connection delimiter in imap_expand_path + + * imap/util.c: Guard against NULL pointers in imap_mxcmp + + * imap/imap_private.h, imap/util.c: Canonicalize IMAP mailboxes before + comparing them. + + * imap/util.c: Fix last commit + + * imap/util.c: Prioritize the entered IMAP folder delimiter. First + priority is the connection delimiter. Second priority is the user's + delimiter if it is in imap_delim_chars. We no longer use the first + character in imap_delim_chars. + +2009-01-06 18:34 -0800 Vsevolod Volkov (4032dfd52118) + + * po/ru.po: Updated Russian translation + +2009-01-05 16:43 -0800 Brendan Cully (0d81ef9d40fd) + + * build-release: Sign tagged revision, not the one after + + * .hgsigs: mutt-1.5.19 signed + + * .hgtags: Added tag mutt-1-5-19-rel for changeset a4b47ac32d32 + + * VERSION, po/bg.po, po/ca.po, po/cs.po, po/da.po, po/de.po, + po/el.po, po/eo.po, po/es.po, po/et.po, po/eu.po, po/fr.po, + po/ga.po, po/gl.po, po/hu.po, po/id.po, po/it.po, po/ja.po, + po/ko.po, po/lt.po, po/nl.po, po/pl.po, po/pt_BR.po, po/ru.po, + po/sk.po, po/sv.po, po/tr.po, po/uk.po, po/zh_CN.po, po/zh_TW.po: + automatic post-release commit for mutt-1.5.19 * build-release: Fall back to vi if VISUAL is unset in build-release diff --git a/Makefile.in b/Makefile.in index e3769c8..8b95ef6 100644 --- a/Makefile.in +++ b/Makefile.in @@ -1,8 +1,9 @@ -# Makefile.in generated by automake 1.10.1 from Makefile.am. +# Makefile.in generated by automake 1.11 from Makefile.am. # @configure_input@ # Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, -# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. +# 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, +# Inc. # This Makefile.in is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. @@ -17,8 +18,9 @@ VPATH = @srcdir@ pkgdatadir = $(datadir)/@PACKAGE@ -pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkglibexecdir = $(libexecdir)/@PACKAGE@ am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd install_sh_DATA = $(install_sh) -c -m 644 install_sh_PROGRAM = $(install_sh) -c @@ -42,17 +44,17 @@ DIST_COMMON = README $(am__configure_deps) $(srcdir)/Makefile.am \ $(srcdir)/hcachever.sh.in $(srcdir)/muttbug.sh.in \ $(top_srcdir)/configure $(top_srcdir)/intl/Makefile.in \ ABOUT-NLS ChangeLog INSTALL NEWS TODO config.guess config.sub \ - depcomp install-sh missing mkinstalldirs regex.c setenv.c \ - snprintf.c strcasecmp.c strdup.c strsep.c strtok_r.c + depcomp install-sh missing mkdtemp.c mkinstalldirs regex.c \ + setenv.c snprintf.c strcasecmp.c strcasestr.c strdup.c \ + strsep.c strtok_r.c wcscasecmp.c ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \ $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \ $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \ $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \ $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \ - $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/libgnutls.m4 \ - $(top_srcdir)/m4/progtest.m4 $(top_srcdir)/m4/types.m4 \ - $(top_srcdir)/configure.ac + $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \ + $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ $(ACLOCAL_M4) am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \ @@ -60,8 +62,8 @@ am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \ mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs CONFIG_HEADER = config.h CONFIG_CLEAN_FILES = intl/Makefile hcachever.sh muttbug.sh +CONFIG_CLEAN_VPATH_FILES = am__installdirs = "$(DESTDIR)$(bindir)" "$(DESTDIR)$(bindir)" -binPROGRAMS_INSTALL = $(INSTALL_PROGRAM) PROGRAMS = $(bin_PROGRAMS) $(noinst_PROGRAMS) am_mutt_OBJECTS = addrbook.$(OBJEXT) alias.$(OBJEXT) attach.$(OBJEXT) \ base64.$(OBJEXT) browser.$(OBJEXT) buffy.$(OBJEXT) \ @@ -103,11 +105,32 @@ am_pgpring_OBJECTS = pgppubring.$(OBJEXT) pgplib.$(OBJEXT) \ lib.$(OBJEXT) extlib.$(OBJEXT) sha1.$(OBJEXT) md5.$(OBJEXT) \ pgppacket.$(OBJEXT) ascii.$(OBJEXT) pgpring_OBJECTS = $(am_pgpring_OBJECTS) -binSCRIPT_INSTALL = $(INSTALL_SCRIPT) +am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; +am__vpath_adj = case $$p in \ + $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \ + *) f=$$p;; \ + esac; +am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`; +am__install_max = 40 +am__nobase_strip_setup = \ + srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'` +am__nobase_strip = \ + for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||" +am__nobase_list = $(am__nobase_strip_setup); \ + for p in $$list; do echo "$$p $$p"; done | \ + sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \ + $(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \ + if (++n[$$2] == $(am__install_max)) \ + { print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \ + END { for (dir in files) print dir, files[dir] }' +am__base_list = \ + sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \ + sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g' SCRIPTS = $(bin_SCRIPTS) DEFAULT_INCLUDES = -I.@am__isrc@ depcomp = $(SHELL) $(top_srcdir)/depcomp am__depfiles_maybe = depfiles +am__mv = mv -f COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \ $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) CCLD = $(CC) @@ -127,6 +150,9 @@ RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \ ps-recursive uninstall-recursive RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive \ distclean-recursive maintainer-clean-recursive +AM_RECURSIVE_TARGETS = $(RECURSIVE_TARGETS:-recursive=) \ + $(RECURSIVE_CLEAN_TARGETS:-recursive=) tags TAGS ctags CTAGS \ + distdir dist dist-all distcheck ETAGS = etags CTAGS = ctags DIST_SUBDIRS = m4 po intl doc contrib imap @@ -134,9 +160,34 @@ DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) distdir = $(PACKAGE)-$(VERSION) top_distdir = $(distdir) am__remove_distdir = \ - { test ! -d $(distdir) \ - || { find $(distdir) -type d ! -perm -200 -exec chmod u+w {} ';' \ - && rm -fr $(distdir); }; } + { test ! -d "$(distdir)" \ + || { find "$(distdir)" -type d ! -perm -200 -exec chmod u+w {} ';' \ + && rm -fr "$(distdir)"; }; } +am__relativize = \ + dir0=`pwd`; \ + sed_first='s,^\([^/]*\)/.*$$,\1,'; \ + sed_rest='s,^[^/]*/*,,'; \ + sed_last='s,^.*/\([^/]*\)$$,\1,'; \ + sed_butlast='s,/*[^/]*$$,,'; \ + while test -n "$$dir1"; do \ + first=`echo "$$dir1" | sed -e "$$sed_first"`; \ + if test "$$first" != "."; then \ + if test "$$first" = ".."; then \ + dir2=`echo "$$dir0" | sed -e "$$sed_last"`/"$$dir2"; \ + dir0=`echo "$$dir0" | sed -e "$$sed_butlast"`; \ + else \ + first2=`echo "$$dir2" | sed -e "$$sed_first"`; \ + if test "$$first2" = "$$first"; then \ + dir2=`echo "$$dir2" | sed -e "$$sed_rest"`; \ + else \ + dir2="../$$dir2"; \ + fi; \ + dir0="$$dir0"/"$$first"; \ + fi; \ + fi; \ + dir1=`echo "$$dir1" | sed -e "$$sed_rest"`; \ + done; \ + reldir="$$dir2" DIST_ARCHIVES = $(distdir).tar.gz GZIP_ENV = --best distuninstallcheck_listfiles = find . -type f -print @@ -198,9 +249,6 @@ INTL_LIBTOOL_SUFFIX_PREFIX = @INTL_LIBTOOL_SUFFIX_PREFIX@ ISPELL = @ISPELL@ KRB5CFGPATH = @KRB5CFGPATH@ LDFLAGS = @LDFLAGS@ -LIBGNUTLS_CFLAGS = @LIBGNUTLS_CFLAGS@ -LIBGNUTLS_CONFIG = @LIBGNUTLS_CONFIG@ -LIBGNUTLS_LIBS = @LIBGNUTLS_LIBS@ LIBICONV = @LIBICONV@ LIBIMAP = @LIBIMAP@ LIBIMAPDEPS = @LIBIMAPDEPS@ @@ -286,6 +334,7 @@ sharedstatedir = @sharedstatedir@ srcdir = @srcdir@ sysconfdir = @sysconfdir@ target_alias = @target_alias@ +top_build_prefix = @top_build_prefix@ top_builddir = @top_builddir@ top_srcdir = @top_srcdir@ AUTOMAKE_OPTIONS = 1.6 foreign @@ -367,15 +416,15 @@ $(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(am__configure_deps) @for dep in $?; do \ case '$(am__configure_deps)' in \ *$$dep*) \ - echo ' cd $(srcdir) && $(AUTOMAKE) --foreign '; \ - cd $(srcdir) && $(AUTOMAKE) --foreign \ + echo ' cd $(srcdir) && $(AUTOMAKE) --foreign'; \ + $(am__cd) $(srcdir) && $(AUTOMAKE) --foreign \ && exit 0; \ exit 1;; \ esac; \ done; \ - echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign Makefile'; \ - cd $(top_srcdir) && \ - $(AUTOMAKE) --foreign Makefile + echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign Makefile'; \ + $(am__cd) $(top_srcdir) && \ + $(AUTOMAKE) --foreign Makefile .PRECIOUS: Makefile Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status @case '$?' in \ @@ -391,9 +440,10 @@ $(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENC $(SHELL) ./config.status --recheck $(top_srcdir)/configure: $(am__configure_deps) - cd $(srcdir) && $(AUTOCONF) + $(am__cd) $(srcdir) && $(AUTOCONF) $(ACLOCAL_M4): $(am__aclocal_m4_deps) - cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS) + $(am__cd) $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS) +$(am__aclocal_m4_deps): config.h: stamp-h1 @if test ! -f $@; then \ @@ -405,7 +455,7 @@ stamp-h1: $(srcdir)/config.h.in $(top_builddir)/config.status @rm -f stamp-h1 cd $(top_builddir) && $(SHELL) ./config.status config.h $(srcdir)/config.h.in: $(am__configure_deps) - cd $(top_srcdir) && $(AUTOHEADER) + ($(am__cd) $(top_srcdir) && $(AUTOHEADER)) rm -f stamp-h1 touch $@ @@ -420,23 +470,37 @@ muttbug.sh: $(top_builddir)/config.status $(srcdir)/muttbug.sh.in install-binPROGRAMS: $(bin_PROGRAMS) @$(NORMAL_INSTALL) test -z "$(bindir)" || $(MKDIR_P) "$(DESTDIR)$(bindir)" - @list='$(bin_PROGRAMS)'; for p in $$list; do \ - p1=`echo $$p|sed 's/$(EXEEXT)$$//'`; \ - if test -f $$p \ - ; then \ - f=`echo "$$p1" | sed 's,^.*/,,;$(transform);s/$$/$(EXEEXT)/'`; \ - echo " $(INSTALL_PROGRAM_ENV) $(binPROGRAMS_INSTALL) '$$p' '$(DESTDIR)$(bindir)/$$f'"; \ - $(INSTALL_PROGRAM_ENV) $(binPROGRAMS_INSTALL) "$$p" "$(DESTDIR)$(bindir)/$$f" || exit 1; \ - else :; fi; \ - done + @list='$(bin_PROGRAMS)'; test -n "$(bindir)" || list=; \ + for p in $$list; do echo "$$p $$p"; done | \ + sed 's/$(EXEEXT)$$//' | \ + while read p p1; do if test -f $$p; \ + then echo "$$p"; echo "$$p"; else :; fi; \ + done | \ + sed -e 'p;s,.*/,,;n;h' -e 's|.*|.|' \ + -e 'p;x;s,.*/,,;s/$(EXEEXT)$$//;$(transform);s/$$/$(EXEEXT)/' | \ + sed 'N;N;N;s,\n, ,g' | \ + $(AWK) 'BEGIN { files["."] = ""; dirs["."] = 1 } \ + { d=$$3; if (dirs[d] != 1) { print "d", d; dirs[d] = 1 } \ + if ($$2 == $$4) files[d] = files[d] " " $$1; \ + else { print "f", $$3 "/" $$4, $$1; } } \ + END { for (d in files) print "f", d, files[d] }' | \ + while read type dir files; do \ + if test "$$dir" = .; then dir=; else dir=/$$dir; fi; \ + test -z "$$files" || { \ + echo " $(INSTALL_PROGRAM_ENV) $(INSTALL_PROGRAM) $$files '$(DESTDIR)$(bindir)$$dir'"; \ + $(INSTALL_PROGRAM_ENV) $(INSTALL_PROGRAM) $$files "$(DESTDIR)$(bindir)$$dir" || exit $$?; \ + } \ + ; done uninstall-binPROGRAMS: @$(NORMAL_UNINSTALL) - @list='$(bin_PROGRAMS)'; for p in $$list; do \ - f=`echo "$$p" | sed 's,^.*/,,;s/$(EXEEXT)$$//;$(transform);s/$$/$(EXEEXT)/'`; \ - echo " rm -f '$(DESTDIR)$(bindir)/$$f'"; \ - rm -f "$(DESTDIR)$(bindir)/$$f"; \ - done + @list='$(bin_PROGRAMS)'; test -n "$(bindir)" || list=; \ + files=`for p in $$list; do echo "$$p"; done | \ + sed -e 'h;s,^.*/,,;s/$(EXEEXT)$$//;$(transform)' \ + -e 's/$$/$(EXEEXT)/' `; \ + test -n "$$list" || exit 0; \ + echo " ( cd '$(DESTDIR)$(bindir)' && rm -f" $$files ")"; \ + cd "$(DESTDIR)$(bindir)" && rm -f $$files clean-binPROGRAMS: -test -z "$(bin_PROGRAMS)" || rm -f $(bin_PROGRAMS) @@ -461,22 +525,37 @@ pgpring$(EXEEXT): $(pgpring_OBJECTS) $(pgpring_DEPENDENCIES) install-binSCRIPTS: $(bin_SCRIPTS) @$(NORMAL_INSTALL) test -z "$(bindir)" || $(MKDIR_P) "$(DESTDIR)$(bindir)" - @list='$(bin_SCRIPTS)'; for p in $$list; do \ + @list='$(bin_SCRIPTS)'; test -n "$(bindir)" || list=; \ + for p in $$list; do \ if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \ - if test -f $$d$$p; then \ - f=`echo "$$p" | sed 's|^.*/||;$(transform)'`; \ - echo " $(binSCRIPT_INSTALL) '$$d$$p' '$(DESTDIR)$(bindir)/$$f'"; \ - $(binSCRIPT_INSTALL) "$$d$$p" "$(DESTDIR)$(bindir)/$$f"; \ - else :; fi; \ - done + if test -f "$$d$$p"; then echo "$$d$$p"; echo "$$p"; else :; fi; \ + done | \ + sed -e 'p;s,.*/,,;n' \ + -e 'h;s|.*|.|' \ + -e 'p;x;s,.*/,,;$(transform)' | sed 'N;N;N;s,\n, ,g' | \ + $(AWK) 'BEGIN { files["."] = ""; dirs["."] = 1; } \ + { d=$$3; if (dirs[d] != 1) { print "d", d; dirs[d] = 1 } \ + if ($$2 == $$4) { files[d] = files[d] " " $$1; \ + if (++n[d] == $(am__install_max)) { \ + print "f", d, files[d]; n[d] = 0; files[d] = "" } } \ + else { print "f", d "/" $$4, $$1 } } \ + END { for (d in files) print "f", d, files[d] }' | \ + while read type dir files; do \ + if test "$$dir" = .; then dir=; else dir=/$$dir; fi; \ + test -z "$$files" || { \ + echo " $(INSTALL_SCRIPT) $$files '$(DESTDIR)$(bindir)$$dir'"; \ + $(INSTALL_SCRIPT) $$files "$(DESTDIR)$(bindir)$$dir" || exit $$?; \ + } \ + ; done uninstall-binSCRIPTS: @$(NORMAL_UNINSTALL) - @list='$(bin_SCRIPTS)'; for p in $$list; do \ - f=`echo "$$p" | sed 's|^.*/||;$(transform)'`; \ - echo " rm -f '$(DESTDIR)$(bindir)/$$f'"; \ - rm -f "$(DESTDIR)$(bindir)/$$f"; \ - done + @list='$(bin_SCRIPTS)'; test -n "$(bindir)" || exit 0; \ + files=`for p in $$list; do echo "$$p"; done | \ + sed -e 's,.*/,,;$(transform)'`; \ + test -n "$$list" || exit 0; \ + echo " ( cd '$(DESTDIR)$(bindir)' && rm -f" $$files ")"; \ + cd "$(DESTDIR)$(bindir)" && rm -f $$files mostlyclean-compile: -rm -f *.$(OBJEXT) @@ -484,13 +563,16 @@ mostlyclean-compile: distclean-compile: -rm -f *.tab.c +@AMDEP_TRUE@@am__include@ @am__quote@$(DEPDIR)/mkdtemp.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@$(DEPDIR)/regex.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@$(DEPDIR)/setenv.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@$(DEPDIR)/snprintf.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@$(DEPDIR)/strcasecmp.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@$(DEPDIR)/strcasestr.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@$(DEPDIR)/strdup.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@$(DEPDIR)/strsep.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@$(DEPDIR)/strtok_r.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@$(DEPDIR)/wcscasecmp.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/account.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/addrbook.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/alias.Po@am__quote@ @@ -598,28 +680,28 @@ distclean-compile: .c.o: @am__fastdepCC_TRUE@ $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $< -@am__fastdepCC_TRUE@ mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po +@am__fastdepCC_TRUE@ $(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po @AMDEP_TRUE@@am__fastdepCC_FALSE@ source='$<' object='$@' libtool=no @AMDEPBACKSLASH@ @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(COMPILE) -c $< .c.obj: @am__fastdepCC_TRUE@ $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ `$(CYGPATH_W) '$<'` -@am__fastdepCC_TRUE@ mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po +@am__fastdepCC_TRUE@ $(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po @AMDEP_TRUE@@am__fastdepCC_FALSE@ source='$<' object='$@' libtool=no @AMDEPBACKSLASH@ @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(COMPILE) -c `$(CYGPATH_W) '$<'` mutt_md5-md5.o: md5.c @am__fastdepCC_TRUE@ $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -MT mutt_md5-md5.o -MD -MP -MF $(DEPDIR)/mutt_md5-md5.Tpo -c -o mutt_md5-md5.o `test -f 'md5.c' || echo '$(srcdir)/'`md5.c -@am__fastdepCC_TRUE@ mv -f $(DEPDIR)/mutt_md5-md5.Tpo $(DEPDIR)/mutt_md5-md5.Po +@am__fastdepCC_TRUE@ $(am__mv) $(DEPDIR)/mutt_md5-md5.Tpo $(DEPDIR)/mutt_md5-md5.Po @AMDEP_TRUE@@am__fastdepCC_FALSE@ source='md5.c' object='mutt_md5-md5.o' libtool=no @AMDEPBACKSLASH@ @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -c -o mutt_md5-md5.o `test -f 'md5.c' || echo '$(srcdir)/'`md5.c mutt_md5-md5.obj: md5.c @am__fastdepCC_TRUE@ $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -MT mutt_md5-md5.obj -MD -MP -MF $(DEPDIR)/mutt_md5-md5.Tpo -c -o mutt_md5-md5.obj `if test -f 'md5.c'; then $(CYGPATH_W) 'md5.c'; else $(CYGPATH_W) '$(srcdir)/md5.c'; fi` -@am__fastdepCC_TRUE@ mv -f $(DEPDIR)/mutt_md5-md5.Tpo $(DEPDIR)/mutt_md5-md5.Po +@am__fastdepCC_TRUE@ $(am__mv) $(DEPDIR)/mutt_md5-md5.Tpo $(DEPDIR)/mutt_md5-md5.Po @AMDEP_TRUE@@am__fastdepCC_FALSE@ source='md5.c' object='mutt_md5-md5.obj' libtool=no @AMDEPBACKSLASH@ @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -c -o mutt_md5-md5.obj `if test -f 'md5.c'; then $(CYGPATH_W) 'md5.c'; else $(CYGPATH_W) '$(srcdir)/md5.c'; fi` @@ -648,7 +730,7 @@ $(RECURSIVE_TARGETS): else \ local_target="$$target"; \ fi; \ - (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \ + ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \ || eval $$failcom; \ done; \ if test "$$dot_seen" = "no"; then \ @@ -682,16 +764,16 @@ $(RECURSIVE_CLEAN_TARGETS): else \ local_target="$$target"; \ fi; \ - (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \ + ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \ || eval $$failcom; \ done && test -z "$$fail" tags-recursive: list='$(SUBDIRS)'; for subdir in $$list; do \ - test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \ + test "$$subdir" = . || ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \ done ctags-recursive: list='$(SUBDIRS)'; for subdir in $$list; do \ - test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \ + test "$$subdir" = . || ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \ done ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES) @@ -699,14 +781,14 @@ ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES) unique=`for i in $$list; do \ if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ done | \ - $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \ + $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ END { if (nonempty) { for (i in files) print i; }; }'`; \ mkid -fID $$unique tags: TAGS TAGS: tags-recursive $(HEADERS) $(SOURCES) config.h.in $(TAGS_DEPENDENCIES) \ $(TAGS_FILES) $(LISP) - tags=; \ + set x; \ here=`pwd`; \ if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \ include_option=--etags-include; \ @@ -718,7 +800,7 @@ TAGS: tags-recursive $(HEADERS) $(SOURCES) config.h.in $(TAGS_DEPENDENCIES) \ list='$(SUBDIRS)'; for subdir in $$list; do \ if test "$$subdir" = .; then :; else \ test ! -f $$subdir/TAGS || \ - tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \ + set "$$@" "$$include_option=$$here/$$subdir/TAGS"; \ fi; \ done; \ list='$(SOURCES) $(HEADERS) config.h.in $(LISP) $(TAGS_FILES)'; \ @@ -727,36 +809,41 @@ TAGS: tags-recursive $(HEADERS) $(SOURCES) config.h.in $(TAGS_DEPENDENCIES) \ done | \ $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ END { if (nonempty) { for (i in files) print i; }; }'`; \ - if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \ + shift; \ + if test -z "$(ETAGS_ARGS)$$*$$unique"; then :; else \ test -n "$$unique" || unique=$$empty_fix; \ - $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ - $$tags $$unique; \ + if test $$# -gt 0; then \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + "$$@" $$unique; \ + else \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + $$unique; \ + fi; \ fi ctags: CTAGS CTAGS: ctags-recursive $(HEADERS) $(SOURCES) config.h.in $(TAGS_DEPENDENCIES) \ $(TAGS_FILES) $(LISP) - tags=; \ list='$(SOURCES) $(HEADERS) config.h.in $(LISP) $(TAGS_FILES)'; \ unique=`for i in $$list; do \ if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ done | \ $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ END { if (nonempty) { for (i in files) print i; }; }'`; \ - test -z "$(CTAGS_ARGS)$$tags$$unique" \ + test -z "$(CTAGS_ARGS)$$unique" \ || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \ - $$tags $$unique + $$unique GTAGS: here=`$(am__cd) $(top_builddir) && pwd` \ - && cd $(top_srcdir) \ - && gtags -i $(GTAGS_ARGS) $$here + && $(am__cd) $(top_srcdir) \ + && gtags -i $(GTAGS_ARGS) "$$here" distclean-tags: -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags distdir: $(DISTFILES) $(am__remove_distdir) - test -d $(distdir) || mkdir $(distdir) + test -d "$(distdir)" || mkdir "$(distdir)" @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ list='$(DISTFILES)'; \ @@ -772,38 +859,54 @@ distdir: $(DISTFILES) if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ if test -d $$d/$$file; then \ dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d "$(distdir)/$$file"; then \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ - cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \ + cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ fi; \ - cp -pR $$d/$$file $(distdir)$$dir || exit 1; \ + cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \ else \ - test -f $(distdir)/$$file \ - || cp -p $$d/$$file $(distdir)/$$file \ + test -f "$(distdir)/$$file" \ + || cp -p $$d/$$file "$(distdir)/$$file" \ || exit 1; \ fi; \ done - list='$(DIST_SUBDIRS)'; for subdir in $$list; do \ + @list='$(DIST_SUBDIRS)'; for subdir in $$list; do \ if test "$$subdir" = .; then :; else \ test -d "$(distdir)/$$subdir" \ || $(MKDIR_P) "$(distdir)/$$subdir" \ || exit 1; \ - distdir=`$(am__cd) $(distdir) && pwd`; \ - top_distdir=`$(am__cd) $(top_distdir) && pwd`; \ - (cd $$subdir && \ + fi; \ + done + @list='$(DIST_SUBDIRS)'; for subdir in $$list; do \ + if test "$$subdir" = .; then :; else \ + dir1=$$subdir; dir2="$(distdir)/$$subdir"; \ + $(am__relativize); \ + new_distdir=$$reldir; \ + dir1=$$subdir; dir2="$(top_distdir)"; \ + $(am__relativize); \ + new_top_distdir=$$reldir; \ + echo " (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) top_distdir="$$new_top_distdir" distdir="$$new_distdir" \\"; \ + echo " am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)"; \ + ($(am__cd) $$subdir && \ $(MAKE) $(AM_MAKEFLAGS) \ - top_distdir="$$top_distdir" \ - distdir="$$distdir/$$subdir" \ + top_distdir="$$new_top_distdir" \ + distdir="$$new_distdir" \ am__remove_distdir=: \ am__skip_length_check=: \ + am__skip_mode_fix=: \ distdir) \ || exit 1; \ fi; \ done - -find $(distdir) -type d ! -perm -777 -exec chmod a+rwx {} \; -o \ + -test -n "$(am__skip_mode_fix)" \ + || find "$(distdir)" -type d ! -perm -777 -exec chmod a+rwx {} \; -o \ ! -type d ! -perm -444 -links 1 -exec chmod a+r {} \; -o \ ! -type d ! -perm -400 -exec chmod a+r {} \; -o \ ! -type d ! -perm -444 -exec $(install_sh) -c -m a+r {} {} \; \ - || chmod -R a+r $(distdir) + || chmod -R a+r "$(distdir)" dist-gzip: distdir tardir=$(distdir) && $(am__tar) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz $(am__remove_distdir) @@ -816,6 +919,10 @@ dist-lzma: distdir tardir=$(distdir) && $(am__tar) | lzma -9 -c >$(distdir).tar.lzma $(am__remove_distdir) +dist-xz: distdir + tardir=$(distdir) && $(am__tar) | xz -c >$(distdir).tar.xz + $(am__remove_distdir) + dist-tarZ: distdir tardir=$(distdir) && $(am__tar) | compress -c >$(distdir).tar.Z $(am__remove_distdir) @@ -844,6 +951,8 @@ distcheck: dist bunzip2 -c $(distdir).tar.bz2 | $(am__untar) ;;\ *.tar.lzma*) \ unlzma -c $(distdir).tar.lzma | $(am__untar) ;;\ + *.tar.xz*) \ + xz -dc $(distdir).tar.xz | $(am__untar) ;;\ *.tar.Z*) \ uncompress -c $(distdir).tar.Z | $(am__untar) ;;\ *.shar.gz*) \ @@ -855,9 +964,11 @@ distcheck: dist mkdir $(distdir)/_build mkdir $(distdir)/_inst chmod a-w $(distdir) + test -d $(distdir)/_build || exit 0; \ dc_install_base=`$(am__cd) $(distdir)/_inst && pwd | sed -e 's,^[^:\\/]:[\\/],/,'` \ && dc_destdir="$${TMPDIR-/tmp}/am-dc-$$$$/" \ - && cd $(distdir)/_build \ + && am__cwd=`pwd` \ + && $(am__cd) $(distdir)/_build \ && ../configure --srcdir=.. --prefix="$$dc_install_base" \ $(DISTCHECK_CONFIGURE_FLAGS) \ && $(MAKE) $(AM_MAKEFLAGS) \ @@ -879,13 +990,15 @@ distcheck: dist && rm -rf "$$dc_destdir" \ && $(MAKE) $(AM_MAKEFLAGS) dist \ && rm -rf $(DIST_ARCHIVES) \ - && $(MAKE) $(AM_MAKEFLAGS) distcleancheck + && $(MAKE) $(AM_MAKEFLAGS) distcleancheck \ + && cd "$$am__cwd" \ + || exit 1 $(am__remove_distdir) @(echo "$(distdir) archives ready for distribution: "; \ list='$(DIST_ARCHIVES)'; for i in $$list; do echo $$i; done) | \ sed -e 1h -e 1s/./=/g -e 1p -e 1x -e '$$p' -e '$$x' distuninstallcheck: - @cd $(distuninstallcheck_dir) \ + @$(am__cd) '$(distuninstallcheck_dir)' \ && test `$(distuninstallcheck_listfiles) | wc -l` -le 1 \ || { echo "ERROR: files left after uninstall:" ; \ if test -n "$(DESTDIR)"; then \ @@ -933,6 +1046,7 @@ clean-generic: distclean-generic: -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES) -test -z "$(DISTCLEANFILES)" || rm -f $(DISTCLEANFILES) maintainer-clean-generic: @@ -957,6 +1071,8 @@ dvi-am: html: html-recursive +html-am: + info: info-recursive info-am: @@ -965,20 +1081,29 @@ install-data-am: install-data-local install-dvi: install-dvi-recursive +install-dvi-am: + install-exec-am: install-binPROGRAMS install-binSCRIPTS @$(NORMAL_INSTALL) $(MAKE) $(AM_MAKEFLAGS) install-exec-hook - install-html: install-html-recursive +install-html-am: + install-info: install-info-recursive +install-info-am: + install-man: install-pdf: install-pdf-recursive +install-pdf-am: + install-ps: install-ps-recursive +install-ps-am: + installcheck-am: maintainer-clean: maintainer-clean-recursive @@ -1003,14 +1128,15 @@ ps-am: uninstall-am: uninstall-binPROGRAMS uninstall-binSCRIPTS \ uninstall-local -.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \ - install-exec-am install-strip +.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) all check \ + ctags-recursive install install-am install-exec-am \ + install-strip tags-recursive .PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \ all all-am am--refresh check check-am clean clean-binPROGRAMS \ clean-generic clean-noinstPROGRAMS ctags ctags-recursive dist \ dist-all dist-bzip2 dist-gzip dist-lzma dist-shar dist-tarZ \ - dist-zip distcheck distclean distclean-compile \ + dist-xz dist-zip distcheck distclean distclean-compile \ distclean-generic distclean-hdr distclean-tags distcleancheck \ distdir distuninstallcheck dvi dvi-am html html-am info \ info-am install install-am install-binPROGRAMS \ @@ -1105,6 +1231,7 @@ update-doc: (cd doc && $(MAKE) update-doc) .PHONY: commit pclean check-security + # Tell versions [3.59,3.63) of GNU make to not export all variables. # Otherwise a system limit (for SysV at least) may be exceeded. .NOEXPORT: diff --git a/OPS b/OPS index 3efddbb..7da7410 100644 --- a/OPS +++ b/OPS @@ -150,7 +150,7 @@ OP_REFORMAT_WINCH "{internal}" OP_RENAME_MAILBOX "rename the current mailbox (IMAP only)" OP_REPLY "reply to a message" OP_RESEND "use the current message as a template for a new one" -OP_SAVE "save message/attachment to a file" +OP_SAVE "save message/attachment to a mailbox/file" OP_SEARCH "search for a regular expression" OP_SEARCH_REVERSE "search backwards for a regular expression" OP_SEARCH_NEXT "search for next match" diff --git a/UPDATING b/UPDATING index eb30299..903d464 100644 --- a/UPDATING +++ b/UPDATING @@ -4,6 +4,25 @@ mutt. Please read this file carefully when upgrading your installation. The keys used are: !: modified feature, -: deleted feature, +: new feature +hg tip: + ! $fcc_attach is a quadoption now + + $honor_disposition to honor Content-Disposition headers + + $search_context specifies number of context lines for search results + in pager/page-based menus + + ssl_use_sslv2 defaults to no + + uncolor works for header + body objects, too + + the "flagged" and "replied" flags are enabled/supported for + POP when built with header caching + ! browser correctly displays maildir's mtime + + and work in the pager, too + + ~x pattern also matches against In-Reply-To + + lower case patterns for string searches perform case-insensitive + search as regex patterns do (except IMAP) + + $ssl_verify_dates controls whether mutt checks the validity period of + SSL certificates + + $ssl_verify_hostname controls whether mutt will accept certificates whose + host names do not match the host name in the folder URL. + 1.5.19 (2009-01-05): + support for SSL certificate chains diff --git a/VERSION b/VERSION index e7a15ce..a7ccabd 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -1.5.19 +1.5.20 diff --git a/aclocal.m4 b/aclocal.m4 index 5c9fa07..5c4aa9c 100644 --- a/aclocal.m4 +++ b/aclocal.m4 @@ -1,7 +1,7 @@ -# generated automatically by aclocal 1.10.1 -*- Autoconf -*- +# generated automatically by aclocal 1.11 -*- Autoconf -*- # Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, -# 2005, 2006, 2007, 2008 Free Software Foundation, Inc. +# 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc. # This file is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. @@ -13,13 +13,38 @@ m4_ifndef([AC_AUTOCONF_VERSION], [m4_copy([m4_PACKAGE_VERSION], [AC_AUTOCONF_VERSION])])dnl -m4_if(AC_AUTOCONF_VERSION, [2.61],, -[m4_warning([this file was generated for autoconf 2.61. +m4_if(m4_defn([AC_AUTOCONF_VERSION]), [2.63],, +[m4_warning([this file was generated for autoconf 2.63. You have another version of autoconf. It may work, but is not guaranteed to. If you have problems, you may need to regenerate the build system entirely. To do so, use the procedure documented by the package, typically `autoreconf'.])]) -# Copyright (C) 2002, 2003, 2005, 2006, 2007 Free Software Foundation, Inc. +# isc-posix.m4 serial 2 (gettext-0.11.2) +dnl Copyright (C) 1995-2002 Free Software Foundation, Inc. +dnl This file is free software; the Free Software Foundation +dnl gives unlimited permission to copy and/or distribute it, +dnl with or without modifications, as long as this notice is preserved. + +# This file is not needed with autoconf-2.53 and newer. Remove it in 2005. + +# This test replaces the one in autoconf. +# Currently this macro should have the same name as the autoconf macro +# because gettext's gettext.m4 (distributed in the automake package) +# still uses it. Otherwise, the use in gettext.m4 makes autoheader +# give these diagnostics: +# configure.in:556: AC_TRY_COMPILE was called before AC_ISC_POSIX +# configure.in:556: AC_TRY_RUN was called before AC_ISC_POSIX + +undefine([AC_ISC_POSIX]) + +AC_DEFUN([AC_ISC_POSIX], + [ + dnl This test replaces the obsolescent AC_ISC_POSIX kludge. + AC_CHECK_LIB(cposix, strerror, [LIBS="$LIBS -lcposix"]) + ] +) + +# Copyright (C) 2002, 2003, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. # # This file is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, @@ -31,10 +56,10 @@ To do so, use the procedure documented by the package, typically `autoreconf'.]) # generated from the m4 files accompanying Automake X.Y. # (This private macro should not be called outside this file.) AC_DEFUN([AM_AUTOMAKE_VERSION], -[am__api_version='1.10' +[am__api_version='1.11' dnl Some users find AM_AUTOMAKE_VERSION and mistake it for a way to dnl require some minimum version. Point them to the right macro. -m4_if([$1], [1.10.1], [], +m4_if([$1], [1.11], [], [AC_FATAL([Do not call $0, use AM_INIT_AUTOMAKE([$1]).])])dnl ]) @@ -48,12 +73,12 @@ m4_define([_AM_AUTOCONF_VERSION], []) # AM_SET_CURRENT_AUTOMAKE_VERSION # ------------------------------- # Call AM_AUTOMAKE_VERSION and AM_AUTOMAKE_VERSION so they can be traced. -# This function is AC_REQUIREd by AC_INIT_AUTOMAKE. +# This function is AC_REQUIREd by AM_INIT_AUTOMAKE. AC_DEFUN([AM_SET_CURRENT_AUTOMAKE_VERSION], -[AM_AUTOMAKE_VERSION([1.10.1])dnl +[AM_AUTOMAKE_VERSION([1.11])dnl m4_ifndef([AC_AUTOCONF_VERSION], [m4_copy([m4_PACKAGE_VERSION], [AC_AUTOCONF_VERSION])])dnl -_AM_AUTOCONF_VERSION(AC_AUTOCONF_VERSION)]) +_AM_AUTOCONF_VERSION(m4_defn([AC_AUTOCONF_VERSION]))]) # AM_AUX_DIR_EXPAND -*- Autoconf -*- @@ -110,14 +135,14 @@ am_aux_dir=`cd $ac_aux_dir && pwd` # AM_CONDITIONAL -*- Autoconf -*- -# Copyright (C) 1997, 2000, 2001, 2003, 2004, 2005, 2006 +# Copyright (C) 1997, 2000, 2001, 2003, 2004, 2005, 2006, 2008 # Free Software Foundation, Inc. # # This file is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. -# serial 8 +# serial 9 # AM_CONDITIONAL(NAME, SHELL-CONDITION) # ------------------------------------- @@ -130,6 +155,7 @@ AC_SUBST([$1_TRUE])dnl AC_SUBST([$1_FALSE])dnl _AM_SUBST_NOTMAKE([$1_TRUE])dnl _AM_SUBST_NOTMAKE([$1_FALSE])dnl +m4_define([_AM_COND_VALUE_$1], [$2])dnl if $2; then $1_TRUE= $1_FALSE='#' @@ -143,14 +169,14 @@ AC_CONFIG_COMMANDS_PRE( Usually this means the macro was only invoked conditionally.]]) fi])]) -# Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 +# Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2009 # Free Software Foundation, Inc. # # This file is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. -# serial 9 +# serial 10 # There are a few dirty hacks below to avoid letting `AC_PROG_CC' be # written in clear, in which case automake, when reading aclocal.m4, @@ -207,6 +233,16 @@ AC_CACHE_CHECK([dependency style of $depcc], if test "$am_compiler_list" = ""; then am_compiler_list=`sed -n ['s/^#*\([a-zA-Z0-9]*\))$/\1/p'] < ./depcomp` fi + am__universal=false + m4_case([$1], [CC], + [case " $depcc " in #( + *\ -arch\ *\ -arch\ *) am__universal=true ;; + esac], + [CXX], + [case " $depcc " in #( + *\ -arch\ *\ -arch\ *) am__universal=true ;; + esac]) + for depmode in $am_compiler_list; do # Setup a source with many dependencies, because some compilers # like to wrap large dependency lists on column 80 (with \), and @@ -224,7 +260,17 @@ AC_CACHE_CHECK([dependency style of $depcc], done echo "${am__include} ${am__quote}sub/conftest.Po${am__quote}" > confmf + # We check with `-c' and `-o' for the sake of the "dashmstdout" + # mode. It turns out that the SunPro C++ compiler does not properly + # handle `-M -o', and we need to detect this. Also, some Intel + # versions had trouble with output in subdirs + am__obj=sub/conftest.${OBJEXT-o} + am__minus_obj="-o $am__obj" case $depmode in + gcc) + # This depmode causes a compiler race in universal mode. + test "$am__universal" = false || continue + ;; nosideeffect) # after this tag, mechanisms are not by side-effect, so they'll # only be used when explicitly requested @@ -234,19 +280,23 @@ AC_CACHE_CHECK([dependency style of $depcc], break fi ;; + msvisualcpp | msvcmsys) + # This compiler won't grok `-c -o', but also, the minuso test has + # not run yet. These depmodes are late enough in the game, and + # so weak that their functioning should not be impacted. + am__obj=conftest.${OBJEXT-o} + am__minus_obj= + ;; none) break ;; esac - # We check with `-c' and `-o' for the sake of the "dashmstdout" - # mode. It turns out that the SunPro C++ compiler does not properly - # handle `-M -o', and we need to detect this. if depmode=$depmode \ - source=sub/conftest.c object=sub/conftest.${OBJEXT-o} \ + source=sub/conftest.c object=$am__obj \ depfile=sub/conftest.Po tmpdepfile=sub/conftest.TPo \ - $SHELL ./depcomp $depcc -c -o sub/conftest.${OBJEXT-o} sub/conftest.c \ + $SHELL ./depcomp $depcc -c $am__minus_obj sub/conftest.c \ >/dev/null 2>conftest.err && grep sub/conftst1.h sub/conftest.Po > /dev/null 2>&1 && grep sub/conftst6.h sub/conftest.Po > /dev/null 2>&1 && - grep sub/conftest.${OBJEXT-o} sub/conftest.Po > /dev/null 2>&1 && + grep $am__obj sub/conftest.Po > /dev/null 2>&1 && ${MAKE-make} -s -f confmf > /dev/null 2>&1; then # icc doesn't choke on unknown options, it will just issue warnings # or remarks (even with -Werror). So we grep stderr for any message @@ -303,57 +353,68 @@ _AM_SUBST_NOTMAKE([AMDEPBACKSLASH])dnl # Generate code to set up dependency tracking. -*- Autoconf -*- -# Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005 +# Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2008 # Free Software Foundation, Inc. # # This file is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. -#serial 3 +#serial 5 # _AM_OUTPUT_DEPENDENCY_COMMANDS # ------------------------------ AC_DEFUN([_AM_OUTPUT_DEPENDENCY_COMMANDS], -[for mf in $CONFIG_FILES; do - # Strip MF so we end up with the name of the file. - mf=`echo "$mf" | sed -e 's/:.*$//'` - # Check whether this is an Automake generated Makefile or not. - # We used to match only the files named `Makefile.in', but - # some people rename them; so instead we look at the file content. - # Grep'ing the first line is not enough: some people post-process - # each Makefile.in and add a new line on top of each file to say so. - # Grep'ing the whole file is not good either: AIX grep has a line - # limit of 2048, but all sed's we know have understand at least 4000. - if sed -n 's,^#.*generated by automake.*,X,p' "$mf" | grep X >/dev/null 2>&1; then - dirpart=`AS_DIRNAME("$mf")` - else - continue - fi - # Extract the definition of DEPDIR, am__include, and am__quote - # from the Makefile without running `make'. - DEPDIR=`sed -n 's/^DEPDIR = //p' < "$mf"` - test -z "$DEPDIR" && continue - am__include=`sed -n 's/^am__include = //p' < "$mf"` - test -z "am__include" && continue - am__quote=`sed -n 's/^am__quote = //p' < "$mf"` - # When using ansi2knr, U may be empty or an underscore; expand it - U=`sed -n 's/^U = //p' < "$mf"` - # Find all dependency output files, they are included files with - # $(DEPDIR) in their names. We invoke sed twice because it is the - # simplest approach to changing $(DEPDIR) to its actual value in the - # expansion. - for file in `sed -n " - s/^$am__include $am__quote\(.*(DEPDIR).*\)$am__quote"'$/\1/p' <"$mf" | \ - sed -e 's/\$(DEPDIR)/'"$DEPDIR"'/g' -e 's/\$U/'"$U"'/g'`; do - # Make sure the directory exists. - test -f "$dirpart/$file" && continue - fdir=`AS_DIRNAME(["$file"])` - AS_MKDIR_P([$dirpart/$fdir]) - # echo "creating $dirpart/$file" - echo '# dummy' > "$dirpart/$file" +[{ + # Autoconf 2.62 quotes --file arguments for eval, but not when files + # are listed without --file. Let's play safe and only enable the eval + # if we detect the quoting. + case $CONFIG_FILES in + *\'*) eval set x "$CONFIG_FILES" ;; + *) set x $CONFIG_FILES ;; + esac + shift + for mf + do + # Strip MF so we end up with the name of the file. + mf=`echo "$mf" | sed -e 's/:.*$//'` + # Check whether this is an Automake generated Makefile or not. + # We used to match only the files named `Makefile.in', but + # some people rename them; so instead we look at the file content. + # Grep'ing the first line is not enough: some people post-process + # each Makefile.in and add a new line on top of each file to say so. + # Grep'ing the whole file is not good either: AIX grep has a line + # limit of 2048, but all sed's we know have understand at least 4000. + if sed -n 's,^#.*generated by automake.*,X,p' "$mf" | grep X >/dev/null 2>&1; then + dirpart=`AS_DIRNAME("$mf")` + else + continue + fi + # Extract the definition of DEPDIR, am__include, and am__quote + # from the Makefile without running `make'. + DEPDIR=`sed -n 's/^DEPDIR = //p' < "$mf"` + test -z "$DEPDIR" && continue + am__include=`sed -n 's/^am__include = //p' < "$mf"` + test -z "am__include" && continue + am__quote=`sed -n 's/^am__quote = //p' < "$mf"` + # When using ansi2knr, U may be empty or an underscore; expand it + U=`sed -n 's/^U = //p' < "$mf"` + # Find all dependency output files, they are included files with + # $(DEPDIR) in their names. We invoke sed twice because it is the + # simplest approach to changing $(DEPDIR) to its actual value in the + # expansion. + for file in `sed -n " + s/^$am__include $am__quote\(.*(DEPDIR).*\)$am__quote"'$/\1/p' <"$mf" | \ + sed -e 's/\$(DEPDIR)/'"$DEPDIR"'/g' -e 's/\$U/'"$U"'/g'`; do + # Make sure the directory exists. + test -f "$dirpart/$file" && continue + fdir=`AS_DIRNAME(["$file"])` + AS_MKDIR_P([$dirpart/$fdir]) + # echo "creating $dirpart/$file" + echo '# dummy' > "$dirpart/$file" + done done -done +} ])# _AM_OUTPUT_DEPENDENCY_COMMANDS @@ -385,13 +446,13 @@ AU_DEFUN([AM_CONFIG_HEADER], [AC_CONFIG_HEADERS($@)]) # Do all the work for Automake. -*- Autoconf -*- # Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, -# 2005, 2006, 2008 Free Software Foundation, Inc. +# 2005, 2006, 2008, 2009 Free Software Foundation, Inc. # # This file is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. -# serial 13 +# serial 16 # This macro actually does too much. Some checks are only needed if # your package does certain things. But this isn't really a big deal. @@ -408,7 +469,7 @@ AU_DEFUN([AM_CONFIG_HEADER], [AC_CONFIG_HEADERS($@)]) # arguments mandatory, and then we can depend on a new Autoconf # release and drop the old call support. AC_DEFUN([AM_INIT_AUTOMAKE], -[AC_PREREQ([2.60])dnl +[AC_PREREQ([2.62])dnl dnl Autoconf wants to disallow AM_ names. We explicitly allow dnl the ones we care about. m4_pattern_allow([^AM_[A-Z]+FLAGS$])dnl @@ -459,8 +520,8 @@ AM_MISSING_PROG(AUTOCONF, autoconf) AM_MISSING_PROG(AUTOMAKE, automake-${am__api_version}) AM_MISSING_PROG(AUTOHEADER, autoheader) AM_MISSING_PROG(MAKEINFO, makeinfo) -AM_PROG_INSTALL_SH -AM_PROG_INSTALL_STRIP +AC_REQUIRE([AM_PROG_INSTALL_SH])dnl +AC_REQUIRE([AM_PROG_INSTALL_STRIP])dnl AC_REQUIRE([AM_PROG_MKDIR_P])dnl # We need awk for the "check" target. The system "awk" is bad on # some platforms. @@ -468,24 +529,37 @@ AC_REQUIRE([AC_PROG_AWK])dnl AC_REQUIRE([AC_PROG_MAKE_SET])dnl AC_REQUIRE([AM_SET_LEADING_DOT])dnl _AM_IF_OPTION([tar-ustar], [_AM_PROG_TAR([ustar])], - [_AM_IF_OPTION([tar-pax], [_AM_PROG_TAR([pax])], - [_AM_PROG_TAR([v7])])]) + [_AM_IF_OPTION([tar-pax], [_AM_PROG_TAR([pax])], + [_AM_PROG_TAR([v7])])]) _AM_IF_OPTION([no-dependencies],, [AC_PROVIDE_IFELSE([AC_PROG_CC], - [_AM_DEPENDENCIES(CC)], - [define([AC_PROG_CC], - defn([AC_PROG_CC])[_AM_DEPENDENCIES(CC)])])dnl + [_AM_DEPENDENCIES(CC)], + [define([AC_PROG_CC], + defn([AC_PROG_CC])[_AM_DEPENDENCIES(CC)])])dnl AC_PROVIDE_IFELSE([AC_PROG_CXX], - [_AM_DEPENDENCIES(CXX)], - [define([AC_PROG_CXX], - defn([AC_PROG_CXX])[_AM_DEPENDENCIES(CXX)])])dnl + [_AM_DEPENDENCIES(CXX)], + [define([AC_PROG_CXX], + defn([AC_PROG_CXX])[_AM_DEPENDENCIES(CXX)])])dnl AC_PROVIDE_IFELSE([AC_PROG_OBJC], - [_AM_DEPENDENCIES(OBJC)], - [define([AC_PROG_OBJC], - defn([AC_PROG_OBJC])[_AM_DEPENDENCIES(OBJC)])])dnl + [_AM_DEPENDENCIES(OBJC)], + [define([AC_PROG_OBJC], + defn([AC_PROG_OBJC])[_AM_DEPENDENCIES(OBJC)])])dnl ]) +_AM_IF_OPTION([silent-rules], [AC_REQUIRE([AM_SILENT_RULES])])dnl +dnl The `parallel-tests' driver may need to know about EXEEXT, so add the +dnl `am__EXEEXT' conditional if _AM_COMPILER_EXEEXT was seen. This macro +dnl is hooked onto _AC_COMPILER_EXEEXT early, see below. +AC_CONFIG_COMMANDS_PRE(dnl +[m4_provide_if([_AM_COMPILER_EXEEXT], + [AM_CONDITIONAL([am__EXEEXT], [test -n "$EXEEXT"])])])dnl ]) +dnl Hook into `_AC_COMPILER_EXEEXT' early to learn its expansion. Do not +dnl add the conditional right here, as _AC_COMPILER_EXEEXT may be further +dnl mangled by Autoconf and run in a shell conditional statement. +m4_define([_AC_COMPILER_EXEEXT], +m4_defn([_AC_COMPILER_EXEEXT])[m4_provide([_AM_COMPILER_EXEEXT])]) + # When config.status generates a header, we must update the stamp-h file. # This file resides in the same directory as the config header @@ -508,7 +582,7 @@ for _am_header in $config_headers :; do done echo "timestamp for $_am_arg" >`AS_DIRNAME(["$_am_arg"])`/stamp-h[]$_am_stamp_count]) -# Copyright (C) 2001, 2003, 2005 Free Software Foundation, Inc. +# Copyright (C) 2001, 2003, 2005, 2008 Free Software Foundation, Inc. # # This file is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, @@ -519,7 +593,14 @@ echo "timestamp for $_am_arg" >`AS_DIRNAME(["$_am_arg"])`/stamp-h[]$_am_stamp_co # Define $install_sh. AC_DEFUN([AM_PROG_INSTALL_SH], [AC_REQUIRE([AM_AUX_DIR_EXPAND])dnl -install_sh=${install_sh-"\$(SHELL) $am_aux_dir/install-sh"} +if test x"${install_sh}" != xset; then + case $am_aux_dir in + *\ * | *\ *) + install_sh="\${SHELL} '$am_aux_dir/install-sh'" ;; + *) + install_sh="\${SHELL} $am_aux_dir/install-sh" + esac +fi AC_SUBST(install_sh)]) # Copyright (C) 2003, 2005 Free Software Foundation, Inc. @@ -545,13 +626,13 @@ AC_SUBST([am__leading_dot])]) # Check to see how 'make' treats includes. -*- Autoconf -*- -# Copyright (C) 2001, 2002, 2003, 2005 Free Software Foundation, Inc. +# Copyright (C) 2001, 2002, 2003, 2005, 2009 Free Software Foundation, Inc. # # This file is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. -# serial 3 +# serial 4 # AM_MAKE_INCLUDE() # ----------------- @@ -560,7 +641,7 @@ AC_DEFUN([AM_MAKE_INCLUDE], [am_make=${MAKE-make} cat > confinc << 'END' am__doit: - @echo done + @echo this is the am__doit target .PHONY: am__doit END # If we don't find an include directive, just comment out the code. @@ -570,24 +651,24 @@ am__quote= _am_result=none # First try GNU make style include. echo "include confinc" > confmf -# We grep out `Entering directory' and `Leaving directory' -# messages which can occur if `w' ends up in MAKEFLAGS. -# In particular we don't look at `^make:' because GNU make might -# be invoked under some other name (usually "gmake"), in which -# case it prints its new name instead of `make'. -if test "`$am_make -s -f confmf 2> /dev/null | grep -v 'ing directory'`" = "done"; then - am__include=include - am__quote= - _am_result=GNU -fi +# Ignore all kinds of additional output from `make'. +case `$am_make -s -f confmf 2> /dev/null` in #( +*the\ am__doit\ target*) + am__include=include + am__quote= + _am_result=GNU + ;; +esac # Now try BSD make style include. if test "$am__include" = "#"; then echo '.include "confinc"' > confmf - if test "`$am_make -s -f confmf 2> /dev/null`" = "done"; then - am__include=.include - am__quote="\"" - _am_result=BSD - fi + case `$am_make -s -f confmf 2> /dev/null` in #( + *the\ am__doit\ target*) + am__include=.include + am__quote="\"" + _am_result=BSD + ;; + esac fi AC_SUBST([am__include]) AC_SUBST([am__quote]) @@ -597,14 +678,14 @@ rm -f confinc confmf # Fake the existence of programs that GNU maintainers use. -*- Autoconf -*- -# Copyright (C) 1997, 1999, 2000, 2001, 2003, 2004, 2005 +# Copyright (C) 1997, 1999, 2000, 2001, 2003, 2004, 2005, 2008 # Free Software Foundation, Inc. # # This file is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. -# serial 5 +# serial 6 # AM_MISSING_PROG(NAME, PROGRAM) # ------------------------------ @@ -621,7 +702,14 @@ AC_SUBST($1)]) AC_DEFUN([AM_MISSING_HAS_RUN], [AC_REQUIRE([AM_AUX_DIR_EXPAND])dnl AC_REQUIRE_AUX_FILE([missing])dnl -test x"${MISSING+set}" = xset || MISSING="\${SHELL} $am_aux_dir/missing" +if test x"${MISSING+set}" != xset; then + case $am_aux_dir in + *\ * | *\ *) + MISSING="\${SHELL} \"$am_aux_dir/missing\"" ;; + *) + MISSING="\${SHELL} $am_aux_dir/missing" ;; + esac +fi # Use eval to expand $SHELL if eval "$MISSING --run true"; then am_missing_run="$MISSING --run " @@ -659,13 +747,13 @@ esac # Helper functions for option handling. -*- Autoconf -*- -# Copyright (C) 2001, 2002, 2003, 2005 Free Software Foundation, Inc. +# Copyright (C) 2001, 2002, 2003, 2005, 2008 Free Software Foundation, Inc. # # This file is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. -# serial 3 +# serial 4 # _AM_MANGLE_OPTION(NAME) # ----------------------- @@ -682,7 +770,7 @@ AC_DEFUN([_AM_SET_OPTION], # ---------------------------------- # OPTIONS is a space-separated list of Automake options. AC_DEFUN([_AM_SET_OPTIONS], -[AC_FOREACH([_AM_Option], [$1], [_AM_SET_OPTION(_AM_Option)])]) +[m4_foreach_w([_AM_Option], [$1], [_AM_SET_OPTION(_AM_Option)])]) # _AM_IF_OPTION(OPTION, IF-SET, [IF-NOT-SET]) # ------------------------------------------- @@ -718,14 +806,14 @@ AU_DEFUN([fp_C_PROTOTYPES], [AM_C_PROTOTYPES]) # Check to make sure that the build environment is sane. -*- Autoconf -*- -# Copyright (C) 1996, 1997, 2000, 2001, 2003, 2005 +# Copyright (C) 1996, 1997, 2000, 2001, 2003, 2005, 2008 # Free Software Foundation, Inc. # # This file is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. -# serial 4 +# serial 5 # AM_SANITY_CHECK # --------------- @@ -734,16 +822,29 @@ AC_DEFUN([AM_SANITY_CHECK], # Just in case sleep 1 echo timestamp > conftest.file +# Reject unsafe characters in $srcdir or the absolute working directory +# name. Accept space and tab only in the latter. +am_lf=' +' +case `pwd` in + *[[\\\"\#\$\&\'\`$am_lf]]*) + AC_MSG_ERROR([unsafe absolute working directory name]);; +esac +case $srcdir in + *[[\\\"\#\$\&\'\`$am_lf\ \ ]]*) + AC_MSG_ERROR([unsafe srcdir value: `$srcdir']);; +esac + # Do `set' in a subshell so we don't clobber the current shell's # arguments. Must try -L first in case configure is actually a # symlink; some systems play weird games with the mod time of symlinks # (eg FreeBSD returns the mod time of the symlink's containing # directory). if ( - set X `ls -Lt $srcdir/configure conftest.file 2> /dev/null` + set X `ls -Lt "$srcdir/configure" conftest.file 2> /dev/null` if test "$[*]" = "X"; then # -L didn't work. - set X `ls -t $srcdir/configure conftest.file` + set X `ls -t "$srcdir/configure" conftest.file` fi rm -f conftest.file if test "$[*]" != "X $srcdir/configure conftest.file" \ @@ -796,18 +897,25 @@ fi INSTALL_STRIP_PROGRAM="\$(install_sh) -c -s" AC_SUBST([INSTALL_STRIP_PROGRAM])]) -# Copyright (C) 2006 Free Software Foundation, Inc. +# Copyright (C) 2006, 2008 Free Software Foundation, Inc. # # This file is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. +# serial 2 + # _AM_SUBST_NOTMAKE(VARIABLE) # --------------------------- # Prevent Automake from outputting VARIABLE = @VARIABLE@ in Makefile.in. # This macro is traced by Automake. AC_DEFUN([_AM_SUBST_NOTMAKE]) +# AM_SUBST_NOTMAKE(VARIABLE) +# --------------------------- +# Public sister of _AM_SUBST_NOTMAKE. +AC_DEFUN([AM_SUBST_NOTMAKE], [_AM_SUBST_NOTMAKE($@)]) + # Check how to create a tarball. -*- Autoconf -*- # Copyright (C) 2004, 2005 Free Software Foundation, Inc. @@ -914,6 +1022,5 @@ m4_include([m4/gpgme.m4]) m4_include([m4/gssapi.m4]) m4_include([m4/iconv.m4]) m4_include([m4/lcmessage.m4]) -m4_include([m4/libgnutls.m4]) m4_include([m4/progtest.m4]) m4_include([m4/types.m4]) diff --git a/addrbook.c b/addrbook.c index a6a0326..7d82cf5 100644 --- a/addrbook.c +++ b/addrbook.c @@ -39,7 +39,7 @@ static struct mapping_t AliasHelp[] = { { N_("Undel"), OP_UNDELETE }, { N_("Select"), OP_GENERIC_SELECT_ENTRY }, { N_("Help"), OP_HELP }, - { NULL } + { NULL, 0 } }; static const char * diff --git a/alias.c b/alias.c index 9128372..a8fa61f 100644 --- a/alias.c +++ b/alias.c @@ -70,7 +70,7 @@ static ADDRESS *mutt_expand_aliases_r (ADDRESS *a, LIST **expn) u->data = safe_strdup (a->mailbox); u->next = *expn; *expn = u; - w = rfc822_cpy_adr (t); + w = rfc822_cpy_adr (t, 0); w = mutt_expand_aliases_r (w, expn); if (head) last->next = w; @@ -359,6 +359,7 @@ retry_name: if (fread(buf, 1, 1, rc) != 1) { mutt_perror (_("Error reading alias file")); + safe_fclose (&rc); return; } if (fseek (rc, 0, SEEK_END) < 0) @@ -378,7 +379,7 @@ retry_name: recode_buf (buf, sizeof (buf)); write_safe_address (rc, buf); fputc ('\n', rc); - fclose (rc); + safe_fclose (&rc); mutt_message _("Alias added."); } else @@ -388,7 +389,7 @@ retry_name: fseek_err: mutt_perror (_("Error seeking in alias file")); - fclose(rc); + safe_fclose (&rc); return; } @@ -487,7 +488,9 @@ int mutt_alias_complete (char *s, size_t buflen) char bestname[HUGE_STRING]; int i; +#ifndef min #define min(a,b) ((afilename); - if(fpin) fclose(fpin); - if(fpout) fclose(fpout); + if(fpin) safe_fclose (&fpin); + if(fpout) safe_fclose (&fpout); return a->unlink ? 0 : -1; } @@ -176,8 +176,8 @@ int mutt_compose_attachment (BODY *a) goto bailout; } mutt_copy_stream (fp, tfp); - fclose (fp); - fclose (tfp); + safe_fclose (&fp); + safe_fclose (&tfp); mutt_unlink (a->filename); if (mutt_rename_file (tempfile, a->filename) != 0) { @@ -416,7 +416,7 @@ int mutt_view_attachment (FILE *fp, BODY *a, int flag, HEADER *hdr, int use_pipe = 0; int use_pager = 1; char type[STRING]; - char command[STRING]; + char command[HUGE_STRING]; char descrip[STRING]; char *fname; rfc1524_entry *entry = NULL; @@ -551,11 +551,11 @@ int mutt_view_attachment (FILE *fp, BODY *a, int flag, HEADER *hdr, { if (a->description) snprintf (descrip, sizeof (descrip), - "---Command: %-20.20s Description: %s", + _("---Command: %-20.20s Description: %s"), command, a->description); else snprintf (descrip, sizeof (descrip), - "---Command: %-30.30s Attachment: %s", command, type); + _("---Command: %-30.30s Attachment: %s"), command, type); } if ((mutt_wait_filter (thepid) || (entry->needsterminal && @@ -601,10 +601,10 @@ int mutt_view_attachment (FILE *fp, BODY *a, int flag, HEADER *hdr, if (a->description) strfcpy (descrip, a->description, sizeof (descrip)); else if (a->filename) - snprintf (descrip, sizeof (descrip), "---Attachment: %s : %s", + snprintf (descrip, sizeof (descrip), _("---Attachment: %s: %s"), a->filename, type); else - snprintf (descrip, sizeof (descrip), "---Attachment: %s", type); + snprintf (descrip, sizeof (descrip), _("---Attachment: %s"), type); } /* We only reach this point if there have been no errors */ @@ -798,21 +798,25 @@ int mutt_save_attachment (FILE *fp, BODY *m, char *path, int flags, HEADER *hdr) else { /* In recv mode, extract from folder and decode */ - + STATE s; - + memset (&s, 0, sizeof (s)); + s.flags |= M_CHARCONV; + if ((s.fpout = mutt_save_attachment_open (path, flags)) == NULL) { mutt_perror ("fopen"); + mutt_sleep (2); return (-1); } fseeko ((s.fpin = fp), m->offset, 0); mutt_decode_attachment (m, &s); - + if (fclose (s.fpout) != 0) { mutt_perror ("fclose"); + mutt_sleep (2); return (-1); } } @@ -884,7 +888,7 @@ int mutt_decode_save_attachment (FILE *fp, BODY *m, char *path, if (stat (m->filename, &st) == -1) { mutt_perror ("stat"); - fclose (s.fpout); + safe_fclose (&s.fpout); return (-1); } @@ -915,7 +919,7 @@ int mutt_decode_save_attachment (FILE *fp, BODY *m, char *path, mutt_body_handler (m, &s); - fclose (s.fpout); + safe_fclose (&s.fpout); if (fp == NULL) { m->length = 0; @@ -926,7 +930,7 @@ int mutt_decode_save_attachment (FILE *fp, BODY *m, char *path, m->parts = saved_parts; m->hdr = saved_hdr; } - fclose (s.fpin); + safe_fclose (&s.fpin); } return (0); diff --git a/bcache.c b/bcache.c index 60e5fdc..81538d2 100644 --- a/bcache.c +++ b/bcache.c @@ -136,6 +136,13 @@ FILE* mutt_bcache_put(body_cache_t *bcache, const char *id, int tmp) snprintf (path, sizeof (path), "%s%s%s", bcache->path, id, tmp ? ".tmp" : ""); + if ((fp = safe_fopen (path, "w+"))) + goto out; + + if (errno == EEXIST) + /* clean up leftover tmp file */ + mutt_unlink (path); + s = strchr (path + 1, '/'); while (!(fp = safe_fopen (path, "w+")) && errno == ENOENT && s) { @@ -147,6 +154,7 @@ FILE* mutt_bcache_put(body_cache_t *bcache, const char *id, int tmp) s = strchr (s + 1, '/'); } + out: dprint (3, (debugfile, "bcache: put: '%s'\n", path)); return fp; diff --git a/browser.c b/browser.c index e9c6390..c05af05 100644 --- a/browser.c +++ b/browser.c @@ -46,7 +46,7 @@ static struct mapping_t FolderHelp[] = { { N_("Chdir"), OP_CHANGE_DIRECTORY }, { N_("Mask"), OP_ENTER_MASK }, { N_("Help"), OP_HELP }, - { NULL } + { NULL, 0 } }; typedef struct folder_t @@ -460,6 +460,21 @@ static int examine_mailboxes (MUTTMENU *menu, struct browser_state *state) if ((! S_ISREG (s.st_mode)) && (! S_ISDIR (s.st_mode)) && (! S_ISLNK (s.st_mode))) continue; + + if (mx_is_maildir (tmp->path)) + { + struct stat st2; + char md[_POSIX_PATH_MAX]; + + snprintf (md, sizeof (md), "%s/new", tmp->path); + if (stat (md, &s) < 0) + s.st_mtime = 0; + snprintf (md, sizeof (md), "%s/cur", tmp->path); + if (stat (md, &st2) < 0) + st2.st_mtime = 0; + if (st2.st_mtime > s.st_mtime) + s.st_mtime = st2.st_mtime; + } strfcpy (buffer, NONULL(tmp->path), sizeof (buffer)); mutt_pretty_mailbox (buffer, sizeof (buffer)); diff --git a/buffy.c b/buffy.c index db20c21..40c229e 100644 --- a/buffy.c +++ b/buffy.c @@ -128,12 +128,37 @@ static int test_new_folder (const char *path) if ((f = fopen (path, "rb"))) { rc = test_last_status_new (f); - fclose (f); + safe_fclose (&f); } return rc; } +void mutt_buffy_cleanup (const char *buf, struct stat *st) +{ + struct utimbuf ut; + BUFFY *tmp; + + if (option(OPTCHECKMBOXSIZE)) + { + tmp = mutt_find_mailbox (buf); + if (tmp && !tmp->new) + mutt_update_mailbox (tmp); + } + else + { + /* fix up the times so buffy won't get confused */ + if (st->st_mtime > st->st_atime) + { + ut.actime = st->st_atime; + ut.modtime = time (NULL); + utime (buf, &ut); + } + else + utime (buf, NULL); + } +} + BUFFY *mutt_find_mailbox (const char *path) { BUFFY *tmp = NULL; @@ -171,6 +196,8 @@ int mutt_parse_mailboxes (BUFFER *path, BUFFER *s, unsigned long data, BUFFER *e BUFFY **tmp,*tmp1; char buf[_POSIX_PATH_MAX]; struct stat sb; + char f1[PATH_MAX], f2[PATH_MAX]; + char *p, *q; while (MoreArgs (s)) { @@ -181,7 +208,6 @@ int mutt_parse_mailboxes (BUFFER *path, BUFFER *s, unsigned long data, BUFFER *e { for (tmp = &Incoming; *tmp;) { - FREE (&((*tmp)->path)); tmp1=(*tmp)->next; FREE (tmp); /* __FREE_CHECKED__ */ *tmp=tmp1; @@ -194,11 +220,16 @@ int mutt_parse_mailboxes (BUFFER *path, BUFFER *s, unsigned long data, BUFFER *e /* Skip empty tokens. */ if(!*buf) continue; - /* simple check to avoid duplicates */ + /* avoid duplicates */ + p = realpath (buf, f1); for (tmp = &Incoming; *tmp; tmp = &((*tmp)->next)) { - if (mutt_strcmp (buf, (*tmp)->path) == 0) + q = realpath ((*tmp)->path, f2); + if (mutt_strcmp (p ? p : buf, q ? q : (*tmp)->path) == 0) + { + dprint(3,(debugfile,"mailbox '%s' already registered as '%s'\n", buf, (*tmp)->path)); break; + } } if(data == M_UNMAILBOXES) @@ -216,7 +247,7 @@ int mutt_parse_mailboxes (BUFFER *path, BUFFER *s, unsigned long data, BUFFER *e if (!*tmp) { *tmp = (BUFFY *) safe_calloc (1, sizeof (BUFFY)); - (*tmp)->path = safe_strdup (buf); + strfcpy ((*tmp)->path, buf, sizeof ((*tmp)->path)); (*tmp)->next = NULL; /* it is tempting to set magic right here */ (*tmp)->magic = 0; @@ -260,6 +291,10 @@ int mutt_buffy_check (int force) struct stat contex_sb; time_t t; + sb.st_size=0; + contex_sb.st_dev=0; + contex_sb.st_ino=0; + #ifdef USE_IMAP /* update postponed count as well, on force */ if (force) @@ -476,59 +511,34 @@ int mutt_buffy_notify (void) * mutt_buffy() -- incoming folders completion routine * * given a folder name, this routine gives the next incoming folder with new - * new mail. + * mail. */ void mutt_buffy (char *s, size_t slen) { - int count; BUFFY *tmp = Incoming; + int pass, found = 0; - mutt_expand_path (s, _POSIX_PATH_MAX); - switch (mutt_buffy_check (0)) - { - case 0: - - *s = '\0'; - break; - - case 1: + mutt_expand_path (s, slen); - while (tmp && !tmp->new) - tmp = tmp->next; - if (!tmp) - { - *s = '\0'; - mutt_buffy_check (1); /* buffy was wrong - resync things */ - break; - } - strfcpy (s, tmp->path, slen); - mutt_pretty_mailbox (s, slen); - break; - - default: - - count = 0; - while (count < 3) - { - if (mutt_strcmp (s, tmp->path) == 0) - count++; - else if (count && tmp->new) - break; - tmp = tmp->next; - if (!tmp) + if (mutt_buffy_check (0)) + { + for (pass = 0; pass < 2; pass++) + for (tmp = Incoming; tmp; tmp = tmp->next) { - tmp = Incoming; - count++; + mutt_expand_path (tmp->path, sizeof (tmp->path)); + if ((found || pass) && tmp->new) + { + strfcpy (s, tmp->path, slen); + mutt_pretty_mailbox (s, slen); + return; + } + if (mutt_strcmp (s, tmp->path) == 0) + found = 1; } - } - if (count >= 3) - { - *s = '\0'; - mutt_buffy_check (1); /* buffy was wrong - resync things */ - break; - } - strfcpy (s, tmp->path, slen); - mutt_pretty_mailbox (s, slen); - break; + + mutt_buffy_check (1); /* buffy was wrong - resync things */ } + + /* no folders with new mail */ + *s = '\0'; } diff --git a/buffy.h b/buffy.h index 14f9517..d7ff3b4 100644 --- a/buffy.h +++ b/buffy.h @@ -22,7 +22,7 @@ typedef struct buffy_t { - char *path; + char path[_POSIX_PATH_MAX]; off_t size; struct buffy_t *next; short new; /* mailbox has new mail */ @@ -39,3 +39,7 @@ extern time_t BuffyDoneTime; /* last time we knew for sure how much mail there w BUFFY *mutt_find_mailbox (const char *path); void mutt_update_mailbox (BUFFY * b); + +/* fixes up atime + mtime after mbox/mmdf mailbox was modified + according to stat() info taken before a modification */ +void mutt_buffy_cleanup (const char *buf, struct stat *st); diff --git a/color.c b/color.c index 0288eb1..b39957f 100644 --- a/color.c +++ b/color.c @@ -364,12 +364,12 @@ int mutt_parse_unmono (BUFFER *buf, BUFFER *s, unsigned long data, return _mutt_parse_uncolor(buf, s, data, err, 0); } -static int -_mutt_parse_uncolor (BUFFER *buf, BUFFER *s, unsigned long data, BUFFER *err, - short parse_uncolor) +static int _mutt_parse_uncolor (BUFFER *buf, BUFFER *s, unsigned long data, + BUFFER *err, short parse_uncolor) { int object = 0, do_cache = 0; COLOR_LINE *tmp, *last = NULL; + COLOR_LINE **list; mutt_extract_token (buf, s, 0); @@ -379,14 +379,20 @@ _mutt_parse_uncolor (BUFFER *buf, BUFFER *s, unsigned long data, BUFFER *err, return (-1); } - if (mutt_strncmp (buf->data, "index", 5) != 0) + if (mutt_strncmp (buf->data, "index", 5) == 0) + list = &ColorIndexList; + else if (mutt_strncmp (buf->data, "body", 4) == 0) + list = &ColorBodyList; + else if (mutt_strncmp (buf->data, "header", 7) == 0) + list = &ColorHdrList; + else { snprintf (err->data, err->dsize, - _("%s: command valid only for index object"), + _("%s: command valid only for index, body, header objects"), parse_uncolor ? "uncolor" : "unmono"); return (-1); } - + if (!MoreArgs (s)) { snprintf (err->data, err->dsize, @@ -415,14 +421,13 @@ _mutt_parse_uncolor (BUFFER *buf, BUFFER *s, unsigned long data, BUFFER *err, return 0; } - - + do { mutt_extract_token (buf, s, 0); if (!mutt_strcmp ("*", buf->data)) { - for (tmp = ColorIndexList; tmp; ) + for (tmp = *list; tmp; ) { if (!do_cache) do_cache = 1; @@ -430,22 +435,22 @@ _mutt_parse_uncolor (BUFFER *buf, BUFFER *s, unsigned long data, BUFFER *err, tmp = tmp->next; mutt_free_color_line(&last, parse_uncolor); } - ColorIndexList = NULL; + *list = NULL; } else { - for (last = NULL, tmp = ColorIndexList; tmp; last = tmp, tmp = tmp->next) + for (last = NULL, tmp = *list; tmp; last = tmp, tmp = tmp->next) { if (!mutt_strcmp (buf->data, tmp->pattern)) { if (!do_cache) do_cache = 1; - dprint(1,(debugfile,"Freeing pattern \"%s\" from ColorIndexList\n", + dprint(1,(debugfile,"Freeing pattern \"%s\" from color list\n", tmp->pattern)); if (last) last->next = tmp->next; else - ColorIndexList = tmp->next; + *list = tmp->next; mutt_free_color_line(&tmp, parse_uncolor); break; } diff --git a/commands.c b/commands.c index 45b9db7..7d9c90d 100644 --- a/commands.c +++ b/commands.c @@ -146,7 +146,7 @@ int mutt_display_message (HEADER *cur) } res = mutt_copy_message (fpout, Context, cur, cmflags, - (option (OPTWEED) ? (CH_WEED | CH_REORDER) : 0) | CH_DECODE | CH_FROM); + (option (OPTWEED) ? (CH_WEED | CH_REORDER) : 0) | CH_DECODE | CH_FROM | CH_DISPLAY); if ((safe_fclose (&fpout) != 0 && errno != EPIPE) || res < 0) { mutt_error (_("Could not copy message")); @@ -246,6 +246,29 @@ void ci_bounce_message (HEADER *h, int *redraw) char *err = NULL; int rc; + /* RfC 5322 mandates a From: header, so warn before bouncing + * messages without one */ + if (h) + { + if (!h->env->from) + { + mutt_error _("Warning: message has no From: header"); + mutt_sleep (2); + } + } + else if (Context) + { + for (rc = 0; rc < Context->msgcount; rc++) + { + if (Context->hdrs[rc]->tagged && !Context->hdrs[rc]->env->from) + { + mutt_error ("Warning: message has no From: header"); + mutt_sleep (2); + break; + } + } + } + if(h) strfcpy(prompt, _("Bounce message to: "), sizeof(prompt)); else @@ -391,7 +414,7 @@ static int _mutt_pipe_message (HEADER *h, char *cmd, } pipe_msg (h, fpout, decode, print); - fclose (fpout); + safe_fclose (&fpout); rc = mutt_wait_filter (thepid); } else @@ -706,8 +729,6 @@ int mutt_save_message (HEADER *h, int delete, char prompt[SHORT_STRING], buf[_POSIX_PATH_MAX]; CONTEXT ctx; struct stat st; - BUFFY *tmp = NULL; - struct utimbuf ut; *redraw = 0; @@ -841,26 +862,7 @@ int mutt_save_message (HEADER *h, int delete, mx_close_mailbox (&ctx, NULL); if (need_buffy_cleanup) - { - if (option(OPTCHECKMBOXSIZE)) - { - tmp = mutt_find_mailbox (buf); - if (tmp && !tmp->new) - mutt_update_mailbox (tmp); - } - else - { - /* fix up the times so buffy won't get confused */ - if (st.st_mtime > st.st_atime) - { - ut.actime = st.st_atime; - ut.modtime = time (NULL); - utime (buf, &ut); - } - else - utime (buf, NULL); - } - } + mutt_buffy_cleanup (ctx.path, &st); mutt_clear_error (); return (0); diff --git a/compose.c b/compose.c index 2829646..5db4c92 100644 --- a/compose.c +++ b/compose.c @@ -94,7 +94,7 @@ static struct mapping_t ComposeHelp[] = { { N_("Attach file"), OP_COMPOSE_ATTACH_FILE }, { N_("Descrip"), OP_COMPOSE_EDIT_DESCRIPTION }, { N_("Help"), OP_HELP }, - { NULL } + { NULL, 0 } }; static void snd_entry (char *b, size_t blen, MUTTMENU *menu, int num) @@ -1073,7 +1073,7 @@ int mutt_compose_menu (HEADER *msg, /* structure for new message */ FREE (&idx[idxlen]); continue; } - fclose (fp); + safe_fclose (&fp); if ((idx[idxlen]->content = mutt_make_file_attach (fname)) == NULL) { diff --git a/config.guess b/config.guess index 0f0fe71..396482d 100755 --- a/config.guess +++ b/config.guess @@ -4,7 +4,7 @@ # 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, # Inc. -timestamp='2007-03-06' +timestamp='2006-07-02' # This file is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by @@ -161,7 +161,6 @@ case "${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in arm*) machine=arm-unknown ;; sh3el) machine=shl-unknown ;; sh3eb) machine=sh-unknown ;; - sh5el) machine=sh5le-unknown ;; *) machine=${UNAME_MACHINE_ARCH}-unknown ;; esac # The Operating System including object format, if it has switched @@ -781,7 +780,7 @@ EOF i*:CYGWIN*:*) echo ${UNAME_MACHINE}-pc-cygwin exit ;; - *:MINGW*:*) + i*:MINGW*:*) echo ${UNAME_MACHINE}-pc-mingw32 exit ;; i*:windows32*:*) @@ -791,15 +790,12 @@ EOF i*:PW*:*) echo ${UNAME_MACHINE}-pc-pw32 exit ;; - *:Interix*:[3456]*) - case ${UNAME_MACHINE} in - x86) - echo i586-pc-interix${UNAME_RELEASE} - exit ;; - EM64T | authenticamd) - echo x86_64-unknown-interix${UNAME_RELEASE} - exit ;; - esac ;; + x86:Interix*:[3456]*) + echo i586-pc-interix${UNAME_RELEASE} + exit ;; + EM64T:Interix*:[3456]*) + echo x86_64-unknown-interix${UNAME_RELEASE} + exit ;; [345]86:Windows_95:* | [345]86:Windows_98:* | [345]86:Windows_NT:*) echo i${UNAME_MACHINE}-pc-mks exit ;; @@ -954,9 +950,6 @@ EOF x86_64:Linux:*:*) echo x86_64-unknown-linux-gnu exit ;; - xtensa:Linux:*:*) - echo xtensa-unknown-linux-gnu - exit ;; i*86:Linux:*:*) # The BFD linker knows what the default object file format is, so # first see if it will tell us. cd to the root directory to prevent @@ -1215,15 +1208,6 @@ EOF SX-6:SUPER-UX:*:*) echo sx6-nec-superux${UNAME_RELEASE} exit ;; - SX-7:SUPER-UX:*:*) - echo sx7-nec-superux${UNAME_RELEASE} - exit ;; - SX-8:SUPER-UX:*:*) - echo sx8-nec-superux${UNAME_RELEASE} - exit ;; - SX-8R:SUPER-UX:*:*) - echo sx8r-nec-superux${UNAME_RELEASE} - exit ;; Power*:Rhapsody:*:*) echo powerpc-apple-rhapsody${UNAME_RELEASE} exit ;; diff --git a/config.h.in b/config.h.in index d314006..3e68286 100644 --- a/config.h.in +++ b/config.h.in @@ -1,5 +1,8 @@ /* config.h.in. Generated from configure.ac by autoheader. */ +/* Define if building universal (internal helper macro) */ +#undef AC_APPLE_UNIVERSAL_BUILD + /* Define to one of `_getb67', `GETB67', `getb67' for Cray-2 and Cray-YMP systems. This function is required for `alloca.c' support on those systems. */ @@ -68,6 +71,10 @@ /* Define to 1 if you have the `dcgettext' function. */ #undef HAVE_DCGETTEXT +/* Define to 1 if you have the declaration of + `GNUTLS_VERIFY_DISABLE_TIME_CHECKS', and to 0 if you don't. */ +#undef HAVE_DECL_GNUTLS_VERIFY_DISABLE_TIME_CHECKS + /* Define to 1 if you have the declaration of `sys_siglist', and to 0 if you don't. */ #undef HAVE_DECL_SYS_SIGLIST @@ -126,9 +133,6 @@ /* Define to 1 if you have the `getuid' function. */ #undef HAVE_GETUID -/* Define to 1 if you have the header file. */ -#undef HAVE_GNUTLS_OPENSSL_H - /* Define if GPGME supports PKA */ #undef HAVE_GPGME_PKA_TRUST @@ -255,6 +259,9 @@ /* Define if you have meta, as a function or macro. */ #undef HAVE_META +/* Define to 1 if you have the `mkdtemp' function. */ +#undef HAVE_MKDTEMP + /* Define to 1 if you have a working `mmap' system call. */ #undef HAVE_MMAP @@ -330,6 +337,9 @@ /* Define to 1 if you have the `strcasecmp' function. */ #undef HAVE_STRCASECMP +/* Define to 1 if you have the `strcasestr' function. */ +#undef HAVE_STRCASESTR + /* Define to 1 if you have the `strchr' function. */ #undef HAVE_STRCHR @@ -414,6 +424,9 @@ /* Define to 1 if you have the header file. */ #undef HAVE_WCHAR_H +/* Define to 1 if you have the `wcscasecmp' function. */ +#undef HAVE_WCSCASECMP + /* Define to 1 if you have the header file. */ #undef HAVE_WCTYPE_H @@ -572,12 +585,42 @@ /* Define if you want support for SSL via OpenSSL. */ #undef USE_SSL_OPENSSL +/* Enable extensions on AIX 3, Interix. */ +#ifndef _ALL_SOURCE +# undef _ALL_SOURCE +#endif +/* Enable GNU extensions on systems that have them. */ +#ifndef _GNU_SOURCE +# undef _GNU_SOURCE +#endif +/* Enable threading extensions on Solaris. */ +#ifndef _POSIX_PTHREAD_SEMANTICS +# undef _POSIX_PTHREAD_SEMANTICS +#endif +/* Enable extensions on HP NonStop. */ +#ifndef _TANDEM_SOURCE +# undef _TANDEM_SOURCE +#endif +/* Enable general extensions on Solaris. */ +#ifndef __EXTENSIONS__ +# undef __EXTENSIONS__ +#endif + + /* Version number of package */ #undef VERSION -/* Define to 1 if your processor stores words with the most significant byte - first (like Motorola and SPARC, unlike Intel and VAX). */ -#undef WORDS_BIGENDIAN +/* Define WORDS_BIGENDIAN to 1 if your processor stores words with the most + significant byte first (like Motorola and SPARC, unlike Intel). */ +#if defined AC_APPLE_UNIVERSAL_BUILD +# if defined __BIG_ENDIAN__ +# define WORDS_BIGENDIAN 1 +# endif +#else +# ifndef WORDS_BIGENDIAN +# undef WORDS_BIGENDIAN +# endif +#endif #ifndef HAVE_C99_INTTYPES # if SIZEOF_SHORT == 4 @@ -600,17 +643,22 @@ typedef unsigned long long uint64_t; /* Number of bits in a file offset, on hosts where this is settable. */ #undef _FILE_OFFSET_BITS -/* Enable GNU extensions on systems that have them. */ -#ifndef _GNU_SOURCE -# undef _GNU_SOURCE -#endif - /* Define to 1 to make fseeko visible on some hosts (e.g. glibc 2.2). */ #undef _LARGEFILE_SOURCE /* Define for large files, on AIX-style hosts. */ #undef _LARGE_FILES +/* Define to 1 if on MINIX. */ +#undef _MINIX + +/* Define to 2 if the system does not provide POSIX.1 features except with + this defined. */ +#undef _POSIX_1_SOURCE + +/* Define to 1 if you need to in order for `stat' and other things to work. */ +#undef _POSIX_SOURCE + /* Define like PROTOTYPES; this can be used by system headers. */ #undef __PROTOTYPES diff --git a/config.sub b/config.sub index 5defff6..fab0aa3 100755 --- a/config.sub +++ b/config.sub @@ -4,7 +4,7 @@ # 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, # Inc. -timestamp='2007-01-18' +timestamp='2006-09-20' # This file is (in principle) common to ALL GNU software. # The presence of a machine in this file suggests that SOME GNU software @@ -245,12 +245,12 @@ case $basic_machine in | bfin \ | c4x | clipper \ | d10v | d30v | dlx | dsp16xx \ - | fido | fr30 | frv \ + | fr30 | frv \ | h8300 | h8500 | hppa | hppa1.[01] | hppa2.0 | hppa2.0[nw] | hppa64 \ | i370 | i860 | i960 | ia64 \ | ip2k | iq2000 \ | m32c | m32r | m32rle | m68000 | m68k | m88k \ - | maxq | mb | microblaze | mcore | mep \ + | maxq | mb | microblaze | mcore \ | mips | mipsbe | mipseb | mipsel | mipsle \ | mips16 \ | mips64 | mips64el \ @@ -324,7 +324,7 @@ case $basic_machine in | clipper-* | craynv-* | cydra-* \ | d10v-* | d30v-* | dlx-* \ | elxsi-* \ - | f30[01]-* | f700-* | fido-* | fr30-* | frv-* | fx80-* \ + | f30[01]-* | f700-* | fr30-* | frv-* | fx80-* \ | h8300-* | h8500-* \ | hppa-* | hppa1.[01]-* | hppa2.0-* | hppa2.0[nw]-* | hppa64-* \ | i*86-* | i860-* | i960-* | ia64-* \ @@ -925,9 +925,6 @@ case $basic_machine in basic_machine=sh-hitachi os=-hms ;; - sh5el) - basic_machine=sh5le-unknown - ;; sh64) basic_machine=sh64-unknown ;; @@ -1222,7 +1219,7 @@ case $os in | -os2* | -vos* | -palmos* | -uclinux* | -nucleus* \ | -morphos* | -superux* | -rtmk* | -rtmk-nova* | -windiss* \ | -powermax* | -dnix* | -nx6 | -nx7 | -sei* | -dragonfly* \ - | -skyos* | -haiku* | -rdos* | -toppers* | -drops*) + | -skyos* | -haiku* | -rdos* | -toppers*) # Remember, each alternative MUST END IN *, to match a version number. ;; -qnx*) @@ -1417,9 +1414,6 @@ case $basic_machine in m68*-cisco) os=-aout ;; - mep-*) - os=-elf - ;; mips*-cisco) os=-elf ;; diff --git a/configure b/configure index 0180a84..d17cd92 100755 --- a/configure +++ b/configure @@ -1,9 +1,9 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.61. +# Generated by GNU Autoconf 2.63. # # Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, -# 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc. +# 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. # This configure script is free software; the Free Software Foundation # gives unlimited permission to copy, distribute and modify it. ## --------------------- ## @@ -15,7 +15,7 @@ DUALCASE=1; export DUALCASE # for MKS sh if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then emulate sh NULLCMD=: - # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which + # Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which # is contrary to our usage. Disable this feature. alias -g '${1+"$@"}'='"$@"' setopt NO_GLOB_SUBST @@ -37,17 +37,45 @@ as_cr_Letters=$as_cr_letters$as_cr_LETTERS as_cr_digits='0123456789' as_cr_alnum=$as_cr_Letters$as_cr_digits -# The user is always right. -if test "${PATH_SEPARATOR+set}" != set; then - echo "#! /bin/sh" >conf$$.sh - echo "exit 0" >>conf$$.sh - chmod +x conf$$.sh - if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then - PATH_SEPARATOR=';' +as_nl=' +' +export as_nl +# Printing a long string crashes Solaris 7 /usr/bin/printf. +as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\' +as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo +as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo +if (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then + as_echo='printf %s\n' + as_echo_n='printf %s' +else + if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then + as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"' + as_echo_n='/usr/ucb/echo -n' else - PATH_SEPARATOR=: + as_echo_body='eval expr "X$1" : "X\\(.*\\)"' + as_echo_n_body='eval + arg=$1; + case $arg in + *"$as_nl"*) + expr "X$arg" : "X\\(.*\\)$as_nl"; + arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;; + esac; + expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl" + ' + export as_echo_n_body + as_echo_n='sh -c $as_echo_n_body as_echo' fi - rm -f conf$$.sh + export as_echo_body + as_echo='sh -c $as_echo_body as_echo' +fi + +# The user is always right. +if test "${PATH_SEPARATOR+set}" != set; then + PATH_SEPARATOR=: + (PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && { + (PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 || + PATH_SEPARATOR=';' + } fi # Support unset when possible. @@ -63,8 +91,6 @@ fi # there to prevent editors from complaining about space-tab. # (If _AS_PATH_WALK were called with IFS unset, it would disable word # splitting by setting IFS to empty value.) -as_nl=' -' IFS=" "" $as_nl" # Find who we are. Look in the path if we contain no directory separator. @@ -87,7 +113,7 @@ if test "x$as_myself" = x; then as_myself=$0 fi if test ! -f "$as_myself"; then - echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2 + $as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2 { (exit 1); exit 1; } fi @@ -100,17 +126,10 @@ PS2='> ' PS4='+ ' # NLS nuisances. -for as_var in \ - LANG LANGUAGE LC_ADDRESS LC_ALL LC_COLLATE LC_CTYPE LC_IDENTIFICATION \ - LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER \ - LC_TELEPHONE LC_TIME -do - if (set +x; test -z "`(eval $as_var=C; export $as_var) 2>&1`"); then - eval $as_var=C; export $as_var - else - ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var - fi -done +LC_ALL=C +export LC_ALL +LANGUAGE=C +export LANGUAGE # Required to use basename. if expr a : '\(a\)' >/dev/null 2>&1 && @@ -132,7 +151,7 @@ as_me=`$as_basename -- "$0" || $as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \ X"$0" : 'X\(//\)$' \| \ X"$0" : 'X\(/\)' \| . 2>/dev/null || -echo X/"$0" | +$as_echo X/"$0" | sed '/^.*\/\([^/][^/]*\)\/*$/{ s//\1/ q @@ -158,7 +177,7 @@ else as_have_required=no fi - if test $as_have_required = yes && (eval ": + if test $as_have_required = yes && (eval ": (as_func_return () { (exit \$1) } @@ -240,7 +259,7 @@ IFS=$as_save_IFS if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then emulate sh NULLCMD=: - # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which + # Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which # is contrary to our usage. Disable this feature. alias -g '${1+"$@"}'='"$@"' setopt NO_GLOB_SUBST @@ -261,7 +280,7 @@ _ASEOF if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then emulate sh NULLCMD=: - # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which + # Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which # is contrary to our usage. Disable this feature. alias -g '${1+"$@"}'='"$@"' setopt NO_GLOB_SUBST @@ -341,10 +360,10 @@ fi if test "x$CONFIG_SHELL" != x; then for as_var in BASH_ENV ENV - do ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var - done - export CONFIG_SHELL - exec "$CONFIG_SHELL" "$as_myself" ${1+"$@"} + do ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var + done + export CONFIG_SHELL + exec "$CONFIG_SHELL" "$as_myself" ${1+"$@"} fi @@ -413,9 +432,10 @@ fi test \$exitcode = 0") || { echo No shell found that supports shell functions. - echo Please tell autoconf@gnu.org about your system, - echo including any error possibly output before this - echo message + echo Please tell bug-autoconf@gnu.org about your system, + echo including any error possibly output before this message. + echo This can help us improve future autoconf versions. + echo Configuration will now proceed without shell functions. } @@ -451,7 +471,7 @@ test \$exitcode = 0") || { s/-\n.*// ' >$as_me.lineno && chmod +x "$as_me.lineno" || - { echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2 + { $as_echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2 { (exit 1); exit 1; }; } # Don't try to exec as it changes $[0], causing all sort of problems @@ -479,7 +499,6 @@ case `echo -n x` in *) ECHO_N='-n';; esac - if expr a : '\(a\)' >/dev/null 2>&1 && test "X`expr 00001 : '.*\(...\)'`" = X001; then as_expr=expr @@ -492,19 +511,22 @@ if test -d conf$$.dir; then rm -f conf$$.dir/conf$$.file else rm -f conf$$.dir - mkdir conf$$.dir -fi -echo >conf$$.file -if ln -s conf$$.file conf$$ 2>/dev/null; then - as_ln_s='ln -s' - # ... but there are two gotchas: - # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail. - # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable. - # In both cases, we have to default to `cp -p'. - ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe || + mkdir conf$$.dir 2>/dev/null +fi +if (echo >conf$$.file) 2>/dev/null; then + if ln -s conf$$.file conf$$ 2>/dev/null; then + as_ln_s='ln -s' + # ... but there are two gotchas: + # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail. + # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable. + # In both cases, we have to default to `cp -p'. + ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe || + as_ln_s='cp -p' + elif ln conf$$.file conf$$ 2>/dev/null; then + as_ln_s=ln + else as_ln_s='cp -p' -elif ln conf$$.file conf$$ 2>/dev/null; then - as_ln_s=ln + fi else as_ln_s='cp -p' fi @@ -529,10 +551,10 @@ else as_test_x=' eval sh -c '\'' if test -d "$1"; then - test -d "$1/."; + test -d "$1/."; else case $1 in - -*)set "./$1";; + -*)set "./$1";; esac; case `ls -ld'$as_ls_L_option' "$1" 2>/dev/null` in ???[sx]*):;;*)false;;esac;fi @@ -613,163 +635,209 @@ ac_includes_default="\ # include #endif" -ac_subst_vars='SHELL -PATH_SEPARATOR -PACKAGE_NAME -PACKAGE_TARNAME -PACKAGE_VERSION -PACKAGE_STRING -PACKAGE_BUGREPORT -exec_prefix -prefix -program_transform_name -bindir -sbindir -libexecdir -datarootdir -datadir -sysconfdir -sharedstatedir -localstatedir -includedir -oldincludedir -docdir -infodir -htmldir -dvidir -pdfdir -psdir -libdir -localedir -mandir -DEFS -ECHO_C -ECHO_N -ECHO_T -LIBS +ac_subst_vars='am__EXEEXT_FALSE +am__EXEEXT_TRUE +LTLIBOBJS +DSLROOT +OSPCAT +INTL_LIBTOOL_SUFFIX_PREFIX +MKINSTALLDIRS +GENCAT +INSTOBJEXT +DATADIRNAME +POSUB +POFILES +INTLOBJS +INTLLIBS +GMOFILES +CATOBJEXT +CATALOGS +USE_INCLUDED_LIBINTL +BUILD_INCLUDED_LIBINTL +INTLBISON +XGETTEXT +GMSGFMT +MSGFMT +USE_NLS +LIBICONV +GLIBC21 +ALLOCA +LIBIMAPDEPS +LIBIMAP +MUTT_LIB_OBJECTS +MUTTLIBS +MUTT_MD5 +USE_SASL_FALSE +USE_SASL_TRUE +USE_SSL_FALSE +USE_SSL_TRUE +USE_GSS_FALSE +USE_GSS_TRUE +KRB5CFGPATH +BUILD_IMAP_FALSE +BUILD_IMAP_TRUE +DOTLOCK_PERMISSION +DOTLOCK_GROUP +DOTLOCK_TARGET +LIBOBJS +ISPELL +SMIMEAUX_TARGET +PGPAUX_TARGET +OPS +GPGME_LIBS +GPGME_CFLAGS +GPGME_CONFIG +SENDMAIL +DEBUGGER +SDB +GDB +DBX +AR +RANLIB +ANSI2KNR +U +host_os +host_vendor +host_cpu +host +build_os +build_vendor +build_cpu +build +EGREP +GREP +CPP +am__fastdepCC_FALSE +am__fastdepCC_TRUE +CCDEPMODE +AMDEPBACKSLASH +AMDEP_FALSE +AMDEP_TRUE +am__quote +am__include +DEPDIR +OBJEXT +EXEEXT +ac_ct_CC +CPPFLAGS +LDFLAGS +CFLAGS +CC +CONFIG_STATUS_DEPENDENCIES +am__untar +am__tar +AMTAR +am__leading_dot +SET_MAKE +AWK +mkdir_p +MKDIR_P +INSTALL_STRIP_PROGRAM +STRIP +install_sh +MAKEINFO +AUTOHEADER +AUTOMAKE +AUTOCONF +ACLOCAL +VERSION +PACKAGE +CYGPATH_W +am__isrc +INSTALL_DATA +INSTALL_SCRIPT +INSTALL_PROGRAM +target_alias +host_alias build_alias +LIBS +ECHO_T +ECHO_N +ECHO_C +DEFS +mandir +localedir +libdir +psdir +pdfdir +dvidir +htmldir +infodir +docdir +oldincludedir +includedir +localstatedir +sharedstatedir +sysconfdir +datadir +datarootdir +libexecdir +sbindir +bindir +program_transform_name +prefix +exec_prefix +PACKAGE_BUGREPORT +PACKAGE_STRING +PACKAGE_VERSION +PACKAGE_TARNAME +PACKAGE_NAME +PATH_SEPARATOR +SHELL' +ac_subst_files='' +ac_user_opts=' +enable_option_checking +enable_dependency_tracking +enable_largefile +enable_gpgme +with_gpgme_prefix +enable_pgp +enable_smime +with_mixmaster +with_slang +with_curses +with_regex +with_homespool +with_mailpath +enable_external_dotlock +with_docdir +with_domain +enable_pop +enable_imap +enable_smtp +with_gss +with_ssl +with_gnutls +with_sasl +enable_debug +enable_flock +enable_fcntl +enable_warnings +enable_nfs_fix +enable_mailtool +enable_locales_fix +with_exec_shell +enable_exact_address +enable_hcache +with_tokyocabinet +with_qdbm +with_gdbm +with_bdb +enable_iconv +with_libiconv_prefix +enable_nls +with_included_gettext +with_idn +with_wc_funcs +enable_full_doc +' + ac_precious_vars='build_alias host_alias target_alias -INSTALL_PROGRAM -INSTALL_SCRIPT -INSTALL_DATA -am__isrc -CYGPATH_W -PACKAGE -VERSION -ACLOCAL -AUTOCONF -AUTOMAKE -AUTOHEADER -MAKEINFO -install_sh -STRIP -INSTALL_STRIP_PROGRAM -mkdir_p -AWK -SET_MAKE -am__leading_dot -AMTAR -am__tar -am__untar -CONFIG_STATUS_DEPENDENCIES -build -build_cpu -build_vendor -build_os -host -host_cpu -host_vendor -host_os CC CFLAGS LDFLAGS -CPPFLAGS -ac_ct_CC -EXEEXT -OBJEXT -DEPDIR -am__include -am__quote -AMDEP_TRUE -AMDEP_FALSE -AMDEPBACKSLASH -CCDEPMODE -am__fastdepCC_TRUE -am__fastdepCC_FALSE -CPP -GREP -EGREP -U -ANSI2KNR -RANLIB -AR -DBX -GDB -SDB -DEBUGGER -SENDMAIL -GPGME_CONFIG -GPGME_CFLAGS -GPGME_LIBS -OPS -PGPAUX_TARGET -SMIMEAUX_TARGET -ISPELL -LIBOBJS -DOTLOCK_TARGET -DOTLOCK_GROUP -DOTLOCK_PERMISSION -BUILD_IMAP_TRUE -BUILD_IMAP_FALSE -KRB5CFGPATH -USE_GSS_TRUE -USE_GSS_FALSE -LIBGNUTLS_CONFIG -LIBGNUTLS_CFLAGS -LIBGNUTLS_LIBS -USE_SSL_TRUE -USE_SSL_FALSE -USE_SASL_TRUE -USE_SASL_FALSE -MUTT_MD5 -MUTTLIBS -MUTT_LIB_OBJECTS -LIBIMAP -LIBIMAPDEPS -ALLOCA -GLIBC21 -LIBICONV -USE_NLS -MSGFMT -GMSGFMT -XGETTEXT -INTLBISON -BUILD_INCLUDED_LIBINTL -USE_INCLUDED_LIBINTL -CATALOGS -CATOBJEXT -GMOFILES -INTLLIBS -INTLOBJS -POFILES -POSUB -DATADIRNAME -INSTOBJEXT -GENCAT -MKINSTALLDIRS -INTL_LIBTOOL_SUFFIX_PREFIX -OSPCAT -DSLROOT -LTLIBOBJS' -ac_subst_files='' - ac_precious_vars='build_alias -host_alias -target_alias -CC -CFLAGS -LDFLAGS -LIBS +LIBS CPPFLAGS CPP' @@ -777,6 +845,8 @@ CPP' # Initialize some variables set by options. ac_init_help= ac_init_version=false +ac_unrecognized_opts= +ac_unrecognized_sep= # The variables have the same names as the options, with # dashes changed to underlines. cache_file=/dev/null @@ -875,13 +945,21 @@ do datarootdir=$ac_optarg ;; -disable-* | --disable-*) - ac_feature=`expr "x$ac_option" : 'x-*disable-\(.*\)'` + ac_useropt=`expr "x$ac_option" : 'x-*disable-\(.*\)'` # Reject names that are not valid shell variable names. - expr "x$ac_feature" : ".*[^-._$as_cr_alnum]" >/dev/null && - { echo "$as_me: error: invalid feature name: $ac_feature" >&2 + expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null && + { $as_echo "$as_me: error: invalid feature name: $ac_useropt" >&2 { (exit 1); exit 1; }; } - ac_feature=`echo $ac_feature | sed 's/[-.]/_/g'` - eval enable_$ac_feature=no ;; + ac_useropt_orig=$ac_useropt + ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'` + case $ac_user_opts in + *" +"enable_$ac_useropt" +"*) ;; + *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--disable-$ac_useropt_orig" + ac_unrecognized_sep=', ';; + esac + eval enable_$ac_useropt=no ;; -docdir | --docdir | --docdi | --doc | --do) ac_prev=docdir ;; @@ -894,13 +972,21 @@ do dvidir=$ac_optarg ;; -enable-* | --enable-*) - ac_feature=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'` + ac_useropt=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'` # Reject names that are not valid shell variable names. - expr "x$ac_feature" : ".*[^-._$as_cr_alnum]" >/dev/null && - { echo "$as_me: error: invalid feature name: $ac_feature" >&2 + expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null && + { $as_echo "$as_me: error: invalid feature name: $ac_useropt" >&2 { (exit 1); exit 1; }; } - ac_feature=`echo $ac_feature | sed 's/[-.]/_/g'` - eval enable_$ac_feature=\$ac_optarg ;; + ac_useropt_orig=$ac_useropt + ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'` + case $ac_user_opts in + *" +"enable_$ac_useropt" +"*) ;; + *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--enable-$ac_useropt_orig" + ac_unrecognized_sep=', ';; + esac + eval enable_$ac_useropt=\$ac_optarg ;; -exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi \ | --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- \ @@ -1091,22 +1177,38 @@ do ac_init_version=: ;; -with-* | --with-*) - ac_package=`expr "x$ac_option" : 'x-*with-\([^=]*\)'` + ac_useropt=`expr "x$ac_option" : 'x-*with-\([^=]*\)'` # Reject names that are not valid shell variable names. - expr "x$ac_package" : ".*[^-._$as_cr_alnum]" >/dev/null && - { echo "$as_me: error: invalid package name: $ac_package" >&2 + expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null && + { $as_echo "$as_me: error: invalid package name: $ac_useropt" >&2 { (exit 1); exit 1; }; } - ac_package=`echo $ac_package | sed 's/[-.]/_/g'` - eval with_$ac_package=\$ac_optarg ;; + ac_useropt_orig=$ac_useropt + ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'` + case $ac_user_opts in + *" +"with_$ac_useropt" +"*) ;; + *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--with-$ac_useropt_orig" + ac_unrecognized_sep=', ';; + esac + eval with_$ac_useropt=\$ac_optarg ;; -without-* | --without-*) - ac_package=`expr "x$ac_option" : 'x-*without-\(.*\)'` + ac_useropt=`expr "x$ac_option" : 'x-*without-\(.*\)'` # Reject names that are not valid shell variable names. - expr "x$ac_package" : ".*[^-._$as_cr_alnum]" >/dev/null && - { echo "$as_me: error: invalid package name: $ac_package" >&2 + expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null && + { $as_echo "$as_me: error: invalid package name: $ac_useropt" >&2 { (exit 1); exit 1; }; } - ac_package=`echo $ac_package | sed 's/[-.]/_/g'` - eval with_$ac_package=no ;; + ac_useropt_orig=$ac_useropt + ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'` + case $ac_user_opts in + *" +"with_$ac_useropt" +"*) ;; + *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--without-$ac_useropt_orig" + ac_unrecognized_sep=', ';; + esac + eval with_$ac_useropt=no ;; --x) # Obsolete; use --with-x. @@ -1126,7 +1228,7 @@ do | --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*) x_libraries=$ac_optarg ;; - -*) { echo "$as_me: error: unrecognized option: $ac_option + -*) { $as_echo "$as_me: error: unrecognized option: $ac_option Try \`$0 --help' for more information." >&2 { (exit 1); exit 1; }; } ;; @@ -1135,16 +1237,16 @@ Try \`$0 --help' for more information." >&2 ac_envvar=`expr "x$ac_option" : 'x\([^=]*\)='` # Reject names that are not valid shell variable names. expr "x$ac_envvar" : ".*[^_$as_cr_alnum]" >/dev/null && - { echo "$as_me: error: invalid variable name: $ac_envvar" >&2 + { $as_echo "$as_me: error: invalid variable name: $ac_envvar" >&2 { (exit 1); exit 1; }; } eval $ac_envvar=\$ac_optarg export $ac_envvar ;; *) # FIXME: should be removed in autoconf 3.0. - echo "$as_me: WARNING: you should use --build, --host, --target" >&2 + $as_echo "$as_me: WARNING: you should use --build, --host, --target" >&2 expr "x$ac_option" : ".*[^-._$as_cr_alnum]" >/dev/null && - echo "$as_me: WARNING: invalid host type: $ac_option" >&2 + $as_echo "$as_me: WARNING: invalid host type: $ac_option" >&2 : ${build_alias=$ac_option} ${host_alias=$ac_option} ${target_alias=$ac_option} ;; @@ -1153,22 +1255,38 @@ done if test -n "$ac_prev"; then ac_option=--`echo $ac_prev | sed 's/_/-/g'` - { echo "$as_me: error: missing argument to $ac_option" >&2 + { $as_echo "$as_me: error: missing argument to $ac_option" >&2 { (exit 1); exit 1; }; } fi -# Be sure to have absolute directory names. +if test -n "$ac_unrecognized_opts"; then + case $enable_option_checking in + no) ;; + fatal) { $as_echo "$as_me: error: unrecognized options: $ac_unrecognized_opts" >&2 + { (exit 1); exit 1; }; } ;; + *) $as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2 ;; + esac +fi + +# Check all directory arguments for consistency. for ac_var in exec_prefix prefix bindir sbindir libexecdir datarootdir \ datadir sysconfdir sharedstatedir localstatedir includedir \ oldincludedir docdir infodir htmldir dvidir pdfdir psdir \ libdir localedir mandir do eval ac_val=\$$ac_var + # Remove trailing slashes. + case $ac_val in + */ ) + ac_val=`expr "X$ac_val" : 'X\(.*[^/]\)' \| "X$ac_val" : 'X\(.*\)'` + eval $ac_var=\$ac_val;; + esac + # Be sure to have absolute directory names. case $ac_val in [\\/$]* | ?:[\\/]* ) continue;; NONE | '' ) case $ac_var in *prefix ) continue;; esac;; esac - { echo "$as_me: error: expected an absolute directory name for --$ac_var: $ac_val" >&2 + { $as_echo "$as_me: error: expected an absolute directory name for --$ac_var: $ac_val" >&2 { (exit 1); exit 1; }; } done @@ -1183,7 +1301,7 @@ target=$target_alias if test "x$host_alias" != x; then if test "x$build_alias" = x; then cross_compiling=maybe - echo "$as_me: WARNING: If you wanted to set the --build type, don't use --host. + $as_echo "$as_me: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used." >&2 elif test "x$build_alias" != "x$host_alias"; then cross_compiling=yes @@ -1199,10 +1317,10 @@ test "$silent" = yes && exec 6>/dev/null ac_pwd=`pwd` && test -n "$ac_pwd" && ac_ls_di=`ls -di .` && ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` || - { echo "$as_me: error: Working directory cannot be determined" >&2 + { $as_echo "$as_me: error: working directory cannot be determined" >&2 { (exit 1); exit 1; }; } test "X$ac_ls_di" = "X$ac_pwd_ls_di" || - { echo "$as_me: error: pwd does not report name of working directory" >&2 + { $as_echo "$as_me: error: pwd does not report name of working directory" >&2 { (exit 1); exit 1; }; } @@ -1210,12 +1328,12 @@ test "X$ac_ls_di" = "X$ac_pwd_ls_di" || if test -z "$srcdir"; then ac_srcdir_defaulted=yes # Try the directory containing this script, then the parent directory. - ac_confdir=`$as_dirname -- "$0" || -$as_expr X"$0" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ - X"$0" : 'X\(//\)[^/]' \| \ - X"$0" : 'X\(//\)$' \| \ - X"$0" : 'X\(/\)' \| . 2>/dev/null || -echo X"$0" | + ac_confdir=`$as_dirname -- "$as_myself" || +$as_expr X"$as_myself" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$as_myself" : 'X\(//\)[^/]' \| \ + X"$as_myself" : 'X\(//\)$' \| \ + X"$as_myself" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$as_myself" | sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/ q @@ -1242,12 +1360,12 @@ else fi if test ! -r "$srcdir/$ac_unique_file"; then test "$ac_srcdir_defaulted" = yes && srcdir="$ac_confdir or .." - { echo "$as_me: error: cannot find sources ($ac_unique_file) in $srcdir" >&2 + { $as_echo "$as_me: error: cannot find sources ($ac_unique_file) in $srcdir" >&2 { (exit 1); exit 1; }; } fi ac_msg="sources are in $srcdir, but \`cd $srcdir' does not work" ac_abs_confdir=`( - cd "$srcdir" && test -r "./$ac_unique_file" || { echo "$as_me: error: $ac_msg" >&2 + cd "$srcdir" && test -r "./$ac_unique_file" || { $as_echo "$as_me: error: $ac_msg" >&2 { (exit 1); exit 1; }; } pwd)` # When building in place, set srcdir=. @@ -1296,9 +1414,9 @@ Configuration: Installation directories: --prefix=PREFIX install architecture-independent files in PREFIX - [$ac_default_prefix] + [$ac_default_prefix] --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX - [PREFIX] + [PREFIX] By default, \`make install' will install all the files in \`$ac_default_prefix/bin', \`$ac_default_prefix/lib' etc. You can specify @@ -1308,25 +1426,25 @@ for instance \`--prefix=\$HOME'. For better control, use the options below. Fine tuning of the installation directories: - --bindir=DIR user executables [EPREFIX/bin] - --sbindir=DIR system admin executables [EPREFIX/sbin] - --libexecdir=DIR program executables [EPREFIX/libexec] - --sysconfdir=DIR read-only single-machine data [PREFIX/etc] - --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] - --localstatedir=DIR modifiable single-machine data [PREFIX/var] - --libdir=DIR object code libraries [EPREFIX/lib] - --includedir=DIR C header files [PREFIX/include] - --oldincludedir=DIR C header files for non-gcc [/usr/include] - --datarootdir=DIR read-only arch.-independent data root [PREFIX/share] - --datadir=DIR read-only architecture-independent data [DATAROOTDIR] - --infodir=DIR info documentation [DATAROOTDIR/info] - --localedir=DIR locale-dependent data [DATAROOTDIR/locale] - --mandir=DIR man documentation [DATAROOTDIR/man] - --docdir=DIR documentation root [DATAROOTDIR/doc/PACKAGE] - --htmldir=DIR html documentation [DOCDIR] - --dvidir=DIR dvi documentation [DOCDIR] - --pdfdir=DIR pdf documentation [DOCDIR] - --psdir=DIR ps documentation [DOCDIR] + --bindir=DIR user executables [EPREFIX/bin] + --sbindir=DIR system admin executables [EPREFIX/sbin] + --libexecdir=DIR program executables [EPREFIX/libexec] + --sysconfdir=DIR read-only single-machine data [PREFIX/etc] + --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] + --localstatedir=DIR modifiable single-machine data [PREFIX/var] + --libdir=DIR object code libraries [EPREFIX/lib] + --includedir=DIR C header files [PREFIX/include] + --oldincludedir=DIR C header files for non-gcc [/usr/include] + --datarootdir=DIR read-only arch.-independent data root [PREFIX/share] + --datadir=DIR read-only architecture-independent data [DATAROOTDIR] + --infodir=DIR info documentation [DATAROOTDIR/info] + --localedir=DIR locale-dependent data [DATAROOTDIR/locale] + --mandir=DIR man documentation [DATAROOTDIR/man] + --docdir=DIR documentation root [DATAROOTDIR/doc/PACKAGE] + --htmldir=DIR html documentation [DOCDIR] + --dvidir=DIR dvi documentation [DOCDIR] + --pdfdir=DIR pdf documentation [DOCDIR] + --psdir=DIR ps documentation [DOCDIR] _ACEOF cat <<\_ACEOF @@ -1347,6 +1465,7 @@ if test -n "$ac_init_help"; then cat <<\_ACEOF Optional Features: + --disable-option-checking ignore unrecognized --enable/--with options --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no) --enable-FEATURE[=ARG] include FEATURE [ARG=yes] --disable-dependency-tracking speeds up one-time build @@ -1386,10 +1505,8 @@ Optional Packages: --with-docdir=PATH Specify where to put the documentation --with-domain=DOMAIN Specify your DNS domain name --with-gss[=PFX] Compile in GSSAPI authentication for IMAP - --with-ssl[=PFX] Compile in SSL support for POP/IMAP/SMTP using - OpenSSL - --with-gnutls[=PFX] Compile in SSL support for POP/IMAP/SMTP using - gnutls + --with-ssl[=PFX] Enable TLS support using OpenSSL + --with-gnutls[=PFX] enable TLS support using gnutls --with-sasl[=PFX] Use Cyrus SASL 2 network security library --with-exec-shell=SHELL Specify alternate shell (ONLY if /bin/sh is broken) --without-tokyocabinet Don't use tokyocabinet even if it is available @@ -1422,15 +1539,17 @@ fi if test "$ac_init_help" = "recursive"; then # If there are subdirs, report their specific --help. for ac_dir in : $ac_subdirs_all; do test "x$ac_dir" = x: && continue - test -d "$ac_dir" || continue + test -d "$ac_dir" || + { cd "$srcdir" && ac_pwd=`pwd` && srcdir=. && test -d "$ac_dir"; } || + continue ac_builddir=. case "$ac_dir" in .) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;; *) - ac_dir_suffix=/`echo "$ac_dir" | sed 's,^\.[\\/],,'` + ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'` # A ".." for each directory in $ac_dir_suffix. - ac_top_builddir_sub=`echo "$ac_dir_suffix" | sed 's,/[^\\/]*,/..,g;s,/,,'` + ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'` case $ac_top_builddir_sub in "") ac_top_builddir_sub=. ac_top_build_prefix= ;; *) ac_top_build_prefix=$ac_top_builddir_sub/ ;; @@ -1466,7 +1585,7 @@ ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix echo && $SHELL "$ac_srcdir/configure" --help=recursive else - echo "$as_me: WARNING: no configuration information is in $ac_dir" >&2 + $as_echo "$as_me: WARNING: no configuration information is in $ac_dir" >&2 fi || ac_status=$? cd "$ac_pwd" || { ac_status=$?; break; } done @@ -1476,10 +1595,10 @@ test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF configure -generated by GNU Autoconf 2.61 +generated by GNU Autoconf 2.63 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, -2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc. +2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. This configure script is free software; the Free Software Foundation gives unlimited permission to copy, distribute and modify it. _ACEOF @@ -1490,7 +1609,7 @@ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by $as_me, which was -generated by GNU Autoconf 2.61. Invocation command line was +generated by GNU Autoconf 2.63. Invocation command line was $ $0 $@ @@ -1526,7 +1645,7 @@ for as_dir in $PATH do IFS=$as_save_IFS test -z "$as_dir" && as_dir=. - echo "PATH: $as_dir" + $as_echo "PATH: $as_dir" done IFS=$as_save_IFS @@ -1561,7 +1680,7 @@ do | -silent | --silent | --silen | --sile | --sil) continue ;; *\'*) - ac_arg=`echo "$ac_arg" | sed "s/'/'\\\\\\\\''/g"` ;; + ac_arg=`$as_echo "$ac_arg" | sed "s/'/'\\\\\\\\''/g"` ;; esac case $ac_pass in 1) ac_configure_args0="$ac_configure_args0 '$ac_arg'" ;; @@ -1613,11 +1732,12 @@ _ASBOX case $ac_val in #( *${as_nl}*) case $ac_var in #( - *_cv_*) { echo "$as_me:$LINENO: WARNING: Cache variable $ac_var contains a newline." >&5 -echo "$as_me: WARNING: Cache variable $ac_var contains a newline." >&2;} ;; + *_cv_*) { $as_echo "$as_me:$LINENO: WARNING: cache variable $ac_var contains a newline" >&5 +$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;; esac case $ac_var in #( _ | IFS | as_nl) ;; #( + BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #( *) $as_unset $ac_var ;; esac ;; esac @@ -1647,9 +1767,9 @@ _ASBOX do eval ac_val=\$$ac_var case $ac_val in - *\'\''*) ac_val=`echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;; + *\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;; esac - echo "$ac_var='\''$ac_val'\''" + $as_echo "$ac_var='\''$ac_val'\''" done | sort echo @@ -1664,9 +1784,9 @@ _ASBOX do eval ac_val=\$$ac_var case $ac_val in - *\'\''*) ac_val=`echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;; + *\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;; esac - echo "$ac_var='\''$ac_val'\''" + $as_echo "$ac_var='\''$ac_val'\''" done | sort echo fi @@ -1682,8 +1802,8 @@ _ASBOX echo fi test "$ac_signal" != 0 && - echo "$as_me: caught signal $ac_signal" - echo "$as_me: exit $exit_status" + $as_echo "$as_me: caught signal $ac_signal" + $as_echo "$as_me: exit $exit_status" } >&5 rm -f core *.core core.conftest.* && rm -f -r conftest* confdefs* conf$$* $ac_clean_files && @@ -1725,21 +1845,24 @@ _ACEOF # Let the site file select an alternate cache file if it wants to. -# Prefer explicitly selected file to automatically selected ones. +# Prefer an explicitly selected file to automatically selected ones. +ac_site_file1=NONE +ac_site_file2=NONE if test -n "$CONFIG_SITE"; then - set x "$CONFIG_SITE" + ac_site_file1=$CONFIG_SITE elif test "x$prefix" != xNONE; then - set x "$prefix/share/config.site" "$prefix/etc/config.site" + ac_site_file1=$prefix/share/config.site + ac_site_file2=$prefix/etc/config.site else - set x "$ac_default_prefix/share/config.site" \ - "$ac_default_prefix/etc/config.site" + ac_site_file1=$ac_default_prefix/share/config.site + ac_site_file2=$ac_default_prefix/etc/config.site fi -shift -for ac_site_file +for ac_site_file in "$ac_site_file1" "$ac_site_file2" do + test "x$ac_site_file" = xNONE && continue if test -r "$ac_site_file"; then - { echo "$as_me:$LINENO: loading site script $ac_site_file" >&5 -echo "$as_me: loading site script $ac_site_file" >&6;} + { $as_echo "$as_me:$LINENO: loading site script $ac_site_file" >&5 +$as_echo "$as_me: loading site script $ac_site_file" >&6;} sed 's/^/| /' "$ac_site_file" >&5 . "$ac_site_file" fi @@ -1749,16 +1872,16 @@ if test -r "$cache_file"; then # Some versions of bash will fail to source /dev/null (special # files actually), so we avoid doing that. if test -f "$cache_file"; then - { echo "$as_me:$LINENO: loading cache $cache_file" >&5 -echo "$as_me: loading cache $cache_file" >&6;} + { $as_echo "$as_me:$LINENO: loading cache $cache_file" >&5 +$as_echo "$as_me: loading cache $cache_file" >&6;} case $cache_file in [\\/]* | ?:[\\/]* ) . "$cache_file";; *) . "./$cache_file";; esac fi else - { echo "$as_me:$LINENO: creating cache $cache_file" >&5 -echo "$as_me: creating cache $cache_file" >&6;} + { $as_echo "$as_me:$LINENO: creating cache $cache_file" >&5 +$as_echo "$as_me: creating cache $cache_file" >&6;} >$cache_file fi @@ -1772,29 +1895,38 @@ for ac_var in $ac_precious_vars; do eval ac_new_val=\$ac_env_${ac_var}_value case $ac_old_set,$ac_new_set in set,) - { echo "$as_me:$LINENO: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5 -echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;} + { $as_echo "$as_me:$LINENO: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5 +$as_echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;} ac_cache_corrupted=: ;; ,set) - { echo "$as_me:$LINENO: error: \`$ac_var' was not set in the previous run" >&5 -echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;} + { $as_echo "$as_me:$LINENO: error: \`$ac_var' was not set in the previous run" >&5 +$as_echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;} ac_cache_corrupted=: ;; ,);; *) if test "x$ac_old_val" != "x$ac_new_val"; then - { echo "$as_me:$LINENO: error: \`$ac_var' has changed since the previous run:" >&5 -echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;} - { echo "$as_me:$LINENO: former value: $ac_old_val" >&5 -echo "$as_me: former value: $ac_old_val" >&2;} - { echo "$as_me:$LINENO: current value: $ac_new_val" >&5 -echo "$as_me: current value: $ac_new_val" >&2;} - ac_cache_corrupted=: + # differences in whitespace do not lead to failure. + ac_old_val_w=`echo x $ac_old_val` + ac_new_val_w=`echo x $ac_new_val` + if test "$ac_old_val_w" != "$ac_new_val_w"; then + { $as_echo "$as_me:$LINENO: error: \`$ac_var' has changed since the previous run:" >&5 +$as_echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;} + ac_cache_corrupted=: + else + { $as_echo "$as_me:$LINENO: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&5 +$as_echo "$as_me: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&2;} + eval $ac_var=\$ac_old_val + fi + { $as_echo "$as_me:$LINENO: former value: \`$ac_old_val'" >&5 +$as_echo "$as_me: former value: \`$ac_old_val'" >&2;} + { $as_echo "$as_me:$LINENO: current value: \`$ac_new_val'" >&5 +$as_echo "$as_me: current value: \`$ac_new_val'" >&2;} fi;; esac # Pass precious variables to config.status. if test "$ac_new_set" = set; then case $ac_new_val in - *\'*) ac_arg=$ac_var=`echo "$ac_new_val" | sed "s/'/'\\\\\\\\''/g"` ;; + *\'*) ac_arg=$ac_var=`$as_echo "$ac_new_val" | sed "s/'/'\\\\\\\\''/g"` ;; *) ac_arg=$ac_var=$ac_new_val ;; esac case " $ac_configure_args " in @@ -1804,10 +1936,12 @@ echo "$as_me: current value: $ac_new_val" >&2;} fi done if $ac_cache_corrupted; then - { echo "$as_me:$LINENO: error: changes in the environment can compromise the build" >&5 -echo "$as_me: error: changes in the environment can compromise the build" >&2;} - { { echo "$as_me:$LINENO: error: run \`make distclean' and/or \`rm $cache_file' and start over" >&5 -echo "$as_me: error: run \`make distclean' and/or \`rm $cache_file' and start over" >&2;} + { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} + { $as_echo "$as_me:$LINENO: error: changes in the environment can compromise the build" >&5 +$as_echo "$as_me: error: changes in the environment can compromise the build" >&2;} + { { $as_echo "$as_me:$LINENO: error: run \`make distclean' and/or \`rm $cache_file' and start over" >&5 +$as_echo "$as_me: error: run \`make distclean' and/or \`rm $cache_file' and start over" >&2;} { (exit 1); exit 1; }; } fi @@ -1838,7 +1972,7 @@ ac_config_headers="$ac_config_headers config.h" mutt_cv_version=`cat $srcdir/VERSION` -am__api_version='1.10' +am__api_version='1.11' ac_aux_dir= for ac_dir in "$srcdir" "$srcdir/.." "$srcdir/../.."; do @@ -1857,8 +1991,8 @@ for ac_dir in "$srcdir" "$srcdir/.." "$srcdir/../.."; do fi done if test -z "$ac_aux_dir"; then - { { echo "$as_me:$LINENO: error: cannot find install-sh or install.sh in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" >&5 -echo "$as_me: error: cannot find install-sh or install.sh in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" >&2;} + { { $as_echo "$as_me:$LINENO: error: cannot find install-sh or install.sh in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" >&5 +$as_echo "$as_me: error: cannot find install-sh or install.sh in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" >&2;} { (exit 1); exit 1; }; } fi @@ -1884,11 +2018,12 @@ ac_configure="$SHELL $ac_aux_dir/configure" # Please don't use this var. # SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff" # OS/2's system install, which has a completely different semantic # ./install, which can be erroneously created by make from ./install.sh. -{ echo "$as_me:$LINENO: checking for a BSD-compatible install" >&5 -echo $ECHO_N "checking for a BSD-compatible install... $ECHO_C" >&6; } +# Reject install programs that cannot install multiple files. +{ $as_echo "$as_me:$LINENO: checking for a BSD-compatible install" >&5 +$as_echo_n "checking for a BSD-compatible install... " >&6; } if test -z "$INSTALL"; then if test "${ac_cv_path_install+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else as_save_IFS=$IFS; IFS=$PATH_SEPARATOR for as_dir in $PATH @@ -1917,17 +2052,29 @@ case $as_dir/ in # program-specific install script used by HP pwplus--don't use. : else - ac_cv_path_install="$as_dir/$ac_prog$ac_exec_ext -c" - break 3 + rm -rf conftest.one conftest.two conftest.dir + echo one > conftest.one + echo two > conftest.two + mkdir conftest.dir + if "$as_dir/$ac_prog$ac_exec_ext" -c conftest.one conftest.two "`pwd`/conftest.dir" && + test -s conftest.one && test -s conftest.two && + test -s conftest.dir/conftest.one && + test -s conftest.dir/conftest.two + then + ac_cv_path_install="$as_dir/$ac_prog$ac_exec_ext -c" + break 3 + fi fi fi done done ;; esac + done IFS=$as_save_IFS +rm -rf conftest.one conftest.two conftest.dir fi if test "${ac_cv_path_install+set}" = set; then @@ -1940,8 +2087,8 @@ fi INSTALL=$ac_install_sh fi fi -{ echo "$as_me:$LINENO: result: $INSTALL" >&5 -echo "${ECHO_T}$INSTALL" >&6; } +{ $as_echo "$as_me:$LINENO: result: $INSTALL" >&5 +$as_echo "$INSTALL" >&6; } # Use test -z because SunOS4 sh mishandles braces in ${var-val}. # It thinks the first close brace ends the variable substitution. @@ -1951,21 +2098,38 @@ test -z "$INSTALL_SCRIPT" && INSTALL_SCRIPT='${INSTALL}' test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644' -{ echo "$as_me:$LINENO: checking whether build environment is sane" >&5 -echo $ECHO_N "checking whether build environment is sane... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether build environment is sane" >&5 +$as_echo_n "checking whether build environment is sane... " >&6; } # Just in case sleep 1 echo timestamp > conftest.file +# Reject unsafe characters in $srcdir or the absolute working directory +# name. Accept space and tab only in the latter. +am_lf=' +' +case `pwd` in + *[\\\"\#\$\&\'\`$am_lf]*) + { { $as_echo "$as_me:$LINENO: error: unsafe absolute working directory name" >&5 +$as_echo "$as_me: error: unsafe absolute working directory name" >&2;} + { (exit 1); exit 1; }; };; +esac +case $srcdir in + *[\\\"\#\$\&\'\`$am_lf\ \ ]*) + { { $as_echo "$as_me:$LINENO: error: unsafe srcdir value: \`$srcdir'" >&5 +$as_echo "$as_me: error: unsafe srcdir value: \`$srcdir'" >&2;} + { (exit 1); exit 1; }; };; +esac + # Do `set' in a subshell so we don't clobber the current shell's # arguments. Must try -L first in case configure is actually a # symlink; some systems play weird games with the mod time of symlinks # (eg FreeBSD returns the mod time of the symlink's containing # directory). if ( - set X `ls -Lt $srcdir/configure conftest.file 2> /dev/null` + set X `ls -Lt "$srcdir/configure" conftest.file 2> /dev/null` if test "$*" = "X"; then # -L didn't work. - set X `ls -t $srcdir/configure conftest.file` + set X `ls -t "$srcdir/configure" conftest.file` fi rm -f conftest.file if test "$*" != "X $srcdir/configure conftest.file" \ @@ -1975,9 +2139,9 @@ if ( # if, for instance, CONFIG_SHELL is bash and it inherits a # broken ls alias from the environment. This has actually # happened. Such a system could not be considered "sane". - { { echo "$as_me:$LINENO: error: ls -t appears to fail. Make sure there is not a broken + { { $as_echo "$as_me:$LINENO: error: ls -t appears to fail. Make sure there is not a broken alias in your environment" >&5 -echo "$as_me: error: ls -t appears to fail. Make sure there is not a broken +$as_echo "$as_me: error: ls -t appears to fail. Make sure there is not a broken alias in your environment" >&2;} { (exit 1); exit 1; }; } fi @@ -1988,45 +2152,158 @@ then # Ok. : else - { { echo "$as_me:$LINENO: error: newly created file is older than distributed files! + { { $as_echo "$as_me:$LINENO: error: newly created file is older than distributed files! Check your system clock" >&5 -echo "$as_me: error: newly created file is older than distributed files! +$as_echo "$as_me: error: newly created file is older than distributed files! Check your system clock" >&2;} { (exit 1); exit 1; }; } fi -{ echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } +{ $as_echo "$as_me:$LINENO: result: yes" >&5 +$as_echo "yes" >&6; } test "$program_prefix" != NONE && program_transform_name="s&^&$program_prefix&;$program_transform_name" # Use a double $ so make ignores it. test "$program_suffix" != NONE && program_transform_name="s&\$&$program_suffix&;$program_transform_name" -# Double any \ or $. echo might interpret backslashes. +# Double any \ or $. # By default was `s,x,x', remove it if useless. -cat <<\_ACEOF >conftest.sed -s/[\\$]/&&/g;s/;s,x,x,$// -_ACEOF -program_transform_name=`echo $program_transform_name | sed -f conftest.sed` -rm -f conftest.sed +ac_script='s/[\\$]/&&/g;s/;s,x,x,$//' +program_transform_name=`$as_echo "$program_transform_name" | sed "$ac_script"` # expand $ac_aux_dir to an absolute path am_aux_dir=`cd $ac_aux_dir && pwd` -test x"${MISSING+set}" = xset || MISSING="\${SHELL} $am_aux_dir/missing" +if test x"${MISSING+set}" != xset; then + case $am_aux_dir in + *\ * | *\ *) + MISSING="\${SHELL} \"$am_aux_dir/missing\"" ;; + *) + MISSING="\${SHELL} $am_aux_dir/missing" ;; + esac +fi # Use eval to expand $SHELL if eval "$MISSING --run true"; then am_missing_run="$MISSING --run " else am_missing_run= - { echo "$as_me:$LINENO: WARNING: \`missing' script is too old or missing" >&5 -echo "$as_me: WARNING: \`missing' script is too old or missing" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: \`missing' script is too old or missing" >&5 +$as_echo "$as_me: WARNING: \`missing' script is too old or missing" >&2;} +fi + +if test x"${install_sh}" != xset; then + case $am_aux_dir in + *\ * | *\ *) + install_sh="\${SHELL} '$am_aux_dir/install-sh'" ;; + *) + install_sh="\${SHELL} $am_aux_dir/install-sh" + esac +fi + +# Installed binaries are usually stripped using `strip' when the user +# run `make install-strip'. However `strip' might not be the right +# tool to use in cross-compilation environments, therefore Automake +# will honor the `STRIP' environment variable to overrule this program. +if test "$cross_compiling" != no; then + if test -n "$ac_tool_prefix"; then + # Extract the first word of "${ac_tool_prefix}strip", so it can be a program name with args. +set dummy ${ac_tool_prefix}strip; ac_word=$2 +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if test "${ac_cv_prog_STRIP+set}" = set; then + $as_echo_n "(cached) " >&6 +else + if test -n "$STRIP"; then + ac_cv_prog_STRIP="$STRIP" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then + ac_cv_prog_STRIP="${ac_tool_prefix}strip" + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done +done +IFS=$as_save_IFS + +fi +fi +STRIP=$ac_cv_prog_STRIP +if test -n "$STRIP"; then + { $as_echo "$as_me:$LINENO: result: $STRIP" >&5 +$as_echo "$STRIP" >&6; } +else + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } +fi + + +fi +if test -z "$ac_cv_prog_STRIP"; then + ac_ct_STRIP=$STRIP + # Extract the first word of "strip", so it can be a program name with args. +set dummy strip; ac_word=$2 +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if test "${ac_cv_prog_ac_ct_STRIP+set}" = set; then + $as_echo_n "(cached) " >&6 +else + if test -n "$ac_ct_STRIP"; then + ac_cv_prog_ac_ct_STRIP="$ac_ct_STRIP" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then + ac_cv_prog_ac_ct_STRIP="strip" + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done +done +IFS=$as_save_IFS + +fi +fi +ac_ct_STRIP=$ac_cv_prog_ac_ct_STRIP +if test -n "$ac_ct_STRIP"; then + { $as_echo "$as_me:$LINENO: result: $ac_ct_STRIP" >&5 +$as_echo "$ac_ct_STRIP" >&6; } +else + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } +fi + + if test "x$ac_ct_STRIP" = x; then + STRIP=":" + else + case $cross_compiling:$ac_tool_warned in +yes:) +{ $as_echo "$as_me:$LINENO: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} +ac_tool_warned=yes ;; +esac + STRIP=$ac_ct_STRIP + fi +else + STRIP="$ac_cv_prog_STRIP" +fi + fi +INSTALL_STRIP_PROGRAM="\$(install_sh) -c -s" -{ echo "$as_me:$LINENO: checking for a thread-safe mkdir -p" >&5 -echo $ECHO_N "checking for a thread-safe mkdir -p... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for a thread-safe mkdir -p" >&5 +$as_echo_n "checking for a thread-safe mkdir -p... " >&6; } if test -z "$MKDIR_P"; then if test "${ac_cv_path_mkdir+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else as_save_IFS=$IFS; IFS=$PATH_SEPARATOR for as_dir in $PATH$PATH_SEPARATOR/opt/sfw/bin @@ -2061,8 +2338,8 @@ fi MKDIR_P="$ac_install_sh -d" fi fi -{ echo "$as_me:$LINENO: result: $MKDIR_P" >&5 -echo "${ECHO_T}$MKDIR_P" >&6; } +{ $as_echo "$as_me:$LINENO: result: $MKDIR_P" >&5 +$as_echo "$MKDIR_P" >&6; } mkdir_p="$MKDIR_P" case $mkdir_p in @@ -2074,10 +2351,10 @@ for ac_prog in gawk mawk nawk awk do # Extract the first word of "$ac_prog", so it can be a program name with args. set dummy $ac_prog; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_prog_AWK+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test -n "$AWK"; then ac_cv_prog_AWK="$AWK" # Let the user override the test. @@ -2090,7 +2367,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_prog_AWK="$ac_prog" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -2101,22 +2378,23 @@ fi fi AWK=$ac_cv_prog_AWK if test -n "$AWK"; then - { echo "$as_me:$LINENO: result: $AWK" >&5 -echo "${ECHO_T}$AWK" >&6; } + { $as_echo "$as_me:$LINENO: result: $AWK" >&5 +$as_echo "$AWK" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi test -n "$AWK" && break done -{ echo "$as_me:$LINENO: checking whether ${MAKE-make} sets \$(MAKE)" >&5 -echo $ECHO_N "checking whether ${MAKE-make} sets \$(MAKE)... $ECHO_C" >&6; } -set x ${MAKE-make}; ac_make=`echo "$2" | sed 's/+/p/g; s/[^a-zA-Z0-9_]/_/g'` +{ $as_echo "$as_me:$LINENO: checking whether ${MAKE-make} sets \$(MAKE)" >&5 +$as_echo_n "checking whether ${MAKE-make} sets \$(MAKE)... " >&6; } +set x ${MAKE-make} +ac_make=`$as_echo "$2" | sed 's/+/p/g; s/[^a-zA-Z0-9_]/_/g'` if { as_var=ac_cv_prog_make_${ac_make}_set; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.make <<\_ACEOF SHELL = /bin/sh @@ -2133,12 +2411,12 @@ esac rm -f conftest.make fi if eval test \$ac_cv_prog_make_${ac_make}_set = yes; then - { echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } + { $as_echo "$as_me:$LINENO: result: yes" >&5 +$as_echo "yes" >&6; } SET_MAKE= else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } SET_MAKE="MAKE=${MAKE-make}" fi @@ -2157,8 +2435,8 @@ if test "`cd $srcdir && pwd`" != "`pwd`"; then am__isrc=' -I$(srcdir)' # test to see if srcdir already configured if test -f $srcdir/config.status; then - { { echo "$as_me:$LINENO: error: source directory already configured; run \"make distclean\" there first" >&5 -echo "$as_me: error: source directory already configured; run \"make distclean\" there first" >&2;} + { { $as_echo "$as_me:$LINENO: error: source directory already configured; run \"make distclean\" there first" >&5 +$as_echo "$as_me: error: source directory already configured; run \"make distclean\" there first" >&2;} { (exit 1); exit 1; }; } fi fi @@ -2203,23 +2481,98 @@ AUTOHEADER=${AUTOHEADER-"${am_missing_run}autoheader"} MAKEINFO=${MAKEINFO-"${am_missing_run}makeinfo"} -install_sh=${install_sh-"\$(SHELL) $am_aux_dir/install-sh"} +# We need awk for the "check" target. The system "awk" is bad on +# some platforms. +# Always define AMTAR for backward compatibility. -# Installed binaries are usually stripped using `strip' when the user -# run `make install-strip'. However `strip' might not be the right -# tool to use in cross-compilation environments, therefore Automake -# will honor the `STRIP' environment variable to overrule this program. -if test "$cross_compiling" != no; then - if test -n "$ac_tool_prefix"; then - # Extract the first word of "${ac_tool_prefix}strip", so it can be a program name with args. -set dummy ${ac_tool_prefix}strip; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } -if test "${ac_cv_prog_STRIP+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 +AMTAR=${AMTAR-"${am_missing_run}tar"} + +am__tar='${AMTAR} chof - "$$tardir"'; am__untar='${AMTAR} xf -' + + + + + +CONFIG_STATUS_DEPENDENCIES='$(top_srcdir)/VERSION' + + +DEPDIR="${am__leading_dot}deps" + +ac_config_commands="$ac_config_commands depfiles" + + +am_make=${MAKE-make} +cat > confinc << 'END' +am__doit: + @echo this is the am__doit target +.PHONY: am__doit +END +# If we don't find an include directive, just comment out the code. +{ $as_echo "$as_me:$LINENO: checking for style of include used by $am_make" >&5 +$as_echo_n "checking for style of include used by $am_make... " >&6; } +am__include="#" +am__quote= +_am_result=none +# First try GNU make style include. +echo "include confinc" > confmf +# Ignore all kinds of additional output from `make'. +case `$am_make -s -f confmf 2> /dev/null` in #( +*the\ am__doit\ target*) + am__include=include + am__quote= + _am_result=GNU + ;; +esac +# Now try BSD make style include. +if test "$am__include" = "#"; then + echo '.include "confinc"' > confmf + case `$am_make -s -f confmf 2> /dev/null` in #( + *the\ am__doit\ target*) + am__include=.include + am__quote="\"" + _am_result=BSD + ;; + esac +fi + + +{ $as_echo "$as_me:$LINENO: result: $_am_result" >&5 +$as_echo "$_am_result" >&6; } +rm -f confinc confmf + +# Check whether --enable-dependency-tracking was given. +if test "${enable_dependency_tracking+set}" = set; then + enableval=$enable_dependency_tracking; +fi + +if test "x$enable_dependency_tracking" != xno; then + am_depcomp="$ac_aux_dir/depcomp" + AMDEPBACKSLASH='\' +fi + if test "x$enable_dependency_tracking" != xno; then + AMDEP_TRUE= + AMDEP_FALSE='#' else - if test -n "$STRIP"; then - ac_cv_prog_STRIP="$STRIP" # Let the user override the test. + AMDEP_TRUE='#' + AMDEP_FALSE= +fi + + +ac_ext=c +ac_cpp='$CPP $CPPFLAGS' +ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' +ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' +ac_compiler_gnu=$ac_cv_c_compiler_gnu +if test -n "$ac_tool_prefix"; then + # Extract the first word of "${ac_tool_prefix}gcc", so it can be a program name with args. +set dummy ${ac_tool_prefix}gcc; ac_word=$2 +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if test "${ac_cv_prog_CC+set}" = set; then + $as_echo_n "(cached) " >&6 +else + if test -n "$CC"; then + ac_cv_prog_CC="$CC" # Let the user override the test. else as_save_IFS=$IFS; IFS=$PATH_SEPARATOR for as_dir in $PATH @@ -2228,230 +2581,8 @@ do test -z "$as_dir" && as_dir=. for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then - ac_cv_prog_STRIP="${ac_tool_prefix}strip" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 - break 2 - fi -done -done -IFS=$as_save_IFS - -fi -fi -STRIP=$ac_cv_prog_STRIP -if test -n "$STRIP"; then - { echo "$as_me:$LINENO: result: $STRIP" >&5 -echo "${ECHO_T}$STRIP" >&6; } -else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } -fi - - -fi -if test -z "$ac_cv_prog_STRIP"; then - ac_ct_STRIP=$STRIP - # Extract the first word of "strip", so it can be a program name with args. -set dummy strip; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } -if test "${ac_cv_prog_ac_ct_STRIP+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - if test -n "$ac_ct_STRIP"; then - ac_cv_prog_ac_ct_STRIP="$ac_ct_STRIP" # Let the user override the test. -else -as_save_IFS=$IFS; IFS=$PATH_SEPARATOR -for as_dir in $PATH -do - IFS=$as_save_IFS - test -z "$as_dir" && as_dir=. - for ac_exec_ext in '' $ac_executable_extensions; do - if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then - ac_cv_prog_ac_ct_STRIP="strip" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 - break 2 - fi -done -done -IFS=$as_save_IFS - -fi -fi -ac_ct_STRIP=$ac_cv_prog_ac_ct_STRIP -if test -n "$ac_ct_STRIP"; then - { echo "$as_me:$LINENO: result: $ac_ct_STRIP" >&5 -echo "${ECHO_T}$ac_ct_STRIP" >&6; } -else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } -fi - - if test "x$ac_ct_STRIP" = x; then - STRIP=":" - else - case $cross_compiling:$ac_tool_warned in -yes:) -{ echo "$as_me:$LINENO: WARNING: In the future, Autoconf will not detect cross-tools -whose name does not start with the host triplet. If you think this -configuration is useful to you, please write to autoconf@gnu.org." >&5 -echo "$as_me: WARNING: In the future, Autoconf will not detect cross-tools -whose name does not start with the host triplet. If you think this -configuration is useful to you, please write to autoconf@gnu.org." >&2;} -ac_tool_warned=yes ;; -esac - STRIP=$ac_ct_STRIP - fi -else - STRIP="$ac_cv_prog_STRIP" -fi - -fi -INSTALL_STRIP_PROGRAM="\$(install_sh) -c -s" - -# We need awk for the "check" target. The system "awk" is bad on -# some platforms. -# Always define AMTAR for backward compatibility. - -AMTAR=${AMTAR-"${am_missing_run}tar"} - -am__tar='${AMTAR} chof - "$$tardir"'; am__untar='${AMTAR} xf -' - - - - - -CONFIG_STATUS_DEPENDENCIES='$(top_srcdir)/VERSION' - - - -cat >>confdefs.h <<\_ACEOF -#define _GNU_SOURCE 1 -_ACEOF - - - -ALL_LINGUAS="de eu ru it es uk fr pl nl cs id sk ko el zh_TW zh_CN pt_BR eo gl sv da lt tr ja hu et ca bg ga" - -# Make sure we can run config.sub. -$SHELL "$ac_aux_dir/config.sub" sun4 >/dev/null 2>&1 || - { { echo "$as_me:$LINENO: error: cannot run $SHELL $ac_aux_dir/config.sub" >&5 -echo "$as_me: error: cannot run $SHELL $ac_aux_dir/config.sub" >&2;} - { (exit 1); exit 1; }; } - -{ echo "$as_me:$LINENO: checking build system type" >&5 -echo $ECHO_N "checking build system type... $ECHO_C" >&6; } -if test "${ac_cv_build+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - ac_build_alias=$build_alias -test "x$ac_build_alias" = x && - ac_build_alias=`$SHELL "$ac_aux_dir/config.guess"` -test "x$ac_build_alias" = x && - { { echo "$as_me:$LINENO: error: cannot guess build type; you must specify one" >&5 -echo "$as_me: error: cannot guess build type; you must specify one" >&2;} - { (exit 1); exit 1; }; } -ac_cv_build=`$SHELL "$ac_aux_dir/config.sub" $ac_build_alias` || - { { echo "$as_me:$LINENO: error: $SHELL $ac_aux_dir/config.sub $ac_build_alias failed" >&5 -echo "$as_me: error: $SHELL $ac_aux_dir/config.sub $ac_build_alias failed" >&2;} - { (exit 1); exit 1; }; } - -fi -{ echo "$as_me:$LINENO: result: $ac_cv_build" >&5 -echo "${ECHO_T}$ac_cv_build" >&6; } -case $ac_cv_build in -*-*-*) ;; -*) { { echo "$as_me:$LINENO: error: invalid value of canonical build" >&5 -echo "$as_me: error: invalid value of canonical build" >&2;} - { (exit 1); exit 1; }; };; -esac -build=$ac_cv_build -ac_save_IFS=$IFS; IFS='-' -set x $ac_cv_build -shift -build_cpu=$1 -build_vendor=$2 -shift; shift -# Remember, the first character of IFS is used to create $*, -# except with old shells: -build_os=$* -IFS=$ac_save_IFS -case $build_os in *\ *) build_os=`echo "$build_os" | sed 's/ /-/g'`;; esac - - -{ echo "$as_me:$LINENO: checking host system type" >&5 -echo $ECHO_N "checking host system type... $ECHO_C" >&6; } -if test "${ac_cv_host+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - if test "x$host_alias" = x; then - ac_cv_host=$ac_cv_build -else - ac_cv_host=`$SHELL "$ac_aux_dir/config.sub" $host_alias` || - { { echo "$as_me:$LINENO: error: $SHELL $ac_aux_dir/config.sub $host_alias failed" >&5 -echo "$as_me: error: $SHELL $ac_aux_dir/config.sub $host_alias failed" >&2;} - { (exit 1); exit 1; }; } -fi - -fi -{ echo "$as_me:$LINENO: result: $ac_cv_host" >&5 -echo "${ECHO_T}$ac_cv_host" >&6; } -case $ac_cv_host in -*-*-*) ;; -*) { { echo "$as_me:$LINENO: error: invalid value of canonical host" >&5 -echo "$as_me: error: invalid value of canonical host" >&2;} - { (exit 1); exit 1; }; };; -esac -host=$ac_cv_host -ac_save_IFS=$IFS; IFS='-' -set x $ac_cv_host -shift -host_cpu=$1 -host_vendor=$2 -shift; shift -# Remember, the first character of IFS is used to create $*, -# except with old shells: -host_os=$* -IFS=$ac_save_IFS -case $host_os in *\ *) host_os=`echo "$host_os" | sed 's/ /-/g'`;; esac - - - -{ echo "$as_me:$LINENO: checking for prefix" >&5 -echo $ECHO_N "checking for prefix... $ECHO_C" >&6; } -if test x$prefix = xNONE; then - mutt_cv_prefix=$ac_default_prefix -else - mutt_cv_prefix=$prefix -fi -{ echo "$as_me:$LINENO: result: $mutt_cv_prefix" >&5 -echo "${ECHO_T}$mutt_cv_prefix" >&6; } - -ac_ext=c -ac_cpp='$CPP $CPPFLAGS' -ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' -ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' -ac_compiler_gnu=$ac_cv_c_compiler_gnu -if test -n "$ac_tool_prefix"; then - # Extract the first word of "${ac_tool_prefix}gcc", so it can be a program name with args. -set dummy ${ac_tool_prefix}gcc; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } -if test "${ac_cv_prog_CC+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - if test -n "$CC"; then - ac_cv_prog_CC="$CC" # Let the user override the test. -else -as_save_IFS=$IFS; IFS=$PATH_SEPARATOR -for as_dir in $PATH -do - IFS=$as_save_IFS - test -z "$as_dir" && as_dir=. - for ac_exec_ext in '' $ac_executable_extensions; do - if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then - ac_cv_prog_CC="${ac_tool_prefix}gcc" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + ac_cv_prog_CC="${ac_tool_prefix}gcc" + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -2462,11 +2593,11 @@ fi fi CC=$ac_cv_prog_CC if test -n "$CC"; then - { echo "$as_me:$LINENO: result: $CC" >&5 -echo "${ECHO_T}$CC" >&6; } + { $as_echo "$as_me:$LINENO: result: $CC" >&5 +$as_echo "$CC" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -2475,10 +2606,10 @@ if test -z "$ac_cv_prog_CC"; then ac_ct_CC=$CC # Extract the first word of "gcc", so it can be a program name with args. set dummy gcc; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_prog_ac_ct_CC+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test -n "$ac_ct_CC"; then ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test. @@ -2491,7 +2622,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_prog_ac_ct_CC="gcc" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -2502,11 +2633,11 @@ fi fi ac_ct_CC=$ac_cv_prog_ac_ct_CC if test -n "$ac_ct_CC"; then - { echo "$as_me:$LINENO: result: $ac_ct_CC" >&5 -echo "${ECHO_T}$ac_ct_CC" >&6; } + { $as_echo "$as_me:$LINENO: result: $ac_ct_CC" >&5 +$as_echo "$ac_ct_CC" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi if test "x$ac_ct_CC" = x; then @@ -2514,12 +2645,8 @@ fi else case $cross_compiling:$ac_tool_warned in yes:) -{ echo "$as_me:$LINENO: WARNING: In the future, Autoconf will not detect cross-tools -whose name does not start with the host triplet. If you think this -configuration is useful to you, please write to autoconf@gnu.org." >&5 -echo "$as_me: WARNING: In the future, Autoconf will not detect cross-tools -whose name does not start with the host triplet. If you think this -configuration is useful to you, please write to autoconf@gnu.org." >&2;} +{ $as_echo "$as_me:$LINENO: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} ac_tool_warned=yes ;; esac CC=$ac_ct_CC @@ -2532,10 +2659,10 @@ if test -z "$CC"; then if test -n "$ac_tool_prefix"; then # Extract the first word of "${ac_tool_prefix}cc", so it can be a program name with args. set dummy ${ac_tool_prefix}cc; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_prog_CC+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test -n "$CC"; then ac_cv_prog_CC="$CC" # Let the user override the test. @@ -2548,7 +2675,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_prog_CC="${ac_tool_prefix}cc" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -2559,11 +2686,11 @@ fi fi CC=$ac_cv_prog_CC if test -n "$CC"; then - { echo "$as_me:$LINENO: result: $CC" >&5 -echo "${ECHO_T}$CC" >&6; } + { $as_echo "$as_me:$LINENO: result: $CC" >&5 +$as_echo "$CC" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -2572,10 +2699,10 @@ fi 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 "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_prog_CC+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test -n "$CC"; then ac_cv_prog_CC="$CC" # Let the user override the test. @@ -2593,7 +2720,7 @@ do continue fi ac_cv_prog_CC="cc" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -2616,11 +2743,11 @@ fi fi CC=$ac_cv_prog_CC if test -n "$CC"; then - { echo "$as_me:$LINENO: result: $CC" >&5 -echo "${ECHO_T}$CC" >&6; } + { $as_echo "$as_me:$LINENO: result: $CC" >&5 +$as_echo "$CC" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -2631,10 +2758,10 @@ if test -z "$CC"; then do # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args. set dummy $ac_tool_prefix$ac_prog; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_prog_CC+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test -n "$CC"; then ac_cv_prog_CC="$CC" # Let the user override the test. @@ -2647,7 +2774,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_prog_CC="$ac_tool_prefix$ac_prog" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -2658,11 +2785,11 @@ fi fi CC=$ac_cv_prog_CC if test -n "$CC"; then - { echo "$as_me:$LINENO: result: $CC" >&5 -echo "${ECHO_T}$CC" >&6; } + { $as_echo "$as_me:$LINENO: result: $CC" >&5 +$as_echo "$CC" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -2675,10 +2802,10 @@ if test -z "$CC"; then do # Extract the first word of "$ac_prog", so it can be a program name with args. set dummy $ac_prog; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_prog_ac_ct_CC+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test -n "$ac_ct_CC"; then ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test. @@ -2691,7 +2818,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_prog_ac_ct_CC="$ac_prog" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -2702,11 +2829,11 @@ fi fi ac_ct_CC=$ac_cv_prog_ac_ct_CC if test -n "$ac_ct_CC"; then - { echo "$as_me:$LINENO: result: $ac_ct_CC" >&5 -echo "${ECHO_T}$ac_ct_CC" >&6; } + { $as_echo "$as_me:$LINENO: result: $ac_ct_CC" >&5 +$as_echo "$ac_ct_CC" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -2718,12 +2845,8 @@ done else case $cross_compiling:$ac_tool_warned in yes:) -{ echo "$as_me:$LINENO: WARNING: In the future, Autoconf will not detect cross-tools -whose name does not start with the host triplet. If you think this -configuration is useful to you, please write to autoconf@gnu.org." >&5 -echo "$as_me: WARNING: In the future, Autoconf will not detect cross-tools -whose name does not start with the host triplet. If you think this -configuration is useful to you, please write to autoconf@gnu.org." >&2;} +{ $as_echo "$as_me:$LINENO: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} ac_tool_warned=yes ;; esac CC=$ac_ct_CC @@ -2733,44 +2856,50 @@ fi fi -test -z "$CC" && { { echo "$as_me:$LINENO: error: no acceptable C compiler found in \$PATH +test -z "$CC" && { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: no acceptable C compiler found in \$PATH See \`config.log' for more details." >&5 -echo "$as_me: error: no acceptable C compiler found in \$PATH +$as_echo "$as_me: error: no acceptable C compiler found in \$PATH See \`config.log' for more details." >&2;} - { (exit 1); exit 1; }; } + { (exit 1); exit 1; }; }; } # Provide some information about the compiler. -echo "$as_me:$LINENO: checking for C compiler version" >&5 -ac_compiler=`set X $ac_compile; echo $2` +$as_echo "$as_me:$LINENO: checking for C compiler version" >&5 +set X $ac_compile +ac_compiler=$2 { (ac_try="$ac_compiler --version >&5" case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compiler --version >&5") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } { (ac_try="$ac_compiler -v >&5" case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compiler -v >&5") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } { (ac_try="$ac_compiler -V >&5" case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compiler -V >&5") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } cat >conftest.$ac_ext <<_ACEOF @@ -2789,27 +2918,22 @@ main () } _ACEOF ac_clean_files_save=$ac_clean_files -ac_clean_files="$ac_clean_files a.out a.exe b.out" +ac_clean_files="$ac_clean_files a.out a.out.dSYM a.exe b.out" # Try to create an executable without -o first, disregard a.out. # It will help us diagnose broken compilers, and finding out an intuition # of exeext. -{ echo "$as_me:$LINENO: checking for C compiler default output file name" >&5 -echo $ECHO_N "checking for C compiler default output file name... $ECHO_C" >&6; } -ac_link_default=`echo "$ac_link" | sed 's/ -o *conftest[^ ]*//'` -# -# List of possible output files, starting from the most likely. -# The algorithm is not robust to junk in `.', hence go to wildcards (a.*) -# only as a last resort. b.out is created by i960 compilers. -ac_files='a_out.exe a.exe conftest.exe a.out conftest a.* conftest.* b.out' -# -# The IRIX 6 linker writes into existing files which may not be -# executable, retaining their permissions. Remove them first so a -# subsequent execution test works. +{ $as_echo "$as_me:$LINENO: checking for C compiler default output file name" >&5 +$as_echo_n "checking for C compiler default output file name... " >&6; } +ac_link_default=`$as_echo "$ac_link" | sed 's/ -o *conftest[^ ]*//'` + +# The possible output files: +ac_files="a.out conftest.exe conftest a.exe a_out.exe b.out conftest.*" + ac_rmfiles= for ac_file in $ac_files do case $ac_file in - *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.o | *.obj ) ;; + *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) ;; * ) ac_rmfiles="$ac_rmfiles $ac_file";; esac done @@ -2820,10 +2944,11 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link_default") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; then # Autoconf-2.13 could set the ac_cv_exeext variable to `no'. # So ignore a value of `no', otherwise this would lead to `EXEEXT = no' @@ -2834,7 +2959,7 @@ for ac_file in $ac_files '' do test -f "$ac_file" || continue case $ac_file in - *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.o | *.obj ) + *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) ;; [ab].out ) # We found the default executable, but exeext='' is most @@ -2861,25 +2986,27 @@ else ac_file='' fi -{ echo "$as_me:$LINENO: result: $ac_file" >&5 -echo "${ECHO_T}$ac_file" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_file" >&5 +$as_echo "$ac_file" >&6; } if test -z "$ac_file"; then - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 -{ { echo "$as_me:$LINENO: error: C compiler cannot create executables +{ { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: C compiler cannot create executables See \`config.log' for more details." >&5 -echo "$as_me: error: C compiler cannot create executables +$as_echo "$as_me: error: C compiler cannot create executables See \`config.log' for more details." >&2;} - { (exit 77); exit 77; }; } + { (exit 77); exit 77; }; }; } fi ac_exeext=$ac_cv_exeext # Check that the compiler produces executables we can run. If not, either # the compiler is broken, or we cross compile. -{ echo "$as_me:$LINENO: checking whether the C compiler works" >&5 -echo $ECHO_N "checking whether the C compiler works... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether the C compiler works" >&5 +$as_echo_n "checking whether the C compiler works... " >&6; } # FIXME: These cross compiler hacks should be removed for Autoconf 3.0 # If not cross compiling, check that we can run a simple program. if test "$cross_compiling" != yes; then @@ -2888,49 +3015,53 @@ if test "$cross_compiling" != yes; then *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then cross_compiling=no else if test "$cross_compiling" = maybe; then cross_compiling=yes else - { { echo "$as_me:$LINENO: error: cannot run C compiled programs. + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: cannot run C compiled programs. If you meant to cross compile, use \`--host'. See \`config.log' for more details." >&5 -echo "$as_me: error: cannot run C compiled programs. +$as_echo "$as_me: error: cannot run C compiled programs. If you meant to cross compile, use \`--host'. See \`config.log' for more details." >&2;} - { (exit 1); exit 1; }; } + { (exit 1); exit 1; }; }; } fi fi fi -{ echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } +{ $as_echo "$as_me:$LINENO: result: yes" >&5 +$as_echo "yes" >&6; } -rm -f a.out a.exe conftest$ac_cv_exeext b.out +rm -f -r a.out a.out.dSYM a.exe conftest$ac_cv_exeext b.out ac_clean_files=$ac_clean_files_save # Check that the compiler produces executables we can run. If not, either # the compiler is broken, or we cross compile. -{ echo "$as_me:$LINENO: checking whether we are cross compiling" >&5 -echo $ECHO_N "checking whether we are cross compiling... $ECHO_C" >&6; } -{ echo "$as_me:$LINENO: result: $cross_compiling" >&5 -echo "${ECHO_T}$cross_compiling" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether we are cross compiling" >&5 +$as_echo_n "checking whether we are cross compiling... " >&6; } +{ $as_echo "$as_me:$LINENO: result: $cross_compiling" >&5 +$as_echo "$cross_compiling" >&6; } -{ echo "$as_me:$LINENO: checking for suffix of executables" >&5 -echo $ECHO_N "checking for suffix of executables... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for suffix of executables" >&5 +$as_echo_n "checking for suffix of executables... " >&6; } if { (ac_try="$ac_link" case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; then # If both `conftest.exe' and `conftest' are `present' (well, observable) # catch `conftest.exe'. For instance with Cygwin, `ls conftest' will @@ -2939,31 +3070,33 @@ eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 for ac_file in conftest.exe conftest conftest.*; do test -f "$ac_file" || continue case $ac_file in - *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.o | *.obj ) ;; + *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) ;; *.* ) ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'` break;; * ) break;; esac done else - { { echo "$as_me:$LINENO: error: cannot compute suffix of executables: cannot compile and link + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: cannot compute suffix of executables: cannot compile and link See \`config.log' for more details." >&5 -echo "$as_me: error: cannot compute suffix of executables: cannot compile and link +$as_echo "$as_me: error: cannot compute suffix of executables: cannot compile and link See \`config.log' for more details." >&2;} - { (exit 1); exit 1; }; } + { (exit 1); exit 1; }; }; } fi rm -f conftest$ac_cv_exeext -{ echo "$as_me:$LINENO: result: $ac_cv_exeext" >&5 -echo "${ECHO_T}$ac_cv_exeext" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_exeext" >&5 +$as_echo "$ac_cv_exeext" >&6; } rm -f conftest.$ac_ext EXEEXT=$ac_cv_exeext ac_exeext=$EXEEXT -{ echo "$as_me:$LINENO: checking for suffix of object files" >&5 -echo $ECHO_N "checking for suffix of object files... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for suffix of object files" >&5 +$as_echo_n "checking for suffix of object files... " >&6; } if test "${ac_cv_objext+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -2986,40 +3119,43 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; then for ac_file in conftest.o conftest.obj conftest.*; do test -f "$ac_file" || continue; case $ac_file in - *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf ) ;; + *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM ) ;; *) ac_cv_objext=`expr "$ac_file" : '.*\.\(.*\)'` break;; esac done else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 -{ { echo "$as_me:$LINENO: error: cannot compute suffix of object files: cannot compile +{ { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: cannot compute suffix of object files: cannot compile See \`config.log' for more details." >&5 -echo "$as_me: error: cannot compute suffix of object files: cannot compile +$as_echo "$as_me: error: cannot compute suffix of object files: cannot compile See \`config.log' for more details." >&2;} - { (exit 1); exit 1; }; } + { (exit 1); exit 1; }; }; } fi rm -f conftest.$ac_cv_objext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_objext" >&5 -echo "${ECHO_T}$ac_cv_objext" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_objext" >&5 +$as_echo "$ac_cv_objext" >&6; } OBJEXT=$ac_cv_objext ac_objext=$OBJEXT -{ echo "$as_me:$LINENO: checking whether we are using the GNU C compiler" >&5 -echo $ECHO_N "checking whether we are using the GNU C compiler... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether we are using the GNU C compiler" >&5 +$as_echo_n "checking whether we are using the GNU C compiler... " >&6; } if test "${ac_cv_c_compiler_gnu+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -3045,20 +3181,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_compiler_gnu=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_compiler_gnu=no @@ -3068,15 +3205,19 @@ rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext ac_cv_c_compiler_gnu=$ac_compiler_gnu fi -{ echo "$as_me:$LINENO: result: $ac_cv_c_compiler_gnu" >&5 -echo "${ECHO_T}$ac_cv_c_compiler_gnu" >&6; } -GCC=`test $ac_compiler_gnu = yes && echo yes` +{ $as_echo "$as_me:$LINENO: result: $ac_cv_c_compiler_gnu" >&5 +$as_echo "$ac_cv_c_compiler_gnu" >&6; } +if test $ac_compiler_gnu = yes; then + GCC=yes +else + GCC= +fi ac_test_CFLAGS=${CFLAGS+set} ac_save_CFLAGS=$CFLAGS -{ echo "$as_me:$LINENO: checking whether $CC accepts -g" >&5 -echo $ECHO_N "checking whether $CC accepts -g... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether $CC accepts -g" >&5 +$as_echo_n "checking whether $CC accepts -g... " >&6; } if test "${ac_cv_prog_cc_g+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_save_c_werror_flag=$ac_c_werror_flag ac_c_werror_flag=yes @@ -3103,20 +3244,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_prog_cc_g=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 CFLAGS="" @@ -3141,20 +3283,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then : else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_c_werror_flag=$ac_save_c_werror_flag @@ -3180,20 +3323,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_prog_cc_g=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -3208,8 +3352,8 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext ac_c_werror_flag=$ac_save_c_werror_flag fi -{ echo "$as_me:$LINENO: result: $ac_cv_prog_cc_g" >&5 -echo "${ECHO_T}$ac_cv_prog_cc_g" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_prog_cc_g" >&5 +$as_echo "$ac_cv_prog_cc_g" >&6; } if test "$ac_test_CFLAGS" = set; then CFLAGS=$ac_save_CFLAGS elif test $ac_cv_prog_cc_g = yes; then @@ -3225,10 +3369,10 @@ else CFLAGS= fi fi -{ echo "$as_me:$LINENO: checking for $CC option to accept ISO C89" >&5 -echo $ECHO_N "checking for $CC option to accept ISO C89... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $CC option to accept ISO C89" >&5 +$as_echo_n "checking for $CC option to accept ISO C89... " >&6; } if test "${ac_cv_prog_cc_c89+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_cv_prog_cc_c89=no ac_save_CC=$CC @@ -3299,20 +3443,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_prog_cc_c89=$ac_arg else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -3328,15 +3473,15 @@ fi # AC_CACHE_VAL case "x$ac_cv_prog_cc_c89" in x) - { echo "$as_me:$LINENO: result: none needed" >&5 -echo "${ECHO_T}none needed" >&6; } ;; + { $as_echo "$as_me:$LINENO: result: none needed" >&5 +$as_echo "none needed" >&6; } ;; xno) - { echo "$as_me:$LINENO: result: unsupported" >&5 -echo "${ECHO_T}unsupported" >&6; } ;; + { $as_echo "$as_me:$LINENO: result: unsupported" >&5 +$as_echo "unsupported" >&6; } ;; *) CC="$CC $ac_cv_prog_cc_c89" - { echo "$as_me:$LINENO: result: $ac_cv_prog_cc_c89" >&5 -echo "${ECHO_T}$ac_cv_prog_cc_c89" >&6; } ;; + { $as_echo "$as_me:$LINENO: result: $ac_cv_prog_cc_c89" >&5 +$as_echo "$ac_cv_prog_cc_c89" >&6; } ;; esac @@ -3345,75 +3490,13 @@ ac_cpp='$CPP $CPPFLAGS' ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' ac_compiler_gnu=$ac_cv_c_compiler_gnu -DEPDIR="${am__leading_dot}deps" - -ac_config_commands="$ac_config_commands depfiles" - - -am_make=${MAKE-make} -cat > confinc << 'END' -am__doit: - @echo done -.PHONY: am__doit -END -# If we don't find an include directive, just comment out the code. -{ echo "$as_me:$LINENO: checking for style of include used by $am_make" >&5 -echo $ECHO_N "checking for style of include used by $am_make... $ECHO_C" >&6; } -am__include="#" -am__quote= -_am_result=none -# First try GNU make style include. -echo "include confinc" > confmf -# We grep out `Entering directory' and `Leaving directory' -# messages which can occur if `w' ends up in MAKEFLAGS. -# In particular we don't look at `^make:' because GNU make might -# be invoked under some other name (usually "gmake"), in which -# case it prints its new name instead of `make'. -if test "`$am_make -s -f confmf 2> /dev/null | grep -v 'ing directory'`" = "done"; then - am__include=include - am__quote= - _am_result=GNU -fi -# Now try BSD make style include. -if test "$am__include" = "#"; then - echo '.include "confinc"' > confmf - if test "`$am_make -s -f confmf 2> /dev/null`" = "done"; then - am__include=.include - am__quote="\"" - _am_result=BSD - fi -fi - - -{ echo "$as_me:$LINENO: result: $_am_result" >&5 -echo "${ECHO_T}$_am_result" >&6; } -rm -f confinc confmf - -# Check whether --enable-dependency-tracking was given. -if test "${enable_dependency_tracking+set}" = set; then - enableval=$enable_dependency_tracking; -fi - -if test "x$enable_dependency_tracking" != xno; then - am_depcomp="$ac_aux_dir/depcomp" - AMDEPBACKSLASH='\' -fi - if test "x$enable_dependency_tracking" != xno; then - AMDEP_TRUE= - AMDEP_FALSE='#' -else - AMDEP_TRUE='#' - AMDEP_FALSE= -fi - - depcc="$CC" am_compiler_list= -{ echo "$as_me:$LINENO: checking dependency style of $depcc" >&5 -echo $ECHO_N "checking dependency style of $depcc... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking dependency style of $depcc" >&5 +$as_echo_n "checking dependency style of $depcc... " >&6; } if test "${am_cv_CC_dependencies_compiler_type+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test -z "$AMDEP_TRUE" && test -f "$am_depcomp"; then # We make a subdir and do the tests there. Otherwise we can end up @@ -3438,6 +3521,11 @@ else if test "$am_compiler_list" = ""; then am_compiler_list=`sed -n 's/^#*\([a-zA-Z0-9]*\))$/\1/p' < ./depcomp` fi + am__universal=false + case " $depcc " in #( + *\ -arch\ *\ -arch\ *) am__universal=true ;; + esac + for depmode in $am_compiler_list; do # Setup a source with many dependencies, because some compilers # like to wrap large dependency lists on column 80 (with \), and @@ -3455,7 +3543,17 @@ else done echo "${am__include} ${am__quote}sub/conftest.Po${am__quote}" > confmf + # We check with `-c' and `-o' for the sake of the "dashmstdout" + # mode. It turns out that the SunPro C++ compiler does not properly + # handle `-M -o', and we need to detect this. Also, some Intel + # versions had trouble with output in subdirs + am__obj=sub/conftest.${OBJEXT-o} + am__minus_obj="-o $am__obj" case $depmode in + gcc) + # This depmode causes a compiler race in universal mode. + test "$am__universal" = false || continue + ;; nosideeffect) # after this tag, mechanisms are not by side-effect, so they'll # only be used when explicitly requested @@ -3465,19 +3563,23 @@ else break fi ;; + msvisualcpp | msvcmsys) + # This compiler won't grok `-c -o', but also, the minuso test has + # not run yet. These depmodes are late enough in the game, and + # so weak that their functioning should not be impacted. + am__obj=conftest.${OBJEXT-o} + am__minus_obj= + ;; none) break ;; esac - # We check with `-c' and `-o' for the sake of the "dashmstdout" - # mode. It turns out that the SunPro C++ compiler does not properly - # handle `-M -o', and we need to detect this. if depmode=$depmode \ - source=sub/conftest.c object=sub/conftest.${OBJEXT-o} \ + source=sub/conftest.c object=$am__obj \ depfile=sub/conftest.Po tmpdepfile=sub/conftest.TPo \ - $SHELL ./depcomp $depcc -c -o sub/conftest.${OBJEXT-o} sub/conftest.c \ + $SHELL ./depcomp $depcc -c $am__minus_obj sub/conftest.c \ >/dev/null 2>conftest.err && grep sub/conftst1.h sub/conftest.Po > /dev/null 2>&1 && grep sub/conftst6.h sub/conftest.Po > /dev/null 2>&1 && - grep sub/conftest.${OBJEXT-o} sub/conftest.Po > /dev/null 2>&1 && + grep $am__obj sub/conftest.Po > /dev/null 2>&1 && ${MAKE-make} -s -f confmf > /dev/null 2>&1; then # icc doesn't choke on unknown options, it will just issue warnings # or remarks (even with -Werror). So we grep stderr for any message @@ -3501,8 +3603,8 @@ else fi fi -{ echo "$as_me:$LINENO: result: $am_cv_CC_dependencies_compiler_type" >&5 -echo "${ECHO_T}$am_cv_CC_dependencies_compiler_type" >&6; } +{ $as_echo "$as_me:$LINENO: result: $am_cv_CC_dependencies_compiler_type" >&5 +$as_echo "$am_cv_CC_dependencies_compiler_type" >&6; } CCDEPMODE=depmode=$am_cv_CC_dependencies_compiler_type if @@ -3517,123 +3619,20 @@ fi -{ echo "$as_me:$LINENO: checking for library containing strerror" >&5 -echo $ECHO_N "checking for library containing strerror... $ECHO_C" >&6; } -if test "${ac_cv_search_strerror+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - ac_func_search_save_LIBS=$LIBS -cat >conftest.$ac_ext <<_ACEOF -/* confdefs.h. */ -_ACEOF -cat confdefs.h >>conftest.$ac_ext -cat >>conftest.$ac_ext <<_ACEOF -/* end confdefs.h. */ - -/* Override any GCC internal prototype to avoid an error. - Use char because int might match the return type of a GCC - builtin and then its argument prototype would still apply. */ -#ifdef __cplusplus -extern "C" -#endif -char strerror (); -int -main () -{ -return strerror (); - ; - return 0; -} -_ACEOF -for ac_lib in '' cposix; do - if test -z "$ac_lib"; then - ac_res="none required" - else - ac_res=-l$ac_lib - LIBS="-l$ac_lib $ac_func_search_save_LIBS" - fi - rm -f conftest.$ac_objext conftest$ac_exeext -if { (ac_try="$ac_link" -case "(($ac_try" in - *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; - *) ac_try_echo=$ac_try;; -esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_link") 2>conftest.er1 - ac_status=$? - grep -v '^ *+' conftest.er1 >conftest.err - rm -f conftest.er1 - cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); } && { - test -z "$ac_c_werror_flag" || - test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then - ac_cv_search_strerror=$ac_res -else - echo "$as_me: failed program was:" >&5 -sed 's/^/| /' conftest.$ac_ext >&5 - - -fi - -rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ - conftest$ac_exeext - if test "${ac_cv_search_strerror+set}" = set; then - break -fi -done -if test "${ac_cv_search_strerror+set}" = set; then - : -else - ac_cv_search_strerror=no -fi -rm conftest.$ac_ext -LIBS=$ac_func_search_save_LIBS -fi -{ echo "$as_me:$LINENO: result: $ac_cv_search_strerror" >&5 -echo "${ECHO_T}$ac_cv_search_strerror" >&6; } -ac_res=$ac_cv_search_strerror -if test "$ac_res" != no; then - test "$ac_res" = "none required" || LIBS="$ac_res $LIBS" - -fi - -{ echo "$as_me:$LINENO: checking for function prototypes" >&5 -echo $ECHO_N "checking for function prototypes... $ECHO_C" >&6; } -if test "$ac_cv_prog_cc_c89" != no; then - { echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } - -cat >>confdefs.h <<\_ACEOF -#define PROTOTYPES 1 -_ACEOF - - -cat >>confdefs.h <<\_ACEOF -#define __PROTOTYPES 1 -_ACEOF - -else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } -fi - -ac_ext=c -ac_cpp='$CPP $CPPFLAGS' -ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' -ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' -ac_compiler_gnu=$ac_cv_c_compiler_gnu -{ echo "$as_me:$LINENO: checking how to run the C preprocessor" >&5 -echo $ECHO_N "checking how to run the C preprocessor... $ECHO_C" >&6; } -# On Suns, sometimes $CPP names a directory. -if test -n "$CPP" && test -d "$CPP"; then - CPP= -fi -if test -z "$CPP"; then - if test "${ac_cv_prog_CPP+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 +ac_ext=c +ac_cpp='$CPP $CPPFLAGS' +ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' +ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' +ac_compiler_gnu=$ac_cv_c_compiler_gnu +{ $as_echo "$as_me:$LINENO: checking how to run the C preprocessor" >&5 +$as_echo_n "checking how to run the C preprocessor... " >&6; } +# On Suns, sometimes $CPP names a directory. +if test -n "$CPP" && test -d "$CPP"; then + CPP= +fi +if test -z "$CPP"; then + if test "${ac_cv_prog_CPP+set}" = set; then + $as_echo_n "(cached) " >&6 else # Double quotes because CPP needs to be expanded for CPP in "$CC -E" "$CC -E -traditional-cpp" "/lib/cpp" @@ -3665,20 +3664,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then : else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 # Broken: fails on valid input. @@ -3702,13 +3702,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err @@ -3716,7 +3717,7 @@ eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 # Broken: success on invalid input. continue else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 # Passes both tests. @@ -3741,8 +3742,8 @@ fi else ac_cv_prog_CPP=$CPP fi -{ echo "$as_me:$LINENO: result: $CPP" >&5 -echo "${ECHO_T}$CPP" >&6; } +{ $as_echo "$as_me:$LINENO: result: $CPP" >&5 +$as_echo "$CPP" >&6; } ac_preproc_ok=false for ac_c_preproc_warn_flag in '' yes do @@ -3770,20 +3771,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then : else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 # Broken: fails on valid input. @@ -3807,13 +3809,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err @@ -3821,7 +3824,7 @@ eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 # Broken: success on invalid input. continue else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 # Passes both tests. @@ -3837,11 +3840,13 @@ rm -f conftest.err conftest.$ac_ext if $ac_preproc_ok; then : else - { { echo "$as_me:$LINENO: error: C preprocessor \"$CPP\" fails sanity check + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: C preprocessor \"$CPP\" fails sanity check See \`config.log' for more details." >&5 -echo "$as_me: error: C preprocessor \"$CPP\" fails sanity check +$as_echo "$as_me: error: C preprocessor \"$CPP\" fails sanity check See \`config.log' for more details." >&2;} - { (exit 1); exit 1; }; } + { (exit 1); exit 1; }; }; } fi ac_ext=c @@ -3851,42 +3856,37 @@ ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $ ac_compiler_gnu=$ac_cv_c_compiler_gnu -{ echo "$as_me:$LINENO: checking for grep that handles long lines and -e" >&5 -echo $ECHO_N "checking for grep that handles long lines and -e... $ECHO_C" >&6; } -if test "${ac_cv_path_GREP+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - # Extract the first word of "grep ggrep" to use in msg output -if test -z "$GREP"; then -set dummy grep ggrep; ac_prog_name=$2 +{ $as_echo "$as_me:$LINENO: checking for grep that handles long lines and -e" >&5 +$as_echo_n "checking for grep that handles long lines and -e... " >&6; } if test "${ac_cv_path_GREP+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else + if test -z "$GREP"; then ac_path_GREP_found=false -# Loop through the user's path and test for each of PROGNAME-LIST -as_save_IFS=$IFS; IFS=$PATH_SEPARATOR + # Loop through the user's path and test for each of PROGNAME-LIST + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR for as_dir in $PATH$PATH_SEPARATOR/usr/xpg4/bin do IFS=$as_save_IFS test -z "$as_dir" && as_dir=. for ac_prog in grep ggrep; do - for ac_exec_ext in '' $ac_executable_extensions; do - ac_path_GREP="$as_dir/$ac_prog$ac_exec_ext" - { test -f "$ac_path_GREP" && $as_test_x "$ac_path_GREP"; } || continue - # Check for GNU ac_path_GREP and select it if it is found. + for ac_exec_ext in '' $ac_executable_extensions; do + ac_path_GREP="$as_dir/$ac_prog$ac_exec_ext" + { test -f "$ac_path_GREP" && $as_test_x "$ac_path_GREP"; } || continue +# Check for GNU ac_path_GREP and select it if it is found. # Check for GNU $ac_path_GREP case `"$ac_path_GREP" --version 2>&1` in *GNU*) ac_cv_path_GREP="$ac_path_GREP" ac_path_GREP_found=:;; *) ac_count=0 - echo $ECHO_N "0123456789$ECHO_C" >"conftest.in" + $as_echo_n 0123456789 >"conftest.in" while : do cat "conftest.in" "conftest.in" >"conftest.tmp" mv "conftest.tmp" "conftest.in" cp "conftest.in" "conftest.nl" - echo 'GREP' >> "conftest.nl" + $as_echo 'GREP' >> "conftest.nl" "$ac_path_GREP" -e 'GREP$' -e '-(cannot match)-' < "conftest.nl" >"conftest.out" 2>/dev/null || break diff "conftest.out" "conftest.nl" >/dev/null 2>&1 || break ac_count=`expr $ac_count + 1` @@ -3901,74 +3901,60 @@ case `"$ac_path_GREP" --version 2>&1` in rm -f conftest.in conftest.tmp conftest.nl conftest.out;; esac - - $ac_path_GREP_found && break 3 + $ac_path_GREP_found && break 3 + done done done - -done IFS=$as_save_IFS - - -fi - -GREP="$ac_cv_path_GREP" -if test -z "$GREP"; then - { { echo "$as_me:$LINENO: error: no acceptable $ac_prog_name could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" >&5 -echo "$as_me: error: no acceptable $ac_prog_name could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" >&2;} + if test -z "$ac_cv_path_GREP"; then + { { $as_echo "$as_me:$LINENO: error: no acceptable grep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" >&5 +$as_echo "$as_me: error: no acceptable grep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" >&2;} { (exit 1); exit 1; }; } -fi - + fi else ac_cv_path_GREP=$GREP fi - fi -{ echo "$as_me:$LINENO: result: $ac_cv_path_GREP" >&5 -echo "${ECHO_T}$ac_cv_path_GREP" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_path_GREP" >&5 +$as_echo "$ac_cv_path_GREP" >&6; } GREP="$ac_cv_path_GREP" -{ echo "$as_me:$LINENO: checking for egrep" >&5 -echo $ECHO_N "checking for egrep... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for egrep" >&5 +$as_echo_n "checking for egrep... " >&6; } if test "${ac_cv_path_EGREP+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if echo a | $GREP -E '(a|b)' >/dev/null 2>&1 then ac_cv_path_EGREP="$GREP -E" else - # Extract the first word of "egrep" to use in msg output -if test -z "$EGREP"; then -set dummy egrep; ac_prog_name=$2 -if test "${ac_cv_path_EGREP+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else + if test -z "$EGREP"; then ac_path_EGREP_found=false -# Loop through the user's path and test for each of PROGNAME-LIST -as_save_IFS=$IFS; IFS=$PATH_SEPARATOR + # Loop through the user's path and test for each of PROGNAME-LIST + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR for as_dir in $PATH$PATH_SEPARATOR/usr/xpg4/bin do IFS=$as_save_IFS test -z "$as_dir" && as_dir=. for ac_prog in egrep; do - for ac_exec_ext in '' $ac_executable_extensions; do - ac_path_EGREP="$as_dir/$ac_prog$ac_exec_ext" - { test -f "$ac_path_EGREP" && $as_test_x "$ac_path_EGREP"; } || continue - # Check for GNU ac_path_EGREP and select it if it is found. + for ac_exec_ext in '' $ac_executable_extensions; do + ac_path_EGREP="$as_dir/$ac_prog$ac_exec_ext" + { test -f "$ac_path_EGREP" && $as_test_x "$ac_path_EGREP"; } || continue +# Check for GNU ac_path_EGREP and select it if it is found. # Check for GNU $ac_path_EGREP case `"$ac_path_EGREP" --version 2>&1` in *GNU*) ac_cv_path_EGREP="$ac_path_EGREP" ac_path_EGREP_found=:;; *) ac_count=0 - echo $ECHO_N "0123456789$ECHO_C" >"conftest.in" + $as_echo_n 0123456789 >"conftest.in" while : do cat "conftest.in" "conftest.in" >"conftest.tmp" mv "conftest.tmp" "conftest.in" cp "conftest.in" "conftest.nl" - echo 'EGREP' >> "conftest.nl" + $as_echo 'EGREP' >> "conftest.nl" "$ac_path_EGREP" 'EGREP$' < "conftest.nl" >"conftest.out" 2>/dev/null || break diff "conftest.out" "conftest.nl" >/dev/null 2>&1 || break ac_count=`expr $ac_count + 1` @@ -3983,40 +3969,31 @@ case `"$ac_path_EGREP" --version 2>&1` in rm -f conftest.in conftest.tmp conftest.nl conftest.out;; esac - - $ac_path_EGREP_found && break 3 + $ac_path_EGREP_found && break 3 + done done done - -done IFS=$as_save_IFS - - -fi - -EGREP="$ac_cv_path_EGREP" -if test -z "$EGREP"; then - { { echo "$as_me:$LINENO: error: no acceptable $ac_prog_name could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" >&5 -echo "$as_me: error: no acceptable $ac_prog_name could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" >&2;} + if test -z "$ac_cv_path_EGREP"; then + { { $as_echo "$as_me:$LINENO: error: no acceptable egrep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" >&5 +$as_echo "$as_me: error: no acceptable egrep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" >&2;} { (exit 1); exit 1; }; } -fi - + fi else ac_cv_path_EGREP=$EGREP fi - fi fi -{ echo "$as_me:$LINENO: result: $ac_cv_path_EGREP" >&5 -echo "${ECHO_T}$ac_cv_path_EGREP" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_path_EGREP" >&5 +$as_echo "$ac_cv_path_EGREP" >&6; } EGREP="$ac_cv_path_EGREP" -{ echo "$as_me:$LINENO: checking for ANSI C header files" >&5 -echo $ECHO_N "checking for ANSI C header files... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for ANSI C header files" >&5 +$as_echo_n "checking for ANSI C header files... " >&6; } if test "${ac_cv_header_stdc+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -4043,20 +4020,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_header_stdc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_header_stdc=no @@ -4095,167 +4073,1402 @@ cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ #include -_ACEOF -if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | - $EGREP "free" >/dev/null 2>&1; then - : +_ACEOF +if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | + $EGREP "free" >/dev/null 2>&1; then + : +else + ac_cv_header_stdc=no +fi +rm -f conftest* + +fi + +if test $ac_cv_header_stdc = yes; then + # /bin/cc in Irix-4.0.5 gets non-ANSI ctype macros unless using -ansi. + if test "$cross_compiling" = yes; then + : +else + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +#include +#include +#if ((' ' & 0x0FF) == 0x020) +# define ISLOWER(c) ('a' <= (c) && (c) <= 'z') +# define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c)) +#else +# define ISLOWER(c) \ + (('a' <= (c) && (c) <= 'i') \ + || ('j' <= (c) && (c) <= 'r') \ + || ('s' <= (c) && (c) <= 'z')) +# define TOUPPER(c) (ISLOWER(c) ? ((c) | 0x40) : (c)) +#endif + +#define XOR(e, f) (((e) && !(f)) || (!(e) && (f))) +int +main () +{ + int i; + for (i = 0; i < 256; i++) + if (XOR (islower (i), ISLOWER (i)) + || toupper (i) != TOUPPER (i)) + return 2; + return 0; +} +_ACEOF +rm -f conftest$ac_exeext +if { (ac_try="$ac_link" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_link") 2>&5 + ac_status=$? + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { ac_try='./conftest$ac_exeext' + { (case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_try") 2>&5 + ac_status=$? + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); }; }; then + : +else + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + +( exit $ac_status ) +ac_cv_header_stdc=no +fi +rm -rf conftest.dSYM +rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext +fi + + +fi +fi +{ $as_echo "$as_me:$LINENO: result: $ac_cv_header_stdc" >&5 +$as_echo "$ac_cv_header_stdc" >&6; } +if test $ac_cv_header_stdc = yes; then + +cat >>confdefs.h <<\_ACEOF +#define STDC_HEADERS 1 +_ACEOF + +fi + +# On IRIX 5.3, sys/types and inttypes.h are conflicting. + + + + + + + + + +for ac_header in sys/types.h sys/stat.h stdlib.h string.h memory.h strings.h \ + inttypes.h stdint.h unistd.h +do +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } +if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then + $as_echo_n "(cached) " >&6 +else + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +$ac_includes_default + +#include <$ac_header> +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + eval "$as_ac_Header=yes" +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + eval "$as_ac_Header=no" +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +fi +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then + cat >>confdefs.h <<_ACEOF +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 +_ACEOF + +fi + +done + + + + if test "${ac_cv_header_minix_config_h+set}" = set; then + { $as_echo "$as_me:$LINENO: checking for minix/config.h" >&5 +$as_echo_n "checking for minix/config.h... " >&6; } +if test "${ac_cv_header_minix_config_h+set}" = set; then + $as_echo_n "(cached) " >&6 +fi +{ $as_echo "$as_me:$LINENO: result: $ac_cv_header_minix_config_h" >&5 +$as_echo "$ac_cv_header_minix_config_h" >&6; } +else + # Is the header compilable? +{ $as_echo "$as_me:$LINENO: checking minix/config.h usability" >&5 +$as_echo_n "checking minix/config.h usability... " >&6; } +cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +$ac_includes_default +#include +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + ac_header_compiler=yes +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_header_compiler=no +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } + +# Is the header present? +{ $as_echo "$as_me:$LINENO: checking minix/config.h presence" >&5 +$as_echo_n "checking minix/config.h presence... " >&6; } +cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +#include +_ACEOF +if { (ac_try="$ac_cpp conftest.$ac_ext" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } >/dev/null && { + test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || + test ! -s conftest.err + }; then + ac_header_preproc=yes +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_header_preproc=no +fi + +rm -f conftest.err conftest.$ac_ext +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } + +# So? What about this header? +case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in + yes:no: ) + { $as_echo "$as_me:$LINENO: WARNING: minix/config.h: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: minix/config.h: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: minix/config.h: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: minix/config.h: proceeding with the compiler's result" >&2;} + ac_header_preproc=yes + ;; + no:yes:* ) + { $as_echo "$as_me:$LINENO: WARNING: minix/config.h: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: minix/config.h: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: minix/config.h: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: minix/config.h: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: minix/config.h: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: minix/config.h: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: minix/config.h: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: minix/config.h: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: minix/config.h: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: minix/config.h: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: minix/config.h: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: minix/config.h: in the future, the compiler will take precedence" >&2;} + + ;; +esac +{ $as_echo "$as_me:$LINENO: checking for minix/config.h" >&5 +$as_echo_n "checking for minix/config.h... " >&6; } +if test "${ac_cv_header_minix_config_h+set}" = set; then + $as_echo_n "(cached) " >&6 +else + ac_cv_header_minix_config_h=$ac_header_preproc +fi +{ $as_echo "$as_me:$LINENO: result: $ac_cv_header_minix_config_h" >&5 +$as_echo "$ac_cv_header_minix_config_h" >&6; } + +fi +if test "x$ac_cv_header_minix_config_h" = x""yes; then + MINIX=yes +else + MINIX= +fi + + + if test "$MINIX" = yes; then + +cat >>confdefs.h <<\_ACEOF +#define _POSIX_SOURCE 1 +_ACEOF + + +cat >>confdefs.h <<\_ACEOF +#define _POSIX_1_SOURCE 2 +_ACEOF + + +cat >>confdefs.h <<\_ACEOF +#define _MINIX 1 +_ACEOF + + fi + + + + { $as_echo "$as_me:$LINENO: checking whether it is safe to define __EXTENSIONS__" >&5 +$as_echo_n "checking whether it is safe to define __EXTENSIONS__... " >&6; } +if test "${ac_cv_safe_to_define___extensions__+set}" = set; then + $as_echo_n "(cached) " >&6 +else + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ + +# define __EXTENSIONS__ 1 + $ac_includes_default +int +main () +{ + + ; + return 0; +} +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + ac_cv_safe_to_define___extensions__=yes +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_cv_safe_to_define___extensions__=no +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +fi +{ $as_echo "$as_me:$LINENO: result: $ac_cv_safe_to_define___extensions__" >&5 +$as_echo "$ac_cv_safe_to_define___extensions__" >&6; } + test $ac_cv_safe_to_define___extensions__ = yes && + cat >>confdefs.h <<\_ACEOF +#define __EXTENSIONS__ 1 +_ACEOF + + cat >>confdefs.h <<\_ACEOF +#define _ALL_SOURCE 1 +_ACEOF + + cat >>confdefs.h <<\_ACEOF +#define _GNU_SOURCE 1 +_ACEOF + + cat >>confdefs.h <<\_ACEOF +#define _POSIX_PTHREAD_SEMANTICS 1 +_ACEOF + + cat >>confdefs.h <<\_ACEOF +#define _TANDEM_SOURCE 1 +_ACEOF + + + +ALL_LINGUAS="de eu ru it es uk fr pl nl cs id sk ko el zh_TW zh_CN pt_BR eo gl sv da lt tr ja hu et ca bg ga" + +# Make sure we can run config.sub. +$SHELL "$ac_aux_dir/config.sub" sun4 >/dev/null 2>&1 || + { { $as_echo "$as_me:$LINENO: error: cannot run $SHELL $ac_aux_dir/config.sub" >&5 +$as_echo "$as_me: error: cannot run $SHELL $ac_aux_dir/config.sub" >&2;} + { (exit 1); exit 1; }; } + +{ $as_echo "$as_me:$LINENO: checking build system type" >&5 +$as_echo_n "checking build system type... " >&6; } +if test "${ac_cv_build+set}" = set; then + $as_echo_n "(cached) " >&6 +else + ac_build_alias=$build_alias +test "x$ac_build_alias" = x && + ac_build_alias=`$SHELL "$ac_aux_dir/config.guess"` +test "x$ac_build_alias" = x && + { { $as_echo "$as_me:$LINENO: error: cannot guess build type; you must specify one" >&5 +$as_echo "$as_me: error: cannot guess build type; you must specify one" >&2;} + { (exit 1); exit 1; }; } +ac_cv_build=`$SHELL "$ac_aux_dir/config.sub" $ac_build_alias` || + { { $as_echo "$as_me:$LINENO: error: $SHELL $ac_aux_dir/config.sub $ac_build_alias failed" >&5 +$as_echo "$as_me: error: $SHELL $ac_aux_dir/config.sub $ac_build_alias failed" >&2;} + { (exit 1); exit 1; }; } + +fi +{ $as_echo "$as_me:$LINENO: result: $ac_cv_build" >&5 +$as_echo "$ac_cv_build" >&6; } +case $ac_cv_build in +*-*-*) ;; +*) { { $as_echo "$as_me:$LINENO: error: invalid value of canonical build" >&5 +$as_echo "$as_me: error: invalid value of canonical build" >&2;} + { (exit 1); exit 1; }; };; +esac +build=$ac_cv_build +ac_save_IFS=$IFS; IFS='-' +set x $ac_cv_build +shift +build_cpu=$1 +build_vendor=$2 +shift; shift +# Remember, the first character of IFS is used to create $*, +# except with old shells: +build_os=$* +IFS=$ac_save_IFS +case $build_os in *\ *) build_os=`echo "$build_os" | sed 's/ /-/g'`;; esac + + +{ $as_echo "$as_me:$LINENO: checking host system type" >&5 +$as_echo_n "checking host system type... " >&6; } +if test "${ac_cv_host+set}" = set; then + $as_echo_n "(cached) " >&6 +else + if test "x$host_alias" = x; then + ac_cv_host=$ac_cv_build +else + ac_cv_host=`$SHELL "$ac_aux_dir/config.sub" $host_alias` || + { { $as_echo "$as_me:$LINENO: error: $SHELL $ac_aux_dir/config.sub $host_alias failed" >&5 +$as_echo "$as_me: error: $SHELL $ac_aux_dir/config.sub $host_alias failed" >&2;} + { (exit 1); exit 1; }; } +fi + +fi +{ $as_echo "$as_me:$LINENO: result: $ac_cv_host" >&5 +$as_echo "$ac_cv_host" >&6; } +case $ac_cv_host in +*-*-*) ;; +*) { { $as_echo "$as_me:$LINENO: error: invalid value of canonical host" >&5 +$as_echo "$as_me: error: invalid value of canonical host" >&2;} + { (exit 1); exit 1; }; };; +esac +host=$ac_cv_host +ac_save_IFS=$IFS; IFS='-' +set x $ac_cv_host +shift +host_cpu=$1 +host_vendor=$2 +shift; shift +# Remember, the first character of IFS is used to create $*, +# except with old shells: +host_os=$* +IFS=$ac_save_IFS +case $host_os in *\ *) host_os=`echo "$host_os" | sed 's/ /-/g'`;; esac + + + +{ $as_echo "$as_me:$LINENO: checking for prefix" >&5 +$as_echo_n "checking for prefix... " >&6; } +if test x$prefix = xNONE; then + mutt_cv_prefix=$ac_default_prefix +else + mutt_cv_prefix=$prefix +fi +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_prefix" >&5 +$as_echo "$mutt_cv_prefix" >&6; } + +ac_ext=c +ac_cpp='$CPP $CPPFLAGS' +ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' +ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' +ac_compiler_gnu=$ac_cv_c_compiler_gnu +if test -n "$ac_tool_prefix"; then + # Extract the first word of "${ac_tool_prefix}gcc", so it can be a program name with args. +set dummy ${ac_tool_prefix}gcc; ac_word=$2 +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if test "${ac_cv_prog_CC+set}" = set; then + $as_echo_n "(cached) " >&6 +else + if test -n "$CC"; then + ac_cv_prog_CC="$CC" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then + ac_cv_prog_CC="${ac_tool_prefix}gcc" + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done +done +IFS=$as_save_IFS + +fi +fi +CC=$ac_cv_prog_CC +if test -n "$CC"; then + { $as_echo "$as_me:$LINENO: result: $CC" >&5 +$as_echo "$CC" >&6; } +else + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } +fi + + +fi +if test -z "$ac_cv_prog_CC"; then + ac_ct_CC=$CC + # Extract the first word of "gcc", so it can be a program name with args. +set dummy gcc; ac_word=$2 +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if test "${ac_cv_prog_ac_ct_CC+set}" = set; then + $as_echo_n "(cached) " >&6 +else + if test -n "$ac_ct_CC"; then + ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then + ac_cv_prog_ac_ct_CC="gcc" + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done +done +IFS=$as_save_IFS + +fi +fi +ac_ct_CC=$ac_cv_prog_ac_ct_CC +if test -n "$ac_ct_CC"; then + { $as_echo "$as_me:$LINENO: result: $ac_ct_CC" >&5 +$as_echo "$ac_ct_CC" >&6; } +else + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } +fi + + if test "x$ac_ct_CC" = x; then + CC="" + else + case $cross_compiling:$ac_tool_warned in +yes:) +{ $as_echo "$as_me:$LINENO: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} +ac_tool_warned=yes ;; +esac + CC=$ac_ct_CC + fi +else + CC="$ac_cv_prog_CC" +fi + +if test -z "$CC"; then + if test -n "$ac_tool_prefix"; then + # Extract the first word of "${ac_tool_prefix}cc", so it can be a program name with args. +set dummy ${ac_tool_prefix}cc; ac_word=$2 +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if test "${ac_cv_prog_CC+set}" = set; then + $as_echo_n "(cached) " >&6 +else + if test -n "$CC"; then + ac_cv_prog_CC="$CC" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then + ac_cv_prog_CC="${ac_tool_prefix}cc" + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done +done +IFS=$as_save_IFS + +fi +fi +CC=$ac_cv_prog_CC +if test -n "$CC"; then + { $as_echo "$as_me:$LINENO: result: $CC" >&5 +$as_echo "$CC" >&6; } +else + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } +fi + + + fi +fi +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 +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if test "${ac_cv_prog_CC+set}" = set; then + $as_echo_n "(cached) " >&6 +else + if test -n "$CC"; then + ac_cv_prog_CC="$CC" # Let the user override the test. +else + ac_prog_rejected=no +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then + if test "$as_dir/$ac_word$ac_exec_ext" = "/usr/ucb/cc"; then + ac_prog_rejected=yes + continue + fi + ac_cv_prog_CC="cc" + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done +done +IFS=$as_save_IFS + +if test $ac_prog_rejected = yes; then + # We found a bogon in the path, so make sure we never use it. + set dummy $ac_cv_prog_CC + shift + if test $# != 0; then + # We chose a different compiler from the bogus one. + # However, it has the same basename, so the bogon will be chosen + # first if we set CC to just the basename; use the full file name. + shift + ac_cv_prog_CC="$as_dir/$ac_word${1+' '}$@" + fi +fi +fi +fi +CC=$ac_cv_prog_CC +if test -n "$CC"; then + { $as_echo "$as_me:$LINENO: result: $CC" >&5 +$as_echo "$CC" >&6; } +else + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } +fi + + +fi +if test -z "$CC"; then + if test -n "$ac_tool_prefix"; then + for ac_prog in cl.exe + do + # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args. +set dummy $ac_tool_prefix$ac_prog; ac_word=$2 +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if test "${ac_cv_prog_CC+set}" = set; then + $as_echo_n "(cached) " >&6 +else + if test -n "$CC"; then + ac_cv_prog_CC="$CC" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then + ac_cv_prog_CC="$ac_tool_prefix$ac_prog" + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done +done +IFS=$as_save_IFS + +fi +fi +CC=$ac_cv_prog_CC +if test -n "$CC"; then + { $as_echo "$as_me:$LINENO: result: $CC" >&5 +$as_echo "$CC" >&6; } +else + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } +fi + + + test -n "$CC" && break + done +fi +if test -z "$CC"; then + ac_ct_CC=$CC + for ac_prog in cl.exe +do + # Extract the first word of "$ac_prog", so it can be a program name with args. +set dummy $ac_prog; ac_word=$2 +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if test "${ac_cv_prog_ac_ct_CC+set}" = set; then + $as_echo_n "(cached) " >&6 +else + if test -n "$ac_ct_CC"; then + ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then + ac_cv_prog_ac_ct_CC="$ac_prog" + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done +done +IFS=$as_save_IFS + +fi +fi +ac_ct_CC=$ac_cv_prog_ac_ct_CC +if test -n "$ac_ct_CC"; then + { $as_echo "$as_me:$LINENO: result: $ac_ct_CC" >&5 +$as_echo "$ac_ct_CC" >&6; } +else + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } +fi + + + test -n "$ac_ct_CC" && break +done + + if test "x$ac_ct_CC" = x; then + CC="" + else + case $cross_compiling:$ac_tool_warned in +yes:) +{ $as_echo "$as_me:$LINENO: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} +ac_tool_warned=yes ;; +esac + CC=$ac_ct_CC + fi +fi + +fi + + +test -z "$CC" && { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: no acceptable C compiler found in \$PATH +See \`config.log' for more details." >&5 +$as_echo "$as_me: error: no acceptable C compiler found in \$PATH +See \`config.log' for more details." >&2;} + { (exit 1); exit 1; }; }; } + +# Provide some information about the compiler. +$as_echo "$as_me:$LINENO: checking for C compiler version" >&5 +set X $ac_compile +ac_compiler=$2 +{ (ac_try="$ac_compiler --version >&5" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compiler --version >&5") 2>&5 + ac_status=$? + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } +{ (ac_try="$ac_compiler -v >&5" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compiler -v >&5") 2>&5 + ac_status=$? + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } +{ (ac_try="$ac_compiler -V >&5" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compiler -V >&5") 2>&5 + ac_status=$? + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } + +{ $as_echo "$as_me:$LINENO: checking whether we are using the GNU C compiler" >&5 +$as_echo_n "checking whether we are using the GNU C compiler... " >&6; } +if test "${ac_cv_c_compiler_gnu+set}" = set; then + $as_echo_n "(cached) " >&6 +else + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ + +int +main () +{ +#ifndef __GNUC__ + choke me +#endif + + ; + return 0; +} +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + ac_compiler_gnu=yes +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_compiler_gnu=no +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +ac_cv_c_compiler_gnu=$ac_compiler_gnu + +fi +{ $as_echo "$as_me:$LINENO: result: $ac_cv_c_compiler_gnu" >&5 +$as_echo "$ac_cv_c_compiler_gnu" >&6; } +if test $ac_compiler_gnu = yes; then + GCC=yes +else + GCC= +fi +ac_test_CFLAGS=${CFLAGS+set} +ac_save_CFLAGS=$CFLAGS +{ $as_echo "$as_me:$LINENO: checking whether $CC accepts -g" >&5 +$as_echo_n "checking whether $CC accepts -g... " >&6; } +if test "${ac_cv_prog_cc_g+set}" = set; then + $as_echo_n "(cached) " >&6 +else + ac_save_c_werror_flag=$ac_c_werror_flag + ac_c_werror_flag=yes + ac_cv_prog_cc_g=no + CFLAGS="-g" + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ + +int +main () +{ + + ; + return 0; +} +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + ac_cv_prog_cc_g=yes +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + CFLAGS="" + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ + +int +main () +{ + + ; + return 0; +} +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + : +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_c_werror_flag=$ac_save_c_werror_flag + CFLAGS="-g" + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ + +int +main () +{ + + ; + return 0; +} +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + ac_cv_prog_cc_g=yes +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext + ac_c_werror_flag=$ac_save_c_werror_flag +fi +{ $as_echo "$as_me:$LINENO: result: $ac_cv_prog_cc_g" >&5 +$as_echo "$ac_cv_prog_cc_g" >&6; } +if test "$ac_test_CFLAGS" = set; then + CFLAGS=$ac_save_CFLAGS +elif test $ac_cv_prog_cc_g = yes; then + if test "$GCC" = yes; then + CFLAGS="-g -O2" + else + CFLAGS="-g" + fi +else + if test "$GCC" = yes; then + CFLAGS="-O2" + else + CFLAGS= + fi +fi +{ $as_echo "$as_me:$LINENO: checking for $CC option to accept ISO C89" >&5 +$as_echo_n "checking for $CC option to accept ISO C89... " >&6; } +if test "${ac_cv_prog_cc_c89+set}" = set; then + $as_echo_n "(cached) " >&6 +else + ac_cv_prog_cc_c89=no +ac_save_CC=$CC +cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +#include +#include +#include +#include +/* Most of the following tests are stolen from RCS 5.7's src/conf.sh. */ +struct buf { int x; }; +FILE * (*rcsopen) (struct buf *, struct stat *, int); +static char *e (p, i) + char **p; + int i; +{ + return p[i]; +} +static char *f (char * (*g) (char **, int), char **p, ...) +{ + char *s; + va_list v; + va_start (v,p); + s = g (p, va_arg (v,int)); + va_end (v); + return s; +} + +/* OSF 4.0 Compaq cc is some sort of almost-ANSI by default. It has + function prototypes and stuff, but not '\xHH' hex character constants. + These don't provoke an error unfortunately, instead are silently treated + as 'x'. The following induces an error, until -std is added to get + proper ANSI mode. Curiously '\x00'!='x' always comes out true, for an + array size at least. It's necessary to write '\x00'==0 to get something + that's true only with -std. */ +int osf4_cc_array ['\x00' == 0 ? 1 : -1]; + +/* IBM C 6 for AIX is almost-ANSI by default, but it replaces macro parameters + inside strings and character constants. */ +#define FOO(x) 'x' +int xlc6_cc_array[FOO(a) == 'x' ? 1 : -1]; + +int test (int i, double x); +struct s1 {int (*f) (int a);}; +struct s2 {int (*f) (double a);}; +int pairnames (int, char **, FILE *(*)(struct buf *, struct stat *, int), int, int); +int argc; +char **argv; +int +main () +{ +return f (e, argv, 0) != argv[0] || f (e, argv, 1) != argv[1]; + ; + return 0; +} +_ACEOF +for ac_arg in '' -qlanglvl=extc89 -qlanglvl=ansi -std \ + -Ae "-Aa -D_HPUX_SOURCE" "-Xc -D__EXTENSIONS__" +do + CC="$ac_save_CC $ac_arg" + rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + ac_cv_prog_cc_c89=$ac_arg +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + +fi + +rm -f core conftest.err conftest.$ac_objext + test "x$ac_cv_prog_cc_c89" != "xno" && break +done +rm -f conftest.$ac_ext +CC=$ac_save_CC + +fi +# AC_CACHE_VAL +case "x$ac_cv_prog_cc_c89" in + x) + { $as_echo "$as_me:$LINENO: result: none needed" >&5 +$as_echo "none needed" >&6; } ;; + xno) + { $as_echo "$as_me:$LINENO: result: unsupported" >&5 +$as_echo "unsupported" >&6; } ;; + *) + CC="$CC $ac_cv_prog_cc_c89" + { $as_echo "$as_me:$LINENO: result: $ac_cv_prog_cc_c89" >&5 +$as_echo "$ac_cv_prog_cc_c89" >&6; } ;; +esac + + +ac_ext=c +ac_cpp='$CPP $CPPFLAGS' +ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' +ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' +ac_compiler_gnu=$ac_cv_c_compiler_gnu + +depcc="$CC" am_compiler_list= + +{ $as_echo "$as_me:$LINENO: checking dependency style of $depcc" >&5 +$as_echo_n "checking dependency style of $depcc... " >&6; } +if test "${am_cv_CC_dependencies_compiler_type+set}" = set; then + $as_echo_n "(cached) " >&6 +else + if test -z "$AMDEP_TRUE" && test -f "$am_depcomp"; then + # We make a subdir and do the tests there. Otherwise we can end up + # making bogus files that we don't know about and never remove. For + # instance it was reported that on HP-UX the gcc test will end up + # making a dummy file named `D' -- because `-MD' means `put the output + # in D'. + mkdir conftest.dir + # Copy depcomp to subdir because otherwise we won't find it if we're + # using a relative directory. + cp "$am_depcomp" conftest.dir + cd conftest.dir + # We will build objects and dependencies in a subdirectory because + # it helps to detect inapplicable dependency modes. For instance + # both Tru64's cc and ICC support -MD to output dependencies as a + # side effect of compilation, but ICC will put the dependencies in + # the current directory while Tru64 will put them in the object + # directory. + mkdir sub + + am_cv_CC_dependencies_compiler_type=none + if test "$am_compiler_list" = ""; then + am_compiler_list=`sed -n 's/^#*\([a-zA-Z0-9]*\))$/\1/p' < ./depcomp` + fi + am__universal=false + case " $depcc " in #( + *\ -arch\ *\ -arch\ *) am__universal=true ;; + esac + + for depmode in $am_compiler_list; do + # Setup a source with many dependencies, because some compilers + # like to wrap large dependency lists on column 80 (with \), and + # we should not choose a depcomp mode which is confused by this. + # + # We need to recreate these files for each test, as the compiler may + # overwrite some of them when testing with obscure command lines. + # This happens at least with the AIX C compiler. + : > sub/conftest.c + for i in 1 2 3 4 5 6; do + echo '#include "conftst'$i'.h"' >> sub/conftest.c + # Using `: > sub/conftst$i.h' creates only sub/conftst1.h with + # Solaris 8's {/usr,}/bin/sh. + touch sub/conftst$i.h + done + echo "${am__include} ${am__quote}sub/conftest.Po${am__quote}" > confmf + + # We check with `-c' and `-o' for the sake of the "dashmstdout" + # mode. It turns out that the SunPro C++ compiler does not properly + # handle `-M -o', and we need to detect this. Also, some Intel + # versions had trouble with output in subdirs + am__obj=sub/conftest.${OBJEXT-o} + am__minus_obj="-o $am__obj" + case $depmode in + gcc) + # This depmode causes a compiler race in universal mode. + test "$am__universal" = false || continue + ;; + nosideeffect) + # after this tag, mechanisms are not by side-effect, so they'll + # only be used when explicitly requested + if test "x$enable_dependency_tracking" = xyes; then + continue + else + break + fi + ;; + msvisualcpp | msvcmsys) + # This compiler won't grok `-c -o', but also, the minuso test has + # not run yet. These depmodes are late enough in the game, and + # so weak that their functioning should not be impacted. + am__obj=conftest.${OBJEXT-o} + am__minus_obj= + ;; + none) break ;; + esac + if depmode=$depmode \ + source=sub/conftest.c object=$am__obj \ + depfile=sub/conftest.Po tmpdepfile=sub/conftest.TPo \ + $SHELL ./depcomp $depcc -c $am__minus_obj sub/conftest.c \ + >/dev/null 2>conftest.err && + grep sub/conftst1.h sub/conftest.Po > /dev/null 2>&1 && + grep sub/conftst6.h sub/conftest.Po > /dev/null 2>&1 && + grep $am__obj sub/conftest.Po > /dev/null 2>&1 && + ${MAKE-make} -s -f confmf > /dev/null 2>&1; then + # icc doesn't choke on unknown options, it will just issue warnings + # or remarks (even with -Werror). So we grep stderr for any message + # that says an option was ignored or not supported. + # When given -MP, icc 7.0 and 7.1 complain thusly: + # icc: Command line warning: ignoring option '-M'; no argument required + # The diagnosis changed in icc 8.0: + # icc: Command line remark: option '-MP' not supported + if (grep 'ignoring option' conftest.err || + grep 'not supported' conftest.err) >/dev/null 2>&1; then :; else + am_cv_CC_dependencies_compiler_type=$depmode + break + fi + fi + done + + cd .. + rm -rf conftest.dir +else + am_cv_CC_dependencies_compiler_type=none +fi + +fi +{ $as_echo "$as_me:$LINENO: result: $am_cv_CC_dependencies_compiler_type" >&5 +$as_echo "$am_cv_CC_dependencies_compiler_type" >&6; } +CCDEPMODE=depmode=$am_cv_CC_dependencies_compiler_type + + if + test "x$enable_dependency_tracking" != xno \ + && test "$am_cv_CC_dependencies_compiler_type" = gcc3; then + am__fastdepCC_TRUE= + am__fastdepCC_FALSE='#' else - ac_cv_header_stdc=no + am__fastdepCC_TRUE='#' + am__fastdepCC_FALSE= fi -rm -f conftest* -fi -if test $ac_cv_header_stdc = yes; then - # /bin/cc in Irix-4.0.5 gets non-ANSI ctype macros unless using -ansi. - if test "$cross_compiling" = yes; then - : + + { $as_echo "$as_me:$LINENO: checking for strerror in -lcposix" >&5 +$as_echo_n "checking for strerror in -lcposix... " >&6; } +if test "${ac_cv_lib_cposix_strerror+set}" = set; then + $as_echo_n "(cached) " >&6 else - cat >conftest.$ac_ext <<_ACEOF + ac_check_lib_save_LIBS=$LIBS +LIBS="-lcposix $LIBS" +cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ -#include -#include -#if ((' ' & 0x0FF) == 0x020) -# define ISLOWER(c) ('a' <= (c) && (c) <= 'z') -# define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c)) -#else -# define ISLOWER(c) \ - (('a' <= (c) && (c) <= 'i') \ - || ('j' <= (c) && (c) <= 'r') \ - || ('s' <= (c) && (c) <= 'z')) -# define TOUPPER(c) (ISLOWER(c) ? ((c) | 0x40) : (c)) -#endif -#define XOR(e, f) (((e) && !(f)) || (!(e) && (f))) +/* Override any GCC internal prototype to avoid an error. + Use char because int might match the return type of a GCC + builtin and then its argument prototype would still apply. */ +#ifdef __cplusplus +extern "C" +#endif +char strerror (); int main () { - int i; - for (i = 0; i < 256; i++) - if (XOR (islower (i), ISLOWER (i)) - || toupper (i) != TOUPPER (i)) - return 2; +return strerror (); + ; return 0; } _ACEOF -rm -f conftest$ac_exeext +rm -f conftest.$ac_objext conftest$ac_exeext if { (ac_try="$ac_link" case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_link") 2>&5 - ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); } && { ac_try='./conftest$ac_exeext' - { (case "(($ac_try" in - *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; - *) ac_try_echo=$ac_try;; -esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_try") 2>&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_link") 2>conftest.er1 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); }; }; then - : + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then + ac_cv_lib_cposix_strerror=yes else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 -( exit $ac_status ) -ac_cv_header_stdc=no -fi -rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext + ac_cv_lib_cposix_strerror=no fi - -fi +rm -rf conftest.dSYM +rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ + conftest$ac_exeext conftest.$ac_ext +LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_header_stdc" >&5 -echo "${ECHO_T}$ac_cv_header_stdc" >&6; } -if test $ac_cv_header_stdc = yes; then - -cat >>confdefs.h <<\_ACEOF -#define STDC_HEADERS 1 -_ACEOF - +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_cposix_strerror" >&5 +$as_echo "$ac_cv_lib_cposix_strerror" >&6; } +if test "x$ac_cv_lib_cposix_strerror" = x""yes; then + LIBS="$LIBS -lcposix" fi -# On IRIX 5.3, sys/types and inttypes.h are conflicting. - - - +{ $as_echo "$as_me:$LINENO: checking for function prototypes" >&5 +$as_echo_n "checking for function prototypes... " >&6; } +if test "$ac_cv_prog_cc_c89" != no; then + { $as_echo "$as_me:$LINENO: result: yes" >&5 +$as_echo "yes" >&6; } - - - -for ac_header in sys/types.h sys/stat.h stdlib.h string.h memory.h strings.h \ - inttypes.h stdint.h unistd.h -do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } -if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - cat >conftest.$ac_ext <<_ACEOF -/* confdefs.h. */ -_ACEOF -cat confdefs.h >>conftest.$ac_ext -cat >>conftest.$ac_ext <<_ACEOF -/* end confdefs.h. */ -$ac_includes_default - -#include <$ac_header> +cat >>confdefs.h <<\_ACEOF +#define PROTOTYPES 1 _ACEOF -rm -f conftest.$ac_objext -if { (ac_try="$ac_compile" -case "(($ac_try" in - *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; - *) ac_try_echo=$ac_try;; -esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_compile") 2>conftest.er1 - ac_status=$? - grep -v '^ *+' conftest.er1 >conftest.err - rm -f conftest.er1 - cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); } && { - test -z "$ac_c_werror_flag" || - test ! -s conftest.err - } && test -s conftest.$ac_objext; then - eval "$as_ac_Header=yes" -else - echo "$as_me: failed program was:" >&5 -sed 's/^/| /' conftest.$ac_ext >&5 - eval "$as_ac_Header=no" -fi -rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_Header'}'` = yes; then - cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +cat >>confdefs.h <<\_ACEOF +#define __PROTOTYPES 1 _ACEOF +else + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi -done - - if test "$ac_cv_prog_cc_stdc" != no; then U= ANSI2KNR= @@ -4267,20 +5480,21 @@ fi for ac_header in string.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -4296,32 +5510,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -4335,69 +5550,73 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi @@ -4406,8 +5625,8 @@ done if test "x$U" != "x"; then - { { echo "$as_me:$LINENO: error: Compiler not ANSI compliant" >&5 -echo "$as_me: error: Compiler not ANSI compliant" >&2;} + { { $as_echo "$as_me:$LINENO: error: Compiler not ANSI compliant" >&5 +$as_echo "$as_me: error: Compiler not ANSI compliant" >&2;} { (exit 1); exit 1; }; } fi ac_ext=c @@ -4415,15 +5634,15 @@ ac_cpp='$CPP $CPPFLAGS' ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' ac_compiler_gnu=$ac_cv_c_compiler_gnu -{ echo "$as_me:$LINENO: checking how to run the C preprocessor" >&5 -echo $ECHO_N "checking how to run the C preprocessor... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking how to run the C preprocessor" >&5 +$as_echo_n "checking how to run the C preprocessor... " >&6; } # On Suns, sometimes $CPP names a directory. if test -n "$CPP" && test -d "$CPP"; then CPP= fi if test -z "$CPP"; then if test "${ac_cv_prog_CPP+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else # Double quotes because CPP needs to be expanded for CPP in "$CC -E" "$CC -E -traditional-cpp" "/lib/cpp" @@ -4455,20 +5674,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then : else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 # Broken: fails on valid input. @@ -4492,13 +5712,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err @@ -4506,7 +5727,7 @@ eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 # Broken: success on invalid input. continue else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 # Passes both tests. @@ -4531,8 +5752,8 @@ fi else ac_cv_prog_CPP=$CPP fi -{ echo "$as_me:$LINENO: result: $CPP" >&5 -echo "${ECHO_T}$CPP" >&6; } +{ $as_echo "$as_me:$LINENO: result: $CPP" >&5 +$as_echo "$CPP" >&6; } ac_preproc_ok=false for ac_c_preproc_warn_flag in '' yes do @@ -4560,20 +5781,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then : else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 # Broken: fails on valid input. @@ -4597,13 +5819,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err @@ -4611,7 +5834,7 @@ eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 # Broken: success on invalid input. continue else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 # Passes both tests. @@ -4627,11 +5850,13 @@ rm -f conftest.err conftest.$ac_ext if $ac_preproc_ok; then : else - { { echo "$as_me:$LINENO: error: C preprocessor \"$CPP\" fails sanity check + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: C preprocessor \"$CPP\" fails sanity check See \`config.log' for more details." >&5 -echo "$as_me: error: C preprocessor \"$CPP\" fails sanity check +$as_echo "$as_me: error: C preprocessor \"$CPP\" fails sanity check See \`config.log' for more details." >&2;} - { (exit 1); exit 1; }; } + { (exit 1); exit 1; }; }; } fi ac_ext=c @@ -4640,11 +5865,12 @@ ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' ac_compiler_gnu=$ac_cv_c_compiler_gnu -{ echo "$as_me:$LINENO: checking whether ${MAKE-make} sets \$(MAKE)" >&5 -echo $ECHO_N "checking whether ${MAKE-make} sets \$(MAKE)... $ECHO_C" >&6; } -set x ${MAKE-make}; ac_make=`echo "$2" | sed 's/+/p/g; s/[^a-zA-Z0-9_]/_/g'` +{ $as_echo "$as_me:$LINENO: checking whether ${MAKE-make} sets \$(MAKE)" >&5 +$as_echo_n "checking whether ${MAKE-make} sets \$(MAKE)... " >&6; } +set x ${MAKE-make} +ac_make=`$as_echo "$2" | sed 's/+/p/g; s/[^a-zA-Z0-9_]/_/g'` if { as_var=ac_cv_prog_make_${ac_make}_set; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.make <<\_ACEOF SHELL = /bin/sh @@ -4661,12 +5887,12 @@ esac rm -f conftest.make fi if eval test \$ac_cv_prog_make_${ac_make}_set = yes; then - { echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } + { $as_echo "$as_me:$LINENO: result: yes" >&5 +$as_echo "yes" >&6; } SET_MAKE= else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } SET_MAKE="MAKE=${MAKE-make}" fi @@ -4683,11 +5909,12 @@ fi # SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff" # OS/2's system install, which has a completely different semantic # ./install, which can be erroneously created by make from ./install.sh. -{ echo "$as_me:$LINENO: checking for a BSD-compatible install" >&5 -echo $ECHO_N "checking for a BSD-compatible install... $ECHO_C" >&6; } +# Reject install programs that cannot install multiple files. +{ $as_echo "$as_me:$LINENO: checking for a BSD-compatible install" >&5 +$as_echo_n "checking for a BSD-compatible install... " >&6; } if test -z "$INSTALL"; then if test "${ac_cv_path_install+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else as_save_IFS=$IFS; IFS=$PATH_SEPARATOR for as_dir in $PATH @@ -4716,17 +5943,29 @@ case $as_dir/ in # program-specific install script used by HP pwplus--don't use. : else - ac_cv_path_install="$as_dir/$ac_prog$ac_exec_ext -c" - break 3 + rm -rf conftest.one conftest.two conftest.dir + echo one > conftest.one + echo two > conftest.two + mkdir conftest.dir + if "$as_dir/$ac_prog$ac_exec_ext" -c conftest.one conftest.two "`pwd`/conftest.dir" && + test -s conftest.one && test -s conftest.two && + test -s conftest.dir/conftest.one && + test -s conftest.dir/conftest.two + then + ac_cv_path_install="$as_dir/$ac_prog$ac_exec_ext -c" + break 3 + fi fi fi done done ;; esac + done IFS=$as_save_IFS +rm -rf conftest.one conftest.two conftest.dir fi if test "${ac_cv_path_install+set}" = set; then @@ -4739,8 +5978,8 @@ fi INSTALL=$ac_install_sh fi fi -{ echo "$as_me:$LINENO: result: $INSTALL" >&5 -echo "${ECHO_T}$INSTALL" >&6; } +{ $as_echo "$as_me:$LINENO: result: $INSTALL" >&5 +$as_echo "$INSTALL" >&6; } # Use test -z because SunOS4 sh mishandles braces in ${var-val}. # It thinks the first close brace ends the variable substitution. @@ -4753,10 +5992,10 @@ test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644' if test -n "$ac_tool_prefix"; then # Extract the first word of "${ac_tool_prefix}ranlib", so it can be a program name with args. set dummy ${ac_tool_prefix}ranlib; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_prog_RANLIB+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test -n "$RANLIB"; then ac_cv_prog_RANLIB="$RANLIB" # Let the user override the test. @@ -4769,7 +6008,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_prog_RANLIB="${ac_tool_prefix}ranlib" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -4780,11 +6019,11 @@ fi fi RANLIB=$ac_cv_prog_RANLIB if test -n "$RANLIB"; then - { echo "$as_me:$LINENO: result: $RANLIB" >&5 -echo "${ECHO_T}$RANLIB" >&6; } + { $as_echo "$as_me:$LINENO: result: $RANLIB" >&5 +$as_echo "$RANLIB" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -4793,10 +6032,10 @@ if test -z "$ac_cv_prog_RANLIB"; then ac_ct_RANLIB=$RANLIB # Extract the first word of "ranlib", so it can be a program name with args. set dummy ranlib; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_prog_ac_ct_RANLIB+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test -n "$ac_ct_RANLIB"; then ac_cv_prog_ac_ct_RANLIB="$ac_ct_RANLIB" # Let the user override the test. @@ -4809,7 +6048,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_prog_ac_ct_RANLIB="ranlib" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -4820,11 +6059,11 @@ fi fi ac_ct_RANLIB=$ac_cv_prog_ac_ct_RANLIB if test -n "$ac_ct_RANLIB"; then - { echo "$as_me:$LINENO: result: $ac_ct_RANLIB" >&5 -echo "${ECHO_T}$ac_ct_RANLIB" >&6; } + { $as_echo "$as_me:$LINENO: result: $ac_ct_RANLIB" >&5 +$as_echo "$ac_ct_RANLIB" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi if test "x$ac_ct_RANLIB" = x; then @@ -4832,12 +6071,8 @@ fi else case $cross_compiling:$ac_tool_warned in yes:) -{ echo "$as_me:$LINENO: WARNING: In the future, Autoconf will not detect cross-tools -whose name does not start with the host triplet. If you think this -configuration is useful to you, please write to autoconf@gnu.org." >&5 -echo "$as_me: WARNING: In the future, Autoconf will not detect cross-tools -whose name does not start with the host triplet. If you think this -configuration is useful to you, please write to autoconf@gnu.org." >&2;} +{ $as_echo "$as_me:$LINENO: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} ac_tool_warned=yes ;; esac RANLIB=$ac_ct_RANLIB @@ -4849,10 +6084,10 @@ fi if test -n "$ac_tool_prefix"; then # Extract the first word of "${ac_tool_prefix}ar", so it can be a program name with args. set dummy ${ac_tool_prefix}ar; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_prog_AR+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test -n "$AR"; then ac_cv_prog_AR="$AR" # Let the user override the test. @@ -4865,7 +6100,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_prog_AR="${ac_tool_prefix}ar" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -4876,11 +6111,11 @@ fi fi AR=$ac_cv_prog_AR if test -n "$AR"; then - { echo "$as_me:$LINENO: result: $AR" >&5 -echo "${ECHO_T}$AR" >&6; } + { $as_echo "$as_me:$LINENO: result: $AR" >&5 +$as_echo "$AR" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -4889,10 +6124,10 @@ if test -z "$ac_cv_prog_AR"; then ac_ct_AR=$AR # Extract the first word of "ar", so it can be a program name with args. set dummy ar; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_prog_ac_ct_AR+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test -n "$ac_ct_AR"; then ac_cv_prog_ac_ct_AR="$ac_ct_AR" # Let the user override the test. @@ -4905,7 +6140,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_prog_ac_ct_AR="ar" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -4916,11 +6151,11 @@ fi fi ac_ct_AR=$ac_cv_prog_ac_ct_AR if test -n "$ac_ct_AR"; then - { echo "$as_me:$LINENO: result: $ac_ct_AR" >&5 -echo "${ECHO_T}$ac_ct_AR" >&6; } + { $as_echo "$as_me:$LINENO: result: $ac_ct_AR" >&5 +$as_echo "$ac_ct_AR" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi if test "x$ac_ct_AR" = x; then @@ -4928,12 +6163,8 @@ fi else case $cross_compiling:$ac_tool_warned in yes:) -{ echo "$as_me:$LINENO: WARNING: In the future, Autoconf will not detect cross-tools -whose name does not start with the host triplet. If you think this -configuration is useful to you, please write to autoconf@gnu.org." >&5 -echo "$as_me: WARNING: In the future, Autoconf will not detect cross-tools -whose name does not start with the host triplet. If you think this -configuration is useful to you, please write to autoconf@gnu.org." >&2;} +{ $as_echo "$as_me:$LINENO: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} ac_tool_warned=yes ;; esac AR=$ac_ct_AR @@ -4943,10 +6174,10 @@ else fi -{ echo "$as_me:$LINENO: checking for inline" >&5 -echo $ECHO_N "checking for inline... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for inline" >&5 +$as_echo_n "checking for inline... " >&6; } if test "${ac_cv_c_inline+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_cv_c_inline=no for ac_kw in inline __inline__ __inline; do @@ -4969,20 +6200,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_c_inline=$ac_kw else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -4993,8 +6225,8 @@ rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext done fi -{ echo "$as_me:$LINENO: result: $ac_cv_c_inline" >&5 -echo "${ECHO_T}$ac_cv_c_inline" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_c_inline" >&5 +$as_echo "$ac_cv_c_inline" >&6; } case $ac_cv_c_inline in @@ -5012,10 +6244,10 @@ _ACEOF ;; esac -{ echo "$as_me:$LINENO: checking for an ANSI C-conforming const" >&5 -echo $ECHO_N "checking for an ANSI C-conforming const... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for an ANSI C-conforming const" >&5 +$as_echo_n "checking for an ANSI C-conforming const... " >&6; } if test "${ac_cv_c_const+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -5087,20 +6319,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_c_const=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_c_const=no @@ -5108,38 +6341,184 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_c_const" >&5 -echo "${ECHO_T}$ac_cv_c_const" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_c_const" >&5 +$as_echo "$ac_cv_c_const" >&6; } if test $ac_cv_c_const = no; then cat >>confdefs.h <<\_ACEOF -#define const +#define const /**/ _ACEOF fi -{ echo "$as_me:$LINENO: checking whether byte ordering is bigendian" >&5 -echo $ECHO_N "checking whether byte ordering is bigendian... $ECHO_C" >&6; } + + { $as_echo "$as_me:$LINENO: checking whether byte ordering is bigendian" >&5 +$as_echo_n "checking whether byte ordering is bigendian... " >&6; } if test "${ac_cv_c_bigendian+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else - # See if sys/param.h defines the BYTE_ORDER macro. -cat >conftest.$ac_ext <<_ACEOF + ac_cv_c_bigendian=unknown + # See if we're dealing with a universal compiler. + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +#ifndef __APPLE_CC__ + not a universal capable compiler + #endif + typedef int dummy; + +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + + # Check for potential -arch flags. It is not universal unless + # there are some -arch flags. Note that *ppc* also matches + # ppc64. This check is also rather less than ideal. + case "${CC} ${CFLAGS} ${CPPFLAGS} ${LDFLAGS}" in #( + *-arch*ppc*|*-arch*i386*|*-arch*x86_64*) ac_cv_c_bigendian=universal;; + esac +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext + if test $ac_cv_c_bigendian = unknown; then + # See if sys/param.h defines the BYTE_ORDER macro. + cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ #include -#include + #include + +int +main () +{ +#if ! (defined BYTE_ORDER && defined BIG_ENDIAN \ + && defined LITTLE_ENDIAN && BYTE_ORDER && BIG_ENDIAN \ + && LITTLE_ENDIAN) + bogus endian macros + #endif + + ; + return 0; +} +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + # It does; now see whether it defined to BIG_ENDIAN or not. + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +#include + #include + +int +main () +{ +#if BYTE_ORDER != BIG_ENDIAN + not big endian + #endif + + ; + return 0; +} +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + ac_cv_c_bigendian=yes +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_cv_c_bigendian=no +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext + fi + if test $ac_cv_c_bigendian = unknown; then + # See if defines _LITTLE_ENDIAN or _BIG_ENDIAN (e.g., Solaris). + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +#include int main () { -#if ! (defined BYTE_ORDER && defined BIG_ENDIAN && defined LITTLE_ENDIAN \ - && BYTE_ORDER && BIG_ENDIAN && LITTLE_ENDIAN) - bogus endian macros -#endif +#if ! (defined _LITTLE_ENDIAN || defined _BIG_ENDIAN) + bogus endian macros + #endif ; return 0; @@ -5151,33 +6530,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then - # It does; now see whether it defined to BIG_ENDIAN or not. -cat >conftest.$ac_ext <<_ACEOF + # It does; now see whether it defined to _BIG_ENDIAN or not. + cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ -#include -#include +#include int main () { -#if BYTE_ORDER != BIG_ENDIAN - not big endian -#endif +#ifndef _BIG_ENDIAN + not big endian + #endif ; return 0; @@ -5189,20 +6568,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_c_bigendian=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_c_bigendian=no @@ -5210,29 +6590,44 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 - # It does not; compile a test program. -if test "$cross_compiling" = yes; then - # try to guess the endianness by grepping values into an object file - ac_cv_c_bigendian=unknown - cat >conftest.$ac_ext <<_ACEOF + +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext + fi + if test $ac_cv_c_bigendian = unknown; then + # Compile a test program. + if test "$cross_compiling" = yes; then + # Try to guess by grepping values from an object file. + cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ -short int ascii_mm[] = { 0x4249, 0x4765, 0x6E44, 0x6961, 0x6E53, 0x7953, 0 }; -short int ascii_ii[] = { 0x694C, 0x5454, 0x656C, 0x6E45, 0x6944, 0x6E61, 0 }; -void _ascii () { char *s = (char *) ascii_mm; s = (char *) ascii_ii; } -short int ebcdic_ii[] = { 0x89D3, 0xE3E3, 0x8593, 0x95C5, 0x89C4, 0x9581, 0 }; -short int ebcdic_mm[] = { 0xC2C9, 0xC785, 0x95C4, 0x8981, 0x95E2, 0xA8E2, 0 }; -void _ebcdic () { char *s = (char *) ebcdic_mm; s = (char *) ebcdic_ii; } +short int ascii_mm[] = + { 0x4249, 0x4765, 0x6E44, 0x6961, 0x6E53, 0x7953, 0 }; + short int ascii_ii[] = + { 0x694C, 0x5454, 0x656C, 0x6E45, 0x6944, 0x6E61, 0 }; + int use_ascii (int i) { + return ascii_mm[i] + ascii_ii[i]; + } + short int ebcdic_ii[] = + { 0x89D3, 0xE3E3, 0x8593, 0x95C5, 0x89C4, 0x9581, 0 }; + short int ebcdic_mm[] = + { 0xC2C9, 0xC785, 0x95C4, 0x8981, 0x95E2, 0xA8E2, 0 }; + int use_ebcdic (int i) { + return ebcdic_mm[i] + ebcdic_ii[i]; + } + extern int foo; + int main () { - _ascii (); _ebcdic (); +return use_ascii (foo) == use_ebcdic (foo); ; return 0; } @@ -5243,30 +6638,31 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then - if grep BIGenDianSyS conftest.$ac_objext >/dev/null ; then - ac_cv_c_bigendian=yes -fi -if grep LiTTleEnDian conftest.$ac_objext >/dev/null ; then - if test "$ac_cv_c_bigendian" = unknown; then - ac_cv_c_bigendian=no - else - # finding both strings is unlikely to happen, but who knows? - ac_cv_c_bigendian=unknown - fi -fi -else - echo "$as_me: failed program was:" >&5 + if grep BIGenDianSyS conftest.$ac_objext >/dev/null; then + ac_cv_c_bigendian=yes + fi + if grep LiTTleEnDian conftest.$ac_objext >/dev/null ; then + if test "$ac_cv_c_bigendian" = unknown; then + ac_cv_c_bigendian=no + else + # finding both strings is unlikely to happen, but who knows? + ac_cv_c_bigendian=unknown + fi + fi +else + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -5285,14 +6681,14 @@ int main () { - /* Are we little or big endian? From Harbison&Steele. */ - union - { - long int l; - char c[sizeof (long int)]; - } u; - u.l = 1; - return u.c[sizeof (long int) - 1] == 1; + /* Are we little or big endian? From Harbison&Steele. */ + union + { + long int l; + char c[sizeof (long int)]; + } u; + u.l = 1; + return u.c[sizeof (long int) - 1] == 1; ; return 0; @@ -5304,55 +6700,62 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then ac_cv_c_bigendian=no else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) ac_cv_c_bigendian=yes fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi + fi fi - -rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -fi -{ echo "$as_me:$LINENO: result: $ac_cv_c_bigendian" >&5 -echo "${ECHO_T}$ac_cv_c_bigendian" >&6; } -case $ac_cv_c_bigendian in - yes) +{ $as_echo "$as_me:$LINENO: result: $ac_cv_c_bigendian" >&5 +$as_echo "$ac_cv_c_bigendian" >&6; } + case $ac_cv_c_bigendian in #( + yes) + cat >>confdefs.h <<\_ACEOF +#define WORDS_BIGENDIAN 1 +_ACEOF +;; #( + no) + ;; #( + universal) cat >>confdefs.h <<\_ACEOF -#define WORDS_BIGENDIAN 1 +#define AC_APPLE_UNIVERSAL_BUILD 1 _ACEOF - ;; - no) - ;; - *) - { { echo "$as_me:$LINENO: error: unknown endianness -presetting ac_cv_c_bigendian=no (or yes) will help" >&5 -echo "$as_me: error: unknown endianness -presetting ac_cv_c_bigendian=no (or yes) will help" >&2;} + + ;; #( + *) + { { $as_echo "$as_me:$LINENO: error: unknown endianness + presetting ac_cv_c_bigendian=no (or yes) will help" >&5 +$as_echo "$as_me: error: unknown endianness + presetting ac_cv_c_bigendian=no (or yes) will help" >&2;} { (exit 1); exit 1; }; } ;; -esac + esac # Check whether --enable-largefile was given. @@ -5362,10 +6765,10 @@ fi if test "$enable_largefile" != no; then - { echo "$as_me:$LINENO: checking for special C compiler options needed for large files" >&5 -echo $ECHO_N "checking for special C compiler options needed for large files... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for special C compiler options needed for large files" >&5 +$as_echo_n "checking for special C compiler options needed for large files... " >&6; } if test "${ac_cv_sys_largefile_CC+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_cv_sys_largefile_CC=no if test "$GCC" != yes; then @@ -5402,20 +6805,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -5429,20 +6833,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_sys_largefile_CC=' -n32'; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -5455,16 +6860,16 @@ rm -f core conftest.err conftest.$ac_objext rm -f conftest.$ac_ext fi fi -{ echo "$as_me:$LINENO: result: $ac_cv_sys_largefile_CC" >&5 -echo "${ECHO_T}$ac_cv_sys_largefile_CC" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_sys_largefile_CC" >&5 +$as_echo "$ac_cv_sys_largefile_CC" >&6; } if test "$ac_cv_sys_largefile_CC" != no; then CC=$CC$ac_cv_sys_largefile_CC fi - { echo "$as_me:$LINENO: checking for _FILE_OFFSET_BITS value needed for large files" >&5 -echo $ECHO_N "checking for _FILE_OFFSET_BITS value needed for large files... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for _FILE_OFFSET_BITS value needed for large files" >&5 +$as_echo_n "checking for _FILE_OFFSET_BITS value needed for large files... " >&6; } if test "${ac_cv_sys_file_offset_bits+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else while :; do cat >conftest.$ac_ext <<_ACEOF @@ -5496,20 +6901,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_sys_file_offset_bits=no; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -5546,20 +6952,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_sys_file_offset_bits=64; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -5570,8 +6977,8 @@ rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext break done fi -{ echo "$as_me:$LINENO: result: $ac_cv_sys_file_offset_bits" >&5 -echo "${ECHO_T}$ac_cv_sys_file_offset_bits" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_sys_file_offset_bits" >&5 +$as_echo "$ac_cv_sys_file_offset_bits" >&6; } case $ac_cv_sys_file_offset_bits in #( no | unknown) ;; *) @@ -5580,12 +6987,12 @@ cat >>confdefs.h <<_ACEOF _ACEOF ;; esac -rm -f conftest* +rm -rf conftest* if test $ac_cv_sys_file_offset_bits = unknown; then - { echo "$as_me:$LINENO: checking for _LARGE_FILES value needed for large files" >&5 -echo $ECHO_N "checking for _LARGE_FILES value needed for large files... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for _LARGE_FILES value needed for large files" >&5 +$as_echo_n "checking for _LARGE_FILES value needed for large files... " >&6; } if test "${ac_cv_sys_large_files+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else while :; do cat >conftest.$ac_ext <<_ACEOF @@ -5617,20 +7024,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_sys_large_files=no; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -5667,20 +7075,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_sys_large_files=1; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -5691,8 +7100,8 @@ rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext break done fi -{ echo "$as_me:$LINENO: result: $ac_cv_sys_large_files" >&5 -echo "${ECHO_T}$ac_cv_sys_large_files" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_sys_large_files" >&5 +$as_echo "$ac_cv_sys_large_files" >&6; } case $ac_cv_sys_large_files in #( no | unknown) ;; *) @@ -5701,14 +7110,14 @@ cat >>confdefs.h <<_ACEOF _ACEOF ;; esac -rm -f conftest* +rm -rf conftest* fi fi -{ echo "$as_me:$LINENO: checking for _LARGEFILE_SOURCE value needed for large files" >&5 -echo $ECHO_N "checking for _LARGEFILE_SOURCE value needed for large files... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for _LARGEFILE_SOURCE value needed for large files" >&5 +$as_echo_n "checking for _LARGEFILE_SOURCE value needed for large files... " >&6; } if test "${ac_cv_sys_largefile_source+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else while :; do cat >conftest.$ac_ext <<_ACEOF @@ -5734,26 +7143,30 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_sys_largefile_source=no; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext cat >conftest.$ac_ext <<_ACEOF @@ -5780,34 +7193,38 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_sys_largefile_source=1; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext ac_cv_sys_largefile_source=unknown break done fi -{ echo "$as_me:$LINENO: result: $ac_cv_sys_largefile_source" >&5 -echo "${ECHO_T}$ac_cv_sys_largefile_source" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_sys_largefile_source" >&5 +$as_echo "$ac_cv_sys_largefile_source" >&6; } case $ac_cv_sys_largefile_source in #( no | unknown) ;; *) @@ -5816,7 +7233,7 @@ cat >>confdefs.h <<_ACEOF _ACEOF ;; esac -rm -f conftest* +rm -rf conftest* # We used to try defining _XOPEN_SOURCE=500 too, to work around a bug # in glibc 2.1.3, but that breaks too many other things. @@ -5829,68 +7246,14 @@ _ACEOF fi -{ echo "$as_me:$LINENO: checking for off_t" >&5 -echo $ECHO_N "checking for off_t... $ECHO_C" >&6; } -if test "${ac_cv_type_off_t+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - cat >conftest.$ac_ext <<_ACEOF -/* confdefs.h. */ -_ACEOF -cat confdefs.h >>conftest.$ac_ext -cat >>conftest.$ac_ext <<_ACEOF -/* end confdefs.h. */ -$ac_includes_default -typedef off_t ac__type_new_; -int -main () -{ -if ((ac__type_new_ *) 0) - return 0; -if (sizeof (ac__type_new_)) - return 0; - ; - return 0; -} -_ACEOF -rm -f conftest.$ac_objext -if { (ac_try="$ac_compile" -case "(($ac_try" in - *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; - *) ac_try_echo=$ac_try;; -esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_compile") 2>conftest.er1 - ac_status=$? - grep -v '^ *+' conftest.er1 >conftest.err - rm -f conftest.er1 - cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); } && { - test -z "$ac_c_werror_flag" || - test ! -s conftest.err - } && test -s conftest.$ac_objext; then - ac_cv_type_off_t=yes -else - echo "$as_me: failed program was:" >&5 -sed 's/^/| /' conftest.$ac_ext >&5 - - ac_cv_type_off_t=no -fi - -rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -fi -{ echo "$as_me:$LINENO: result: $ac_cv_type_off_t" >&5 -echo "${ECHO_T}$ac_cv_type_off_t" >&6; } - # The cast to long int works around a bug in the HP C Compiler # version HP92453-01 B.11.11.23709.GP, which incorrectly rejects # declarations like `int a3[[(sizeof (unsigned char)) >= 0]];'. # This bug is HP SR number 8606223364. -{ echo "$as_me:$LINENO: checking size of off_t" >&5 -echo $ECHO_N "checking size of off_t... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking size of off_t" >&5 +$as_echo_n "checking size of off_t... " >&6; } if test "${ac_cv_sizeof_off_t+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test "$cross_compiling" = yes; then # Depending upon the size, compute the lo and hi bounds. @@ -5901,11 +7264,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef off_t ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) >= 0)]; +static int test_array [1 - 2 * !(((long int) (sizeof (off_t))) >= 0)]; test_array [0] = 0 ; @@ -5918,13 +7280,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err @@ -5938,11 +7301,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef off_t ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) <= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (off_t))) <= $ac_mid)]; test_array [0] = 0 ; @@ -5955,20 +7317,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_hi=$ac_mid; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo=`expr $ac_mid + 1` @@ -5982,7 +7345,7 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext done else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 cat >conftest.$ac_ext <<_ACEOF @@ -5992,11 +7355,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef off_t ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) < 0)]; +static int test_array [1 - 2 * !(((long int) (sizeof (off_t))) < 0)]; test_array [0] = 0 ; @@ -6009,13 +7371,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err @@ -6029,11 +7392,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef off_t ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) >= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (off_t))) >= $ac_mid)]; test_array [0] = 0 ; @@ -6046,20 +7408,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_lo=$ac_mid; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_hi=`expr '(' $ac_mid ')' - 1` @@ -6073,7 +7436,7 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext done else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo= ac_hi= @@ -6093,11 +7456,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef off_t ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) <= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (off_t))) <= $ac_mid)]; test_array [0] = 0 ; @@ -6110,20 +7472,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_hi=$ac_mid else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo=`expr '(' $ac_mid ')' + 1` @@ -6134,11 +7497,13 @@ done case $ac_lo in ?*) ac_cv_sizeof_off_t=$ac_lo;; '') if test "$ac_cv_type_off_t" = yes; then - { { echo "$as_me:$LINENO: error: cannot compute sizeof (off_t) + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: cannot compute sizeof (off_t) See \`config.log' for more details." >&5 -echo "$as_me: error: cannot compute sizeof (off_t) +$as_echo "$as_me: error: cannot compute sizeof (off_t) See \`config.log' for more details." >&2;} - { (exit 77); exit 77; }; } + { (exit 77); exit 77; }; }; } else ac_cv_sizeof_off_t=0 fi ;; @@ -6151,9 +7516,8 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef off_t ac__type_sizeof_; -static long int longval () { return (long int) (sizeof (ac__type_sizeof_)); } -static unsigned long int ulongval () { return (long int) (sizeof (ac__type_sizeof_)); } +static long int longval () { return (long int) (sizeof (off_t)); } +static unsigned long int ulongval () { return (long int) (sizeof (off_t)); } #include #include int @@ -6163,20 +7527,22 @@ main () FILE *f = fopen ("conftest.val", "w"); if (! f) return 1; - if (((long int) (sizeof (ac__type_sizeof_))) < 0) + if (((long int) (sizeof (off_t))) < 0) { long int i = longval (); - if (i != ((long int) (sizeof (ac__type_sizeof_)))) + if (i != ((long int) (sizeof (off_t)))) return 1; - fprintf (f, "%ld\n", i); + fprintf (f, "%ld", i); } else { unsigned long int i = ulongval (); - if (i != ((long int) (sizeof (ac__type_sizeof_)))) + if (i != ((long int) (sizeof (off_t)))) return 1; - fprintf (f, "%lu\n", i); + fprintf (f, "%lu", i); } + /* Do not output a trailing newline, as this causes \r\n confusion + on some platforms. */ return ferror (f) || fclose (f) != 0; ; @@ -6189,43 +7555,48 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then ac_cv_sizeof_off_t=`cat conftest.val` else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) if test "$ac_cv_type_off_t" = yes; then - { { echo "$as_me:$LINENO: error: cannot compute sizeof (off_t) + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: cannot compute sizeof (off_t) See \`config.log' for more details." >&5 -echo "$as_me: error: cannot compute sizeof (off_t) +$as_echo "$as_me: error: cannot compute sizeof (off_t) See \`config.log' for more details." >&2;} - { (exit 77); exit 77; }; } + { (exit 77); exit 77; }; }; } else ac_cv_sizeof_off_t=0 fi fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi rm -f conftest.val fi -{ echo "$as_me:$LINENO: result: $ac_cv_sizeof_off_t" >&5 -echo "${ECHO_T}$ac_cv_sizeof_off_t" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_sizeof_off_t" >&5 +$as_echo "$ac_cv_sizeof_off_t" >&6; } @@ -6237,10 +7608,10 @@ _ACEOF # Extract the first word of "dbx", so it can be a program name with args. set dummy dbx; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_DBX+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case $DBX in [\\/]* | ?:[\\/]*) @@ -6255,7 +7626,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_path_DBX="$as_dir/$ac_word$ac_exec_ext" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -6268,20 +7639,20 @@ esac fi DBX=$ac_cv_path_DBX if test -n "$DBX"; then - { echo "$as_me:$LINENO: result: $DBX" >&5 -echo "${ECHO_T}$DBX" >&6; } + { $as_echo "$as_me:$LINENO: result: $DBX" >&5 +$as_echo "$DBX" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi # Extract the first word of "gdb", so it can be a program name with args. set dummy gdb; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_GDB+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case $GDB in [\\/]* | ?:[\\/]*) @@ -6296,7 +7667,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_path_GDB="$as_dir/$ac_word$ac_exec_ext" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -6309,20 +7680,20 @@ esac fi GDB=$ac_cv_path_GDB if test -n "$GDB"; then - { echo "$as_me:$LINENO: result: $GDB" >&5 -echo "${ECHO_T}$GDB" >&6; } + { $as_echo "$as_me:$LINENO: result: $GDB" >&5 +$as_echo "$GDB" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi # Extract the first word of "sdb", so it can be a program name with args. set dummy sdb; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_SDB+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case $SDB in [\\/]* | ?:[\\/]*) @@ -6337,7 +7708,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_path_SDB="$as_dir/$ac_word$ac_exec_ext" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -6350,11 +7721,11 @@ esac fi SDB=$ac_cv_path_SDB if test -n "$SDB"; then - { echo "$as_me:$LINENO: result: $SDB" >&5 -echo "${ECHO_T}$SDB" >&6; } + { $as_echo "$as_me:$LINENO: result: $SDB" >&5 +$as_echo "$SDB" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -6397,20 +7768,21 @@ fi for ac_header in inttypes.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -6426,32 +7798,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -6465,95 +7838,97 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi done -{ echo "$as_me:$LINENO: checking for uint32_t" >&5 -echo $ECHO_N "checking for uint32_t... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for uint32_t" >&5 +$as_echo_n "checking for uint32_t... " >&6; } if test "${ac_cv_type_uint32_t+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else - cat >conftest.$ac_ext <<_ACEOF + ac_cv_type_uint32_t=no +cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default -typedef uint32_t ac__type_new_; int main () { -if ((ac__type_new_ *) 0) - return 0; -if (sizeof (ac__type_new_)) - return 0; +if (sizeof (uint32_t)) + return 0; ; return 0; } @@ -6564,42 +7939,18 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then - ac_cv_type_uint32_t=yes -else - echo "$as_me: failed program was:" >&5 -sed 's/^/| /' conftest.$ac_ext >&5 - - ac_cv_type_uint32_t=no -fi - -rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -fi -{ echo "$as_me:$LINENO: result: $ac_cv_type_uint32_t" >&5 -echo "${ECHO_T}$ac_cv_type_uint32_t" >&6; } -if test $ac_cv_type_uint32_t = yes; then - -cat >>confdefs.h <<\_ACEOF -#define HAVE_C99_INTTYPES 1 -_ACEOF - -fi - -{ echo "$as_me:$LINENO: checking for short" >&5 -echo $ECHO_N "checking for short... $ECHO_C" >&6; } -if test "${ac_cv_type_short+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -6607,14 +7958,11 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default -typedef short ac__type_new_; int main () { -if ((ac__type_new_ *) 0) - return 0; -if (sizeof (ac__type_new_)) - return 0; +if (sizeof ((uint32_t))) + return 0; ; return 0; } @@ -6625,38 +7973,54 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then - ac_cv_type_short=yes + : +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_cv_type_uint32_t=yes +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 - ac_cv_type_short=no + fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_type_short" >&5 -echo "${ECHO_T}$ac_cv_type_short" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_type_uint32_t" >&5 +$as_echo "$ac_cv_type_uint32_t" >&6; } +if test "x$ac_cv_type_uint32_t" = x""yes; then + +cat >>confdefs.h <<\_ACEOF +#define HAVE_C99_INTTYPES 1 +_ACEOF + +fi # The cast to long int works around a bug in the HP C Compiler # version HP92453-01 B.11.11.23709.GP, which incorrectly rejects # declarations like `int a3[[(sizeof (unsigned char)) >= 0]];'. # This bug is HP SR number 8606223364. -{ echo "$as_me:$LINENO: checking size of short" >&5 -echo $ECHO_N "checking size of short... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking size of short" >&5 +$as_echo_n "checking size of short... " >&6; } if test "${ac_cv_sizeof_short+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test "$cross_compiling" = yes; then # Depending upon the size, compute the lo and hi bounds. @@ -6667,11 +8031,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef short ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) >= 0)]; +static int test_array [1 - 2 * !(((long int) (sizeof (short))) >= 0)]; test_array [0] = 0 ; @@ -6684,13 +8047,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err @@ -6704,11 +8068,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef short ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) <= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (short))) <= $ac_mid)]; test_array [0] = 0 ; @@ -6721,20 +8084,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_hi=$ac_mid; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo=`expr $ac_mid + 1` @@ -6748,7 +8112,7 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext done else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 cat >conftest.$ac_ext <<_ACEOF @@ -6758,11 +8122,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef short ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) < 0)]; +static int test_array [1 - 2 * !(((long int) (sizeof (short))) < 0)]; test_array [0] = 0 ; @@ -6775,13 +8138,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err @@ -6795,11 +8159,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef short ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) >= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (short))) >= $ac_mid)]; test_array [0] = 0 ; @@ -6812,20 +8175,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_lo=$ac_mid; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_hi=`expr '(' $ac_mid ')' - 1` @@ -6839,7 +8203,7 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext done else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo= ac_hi= @@ -6859,11 +8223,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef short ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) <= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (short))) <= $ac_mid)]; test_array [0] = 0 ; @@ -6876,20 +8239,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_hi=$ac_mid else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo=`expr '(' $ac_mid ')' + 1` @@ -6900,11 +8264,13 @@ done case $ac_lo in ?*) ac_cv_sizeof_short=$ac_lo;; '') if test "$ac_cv_type_short" = yes; then - { { echo "$as_me:$LINENO: error: cannot compute sizeof (short) + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: cannot compute sizeof (short) See \`config.log' for more details." >&5 -echo "$as_me: error: cannot compute sizeof (short) +$as_echo "$as_me: error: cannot compute sizeof (short) See \`config.log' for more details." >&2;} - { (exit 77); exit 77; }; } + { (exit 77); exit 77; }; }; } else ac_cv_sizeof_short=0 fi ;; @@ -6917,9 +8283,8 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef short ac__type_sizeof_; -static long int longval () { return (long int) (sizeof (ac__type_sizeof_)); } -static unsigned long int ulongval () { return (long int) (sizeof (ac__type_sizeof_)); } +static long int longval () { return (long int) (sizeof (short)); } +static unsigned long int ulongval () { return (long int) (sizeof (short)); } #include #include int @@ -6929,20 +8294,22 @@ main () FILE *f = fopen ("conftest.val", "w"); if (! f) return 1; - if (((long int) (sizeof (ac__type_sizeof_))) < 0) + if (((long int) (sizeof (short))) < 0) { long int i = longval (); - if (i != ((long int) (sizeof (ac__type_sizeof_)))) + if (i != ((long int) (sizeof (short)))) return 1; - fprintf (f, "%ld\n", i); + fprintf (f, "%ld", i); } else { unsigned long int i = ulongval (); - if (i != ((long int) (sizeof (ac__type_sizeof_)))) + if (i != ((long int) (sizeof (short)))) return 1; - fprintf (f, "%lu\n", i); + fprintf (f, "%lu", i); } + /* Do not output a trailing newline, as this causes \r\n confusion + on some platforms. */ return ferror (f) || fclose (f) != 0; ; @@ -6955,43 +8322,48 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then ac_cv_sizeof_short=`cat conftest.val` else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) if test "$ac_cv_type_short" = yes; then - { { echo "$as_me:$LINENO: error: cannot compute sizeof (short) + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: cannot compute sizeof (short) See \`config.log' for more details." >&5 -echo "$as_me: error: cannot compute sizeof (short) +$as_echo "$as_me: error: cannot compute sizeof (short) See \`config.log' for more details." >&2;} - { (exit 77); exit 77; }; } + { (exit 77); exit 77; }; }; } else ac_cv_sizeof_short=0 fi fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi rm -f conftest.val fi -{ echo "$as_me:$LINENO: result: $ac_cv_sizeof_short" >&5 -echo "${ECHO_T}$ac_cv_sizeof_short" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_sizeof_short" >&5 +$as_echo "$ac_cv_sizeof_short" >&6; } @@ -7000,68 +8372,14 @@ cat >>confdefs.h <<_ACEOF _ACEOF -{ echo "$as_me:$LINENO: checking for int" >&5 -echo $ECHO_N "checking for int... $ECHO_C" >&6; } -if test "${ac_cv_type_int+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - cat >conftest.$ac_ext <<_ACEOF -/* confdefs.h. */ -_ACEOF -cat confdefs.h >>conftest.$ac_ext -cat >>conftest.$ac_ext <<_ACEOF -/* end confdefs.h. */ -$ac_includes_default -typedef int ac__type_new_; -int -main () -{ -if ((ac__type_new_ *) 0) - return 0; -if (sizeof (ac__type_new_)) - return 0; - ; - return 0; -} -_ACEOF -rm -f conftest.$ac_objext -if { (ac_try="$ac_compile" -case "(($ac_try" in - *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; - *) ac_try_echo=$ac_try;; -esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_compile") 2>conftest.er1 - ac_status=$? - grep -v '^ *+' conftest.er1 >conftest.err - rm -f conftest.er1 - cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); } && { - test -z "$ac_c_werror_flag" || - test ! -s conftest.err - } && test -s conftest.$ac_objext; then - ac_cv_type_int=yes -else - echo "$as_me: failed program was:" >&5 -sed 's/^/| /' conftest.$ac_ext >&5 - - ac_cv_type_int=no -fi - -rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -fi -{ echo "$as_me:$LINENO: result: $ac_cv_type_int" >&5 -echo "${ECHO_T}$ac_cv_type_int" >&6; } - # The cast to long int works around a bug in the HP C Compiler # version HP92453-01 B.11.11.23709.GP, which incorrectly rejects # declarations like `int a3[[(sizeof (unsigned char)) >= 0]];'. # This bug is HP SR number 8606223364. -{ echo "$as_me:$LINENO: checking size of int" >&5 -echo $ECHO_N "checking size of int... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking size of int" >&5 +$as_echo_n "checking size of int... " >&6; } if test "${ac_cv_sizeof_int+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test "$cross_compiling" = yes; then # Depending upon the size, compute the lo and hi bounds. @@ -7072,11 +8390,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef int ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) >= 0)]; +static int test_array [1 - 2 * !(((long int) (sizeof (int))) >= 0)]; test_array [0] = 0 ; @@ -7089,13 +8406,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err @@ -7109,11 +8427,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef int ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) <= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (int))) <= $ac_mid)]; test_array [0] = 0 ; @@ -7126,20 +8443,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_hi=$ac_mid; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo=`expr $ac_mid + 1` @@ -7153,7 +8471,7 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext done else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 cat >conftest.$ac_ext <<_ACEOF @@ -7163,11 +8481,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef int ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) < 0)]; +static int test_array [1 - 2 * !(((long int) (sizeof (int))) < 0)]; test_array [0] = 0 ; @@ -7180,13 +8497,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err @@ -7200,11 +8518,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef int ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) >= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (int))) >= $ac_mid)]; test_array [0] = 0 ; @@ -7217,20 +8534,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_lo=$ac_mid; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_hi=`expr '(' $ac_mid ')' - 1` @@ -7244,7 +8562,7 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext done else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo= ac_hi= @@ -7264,11 +8582,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef int ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) <= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (int))) <= $ac_mid)]; test_array [0] = 0 ; @@ -7281,20 +8598,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_hi=$ac_mid else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo=`expr '(' $ac_mid ')' + 1` @@ -7305,11 +8623,13 @@ done case $ac_lo in ?*) ac_cv_sizeof_int=$ac_lo;; '') if test "$ac_cv_type_int" = yes; then - { { echo "$as_me:$LINENO: error: cannot compute sizeof (int) + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: cannot compute sizeof (int) See \`config.log' for more details." >&5 -echo "$as_me: error: cannot compute sizeof (int) +$as_echo "$as_me: error: cannot compute sizeof (int) See \`config.log' for more details." >&2;} - { (exit 77); exit 77; }; } + { (exit 77); exit 77; }; }; } else ac_cv_sizeof_int=0 fi ;; @@ -7322,9 +8642,8 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef int ac__type_sizeof_; -static long int longval () { return (long int) (sizeof (ac__type_sizeof_)); } -static unsigned long int ulongval () { return (long int) (sizeof (ac__type_sizeof_)); } +static long int longval () { return (long int) (sizeof (int)); } +static unsigned long int ulongval () { return (long int) (sizeof (int)); } #include #include int @@ -7334,20 +8653,22 @@ main () FILE *f = fopen ("conftest.val", "w"); if (! f) return 1; - if (((long int) (sizeof (ac__type_sizeof_))) < 0) + if (((long int) (sizeof (int))) < 0) { long int i = longval (); - if (i != ((long int) (sizeof (ac__type_sizeof_)))) + if (i != ((long int) (sizeof (int)))) return 1; - fprintf (f, "%ld\n", i); + fprintf (f, "%ld", i); } else { unsigned long int i = ulongval (); - if (i != ((long int) (sizeof (ac__type_sizeof_)))) + if (i != ((long int) (sizeof (int)))) return 1; - fprintf (f, "%lu\n", i); + fprintf (f, "%lu", i); } + /* Do not output a trailing newline, as this causes \r\n confusion + on some platforms. */ return ferror (f) || fclose (f) != 0; ; @@ -7360,43 +8681,48 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then ac_cv_sizeof_int=`cat conftest.val` else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) if test "$ac_cv_type_int" = yes; then - { { echo "$as_me:$LINENO: error: cannot compute sizeof (int) + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: cannot compute sizeof (int) See \`config.log' for more details." >&5 -echo "$as_me: error: cannot compute sizeof (int) +$as_echo "$as_me: error: cannot compute sizeof (int) See \`config.log' for more details." >&2;} - { (exit 77); exit 77; }; } + { (exit 77); exit 77; }; }; } else ac_cv_sizeof_int=0 fi fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi rm -f conftest.val fi -{ echo "$as_me:$LINENO: result: $ac_cv_sizeof_int" >&5 -echo "${ECHO_T}$ac_cv_sizeof_int" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_sizeof_int" >&5 +$as_echo "$ac_cv_sizeof_int" >&6; } @@ -7405,68 +8731,14 @@ cat >>confdefs.h <<_ACEOF _ACEOF -{ echo "$as_me:$LINENO: checking for long" >&5 -echo $ECHO_N "checking for long... $ECHO_C" >&6; } -if test "${ac_cv_type_long+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - cat >conftest.$ac_ext <<_ACEOF -/* confdefs.h. */ -_ACEOF -cat confdefs.h >>conftest.$ac_ext -cat >>conftest.$ac_ext <<_ACEOF -/* end confdefs.h. */ -$ac_includes_default -typedef long ac__type_new_; -int -main () -{ -if ((ac__type_new_ *) 0) - return 0; -if (sizeof (ac__type_new_)) - return 0; - ; - return 0; -} -_ACEOF -rm -f conftest.$ac_objext -if { (ac_try="$ac_compile" -case "(($ac_try" in - *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; - *) ac_try_echo=$ac_try;; -esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_compile") 2>conftest.er1 - ac_status=$? - grep -v '^ *+' conftest.er1 >conftest.err - rm -f conftest.er1 - cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); } && { - test -z "$ac_c_werror_flag" || - test ! -s conftest.err - } && test -s conftest.$ac_objext; then - ac_cv_type_long=yes -else - echo "$as_me: failed program was:" >&5 -sed 's/^/| /' conftest.$ac_ext >&5 - - ac_cv_type_long=no -fi - -rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -fi -{ echo "$as_me:$LINENO: result: $ac_cv_type_long" >&5 -echo "${ECHO_T}$ac_cv_type_long" >&6; } - # The cast to long int works around a bug in the HP C Compiler # version HP92453-01 B.11.11.23709.GP, which incorrectly rejects # declarations like `int a3[[(sizeof (unsigned char)) >= 0]];'. # This bug is HP SR number 8606223364. -{ echo "$as_me:$LINENO: checking size of long" >&5 -echo $ECHO_N "checking size of long... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking size of long" >&5 +$as_echo_n "checking size of long... " >&6; } if test "${ac_cv_sizeof_long+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test "$cross_compiling" = yes; then # Depending upon the size, compute the lo and hi bounds. @@ -7477,11 +8749,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef long ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) >= 0)]; +static int test_array [1 - 2 * !(((long int) (sizeof (long))) >= 0)]; test_array [0] = 0 ; @@ -7494,13 +8765,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err @@ -7514,11 +8786,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef long ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) <= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (long))) <= $ac_mid)]; test_array [0] = 0 ; @@ -7531,20 +8802,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_hi=$ac_mid; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo=`expr $ac_mid + 1` @@ -7558,7 +8830,7 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext done else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 cat >conftest.$ac_ext <<_ACEOF @@ -7568,11 +8840,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef long ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) < 0)]; +static int test_array [1 - 2 * !(((long int) (sizeof (long))) < 0)]; test_array [0] = 0 ; @@ -7585,13 +8856,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err @@ -7605,11 +8877,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef long ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) >= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (long))) >= $ac_mid)]; test_array [0] = 0 ; @@ -7622,20 +8893,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_lo=$ac_mid; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_hi=`expr '(' $ac_mid ')' - 1` @@ -7649,7 +8921,7 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext done else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo= ac_hi= @@ -7669,11 +8941,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef long ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) <= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (long))) <= $ac_mid)]; test_array [0] = 0 ; @@ -7686,20 +8957,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_hi=$ac_mid else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo=`expr '(' $ac_mid ')' + 1` @@ -7710,11 +8982,13 @@ done case $ac_lo in ?*) ac_cv_sizeof_long=$ac_lo;; '') if test "$ac_cv_type_long" = yes; then - { { echo "$as_me:$LINENO: error: cannot compute sizeof (long) + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: cannot compute sizeof (long) See \`config.log' for more details." >&5 -echo "$as_me: error: cannot compute sizeof (long) +$as_echo "$as_me: error: cannot compute sizeof (long) See \`config.log' for more details." >&2;} - { (exit 77); exit 77; }; } + { (exit 77); exit 77; }; }; } else ac_cv_sizeof_long=0 fi ;; @@ -7727,9 +9001,8 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef long ac__type_sizeof_; -static long int longval () { return (long int) (sizeof (ac__type_sizeof_)); } -static unsigned long int ulongval () { return (long int) (sizeof (ac__type_sizeof_)); } +static long int longval () { return (long int) (sizeof (long)); } +static unsigned long int ulongval () { return (long int) (sizeof (long)); } #include #include int @@ -7739,20 +9012,22 @@ main () FILE *f = fopen ("conftest.val", "w"); if (! f) return 1; - if (((long int) (sizeof (ac__type_sizeof_))) < 0) + if (((long int) (sizeof (long))) < 0) { long int i = longval (); - if (i != ((long int) (sizeof (ac__type_sizeof_)))) + if (i != ((long int) (sizeof (long)))) return 1; - fprintf (f, "%ld\n", i); + fprintf (f, "%ld", i); } else { unsigned long int i = ulongval (); - if (i != ((long int) (sizeof (ac__type_sizeof_)))) + if (i != ((long int) (sizeof (long)))) return 1; - fprintf (f, "%lu\n", i); + fprintf (f, "%lu", i); } + /* Do not output a trailing newline, as this causes \r\n confusion + on some platforms. */ return ferror (f) || fclose (f) != 0; ; @@ -7765,113 +9040,64 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_link") 2>&5 - ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); } && { ac_try='./conftest$ac_exeext' - { (case "(($ac_try" in - *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; - *) ac_try_echo=$ac_try;; -esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_try") 2>&5 - ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); }; }; then - ac_cv_sizeof_long=`cat conftest.val` -else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 -sed 's/^/| /' conftest.$ac_ext >&5 - -( exit $ac_status ) -if test "$ac_cv_type_long" = yes; then - { { echo "$as_me:$LINENO: error: cannot compute sizeof (long) -See \`config.log' for more details." >&5 -echo "$as_me: error: cannot compute sizeof (long) -See \`config.log' for more details." >&2;} - { (exit 77); exit 77; }; } - else - ac_cv_sizeof_long=0 - fi -fi -rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext -fi -rm -f conftest.val -fi -{ echo "$as_me:$LINENO: result: $ac_cv_sizeof_long" >&5 -echo "${ECHO_T}$ac_cv_sizeof_long" >&6; } - - - -cat >>confdefs.h <<_ACEOF -#define SIZEOF_LONG $ac_cv_sizeof_long -_ACEOF - - -{ echo "$as_me:$LINENO: checking for long long" >&5 -echo $ECHO_N "checking for long long... $ECHO_C" >&6; } -if test "${ac_cv_type_long_long+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - cat >conftest.$ac_ext <<_ACEOF -/* confdefs.h. */ -_ACEOF -cat confdefs.h >>conftest.$ac_ext -cat >>conftest.$ac_ext <<_ACEOF -/* end confdefs.h. */ -$ac_includes_default -typedef long long ac__type_new_; -int -main () -{ -if ((ac__type_new_ *) 0) - return 0; -if (sizeof (ac__type_new_)) - return 0; - ; - return 0; -} -_ACEOF -rm -f conftest.$ac_objext -if { (ac_try="$ac_compile" -case "(($ac_try" in - *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; - *) ac_try_echo=$ac_try;; -esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_compile") 2>conftest.er1 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_link") 2>&5 ac_status=$? - grep -v '^ *+' conftest.er1 >conftest.err - rm -f conftest.er1 - cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); } && { - test -z "$ac_c_werror_flag" || - test ! -s conftest.err - } && test -s conftest.$ac_objext; then - ac_cv_type_long_long=yes + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { ac_try='./conftest$ac_exeext' + { (case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_try") 2>&5 + ac_status=$? + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); }; }; then + ac_cv_sizeof_long=`cat conftest.val` else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 - ac_cv_type_long_long=no +( exit $ac_status ) +if test "$ac_cv_type_long" = yes; then + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: cannot compute sizeof (long) +See \`config.log' for more details." >&5 +$as_echo "$as_me: error: cannot compute sizeof (long) +See \`config.log' for more details." >&2;} + { (exit 77); exit 77; }; }; } + else + ac_cv_sizeof_long=0 + fi fi - -rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +rm -rf conftest.dSYM +rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_type_long_long" >&5 -echo "${ECHO_T}$ac_cv_type_long_long" >&6; } +rm -f conftest.val +fi +{ $as_echo "$as_me:$LINENO: result: $ac_cv_sizeof_long" >&5 +$as_echo "$ac_cv_sizeof_long" >&6; } + + + +cat >>confdefs.h <<_ACEOF +#define SIZEOF_LONG $ac_cv_sizeof_long +_ACEOF + # The cast to long int works around a bug in the HP C Compiler # version HP92453-01 B.11.11.23709.GP, which incorrectly rejects # declarations like `int a3[[(sizeof (unsigned char)) >= 0]];'. # This bug is HP SR number 8606223364. -{ echo "$as_me:$LINENO: checking size of long long" >&5 -echo $ECHO_N "checking size of long long... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking size of long long" >&5 +$as_echo_n "checking size of long long... " >&6; } if test "${ac_cv_sizeof_long_long+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test "$cross_compiling" = yes; then # Depending upon the size, compute the lo and hi bounds. @@ -7882,11 +9108,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef long long ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) >= 0)]; +static int test_array [1 - 2 * !(((long int) (sizeof (long long))) >= 0)]; test_array [0] = 0 ; @@ -7899,13 +9124,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err @@ -7919,11 +9145,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef long long ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) <= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (long long))) <= $ac_mid)]; test_array [0] = 0 ; @@ -7936,20 +9161,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_hi=$ac_mid; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo=`expr $ac_mid + 1` @@ -7963,7 +9189,7 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext done else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 cat >conftest.$ac_ext <<_ACEOF @@ -7973,11 +9199,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef long long ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) < 0)]; +static int test_array [1 - 2 * !(((long int) (sizeof (long long))) < 0)]; test_array [0] = 0 ; @@ -7990,13 +9215,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err @@ -8010,11 +9236,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef long long ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) >= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (long long))) >= $ac_mid)]; test_array [0] = 0 ; @@ -8027,20 +9252,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_lo=$ac_mid; break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_hi=`expr '(' $ac_mid ')' - 1` @@ -8054,7 +9280,7 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext done else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo= ac_hi= @@ -8074,11 +9300,10 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef long long ac__type_sizeof_; int main () { -static int test_array [1 - 2 * !(((long int) (sizeof (ac__type_sizeof_))) <= $ac_mid)]; +static int test_array [1 - 2 * !(((long int) (sizeof (long long))) <= $ac_mid)]; test_array [0] = 0 ; @@ -8091,20 +9316,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_hi=$ac_mid else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_lo=`expr '(' $ac_mid ')' + 1` @@ -8115,11 +9341,13 @@ done case $ac_lo in ?*) ac_cv_sizeof_long_long=$ac_lo;; '') if test "$ac_cv_type_long_long" = yes; then - { { echo "$as_me:$LINENO: error: cannot compute sizeof (long long) + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: cannot compute sizeof (long long) See \`config.log' for more details." >&5 -echo "$as_me: error: cannot compute sizeof (long long) +$as_echo "$as_me: error: cannot compute sizeof (long long) See \`config.log' for more details." >&2;} - { (exit 77); exit 77; }; } + { (exit 77); exit 77; }; }; } else ac_cv_sizeof_long_long=0 fi ;; @@ -8132,9 +9360,8 @@ cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default - typedef long long ac__type_sizeof_; -static long int longval () { return (long int) (sizeof (ac__type_sizeof_)); } -static unsigned long int ulongval () { return (long int) (sizeof (ac__type_sizeof_)); } +static long int longval () { return (long int) (sizeof (long long)); } +static unsigned long int ulongval () { return (long int) (sizeof (long long)); } #include #include int @@ -8144,20 +9371,22 @@ main () FILE *f = fopen ("conftest.val", "w"); if (! f) return 1; - if (((long int) (sizeof (ac__type_sizeof_))) < 0) + if (((long int) (sizeof (long long))) < 0) { long int i = longval (); - if (i != ((long int) (sizeof (ac__type_sizeof_)))) + if (i != ((long int) (sizeof (long long)))) return 1; - fprintf (f, "%ld\n", i); + fprintf (f, "%ld", i); } else { unsigned long int i = ulongval (); - if (i != ((long int) (sizeof (ac__type_sizeof_)))) + if (i != ((long int) (sizeof (long long)))) return 1; - fprintf (f, "%lu\n", i); + fprintf (f, "%lu", i); } + /* Do not output a trailing newline, as this causes \r\n confusion + on some platforms. */ return ferror (f) || fclose (f) != 0; ; @@ -8170,43 +9399,48 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then ac_cv_sizeof_long_long=`cat conftest.val` else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) if test "$ac_cv_type_long_long" = yes; then - { { echo "$as_me:$LINENO: error: cannot compute sizeof (long long) + { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +{ { $as_echo "$as_me:$LINENO: error: cannot compute sizeof (long long) See \`config.log' for more details." >&5 -echo "$as_me: error: cannot compute sizeof (long long) +$as_echo "$as_me: error: cannot compute sizeof (long long) See \`config.log' for more details." >&2;} - { (exit 77); exit 77; }; } + { (exit 77); exit 77; }; }; } else ac_cv_sizeof_long_long=0 fi fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi rm -f conftest.val fi -{ echo "$as_me:$LINENO: result: $ac_cv_sizeof_long_long" >&5 -echo "${ECHO_T}$ac_cv_sizeof_long_long" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_sizeof_long_long" >&5 +$as_echo "$ac_cv_sizeof_long_long" >&6; } @@ -8219,10 +9453,10 @@ _ACEOF ac_aux_path_sendmail=/usr/sbin:/usr/lib # Extract the first word of "sendmail", so it can be a program name with args. set dummy sendmail; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_SENDMAIL+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case $SENDMAIL in [\\/]* | ?:[\\/]*) @@ -8238,7 +9472,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_path_SENDMAIL="$as_dir/$ac_word$ac_exec_ext" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -8251,11 +9485,11 @@ esac fi SENDMAIL=$ac_cv_path_SENDMAIL if test -n "$SENDMAIL"; then - { echo "$as_me:$LINENO: result: $SENDMAIL" >&5 -echo "${ECHO_T}$SENDMAIL" >&6; } + { $as_echo "$as_me:$LINENO: result: $SENDMAIL" >&5 +$as_echo "$SENDMAIL" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -8267,8 +9501,8 @@ _ACEOF OPS='$(srcdir)/OPS' -{ echo "$as_me:$LINENO: checking whether to build with GPGME support" >&5 -echo $ECHO_N "checking whether to build with GPGME support... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether to build with GPGME support" >&5 +$as_echo_n "checking whether to build with GPGME support... " >&6; } # Check whether --enable-gpgme was given. if test "${enable_gpgme+set}" = set; then enableval=$enable_gpgme; if test x$enableval = xyes; then @@ -8279,8 +9513,8 @@ fi if test x"$enable_gpgme" = xyes; then - { echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } + { $as_echo "$as_me:$LINENO: result: yes" >&5 +$as_echo "yes" >&6; } # Check whether --with-gpgme-prefix was given. if test "${with_gpgme_prefix+set}" = set; then @@ -8294,10 +9528,10 @@ fi fi # Extract the first word of "gpgme-config", so it can be a program name with args. set dummy gpgme-config; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_GPGME_CONFIG+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case $GPGME_CONFIG in [\\/]* | ?:[\\/]*) @@ -8312,7 +9546,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_path_GPGME_CONFIG="$as_dir/$ac_word$ac_exec_ext" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -8325,11 +9559,11 @@ esac fi GPGME_CONFIG=$ac_cv_path_GPGME_CONFIG if test -n "$GPGME_CONFIG"; then - { echo "$as_me:$LINENO: result: $GPGME_CONFIG" >&5 -echo "${ECHO_T}$GPGME_CONFIG" >&6; } + { $as_echo "$as_me:$LINENO: result: $GPGME_CONFIG" >&5 +$as_echo "$GPGME_CONFIG" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -8353,8 +9587,8 @@ fi min_gpgme_version="$tmp" fi - { echo "$as_me:$LINENO: checking for GPGME - version >= $min_gpgme_version" >&5 -echo $ECHO_N "checking for GPGME - version >= $min_gpgme_version... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for GPGME - version >= $min_gpgme_version" >&5 +$as_echo_n "checking for GPGME - version >= $min_gpgme_version... " >&6; } ok=no if test "$GPGME_CONFIG" != "no" ; then req_major=`echo $min_gpgme_version | \ @@ -8394,8 +9628,8 @@ echo $ECHO_N "checking for GPGME - version >= $min_gpgme_version... $ECHO_C" >&6 if test $ok = yes; then GPGME_CFLAGS=`$GPGME_CONFIG --cflags` GPGME_LIBS=`$GPGME_CONFIG --libs` - { echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } + { $as_echo "$as_me:$LINENO: result: yes" >&5 +$as_echo "yes" >&6; } cat >>confdefs.h <<\_ACEOF #define CRYPT_BACKEND_GPGME 1 @@ -8404,16 +9638,16 @@ _ACEOF else GPGME_CFLAGS="" GPGME_LIBS="" - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } gpgme_found=no fi if test x"$gpgme_found" = xno; then - { { echo "$as_me:$LINENO: error: *** GPGME not found ***" >&5 -echo "$as_me: error: *** GPGME not found ***" >&2;} + { { $as_echo "$as_me:$LINENO: error: *** GPGME not found ***" >&5 +$as_echo "$as_me: error: *** GPGME not found ***" >&2;} { (exit 1); exit 1; }; } else tmp=1.1.1 @@ -8425,8 +9659,8 @@ echo "$as_me: error: *** GPGME not found ***" >&2;} min_gpgme_version="$tmp" fi - { echo "$as_me:$LINENO: checking for GPGME - version >= $min_gpgme_version" >&5 -echo $ECHO_N "checking for GPGME - version >= $min_gpgme_version... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for GPGME - version >= $min_gpgme_version" >&5 +$as_echo_n "checking for GPGME - version >= $min_gpgme_version... " >&6; } ok=no if test "$GPGME_CONFIG" != "no" ; then req_major=`echo $min_gpgme_version | \ @@ -8466,8 +9700,8 @@ echo $ECHO_N "checking for GPGME - version >= $min_gpgme_version... $ECHO_C" >&6 if test $ok = yes; then GPGME_CFLAGS=`$GPGME_CONFIG --cflags` GPGME_LIBS=`$GPGME_CONFIG --libs` - { echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } + { $as_echo "$as_me:$LINENO: result: yes" >&5 +$as_echo "yes" >&6; } cat >>confdefs.h <<\_ACEOF #define HAVE_GPGME_PKA_TRUST 1 @@ -8476,8 +9710,8 @@ _ACEOF else GPGME_CFLAGS="" GPGME_LIBS="" - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } : fi @@ -8493,8 +9727,8 @@ echo "${ECHO_T}no" >&6; } min_gpgme_version="$tmp" fi - { echo "$as_me:$LINENO: checking for GPGME - version >= $min_gpgme_version" >&5 -echo $ECHO_N "checking for GPGME - version >= $min_gpgme_version... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for GPGME - version >= $min_gpgme_version" >&5 +$as_echo_n "checking for GPGME - version >= $min_gpgme_version... " >&6; } ok=no if test "$GPGME_CONFIG" != "no" ; then req_major=`echo $min_gpgme_version | \ @@ -8534,8 +9768,8 @@ echo $ECHO_N "checking for GPGME - version >= $min_gpgme_version... $ECHO_C" >&6 if test $ok = yes; then GPGME_CFLAGS=`$GPGME_CONFIG --cflags` GPGME_LIBS=`$GPGME_CONFIG --libs` - { echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } + { $as_echo "$as_me:$LINENO: result: yes" >&5 +$as_echo "yes" >&6; } cat >>confdefs.h <<\_ACEOF #define CRYPT_BACKEND_GPGME 1 @@ -8544,8 +9778,8 @@ _ACEOF else GPGME_CFLAGS="" GPGME_LIBS="" - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } : fi @@ -8554,8 +9788,8 @@ echo "${ECHO_T}no" >&6; } MUTT_LIB_OBJECTS="$MUTT_LIB_OBJECTS crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o" fi else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi # Check whether --enable-pgp was given. @@ -8627,10 +9861,10 @@ OPS="$OPS \$(srcdir)/OPS.PGP \$(srcdir)/OPS.SMIME \$(srcdir)/OPS.CRYPT " # Extract the first word of "ispell", so it can be a program name with args. set dummy ispell; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_ISPELL+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case $ISPELL in [\\/]* | ?:[\\/]*) @@ -8645,7 +9879,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_path_ISPELL="$as_dir/$ac_word$ac_exec_ext" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -8658,11 +9892,11 @@ esac fi ISPELL=$ac_cv_path_ISPELL if test -n "$ISPELL"; then - { echo "$as_me:$LINENO: result: $ISPELL" >&5 -echo "${ECHO_T}$ISPELL" >&6; } + { $as_echo "$as_me:$LINENO: result: $ISPELL" >&5 +$as_echo "$ISPELL" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -8677,10 +9911,10 @@ fi # Check whether --with-slang was given. if test "${with_slang+set}" = set; then - withval=$with_slang; { echo "$as_me:$LINENO: checking if this is a BSD system" >&5 -echo $ECHO_N "checking if this is a BSD system... $ECHO_C" >&6; } + withval=$with_slang; { $as_echo "$as_me:$LINENO: checking if this is a BSD system" >&5 +$as_echo_n "checking if this is a BSD system... " >&6; } if test "${mutt_cv_bsdish+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test "$cross_compiling" = yes; then mutt_cv_bsdish=no @@ -8709,39 +9943,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then mutt_cv_bsdish=yes else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) mutt_cv_bsdish=no fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi fi -{ echo "$as_me:$LINENO: result: $mutt_cv_bsdish" >&5 -echo "${ECHO_T}$mutt_cv_bsdish" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_bsdish" >&5 +$as_echo "$mutt_cv_bsdish" >&6; } - { echo "$as_me:$LINENO: checking for S-Lang" >&5 -echo $ECHO_N "checking for S-Lang... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for S-Lang" >&5 +$as_echo_n "checking for S-Lang... " >&6; } if test $withval = yes; then if test -d $srcdir/../slang; then mutt_cv_slang=$srcdir/../slang/src @@ -8770,14 +10007,14 @@ echo $ECHO_N "checking for S-Lang... $ECHO_C" >&6; } LDFLAGS="$LDFLAGS -L${withval}/lib" fi fi - { echo "$as_me:$LINENO: result: $mutt_cv_slang" >&5 -echo "${ECHO_T}$mutt_cv_slang" >&6; } + { $as_echo "$as_me:$LINENO: result: $mutt_cv_slang" >&5 +$as_echo "$mutt_cv_slang" >&6; } if test $mutt_cv_bsdish = yes; then -{ echo "$as_me:$LINENO: checking for main in -ltermlib" >&5 -echo $ECHO_N "checking for main in -ltermlib... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for main in -ltermlib" >&5 +$as_echo_n "checking for main in -ltermlib... " >&6; } if test "${ac_cv_lib_termlib_main+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-ltermlib $LIBS" @@ -8803,33 +10040,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_termlib_main=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_termlib_main=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_termlib_main" >&5 -echo "${ECHO_T}$ac_cv_lib_termlib_main" >&6; } -if test $ac_cv_lib_termlib_main = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_termlib_main" >&5 +$as_echo "$ac_cv_lib_termlib_main" >&6; } +if test "x$ac_cv_lib_termlib_main" = x""yes; then cat >>confdefs.h <<_ACEOF #define HAVE_LIBTERMLIB 1 _ACEOF @@ -8852,10 +10093,10 @@ _ACEOF MUTT_LIB_OBJECTS="$MUTT_LIB_OBJECTS resize.o" - { echo "$as_me:$LINENO: checking for SLtt_get_terminfo in -lslang" >&5 -echo $ECHO_N "checking for SLtt_get_terminfo in -lslang... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for SLtt_get_terminfo in -lslang" >&5 +$as_echo_n "checking for SLtt_get_terminfo in -lslang... " >&6; } if test "${ac_cv_lib_slang_SLtt_get_terminfo+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lslang -lm $LIBS" @@ -8887,37 +10128,41 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_slang_SLtt_get_terminfo=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_slang_SLtt_get_terminfo=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_slang_SLtt_get_terminfo" >&5 -echo "${ECHO_T}$ac_cv_lib_slang_SLtt_get_terminfo" >&6; } -if test $ac_cv_lib_slang_SLtt_get_terminfo = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_slang_SLtt_get_terminfo" >&5 +$as_echo "$ac_cv_lib_slang_SLtt_get_terminfo" >&6; } +if test "x$ac_cv_lib_slang_SLtt_get_terminfo" = x""yes; then MUTTLIBS="$MUTTLIBS -lslang -lm" else - { { echo "$as_me:$LINENO: error: unable to compile. check config.log" >&5 -echo "$as_me: error: unable to compile. check config.log" >&2;} + { { $as_echo "$as_me:$LINENO: error: unable to compile. check config.log" >&5 +$as_echo "$as_me: error: unable to compile. check config.log" >&2;} { (exit 1); exit 1; }; } fi @@ -8938,10 +10183,10 @@ if test "${with_curses+set}" = set; then fi - { echo "$as_me:$LINENO: checking for initscr" >&5 -echo $ECHO_N "checking for initscr... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for initscr" >&5 +$as_echo_n "checking for initscr... " >&6; } if test "${ac_cv_func_initscr+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -8994,43 +10239,47 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_func_initscr=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_func_initscr=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_func_initscr" >&5 -echo "${ECHO_T}$ac_cv_func_initscr" >&6; } -if test $ac_cv_func_initscr = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_func_initscr" >&5 +$as_echo "$ac_cv_func_initscr" >&6; } +if test "x$ac_cv_func_initscr" = x""yes; then : else cf_ncurses="ncurses" for lib in ncurses ncursesw do - as_ac_Lib=`echo "ac_cv_lib_$lib''_waddnwstr" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for waddnwstr in -l$lib" >&5 -echo $ECHO_N "checking for waddnwstr in -l$lib... $ECHO_C" >&6; } + as_ac_Lib=`$as_echo "ac_cv_lib_$lib''_waddnwstr" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for waddnwstr in -l$lib" >&5 +$as_echo_n "checking for waddnwstr in -l$lib... " >&6; } if { as_var=$as_ac_Lib; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-l$lib $LIBS" @@ -9062,43 +10311,50 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_Lib=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_Lib=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -ac_res=`eval echo '${'$as_ac_Lib'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_Lib'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_Lib'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_Lib'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cf_ncurses="$lib"; break fi done - as_ac_Lib=`echo "ac_cv_lib_$cf_ncurses''_initscr" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for initscr in -l$cf_ncurses" >&5 -echo $ECHO_N "checking for initscr in -l$cf_ncurses... $ECHO_C" >&6; } + as_ac_Lib=`$as_echo "ac_cv_lib_$cf_ncurses''_initscr" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for initscr in -l$cf_ncurses" >&5 +$as_echo_n "checking for initscr in -l$cf_ncurses... " >&6; } if { as_var=$as_ac_Lib; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-l$cf_ncurses $LIBS" @@ -9130,54 +10386,62 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_Lib=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_Lib=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -ac_res=`eval echo '${'$as_ac_Lib'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_Lib'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_Lib'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_Lib'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then MUTTLIBS="$MUTTLIBS -l$cf_ncurses" if test "$cf_ncurses" = ncursesw; then for ac_header in ncursesw/ncurses.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -9193,32 +10457,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -9232,69 +10497,73 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF cf_cv_ncurses_header="ncursesw/ncurses.h" fi @@ -9305,20 +10574,21 @@ done for ac_header in ncurses/ncurses.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -9334,32 +10604,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -9373,89 +10644,94 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF cf_cv_ncurses_header="ncurses/ncurses.h" else for ac_header in ncurses.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -9471,32 +10747,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -9510,69 +10787,73 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF cf_cv_ncurses_header="ncurses.h" fi @@ -9586,10 +10867,10 @@ done fi else -{ echo "$as_me:$LINENO: checking for initscr" >&5 -echo $ECHO_N "checking for initscr... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for initscr" >&5 +$as_echo_n "checking for initscr... " >&6; } if test "${ac_cv_func_initscr+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -9642,41 +10923,45 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_func_initscr=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_func_initscr=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_func_initscr" >&5 -echo "${ECHO_T}$ac_cv_func_initscr" >&6; } -if test $ac_cv_func_initscr = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_func_initscr" >&5 +$as_echo "$ac_cv_func_initscr" >&6; } +if test "x$ac_cv_func_initscr" = x""yes; then : else case $host_os in #(vi freebsd*) #(vi - { echo "$as_me:$LINENO: checking for tgoto in -lmytinfo" >&5 -echo $ECHO_N "checking for tgoto in -lmytinfo... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for tgoto in -lmytinfo" >&5 +$as_echo_n "checking for tgoto in -lmytinfo... " >&6; } if test "${ac_cv_lib_mytinfo_tgoto+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lmytinfo $LIBS" @@ -9708,42 +10993,46 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_mytinfo_tgoto=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_mytinfo_tgoto=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_mytinfo_tgoto" >&5 -echo "${ECHO_T}$ac_cv_lib_mytinfo_tgoto" >&6; } -if test $ac_cv_lib_mytinfo_tgoto = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_mytinfo_tgoto" >&5 +$as_echo "$ac_cv_lib_mytinfo_tgoto" >&6; } +if test "x$ac_cv_lib_mytinfo_tgoto" = x""yes; then LIBS="-lmytinfo $LIBS" fi ;; hpux10.*|hpux11.*) - { echo "$as_me:$LINENO: checking for initscr in -lcur_colr" >&5 -echo $ECHO_N "checking for initscr in -lcur_colr... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for initscr in -lcur_colr" >&5 +$as_echo_n "checking for initscr in -lcur_colr... " >&6; } if test "${ac_cv_lib_cur_colr_initscr+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lcur_colr $LIBS" @@ -9775,33 +11064,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_cur_colr_initscr=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_cur_colr_initscr=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_cur_colr_initscr" >&5 -echo "${ECHO_T}$ac_cv_lib_cur_colr_initscr" >&6; } -if test $ac_cv_lib_cur_colr_initscr = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_cur_colr_initscr" >&5 +$as_echo "$ac_cv_lib_cur_colr_initscr" >&6; } +if test "x$ac_cv_lib_cur_colr_initscr" = x""yes; then LIBS="-lcur_colr $LIBS" CFLAGS="-I/usr/include/curses_colr $CFLAGS" @@ -9809,10 +11102,10 @@ if test $ac_cv_lib_cur_colr_initscr = yes; then else - { echo "$as_me:$LINENO: checking for initscr in -lHcurses" >&5 -echo $ECHO_N "checking for initscr in -lHcurses... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for initscr in -lHcurses" >&5 +$as_echo_n "checking for initscr in -lHcurses... " >&6; } if test "${ac_cv_lib_Hcurses_initscr+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lHcurses $LIBS" @@ -9844,33 +11137,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_Hcurses_initscr=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_Hcurses_initscr=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_Hcurses_initscr" >&5 -echo "${ECHO_T}$ac_cv_lib_Hcurses_initscr" >&6; } -if test $ac_cv_lib_Hcurses_initscr = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_Hcurses_initscr" >&5 +$as_echo "$ac_cv_lib_Hcurses_initscr" >&6; } +if test "x$ac_cv_lib_Hcurses_initscr" = x""yes; then # HP's header uses __HP_CURSES, but user claims _HP_CURSES. LIBS="-lHcurses $LIBS" @@ -9902,10 +11199,10 @@ if test ".$ac_cv_func_initscr" != .yes ; then # Check for library containing tgoto. Do this before curses library # because it may be needed to link the test-case for initscr. - { echo "$as_me:$LINENO: checking for tgoto" >&5 -echo $ECHO_N "checking for tgoto... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for tgoto" >&5 +$as_echo_n "checking for tgoto... " >&6; } if test "${ac_cv_func_tgoto+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -9958,42 +11255,46 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_func_tgoto=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_func_tgoto=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_func_tgoto" >&5 -echo "${ECHO_T}$ac_cv_func_tgoto" >&6; } -if test $ac_cv_func_tgoto = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_func_tgoto" >&5 +$as_echo "$ac_cv_func_tgoto" >&6; } +if test "x$ac_cv_func_tgoto" = x""yes; then cf_term_lib=predefined else for cf_term_lib in termcap termlib unknown do - as_ac_Lib=`echo "ac_cv_lib_$cf_term_lib''_tgoto" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for tgoto in -l$cf_term_lib" >&5 -echo $ECHO_N "checking for tgoto in -l$cf_term_lib... $ECHO_C" >&6; } + as_ac_Lib=`$as_echo "ac_cv_lib_$cf_term_lib''_tgoto" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for tgoto in -l$cf_term_lib" >&5 +$as_echo_n "checking for tgoto in -l$cf_term_lib... " >&6; } if { as_var=$as_ac_Lib; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-l$cf_term_lib $LIBS" @@ -10025,34 +11326,41 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_Lib=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_Lib=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -ac_res=`eval echo '${'$as_ac_Lib'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_Lib'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_Lib'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_Lib'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then break fi @@ -10065,11 +11373,11 @@ fi test "$cf_term_lib" != predefined && test "$cf_term_lib" != unknown && LIBS="-l$cf_term_lib $cf_save_LIBS" for cf_curs_lib in cursesX curses ncurses xcurses jcurses unknown do - as_ac_Lib=`echo "ac_cv_lib_$cf_curs_lib''_initscr" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for initscr in -l$cf_curs_lib" >&5 -echo $ECHO_N "checking for initscr in -l$cf_curs_lib... $ECHO_C" >&6; } + as_ac_Lib=`$as_echo "ac_cv_lib_$cf_curs_lib''_initscr" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for initscr in -l$cf_curs_lib" >&5 +$as_echo_n "checking for initscr in -l$cf_curs_lib... " >&6; } if { as_var=$as_ac_Lib; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-l$cf_curs_lib $LIBS" @@ -10101,46 +11409,53 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_Lib=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_Lib=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -ac_res=`eval echo '${'$as_ac_Lib'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_Lib'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_Lib'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_Lib'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then break fi done - test $cf_curs_lib = unknown && { { echo "$as_me:$LINENO: error: no curses library found" >&5 -echo "$as_me: error: no curses library found" >&2;} + test $cf_curs_lib = unknown && { { $as_echo "$as_me:$LINENO: error: no curses library found" >&5 +$as_echo "$as_me: error: no curses library found" >&2;} { (exit 1); exit 1; }; } LIBS="-l$cf_curs_lib $cf_save_LIBS" if test "$cf_term_lib" = unknown ; then - { echo "$as_me:$LINENO: checking if we can link with $cf_curs_lib library" >&5 -echo $ECHO_N "checking if we can link with $cf_curs_lib library... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking if we can link with $cf_curs_lib library" >&5 +$as_echo_n "checking if we can link with $cf_curs_lib library... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -10162,36 +11477,40 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then cf_result=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 cf_result=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext - { echo "$as_me:$LINENO: result: $cf_result" >&5 -echo "${ECHO_T}$cf_result" >&6; } - test $cf_result = no && { { echo "$as_me:$LINENO: error: Cannot link curses library" >&5 -echo "$as_me: error: Cannot link curses library" >&2;} + { $as_echo "$as_me:$LINENO: result: $cf_result" >&5 +$as_echo "$cf_result" >&6; } + test $cf_result = no && { { $as_echo "$as_me:$LINENO: error: Cannot link curses library" >&5 +$as_echo "$as_me: error: Cannot link curses library" >&2;} { (exit 1); exit 1; }; } elif test "$cf_term_lib" != predefined ; then - { echo "$as_me:$LINENO: checking if we need both $cf_curs_lib and $cf_term_lib libraries" >&5 -echo $ECHO_N "checking if we need both $cf_curs_lib and $cf_term_lib libraries... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking if we need both $cf_curs_lib and $cf_term_lib libraries" >&5 +$as_echo_n "checking if we need both $cf_curs_lib and $cf_term_lib libraries... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -10213,21 +11532,24 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then cf_result=no else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -10253,35 +11575,40 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then cf_result=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 cf_result=error fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext - { echo "$as_me:$LINENO: result: $cf_result" >&5 -echo "${ECHO_T}$cf_result" >&6; } + { $as_echo "$as_me:$LINENO: result: $cf_result" >&5 +$as_echo "$cf_result" >&6; } fi fi @@ -10299,10 +11626,10 @@ fi for ac_func in start_color typeahead bkgdset curs_set meta use_default_colors resizeterm do -{ echo "$as_me:$LINENO: checking for $ac_func declaration" >&5 -echo $ECHO_N "checking for $ac_func declaration... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_func declaration" >&5 +$as_echo_n "checking for $ac_func declaration... " >&6; } if { as_var=ac_cv_func_decl_$ac_func; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -10327,13 +11654,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err @@ -10362,13 +11690,14 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err @@ -10376,7 +11705,7 @@ eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 eval "ac_cv_func_decl_$ac_func=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -10385,7 +11714,7 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -10396,8 +11725,8 @@ rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext fi if eval "test \"`echo '$ac_cv_func_'decl_$ac_func`\" = yes"; then - { echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } + { $as_echo "$as_me:$LINENO: result: yes" >&5 +$as_echo "yes" >&6; } ac_tr_func=`echo HAVE_$ac_func | tr '[a-z]' '[A-Z]'` @@ -10407,8 +11736,8 @@ ac_tr_func=`echo HAVE_$ac_func | tr '[a-z]' '[A-Z]'` _ACEOF else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi done @@ -10427,10 +11756,10 @@ _ACEOF fi -{ echo "$as_me:$LINENO: checking for ANSI C header files" >&5 -echo $ECHO_N "checking for ANSI C header files... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for ANSI C header files" >&5 +$as_echo_n "checking for ANSI C header files... " >&6; } if test "${ac_cv_header_stdc+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -10457,20 +11786,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_header_stdc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_header_stdc=no @@ -10562,37 +11892,40 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then : else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) ac_cv_header_stdc=no fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi fi fi -{ echo "$as_me:$LINENO: result: $ac_cv_header_stdc" >&5 -echo "${ECHO_T}$ac_cv_header_stdc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_header_stdc" >&5 +$as_echo "$ac_cv_header_stdc" >&6; } if test $ac_cv_header_stdc = yes; then cat >>confdefs.h <<\_ACEOF @@ -10608,20 +11941,21 @@ fi for ac_header in stdarg.h sys/ioctl.h ioctl.h sysexits.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -10637,32 +11971,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -10676,69 +12011,73 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi @@ -10749,20 +12088,21 @@ done for ac_header in sys/time.h sys/resource.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -10778,32 +12118,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -10817,69 +12158,73 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi @@ -10889,20 +12234,21 @@ done for ac_header in unix.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -10918,32 +12264,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -10957,69 +12304,73 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi @@ -11031,11 +12382,11 @@ done for ac_func in setrlimit getsid do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -11088,45 +12439,52 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi done -{ echo "$as_me:$LINENO: checking return type of signal handlers" >&5 -echo $ECHO_N "checking return type of signal handlers... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking return type of signal handlers" >&5 +$as_echo_n "checking return type of signal handlers... " >&6; } if test "${ac_cv_type_signal+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -11151,20 +12509,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_type_signal=int else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_type_signal=void @@ -11172,8 +12531,8 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_type_signal" >&5 -echo "${ECHO_T}$ac_cv_type_signal" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_type_signal" >&5 +$as_echo "$ac_cv_type_signal" >&6; } cat >>confdefs.h <<_ACEOF #define RETSIGTYPE $ac_cv_type_signal @@ -11181,8 +12540,8 @@ _ACEOF -{ echo "$as_me:$LINENO: checking for sig_atomic_t in signal.h" >&5 -echo $ECHO_N "checking for sig_atomic_t in signal.h... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for sig_atomic_t in signal.h" >&5 +$as_echo_n "checking for sig_atomic_t in signal.h... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -11209,14 +12568,14 @@ if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | $EGREP "volatile.*sig_atomic_t" >/dev/null 2>&1; then is_sig_atomic_t_volatile=yes; - { echo "$as_me:$LINENO: result: yes, volatile" >&5 -echo "${ECHO_T}yes, volatile" >&6; } + { $as_echo "$as_me:$LINENO: result: yes, volatile" >&5 +$as_echo "yes, volatile" >&6; } else is_sig_atomic_t_volatile=no; - { echo "$as_me:$LINENO: result: yes, non volatile" >&5 -echo "${ECHO_T}yes, non volatile" >&6; } + { $as_echo "$as_me:$LINENO: result: yes, non volatile" >&5 +$as_echo "yes, non volatile" >&6; } fi rm -f conftest* @@ -11224,28 +12583,60 @@ rm -f conftest* else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } - { echo "$as_me:$LINENO: checking for sig_atomic_t" >&5 -echo $ECHO_N "checking for sig_atomic_t... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } + { $as_echo "$as_me:$LINENO: checking for sig_atomic_t" >&5 +$as_echo_n "checking for sig_atomic_t... " >&6; } if test "${ac_cv_type_sig_atomic_t+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else - cat >conftest.$ac_ext <<_ACEOF + ac_cv_type_sig_atomic_t=no +cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default -typedef sig_atomic_t ac__type_new_; int main () { -if ((ac__type_new_ *) 0) - return 0; -if (sizeof (ac__type_new_)) +if (sizeof (sig_atomic_t)) + return 0; + ; return 0; +} +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +$ac_includes_default +int +main () +{ +if (sizeof ((sig_atomic_t))) + return 0; ; return 0; } @@ -11256,30 +12647,39 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then - ac_cv_type_sig_atomic_t=yes + : +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_cv_type_sig_atomic_t=yes +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 - ac_cv_type_sig_atomic_t=no + fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_type_sig_atomic_t" >&5 -echo "${ECHO_T}$ac_cv_type_sig_atomic_t" >&6; } -if test $ac_cv_type_sig_atomic_t = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_type_sig_atomic_t" >&5 +$as_echo "$ac_cv_type_sig_atomic_t" >&6; } +if test "x$ac_cv_type_sig_atomic_t" = x""yes; then : else @@ -11307,10 +12707,10 @@ _ACEOF fi -{ echo "$as_me:$LINENO: checking whether sys_siglist is declared" >&5 -echo $ECHO_N "checking whether sys_siglist is declared... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether sys_siglist is declared" >&5 +$as_echo_n "checking whether sys_siglist is declared... " >&6; } if test "${ac_cv_have_decl_sys_siglist+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -11342,20 +12742,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_cv_have_decl_sys_siglist=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_have_decl_sys_siglist=no @@ -11363,9 +12764,9 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_have_decl_sys_siglist" >&5 -echo "${ECHO_T}$ac_cv_have_decl_sys_siglist" >&6; } -if test $ac_cv_have_decl_sys_siglist = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_have_decl_sys_siglist" >&5 +$as_echo "$ac_cv_have_decl_sys_siglist" >&6; } +if test "x$ac_cv_have_decl_sys_siglist" = x""yes; then cat >>confdefs.h <<_ACEOF #define HAVE_DECL_SYS_SIGLIST 1 @@ -11383,26 +12784,58 @@ fi -{ echo "$as_me:$LINENO: checking for pid_t" >&5 -echo $ECHO_N "checking for pid_t... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for pid_t" >&5 +$as_echo_n "checking for pid_t... " >&6; } if test "${ac_cv_type_pid_t+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else - cat >conftest.$ac_ext <<_ACEOF + ac_cv_type_pid_t=no +cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default -typedef pid_t ac__type_new_; int main () { -if ((ac__type_new_ *) 0) - return 0; -if (sizeof (ac__type_new_)) +if (sizeof (pid_t)) + return 0; + ; return 0; +} +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +$ac_includes_default +int +main () +{ +if (sizeof ((pid_t))) + return 0; ; return 0; } @@ -11413,30 +12846,39 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then - ac_cv_type_pid_t=yes + : +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_cv_type_pid_t=yes +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 - ac_cv_type_pid_t=no + fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_type_pid_t" >&5 -echo "${ECHO_T}$ac_cv_type_pid_t" >&6; } -if test $ac_cv_type_pid_t = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_type_pid_t" >&5 +$as_echo "$ac_cv_type_pid_t" >&6; } +if test "x$ac_cv_type_pid_t" = x""yes; then : else @@ -11446,26 +12888,58 @@ _ACEOF fi -{ echo "$as_me:$LINENO: checking for ssize_t" >&5 -echo $ECHO_N "checking for ssize_t... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for ssize_t" >&5 +$as_echo_n "checking for ssize_t... " >&6; } if test "${ac_cv_type_ssize_t+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else - cat >conftest.$ac_ext <<_ACEOF + ac_cv_type_ssize_t=no +cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default -typedef ssize_t ac__type_new_; int main () { -if ((ac__type_new_ *) 0) - return 0; -if (sizeof (ac__type_new_)) +if (sizeof (ssize_t)) + return 0; + ; return 0; +} +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +$ac_includes_default +int +main () +{ +if (sizeof ((ssize_t))) + return 0; ; return 0; } @@ -11476,38 +12950,153 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + : +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_cv_type_ssize_t=yes +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +fi +{ $as_echo "$as_me:$LINENO: result: $ac_cv_type_ssize_t" >&5 +$as_echo "$ac_cv_type_ssize_t" >&6; } +if test "x$ac_cv_type_ssize_t" = x""yes; then + : +else + +cat >>confdefs.h <<_ACEOF +#define ssize_t int +_ACEOF + +fi + + + + + + + +for ac_func in fgetpos memmove setegid srand48 strerror +do +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } +if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then + $as_echo_n "(cached) " >&6 +else + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +/* Define $ac_func to an innocuous variant, in case declares $ac_func. + For example, HP-UX 11i declares gettimeofday. */ +#define $ac_func innocuous_$ac_func + +/* System header to define __stub macros and hopefully few prototypes, + which can conflict with char $ac_func (); below. + Prefer to if __STDC__ is defined, since + exists even on freestanding compilers. */ + +#ifdef __STDC__ +# include +#else +# include +#endif + +#undef $ac_func + +/* Override any GCC internal prototype to avoid an error. + Use char because int might match the return type of a GCC + builtin and then its argument prototype would still apply. */ +#ifdef __cplusplus +extern "C" +#endif +char $ac_func (); +/* The GNU C library defines this for functions which it implements + to always fail with ENOSYS. Some functions are actually named + something starting with __ and the normal name is an alias. */ +#if defined __stub_$ac_func || defined __stub___$ac_func +choke me +#endif + +int +main () +{ +return $ac_func (); + ; + return 0; +} +_ACEOF +rm -f conftest.$ac_objext conftest$ac_exeext +if { (ac_try="$ac_link" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_link") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest.$ac_objext; then - ac_cv_type_ssize_t=yes + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then + eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 - ac_cv_type_ssize_t=no + eval "$as_ac_var=no" fi -rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +rm -rf conftest.dSYM +rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ + conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_type_ssize_t" >&5 -echo "${ECHO_T}$ac_cv_type_ssize_t" >&6; } -if test $ac_cv_type_ssize_t = yes; then - : -else - -cat >>confdefs.h <<_ACEOF -#define ssize_t int +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then + cat >>confdefs.h <<_ACEOF +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi +done @@ -11515,13 +13104,14 @@ fi -for ac_func in fgetpos memmove setegid srand48 strerror + +for ac_func in setenv strcasecmp strdup strsep strtok_r wcscasecmp do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -11574,53 +13164,64 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF +else + case " $LIBOBJS " in + *" $ac_func.$ac_objext "* ) ;; + *) LIBOBJS="$LIBOBJS $ac_func.$ac_objext" + ;; +esac + fi done - - - -for ac_func in setenv strcasecmp strdup strsep strtok_r +for ac_func in strcasestr mkdtemp do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -11673,35 +13274,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF else @@ -11716,10 +13324,10 @@ done -{ echo "$as_me:$LINENO: checking for getopt" >&5 -echo $ECHO_N "checking for getopt... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for getopt" >&5 +$as_echo_n "checking for getopt... " >&6; } if test "${ac_cv_func_getopt+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -11772,50 +13380,55 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_func_getopt=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_func_getopt=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_func_getopt" >&5 -echo "${ECHO_T}$ac_cv_func_getopt" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_func_getopt" >&5 +$as_echo "$ac_cv_func_getopt" >&6; } if test $ac_cv_func_getopt = yes; then for ac_header in getopt.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -11831,32 +13444,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -11870,69 +13484,73 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi @@ -11942,10 +13560,10 @@ done fi SNPRINTFOBJS="" -{ echo "$as_me:$LINENO: checking for snprintf" >&5 -echo $ECHO_N "checking for snprintf... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for snprintf" >&5 +$as_echo_n "checking for snprintf... " >&6; } if test "${ac_cv_func_snprintf+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -11998,41 +13616,45 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_func_snprintf=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_func_snprintf=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_func_snprintf" >&5 -echo "${ECHO_T}$ac_cv_func_snprintf" >&6; } -if test $ac_cv_func_snprintf = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_func_snprintf" >&5 +$as_echo "$ac_cv_func_snprintf" >&6; } +if test "x$ac_cv_func_snprintf" = x""yes; then mutt_cv_func_snprintf=yes else mutt_cv_func_snprintf=no fi -{ echo "$as_me:$LINENO: checking for vsnprintf" >&5 -echo $ECHO_N "checking for vsnprintf... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for vsnprintf" >&5 +$as_echo_n "checking for vsnprintf... " >&6; } if test "${ac_cv_func_vsnprintf+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -12085,42 +13707,46 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_func_vsnprintf=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_func_vsnprintf=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_func_vsnprintf" >&5 -echo "${ECHO_T}$ac_cv_func_vsnprintf" >&6; } -if test $ac_cv_func_vsnprintf = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_func_vsnprintf" >&5 +$as_echo "$ac_cv_func_vsnprintf" >&6; } +if test "x$ac_cv_func_vsnprintf" = x""yes; then mutt_cv_func_vsnprintf=yes else mutt_cv_func_vsnprintf=no fi if test $mutt_cv_func_snprintf = yes; then -{ echo "$as_me:$LINENO: checking whether your system's snprintf is C99 compliant" >&5 -echo $ECHO_N "checking whether your system's snprintf is C99 compliant... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether your system's snprintf is C99 compliant" >&5 +$as_echo_n "checking whether your system's snprintf is C99 compliant... " >&6; } if test "${mutt_cv_c99_snprintf+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test "$cross_compiling" = yes; then mutt_cv_c99_snprintf=no @@ -12147,44 +13773,47 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then mutt_cv_c99_snprintf=yes else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) mutt_cv_c99_snprintf=no fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi fi -{ echo "$as_me:$LINENO: result: $mutt_cv_c99_snprintf" >&5 -echo "${ECHO_T}$mutt_cv_c99_snprintf" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_c99_snprintf" >&5 +$as_echo "$mutt_cv_c99_snprintf" >&6; } else mutt_cv_c99_snprintf=no fi if test $mutt_cv_func_vsnprintf = yes; then -{ echo "$as_me:$LINENO: checking whether your system's vsnprintf is C99 compliant" >&5 -echo $ECHO_N "checking whether your system's vsnprintf is C99 compliant... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether your system's vsnprintf is C99 compliant" >&5 +$as_echo_n "checking whether your system's vsnprintf is C99 compliant... " >&6; } if test "${mutt_cv_c99_vsnprintf+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test "$cross_compiling" = yes; then mutt_cv_c99_vsnprintf=no @@ -12221,36 +13850,39 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then mutt_cv_c99_vsnprintf=yes else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) mutt_cv_c99_vsnprintf=no fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi fi -{ echo "$as_me:$LINENO: result: $mutt_cv_c99_vsnprintf" >&5 -echo "${ECHO_T}$mutt_cv_c99_vsnprintf" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_c99_vsnprintf" >&5 +$as_echo "$mutt_cv_c99_vsnprintf" >&6; } else mutt_cv_c99_vsnprintf=no fi @@ -12277,8 +13909,8 @@ esac fi -{ echo "$as_me:$LINENO: checking for va_copy" >&5 -echo $ECHO_N "checking for va_copy... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for va_copy" >&5 +$as_echo_n "checking for va_copy... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -12300,22 +13932,25 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then - { echo "$as_me:$LINENO: result: va_copy" >&5 -echo "${ECHO_T}va_copy" >&6; } + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then + { $as_echo "$as_me:$LINENO: result: va_copy" >&5 +$as_echo "va_copy" >&6; } else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 @@ -12341,42 +13976,47 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then cat >>confdefs.h <<\_ACEOF #define va_copy __va_copy _ACEOF - { echo "$as_me:$LINENO: result: __va_copy" >&5 -echo "${ECHO_T}__va_copy" >&6; } + { $as_echo "$as_me:$LINENO: result: __va_copy" >&5 +$as_echo "__va_copy" >&6; } else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 cat >>confdefs.h <<\_ACEOF #define va_copy(dest,src) memcpy(&dest,&src,sizeof(va_list)) _ACEOF - { echo "$as_me:$LINENO: result: memcpy" >&5 -echo "${ECHO_T}memcpy" >&6; } + { $as_echo "$as_me:$LINENO: result: memcpy" >&5 +$as_echo "memcpy" >&6; } fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext @@ -12384,11 +14024,11 @@ rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ for ac_func in ftruncate do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -12441,43 +14081,50 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF else -{ echo "$as_me:$LINENO: checking for chsize in -lx" >&5 -echo $ECHO_N "checking for chsize in -lx... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for chsize in -lx" >&5 +$as_echo_n "checking for chsize in -lx... " >&6; } if test "${ac_cv_lib_x_chsize+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lx $LIBS" @@ -12509,33 +14156,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_x_chsize=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_x_chsize=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_x_chsize" >&5 -echo "${ECHO_T}$ac_cv_lib_x_chsize" >&6; } -if test $ac_cv_lib_x_chsize = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_x_chsize" >&5 +$as_echo "$ac_cv_lib_x_chsize" >&6; } +if test "x$ac_cv_lib_x_chsize" = x""yes; then cat >>confdefs.h <<_ACEOF #define HAVE_LIBX 1 _ACEOF @@ -12551,11 +14202,11 @@ done for ac_func in strftime do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -12608,43 +14259,50 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF else -{ echo "$as_me:$LINENO: checking for strftime in -lintl" >&5 -echo $ECHO_N "checking for strftime in -lintl... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for strftime in -lintl" >&5 +$as_echo_n "checking for strftime in -lintl... " >&6; } if test "${ac_cv_lib_intl_strftime+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lintl $LIBS" @@ -12676,33 +14334,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_intl_strftime=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_intl_strftime=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_intl_strftime" >&5 -echo "${ECHO_T}$ac_cv_lib_intl_strftime" >&6; } -if test $ac_cv_lib_intl_strftime = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_intl_strftime" >&5 +$as_echo "$ac_cv_lib_intl_strftime" >&6; } +if test "x$ac_cv_lib_intl_strftime" = x""yes; then cat >>confdefs.h <<_ACEOF #define HAVE_LIBINTL 1 _ACEOF @@ -12718,11 +14380,11 @@ done for ac_func in fchdir do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -12775,35 +14437,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF else @@ -12820,11 +14489,11 @@ else for ac_func in regcomp do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -12877,35 +14546,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF mutt_cv_regex=no else @@ -12917,10 +14593,10 @@ fi if test $mutt_cv_regex = no ; then -{ echo "$as_me:$LINENO: checking whether your system's regexp library is completely broken" >&5 -echo $ECHO_N "checking whether your system's regexp library is completely broken... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether your system's regexp library is completely broken" >&5 +$as_echo_n "checking whether your system's regexp library is completely broken... " >&6; } if test "${mutt_cv_regex_broken+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test "$cross_compiling" = yes; then mutt_cv_regex_broken=yes @@ -12942,36 +14618,39 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then mutt_cv_regex_broken=no else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) mutt_cv_regex_broken=yes fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi fi -{ echo "$as_me:$LINENO: result: $mutt_cv_regex_broken" >&5 -echo "${ECHO_T}$mutt_cv_regex_broken" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_regex_broken" >&5 +$as_echo "$mutt_cv_regex_broken" >&6; } if test $mutt_cv_regex_broken = yes ; then echo "Using the included GNU regex instead." >&6 mutt_cv_regex=yes @@ -13025,10 +14704,10 @@ else if test "${with_mailpath+set}" = set; then withval=$with_mailpath; mutt_cv_mailpath=$withval else - { echo "$as_me:$LINENO: checking where new mail is stored" >&5 -echo $ECHO_N "checking where new mail is stored... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking where new mail is stored" >&5 +$as_echo_n "checking where new mail is stored... " >&6; } if test "${mutt_cv_mailpath+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else mutt_cv_mailpath=no if test -d /var/mail; then @@ -13041,14 +14720,14 @@ else mutt_cv_mailpath=/usr/mail fi fi -{ echo "$as_me:$LINENO: result: $mutt_cv_mailpath" >&5 -echo "${ECHO_T}$mutt_cv_mailpath" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_mailpath" >&5 +$as_echo "$mutt_cv_mailpath" >&6; } fi if test "$mutt_cv_mailpath" = no; then - { { echo "$as_me:$LINENO: error: \"Could not determine where new mail is stored.\"" >&5 -echo "$as_me: error: \"Could not determine where new mail is stored.\"" >&2;} + { { $as_echo "$as_me:$LINENO: error: \"Could not determine where new mail is stored.\"" >&5 +$as_echo "$as_me: error: \"Could not determine where new mail is stored.\"" >&2;} { (exit 1); exit 1; }; } fi @@ -13057,10 +14736,10 @@ cat >>confdefs.h <<_ACEOF _ACEOF - { echo "$as_me:$LINENO: checking if $mutt_cv_mailpath is world writable" >&5 -echo $ECHO_N "checking if $mutt_cv_mailpath is world writable... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking if $mutt_cv_mailpath is world writable" >&5 +$as_echo_n "checking if $mutt_cv_mailpath is world writable... " >&6; } if test "${mutt_cv_worldwrite+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test "$cross_compiling" = yes; then mutt_cv_worldwrite=no @@ -13090,36 +14769,39 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then mutt_cv_worldwrite=yes else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) mutt_cv_worldwrite=no fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi fi -{ echo "$as_me:$LINENO: result: $mutt_cv_worldwrite" >&5 -echo "${ECHO_T}$mutt_cv_worldwrite" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_worldwrite" >&5 +$as_echo "$mutt_cv_worldwrite" >&6; } mutt_cv_setgid=no if test $mutt_cv_worldwrite = yes; then @@ -13130,10 +14812,10 @@ _ACEOF else - { echo "$as_me:$LINENO: checking if $mutt_cv_mailpath is group writable" >&5 -echo $ECHO_N "checking if $mutt_cv_mailpath is group writable... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking if $mutt_cv_mailpath is group writable" >&5 +$as_echo_n "checking if $mutt_cv_mailpath is group writable... " >&6; } if test "${mutt_cv_groupwrite+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test "$cross_compiling" = yes; then mutt_cv_groupwrite=no @@ -13163,36 +14845,39 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then mutt_cv_groupwrite=yes else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) mutt_cv_groupwrite=no fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi fi -{ echo "$as_me:$LINENO: result: $mutt_cv_groupwrite" >&5 -echo "${ECHO_T}$mutt_cv_groupwrite" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_groupwrite" >&5 +$as_echo "$mutt_cv_groupwrite" >&6; } if test $mutt_cv_groupwrite = yes; then @@ -13236,8 +14921,8 @@ if test -z "$datarootdir"; then fi -{ echo "$as_me:$LINENO: checking where to put the documentation" >&5 -echo $ECHO_N "checking where to put the documentation... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking where to put the documentation" >&5 +$as_echo_n "checking where to put the documentation... " >&6; } # Check whether --with-docdir was given. if test "${with_docdir+set}" = set; then @@ -13246,8 +14931,8 @@ else mutt_cv_docdir='${datarootdir}/doc/mutt' fi -{ echo "$as_me:$LINENO: result: $mutt_cv_docdir" >&5 -echo "${ECHO_T}$mutt_cv_docdir" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_docdir" >&5 +$as_echo "$mutt_cv_docdir" >&6; } docdir=$mutt_cv_docdir @@ -13347,20 +15032,21 @@ then for ac_header in sys/select.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -13376,32 +15062,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -13415,77 +15102,81 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi done - { echo "$as_me:$LINENO: checking for socklen_t" >&5 -echo $ECHO_N "checking for socklen_t... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for socklen_t" >&5 +$as_echo_n "checking for socklen_t... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -13497,11 +15188,11 @@ cat >>conftest.$ac_ext <<_ACEOF _ACEOF if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | $EGREP "socklen_t" >/dev/null 2>&1; then - { echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } + { $as_echo "$as_me:$LINENO: result: yes" >&5 +$as_echo "yes" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } cat >>confdefs.h <<\_ACEOF #define socklen_t int @@ -13510,10 +15201,10 @@ _ACEOF fi rm -f conftest* - { echo "$as_me:$LINENO: checking for gethostent" >&5 -echo $ECHO_N "checking for gethostent... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for gethostent" >&5 +$as_echo_n "checking for gethostent... " >&6; } if test "${ac_cv_func_gethostent+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -13566,39 +15257,43 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_func_gethostent=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_func_gethostent=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_func_gethostent" >&5 -echo "${ECHO_T}$ac_cv_func_gethostent" >&6; } -if test $ac_cv_func_gethostent = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_func_gethostent" >&5 +$as_echo "$ac_cv_func_gethostent" >&6; } +if test "x$ac_cv_func_gethostent" = x""yes; then : else -{ echo "$as_me:$LINENO: checking for gethostent in -lnsl" >&5 -echo $ECHO_N "checking for gethostent in -lnsl... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for gethostent in -lnsl" >&5 +$as_echo_n "checking for gethostent in -lnsl... " >&6; } if test "${ac_cv_lib_nsl_gethostent+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lnsl $LIBS" @@ -13630,33 +15325,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_nsl_gethostent=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_nsl_gethostent=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_nsl_gethostent" >&5 -echo "${ECHO_T}$ac_cv_lib_nsl_gethostent" >&6; } -if test $ac_cv_lib_nsl_gethostent = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_nsl_gethostent" >&5 +$as_echo "$ac_cv_lib_nsl_gethostent" >&6; } +if test "x$ac_cv_lib_nsl_gethostent" = x""yes; then cat >>confdefs.h <<_ACEOF #define HAVE_LIBNSL 1 _ACEOF @@ -13667,10 +15366,10 @@ fi fi - { echo "$as_me:$LINENO: checking for setsockopt" >&5 -echo $ECHO_N "checking for setsockopt... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for setsockopt" >&5 +$as_echo_n "checking for setsockopt... " >&6; } if test "${ac_cv_func_setsockopt+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -13723,39 +15422,43 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_func_setsockopt=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_func_setsockopt=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_func_setsockopt" >&5 -echo "${ECHO_T}$ac_cv_func_setsockopt" >&6; } -if test $ac_cv_func_setsockopt = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_func_setsockopt" >&5 +$as_echo "$ac_cv_func_setsockopt" >&6; } +if test "x$ac_cv_func_setsockopt" = x""yes; then : else -{ echo "$as_me:$LINENO: checking for setsockopt in -lsocket" >&5 -echo $ECHO_N "checking for setsockopt in -lsocket... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for setsockopt in -lsocket" >&5 +$as_echo_n "checking for setsockopt in -lsocket... " >&6; } if test "${ac_cv_lib_socket_setsockopt+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lsocket $LIBS" @@ -13787,33 +15490,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_socket_setsockopt=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_socket_setsockopt=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_socket_setsockopt" >&5 -echo "${ECHO_T}$ac_cv_lib_socket_setsockopt" >&6; } -if test $ac_cv_lib_socket_setsockopt = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_socket_setsockopt" >&5 +$as_echo "$ac_cv_lib_socket_setsockopt" >&6; } +if test "x$ac_cv_lib_socket_setsockopt" = x""yes; then cat >>confdefs.h <<_ACEOF #define HAVE_LIBSOCKET 1 _ACEOF @@ -13827,11 +15534,11 @@ fi for ac_func in getaddrinfo do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -13884,35 +15591,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi @@ -13953,10 +15667,10 @@ then fi # Extract the first word of "krb5-config", so it can be a program name with args. set dummy krb5-config; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_KRB5CFGPATH+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case $KRB5CFGPATH in [\\/]* | ?:[\\/]*) @@ -13971,7 +15685,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_path_KRB5CFGPATH="$as_dir/$ac_word$ac_exec_ext" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -13984,11 +15698,11 @@ esac fi KRB5CFGPATH=$ac_cv_path_KRB5CFGPATH if test -n "$KRB5CFGPATH"; then - { echo "$as_me:$LINENO: result: $KRB5CFGPATH" >&5 -echo "${ECHO_T}$KRB5CFGPATH" >&6; } + { $as_echo "$as_me:$LINENO: result: $KRB5CFGPATH" >&5 +$as_echo "$KRB5CFGPATH" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -14010,10 +15724,10 @@ fi LDFLAGS="$LDFLAGS $GSSAPI_LDFLAGS" fi - { echo "$as_me:$LINENO: checking for gss_init_sec_context in -lgssapi_krb5" >&5 -echo $ECHO_N "checking for gss_init_sec_context in -lgssapi_krb5... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for gss_init_sec_context in -lgssapi_krb5" >&5 +$as_echo_n "checking for gss_init_sec_context in -lgssapi_krb5... " >&6; } if test "${ac_cv_lib_gssapi_krb5_gss_init_sec_context+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err $LIBS" @@ -14045,33 +15759,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_gssapi_krb5_gss_init_sec_context=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_gssapi_krb5_gss_init_sec_context=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_gssapi_krb5_gss_init_sec_context" >&5 -echo "${ECHO_T}$ac_cv_lib_gssapi_krb5_gss_init_sec_context" >&6; } -if test $ac_cv_lib_gssapi_krb5_gss_init_sec_context = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_gssapi_krb5_gss_init_sec_context" >&5 +$as_echo "$ac_cv_lib_gssapi_krb5_gss_init_sec_context" >&6; } +if test "x$ac_cv_lib_gssapi_krb5_gss_init_sec_context" = x""yes; then GSSAPI_IMPL="MIT", GSSAPI_LIBS="$GSSAPI_LDFLAGS -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err" @@ -14081,10 +15799,10 @@ fi if test "$GSSAPI_IMPL" = "none" then - { echo "$as_me:$LINENO: checking for gss_init_sec_context in -lgssapi" >&5 -echo $ECHO_N "checking for gss_init_sec_context in -lgssapi... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for gss_init_sec_context in -lgssapi" >&5 +$as_echo_n "checking for gss_init_sec_context in -lgssapi... " >&6; } if test "${ac_cv_lib_gssapi_gss_init_sec_context+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lgssapi -lkrb5 -ldes -lasn1 -lroken -lcrypt -lcom_err $LIBS" @@ -14116,33 +15834,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_gssapi_gss_init_sec_context=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_gssapi_gss_init_sec_context=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_gssapi_gss_init_sec_context" >&5 -echo "${ECHO_T}$ac_cv_lib_gssapi_gss_init_sec_context" >&6; } -if test $ac_cv_lib_gssapi_gss_init_sec_context = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_gssapi_gss_init_sec_context" >&5 +$as_echo "$ac_cv_lib_gssapi_gss_init_sec_context" >&6; } +if test "x$ac_cv_lib_gssapi_gss_init_sec_context" = x""yes; then GSSAPI_IMPL="Heimdal" GSSAPI_LIBS="$GSSAPI_LDFLAGS -lgssapi -lkrb5 -ldes -lasn1 -lroken" @@ -14154,10 +15876,10 @@ fi if test "$GSSAPI_IMPL" = "none" then - { echo "$as_me:$LINENO: checking for g_order_init in -lgssapi_krb5" >&5 -echo $ECHO_N "checking for g_order_init in -lgssapi_krb5... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for g_order_init in -lgssapi_krb5" >&5 +$as_echo_n "checking for g_order_init in -lgssapi_krb5... " >&6; } if test "${ac_cv_lib_gssapi_krb5_g_order_init+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lgssapi_krb5 -lkrb5 -lcrypto -lcom_err $LIBS" @@ -14189,33 +15911,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_gssapi_krb5_g_order_init=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_gssapi_krb5_g_order_init=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_gssapi_krb5_g_order_init" >&5 -echo "${ECHO_T}$ac_cv_lib_gssapi_krb5_g_order_init" >&6; } -if test $ac_cv_lib_gssapi_krb5_g_order_init = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_gssapi_krb5_g_order_init" >&5 +$as_echo "$ac_cv_lib_gssapi_krb5_g_order_init" >&6; } +if test "x$ac_cv_lib_gssapi_krb5_g_order_init" = x""yes; then GSSAPI_IMPL="OldMIT", GSSAPI_LIBS="$GSSAPI_LDFLAGS -lgssapi_krb5 -lkrb5 -lcrypto -lcom_err" @@ -14229,10 +15955,10 @@ fi LDFLAGS="$saved_LDFLAGS" LIBS="$saved_LIBS" - { echo "$as_me:$LINENO: checking GSSAPI implementation" >&5 -echo $ECHO_N "checking GSSAPI implementation... $ECHO_C" >&6; } - { echo "$as_me:$LINENO: result: $GSSAPI_IMPL" >&5 -echo "${ECHO_T}$GSSAPI_IMPL" >&6; } + { $as_echo "$as_me:$LINENO: checking GSSAPI implementation" >&5 +$as_echo_n "checking GSSAPI implementation... " >&6; } + { $as_echo "$as_me:$LINENO: result: $GSSAPI_IMPL" >&5 +$as_echo "$GSSAPI_IMPL" >&6; } if test "$GSSAPI_IMPL" = "none" then cat >confcache <<\_ACEOF @@ -14262,11 +15988,12 @@ _ACEOF case $ac_val in #( *${as_nl}*) case $ac_var in #( - *_cv_*) { echo "$as_me:$LINENO: WARNING: Cache variable $ac_var contains a newline." >&5 -echo "$as_me: WARNING: Cache variable $ac_var contains a newline." >&2;} ;; + *_cv_*) { $as_echo "$as_me:$LINENO: WARNING: cache variable $ac_var contains a newline" >&5 +$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;; esac case $ac_var in #( _ | IFS | as_nl) ;; #( + BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #( *) $as_unset $ac_var ;; esac ;; esac @@ -14299,17 +16026,17 @@ echo "$as_me: WARNING: Cache variable $ac_var contains a newline." >&2;} ;; if diff "$cache_file" confcache >/dev/null 2>&1; then :; else if test -w "$cache_file"; then test "x$cache_file" != "x/dev/null" && - { echo "$as_me:$LINENO: updating cache $cache_file" >&5 -echo "$as_me: updating cache $cache_file" >&6;} + { $as_echo "$as_me:$LINENO: updating cache $cache_file" >&5 +$as_echo "$as_me: updating cache $cache_file" >&6;} cat confcache >$cache_file else - { echo "$as_me:$LINENO: not updating unwritable cache $cache_file" >&5 -echo "$as_me: not updating unwritable cache $cache_file" >&6;} + { $as_echo "$as_me:$LINENO: not updating unwritable cache $cache_file" >&5 +$as_echo "$as_me: not updating unwritable cache $cache_file" >&6;} fi fi rm -f confcache - { echo "$as_me:$LINENO: result: GSSAPI libraries not found" >&5 -echo "${ECHO_T}GSSAPI libraries not found" >&6; } + { $as_echo "$as_me:$LINENO: result: GSSAPI libraries not found" >&5 +$as_echo "GSSAPI libraries not found" >&6; } fi if test "$GSSAPI_IMPL" = "Heimdal" then @@ -14328,8 +16055,8 @@ _ACEOF need_gss="yes" else - { echo "$as_me:$LINENO: WARNING: GSS was requested but IMAP is not enabled" >&5 -echo "$as_me: WARNING: GSS was requested but IMAP is not enabled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: GSS was requested but IMAP is not enabled" >&5 +$as_echo "$as_me: WARNING: GSS was requested but IMAP is not enabled" >&2;} fi fi if test x$need_gss = xyes; then @@ -14348,8 +16075,8 @@ if test "${with_ssl+set}" = set; then withval=$with_ssl; if test "$with_ssl" != "no" then if test "$need_socket" != "yes"; then - { echo "$as_me:$LINENO: WARNING: SSL support is only useful with POP, IMAP or SMTP support" >&5 -echo "$as_me: WARNING: SSL support is only useful with POP, IMAP or SMTP support" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: SSL support is only useful with POP, IMAP or SMTP support" >&5 +$as_echo "$as_me: WARNING: SSL support is only useful with POP, IMAP or SMTP support" >&2;} else if test "$with_ssl" != "yes" then @@ -14359,10 +16086,10 @@ echo "$as_me: WARNING: SSL support is only useful with POP, IMAP or SMTP support saved_LIBS="$LIBS" crypto_libs="" - { echo "$as_me:$LINENO: checking for deflate in -lz" >&5 -echo $ECHO_N "checking for deflate in -lz... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for deflate in -lz" >&5 +$as_echo_n "checking for deflate in -lz... " >&6; } if test "${ac_cv_lib_z_deflate+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lz $LIBS" @@ -14394,40 +16121,44 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_z_deflate=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_z_deflate=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_z_deflate" >&5 -echo "${ECHO_T}$ac_cv_lib_z_deflate" >&6; } -if test $ac_cv_lib_z_deflate = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_z_deflate" >&5 +$as_echo "$ac_cv_lib_z_deflate" >&6; } +if test "x$ac_cv_lib_z_deflate" = x""yes; then crypto_libs=-lz fi - { echo "$as_me:$LINENO: checking for X509_new in -lcrypto" >&5 -echo $ECHO_N "checking for X509_new in -lcrypto... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for X509_new in -lcrypto" >&5 +$as_echo_n "checking for X509_new in -lcrypto... " >&6; } if test "${ac_cv_lib_crypto_X509_new+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lcrypto $crypto_libs $LIBS" @@ -14459,41 +16190,45 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_crypto_X509_new=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_crypto_X509_new=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_crypto_X509_new" >&5 -echo "${ECHO_T}$ac_cv_lib_crypto_X509_new" >&6; } -if test $ac_cv_lib_crypto_X509_new = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_crypto_X509_new" >&5 +$as_echo "$ac_cv_lib_crypto_X509_new" >&6; } +if test "x$ac_cv_lib_crypto_X509_new" = x""yes; then crypto_libs="-lcrypto $crypto_libs" fi -{ echo "$as_me:$LINENO: checking for SSL_new in -lssl" >&5 -echo $ECHO_N "checking for SSL_new in -lssl... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for SSL_new in -lssl" >&5 +$as_echo_n "checking for SSL_new in -lssl... " >&6; } if test "${ac_cv_lib_ssl_SSL_new+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lssl $crypto_libs $LIBS" @@ -14525,33 +16260,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_ssl_SSL_new=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_ssl_SSL_new=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_ssl_SSL_new" >&5 -echo "${ECHO_T}$ac_cv_lib_ssl_SSL_new" >&6; } -if test $ac_cv_lib_ssl_SSL_new = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_ssl_SSL_new" >&5 +$as_echo "$ac_cv_lib_ssl_SSL_new" >&6; } +if test "x$ac_cv_lib_ssl_SSL_new" = x""yes; then cat >>confdefs.h <<_ACEOF #define HAVE_LIBSSL 1 _ACEOF @@ -14559,8 +16298,8 @@ _ACEOF LIBS="-lssl $LIBS" else - { { echo "$as_me:$LINENO: error: Unable to find SSL library" >&5 -echo "$as_me: error: Unable to find SSL library" >&2;} + { { $as_echo "$as_me:$LINENO: error: Unable to find SSL library" >&5 +$as_echo "$as_me: error: Unable to find SSL library" >&2;} { (exit 1); exit 1; }; } fi @@ -14570,11 +16309,11 @@ fi for ac_func in RAND_status RAND_egd do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -14627,35 +16366,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi @@ -14694,206 +16440,105 @@ if test "$gnutls_prefix" != "no" && test x"$need_ssl" != xyes then if test "$need_socket" != "yes" then - { echo "$as_me:$LINENO: WARNING: SSL support is only useful with POP, IMAP or SMTP support" >&5 -echo "$as_me: WARNING: SSL support is only useful with POP, IMAP or SMTP support" >&2;} - else - libgnutls_config_prefix=$gnutls_prefix - min_libgnutls_version=0.1.0 - - if test x$libgnutls_config_prefix != x ; then - if test x${LIBGNUTLS_CONFIG+set} != xset ; then - LIBGNUTLS_CONFIG=$libgnutls_config_prefix/bin/libgnutls-config - fi - fi - - # Extract the first word of "libgnutls-config", so it can be a program name with args. -set dummy libgnutls-config; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } -if test "${ac_cv_path_LIBGNUTLS_CONFIG+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - case $LIBGNUTLS_CONFIG in - [\\/]* | ?:[\\/]*) - ac_cv_path_LIBGNUTLS_CONFIG="$LIBGNUTLS_CONFIG" # Let the user override the test with a path. - ;; - *) - as_save_IFS=$IFS; IFS=$PATH_SEPARATOR -for as_dir in $PATH -do - IFS=$as_save_IFS - test -z "$as_dir" && as_dir=. - for ac_exec_ext in '' $ac_executable_extensions; do - if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then - ac_cv_path_LIBGNUTLS_CONFIG="$as_dir/$ac_word$ac_exec_ext" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 - break 2 - fi -done -done -IFS=$as_save_IFS - - test -z "$ac_cv_path_LIBGNUTLS_CONFIG" && ac_cv_path_LIBGNUTLS_CONFIG="no" - ;; -esac -fi -LIBGNUTLS_CONFIG=$ac_cv_path_LIBGNUTLS_CONFIG -if test -n "$LIBGNUTLS_CONFIG"; then - { echo "$as_me:$LINENO: result: $LIBGNUTLS_CONFIG" >&5 -echo "${ECHO_T}$LIBGNUTLS_CONFIG" >&6; } -else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } -fi - - - { echo "$as_me:$LINENO: checking for libgnutls - version >= $min_libgnutls_version" >&5 -echo $ECHO_N "checking for libgnutls - version >= $min_libgnutls_version... $ECHO_C" >&6; } - no_libgnutls="" - if test "$LIBGNUTLS_CONFIG" = "no" ; then - no_libgnutls=yes + { $as_echo "$as_me:$LINENO: WARNING: SSL support is only useful with POP, IMAP or SMTP support" >&5 +$as_echo "$as_me: WARNING: SSL support is only useful with POP, IMAP or SMTP support" >&2;} else - LIBGNUTLS_CFLAGS=`$LIBGNUTLS_CONFIG $libgnutls_config_args --cflags` - LIBGNUTLS_LIBS=`$LIBGNUTLS_CONFIG $libgnutls_config_args --libs` - libgnutls_config_version=`$LIBGNUTLS_CONFIG $libgnutls_config_args --version` - - - ac_save_CFLAGS="$CFLAGS" - ac_save_LIBS="$LIBS" - CFLAGS="$CFLAGS $LIBGNUTLS_CFLAGS" - LIBS="$LIBS $LIBGNUTLS_LIBS" + if test "$gnutls_prefix" != "yes" + then + LDFLAGS="$LDFLAGS -L$gnutls_prefix/lib" + CPPFLAGS="$CPPFLAGS -I$gnutls_prefix/include" + fi + saved_LIBS="$LIBS" - rm -f conf.libgnutlstest - if test "$cross_compiling" = yes; then - echo $ac_n "cross compiling; assumed OK... $ac_c" + { $as_echo "$as_me:$LINENO: checking for gnutls_check_version in -lgnutls" >&5 +$as_echo_n "checking for gnutls_check_version in -lgnutls... " >&6; } +if test "${ac_cv_lib_gnutls_gnutls_check_version+set}" = set; then + $as_echo_n "(cached) " >&6 else - cat >conftest.$ac_ext <<_ACEOF + ac_check_lib_save_LIBS=$LIBS +LIBS="-lgnutls $LIBS" +cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ -#include -#include -#include -#include - +/* Override any GCC internal prototype to avoid an error. + Use char because int might match the return type of a GCC + builtin and then its argument prototype would still apply. */ +#ifdef __cplusplus +extern "C" +#endif +char gnutls_check_version (); int main () { - system ("touch conf.libgnutlstest"); - - if( strcmp( gnutls_check_version(NULL), "$libgnutls_config_version" ) ) - { - printf("\n*** 'libgnutls-config --version' returned %s, but LIBGNUTLS (%s)\n", - "$libgnutls_config_version", gnutls_check_version(NULL) ); - printf("*** was found! If libgnutls-config was correct, then it is best\n"); - printf("*** to remove the old version of LIBGNUTLS. You may also be able to fix the error\n"); - printf("*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing\n"); - printf("*** /etc/ld.so.conf. Make sure you have run ldconfig if that is\n"); - printf("*** required on your system.\n"); - printf("*** If libgnutls-config was wrong, set the environment variable LIBGNUTLS_CONFIG\n"); - printf("*** to point to the correct copy of libgnutls-config, and remove the file config.cache\n"); - printf("*** before re-running configure\n"); - } - else if ( strcmp(gnutls_check_version(NULL), LIBGNUTLS_VERSION ) ) - { - printf("\n*** LIBGNUTLS header file (version %s) does not match\n", LIBGNUTLS_VERSION); - printf("*** library (version %s)\n", gnutls_check_version(NULL) ); - } - else - { - if ( gnutls_check_version( "$min_libgnutls_version" ) ) - { - return 0; - } - else - { - printf("no\n*** An old version of LIBGNUTLS (%s) was found.\n", - gnutls_check_version(NULL) ); - printf("*** You need a version of LIBGNUTLS newer than %s. The latest version of\n", - "$min_libgnutls_version" ); - printf("*** LIBGNUTLS is always available from ftp://gnutls.hellug.gr/pub/gnutls.\n"); - printf("*** \n"); - printf("*** If you have already installed a sufficiently new version, this error\n"); - printf("*** probably means that the wrong copy of the libgnutls-config shell script is\n"); - printf("*** being found. The easiest way to fix this is to remove the old version\n"); - printf("*** of LIBGNUTLS, but you can also set the LIBGNUTLS_CONFIG environment to point to the\n"); - printf("*** correct copy of libgnutls-config. (In this case, you will have to\n"); - printf("*** modify your LD_LIBRARY_PATH enviroment variable, or edit /etc/ld.so.conf\n"); - printf("*** so that the correct libraries are found at run-time))\n"); - } - } - return 1; +return gnutls_check_version (); + ; + return 0; } - _ACEOF -rm -f conftest$ac_exeext +rm -f conftest.$ac_objext conftest$ac_exeext if { (ac_try="$ac_link" case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_link") 2>&5 - ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); } && { ac_try='./conftest$ac_exeext' - { (case "(($ac_try" in - *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; - *) ac_try_echo=$ac_try;; -esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_try") 2>&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_link") 2>conftest.er1 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); }; }; then - : + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then + ac_cv_lib_gnutls_gnutls_check_version=yes else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 -( exit $ac_status ) -no_libgnutls=yes -fi -rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext + ac_cv_lib_gnutls_gnutls_check_version=no fi - - CFLAGS="$ac_save_CFLAGS" - LIBS="$ac_save_LIBS" - fi - - if test "x$no_libgnutls" = x ; then - { echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } - -for ac_header in gnutls/openssl.h -do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` -if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } -if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 +rm -rf conftest.dSYM +rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ + conftest$ac_exeext conftest.$ac_ext +LIBS=$ac_check_lib_save_LIBS fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_gnutls_gnutls_check_version" >&5 +$as_echo "$ac_cv_lib_gnutls_gnutls_check_version" >&6; } +if test "x$ac_cv_lib_gnutls_gnutls_check_version" = x""yes; then + { $as_echo "$as_me:$LINENO: checking whether GNUTLS_VERIFY_DISABLE_TIME_CHECKS is declared" >&5 +$as_echo_n "checking whether GNUTLS_VERIFY_DISABLE_TIME_CHECKS is declared... " >&6; } +if test "${ac_cv_have_decl_GNUTLS_VERIFY_DISABLE_TIME_CHECKS+set}" = set; then + $as_echo_n "(cached) " >&6 else - # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } -cat >conftest.$ac_ext <<_ACEOF + cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ -$ac_includes_default -#include <$ac_header> +#include + +int +main () +{ +#ifndef GNUTLS_VERIFY_DISABLE_TIME_CHECKS + (void) GNUTLS_VERIFY_DISABLE_TIME_CHECKS; +#endif + + ; + return 0; +} _ACEOF rm -f conftest.$ac_objext if { (ac_try="$ac_compile" @@ -14901,226 +16546,72 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then - ac_header_compiler=yes + ac_cv_have_decl_GNUTLS_VERIFY_DISABLE_TIME_CHECKS=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 - ac_header_compiler=no + ac_cv_have_decl_GNUTLS_VERIFY_DISABLE_TIME_CHECKS=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } - -# Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } -cat >conftest.$ac_ext <<_ACEOF -/* confdefs.h. */ -_ACEOF -cat confdefs.h >>conftest.$ac_ext -cat >>conftest.$ac_ext <<_ACEOF -/* end confdefs.h. */ -#include <$ac_header> -_ACEOF -if { (ac_try="$ac_cpp conftest.$ac_ext" -case "(($ac_try" in - *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; - *) ac_try_echo=$ac_try;; -esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 - ac_status=$? - grep -v '^ *+' conftest.er1 >conftest.err - rm -f conftest.er1 - cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); } >/dev/null && { - test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || - test ! -s conftest.err - }; then - ac_header_preproc=yes -else - echo "$as_me: failed program was:" >&5 -sed 's/^/| /' conftest.$ac_ext >&5 - - ac_header_preproc=no fi +{ $as_echo "$as_me:$LINENO: result: $ac_cv_have_decl_GNUTLS_VERIFY_DISABLE_TIME_CHECKS" >&5 +$as_echo "$ac_cv_have_decl_GNUTLS_VERIFY_DISABLE_TIME_CHECKS" >&6; } +if test "x$ac_cv_have_decl_GNUTLS_VERIFY_DISABLE_TIME_CHECKS" = x""yes; then -rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +cat >>confdefs.h <<_ACEOF +#define HAVE_DECL_GNUTLS_VERIFY_DISABLE_TIME_CHECKS 1 +_ACEOF -# So? What about this header? -case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in - yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} - ac_header_preproc=yes - ;; - no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} - ;; -esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } -if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 else - eval "$as_ac_Header=\$ac_header_preproc" -fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } - -fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 -_ACEOF - -fi - -done - - CPPFLAGS="$CPPFLAGS $LIBGNUTLS_CFLAGS" - MUTTLIBS="$MUTTLIBS $LIBGNUTLS_LIBS" - - -cat >>confdefs.h <<\_ACEOF -#define USE_SSL 1 -_ACEOF - - -cat >>confdefs.h <<\_ACEOF -#define USE_SSL_GNUTLS 1 +#define HAVE_DECL_GNUTLS_VERIFY_DISABLE_TIME_CHECKS 0 _ACEOF - MUTT_LIB_OBJECTS="$MUTT_LIB_OBJECTS mutt_ssl_gnutls.o" - need_ssl=yes - else - if test -f conf.libgnutlstest ; then - : - else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } - fi - if test "$LIBGNUTLS_CONFIG" = "no" ; then - echo "*** The libgnutls-config script installed by LIBGNUTLS could not be found" - echo "*** If LIBGNUTLS was installed in PREFIX, make sure PREFIX/bin is in" - echo "*** your path, or set the LIBGNUTLS_CONFIG environment variable to the" - echo "*** full path to libgnutls-config." - else - if test -f conf.libgnutlstest ; then - : - else - echo "*** Could not run libgnutls test program, checking why..." - CFLAGS="$CFLAGS $LIBGNUTLS_CFLAGS" - LIBS="$LIBS $LIBGNUTLS_LIBS" - cat >conftest.$ac_ext <<_ACEOF -/* confdefs.h. */ -_ACEOF -cat confdefs.h >>conftest.$ac_ext -cat >>conftest.$ac_ext <<_ACEOF -/* end confdefs.h. */ +fi -#include -#include -#include -#include -int -main () -{ - return !!gnutls_check_version(NULL); - ; - return 0; -} -_ACEOF -rm -f conftest.$ac_objext conftest$ac_exeext -if { (ac_try="$ac_link" -case "(($ac_try" in - *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; - *) ac_try_echo=$ac_try;; -esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 - (eval "$ac_link") 2>conftest.er1 - ac_status=$? - grep -v '^ *+' conftest.er1 >conftest.err - rm -f conftest.er1 - cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 - (exit $ac_status); } && { - test -z "$ac_c_werror_flag" || - test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then - echo "*** The test program compiled, but did not run. This usually means" - echo "*** that the run-time linker is not finding LIBGNUTLS or finding the wrong" - echo "*** version of LIBGNUTLS. If it is not finding LIBGNUTLS, you'll need to set your" - echo "*** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point" - echo "*** to the installed location Also, make sure you have run ldconfig if that" - echo "*** is required on your system" - echo "***" - echo "*** If you have an old version installed, it is best to remove it, although" - echo "*** you may also be able to get things to work by modifying LD_LIBRARY_PATH" - echo "***" -else - echo "$as_me: failed program was:" >&5 -sed 's/^/| /' conftest.$ac_ext >&5 - echo "*** The test program failed to compile or link. See the file config.log for the" - echo "*** exact error that occured. This usually means LIBGNUTLS was incorrectly installed" - echo "*** or that you have moved LIBGNUTLS since it was installed. In the latter case, you" - echo "*** may want to edit the libgnutls-config script: $LIBGNUTLS_CONFIG" -fi + LIBS="$saved_LIBS" + MUTTLIBS="$MUTTLIBS -lgnutls" -rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ - conftest$ac_exeext conftest.$ac_ext - CFLAGS="$ac_save_CFLAGS" - LIBS="$ac_save_LIBS" - fi - fi - LIBGNUTLS_CFLAGS="" - LIBGNUTLS_LIBS="" - { { echo "$as_me:$LINENO: error: could not find libgnutls" >&5 -echo "$as_me: error: could not find libgnutls" >&2;} - { (exit 1); exit 1; }; } - fi - rm -f conf.libgnutlstest +cat >>confdefs.h <<\_ACEOF +#define USE_SSL 1 +_ACEOF + + +cat >>confdefs.h <<\_ACEOF +#define USE_SSL_GNUTLS 1 +_ACEOF + MUTT_LIB_OBJECTS="$MUTT_LIB_OBJECTS mutt_ssl_gnutls.o" + need_ssl=yes +else + { { $as_echo "$as_me:$LINENO: error: could not find libgnutls" >&5 +$as_echo "$as_me: error: could not find libgnutls" >&2;} + { (exit 1); exit 1; }; } +fi fi fi + if test x$need_ssl = xyes; then USE_SSL_TRUE= USE_SSL_FALSE='#' @@ -15138,8 +16629,8 @@ if test "${with_sasl+set}" = set; then then if test "$need_socket" != "yes" then - { { echo "$as_me:$LINENO: error: SASL support is only useful with POP or IMAP support" >&5 -echo "$as_me: error: SASL support is only useful with POP or IMAP support" >&2;} + { { $as_echo "$as_me:$LINENO: error: SASL support is only useful with POP or IMAP support" >&5 +$as_echo "$as_me: error: SASL support is only useful with POP or IMAP support" >&2;} { (exit 1); exit 1; }; } fi @@ -15152,10 +16643,10 @@ echo "$as_me: error: SASL support is only useful with POP or IMAP support" >&2;} saved_LIBS="$LIBS" -{ echo "$as_me:$LINENO: checking for sasl_client_init in -lsasl2" >&5 -echo $ECHO_N "checking for sasl_client_init in -lsasl2... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for sasl_client_init in -lsasl2" >&5 +$as_echo_n "checking for sasl_client_init in -lsasl2... " >&6; } if test "${ac_cv_lib_sasl2_sasl_client_init+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lsasl2 $LIBS" @@ -15187,33 +16678,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_sasl2_sasl_client_init=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_sasl2_sasl_client_init=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_sasl2_sasl_client_init" >&5 -echo "${ECHO_T}$ac_cv_lib_sasl2_sasl_client_init" >&6; } -if test $ac_cv_lib_sasl2_sasl_client_init = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_sasl2_sasl_client_init" >&5 +$as_echo "$ac_cv_lib_sasl2_sasl_client_init" >&6; } +if test "x$ac_cv_lib_sasl2_sasl_client_init" = x""yes; then cat >>confdefs.h <<_ACEOF #define HAVE_LIBSASL2 1 _ACEOF @@ -15221,8 +16716,8 @@ _ACEOF LIBS="-lsasl2 $LIBS" else - { { echo "$as_me:$LINENO: error: could not find libsasl2" >&5 -echo "$as_me: error: could not find libsasl2" >&2;} + { { $as_echo "$as_me:$LINENO: error: could not find libsasl2" >&5 +$as_echo "$as_me: error: could not find libsasl2" >&2;} { (exit 1); exit 1; }; } fi @@ -15290,8 +16785,8 @@ _ACEOF fi -{ echo "$as_me:$LINENO: checking whether struct dirent defines d_ino" >&5 -echo $ECHO_N "checking whether struct dirent defines d_ino... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether struct dirent defines d_ino" >&5 +$as_echo_n "checking whether struct dirent defines d_ino... " >&6; } ac_cv_dirent_d_ino=no cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -15314,26 +16809,30 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_dirent_d_ino=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext if test x$ac_cv_dirent_d_ino = xyes ; then @@ -15343,8 +16842,8 @@ cat >>confdefs.h <<\_ACEOF _ACEOF fi -{ echo "$as_me:$LINENO: result: $ac_cv_dirent_d_ino" >&5 -echo "${ECHO_T}$ac_cv_dirent_d_ino" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_dirent_d_ino" >&5 +$as_echo "$ac_cv_dirent_d_ino" >&6; } mutt_cv_warnings=yes # Check whether --enable-warnings was given. @@ -15486,8 +16985,8 @@ _ACEOF then if test "$db_requested" != "auto" then - { { echo "$as_me:$LINENO: error: more than one header cache engine requested." >&5 -echo "$as_me: error: more than one header cache engine requested." >&2;} + { { $as_echo "$as_me:$LINENO: error: more than one header cache engine requested." >&5 +$as_echo "$as_me: error: more than one header cache engine requested." >&2;} { (exit 1); exit 1; }; } else db_requested=qdbm @@ -15497,8 +16996,8 @@ echo "$as_me: error: more than one header cache engine requested." >&2;} then if test "$db_requested" != "auto" then - { { echo "$as_me:$LINENO: error: more than one header cache engine requested." >&5 -echo "$as_me: error: more than one header cache engine requested." >&2;} + { { $as_echo "$as_me:$LINENO: error: more than one header cache engine requested." >&5 +$as_echo "$as_me: error: more than one header cache engine requested." >&2;} { (exit 1); exit 1; }; } else db_requested=gdbm @@ -15508,8 +17007,8 @@ echo "$as_me: error: more than one header cache engine requested." >&2;} then if test "$db_requested" != "auto" then - { { echo "$as_me:$LINENO: error: more than one header cache engine requested." >&5 -echo "$as_me: error: more than one header cache engine requested." >&2;} + { { $as_echo "$as_me:$LINENO: error: more than one header cache engine requested." >&5 +$as_echo "$as_me: error: more than one header cache engine requested." >&2;} { (exit 1); exit 1; }; } else db_requested=bdb @@ -15526,17 +17025,17 @@ echo "$as_me: error: more than one header cache engine requested." >&2;} fi if test "${ac_cv_header_tcbdb_h+set}" = set; then - { echo "$as_me:$LINENO: checking for tcbdb.h" >&5 -echo $ECHO_N "checking for tcbdb.h... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for tcbdb.h" >&5 +$as_echo_n "checking for tcbdb.h... " >&6; } if test "${ac_cv_header_tcbdb_h+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -{ echo "$as_me:$LINENO: result: $ac_cv_header_tcbdb_h" >&5 -echo "${ECHO_T}$ac_cv_header_tcbdb_h" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_header_tcbdb_h" >&5 +$as_echo "$ac_cv_header_tcbdb_h" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking tcbdb.h usability" >&5 -echo $ECHO_N "checking tcbdb.h usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking tcbdb.h usability" >&5 +$as_echo_n "checking tcbdb.h usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -15552,32 +17051,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking tcbdb.h presence" >&5 -echo $ECHO_N "checking tcbdb.h presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking tcbdb.h presence" >&5 +$as_echo_n "checking tcbdb.h presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -15591,70 +17091,71 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: tcbdb.h: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: tcbdb.h: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: tcbdb.h: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: tcbdb.h: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: tcbdb.h: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: tcbdb.h: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: tcbdb.h: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: tcbdb.h: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: tcbdb.h: present but cannot be compiled" >&5 -echo "$as_me: WARNING: tcbdb.h: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: tcbdb.h: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: tcbdb.h: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: tcbdb.h: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: tcbdb.h: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: tcbdb.h: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: tcbdb.h: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: tcbdb.h: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: tcbdb.h: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: tcbdb.h: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: tcbdb.h: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: tcbdb.h: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: tcbdb.h: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: tcbdb.h: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: tcbdb.h: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: tcbdb.h: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: tcbdb.h: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: tcbdb.h: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: tcbdb.h: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: tcbdb.h: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: tcbdb.h: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: tcbdb.h: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: tcbdb.h: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for tcbdb.h" >&5 -echo $ECHO_N "checking for tcbdb.h... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for tcbdb.h" >&5 +$as_echo_n "checking for tcbdb.h... " >&6; } if test "${ac_cv_header_tcbdb_h+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_cv_header_tcbdb_h=$ac_header_preproc fi -{ echo "$as_me:$LINENO: result: $ac_cv_header_tcbdb_h" >&5 -echo "${ECHO_T}$ac_cv_header_tcbdb_h" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_header_tcbdb_h" >&5 +$as_echo "$ac_cv_header_tcbdb_h" >&6; } fi -if test $ac_cv_header_tcbdb_h = yes; then - { echo "$as_me:$LINENO: checking for tcbdbopen in -ltokyocabinet" >&5 -echo $ECHO_N "checking for tcbdbopen in -ltokyocabinet... $ECHO_C" >&6; } +if test "x$ac_cv_header_tcbdb_h" = x""yes; then + { $as_echo "$as_me:$LINENO: checking for tcbdbopen in -ltokyocabinet" >&5 +$as_echo_n "checking for tcbdbopen in -ltokyocabinet... " >&6; } if test "${ac_cv_lib_tokyocabinet_tcbdbopen+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-ltokyocabinet $LIBS" @@ -15686,33 +17187,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_tokyocabinet_tcbdbopen=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_tokyocabinet_tcbdbopen=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_tokyocabinet_tcbdbopen" >&5 -echo "${ECHO_T}$ac_cv_lib_tokyocabinet_tcbdbopen" >&6; } -if test $ac_cv_lib_tokyocabinet_tcbdbopen = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_tokyocabinet_tcbdbopen" >&5 +$as_echo "$ac_cv_lib_tokyocabinet_tcbdbopen" >&6; } +if test "x$ac_cv_lib_tokyocabinet_tcbdbopen" = x""yes; then MUTTLIBS="$MUTTLIBS -ltokyocabinet" cat >>confdefs.h <<\_ACEOF @@ -15730,8 +17235,8 @@ fi if test "$db_requested" != auto && test "$db_found" != "$db_requested" then - { { echo "$as_me:$LINENO: error: Tokyo Cabinet could not be used. Check config.log for details." >&5 -echo "$as_me: error: Tokyo Cabinet could not be used. Check config.log for details." >&2;} + { { $as_echo "$as_me:$LINENO: error: Tokyo Cabinet could not be used. Check config.log for details." >&5 +$as_echo "$as_me: error: Tokyo Cabinet could not be used. Check config.log for details." >&2;} { (exit 1); exit 1; }; } fi fi @@ -15757,20 +17262,21 @@ echo "$as_me: error: Tokyo Cabinet could not be used. Check config.log for detai for ac_header in villa.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -15786,32 +17292,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -15825,79 +17332,83 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi done - { echo "$as_me:$LINENO: checking for vlopen in -lqdbm" >&5 -echo $ECHO_N "checking for vlopen in -lqdbm... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for vlopen in -lqdbm" >&5 +$as_echo_n "checking for vlopen in -lqdbm... " >&6; } if test "${ac_cv_lib_qdbm_vlopen+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_check_lib_save_LIBS=$LIBS LIBS="-lqdbm $LIBS" @@ -15929,33 +17440,37 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_lib_qdbm_vlopen=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_lib_qdbm_vlopen=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS=$ac_check_lib_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_lib_qdbm_vlopen" >&5 -echo "${ECHO_T}$ac_cv_lib_qdbm_vlopen" >&6; } -if test $ac_cv_lib_qdbm_vlopen = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_lib_qdbm_vlopen" >&5 +$as_echo "$ac_cv_lib_qdbm_vlopen" >&6; } +if test "x$ac_cv_lib_qdbm_vlopen" = x""yes; then MUTTLIBS="$MUTTLIBS -lqdbm" cat >>confdefs.h <<\_ACEOF @@ -15971,8 +17486,8 @@ fi LIBS="$saved_LIBS" if test "$db_requested" != auto && test "$db_found" != "$db_requested" then - { { echo "$as_me:$LINENO: error: QDBM could not be used. Check config.log for details." >&5 -echo "$as_me: error: QDBM could not be used. Check config.log for details." >&2;} + { { $as_echo "$as_me:$LINENO: error: QDBM could not be used. Check config.log for details." >&5 +$as_echo "$as_me: error: QDBM could not be used. Check config.log for details." >&2;} { (exit 1); exit 1; }; } fi fi @@ -15987,10 +17502,10 @@ echo "$as_me: error: QDBM could not be used. Check config.log for details." >&2; fi saved_LIBS="$LIBS" LIBS="$LIBS -lgdbm" - { echo "$as_me:$LINENO: checking for gdbm_open" >&5 -echo $ECHO_N "checking for gdbm_open... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for gdbm_open" >&5 +$as_echo_n "checking for gdbm_open... " >&6; } if test "${ac_cv_gdbmopen+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_cv_gdbmopen=no @@ -16015,32 +17530,36 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_gdbmopen=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_gdbmopen" >&5 -echo "${ECHO_T}$ac_cv_gdbmopen" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_gdbmopen" >&5 +$as_echo "$ac_cv_gdbmopen" >&6; } LIBS="$saved_LIBS" if test "$ac_cv_gdbmopen" = yes then @@ -16054,8 +17573,8 @@ _ACEOF fi if test "$db_requested" != auto && test "$db_found" != "$db_requested" then - { { echo "$as_me:$LINENO: error: GDBM could not be used. Check config.log for details." >&5 -echo "$as_me: error: GDBM could not be used. Check config.log for details." >&2;} + { { $as_echo "$as_me:$LINENO: error: GDBM could not be used. Check config.log for details." >&5 +$as_echo "$as_me: error: GDBM could not be used. Check config.log for details." >&2;} { (exit 1); exit 1; }; } fi fi @@ -16074,8 +17593,8 @@ echo "$as_me: error: GDBM could not be used. Check config.log for details." >&2; done done BDB_VERSIONS="db-4 db4 db-4.6 db4.6 db46 db-4.5 db4.5 db45 db-4.4 db4.4 db44 db-4.3 db4.3 db43 db-4.2 db4.2 db42 db-4.1 db4.1 db41 db ''" - { echo "$as_me:$LINENO: checking for BerkeleyDB > 4.0" >&5 -echo $ECHO_N "checking for BerkeleyDB > 4.0... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for BerkeleyDB > 4.0" >&5 +$as_echo_n "checking for BerkeleyDB > 4.0... " >&6; } for d in $bdbpfx; do BDB_INCLUDE_DIR="" BDB_LIB_DIR="" @@ -16115,30 +17634,34 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_dbcreate=yes BDB_LIB="$l" break else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext done @@ -16150,8 +17673,8 @@ rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ done if test x$ac_cv_dbcreate = xyes then - { echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } + { $as_echo "$as_me:$LINENO: result: yes" >&5 +$as_echo "yes" >&6; } CPPFLAGS="$OLDCPPFLAGS -I$BDB_INCLUDE_DIR" LIBS="$OLDLIBS -L$BDB_LIB_DIR -l$BDB_LIB" @@ -16161,15 +17684,15 @@ _ACEOF db_found=bdb else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi fi if test $db_found = no then - { { echo "$as_me:$LINENO: error: You need Tokyo Cabinet, QDBM, GDBM or Berkeley DB4 for hcache" >&5 -echo "$as_me: error: You need Tokyo Cabinet, QDBM, GDBM or Berkeley DB4 for hcache" >&2;} + { { $as_echo "$as_me:$LINENO: error: You need Tokyo Cabinet, QDBM, GDBM or Berkeley DB4 for hcache" >&5 +$as_echo "$as_me: error: You need Tokyo Cabinet, QDBM, GDBM or Berkeley DB4 for hcache" >&2;} { (exit 1); exit 1; }; } fi fi @@ -16196,26 +17719,58 @@ if test "${enable_iconv+set}" = set; then fi -{ echo "$as_me:$LINENO: checking for off_t" >&5 -echo $ECHO_N "checking for off_t... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for off_t" >&5 +$as_echo_n "checking for off_t... " >&6; } if test "${ac_cv_type_off_t+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else - cat >conftest.$ac_ext <<_ACEOF + ac_cv_type_off_t=no +cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default -typedef off_t ac__type_new_; int main () { -if ((ac__type_new_ *) 0) - return 0; -if (sizeof (ac__type_new_)) +if (sizeof (off_t)) + return 0; + ; return 0; +} +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +$ac_includes_default +int +main () +{ +if (sizeof ((off_t))) + return 0; ; return 0; } @@ -16226,30 +17781,39 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then - ac_cv_type_off_t=yes + : +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_cv_type_off_t=yes +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 - ac_cv_type_off_t=no + fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_type_off_t" >&5 -echo "${ECHO_T}$ac_cv_type_off_t" >&6; } -if test $ac_cv_type_off_t = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_type_off_t" >&5 +$as_echo "$ac_cv_type_off_t" >&6; } +if test "x$ac_cv_type_off_t" = x""yes; then : else @@ -16259,26 +17823,58 @@ _ACEOF fi -{ echo "$as_me:$LINENO: checking for size_t" >&5 -echo $ECHO_N "checking for size_t... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for size_t" >&5 +$as_echo_n "checking for size_t... " >&6; } if test "${ac_cv_type_size_t+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else - cat >conftest.$ac_ext <<_ACEOF + ac_cv_type_size_t=no +cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ $ac_includes_default -typedef size_t ac__type_new_; int main () { -if ((ac__type_new_ *) 0) - return 0; -if (sizeof (ac__type_new_)) +if (sizeof (size_t)) + return 0; + ; return 0; +} +_ACEOF +rm -f conftest.$ac_objext +if { (ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 + (eval "$ac_compile") 2>conftest.er1 + ac_status=$? + grep -v '^ *+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then + cat >conftest.$ac_ext <<_ACEOF +/* confdefs.h. */ +_ACEOF +cat confdefs.h >>conftest.$ac_ext +cat >>conftest.$ac_ext <<_ACEOF +/* end confdefs.h. */ +$ac_includes_default +int +main () +{ +if (sizeof ((size_t))) + return 0; ; return 0; } @@ -16289,30 +17885,39 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then - ac_cv_type_size_t=yes + : +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_cv_type_size_t=yes +fi + +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 - ac_cv_type_size_t=no + fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_type_size_t" >&5 -echo "${ECHO_T}$ac_cv_type_size_t" >&6; } -if test $ac_cv_type_size_t = yes; then +{ $as_echo "$as_me:$LINENO: result: $ac_cv_type_size_t" >&5 +$as_echo "$ac_cv_type_size_t" >&6; } +if test "x$ac_cv_type_size_t" = x""yes; then : else @@ -16324,10 +17929,10 @@ fi # The Ultrix 4.2 mips builtin alloca declared by alloca.h only works # for constant arguments. Useless! -{ echo "$as_me:$LINENO: checking for working alloca.h" >&5 -echo $ECHO_N "checking for working alloca.h... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for working alloca.h" >&5 +$as_echo_n "checking for working alloca.h... " >&6; } if test "${ac_cv_working_alloca_h+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -16351,31 +17956,35 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_working_alloca_h=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_working_alloca_h=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_working_alloca_h" >&5 -echo "${ECHO_T}$ac_cv_working_alloca_h" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_working_alloca_h" >&5 +$as_echo "$ac_cv_working_alloca_h" >&6; } if test $ac_cv_working_alloca_h = yes; then cat >>confdefs.h <<\_ACEOF @@ -16384,10 +17993,10 @@ _ACEOF fi -{ echo "$as_me:$LINENO: checking for alloca" >&5 -echo $ECHO_N "checking for alloca... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for alloca" >&5 +$as_echo_n "checking for alloca... " >&6; } if test "${ac_cv_func_alloca_works+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -16431,31 +18040,35 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_func_alloca_works=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_cv_func_alloca_works=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $ac_cv_func_alloca_works" >&5 -echo "${ECHO_T}$ac_cv_func_alloca_works" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_func_alloca_works" >&5 +$as_echo "$ac_cv_func_alloca_works" >&6; } if test $ac_cv_func_alloca_works = yes; then @@ -16476,10 +18089,10 @@ cat >>confdefs.h <<\_ACEOF _ACEOF -{ echo "$as_me:$LINENO: checking whether \`alloca.c' needs Cray hooks" >&5 -echo $ECHO_N "checking whether \`alloca.c' needs Cray hooks... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether \`alloca.c' needs Cray hooks" >&5 +$as_echo_n "checking whether \`alloca.c' needs Cray hooks... " >&6; } if test "${ac_cv_os_cray+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -16503,15 +18116,15 @@ fi rm -f conftest* fi -{ echo "$as_me:$LINENO: result: $ac_cv_os_cray" >&5 -echo "${ECHO_T}$ac_cv_os_cray" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_os_cray" >&5 +$as_echo "$ac_cv_os_cray" >&6; } if test $ac_cv_os_cray = yes; then for ac_func in _getb67 GETB67 getb67; do - as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } + as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -16564,33 +18177,40 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF #define CRAY_STACKSEG_END $ac_func @@ -16602,10 +18222,10 @@ fi done fi -{ echo "$as_me:$LINENO: checking stack direction for C alloca" >&5 -echo $ECHO_N "checking stack direction for C alloca... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking stack direction for C alloca" >&5 +$as_echo_n "checking stack direction for C alloca... " >&6; } if test "${ac_cv_c_stack_direction+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test "$cross_compiling" = yes; then ac_cv_c_stack_direction=0 @@ -16643,36 +18263,39 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then ac_cv_c_stack_direction=1 else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) ac_cv_c_stack_direction=-1 fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi fi -{ echo "$as_me:$LINENO: result: $ac_cv_c_stack_direction" >&5 -echo "${ECHO_T}$ac_cv_c_stack_direction" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_c_stack_direction" >&5 +$as_echo "$ac_cv_c_stack_direction" >&6; } cat >>confdefs.h <<_ACEOF #define STACK_DIRECTION $ac_cv_c_stack_direction @@ -16685,20 +18308,21 @@ fi for ac_header in stdlib.h unistd.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -16714,32 +18338,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -16753,69 +18378,73 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi @@ -16825,11 +18454,11 @@ done for ac_func in getpagesize do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -16882,44 +18511,51 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi done -{ echo "$as_me:$LINENO: checking for working mmap" >&5 -echo $ECHO_N "checking for working mmap... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for working mmap" >&5 +$as_echo_n "checking for working mmap... " >&6; } if test "${ac_cv_func_mmap_fixed_mapped+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test "$cross_compiling" = yes; then ac_cv_func_mmap_fixed_mapped=no @@ -17063,36 +18699,39 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then ac_cv_func_mmap_fixed_mapped=yes else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) ac_cv_func_mmap_fixed_mapped=no fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi fi -{ echo "$as_me:$LINENO: result: $ac_cv_func_mmap_fixed_mapped" >&5 -echo "${ECHO_T}$ac_cv_func_mmap_fixed_mapped" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_func_mmap_fixed_mapped" >&5 +$as_echo "$ac_cv_func_mmap_fixed_mapped" >&6; } if test $ac_cv_func_mmap_fixed_mapped = yes; then cat >>confdefs.h <<\_ACEOF @@ -17103,10 +18742,10 @@ fi rm -f conftest.mmap - { echo "$as_me:$LINENO: checking whether we are using the GNU C Library 2.1 or newer" >&5 -echo $ECHO_N "checking whether we are using the GNU C Library 2.1 or newer... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking whether we are using the GNU C Library 2.1 or newer" >&5 +$as_echo_n "checking whether we are using the GNU C Library 2.1 or newer... " >&6; } if test "${ac_cv_gnu_library_2_1+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -17134,8 +18773,8 @@ rm -f conftest* fi -{ echo "$as_me:$LINENO: result: $ac_cv_gnu_library_2_1" >&5 -echo "${ECHO_T}$ac_cv_gnu_library_2_1" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_gnu_library_2_1" >&5 +$as_echo "$ac_cv_gnu_library_2_1" >&6; } GLIBC21="$ac_cv_gnu_library_2_1" @@ -17154,20 +18793,21 @@ echo "${ECHO_T}$ac_cv_gnu_library_2_1" >&6; } for ac_header in argz.h limits.h locale.h nl_types.h malloc.h stddef.h \ stdlib.h string.h unistd.h sys/param.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -17183,32 +18823,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -17222,69 +18863,73 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi @@ -17316,11 +18961,11 @@ for ac_func in feof_unlocked fgets_unlocked getcwd getegid geteuid \ getgid getuid mempcpy munmap putenv setenv setlocale stpcpy strchr strcasecmp \ strdup strtoul tsearch __argz_count __argz_stringify __argz_next do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -17373,35 +19018,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi @@ -17422,10 +19074,10 @@ if test "${with_libiconv_prefix+set}" = set; then fi - { echo "$as_me:$LINENO: checking for iconv" >&5 -echo $ECHO_N "checking for iconv... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for iconv" >&5 +$as_echo_n "checking for iconv... " >&6; } if test "${am_cv_func_iconv+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else am_cv_func_iconv="no, consider installing GNU libiconv" @@ -17454,26 +19106,30 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then am_cv_func_iconv=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext if test "$am_cv_func_iconv" != yes; then @@ -17503,45 +19159,49 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then am_cv_lib_iconv=yes am_cv_func_iconv=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS="$am_save_LIBS" fi fi -{ echo "$as_me:$LINENO: result: $am_cv_func_iconv" >&5 -echo "${ECHO_T}$am_cv_func_iconv" >&6; } +{ $as_echo "$as_me:$LINENO: result: $am_cv_func_iconv" >&5 +$as_echo "$am_cv_func_iconv" >&6; } if test "$am_cv_func_iconv" = yes; then cat >>confdefs.h <<\_ACEOF #define HAVE_ICONV 1 _ACEOF - { echo "$as_me:$LINENO: checking for iconv declaration" >&5 -echo $ECHO_N "checking for iconv declaration... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for iconv declaration" >&5 +$as_echo_n "checking for iconv declaration... " >&6; } if test "${am_cv_proto_iconv+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF @@ -17577,20 +19237,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then am_cv_proto_iconv_arg1="" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 am_cv_proto_iconv_arg1="const" @@ -17601,9 +19262,9 @@ rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext fi am_cv_proto_iconv=`echo "$am_cv_proto_iconv" | tr -s ' ' | sed -e 's/( /(/'` - { echo "$as_me:$LINENO: result: ${ac_t:- + { $as_echo "$as_me:$LINENO: result: ${ac_t:- }$am_cv_proto_iconv" >&5 -echo "${ECHO_T}${ac_t:- +$as_echo "${ac_t:- }$am_cv_proto_iconv" >&6; } cat >>confdefs.h <<_ACEOF @@ -17618,10 +19279,10 @@ _ACEOF - { echo "$as_me:$LINENO: checking for nl_langinfo and CODESET" >&5 -echo $ECHO_N "checking for nl_langinfo and CODESET... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for nl_langinfo and CODESET" >&5 +$as_echo_n "checking for nl_langinfo and CODESET... " >&6; } if test "${am_cv_langinfo_codeset+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -17644,32 +19305,36 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then am_cv_langinfo_codeset=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 am_cv_langinfo_codeset=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $am_cv_langinfo_codeset" >&5 -echo "${ECHO_T}$am_cv_langinfo_codeset" >&6; } +{ $as_echo "$as_me:$LINENO: result: $am_cv_langinfo_codeset" >&5 +$as_echo "$am_cv_langinfo_codeset" >&6; } if test $am_cv_langinfo_codeset = yes; then cat >>confdefs.h <<\_ACEOF @@ -17679,10 +19344,10 @@ _ACEOF fi if test $ac_cv_header_locale_h = yes; then - { echo "$as_me:$LINENO: checking for LC_MESSAGES" >&5 -echo $ECHO_N "checking for LC_MESSAGES... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for LC_MESSAGES" >&5 +$as_echo_n "checking for LC_MESSAGES... " >&6; } if test "${am_cv_val_LC_MESSAGES+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -17705,31 +19370,35 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then am_cv_val_LC_MESSAGES=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 am_cv_val_LC_MESSAGES=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $am_cv_val_LC_MESSAGES" >&5 -echo "${ECHO_T}$am_cv_val_LC_MESSAGES" >&6; } +{ $as_echo "$as_me:$LINENO: result: $am_cv_val_LC_MESSAGES" >&5 +$as_echo "$am_cv_val_LC_MESSAGES" >&6; } if test $am_cv_val_LC_MESSAGES = yes; then cat >>confdefs.h <<\_ACEOF @@ -17738,8 +19407,8 @@ _ACEOF fi fi - { echo "$as_me:$LINENO: checking whether NLS is requested" >&5 -echo $ECHO_N "checking whether NLS is requested... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking whether NLS is requested" >&5 +$as_echo_n "checking whether NLS is requested... " >&6; } # Check whether --enable-nls was given. if test "${enable_nls+set}" = set; then enableval=$enable_nls; USE_NLS=$enableval @@ -17747,8 +19416,8 @@ else USE_NLS=yes fi - { echo "$as_me:$LINENO: result: $USE_NLS" >&5 -echo "${ECHO_T}$USE_NLS" >&6; } + { $as_echo "$as_me:$LINENO: result: $USE_NLS" >&5 +$as_echo "$USE_NLS" >&6; } BUILD_INCLUDED_LIBINTL=no @@ -17761,8 +19430,8 @@ cat >>confdefs.h <<\_ACEOF #define ENABLE_NLS 1 _ACEOF - { echo "$as_me:$LINENO: checking whether included gettext is requested" >&5 -echo $ECHO_N "checking whether included gettext is requested... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking whether included gettext is requested" >&5 +$as_echo_n "checking whether included gettext is requested... " >&6; } # Check whether --with-included-gettext was given. if test "${with_included_gettext+set}" = set; then @@ -17771,8 +19440,8 @@ else nls_cv_force_use_gnu_gettext=no fi - { echo "$as_me:$LINENO: result: $nls_cv_force_use_gnu_gettext" >&5 -echo "${ECHO_T}$nls_cv_force_use_gnu_gettext" >&6; } + { $as_echo "$as_me:$LINENO: result: $nls_cv_force_use_gnu_gettext" >&5 +$as_echo "$nls_cv_force_use_gnu_gettext" >&6; } nls_cv_use_gnu_gettext="$nls_cv_force_use_gnu_gettext" if test "$nls_cv_force_use_gnu_gettext" != "yes"; then @@ -17782,17 +19451,17 @@ echo "${ECHO_T}$nls_cv_force_use_gnu_gettext" >&6; } if test "${ac_cv_header_libintl_h+set}" = set; then - { echo "$as_me:$LINENO: checking for libintl.h" >&5 -echo $ECHO_N "checking for libintl.h... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for libintl.h" >&5 +$as_echo_n "checking for libintl.h... " >&6; } if test "${ac_cv_header_libintl_h+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -{ echo "$as_me:$LINENO: result: $ac_cv_header_libintl_h" >&5 -echo "${ECHO_T}$ac_cv_header_libintl_h" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_header_libintl_h" >&5 +$as_echo "$ac_cv_header_libintl_h" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking libintl.h usability" >&5 -echo $ECHO_N "checking libintl.h usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking libintl.h usability" >&5 +$as_echo_n "checking libintl.h usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -17808,32 +19477,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking libintl.h presence" >&5 -echo $ECHO_N "checking libintl.h presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking libintl.h presence" >&5 +$as_echo_n "checking libintl.h presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -17847,70 +19517,71 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: libintl.h: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: libintl.h: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: libintl.h: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: libintl.h: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: libintl.h: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: libintl.h: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: libintl.h: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: libintl.h: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: libintl.h: present but cannot be compiled" >&5 -echo "$as_me: WARNING: libintl.h: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: libintl.h: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: libintl.h: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: libintl.h: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: libintl.h: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: libintl.h: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: libintl.h: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: libintl.h: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: libintl.h: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: libintl.h: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: libintl.h: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: libintl.h: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: libintl.h: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: libintl.h: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: libintl.h: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: libintl.h: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: libintl.h: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: libintl.h: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: libintl.h: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: libintl.h: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: libintl.h: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: libintl.h: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: libintl.h: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for libintl.h" >&5 -echo $ECHO_N "checking for libintl.h... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for libintl.h" >&5 +$as_echo_n "checking for libintl.h... " >&6; } if test "${ac_cv_header_libintl_h+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_cv_header_libintl_h=$ac_header_preproc fi -{ echo "$as_me:$LINENO: result: $ac_cv_header_libintl_h" >&5 -echo "${ECHO_T}$ac_cv_header_libintl_h" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_header_libintl_h" >&5 +$as_echo "$ac_cv_header_libintl_h" >&6; } fi -if test $ac_cv_header_libintl_h = yes; then - { echo "$as_me:$LINENO: checking for GNU gettext in libc" >&5 -echo $ECHO_N "checking for GNU gettext in libc... $ECHO_C" >&6; } +if test "x$ac_cv_header_libintl_h" = x""yes; then + { $as_echo "$as_me:$LINENO: checking for GNU gettext in libc" >&5 +$as_echo_n "checking for GNU gettext in libc... " >&6; } if test "${gt_cv_func_gnugettext1_libc+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -17935,37 +19606,41 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then gt_cv_func_gnugettext1_libc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 gt_cv_func_gnugettext1_libc=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $gt_cv_func_gnugettext1_libc" >&5 -echo "${ECHO_T}$gt_cv_func_gnugettext1_libc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $gt_cv_func_gnugettext1_libc" >&5 +$as_echo "$gt_cv_func_gnugettext1_libc" >&6; } if test "$gt_cv_func_gnugettext1_libc" != "yes"; then - { echo "$as_me:$LINENO: checking for GNU gettext in libintl" >&5 -echo $ECHO_N "checking for GNU gettext in libintl... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for GNU gettext in libintl" >&5 +$as_echo_n "checking for GNU gettext in libintl... " >&6; } if test "${gt_cv_func_gnugettext1_libintl+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else gt_save_LIBS="$LIBS" LIBS="$LIBS -lintl $LIBICONV" @@ -17992,32 +19667,36 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then gt_cv_func_gnugettext1_libintl=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 gt_cv_func_gnugettext1_libintl=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext LIBS="$gt_save_LIBS" fi -{ echo "$as_me:$LINENO: result: $gt_cv_func_gnugettext1_libintl" >&5 -echo "${ECHO_T}$gt_cv_func_gnugettext1_libintl" >&6; } +{ $as_echo "$as_me:$LINENO: result: $gt_cv_func_gnugettext1_libintl" >&5 +$as_echo "$gt_cv_func_gnugettext1_libintl" >&6; } fi if test "$gt_cv_func_gnugettext1_libc" = "yes" \ @@ -18038,11 +19717,11 @@ _ACEOF for ac_func in dcgettext do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -18095,35 +19774,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi @@ -18133,10 +19819,10 @@ done # Extract the first word of "msgfmt", so it can be a program name with args. set dummy msgfmt; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_MSGFMT+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case "$MSGFMT" in /*) @@ -18160,19 +19846,19 @@ esac fi MSGFMT="$ac_cv_path_MSGFMT" if test "$MSGFMT" != ":"; then - { echo "$as_me:$LINENO: result: $MSGFMT" >&5 -echo "${ECHO_T}$MSGFMT" >&6; } + { $as_echo "$as_me:$LINENO: result: $MSGFMT" >&5 +$as_echo "$MSGFMT" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi # Extract the first word of "gmsgfmt", so it can be a program name with args. set dummy gmsgfmt; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_GMSGFMT+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case $GMSGFMT in [\\/]* | ?:[\\/]*) @@ -18187,7 +19873,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_path_GMSGFMT="$as_dir/$ac_word$ac_exec_ext" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -18200,21 +19886,21 @@ esac fi GMSGFMT=$ac_cv_path_GMSGFMT if test -n "$GMSGFMT"; then - { echo "$as_me:$LINENO: result: $GMSGFMT" >&5 -echo "${ECHO_T}$GMSGFMT" >&6; } + { $as_echo "$as_me:$LINENO: result: $GMSGFMT" >&5 +$as_echo "$GMSGFMT" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi # Extract the first word of "xgettext", so it can be a program name with args. set dummy xgettext; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_XGETTEXT+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case "$XGETTEXT" in /*) @@ -18238,11 +19924,11 @@ esac fi XGETTEXT="$ac_cv_path_XGETTEXT" if test "$XGETTEXT" != ":"; then - { echo "$as_me:$LINENO: result: $XGETTEXT" >&5 -echo "${ECHO_T}$XGETTEXT" >&6; } + { $as_echo "$as_me:$LINENO: result: $XGETTEXT" >&5 +$as_echo "$XGETTEXT" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -18262,10 +19948,10 @@ fi INTLOBJS="\$(GETTOBJS)" # Extract the first word of "msgfmt", so it can be a program name with args. set dummy msgfmt; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_MSGFMT+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case "$MSGFMT" in /*) @@ -18289,19 +19975,19 @@ esac fi MSGFMT="$ac_cv_path_MSGFMT" if test "$MSGFMT" != ":"; then - { echo "$as_me:$LINENO: result: $MSGFMT" >&5 -echo "${ECHO_T}$MSGFMT" >&6; } + { $as_echo "$as_me:$LINENO: result: $MSGFMT" >&5 +$as_echo "$MSGFMT" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi # Extract the first word of "gmsgfmt", so it can be a program name with args. set dummy gmsgfmt; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_GMSGFMT+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case $GMSGFMT in [\\/]* | ?:[\\/]*) @@ -18316,7 +20002,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_path_GMSGFMT="$as_dir/$ac_word$ac_exec_ext" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -18329,20 +20015,20 @@ esac fi GMSGFMT=$ac_cv_path_GMSGFMT if test -n "$GMSGFMT"; then - { echo "$as_me:$LINENO: result: $GMSGFMT" >&5 -echo "${ECHO_T}$GMSGFMT" >&6; } + { $as_echo "$as_me:$LINENO: result: $GMSGFMT" >&5 +$as_echo "$GMSGFMT" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi # Extract the first word of "xgettext", so it can be a program name with args. set dummy xgettext; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_XGETTEXT+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case "$XGETTEXT" in /*) @@ -18366,11 +20052,11 @@ esac fi XGETTEXT="$ac_cv_path_XGETTEXT" if test "$XGETTEXT" != ":"; then - { echo "$as_me:$LINENO: result: $XGETTEXT" >&5 -echo "${ECHO_T}$XGETTEXT" >&6; } + { $as_echo "$as_me:$LINENO: result: $XGETTEXT" >&5 +$as_echo "$XGETTEXT" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -18385,8 +20071,8 @@ fi if $GMSGFMT --statistics /dev/null >/dev/null 2>&1; then : ; else - { echo "$as_me:$LINENO: result: found msgfmt program is not GNU msgfmt; ignore it" >&5 -echo "${ECHO_T}found msgfmt program is not GNU msgfmt; ignore it" >&6; } + { $as_echo "$as_me:$LINENO: result: found msgfmt program is not GNU msgfmt; ignore it" >&5 +$as_echo "found msgfmt program is not GNU msgfmt; ignore it" >&6; } GMSGFMT=":" fi fi @@ -18395,8 +20081,8 @@ echo "${ECHO_T}found msgfmt program is not GNU msgfmt; ignore it" >&6; } if $XGETTEXT --omit-header /dev/null >/dev/null 2>&1; then : ; else - { echo "$as_me:$LINENO: result: found xgettext program is not GNU xgettext; ignore it" >&5 -echo "${ECHO_T}found xgettext program is not GNU xgettext; ignore it" >&6; } + { $as_echo "$as_me:$LINENO: result: found xgettext program is not GNU xgettext; ignore it" >&5 +$as_echo "found xgettext program is not GNU xgettext; ignore it" >&6; } XGETTEXT=":" fi fi @@ -18415,10 +20101,10 @@ echo "${ECHO_T}found xgettext program is not GNU xgettext; ignore it" >&6; } do # Extract the first word of "$ac_prog", so it can be a program name with args. set dummy $ac_prog; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_prog_INTLBISON+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else if test -n "$INTLBISON"; then ac_cv_prog_INTLBISON="$INTLBISON" # Let the user override the test. @@ -18431,7 +20117,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_prog_INTLBISON="$ac_prog" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -18442,11 +20128,11 @@ fi fi INTLBISON=$ac_cv_prog_INTLBISON if test -n "$INTLBISON"; then - { echo "$as_me:$LINENO: result: $INTLBISON" >&5 -echo "${ECHO_T}$INTLBISON" >&6; } + { $as_echo "$as_me:$LINENO: result: $INTLBISON" >&5 +$as_echo "$INTLBISON" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi @@ -18456,8 +20142,8 @@ done if test -z "$INTLBISON"; then ac_verc_fail=yes else - { echo "$as_me:$LINENO: checking version of bison" >&5 -echo $ECHO_N "checking version of bison... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking version of bison" >&5 +$as_echo_n "checking version of bison... " >&6; } ac_prog_version=`$INTLBISON --version 2>&1 | sed -n 's/^.*GNU Bison.* \([0-9]*\.[0-9.]*\).*$/\1/p'` case $ac_prog_version in '') ac_prog_version="v. ?.??, bad"; ac_verc_fail=yes;; @@ -18465,8 +20151,8 @@ echo $ECHO_N "checking version of bison... $ECHO_C" >&6; } ac_prog_version="$ac_prog_version, ok"; ac_verc_fail=no;; *) ac_prog_version="$ac_prog_version, bad"; ac_verc_fail=yes;; esac - { echo "$as_me:$LINENO: result: $ac_prog_version" >&5 -echo "${ECHO_T}$ac_prog_version" >&6; } + { $as_echo "$as_me:$LINENO: result: $ac_prog_version" >&5 +$as_echo "$ac_prog_version" >&6; } fi if test $ac_verc_fail = yes; then INTLBISON=: @@ -18504,8 +20190,8 @@ echo "${ECHO_T}$ac_prog_version" >&6; } if test "x$ALL_LINGUAS" = "x"; then LINGUAS= else - { echo "$as_me:$LINENO: checking for catalogs to be installed" >&5 -echo $ECHO_N "checking for catalogs to be installed... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for catalogs to be installed" >&5 +$as_echo_n "checking for catalogs to be installed... " >&6; } NEW_LINGUAS= for presentlang in $ALL_LINGUAS; do useit=no @@ -18524,8 +20210,8 @@ echo $ECHO_N "checking for catalogs to be installed... $ECHO_C" >&6; } fi done LINGUAS=$NEW_LINGUAS - { echo "$as_me:$LINENO: result: $LINGUAS" >&5 -echo "${ECHO_T}$LINGUAS" >&6; } + { $as_echo "$as_me:$LINENO: result: $LINGUAS" >&5 +$as_echo "$LINGUAS" >&6; } fi if test -n "$LINGUAS"; then @@ -18548,27 +20234,28 @@ echo "${ECHO_T}$LINGUAS" >&6; } if test "$am_cv_func_iconv" != "yes" then - { echo "$as_me:$LINENO: WARNING: Configuring without iconv support. See INSTALL for details" >&5 -echo "$as_me: WARNING: Configuring without iconv support. See INSTALL for details" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: Configuring without iconv support. See INSTALL for details" >&5 +$as_echo "$as_me: WARNING: Configuring without iconv support. See INSTALL for details" >&2;} else for ac_header in iconv.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -18584,32 +20271,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -18623,72 +20311,76 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF - { echo "$as_me:$LINENO: checking whether iconv.h defines iconv_t" >&5 -echo $ECHO_N "checking whether iconv.h defines iconv_t... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking whether iconv.h defines iconv_t" >&5 +$as_echo_n "checking whether iconv.h defines iconv_t... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -18700,16 +20392,16 @@ cat >>conftest.$ac_ext <<_ACEOF _ACEOF if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | $EGREP "typedef.*iconv_t" >/dev/null 2>&1; then - { echo "$as_me:$LINENO: result: yes" >&5 -echo "${ECHO_T}yes" >&6; } + { $as_echo "$as_me:$LINENO: result: yes" >&5 +$as_echo "yes" >&6; } cat >>confdefs.h <<\_ACEOF #define HAVE_ICONV_T_DEF 1 _ACEOF else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi rm -f conftest* @@ -18718,10 +20410,10 @@ fi done -{ echo "$as_me:$LINENO: checking whether this iconv is good enough" >&5 -echo $ECHO_N "checking whether this iconv is good enough... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether this iconv is good enough" >&5 +$as_echo_n "checking whether this iconv is good enough... " >&6; } if test "${mutt_cv_iconv_good+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else mutt_save_LIBS="$LIBS" LIBS="$LIBS $LIBICONV" @@ -18756,47 +20448,50 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then mutt_cv_iconv_good=yes else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) mutt_cv_iconv_good=no fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi LIBS="$mutt_save_LIBS" fi -{ echo "$as_me:$LINENO: result: $mutt_cv_iconv_good" >&5 -echo "${ECHO_T}$mutt_cv_iconv_good" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_iconv_good" >&5 +$as_echo "$mutt_cv_iconv_good" >&6; } if test "$mutt_cv_iconv_good" = no; then - { { echo "$as_me:$LINENO: error: Try using libiconv instead" >&5 -echo "$as_me: error: Try using libiconv instead" >&2;} + { { $as_echo "$as_me:$LINENO: error: Try using libiconv instead" >&5 +$as_echo "$as_me: error: Try using libiconv instead" >&2;} { (exit 1); exit 1; }; } fi -{ echo "$as_me:$LINENO: checking whether iconv is non-transcribing" >&5 -echo $ECHO_N "checking whether iconv is non-transcribing... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking whether iconv is non-transcribing" >&5 +$as_echo_n "checking whether iconv is non-transcribing... " >&6; } if test "${mutt_cv_iconv_nontrans+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else mutt_save_LIBS="$LIBS" LIBS="$LIBS $LIBICONV" @@ -18832,37 +20527,40 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { ac_try='./conftest$ac_exeext' { (case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_try") 2>&5 ac_status=$? - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); }; }; then mutt_cv_iconv_nontrans=no else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: program exited with status $ac_status" >&5 +$as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ( exit $ac_status ) mutt_cv_iconv_nontrans=yes fi +rm -rf conftest.dSYM rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext fi LIBS="$mutt_save_LIBS" fi -{ echo "$as_me:$LINENO: result: $mutt_cv_iconv_nontrans" >&5 -echo "${ECHO_T}$mutt_cv_iconv_nontrans" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_iconv_nontrans" >&5 +$as_echo "$mutt_cv_iconv_nontrans" >&6; } if test "$mutt_cv_iconv_nontrans" = yes; then cat >>confdefs.h <<\_ACEOF #define ICONV_NONTRANS 1 @@ -18889,11 +20587,11 @@ else for ac_func in bind_textdomain_codeset do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -18946,35 +20644,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi @@ -19006,15 +20711,15 @@ if test "x$with_idn" != "xno"; then then if test "x$with_idn" != "x" then - { { echo "$as_me:$LINENO: error: IDN requested but iconv is disabled or unavailable" >&5 -echo "$as_me: error: IDN requested but iconv is disabled or unavailable" >&2;} + { { $as_echo "$as_me:$LINENO: error: IDN requested but iconv is disabled or unavailable" >&5 +$as_echo "$as_me: error: IDN requested but iconv is disabled or unavailable" >&2;} { (exit 1); exit 1; }; } fi else - { echo "$as_me:$LINENO: checking for library containing stringprep_check_version" >&5 -echo $ECHO_N "checking for library containing stringprep_check_version... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for library containing stringprep_check_version" >&5 +$as_echo_n "checking for library containing stringprep_check_version... " >&6; } if test "${ac_cv_search_stringprep_check_version+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else ac_func_search_save_LIBS=$LIBS cat >conftest.$ac_ext <<_ACEOF @@ -19052,26 +20757,30 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then ac_cv_search_stringprep_check_version=$ac_res else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext if test "${ac_cv_search_stringprep_check_version+set}" = set; then @@ -19086,8 +20795,8 @@ fi rm conftest.$ac_ext LIBS=$ac_func_search_save_LIBS fi -{ echo "$as_me:$LINENO: result: $ac_cv_search_stringprep_check_version" >&5 -echo "${ECHO_T}$ac_cv_search_stringprep_check_version" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_cv_search_stringprep_check_version" >&5 +$as_echo "$ac_cv_search_stringprep_check_version" >&6; } ac_res=$ac_cv_search_stringprep_check_version if test "$ac_res" != no; then test "$ac_res" = "none required" || LIBS="$ac_res $LIBS" @@ -19105,11 +20814,11 @@ fi for ac_func in idna_to_unicode_utf8_from_utf8 idna_to_unicode_8z8z do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -19162,35 +20871,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi @@ -19200,11 +20916,11 @@ done for ac_func in idna_to_ascii_from_utf8 idna_to_ascii_8z do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -19257,35 +20973,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi @@ -19295,11 +21018,11 @@ done for ac_func in idna_to_ascii_lz idna_to_ascii_from_locale do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -19352,35 +21075,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi @@ -19393,20 +21123,21 @@ fi for ac_header in wchar.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -19422,32 +21153,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -19461,69 +21193,73 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi @@ -19531,10 +21267,10 @@ fi done -{ echo "$as_me:$LINENO: checking for wchar_t" >&5 -echo $ECHO_N "checking for wchar_t... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for wchar_t" >&5 +$as_echo_n "checking for wchar_t... " >&6; } if test "${mutt_cv_wchar_t+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -19563,20 +21299,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then mutt_cv_wchar_t=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 mutt_cv_wchar_t=no @@ -19584,8 +21321,8 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $mutt_cv_wchar_t" >&5 -echo "${ECHO_T}$mutt_cv_wchar_t" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_wchar_t" >&5 +$as_echo "$mutt_cv_wchar_t" >&6; } if test "$mutt_cv_wchar_t" = no; then @@ -19595,10 +21332,10 @@ _ACEOF fi -{ echo "$as_me:$LINENO: checking for wint_t" >&5 -echo $ECHO_N "checking for wint_t... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for wint_t" >&5 +$as_echo_n "checking for wint_t... " >&6; } if test "${mutt_cv_wint_t+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -19627,20 +21364,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then mutt_cv_wint_t=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 mutt_cv_wint_t=no @@ -19648,8 +21386,8 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $mutt_cv_wint_t" >&5 -echo "${ECHO_T}$mutt_cv_wint_t" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_wint_t" >&5 +$as_echo "$mutt_cv_wint_t" >&6; } if test "$mutt_cv_wint_t" = no; then @@ -19662,20 +21400,21 @@ fi for ac_header in wctype.h do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - { echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } else # Is the header compilable? -{ echo "$as_me:$LINENO: checking $ac_header usability" >&5 -echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header usability" >&5 +$as_echo_n "checking $ac_header usability... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -19691,32 +21430,33 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then ac_header_compiler=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_compiler=no fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 -echo "${ECHO_T}$ac_header_compiler" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } # Is the header present? -{ echo "$as_me:$LINENO: checking $ac_header presence" >&5 -echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking $ac_header presence" >&5 +$as_echo_n "checking $ac_header presence... " >&6; } cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -19730,69 +21470,73 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_cpp conftest.$ac_ext") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } >/dev/null && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then ac_header_preproc=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 ac_header_preproc=no fi rm -f conftest.err conftest.$ac_ext -{ echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 -echo "${ECHO_T}$ac_header_preproc" >&6; } +{ $as_echo "$as_me:$LINENO: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } # So? What about this header? case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in yes:no: ) - { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 -echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;} ac_header_preproc=yes ;; no:yes:* ) - { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 -echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 -echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 -echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 -echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 -echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} - { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 -echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5 +$as_echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5 +$as_echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;} ;; esac -{ echo "$as_me:$LINENO: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 +$as_echo_n "checking for $ac_header... " >&6; } if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else eval "$as_ac_Header=\$ac_header_preproc" fi -ac_res=`eval echo '${'$as_ac_Header'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } +ac_res=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } fi -if test `eval echo '${'$as_ac_Header'}'` = yes; then +as_val=`eval 'as_val=${'$as_ac_Header'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_header" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF fi @@ -19805,11 +21549,11 @@ done for ac_func in iswalnum iswalpha iswcntrl iswdigit do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -19862,35 +21606,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi @@ -19904,11 +21655,11 @@ done for ac_func in iswgraph iswlower iswprint iswpunct iswspace iswupper do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -19961,35 +21712,42 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi @@ -20000,11 +21758,11 @@ done for ac_func in iswxdigit towupper towlower do -as_ac_var=`echo "ac_cv_func_$ac_func" | $as_tr_sh` -{ echo "$as_me:$LINENO: checking for $ac_func" >&5 -echo $ECHO_N "checking for $ac_func... $ECHO_C" >&6; } +as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +{ $as_echo "$as_me:$LINENO: checking for $ac_func" >&5 +$as_echo_n "checking for $ac_func... " >&6; } if { as_var=$as_ac_var; eval "test \"\${$as_var+set}\" = set"; }; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -20057,45 +21815,52 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then eval "$as_ac_var=yes" else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 eval "$as_ac_var=no" fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -ac_res=`eval echo '${'$as_ac_var'}'` - { echo "$as_me:$LINENO: result: $ac_res" >&5 -echo "${ECHO_T}$ac_res" >&6; } -if test `eval echo '${'$as_ac_var'}'` = yes; then +ac_res=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + { $as_echo "$as_me:$LINENO: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +as_val=`eval 'as_val=${'$as_ac_var'} + $as_echo "$as_val"'` + if test "x$as_val" = x""yes; then cat >>confdefs.h <<_ACEOF -#define `echo "HAVE_$ac_func" | $as_tr_cpp` 1 +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF fi done -{ echo "$as_me:$LINENO: checking for mbstate_t" >&5 -echo $ECHO_N "checking for mbstate_t... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for mbstate_t" >&5 +$as_echo_n "checking for mbstate_t... " >&6; } if test "${mutt_cv_mbstate_t+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -20124,20 +21889,21 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_compile") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err } && test -s conftest.$ac_objext; then mutt_cv_mbstate_t=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 mutt_cv_mbstate_t=no @@ -20145,8 +21911,8 @@ fi rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $mutt_cv_mbstate_t" >&5 -echo "${ECHO_T}$mutt_cv_mbstate_t" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_mbstate_t" >&5 +$as_echo "$mutt_cv_mbstate_t" >&6; } if test "$mutt_cv_mbstate_t" = no; then @@ -20165,10 +21931,10 @@ fi if test "$wc_funcs" != yes && test "$wc_funcs" != no; then - { echo "$as_me:$LINENO: checking for wchar_t functions" >&5 -echo $ECHO_N "checking for wchar_t functions... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for wchar_t functions" >&5 +$as_echo_n "checking for wchar_t functions... " >&6; } if test "${mutt_cv_wc_funcs+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else mutt_cv_wc_funcs=no cat >conftest.$ac_ext <<_ACEOF @@ -20202,31 +21968,35 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then mutt_cv_wc_funcs=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $mutt_cv_wc_funcs" >&5 -echo "${ECHO_T}$mutt_cv_wc_funcs" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_wc_funcs" >&5 +$as_echo "$mutt_cv_wc_funcs" >&6; } wc_funcs=$mutt_cv_wc_funcs fi @@ -20240,10 +22010,10 @@ else MUTT_LIB_OBJECTS="$MUTT_LIB_OBJECTS utf8.o wcwidth.o" fi -{ echo "$as_me:$LINENO: checking for nl_langinfo and CODESET" >&5 -echo $ECHO_N "checking for nl_langinfo and CODESET... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for nl_langinfo and CODESET" >&5 +$as_echo_n "checking for nl_langinfo and CODESET... " >&6; } if test "${mutt_cv_langinfo_codeset+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -20266,31 +22036,35 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then mutt_cv_langinfo_codeset=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 mutt_cv_langinfo_codeset=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $mutt_cv_langinfo_codeset" >&5 -echo "${ECHO_T}$mutt_cv_langinfo_codeset" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_langinfo_codeset" >&5 +$as_echo "$mutt_cv_langinfo_codeset" >&6; } if test $mutt_cv_langinfo_codeset = yes; then cat >>confdefs.h <<\_ACEOF @@ -20299,10 +22073,10 @@ _ACEOF fi -{ echo "$as_me:$LINENO: checking for nl_langinfo and YESEXPR" >&5 -echo $ECHO_N "checking for nl_langinfo and YESEXPR... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for nl_langinfo and YESEXPR" >&5 +$as_echo_n "checking for nl_langinfo and YESEXPR... " >&6; } if test "${mutt_cv_langinfo_yesexpr+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ @@ -20325,31 +22099,35 @@ case "(($ac_try" in *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; *) ac_try_echo=$ac_try;; esac -eval "echo \"\$as_me:$LINENO: $ac_try_echo\"") >&5 +eval ac_try_echo="\"\$as_me:$LINENO: $ac_try_echo\"" +$as_echo "$ac_try_echo") >&5 (eval "$ac_link") 2>conftest.er1 ac_status=$? grep -v '^ *+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:$LINENO: \$? = $ac_status" >&5 + $as_echo "$as_me:$LINENO: \$? = $ac_status" >&5 (exit $ac_status); } && { test -z "$ac_c_werror_flag" || test ! -s conftest.err - } && test -s conftest$ac_exeext && - $as_test_x conftest$ac_exeext; then + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + $as_test_x conftest$ac_exeext + }; then mutt_cv_langinfo_yesexpr=yes else - echo "$as_me: failed program was:" >&5 + $as_echo "$as_me: failed program was:" >&5 sed 's/^/| /' conftest.$ac_ext >&5 mutt_cv_langinfo_yesexpr=no fi +rm -rf conftest.dSYM rm -f core conftest.err conftest.$ac_objext conftest_ipa8_conftest.oo \ conftest$ac_exeext conftest.$ac_ext fi -{ echo "$as_me:$LINENO: result: $mutt_cv_langinfo_yesexpr" >&5 -echo "${ECHO_T}$mutt_cv_langinfo_yesexpr" >&6; } +{ $as_echo "$as_me:$LINENO: result: $mutt_cv_langinfo_yesexpr" >&5 +$as_echo "$mutt_cv_langinfo_yesexpr" >&6; } if test $mutt_cv_langinfo_yesexpr = yes; then cat >>confdefs.h <<\_ACEOF @@ -20361,10 +22139,10 @@ fi have_openjade="no" # Extract the first word of "ospcat", so it can be a program name with args. set dummy ospcat; ac_word=$2 -{ echo "$as_me:$LINENO: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; } +{ $as_echo "$as_me:$LINENO: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } if test "${ac_cv_path_OSPCAT+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 + $as_echo_n "(cached) " >&6 else case $OSPCAT in [\\/]* | ?:[\\/]*) @@ -20379,7 +22157,7 @@ do for ac_exec_ext in '' $ac_executable_extensions; do if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then ac_cv_path_OSPCAT="$as_dir/$ac_word$ac_exec_ext" - echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 + $as_echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5 break 2 fi done @@ -20392,18 +22170,18 @@ esac fi OSPCAT=$ac_cv_path_OSPCAT if test -n "$OSPCAT"; then - { echo "$as_me:$LINENO: result: $OSPCAT" >&5 -echo "${ECHO_T}$OSPCAT" >&6; } + { $as_echo "$as_me:$LINENO: result: $OSPCAT" >&5 +$as_echo "$OSPCAT" >&6; } else - { echo "$as_me:$LINENO: result: no" >&5 -echo "${ECHO_T}no" >&6; } + { $as_echo "$as_me:$LINENO: result: no" >&5 +$as_echo "no" >&6; } fi if test "$OSPCAT" != "none" then - { echo "$as_me:$LINENO: checking for openjade docbook stylesheets" >&5 -echo $ECHO_N "checking for openjade docbook stylesheets... $ECHO_C" >&6; } + { $as_echo "$as_me:$LINENO: checking for openjade docbook stylesheets" >&5 +$as_echo_n "checking for openjade docbook stylesheets... " >&6; } dslosfile=`ospcat --public-id="-//Norman Walsh//DOCUMENT DocBook Print Stylesheet//EN"` DSLROOT=`echo $dslosfile | sed -n -e "s/.*SOIBASE='\([^']*\)\/catalog'.*/\1/p"` # ospcat may spit out an absolute path without an SOIBASE @@ -20413,12 +22191,12 @@ echo $ECHO_N "checking for openjade docbook stylesheets... $ECHO_C" >&6; } fi if test -f $DSLROOT/print/docbook.dsl then - { echo "$as_me:$LINENO: result: in $DSLROOT" >&5 -echo "${ECHO_T}in $DSLROOT" >&6; } + { $as_echo "$as_me:$LINENO: result: in $DSLROOT" >&5 +$as_echo "in $DSLROOT" >&6; } have_openjade="yes" else - { echo "$as_me:$LINENO: result: not found: PDF documentation will not be built." >&5 -echo "${ECHO_T}not found: PDF documentation will not be built." >&6; } + { $as_echo "$as_me:$LINENO: result: not found: PDF documentation will not be built." >&5 +$as_echo "not found: PDF documentation will not be built." >&6; } fi fi @@ -20468,11 +22246,12 @@ _ACEOF case $ac_val in #( *${as_nl}*) case $ac_var in #( - *_cv_*) { echo "$as_me:$LINENO: WARNING: Cache variable $ac_var contains a newline." >&5 -echo "$as_me: WARNING: Cache variable $ac_var contains a newline." >&2;} ;; + *_cv_*) { $as_echo "$as_me:$LINENO: WARNING: cache variable $ac_var contains a newline" >&5 +$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;; esac case $ac_var in #( _ | IFS | as_nl) ;; #( + BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #( *) $as_unset $ac_var ;; esac ;; esac @@ -20505,12 +22284,12 @@ echo "$as_me: WARNING: Cache variable $ac_var contains a newline." >&2;} ;; if diff "$cache_file" confcache >/dev/null 2>&1; then :; else if test -w "$cache_file"; then test "x$cache_file" != "x/dev/null" && - { echo "$as_me:$LINENO: updating cache $cache_file" >&5 -echo "$as_me: updating cache $cache_file" >&6;} + { $as_echo "$as_me:$LINENO: updating cache $cache_file" >&5 +$as_echo "$as_me: updating cache $cache_file" >&6;} cat confcache >$cache_file else - { echo "$as_me:$LINENO: not updating unwritable cache $cache_file" >&5 -echo "$as_me: not updating unwritable cache $cache_file" >&6;} + { $as_echo "$as_me:$LINENO: not updating unwritable cache $cache_file" >&5 +$as_echo "$as_me: not updating unwritable cache $cache_file" >&6;} fi fi rm -f confcache @@ -20526,7 +22305,7 @@ ac_ltlibobjs= for ac_i in : $LIBOBJS; do test "x$ac_i" = x: && continue # 1. Remove the extension, and $U if already installed. ac_script='s/\$U\././;s/\.o$//;s/\.obj$//' - ac_i=`echo "$ac_i" | sed "$ac_script"` + ac_i=`$as_echo "$ac_i" | sed "$ac_script"` # 2. Prepend LIBOBJDIR. When used with automake>=1.10 LIBOBJDIR # will be set to the directory where LIBOBJS objects are built. ac_libobjs="$ac_libobjs \${LIBOBJDIR}$ac_i\$U.$ac_objext" @@ -20537,55 +22316,72 @@ LIBOBJS=$ac_libobjs LTLIBOBJS=$ac_ltlibobjs + if test -n "$EXEEXT"; then + am__EXEEXT_TRUE= + am__EXEEXT_FALSE='#' +else + am__EXEEXT_TRUE='#' + am__EXEEXT_FALSE= +fi + if test -z "${AMDEP_TRUE}" && test -z "${AMDEP_FALSE}"; then - { { echo "$as_me:$LINENO: error: conditional \"AMDEP\" was never defined. + { { $as_echo "$as_me:$LINENO: error: conditional \"AMDEP\" was never defined. +Usually this means the macro was only invoked conditionally." >&5 +$as_echo "$as_me: error: conditional \"AMDEP\" was never defined. +Usually this means the macro was only invoked conditionally." >&2;} + { (exit 1); exit 1; }; } +fi +if test -z "${am__fastdepCC_TRUE}" && test -z "${am__fastdepCC_FALSE}"; then + { { $as_echo "$as_me:$LINENO: error: conditional \"am__fastdepCC\" was never defined. Usually this means the macro was only invoked conditionally." >&5 -echo "$as_me: error: conditional \"AMDEP\" was never defined. +$as_echo "$as_me: error: conditional \"am__fastdepCC\" was never defined. Usually this means the macro was only invoked conditionally." >&2;} { (exit 1); exit 1; }; } fi if test -z "${am__fastdepCC_TRUE}" && test -z "${am__fastdepCC_FALSE}"; then - { { echo "$as_me:$LINENO: error: conditional \"am__fastdepCC\" was never defined. + { { $as_echo "$as_me:$LINENO: error: conditional \"am__fastdepCC\" was never defined. Usually this means the macro was only invoked conditionally." >&5 -echo "$as_me: error: conditional \"am__fastdepCC\" was never defined. +$as_echo "$as_me: error: conditional \"am__fastdepCC\" was never defined. Usually this means the macro was only invoked conditionally." >&2;} { (exit 1); exit 1; }; } fi + if test -z "${BUILD_IMAP_TRUE}" && test -z "${BUILD_IMAP_FALSE}"; then - { { echo "$as_me:$LINENO: error: conditional \"BUILD_IMAP\" was never defined. + { { $as_echo "$as_me:$LINENO: error: conditional \"BUILD_IMAP\" was never defined. Usually this means the macro was only invoked conditionally." >&5 -echo "$as_me: error: conditional \"BUILD_IMAP\" was never defined. +$as_echo "$as_me: error: conditional \"BUILD_IMAP\" was never defined. Usually this means the macro was only invoked conditionally." >&2;} { (exit 1); exit 1; }; } fi if test -z "${USE_GSS_TRUE}" && test -z "${USE_GSS_FALSE}"; then - { { echo "$as_me:$LINENO: error: conditional \"USE_GSS\" was never defined. + { { $as_echo "$as_me:$LINENO: error: conditional \"USE_GSS\" was never defined. Usually this means the macro was only invoked conditionally." >&5 -echo "$as_me: error: conditional \"USE_GSS\" was never defined. +$as_echo "$as_me: error: conditional \"USE_GSS\" was never defined. Usually this means the macro was only invoked conditionally." >&2;} { (exit 1); exit 1; }; } fi if test -z "${USE_SSL_TRUE}" && test -z "${USE_SSL_FALSE}"; then - { { echo "$as_me:$LINENO: error: conditional \"USE_SSL\" was never defined. + { { $as_echo "$as_me:$LINENO: error: conditional \"USE_SSL\" was never defined. Usually this means the macro was only invoked conditionally." >&5 -echo "$as_me: error: conditional \"USE_SSL\" was never defined. +$as_echo "$as_me: error: conditional \"USE_SSL\" was never defined. Usually this means the macro was only invoked conditionally." >&2;} { (exit 1); exit 1; }; } fi if test -z "${USE_SASL_TRUE}" && test -z "${USE_SASL_FALSE}"; then - { { echo "$as_me:$LINENO: error: conditional \"USE_SASL\" was never defined. + { { $as_echo "$as_me:$LINENO: error: conditional \"USE_SASL\" was never defined. Usually this means the macro was only invoked conditionally." >&5 -echo "$as_me: error: conditional \"USE_SASL\" was never defined. +$as_echo "$as_me: error: conditional \"USE_SASL\" was never defined. Usually this means the macro was only invoked conditionally." >&2;} { (exit 1); exit 1; }; } fi : ${CONFIG_STATUS=./config.status} +ac_write_fail=0 ac_clean_files_save=$ac_clean_files ac_clean_files="$ac_clean_files $CONFIG_STATUS" -{ echo "$as_me:$LINENO: creating $CONFIG_STATUS" >&5 -echo "$as_me: creating $CONFIG_STATUS" >&6;} -cat >$CONFIG_STATUS <<_ACEOF +{ $as_echo "$as_me:$LINENO: creating $CONFIG_STATUS" >&5 +$as_echo "$as_me: creating $CONFIG_STATUS" >&6;} +cat >$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 #! $SHELL # Generated by $as_me. # Run this file to recreate the current configuration. @@ -20598,7 +22394,7 @@ ac_cs_silent=false SHELL=\${CONFIG_SHELL-$SHELL} _ACEOF -cat >>$CONFIG_STATUS <<\_ACEOF +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 ## --------------------- ## ## M4sh Initialization. ## ## --------------------- ## @@ -20608,7 +22404,7 @@ DUALCASE=1; export DUALCASE # for MKS sh if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then emulate sh NULLCMD=: - # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which + # Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which # is contrary to our usage. Disable this feature. alias -g '${1+"$@"}'='"$@"' setopt NO_GLOB_SUBST @@ -20630,17 +22426,45 @@ as_cr_Letters=$as_cr_letters$as_cr_LETTERS as_cr_digits='0123456789' as_cr_alnum=$as_cr_Letters$as_cr_digits -# The user is always right. -if test "${PATH_SEPARATOR+set}" != set; then - echo "#! /bin/sh" >conf$$.sh - echo "exit 0" >>conf$$.sh - chmod +x conf$$.sh - if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then - PATH_SEPARATOR=';' +as_nl=' +' +export as_nl +# Printing a long string crashes Solaris 7 /usr/bin/printf. +as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\' +as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo +as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo +if (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then + as_echo='printf %s\n' + as_echo_n='printf %s' +else + if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then + as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"' + as_echo_n='/usr/ucb/echo -n' else - PATH_SEPARATOR=: + as_echo_body='eval expr "X$1" : "X\\(.*\\)"' + as_echo_n_body='eval + arg=$1; + case $arg in + *"$as_nl"*) + expr "X$arg" : "X\\(.*\\)$as_nl"; + arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;; + esac; + expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl" + ' + export as_echo_n_body + as_echo_n='sh -c $as_echo_n_body as_echo' fi - rm -f conf$$.sh + export as_echo_body + as_echo='sh -c $as_echo_body as_echo' +fi + +# The user is always right. +if test "${PATH_SEPARATOR+set}" != set; then + PATH_SEPARATOR=: + (PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && { + (PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 || + PATH_SEPARATOR=';' + } fi # Support unset when possible. @@ -20656,8 +22480,6 @@ fi # there to prevent editors from complaining about space-tab. # (If _AS_PATH_WALK were called with IFS unset, it would disable word # splitting by setting IFS to empty value.) -as_nl=' -' IFS=" "" $as_nl" # Find who we are. Look in the path if we contain no directory separator. @@ -20680,7 +22502,7 @@ if test "x$as_myself" = x; then as_myself=$0 fi if test ! -f "$as_myself"; then - echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2 + $as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2 { (exit 1); exit 1; } fi @@ -20693,17 +22515,10 @@ PS2='> ' PS4='+ ' # NLS nuisances. -for as_var in \ - LANG LANGUAGE LC_ADDRESS LC_ALL LC_COLLATE LC_CTYPE LC_IDENTIFICATION \ - LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER \ - LC_TELEPHONE LC_TIME -do - if (set +x; test -z "`(eval $as_var=C; export $as_var) 2>&1`"); then - eval $as_var=C; export $as_var - else - ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var - fi -done +LC_ALL=C +export LC_ALL +LANGUAGE=C +export LANGUAGE # Required to use basename. if expr a : '\(a\)' >/dev/null 2>&1 && @@ -20725,7 +22540,7 @@ as_me=`$as_basename -- "$0" || $as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \ X"$0" : 'X\(//\)$' \| \ X"$0" : 'X\(/\)' \| . 2>/dev/null || -echo X/"$0" | +$as_echo X/"$0" | sed '/^.*\/\([^/][^/]*\)\/*$/{ s//\1/ q @@ -20776,7 +22591,7 @@ $as_unset CDPATH s/-\n.*// ' >$as_me.lineno && chmod +x "$as_me.lineno" || - { echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2 + { $as_echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2 { (exit 1); exit 1; }; } # Don't try to exec as it changes $[0], causing all sort of problems @@ -20804,7 +22619,6 @@ case `echo -n x` in *) ECHO_N='-n';; esac - if expr a : '\(a\)' >/dev/null 2>&1 && test "X`expr 00001 : '.*\(...\)'`" = X001; then as_expr=expr @@ -20817,19 +22631,22 @@ if test -d conf$$.dir; then rm -f conf$$.dir/conf$$.file else rm -f conf$$.dir - mkdir conf$$.dir -fi -echo >conf$$.file -if ln -s conf$$.file conf$$ 2>/dev/null; then - as_ln_s='ln -s' - # ... but there are two gotchas: - # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail. - # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable. - # In both cases, we have to default to `cp -p'. - ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe || + mkdir conf$$.dir 2>/dev/null +fi +if (echo >conf$$.file) 2>/dev/null; then + if ln -s conf$$.file conf$$ 2>/dev/null; then + as_ln_s='ln -s' + # ... but there are two gotchas: + # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail. + # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable. + # In both cases, we have to default to `cp -p'. + ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe || + as_ln_s='cp -p' + elif ln conf$$.file conf$$ 2>/dev/null; then + as_ln_s=ln + else as_ln_s='cp -p' -elif ln conf$$.file conf$$ 2>/dev/null; then - as_ln_s=ln + fi else as_ln_s='cp -p' fi @@ -20854,10 +22671,10 @@ else as_test_x=' eval sh -c '\'' if test -d "$1"; then - test -d "$1/."; + test -d "$1/."; else case $1 in - -*)set "./$1";; + -*)set "./$1";; esac; case `ls -ld'$as_ls_L_option' "$1" 2>/dev/null` in ???[sx]*):;;*)false;;esac;fi @@ -20880,7 +22697,7 @@ exec 6>&1 # values after options handling. ac_log=" This file was extended by $as_me, which was -generated by GNU Autoconf 2.61. Invocation command line was +generated by GNU Autoconf 2.63. Invocation command line was CONFIG_FILES = $CONFIG_FILES CONFIG_HEADERS = $CONFIG_HEADERS @@ -20893,7 +22710,16 @@ on `(hostname || uname -n) 2>/dev/null | sed 1q` _ACEOF -cat >>$CONFIG_STATUS <<_ACEOF +case $ac_config_files in *" +"*) set x $ac_config_files; shift; ac_config_files=$*;; +esac + +case $ac_config_headers in *" +"*) set x $ac_config_headers; shift; ac_config_headers=$*;; +esac + + +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 # Files that config.status was made for. config_files="$ac_config_files" config_headers="$ac_config_headers" @@ -20901,22 +22727,23 @@ config_commands="$ac_config_commands" _ACEOF -cat >>$CONFIG_STATUS <<\_ACEOF +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 ac_cs_usage="\ \`$as_me' instantiates files from templates according to the current configuration. -Usage: $0 [OPTIONS] [FILE]... +Usage: $0 [OPTION]... [FILE]... -h, --help print this help, then exit -V, --version print version number and configuration settings, then exit - -q, --quiet do not print progress messages + -q, --quiet, --silent + do not print progress messages -d, --debug don't remove temporary files --recheck update $as_me by reconfiguring in the same conditions - --file=FILE[:TEMPLATE] - instantiate the configuration file FILE - --header=FILE[:TEMPLATE] - instantiate the configuration header FILE + --file=FILE[:TEMPLATE] + instantiate the configuration file FILE + --header=FILE[:TEMPLATE] + instantiate the configuration header FILE Configuration files: $config_files @@ -20930,13 +22757,13 @@ $config_commands Report bugs to ." _ACEOF -cat >>$CONFIG_STATUS <<_ACEOF +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_cs_version="\\ config.status -configured by $0, generated by GNU Autoconf 2.61, - with options \\"`echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`\\" +configured by $0, generated by GNU Autoconf 2.63, + with options \\"`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`\\" -Copyright (C) 2006 Free Software Foundation, Inc. +Copyright (C) 2008 Free Software Foundation, Inc. This config.status script is free software; the Free Software Foundation gives unlimited permission to copy, distribute and modify it." @@ -20944,11 +22771,12 @@ ac_pwd='$ac_pwd' srcdir='$srcdir' INSTALL='$INSTALL' MKDIR_P='$MKDIR_P' +AWK='$AWK' +test -n "\$AWK" || AWK=awk _ACEOF -cat >>$CONFIG_STATUS <<\_ACEOF -# If no file are specified by the user, then we need to provide default -# value. By we need to know if files were specified by the user. +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 +# The default lists apply if the user does not specify any file. ac_need_defaults=: while test $# != 0 do @@ -20970,30 +22798,36 @@ do -recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r) ac_cs_recheck=: ;; --version | --versio | --versi | --vers | --ver | --ve | --v | -V ) - echo "$ac_cs_version"; exit ;; + $as_echo "$ac_cs_version"; exit ;; --debug | --debu | --deb | --de | --d | -d ) debug=: ;; --file | --fil | --fi | --f ) $ac_shift - CONFIG_FILES="$CONFIG_FILES $ac_optarg" + case $ac_optarg in + *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;; + esac + CONFIG_FILES="$CONFIG_FILES '$ac_optarg'" ac_need_defaults=false;; --header | --heade | --head | --hea ) $ac_shift - CONFIG_HEADERS="$CONFIG_HEADERS $ac_optarg" + case $ac_optarg in + *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;; + esac + CONFIG_HEADERS="$CONFIG_HEADERS '$ac_optarg'" ac_need_defaults=false;; --he | --h) # Conflict between --help and --header - { echo "$as_me: error: ambiguous option: $1 + { $as_echo "$as_me: error: ambiguous option: $1 Try \`$0 --help' for more information." >&2 { (exit 1); exit 1; }; };; --help | --hel | -h ) - echo "$ac_cs_usage"; exit ;; + $as_echo "$ac_cs_usage"; exit ;; -q | -quiet | --quiet | --quie | --qui | --qu | --q \ | -silent | --silent | --silen | --sile | --sil | --si | --s) ac_cs_silent=: ;; # This is an error. - -*) { echo "$as_me: error: unrecognized option: $1 + -*) { $as_echo "$as_me: error: unrecognized option: $1 Try \`$0 --help' for more information." >&2 { (exit 1); exit 1; }; } ;; @@ -21012,27 +22846,29 @@ if $ac_cs_silent; then fi _ACEOF -cat >>$CONFIG_STATUS <<_ACEOF +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 if \$ac_cs_recheck; then - echo "running CONFIG_SHELL=$SHELL $SHELL $0 "$ac_configure_args \$ac_configure_extra_args " --no-create --no-recursion" >&6 - CONFIG_SHELL=$SHELL + set X '$SHELL' '$0' $ac_configure_args \$ac_configure_extra_args --no-create --no-recursion + shift + \$as_echo "running CONFIG_SHELL=$SHELL \$*" >&6 + CONFIG_SHELL='$SHELL' export CONFIG_SHELL - exec $SHELL "$0"$ac_configure_args \$ac_configure_extra_args --no-create --no-recursion + exec "\$@" fi _ACEOF -cat >>$CONFIG_STATUS <<\_ACEOF +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 exec 5>>config.log { echo sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX ## Running $as_me. ## _ASBOX - echo "$ac_log" + $as_echo "$ac_log" } >&5 _ACEOF -cat >>$CONFIG_STATUS <<_ACEOF +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 # # INIT-COMMANDS # @@ -21041,7 +22877,7 @@ AMDEP_TRUE="$AMDEP_TRUE" ac_aux_dir="$ac_aux_dir" _ACEOF -cat >>$CONFIG_STATUS <<\_ACEOF +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 # Handling of arguments. for ac_config_target in $ac_config_targets @@ -21061,8 +22897,8 @@ do "muttbug.sh") CONFIG_FILES="$CONFIG_FILES muttbug.sh" ;; "doc/instdoc.sh") CONFIG_FILES="$CONFIG_FILES doc/instdoc.sh" ;; - *) { { echo "$as_me:$LINENO: error: invalid argument: $ac_config_target" >&5 -echo "$as_me: error: invalid argument: $ac_config_target" >&2;} + *) { { $as_echo "$as_me:$LINENO: error: invalid argument: $ac_config_target" >&5 +$as_echo "$as_me: error: invalid argument: $ac_config_target" >&2;} { (exit 1); exit 1; }; };; esac done @@ -21103,255 +22939,144 @@ $debug || (umask 077 && mkdir "$tmp") } || { - echo "$me: cannot create a temporary directory in ." >&2 + $as_echo "$as_me: cannot create a temporary directory in ." >&2 { (exit 1); exit 1; } } -# -# Set up the sed scripts for CONFIG_FILES section. -# - -# No need to generate the scripts if there are no CONFIG_FILES. -# This happens for instance when ./config.status config.h +# Set up the scripts for CONFIG_FILES section. +# No need to generate them if there are no CONFIG_FILES. +# This happens for instance with `./config.status config.h'. if test -n "$CONFIG_FILES"; then -_ACEOF - - - -ac_delim='%!_!# ' -for ac_last_try in false false false false false :; do - cat >conf$$subs.sed <<_ACEOF -SHELL!$SHELL$ac_delim -PATH_SEPARATOR!$PATH_SEPARATOR$ac_delim -PACKAGE_NAME!$PACKAGE_NAME$ac_delim -PACKAGE_TARNAME!$PACKAGE_TARNAME$ac_delim -PACKAGE_VERSION!$PACKAGE_VERSION$ac_delim -PACKAGE_STRING!$PACKAGE_STRING$ac_delim -PACKAGE_BUGREPORT!$PACKAGE_BUGREPORT$ac_delim -exec_prefix!$exec_prefix$ac_delim -prefix!$prefix$ac_delim -program_transform_name!$program_transform_name$ac_delim -bindir!$bindir$ac_delim -sbindir!$sbindir$ac_delim -libexecdir!$libexecdir$ac_delim -datarootdir!$datarootdir$ac_delim -datadir!$datadir$ac_delim -sysconfdir!$sysconfdir$ac_delim -sharedstatedir!$sharedstatedir$ac_delim -localstatedir!$localstatedir$ac_delim -includedir!$includedir$ac_delim -oldincludedir!$oldincludedir$ac_delim -docdir!$docdir$ac_delim -infodir!$infodir$ac_delim -htmldir!$htmldir$ac_delim -dvidir!$dvidir$ac_delim -pdfdir!$pdfdir$ac_delim -psdir!$psdir$ac_delim -libdir!$libdir$ac_delim -localedir!$localedir$ac_delim -mandir!$mandir$ac_delim -DEFS!$DEFS$ac_delim -ECHO_C!$ECHO_C$ac_delim -ECHO_N!$ECHO_N$ac_delim -ECHO_T!$ECHO_T$ac_delim -LIBS!$LIBS$ac_delim -build_alias!$build_alias$ac_delim -host_alias!$host_alias$ac_delim -target_alias!$target_alias$ac_delim -INSTALL_PROGRAM!$INSTALL_PROGRAM$ac_delim -INSTALL_SCRIPT!$INSTALL_SCRIPT$ac_delim -INSTALL_DATA!$INSTALL_DATA$ac_delim -am__isrc!$am__isrc$ac_delim -CYGPATH_W!$CYGPATH_W$ac_delim -PACKAGE!$PACKAGE$ac_delim -VERSION!$VERSION$ac_delim -ACLOCAL!$ACLOCAL$ac_delim -AUTOCONF!$AUTOCONF$ac_delim -AUTOMAKE!$AUTOMAKE$ac_delim -AUTOHEADER!$AUTOHEADER$ac_delim -MAKEINFO!$MAKEINFO$ac_delim -install_sh!$install_sh$ac_delim -STRIP!$STRIP$ac_delim -INSTALL_STRIP_PROGRAM!$INSTALL_STRIP_PROGRAM$ac_delim -mkdir_p!$mkdir_p$ac_delim -AWK!$AWK$ac_delim -SET_MAKE!$SET_MAKE$ac_delim -am__leading_dot!$am__leading_dot$ac_delim -AMTAR!$AMTAR$ac_delim -am__tar!$am__tar$ac_delim -am__untar!$am__untar$ac_delim -CONFIG_STATUS_DEPENDENCIES!$CONFIG_STATUS_DEPENDENCIES$ac_delim -build!$build$ac_delim -build_cpu!$build_cpu$ac_delim -build_vendor!$build_vendor$ac_delim -build_os!$build_os$ac_delim -host!$host$ac_delim -host_cpu!$host_cpu$ac_delim -host_vendor!$host_vendor$ac_delim -host_os!$host_os$ac_delim -CC!$CC$ac_delim -CFLAGS!$CFLAGS$ac_delim -LDFLAGS!$LDFLAGS$ac_delim -CPPFLAGS!$CPPFLAGS$ac_delim -ac_ct_CC!$ac_ct_CC$ac_delim -EXEEXT!$EXEEXT$ac_delim -OBJEXT!$OBJEXT$ac_delim -DEPDIR!$DEPDIR$ac_delim -am__include!$am__include$ac_delim -am__quote!$am__quote$ac_delim -AMDEP_TRUE!$AMDEP_TRUE$ac_delim -AMDEP_FALSE!$AMDEP_FALSE$ac_delim -AMDEPBACKSLASH!$AMDEPBACKSLASH$ac_delim -CCDEPMODE!$CCDEPMODE$ac_delim -am__fastdepCC_TRUE!$am__fastdepCC_TRUE$ac_delim -am__fastdepCC_FALSE!$am__fastdepCC_FALSE$ac_delim -CPP!$CPP$ac_delim -GREP!$GREP$ac_delim -EGREP!$EGREP$ac_delim -U!$U$ac_delim -ANSI2KNR!$ANSI2KNR$ac_delim -RANLIB!$RANLIB$ac_delim -AR!$AR$ac_delim -DBX!$DBX$ac_delim -GDB!$GDB$ac_delim -SDB!$SDB$ac_delim -DEBUGGER!$DEBUGGER$ac_delim -SENDMAIL!$SENDMAIL$ac_delim -GPGME_CONFIG!$GPGME_CONFIG$ac_delim -_ACEOF - - if test `sed -n "s/.*$ac_delim\$/X/p" conf$$subs.sed | grep -c X` = 97; then - break - elif $ac_last_try; then - { { echo "$as_me:$LINENO: error: could not make $CONFIG_STATUS" >&5 -echo "$as_me: error: could not make $CONFIG_STATUS" >&2;} - { (exit 1); exit 1; }; } - else - ac_delim="$ac_delim!$ac_delim _$ac_delim!! " - fi -done -ac_eof=`sed -n '/^CEOF[0-9]*$/s/CEOF/0/p' conf$$subs.sed` -if test -n "$ac_eof"; then - ac_eof=`echo "$ac_eof" | sort -nru | sed 1q` - ac_eof=`expr $ac_eof + 1` +ac_cr=' ' +ac_cs_awk_cr=`$AWK 'BEGIN { print "a\rb" }' /dev/null` +if test "$ac_cs_awk_cr" = "a${ac_cr}b"; then + ac_cs_awk_cr='\\r' +else + ac_cs_awk_cr=$ac_cr fi -cat >>$CONFIG_STATUS <<_ACEOF -cat >"\$tmp/subs-1.sed" <<\CEOF$ac_eof -/@[a-zA-Z_][a-zA-Z_0-9]*@/!b -_ACEOF -sed ' -s/[,\\&]/\\&/g; s/@/@|#_!!_#|/g -s/^/s,@/; s/!/@,|#_!!_#|/ -:n -t n -s/'"$ac_delim"'$/,g/; t -s/$/\\/; p -N; s/^.*\n//; s/[,\\&]/\\&/g; s/@/@|#_!!_#|/g; b n -' >>$CONFIG_STATUS >$CONFIG_STATUS <<_ACEOF -CEOF$ac_eof +echo 'BEGIN {' >"$tmp/subs1.awk" && _ACEOF +{ + echo "cat >conf$$subs.awk <<_ACEOF" && + echo "$ac_subst_vars" | sed 's/.*/&!$&$ac_delim/' && + echo "_ACEOF" +} >conf$$subs.sh || + { { $as_echo "$as_me:$LINENO: error: could not make $CONFIG_STATUS" >&5 +$as_echo "$as_me: error: could not make $CONFIG_STATUS" >&2;} + { (exit 1); exit 1; }; } +ac_delim_num=`echo "$ac_subst_vars" | grep -c '$'` ac_delim='%!_!# ' for ac_last_try in false false false false false :; do - cat >conf$$subs.sed <<_ACEOF -GPGME_CFLAGS!$GPGME_CFLAGS$ac_delim -GPGME_LIBS!$GPGME_LIBS$ac_delim -OPS!$OPS$ac_delim -PGPAUX_TARGET!$PGPAUX_TARGET$ac_delim -SMIMEAUX_TARGET!$SMIMEAUX_TARGET$ac_delim -ISPELL!$ISPELL$ac_delim -LIBOBJS!$LIBOBJS$ac_delim -DOTLOCK_TARGET!$DOTLOCK_TARGET$ac_delim -DOTLOCK_GROUP!$DOTLOCK_GROUP$ac_delim -DOTLOCK_PERMISSION!$DOTLOCK_PERMISSION$ac_delim -BUILD_IMAP_TRUE!$BUILD_IMAP_TRUE$ac_delim -BUILD_IMAP_FALSE!$BUILD_IMAP_FALSE$ac_delim -KRB5CFGPATH!$KRB5CFGPATH$ac_delim -USE_GSS_TRUE!$USE_GSS_TRUE$ac_delim -USE_GSS_FALSE!$USE_GSS_FALSE$ac_delim -LIBGNUTLS_CONFIG!$LIBGNUTLS_CONFIG$ac_delim -LIBGNUTLS_CFLAGS!$LIBGNUTLS_CFLAGS$ac_delim -LIBGNUTLS_LIBS!$LIBGNUTLS_LIBS$ac_delim -USE_SSL_TRUE!$USE_SSL_TRUE$ac_delim -USE_SSL_FALSE!$USE_SSL_FALSE$ac_delim -USE_SASL_TRUE!$USE_SASL_TRUE$ac_delim -USE_SASL_FALSE!$USE_SASL_FALSE$ac_delim -MUTT_MD5!$MUTT_MD5$ac_delim -MUTTLIBS!$MUTTLIBS$ac_delim -MUTT_LIB_OBJECTS!$MUTT_LIB_OBJECTS$ac_delim -LIBIMAP!$LIBIMAP$ac_delim -LIBIMAPDEPS!$LIBIMAPDEPS$ac_delim -ALLOCA!$ALLOCA$ac_delim -GLIBC21!$GLIBC21$ac_delim -LIBICONV!$LIBICONV$ac_delim -USE_NLS!$USE_NLS$ac_delim -MSGFMT!$MSGFMT$ac_delim -GMSGFMT!$GMSGFMT$ac_delim -XGETTEXT!$XGETTEXT$ac_delim -INTLBISON!$INTLBISON$ac_delim -BUILD_INCLUDED_LIBINTL!$BUILD_INCLUDED_LIBINTL$ac_delim -USE_INCLUDED_LIBINTL!$USE_INCLUDED_LIBINTL$ac_delim -CATALOGS!$CATALOGS$ac_delim -CATOBJEXT!$CATOBJEXT$ac_delim -GMOFILES!$GMOFILES$ac_delim -INTLLIBS!$INTLLIBS$ac_delim -INTLOBJS!$INTLOBJS$ac_delim -POFILES!$POFILES$ac_delim -POSUB!$POSUB$ac_delim -DATADIRNAME!$DATADIRNAME$ac_delim -INSTOBJEXT!$INSTOBJEXT$ac_delim -GENCAT!$GENCAT$ac_delim -MKINSTALLDIRS!$MKINSTALLDIRS$ac_delim -INTL_LIBTOOL_SUFFIX_PREFIX!$INTL_LIBTOOL_SUFFIX_PREFIX$ac_delim -OSPCAT!$OSPCAT$ac_delim -DSLROOT!$DSLROOT$ac_delim -LTLIBOBJS!$LTLIBOBJS$ac_delim -_ACEOF - - if test `sed -n "s/.*$ac_delim\$/X/p" conf$$subs.sed | grep -c X` = 52; then + . ./conf$$subs.sh || + { { $as_echo "$as_me:$LINENO: error: could not make $CONFIG_STATUS" >&5 +$as_echo "$as_me: error: could not make $CONFIG_STATUS" >&2;} + { (exit 1); exit 1; }; } + + ac_delim_n=`sed -n "s/.*$ac_delim\$/X/p" conf$$subs.awk | grep -c X` + if test $ac_delim_n = $ac_delim_num; then break elif $ac_last_try; then - { { echo "$as_me:$LINENO: error: could not make $CONFIG_STATUS" >&5 -echo "$as_me: error: could not make $CONFIG_STATUS" >&2;} + { { $as_echo "$as_me:$LINENO: error: could not make $CONFIG_STATUS" >&5 +$as_echo "$as_me: error: could not make $CONFIG_STATUS" >&2;} { (exit 1); exit 1; }; } else ac_delim="$ac_delim!$ac_delim _$ac_delim!! " fi done +rm -f conf$$subs.sh + +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 +cat >>"\$tmp/subs1.awk" <<\\_ACAWK && +_ACEOF +sed -n ' +h +s/^/S["/; s/!.*/"]=/ +p +g +s/^[^!]*!// +:repl +t repl +s/'"$ac_delim"'$// +t delim +:nl +h +s/\(.\{148\}\).*/\1/ +t more1 +s/["\\]/\\&/g; s/^/"/; s/$/\\n"\\/ +p +n +b repl +:more1 +s/["\\]/\\&/g; s/^/"/; s/$/"\\/ +p +g +s/.\{148\}// +t nl +:delim +h +s/\(.\{148\}\).*/\1/ +t more2 +s/["\\]/\\&/g; s/^/"/; s/$/"/ +p +b +:more2 +s/["\\]/\\&/g; s/^/"/; s/$/"\\/ +p +g +s/.\{148\}// +t delim +' >$CONFIG_STATUS || ac_write_fail=1 +rm -f conf$$subs.awk +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 +_ACAWK +cat >>"\$tmp/subs1.awk" <<_ACAWK && + for (key in S) S_is_set[key] = 1 + FS = "" -ac_eof=`sed -n '/^CEOF[0-9]*$/s/CEOF/0/p' conf$$subs.sed` -if test -n "$ac_eof"; then - ac_eof=`echo "$ac_eof" | sort -nru | sed 1q` - ac_eof=`expr $ac_eof + 1` -fi +} +{ + line = $ 0 + nfields = split(line, field, "@") + substed = 0 + len = length(field[1]) + for (i = 2; i < nfields; i++) { + key = field[i] + keylen = length(key) + if (S_is_set[key]) { + value = S[key] + line = substr(line, 1, len) "" value "" substr(line, len + keylen + 3) + len += length(value) + length(field[++i]) + substed = 1 + } else + len += 1 + keylen + } -cat >>$CONFIG_STATUS <<_ACEOF -cat >"\$tmp/subs-2.sed" <<\CEOF$ac_eof -/@[a-zA-Z_][a-zA-Z_0-9]*@/!b end + print line +} + +_ACAWK _ACEOF -sed ' -s/[,\\&]/\\&/g; s/@/@|#_!!_#|/g -s/^/s,@/; s/!/@,|#_!!_#|/ -:n -t n -s/'"$ac_delim"'$/,g/; t -s/$/\\/; p -N; s/^.*\n//; s/[,\\&]/\\&/g; s/@/@|#_!!_#|/g; b n -' >>$CONFIG_STATUS >$CONFIG_STATUS <<_ACEOF -:end -s/|#_!!_#|//g -CEOF$ac_eof +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 +if sed "s/$ac_cr//" < /dev/null > /dev/null 2>&1; then + sed "s/$ac_cr\$//; s/$ac_cr/$ac_cs_awk_cr/g" +else + cat +fi < "$tmp/subs1.awk" > "$tmp/subs.awk" \ + || { { $as_echo "$as_me:$LINENO: error: could not setup config files machinery" >&5 +$as_echo "$as_me: error: could not setup config files machinery" >&2;} + { (exit 1); exit 1; }; } _ACEOF - # VPATH may cause trouble with some makes, so we remove $(srcdir), # ${srcdir} and @srcdir@ from VPATH if srcdir is ".", strip leading and # trailing colons and then remove the whole line if VPATH becomes empty @@ -21367,19 +23092,133 @@ s/^[^=]*=[ ]*$// }' fi -cat >>$CONFIG_STATUS <<\_ACEOF +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 fi # test -n "$CONFIG_FILES" +# Set up the scripts for CONFIG_HEADERS section. +# No need to generate them if there are no CONFIG_HEADERS. +# This happens for instance with `./config.status Makefile'. +if test -n "$CONFIG_HEADERS"; then +cat >"$tmp/defines.awk" <<\_ACAWK || +BEGIN { +_ACEOF + +# Transform confdefs.h into an awk script `defines.awk', embedded as +# here-document in config.status, that substitutes the proper values into +# config.h.in to produce config.h. + +# Create a delimiter string that does not exist in confdefs.h, to ease +# handling of long lines. +ac_delim='%!_!# ' +for ac_last_try in false false :; do + ac_t=`sed -n "/$ac_delim/p" confdefs.h` + if test -z "$ac_t"; then + break + elif $ac_last_try; then + { { $as_echo "$as_me:$LINENO: error: could not make $CONFIG_HEADERS" >&5 +$as_echo "$as_me: error: could not make $CONFIG_HEADERS" >&2;} + { (exit 1); exit 1; }; } + else + ac_delim="$ac_delim!$ac_delim _$ac_delim!! " + fi +done + +# For the awk script, D is an array of macro values keyed by name, +# likewise P contains macro parameters if any. Preserve backslash +# newline sequences. + +ac_word_re=[_$as_cr_Letters][_$as_cr_alnum]* +sed -n ' +s/.\{148\}/&'"$ac_delim"'/g +t rset +:rset +s/^[ ]*#[ ]*define[ ][ ]*/ / +t def +d +:def +s/\\$// +t bsnl +s/["\\]/\\&/g +s/^ \('"$ac_word_re"'\)\(([^()]*)\)[ ]*\(.*\)/P["\1"]="\2"\ +D["\1"]=" \3"/p +s/^ \('"$ac_word_re"'\)[ ]*\(.*\)/D["\1"]=" \2"/p +d +:bsnl +s/["\\]/\\&/g +s/^ \('"$ac_word_re"'\)\(([^()]*)\)[ ]*\(.*\)/P["\1"]="\2"\ +D["\1"]=" \3\\\\\\n"\\/p +t cont +s/^ \('"$ac_word_re"'\)[ ]*\(.*\)/D["\1"]=" \2\\\\\\n"\\/p +t cont +d +:cont +n +s/.\{148\}/&'"$ac_delim"'/g +t clear +:clear +s/\\$// +t bsnlc +s/["\\]/\\&/g; s/^/"/; s/$/"/p +d +:bsnlc +s/["\\]/\\&/g; s/^/"/; s/$/\\\\\\n"\\/p +b cont +' >$CONFIG_STATUS || ac_write_fail=1 + +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 + for (key in D) D_is_set[key] = 1 + FS = "" +} +/^[\t ]*#[\t ]*(define|undef)[\t ]+$ac_word_re([\t (]|\$)/ { + line = \$ 0 + split(line, arg, " ") + if (arg[1] == "#") { + defundef = arg[2] + mac1 = arg[3] + } else { + defundef = substr(arg[1], 2) + mac1 = arg[2] + } + split(mac1, mac2, "(") #) + macro = mac2[1] + prefix = substr(line, 1, index(line, defundef) - 1) + if (D_is_set[macro]) { + # Preserve the white space surrounding the "#". + print prefix "define", macro P[macro] D[macro] + next + } else { + # Replace #undef with comments. This is necessary, for example, + # in the case of _POSIX_SOURCE, which is predefined and required + # on some systems where configure will not decide to define it. + if (defundef == "undef") { + print "/*", prefix defundef, macro, "*/" + next + } + } +} +{ print } +_ACAWK +_ACEOF +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 + { { $as_echo "$as_me:$LINENO: error: could not setup config headers machinery" >&5 +$as_echo "$as_me: error: could not setup config headers machinery" >&2;} + { (exit 1); exit 1; }; } +fi # test -n "$CONFIG_HEADERS" + -for ac_tag in :F $CONFIG_FILES :H $CONFIG_HEADERS :C $CONFIG_COMMANDS +eval set X " :F $CONFIG_FILES :H $CONFIG_HEADERS :C $CONFIG_COMMANDS" +shift +for ac_tag do case $ac_tag in :[FHLC]) ac_mode=$ac_tag; continue;; esac case $ac_mode$ac_tag in :[FHL]*:*);; - :L* | :C*:*) { { echo "$as_me:$LINENO: error: Invalid tag $ac_tag." >&5 -echo "$as_me: error: Invalid tag $ac_tag." >&2;} + :L* | :C*:*) { { $as_echo "$as_me:$LINENO: error: invalid tag $ac_tag" >&5 +$as_echo "$as_me: error: invalid tag $ac_tag" >&2;} { (exit 1); exit 1; }; };; :[FH]-) ac_tag=-:-;; :[FH]*) ac_tag=$ac_tag:$ac_tag.in;; @@ -21408,26 +23247,38 @@ echo "$as_me: error: Invalid tag $ac_tag." >&2;} [\\/$]*) false;; *) test -f "$srcdir/$ac_f" && ac_f="$srcdir/$ac_f";; esac || - { { echo "$as_me:$LINENO: error: cannot find input file: $ac_f" >&5 -echo "$as_me: error: cannot find input file: $ac_f" >&2;} + { { $as_echo "$as_me:$LINENO: error: cannot find input file: $ac_f" >&5 +$as_echo "$as_me: error: cannot find input file: $ac_f" >&2;} { (exit 1); exit 1; }; };; esac - ac_file_inputs="$ac_file_inputs $ac_f" + case $ac_f in *\'*) ac_f=`$as_echo "$ac_f" | sed "s/'/'\\\\\\\\''/g"`;; esac + ac_file_inputs="$ac_file_inputs '$ac_f'" done # Let's still pretend it is `configure' which instantiates (i.e., don't # use $as_me), people would be surprised to read: # /* config.h. Generated by config.status. */ - configure_input="Generated from "`IFS=: - echo $* | sed 's|^[^:]*/||;s|:[^:]*/|, |g'`" by configure." + configure_input='Generated from '` + $as_echo "$*" | sed 's|^[^:]*/||;s|:[^:]*/|, |g' + `' by configure.' if test x"$ac_file" != x-; then configure_input="$ac_file. $configure_input" - { echo "$as_me:$LINENO: creating $ac_file" >&5 -echo "$as_me: creating $ac_file" >&6;} + { $as_echo "$as_me:$LINENO: creating $ac_file" >&5 +$as_echo "$as_me: creating $ac_file" >&6;} fi + # Neutralize special characters interpreted by sed in replacement strings. + case $configure_input in #( + *\&* | *\|* | *\\* ) + ac_sed_conf_input=`$as_echo "$configure_input" | + sed 's/[\\\\&|]/\\\\&/g'`;; #( + *) ac_sed_conf_input=$configure_input;; + esac case $ac_tag in - *:-:* | *:-) cat >"$tmp/stdin";; + *:-:* | *:-) cat >"$tmp/stdin" \ + || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5 +$as_echo "$as_me: error: could not create $ac_file" >&2;} + { (exit 1); exit 1; }; } ;; esac ;; esac @@ -21437,7 +23288,7 @@ $as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ X"$ac_file" : 'X\(//\)[^/]' \| \ X"$ac_file" : 'X\(//\)$' \| \ X"$ac_file" : 'X\(/\)' \| . 2>/dev/null || -echo X"$ac_file" | +$as_echo X"$ac_file" | sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/ q @@ -21463,7 +23314,7 @@ echo X"$ac_file" | as_dirs= while :; do case $as_dir in #( - *\'*) as_qdir=`echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #( + *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'( *) as_qdir=$as_dir;; esac as_dirs="'$as_qdir' $as_dirs" @@ -21472,7 +23323,7 @@ $as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ X"$as_dir" : 'X\(//\)[^/]' \| \ X"$as_dir" : 'X\(//\)$' \| \ X"$as_dir" : 'X\(/\)' \| . 2>/dev/null || -echo X"$as_dir" | +$as_echo X"$as_dir" | sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/ q @@ -21493,17 +23344,17 @@ echo X"$as_dir" | test -d "$as_dir" && break done test -z "$as_dirs" || eval "mkdir $as_dirs" - } || test -d "$as_dir" || { { echo "$as_me:$LINENO: error: cannot create directory $as_dir" >&5 -echo "$as_me: error: cannot create directory $as_dir" >&2;} + } || test -d "$as_dir" || { { $as_echo "$as_me:$LINENO: error: cannot create directory $as_dir" >&5 +$as_echo "$as_me: error: cannot create directory $as_dir" >&2;} { (exit 1); exit 1; }; }; } ac_builddir=. case "$ac_dir" in .) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;; *) - ac_dir_suffix=/`echo "$ac_dir" | sed 's,^\.[\\/],,'` + ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'` # A ".." for each directory in $ac_dir_suffix. - ac_top_builddir_sub=`echo "$ac_dir_suffix" | sed 's,/[^\\/]*,/..,g;s,/,,'` + ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'` case $ac_top_builddir_sub in "") ac_top_builddir_sub=. ac_top_build_prefix= ;; *) ac_top_build_prefix=$ac_top_builddir_sub/ ;; @@ -21548,12 +23399,13 @@ ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix esac _ACEOF -cat >>$CONFIG_STATUS <<\_ACEOF +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 # If the template does not know about datarootdir, expand it. # FIXME: This hack should be removed a few years after 2.60. ac_datarootdir_hack=; ac_datarootdir_seen= -case `sed -n '/datarootdir/ { +ac_sed_dataroot=' +/datarootdir/ { p q } @@ -21562,13 +23414,14 @@ case `sed -n '/datarootdir/ { /@infodir@/p /@localedir@/p /@mandir@/p -' $ac_file_inputs` in +' +case `eval "sed -n \"\$ac_sed_dataroot\" $ac_file_inputs"` in *datarootdir*) ac_datarootdir_seen=yes;; *@datadir@*|*@docdir@*|*@infodir@*|*@localedir@*|*@mandir@*) - { echo "$as_me:$LINENO: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&5 -echo "$as_me: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&2;} + { $as_echo "$as_me:$LINENO: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&5 +$as_echo "$as_me: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&2;} _ACEOF -cat >>$CONFIG_STATUS <<_ACEOF +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_datarootdir_hack=' s&@datadir@&$datadir&g s&@docdir@&$docdir&g @@ -21582,15 +23435,16 @@ _ACEOF # Neutralize VPATH when `$srcdir' = `.'. # Shell code in configure.ac might set extrasub. # FIXME: do we really want to maintain this feature? -cat >>$CONFIG_STATUS <<_ACEOF - sed "$ac_vpsub +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 +ac_sed_extra="$ac_vpsub $extrasub _ACEOF -cat >>$CONFIG_STATUS <<\_ACEOF +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 :t /@[a-zA-Z_][a-zA-Z_0-9]*@/!b -s&@configure_input@&$configure_input&;t t +s|@configure_input@|$ac_sed_conf_input|;t t s&@top_builddir@&$ac_top_builddir_sub&;t t +s&@top_build_prefix@&$ac_top_build_prefix&;t t s&@srcdir@&$ac_srcdir&;t t s&@abs_srcdir@&$ac_abs_srcdir&;t t s&@top_srcdir@&$ac_top_srcdir&;t t @@ -21601,121 +23455,60 @@ s&@abs_top_builddir@&$ac_abs_top_builddir&;t t s&@INSTALL@&$ac_INSTALL&;t t s&@MKDIR_P@&$ac_MKDIR_P&;t t $ac_datarootdir_hack -" $ac_file_inputs | sed -f "$tmp/subs-1.sed" | sed -f "$tmp/subs-2.sed" >$tmp/out +" +eval sed \"\$ac_sed_extra\" "$ac_file_inputs" | $AWK -f "$tmp/subs.awk" >$tmp/out \ + || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5 +$as_echo "$as_me: error: could not create $ac_file" >&2;} + { (exit 1); exit 1; }; } test -z "$ac_datarootdir_hack$ac_datarootdir_seen" && { ac_out=`sed -n '/\${datarootdir}/p' "$tmp/out"`; test -n "$ac_out"; } && { ac_out=`sed -n '/^[ ]*datarootdir[ ]*:*=/p' "$tmp/out"`; test -z "$ac_out"; } && - { echo "$as_me:$LINENO: WARNING: $ac_file contains a reference to the variable \`datarootdir' + { $as_echo "$as_me:$LINENO: WARNING: $ac_file contains a reference to the variable \`datarootdir' which seems to be undefined. Please make sure it is defined." >&5 -echo "$as_me: WARNING: $ac_file contains a reference to the variable \`datarootdir' +$as_echo "$as_me: WARNING: $ac_file contains a reference to the variable \`datarootdir' which seems to be undefined. Please make sure it is defined." >&2;} rm -f "$tmp/stdin" case $ac_file in - -) cat "$tmp/out"; rm -f "$tmp/out";; - *) rm -f "$ac_file"; mv "$tmp/out" $ac_file;; - esac + -) cat "$tmp/out" && rm -f "$tmp/out";; + *) rm -f "$ac_file" && mv "$tmp/out" "$ac_file";; + esac \ + || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5 +$as_echo "$as_me: error: could not create $ac_file" >&2;} + { (exit 1); exit 1; }; } ;; :H) # # CONFIG_HEADER # -_ACEOF - -# Transform confdefs.h into a sed script `conftest.defines', that -# substitutes the proper values into config.h.in to produce config.h. -rm -f conftest.defines conftest.tail -# First, append a space to every undef/define line, to ease matching. -echo 's/$/ /' >conftest.defines -# Then, protect against being on the right side of a sed subst, or in -# an unquoted here document, in config.status. If some macros were -# called several times there might be several #defines for the same -# symbol, which is useless. But do not sort them, since the last -# AC_DEFINE must be honored. -ac_word_re=[_$as_cr_Letters][_$as_cr_alnum]* -# These sed commands are passed to sed as "A NAME B PARAMS C VALUE D", where -# NAME is the cpp macro being defined, VALUE is the value it is being given. -# PARAMS is the parameter list in the macro definition--in most cases, it's -# just an empty string. -ac_dA='s,^\\([ #]*\\)[^ ]*\\([ ]*' -ac_dB='\\)[ (].*,\\1define\\2' -ac_dC=' ' -ac_dD=' ,' - -uniq confdefs.h | - sed -n ' - t rset - :rset - s/^[ ]*#[ ]*define[ ][ ]*// - t ok - d - :ok - s/[\\&,]/\\&/g - s/^\('"$ac_word_re"'\)\(([^()]*)\)[ ]*\(.*\)/ '"$ac_dA"'\1'"$ac_dB"'\2'"${ac_dC}"'\3'"$ac_dD"'/p - s/^\('"$ac_word_re"'\)[ ]*\(.*\)/'"$ac_dA"'\1'"$ac_dB$ac_dC"'\2'"$ac_dD"'/p - ' >>conftest.defines - -# Remove the space that was appended to ease matching. -# Then replace #undef with comments. This is necessary, for -# example, in the case of _POSIX_SOURCE, which is predefined and required -# on some systems where configure will not decide to define it. -# (The regexp can be short, since the line contains either #define or #undef.) -echo 's/ $// -s,^[ #]*u.*,/* & */,' >>conftest.defines - -# Break up conftest.defines: -ac_max_sed_lines=50 - -# First sed command is: sed -f defines.sed $ac_file_inputs >"$tmp/out1" -# Second one is: sed -f defines.sed "$tmp/out1" >"$tmp/out2" -# Third one will be: sed -f defines.sed "$tmp/out2" >"$tmp/out1" -# et cetera. -ac_in='$ac_file_inputs' -ac_out='"$tmp/out1"' -ac_nxt='"$tmp/out2"' - -while : -do - # Write a here document: - cat >>$CONFIG_STATUS <<_ACEOF - # First, check the format of the line: - cat >"\$tmp/defines.sed" <<\\CEOF -/^[ ]*#[ ]*undef[ ][ ]*$ac_word_re[ ]*\$/b def -/^[ ]*#[ ]*define[ ][ ]*$ac_word_re[( ]/b def -b -:def -_ACEOF - sed ${ac_max_sed_lines}q conftest.defines >>$CONFIG_STATUS - echo 'CEOF - sed -f "$tmp/defines.sed"' "$ac_in >$ac_out" >>$CONFIG_STATUS - ac_in=$ac_out; ac_out=$ac_nxt; ac_nxt=$ac_in - sed 1,${ac_max_sed_lines}d conftest.defines >conftest.tail - grep . conftest.tail >/dev/null || break - rm -f conftest.defines - mv conftest.tail conftest.defines -done -rm -f conftest.defines conftest.tail - -echo "ac_result=$ac_in" >>$CONFIG_STATUS -cat >>$CONFIG_STATUS <<\_ACEOF if test x"$ac_file" != x-; then - echo "/* $configure_input */" >"$tmp/config.h" - cat "$ac_result" >>"$tmp/config.h" - if diff $ac_file "$tmp/config.h" >/dev/null 2>&1; then - { echo "$as_me:$LINENO: $ac_file is unchanged" >&5 -echo "$as_me: $ac_file is unchanged" >&6;} + { + $as_echo "/* $configure_input */" \ + && eval '$AWK -f "$tmp/defines.awk"' "$ac_file_inputs" + } >"$tmp/config.h" \ + || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5 +$as_echo "$as_me: error: could not create $ac_file" >&2;} + { (exit 1); exit 1; }; } + if diff "$ac_file" "$tmp/config.h" >/dev/null 2>&1; then + { $as_echo "$as_me:$LINENO: $ac_file is unchanged" >&5 +$as_echo "$as_me: $ac_file is unchanged" >&6;} else - rm -f $ac_file - mv "$tmp/config.h" $ac_file + rm -f "$ac_file" + mv "$tmp/config.h" "$ac_file" \ + || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5 +$as_echo "$as_me: error: could not create $ac_file" >&2;} + { (exit 1); exit 1; }; } fi else - echo "/* $configure_input */" - cat "$ac_result" + $as_echo "/* $configure_input */" \ + && eval '$AWK -f "$tmp/defines.awk"' "$ac_file_inputs" \ + || { { $as_echo "$as_me:$LINENO: error: could not create -" >&5 +$as_echo "$as_me: error: could not create -" >&2;} + { (exit 1); exit 1; }; } fi - rm -f "$tmp/out12" -# Compute $ac_file's index in $config_headers. -_am_arg=$ac_file +# Compute "$ac_file"'s index in $config_headers. +_am_arg="$ac_file" _am_stamp_count=1 for _am_header in $config_headers :; do case $_am_header in @@ -21730,7 +23523,7 @@ $as_expr X"$_am_arg" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ X"$_am_arg" : 'X\(//\)[^/]' \| \ X"$_am_arg" : 'X\(//\)$' \| \ X"$_am_arg" : 'X\(/\)' \| . 2>/dev/null || -echo X"$_am_arg" | +$as_echo X"$_am_arg" | sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/ q @@ -21750,30 +23543,40 @@ echo X"$_am_arg" | s/.*/./; q'`/stamp-h$_am_stamp_count ;; - :C) { echo "$as_me:$LINENO: executing $ac_file commands" >&5 -echo "$as_me: executing $ac_file commands" >&6;} + :C) { $as_echo "$as_me:$LINENO: executing $ac_file commands" >&5 +$as_echo "$as_me: executing $ac_file commands" >&6;} ;; esac case $ac_file$ac_mode in - "depfiles":C) test x"$AMDEP_TRUE" != x"" || for mf in $CONFIG_FILES; do - # Strip MF so we end up with the name of the file. - mf=`echo "$mf" | sed -e 's/:.*$//'` - # Check whether this is an Automake generated Makefile or not. - # We used to match only the files named `Makefile.in', but - # some people rename them; so instead we look at the file content. - # Grep'ing the first line is not enough: some people post-process - # each Makefile.in and add a new line on top of each file to say so. - # Grep'ing the whole file is not good either: AIX grep has a line - # limit of 2048, but all sed's we know have understand at least 4000. - if sed -n 's,^#.*generated by automake.*,X,p' "$mf" | grep X >/dev/null 2>&1; then - dirpart=`$as_dirname -- "$mf" || + "depfiles":C) test x"$AMDEP_TRUE" != x"" || { + # Autoconf 2.62 quotes --file arguments for eval, but not when files + # are listed without --file. Let's play safe and only enable the eval + # if we detect the quoting. + case $CONFIG_FILES in + *\'*) eval set x "$CONFIG_FILES" ;; + *) set x $CONFIG_FILES ;; + esac + shift + for mf + do + # Strip MF so we end up with the name of the file. + mf=`echo "$mf" | sed -e 's/:.*$//'` + # Check whether this is an Automake generated Makefile or not. + # We used to match only the files named `Makefile.in', but + # some people rename them; so instead we look at the file content. + # Grep'ing the first line is not enough: some people post-process + # each Makefile.in and add a new line on top of each file to say so. + # Grep'ing the whole file is not good either: AIX grep has a line + # limit of 2048, but all sed's we know have understand at least 4000. + if sed -n 's,^#.*generated by automake.*,X,p' "$mf" | grep X >/dev/null 2>&1; then + dirpart=`$as_dirname -- "$mf" || $as_expr X"$mf" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ X"$mf" : 'X\(//\)[^/]' \| \ X"$mf" : 'X\(//\)$' \| \ X"$mf" : 'X\(/\)' \| . 2>/dev/null || -echo X"$mf" | +$as_echo X"$mf" | sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/ q @@ -21791,33 +23594,33 @@ echo X"$mf" | q } s/.*/./; q'` - else - continue - fi - # Extract the definition of DEPDIR, am__include, and am__quote - # from the Makefile without running `make'. - DEPDIR=`sed -n 's/^DEPDIR = //p' < "$mf"` - test -z "$DEPDIR" && continue - am__include=`sed -n 's/^am__include = //p' < "$mf"` - test -z "am__include" && continue - am__quote=`sed -n 's/^am__quote = //p' < "$mf"` - # When using ansi2knr, U may be empty or an underscore; expand it - U=`sed -n 's/^U = //p' < "$mf"` - # Find all dependency output files, they are included files with - # $(DEPDIR) in their names. We invoke sed twice because it is the - # simplest approach to changing $(DEPDIR) to its actual value in the - # expansion. - for file in `sed -n " - s/^$am__include $am__quote\(.*(DEPDIR).*\)$am__quote"'$/\1/p' <"$mf" | \ - sed -e 's/\$(DEPDIR)/'"$DEPDIR"'/g' -e 's/\$U/'"$U"'/g'`; do - # Make sure the directory exists. - test -f "$dirpart/$file" && continue - fdir=`$as_dirname -- "$file" || + else + continue + fi + # Extract the definition of DEPDIR, am__include, and am__quote + # from the Makefile without running `make'. + DEPDIR=`sed -n 's/^DEPDIR = //p' < "$mf"` + test -z "$DEPDIR" && continue + am__include=`sed -n 's/^am__include = //p' < "$mf"` + test -z "am__include" && continue + am__quote=`sed -n 's/^am__quote = //p' < "$mf"` + # When using ansi2knr, U may be empty or an underscore; expand it + U=`sed -n 's/^U = //p' < "$mf"` + # Find all dependency output files, they are included files with + # $(DEPDIR) in their names. We invoke sed twice because it is the + # simplest approach to changing $(DEPDIR) to its actual value in the + # expansion. + for file in `sed -n " + s/^$am__include $am__quote\(.*(DEPDIR).*\)$am__quote"'$/\1/p' <"$mf" | \ + sed -e 's/\$(DEPDIR)/'"$DEPDIR"'/g' -e 's/\$U/'"$U"'/g'`; do + # Make sure the directory exists. + test -f "$dirpart/$file" && continue + fdir=`$as_dirname -- "$file" || $as_expr X"$file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ X"$file" : 'X\(//\)[^/]' \| \ X"$file" : 'X\(//\)$' \| \ X"$file" : 'X\(/\)' \| . 2>/dev/null || -echo X"$file" | +$as_echo X"$file" | sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/ q @@ -21835,7 +23638,7 @@ echo X"$file" | q } s/.*/./; q'` - { as_dir=$dirpart/$fdir + { as_dir=$dirpart/$fdir case $as_dir in #( -*) as_dir=./$as_dir;; esac @@ -21843,7 +23646,7 @@ echo X"$file" | as_dirs= while :; do case $as_dir in #( - *\'*) as_qdir=`echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #( + *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'( *) as_qdir=$as_dir;; esac as_dirs="'$as_qdir' $as_dirs" @@ -21852,7 +23655,7 @@ $as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ X"$as_dir" : 'X\(//\)[^/]' \| \ X"$as_dir" : 'X\(//\)$' \| \ X"$as_dir" : 'X\(/\)' \| . 2>/dev/null || -echo X"$as_dir" | +$as_echo X"$as_dir" | sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/ q @@ -21873,13 +23676,14 @@ echo X"$as_dir" | test -d "$as_dir" && break done test -z "$as_dirs" || eval "mkdir $as_dirs" - } || test -d "$as_dir" || { { echo "$as_me:$LINENO: error: cannot create directory $as_dir" >&5 -echo "$as_me: error: cannot create directory $as_dir" >&2;} + } || test -d "$as_dir" || { { $as_echo "$as_me:$LINENO: error: cannot create directory $as_dir" >&5 +$as_echo "$as_me: error: cannot create directory $as_dir" >&2;} { (exit 1); exit 1; }; }; } - # echo "creating $dirpart/$file" - echo '# dummy' > "$dirpart/$file" + # echo "creating $dirpart/$file" + echo '# dummy' > "$dirpart/$file" + done done -done +} ;; "default-1":C) for ac_file in $CONFIG_FILES; do # Support "outfile[:infile[:infile...]]" @@ -21920,6 +23724,11 @@ _ACEOF chmod +x $CONFIG_STATUS ac_clean_files=$ac_clean_files_save +test $ac_write_fail = 0 || + { { $as_echo "$as_me:$LINENO: error: write failure creating $CONFIG_STATUS" >&5 +$as_echo "$as_me: error: write failure creating $CONFIG_STATUS" >&2;} + { (exit 1); exit 1; }; } + # configure is writing to config.log, and then calls config.status. # config.status does its own redirection, appending to config.log. @@ -21941,4 +23750,8 @@ if test "$no_create" != yes; then # would make configure fail if this is the last instruction. $ac_cs_success || { (exit 1); exit 1; } fi +if test -n "$ac_unrecognized_opts" && test "$enable_option_checking" != no; then + { $as_echo "$as_me:$LINENO: WARNING: unrecognized options: $ac_unrecognized_opts" >&5 +$as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2;} +fi diff --git a/configure.ac b/configure.ac index 80566d0..9f180b9 100644 --- a/configure.ac +++ b/configure.ac @@ -343,7 +343,8 @@ AC_CHECK_TYPE(ssize_t, int) AC_CHECK_FUNCS(fgetpos memmove setegid srand48 strerror) -AC_REPLACE_FUNCS([setenv strcasecmp strdup strsep strtok_r]) +AC_REPLACE_FUNCS([setenv strcasecmp strdup strsep strtok_r wcscasecmp]) +AC_REPLACE_FUNCS([strcasestr mkdtemp]) AC_CHECK_FUNC(getopt) if test $ac_cv_func_getopt = yes; then @@ -648,7 +649,7 @@ AM_CONDITIONAL(USE_GSS, test x$need_gss = xyes) dnl -- end imap dependencies -- -AC_ARG_WITH(ssl, AC_HELP_STRING([--with-ssl@<:@=PFX@:>@], [Compile in SSL support for POP/IMAP/SMTP using OpenSSL]), +AC_ARG_WITH(ssl, AC_HELP_STRING([--with-ssl@<:@=PFX@:>@], [Enable TLS support using OpenSSL]), [ if test "$with_ssl" != "no" then if test "$need_socket" != "yes"; then @@ -681,7 +682,7 @@ AC_ARG_WITH(ssl, AC_HELP_STRING([--with-ssl@<:@=PFX@:>@], [Compile in SSL suppor fi ]) -AC_ARG_WITH([gnutls], AC_HELP_STRING([--with-gnutls@<:@=PFX@:>@], [Compile in SSL support for POP/IMAP/SMTP using gnutls]), +AC_ARG_WITH([gnutls], AC_HELP_STRING([--with-gnutls@<:@=PFX@:>@], [enable TLS support using gnutls]), [gnutls_prefix="$withval"], [gnutls_prefix="no"]) if test "$gnutls_prefix" != "no" && test x"$need_ssl" != xyes then @@ -689,21 +690,30 @@ then then AC_MSG_WARN([SSL support is only useful with POP, IMAP or SMTP support]) else - MUTT_AM_PATH_GNUTLS([$gnutls_prefix], + if test "$gnutls_prefix" != "yes" + then + LDFLAGS="$LDFLAGS -L$gnutls_prefix/lib" + CPPFLAGS="$CPPFLAGS -I$gnutls_prefix/include" + fi + saved_LIBS="$LIBS" + + AC_CHECK_LIB(gnutls, gnutls_check_version, [dnl GNUTLS found - CPPFLAGS="$CPPFLAGS $LIBGNUTLS_CFLAGS" - MUTTLIBS="$MUTTLIBS $LIBGNUTLS_LIBS" + AC_CHECK_DECLS([GNUTLS_VERIFY_DISABLE_TIME_CHECKS], [], [], + [[#include ]]) - AC_DEFINE(USE_SSL,1,[ Define if you want support for SSL. ]) - AC_DEFINE(USE_SSL_GNUTLS,1,[ Define if you want support for SSL via GNUTLS. ]) + LIBS="$saved_LIBS" + MUTTLIBS="$MUTTLIBS -lgnutls" + + AC_DEFINE(USE_SSL, 1, [ Define if you want support for SSL. ]) + AC_DEFINE(USE_SSL_GNUTLS, 1, [ Define if you want support for SSL via GNUTLS. ]) MUTT_LIB_OBJECTS="$MUTT_LIB_OBJECTS mutt_ssl_gnutls.o" need_ssl=yes], - [dnl GNUTLS not found - AC_MSG_ERROR([could not find libgnutls]) - ]) + [AC_MSG_ERROR([could not find libgnutls])]) fi fi + AM_CONDITIONAL(USE_SSL, test x$need_ssl = xyes) AC_ARG_WITH(sasl, AC_HELP_STRING([--with-sasl@<:@=PFX@:>@], [Use Cyrus SASL 2 network security library]), diff --git a/contrib/Makefile.in b/contrib/Makefile.in index 6720f5b..d985a5c 100644 --- a/contrib/Makefile.in +++ b/contrib/Makefile.in @@ -1,8 +1,9 @@ -# Makefile.in generated by automake 1.10.1 from Makefile.am. +# Makefile.in generated by automake 1.11 from Makefile.am. # @configure_input@ # Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, -# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. +# 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, +# Inc. # This Makefile.in is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. @@ -17,8 +18,9 @@ # $Id$ VPATH = @srcdir@ pkgdatadir = $(datadir)/@PACKAGE@ -pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkglibexecdir = $(libexecdir)/@PACKAGE@ am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd install_sh_DATA = $(install_sh) -c -m 644 install_sh_PROGRAM = $(install_sh) -c @@ -40,14 +42,14 @@ am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \ $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \ $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \ $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \ - $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/libgnutls.m4 \ - $(top_srcdir)/m4/progtest.m4 $(top_srcdir)/m4/types.m4 \ - $(top_srcdir)/configure.ac + $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \ + $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ $(ACLOCAL_M4) mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs CONFIG_HEADER = $(top_builddir)/config.h CONFIG_CLEAN_FILES = +CONFIG_CLEAN_VPATH_FILES = SOURCES = DIST_SOURCES = DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) @@ -105,9 +107,6 @@ INTL_LIBTOOL_SUFFIX_PREFIX = @INTL_LIBTOOL_SUFFIX_PREFIX@ ISPELL = @ISPELL@ KRB5CFGPATH = @KRB5CFGPATH@ LDFLAGS = @LDFLAGS@ -LIBGNUTLS_CFLAGS = @LIBGNUTLS_CFLAGS@ -LIBGNUTLS_CONFIG = @LIBGNUTLS_CONFIG@ -LIBGNUTLS_LIBS = @LIBGNUTLS_LIBS@ LIBICONV = @LIBICONV@ LIBIMAP = @LIBIMAP@ LIBIMAPDEPS = @LIBIMAPDEPS@ @@ -193,6 +192,7 @@ sharedstatedir = @sharedstatedir@ srcdir = @srcdir@ sysconfdir = @sysconfdir@ target_alias = @target_alias@ +top_build_prefix = @top_build_prefix@ top_builddir = @top_builddir@ top_srcdir = @top_srcdir@ subdir = contrib @@ -215,14 +215,14 @@ $(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(am__configure_deps) @for dep in $?; do \ case '$(am__configure_deps)' in \ *$$dep*) \ - cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \ - && exit 0; \ + ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \ + && { if test -f $@; then exit 0; else break; fi; }; \ exit 1;; \ esac; \ done; \ - echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign contrib/Makefile'; \ - cd $(top_srcdir) && \ - $(AUTOMAKE) --foreign contrib/Makefile + echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu contrib/Makefile'; \ + $(am__cd) $(top_srcdir) && \ + $(AUTOMAKE) --gnu contrib/Makefile .PRECIOUS: Makefile Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status @case '$?' in \ @@ -240,6 +240,7 @@ $(top_srcdir)/configure: $(am__configure_deps) cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh $(ACLOCAL_M4): $(am__aclocal_m4_deps) cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(am__aclocal_m4_deps): tags: TAGS TAGS: @@ -263,13 +264,17 @@ distdir: $(DISTFILES) if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ if test -d $$d/$$file; then \ dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d "$(distdir)/$$file"; then \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ - cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \ + cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ fi; \ - cp -pR $$d/$$file $(distdir)$$dir || exit 1; \ + cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \ else \ - test -f $(distdir)/$$file \ - || cp -p $$d/$$file $(distdir)/$$file \ + test -f "$(distdir)/$$file" \ + || cp -p $$d/$$file "$(distdir)/$$file" \ || exit 1; \ fi; \ done @@ -300,6 +305,7 @@ clean-generic: distclean-generic: -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES) maintainer-clean-generic: @echo "This command is intended for maintainers to use" @@ -318,6 +324,8 @@ dvi-am: html: html-am +html-am: + info: info-am info-am: @@ -326,18 +334,28 @@ install-data-am: install-data-local install-dvi: install-dvi-am +install-dvi-am: + install-exec-am: install-html: install-html-am +install-html-am: + install-info: install-info-am +install-info-am: + install-man: install-pdf: install-pdf-am +install-pdf-am: + install-ps: install-ps-am +install-ps-am: + installcheck-am: maintainer-clean: maintainer-clean-am @@ -394,6 +412,7 @@ dist-hook: Makefile $(DISTFILES) ln $$file $(distdir)/iconv 2> /dev/null \ || cp -p $$file $(distdir)/iconv ; \ done + # Tell versions [3.59,3.63) of GNU make to not export all variables. # Otherwise a system limit (for SysV at least) may be exceeded. .NOEXPORT: diff --git a/copy.c b/copy.c index fa28320..9ddf411 100644 --- a/copy.c +++ b/copy.c @@ -287,7 +287,7 @@ mutt_copy_hdr (FILE *in, FILE *out, LOFF_T off_start, LOFF_T off_end, int flags, if (flags & (CH_DECODE|CH_PREFIX)) { if (mutt_write_one_header (out, 0, headers[x], - flags & CH_PREFIX ? prefix : 0, mutt_term_width (Wrap)) == -1) + flags & CH_PREFIX ? prefix : 0, mutt_term_width (Wrap), flags) == -1) { error = TRUE; break; @@ -633,12 +633,12 @@ _mutt_copy_message (FILE *fpout, FILE *fpin, HEADER *hdr, BODY *body, fseeko (fp, cur->offset, 0); if (mutt_copy_bytes (fp, fpout, cur->length) == -1) { - fclose (fp); + safe_fclose (&fp); mutt_free_body (&cur); return (-1); } mutt_free_body (&cur); - fclose (fp); + safe_fclose (&fp); } else { @@ -865,7 +865,7 @@ static void format_address_header (char **h, ADDRESS *a) static int address_header_decode (char **h) { char *s = *h; - int l; + int l, rp = 0; ADDRESS *a = NULL; @@ -876,6 +876,7 @@ static int address_header_decode (char **h) if (ascii_strncasecmp (s, "return-path:", 12) == 0) { l = 12; + rp = 1; break; } else if (ascii_strncasecmp (s, "reply-to:", 9) == 0) @@ -936,15 +937,20 @@ static int address_header_decode (char **h) mutt_addrlist_to_local (a); rfc2047_decode_adrlist (a); - - *h = safe_calloc (1, l + 2); - - strfcpy (*h, s, l + 1); - - format_address_header (h, a); + + /* angle brackets for return path are mandated by RfC5322, + * so leave Return-Path as-is */ + if (rp) + *h = safe_strdup (s); + else + { + *h = safe_calloc (1, l + 2); + strfcpy (*h, s, l + 1); + format_address_header (h, a); + } rfc822_free_address (&a); - + FREE (&s); return 1; } diff --git a/copy.h b/copy.h index 9aff9da..5f12a3c 100644 --- a/copy.h +++ b/copy.h @@ -52,6 +52,7 @@ #define CH_NOQFROM (1<<15) /* ignore ">From " line */ #define CH_UPDATE_IRT (1<<16) /* update In-Reply-To: */ #define CH_UPDATE_REFS (1<<17) /* update References: */ +#define CH_DISPLAY (1<<18) /* display result to user */ int mutt_copy_hdr (FILE *, FILE *, LOFF_T, LOFF_T, int, const char *); diff --git a/crypt-gpgme.c b/crypt-gpgme.c index 8aac3dd..2dc4f0a 100644 --- a/crypt-gpgme.c +++ b/crypt-gpgme.c @@ -440,12 +440,12 @@ static gpgme_data_t body_to_data_object (BODY *a, int convert) buf[0] = c; gpgme_data_write (data, buf, 1); } - fclose(fptmp); + safe_fclose (&fptmp); gpgme_data_seek (data, 0, SEEK_SET); } else { - fclose(fptmp); + safe_fclose (&fptmp); err = gpgme_data_new_from_file (&data, tempfile, 1); } unlink (tempfile); @@ -544,7 +544,7 @@ static char *data_object_to_tempfile (gpgme_data_t data, FILE **ret_fp) if (fwrite (buf, nread, 1, fp) != 1) { mutt_perror (tempfile); - fclose (fp); + safe_fclose (&fp); unlink (tempfile); return NULL; } @@ -553,12 +553,12 @@ static char *data_object_to_tempfile (gpgme_data_t data, FILE **ret_fp) if (ret_fp) rewind (fp); else - fclose (fp); + safe_fclose (&fp); if (nread == -1) { mutt_error (_("error reading data object: %s\n"), gpgme_strerror (err)); unlink (tempfile); - fclose (fp); + safe_fclose (&fp); return NULL; } if (ret_fp) @@ -1788,7 +1788,7 @@ int smime_gpgme_decrypt_mime (FILE *fpin, FILE **fpout, BODY *b, BODY **cur) b->type = saved_b_type; b->length = saved_b_length; b->offset = saved_b_offset; - fclose (tmpfp); + safe_fclose (&tmpfp); rewind (*fpout); if (*cur && !is_signed && !(*cur)->parts && mutt_is_application_smime (*cur)) { @@ -1824,7 +1824,7 @@ int smime_gpgme_decrypt_mime (FILE *fpin, FILE **fpout, BODY *b, BODY **cur) bb->length = ftello (s.fpout); bb->offset = 0; rewind (tmpfp); - fclose (*fpout); + safe_fclose (fpout); memset (&s, 0, sizeof (s)); s.fpin = tmpfp; @@ -1843,7 +1843,7 @@ int smime_gpgme_decrypt_mime (FILE *fpin, FILE **fpout, BODY *b, BODY **cur) bb->type = saved_b_type; bb->length = saved_b_length; bb->offset = saved_b_offset; - fclose (tmpfp); + safe_fclose (&tmpfp); rewind (*fpout); mutt_free_body (cur); *cur = tmp_b; @@ -1956,10 +1956,7 @@ static int pgp_gpgme_extract_keys (gpgme_data_t keydata, FILE** fp, int dryrun) err_fp: if (rc) - { - fclose (*fp); - *fp = NULL; - } + safe_fclose (fp); err_tmpdir: if (dryrun) mutt_rmtree (tmpdir); @@ -2068,7 +2065,7 @@ void pgp_gpgme_invoke_import (const char *fname) dprint (1, (debugfile, "error converting key file into data object\n")); return; } - fclose (in); + safe_fclose (&in); if (!pgp_gpgme_extract_keys (keydata, &out, 0)) { @@ -2076,7 +2073,7 @@ void pgp_gpgme_invoke_import (const char *fname) outlen = ftell (out); fseek (out, 0, SEEK_SET); mutt_copy_bytes (out, stdout, outlen); - fclose (out); + safe_fclose (&out); } else printf (_("Error extracting key data!\n")); @@ -2150,7 +2147,7 @@ static void copy_clearsigned (gpgme_data_t data, STATE *s, char *charset) } fgetconv_close (&fc); - fclose (fp); + safe_fclose (&fp); } @@ -2476,7 +2473,7 @@ int pgp_gpgme_encrypted_handler (BODY *a, STATE *s) mutt_free_body (&tattach); } - fclose (fpout); + safe_fclose (&fpout); mutt_unlink(tempfile); dprint (2, (debugfile, "Leaving pgp_encrypted handler\n")); @@ -2550,7 +2547,7 @@ int smime_gpgme_application_handler (BODY *a, STATE *s) mutt_free_body (&tattach); } - fclose (fpout); + safe_fclose (&fpout); mutt_unlink(tempfile); dprint (2, (debugfile, "Leaving smime_encrypted handler\n")); @@ -3506,7 +3503,7 @@ verify_key (crypt_key_t *key) leave: gpgme_key_release (k); gpgme_release (listctx); - fclose (fp); + safe_fclose (&fp); mutt_clear_error (); snprintf (cmd, sizeof (cmd), _("Key ID: 0x%s"), crypt_keyid (key)); mutt_do_pager (cmd, tempfile, 0, NULL); @@ -4240,7 +4237,7 @@ static char *find_keys (ADDRESS *to, ADDRESS *cc, ADDRESS *bcc, default: abort (); } - *last = rfc822_cpy_adr (p); + *last = rfc822_cpy_adr (p, 0); while (*last) last = &((*last)->next); } diff --git a/crypt.c b/crypt.c index eb2c3e0..60b594d 100644 --- a/crypt.c +++ b/crypt.c @@ -538,7 +538,7 @@ int crypt_write_signed(BODY *a, STATE *s, const char *tempfile) fputc (c, fp); } - fclose (fp); + safe_fclose (&fp); return 0; } @@ -613,7 +613,7 @@ void crypt_extract_keys_from_messages (HEADER * h) if (Context->hdrs[Context->v2r[i]]->security & ENCRYPT && !crypt_valid_passphrase (Context->hdrs[Context->v2r[i]]->security)) { - fclose (fpout); + safe_fclose (&fpout); break; } @@ -695,7 +695,7 @@ void crypt_extract_keys_from_messages (HEADER * h) } } - fclose (fpout); + safe_fclose (&fpout); if (isendwin()) mutt_any_key_to_continue (NULL); diff --git a/curs_lib.c b/curs_lib.c index b7ef169..2427e60 100644 --- a/curs_lib.c +++ b/curs_lib.c @@ -420,7 +420,6 @@ void mutt_progress_update (progress_t* progress, long pos, int percent) if (update) { - dprint (1, (debugfile, "Updating progress: %ld\n", pos)); if (progress->flags & M_PROGRESS_SIZE) { pos = pos / (progress->inc << 10) * (progress->inc << 10); @@ -428,7 +427,9 @@ void mutt_progress_update (progress_t* progress, long pos, int percent) } else snprintf (posstr, sizeof (posstr), "%ld", pos); - + + dprint (5, (debugfile, "updating progress: %s\n", posstr)); + progress->pos = pos; if (now) progress->timestamp = now; diff --git a/curs_main.c b/curs_main.c index 7f31bf9..b701d91 100644 --- a/curs_main.c +++ b/curs_main.c @@ -1,20 +1,20 @@ /* * Copyright (C) 1996-2000,2002 Michael R. Elkins - * + * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. - * + * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. - * + * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. - */ + */ #if HAVE_CONFIG_H # include "config.h" @@ -81,7 +81,7 @@ static const char *No_visible = N_("No visible messages."); mutt_error _(No_visible); \ break; \ } - + #define CHECK_READONLY if (Context->readonly) \ { \ @@ -272,7 +272,7 @@ static void update_index (MUTTMENU *menu, CONTEXT *ctx, int check, /* store pointers to the newly added messages */ HEADER **save_new = NULL; int j; - + /* take note of the current message */ if (oldcount) { @@ -281,7 +281,7 @@ static void update_index (MUTTMENU *menu, CONTEXT *ctx, int check, else oldcount = 0; /* invalid message number! */ } - + /* We are in a limited view. Check if the new message(s) satisfy * the limit criteria. If they do, set their virtual msgno so that * they will be visible in the limited view */ @@ -294,7 +294,7 @@ static void update_index (MUTTMENU *menu, CONTEXT *ctx, int check, ctx->vcount = 0; if (mutt_pattern_exec (ctx->limit_pattern, - M_MATCH_FULL_ADDRESS, + M_MATCH_FULL_ADDRESS, ctx, ctx->hdrs[j])) { assert (ctx->vcount < ctx->msgcount); @@ -307,7 +307,7 @@ static void update_index (MUTTMENU *menu, CONTEXT *ctx, int check, } #undef THIS_BODY } - + /* save the list of new messages */ if (oldcount && check != M_REOPENED && ((Sort & SORT_MASK) == SORT_THREADS)) @@ -316,7 +316,7 @@ static void update_index (MUTTMENU *menu, CONTEXT *ctx, int check, for (j = oldcount; j < ctx->msgcount; j++) save_new[j-oldcount] = ctx->hdrs[j]; } - + /* if the mailbox was reopened, need to rethread from scratch */ mutt_sort_headers (ctx, (check == M_REOPENED)); @@ -326,9 +326,9 @@ static void update_index (MUTTMENU *menu, CONTEXT *ctx, int check, if (check == M_REOPENED) { THREAD *h, *j; - + ctx->collapsed = 0; - + for (h = ctx->tree; h; h = h->next) { for (j = h; !j->message; j = j->child) @@ -342,7 +342,7 @@ static void update_index (MUTTMENU *menu, CONTEXT *ctx, int check, for (j = 0; j < ctx->msgcount - oldcount; j++) { int k; - + for (k = 0; k < ctx->msgcount; k++) { HEADER *h = ctx->hdrs[k]; @@ -354,7 +354,7 @@ static void update_index (MUTTMENU *menu, CONTEXT *ctx, int check, mutt_set_virtual (ctx); } } - + menu->current = -1; if (oldcount) { @@ -368,10 +368,10 @@ static void update_index (MUTTMENU *menu, CONTEXT *ctx, int check, } } } - + if (menu->current < 0) menu->current = ci_first_message (); - + } static void resort_index (MUTTMENU *menu) @@ -391,13 +391,13 @@ static void resort_index (MUTTMENU *menu) break; } } - + if ((Sort & SORT_MASK) == SORT_THREADS && menu->current < 0) menu->current = mutt_parent_message (Context, current); - + if (menu->current < 0) menu->current = ci_first_message (); - + menu->redraw = REDRAW_INDEX | REDRAW_STATUS; } @@ -410,7 +410,7 @@ static struct mapping_t IndexHelp[] = { { N_("Reply"), OP_REPLY }, { N_("Group"), OP_GROUP_REPLY }, { N_("Help"), OP_HELP }, - { NULL } + { NULL, 0 } }; /* This function handles the message index window as well as commands returned @@ -432,7 +432,7 @@ int mutt_index_menu (void) int do_buffy_notify = 1; int close = 0; /* did we OP_QUIT or OP_EXIT out of this menu? */ int attach_msg = option(OPTATTACHMSG); - + menu = mutt_new_menu (MENU_MAIN); menu->offset = 1; menu->pagelen = LINES - 3; @@ -440,8 +440,8 @@ int mutt_index_menu (void) menu->color = index_color; menu->current = ci_first_message (); menu->help = mutt_compile_help (helpstr, sizeof (helpstr), MENU_MAIN, IndexHelp); - - if (!attach_msg) + + if (!attach_msg) mutt_buffy_check(1); /* force the buffy check after we enter the folder */ FOREVER @@ -452,7 +452,7 @@ int mutt_index_menu (void) * any 'op' below could do mutt_enter_command(), either here or * from any new menu launched, and change $sort/$sort_aux */ - if (option (OPTNEEDRESORT) && Context && Context->msgcount) + if (option (OPTNEEDRESORT) && Context && Context->msgcount && menu->current >= 0) resort_index (menu); menu->max = Context ? Context->vcount : 0; @@ -476,7 +476,7 @@ int mutt_index_menu (void) #ifdef USE_IMAP imap_allow_reopen (Context); #endif - + index_hint = (Context->vcount && menu->current >= 0 && menu->current < Context->vcount) ? CURHDR->index : 0; if ((check = mx_check_mailbox (Context, &index_hint, 0)) < 0) @@ -493,7 +493,7 @@ int mutt_index_menu (void) else if (check == M_NEW_MAIL || check == M_REOPENED || check == M_FLAGS) { update_index (menu, Context, check, oldcount, index_hint); - + /* notify the user of new mail */ if (check == M_REOPENED) mutt_error _("Mailbox was externally modified. Flags may be wrong."); @@ -507,10 +507,10 @@ int mutt_index_menu (void) /* avoid the message being overwritten by buffy */ do_buffy_notify = 0; - + menu->redraw = REDRAW_FULL; menu->max = Context->vcount; - + set_option (OPTSEARCHINVALID); } } @@ -556,7 +556,7 @@ int mutt_index_menu (void) menu_redraw_current (menu); } - if (menu->redraw & REDRAW_STATUS) + if (menu->redraw & REDRAW_STATUS) { menu_status_line (buf, sizeof (buf), menu, NONULL (Status)); CLEARLINE (option (OPTSTATUSONTOP) ? 0 : LINES-2); @@ -606,9 +606,9 @@ int mutt_index_menu (void) if (op == -1) continue; /* either user abort or timeout */ - + mutt_curs_set (1); - + /* special handling for the tag-prefix function */ if (op == OP_TAG_PREFIX) { @@ -682,7 +682,7 @@ int mutt_index_menu (void) menu->oldcurrent = menu->current; else menu->oldcurrent = -1; - + mutt_curs_set (1); /* fallback from the pager */ } @@ -750,13 +750,12 @@ int mutt_index_menu (void) || !buf[0]) break; - if (! isdigit ((unsigned char) buf[0])) + if (mutt_atoi (buf, &i) < 0) { mutt_error _("Argument must be a message number."); break; } - i = atoi (buf); if (i > 0 && i <= Context->msgcount) { for (j = i-1; j < Context->msgcount; j++) @@ -864,7 +863,7 @@ int mutt_index_menu (void) } if (Context->pattern) mutt_message _("To view all messages, limit to \"all\"."); - break; + break; case OP_QUIT: @@ -878,7 +877,7 @@ int mutt_index_menu (void) if (query_quadoption (OPT_QUIT, _("Quit Mutt?")) == M_YES) { int check; - + oldcount = Context ? Context->msgcount : 0; if (!Context || (check = mx_close_mailbox (Context, &index_hint)) == 0) @@ -993,7 +992,7 @@ int mutt_index_menu (void) imap_check_mailbox (Context, &index_hint, 1); break; #endif - + case OP_MAIN_SYNC_FOLDER: if (Context && !Context->msgcount) @@ -1005,28 +1004,36 @@ int mutt_index_menu (void) { int oldvcount = Context->vcount; int oldcount = Context->msgcount; - int dcount = 0; - int check; - - /* calculate the number of messages _above_ the cursor, - * so we can keep the cursor on the current message - */ - for (j = 0; j <= menu->current; j++) - { - if (Context->hdrs[Context->v2r[j]]->deleted) - dcount++; - } + int check, newidx; + HEADER *newhdr = NULL; + + /* threads may be reordered, so figure out what header the cursor + * should be on. #3092 */ + newidx = menu->current; + if (CURHDR->deleted) + newidx = ci_next_undeleted (menu->current); + if (newidx < 0) + newidx = ci_previous_undeleted (menu->current); + if (newidx >= 0) + newhdr = Context->hdrs[Context->v2r[newidx]]; if ((check = mx_sync_mailbox (Context, &index_hint)) == 0) { - if (Context->vcount != oldvcount) - menu->current -= dcount; + if (newhdr && Context->vcount != oldvcount) + for (j = 0; j < Context->vcount; j++) + { + if (Context->hdrs[Context->v2r[j]] == newhdr) + { + menu->current = j; + break; + } + } set_option (OPTSEARCHINVALID); } else if (check == M_NEW_MAIL || check == M_REOPENED) update_index (menu, Context, check, oldcount, index_hint); - /* + /* * do a sanity check even if mx_sync_mailbox failed. */ @@ -1050,7 +1057,7 @@ int mutt_index_menu (void) case OP_MAIN_CHANGE_FOLDER: case OP_MAIN_NEXT_UNREAD_MAILBOX: - + if (attach_msg) op = OP_MAIN_CHANGE_FOLDER_READONLY; @@ -1115,7 +1122,7 @@ int mutt_index_menu (void) { if (check == M_NEW_MAIL || check == M_REOPENED) update_index (menu, Context, check, oldcount, index_hint); - + set_option (OPTSEARCHINVALID); menu->redraw = REDRAW_INDEX | REDRAW_STATUS; break; @@ -1124,7 +1131,7 @@ int mutt_index_menu (void) } mutt_sleep (0); - + /* Set CurrentMenu to MENU_MAIN before executing any folder * hooks so that all the index menu functions are available to * the exec command. @@ -1133,7 +1140,7 @@ int mutt_index_menu (void) CurrentMenu = MENU_MAIN; mutt_folder_hook (buf); - if ((Context = mx_open_mailbox (buf, + if ((Context = mx_open_mailbox (buf, (option (OPTREADONLY) || op == OP_MAIN_CHANGE_FOLDER_READONLY) ? M_READONLY : 0, NULL)) != NULL) { @@ -1170,8 +1177,8 @@ int mutt_index_menu (void) if (option (OPTUNCOLLAPSEJUMP)) menu->current = mutt_thread_next_unread (Context, CURHDR); } - - if (option (OPTPGPAUTODEC) && (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED))) + + if (option (OPTPGPAUTODEC) && (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED))) mutt_check_traditional_pgp (tag ? NULL : CURHDR, &menu->redraw); if ((op = mutt_display_message (CURHDR)) == -1) { @@ -1193,7 +1200,7 @@ int mutt_index_menu (void) } if ((menu->menu == MENU_MAIN) - && (query_quadoption (OPT_QUIT, + && (query_quadoption (OPT_QUIT, _("Exit Mutt without saving?")) == M_YES)) { if (Context) @@ -1250,7 +1257,7 @@ int mutt_index_menu (void) mutt_error _("No Message-ID: header available to link thread"); else if (!tag && (!Context->last_tag || !Context->last_tag->tagged)) mutt_error _("First, please tag a message to be linked here"); - else + else { HEADER *oldcur = CURHDR; @@ -1259,7 +1266,7 @@ int mutt_index_menu (void) { mutt_sort_headers (Context, 1); menu->current = oldcur->virtual; - + Context->changed = 1; mutt_message _("Threads linked"); } @@ -1384,7 +1391,7 @@ int mutt_index_menu (void) case OP_DECRYPT_COPY: case OP_DECRYPT_SAVE: if (!WithCrypto) - break; + break; /* fall thru */ case OP_COPY_MESSAGE: case OP_SAVE: @@ -1429,7 +1436,7 @@ int mutt_index_menu (void) { int first_unread = -1; int first_new = -1; - + CHECK_MSGCOUNT; CHECK_VISIBLE; @@ -1437,7 +1444,7 @@ int mutt_index_menu (void) menu->current = -1; for (j = 0; j != Context->vcount; j++) { -#define CURHDRi Context->hdrs[Context->v2r[i]] +#define CURHDRi Context->hdrs[Context->v2r[i]] if (op == OP_MAIN_NEXT_NEW || op == OP_MAIN_NEXT_UNREAD || op == OP_MAIN_NEXT_NEW_THEN_UNREAD) { i++; @@ -1471,7 +1478,7 @@ int mutt_index_menu (void) if ((!CURHDRi->old) && first_new == -1) first_new = i; } - + if ((op == OP_MAIN_NEXT_UNREAD || op == OP_MAIN_PREV_UNREAD) && first_unread != -1) break; @@ -1482,7 +1489,7 @@ int mutt_index_menu (void) } #undef CURHDRi if ((op == OP_MAIN_NEXT_NEW || op == OP_MAIN_PREV_NEW || - op == OP_MAIN_NEXT_NEW_THEN_UNREAD || op == OP_MAIN_PREV_NEW_THEN_UNREAD) + op == OP_MAIN_NEXT_NEW_THEN_UNREAD || op == OP_MAIN_PREV_NEW_THEN_UNREAD) && first_new != -1) menu->current = first_new; else if ((op == OP_MAIN_NEXT_UNREAD || op == OP_MAIN_PREV_UNREAD || @@ -1610,7 +1617,7 @@ int mutt_index_menu (void) case OP_MAIN_NEXT_SUBTHREAD: menu->current = mutt_next_subthread (CURHDR); break; - + case OP_MAIN_PREV_THREAD: menu->current = mutt_previous_thread (CURHDR); break; @@ -1692,7 +1699,7 @@ int mutt_index_menu (void) mutt_error _("Threading is not enabled."); break; } - + if (CURHDR->collapsed) { menu->current = mutt_uncollapse_thread (Context, CURHDR); @@ -1729,16 +1736,16 @@ int mutt_index_menu (void) HEADER *h, *base; THREAD *thread, *top; int final; - + if (CURHDR->collapsed) final = mutt_uncollapse_thread (Context, CURHDR); else if (option (OPTCOLLAPSEUNREAD) || !UNREAD (CURHDR)) final = mutt_collapse_thread (Context, CURHDR); else final = CURHDR->virtual; - + base = Context->hdrs[Context->v2r[final]]; - + top = Context->tree; Context->collapsed = !Context->collapsed; while ((thread = top) != NULL) @@ -1756,7 +1763,7 @@ int mutt_index_menu (void) } top = top->next; } - + mutt_set_virtual (Context); for (j = 0; j < Context->vcount; j++) { @@ -1766,11 +1773,11 @@ int mutt_index_menu (void) break; } } - + menu->redraw = REDRAW_INDEX | REDRAW_STATUS; } break; - + /* -------------------------------------------------------------------- * These functions are invoked directly from the internal-pager */ @@ -1850,7 +1857,7 @@ int mutt_index_menu (void) if (rc != -1) { if (option (OPTDELETEUNTAG)) - mutt_thread_set_flag (CURHDR, M_TAG, 0, + mutt_thread_set_flag (CURHDR, M_TAG, 0, op == OP_DELETE_THREAD ? 0 : 1); if (option (OPTRESOLVE)) if ((menu->current = ci_next_undeleted (menu->current)) == -1) @@ -1885,7 +1892,7 @@ int mutt_index_menu (void) CHECK_ATTACH; CHECK_ACL(M_ACL_INSERT, _("edit message")); - if (option (OPTPGPAUTODEC) && (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED))) + if (option (OPTPGPAUTODEC) && (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED))) mutt_check_traditional_pgp (tag ? NULL : CURHDR, &menu->redraw); mutt_edit_message (Context, tag ? NULL : CURHDR); menu->redraw = REDRAW_FULL; @@ -1897,7 +1904,7 @@ int mutt_index_menu (void) CHECK_MSGCOUNT; CHECK_VISIBLE; CHECK_ATTACH; - if (option (OPTPGPAUTODEC) && (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED))) + if (option (OPTPGPAUTODEC) && (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED))) mutt_check_traditional_pgp (tag ? NULL : CURHDR, &menu->redraw); ci_send_message (SENDFORWARD, NULL, NULL, Context, tag ? NULL : CURHDR); menu->redraw = REDRAW_FULL; @@ -1913,7 +1920,7 @@ int mutt_index_menu (void) CHECK_MSGCOUNT; CHECK_VISIBLE; CHECK_ATTACH; - if (option (OPTPGPAUTODEC) && (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED))) + if (option (OPTPGPAUTODEC) && (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED))) mutt_check_traditional_pgp (tag ? NULL : CURHDR, &menu->redraw); ci_send_message (SENDREPLY|SENDGROUPREPLY, NULL, NULL, Context, tag ? NULL : CURHDR); menu->redraw = REDRAW_FULL; @@ -1924,7 +1931,7 @@ int mutt_index_menu (void) CHECK_ATTACH; CHECK_MSGCOUNT; CHECK_VISIBLE; - if (option (OPTPGPAUTODEC) && (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED))) + if (option (OPTPGPAUTODEC) && (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED))) mutt_check_traditional_pgp (tag ? NULL : CURHDR, &menu->redraw); ci_send_message (SENDREPLY|SENDLISTREPLY, NULL, NULL, Context, tag ? NULL : CURHDR); menu->redraw = REDRAW_FULL; @@ -1945,7 +1952,7 @@ int mutt_index_menu (void) menu->redraw = REDRAW_FULL; break; - + case OP_EXTRACT_KEYS: if (!WithCrypto) break; @@ -1959,11 +1966,11 @@ int mutt_index_menu (void) case OP_CHECK_TRADITIONAL: if (!(WithCrypto & APPLICATION_PGP)) break; - CHECK_MSGCOUNT; + CHECK_MSGCOUNT; CHECK_VISIBLE; - if (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED)) + if (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED)) mutt_check_traditional_pgp (tag ? NULL : CURHDR, &menu->redraw); - + if (menu->menu == MENU_PAGER) { op = OP_DISPLAY_MESSAGE; @@ -2023,7 +2030,7 @@ int mutt_index_menu (void) { if (option (OPTRESOLVE)) { - if ((menu->current = (op == OP_MAIN_READ_THREAD ? + if ((menu->current = (op == OP_MAIN_READ_THREAD ? mutt_next_thread (CURHDR) : mutt_next_subthread (CURHDR))) == -1) menu->current = menu->oldcurrent; } @@ -2039,11 +2046,11 @@ int mutt_index_menu (void) break; case OP_RESEND: - + CHECK_ATTACH; CHECK_MSGCOUNT; CHECK_VISIBLE; - + if (tag) { for (j = 0; j < Context->vcount; j++) @@ -2054,16 +2061,16 @@ int mutt_index_menu (void) } else mutt_resend_message (NULL, Context, CURHDR); - + menu->redraw = REDRAW_FULL; break; - + case OP_REPLY: CHECK_ATTACH; CHECK_MSGCOUNT; CHECK_VISIBLE; - if (option (OPTPGPAUTODEC) && (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED))) + if (option (OPTPGPAUTODEC) && (tag || !(CURHDR->security & PGP_TRADITIONAL_CHECKED))) mutt_check_traditional_pgp (tag ? NULL : CURHDR, &menu->redraw); ci_send_message (SENDREPLY, NULL, NULL, Context, tag ? NULL : CURHDR); menu->redraw = REDRAW_FULL; @@ -2082,7 +2089,7 @@ int mutt_index_menu (void) CHECK_VISIBLE; rc = mutt_thread_set_flag (CURHDR, M_TAG, !CURHDR->tagged, op == OP_TAG_THREAD ? 0 : 1); - + if (rc != -1) { if (option (OPTRESOLVE)) @@ -2105,7 +2112,7 @@ int mutt_index_menu (void) CHECK_VISIBLE; CHECK_READONLY; CHECK_ACL(M_ACL_DELETE, _("undelete message")); - + if (tag) { mutt_tag_set_flag (M_DELETE, 0); @@ -2203,7 +2210,7 @@ void mutt_set_header_color (CONTEXT *ctx, HEADER *curhdr) if (!curhdr) return; - + for (color = ColorIndexList; color; color = color->next) if (mutt_pattern_exec (color->color_pattern, M_MATCH_FULL_ADDRESS, ctx, curhdr)) { diff --git a/debian/stamp-patched b/debian/stamp-patched new file mode 100644 index 0000000..e69de29 diff --git a/doc/Makefile.am b/doc/Makefile.am index 2490b7d..1af0ee4 100644 --- a/doc/Makefile.am +++ b/doc/Makefile.am @@ -29,9 +29,11 @@ EXTRA_DIST = dotlock.man \ makedoc.c makedoc-defs.h \ mutt.css mutt.xsl html.xsl chunk.xsl $(BUILT_DISTFILES) -HTML_DOCFILES = manual.html index.html intro.html gettingstarted.html \ +CHUNKED_DOCFILES = index.html intro.html gettingstarted.html \ configuration.html mimesupport.html advancedusage.html \ - optionalfeatures.html tuning.html reference.html miscellany.html + optionalfeatures.html security.html tuning.html reference.html miscellany.html + +HTML_DOCFILES = manual.html $(CHUNKED_DOCFILES) BUILT_DISTFILES = stamp-doc-xml stamp-doc-chunked manual.txt $(HTML_DOCFILES) @@ -118,7 +120,7 @@ stamp-doc-chunked: $(srcdir)/chunk.xsl $(srcdir)/mutt.xsl stamp-doc-xml $(srcdir -xsltproc --nonet $(srcdir)/chunk.xsl manual.xml touch stamp-doc-chunked -$(HTML_DOCFILES): stamp-doc-chunked +$(CHUNKED_DOCFILES): stamp-doc-chunked manual.pdf: manual.tex -if test -f manual.tex; then pdfjadetex manual.tex; fi @@ -135,6 +137,12 @@ spellcheck: -aspell -l en --mode sgml -c manual.xml.head && \ -aspell -l en --mode nroff -c muttrc.man.head +sortcheck: manual.xml + sed -n -e '1,/^/d' -e '1,/^/s//\1/p' < manual.xml > vars.tmp.1 + sort < vars.tmp.1 > vars.tmp.2 + cmp -s vars.tmp.1 vars.tmp.2 || diff -u vars.tmp.1 vars.tmp.2 | less + rm -rf vars.tmp.1 vars.tmp.2 + clean-local: rm -f *~ *.html *.orig *.rej stamp-doc-* *.ps mutt.1 muttrc.man rm -f *.aux *.log *.tex *.out diff --git a/doc/Makefile.in b/doc/Makefile.in index b390b99..9a82f63 100644 --- a/doc/Makefile.in +++ b/doc/Makefile.in @@ -1,8 +1,9 @@ -# Makefile.in generated by automake 1.10.1 from Makefile.am. +# Makefile.in generated by automake 1.11 from Makefile.am. # @configure_input@ # Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, -# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. +# 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, +# Inc. # This Makefile.in is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. @@ -16,8 +17,9 @@ VPATH = @srcdir@ pkgdatadir = $(datadir)/@PACKAGE@ -pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkglibexecdir = $(libexecdir)/@PACKAGE@ am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd install_sh_DATA = $(install_sh) -c -m 644 install_sh_PROGRAM = $(install_sh) -c @@ -41,14 +43,14 @@ am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \ $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \ $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \ $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \ - $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/libgnutls.m4 \ - $(top_srcdir)/m4/progtest.m4 $(top_srcdir)/m4/types.m4 \ - $(top_srcdir)/configure.ac + $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \ + $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ $(ACLOCAL_M4) mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs CONFIG_HEADER = $(top_builddir)/config.h CONFIG_CLEAN_FILES = instdoc.sh +CONFIG_CLEAN_VPATH_FILES = PROGRAMS = $(noinst_PROGRAMS) makedoc_SOURCES = makedoc.c makedoc_OBJECTS = makedoc.$(OBJEXT) @@ -56,6 +58,7 @@ makedoc_LDADD = $(LDADD) DEFAULT_INCLUDES = -I.@am__isrc@ -I$(top_builddir) depcomp = $(SHELL) $(top_srcdir)/depcomp am__depfiles_maybe = depfiles +am__mv = mv -f COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \ $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) CCLD = $(CC) @@ -119,9 +122,6 @@ INTL_LIBTOOL_SUFFIX_PREFIX = @INTL_LIBTOOL_SUFFIX_PREFIX@ ISPELL = @ISPELL@ KRB5CFGPATH = @KRB5CFGPATH@ LDFLAGS = @LDFLAGS@ -LIBGNUTLS_CFLAGS = @LIBGNUTLS_CFLAGS@ -LIBGNUTLS_CONFIG = @LIBGNUTLS_CONFIG@ -LIBGNUTLS_LIBS = @LIBGNUTLS_LIBS@ LIBICONV = @LIBICONV@ LIBIMAP = @LIBIMAP@ LIBIMAPDEPS = @LIBIMAPDEPS@ @@ -207,6 +207,7 @@ sharedstatedir = @sharedstatedir@ srcdir = @srcdir@ sysconfdir = @sysconfdir@ target_alias = @target_alias@ +top_build_prefix = @top_build_prefix@ top_builddir = @top_builddir@ top_srcdir = @top_srcdir@ subdir = doc @@ -232,10 +233,11 @@ EXTRA_DIST = dotlock.man \ makedoc.c makedoc-defs.h \ mutt.css mutt.xsl html.xsl chunk.xsl $(BUILT_DISTFILES) -HTML_DOCFILES = manual.html index.html intro.html gettingstarted.html \ +CHUNKED_DOCFILES = index.html intro.html gettingstarted.html \ configuration.html mimesupport.html advancedusage.html \ - optionalfeatures.html tuning.html reference.html miscellany.html + optionalfeatures.html security.html tuning.html reference.html miscellany.html +HTML_DOCFILES = manual.html $(CHUNKED_DOCFILES) BUILT_DISTFILES = stamp-doc-xml stamp-doc-chunked manual.txt $(HTML_DOCFILES) srcdir_DOCFILES = PGP-Notes.txt applying-patches.txt \ devel-notes.txt patch-notes.txt smime-notes.txt @@ -258,14 +260,14 @@ $(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(am__configure_deps) @for dep in $?; do \ case '$(am__configure_deps)' in \ *$$dep*) \ - cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \ - && exit 0; \ + ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \ + && { if test -f $@; then exit 0; else break; fi; }; \ exit 1;; \ esac; \ done; \ - echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign doc/Makefile'; \ - cd $(top_srcdir) && \ - $(AUTOMAKE) --foreign doc/Makefile + echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu doc/Makefile'; \ + $(am__cd) $(top_srcdir) && \ + $(AUTOMAKE) --gnu doc/Makefile .PRECIOUS: Makefile Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status @case '$?' in \ @@ -283,6 +285,7 @@ $(top_srcdir)/configure: $(am__configure_deps) cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh $(ACLOCAL_M4): $(am__aclocal_m4_deps) cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(am__aclocal_m4_deps): instdoc.sh: $(top_builddir)/config.status $(srcdir)/instdoc.sh.in cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ @@ -302,14 +305,14 @@ distclean-compile: .c.o: @am__fastdepCC_TRUE@ $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $< -@am__fastdepCC_TRUE@ mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po +@am__fastdepCC_TRUE@ $(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po @AMDEP_TRUE@@am__fastdepCC_FALSE@ source='$<' object='$@' libtool=no @AMDEPBACKSLASH@ @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(COMPILE) -c $< .c.obj: @am__fastdepCC_TRUE@ $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ `$(CYGPATH_W) '$<'` -@am__fastdepCC_TRUE@ mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po +@am__fastdepCC_TRUE@ $(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po @AMDEP_TRUE@@am__fastdepCC_FALSE@ source='$<' object='$@' libtool=no @AMDEPBACKSLASH@ @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(COMPILE) -c `$(CYGPATH_W) '$<'` @@ -319,14 +322,14 @@ ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES) unique=`for i in $$list; do \ if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ done | \ - $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \ + $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ END { if (nonempty) { for (i in files) print i; }; }'`; \ mkid -fID $$unique tags: TAGS TAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \ $(TAGS_FILES) $(LISP) - tags=; \ + set x; \ here=`pwd`; \ list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ unique=`for i in $$list; do \ @@ -334,29 +337,34 @@ TAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \ done | \ $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ END { if (nonempty) { for (i in files) print i; }; }'`; \ - if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \ + shift; \ + if test -z "$(ETAGS_ARGS)$$*$$unique"; then :; else \ test -n "$$unique" || unique=$$empty_fix; \ - $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ - $$tags $$unique; \ + if test $$# -gt 0; then \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + "$$@" $$unique; \ + else \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + $$unique; \ + fi; \ fi ctags: CTAGS CTAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \ $(TAGS_FILES) $(LISP) - tags=; \ list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ unique=`for i in $$list; do \ if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ done | \ $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ END { if (nonempty) { for (i in files) print i; }; }'`; \ - test -z "$(CTAGS_ARGS)$$tags$$unique" \ + test -z "$(CTAGS_ARGS)$$unique" \ || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \ - $$tags $$unique + $$unique GTAGS: here=`$(am__cd) $(top_builddir) && pwd` \ - && cd $(top_srcdir) \ - && gtags -i $(GTAGS_ARGS) $$here + && $(am__cd) $(top_srcdir) \ + && gtags -i $(GTAGS_ARGS) "$$here" distclean-tags: -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags @@ -377,13 +385,17 @@ distdir: $(DISTFILES) if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ if test -d $$d/$$file; then \ dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d "$(distdir)/$$file"; then \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ - cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \ + cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ fi; \ - cp -pR $$d/$$file $(distdir)$$dir || exit 1; \ + cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \ else \ - test -f $(distdir)/$$file \ - || cp -p $$d/$$file $(distdir)/$$file \ + test -f "$(distdir)/$$file" \ + || cp -p $$d/$$file "$(distdir)/$$file" \ || exit 1; \ fi; \ done @@ -411,6 +423,7 @@ clean-generic: distclean-generic: -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES) -test -z "$(DISTCLEANFILES)" || rm -f $(DISTCLEANFILES) maintainer-clean-generic: @@ -433,6 +446,8 @@ dvi-am: html: html-am +html-am: + info: info-am info-am: @@ -441,18 +456,28 @@ install-data-am: install-data-local install-dvi: install-dvi-am +install-dvi-am: + install-exec-am: install-html: install-html-am +install-html-am: + install-info: install-info-am +install-info-am: + install-man: install-pdf: install-pdf-am +install-pdf-am: + install-ps: install-ps-am +install-ps-am: + installcheck-am: maintainer-clean: maintainer-clean-am @@ -567,7 +592,7 @@ stamp-doc-chunked: $(srcdir)/chunk.xsl $(srcdir)/mutt.xsl stamp-doc-xml $(srcdir -xsltproc --nonet $(srcdir)/chunk.xsl manual.xml touch stamp-doc-chunked -$(HTML_DOCFILES): stamp-doc-chunked +$(CHUNKED_DOCFILES): stamp-doc-chunked manual.pdf: manual.tex -if test -f manual.tex; then pdfjadetex manual.tex; fi @@ -584,6 +609,12 @@ spellcheck: -aspell -l en --mode sgml -c manual.xml.head && \ -aspell -l en --mode nroff -c muttrc.man.head +sortcheck: manual.xml + sed -n -e '1,/^/d' -e '1,/^/s//\1/p' < manual.xml > vars.tmp.1 + sort < vars.tmp.1 > vars.tmp.2 + cmp -s vars.tmp.1 vars.tmp.2 || diff -u vars.tmp.1 vars.tmp.2 | less + rm -rf vars.tmp.1 vars.tmp.2 + clean-local: rm -f *~ *.html *.orig *.rej stamp-doc-* *.ps mutt.1 muttrc.man rm -f *.aux *.log *.tex *.out @@ -612,6 +643,7 @@ stamp-doc-xml: makedoc$(EXEEXT) $(top_srcdir)/init.h \ perl $(srcdir)/gen-map-doc $(srcdir)/manual.xml.tail $(top_srcdir)/OPS* \ ) > manual.xml touch stamp-doc-xml + # Tell versions [3.59,3.63) of GNU make to not export all variables. # Otherwise a system limit (for SysV at least) may be exceeded. .NOEXPORT: diff --git a/doc/Muttrc b/doc/Muttrc index d5606a8..40ac02c 100644 --- a/doc/Muttrc +++ b/doc/Muttrc @@ -268,7 +268,10 @@ attachments -I message/external-body # # # This variable is a colon-separated list of character encoding -# schemes for text file attachments. +# schemes for text file attachments. Mutt uses this setting to guess +# which encoding files being attached are encoded in to convert them to +# a proper character set given in $send_charset. +# # If unset, the value of $charset will be used instead. # For example, the following configuration would work for Japanese # text handling: @@ -349,6 +352,19 @@ attachments -I message/external-body # the section on $index_format. # # +# set auto_tag=no +# +# Name: auto_tag +# Type: boolean +# Default: no +# +# +# When set, functions in the index menu which affect a message +# will be applied to all tagged messages (if there are any). When +# unset, you must first use the function (bound to ``;'' +# by default) to make the next function apply to all tagged messages. +# +# # set autoedit=no # # Name: autoedit @@ -362,20 +378,11 @@ attachments -I message/external-body # message. The send-menu may still be accessed once you have finished # editing the body of your message. # -# Also see $fast_reply. -# +# Note: when this option is set, you cannot use send-hooks that depend +# on the recipients when composing a new (non-reply) message, as the initial +# list of recipients is empty. # -# set auto_tag=no -# -# Name: auto_tag -# Type: boolean -# Default: no -# -# -# When set, functions in the index menu which affect a message -# will be applied to all tagged messages (if there are any). When -# unset, you must first use the function (bound to ``;'' -# by default) to make the next function apply to all tagged messages. +# Also see $fast_reply. # # # set beep=yes @@ -438,24 +445,25 @@ attachments -I message/external-body # visual terminals don't permit making the cursor invisible. # # -# set check_mbox_size=no +# set certificate_file="~/.mutt_certificates" # -# Name: check_mbox_size -# Type: boolean -# Default: no +# Name: certificate_file +# Type: path +# Default: "~/.mutt_certificates" # # -# When this variable is set, mutt will use file size attribute instead of -# access time when checking for new mail in mbox and mmdf folders. +# This variable specifies the file where the certificates you trust +# are saved. When an unknown certificate is encountered, you are asked +# if you accept it or not. If you accept it, the certificate can also +# be saved in this file and further connections are automatically +# accepted. # -# This variable is unset by default and should only be enabled when -# new mail detection for these folder types is unreliable or doesn't work. +# You can also manually add CA certificates in this file. Any server +# certificate that is signed with one of these CA certificates is +# also automatically accepted. # -# Note that enabling this variable should happen before any ``mailboxes'' -# directives occur in configuration files regarding mbox or mmdf folders -# because mutt needs to determine the initial new mail status of such a -# mailbox by performing a fast mailbox scan when it is defined. -# Afterwards the new mail status is tracked by file size changes. +# Example: +# set certificate_file=~/.mutt/certificates # # # set charset="" @@ -475,6 +483,26 @@ attachments -I message/external-body # character set used correctly. # # +# set check_mbox_size=no +# +# Name: check_mbox_size +# Type: boolean +# Default: no +# +# +# When this variable is set, mutt will use file size attribute instead of +# access time when checking for new mail in mbox and mmdf folders. +# +# This variable is unset by default and should only be enabled when +# new mail detection for these folder types is unreliable or doesn't work. +# +# Note that enabling this variable should happen before any ``mailboxes'' +# directives occur in configuration files regarding mbox or mmdf folders +# because mutt needs to determine the initial new mail status of such a +# mailbox by performing a fast mailbox scan when it is defined. +# Afterwards the new mail status is tracked by file size changes. +# +# # set check_new=yes # # Name: check_new @@ -504,17 +532,6 @@ attachments -I message/external-body # unread messages. # # -# set uncollapse_jump=no -# -# Name: uncollapse_jump -# Type: boolean -# Default: no -# -# -# When set, Mutt will jump to the next unread message, if any, -# when the current thread is uncollapsed. -# -# # set compose_format="-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-" # # Name: compose_format @@ -610,30 +627,21 @@ attachments -I message/external-body # $save_name, $force_name and ``fcc-hook''. # # -# set crypt_use_gpgme=no -# -# Name: crypt_use_gpgme -# Type: boolean -# Default: no -# -# -# This variable controls the use of the GPGME-enabled crypto backends. -# If it is set and Mutt was built with gpgme support, the gpgme code for -# S/MIME and PGP will be used instead of the classic code. Note that -# you need to set this option in .muttrc; it won't have any effect when -# used interactively. -# -# -# set crypt_use_pka=no +# set crypt_autoencrypt=no # -# Name: crypt_use_pka +# Name: crypt_autoencrypt # Type: boolean # Default: no # # -# Controls whether mutt uses PKA -# (see http://www.g10code.de/docs/pka-intro.de.pdf) during signature -# verification (only supported by the GPGME backend). +# Setting this variable will cause Mutt to always attempt to PGP +# encrypt outgoing messages. This is probably only useful in +# connection to the ``send-hook'' command. It can be overridden +# by use of the pgp menu, when encryption is not required or +# signing is requested as well. If $smime_is_default is set, +# then OpenSSL is used instead to create S/MIME messages and +# settings can be overridden by use of the smime menu instead. +# (Crypto only) # # # set crypt_autopgp=yes @@ -649,6 +657,22 @@ attachments -I message/external-body # $crypt_autosign, $crypt_replysign and $smime_is_default. # # +# set crypt_autosign=no +# +# Name: crypt_autosign +# Type: boolean +# Default: no +# +# +# Setting this variable will cause Mutt to always attempt to +# cryptographically sign outgoing messages. This can be overridden +# by use of the pgp menu, when signing is not required or +# encryption is requested as well. If $smime_is_default is set, +# then OpenSSL is used instead to create S/MIME messages and settings can +# be overridden by use of the smime menu instead of the pgp menu. +# (Crypto only) +# +# # set crypt_autosmime=yes # # Name: crypt_autosmime @@ -662,6 +686,102 @@ attachments -I message/external-body # $crypt_autosign, $crypt_replysign and $smime_is_default. # # +# set crypt_replyencrypt=yes +# +# Name: crypt_replyencrypt +# Type: boolean +# Default: yes +# +# +# If set, automatically PGP or OpenSSL encrypt replies to messages which are +# encrypted. +# (Crypto only) +# +# +# set crypt_replysign=no +# +# Name: crypt_replysign +# Type: boolean +# Default: no +# +# +# If set, automatically PGP or OpenSSL sign replies to messages which are +# signed. +# +# Note: this does not work on messages that are encrypted +# and signed! +# (Crypto only) +# +# +# set crypt_replysignencrypted=no +# +# Name: crypt_replysignencrypted +# Type: boolean +# Default: no +# +# +# If set, automatically PGP or OpenSSL sign replies to messages +# which are encrypted. This makes sense in combination with +# $crypt_replyencrypt, because it allows you to sign all +# messages which are automatically encrypted. This works around +# the problem noted in $crypt_replysign, that mutt is not able +# to find out whether an encrypted message is also signed. +# (Crypto only) +# +# +# set crypt_timestamp=yes +# +# Name: crypt_timestamp +# Type: boolean +# Default: yes +# +# +# If set, mutt will include a time stamp in the lines surrounding +# PGP or S/MIME output, so spoofing such lines is more difficult. +# If you are using colors to mark these lines, and rely on these, +# you may unset this setting. +# (Crypto only) +# +# +# set crypt_use_gpgme=no +# +# Name: crypt_use_gpgme +# Type: boolean +# Default: no +# +# +# This variable controls the use of the GPGME-enabled crypto backends. +# If it is set and Mutt was built with gpgme support, the gpgme code for +# S/MIME and PGP will be used instead of the classic code. Note that +# you need to set this option in .muttrc; it won't have any effect when +# used interactively. +# +# +# set crypt_use_pka=no +# +# Name: crypt_use_pka +# Type: boolean +# Default: no +# +# +# Controls whether mutt uses PKA +# (see http://www.g10code.de/docs/pka-intro.de.pdf) during signature +# verification (only supported by the GPGME backend). +# +# +# set crypt_verify_sig=yes +# +# Name: crypt_verify_sig +# Type: quadoption +# Default: yes +# +# +# If ``yes'', always attempt to verify PGP or S/MIME signatures. +# If ``ask-*'', ask whether or not to verify the signature. +# If \Fi``no'', never attempt to verify cryptographic signatures. +# (Crypto only) +# +# # set date_format="!%a, %b %d, %Y at %I:%M:%S%p %Z" # # Name: date_format @@ -859,6 +979,17 @@ attachments -I message/external-body # misinterpreting the line as a mbox message separator). # # +# set entropy_file="" +# +# Name: entropy_file +# Type: path +# Default: "" +# +# +# The file which includes random data that is used to initialize SSL +# library functions. +# +# # set envelope_from_address="" # # Name: envelope_from_address @@ -898,7 +1029,7 @@ attachments -I message/external-body # set fcc_attach=yes # # Name: fcc_attach -# Type: boolean +# Type: quadoption # Default: yes # # @@ -946,7 +1077,9 @@ attachments -I message/external-body # its own set of printf(3)-like sequences: # %C current file number # %d date/time folder was last modified -# %f filename +# %f filename (``/'' is appended to directory names, +# ``@'' to symbolic links and ``*'' to executable +# files) # %F file permissions # %g group name (or numeric gid, if missing) # %l number of hard links @@ -1015,6 +1148,20 @@ attachments -I message/external-body # otherwise $mime_forward_decode is used instead. # # +# set forward_decrypt=yes +# +# Name: forward_decrypt +# Type: boolean +# Default: yes +# +# +# Controls the handling of encrypted messages when forwarding a message. +# When set, the outer layer of encryption is stripped off. This +# variable is only used if $mime_forward is set and +# $mime_forward_decode is unset. +# (PGP only) +# +# # set forward_edit=yes # # Name: forward_edit @@ -1077,7 +1224,7 @@ attachments -I message/external-body # If the GECOS field contains a string like ``lastname, firstname'' then you # should set it to ``.*''. # -# This can be useful if you see the following behavior: you address a e-mail +# This can be useful if you see the following behavior: you address an e-mail # to user ID ``stevef'' whose full name is ``Steve Franklin''. If mutt expands # ``stevef'' to ``"Franklin" stevef@foo.bar'' then you should set the $gecos_mask to # a regular expression that will match the whole name so mutt will expand @@ -1109,7 +1256,52 @@ attachments -I message/external-body # The $weed setting applies. # # -# set help=yes +# set header_cache="" +# +# Name: header_cache +# Type: path +# Default: "" +# +# +# This variable points to the header cache database. +# If pointing to a directory Mutt will contain a header cache +# database file per folder, if pointing to a file that file will +# be a single global header cache. By default it is unset so no header +# caching will be used. +# +# Header caching can greatly improve speed when opening POP, IMAP +# MH or Maildir folders, see ``caching'' for details. +# +# +# set header_cache_compress=yes +# +# Name: header_cache_compress +# Type: boolean +# Default: yes +# +# +# When mutt is compiled with qdbm or tokyocabinet as header cache backend, +# this option determines whether the database will be compressed. +# Compression results in database files roughly being one fifth +# of the usual diskspace, but the uncompression can result in a +# slower opening of cached folder(s) which in general is still +# much faster than opening non header cached folders. +# +# +# set header_cache_pagesize="16384" +# +# Name: header_cache_pagesize +# Type: string +# Default: "16384" +# +# +# When mutt is compiled with either gdbm or bdb4 as the header cache backend, +# this option changes the database page size. Too large or too small +# values can waste space, memory, or CPU time. The default should be more +# or less optimal for most use cases. +# +# +# set help=yes # # Name: help # Type: boolean @@ -1219,6 +1411,22 @@ attachments -I message/external-body # The file in which Mutt will save its history. # # +# set honor_disposition=no +# +# Name: honor_disposition +# Type: boolean +# Default: no +# +# +# When set, Mutt will not display attachments with a +# disposition of ``attachment'' inline even if it could +# render the part to plain text. These MIME parts can only +# be viewed from the attachment menu. +# +# If unset, Mutt will render all MIME parts it can +# properly transform to plain text. +# +# # set honor_followup_to=yes # # Name: honor_followup_to @@ -1412,7 +1620,7 @@ attachments -I message/external-body # # # Specifies the password for your IMAP account. If unset, Mutt will -# prompt you for your password when you invoke the function +# prompt you for your password when you invoke the function # or try to open an IMAP folder. # # Warning: you should only use this option when you are on a @@ -1537,13 +1745,12 @@ attachments -I message/external-body # message to which you are replying. You are strongly encouraged not to # change this value, as it tends to agitate the more fanatical netizens. # +# The value of this option is ignored if $text_flowed is set, too because +# the quoting mechanism is strictly defined for format=flowed. +# # This option is a format string, please see the description of # $index_format for supported printf(3)-style sequences. # -# Because for format=lowed style messages the quoting mechanism -# is strictly defined, this setting is ignored if $text_flowed is -# set. -# # # set index_format="%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s" # @@ -1698,23 +1905,6 @@ attachments -I message/external-body # DOING! # # -# set header_cache="" -# -# Name: header_cache -# Type: path -# Default: "" -# -# -# This variable points to the header cache database. -# If pointing to a directory Mutt will contain a header cache -# database file per folder, if pointing to a file that file will -# be a single global header cache. By default it is unset so no header -# caching will be used. -# -# Header caching can greatly improve speed when opening POP, IMAP -# MH or Maildir folders, see ``caching'' for details. -# -# # set maildir_header_cache_verify=yes # # Name: maildir_header_cache_verify @@ -1728,34 +1918,6 @@ attachments -I message/external-body # folders). # # -# set header_cache_pagesize="16384" -# -# Name: header_cache_pagesize -# Type: string -# Default: "16384" -# -# -# When mutt is compiled with either gdbm or bdb4 as the header cache backend, -# this option changes the database page size. Too large or too small -# values can waste space, memory, or CPU time. The default should be more -# or less optimal for most use cases. -# -# -# set header_cache_compress=yes -# -# Name: header_cache_compress -# Type: boolean -# Default: yes -# -# -# When mutt is compiled with qdbm or tokyocabinet as header cache backend, -# this option determines whether the database will be compressed. -# Compression results in database files roughly being one fifth -# of the usual diskspace, but the uncompression can result in a -# slower opening of cached folder(s) which in general is still -# much faster than opening non header cached folders. -# -# # set maildir_trash=no # # Name: maildir_trash @@ -1829,18 +1991,8 @@ attachments -I message/external-body # # # The default mailbox type used when creating new folders. May be any of -# ``mbox'', ``MMDF'', ``MH'' and ``Maildir''. -# -# -# set metoo=no -# -# Name: metoo -# Type: boolean -# Default: no -# -# -# If unset, Mutt will remove your address (see the ``alternates'' -# command) from the list of recipients when replying to a message. +# ``mbox'', ``MMDF'', ``MH'' and ``Maildir''. This is overriden by the +# -m command-line option. # # # set menu_context=0 @@ -1879,6 +2031,49 @@ attachments -I message/external-body # (useful for slow links to avoid many redraws). # # +# set message_cache_clean=no +# +# Name: message_cache_clean +# Type: boolean +# Default: no +# +# +# If set, mutt will clean out obsolete entries from the message cache when +# the mailbox is synchronized. You probably only want to set it +# every once in a while, since it can be a little slow +# (especially for large folders). +# +# +# set message_cachedir="" +# +# Name: message_cachedir +# Type: path +# Default: "" +# +# +# Set this to a directory and mutt will cache copies of messages from +# your IMAP and POP servers here. You are free to remove entries at any +# time. +# +# When setting this variable to a directory, mutt needs to fetch every +# remote message only once and can perform regular expression searches +# as fast as for local folders. +# +# Also see the $message_cache_clean variable. +# +# +# set message_format="%s" +# +# Name: message_format +# Type: string +# Default: "%s" +# +# +# This is the string displayed in the ``attachment'' menu for +# attachments of type message/rfc822. For a full listing of defined +# printf(3)-like sequences see the section on $index_format. +# +# # set meta_key=no # # Name: meta_key @@ -1895,6 +2090,17 @@ attachments -I message/external-body # ``x''. # # +# set metoo=no +# +# Name: metoo +# Type: boolean +# Default: no +# +# +# If unset, Mutt will remove your address (see the ``alternates'' +# command) from the list of recipients when replying to a message. +# +# # set mh_purge=no # # Name: mh_purge @@ -2023,49 +2229,6 @@ attachments -I message/external-body # a ``mbox-hook'' command. # # -# set message_cachedir="" -# -# Name: message_cachedir -# Type: path -# Default: "" -# -# -# Set this to a directory and mutt will cache copies of messages from -# your IMAP and POP servers here. You are free to remove entries at any -# time. -# -# When setting this variable to a directory, mutt needs to fetch every -# remote message only once and can perform regular expression searches -# as fast as for local folders. -# -# Also see the $message_cache_clean variable. -# -# -# set message_cache_clean=no -# -# Name: message_cache_clean -# Type: boolean -# Default: no -# -# -# If set, mutt will clean out obsolete entries from the message cache when -# the mailbox is synchronized. You probably only want to set it -# every once in a while, since it can be a little slow -# (especially for large folders). -# -# -# set message_format="%s" -# -# Name: message_format -# Type: string -# Default: "%s" -# -# -# This is the string displayed in the ``attachment'' menu for -# attachments of type message/rfc822. For a full listing of defined -# printf(3)-like sequences see the section on $index_format. -# -# # set narrow_tree=no # # Name: narrow_tree @@ -2121,6 +2284,10 @@ attachments -I message/external-body # default, Mutt will display the line after the last one on the screen # at the top of the next page (0 lines of context). # +# This variable also specifies the amount of context given for search +# results. If positive, this many lines will be given before a match, +# if 0, the match will be top-aligned. +# # # set pager_format="-%Z- %C/%m: %-20.20n %s%* -- (%P)" # @@ -2167,172 +2334,141 @@ attachments -I message/external-body # function. # # -# set crypt_autosign=no +# set pgp_auto_decode=no # -# Name: crypt_autosign +# Name: pgp_auto_decode # Type: boolean # Default: no # # -# Setting this variable will cause Mutt to always attempt to -# cryptographically sign outgoing messages. This can be overridden -# by use of the pgp menu, when signing is not required or -# encryption is requested as well. If $smime_is_default is set, -# then OpenSSL is used instead to create S/MIME messages and settings can -# be overridden by use of the smime menu instead of the pgp menu. -# (Crypto only) +# If set, mutt will automatically attempt to decrypt traditional PGP +# messages whenever the user performs an operation which ordinarily would +# result in the contents of the message being operated on. For example, +# if the user displays a pgp-traditional message which has not been manually +# checked with the function, mutt will automatically +# check the message for traditional pgp. # # -# set crypt_autoencrypt=no +# set pgp_autoinline=no # -# Name: crypt_autoencrypt +# Name: pgp_autoinline # Type: boolean # Default: no # # -# Setting this variable will cause Mutt to always attempt to PGP -# encrypt outgoing messages. This is probably only useful in -# connection to the ``send-hook'' command. It can be overridden -# by use of the pgp menu, when encryption is not required or -# signing is requested as well. If $smime_is_default is set, -# then OpenSSL is used instead to create S/MIME messages and -# settings can be overridden by use of the smime menu instead. -# (Crypto only) +# This option controls whether Mutt generates old-style inline +# (traditional) PGP encrypted or signed messages under certain +# circumstances. This can be overridden by use of the pgp menu, +# when inline is not required. # +# Note that Mutt might automatically use PGP/MIME for messages +# which consist of more than a single MIME part. Mutt can be +# configured to ask before sending PGP/MIME messages when inline +# (traditional) would not work. # -# set pgp_ignore_subkeys=yes -# -# Name: pgp_ignore_subkeys -# Type: boolean -# Default: yes +# Also see the $pgp_mime_auto variable. # +# Also note that using the old-style PGP message format is strongly +# deprecated. +# (PGP only) # -# Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, -# the principal key will inherit the subkeys' capabilities. Unset this -# if you want to play interesting key selection games. -# (PGP only) # -# -# set crypt_replyencrypt=yes +# set pgp_check_exit=yes # -# Name: crypt_replyencrypt +# Name: pgp_check_exit # Type: boolean # Default: yes # # -# If set, automatically PGP or OpenSSL encrypt replies to messages which are -# encrypted. -# (Crypto only) +# If set, mutt will check the exit code of the PGP subprocess when +# signing or encrypting. A non-zero exit code means that the +# subprocess failed. +# (PGP only) # # -# set crypt_replysign=no +# set pgp_clearsign_command="" # -# Name: crypt_replysign -# Type: boolean -# Default: no +# Name: pgp_clearsign_command +# Type: string +# Default: "" # # -# If set, automatically PGP or OpenSSL sign replies to messages which are -# signed. +# This format is used to create an old-style ``clearsigned'' PGP +# message. Note that the use of this format is strongly +# deprecated. # -# Note: this does not work on messages that are encrypted -# and signed! -# (Crypto only) +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) # # -# set crypt_replysignencrypted=no +# set pgp_decode_command="" # -# Name: crypt_replysignencrypted -# Type: boolean -# Default: no -# +# Name: pgp_decode_command +# Type: string +# Default: "" # -# If set, automatically PGP or OpenSSL sign replies to messages -# which are encrypted. This makes sense in combination with -# $crypt_replyencrypt, because it allows you to sign all -# messages which are automatically encrypted. This works around -# the problem noted in $crypt_replysign, that mutt is not able -# to find out whether an encrypted message is also signed. -# (Crypto only) # +# This format strings specifies a command which is used to decode +# application/pgp attachments. # -# set crypt_timestamp=yes -# -# Name: crypt_timestamp -# Type: boolean -# Default: yes +# The PGP command formats have their own set of printf(3)-like sequences: +# %p Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty +# string otherwise. Note: This may be used with a %? construct. +# %f Expands to the name of a file containing a message. +# %s Expands to the name of a file containing the signature part +# of a multipart/signed attachment when verifying it. +# %a The value of $pgp_sign_as. +# %r One or more key IDs. # # -# If set, mutt will include a time stamp in the lines surrounding -# PGP or S/MIME output, so spoofing such lines is more difficult. -# If you are using colors to mark these lines, and rely on these, -# you may unset this setting. -# (Crypto only) +# For examples on how to configure these formats for the various versions +# of PGP which are floating around, see the pgp and gpg sample configuration files in +# the samples/ subdirectory which has been installed on your system +# alongside the documentation. +# (PGP only) # # -# set pgp_use_gpg_agent=no +# set pgp_decrypt_command="" # -# Name: pgp_use_gpg_agent -# Type: boolean -# Default: no +# Name: pgp_decrypt_command +# Type: string +# Default: "" # # -# If set, mutt will use a possibly-running gpg-agent(1) process. +# This command is used to decrypt a PGP encrypted message. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. # (PGP only) # # -# set crypt_verify_sig=yes +# set pgp_encrypt_only_command="" # -# Name: crypt_verify_sig -# Type: quadoption -# Default: yes -# -# -# If ``yes'', always attempt to verify PGP or S/MIME signatures. -# If ``ask-*'', ask whether or not to verify the signature. -# If \Fi``no'', never attempt to verify cryptographic signatures. -# (Crypto only) -# +# Name: pgp_encrypt_only_command +# Type: string +# Default: "" # -# set smime_is_default=no -# -# Name: smime_is_default -# Type: boolean -# Default: no # +# This command is used to encrypt a body part without signing it. # -# The default behaviour of mutt is to use PGP on all auto-sign/encryption -# operations. To override and to use OpenSSL instead this must be set. -# However, this has no effect while replying, since mutt will automatically -# select the same application that was used to sign/encrypt the original -# message. (Note that this variable can be overridden by unsetting $crypt_autosmime.) -# (S/MIME only) +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) # # -# set smime_ask_cert_label=yes +# set pgp_encrypt_sign_command="" # -# Name: smime_ask_cert_label -# Type: boolean -# Default: yes -# -# -# This flag controls whether you want to be asked to enter a label -# for a certificate about to be added to the database or not. It is -# set by default. -# (S/MIME only) -# +# Name: pgp_encrypt_sign_command +# Type: string +# Default: "" # -# set smime_decrypt_use_default_key=yes -# -# Name: smime_decrypt_use_default_key -# Type: boolean -# Default: yes # +# This command is used to both sign and encrypt a body part. # -# If set (default) this tells mutt to use the default key for decryption. Otherwise, -# if managing multiple certificate-key-pairs, mutt will try to use the mailbox-address -# to determine the key to use. It will ask you to supply a key, if it can't find one. -# (S/MIME only) +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) # # # set pgp_entry_format="%4n %t%f %4l/0x%k %-4a %2c %u" @@ -2359,6 +2495,34 @@ attachments -I message/external-body # (PGP only) # # +# set pgp_export_command="" +# +# Name: pgp_export_command +# Type: string +# Default: "" +# +# +# This command is used to export a public key from the user's +# key ring. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) +# +# +# set pgp_getkeys_command="" +# +# Name: pgp_getkeys_command +# Type: string +# Default: "" +# +# +# This command is invoked whenever mutt will need public key information. +# Of the sequences supported by $pgp_decode_command, %r is the only +# printf(3)-like sequence used with this format. +# (PGP only) +# +# # set pgp_good_sign="" # # Name: pgp_good_sign @@ -2373,83 +2537,112 @@ attachments -I message/external-body # (PGP only) # # -# set pgp_check_exit=yes +# set pgp_ignore_subkeys=yes # -# Name: pgp_check_exit +# Name: pgp_ignore_subkeys # Type: boolean # Default: yes # # -# If set, mutt will check the exit code of the PGP subprocess when -# signing or encrypting. A non-zero exit code means that the -# subprocess failed. +# Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, +# the principal key will inherit the subkeys' capabilities. Unset this +# if you want to play interesting key selection games. # (PGP only) # # -# set pgp_long_ids=no +# set pgp_import_command="" # -# Name: pgp_long_ids -# Type: boolean -# Default: no +# Name: pgp_import_command +# Type: string +# Default: "" # # -# If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs. +# This command is used to import a key from a message into +# the user's public key ring. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. # (PGP only) # # -# set pgp_retainable_sigs=no +# set pgp_list_pubring_command="" # -# Name: pgp_retainable_sigs -# Type: boolean -# Default: no +# Name: pgp_list_pubring_command +# Type: string +# Default: "" # # -# If set, signed and encrypted messages will consist of nested -# multipart/signed and multipart/encrypted body parts. +# This command is used to list the public key ring's contents. The +# output format must be analogous to the one used by +# gpg --list-keys --with-colons. # -# This is useful for applications like encrypted and signed mailing -# lists, where the outer layer (multipart/encrypted) can be easily -# removed, while the inner multipart/signed part is retained. +# This format is also generated by the pgpring utility which comes +# with mutt. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. # (PGP only) # # -# set pgp_autoinline=no +# set pgp_list_secring_command="" # -# Name: pgp_autoinline -# Type: boolean -# Default: no -# +# Name: pgp_list_secring_command +# Type: string +# Default: "" # -# This option controls whether Mutt generates old-style inline -# (traditional) PGP encrypted or signed messages under certain -# circumstances. This can be overridden by use of the pgp menu, -# when inline is not required. # -# Note that Mutt might automatically use PGP/MIME for messages -# which consist of more than a single MIME part. Mutt can be -# configured to ask before sending PGP/MIME messages when inline -# (traditional) would not work. +# This command is used to list the secret key ring's contents. The +# output format must be analogous to the one used by: +# gpg --list-keys --with-colons. # -# Also see the $pgp_mime_auto variable. +# This format is also generated by the pgpring utility which comes +# with mutt. # -# Also note that using the old-style PGP message format is strongly -# deprecated. +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. # (PGP only) # # -# set pgp_replyinline=no +# set pgp_long_ids=no # -# Name: pgp_replyinline +# Name: pgp_long_ids # Type: boolean # Default: no # # -# Setting this variable will cause Mutt to always attempt to -# create an inline (traditional) message when replying to a -# message which is PGP encrypted/signed inline. This can be -# overridden by use of the pgp menu, when inline is not -# required. This option does not automatically detect if the -# (replied-to) message is inline; instead it relies on Mutt +# If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs. +# (PGP only) +# +# +# set pgp_mime_auto=ask-yes +# +# Name: pgp_mime_auto +# Type: quadoption +# Default: ask-yes +# +# +# This option controls whether Mutt will prompt you for +# automatically sending a (signed/encrypted) message using +# PGP/MIME when inline (traditional) fails (for any reason). +# +# Also note that using the old-style PGP message format is strongly +# deprecated. +# (PGP only) +# +# +# set pgp_replyinline=no +# +# Name: pgp_replyinline +# Type: boolean +# Default: no +# +# +# Setting this variable will cause Mutt to always attempt to +# create an inline (traditional) message when replying to a +# message which is PGP encrypted/signed inline. This can be +# overridden by use of the pgp menu, when inline is not +# required. This option does not automatically detect if the +# (replied-to) message is inline; instead it relies on Mutt # internals for previously checked/flagged messages. # # Note that Mutt might automatically use PGP/MIME for messages @@ -2464,6 +2657,22 @@ attachments -I message/external-body # (PGP only) # # +# set pgp_retainable_sigs=no +# +# Name: pgp_retainable_sigs +# Type: boolean +# Default: no +# +# +# If set, signed and encrypted messages will consist of nested +# multipart/signed and multipart/encrypted body parts. +# +# This is useful for applications like encrypted and signed mailing +# lists, where the outer layer (multipart/encrypted) can be easily +# removed, while the inner multipart/signed part is retained. +# (PGP only) +# +# # set pgp_show_unusable=yes # # Name: pgp_show_unusable @@ -2490,29 +2699,18 @@ attachments -I message/external-body # (PGP only) # # -# set pgp_strict_enc=yes +# set pgp_sign_command="" # -# Name: pgp_strict_enc -# Type: boolean -# Default: yes -# -# -# If set, Mutt will automatically encode PGP/MIME signed messages as -# quoted-printable. Please note that unsetting this variable may -# lead to problems with non-verifyable PGP signatures, so only change -# this if you know what you are doing. -# (PGP only) -# +# Name: pgp_sign_command +# Type: string +# Default: "" # -# set pgp_timeout=300 -# -# Name: pgp_timeout -# Type: number -# Default: 300 # +# This command is used to create the detached PGP signature for a +# multipart/signed PGP/MIME body part. # -# The number of seconds after which a cached passphrase will expire if -# not used. +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. # (PGP only) # # @@ -2536,74 +2734,40 @@ attachments -I message/external-body # (PGP only) # # -# set pgp_mime_auto=ask-yes -# -# Name: pgp_mime_auto -# Type: quadoption -# Default: ask-yes -# -# -# This option controls whether Mutt will prompt you for -# automatically sending a (signed/encrypted) message using -# PGP/MIME when inline (traditional) fails (for any reason). -# -# Also note that using the old-style PGP message format is strongly -# deprecated. -# (PGP only) -# -# -# set pgp_auto_decode=no +# set pgp_strict_enc=yes # -# Name: pgp_auto_decode +# Name: pgp_strict_enc # Type: boolean -# Default: no +# Default: yes # # -# If set, mutt will automatically attempt to decrypt traditional PGP -# messages whenever the user performs an operation which ordinarily would -# result in the contents of the message being operated on. For example, -# if the user displays a pgp-traditional message which has not been manually -# checked with the function, mutt will automatically -# check the message for traditional pgp. +# If set, Mutt will automatically encode PGP/MIME signed messages as +# quoted-printable. Please note that unsetting this variable may +# lead to problems with non-verifyable PGP signatures, so only change +# this if you know what you are doing. +# (PGP only) # # -# set pgp_decode_command="" +# set pgp_timeout=300 # -# Name: pgp_decode_command -# Type: string -# Default: "" -# -# -# This format strings specifies a command which is used to decode -# application/pgp attachments. -# -# The PGP command formats have their own set of printf(3)-like sequences: -# %p Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty -# string otherwise. Note: This may be used with a %? construct. -# %f Expands to the name of a file containing a message. -# %s Expands to the name of a file containing the signature part -# of a multipart/signed attachment when verifying it. -# %a The value of $pgp_sign_as. -# %r One or more key IDs. +# Name: pgp_timeout +# Type: number +# Default: 300 # # -# For examples on how to configure these formats for the various versions -# of PGP which are floating around, see the pgp and gpg sample configuration files in -# the samples/ subdirectory which has been installed on your system -# alongside the documentation. +# The number of seconds after which a cached passphrase will expire if +# not used. # (PGP only) # # -# set pgp_getkeys_command="" +# set pgp_use_gpg_agent=no # -# Name: pgp_getkeys_command -# Type: string -# Default: "" +# Name: pgp_use_gpg_agent +# Type: boolean +# Default: no # # -# This command is invoked whenever mutt will need public key information. -# Of the sequences supported by $pgp_decode_command, %r is the only -# printf(3)-like sequence used with this format. +# If set, mutt will use a possibly-running gpg-agent(1) process. # (PGP only) # # @@ -2621,1404 +2785,1160 @@ attachments -I message/external-body # (PGP only) # # -# set pgp_decrypt_command="" +# set pgp_verify_key_command="" # -# Name: pgp_decrypt_command +# Name: pgp_verify_key_command # Type: string # Default: "" # # -# This command is used to decrypt a PGP encrypted message. +# This command is used to verify key information from the key selection +# menu. # # This is a format string, see the $pgp_decode_command command for # possible printf(3)-like sequences. # (PGP only) # # -# set pgp_clearsign_command="" +# set pipe_decode=no # -# Name: pgp_clearsign_command -# Type: string -# Default: "" -# +# Name: pipe_decode +# Type: boolean +# Default: no # -# This format is used to create a old-style ``clearsigned'' PGP -# message. Note that the use of this format is strongly -# deprecated. # -# This is a format string, see the $pgp_decode_command command for -# possible printf(3)-like sequences. -# (PGP only) +# Used in connection with the command. When unset, +# Mutt will pipe the messages without any preprocessing. When set, Mutt +# will weed headers and will attempt to decode the messages +# first. # # -# set pgp_sign_command="" +# set pipe_sep="\n" # -# Name: pgp_sign_command +# Name: pipe_sep # Type: string -# Default: "" -# +# Default: "\n" # -# This command is used to create the detached PGP signature for a -# multipart/signed PGP/MIME body part. # -# This is a format string, see the $pgp_decode_command command for -# possible printf(3)-like sequences. -# (PGP only) +# The separator to add between messages when piping a list of tagged +# messages to an external Unix command. # # -# set pgp_encrypt_sign_command="" +# set pipe_split=no # -# Name: pgp_encrypt_sign_command -# Type: string -# Default: "" -# +# Name: pipe_split +# Type: boolean +# Default: no # -# This command is used to both sign and encrypt a body part. # -# This is a format string, see the $pgp_decode_command command for -# possible printf(3)-like sequences. -# (PGP only) +# Used in connection with the function following +# . If this variable is unset, when piping a list of +# tagged messages Mutt will concatenate the messages and will pipe them +# all concatenated. When set, Mutt will pipe the messages one by one. +# In both cases the messages are piped in the current sorted order, +# and the $pipe_sep separator is added after each message. # # -# set pgp_encrypt_only_command="" +# set pop_auth_try_all=yes # -# Name: pgp_encrypt_only_command -# Type: string -# Default: "" -# +# Name: pop_auth_try_all +# Type: boolean +# Default: yes # -# This command is used to encrypt a body part without signing it. # -# This is a format string, see the $pgp_decode_command command for -# possible printf(3)-like sequences. -# (PGP only) +# If set, Mutt will try all available authentication methods. +# When unset, Mutt will only fall back to other authentication +# methods if the previous methods are unavailable. If a method is +# available but authentication fails, Mutt will not connect to the POP server. # # -# set pgp_import_command="" +# set pop_authenticators="" # -# Name: pgp_import_command +# Name: pop_authenticators # Type: string # Default: "" # # -# This command is used to import a key from a message into -# the user's public key ring. +# This is a colon-delimited list of authentication methods mutt may +# attempt to use to log in to an POP server, in the order mutt should +# try them. Authentication methods are either ``user'', ``apop'' or any +# SASL mechanism, eg ``digest-md5'', ``gssapi'' or ``cram-md5''. +# This option is case-insensitive. If this option is unset +# (the default) mutt will try all available methods, in order from +# most-secure to least-secure. # -# This is a format string, see the $pgp_decode_command command for -# possible printf(3)-like sequences. -# (PGP only) +# Example: +# set pop_authenticators="digest-md5:apop:user" # # -# set pgp_export_command="" +# set pop_checkinterval=60 # -# Name: pgp_export_command -# Type: string -# Default: "" +# Name: pop_checkinterval +# Type: number +# Default: 60 # # -# This command is used to export a public key from the user's -# key ring. +# This variable configures how often (in seconds) mutt should look for +# new mail in the currently selected mailbox if it is a POP mailbox. # -# This is a format string, see the $pgp_decode_command command for -# possible printf(3)-like sequences. -# (PGP only) # -# -# set pgp_verify_key_command="" +# set pop_delete=ask-no # -# Name: pgp_verify_key_command -# Type: string -# Default: "" -# +# Name: pop_delete +# Type: quadoption +# Default: ask-no # -# This command is used to verify key information from the key selection -# menu. # -# This is a format string, see the $pgp_decode_command command for -# possible printf(3)-like sequences. -# (PGP only) +# If set, Mutt will delete successfully downloaded messages from the POP +# server when using the function. When unset, Mutt will +# download messages but also leave them on the POP server. # # -# set pgp_list_secring_command="" +# set pop_host="" # -# Name: pgp_list_secring_command +# Name: pop_host # Type: string # Default: "" # # -# This command is used to list the secret key ring's contents. The -# output format must be analogous to the one used by: -# gpg --list-keys --with-colons. -# -# This format is also generated by the pgpring utility which comes -# with mutt. +# The name of your POP server for the function. You +# can also specify an alternative port, username and password, ie: +# [pop[s]://][username[:password]@]popserver[:port] # -# This is a format string, see the $pgp_decode_command command for -# possible printf(3)-like sequences. -# (PGP only) +# where ``[...]'' denotes an optional part. # # -# set pgp_list_pubring_command="" +# set pop_last=no # -# Name: pgp_list_pubring_command -# Type: string -# Default: "" -# -# -# This command is used to list the public key ring's contents. The -# output format must be analogous to the one used by -# gpg --list-keys --with-colons. +# Name: pop_last +# Type: boolean +# Default: no # -# This format is also generated by the pgpring utility which comes -# with mutt. # -# This is a format string, see the $pgp_decode_command command for -# possible printf(3)-like sequences. -# (PGP only) +# If this variable is set, mutt will try to use the ``LAST'' POP command +# for retrieving only unread messages from the POP server when using +# the function. # # -# set forward_decrypt=yes +# set pop_pass="" # -# Name: forward_decrypt -# Type: boolean -# Default: yes +# Name: pop_pass +# Type: string +# Default: "" # # -# Controls the handling of encrypted messages when forwarding a message. -# When set, the outer layer of encryption is stripped off. This -# variable is only used if $mime_forward is set and -# $mime_forward_decode is unset. -# (PGP only) +# Specifies the password for your POP account. If unset, Mutt will +# prompt you for your password when you open a POP mailbox. +# +# Warning: you should only use this option when you are on a +# fairly secure machine, because the superuser can read your muttrc +# even if you are the only one who can read the file. # # -# set smime_timeout=300 +# set pop_reconnect=ask-yes # -# Name: smime_timeout -# Type: number -# Default: 300 +# Name: pop_reconnect +# Type: quadoption +# Default: ask-yes # # -# The number of seconds after which a cached passphrase will expire if -# not used. -# (S/MIME only) +# Controls whether or not Mutt will try to reconnect to the POP server if +# the connection is lost. # # -# set smime_encrypt_with="" +# set pop_user="" # -# Name: smime_encrypt_with +# Name: pop_user # Type: string # Default: "" # # -# This sets the algorithm that should be used for encryption. -# Valid choices are ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``rc2-128''. -# If unset, ``3des'' (TripleDES) is used. -# (S/MIME only) +# Your login name on the POP server. +# +# This variable defaults to your user name on the local machine. # # -# set smime_keys="" +# set post_indent_string="" # -# Name: smime_keys -# Type: path +# Name: post_indent_string +# Type: string # Default: "" # # -# Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle -# storage and retrieval of keys/certs by itself. This is very basic right now, -# and stores keys and certificates in two different directories, both -# named as the hash-value retrieved from OpenSSL. There is an index file -# which contains mailbox-address keyid pair, and which can be manually -# edited. This option points to the location of the private keys. -# (S/MIME only) +# Similar to the $attribution variable, Mutt will append this +# string after the inclusion of a message which is being replied to. # # -# set smime_ca_location="" +# set postpone=ask-yes # -# Name: smime_ca_location -# Type: path -# Default: "" +# Name: postpone +# Type: quadoption +# Default: ask-yes # # -# This variable contains the name of either a directory, or a file which -# contains trusted certificates for use with OpenSSL. -# (S/MIME only) +# Controls whether or not messages are saved in the $postponed +# mailbox when you elect not to send immediately. +# +# Also see the $recall variable. # # -# set smime_certificates="" +# set postponed="~/postponed" # -# Name: smime_certificates +# Name: postponed # Type: path -# Default: "" +# Default: "~/postponed" # # -# Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle -# storage and retrieval of keys by itself. This is very basic right -# now, and keys and certificates are stored in two different -# directories, both named as the hash-value retrieved from -# OpenSSL. There is an index file which contains mailbox-address -# keyid pairs, and which can be manually edited. This option points to -# the location of the certificates. -# (S/MIME only) +# Mutt allows you to indefinitely ``postpone sending a message'' which +# you are editing. When you choose to postpone a message, Mutt saves it +# in the mailbox specified by this variable. # +# Also see the $postpone variable. # -# set smime_decrypt_command="" +# +# set preconnect="" # -# Name: smime_decrypt_command +# Name: preconnect # Type: string # Default: "" # # -# This format string specifies a command which is used to decrypt -# application/x-pkcs7-mime attachments. -# -# The OpenSSL command formats have their own set of printf(3)-like sequences -# similar to PGP's: -# %f Expands to the name of a file containing a message. -# %s Expands to the name of a file containing the signature part -# of a multipart/signed attachment when verifying it. -# %k The key-pair specified with $smime_default_key -# %c One or more certificate IDs. -# %a The algorithm used for encryption. -# %C CA location: Depending on whether $smime_ca_location -# points to a directory or file, this expands to -# ``-CApath $smime_ca_location'' or ``-CAfile $smime_ca_location''. +# If set, a shell command to be executed if mutt fails to establish +# a connection to the server. This is useful for setting up secure +# connections, e.g. with ssh(1). If the command returns a nonzero +# status, mutt gives up opening the server. Example: +# set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \ +# sleep 20 < /dev/null > /dev/null" # +# Mailbox ``foo'' on ``mailhost.net'' can now be reached +# as ``{localhost:1234}foo''. # -# For examples on how to configure these formats, see the smime.rc in -# the samples/ subdirectory which has been installed on your system -# alongside the documentation. -# (S/MIME only) +# Note: For this example to work, you must be able to log in to the +# remote machine without having to enter a password. # # -# set smime_verify_command="" +# set print=ask-no # -# Name: smime_verify_command -# Type: string -# Default: "" -# +# Name: print +# Type: quadoption +# Default: ask-no # -# This command is used to verify S/MIME signatures of type multipart/signed. # -# This is a format string, see the $smime_decrypt_command command for -# possible printf(3)-like sequences. -# (S/MIME only) +# Controls whether or not Mutt really prints messages. +# This is set to ``ask-no'' by default, because some people +# accidentally hit ``p'' often. # # -# set smime_verify_opaque_command="" +# set print_command="lpr" # -# Name: smime_verify_opaque_command -# Type: string -# Default: "" -# +# Name: print_command +# Type: path +# Default: "lpr" # -# This command is used to verify S/MIME signatures of type -# application/x-pkcs7-mime. # -# This is a format string, see the $smime_decrypt_command command for -# possible printf(3)-like sequences. -# (S/MIME only) +# This specifies the command pipe that should be used to print messages. # # -# set smime_sign_command="" +# set print_decode=yes # -# Name: smime_sign_command -# Type: string -# Default: "" -# +# Name: print_decode +# Type: boolean +# Default: yes # -# This command is used to created S/MIME signatures of type -# multipart/signed, which can be read by all mail clients. # -# This is a format string, see the $smime_decrypt_command command for -# possible printf(3)-like sequences. -# (S/MIME only) +# Used in connection with the command. If this +# option is set, the message is decoded before it is passed to the +# external command specified by $print_command. If this option +# is unset, no processing will be applied to the message when +# printing it. The latter setting may be useful if you are using +# some advanced printer filter which is able to properly format +# e-mail messages for printing. # # -# set smime_sign_opaque_command="" +# set print_split=no # -# Name: smime_sign_opaque_command -# Type: string -# Default: "" +# Name: print_split +# Type: boolean +# Default: no # # -# This command is used to created S/MIME signatures of type -# application/x-pkcs7-signature, which can only be handled by mail -# clients supporting the S/MIME extension. +# Used in connection with the command. If this option +# is set, the command specified by $print_command is executed once for +# each message which is to be printed. If this option is unset, +# the command specified by $print_command is executed only once, and +# all the messages are concatenated, with a form feed as the message +# separator. # -# This is a format string, see the $smime_decrypt_command command for -# possible printf(3)-like sequences. -# (S/MIME only) +# Those who use the enscript(1) program's mail-printing mode will +# most likely want to set this option. # # -# set smime_encrypt_command="" +# set prompt_after=yes # -# Name: smime_encrypt_command -# Type: string -# Default: "" -# +# Name: prompt_after +# Type: boolean +# Default: yes # -# This command is used to create encrypted S/MIME messages. # -# This is a format string, see the $smime_decrypt_command command for -# possible printf(3)-like sequences. -# (S/MIME only) +# If you use an external $pager, setting this variable will +# cause Mutt to prompt you for a command when the pager exits rather +# than returning to the index menu. If unset, Mutt will return to the +# index menu when the external pager exits. # # -# set smime_pk7out_command="" +# set query_command="" # -# Name: smime_pk7out_command -# Type: string +# Name: query_command +# Type: path # Default: "" # # -# This command is used to extract PKCS7 structures of S/MIME signatures, -# in order to extract the public X509 certificate(s). -# -# This is a format string, see the $smime_decrypt_command command for -# possible printf(3)-like sequences. -# (S/MIME only) +# 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. # # -# set smime_get_cert_command="" +# set query_format="%4c %t %-25.25a %-25.25n %?e?(%e)?" # -# Name: smime_get_cert_command +# Name: query_format # Type: string -# Default: "" +# Default: "%4c %t %-25.25a %-25.25n %?e?(%e)?" # # -# This command is used to extract X509 certificates from a PKCS7 structure. +# This variable describes the format of the ``query'' menu. The +# following printf(3)-style sequences are understood: +# %a destination address +# %c current entry number +# %e extra information * +# %n destination name +# %t ``*'' if current entry is tagged, a space otherwise +# %>X right justify the rest of the string and pad with ``X'' +# %|X pad to the end of the line with ``X'' +# %*X soft-fill with character ``X'' as pad # -# This is a format string, see the $smime_decrypt_command command for -# possible printf(3)-like sequences. -# (S/MIME only) # +# For an explanation of ``soft-fill'', see the $index_format documentation. # -# set smime_get_signer_cert_command="" -# -# Name: smime_get_signer_cert_command -# Type: string -# Default: "" +# * = can be optionally printed if nonzero, see the $status_format documentation. # # -# This command is used to extract only the signers X509 certificate from a S/MIME -# signature, so that the certificate's owner may get compared to the -# email's ``From:'' field. +# set quit=yes +# +# Name: quit +# Type: quadoption +# Default: yes # -# This is a format string, see the $smime_decrypt_command command for -# possible printf(3)-like sequences. -# (S/MIME only) +# +# This variable controls whether ``quit'' and ``exit'' actually quit +# from mutt. If this option is set, they do quit, if it is unset, 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. # # -# set smime_import_cert_command="" +# set quote_regexp="^([ \t]*[|>:}#])+" # -# Name: smime_import_cert_command -# Type: string -# Default: "" +# Name: quote_regexp +# Type: regular expression +# Default: "^([ \t]*[|>:}#])+" # # -# This command is used to import a certificate via smime_keys. +# A regular expression used in the internal pager to determine quoted +# sections of text in the body of a message. Quoted text may be filtered +# out using the command, or colored according to the +# ``color quoted'' family of directives. # -# This is a format string, see the $smime_decrypt_command command for -# possible printf(3)-like sequences. -# (S/MIME only) +# Higher levels of quoting may be colored differently (``color quoted1'', +# ``color quoted2'', etc.). The quoting level is determined by removing +# the last character from the matched text and recursively reapplying +# the regular expression until it fails to produce a match. # +# Match detection may be overridden by the $smileys regular expression. # -# set smime_get_cert_email_command="" +# +# set read_inc=10 # -# Name: smime_get_cert_email_command -# Type: string -# Default: "" +# Name: read_inc +# Type: number +# Default: 10 # # -# This command is used to extract the mail address(es) used for storing -# X509 certificates, and for verification purposes (to check whether the -# certificate was issued for the sender's mailbox). +# If set to a value greater than 0, Mutt will display which message it +# is currently on when reading a mailbox or when performing search actions +# such as search and limit. The message is printed after +# this many messages have been read or searched (e.g., if set to 25, Mutt will +# print a message when it is at message 25, and then again when it gets +# to message 50). This variable is meant to indicate progress when +# reading or searching large mailboxes which may take some time. +# When set to 0, only a single message will appear before the reading +# the mailbox. # -# This is a format string, see the $smime_decrypt_command command for -# possible printf(3)-like sequences. -# (S/MIME only) +# Also see the $write_inc, $net_inc and $time_inc variables and the +# ``tuning'' section of the manual for performance considerations. # # -# set smime_default_key="" +# set read_only=no # -# Name: smime_default_key -# Type: string -# Default: "" +# Name: read_only +# Type: boolean +# Default: no # # -# This is the default key-pair to use for signing. This must be set to the -# keyid (the hash-value that OpenSSL generates) to work properly -# (S/MIME only) +# If set, all folders are opened in read-only mode. # # -# set ssl_client_cert="" +# set realname="" # -# Name: ssl_client_cert -# Type: path +# Name: realname +# Type: string # Default: "" # # -# The file containing a client certificate and its associated private -# key. -# -# -# set ssl_force_tls=no -# -# Name: ssl_force_tls -# Type: boolean -# Default: no -# +# This variable specifies what ``real'' or ``personal'' name should be used +# when sending messages. # -# If this variable is set, Mutt will require that all connections -# to remote servers be encrypted. Furthermore it will attempt to -# negotiate TLS even if the server does not advertise the capability, -# since it would otherwise have to abort the connection anyway. This -# option supersedes $ssl_starttls. +# By default, this is the GECOS field from /etc/passwd. Note that this +# variable will not be used when the user has set a real name +# in the $from variable. # # -# set ssl_starttls=yes +# set recall=ask-yes # -# Name: ssl_starttls +# Name: recall # Type: quadoption -# Default: yes +# Default: ask-yes # # -# If set (the default), mutt will attempt to use STARTTLS on servers -# advertising the capability. When unset, mutt will not attempt to -# use STARTTLS regardless of the server's capabilities. +# Controls whether or not Mutt recalls postponed messages +# when composing a new message. +# +# Setting this variable to is not generally useful, and thus not +# recommended. +# +# Also see $postponed variable. # # -# set certificate_file="~/.mutt_certificates" +# set record="~/sent" # -# Name: certificate_file +# Name: record # Type: path -# Default: "~/.mutt_certificates" -# +# Default: "~/sent" # -# This variable specifies the file where the certificates you trust -# are saved. When an unknown certificate is encountered, you are asked -# if you accept it or not. If you accept it, the certificate can also -# be saved in this file and further connections are automatically -# accepted. # -# You can also manually add CA certificates in this file. Any server -# certificate that is signed with one of these CA certificates is -# also automatically accepted. +# This specifies the file into which your outgoing messages should be +# appended. (This is meant as the primary method for saving a copy of +# your messages, but another way to do this is using the ``my_hdr'' +# command to create a ``Bcc:'' field with your email address in it.) # -# Example: -# set certificate_file=~/.mutt/certificates +# The value of $record is overridden by the $force_name and +# $save_name variables, and the ``fcc-hook'' command. # # -# set ssl_usesystemcerts=yes +# set reply_regexp="^(re([\\[0-9\\]+])*|aw):[ \t]*" # -# Name: ssl_usesystemcerts -# Type: boolean -# Default: yes +# Name: reply_regexp +# Type: regular expression +# Default: "^(re([\\[0-9\\]+])*|aw):[ \t]*" # # -# If set to yes, mutt will use CA certificates in the -# system-wide certificate store when checking if a server certificate -# is signed by a trusted CA. +# A regular expression used to recognize reply messages when threading +# and replying. The default value corresponds to the English "Re:" and +# the German "Aw:". # # -# set entropy_file="" +# set reply_self=no # -# Name: entropy_file -# Type: path -# Default: "" +# Name: reply_self +# Type: boolean +# Default: no # # -# The file which includes random data that is used to initialize SSL -# library functions. +# If unset and you are replying to a message sent by you, Mutt will +# assume that you want to reply to the recipients of that message rather +# than to yourself. +# +# Also see the ``alternates'' command. # # -# set ssl_use_sslv2=yes +# set reply_to=ask-yes # -# Name: ssl_use_sslv2 -# Type: boolean -# Default: yes +# Name: reply_to +# Type: quadoption +# Default: ask-yes # # -# This variables specifies whether to attempt to use SSLv2 in the -# SSL authentication process. +# If set, when replying to a message, Mutt will use the address listed +# in the Reply-to: header as the recipient of the reply. If unset, +# it will use the address in the From: header field instead. This +# option is useful for reading a mailing list that sets the Reply-To: +# header field to the list address and you want to send a private +# message to the author of a message. # # -# set ssl_use_sslv3=yes +# set resolve=yes # -# Name: ssl_use_sslv3 +# Name: resolve # Type: boolean # Default: yes # # -# This variables specifies whether to attempt to use SSLv3 in the -# SSL authentication process. +# When set, the cursor will be automatically advanced to the next +# (possibly undeleted) message whenever a command that modifies the +# current message is executed. # # -# set ssl_use_tlsv1=yes +# set reverse_alias=no # -# Name: ssl_use_tlsv1 +# Name: reverse_alias # Type: boolean -# Default: yes +# Default: no # # -# This variables specifies whether to attempt to use TLSv1 in the -# SSL authentication process. -# -# -# set ssl_min_dh_prime_bits=0 -# -# Name: ssl_min_dh_prime_bits -# Type: number -# Default: 0 +# This variable controls whether or not Mutt will display the ``personal'' +# name from your aliases in the index menu if it finds an alias that +# matches the message's sender. For example, if you have the following +# alias: +# alias juser abd30425@somewhere.net (Joe User) # +# and then you receive mail which contains the following header: +# From: abd30425@somewhere.net # -# This variable specifies the minimum acceptable prime size (in bits) -# for use in any Diffie-Hellman key exchange. A value of 0 will use -# the default from the GNUTLS library. +# 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. # # -# set ssl_ca_certificates_file="" +# set reverse_name=no # -# Name: ssl_ca_certificates_file -# Type: path -# Default: "" +# Name: reverse_name +# Type: boolean +# Default: no # # -# This variable specifies a file containing trusted CA certificates. -# Any server certificate that is signed with one of these CA -# certificates is also automatically accepted. +# It may sometimes arrive that you receive mail to a certain machine, +# move the messages to another machine, and reply to some the messages +# from there. If this variable is set, the default From: line of +# the reply messages is built using the address where you received the +# messages you are replying to if that address matches your +# ``alternates''. If the variable is unset, or the address that would be +# used doesn't match your ``alternates'', the From: line will use +# your address on the current machine. # -# Example: -# set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt +# Also see the ``alternates'' command. # # -# set pipe_split=no +# set reverse_realname=yes # -# Name: pipe_split +# Name: reverse_realname # Type: boolean -# Default: no +# Default: yes # # -# Used in connection with the function following -# . If this variable is unset, when piping a list of -# tagged messages Mutt will concatenate the messages and will pipe them -# all concatenated. When set, Mutt will pipe the messages one by one. -# In both cases the messages are piped in the current sorted order, -# and the $pipe_sep separator is added after each message. +# This variable fine-tunes the behaviour of the $reverse_name feature. +# When it is set, mutt will use the address from incoming messages as-is, +# possibly including eventual real names. When it is unset, mutt will +# override any such real names with the setting of the $realname variable. # # -# set pipe_decode=no +# set rfc2047_parameters=no # -# Name: pipe_decode +# Name: rfc2047_parameters # Type: boolean # Default: no # # -# Used in connection with the command. When unset, -# Mutt will pipe the messages without any preprocessing. When set, Mutt -# will weed headers and will attempt to decode the messages -# first. -# +# When this variable is set, Mutt will decode RFC2047-encoded MIME +# parameters. You want to set this variable when mutt suggests you +# to save attachments to files named like: +# =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?= # -# set pipe_sep="\n" -# -# Name: pipe_sep -# Type: string -# Default: "\n" +# When this variable is set interactively, the change won't be +# active until you change folders. # +# Note that this use of RFC2047's encoding is explicitly +# prohibited by the standard, but nevertheless encountered in the +# wild. # -# The separator to add between messages when piping a list of tagged -# messages to an external Unix command. +# Also note that setting this parameter will not have the effect +# that mutt generates this kind of encoding. Instead, mutt will +# unconditionally use the encoding specified in RFC2231. # # -# set pop_authenticators="" +# set save_address=no # -# Name: pop_authenticators -# Type: string -# Default: "" -# +# Name: save_address +# Type: boolean +# Default: no # -# This is a colon-delimited list of authentication methods mutt may -# attempt to use to log in to an POP server, in the order mutt should -# try them. Authentication methods are either ``user'', ``apop'' or any -# SASL mechanism, eg ``digest-md5'', ``gssapi'' or ``cram-md5''. -# This option is case-insensitive. If this option is unset -# (the default) mutt will try all available methods, in order from -# most-secure to least-secure. # -# Example: -# set pop_authenticators="digest-md5:apop:user" +# If set, mutt will take the sender's full address when choosing a +# 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. # # -# set pop_auth_try_all=yes +# set save_empty=yes # -# Name: pop_auth_try_all +# Name: save_empty # Type: boolean # Default: yes # # -# If set, Mutt will try all available authentication methods. -# When unset, Mutt will only fall back to other authentication -# methods if the previous methods are unavailable. If a method is -# available but authentication fails, Mutt will not connect to the POP server. -# -# -# set pop_checkinterval=60 -# -# Name: pop_checkinterval -# Type: number -# Default: 60 -# +# When unset, mailboxes which contain no saved messages will be removed +# when closed (the exception is $spoolfile which is never removed). +# If set, mailboxes are never removed. # -# This variable configures how often (in seconds) mutt should look for -# new mail in the currently selected mailbox if it is a POP mailbox. +# Note: This only applies to mbox and MMDF folders, Mutt does not +# delete MH and Maildir directories. # # -# set pop_delete=ask-no +# set save_history=0 # -# Name: pop_delete -# Type: quadoption -# Default: ask-no +# Name: save_history +# Type: number +# Default: 0 # # -# If set, Mutt will delete successfully downloaded messages from the POP -# server when using the function. When unset, Mutt will -# download messages but also leave them on the POP server. +# This variable controls the size of the history (per category) saved in the +# $history_file file. # # -# set pop_host="" +# set save_name=no # -# Name: pop_host -# Type: string -# Default: "" +# Name: save_name +# Type: boolean +# Default: no # # -# The name of your POP server for the function. You -# can also specify an alternative port, username and password, ie: -# [pop[s]://][username[:password]@]popserver[:port] +# This variable controls how copies of outgoing messages are saved. +# When set, a check is made to see if a mailbox specified by the +# recipient address exists (this is done by searching for a mailbox in +# the $folder directory with the username part of the +# recipient address). If the mailbox exists, the outgoing message will +# be saved to that mailbox, otherwise the message is saved to the +# $record mailbox. # -# where ``[...]'' denotes an optional part. +# Also see the $force_name variable. # # -# set pop_last=no +# set score=yes # -# Name: pop_last +# Name: score # Type: boolean -# Default: no +# Default: yes # # -# If this variable is set, mutt will try to use the ``LAST'' POP command -# for retrieving only unread messages from the POP server when using -# the function. +# When this variable is unset, scoring is turned off. This can +# be useful to selectively disable scoring for certain folders when the +# $score_threshold_delete variable and related are used. # # -# set pop_reconnect=ask-yes +# set score_threshold_delete=-1 # -# Name: pop_reconnect -# Type: quadoption -# Default: ask-yes +# Name: score_threshold_delete +# Type: number +# Default: -1 # # -# Controls whether or not Mutt will try to reconnect to the POP server if -# the connection is lost. +# Messages which have been assigned a score equal to or lower than the value +# of this variable are automatically marked for deletion by mutt. Since +# mutt scores are always greater than or equal to zero, the default setting +# of this variable will never mark a message for deletion. # # -# set pop_user="" +# set score_threshold_flag=9999 # -# Name: pop_user -# Type: string -# Default: "" -# +# Name: score_threshold_flag +# Type: number +# Default: 9999 # -# Your login name on the POP server. # -# This variable defaults to your user name on the local machine. +# Messages which have been assigned a score greater than or equal to this +# variable's value are automatically marked "flagged". # # -# set pop_pass="" +# set score_threshold_read=-1 # -# Name: pop_pass -# Type: string -# Default: "" -# +# Name: score_threshold_read +# Type: number +# Default: -1 # -# Specifies the password for your POP account. If unset, Mutt will -# prompt you for your password when you open a POP mailbox. # -# Warning: you should only use this option when you are on a -# fairly secure machine, because the superuser can read your muttrc -# even if you are the only one who can read the file. +# Messages which have been assigned a score equal to or lower than the value +# of this variable are automatically marked as read by mutt. Since +# mutt scores are always greater than or equal to zero, the default setting +# of this variable will never mark a message read. # # -# set post_indent_string="" +# set search_context=0 # -# Name: post_indent_string -# Type: string -# Default: "" +# Name: search_context +# Type: number +# Default: 0 # # -# Similar to the $attribution variable, Mutt will append this -# string after the inclusion of a message which is being replied to. +# For the pager, this variable specifies the number of lines shown +# before search results. By default, search results will be top-aligned. # # -# set postpone=ask-yes +# set send_charset="us-ascii:iso-8859-1:utf-8" # -# Name: postpone -# Type: quadoption -# Default: ask-yes +# Name: send_charset +# Type: string +# Default: "us-ascii:iso-8859-1:utf-8" # # -# Controls whether or not messages are saved in the $postponed -# mailbox when you elect not to send immediately. +# A colon-delimited list of character sets for outgoing messages. Mutt will use the +# first character set into which the text can be converted exactly. +# If your $charset is not ``iso-8859-1'' and recipients may not +# understand ``UTF-8'', it is advisable to include in the list an +# appropriate widely used standard character set (such as +# ``iso-8859-2'', ``koi8-r'' or ``iso-2022-jp'') either instead of or after +# ``iso-8859-1''. # -# Also see the $recall variable. +# In case the text cannot be converted into one of these exactly, +# mutt uses $charset as a fallback. # # -# set postponed="~/postponed" +# set sendmail="/usr/sbin/sendmail -oem -oi" # -# Name: postponed +# Name: sendmail # Type: path -# Default: "~/postponed" +# Default: "/usr/sbin/sendmail -oem -oi" # # -# Mutt allows you to indefinitely ``postpone sending a message'' which -# you are editing. When you choose to postpone a message, Mutt saves it -# in the mailbox specified by this variable. -# -# Also see the $postpone variable. +# Specifies the program and arguments used to deliver mail sent by Mutt. +# Mutt expects that the specified program interprets additional +# arguments as recipient addresses. # # -# set preconnect="" +# set sendmail_wait=0 # -# Name: preconnect -# Type: string -# Default: "" -# -# -# If set, a shell command to be executed if mutt fails to establish -# a connection to the server. This is useful for setting up secure -# connections, e.g. with ssh(1). If the command returns a nonzero -# status, mutt gives up opening the server. Example: -# set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \ -# sleep 20 < /dev/null > /dev/null" -# -# Mailbox ``foo'' on ``mailhost.net'' can now be reached -# as ``{localhost:1234}foo''. +# Name: sendmail_wait +# Type: number +# Default: 0 # -# Note: For this example to work, you must be able to log in to the -# remote machine without having to enter a password. # +# Specifies the number of seconds to wait for the $sendmail process +# to finish before giving up and putting delivery in the background. # -# set print=ask-no -# -# Name: print -# Type: quadoption -# Default: ask-no +# Mutt interprets the value of this variable as follows: +# >0 number of seconds to wait for sendmail to finish before continuing +# 0 wait forever for sendmail to finish +# <0 always put sendmail in the background without waiting # # -# Controls whether or not Mutt really prints messages. -# This is set to ``ask-no'' by default, because some people -# accidentally hit ``p'' often. +# 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. # # -# set print_command="lpr" +# set shell="" # -# Name: print_command +# Name: shell # Type: path -# Default: "lpr" +# Default: "" # # -# This specifies the command pipe that should be used to print messages. +# Command to use when spawning a subshell. By default, the user's login +# shell from /etc/passwd is used. # # -# set print_decode=yes +# set sig_dashes=yes # -# Name: print_decode +# Name: sig_dashes # Type: boolean # Default: yes # # -# Used in connection with the command. If this -# option is set, the message is decoded before it is passed to the -# external command specified by $print_command. If this option -# is unset, no processing will be applied to the message when -# printing it. The latter setting may be useful if you are using -# some advanced printer filter which is able to properly format -# e-mail messages for printing. +# If set, a line containing ``-- '' (note the trailing space) will be inserted before your +# $signature. It is strongly recommended that you not unset +# this variable unless your signature contains just your name. The +# reason for this is because many software packages use ``-- \n'' to +# detect your signature. For example, Mutt has the ability to highlight +# the signature in a different color in the builtin pager. # # -# set print_split=no +# set sig_on_top=no # -# Name: print_split +# Name: sig_on_top # Type: boolean # Default: no # # -# Used in connection with the command. If this option -# is set, the command specified by $print_command is executed once for -# each message which is to be printed. If this option is unset, -# the command specified by $print_command is executed only once, and -# all the messages are concatenated, with a form feed as the message -# separator. -# -# Those who use the enscript(1) program's mail-printing mode will -# most likely want to set this option. -# -# -# set prompt_after=yes -# -# Name: prompt_after -# Type: boolean -# Default: yes -# -# -# If you use an external $pager, setting this variable will -# cause Mutt to prompt you for a command when the pager exits rather -# than returning to the index menu. If unset, Mutt will return to the -# index menu when the external pager exits. +# If set, the signature will be included before any quoted or forwarded +# text. It is strongly recommended that you do not set this variable +# unless you really know what you are doing, and are prepared to take +# some heat from netiquette guardians. # # -# set query_command="" +# set signature="~/.signature" # -# Name: query_command +# Name: signature # Type: path -# Default: "" +# Default: "~/.signature" # # -# 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. +# Specifies the filename of your signature, which is appended to all +# 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 standard output. # # -# set query_format="%4c %t %-25.25a %-25.25n %?e?(%e)?" +# set simple_search="~f %s | ~s %s" # -# Name: query_format +# Name: simple_search # Type: string -# Default: "%4c %t %-25.25a %-25.25n %?e?(%e)?" -# -# -# This variable describes the format of the ``query'' menu. The -# following printf(3)-style sequences are understood: -# %a destination address -# %c current entry number -# %e extra information * -# %n destination name -# %t ``*'' if current entry is tagged, a space otherwise -# %>X right justify the rest of the string and pad with ``X'' -# %|X pad to the end of the line with ``X'' -# %*X soft-fill with character ``X'' as pad +# Default: "~f %s | ~s %s" # # -# For an explanation of ``soft-fill'', see the $index_format documentation. +# 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 ``~'' pattern +# operators. See ``patterns'' for more information on search patterns. # -# * = can be optionally printed if nonzero, see the $status_format documentation. +# 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 by +# replacing ``%s'' with the supplied string. +# For the default value, ``joe'' would be expanded to: ``~f joe | ~s joe''. # # -# set quit=yes +# set sleep_time=1 # -# Name: quit -# Type: quadoption -# Default: yes +# Name: sleep_time +# Type: number +# Default: 1 # # -# This variable controls whether ``quit'' and ``exit'' actually quit -# from mutt. If this option is set, they do quit, if it is unset, 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. +# Specifies time, in seconds, to pause while displaying certain informational +# messages, while moving from folder to folder and after expunging +# messages from the current folder. The default is to pause one second, so +# a value of zero for this option suppresses the pause. # # -# set quote_regexp="^([ \t]*[|>:}#])+" +# set smart_wrap=yes # -# Name: quote_regexp -# Type: regular expression -# Default: "^([ \t]*[|>:}#])+" -# -# -# A regular expression used in the internal pager to determine quoted -# sections of text in the body of a message. Quoted text may be filtered -# out using the command, or colored according to the -# ``color quoted'' family of directives. +# Name: smart_wrap +# Type: boolean +# Default: yes # -# Higher levels of quoting may be colored differently (``color quoted1'', -# ``color quoted2'', etc.). The quoting level is determined by removing -# the last character from the matched text and recursively reapplying -# the regular expression until it fails to produce a match. # -# Match detection may be overridden by the $smileys regular expression. +# Controls the display of lines longer than the screen width in the +# internal pager. If set, long lines are wrapped at a word boundary. If +# unset, lines are simply wrapped at the screen edge. Also see the +# $markers variable. # # -# set read_inc=10 +# set smileys="(>From )|(:[-^]?[][)(><}{|/DP])" # -# Name: read_inc -# Type: number -# Default: 10 -# +# Name: smileys +# Type: regular expression +# Default: "(>From )|(:[-^]?[][)(><}{|/DP])" # -# If set to a value greater than 0, Mutt will display which message it -# is currently on when reading a mailbox or when performing search actions -# such as search and limit. The message is printed after -# this many messages have been read or searched (e.g., if set to 25, Mutt will -# print a message when it is at message 25, and then again when it gets -# to message 50). This variable is meant to indicate progress when -# reading or searching large mailboxes which may take some time. -# When set to 0, only a single message will appear before the reading -# the mailbox. # -# Also see the $write_inc, $net_inc and $time_inc variables and the -# ``tuning'' section of the manual for performance considerations. +# The pager uses this variable to catch some common false +# positives of $quote_regexp, most notably smileys and not consider +# a line quoted text if it also matches $smileys. This mostly +# happens at the beginning of a line. # # -# set read_only=no +# set smime_ask_cert_label=yes # -# Name: read_only +# Name: smime_ask_cert_label # Type: boolean -# Default: no +# Default: yes # # -# If set, all folders are opened in read-only mode. +# This flag controls whether you want to be asked to enter a label +# for a certificate about to be added to the database or not. It is +# set by default. +# (S/MIME only) # # -# set realname="" +# set smime_ca_location="" # -# Name: realname -# Type: string +# Name: smime_ca_location +# Type: path # Default: "" # # -# This variable specifies what ``real'' or ``personal'' name should be used -# when sending messages. -# -# By default, this is the GECOS field from /etc/passwd. Note that this -# variable will not be used when the user has set a real name -# in the $from variable. +# This variable contains the name of either a directory, or a file which +# contains trusted certificates for use with OpenSSL. +# (S/MIME only) # # -# set recall=ask-yes +# set smime_certificates="" # -# Name: recall -# Type: quadoption -# Default: ask-yes +# Name: smime_certificates +# Type: path +# Default: "" # # -# Controls whether or not Mutt recalls postponed messages -# when composing a new message. +# Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle +# storage and retrieval of keys by itself. This is very basic right +# now, and keys and certificates are stored in two different +# directories, both named as the hash-value retrieved from +# OpenSSL. There is an index file which contains mailbox-address +# keyid pairs, and which can be manually edited. This option points to +# the location of the certificates. +# (S/MIME only) # -# Setting this variable to is not generally useful, and thus not -# recommended. # -# Also see $postponed variable. +# set smime_decrypt_command="" +# +# Name: smime_decrypt_command +# Type: string +# Default: "" # # -# set record="~/sent" -# -# Name: record -# Type: path -# Default: "~/sent" -# -# -# This specifies the file into which your outgoing messages should be -# appended. (This is meant as the primary method for saving a copy of -# your messages, but another way to do this is using the ``my_hdr'' -# command to create a ``Bcc:'' field with your email address in it.) -# -# The value of $record is overridden by the $force_name and -# $save_name variables, and the ``fcc-hook'' command. -# -# -# set reply_regexp="^(re([\\[0-9\\]+])*|aw):[ \t]*" -# -# Name: reply_regexp -# Type: regular expression -# Default: "^(re([\\[0-9\\]+])*|aw):[ \t]*" -# -# -# A regular expression used to recognize reply messages when threading -# and replying. The default value corresponds to the English "Re:" and -# the German "Aw:". -# -# -# set reply_self=no -# -# Name: reply_self -# Type: boolean -# Default: no -# -# -# If unset and you are replying to a message sent by you, Mutt will -# assume that you want to reply to the recipients of that message rather -# than to yourself. -# -# Also see the ``alternates'' command. -# -# -# set reply_to=ask-yes -# -# Name: reply_to -# Type: quadoption -# Default: ask-yes -# -# -# If set, when replying to a message, Mutt will use the address listed -# in the Reply-to: header as the recipient of the reply. If unset, -# it will use the address in the From: header field instead. This -# option is useful for reading a mailing list that sets the Reply-To: -# header field to the list address and you want to send a private -# message to the author of a message. -# -# -# set resolve=yes -# -# Name: resolve -# Type: boolean -# Default: yes -# -# -# When set, the cursor will be automatically advanced to the next -# (possibly undeleted) message whenever a command that modifies the -# current message is executed. -# -# -# set reverse_alias=no -# -# Name: reverse_alias -# Type: boolean -# Default: no -# -# -# This variable controls whether or not Mutt will display the ``personal'' -# name from your aliases in the index menu if it finds an alias that -# matches the message's sender. For example, if you have the following -# alias: -# 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. -# -# -# set reverse_name=no -# -# Name: reverse_name -# Type: boolean -# Default: no +# This format string specifies a command which is used to decrypt +# application/x-pkcs7-mime attachments. # +# The OpenSSL command formats have their own set of printf(3)-like sequences +# similar to PGP's: +# %f Expands to the name of a file containing a message. +# %s Expands to the name of a file containing the signature part +# of a multipart/signed attachment when verifying it. +# %k The key-pair specified with $smime_default_key +# %c One or more certificate IDs. +# %a The algorithm used for encryption. +# %C CA location: Depending on whether $smime_ca_location +# points to a directory or file, this expands to +# ``-CApath $smime_ca_location'' or ``-CAfile $smime_ca_location''. # -# It may sometimes arrive that you receive mail to a certain machine, -# move the messages to another machine, and reply to some the messages -# from there. If this variable is set, the default From: line of -# the reply messages is built using the address where you received the -# messages you are replying to if that address matches your -# ``alternates''. If the variable is unset, or the address that would be -# used doesn't match your ``alternates'', the From: line will use -# your address on the current machine. # -# Also see the ``alternates'' command. +# For examples on how to configure these formats, see the smime.rc in +# the samples/ subdirectory which has been installed on your system +# alongside the documentation. +# (S/MIME only) # # -# set reverse_realname=yes +# set smime_decrypt_use_default_key=yes # -# Name: reverse_realname +# Name: smime_decrypt_use_default_key # Type: boolean # Default: yes # # -# This variable fine-tunes the behaviour of the $reverse_name feature. -# When it is set, mutt will use the address from incoming messages as-is, -# possibly including eventual real names. When it is unset, mutt will -# override any such real names with the setting of the $realname variable. -# -# -# set rfc2047_parameters=no -# -# Name: rfc2047_parameters -# Type: boolean -# Default: no -# -# -# When this variable is set, Mutt will decode RFC2047-encoded MIME -# parameters. You want to set this variable when mutt suggests you -# to save attachments to files named like: -# =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?= -# -# When this variable is set interactively, the change won't be -# active until you change folders. -# -# Note that this use of RFC2047's encoding is explicitly -# prohibited by the standard, but nevertheless encountered in the -# wild. -# -# Also note that setting this parameter will not have the effect -# that mutt generates this kind of encoding. Instead, mutt will -# unconditionally use the encoding specified in RFC2231. +# If set (default) this tells mutt to use the default key for decryption. Otherwise, +# if managing multiple certificate-key-pairs, mutt will try to use the mailbox-address +# to determine the key to use. It will ask you to supply a key, if it can't find one. +# (S/MIME only) # # -# set save_address=no +# set smime_default_key="" # -# Name: save_address -# Type: boolean -# Default: no +# Name: smime_default_key +# Type: string +# Default: "" # # -# If set, mutt will take the sender's full address when choosing a -# 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. +# This is the default key-pair to use for signing. This must be set to the +# keyid (the hash-value that OpenSSL generates) to work properly +# (S/MIME only) # # -# set save_empty=yes +# set smime_encrypt_command="" # -# Name: save_empty -# Type: boolean -# Default: yes +# Name: smime_encrypt_command +# Type: string +# Default: "" # # -# When unset, mailboxes which contain no saved messages will be removed -# when closed (the exception is $spoolfile which is never removed). -# If set, mailboxes are never removed. +# This command is used to create encrypted S/MIME messages. # -# Note: This only applies to mbox and MMDF folders, Mutt does not -# delete MH and Maildir directories. +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) # # -# set save_history=0 +# set smime_encrypt_with="" # -# Name: save_history -# Type: number -# Default: 0 +# Name: smime_encrypt_with +# Type: string +# Default: "" # # -# This variable controls the size of the history (per category) saved in the -# $history_file file. +# This sets the algorithm that should be used for encryption. +# Valid choices are ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``rc2-128''. +# If unset, ``3des'' (TripleDES) is used. +# (S/MIME only) # # -# set save_name=no +# set smime_get_cert_command="" # -# Name: save_name -# Type: boolean -# Default: no +# Name: smime_get_cert_command +# Type: string +# Default: "" # # -# This variable controls how copies of outgoing messages are saved. -# When set, a check is made to see if a mailbox specified by the -# recipient address exists (this is done by searching for a mailbox in -# the $folder directory with the username part of the -# recipient address). If the mailbox exists, the outgoing message will -# be saved to that mailbox, otherwise the message is saved to the -# $record mailbox. +# This command is used to extract X509 certificates from a PKCS7 structure. # -# Also see the $force_name variable. +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) # # -# set score=yes +# set smime_get_cert_email_command="" # -# Name: score -# Type: boolean -# Default: yes -# -# -# When this variable is unset, scoring is turned off. This can -# be useful to selectively disable scoring for certain folders when the -# $score_threshold_delete variable and related are used. -# +# Name: smime_get_cert_email_command +# Type: string +# Default: "" # -# set score_threshold_delete=-1 -# -# Name: score_threshold_delete -# Type: number -# Default: -1 # +# This command is used to extract the mail address(es) used for storing +# X509 certificates, and for verification purposes (to check whether the +# certificate was issued for the sender's mailbox). # -# Messages which have been assigned a score equal to or lower than the value -# of this variable are automatically marked for deletion by mutt. Since -# mutt scores are always greater than or equal to zero, the default setting -# of this variable will never mark a message for deletion. +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) # # -# set score_threshold_flag=9999 +# set smime_get_signer_cert_command="" # -# Name: score_threshold_flag -# Type: number -# Default: 9999 -# -# -# Messages which have been assigned a score greater than or equal to this -# variable's value are automatically marked "flagged". -# +# Name: smime_get_signer_cert_command +# Type: string +# Default: "" # -# set score_threshold_read=-1 -# -# Name: score_threshold_read -# Type: number -# Default: -1 # +# This command is used to extract only the signers X509 certificate from a S/MIME +# signature, so that the certificate's owner may get compared to the +# email's ``From:'' field. # -# Messages which have been assigned a score equal to or lower than the value -# of this variable are automatically marked as read by mutt. Since -# mutt scores are always greater than or equal to zero, the default setting -# of this variable will never mark a message read. +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) # # -# set send_charset="us-ascii:iso-8859-1:utf-8" +# set smime_import_cert_command="" # -# Name: send_charset +# Name: smime_import_cert_command # Type: string -# Default: "us-ascii:iso-8859-1:utf-8" -# -# -# A colon-delimited list of character sets for outgoing messages. Mutt will use the -# first character set into which the text can be converted exactly. -# If your $charset is not ``iso-8859-1'' and recipients may not -# understand ``UTF-8'', it is advisable to include in the list an -# appropriate widely used standard character set (such as -# ``iso-8859-2'', ``koi8-r'' or ``iso-2022-jp'') either instead of or after -# ``iso-8859-1''. -# -# In case the text cannot be converted into one of these exactly, -# mutt uses $charset as a fallback. +# Default: "" # # -# set sendmail="/usr/sbin/sendmail -oem -oi" -# -# Name: sendmail -# Type: path -# Default: "/usr/sbin/sendmail -oem -oi" -# +# This command is used to import a certificate via smime_keys. # -# Specifies the program and arguments used to deliver mail sent by Mutt. -# Mutt expects that the specified program interprets additional -# arguments as recipient addresses. +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) # # -# set sendmail_wait=0 +# set smime_is_default=no # -# Name: sendmail_wait -# Type: number -# Default: 0 -# -# -# Specifies the number of seconds to wait for the $sendmail process -# to finish before giving up and putting delivery in the background. -# -# Mutt interprets the value of this variable as follows: -# >0 number of seconds to wait for sendmail to finish before continuing -# 0 wait forever for sendmail to finish -# <0 always put sendmail in the background without waiting +# Name: smime_is_default +# Type: boolean +# Default: no # # -# 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. +# The default behaviour of mutt is to use PGP on all auto-sign/encryption +# operations. To override and to use OpenSSL instead this must be set. +# However, this has no effect while replying, since mutt will automatically +# select the same application that was used to sign/encrypt the original +# message. (Note that this variable can be overridden by unsetting $crypt_autosmime.) +# (S/MIME only) # # -# set shell="" +# set smime_keys="" # -# Name: shell +# Name: smime_keys # Type: path # Default: "" # # -# Command to use when spawning a subshell. By default, the user's login -# shell from /etc/passwd is used. +# Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle +# storage and retrieval of keys/certs by itself. This is very basic right now, +# and stores keys and certificates in two different directories, both +# named as the hash-value retrieved from OpenSSL. There is an index file +# which contains mailbox-address keyid pair, and which can be manually +# edited. This option points to the location of the private keys. +# (S/MIME only) # # -# set sig_dashes=yes +# set smime_pk7out_command="" # -# Name: sig_dashes -# Type: boolean -# Default: yes -# -# -# If set, a line containing ``-- '' (note the trailing space) will be inserted before your -# $signature. It is strongly recommended that you not unset -# this variable unless your signature contains just your name. The -# reason for this is because many software packages use ``-- \n'' to -# detect your signature. For example, Mutt has the ability to highlight -# the signature in a different color in the builtin pager. +# Name: smime_pk7out_command +# Type: string +# Default: "" # # -# set sig_on_top=no -# -# Name: sig_on_top -# Type: boolean -# Default: no -# +# This command is used to extract PKCS7 structures of S/MIME signatures, +# in order to extract the public X509 certificate(s). # -# If set, the signature will be included before any quoted or forwarded -# text. It is strongly recommended that you do not set this variable -# unless you really know what you are doing, and are prepared to take -# some heat from netiquette guardians. +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) # # -# set signature="~/.signature" +# set smime_sign_command="" # -# Name: signature -# Type: path -# Default: "~/.signature" +# Name: smime_sign_command +# Type: string +# Default: "" # # -# Specifies the filename of your signature, which is appended to all -# 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 standard output. +# This command is used to created S/MIME signatures of type +# multipart/signed, which can be read by all mail clients. +# +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) # # -# set simple_search="~f %s | ~s %s" +# set smime_sign_opaque_command="" # -# Name: simple_search +# Name: smime_sign_opaque_command # Type: string -# Default: "~f %s | ~s %s" +# Default: "" # # -# 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 ``~'' pattern -# operators. See ``patterns'' for more information on search patterns. +# This command is used to created S/MIME signatures of type +# application/x-pkcs7-signature, which can only be handled by mail +# clients supporting the S/MIME extension. # -# 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 by -# replacing ``%s'' with the supplied string. -# For the default value, ``joe'' would be expanded to: ``~f joe | ~s joe''. +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) # # -# set smart_wrap=yes +# set smime_timeout=300 # -# Name: smart_wrap -# Type: boolean -# Default: yes +# Name: smime_timeout +# Type: number +# Default: 300 # # -# Controls the display of lines longer than the screen width in the -# internal pager. If set, long lines are wrapped at a word boundary. If -# unset, lines are simply wrapped at the screen edge. Also see the -# $markers variable. +# The number of seconds after which a cached passphrase will expire if +# not used. +# (S/MIME only) # # -# set smileys="(>From )|(:[-^]?[][)(><}{|/DP])" +# set smime_verify_command="" # -# Name: smileys -# Type: regular expression -# Default: "(>From )|(:[-^]?[][)(><}{|/DP])" +# Name: smime_verify_command +# Type: string +# Default: "" # # -# The pager uses this variable to catch some common false -# positives of $quote_regexp, most notably smileys and not consider -# a line quoted text if it also matches $smileys. This mostly -# happens at the beginning of a line. +# This command is used to verify S/MIME signatures of type multipart/signed. # +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) # -# set sleep_time=1 +# +# set smime_verify_opaque_command="" # -# Name: sleep_time -# Type: number -# Default: 1 +# Name: smime_verify_opaque_command +# Type: string +# Default: "" # # -# Specifies time, in seconds, to pause while displaying certain informational -# messages, while moving from folder to folder and after expunging -# messages from the current folder. The default is to pause one second, so -# a value of zero for this option suppresses the pause. +# This command is used to verify S/MIME signatures of type +# application/x-pkcs7-mime. +# +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) # # # set smtp_authenticators="" @@ -4067,7 +3987,7 @@ attachments -I message/external-body # delivery. This should take the form of an SMTP URL, eg: # smtp[s]://[user[:pass]@]host[:port]/ # -# ... where ``[...]'' denotes an optional part. +# where ``[...]'' denotes an optional part. # Setting this variable overrides the value of the $sendmail # variable. # @@ -4196,8 +4116,143 @@ attachments -I message/external-body # # If your spool mailbox is in a non-default place where Mutt cannot find # it, you can specify its location with this variable. Mutt will -# automatically set this variable to the value of the environment -# variable $MAIL if it is not set. +# initially set this variable to the value of the environment +# variable $MAIL or $MAILDIR if either is defined. +# +# +# set ssl_ca_certificates_file="" +# +# Name: ssl_ca_certificates_file +# Type: path +# Default: "" +# +# +# This variable specifies a file containing trusted CA certificates. +# Any server certificate that is signed with one of these CA +# certificates is also automatically accepted. +# +# Example: +# set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt +# +# +# set ssl_client_cert="" +# +# Name: ssl_client_cert +# Type: path +# Default: "" +# +# +# The file containing a client certificate and its associated private +# key. +# +# +# set ssl_force_tls=no +# +# Name: ssl_force_tls +# Type: boolean +# Default: no +# +# +# If this variable is set, Mutt will require that all connections +# to remote servers be encrypted. Furthermore it will attempt to +# negotiate TLS even if the server does not advertise the capability, +# since it would otherwise have to abort the connection anyway. This +# option supersedes $ssl_starttls. +# +# +# set ssl_min_dh_prime_bits=0 +# +# Name: ssl_min_dh_prime_bits +# Type: number +# Default: 0 +# +# +# This variable specifies the minimum acceptable prime size (in bits) +# for use in any Diffie-Hellman key exchange. A value of 0 will use +# the default from the GNUTLS library. +# +# +# set ssl_starttls=yes +# +# Name: ssl_starttls +# Type: quadoption +# Default: yes +# +# +# If set (the default), mutt will attempt to use STARTTLS on servers +# advertising the capability. When unset, mutt will not attempt to +# use STARTTLS regardless of the server's capabilities. +# +# +# set ssl_use_sslv2=no +# +# Name: ssl_use_sslv2 +# Type: boolean +# Default: no +# +# +# This variable specifies whether to attempt to use SSLv2 in the +# SSL authentication process. +# +# +# set ssl_use_sslv3=yes +# +# Name: ssl_use_sslv3 +# Type: boolean +# Default: yes +# +# +# This variable specifies whether to attempt to use SSLv3 in the +# SSL authentication process. +# +# +# set ssl_use_tlsv1=yes +# +# Name: ssl_use_tlsv1 +# Type: boolean +# Default: yes +# +# +# This variable specifies whether to attempt to use TLSv1 in the +# SSL authentication process. +# +# +# set ssl_usesystemcerts=yes +# +# Name: ssl_usesystemcerts +# Type: boolean +# Default: yes +# +# +# If set to yes, mutt will use CA certificates in the +# system-wide certificate store when checking if a server certificate +# is signed by a trusted CA. +# +# +# set ssl_verify_dates=yes +# +# Name: ssl_verify_dates +# Type: boolean +# Default: yes +# +# +# If set (the default), mutt will not automatically accept a server +# certificate that is either not yet valid or already expired. You should +# only unset this for particular known hosts, using the +# function. +# +# +# set ssl_verify_host=yes +# +# Name: ssl_verify_host +# Type: boolean +# Default: yes +# +# +# If set (the default), mutt will not automatically accept a server +# certificate whose host name does not match the host used in your folder +# URL. You should only unset this for particular known hosts, using +# the function. # # # set status_chars="-*%A" @@ -4353,17 +4408,6 @@ attachments -I message/external-body # Note that $indent_string is ignored when this option is set. # # -# set thread_received=no -# -# Name: thread_received -# Type: boolean -# Default: no -# -# -# When set, mutt uses the date received rather than the date sent -# to thread messages by subject. -# -# # set thorough_search=no # # Name: thorough_search @@ -4383,6 +4427,17 @@ attachments -I message/external-body # headers) which may lead to incorrect search results. # # +# set thread_received=no +# +# Name: thread_received +# Type: boolean +# Default: no +# +# +# When set, mutt uses the date received rather than the date sent +# to thread messages by subject. +# +# # set tilde=no # # Name: tilde @@ -4477,6 +4532,21 @@ attachments -I message/external-body # Note: For this example to work you must be able to log in to the remote # machine without having to enter a password. # +# When set, Mutt uses the tunnel for all remote connections. +# Please see ``account-hook'' in the manual for how to use different +# tunnel commands per connection. +# +# +# set uncollapse_jump=no +# +# Name: uncollapse_jump +# Type: boolean +# Default: no +# +# +# When set, Mutt will jump to the next unread message, if any, +# when the current thread is uncollapsed. +# # # set use_8bitmime=no # @@ -4649,6 +4719,20 @@ attachments -I message/external-body # (DEPRECATED) Equivalent to setting $wrap with a negative value. # # +# set write_bcc=yes +# +# Name: write_bcc +# Type: boolean +# Default: yes +# +# +# Controls whether mutt writes out the ``Bcc:'' header when preparing +# messages to be sent. Exim users may wish to unset this. If mutt +# is set to deliver directly via SMTP (see $smtp_url), this +# option does nothing: mutt will never write out the ``Bcc:'' header +# in this case. +# +# # set write_inc=10 # # Name: write_inc @@ -4664,17 +4748,3 @@ attachments -I message/external-body # ``tuning'' section of the manual for performance considerations. # # -# set write_bcc=yes -# -# Name: write_bcc -# Type: boolean -# Default: yes -# -# -# Controls whether mutt writes out the ``Bcc:'' header when preparing -# messages to be sent. Exim users may wish to unset this. If mutt -# is set to deliver directly via SMTP (see $smtp_url), this -# option does nothing: mutt will never write out the ``Bcc:'' header -# in this case. -# -# diff --git a/doc/advancedusage.html b/doc/advancedusage.html index 7b919d9..336aa19 100644 --- a/doc/advancedusage.html +++ b/doc/advancedusage.html @@ -1,27 +1,31 @@ -Chapter 4. Advanced Usage
Chapter 4. Advanced Usage
Prev   Next

Chapter 4. Advanced Usage

Table of Contents

1. Regular Expressions
2. Patterns: Searching, Limiting and Tagging
2.1. Pattern Modifier
2.2. Simple Patterns
2.3. Complex Patterns
2.4. Searching by Date
3. Using Tags
4. Using Hooks
4.1. Message Matching in Hooks
5. External Address Queries
6. Mailbox Formats
7. Mailbox Shortcuts
8. Handling Mailing Lists
9. Handling multiple folders
10. Editing threads
10.1. Linking threads
10.2. Breaking threads
11. Delivery Status Notification (DSN) Support
12. Start a WWW Browser on URLs

1. Regular Expressions

+

Chapter 4. Advanced Usage
Prev   Next

Chapter 4. Advanced Usage

Table of Contents

1. Regular Expressions
2. Patterns: Searching, Limiting and Tagging
2.1. Pattern Modifier
2.2. Simple Searches
2.3. Nesting and Boolean Operators
2.4. Searching by Date
3. Using Tags
4. Using Hooks
4.1. Message Matching in Hooks
5. External Address Queries
6. Mailbox Formats
7. Mailbox Shortcuts
8. Handling Mailing Lists
9. Handling multiple folders
10. Editing Threads
10.1. Linking Threads
10.2. Breaking Threads
11. Delivery Status Notification (DSN) Support
12. Start a WWW Browser on URLs
13. Miscellany

1. Regular Expressions

All string patterns in Mutt including those in more complex patterns must be specified using regular expressions (regexp) in the “POSIX extended” syntax (which @@ -31,7 +35,7 @@ convenience, we have included below a brief description of this syntax. The search is case sensitive if the pattern contains at least one upper case letter, and case insensitive otherwise.

Note

-Note that “\” +“\” must be quoted if used for a regular expression in an initialization command: “\\”.

@@ -39,7 +43,7 @@ A regular expression is a pattern that describes a set of strings. Regular expressions are constructed analogously to arithmetic expressions, by using various operators to combine smaller expressions.

Note

-Note that the regular expression can be enclosed/delimited by either " +The regular expression can be enclosed/delimited by either " or ' which is useful if the regular expression includes a white-space character. See Syntax of Initialization Files for more information on " and ' delimiter processing. To match a @@ -56,8 +60,8 @@ the empty string at the beginning and end of a line.

A list of characters enclosed by “[” and “]” matches any single character in that list; if the first character of the list -is a caret “^” then it matches any character not in the -list. For example, the regular expression [0123456789] +is a caret “^” then it matches any character not in the +list. For example, the regular expression [0123456789] matches any single digit. A range of ASCII characters may be specified by giving the first and last characters, separated by a hyphen “-”. Most metacharacters lose their special meaning inside @@ -76,8 +80,8 @@ brackets of a character list. Note that the brackets in these class names are part of the symbolic names, and must be included in addition to the brackets delimiting the bracket list. For -example, [[:digit:]] is equivalent to -[0-9]. +example, [[:digit:]] is equivalent to +[0-9].

Two additional special sequences can appear in character lists. These apply to non-ASCII character sets, which can have single symbols (called @@ -87,15 +91,15 @@ sorting purposes:

Collating Symbols

A collating symbol is a multi-character collating element enclosed in “[.” and “.]”. For example, if “ch” is a collating -element, then [[.ch.]] is a regexp that matches -this collating element, while [ch] is a regexp that +element, then [[.ch.]] is a regexp that matches +this collating element, while [ch] is a regexp that matches either “c” or “h”.

Equivalence Classes

An equivalence class is a locale-specific name for a list of characters that are equivalent. The name is enclosed in “[=” and “=]”. For example, the name “e” might be used to represent all of “è” “é” and “e”. In this case, -[[=e=]] is a regexp that matches any of +[[=e=]] is a regexp that matches any of “è”, “é” and “e”.

A regular expression matching a single character may be followed by one @@ -113,52 +117,56 @@ Repetition takes precedence over concatenation, which in turn takes precedence over alternation. A whole subexpression may be enclosed in parentheses to override these precedence rules.

Note

-If you compile Mutt with the GNU rx package, the +If you compile Mutt with the included regular expression engine, the following operators may also be used in regular expressions as described in Table 4.3, “GNU regular expression extensions”.

Table 4.3. GNU regular expression extensions

ExpressionDescription
\\yMatches the empty string at either the beginning or the end of a word
\\BMatches the empty string within a word
\\<Matches the empty string at the beginning of a word
\\>Matches the empty string at the end of a word
\\wMatches any word-constituent character (letter, digit, or underscore)
\\WMatches any character that is not word-constituent
\\`Matches the empty string at the beginning of a buffer (string)
\\'Matches the empty string at the end of a buffer

Please note however that these operators are not defined by POSIX, so they may or may not be available in stock libraries on various systems. -

2. Patterns: Searching, Limiting and Tagging

+

2. Patterns: Searching, Limiting and Tagging

2.1. Pattern Modifier

Many of Mutt's commands allow you to specify a pattern to match (limit, tag-pattern, delete-pattern, etc.). Table 4.4, “Pattern modifiers” shows several ways to select messages. -

Table 4.4. Pattern modifiers

\n", out); docstat |= D_DL; break; } case SP_DT: { - fputs ("", out); + fputs ("", out); break; } case SP_DD: { docstat |= D_DD; if (docstat & D_DL) - fputs("\n", out); - fputs ("", out); + fputs("", out); + else + fputs ("", out); break; } case SP_END_DD: { - docstat &= ~D_DD; - fputs ("", out); if (docstat & D_DL) - fputs("\n", out); + fputs ("\n", out); + else + fputs ("", out); + docstat &= ~D_DD; break; } case SP_END_DL: { - fputs ("\n", out); + fputs ("\n", out); docstat &= ~(D_DD|D_DL); break; } diff --git a/doc/manual.html b/doc/manual.html index 07afabc..767669e 100644 --- a/doc/manual.html +++ b/doc/manual.html @@ -1,28 +1,33 @@ + -The Mutt E-Mail Client

The Mutt E-Mail Client

Michael Elkins

version 1.5.19 (2009-01-05)

Abstract

-“All mail clients suck. This one just sucks less.” -me, circa 1995 -

Table of Contents

1. Introduction
1. Mutt Home Page
2. Mailing Lists
3. Software Distribution Sites
4. Mutt online resources
5. Contributing to Mutt
6. Typograhical conventions
7. Copyright
2. Getting Started
1. Core concepts
2. Moving Around in Menus
3. Editing Input Fields
3.1. Introduction
3.2. History
4. Reading Mail - The Index and Pager
4.1. The Message Index
4.2. The Pager
4.3. Threaded Mode
4.4. Miscellaneous Functions
5. Sending Mail
5.1. Introduction
5.2. Editing the message header
5.3. Sending cryptographically signed/encrypted messages
5.4. Sending anonymous messages via mixmaster
5.5. Sending format=flowed messages
6. Forwarding and Bouncing Mail
7. Postponing Mail
3. Configuration
1. Location of initialization files
2. Syntax of Initialization Files
3. Address groups
4. Defining/Using aliases
5. Changing the default key bindings
6. Defining aliases for character sets
7. Setting variables based upon mailbox
8. Keyboard macros
9. Using color and mono video attributes
10. Message header display
11. Alternative addresses
12. Mailing lists
13. Using Multiple spool mailboxes
14. Monitoring incoming mail
15. User defined headers
16. Specify default save mailbox
17. Specify default Fcc: mailbox when composing
18. Specify default save filename and default Fcc: mailbox at once
19. Change settings based upon message recipients
20. Change settings before formatting a message
21. Choosing the cryptographic key of the recipient
22. Adding key sequences to the keyboard buffer
23. Executing functions
24. Message Scoring
25. Spam detection
26. Setting and Querying Variables
26.1. Commands
26.2. User-defined variables
27. Reading initialization commands from another file
28. Removing hooks
29. Format Strings
29.1. Basic usage
29.2. Filters
4. Advanced Usage
1. Regular Expressions
2. Patterns: Searching, Limiting and Tagging
2.1. Pattern Modifier
2.2. Simple Patterns
2.3. Complex Patterns
2.4. Searching by Date
3. Using Tags
4. Using Hooks
4.1. Message Matching in Hooks
5. External Address Queries
6. Mailbox Formats
7. Mailbox Shortcuts
8. Handling Mailing Lists
9. Handling multiple folders
10. Editing threads
10.1. Linking threads
10.2. Breaking threads
11. Delivery Status Notification (DSN) Support
12. Start a WWW Browser on URLs
5. Mutt's MIME Support
1. Using MIME in Mutt
1.1. Viewing MIME messages in the pager
1.2. The Attachment Menu
1.3. The Compose Menu
2. MIME Type configuration with mime.types
3. MIME Viewer configuration with mailcap
3.1. The Basics of the mailcap file
3.2. Secure use of mailcap
3.3. Advanced mailcap Usage
3.4. Example mailcap files
4. MIME Autoview
5. MIME Multipart/Alternative
6. Attachment Searching and Counting
7. MIME Lookup
6. Optional features
1. General notes
1.1. Enabling/disabling features
1.2. URL syntax
2. SSL/TLS Support
3. POP3 Support
4. IMAP Support
4.1. The Folder Browser
4.2. Authentication
5. SMTP Support
6. Managing multiple accounts
7. Local caching
7.1. Header caching
7.2. Body caching
7.3. Maintenance
8. Exact address generation
7. Performance tuning
1. Reading and writing mailboxes
2. Reading messages from remote folders
3. Searching and limiting
8. Reference
1. Command line options
2. Configuration Commands
3. Configuration variables
3.1. abort_nosubject
3.2. abort_unmodified
3.3. alias_file
3.4. alias_format
3.5. allow_8bit
3.6. allow_ansi
3.7. arrow_cursor
3.8. ascii_chars
3.9. askbcc
3.10. askcc
3.11. assumed_charset
3.12. attach_charset
3.13. attach_format
3.14. attach_sep
3.15. attach_split
3.16. attribution
3.17. autoedit
3.18. auto_tag
3.19. beep
3.20. beep_new
3.21. bounce
3.22. bounce_delivered
3.23. braille_friendly
3.24. check_mbox_size
3.25. charset
3.26. check_new
3.27. collapse_unread
3.28. uncollapse_jump
3.29. compose_format
3.30. config_charset
3.31. confirmappend
3.32. confirmcreate
3.33. connect_timeout
3.34. content_type
3.35. copy
3.36. crypt_use_gpgme
3.37. crypt_use_pka
3.38. crypt_autopgp
3.39. crypt_autosmime
3.40. date_format
3.41. default_hook
3.42. delete
3.43. delete_untag
3.44. digest_collapse
3.45. display_filter
3.46. dotlock_program
3.47. dsn_notify
3.48. dsn_return
3.49. duplicate_threads
3.50. edit_headers
3.51. editor
3.52. encode_from
3.53. envelope_from_address
3.54. escape
3.55. fast_reply
3.56. fcc_attach
3.57. fcc_clear
3.58. folder
3.59. folder_format
3.60. followup_to
3.61. force_name
3.62. forward_decode
3.63. forward_edit
3.64. forward_format
3.65. forward_quote
3.66. from
3.67. gecos_mask
3.68. hdrs
3.69. header
3.70. help
3.71. hidden_host
3.72. hide_limited
3.73. hide_missing
3.74. hide_thread_subject
3.75. hide_top_limited
3.76. hide_top_missing
3.77. history
3.78. history_file
3.79. honor_followup_to
3.80. hostname
3.81. ignore_linear_white_space
3.82. ignore_list_reply_to
3.83. imap_authenticators
3.84. imap_check_subscribed
3.85. imap_delim_chars
3.86. imap_headers
3.87. imap_idle
3.88. imap_keepalive
3.89. imap_list_subscribed
3.90. imap_login
3.91. imap_pass
3.92. imap_passive
3.93. imap_peek
3.94. imap_pipeline_depth
3.95. imap_servernoise
3.96. imap_user
3.97. implicit_autoview
3.98. include
3.99. include_onlyfirst
3.100. indent_string
3.101. index_format
3.102. ispell
3.103. keep_flagged
3.104. locale
3.105. mail_check
3.106. mailcap_path
3.107. mailcap_sanitize
3.108. header_cache
3.109. maildir_header_cache_verify
3.110. header_cache_pagesize
3.111. header_cache_compress
3.112. maildir_trash
3.113. mark_old
3.114. markers
3.115. mask
3.116. mbox
3.117. mbox_type
3.118. metoo
3.119. menu_context
3.120. menu_move_off
3.121. menu_scroll
3.122. meta_key
3.123. mh_purge
3.124. mh_seq_flagged
3.125. mh_seq_replied
3.126. mh_seq_unseen
3.127. mime_forward
3.128. mime_forward_decode
3.129. mime_forward_rest
3.130. mix_entry_format
3.131. mixmaster
3.132. move
3.133. message_cachedir
3.134. message_cache_clean
3.135. message_format
3.136. narrow_tree
3.137. net_inc
3.138. pager
3.139. pager_context
3.140. pager_format
3.141. pager_index_lines
3.142. pager_stop
3.143. crypt_autosign
3.144. crypt_autoencrypt
3.145. pgp_ignore_subkeys
3.146. crypt_replyencrypt
3.147. crypt_replysign
3.148. crypt_replysignencrypted
3.149. crypt_timestamp
3.150. pgp_use_gpg_agent
3.151. crypt_verify_sig
3.152. smime_is_default
3.153. smime_ask_cert_label
3.154. smime_decrypt_use_default_key
3.155. pgp_entry_format
3.156. pgp_good_sign
3.157. pgp_check_exit
3.158. pgp_long_ids
3.159. pgp_retainable_sigs
3.160. pgp_autoinline
3.161. pgp_replyinline
3.162. pgp_show_unusable
3.163. pgp_sign_as
3.164. pgp_strict_enc
3.165. pgp_timeout
3.166. pgp_sort_keys
3.167. pgp_mime_auto
3.168. pgp_auto_decode
3.169. pgp_decode_command
3.170. pgp_getkeys_command
3.171. pgp_verify_command
3.172. pgp_decrypt_command
3.173. pgp_clearsign_command
3.174. pgp_sign_command
3.175. pgp_encrypt_sign_command
3.176. pgp_encrypt_only_command
3.177. pgp_import_command
3.178. pgp_export_command
3.179. pgp_verify_key_command
3.180. pgp_list_secring_command
3.181. pgp_list_pubring_command
3.182. forward_decrypt
3.183. smime_timeout
3.184. smime_encrypt_with
3.185. smime_keys
3.186. smime_ca_location
3.187. smime_certificates
3.188. smime_decrypt_command
3.189. smime_verify_command
3.190. smime_verify_opaque_command
3.191. smime_sign_command
3.192. smime_sign_opaque_command
3.193. smime_encrypt_command
3.194. smime_pk7out_command
3.195. smime_get_cert_command
3.196. smime_get_signer_cert_command
3.197. smime_import_cert_command
3.198. smime_get_cert_email_command
3.199. smime_default_key
3.200. ssl_client_cert
3.201. ssl_force_tls
3.202. ssl_starttls
3.203. certificate_file
3.204. ssl_usesystemcerts
3.205. entropy_file
3.206. ssl_use_sslv2
3.207. ssl_use_sslv3
3.208. ssl_use_tlsv1
3.209. ssl_min_dh_prime_bits
3.210. ssl_ca_certificates_file
3.211. pipe_split
3.212. pipe_decode
3.213. pipe_sep
3.214. pop_authenticators
3.215. pop_auth_try_all
3.216. pop_checkinterval
3.217. pop_delete
3.218. pop_host
3.219. pop_last
3.220. pop_reconnect
3.221. pop_user
3.222. pop_pass
3.223. post_indent_string
3.224. postpone
3.225. postponed
3.226. preconnect
3.227. print
3.228. print_command
3.229. print_decode
3.230. print_split
3.231. prompt_after
3.232. query_command
3.233. query_format
3.234. quit
3.235. quote_regexp
3.236. read_inc
3.237. read_only
3.238. realname
3.239. recall
3.240. record
3.241. reply_regexp
3.242. reply_self
3.243. reply_to
3.244. resolve
3.245. reverse_alias
3.246. reverse_name
3.247. reverse_realname
3.248. rfc2047_parameters
3.249. save_address
3.250. save_empty
3.251. save_history
3.252. save_name
3.253. score
3.254. score_threshold_delete
3.255. score_threshold_flag
3.256. score_threshold_read
3.257. send_charset
3.258. sendmail
3.259. sendmail_wait
3.260. shell
3.261. sig_dashes
3.262. sig_on_top
3.263. signature
3.264. simple_search
3.265. smart_wrap
3.266. smileys
3.267. sleep_time
3.268. smtp_authenticators
3.269. smtp_pass
3.270. smtp_url
3.271. sort
3.272. sort_alias
3.273. sort_aux
3.274. sort_browser
3.275. sort_re
3.276. spam_separator
3.277. spoolfile
3.278. status_chars
3.279. status_format
3.280. status_on_top
3.281. strict_threads
3.282. suspend
3.283. text_flowed
3.284. thread_received
3.285. thorough_search
3.286. tilde
3.287. time_inc
3.288. timeout
3.289. tmpdir
3.290. to_chars
3.291. tunnel
3.292. use_8bitmime
3.293. use_domain
3.294. use_envelope_from
3.295. use_from
3.296. use_idn
3.297. use_ipv6
3.298. user_agent
3.299. visual
3.300. wait_key
3.301. weed
3.302. wrap
3.303. wrap_search
3.304. wrapmargin
3.305. write_inc
3.306. write_bcc
4. Functions
4.1. generic menu
4.2. index menu
4.3. pager menu
4.4. alias menu
4.5. query menu
4.6. attach menu
4.7. compose menu
4.8. postpone menu
4.9. browser menu
4.10. pgp menu
4.11. smime menu
4.12. mix menu
4.13. editor menu
9. Miscellany
1. Acknowledgements
2. About this document

List of Tables

1.1. Typographical conventions for special terms
2.1. Most common navigation keys
2.2. Most common line editor keys
2.3. Most common message index keys
2.4. Message status flags
2.5. Message recipient flags
2.6. Most common pager keys
2.7. ANSI escape sequences
2.8. Color sequences
2.9. Most common thread mode keys
2.10. Most common mail sending keys
2.11. Most common compose menu keys
2.12. PGP key menu flags
3.1. Symbolic key names
4.1. POSIX regular expression character classes
4.2. Regular expression repetition operators
4.3. GNU regular expression extensions
4.4. Pattern modifiers
4.5. Simple search keywords
4.6. Date units
8.1. Command line options
8.2. Default generic function bindings
8.3. Default index function bindings
8.4. Default pager function bindings
8.5. Default alias function bindings
8.6. Default query function bindings
8.7. Default attach function bindings
8.8. Default compose function bindings
8.9. Default postpone function bindings
8.10. Default browser function bindings
8.11. Default pgp function bindings
8.12. Default smime function bindings
8.13. Default mix function bindings
8.14. Default editor function bindings

List of Examples

3.1. Multiple configuration commands per line
3.2. Commenting configuration files
3.3. Escaping quotes in congfiguration files
3.4. Using external command's output in configuration files
3.5. Using environment variables in configuration files
3.6. Configuring external alias files
3.7. Setting sort method based on mailbox name
3.8. Header weeding
3.9. Configuring header display order
3.10. Defining custom headers
3.11. Using %-expandos in save-hook
3.12. Embedding push in folder-hook
3.13. Configuring spam detection
3.14. Using user-defined variables for config file readability
3.15. Using user-defined variables for backing up other config option values
3.16. Deferring user-defined variable expansion to runtime
3.17. Using external filters in format strings
4.1. Using boolean operators in patterns
4.2. Combining send-hook and my_hdr
5.1. Attachment counting

Chapter 1. Introduction

Table of Contents

1. Mutt Home Page
2. Mailing Lists
3. Software Distribution Sites
4. Mutt online resources
5. Contributing to Mutt
6. Typograhical conventions
7. Copyright

+

The Mutt E-Mail Client

Michael Elkins

version 1.5.20 (2009-06-14)

Abstract

+“All mail clients suck. This one just sucks less.” — me, circa 1995 +

Table of Contents

1. Introduction
1. Mutt Home Page
2. Mailing Lists
3. Getting Mutt
4. Mutt Online Resources
5. Contributing to Mutt
6. Typograhical Conventions
7. Copyright
2. Getting Started
1. Core Concepts
2. Screens and Menus
2.1. Index
2.2. Pager
2.3. File Browser
2.4. Help
2.5. Compose Menu
2.6. Alias Menu
2.7. Attachment Menu
3. Moving Around in Menus
4. Editing Input Fields
4.1. Introduction
4.2. History
5. Reading Mail
5.1. The Message Index
5.2. The Pager
5.3. Threaded Mode
5.4. Miscellaneous Functions
6. Sending Mail
6.1. Introduction
6.2. Editing the Message Header
6.3. Sending Cryptographically Signed/Encrypted Messages
6.4. Sending Format=Flowed Messages
7. Forwarding and Bouncing Mail
8. Postponing Mail
3. Configuration
1. Location of Initialization Files
2. Syntax of Initialization Files
3. Address Groups
4. Defining/Using Aliases
5. Changing the Default Key Bindings
6. Defining Aliases for Character Sets
7. Setting Variables Based Upon Mailbox
8. Keyboard Macros
9. Using Color and Mono Video Attributes
10. Message Header Display
10.1. Selecting Headers
10.2. Ordering Displayed Headers
11. Alternative Addresses
12. Mailing Lists
13. Using Multiple Spool Mailboxes
14. Monitoring Incoming Mail
15. User-Defined Headers
16. Specify Default Save Mailbox
17. Specify Default Fcc: Mailbox When Composing
18. Specify Default Save Filename and Default Fcc: Mailbox at Once
19. Change Settings Based Upon Message Recipients
20. Change Settings Before Formatting a Message
21. Choosing the Cryptographic Key of the Recipient
22. Adding Key Sequences to the Keyboard Buffer
23. Executing Functions
24. Message Scoring
25. Spam Detection
26. Setting and Querying Variables
26.1. Variable Types
26.2. Commands
26.3. User-Defined Variables
27. Reading Initialization Commands From Another File
28. Removing Hooks
29. Format Strings
29.1. Basic usage
29.2. Conditionals
29.3. Filters
29.4. Padding
4. Advanced Usage
1. Regular Expressions
2. Patterns: Searching, Limiting and Tagging
2.1. Pattern Modifier
2.2. Simple Searches
2.3. Nesting and Boolean Operators
2.4. Searching by Date
3. Using Tags
4. Using Hooks
4.1. Message Matching in Hooks
5. External Address Queries
6. Mailbox Formats
7. Mailbox Shortcuts
8. Handling Mailing Lists
9. Handling multiple folders
10. Editing Threads
10.1. Linking Threads
10.2. Breaking Threads
11. Delivery Status Notification (DSN) Support
12. Start a WWW Browser on URLs
13. Miscellany
5. Mutt's MIME Support
1. Using MIME in Mutt
1.1. Viewing MIME Messages in the Pager
1.2. The Attachment Menu
1.3. The Compose Menu
2. MIME Type Configuration with mime.types
3. MIME Viewer Configuration with Mailcap
3.1. The Basics of the Mailcap File
3.2. Secure Use of Mailcap
3.3. Advanced Mailcap Usage
3.4. Example Mailcap Files
4. MIME Autoview
5. MIME Multipart/Alternative
6. Attachment Searching and Counting
7. MIME Lookup
6. Optional Features
1. General Notes
1.1. Enabling/Disabling Features
1.2. URL Syntax
2. SSL/TLS Support
3. POP3 Support
4. IMAP Support
4.1. The IMAP Folder Browser
4.2. Authentication
5. SMTP Support
6. Managing Multiple Accounts
7. Local Caching
7.1. Header Caching
7.2. Body Caching
7.3. Maintenance
8. Exact Address Generation
9. Sending Anonymous Messages via Mixmaster
7. Security Considerations
1. Passwords
2. Temporary Files
3. Information Leaks
3.1. Message-Id: headers
3.2. mailto:-style Links
4. External Applications
8. Performance Tuning
1. Reading and Writing Mailboxes
2. Reading Messages from Remote Folders
3. Searching and Limiting
9. Reference
1. Command-Line Options
2. Configuration Commands
3. Configuration Variables
3.1. abort_nosubject
3.2. abort_unmodified
3.3. alias_file
3.4. alias_format
3.5. allow_8bit
3.6. allow_ansi
3.7. arrow_cursor
3.8. ascii_chars
3.9. askbcc
3.10. askcc
3.11. assumed_charset
3.12. attach_charset
3.13. attach_format
3.14. attach_sep
3.15. attach_split
3.16. attribution
3.17. auto_tag
3.18. autoedit
3.19. beep
3.20. beep_new
3.21. bounce
3.22. bounce_delivered
3.23. braille_friendly
3.24. certificate_file
3.25. charset
3.26. check_mbox_size
3.27. check_new
3.28. collapse_unread
3.29. compose_format
3.30. config_charset
3.31. confirmappend
3.32. confirmcreate
3.33. connect_timeout
3.34. content_type
3.35. copy
3.36. crypt_autoencrypt
3.37. crypt_autopgp
3.38. crypt_autosign
3.39. crypt_autosmime
3.40. crypt_replyencrypt
3.41. crypt_replysign
3.42. crypt_replysignencrypted
3.43. crypt_timestamp
3.44. crypt_use_gpgme
3.45. crypt_use_pka
3.46. crypt_verify_sig
3.47. date_format
3.48. default_hook
3.49. delete
3.50. delete_untag
3.51. digest_collapse
3.52. display_filter
3.53. dotlock_program
3.54. dsn_notify
3.55. dsn_return
3.56. duplicate_threads
3.57. edit_headers
3.58. editor
3.59. encode_from
3.60. entropy_file
3.61. envelope_from_address
3.62. escape
3.63. fast_reply
3.64. fcc_attach
3.65. fcc_clear
3.66. folder
3.67. folder_format
3.68. followup_to
3.69. force_name
3.70. forward_decode
3.71. forward_decrypt
3.72. forward_edit
3.73. forward_format
3.74. forward_quote
3.75. from
3.76. gecos_mask
3.77. hdrs
3.78. header
3.79. header_cache
3.80. header_cache_compress
3.81. header_cache_pagesize
3.82. help
3.83. hidden_host
3.84. hide_limited
3.85. hide_missing
3.86. hide_thread_subject
3.87. hide_top_limited
3.88. hide_top_missing
3.89. history
3.90. history_file
3.91. honor_disposition
3.92. honor_followup_to
3.93. hostname
3.94. ignore_linear_white_space
3.95. ignore_list_reply_to
3.96. imap_authenticators
3.97. imap_check_subscribed
3.98. imap_delim_chars
3.99. imap_headers
3.100. imap_idle
3.101. imap_keepalive
3.102. imap_list_subscribed
3.103. imap_login
3.104. imap_pass
3.105. imap_passive
3.106. imap_peek
3.107. imap_pipeline_depth
3.108. imap_servernoise
3.109. imap_user
3.110. implicit_autoview
3.111. include
3.112. include_onlyfirst
3.113. indent_string
3.114. index_format
3.115. ispell
3.116. keep_flagged
3.117. locale
3.118. mail_check
3.119. mailcap_path
3.120. mailcap_sanitize
3.121. maildir_header_cache_verify
3.122. maildir_trash
3.123. mark_old
3.124. markers
3.125. mask
3.126. mbox
3.127. mbox_type
3.128. menu_context
3.129. menu_move_off
3.130. menu_scroll
3.131. message_cache_clean
3.132. message_cachedir
3.133. message_format
3.134. meta_key
3.135. metoo
3.136. mh_purge
3.137. mh_seq_flagged
3.138. mh_seq_replied
3.139. mh_seq_unseen
3.140. mime_forward
3.141. mime_forward_decode
3.142. mime_forward_rest
3.143. mix_entry_format
3.144. mixmaster
3.145. move
3.146. narrow_tree
3.147. net_inc
3.148. pager
3.149. pager_context
3.150. pager_format
3.151. pager_index_lines
3.152. pager_stop
3.153. pgp_auto_decode
3.154. pgp_autoinline
3.155. pgp_check_exit
3.156. pgp_clearsign_command
3.157. pgp_decode_command
3.158. pgp_decrypt_command
3.159. pgp_encrypt_only_command
3.160. pgp_encrypt_sign_command
3.161. pgp_entry_format
3.162. pgp_export_command
3.163. pgp_getkeys_command
3.164. pgp_good_sign
3.165. pgp_ignore_subkeys
3.166. pgp_import_command
3.167. pgp_list_pubring_command
3.168. pgp_list_secring_command
3.169. pgp_long_ids
3.170. pgp_mime_auto
3.171. pgp_replyinline
3.172. pgp_retainable_sigs
3.173. pgp_show_unusable
3.174. pgp_sign_as
3.175. pgp_sign_command
3.176. pgp_sort_keys
3.177. pgp_strict_enc
3.178. pgp_timeout
3.179. pgp_use_gpg_agent
3.180. pgp_verify_command
3.181. pgp_verify_key_command
3.182. pipe_decode
3.183. pipe_sep
3.184. pipe_split
3.185. pop_auth_try_all
3.186. pop_authenticators
3.187. pop_checkinterval
3.188. pop_delete
3.189. pop_host
3.190. pop_last
3.191. pop_pass
3.192. pop_reconnect
3.193. pop_user
3.194. post_indent_string
3.195. postpone
3.196. postponed
3.197. preconnect
3.198. print
3.199. print_command
3.200. print_decode
3.201. print_split
3.202. prompt_after
3.203. query_command
3.204. query_format
3.205. quit
3.206. quote_regexp
3.207. read_inc
3.208. read_only
3.209. realname
3.210. recall
3.211. record
3.212. reply_regexp
3.213. reply_self
3.214. reply_to
3.215. resolve
3.216. reverse_alias
3.217. reverse_name
3.218. reverse_realname
3.219. rfc2047_parameters
3.220. save_address
3.221. save_empty
3.222. save_history
3.223. save_name
3.224. score
3.225. score_threshold_delete
3.226. score_threshold_flag
3.227. score_threshold_read
3.228. search_context
3.229. send_charset
3.230. sendmail
3.231. sendmail_wait
3.232. shell
3.233. sig_dashes
3.234. sig_on_top
3.235. signature
3.236. simple_search
3.237. sleep_time
3.238. smart_wrap
3.239. smileys
3.240. smime_ask_cert_label
3.241. smime_ca_location
3.242. smime_certificates
3.243. smime_decrypt_command
3.244. smime_decrypt_use_default_key
3.245. smime_default_key
3.246. smime_encrypt_command
3.247. smime_encrypt_with
3.248. smime_get_cert_command
3.249. smime_get_cert_email_command
3.250. smime_get_signer_cert_command
3.251. smime_import_cert_command
3.252. smime_is_default
3.253. smime_keys
3.254. smime_pk7out_command
3.255. smime_sign_command
3.256. smime_sign_opaque_command
3.257. smime_timeout
3.258. smime_verify_command
3.259. smime_verify_opaque_command
3.260. smtp_authenticators
3.261. smtp_pass
3.262. smtp_url
3.263. sort
3.264. sort_alias
3.265. sort_aux
3.266. sort_browser
3.267. sort_re
3.268. spam_separator
3.269. spoolfile
3.270. ssl_ca_certificates_file
3.271. ssl_client_cert
3.272. ssl_force_tls
3.273. ssl_min_dh_prime_bits
3.274. ssl_starttls
3.275. ssl_use_sslv2
3.276. ssl_use_sslv3
3.277. ssl_use_tlsv1
3.278. ssl_usesystemcerts
3.279. ssl_verify_dates
3.280. ssl_verify_host
3.281. status_chars
3.282. status_format
3.283. status_on_top
3.284. strict_threads
3.285. suspend
3.286. text_flowed
3.287. thorough_search
3.288. thread_received
3.289. tilde
3.290. time_inc
3.291. timeout
3.292. tmpdir
3.293. to_chars
3.294. tunnel
3.295. uncollapse_jump
3.296. use_8bitmime
3.297. use_domain
3.298. use_envelope_from
3.299. use_from
3.300. use_idn
3.301. use_ipv6
3.302. user_agent
3.303. visual
3.304. wait_key
3.305. weed
3.306. wrap
3.307. wrap_search
3.308. wrapmargin
3.309. write_bcc
3.310. write_inc
4. Functions
4.1. Generic Menu
4.2. Index Menu
4.3. Pager Menu
4.4. Alias Menu
4.5. Query Menu
4.6. Attach Menu
4.7. Compose Menu
4.8. Postpone Menu
4.9. Browser Menu
4.10. Pgp Menu
4.11. Smime Menu
4.12. Mix Menu
4.13. Editor Menu
10. Miscellany
1. Acknowledgements
2. About This Document

List of Tables

1.1. Typographical conventions for special terms
2.1. Most common navigation keys in entry-based menus
2.2. Most common navigation keys in page-based menus
2.3. Most common line editor keys
2.4. Most common message index keys
2.5. Message status flags
2.6. Message recipient flags
2.7. Most common pager keys
2.8. ANSI escape sequences
2.9. Color sequences
2.10. Most common thread mode keys
2.11. Most common mail sending keys
2.12. Most common compose menu keys
2.13. PGP key menu flags
3.1. Symbolic key names
4.1. POSIX regular expression character classes
4.2. Regular expression repetition operators
4.3. GNU regular expression extensions
4.4. Pattern modifiers
4.5. Simple search keywords
4.6. Date units
9.1. Command line options
9.2. Default generic Function Bindings
9.3. Default index Function Bindings
9.4. Default pager Function Bindings
9.5. Default alias Function Bindings
9.6. Default query Function Bindings
9.7. Default attach Function Bindings
9.8. Default compose Function Bindings
9.9. Default postpone Function Bindings
9.10. Default browser Function Bindings
9.11. Default pgp Function Bindings
9.12. Default smime Function Bindings
9.13. Default mix Function Bindings
9.14. Default editor Function Bindings

List of Examples

3.1. Multiple configuration commands per line
3.2. Commenting configuration files
3.3. Escaping quotes in congfiguration files
3.4. Splitting long configuration commands over several lines
3.5. Using external command's output in configuration files
3.6. Using environment variables in configuration files
3.7. Configuring external alias files
3.8. Setting sort method based on mailbox name
3.9. Header weeding
3.10. Configuring header display order
3.11. Defining custom headers
3.12. Using %-expandos in save-hook
3.13. Embedding push in folder-hook
3.14. Configuring spam detection
3.15. Using user-defined variables for config file readability
3.16. Using user-defined variables for backing up other config option values
3.17. Deferring user-defined variable expansion to runtime
3.18. Using external filters in format strings
4.1. Matching all addresses in address lists
4.2. Using boolean operators in patterns
4.3. Specifying a default hook
5.1. Attachment counting
6.1. URLs
6.2. Managing multiple accounts

Chapter 1. Introduction

Table of Contents

1. Mutt Home Page
2. Mailing Lists
3. Getting Mutt
4. Mutt Online Resources
5. Contributing to Mutt
6. Typograhical Conventions
7. Copyright

Mutt is a small but very powerful text-based MIME mail client. Mutt is highly configurable, and is well suited to the mail power user with advanced features like key bindings, keyboard macros, mail threading, regular @@ -46,14 +51,17 @@ All messages posted to mutt-announce are automatically forwarded to mutt-users, so you do not need to be subscribed to both lists. -

3. Software Distribution Sites

+

3. Getting Mutt

Mutt releases can be downloaded from ftp://ftp.mutt.org/mutt/. For a list of mirror sites, please refer to http://www.mutt.org/download.html. -

4. Mutt online resources

Bug Tracking System

-The official mutt bug tracking system can be found at -http://dev.mutt.org/ +

+For nightly tarballs and version control access, please refer to the +Mutt development site. +

4. Mutt Online Resources

Bug Tracking System

+The official Mutt bug tracking system can be found at +http://bugs.mutt.org/

Wiki

An (unofficial) wiki can be found at http://wiki.mutt.org/. @@ -70,17 +78,17 @@ experienced users to chat about Mutt, talk about problems and share tricks.

Since translations of Mutt into other languages are highly appreciated, -the mutt developers always look for skilled translators that help +the Mutt developers always look for skilled translators that help improve and continue to maintain stale translations.

For contributing code patches for new features and bug fixes, please refer to the developer pages at http://dev.mutt.org/ for more details. -

6. Typograhical conventions

+

6. Typograhical Conventions

This section lists typographical conventions followed throughout this manual. See table Table 1.1, “Typographical conventions for special terms” for typographical conventions for special terms. -

Table 1.1. Typographical conventions for special terms

Pattern modifierDescription
~Aall messages
~b EXPRmessages which contain EXPR in the message body
=b STRINGmessages which contain STRING in the message body. If IMAP is enabled, searches for STRING on the server, rather than downloading each message and searching it locally.
~B EXPRmessages which contain EXPR in the whole message
~c EXPRmessages carbon-copied to EXPR
%c GROUPmessages carbon-copied to any member of GROUP
~C EXPRmessages either to: or cc: EXPR
%C GROUPmessages either to: or cc: to any member of GROUP
~d [MIN]-[MAX]messages with “date-sent” in a Date range
~Ddeleted messages
~e EXPRmessages which contains EXPR in the “Sender” field
%e GROUPmessages which contain a member of GROUP in the “Sender” field
~Eexpired messages
~Fflagged messages
~f EXPRmessages originating from EXPR
%f GROUPmessages originating from any member of GROUP
~gcryptographically signed messages
~Gcryptographically encrypted messages
~h EXPRmessages which contain EXPR in the message header
~H EXPRmessages with a spam attribute matching EXPR
~i EXPRmessages which match EXPR in the “Message-ID” field
~kmessages which contain PGP key material
~L EXPRmessages either originated or received by EXPR
%L GROUPmessage either originated or received by any member of GROUP
~lmessages addressed to a known mailing list
~m [MIN]-[MAX]messages in the range MIN to MAX *)
~n [MIN]-[MAX]messages with a score in the range MIN to MAX *)
~Nnew messages
~Oold messages
~pmessages addressed to you (consults alternates)
~Pmessages from you (consults alternates)
~Qmessages which have been replied to
~r [MIN]-[MAX]messages with “date-received” in a Date range
~Rread messages
~s EXPRmessages having EXPR in the “Subject” field.
~Ssuperseded messages
~t EXPRmessages addressed to EXPR
~Ttagged messages
~umessages addressed to a subscribed mailing list
~Uunread messages
~vmessages part of a collapsed thread.
~Vcryptographically verified messages
~x EXPRmessages which contain EXPR in the “References” field
~X [MIN]-[MAX]messages with MIN to MAX attachments *)
~y EXPRmessages which contain EXPR in the “X-Label” field
~z [MIN]-[MAX]messages with a size in the range MIN to MAX *)
~=duplicated messages (see $duplicate_threads)
~$unreferenced messages (requires threaded view)
~(PATTERN)messages in threads +

Table 4.4. Pattern modifiers

Pattern modifierDescription
~Aall messages
~b EXPRmessages which contain EXPR in the message body
=b STRINGmessages which contain STRING in the message body. If IMAP is enabled, searches for STRING on the server, rather than downloading each message and searching it locally.
~B EXPRmessages which contain EXPR in the whole message
~c EXPRmessages carbon-copied to EXPR
%c GROUPmessages carbon-copied to any member of GROUP
~C EXPRmessages either to: or cc: EXPR
%C GROUPmessages either to: or cc: to any member of GROUP
~d [MIN]-[MAX]messages with “date-sent” in a Date range
~Ddeleted messages
~e EXPRmessages which contains EXPR in the “Sender” field
%e GROUPmessages which contain a member of GROUP in the “Sender” field
~Eexpired messages
~Fflagged messages
~f EXPRmessages originating from EXPR
%f GROUPmessages originating from any member of GROUP
~gcryptographically signed messages
~Gcryptographically encrypted messages
~h EXPRmessages which contain EXPR in the message header
~H EXPRmessages with a spam attribute matching EXPR
~i EXPRmessages which match EXPR in the “Message-ID” field
~kmessages which contain PGP key material
~L EXPRmessages either originated or received by EXPR
%L GROUPmessage either originated or received by any member of GROUP
~lmessages addressed to a known mailing list
~m [MIN]-[MAX]messages in the range MIN to MAX *)
~n [MIN]-[MAX]messages with a score in the range MIN to MAX *)
~Nnew messages
~Oold messages
~pmessages addressed to you (consults alternates)
~Pmessages from you (consults alternates)
~Qmessages which have been replied to
~r [MIN]-[MAX]messages with “date-received” in a Date range
~Rread messages
~s EXPRmessages having EXPR in the “Subject” field.
~Ssuperseded messages
~t EXPRmessages addressed to EXPR
~Ttagged messages
~umessages addressed to a subscribed mailing list
~Uunread messages
~vmessages part of a collapsed thread.
~Vcryptographically verified messages
~x EXPRmessages which contain EXPR in the “References” or “In-Reply-To” field
~X [MIN]-[MAX]messages with MIN to MAX attachments *)
~y EXPRmessages which contain EXPR in the “X-Label” field
~z [MIN]-[MAX]messages with a size in the range MIN to MAX *) **)
~=duplicated messages (see $duplicate_threads)
~$unreferenced messages (requires threaded view)
~(PATTERN)messages in threads containing messages matching PATTERN, e.g. all threads containing messages from you: ~(~P)

Where EXPR is a -regular expression. Special attention has to be -made when using regular expressions inside of patterns. Specifically, +regular expression. +

+*) The forms “<[MAX]”, “>[MIN]”, +“[MIN]-” and “-[MAX]” +are allowed, too. +

+**) The suffixes “K” and “M” are allowed to specify kilobyte and megabyte respectively. +

+Special attention has to be +payed when using regular expressions inside of patterns. Specifically, Mutt's parser for these patterns will strip one level of backslash (“\”), which is normally used for quoting. If it is your intention to use a backslash in the regular expression, you will need to use two backslashes -instead (“\\”). You can force mutt to treat EXPR as a simple string +instead (“\\”). You can force Mutt to treat EXPR as a simple string instead of a regular expression by using = instead of ˜ in the pattern name. For example, =b *.* will find all messages that contain the literal string “*.*”. Simple string matches are less powerful than regular expressions but can be considerably faster. This is especially true for IMAP folders, because string matches can be performed on the server instead of by fetching every message. IMAP treats =h specially: -it must be of the form "header: substring" and will not partially +it must be of the form “header: substring” and will not partially match header names. The substring part may be omitted if you simply wish to find messages containing a particular header without regard to its value.

-*) The forms “<[MAX]”, “>[MIN]”, -“[MIN]-” and “-[MAX]” -are allowed, too. -

2.1. Pattern Modifier

Note

-Note that patterns matching 'lists' of addresses (notably c, C, p, P and t) +Patterns matching lists of addresses (notably c, C, p, P and t) match if there is at least one match in the whole list. If you want to make sure that all elements of that list match, you need to prefix your pattern with “^”. This example matches all mails which only has recipients from Germany. -

+
Example 4.1. Matching all addresses in address lists
 ^~C \.de$
-
2.2. Simple Patterns

-Mutt supports two versions of so called “simple searches” which are
+

2.2. Simple Searches

+Mutt supports two versions of so called “simple searches”. These are issued if the query entered for searching, limiting and similar -operations does not seem to be a valid pattern (i.e. it does not contain +operations does not seem to contain a valid pattern modifier (i.e. it does not contain one of these characters: “˜”, “=” or “%”). If the query is supposed to contain one of these special characters, they must be escaped by prepending a backslash (“\”). @@ -169,37 +177,37 @@ If that is the case, Mutt will use the shown pattern modifier instead. If a keyword would conflict with your search keyword, you need to turn it into a regular expression to avoid matching the keyword table. For example, if you want to find all messages matching “flag” -(using $simple_search) +(using $simple_search) but don't want to match flagged messages, simply search for “[f]lag”.

Table 4.5. Simple search keywords

KeywordPattern modifier
all~A
.~A
^~A
del~D
flag~F
new~N
old~O
repl~Q
read~R
tag~T
unread~U

The second type of simple search is to build a complex search -pattern using $simple_search +pattern using $simple_search as a template. Mutt will insert your query properly quoted and search for the composed complex query. -

2.3. Complex Patterns

+

2.3. Nesting and Boolean Operators

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 and that have the word “elkins” in the “From” header +recipients and that have the word “elkins” in the “From” header field.

Mutt also recognizes the following operators to create more complex search patterns:

  • -! -- logical NOT operator +! — logical NOT operator

  • -| -- logical OR operator +| — logical OR operator

  • -() -- logical grouping operator +() — 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”. -

Example 4.1. Using boolean operators in patterns

+
Example 4.2. Using boolean operators in patterns
 !(~t mutt|~c mutt) ~f elkins
 


 Here is an example using white space in the regular expression (note
@@ -210,17 +218,16 @@ or “Ed +SomeoneElse”:
  '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'

Note

If a regular expression contains parenthesis, or a vertical bar -("|"), you must enclose the expression in double or single quotes since +("|"), you must enclose the expression in double or single quotes since those characters are also used to separate different parts of Mutt's pattern language. For example: ~f "me@(mutt\.org|cs\.hmc\.edu)" -

Without the quotes, the parenthesis wouldn't end. This would be separated to two OR'd patterns: ˜f me@(mutt\.org and cs\.hmc\.edu). They are never what you want. -

2.4. Searching by Date

+

2.4. Searching by Date

Mutt supports two types of dates, absolute and relative. -

-Absolute. Dates must be in DD/MM/YY format (month and year are +

2.4.1. Absolute Dates

+Dates must be in DD/MM/YY format (month and year are optional, defaulting to the current month and year). An example of a valid range of dates is: 

@@ -232,7 +239,7 @@ messages before the given date will be se
 date will be selected.  If you specify a single date with no dash (“-”),
 only messages sent on the given date will be selected.
 

-Error Margins.  You can add error margins to absolute dates.
+You can add error margins to absolute dates.
 An error margin is a sign (+ or -), followed by a digit, followed by
 one of the units in Table 4.6, “Date units”. As a special case, you can replace the
 sign by a “*” character, which is equivalent to giving identical plus and minus error margins.
@@ -241,15 +248,15 @@ Example: To select any messages two weeks around January 15, 2001,
 you'd use the following pattern:
 
 Limit to messages matching: ~d 15/1/2001*2w
-

-Relative.  This type of date is relative to the current date, and may
+

2.4.2. Relative Dates

+This type of date is relative to the current date, and may be specified as:

  • ->offset (messages older than offset units) +>offset for messages older than offset units

  • -<offset (messages newer than offset units) +<offset for messages newer than offset units

  • -=offset (messages exactly offset units old) +=offset for messages exactly offset units old

offset is specified as a positive number with one of the units from Table 4.6, “Date units”.

@@ -258,10 +265,10 @@ Example: to select messages less than 1 month old, you would use Limit to messages matching: ~d <1m

Note

All dates used when searching are relative to the -local time zone, so unless you change the setting of your $index_format to include a -%[...] format, these are not the dates shown +local time zone, so unless you change the setting of your $index_format to include a +%[...] format, these are not the dates shown in the main index. -

3. Using Tags

+

3. Using Tags

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 @@ -274,17 +281,17 @@ matching syntax.

Once you have tagged the desired messages, you can use the “tag-prefix” operator, which is the “;” (semicolon) key by default. -When the “tag-prefix” operator is used, the next operation will +When the “tag-prefix” operator is used, the next operation will be applied to all tagged messages if that operation can be used in that -manner. If the $auto_tag +manner. If the $auto_tag variable is set, the next operation applies to the tagged messages automatically, without requiring the “tag-prefix”.

-In macros or push commands, -you can use the “tag-prefix-cond” operator. If there are no tagged -messages, mutt will "eat" the rest of the macro to abort it's execution. -Mutt will stop "eating" the macro when it encounters the “end-cond” -operator; after this operator the rest of the macro will be executed as +In macros or push commands, +you can use the <tag-prefix-cond> operator. If there are no tagged +messages, Mutt will “eat” the rest of the macro to abort it's execution. +Mutt will stop “eating” the macro when it encounters the <end-cond> +operator; after this operator the rest of the macro will be executed as normal.

4. Using Hooks

A hook is a concept found in many other programs which allows you to @@ -293,37 +300,55 @@ you may wish to tailor your configuration based upon which mailbox you are reading, or to whom you are sending mail. In the Mutt world, a hook consists of a regular expression or pattern along with a -configuration option/command. See +configuration option/command. See:

for specific details on each type of hook available.

Note

If a hook changes configuration settings, these changes remain -effective until the end of the current mutt session. As this is generally -not desired, a default hook needs to be added before all other hooks to -restore configuration defaults. Here is an example with send-hook and the -my_hdr directive: -

Example 4.2. Combining send-hook and my_hdr

+effective until the end of the current Mutt session. As this is generally
+not desired, a “default” hook needs to be added before all
+other hooks  of that type to restore configuration defaults.
+

Example 4.3. Specifying a “default” hook

 send-hook . 'unmy_hdr From:'
 send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
-

4.1. Message Matching in Hooks

-Hooks that act upon messages (message-hook, reply-hook, -send-hook, send2-hook, save-hook, fcc-hook) are evaluated in a +


+In Example 4.3, “Specifying a default hook”, by default the value of +$from +and $realname +is not overridden. When sending messages either To: or Cc: +to <b@b.b>, the From: header is changed to +<c@c.c>. +

4.1. Message Matching in Hooks

+Hooks that act upon messages (message-hook, reply-hook, +send-hook, send2-hook, save-hook, fcc-hook) are evaluated in a slightly different manner. For the other types of hooks, a regular expression is sufficient. But in dealing with messages a finer grain of control is @@ -334,7 +359,7 @@ Mutt allows the use of the limiting or searching the mailbox, except that you are restricted to those -operators which match information mutt extracts from the header of +operators which match information Mutt extracts from the header of the message (i.e., from, to, cc, date, subject, etc.).

For example, if you wanted to set your return address based upon sending @@ -349,14 +374,14 @@ However, it is not required that you write the pattern to match using the full searching language. You can still specify a simple regular expression like the other hooks, in which case Mutt will translate your pattern into the full language, using the translation specified by the -$default_hook variable. The +$default_hook variable. The pattern is translated at the time the hook is declared, so the value of -$default_hook that is in effect +$default_hook that is in effect at that time will be used.

5. External Address Queries

Mutt supports connecting to external directory databases such as LDAP, -ph/qi, bbdb, or NIS through a wrapper script which connects to mutt -using a simple interface. Using the $query_command variable, you specify the wrapper +ph/qi, bbdb, or NIS through a wrapper script which connects to Mutt +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'"
@@ -374,7 +399,7 @@ me@cs.hmc.edu           Michael Elkins  mutt dude
 blong@fiction.net       Brandon Long    mutt and more
 roessler@does-not-exist.org        Thomas Roessler mutt pgp

-There are two mechanisms for accessing the query function of mutt. One +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 menu which will list the matching responses. From the query menu, you can select @@ -385,80 +410,107 @@ responses. The other mechanism for accessing the query function is for address completion, similar to the alias completion. In any prompt for address entry, you can use the <complete-query> function (default: ^T) to run a -query based on the current address you have typed. Like aliases, mutt +query based on the current address you have typed. Like aliases, Mutt will look for what you have typed back to the last space or comma. If -there is a single response for that query, mutt will expand the address -in place. If there are multiple responses, mutt will activate the query +there is a single response for that query, Mutt will expand the address +in place. If there are multiple responses, Mutt will activate the query menu. At the query menu, you can select one or more addresses to be added to the prompt.

6. Mailbox Formats

-Mutt supports reading and writing of four different mailbox formats: +Mutt supports reading and writing of four different local mailbox formats: mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to use a flag for different mailbox types. When creating new -mailboxes, Mutt uses the default specified with the $mbox_type variable. +mailboxes, Mutt uses the default specified with the +$mbox_type variable. A +short description of the formats follows.

-mbox. This is the most widely used mailbox format for UNIX. All +mbox. This is a widely used mailbox format for UNIX. All 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). -

-MMDF. This is a variant of the mbox format. Each message is -surrounded by lines containing “^A^A^A^A” (four control-A's). -

-MH. A radical departure from mbox and MMDF, a mailbox +“From_” line). The mbox format requires mailbox +locking, is prone to mailbox corruption with concurrently writing +clients or misinterpreted From_ lines. Depending on the +environment, new mail detection can be unreliable. Mbox folders are fast +to open and easy to archive. +

+MMDF. This is a variant of +the mbox format. Each message is surrounded by +lines containing “^A^A^A^A” (four +control-A's). The same problems as for mbox apply (also with finding the +right message separator as four control-A's may appear in message +bodies). +

+MH. A radical departure from mbox and MMDF, a mailbox consists of a directory and each message is stored in a separate file. The filename indicates the message number (however, this is may not correspond to the message number Mutt displays). Deleted messages are -renamed with a comma (,) prepended to the filename. Mutt +renamed with a comma (“,”) prepended to the filename. Mutt detects this type of mailbox by looking for either .mh_sequences -or .xmhcache (needed to distinguish normal directories from MH -mailboxes). -

-Maildir. The newest of the mailbox formats, used by the Qmail MTA (a +or .xmhcache files (needed to distinguish normal directories from MH +mailboxes). MH is more robust with concurrent clients writing the mailbox, +but still may suffer from lost flags; message corruption is less likely +to occur than with mbox/mmdf. It's usually slower to open compared to +mbox/mmdf since many small files have to be read (Mutt provides +Section 7.1, “Header Caching” to greatly speed this process up). +Depending on the environment, MH is not very disk-space efficient. +

+Maildir. The newest of the mailbox formats, used by the Qmail MTA (a replacement for sendmail). Similar to MH, except that it adds three subdirectories of the mailbox: tmp, new and cur. Filenames for the messages are chosen in such a way they are unique, even when two programs are writing the mailbox over NFS, which means that no file locking -is needed. +is needed and corruption is very unlikely. Maildir maybe +slower to open without caching in Mutt, it too is not very +disk-space efficient depending on the environment. Since no additional +files are used for metadata (which is embedded in the message filenames) +and Maildir is locking-free, it's easy to sync across different machines +using file-level synchronization tools.

7. Mailbox Shortcuts

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. +path or in path-related configuration variables. Note that these only +work at the beginning of a string.

  • -! -- refers to your $spoolfile (incoming) mailbox +! — refers to your $spoolfile (incoming) mailbox

  • -> -- refers to your $mbox file +> — refers to your $mbox file

  • -< -- refers to your $record file +< — refers to your $record file

  • -^ -- refers to the current mailbox +^ — refers to the current mailbox

  • -- or !! -- refers to the file you've last visited +- or !! — refers to the file you've last visited

  • -˜ -- refers to your home directory +˜ — refers to your home directory

  • -= or + -- refers to your $folder directory += or + — refers to your $folder directory

  • -@alias -- refers to the default save folder as determined by the address of the alias -

8. Handling Mailing Lists

+@alias — refers to the default save folder as determined by the address of the alias +

+For example, to store a copy of outgoing messages in the folder they +were composed in, +a folder-hook can +be used to set $record: +

+folder-hook . 'set record=^'

8. Handling Mailing Lists

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 does not have to be a mailing list, but that is what it is most often used for), and what lists you are subscribed to. This is -accomplished through the use of the lists and subscribe commands in your muttrc. +accomplished through the use of the lists and subscribe commands in your .muttrc.

Now that Mutt knows what your mailing lists are, it can do several things, the first of which is the ability to show the name of a list through which you received a message (i.e., of a subscribed list) in the index menu display. This is useful to distinguish between -personal and list mail in the same mailbox. In the $index_format variable, the escape “%L” -will return the string “To <list>” when “list” appears in the +personal and list mail in the same mailbox. In the $index_format variable, the expando “%L” +will print the string “To <list>” when “list” appears in the “To” field, and “Cc <list>” when it appears in the “Cc” -field (otherwise it returns the name of the author). +field (otherwise it prints 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 @@ -471,7 +523,7 @@ specified by Mail-Followup-To, see below).

Mutt also supports the Mail-Followup-To header. When you send a message to a list of recipients which includes one or several -subscribed mailing lists, and if the $followup_to option is set, mutt will generate +subscribed mailing lists, and if the $followup_to option is set, Mutt will generate a Mail-Followup-To header which contains all the recipients to whom you send this message, but not your address. This indicates that group-replies or list-replies (also known as “followups”) to this @@ -480,9 +532,9 @@ message, and not separately to you - you'll receive your copy through one of the mailing lists you are subscribed to.

Conversely, when group-replying or list-replying to a message which -has a Mail-Followup-To header, mutt will respect this header if -the $honor_followup_to configuration -variable is set. Using list-reply will in this case also make sure +has a Mail-Followup-To header, Mutt will respect this header if +the $honor_followup_to configuration +variable is set. Using list-reply will in this case also make sure that the reply goes to the mailing list, even if it's not specified in the list of recipients in the Mail-Followup-To.

Note

@@ -495,7 +547,7 @@ The other method some mailing list admins use is to generate a than the author of the message. This can create problems when trying to reply directly to the author in private, since most mail clients will automatically reply to the address given in the “Reply-To” -field. Mutt uses the $reply_to +field. Mutt uses the $reply_to variable to help decide which address to use. If set to ask-yes or ask-no, you will be prompted as to whether or not you would like to use the address given in @@ -505,15 +557,15 @@ present.

The “X-Label:” header field can be used to further identify mailing lists or list subject matter (or just to annotate messages -individually). The $index_format variable's “%y” and -“%Y” escapes can be used to expand “X-Label:” fields in the +individually). The $index_format variable's “%y” and +“%Y” expandos can be used to expand “X-Label:” fields in the index, and Mutt's pattern-matcher can match regular expressions to “X-Label:” fields with the “˜y” selector. “X-Label:” is not a standard message header field, but it can easily be inserted by procmail and other mail filtering agents.

-Lastly, Mutt has the ability to sort the mailbox into -threads. A thread is a group of messages which all relate to the same +Lastly, Mutt has the ability to sort the mailbox into +threads. A thread is a group of messages which all relate to the same subject. This is usually organized into a tree-like structure where a message and all of its replies are represented graphically. If you've ever used a threaded news client, this is the same concept. It makes dealing @@ -521,21 +573,21 @@ with large volume mailing lists easier because you can easily delete uninteresting threads and quickly find topics of value.

9. Handling multiple folders

Mutt supports setups with multiple folders, allowing all of them to -be monitored for new mail (see Section 14, “Monitoring incoming mail” for details). +be monitored for new mail (see Section 14, “Monitoring Incoming Mail” for details).

When in the index menu and being idle (also see -$timeout), Mutt periodically checks +$timeout), Mutt periodically checks for new mail in all folders which have been configured via the -mailboxes command. The interval depends on the folder +mailboxes command. The interval depends on the folder type: for local/IMAP folders it consults -$mail_check and -$pop_checkinterval +$mail_check and +$pop_checkinterval for POP folders.

Outside the index menu the directory browser supports checking for new mail using the <check-new> function which is unbound by default. Pressing TAB will bring up a -menu showing the files specified by the mailboxes command, +menu showing the files specified by the mailboxes command, and indicate which contain new messages. Mutt will automatically enter this mode when invoked from the command line with the -y option.

@@ -546,31 +598,31 @@ the bottom of the screen.

For the index, by default Mutt displays the number of mailboxes with new mail in the status bar, please refer to the -$index_format +$status_format variable for details.

When changing folders, Mutt fills the prompt with the first folder from the mailboxes list containing new mail (if any), pressing space will cycle through folders with new mail. -

10. Editing threads

+

10. Editing Threads

Mutt has the ability to dynamically restructure threads that are broken either by misconfigured software or bad behavior from some -correspondents. This allows to clean your mailboxes formats) from these +correspondents. This allows to clean your mailboxes from these annoyances which make it hard to follow a discussion. -

10.1. Linking threads

-Some mailers tend to "forget" to correctly set the "In-Reply-To:" and -"References:" headers when replying to a message. This results in broken +

10.1. Linking Threads

+Some mailers tend to “forget” to correctly set the “In-Reply-To:” and +“References:” headers when replying to a message. This results in broken discussions because Mutt has not enough information to guess the correct threading. You can fix this by tagging the reply, then moving to the parent message and using the <link-threads> function (bound to & by default). The -reply will then be connected to this "parent" message. +reply will then be connected to this parent message.

You can also connect multiple children at once, tagging them and using the -tag-prefix command (';') or the auto_tag option. -

10.2. Breaking threads

+<tag-prefix> command (';') or the $auto_tag option. +

10.2. Breaking Threads

On mailing lists, some people are in the bad habit of starting a new -discussion by hitting "reply" to any message from the list and changing +discussion by hitting “reply” to any message from the list and changing the subject to a totally unrelated one. You can fix such threads by using the <break-thread> function (bound by default to #), which will turn the subthread starting from the @@ -580,21 +632,21 @@ RFC1894 defines a set of MIME content types for relaying information about the status of electronic mail messages. These can be thought of as “return receipts.”

-To support DSN, there are two variables. $dsn_notify is used to request receipts for +To support DSN, there are two variables. $dsn_notify is used to request receipts for different results (such as failed message, message delivered, etc.). -$dsn_return requests how much +$dsn_return requests how much of your message should be returned with the receipt (headers or full message).

-When using $sendmail for mail +When using $sendmail for mail delivery, you need to use either Berkeley sendmail 8.8.x (or greater) a MTA supporting DSN command line options compatible to Sendmail: The -N and -R options can be used by the mail client to make requests as to what type of status messages should be returned. Please consider your MTA documentation whether DSN is supported.

-For SMTP delivery using $smtp_url, it depends on the -capabilities announced by the server whether mutt will attempt to +For SMTP delivery using $smtp_url, it depends on the +capabilities announced by the server whether Mutt will attempt to request DSN or not.

12. Start a WWW Browser on URLs

If a message contains URLs, it is efficient to get @@ -606,4 +658,28 @@ and the configuration commands: 

 macro index \cb |urlview\n
 macro pager \cb |urlview\n
-
Prev   Next
Chapter 3. Configuration Home Chapter 5. Mutt's MIME Support
+

13. Miscellany

+This section documents various features that fit nowhere else. +

+Address normalization +

+Mutt normalizes all e-mail addresses to the simplest form possible. If +an address contains a realname, the form +Joe User <joe@example.com> is used and the +pure e-mail address without angle brackets otherwise, i.e. just +joe@example.com. +

+This normalization affects all headers Mutt generates including aliases. +

+Initial folder selection +

+The folder Mutt opens at startup is determined as follows: the folder +specified in the $MAIL environment variable if +present. Otherwise, the value of $MAILDIR is taken +into account. If that isn't present either, Mutt takes the user's +mailbox in the mailspool as determined at compile-time (which may also +reside in the home directory). The +$spoolfile setting overrides +this selection. Highest priority has the mailbox given with the +-f command line option. +

Prev   Next
Chapter 3. Configuration Home Chapter 5. Mutt's MIME Support
diff --git a/doc/configuration.html b/doc/configuration.html index 9915532..0e89131 100644 --- a/doc/configuration.html +++ b/doc/configuration.html @@ -1,74 +1,78 @@ -Chapter 3. Configuration
Chapter 3. Configuration
Prev   Next

Chapter 3. Configuration

Table of Contents

1. Location of initialization files
2. Syntax of Initialization Files
3. Address groups
4. Defining/Using aliases
5. Changing the default key bindings
6. Defining aliases for character sets
7. Setting variables based upon mailbox
8. Keyboard macros
9. Using color and mono video attributes
10. Message header display
11. Alternative addresses
12. Mailing lists
13. Using Multiple spool mailboxes
14. Monitoring incoming mail
15. User defined headers
16. Specify default save mailbox
17. Specify default Fcc: mailbox when composing
18. Specify default save filename and default Fcc: mailbox at once
19. Change settings based upon message recipients
20. Change settings before formatting a message
21. Choosing the cryptographic key of the recipient
22. Adding key sequences to the keyboard buffer
23. Executing functions
24. Message Scoring
25. Spam detection
26. Setting and Querying Variables
26.1. Commands
26.2. User-defined variables
27. Reading initialization commands from another file
28. Removing hooks
29. Format Strings
29.1. Basic usage
29.2. Filters

1. Location of initialization files

+

Chapter 3. Configuration
Prev   Next

Chapter 3. Configuration

Table of Contents

1. Location of Initialization Files
2. Syntax of Initialization Files
3. Address Groups
4. Defining/Using Aliases
5. Changing the Default Key Bindings
6. Defining Aliases for Character Sets
7. Setting Variables Based Upon Mailbox
8. Keyboard Macros
9. Using Color and Mono Video Attributes
10. Message Header Display
10.1. Selecting Headers
10.2. Ordering Displayed Headers
11. Alternative Addresses
12. Mailing Lists
13. Using Multiple Spool Mailboxes
14. Monitoring Incoming Mail
15. User-Defined Headers
16. Specify Default Save Mailbox
17. Specify Default Fcc: Mailbox When Composing
18. Specify Default Save Filename and Default Fcc: Mailbox at Once
19. Change Settings Based Upon Message Recipients
20. Change Settings Before Formatting a Message
21. Choosing the Cryptographic Key of the Recipient
22. Adding Key Sequences to the Keyboard Buffer
23. Executing Functions
24. Message Scoring
25. Spam Detection
26. Setting and Querying Variables
26.1. Variable Types
26.2. Commands
26.3. User-Defined Variables
27. Reading Initialization Commands From Another File
28. Removing Hooks
29. Format Strings
29.1. Basic usage
29.2. Conditionals
29.3. Filters
29.4. Padding

1. Location of Initialization Files

While the default configuration (or “preferences”) make Mutt usable right out of the box, it is often desirable to tailor Mutt to suit your own tastes. When Mutt is first invoked, it will attempt to read the “system” configuration file (defaults set by your local -system administrator), unless the “-n” command line option is specified. This file is typically +system administrator), unless the “-n” command line option is specified. This file is typically /usr/local/share/mutt/Muttrc or /etc/Muttrc. Mutt will next look for a file named .muttrc in your home directory. If this file does not exist and your home directory has -a subdirectory named .mutt, mutt try to load a file named +a subdirectory named .mutt, Mutt tries to load a file named .mutt/muttrc.

.muttrc is the file where you will usually place your commands to configure Mutt.

-In addition, mutt supports version specific configuration files that are +In addition, Mutt supports version specific configuration files that are parsed instead of the default files as explained above. For instance, if your system has a Muttrc-0.88 file in the system configuration -directory, and you are running version 0.88 of mutt, this file will be +directory, and you are running version 0.88 of Mutt, this file will be sourced instead of the Muttrc file. The same is true of the user configuration file, if you have a file .muttrc-0.88.6 in your home -directory, when you run mutt version 0.88.6, it will source this file +directory, when you run Mutt version 0.88.6, it will source this file instead of the default .muttrc file. The version number is the -same which is visible using the “-v” command line switch or using the show-version key (default: +same which is visible using the “-v” command line switch or using the show-version key (default: V) from the index menu.

2. Syntax of Initialization Files

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 -(;). +(“;”).

Example 3.1. Multiple configuration commands per line

 set realname='Mutt user' ; ignore x-

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, +to the end of the line is ignored.

Example 3.2. Commenting configuration files

 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 +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 shell programs, namely that a single quote is used to specify a literal string (one that is not interpreted for shell variables or quoting with a backslash [see next paragraph]), while double quotes indicate a string for which should be evaluated. For example, backticks are evaluated inside of double -quotes, but not for single quotes. +quotes, but not for single quotes.

-\ quotes the next character, just as in shells such as bash and zsh. +“\” quotes the next character, just as in shells such as bash and zsh. For example, if want to put quotes “"” inside of a string, you can use “\” to force the next character to be a literal instead of interpreted character. @@ -79,30 +83,34 @@ set realname="Michael \"MuttDude\" Elkins" “\n” and “\r” have their usual C meanings of linefeed and carriage-return, respectively.

-A \ at the end of a line can be used to split commands over -multiple lines, provided that the split points don't appear in the -middle of command names. -

+A “\” at the end of a line can be used to split commands over +multiple lines as it “escapes” the line end, provided that the split points don't appear in the +middle of command names. Lines are first concatenated before +interpretation so that a multi-line can be commented by commenting out +the first line only. +

Example 3.4. Splitting long configuration commands over several lines

+set status_format="some very \
+long value split \
+over several lines"
+

It is also possible to substitute the output of a Unix command in an initialization file. This is accomplished by enclosing the command in -backticks (``). For example, -

Example 3.4. Using external command's output in configuration files

-my_hdr X-Operating-System: `uname -a`
-

-The output of the Unix command “uname -a” will be substituted before the +backticks (``). In Example 3.5, “Using external command's output in configuration files”, the output of the +Unix command “uname -a” will be substituted before the line is parsed. -

Note

Since initialization files are line oriented, only the first line of output from the Unix command will be substituted. -

-Both environment variables and mutt variables can be accessed by +

Example 3.5. Using external command's output in configuration files

+my_hdr X-Operating-System: `uname -a`
+

+Both environment variables and Mutt variables can be accessed by prepending “$” to the name of the variable. For example, -

Example 3.5. Using environment variables in configuration files

+
Example 3.6. Using environment variables in configuration files
 set record=+sent_on_$HOSTNAME
 


-will cause mutt to save outgoing messages to a folder named
-“sent_on_kremvax” if the environment variable HOSTNAME is set to
-“kremvax.” (See $record for
+will cause Mutt to save outgoing messages to a folder named
+“sent_on_kremvax” if the environment variable $HOSTNAME is set to
+“kremvax.” (See $record for
 details.)
 

 Mutt expands the variable when it is assigned, not when it is used. If
@@ -110,7 +118,7 @@ the value of a variable on the right-hand side of an assignment
 changes after the assignment, the variable on the left-hand side will
 not be affected.
 

-The commands understood by mutt are explained in the next paragraphs.
+The commands understood by Mutt are explained in the next paragraphs.
 For a complete list, see the command reference.
 

 All configuration files are expected to be in the current locale as
@@ -119,19 +127,21 @@ which doesn't have a default value since it's determined by Mutt at startup.
 If a configuration file is not encoded in the same character set the
 $config_charset
 variable should be used: all lines starting with the next are recoded
-from $config_charset to $charset.
+from $config_charset
+to $charset.
 

 This mechanism should be avoided if possible as it has the
 following implications:
 
  • These variables should be set early in a configuration
-file with $charset preceding $config_charset so Mutt
-know what character set to convert to.
  • If $config_charset is set, it should be set
+file with $charset preceding
+$config_charset so Mutt
+knows what character set to convert to.
  • If $config_charset is set, it should be set
 in each configuration file because the value is global and not
 per configuration file.
  • Because Mutt first recodes a line before it attempts to parse it,
 a conversion introducing question marks or other characters as
 part of errors (unconvertable characters, transliteration) may introduce syntax
 errors or silently change the meaning of certain tokens (e.g. inserting
-question marks into regular expressions).

3. Address groups

Usage:

group [ +question marks into regular expressions).

3. Address Groups

Usage:

group [ -group name ...] { @@ -140,7 +150,7 @@ question marks into regular expressions).

-addr expr -... }

ungroup [ +... }
ungroup [ -group name ...] { @@ -152,30 +162,30 @@ question marks into regular expressions).

-addr expr ... }

-group is used to directly add either addresses or +group is used to directly add either addresses or regular expressions to the specified group or groups. The different -categories of arguments to the group command can be +categories of arguments to the group command can be in any order. The flags -rx and -addr specify what the following strings (that cannot begin with a hyphen) should be interpreted as: either a regular expression or an email address, respectively.

These address groups can also be created implicitly by the -alias, lists, -subscribe and -alternates commands by specifying the +alias, lists, +subscribe and +alternates commands by specifying the optional -group option.

Once defined, these address groups can be used in patterns to search for and limit the display to messages matching a group.

-ungroup is used to remove addresses or regular +ungroup is used to remove addresses or regular expressions from the specified group or groups. The syntax is similar to -the group command, however the special character +the group command, however the special character * can be used to empty a group of all of its contents. -

4. Defining/Using aliases

Usage:

alias [ +

4. Defining/Using Aliases

Usage:

alias [ -group name ...] @@ -184,63 +194,61 @@ contents. address [ address -...]

+...]
unalias [ +-group +name +...] { +* + | +key +... }

It's usually very cumbersome to remember or type out the address of someone you are communicating with. Mutt allows you to create “aliases” which map a short string to a full address.

Note

If you want to create an alias for more than -one address, you must separate the addresses with a comma (“,”). +one address, you must separate the addresses with a comma (“,”).

The optional -group argument to -alias causes the aliased address(es) to be added to +alias causes the aliased address(es) to be added to the named group.

To remove an alias or aliases (“*” means all aliases): -

unalias [ --group -name -...] { -* - | -key -... }

+
 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.  Consequently, you can have multiple alias files, or
-you can have all aliases defined in your muttrc.
+in a special file.  The alias command can appear anywhere in
+a configuration file, as long as this file is sourced.  Consequently, you can have multiple alias files, or
+you can have all aliases defined in your .muttrc.
 

 On the other hand, the <create-alias>
 function can use only one file, the one pointed to by the $alias_file variable (which is
 ˜/.muttrc by default). This file is not special either,
 in the sense that Mutt will happily append aliases to any file, but in
-order for the new aliases to take effect you need to explicitly source this file too.
-

-For example:
-
Example 3.6. Configuring external alias files
+order for the new aliases to take effect you need to explicitly source this file too.
+
Example 3.7. Configuring external alias files
 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
+To use aliases, you merely use the alias at any place in Mutt where Mutt
 prompts for addresses, such as the To: or Cc: prompt.  You can
 also enter aliases in your editor at the appropriate headers if you have the
-$edit_headers variable set.
+$edit_headers variable set.
 

 In addition, at the various address prompts, you can use the tab character
 to expand a partial alias to the full alias.  If there are multiple matches,
-mutt will bring up a menu with the matching aliases.  In order to be
-presented with the full list of aliases, you must hit tab with out a partial
+Mutt will bring up a menu with the matching aliases.  In order to be
+presented with the full list of aliases, you must hit tab without a partial
 alias, such as at the beginning of the prompt or after a comma denoting
 multiple addresses.
 

 In the alias menu, you can select as many aliases as you want with the
 select-entry key (default: <Return>), and use the
 exit key (default: q) to return to the address prompt.
-
5. Changing the default key bindings
Usage:
bind   
+
5. Changing the Default Key Bindings
Usage:
bind   
 map
    
 key
@@ -258,10 +266,10 @@ This is not a real menu, but is used as a fallback for all of the other
 menus except for the pager and editor modes.  If a key is not defined in
 another menu, Mutt will look for a binding to use in this menu.  This allows
 you to bind a key to a certain function in multiple menus instead of having
-multiple bind statements to accomplish the same task.
+multiple bind statements to accomplish the same task.
 
alias

 The alias menu is the list of your personal aliases as defined in your
-muttrc.  It is the mapping from a short alias name to the full email
+.muttrc.  It is the mapping from a short alias name to the full email
 address(es) of the recipient(s).
 
attach

 The attachment menu is used to access the attachments on received messages.
@@ -288,7 +296,7 @@ The postpone menu is similar to the index menu, except is used when
 recalling a message the user was composing, but saved until later.
 
query

 The query menu is the browser for results returned by
-$query_command.
+$query_command.
 
mix

 The mixmaster screen is used to select remailer options for outgoing
 messages (if Mutt is compiled with Mixmaster support).
@@ -309,56 +317,59 @@ space (“ ”) or semi-colon (“function specifies which action to take when key is pressed.
 For a complete list of functions, see the reference.  The special function <noop> unbinds the specified key
 sequence.
-
6. Defining aliases for character sets 
Usage:
charset-hook   
+
6. Defining Aliases for Character Sets
Usage:
charset-hook   
 alias
    
 charset
- 
iconv-hook   
+ 
iconv-hook   
 charset
    
 local-charset
  

-The charset-hook command defines an alias for a character set.
+The charset-hook command defines an alias for a character set.
 This is useful to properly display messages which are tagged with a
-character set name not known to mutt.
+character set name not known to Mutt.
 

-The iconv-hook command defines a system-specific name for a
+The iconv-hook command defines a system-specific name for a
 character set.  This is helpful when your systems character
 conversion library insists on using strange, system-specific names
 for character sets.
-
7. Setting variables based upon mailbox
Usage:
folder-hook   
+
7. Setting Variables Based Upon Mailbox
Usage:
folder-hook   
 [!]regexp
    
 command
  

 It is often desirable to change settings based on which mailbox you are
-reading.  The folder-hook command provides a method by which you can execute
+reading.  The folder-hook command provides a method by which you can execute
 any configuration command.  regexp is a regular expression specifying
 in which mailboxes to execute command before loading.  If a mailbox
-matches multiple folder-hook's, they are executed in the order given in the
-muttrc.
+matches multiple folder-hooks, they are executed in the order given in the
+.muttrc.
 
Note

-If you use the “!” shortcut for $spoolfile at the beginning of the pattern, you must place it
+If you use the “!” shortcut for $spoolfile at the beginning of the pattern, you must place it
 inside of double or single quotes in order to distinguish it from the
 logical not operator for the expression.
 
Note

 Settings are not restored when you leave the mailbox.
 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
-

+
+
+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 default command, use the
-pattern “.” before other folder-hooks adjusting a value on a per-folder basis
-because folder-hooks are evaluated in the order given in the configuration file.
-The following example will set the sort variable
+pattern “.” before other folder-hooks adjusting a value on a per-folder basis
+because folder-hooks are evaluated in the order given in the
+configuration file.
+

+The following example will set the sort variable
 to date-sent for all folders but to threads
 for all folders containing “mutt” in their name.
-
Example 3.7. Setting sort method based on mailbox name
-folder-hook . set sort=date-sent
-folder-hook mutt set sort=threads
-

8. Keyboard macros
Usage:
macro   
+
Example 3.8. Setting sort method based on mailbox name
+folder-hook . "set sort=date-sent"
+folder-hook mutt "set sort=threads"
+

8. Keyboard Macros
Usage:
macro   
 menu
    
 key
@@ -379,13 +390,13 @@ commas. Whitespace may not be used in between the menu arguments and the
 commas separating them.
 

 key and sequence are expanded by the same rules as the
-key bindings with some additions.  The
+key bindings with some additions.  The
 first is that control characters in sequence can also be specified
 as ^x.  In order to get a caret (“^”) you need to use
 ^^.  Secondly, to specify a certain key such as up
 or to invoke a function directly, you can use the format
 <key name> and <function name>.  For a listing of key
-names see the section on key bindings.  Functions
+names see the section on key bindings.  Functions
 are listed in the reference.
 

 The advantage with using function names directly is that the macros will
@@ -395,17 +406,17 @@ and portable, and also facilitates defining of macros in files used by more
 than one user (e.g., the system Muttrc).
 

 Optionally you can specify a descriptive text after sequence,
-which is shown in the help screens.
+which is shown in the help screens if they contain a description.
 
Note

 Macro definitions (if any) listed in the help screen(s), are
 silently truncated at the screen width, and are not wrapped.
-
9. Using color and mono video attributes
Usage:
color   
+
9. Using Color and Mono Video Attributes
Usage:
color   
 object
    
 foreground
    
 background
- 
color  { 
+ 
color  { 
 header
   |   
 body
@@ -415,7 +426,7 @@ silently truncated at the screen width, and are not wrapped.
 background
    
 regexp
- 
color   
+ 
color   
 index
    
 foreground
@@ -423,16 +434,20 @@ silently truncated at the screen width, and are not wrapped.
 background
    
 pattern
- 
uncolor   
+ 
uncolor  { 
 index
-  { 
+  |   
+header
+  |   
+body
+ } { 
 *
   |   
 pattern
 ... }

 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 information), you
-must specify both a foreground color and a background color (it is not
+must specify both a foreground color and a background color (it is not
 possible to only specify one or the other).
 

 header and body match regexp
@@ -440,7 +455,7 @@ in the header/body of a message, index ma
 (see Section 2, “Patterns: Searching, Limiting and Tagging”) in the message index.
 

 object can be one of:
-
  • attachment
  • bold (hiliting bold patterns in the body of messages)
  • error (error messages printed by Mutt)
  • hdrdefault (default color of the message header in the pager)
  • indicator (arrow or bar used to indicate the current item in a menu)
  • markers (the “+” markers at the beginning of wrapped lines in the pager)
  • message (informational messages)
  • normal
  • quoted (text matching $quote_regexp in the body of a message)
  • quoted1, quoted2, ..., quotedN (higher levels of quoting)
  • search (hiliting of words in the pager)
  • signature
  • status (mode lines used to display info about the mailbox or message)
  • tilde (the “˜” used to pad blank lines in the pager)
  • tree (thread tree drawn in the message index and attachment menu)
  • underline (hiliting underlined patterns in the body of messages)

+
  • attachment
  • bold (hiliting bold patterns in the body of messages)
  • error (error messages printed by Mutt)
  • hdrdefault (default color of the message header in the pager)
  • indicator (arrow or bar used to indicate the current item in a menu)
  • markers (the “+” markers at the beginning of wrapped lines in the pager)
  • message (informational messages)
  • normal
  • quoted (text matching $quote_regexp in the body of a message)
  • quoted1, quoted2, ..., quotedN (higher levels of quoting)
  • search (hiliting of words in the pager)
  • signature
  • status (mode lines used to display info about the mailbox or message)
  • tilde (the “˜” used to pad blank lines in the pager)
  • tree (thread tree drawn in the message index and attachment menu)
  • underline (hiliting underlined patterns in the body of messages)

 foreground and background can be one of the following:
 
  • white
  • black
  • green
  • magenta
  • blue
  • cyan
  • yellow
  • red
  • default
  • colorx

 foreground can optionally be prefixed with the keyword bright to make
@@ -449,7 +464,7 @@ the foreground color boldfaced (e.g., brightred).
 If your terminal supports it, the special keyword default can be
 used as a transparent color.  The value brightdefault is also valid.
 If Mutt is linked against the S-Lang library, you also need to set
-the COLORFGBG environment variable to the default colors of your
+the $COLORFGBG environment variable to the default colors of your
 terminal for this to work; for example (for Bourne-like shells):
 
 set COLORFGBG="green;black"
@@ -459,24 +474,24 @@ The S-Lang library requires you to use th
 and brown keywords instead of white and yellow when
 setting this variable.
 
Note

-The uncolor command can be applied to the index object only.  It
-removes entries from the list. You must 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.
+The uncolor command can be applied to the index, header and body objects only.  It
+removes entries from the list. You must 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 list of all entries.
 

 Mutt also recognizes the keywords color0, color1, …,
-colorN-1 (N being the number of colors supported
+colorN-1 (N being the number of colors supported
 by your terminal).  This is useful when you remap the colors for your
 display (for example by changing the color associated with color2
 for your xterm), since color names may then lose their normal meaning.
-

+

 If your terminal does not support color, it is still possible change the video
-attributes through the use of the “mono” command:
-
Usage:
mono   
+attributes through the use of the “mono” command. Usage:
+
mono   
 object
    
 attribute
- 
mono  { 
+ 
mono  { 
 header
   |   
 body
@@ -484,26 +499,30 @@ attributes through the use of the “mono” command:
 attribute
    
 regexp
- 
mono   
+ 
mono   
 index
    
 attribute
    
 pattern
- 
unmono   
+ 
unmono  { 
 index
-  { 
+  |   
+header
+  |   
+body
+ } { 
 *
   |   
 pattern
 ... }

-For object, see the color command. attribute
+For object, see the color command. attribute
 can be one of the following:
-
  • none
  • bold
  • underline
  • reverse
  • standout
10. Message header display
Usage:
ignore   
+
  • none
  • bold
  • underline
  • reverse
  • standout
10. Message Header Display
10.1. Selecting Headers
Usage:
ignore   
 pattern
   [
 pattern
-...]
unignore  { 
+...]
unignore  { 
 *
   |   
 pattern
@@ -521,38 +540,36 @@ The “unignore” command will make Mutt display hea
 For example, if you do “ignore x-” it is possible to “unignore x-mailer”.
 

 “unignore *” will remove all tokens from the ignore list.
-

-For example:
-
Example 3.8. Header weeding
+
Example 3.9. Header weeding
 # 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:
-

Usage:
hdr_order   
+

10.2. Ordering Displayed Headers
Usage:
hdr_order   
 header
   [
 header
-...]
unhdr_order  { 
+...]
unhdr_order  { 
 *
   |   
 header
 ... }

-With the hdr_order command you can specify an order in
-which mutt will attempt to present these headers to you when viewing messages.
+With the hdr_order command you can specify an order in
+which Mutt will attempt to present these headers to you when viewing messages.
 

-“unhdr_order *” will clear all previous headers from the order list,
+“unhdr_order *” will clear all previous headers from the order list,
 thus removing the header order effects set by the system-wide startup file.
-
Example 3.9. Configuring header display order
+
Example 3.10. Configuring header display order
 hdr_order From Date: From: To: Cc: Subject:
-

11. Alternative addresses
Usage:
alternates  [
+

11. Alternative Addresses

Usage:

alternates [ -group name ...] regexp [ regexp -...]

unalternates [ +...]
unalternates [ -group name ...] { @@ -560,17 +577,17 @@ hdr_order From Date: From: To: Cc: Subject: | regexp ... }

-With various functions, mutt will treat messages differently, +With various functions, Mutt will treat messages differently, depending on whether you sent them or whether you received them from someone else. For instance, when replying to a message that you -sent to a different party, mutt will automatically suggest to send -the response to the original message's recipients -- responding to -yourself won't make much sense in many cases. (See $reply_to.) +sent to a different party, Mutt will automatically suggest to send +the response to the original message's recipients — responding to +yourself won't make much sense in many cases. (See $reply_to.)

Many users receive e-mail under a number of different addresses. To -fully use mutt's features here, the program must be able to +fully use Mutt's features here, the program must be able to recognize what e-mail addresses you receive mail under. That's the -purpose of the alternates command: It takes a list of regular +purpose of the alternates command: It takes a list of regular expressions, each of which can identify an address under which you receive e-mail.

@@ -580,7 +597,7 @@ as possible to avoid mismatches. For example, if you specify: 

 alternates user@example

-mutt will consider “some-user@example” as +Mutt will consider “some-user@example” as being your address, too which may not be desired. As a solution, in such cases addresses should be specified as: 

@@ -589,40 +606,40 @@ alternates '^user@example$'
 The -group flag causes all of the subsequent regular expressions
 to be added to the named group.
 

-The unalternates command can be used to write exceptions to
-alternates patterns. If an address matches something in an
-alternates command, but you nonetheless do not think it is
-from you, you can list a more precise pattern under an unalternates
+The unalternates command can be used to write exceptions to
+alternates patterns. If an address matches something in an
+alternates command, but you nonetheless do not think it is
+from you, you can list a more precise pattern under an unalternates
 command.
 

-To remove a regular expression from the alternates list, use the
-unalternates command with exactly the same regexp.
-Likewise, if the regexp for an alternates command matches
-an entry on the unalternates list, that unalternates
-entry will be removed. If the regexp for unalternates
-is “*”, all entries on alternates will be removed.
-

12. Mailing lists

Usage:

lists [ +To remove a regular expression from the alternates list, use the +unalternates command with exactly the same regexp. +Likewise, if the regexp for an alternates command matches +an entry on the unalternates list, that unalternates +entry will be removed. If the regexp for unalternates +is “*”, all entries on alternates will be removed. +

12. Mailing Lists

Usage:

lists [ -group name ...] regexp [ regexp -...]

unlists [ +...]
unlists [ -group name ...] { * | regexp -... }

subscribe [ +... }
subscribe [ -group name ...] regexp [ regexp -...]

unsubscribe [ +...]
unsubscribe [ -group name ...] { @@ -632,8 +649,15 @@ is “*”, all entries

Mutt has a few nice features for handling mailing lists. In order to take advantage of them, you must specify which addresses belong to mailing lists, and which mailing -lists you are subscribed to. Once you have done this, the <list-reply> function will work for all known lists. -Additionally, when you send a message to a subscribed list, mutt will +lists you are subscribed to. Mutt also has limited support for +auto-detecting mailing lists: it supports parsing +mailto: links in the common +List-Post: header which has the same effect as +specifying the list address via the lists command +(except the group feature). Once you have done this, the +<list-reply> +function will work for all known lists. +Additionally, when you send a message to a subscribed list, Mutt will add a Mail-Followup-To header to tell other users' mail user agents not to send copies of replies to your personal address.

Note

@@ -641,30 +665,32 @@ The Mail-Followup-To header is a non-standard extension which is not supported by all mail user agents. Adding it is not bullet-proof against receiving personal CCs of list messages. Also note that the generation of the Mail-Followup-To header is controlled by the -$followup_to -configuration variable. +$followup_to +configuration variable since it's common practice on some mailing lists +to send Cc upons replies (which is more a group- than a list-reply).

More precisely, Mutt maintains lists of patterns for the addresses of known and subscribed mailing lists. Every subscribed mailing -list is known. To mark a mailing list as known, use the “lists” -command. To mark it as subscribed, use “subscribe”. +list is known. To mark a mailing list as known, use the list +command. To mark it as subscribed, use subscribe.

-You can use regular expressions with both commands. To mark all -messages sent to a specific bug report's address on mutt's bug +You can use regular expressions with both commands. To mark all +messages sent to a specific bug report's address on Debian's bug tracking system as list mail, for instance, you could say -“subscribe [0-9]*@bugs.guug.de”. Often, it's sufficient to just -give a portion of the list's e-mail address. +

+subscribe [0-9]*.*@bugs.debian.org

+as it's often, it's sufficient to just give a portion of the list's e-mail address.

Specify as much of the address as you need to to remove ambiguity. For example, if you've subscribed to the Mutt mailing list, you will receive mail -addressed to mutt-users@mutt.org. So, to tell Mutt -that this is a mailing list, you could add “lists mutt-users@” to your -initialization file. To tell mutt that you are subscribed to it, -add “subscribe mutt-users” to your initialization file instead. +addressed to mutt-users@mutt.org. So, to tell Mutt +that this is a mailing list, you could add lists mutt-users@ to your +initialization file. To tell Mutt that you are subscribed to it, +add subscribe mutt-users to your initialization file instead. If you also happen to get mail from someone whose address is -mutt-users@example.com, you could use -“lists ^mutt-users@mutt\\.org$” -or “subscribe ^mutt-users@mutt\\.org$” to +mutt-users@example.com, you could use +lists ^mutt-users@mutt\\.org$ +or subscribe ^mutt-users@mutt\\.org$ to match only mail from the actual list.

The -group flag adds all of the subsequent regular expressions @@ -675,8 +701,8 @@ known and subscribed mailing-lists. Use “unlists * tokens.

To remove a mailing list from the list of subscribed mailing lists, -but keep it on the list of known mailing lists, use “unsubscribe”. -

13. Using Multiple spool mailboxes

Usage:

mbox-hook +but keep it on the list of known mailing lists, use unsubscribe. +

13. Using Multiple Spool Mailboxes

Usage:

mbox-hook [!]pattern mailbox @@ -690,11 +716,11 @@ read. Unlike some of the other hook commands, only the first matching pattern is used (it is not possible to save read mail in more than a single mailbox). -

14. Monitoring incoming mail

Usage:

mailboxes +

14. Monitoring Incoming Mail

Usage:

mailboxes mailbox [ mailbox -...]

unmailboxes { +...]
unmailboxes { * | mailbox @@ -705,7 +731,7 @@ which will be checked for new messages periodically. folder can either be a local file or directory (Mbox/Mmdf or Maildir/Mh). If Mutt was built with POP and/or IMAP support, folder can also be a POP/IMAP folder -URL. The URL syntax is described in Section 1.2, “URL syntax”, +URL. The URL syntax is described in Section 1.2, “URL Syntax”, POP and IMAP are described in Section 3, “POP3 Support” and Section 4, “IMAP Support” respectively.

@@ -718,13 +744,13 @@ The “unmailboxes” command is used to remove a tok of folders which receive mail. Use “unmailboxes *” to remove all tokens.

Note

-The folders in the mailboxes command are resolved when +The folders 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 affects these characters (like $folder and $spoolfile) -should be set before the mailboxes command. If +definition that affects these characters (like $folder and $spoolfile) +should be set before the mailboxes command. If none of these shorcuts are used, a local path should be absolute as -otherwise mutt tries to find it relative to the directory -from where mutt was started which may not always be desired. +otherwise Mutt tries to find it relative to the directory +from where Mutt was started which may not always be desired.

For Mbox and Mmdf folders, new mail is detected by comparing access and/or modification times of files: Mutt assumes a folder has new mail if it wasn't @@ -737,42 +763,42 @@ access time update support.

In cases where new mail detection for Mbox or Mmdf folders appears to be unreliable, the -$check_mbox_size +$check_mbox_size option can be used to make Mutt track and consult file sizes for new -mail detection instead. -

15. User defined headers

Usage:

my_hdr +mail detection instead which won't work for size-neutral changes. +

15. User-Defined Headers

Usage:

my_hdr string -

unmy_hdr { +
unmy_hdr { * | field ... }

-The my_hdr command allows you to create your own header -fields which will be added to every message you send. +The my_hdr command allows you to create your own header +fields which will be added to every message you send and appear in the +editor if $edit_headers is set.

For example, if you would like to add an “Organization:” header field to -all of your outgoing messages, you can put the command -

Example 3.10. Defining custom headers

+all of your outgoing messages, you can put the command something like
+shown in Example 3.11, “Defining custom headers” in your .muttrc.
+
Example 3.11. Defining custom headers
 my_hdr Organization: A Really Big Company, Anytown, USA
-


-in your .muttrc.
-
Note

+

Note

Space characters are not allowed between the keyword and the colon (“:”). The standard for electronic mail (RFC2822) says that space is illegal there, so Mutt enforces the rule.

If you would like to add a header field to a single message, you should -either set the $edit_headers variable, +either set the $edit_headers variable, or use the <edit-headers> function (default: “E”) in the compose 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 +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
-

16. Specify default save mailbox

Usage:

save-hook +

16. Specify Default Save Mailbox

Usage:

save-hook [!]pattern mailbox @@ -783,11 +809,9 @@ matches pattern, see

To provide more flexibility and good defaults, Mutt applies the -expandos of $index_format to +expandos of $index_format to mailbox after it was expanded. -

-Examples: -

Example 3.11. Using %-expandos in save-hook

+
Example 3.12. Using %-expandos in save-hook
 # default: save all to ~/Mail/<author name>
 save-hook . ~/Mail/%F
 
@@ -797,46 +821,44 @@ save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
 # save from aol.com to $folder/spam
 save-hook aol\\.com$ +spam
 


-Also see the fcc-save-hook command.
-

17. Specify default Fcc: mailbox when composing

Usage:

fcc-hook +Also see the fcc-save-hook command. +

17. Specify Default Fcc: Mailbox When Composing

Usage:

fcc-hook [!]pattern mailbox

This command is used to save outgoing mail in a mailbox other than -$record. Mutt searches the initial list of +$record. Mutt searches the initial list of message recipients for the first matching regexp and uses mailbox as the default Fcc: mailbox. If no match is found the message will be saved -to $record mailbox. +to $record mailbox.

To provide more flexibility and good defaults, Mutt applies the -expandos of $index_format to +expandos of $index_format to mailbox after it was expanded.

See Message Matching in Hooks for information on the exact format of pattern. -

-Example: fcc-hook [@.]aol\\.com$ +spammers -

-The above will save a copy of all messages going to the aol.com domain to -the `+spammers' mailbox by default. Also see the fcc-save-hook command. -

18. Specify default save filename and default Fcc: mailbox at once

Usage:

fcc-save-hook +

fcc-hook [@.]aol\\.com$ +spammers

+...will save a copy of all messages going to the aol.com domain to +the `+spammers' mailbox by default. Also see the fcc-save-hook command. +

18. Specify Default Save Filename and Default Fcc: Mailbox at Once

Usage:

fcc-save-hook [!]pattern mailbox

-This command is a shortcut, equivalent to doing both a fcc-hook -and a save-hook with its arguments, +This command is a shortcut, equivalent to doing both a fcc-hook +and a save-hook with its arguments, including %-expansion on mailbox according -to $index_format. -

19. Change settings based upon message recipients

Usage:

reply-hook +to $index_format. +

19. Change Settings Based Upon Message Recipients

Usage:

reply-hook [!]pattern command -

send-hook +
send-hook [!]pattern command -

send2-hook +
send2-hook [!]pattern command @@ -846,38 +868,40 @@ upon recipients of the message. pattern the message, see Message Matching in Hooks for details. command is executed when pattern matches.

-reply-hook is matched against the message you are replying to, -instead of the message you are sending. send-hook is +reply-hook is matched against the message you are replying to, +instead of the message you are sending. send-hook is matched against all messages, both new and replies.

Note

-reply-hooks are matched before the send-hook, regardless +reply-hooks are matched before the send-hook, regardless of the order specified in the user's configuration file.

-send2-hook is matched every time a message is changed, either +send2-hook is matched every time a message is changed, either by editing it, or by using the compose menu to change its recipients -or subject. send2-hook is executed after send-hook, and -can, e.g., be used to set parameters such as the $sendmail variable depending on the message's sender +or subject. send2-hook is executed after send-hook, and +can, e.g., be used to set parameters such as the $sendmail variable depending on the message's sender address.

-For each type of send-hook or reply-hook, when multiple matches -occur, commands are executed in the order they are specified in the muttrc +For each type of send-hook or reply-hook, when multiple matches +occur, commands are executed in the order they are specified in the .muttrc (for that type of hook).

-Example: send-hook mutt "set mime_forward 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 +$attribution, $signature and $locale variables in order to change the language of the attributions and signatures based upon the recipients.

Note

-send-hook's are only executed once after getting the initial -list of recipients. Adding a recipient after replying or editing the -message will not cause any send-hook to be executed. Also note that -my_hdr commands which modify recipient headers, or the message's -subject, don't have any effect on the current message when executed -from a send-hook. -

20. Change settings before formatting a message

Usage:

message-hook +send-hook's are only executed once after getting the +initial list of recipients. Adding a recipient after replying or +editing the message will not cause any send-hook to be executed, +similarily if $autoedit is set +(as then the initial list of recipients is empty). Also note that my_hdr commands which +modify recipient headers, or the message's subject, don't have any +effect on the current message when executed from a +send-hook. +

20. Change Settings Before Formatting a Message

Usage:

message-hook [!]pattern command @@ -886,7 +910,7 @@ This command can be used to execute arbitrary configuration commands before viewing or formatting a message based upon information about the message. command is executed if the pattern matches the message to be displayed. When multiple matches occur, commands are executed in the order -they are specified in the muttrc. +they are specified in the .muttrc.

See Message Matching in Hooks for information on the exact format of pattern. @@ -895,7 +919,7 @@ Example: 

 message-hook ~A 'set pager=builtin'
 message-hook '~f freshmeat-news' 'set pager="less \"+/^  subject: .*\""'
-

21. Choosing the cryptographic key of the recipient

Usage:

crypt-hook +

21. Choosing the Cryptographic Key of the Recipient

Usage:

crypt-hook pattern keyid @@ -904,76 +928,77 @@ When encrypting messages with PGP/GnuPG or OpenSSL, you may want to associate a key with a given e-mail address automatically, either because the recipient's public key can't be deduced from the destination address, or because, for some reasons, you need to override the key Mutt would -normally use. The crypt-hook command provides a +normally use. The crypt-hook command provides a method by which you can specify the ID of the public key to be used when encrypting messages to a certain recipient.

The meaning of keyid is to be taken broadly in this context: You can either put a numerical key ID here, an e-mail address, or even just a real name. -

22. Adding key sequences to the keyboard buffer

Usage:

push +

22. Adding Key Sequences to the Keyboard Buffer

Usage:

push string

This command adds the named string to the keyboard buffer. The string may contain control characters, key names and function names like the sequence -string in the macro command. You may use it to +string in the macro command. You may use it to automatically run a sequence of commands at startup, or when entering -certain folders. For example, the following command will automatically -collapse all threads when entering a folder: -

Example 3.12. Embedding push in folder-hook

+certain folders. For example, Example 3.13, “Embedding push in folder-hook”
+shows how to automatically collapse all threads when entering a folder.
+
Example 3.13. Embedding push in folder-hook
 folder-hook . 'push <collapse-all>'
-

23. Executing functions

Usage:

exec +


23. Executing Functions

Usage:

exec function [ function ...]

This command can be used to execute any function. Functions are listed in the function reference. -“exec function” is equivalent to “push <function>”. +“execfunction” is equivalent to +“push <function>”.

24. Message Scoring

Usage:

score pattern value -

unscore { +
unscore { * | pattern ... }

-The score commands adds value to a message's score if pattern +The score commands adds value to a message's score if pattern matches it. pattern is a string in the format described in the patterns section (note: For efficiency reasons, patterns which scan information not available in the index, such as ˜b, ˜B or ˜h, may not be used). value is a positive or negative integer. A message's final score is the sum total of all -matching score entries. However, you may optionally prefix value with -an equal sign (=) to cause evaluation to stop at a particular entry if there is +matching score entries. However, you may optionally prefix value with +an equal sign (“=”) to cause evaluation to stop at a particular entry if there is a match. Negative final scores are rounded up to 0.

-The unscore command removes score entries from the list. You must -specify the same pattern specified in the score command for it to be +The unscore command removes score entries from the list. You must +specify the same pattern specified in the score command for it to be removed. The pattern “*” is a special token which means to clear the list of all score entries. -

25. Spam detection

Usage:

spam +

25. Spam Detection

Usage:

spam pattern format -

nospam { +
nospam { * | pattern }

Mutt has generalized support for external spam-scoring filters. -By defining your spam patterns with the spam and nospam +By defining your spam patterns with the spam and nospam commands, you can limit, search, and sort your mail based on its spam attributes, as determined by the external filter. You also can display the spam attributes in your index -display using the %H selector in the $index_format variable. (Tip: try %?H?[%H] ? +display using the %H selector in the $index_format variable. (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a given message.)

Your first step is to define your external filter's spam patterns using -the spam command. pattern should be a regular expression +the spam command. pattern should be a regular expression that matches a header in a mail message. If any message in the mailbox matches this regular expression, it will receive a “spam tag” or -“spam attribute” (unless it also matches a nospam pattern -- see +“spam attribute” (unless it also matches a nospam pattern — see below.) The appearance of this attribute is entirely up to you, and is governed by the format parameter. format can be any static text, but it also can include back-references from the pattern @@ -981,96 +1006,134 @@ expression. (A regular expression “back-reference sub-expression contained within parentheses.) %1 is replaced with the first back-reference in the regex, %2 with the second, etc.

+To match spam tags, mutt needs the corresponding header information +which is always the case for local and POP folders but not for IMAP in +the default configuration. Depending on the spam header to be analyzed, +$imap_headers may need +to be adjusted. +

If you're using multiple spam filters, a message can have more than -one spam-related header. You can define spam patterns for each +one spam-related header. You can define spam patterns for each filter you use. If a message matches two or more of these patterns, and -the $spam_separator variable is set to a string, then the +the $spam_separator variable is set to a string, then the message's spam tag will consist of all the format strings joined -together, with the value of $spam_separator separating +together, with the value of $spam_separator separating them.

-For example, suppose I use DCC, SpamAssassin, and PureMessage. I might -define these spam settings: -

Example 3.13. Configuring spam detection

+For example, suppose one uses DCC, SpamAssassin, and PureMessage, then
+the configuration might look like in Example 3.14, “Configuring spam detection”.
+
Example 3.14. Configuring spam detection
 spam "X-DCC-.*-Metrics:.*(....)=many"         "90+/DCC-%1"
 spam "X-Spam-Status: Yes"                     "90+/SA"
 spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
 set spam_separator=", "
 


-If I then received a message that DCC registered with “many” hits
+If then a message is received that DCC registered with “many” hits
 under the “Fuz2” checksum, and that PureMessage registered with a
 97% probability of being spam, that message's spam tag would read
 90+/DCC-Fuz2, 97/PM. (The four characters before “=many” in a
-DCC report indicate the checksum used -- in this case, “Fuz2”.)
+DCC report indicate the checksum used — in this case, “Fuz2”.)
 

-If the $spam_separator variable is unset, then each
+If the $spam_separator variable is unset, then each
 spam pattern match supersedes the previous one. Instead of getting
 joined format strings, you'll get only the last one to match.
 

 The spam tag is what will be displayed in the index when you use
-%H in the $index_format variable. It's also the
+%H in the $index_format variable. It's also the
 string that the ˜H pattern-matching expression matches against for
 <search> and <limit> functions. And it's what sorting by spam
 attribute will use as a sort key.
 

 That's a pretty complicated example, and most people's actual
 environments will have only one spam filter. The simpler your
-configuration, the more effective mutt can be, especially when it comes
+configuration, the more effective Mutt can be, especially when it comes
 to sorting.
 

-Generally, when you sort by spam tag, mutt will sort lexically --
+Generally, when you sort by spam tag, Mutt will sort lexically —
 that is, by ordering strings alphanumerically. However, if a spam tag
-begins with a number, mutt will sort numerically first, and lexically
+begins with a number, Mutt will sort numerically first, and lexically
 only when two numbers are equal in value. (This is like UNIX's
-sort -n.) A message with no spam attributes at all -- that is, one
-that didn't match any of your spam patterns -- is sorted at
+sort -n.) A message with no spam attributes at all — that is, one
+that didn't match any of your spam patterns — is sorted at
 lowest priority. Numbers are sorted next, beginning with 0 and ranging
 upward. Finally, non-numeric strings are sorted, with “a” taking lower
 priority than “z”. Clearly, in general, sorting by spam tags is most
 effective when you can coerce your filter to give you a raw number. But
-in case you can't, mutt can still do something useful.
+in case you can't, Mutt can still do something useful.
 

-The nospam command can be used to write exceptions to spam
-patterns. If a header pattern matches something in a spam command,
+The nospam command can be used to write exceptions to spam
+patterns. If a header pattern matches something in a spam command,
 but you nonetheless do not want it to receive a spam tag, you can list a
-more precise pattern under a nospam command.
+more precise pattern under a nospam command.
 

-If the pattern given to nospam is exactly the same as the
-pattern on an existing spam list entry, the effect will be to
+If the pattern given to nospam is exactly the same as the
+pattern on an existing spam list entry, the effect will be to
 remove the entry from the spam list, instead of adding an exception.
-Likewise, if the pattern for a spam command matches an entry
-on the nospam list, that nospam entry will be removed. If the
-pattern for nospam is “*”, all entries on both lists
-will be removed. This might be the default action if you use spam
-and nospam in conjunction with a folder-hook.
-

-You can have as many spam or nospam commands as you like.
-You can even do your own primitive spam detection within mutt -- for
+Likewise, if the pattern for a spam command matches an entry
+on the nospam list, that nospam entry will be removed. If the
+pattern for nospam is “*”, all entries on both lists
+will be removed. This might be the default action if you use spam
+and nospam in conjunction with a folder-hook.
+

+You can have as many spam or nospam commands as you like.
+You can even do your own primitive spam detection within Mutt — for
 example, if you consider all mail from MAILER-DAEMON to be spam,
-you can use a spam command like this:
+you can use a spam command like this:
 
 spam "^From: .*MAILER-DAEMON"       "999"
-

26. Setting and Querying Variables

26.1. Commands

+

26. Setting and Querying Variables

26.1. Variable Types

+Mutt supports these types of configuration variables: +

boolean

+A boolean expression, either “yes” or “no”. +

number

+A signed integer number in the range -32768 to 32767. +

string

+Arbitrary text. +

path

+A specialized string for representing paths including support for +mailbox shortcuts (see Section 7, “Mailbox Shortcuts”) as well as tilde +(“˜”) for a user's home directory and more. +

quadoption

+Like a boolean but triggers a prompt when set to “ask-yes” +or “ask-no” with “yes” and “no” +preselected respectively. +

sort order

+A specialized string allowing only particular words as values depending +on the variable. +

regular expression

+A regular expression, see Section 1, “Regular Expressions” for an introduction. +

folder magic

+Specifies the type of folder to use: mbox, +mmdf, mh +or maildir. +Currently only used to determine the type for newly created folders. +

e-mail address

+An e-mail address either with or without +realname. The older “user@example.org (Joe User)” +form is supported but strongly deprecated. +

user-defined

+Arbitrary text, see Section 26.3, “User-Defined Variables” for details. +

26.2. Commands

The following commands are available to manipulate and query variables:

Usage:

set { [ no | inv ] variable | variable=value - } [...]

toggle + } [...]
toggle variable [ variable -...]

unset +...]
unset variable [ variable -...]

reset +...]
reset variable [ variable ...]

-This command is used to set (and unset) configuration variables. There are four basic types of variables: +This command is used to set (and unset) configuration variables. There are four basic types of variables: boolean, number, string and quadoption. boolean variables can be set (true) or unset (false). number variables can be assigned a positive integer value. @@ -1085,16 +1148,16 @@ action to be carried out as if you had answered “no.ask-yes will cause a prompt with a default answer of “yes” and ask-no will provide a default answer of “no.”

-Prefixing a variable with “no” will unset it. Example: set noaskbcc. +Prefixing a variable with “no” will unset it. Example: set noaskbcc.

For boolean variables, you may optionally prefix the variable name with inv to toggle the value (on or off). This is useful when writing -macros. Example: set invsmart_wrap. +macros. Example: set invsmart_wrap.

-The toggle command automatically prepends the inv prefix to all +The toggle command automatically prepends the inv prefix to all specified variables.

-The unset command automatically prepends the no prefix to all +The unset command automatically prepends the no prefix to all specified variables.

Using the <enter-command> function in the index menu, you can query the @@ -1106,23 +1169,23 @@ set ?allow_8bit The question mark is actually only required for boolean and quadoption variables.

-The reset command resets all given variables to the compile time +The reset command resets all given variables to the compile time defaults (hopefully mentioned in this manual). If you use the command -set and prefix the variable with “&” this has the same -behavior as the reset command. +set and prefix the variable with “&” this has the same +behavior as the reset command.

-With the reset command there exists the special variable “all”, +With the reset command there exists the special variable “all”, which allows you to reset all variables to their system defaults. -

26.2. User-defined variables

26.2.1. Introduction

+

26.3. User-Defined Variables

26.3.1. Introduction

Along with the variables listed in the -Configuration variables section, mutt +Configuration variables section, Mutt supports user-defined variables with names starting with my_ as in, for example, my_cfgdir.

-The set command either creates a +The set command either creates a custom my_ variable or changes its -value if it does exist already. The unset and reset +value if it does exist already. The unset and reset commands remove the variable entirely.

Since user-defined variables are expanded in the same way that @@ -1130,10 +1193,10 @@ environment variables are (except for the shell-escape command and backtick expansion), this feature can be used to make configuration files more readable. -

26.2.2. Examples

+

26.3.2. Examples

The following example defines and uses the variable my_cfgdir -to abbreviate the calls of the source command: -

Example 3.14. Using user-defined variables for config file readability

+to abbreviate the calls of the source command:
+
Example 3.15. Using user-defined variables for config file readability
 set my_cfgdir = $HOME/mutt/config
 
 source $my_cfgdir/hooks
@@ -1142,26 +1205,26 @@ source $my_cfgdir/macros
 


 A custom variable can also be used in macros to backup the current value
 of another variable. In the following example, the value of the
-$delete is changed temporarily
+$delete is changed temporarily
 while its original value is saved as my_delete.
-After the macro has executed all commands, the original value of $delete is restored.
-
Example 3.15. Using user-defined variables for backing up other config option values
+After the macro has executed all commands, the original value of $delete is restored.
+
Example 3.16. Using user-defined variables for backing up other config option values
 macro pager ,x '\
 <enter-command>set my_delete=$delete<enter>\
 <enter-command>set delete=yes<enter>\
 ...\
 <enter-command>set delete=$my_delete<enter>'
 


-Since mutt expands such values already when parsing the configuration
+Since Mutt expands such values already when parsing the configuration
 file(s), the value of $my_delete in the
-last example would be the value of $delete exactly
+last example would be the value of $delete exactly
 as it was at that point during parsing the configuration file. If
-another statement would change the value for $delete
+another statement would change the value for $delete
 later in the same or another file, it would have no effect on
 $my_delete. However, the expansion can
 be deferred to runtime, as shown in the next example, when escaping the
 dollar sign.
-
Example 3.16. Deferring user-defined variable expansion to runtime
+
Example 3.17. Deferring user-defined variable expansion to runtime
 macro pager <PageDown> "\
 <enter-command> set my_old_pager_stop=\$pager_stop pager_stop<Enter>\
 <next-page>\
@@ -1170,9 +1233,9 @@ macro pager <PageDown> "\
 


 Note that there is a space
 between <enter-command> and
-the set configuration command, preventing mutt from
-recording the macro's commands into its history.
-
27. Reading initialization commands from another file
Usage:
source   
+the set configuration command, preventing Mutt from
+recording the macro's commands into its history.
+
27. Reading Initialization Commands From Another File
Usage:
source   
 filename
  

 This command allows the inclusion of initialization commands
@@ -1183,10 +1246,10 @@ from other files.  For example, I place all of my aliases in
 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 filename is
+If the filename ends with a vertical bar (“|”), then filename is
 considered to be an executable program from which to read input (eg.
-source ˜/bin/myscript|).
-
28. Removing hooks
Usage:
unhook  { 
+source ˜/bin/myscript|).
+
28. Removing Hooks
Usage:
unhook  { 
 *
   |   
 hook-type
@@ -1194,58 +1257,82 @@ considered to be an executable program from which to read input (eg.
 This command permits you to flush hooks you have previously defined.
 You can either remove all hooks by giving the “*” character as an
 argument, or you can remove all hooks of a specific type by saying
-something like unhook send-hook.
+something like unhook send-hook.
 
29. Format Strings
29.1. Basic usage

 Format strings are a general concept you'll find in several locations
-through the mutt configuration, especially in the
-$index_format,
-$pager_format,
-$status_format,
-and other “*_format” variables. These can be very straightforward,
+through the Mutt configuration, especially in the
+$index_format,
+$pager_format,
+$status_format,
+and other related variables. These can be very straightforward,
 and it's quite possible you already know how to use them.
 

 The most basic format string element is a percent symbol followed
 by another character. For example, %s
-represents a message's Subject: header in the $index_format variable. The
+represents a message's Subject: header in the $index_format variable. The
 “expandos” available are documented with each format variable, but
 there are general modifiers available with all formatting expandos,
 too. Those are our concern here.
 

 Some of the modifiers are borrowed right out of C (though you might
 know them from Perl, Python, shell, or another language). These are
-the [-]m.n modifiers, as in %-12.12s. As with
+the [-]m.n modifiers, as in %-12.12s. As with
 such programming languages, these modifiers allow you to specify the
 minimum and maximum size of the resulting string, as well as its
 justification. If the “-” sign follows the percent, the string will
 be left-justified instead of right-justified. If there's a number
 immediately following that, it's the minimum amount of space the
-formatted string will occupy -- if it's naturally smaller than that, it
+formatted string will occupy — if it's naturally smaller than that, it
 will be padded out with spaces.  If a decimal point and another number
-follow, that's the maximum space allowable -- the string will not be
+follow, that's the maximum space allowable — the string will not be
 permitted to exceed that width, no matter its natural size. Each of
 these three elements is optional, so that all these are legal format
-strings:
-%-12s
-%4c
-%.15F
-%-12.15L
+strings: %-12s, %4c,
+%.15F and %-12.15L.
 

 Mutt adds some other modifiers to format strings. If you use an equals
 symbol (=) as a numeric prefix (like the minus
 above), it will force the string to be centered within its minimum
 space range. For example, %=14y will reserve 14
-characters for the %y expansion -- that's the X-Label: header, in
-$index_format. If the expansion
+characters for the %y expansion — that's the X-Label: header, in
+$index_format. If the expansion
 results in a string less than 14 characters, it will be centered in a
-14-character space.  If the X-Label for a message were "test", that
-expansion would look like “     test     ”.
+14-character space.  If the X-Label for a message were “test”, that
+expansion would look like “     test     ”.
 

 There are two very little-known modifiers that affect the way that an
 expando is replaced. If there is an underline (“_”) character
 between any format modifiers (as above) and the expando letter, it will
 expands in all lower case. And if you use a colon (“:”), it will
 replace all decimal points with underlines.
-
29.2. Filters

+
29.2. Conditionals

+Depending on the format string variable, some of its 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:
+
+%?<sequence_char>?<optional_string>?

+where sequence_char is an expando, and
+optional_string is the string you would like printed if
+sequence_char is nonzero.
+optional_string may contain other
+sequences as well as normal text, but you may not nest optional
+strings.
+

+Here is an example illustrating how to optionally print the number of
+new messages in a mailbox in
+$status_format:
+
+%?n?%n new messages.?

+You can also switch between two strings using the following construct:
+
+%?<sequence_char>?<if_string>&<else_string>?

+If the value of sequence_char is
+non-zero, if_string will be expanded,
+otherwise else_string will be expanded.
+
29.3. Filters

 Any format string ending in a vertical bar (“|”) will be
 expanded and piped through the first word in the string, using spaces
 as separator. The string returned will be used for display.
@@ -1255,10 +1342,10 @@ replacement format string including % expandos.
 

 All % expandos in a format string are expanded before the script
 is called so that:
-
Example 3.17. Using external filters in format strings
+
Example 3.18. Using external filters in format strings
 set status_format="script.sh '%r %f (%L)'|"
 


-will make mutt expand %r,
+will make Mutt expand %r,
 %f and %L
 before calling the script. The example also shows that arguments can be
 quoted: the script will receive the expanded string between the single quotes
@@ -1266,7 +1353,40 @@ as the only argument.
 

 A practical example is the mutt_xtitle
 script installed in the samples
-subdirectory of the mutt documentation: it can be used as filter for
-$status_format to set the current
+subdirectory of the Mutt documentation: it can be used as filter for
+$status_format to set the current
 terminal's title, if supported.
-
Prev   Next
Chapter 2. Getting Started Home Chapter 4. Advanced Usage

+
29.4. Padding

+In most format strings, Mutt supports different types of padding using
+special %-expandos:
+
%|X

+When this occurs, Mutt will fill the rest of the
+line with the character X. For
+example, filling the rest of the line with dashes is
+done by setting:
+
+set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"

+%>X
+

+Since the previous expando stops at the end of line, there must be a way
+to fill the gap between two items via the %>X
+expando: it puts as many characters X in between two
+items so that the rest of the line will be right-justified. For example,
+to not put the version string and hostname the above example on the left
+but on the right and fill the gap with spaces, one might use (note the
+space after %>):
+
+set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
%*X
+

+Normal right-justification will print everything to the left of the
+%>, displaying padding and whatever lies to the
+right only if there's room. By contrast, “soft-fill” gives
+priority to the right-hand side, guaranteeing space to display it and
+showing padding only if there's still room. If necessary, soft-fill will
+eat text leftwards to make room for rightward text. For example, to
+right-justify the subject making sure as much as possible of it fits on
+screen, one might use (note two spaces after %*
+: the second ensures there's a space between the truncated
+right-hand side and the subject):
+
+set index_format="%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?)%*  %s"
Prev   Next
Chapter 2. Getting Started Home Chapter 4. Advanced Usage

diff --git a/doc/dotlock.man b/doc/dotlock.man
index 4d3256d..02d43de 100644
--- a/doc/dotlock.man
+++ b/doc/dotlock.man
@@ -24,7 +24,7 @@ mutt_dotlock \- Lock mail spool files.
 .SH SYNOPSIS
 .PP
 .B mutt_dotlock 
-[-t|-f|-u|-d] [-p] [-r \fIretries\fP] \fIfile\fP
+[\-t|\-f|\-u|\-d] [\-p] [\-r \fIretries\fP] \fIfile\fP
 .SH DESCRIPTION
 .PP
 .B mutt_dotlock
diff --git a/doc/gen-map-doc b/doc/gen-map-doc
index cafc68d..1a99cf8 100644
--- a/doc/gen-map-doc
+++ b/doc/gen-map-doc
@@ -49,17 +49,19 @@ open XML, $xml or die "$xml: $!";
 while () {
   if (/__print_map\((.*)\)/) {
     my $map = $1;
+    my $maptitle = $1;
+    $maptitle =~ s/^(.)/\U$1\E/;
     unless ($MAP{$map}) {
       warn "map $map undefined";
       next;
     }
     print <
-$map menu
+
+$maptitle Menu
 $DOC{$map}
 
-
-Default $map function bindings
+

+Default $map Function Bindings
 FunctionDefault keyDescription
@@ -73,7 +75,7 @@ $MAP{$map}
 
 
 EOT
-    delete $MAP{$1};
+    delete $MAP{$map};
   } else {
     print;
   }
diff --git a/doc/gettingstarted.html b/doc/gettingstarted.html
index feb9db7..2d022ac 100644
--- a/doc/gettingstarted.html
+++ b/doc/gettingstarted.html
@@ -1,27 +1,31 @@
 
-Chapter 2. Getting Started

 
 
 
Chapter 2. Getting Started
Prev   Next

Chapter 2. Getting Started

Table of Contents

1. Core concepts
2. Moving Around in Menus
3. Editing Input Fields
3.1. Introduction
3.2. History
4. Reading Mail - The Index and Pager
4.1. The Message Index
4.2. The Pager
4.3. Threaded Mode
4.4. Miscellaneous Functions
5. Sending Mail
5.1. Introduction
5.2. Editing the message header
5.3. Sending cryptographically signed/encrypted messages
5.4. Sending anonymous messages via mixmaster
5.5. Sending format=flowed messages
6. Forwarding and Bouncing Mail
7. Postponing Mail

+

Chapter 2. Getting Started
Prev   Next

Chapter 2. Getting Started

Table of Contents

1. Core Concepts
2. Screens and Menus
2.1. Index
2.2. Pager
2.3. File Browser
2.4. Help
2.5. Compose Menu
2.6. Alias Menu
2.7. Attachment Menu
3. Moving Around in Menus
4. Editing Input Fields
4.1. Introduction
4.2. History
5. Reading Mail
5.1. The Message Index
5.2. The Pager
5.3. Threaded Mode
5.4. Miscellaneous Functions
6. Sending Mail
6.1. Introduction
6.2. Editing the Message Header
6.3. Sending Cryptographically Signed/Encrypted Messages
6.4. Sending Format=Flowed Messages
7. Forwarding and Bouncing Mail
8. Postponing Mail

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 various web @@ -31,10 +35,10 @@ The keybindings described in this section are the defaults as distributed. Your local system administrator may have altered the defaults for your site. You can always type “?” in any menu to display the current bindings.

-The first thing you need to do is invoke mutt, simply by typing mutt +The first thing you need to do is invoke Mutt, simply by typing mutt at the command line. There are various command-line options, see -either the mutt man page or the reference. -

1. Core concepts

+either the Mutt man page or the reference. +

1. Core Concepts

Mutt is a text-based application which interacts with users through different menus which are mostly line-/entry-based or page-based. A line-based menu is the so-called “index” menu (listing all messages of @@ -49,6 +53,11 @@ finally the command line. The command line is used to display informational and error messages as well as for prompts and for entering interactive commands.

+Mutt is configured through variables which, if the user wants to +permanently use a non-default value, are written to configuration +files. Mutt supports a rich config file syntax to make even complex +configuration files readable and commentable. +

Because Mutt allows for customizing almost all key bindings, there are so-called “functions” which can be executed manually (using the command line) or in macros. Macros allow the user to bind a sequence of @@ -72,69 +81,143 @@ existing one. These hooks can be used to highly customize Mutt's behaviour including managing multiple identities, customizing the display for a folder or even implementing auto-archiving based on a per-folder basis and much more. -

2. Moving Around in Menus

-The most important navigation keys common to all menus are shown in -Table 2.1, “Most common navigation keys”. -

Table 2.1. Most common navigation keys

KeyFunctionDescription
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
Z or <PageUp><page-up>go to the previous page
= or <Home><first-entry>jump to the first entry
* or <End><last-entry>jump to the last entry
q<quit>exit the current menu
?<help>list all keybindings for the current menu

3. Editing Input Fields

3.1. Introduction

+

+Besides an interactive mode, Mutt can also be used as a command-line +tool only send messages. It also supports a +mailx(1)-compatible interface, see Table 9.1, “Command line options” for a complete list of command-line +options. +

2. Screens and Menus

2.1. Index

+The index is the screen that you usually see first when you start +Mutt. It gives an overview over your emails in the currently opened +mailbox. By default, this is your system mailbox. The information you +see in the index is a list of emails, each with its number on the left, +its flags (new email, important email, email that has been forwarded or +replied to, tagged email, ...), the date when email was sent, its +sender, the email size, and the subject. Additionally, the index also +shows thread hierarchies: when you reply to an email, and the other +person replies back, you can see the other's person email in a +"sub-tree" below. This is especially useful for personal email between +a group of people or when you've subscribed to mailing lists. +

2.2. Pager

+The pager is responsible for showing the email content. On the top of +the pager you have an overview over the most important email headers +like the sender, the recipient, the subject, and much more +information. How much information you actually see depends on your +configuration, which we'll describe below. +

+Below the headers, you see the email body which usually contains the +message. If the email contains any attachments, you will see more +information about them below the email body, or, if the attachments are +text files, you can view them directly in the pager. +

+To give the user a good overview, it is possible to configure Mutt to +show different things in the pager with different colors. Virtually +everything that can be described with a regular expression can be +colored, e.g. URLs, email addresses or smileys. +

2.3. File Browser

+The file browser is the interface to the local or remote file +system. When selecting a mailbox to open, the browser allows custom +sorting of items, limiting the items shown by a regular expression and a +freely adjustable format of what to display in which way. It also allows +for easy navigation through the file system when selecting file(s) to +attach to a message, select multiple files to attach and many more. +

2.4. Help

+The help screen is meant to offer a quick help to the user. It lists the +current configuration of key bindings and their associated commands +including a short description, and currently unbound functions that +still need to be associated with a key binding (or alternatively, they +can be called via the Mutt command prompt). +

2.5. Compose Menu

+The compose menu features a split screen containing the information +which really matter before actually sending a message by mail: who gets +the message as what (recipients and who gets what kind of +copy). Additionally, users may set security options like deciding +whether to sign, encrypt or sign and encrypt a message with/for what +keys. Also, it's used to attach messages, to re-edit any attachment +including the message itself. +

2.6. Alias Menu

+The alias menu is used to help users finding the recipients of +messages. For users who need to contact many people, there's no need to +remember addresses or names completely because it allows for searching, +too. The alias mechanism and thus the alias menu also features grouping +several addresses by a shorter nickname, the actual alias, so that users +don't have to select each single recipient manually. +

2.7. Attachment Menu

+As will be later discussed in detail, Mutt features a good and stable +MIME implementation, that is, it supports sending and receiving messages +of arbitrary MIME types. The attachment menu displays a message's +structure in detail: what content parts are attached to which parent +part (which gives a true tree structure), which type is of what type and +what size. Single parts may saved, deleted or modified to offer great +and easy access to message's internals. +

3. Moving Around in Menus

+The most important navigation keys common to line- or entry-based menus +are shown in Table 2.1, “Most common navigation keys in entry-based menus” and in +Table 2.2, “Most common navigation keys in page-based menus” for page-based menus. +

Table 2.1. Most common navigation keys in entry-based menus

KeyFunctionDescription
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
Z or <PageUp><page-up>go to the previous page
= or <Home><first-entry>jump to the first entry
* or <End><last-entry>jump to the last entry
q<quit>exit the current menu
?<help>list all keybindings for the current menu

Table 2.2. Most common navigation keys in page-based menus

KeyFunctionDescription
J or <Return><next-line>scroll down one line
<Backspace><previous-line>sroll up one line
K, <Space> or <PageDn><next-page>move to the next page
- or <PageUp><previous-page>move the previous page
<Home><top>move to the top
<End><bottom>move to the bottom

4. Editing Input Fields

4.1. Introduction

Mutt has a built-in line editor for inputting text, e.g. email addresses or filenames. The keys used to manipulate text input are -very similar to those of Emacs. See Table 2.2, “Most common line editor keys” for a full +very similar to those of Emacs. See Table 2.3, “Most common line editor keys” for a full reference of available functions, their default key bindings, and short descriptions. -

Table 2.2. Most common line editor keys

KeyFunctionDescription
^A or <Home><bol>move to the start of the line
^B or <Left><backward-char>move back one char
Esc B<backward-word>move back one word
^D or <Delete><delete-char>delete the char under the cursor
^E or <End><eol>move to the end of the line
^F or <Right><forward-char>move forward one char
Esc F<forward-word>move forward one word
<Tab><complete>complete filename or alias
^T<complete-query>complete address with query
^K<kill-eol>delete to the end of the line
Esc d<kill-eow>delete to the end of the word
^W<kill-word>kill the word in front of the cursor
^U<kill-line>delete entire line
^V<quote-char>quote the next typed key
<Up><history-up>recall previous string from history
<Down><history-down>recall next string from history
<BackSpace><backspace>kill the char in front of the cursor
Esc u<upcase-word>convert word to upper case
Esc l<downcase-word>convert word to lower case
Esc c<capitalize-word>capitalize the word
^Gn/aabort
<Return>n/afinish editing

+

Table 2.3. Most common line editor keys

KeyFunctionDescription
^A or <Home><bol>move to the start of the line
^B or <Left><backward-char>move back one char
Esc B<backward-word>move back one word
^D or <Delete><delete-char>delete the char under the cursor
^E or <End><eol>move to the end of the line
^F or <Right><forward-char>move forward one char
Esc F<forward-word>move forward one word
<Tab><complete>complete filename or alias
^T<complete-query>complete address with query
^K<kill-eol>delete to the end of the line
Esc d<kill-eow>delete to the end of the word
^W<kill-word>kill the word in front of the cursor
^U<kill-line>delete entire line
^V<quote-char>quote the next typed key
<Up><history-up>recall previous string from history
<Down><history-down>recall next string from history
<BackSpace><backspace>kill the char in front of the cursor
Esc u<upcase-word>convert word to upper case
Esc l<downcase-word>convert word to lower case
Esc c<capitalize-word>capitalize the word
^Gn/aabort
<Return>n/afinish editing

You can remap the editor functions using the -bind command. For example, to make +bind command. For example, to make the <Delete> key delete the character in front of the cursor rather than under, you could use: 

 bind editor <delete> backspace
-

3.2. History

+

4.2. History

Mutt maintains a history for the built-in editor. The number of items -is controlled by the $history +is controlled by the $history variable and can be made persistent using an external file specified -using $history_file. +using $history_file. You may cycle through them at an editor prompt by using the <history-up> and/or -<history-down> commands. +<history-down> commands. But notice that Mutt +does not remember the currently entered text, it only cycles through +history and wraps around at the end or beginning.

Mutt maintains several distinct history lists, one for each of the following categories: -

  • muttrc commands

  • addresses and aliases

  • shell commands

  • filenames

  • patterns

  • everything else

-Mutt automatically filters out repeated items from the history. It +

  • .muttrc commands

  • addresses and aliases

  • shell commands

  • filenames

  • patterns

  • everything else

+Mutt automatically filters out consecutively repeated items from the history. It also mimics the behavior of some shells by ignoring items starting with a space. The latter feature can be useful in macros to not clobber the history's valuable entries with unwanted entries. -

4. Reading Mail - The Index and Pager

+

5. Reading Mail

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 of the +read in Mutt. The first is a list of messages in the mailbox, which is +called the “index” menu in Mutt. The second mode is the display of the message contents. This is called the “pager.”

The next few sections describe the functions provided in each of these modes. -

4.1. The Message Index

+

5.1. The Message Index

Common keys used to navigate through and manage messages in the index -are shown in Table 2.3, “Most common message index keys”. How messages are presented +are shown in Table 2.4, “Most common message index keys”. How messages are presented in the index menu can be customized using the -$index_format variable. -

Table 2.3. Most common message index keys

KeyDescription
cchange to a different mailbox
Esc cchange to a folder in read-only mode
Ccopy the current message to another mailbox
Esc Cdecode a message and copy it to a folder
Esc sdecode a message and save it to a folder
Ddelete messages matching a pattern
ddelete the current message
Fmark as important
lshow messages matching a pattern
Nmark message as new
ochange the current sort method
Oreverse sort the mailbox
qsave changes and exit
ssave-message
Ttag messages matching a pattern
ttoggle the tag on a message
Esc ttoggle tag on entire message thread
Uundelete messages matching a pattern
uundelete-message
vview-attachments
xabort changes and exit
<Return>display-message
<Tab>jump to the next new or unread message
@show the author's full e-mail address
$save changes to mailbox
/search
Esc /search-reverse
^Lclear and redraw the screen
^Tuntag messages matching a pattern

+$index_format variable. +

Table 2.4. Most common message index keys

KeyDescription
cchange to a different mailbox
Esc cchange to a folder in read-only mode
Ccopy the current message to another mailbox
Esc Cdecode a message and copy it to a folder
Esc sdecode a message and save it to a folder
Ddelete messages matching a pattern
ddelete the current message
Fmark as important
lshow messages matching a pattern
Nmark message as new
ochange the current sort method
Oreverse sort the mailbox
qsave changes and exit
ssave-message
Ttag messages matching a pattern
ttoggle the tag on a message
Esc ttoggle tag on entire message thread
Uundelete messages matching a pattern
uundelete-message
vview-attachments
xabort changes and exit
<Return>display-message
<Tab>jump to the next new or unread message
@show the author's full e-mail address
$save changes to mailbox
/search
Esc /search-reverse
^Lclear and redraw the screen
^Tuntag messages matching a pattern

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 “flags” in Table 2.4, “Message status flags” +Zero or more of the “flags” in Table 2.5, “Message status flags” may appear, some of which can be turned on or off using these functions: <set-flag> and <clear-flag> bound by default to “w” and “W” respectively.

-Furthermore, the flags in Table 2.5, “Message recipient flags” reflect +Furthermore, the flags in Table 2.6, “Message recipient flags” reflect who the message is addressed to. They can be customized with the -$to_chars variable. -

Table 2.4. Message status flags

FlagDescription
Dmessage is deleted (is marked for deletion)
dmessage has attachments marked for deletion
Kcontains a PGP public key
Nmessage is new
Omessage is old
Pmessage is PGP encrypted
rmessage has been replied to
Smessage is signed, and the signature is successfully verified
smessage is signed
!message is flagged
*message is tagged

Table 2.5. Message recipient flags

FlagDescription
+message is to you and you only
Tmessage is to you, but also to or cc'ed to others
Cmessage is cc'ed to you
Fmessage is from you
Lmessage is sent to a subscribed mailing list

4.2. The Pager

-By default, Mutt uses its builtin pager to display the contents of messages. -The pager is very similar to the Unix program less though not nearly as -featureful. -

Table 2.6. Most common pager keys

KeyDescription
<Return>go down one line
<Space>display the next page (or next message if at the end of a message)
-go back to the previous page
nsearch for next match
Sskip beyond quoted text
Ttoggle display of quoted text
?show keybindings
/regular expression search
Esc /backward regular expression search
\toggle highlighting of search matches
^jump to the top of the message

-In addition to key bindings in Table 2.6, “Most common pager keys”, +$to_chars variable. +

Table 2.5. Message status flags

FlagDescription
Dmessage is deleted (is marked for deletion)
dmessage has attachments marked for deletion
Kcontains a PGP public key
Nmessage is new
Omessage is old
Pmessage is PGP encrypted
rmessage has been replied to
Smessage is signed, and the signature is successfully verified
smessage is signed
!message is flagged
*message is tagged

Table 2.6. Message recipient flags

FlagDescription
+message is to you and you only
Tmessage is to you, but also to or cc'ed to others
Cmessage is cc'ed to you
Fmessage is from you
Lmessage is sent to a subscribed mailing list

5.2. The Pager

+By default, Mutt uses its builtin pager to display the contents of +messages (an external pager such as less(1) can be +configured, see $pager variable). +The pager is very similar to the Unix program less(1) +though not nearly as featureful. +

Table 2.7. Most common pager keys

KeyDescription
<Return>go down one line
<Space>display the next page (or next message if at the end of a message)
-go back to the previous page
nsearch for next match
Sskip beyond quoted text
Ttoggle display of quoted text
?show keybindings
/regular expression search
Esc /backward regular expression search
\toggle highlighting of search matches
^jump to the top of the message

+In addition to key bindings in Table 2.7, “Most common pager keys”, many of the functions from the index menu are also available in the pager, such as <delete-message> or <copy-message> (this is one advantage over using an external pager to view messages). @@ -142,11 +225,11 @@ the pager, such as <delete-message> or standard” nroff sequences for bold and underline. These sequences are a series of either the letter, -backspace (^H), the letter again for bold or the letter, backspace, +backspace (“^H”), the letter again for bold or the letter, backspace, “_” for denoting underline. Mutt will attempt to display these in bold and underline respectively if your terminal supports them. If -not, you can use the bold and underline color -objects to specify a color or mono attribute for them. +not, you can use the bold and underline color +objects to specify a color or mono attribute for them.

Additionally, the internal pager supports the ANSI escape sequences for character attributes. Mutt translates them into the correct color and @@ -155,8 +238,8 @@ character settings. The sequences Mutt supports are: \e[Ps;Ps;..Ps;m

where Ps can be one of the codes shown in -Table 2.7, “ANSI escape sequences”. -

Table 2.7. ANSI escape sequences

Escape codeDescription
0All attributes off
1Bold on
4Underline on
5Blink on
7Reverse video on
3<color>Foreground color is <color> (see Table 2.8, “Color sequences”)
4<color>Background color is <color> (see Table 2.8, “Color sequences”)

Table 2.8. Color sequences

Color codeColor
0Black
1Red
2Green
3Yellow
4Blue
5Magenta
6Cyan
7White

+Table 2.8, “ANSI escape sequences”. +

Table 2.8. ANSI escape sequences

Escape codeDescription
0All attributes off
1Bold on
4Underline on
5Blink on
7Reverse video on
3<color>Foreground color is <color> (see Table 2.9, “Color sequences”)
4<color>Background color is <color> (see Table 2.9, “Color sequences”)

Table 2.9. Color sequences

Color codeColor
0Black
1Red
2Green
3Yellow
4Blue
5Magenta
6Cyan
7White

Mutt uses these attributes for handling text/enriched messages, and they can also be used by an external autoview script for highlighting @@ -169,36 +252,48 @@ your xterm, then that color will be used instead of green. Note that the search commands in the pager take regular expressions, which are not quite the same as the more complex patterns used by the search -command in the index. This is because the pager only performs simple -text search, whereas the index provides boolean filtering on several -aspects of messages. -

4.3. Threaded Mode

-When the mailbox is sorted by threads, there are -a few additional functions available in the index and pager modes -as shown in Table 2.9, “Most common thread mode keys”. -

Table 2.9. Most common thread mode keys

KeyFunctionDescription
^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
^P<previous-thread>jump to the start of the previous thread
^R<read-thread>mark the current thread as read
Esc d<delete-subthread>delete all messages in the current subthread
Esc u<undelete-subthread>undelete all messages in the current subthread
Esc n<next-subthread>jump to the start of the next subthread
Esc p<previous-subthread>jump to the start of the previous subthread
Esc r<read-subthread>mark the current subthread as read
Esc t<tag-thread>toggle the tag on the current thread
Esc v<collapse-thread>toggle collapse for the current thread
Esc V<collapse-all>toggle collapse for all threads
P<parent-message>jump to parent message in thread

Note

+command in the index. This is because patterns are used to select messages by +criteria whereas the pager already displays a selected message. +

5.3. Threaded Mode

+So-called “threads” provide a hierarchy of messages where +replies are linked to their parent message(s). This organizational form +is extremely useful in mailing lists where different parts of the +discussion diverge. Mutt displays threads as a tree structure. +

+In Mutt, when a mailbox is sorted +by threads, there are a few additional functions +available in the index +and pager modes as shown in +Table 2.10, “Most common thread mode keys”. +

Table 2.10. Most common thread mode keys

KeyFunctionDescription
^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
^P<previous-thread>jump to the start of the previous thread
^R<read-thread>mark the current thread as read
Esc d<delete-subthread>delete all messages in the current subthread
Esc u<undelete-subthread>undelete all messages in the current subthread
Esc n<next-subthread>jump to the start of the next subthread
Esc p<previous-subthread>jump to the start of the previous subthread
Esc r<read-subthread>mark the current subthread as read
Esc t<tag-thread>toggle the tag on the current thread
Esc v<collapse-thread>toggle collapse for the current thread
Esc V<collapse-all>toggle collapse for all threads
P<parent-message>jump to parent message in thread

Collapsing a thread displays only the first message in the thread and hides the others. This is useful when threads contain so many messages that you can only see a handful of threads on -the screen. See %M in $index_format. -For example, you could use "%?M?(#%03M)&(%4l)?" in $index_format to optionally -display the number of hidden messages if the thread is collapsed. -

-See also: $strict_threads. -

4.4. Miscellaneous Functions

+the screen. See %M in $index_format. +For example, you could use “%?M?(#%03M)&(%4l)?” in $index_format to optionally +display the number of hidden messages if the thread is +collapsed. The %?<char>?<if-part>&<else-part>? +syntax is explained in detail in +format string conditionals. +

+Technically, every reply should contain a list of its parent messages in +the thread tree, but not all do. In these cases, Mutt groups them by +subject which can be controlled using the +$strict_threads variable. +

5.4. Miscellaneous Functions

In addition, the index and pager menus have these interesting functions:

<create-alias> (default: a)

Creates a new alias based upon the current message (or prompts for a -new one). Once editing is complete, an alias +new one). Once editing is complete, an alias command is added to the file specified by the $alias_file variable for future use

Note

Mutt does not read the $alias_file -upon startup so you must explicitly source the file. +upon startup so you must explicitly source the file.

<check-traditional-pgp> (default: Esc P)

@@ -237,7 +332,7 @@ to send.

This command is used to execute any command you would normally put in a configuration file. A common use is to check the settings of variables, or -in conjunction with macros to change settings on the +in conjunction with macros to change settings on the fly.

<extract-keys> (default: ^K) @@ -254,9 +349,9 @@ you misspelled the passphrase. <list-reply> (default: L)

Reply to the current or tagged message(s) by extracting any addresses which -match the regular expressions given by the lists or subscribe +match the regular expressions given by the lists or subscribe commands, but also honor any Mail-Followup-To header(s) if the -$honor_followup_to +$honor_followup_to configuration variable is set. Using this when replying to messages posted to mailing lists helps avoid duplicate copies being sent to the author of the message you are replying to. @@ -264,8 +359,8 @@ the message you are replying to. <pipe-message> (default: |)

Asks for an external Unix command and pipes the current or -tagged message(s) to it. The variables $pipe_decode, $pipe_split, -$pipe_sep and $wait_key control the exact behavior of this function. +tagged message(s) to it. The variables $pipe_decode, $pipe_split, +$pipe_sep and $wait_key control the exact behavior of this function.

<resend-message> (default: Esc e)

@@ -273,7 +368,7 @@ Mutt takes the current message as a template for a new message. This function is best described as "recall from arbitrary folders". It can conveniently be used to forward MIME messages while preserving the original mail structure. Note that the amount of headers -included here depends on the value of the $weed +included here depends on the value of the $weed variable.

This function is also available from the attachment menu. You can use this @@ -282,7 +377,7 @@ as a message/rfc822 body part.

<shell-escape> (default: !)

-Asks for an external Unix command and executes it. The $wait_key can be used to control +Asks for an external Unix command and executes it. The $wait_key can be used to control whether Mutt will wait for a key to be pressed when the command returns (presumably to let the user read the output of the command), based on the return status of the named command. If no command is given, an @@ -290,7 +385,7 @@ interactive shell is executed.

<toggle-quoted> (default: T)

-The pager uses the $quote_regexp variable to detect quoted text when +The pager uses the $quote_regexp variable to detect quoted text when displaying the body of the message. This function toggles the display of the quoted material in the message. It is particularly useful when being interested in just the response and there is a large amount of @@ -300,45 +395,59 @@ quoted text in the way.

This function will go to the next line of non-quoted text which comes after a line of quoted text in the internal pager. -

5. Sending Mail

5.1. Introduction

-The bindings shown in Table 2.10, “Most common mail sending keys” are available in the +

6. Sending Mail

6.1. Introduction

+The bindings shown in Table 2.11, “Most common mail sending keys” are available in the index and pager to start a new message. -

Table 2.10. Most common mail sending keys

KeyFunctionDescription
m<compose>compose a new message
r<reply>reply to sender
g<group-reply>reply to all recipients
L<list-reply>reply to mailing list address
f<forward>forward message
b<bounce>bounce (remail) message
Esc k<mail-key>mail a PGP public key to someone

+

Table 2.11. Most common mail sending keys

KeyFunctionDescription
m<compose>compose a new message
r<reply>reply to sender
g<group-reply>reply to all recipients
L<list-reply>reply to mailing list address
f<forward>forward message
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. These items are discussed -in greater detail in the next chapter “Forwarding +in greater detail in the next section “Forwarding and Bouncing Mail.”

Mutt will then enter the compose menu and prompt you for the -recipients to place on the “To:” header field. Next, it will ask +recipients to place on the “To:” header field when you hit m to start a new message. Next, it will ask you for the “Subject:” field for the message, providing a default if -you are replying to or forwarding a message. See also +you are replying to or forwarding a message. You again +have the chance to adjust recipients, subject, and security settings +right before actually sending the message. See also $askcc, $askbcc, -$autoedit, +$autoedit, $bounce, -$fast_reply, -and $include -for changing how Mutt asks these questions. -

-Mutt will then automatically start your $editor -on the message body. If the $edit_headers -variable is set, the headers will be at the top of the message in your editor. -Any messages you are replying to will be added in sort order to the message, +$fast_reply, +and $include +for changing how and if Mutt asks these questions. +

+When replying, Mutt fills these fields with proper values depending on +the reply type. The types of replying supported are: +

Simple reply

+Reply to the author directly. +

Group reply

+Reply to the author as well to all recipients except you; this consults +alternates. +

List reply

+Reply to all mailing list addresses found, either specified via +configuration or auto-detected. See Section 12, “Mailing Lists” for +details. +

+After getting recipients for new messages, forwards or replies, Mutt +will then automatically start your $editor on the message body. If the $edit_headers variable is +set, the headers will be at the top of the message in your editor. Any +messages you are replying to will be added in sort order to the message, with appropriate $attribution, -$indent_string and -$post_indent_string. -When forwarding a message, if the $mime_forward -variable is unset, a copy of the forwarded message will be included. If -you have specified a $signature, it -will be appended to the message. +$indent_string and +$post_indent_string. +When forwarding a message, if the $mime_forward variable is +unset, a copy of the forwarded message will be included. If you have +specified a $signature, it will +be appended to the message.

Once you have finished editing the body of your mail message, you are returned to the compose menu providing the functions -shown in Table 2.11, “Most common compose menu keys” to modify, send or postpone the +shown in Table 2.12, “Most common compose menu keys” to modify, send or postpone the message. -

Table 2.11. Most common compose menu keys

KeyFunctionDescription
a<attach-file>attach a file
A<attach-message>attach message(s) to the message
Esc k<attach-key>attach a PGP public key
d<edit-description>edit description on attachment
D<detach-file>detach a file
t<edit-to>edit the To field
Esc f<edit-from>edit the From field
r<edit-reply-to>edit the Reply-To field
c<edit-cc>edit the Cc field
b<edit-bcc>edit the Bcc field
y<send-message>send the message
s<edit-subject>edit the Subject
S<smime-menu>select S/MIME options
f<edit-fcc>specify an “Fcc” mailbox
p<pgp-menu>select PGP options
P<postpone-message>postpone this message until later
q<quit>quit (abort) sending the message
w<write-fcc>write the message to a folder
i<ispell>check spelling (if available on your system)
^F<forget-passphrase>wipe passphrase(s) from memory

+

Table 2.12. Most common compose menu keys

KeyFunctionDescription
a<attach-file>attach a file
A<attach-message>attach message(s) to the message
Esc k<attach-key>attach a PGP public key
d<edit-description>edit description on attachment
D<detach-file>detach a file
t<edit-to>edit the To field
Esc f<edit-from>edit the From field
r<edit-reply-to>edit the Reply-To field
c<edit-cc>edit the Cc field
b<edit-bcc>edit the Bcc field
y<send-message>send the message
s<edit-subject>edit the Subject
S<smime-menu>select S/MIME options
f<edit-fcc>specify an “Fcc” mailbox
p<pgp-menu>select PGP options
P<postpone-message>postpone this message until later
q<quit>quit (abort) sending the message
w<write-fcc>write the message to a folder
i<ispell>check spelling (if available on your system)
^F<forget-passphrase>wipe passphrase(s) from memory

The compose menu is also used to edit the attachments for a message which can be either files or other messages. The <attach-message> function to will prompt you for a folder to attach messages from. You can now tag messages in that folder and they @@ -347,27 +456,31 @@ will be attached to the message you are sending. Note that certain operations like composing a new mail, replying, forwarding, etc. are not permitted when you are in that folder. The %r in -$status_format will change to +$status_format will change to a “A” to indicate that you are in attach-message mode. -

5.2. Editing the message header

-When editing the header because of $edit_headers +

6.2. Editing the Message Header

+When editing the header because of $edit_headers being set, there are a several pseudo headers available which -will not be included in sent messages. -

5.2.1. Fcc: pseudo header

+will not be included in sent messages but trigger special Mutt behavior. +

6.2.1. Fcc: Pseudo Header

If you specify - +

Fcc: filename - +

as a header, Mutt will pick up filename just as if you had used the <edit-fcc> function in the compose menu. -

5.2.2. Attach: pseudo header

+It can later be changed from the compose menu. +

6.2.2. Attach: Pseudo Header

You can also attach files to your message by specifying - -Attach: filename [ description ] - +

+Attach: filename +[ description ] +

where filename is the file to attach and description is an -optional string to use as the description of the attached file. -

5.2.3. Pgp: pseudo header

+optional string to use as the description of the attached file. Spaces +in filenames have to be escaped using backslash (“\”). +The file can be removed as well as more added from the compose menu. +

6.2.3. Pgp: Pseudo Header

If you want to use PGP, you can specify

Pgp: [ E | S | S<id> ] @@ -375,15 +488,15 @@ If you want to use PGP, you can specify

“E” selects encryption, “S” selects signing and “S<id>” selects signing with the given key, setting -$pgp_sign_as -permanently. -

5.2.4. In-Reply-To: header

+$pgp_sign_as +permanently. The selection can later be changed in the compose menu. +

6.2.4. In-Reply-To: Header

When replying to messages, the In-Reply-To: header contains the -Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a +Message-Id of the message(s) you reply to. If you remove or modify its value, Mutt will not generate a References: field, which allows you to create a new message thread, for example to create a new message to a mailing list without having to enter the mailing list's address. -

5.3. Sending cryptographically signed/encrypted messages

-If you have told mutt to PGP or S/MIME encrypt a message, it will guide you +

6.3. Sending Cryptographically Signed/Encrypted Messages

+If you have told Mutt to PGP or S/MIME encrypt a message, it will guide you through a key selection process when you try to send the message. Mutt will not ask you any questions about keys which have a certified user ID matching one of the message recipients' mail @@ -392,22 +505,22 @@ several keys, weakly certified user ID fields, or where no matching keys can be found.

In these cases, you are dropped into a menu with a list of keys from -which you can select one. When you quit this menu, or mutt can't +which you can select one. When you quit this menu, or Mutt can't find any matching keys, you are prompted for a user ID. You can, as -usually, abort this prompt using ^G. When you do so, mutt will +usually, abort this prompt using ^G. When you do so, Mutt will return to the compose screen.

Once you have successfully finished the key selection, the message will be encrypted using the selected public keys when sent out.

-Most fields of the entries in the key selection menu (see also $pgp_entry_format) +Most fields of the entries in the key selection menu (see also $pgp_entry_format) have obvious meanings. But some explanations on the capabilities, flags, and validity fields are in order.

-The flags sequence (%f) will expand to one of the flags in -Table 2.12, “PGP key menu flags”. -

Table 2.12. PGP key menu flags

FlagDescription
RThe key has been revoked and can't be used.
XThe key is expired and can't be used.
dYou have marked the key as disabled.
cThere are unknown critical self-signature packets.

-The capabilities field (%c) expands to a two-character sequence +The flags sequence (“%f”) will expand to one of the flags in +Table 2.13, “PGP key menu flags”. +

Table 2.13. PGP key menu flags

FlagDescription
RThe key has been revoked and can't be used.
XThe key is expired and can't be used.
dYou have marked the key as disabled.
cThere are unknown critical self-signature packets.

+The capabilities field (“%c”) expands to a two-character sequence representing a key's capabilities. The first character gives the key's encryption capabilities: A minus sign (“-”) means that the key cannot be used for encryption. A dot (“.”) means that @@ -420,47 +533,12 @@ again, a “-” implies “not f that the key is marked as an encryption key in one of the user-ids, and “s” denotes a key which can be used for signing.

-Finally, the validity field (%t) indicates how well-certified a user-id +Finally, the validity field (“%t”) indicates how well-certified a user-id is. A question mark (“?”) indicates undefined validity, a minus character (“-”) marks an untrusted association, a space character means a partially trusted association, and a plus character (“+”) indicates complete validity. -

5.4. Sending anonymous messages via mixmaster

-You may also have compiled mutt to co-operate with Mixmaster, an -anonymous remailer. Mixmaster permits you to send your messages -anonymously using a chain of remailers. Mixmaster support in mutt is for -mixmaster version 2.04 (beta 45 appears to be the latest) and 2.03. -It does not support earlier versions or the later so-called version 3 betas, -of which the latest appears to be called 2.9b23. -

-To use it, you'll have to obey certain restrictions. Most -important, you cannot use the Cc and Bcc headers. To tell -Mutt to use mixmaster, you have to select a remailer chain, using -the mix function on the compose menu. -

-The chain selection screen is divided into two parts. In the -(larger) upper part, you get a list of remailers you may use. In -the lower part, you see the currently selected chain of remailers. -

-You can navigate in the chain using the <chain-prev> and -<chain-next> functions, which are by default bound to the left -and right arrows and to the h and l keys (think vi -keyboard bindings). To insert a remailer at the current chain -position, use the <insert> function. To append a remailer behind -the current chain position, use <select-entry> or <append>. -You can also delete entries from the chain, using the corresponding -function. Finally, to abandon your changes, leave the menu, or -<accept> them pressing (by default) the Return key. -

-Note that different remailers do have different capabilities, -indicated in the %c entry of the remailer menu lines (see -$mix_entry_format). Most important is -the “middleman” capability, indicated by a capital “M”: This -means that the remailer in question cannot be used as the final -element of a chain, but will only forward messages to other -mixmaster remailers. For details on the other capabilities, please -have a look at the mixmaster documentation. -

5.5. Sending format=flowed messages

5.5.1. Concept

+

6.4. Sending Format=Flowed Messages

6.4.1. Concept

format=flowed-style messages (or f=f for short) are text/plain messages that consist of paragraphs which a receiver's mail client may reformat to its own needs which mostly means to @@ -468,17 +546,17 @@ customize line lengths regardless of what the sender sent. Technically this is achieved by letting lines of a “flowable” paragraph end in spaces except for the last line.

-While for text-mode clients like mutt it's the best way to assume only a +While for text-mode clients like Mutt it's the best way to assume only a standard 80x25 character cell terminal, it may be desired to let the receiver decide completely how to view a message. -

5.5.2. Mutt support

+

6.4.2. Mutt Support

Mutt only supports setting the required format=flowed -MIME parameter on outgoing messages if the $text_flowed +MIME parameter on outgoing messages if the $text_flowed variable is set, specifically it does not add the trailing spaces.

After editing the initial message text and before entering -the compose menu, mutt properly space-stuffes the message. +the compose menu, Mutt properly space-stuffes the message. Space-stuffing is required by RfC3676 defining format=flowed and means to prepend a space to:

  • all lines starting with a space

  • lines starting with the word “From” @@ -492,8 +570,8 @@ quote or not. Furthermore, Mutt only applies space-stuffing

All leading spaces are to be removed by receiving clients to restore the original message prior to further processing. -

5.5.3. Editor considerations

-As mutt provides no additional features to compose f=f +

6.4.3. Editor Considerations

+As Mutt provides no additional features to compose f=f messages, it's completely up to the user and his editor to produce proper messages. Please consider your editor's documentation if you intend to send f=f messages. @@ -506,7 +584,7 @@ For example, vim provides the formatoptions setting to assist in creating f=f messages, see :help fo-table for details. -

6. Forwarding and Bouncing Mail

+

7. Forwarding and Bouncing Mail

Bouncing and forwarding let you send an existing message to recipients that you specify. Bouncing a message sends a verbatim copy of a message to alternative addresses as if they were the message's original @@ -519,22 +597,22 @@ respectively.

Forwarding can be done by including the original message in the new message's body (surrounded by indicating lines) or including it as a MIME -attachment, depending on the value of the $mime_forward variable. Decoding of attachments, -like in the pager, can be controlled by the $forward_decode and $mime_forward_decode variables, +attachment, depending on the value of the $mime_forward variable. Decoding of attachments, +like in the pager, can be controlled by the $forward_decode and $mime_forward_decode variables, respectively. The desired forwarding format may depend on the content, -therefore $mime_forward is a quadoption which, for +therefore $mime_forward is a quadoption which, for example, can be set to “ask-no”.

The inclusion of headers is controlled by the current setting of the -$weed variable, unless $mime_forward is set. +$weed variable, unless $mime_forward is set.

Editing the message to forward follows the same procedure as sending or replying to a message does. -

7. Postponing Mail

+

8. Postponing Mail

At times it is desirable to delay sending a message that you have already begun to compose. When the <postpone-message> function is used in the compose menu, the body of your message and attachments -are stored in the mailbox specified by the $postponed variable. This means that you can recall the +are stored in the mailbox specified by the $postponed variable. This means that you can recall the message even if you exit Mutt and then restart it at a later time.

Once a message is postponed, there are several ways to resume it. From the @@ -549,5 +627,5 @@ the message is only updated when you actually finish the message and send it. Also, you must be in the same folder with the message you replied to for the status of the message to be updated.

-See also the $postpone quad-option. +See also the $postpone quad-option.

Prev   Next
Chapter 1. Introduction Home Chapter 3. Configuration
diff --git a/doc/index.html b/doc/index.html index f917202..44423b7 100644 --- a/doc/index.html +++ b/doc/index.html @@ -1,26 +1,30 @@ -The Mutt E-Mail Client
The Mutt E-Mail Client
   Next

The Mutt E-Mail Client

Michael Elkins

version 1.5.19 (2009-01-05)

Abstract

-“All mail clients suck. This one just sucks less.” -me, circa 1995 -

Table of Contents

1. Introduction
1. Mutt Home Page
2. Mailing Lists
3. Software Distribution Sites
4. Mutt online resources
5. Contributing to Mutt
6. Typograhical conventions
7. Copyright
2. Getting Started
1. Core concepts
2. Moving Around in Menus
3. Editing Input Fields
3.1. Introduction
3.2. History
4. Reading Mail - The Index and Pager
4.1. The Message Index
4.2. The Pager
4.3. Threaded Mode
4.4. Miscellaneous Functions
5. Sending Mail
5.1. Introduction
5.2. Editing the message header
5.3. Sending cryptographically signed/encrypted messages
5.4. Sending anonymous messages via mixmaster
5.5. Sending format=flowed messages
6. Forwarding and Bouncing Mail
7. Postponing Mail
3. Configuration
1. Location of initialization files
2. Syntax of Initialization Files
3. Address groups
4. Defining/Using aliases
5. Changing the default key bindings
6. Defining aliases for character sets
7. Setting variables based upon mailbox
8. Keyboard macros
9. Using color and mono video attributes
10. Message header display
11. Alternative addresses
12. Mailing lists
13. Using Multiple spool mailboxes
14. Monitoring incoming mail
15. User defined headers
16. Specify default save mailbox
17. Specify default Fcc: mailbox when composing
18. Specify default save filename and default Fcc: mailbox at once
19. Change settings based upon message recipients
20. Change settings before formatting a message
21. Choosing the cryptographic key of the recipient
22. Adding key sequences to the keyboard buffer
23. Executing functions
24. Message Scoring
25. Spam detection
26. Setting and Querying Variables
26.1. Commands
26.2. User-defined variables
27. Reading initialization commands from another file
28. Removing hooks
29. Format Strings
29.1. Basic usage
29.2. Filters
4. Advanced Usage
1. Regular Expressions
2. Patterns: Searching, Limiting and Tagging
2.1. Pattern Modifier
2.2. Simple Patterns
2.3. Complex Patterns
2.4. Searching by Date
3. Using Tags
4. Using Hooks
4.1. Message Matching in Hooks
5. External Address Queries
6. Mailbox Formats
7. Mailbox Shortcuts
8. Handling Mailing Lists
9. Handling multiple folders
10. Editing threads
10.1. Linking threads
10.2. Breaking threads
11. Delivery Status Notification (DSN) Support
12. Start a WWW Browser on URLs
5. Mutt's MIME Support
1. Using MIME in Mutt
1.1. Viewing MIME messages in the pager
1.2. The Attachment Menu
1.3. The Compose Menu
2. MIME Type configuration with mime.types
3. MIME Viewer configuration with mailcap
3.1. The Basics of the mailcap file
3.2. Secure use of mailcap
3.3. Advanced mailcap Usage
3.4. Example mailcap files
4. MIME Autoview
5. MIME Multipart/Alternative
6. Attachment Searching and Counting
7. MIME Lookup
6. Optional features
1. General notes
1.1. Enabling/disabling features
1.2. URL syntax
2. SSL/TLS Support
3. POP3 Support
4. IMAP Support
4.1. The Folder Browser
4.2. Authentication
5. SMTP Support
6. Managing multiple accounts
7. Local caching
7.1. Header caching
7.2. Body caching
7.3. Maintenance
8. Exact address generation
7. Performance tuning
1. Reading and writing mailboxes
2. Reading messages from remote folders
3. Searching and limiting
8. Reference
1. Command line options
2. Configuration Commands
3. Configuration variables
3.1. abort_nosubject
3.2. abort_unmodified
3.3. alias_file
3.4. alias_format
3.5. allow_8bit
3.6. allow_ansi
3.7. arrow_cursor
3.8. ascii_chars
3.9. askbcc
3.10. askcc
3.11. assumed_charset
3.12. attach_charset
3.13. attach_format
3.14. attach_sep
3.15. attach_split
3.16. attribution
3.17. autoedit
3.18. auto_tag
3.19. beep
3.20. beep_new
3.21. bounce
3.22. bounce_delivered
3.23. braille_friendly
3.24. check_mbox_size
3.25. charset
3.26. check_new
3.27. collapse_unread
3.28. uncollapse_jump
3.29. compose_format
3.30. config_charset
3.31. confirmappend
3.32. confirmcreate
3.33. connect_timeout
3.34. content_type
3.35. copy
3.36. crypt_use_gpgme
3.37. crypt_use_pka
3.38. crypt_autopgp
3.39. crypt_autosmime
3.40. date_format
3.41. default_hook
3.42. delete
3.43. delete_untag
3.44. digest_collapse
3.45. display_filter
3.46. dotlock_program
3.47. dsn_notify
3.48. dsn_return
3.49. duplicate_threads
3.50. edit_headers
3.51. editor
3.52. encode_from
3.53. envelope_from_address
3.54. escape
3.55. fast_reply
3.56. fcc_attach
3.57. fcc_clear
3.58. folder
3.59. folder_format
3.60. followup_to
3.61. force_name
3.62. forward_decode
3.63. forward_edit
3.64. forward_format
3.65. forward_quote
3.66. from
3.67. gecos_mask
3.68. hdrs
3.69. header
3.70. help
3.71. hidden_host
3.72. hide_limited
3.73. hide_missing
3.74. hide_thread_subject
3.75. hide_top_limited
3.76. hide_top_missing
3.77. history
3.78. history_file
3.79. honor_followup_to
3.80. hostname
3.81. ignore_linear_white_space
3.82. ignore_list_reply_to
3.83. imap_authenticators
3.84. imap_check_subscribed
3.85. imap_delim_chars
3.86. imap_headers
3.87. imap_idle
3.88. imap_keepalive
3.89. imap_list_subscribed
3.90. imap_login
3.91. imap_pass
3.92. imap_passive
3.93. imap_peek
3.94. imap_pipeline_depth
3.95. imap_servernoise
3.96. imap_user
3.97. implicit_autoview
3.98. include
3.99. include_onlyfirst
3.100. indent_string
3.101. index_format
3.102. ispell
3.103. keep_flagged
3.104. locale
3.105. mail_check
3.106. mailcap_path
3.107. mailcap_sanitize
3.108. header_cache
3.109. maildir_header_cache_verify
3.110. header_cache_pagesize
3.111. header_cache_compress
3.112. maildir_trash
3.113. mark_old
3.114. markers
3.115. mask
3.116. mbox
3.117. mbox_type
3.118. metoo
3.119. menu_context
3.120. menu_move_off
3.121. menu_scroll
3.122. meta_key
3.123. mh_purge
3.124. mh_seq_flagged
3.125. mh_seq_replied
3.126. mh_seq_unseen
3.127. mime_forward
3.128. mime_forward_decode
3.129. mime_forward_rest
3.130. mix_entry_format
3.131. mixmaster
3.132. move
3.133. message_cachedir
3.134. message_cache_clean
3.135. message_format
3.136. narrow_tree
3.137. net_inc
3.138. pager
3.139. pager_context
3.140. pager_format
3.141. pager_index_lines
3.142. pager_stop
3.143. crypt_autosign
3.144. crypt_autoencrypt
3.145. pgp_ignore_subkeys
3.146. crypt_replyencrypt
3.147. crypt_replysign
3.148. crypt_replysignencrypted
3.149. crypt_timestamp
3.150. pgp_use_gpg_agent
3.151. crypt_verify_sig
3.152. smime_is_default
3.153. smime_ask_cert_label
3.154. smime_decrypt_use_default_key
3.155. pgp_entry_format
3.156. pgp_good_sign
3.157. pgp_check_exit
3.158. pgp_long_ids
3.159. pgp_retainable_sigs
3.160. pgp_autoinline
3.161. pgp_replyinline
3.162. pgp_show_unusable
3.163. pgp_sign_as
3.164. pgp_strict_enc
3.165. pgp_timeout
3.166. pgp_sort_keys
3.167. pgp_mime_auto
3.168. pgp_auto_decode
3.169. pgp_decode_command
3.170. pgp_getkeys_command
3.171. pgp_verify_command
3.172. pgp_decrypt_command
3.173. pgp_clearsign_command
3.174. pgp_sign_command
3.175. pgp_encrypt_sign_command
3.176. pgp_encrypt_only_command
3.177. pgp_import_command
3.178. pgp_export_command
3.179. pgp_verify_key_command
3.180. pgp_list_secring_command
3.181. pgp_list_pubring_command
3.182. forward_decrypt
3.183. smime_timeout
3.184. smime_encrypt_with
3.185. smime_keys
3.186. smime_ca_location
3.187. smime_certificates
3.188. smime_decrypt_command
3.189. smime_verify_command
3.190. smime_verify_opaque_command
3.191. smime_sign_command
3.192. smime_sign_opaque_command
3.193. smime_encrypt_command
3.194. smime_pk7out_command
3.195. smime_get_cert_command
3.196. smime_get_signer_cert_command
3.197. smime_import_cert_command
3.198. smime_get_cert_email_command
3.199. smime_default_key
3.200. ssl_client_cert
3.201. ssl_force_tls
3.202. ssl_starttls
3.203. certificate_file
3.204. ssl_usesystemcerts
3.205. entropy_file
3.206. ssl_use_sslv2
3.207. ssl_use_sslv3
3.208. ssl_use_tlsv1
3.209. ssl_min_dh_prime_bits
3.210. ssl_ca_certificates_file
3.211. pipe_split
3.212. pipe_decode
3.213. pipe_sep
3.214. pop_authenticators
3.215. pop_auth_try_all
3.216. pop_checkinterval
3.217. pop_delete
3.218. pop_host
3.219. pop_last
3.220. pop_reconnect
3.221. pop_user
3.222. pop_pass
3.223. post_indent_string
3.224. postpone
3.225. postponed
3.226. preconnect
3.227. print
3.228. print_command
3.229. print_decode
3.230. print_split
3.231. prompt_after
3.232. query_command
3.233. query_format
3.234. quit
3.235. quote_regexp
3.236. read_inc
3.237. read_only
3.238. realname
3.239. recall
3.240. record
3.241. reply_regexp
3.242. reply_self
3.243. reply_to
3.244. resolve
3.245. reverse_alias
3.246. reverse_name
3.247. reverse_realname
3.248. rfc2047_parameters
3.249. save_address
3.250. save_empty
3.251. save_history
3.252. save_name
3.253. score
3.254. score_threshold_delete
3.255. score_threshold_flag
3.256. score_threshold_read
3.257. send_charset
3.258. sendmail
3.259. sendmail_wait
3.260. shell
3.261. sig_dashes
3.262. sig_on_top
3.263. signature
3.264. simple_search
3.265. smart_wrap
3.266. smileys
3.267. sleep_time
3.268. smtp_authenticators
3.269. smtp_pass
3.270. smtp_url
3.271. sort
3.272. sort_alias
3.273. sort_aux
3.274. sort_browser
3.275. sort_re
3.276. spam_separator
3.277. spoolfile
3.278. status_chars
3.279. status_format
3.280. status_on_top
3.281. strict_threads
3.282. suspend
3.283. text_flowed
3.284. thread_received
3.285. thorough_search
3.286. tilde
3.287. time_inc
3.288. timeout
3.289. tmpdir
3.290. to_chars
3.291. tunnel
3.292. use_8bitmime
3.293. use_domain
3.294. use_envelope_from
3.295. use_from
3.296. use_idn
3.297. use_ipv6
3.298. user_agent
3.299. visual
3.300. wait_key
3.301. weed
3.302. wrap
3.303. wrap_search
3.304. wrapmargin
3.305. write_inc
3.306. write_bcc
4. Functions
4.1. generic menu
4.2. index menu
4.3. pager menu
4.4. alias menu
4.5. query menu
4.6. attach menu
4.7. compose menu
4.8. postpone menu
4.9. browser menu
4.10. pgp menu
4.11. smime menu
4.12. mix menu
4.13. editor menu
9. Miscellany
1. Acknowledgements
2. About this document

List of Tables

1.1. Typographical conventions for special terms
2.1. Most common navigation keys
2.2. Most common line editor keys
2.3. Most common message index keys
2.4. Message status flags
2.5. Message recipient flags
2.6. Most common pager keys
2.7. ANSI escape sequences
2.8. Color sequences
2.9. Most common thread mode keys
2.10. Most common mail sending keys
2.11. Most common compose menu keys
2.12. PGP key menu flags
3.1. Symbolic key names
4.1. POSIX regular expression character classes
4.2. Regular expression repetition operators
4.3. GNU regular expression extensions
4.4. Pattern modifiers
4.5. Simple search keywords
4.6. Date units
8.1. Command line options
8.2. Default generic function bindings
8.3. Default index function bindings
8.4. Default pager function bindings
8.5. Default alias function bindings
8.6. Default query function bindings
8.7. Default attach function bindings
8.8. Default compose function bindings
8.9. Default postpone function bindings
8.10. Default browser function bindings
8.11. Default pgp function bindings
8.12. Default smime function bindings
8.13. Default mix function bindings
8.14. Default editor function bindings

List of Examples

3.1. Multiple configuration commands per line
3.2. Commenting configuration files
3.3. Escaping quotes in congfiguration files
3.4. Using external command's output in configuration files
3.5. Using environment variables in configuration files
3.6. Configuring external alias files
3.7. Setting sort method based on mailbox name
3.8. Header weeding
3.9. Configuring header display order
3.10. Defining custom headers
3.11. Using %-expandos in save-hook
3.12. Embedding push in folder-hook
3.13. Configuring spam detection
3.14. Using user-defined variables for config file readability
3.15. Using user-defined variables for backing up other config option values
3.16. Deferring user-defined variable expansion to runtime
3.17. Using external filters in format strings
4.1. Using boolean operators in patterns
4.2. Combining send-hook and my_hdr
5.1. Attachment counting
   Next
   Chapter 1. Introduction
+
The Mutt E-Mail Client
   Next

The Mutt E-Mail Client

Michael Elkins

version 1.5.20 (2009-06-14)

Abstract

+“All mail clients suck. This one just sucks less.” — me, circa 1995 +

Table of Contents

1. Introduction
1. Mutt Home Page
2. Mailing Lists
3. Getting Mutt
4. Mutt Online Resources
5. Contributing to Mutt
6. Typograhical Conventions
7. Copyright
2. Getting Started
1. Core Concepts
2. Screens and Menus
2.1. Index
2.2. Pager
2.3. File Browser
2.4. Help
2.5. Compose Menu
2.6. Alias Menu
2.7. Attachment Menu
3. Moving Around in Menus
4. Editing Input Fields
4.1. Introduction
4.2. History
5. Reading Mail
5.1. The Message Index
5.2. The Pager
5.3. Threaded Mode
5.4. Miscellaneous Functions
6. Sending Mail
6.1. Introduction
6.2. Editing the Message Header
6.3. Sending Cryptographically Signed/Encrypted Messages
6.4. Sending Format=Flowed Messages
7. Forwarding and Bouncing Mail
8. Postponing Mail
3. Configuration
1. Location of Initialization Files
2. Syntax of Initialization Files
3. Address Groups
4. Defining/Using Aliases
5. Changing the Default Key Bindings
6. Defining Aliases for Character Sets
7. Setting Variables Based Upon Mailbox
8. Keyboard Macros
9. Using Color and Mono Video Attributes
10. Message Header Display
10.1. Selecting Headers
10.2. Ordering Displayed Headers
11. Alternative Addresses
12. Mailing Lists
13. Using Multiple Spool Mailboxes
14. Monitoring Incoming Mail
15. User-Defined Headers
16. Specify Default Save Mailbox
17. Specify Default Fcc: Mailbox When Composing
18. Specify Default Save Filename and Default Fcc: Mailbox at Once
19. Change Settings Based Upon Message Recipients
20. Change Settings Before Formatting a Message
21. Choosing the Cryptographic Key of the Recipient
22. Adding Key Sequences to the Keyboard Buffer
23. Executing Functions
24. Message Scoring
25. Spam Detection
26. Setting and Querying Variables
26.1. Variable Types
26.2. Commands
26.3. User-Defined Variables
27. Reading Initialization Commands From Another File
28. Removing Hooks
29. Format Strings
29.1. Basic usage
29.2. Conditionals
29.3. Filters
29.4. Padding
4. Advanced Usage
1. Regular Expressions
2. Patterns: Searching, Limiting and Tagging
2.1. Pattern Modifier
2.2. Simple Searches
2.3. Nesting and Boolean Operators
2.4. Searching by Date
3. Using Tags
4. Using Hooks
4.1. Message Matching in Hooks
5. External Address Queries
6. Mailbox Formats
7. Mailbox Shortcuts
8. Handling Mailing Lists
9. Handling multiple folders
10. Editing Threads
10.1. Linking Threads
10.2. Breaking Threads
11. Delivery Status Notification (DSN) Support
12. Start a WWW Browser on URLs
13. Miscellany
5. Mutt's MIME Support
1. Using MIME in Mutt
1.1. Viewing MIME Messages in the Pager
1.2. The Attachment Menu
1.3. The Compose Menu
2. MIME Type Configuration with mime.types
3. MIME Viewer Configuration with Mailcap
3.1. The Basics of the Mailcap File
3.2. Secure Use of Mailcap
3.3. Advanced Mailcap Usage
3.4. Example Mailcap Files
4. MIME Autoview
5. MIME Multipart/Alternative
6. Attachment Searching and Counting
7. MIME Lookup
6. Optional Features
1. General Notes
1.1. Enabling/Disabling Features
1.2. URL Syntax
2. SSL/TLS Support
3. POP3 Support
4. IMAP Support
4.1. The IMAP Folder Browser
4.2. Authentication
5. SMTP Support
6. Managing Multiple Accounts
7. Local Caching
7.1. Header Caching
7.2. Body Caching
7.3. Maintenance
8. Exact Address Generation
9. Sending Anonymous Messages via Mixmaster
7. Security Considerations
1. Passwords
2. Temporary Files
3. Information Leaks
3.1. Message-Id: headers
3.2. mailto:-style Links
4. External Applications
8. Performance Tuning
1. Reading and Writing Mailboxes
2. Reading Messages from Remote Folders
3. Searching and Limiting
9. Reference
1. Command-Line Options
2. Configuration Commands
3. Configuration Variables
3.1. abort_nosubject
3.2. abort_unmodified
3.3. alias_file
3.4. alias_format
3.5. allow_8bit
3.6. allow_ansi
3.7. arrow_cursor
3.8. ascii_chars
3.9. askbcc
3.10. askcc
3.11. assumed_charset
3.12. attach_charset
3.13. attach_format
3.14. attach_sep
3.15. attach_split
3.16. attribution
3.17. auto_tag
3.18. autoedit
3.19. beep
3.20. beep_new
3.21. bounce
3.22. bounce_delivered
3.23. braille_friendly
3.24. certificate_file
3.25. charset
3.26. check_mbox_size
3.27. check_new
3.28. collapse_unread
3.29. compose_format
3.30. config_charset
3.31. confirmappend
3.32. confirmcreate
3.33. connect_timeout
3.34. content_type
3.35. copy
3.36. crypt_autoencrypt
3.37. crypt_autopgp
3.38. crypt_autosign
3.39. crypt_autosmime
3.40. crypt_replyencrypt
3.41. crypt_replysign
3.42. crypt_replysignencrypted
3.43. crypt_timestamp
3.44. crypt_use_gpgme
3.45. crypt_use_pka
3.46. crypt_verify_sig
3.47. date_format
3.48. default_hook
3.49. delete
3.50. delete_untag
3.51. digest_collapse
3.52. display_filter
3.53. dotlock_program
3.54. dsn_notify
3.55. dsn_return
3.56. duplicate_threads
3.57. edit_headers
3.58. editor
3.59. encode_from
3.60. entropy_file
3.61. envelope_from_address
3.62. escape
3.63. fast_reply
3.64. fcc_attach
3.65. fcc_clear
3.66. folder
3.67. folder_format
3.68. followup_to
3.69. force_name
3.70. forward_decode
3.71. forward_decrypt
3.72. forward_edit
3.73. forward_format
3.74. forward_quote
3.75. from
3.76. gecos_mask
3.77. hdrs
3.78. header
3.79. header_cache
3.80. header_cache_compress
3.81. header_cache_pagesize
3.82. help
3.83. hidden_host
3.84. hide_limited
3.85. hide_missing
3.86. hide_thread_subject
3.87. hide_top_limited
3.88. hide_top_missing
3.89. history
3.90. history_file
3.91. honor_disposition
3.92. honor_followup_to
3.93. hostname
3.94. ignore_linear_white_space
3.95. ignore_list_reply_to
3.96. imap_authenticators
3.97. imap_check_subscribed
3.98. imap_delim_chars
3.99. imap_headers
3.100. imap_idle
3.101. imap_keepalive
3.102. imap_list_subscribed
3.103. imap_login
3.104. imap_pass
3.105. imap_passive
3.106. imap_peek
3.107. imap_pipeline_depth
3.108. imap_servernoise
3.109. imap_user
3.110. implicit_autoview
3.111. include
3.112. include_onlyfirst
3.113. indent_string
3.114. index_format
3.115. ispell
3.116. keep_flagged
3.117. locale
3.118. mail_check
3.119. mailcap_path
3.120. mailcap_sanitize
3.121. maildir_header_cache_verify
3.122. maildir_trash
3.123. mark_old
3.124. markers
3.125. mask
3.126. mbox
3.127. mbox_type
3.128. menu_context
3.129. menu_move_off
3.130. menu_scroll
3.131. message_cache_clean
3.132. message_cachedir
3.133. message_format
3.134. meta_key
3.135. metoo
3.136. mh_purge
3.137. mh_seq_flagged
3.138. mh_seq_replied
3.139. mh_seq_unseen
3.140. mime_forward
3.141. mime_forward_decode
3.142. mime_forward_rest
3.143. mix_entry_format
3.144. mixmaster
3.145. move
3.146. narrow_tree
3.147. net_inc
3.148. pager
3.149. pager_context
3.150. pager_format
3.151. pager_index_lines
3.152. pager_stop
3.153. pgp_auto_decode
3.154. pgp_autoinline
3.155. pgp_check_exit
3.156. pgp_clearsign_command
3.157. pgp_decode_command
3.158. pgp_decrypt_command
3.159. pgp_encrypt_only_command
3.160. pgp_encrypt_sign_command
3.161. pgp_entry_format
3.162. pgp_export_command
3.163. pgp_getkeys_command
3.164. pgp_good_sign
3.165. pgp_ignore_subkeys
3.166. pgp_import_command
3.167. pgp_list_pubring_command
3.168. pgp_list_secring_command
3.169. pgp_long_ids
3.170. pgp_mime_auto
3.171. pgp_replyinline
3.172. pgp_retainable_sigs
3.173. pgp_show_unusable
3.174. pgp_sign_as
3.175. pgp_sign_command
3.176. pgp_sort_keys
3.177. pgp_strict_enc
3.178. pgp_timeout
3.179. pgp_use_gpg_agent
3.180. pgp_verify_command
3.181. pgp_verify_key_command
3.182. pipe_decode
3.183. pipe_sep
3.184. pipe_split
3.185. pop_auth_try_all
3.186. pop_authenticators
3.187. pop_checkinterval
3.188. pop_delete
3.189. pop_host
3.190. pop_last
3.191. pop_pass
3.192. pop_reconnect
3.193. pop_user
3.194. post_indent_string
3.195. postpone
3.196. postponed
3.197. preconnect
3.198. print
3.199. print_command
3.200. print_decode
3.201. print_split
3.202. prompt_after
3.203. query_command
3.204. query_format
3.205. quit
3.206. quote_regexp
3.207. read_inc
3.208. read_only
3.209. realname
3.210. recall
3.211. record
3.212. reply_regexp
3.213. reply_self
3.214. reply_to
3.215. resolve
3.216. reverse_alias
3.217. reverse_name
3.218. reverse_realname
3.219. rfc2047_parameters
3.220. save_address
3.221. save_empty
3.222. save_history
3.223. save_name
3.224. score
3.225. score_threshold_delete
3.226. score_threshold_flag
3.227. score_threshold_read
3.228. search_context
3.229. send_charset
3.230. sendmail
3.231. sendmail_wait
3.232. shell
3.233. sig_dashes
3.234. sig_on_top
3.235. signature
3.236. simple_search
3.237. sleep_time
3.238. smart_wrap
3.239. smileys
3.240. smime_ask_cert_label
3.241. smime_ca_location
3.242. smime_certificates
3.243. smime_decrypt_command
3.244. smime_decrypt_use_default_key
3.245. smime_default_key
3.246. smime_encrypt_command
3.247. smime_encrypt_with
3.248. smime_get_cert_command
3.249. smime_get_cert_email_command
3.250. smime_get_signer_cert_command
3.251. smime_import_cert_command
3.252. smime_is_default
3.253. smime_keys
3.254. smime_pk7out_command
3.255. smime_sign_command
3.256. smime_sign_opaque_command
3.257. smime_timeout
3.258. smime_verify_command
3.259. smime_verify_opaque_command
3.260. smtp_authenticators
3.261. smtp_pass
3.262. smtp_url
3.263. sort
3.264. sort_alias
3.265. sort_aux
3.266. sort_browser
3.267. sort_re
3.268. spam_separator
3.269. spoolfile
3.270. ssl_ca_certificates_file
3.271. ssl_client_cert
3.272. ssl_force_tls
3.273. ssl_min_dh_prime_bits
3.274. ssl_starttls
3.275. ssl_use_sslv2
3.276. ssl_use_sslv3
3.277. ssl_use_tlsv1
3.278. ssl_usesystemcerts
3.279. ssl_verify_dates
3.280. ssl_verify_host
3.281. status_chars
3.282. status_format
3.283. status_on_top
3.284. strict_threads
3.285. suspend
3.286. text_flowed
3.287. thorough_search
3.288. thread_received
3.289. tilde
3.290. time_inc
3.291. timeout
3.292. tmpdir
3.293. to_chars
3.294. tunnel
3.295. uncollapse_jump
3.296. use_8bitmime
3.297. use_domain
3.298. use_envelope_from
3.299. use_from
3.300. use_idn
3.301. use_ipv6
3.302. user_agent
3.303. visual
3.304. wait_key
3.305. weed
3.306. wrap
3.307. wrap_search
3.308. wrapmargin
3.309. write_bcc
3.310. write_inc
4. Functions
4.1. Generic Menu
4.2. Index Menu
4.3. Pager Menu
4.4. Alias Menu
4.5. Query Menu
4.6. Attach Menu
4.7. Compose Menu
4.8. Postpone Menu
4.9. Browser Menu
4.10. Pgp Menu
4.11. Smime Menu
4.12. Mix Menu
4.13. Editor Menu
10. Miscellany
1. Acknowledgements
2. About This Document

List of Tables

1.1. Typographical conventions for special terms
2.1. Most common navigation keys in entry-based menus
2.2. Most common navigation keys in page-based menus
2.3. Most common line editor keys
2.4. Most common message index keys
2.5. Message status flags
2.6. Message recipient flags
2.7. Most common pager keys
2.8. ANSI escape sequences
2.9. Color sequences
2.10. Most common thread mode keys
2.11. Most common mail sending keys
2.12. Most common compose menu keys
2.13. PGP key menu flags
3.1. Symbolic key names
4.1. POSIX regular expression character classes
4.2. Regular expression repetition operators
4.3. GNU regular expression extensions
4.4. Pattern modifiers
4.5. Simple search keywords
4.6. Date units
9.1. Command line options
9.2. Default generic Function Bindings
9.3. Default index Function Bindings
9.4. Default pager Function Bindings
9.5. Default alias Function Bindings
9.6. Default query Function Bindings
9.7. Default attach Function Bindings
9.8. Default compose Function Bindings
9.9. Default postpone Function Bindings
9.10. Default browser Function Bindings
9.11. Default pgp Function Bindings
9.12. Default smime Function Bindings
9.13. Default mix Function Bindings
9.14. Default editor Function Bindings

List of Examples

3.1. Multiple configuration commands per line
3.2. Commenting configuration files
3.3. Escaping quotes in congfiguration files
3.4. Splitting long configuration commands over several lines
3.5. Using external command's output in configuration files
3.6. Using environment variables in configuration files
3.7. Configuring external alias files
3.8. Setting sort method based on mailbox name
3.9. Header weeding
3.10. Configuring header display order
3.11. Defining custom headers
3.12. Using %-expandos in save-hook
3.13. Embedding push in folder-hook
3.14. Configuring spam detection
3.15. Using user-defined variables for config file readability
3.16. Using user-defined variables for backing up other config option values
3.17. Deferring user-defined variable expansion to runtime
3.18. Using external filters in format strings
4.1. Matching all addresses in address lists
4.2. Using boolean operators in patterns
4.3. Specifying a default hook
5.1. Attachment counting
6.1. URLs
6.2. Managing multiple accounts
   Next
   Chapter 1. Introduction
diff --git a/doc/intro.html b/doc/intro.html index b9c322b..7e5afc7 100644 --- a/doc/intro.html +++ b/doc/intro.html @@ -1,27 +1,31 @@ -Chapter 1. Introduction
Chapter 1. Introduction
Prev   Next

Chapter 1. Introduction

Table of Contents

1. Mutt Home Page
2. Mailing Lists
3. Software Distribution Sites
4. Mutt online resources
5. Contributing to Mutt
6. Typograhical conventions
7. Copyright

+

Chapter 1. Introduction
Prev   Next

Chapter 1. Introduction

Table of Contents

1. Mutt Home Page
2. Mailing Lists
3. Getting Mutt
4. Mutt Online Resources
5. Contributing to Mutt
6. Typograhical Conventions
7. Copyright

Mutt is a small but very powerful text-based MIME mail client. Mutt is highly configurable, and is well suited to the mail power user with advanced features like key bindings, keyboard macros, mail threading, regular @@ -45,14 +49,17 @@ All messages posted to mutt-announce are automatically forwarded to mutt-users, so you do not need to be subscribed to both lists. -

3. Software Distribution Sites

+

3. Getting Mutt

Mutt releases can be downloaded from ftp://ftp.mutt.org/mutt/. For a list of mirror sites, please refer to http://www.mutt.org/download.html. -

4. Mutt online resources

Bug Tracking System

-The official mutt bug tracking system can be found at -http://dev.mutt.org/ +

+For nightly tarballs and version control access, please refer to the +Mutt development site. +

4. Mutt Online Resources

Bug Tracking System

+The official Mutt bug tracking system can be found at +http://bugs.mutt.org/

Wiki

An (unofficial) wiki can be found at http://wiki.mutt.org/. @@ -69,17 +76,17 @@ experienced users to chat about Mutt, talk about problems and share tricks.

Since translations of Mutt into other languages are highly appreciated, -the mutt developers always look for skilled translators that help +the Mutt developers always look for skilled translators that help improve and continue to maintain stale translations.

For contributing code patches for new features and bug fixes, please refer to the developer pages at http://dev.mutt.org/ for more details. -

6. Typograhical conventions

+

6. Typograhical Conventions

This section lists typographical conventions followed throughout this manual. See table Table 1.1, “Typographical conventions for special terms” for typographical conventions for special terms. -

Table 1.1. Typographical conventions for special terms

ItemRefers to...
printf(3)UNIX manual pages, execute man 3 printf
<PageUp>named keys
<create-alias>named Mutt function
^GControl+G key combination
$mail_checkMutt configuration option

+

Table 1.1. Typographical conventions for special terms

ItemRefers to...
printf(3)UNIX manual pages, execute man 3 printf
<PageUp>named keys
<create-alias>named Mutt function
^GControl+G key combination
$mail_checkMutt configuration option
$HOMEenvironment variable

Examples are presented as: 

 mutt -v
@@ -89,7 +96,7 @@ of options of which one is mandatory, square brackets
 (“[]”) denote optional arguments, three dots
 denote that the argument may be repeated arbitrary times.

7. Copyright

-Mutt is Copyright (C) 1996-2009 Michael R. Elkins +Mutt is Copyright © 1996-2009 Michael R. Elkins and others.

This program is free software; you can redistribute it and/or modify diff --git a/doc/makedoc.c b/doc/makedoc.c index 8075d58..07d3405 100644 --- a/doc/makedoc.c +++ b/doc/makedoc.c @@ -576,6 +576,8 @@ static void man_print_strval (const char *v, FILE *out) fputs ("\\(rq", out); else if (*v == '\\') fputs ("\\\\", out); + else if (*v == '-') + fputs ("\\-", out); else fputc (*v, out); } @@ -697,8 +699,11 @@ static void print_confline (const char *varname, int type, const char *val, FILE man_print_strval (val, out); fputs ("\\(rq\n", out); } - else - fprintf (out, "Default: %s\n", val); + else { + fputs ("Default: ", out); + man_print_strval (val, out); + fputs ("\n", out); + } fputs (".fi", out); @@ -1040,6 +1045,8 @@ static int print_it (int special, char *str, FILE *out, int docstat) fputs ("\\(rq", out); else if (*str == '\\') fputs ("\\\\", out); + else if (*str == '-') + fputs ("\\-", out); else if (!strncmp (str, "``", 2)) { fputs ("\\(lq", out); @@ -1143,7 +1150,7 @@ static int print_it (int special, char *str, FILE *out, int docstat) } case SP_END_TAB: { - fputs ("\n", out); + fputs ("", out); docstat &= ~D_TAB; docstat |= D_NL; break; @@ -1155,34 +1162,36 @@ static int print_it (int special, char *str, FILE *out, int docstat) fputs ("\n\n", out); docstat &= ~D_PA; } - fputs ("\n\n", out); + fputs ("\n\n\n
ItemRefers to...
printf(3)UNIX manual pages, execute man 3 printf
<PageUp>named keys
<create-alias>named Mutt function
^GControl+G key combination
$mail_checkMutt configuration option

+

Table 1.1. Typographical conventions for special terms

ItemRefers to...
printf(3)UNIX manual pages, execute man 3 printf
<PageUp>named keys
<create-alias>named Mutt function
^GControl+G key combination
$mail_checkMutt configuration option
$HOMEenvironment variable

Examples are presented as: 

 mutt -v
@@ -90,7 +98,7 @@ of options of which one is mandatory, square brackets
 (“[]”) denote optional arguments, three dots
 denote that the argument may be repeated arbitrary times.

7. Copyright

-Mutt is Copyright (C) 1996-2009 Michael R. Elkins +Mutt is Copyright © 1996-2009 Michael R. Elkins and others.

This program is free software; you can redistribute it and/or modify @@ -106,7 +114,7 @@ GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. -

Chapter 2. Getting Started

Table of Contents

1. Core concepts
2. Moving Around in Menus
3. Editing Input Fields
3.1. Introduction
3.2. History
4. Reading Mail - The Index and Pager
4.1. The Message Index
4.2. The Pager
4.3. Threaded Mode
4.4. Miscellaneous Functions
5. Sending Mail
5.1. Introduction
5.2. Editing the message header
5.3. Sending cryptographically signed/encrypted messages
5.4. Sending anonymous messages via mixmaster
5.5. Sending format=flowed messages
6. Forwarding and Bouncing Mail
7. Postponing Mail

+

Chapter 2. Getting Started

Table of Contents

1. Core Concepts
2. Screens and Menus
2.1. Index
2.2. Pager
2.3. File Browser
2.4. Help
2.5. Compose Menu
2.6. Alias Menu
2.7. Attachment Menu
3. Moving Around in Menus
4. Editing Input Fields
4.1. Introduction
4.2. History
5. Reading Mail
5.1. The Message Index
5.2. The Pager
5.3. Threaded Mode
5.4. Miscellaneous Functions
6. Sending Mail
6.1. Introduction
6.2. Editing the Message Header
6.3. Sending Cryptographically Signed/Encrypted Messages
6.4. Sending Format=Flowed Messages
7. Forwarding and Bouncing Mail
8. Postponing Mail

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 various web @@ -116,10 +124,10 @@ The keybindings described in this section are the defaults as distributed. Your local system administrator may have altered the defaults for your site. You can always type “?” in any menu to display the current bindings.

-The first thing you need to do is invoke mutt, simply by typing mutt +The first thing you need to do is invoke Mutt, simply by typing mutt at the command line. There are various command-line options, see -either the mutt man page or the reference. -

1. Core concepts

+either the Mutt man page or the reference. +

1. Core Concepts

Mutt is a text-based application which interacts with users through different menus which are mostly line-/entry-based or page-based. A line-based menu is the so-called “index” menu (listing all messages of @@ -134,6 +142,11 @@ finally the command line. The command line is used to display informational and error messages as well as for prompts and for entering interactive commands.

+Mutt is configured through variables which, if the user wants to +permanently use a non-default value, are written to configuration +files. Mutt supports a rich config file syntax to make even complex +configuration files readable and commentable. +

Because Mutt allows for customizing almost all key bindings, there are so-called “functions” which can be executed manually (using the command line) or in macros. Macros allow the user to bind a sequence of @@ -157,69 +170,143 @@ existing one. These hooks can be used to highly customize Mutt's behaviour including managing multiple identities, customizing the display for a folder or even implementing auto-archiving based on a per-folder basis and much more. -

2. Moving Around in Menus

-The most important navigation keys common to all menus are shown in -Table 2.1, “Most common navigation keys”. -

Table 2.1. Most common navigation keys

KeyFunctionDescription
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
Z or <PageUp><page-up>go to the previous page
= or <Home><first-entry>jump to the first entry
* or <End><last-entry>jump to the last entry
q<quit>exit the current menu
?<help>list all keybindings for the current menu

3. Editing Input Fields

3.1. Introduction

+

+Besides an interactive mode, Mutt can also be used as a command-line +tool only send messages. It also supports a +mailx(1)-compatible interface, see Table 9.1, “Command line options” for a complete list of command-line +options. +

2. Screens and Menus

2.1. Index

+The index is the screen that you usually see first when you start +Mutt. It gives an overview over your emails in the currently opened +mailbox. By default, this is your system mailbox. The information you +see in the index is a list of emails, each with its number on the left, +its flags (new email, important email, email that has been forwarded or +replied to, tagged email, ...), the date when email was sent, its +sender, the email size, and the subject. Additionally, the index also +shows thread hierarchies: when you reply to an email, and the other +person replies back, you can see the other's person email in a +"sub-tree" below. This is especially useful for personal email between +a group of people or when you've subscribed to mailing lists. +

2.2. Pager

+The pager is responsible for showing the email content. On the top of +the pager you have an overview over the most important email headers +like the sender, the recipient, the subject, and much more +information. How much information you actually see depends on your +configuration, which we'll describe below. +

+Below the headers, you see the email body which usually contains the +message. If the email contains any attachments, you will see more +information about them below the email body, or, if the attachments are +text files, you can view them directly in the pager. +

+To give the user a good overview, it is possible to configure Mutt to +show different things in the pager with different colors. Virtually +everything that can be described with a regular expression can be +colored, e.g. URLs, email addresses or smileys. +

2.3. File Browser

+The file browser is the interface to the local or remote file +system. When selecting a mailbox to open, the browser allows custom +sorting of items, limiting the items shown by a regular expression and a +freely adjustable format of what to display in which way. It also allows +for easy navigation through the file system when selecting file(s) to +attach to a message, select multiple files to attach and many more. +

2.4. Help

+The help screen is meant to offer a quick help to the user. It lists the +current configuration of key bindings and their associated commands +including a short description, and currently unbound functions that +still need to be associated with a key binding (or alternatively, they +can be called via the Mutt command prompt). +

2.5. Compose Menu

+The compose menu features a split screen containing the information +which really matter before actually sending a message by mail: who gets +the message as what (recipients and who gets what kind of +copy). Additionally, users may set security options like deciding +whether to sign, encrypt or sign and encrypt a message with/for what +keys. Also, it's used to attach messages, to re-edit any attachment +including the message itself. +

2.6. Alias Menu

+The alias menu is used to help users finding the recipients of +messages. For users who need to contact many people, there's no need to +remember addresses or names completely because it allows for searching, +too. The alias mechanism and thus the alias menu also features grouping +several addresses by a shorter nickname, the actual alias, so that users +don't have to select each single recipient manually. +

2.7. Attachment Menu

+As will be later discussed in detail, Mutt features a good and stable +MIME implementation, that is, it supports sending and receiving messages +of arbitrary MIME types. The attachment menu displays a message's +structure in detail: what content parts are attached to which parent +part (which gives a true tree structure), which type is of what type and +what size. Single parts may saved, deleted or modified to offer great +and easy access to message's internals. +

3. Moving Around in Menus

+The most important navigation keys common to line- or entry-based menus +are shown in Table 2.1, “Most common navigation keys in entry-based menus” and in +Table 2.2, “Most common navigation keys in page-based menus” for page-based menus. +

Table 2.1. Most common navigation keys in entry-based menus

KeyFunctionDescription
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
Z or <PageUp><page-up>go to the previous page
= or <Home><first-entry>jump to the first entry
* or <End><last-entry>jump to the last entry
q<quit>exit the current menu
?<help>list all keybindings for the current menu

Table 2.2. Most common navigation keys in page-based menus

KeyFunctionDescription
J or <Return><next-line>scroll down one line
<Backspace><previous-line>sroll up one line
K, <Space> or <PageDn><next-page>move to the next page
- or <PageUp><previous-page>move the previous page
<Home><top>move to the top
<End><bottom>move to the bottom

4. Editing Input Fields

4.1. Introduction

Mutt has a built-in line editor for inputting text, e.g. email addresses or filenames. The keys used to manipulate text input are -very similar to those of Emacs. See Table 2.2, “Most common line editor keys” for a full +very similar to those of Emacs. See Table 2.3, “Most common line editor keys” for a full reference of available functions, their default key bindings, and short descriptions. -

Table 2.2. Most common line editor keys

KeyFunctionDescription
^A or <Home><bol>move to the start of the line
^B or <Left><backward-char>move back one char
Esc B<backward-word>move back one word
^D or <Delete><delete-char>delete the char under the cursor
^E or <End><eol>move to the end of the line
^F or <Right><forward-char>move forward one char
Esc F<forward-word>move forward one word
<Tab><complete>complete filename or alias
^T<complete-query>complete address with query
^K<kill-eol>delete to the end of the line
Esc d<kill-eow>delete to the end of the word
^W<kill-word>kill the word in front of the cursor
^U<kill-line>delete entire line
^V<quote-char>quote the next typed key
<Up><history-up>recall previous string from history
<Down><history-down>recall next string from history
<BackSpace><backspace>kill the char in front of the cursor
Esc u<upcase-word>convert word to upper case
Esc l<downcase-word>convert word to lower case
Esc c<capitalize-word>capitalize the word
^Gn/aabort
<Return>n/afinish editing

+

Table 2.3. Most common line editor keys

KeyFunctionDescription
^A or <Home><bol>move to the start of the line
^B or <Left><backward-char>move back one char
Esc B<backward-word>move back one word
^D or <Delete><delete-char>delete the char under the cursor
^E or <End><eol>move to the end of the line
^F or <Right><forward-char>move forward one char
Esc F<forward-word>move forward one word
<Tab><complete>complete filename or alias
^T<complete-query>complete address with query
^K<kill-eol>delete to the end of the line
Esc d<kill-eow>delete to the end of the word
^W<kill-word>kill the word in front of the cursor
^U<kill-line>delete entire line
^V<quote-char>quote the next typed key
<Up><history-up>recall previous string from history
<Down><history-down>recall next string from history
<BackSpace><backspace>kill the char in front of the cursor
Esc u<upcase-word>convert word to upper case
Esc l<downcase-word>convert word to lower case
Esc c<capitalize-word>capitalize the word
^Gn/aabort
<Return>n/afinish editing

You can remap the editor functions using the -bind command. For example, to make +bind command. For example, to make the <Delete> key delete the character in front of the cursor rather than under, you could use: 

 bind editor <delete> backspace
-

3.2. History

+

4.2. History

Mutt maintains a history for the built-in editor. The number of items -is controlled by the $history +is controlled by the $history variable and can be made persistent using an external file specified -using $history_file. +using $history_file. You may cycle through them at an editor prompt by using the <history-up> and/or -<history-down> commands. +<history-down> commands. But notice that Mutt +does not remember the currently entered text, it only cycles through +history and wraps around at the end or beginning.

Mutt maintains several distinct history lists, one for each of the following categories: -

  • muttrc commands

  • addresses and aliases

  • shell commands

  • filenames

  • patterns

  • everything else

-Mutt automatically filters out repeated items from the history. It +

  • .muttrc commands

  • addresses and aliases

  • shell commands

  • filenames

  • patterns

  • everything else

+Mutt automatically filters out consecutively repeated items from the history. It also mimics the behavior of some shells by ignoring items starting with a space. The latter feature can be useful in macros to not clobber the history's valuable entries with unwanted entries. -

4. Reading Mail - The Index and Pager

+

5. Reading Mail

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 of the +read in Mutt. The first is a list of messages in the mailbox, which is +called the “index” menu in Mutt. The second mode is the display of the message contents. This is called the “pager.”

The next few sections describe the functions provided in each of these modes. -

4.1. The Message Index

+

5.1. The Message Index

Common keys used to navigate through and manage messages in the index -are shown in Table 2.3, “Most common message index keys”. How messages are presented +are shown in Table 2.4, “Most common message index keys”. How messages are presented in the index menu can be customized using the -$index_format variable. -

Table 2.3. Most common message index keys

KeyDescription
cchange to a different mailbox
Esc cchange to a folder in read-only mode
Ccopy the current message to another mailbox
Esc Cdecode a message and copy it to a folder
Esc sdecode a message and save it to a folder
Ddelete messages matching a pattern
ddelete the current message
Fmark as important
lshow messages matching a pattern
Nmark message as new
ochange the current sort method
Oreverse sort the mailbox
qsave changes and exit
ssave-message
Ttag messages matching a pattern
ttoggle the tag on a message
Esc ttoggle tag on entire message thread
Uundelete messages matching a pattern
uundelete-message
vview-attachments
xabort changes and exit
<Return>display-message
<Tab>jump to the next new or unread message
@show the author's full e-mail address
$save changes to mailbox
/search
Esc /search-reverse
^Lclear and redraw the screen
^Tuntag messages matching a pattern

+$index_format variable. +

Table 2.4. Most common message index keys

KeyDescription
cchange to a different mailbox
Esc cchange to a folder in read-only mode
Ccopy the current message to another mailbox
Esc Cdecode a message and copy it to a folder
Esc sdecode a message and save it to a folder
Ddelete messages matching a pattern
ddelete the current message
Fmark as important
lshow messages matching a pattern
Nmark message as new
ochange the current sort method
Oreverse sort the mailbox
qsave changes and exit
ssave-message
Ttag messages matching a pattern
ttoggle the tag on a message
Esc ttoggle tag on entire message thread
Uundelete messages matching a pattern
uundelete-message
vview-attachments
xabort changes and exit
<Return>display-message
<Tab>jump to the next new or unread message
@show the author's full e-mail address
$save changes to mailbox
/search
Esc /search-reverse
^Lclear and redraw the screen
^Tuntag messages matching a pattern

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 “flags” in Table 2.4, “Message status flags” +Zero or more of the “flags” in Table 2.5, “Message status flags” may appear, some of which can be turned on or off using these functions: <set-flag> and <clear-flag> bound by default to “w” and “W” respectively.

-Furthermore, the flags in Table 2.5, “Message recipient flags” reflect +Furthermore, the flags in Table 2.6, “Message recipient flags” reflect who the message is addressed to. They can be customized with the -$to_chars variable. -

Table 2.4. Message status flags

FlagDescription
Dmessage is deleted (is marked for deletion)
dmessage has attachments marked for deletion
Kcontains a PGP public key
Nmessage is new
Omessage is old
Pmessage is PGP encrypted
rmessage has been replied to
Smessage is signed, and the signature is successfully verified
smessage is signed
!message is flagged
*message is tagged

Table 2.5. Message recipient flags

FlagDescription
+message is to you and you only
Tmessage is to you, but also to or cc'ed to others
Cmessage is cc'ed to you
Fmessage is from you
Lmessage is sent to a subscribed mailing list

4.2. The Pager

-By default, Mutt uses its builtin pager to display the contents of messages. -The pager is very similar to the Unix program less though not nearly as -featureful. -

Table 2.6. Most common pager keys

KeyDescription
<Return>go down one line
<Space>display the next page (or next message if at the end of a message)
-go back to the previous page
nsearch for next match
Sskip beyond quoted text
Ttoggle display of quoted text
?show keybindings
/regular expression search
Esc /backward regular expression search
\toggle highlighting of search matches
^jump to the top of the message

-In addition to key bindings in Table 2.6, “Most common pager keys”, +$to_chars variable. +

Table 2.5. Message status flags

FlagDescription
Dmessage is deleted (is marked for deletion)
dmessage has attachments marked for deletion
Kcontains a PGP public key
Nmessage is new
Omessage is old
Pmessage is PGP encrypted
rmessage has been replied to
Smessage is signed, and the signature is successfully verified
smessage is signed
!message is flagged
*message is tagged

Table 2.6. Message recipient flags

FlagDescription
+message is to you and you only
Tmessage is to you, but also to or cc'ed to others
Cmessage is cc'ed to you
Fmessage is from you
Lmessage is sent to a subscribed mailing list

5.2. The Pager

+By default, Mutt uses its builtin pager to display the contents of +messages (an external pager such as less(1) can be +configured, see $pager variable). +The pager is very similar to the Unix program less(1) +though not nearly as featureful. +

Table 2.7. Most common pager keys

KeyDescription
<Return>go down one line
<Space>display the next page (or next message if at the end of a message)
-go back to the previous page
nsearch for next match
Sskip beyond quoted text
Ttoggle display of quoted text
?show keybindings
/regular expression search
Esc /backward regular expression search
\toggle highlighting of search matches
^jump to the top of the message

+In addition to key bindings in Table 2.7, “Most common pager keys”, many of the functions from the index menu are also available in the pager, such as <delete-message> or <copy-message> (this is one advantage over using an external pager to view messages). @@ -227,11 +314,11 @@ the pager, such as <delete-message> or standard” nroff sequences for bold and underline. These sequences are a series of either the letter, -backspace (^H), the letter again for bold or the letter, backspace, +backspace (“^H”), the letter again for bold or the letter, backspace, “_” for denoting underline. Mutt will attempt to display these in bold and underline respectively if your terminal supports them. If -not, you can use the bold and underline color -objects to specify a color or mono attribute for them. +not, you can use the bold and underline color +objects to specify a color or mono attribute for them.

Additionally, the internal pager supports the ANSI escape sequences for character attributes. Mutt translates them into the correct color and @@ -240,8 +327,8 @@ character settings. The sequences Mutt supports are: \e[Ps;Ps;..Ps;m

where Ps can be one of the codes shown in -Table 2.7, “ANSI escape sequences”. -

Table 2.7. ANSI escape sequences

Escape codeDescription
0All attributes off
1Bold on
4Underline on
5Blink on
7Reverse video on
3<color>Foreground color is <color> (see Table 2.8, “Color sequences”)
4<color>Background color is <color> (see Table 2.8, “Color sequences”)

Table 2.8. Color sequences

Color codeColor
0Black
1Red
2Green
3Yellow
4Blue
5Magenta
6Cyan
7White

+Table 2.8, “ANSI escape sequences”. +

Table 2.8. ANSI escape sequences

Escape codeDescription
0All attributes off
1Bold on
4Underline on
5Blink on
7Reverse video on
3<color>Foreground color is <color> (see Table 2.9, “Color sequences”)
4<color>Background color is <color> (see Table 2.9, “Color sequences”)

Table 2.9. Color sequences

Color codeColor
0Black
1Red
2Green
3Yellow
4Blue
5Magenta
6Cyan
7White

Mutt uses these attributes for handling text/enriched messages, and they can also be used by an external autoview script for highlighting @@ -254,36 +341,48 @@ your xterm, then that color will be used instead of green. Note that the search commands in the pager take regular expressions, which are not quite the same as the more complex patterns used by the search -command in the index. This is because the pager only performs simple -text search, whereas the index provides boolean filtering on several -aspects of messages. -

4.3. Threaded Mode

-When the mailbox is sorted by threads, there are -a few additional functions available in the index and pager modes -as shown in Table 2.9, “Most common thread mode keys”. -

Table 2.9. Most common thread mode keys

KeyFunctionDescription
^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
^P<previous-thread>jump to the start of the previous thread
^R<read-thread>mark the current thread as read
Esc d<delete-subthread>delete all messages in the current subthread
Esc u<undelete-subthread>undelete all messages in the current subthread
Esc n<next-subthread>jump to the start of the next subthread
Esc p<previous-subthread>jump to the start of the previous subthread
Esc r<read-subthread>mark the current subthread as read
Esc t<tag-thread>toggle the tag on the current thread
Esc v<collapse-thread>toggle collapse for the current thread
Esc V<collapse-all>toggle collapse for all threads
P<parent-message>jump to parent message in thread

Note

+command in the index. This is because patterns are used to select messages by +criteria whereas the pager already displays a selected message. +

5.3. Threaded Mode

+So-called “threads” provide a hierarchy of messages where +replies are linked to their parent message(s). This organizational form +is extremely useful in mailing lists where different parts of the +discussion diverge. Mutt displays threads as a tree structure. +

+In Mutt, when a mailbox is sorted +by threads, there are a few additional functions +available in the index +and pager modes as shown in +Table 2.10, “Most common thread mode keys”. +

Table 2.10. Most common thread mode keys

KeyFunctionDescription
^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
^P<previous-thread>jump to the start of the previous thread
^R<read-thread>mark the current thread as read
Esc d<delete-subthread>delete all messages in the current subthread
Esc u<undelete-subthread>undelete all messages in the current subthread
Esc n<next-subthread>jump to the start of the next subthread
Esc p<previous-subthread>jump to the start of the previous subthread
Esc r<read-subthread>mark the current subthread as read
Esc t<tag-thread>toggle the tag on the current thread
Esc v<collapse-thread>toggle collapse for the current thread
Esc V<collapse-all>toggle collapse for all threads
P<parent-message>jump to parent message in thread

Collapsing a thread displays only the first message in the thread and hides the others. This is useful when threads contain so many messages that you can only see a handful of threads on -the screen. See %M in $index_format. -For example, you could use "%?M?(#%03M)&(%4l)?" in $index_format to optionally -display the number of hidden messages if the thread is collapsed. -

-See also: $strict_threads. -

4.4. Miscellaneous Functions

+the screen. See %M in $index_format. +For example, you could use “%?M?(#%03M)&(%4l)?” in $index_format to optionally +display the number of hidden messages if the thread is +collapsed. The %?<char>?<if-part>&<else-part>? +syntax is explained in detail in +format string conditionals. +

+Technically, every reply should contain a list of its parent messages in +the thread tree, but not all do. In these cases, Mutt groups them by +subject which can be controlled using the +$strict_threads variable. +

5.4. Miscellaneous Functions

In addition, the index and pager menus have these interesting functions:

<create-alias> (default: a)

Creates a new alias based upon the current message (or prompts for a -new one). Once editing is complete, an alias +new one). Once editing is complete, an alias command is added to the file specified by the $alias_file variable for future use

Note

Mutt does not read the $alias_file -upon startup so you must explicitly source the file. +upon startup so you must explicitly source the file.

<check-traditional-pgp> (default: Esc P)

@@ -322,7 +421,7 @@ to send.

This command is used to execute any command you would normally put in a configuration file. A common use is to check the settings of variables, or -in conjunction with macros to change settings on the +in conjunction with macros to change settings on the fly.

<extract-keys> (default: ^K) @@ -339,9 +438,9 @@ you misspelled the passphrase. <list-reply> (default: L)

Reply to the current or tagged message(s) by extracting any addresses which -match the regular expressions given by the lists or subscribe +match the regular expressions given by the lists or subscribe commands, but also honor any Mail-Followup-To header(s) if the -$honor_followup_to +$honor_followup_to configuration variable is set. Using this when replying to messages posted to mailing lists helps avoid duplicate copies being sent to the author of the message you are replying to. @@ -349,8 +448,8 @@ the message you are replying to. <pipe-message> (default: |)

Asks for an external Unix command and pipes the current or -tagged message(s) to it. The variables $pipe_decode, $pipe_split, -$pipe_sep and $wait_key control the exact behavior of this function. +tagged message(s) to it. The variables $pipe_decode, $pipe_split, +$pipe_sep and $wait_key control the exact behavior of this function.

<resend-message> (default: Esc e)

@@ -358,7 +457,7 @@ Mutt takes the current message as a template for a new message. This function is best described as "recall from arbitrary folders". It can conveniently be used to forward MIME messages while preserving the original mail structure. Note that the amount of headers -included here depends on the value of the $weed +included here depends on the value of the $weed variable.

This function is also available from the attachment menu. You can use this @@ -367,7 +466,7 @@ as a message/rfc822 body part.

<shell-escape> (default: !)

-Asks for an external Unix command and executes it. The $wait_key can be used to control +Asks for an external Unix command and executes it. The $wait_key can be used to control whether Mutt will wait for a key to be pressed when the command returns (presumably to let the user read the output of the command), based on the return status of the named command. If no command is given, an @@ -375,7 +474,7 @@ interactive shell is executed.

<toggle-quoted> (default: T)

-The pager uses the $quote_regexp variable to detect quoted text when +The pager uses the $quote_regexp variable to detect quoted text when displaying the body of the message. This function toggles the display of the quoted material in the message. It is particularly useful when being interested in just the response and there is a large amount of @@ -385,45 +484,59 @@ quoted text in the way.

This function will go to the next line of non-quoted text which comes after a line of quoted text in the internal pager. -

5. Sending Mail

5.1. Introduction

-The bindings shown in Table 2.10, “Most common mail sending keys” are available in the +

6. Sending Mail

6.1. Introduction

+The bindings shown in Table 2.11, “Most common mail sending keys” are available in the index and pager to start a new message. -

Table 2.10. Most common mail sending keys

KeyFunctionDescription
m<compose>compose a new message
r<reply>reply to sender
g<group-reply>reply to all recipients
L<list-reply>reply to mailing list address
f<forward>forward message
b<bounce>bounce (remail) message
Esc k<mail-key>mail a PGP public key to someone

+

Table 2.11. Most common mail sending keys

KeyFunctionDescription
m<compose>compose a new message
r<reply>reply to sender
g<group-reply>reply to all recipients
L<list-reply>reply to mailing list address
f<forward>forward message
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. These items are discussed -in greater detail in the next chapter “Forwarding +in greater detail in the next section “Forwarding and Bouncing Mail.”

Mutt will then enter the compose menu and prompt you for the -recipients to place on the “To:” header field. Next, it will ask +recipients to place on the “To:” header field when you hit m to start a new message. Next, it will ask you for the “Subject:” field for the message, providing a default if -you are replying to or forwarding a message. See also +you are replying to or forwarding a message. You again +have the chance to adjust recipients, subject, and security settings +right before actually sending the message. See also $askcc, $askbcc, -$autoedit, +$autoedit, $bounce, -$fast_reply, -and $include -for changing how Mutt asks these questions. -

-Mutt will then automatically start your $editor -on the message body. If the $edit_headers -variable is set, the headers will be at the top of the message in your editor. -Any messages you are replying to will be added in sort order to the message, +$fast_reply, +and $include +for changing how and if Mutt asks these questions. +

+When replying, Mutt fills these fields with proper values depending on +the reply type. The types of replying supported are: +

Simple reply

+Reply to the author directly. +

Group reply

+Reply to the author as well to all recipients except you; this consults +alternates. +

List reply

+Reply to all mailing list addresses found, either specified via +configuration or auto-detected. See Section 12, “Mailing Lists” for +details. +

+After getting recipients for new messages, forwards or replies, Mutt +will then automatically start your $editor on the message body. If the $edit_headers variable is +set, the headers will be at the top of the message in your editor. Any +messages you are replying to will be added in sort order to the message, with appropriate $attribution, -$indent_string and -$post_indent_string. -When forwarding a message, if the $mime_forward -variable is unset, a copy of the forwarded message will be included. If -you have specified a $signature, it -will be appended to the message. +$indent_string and +$post_indent_string. +When forwarding a message, if the $mime_forward variable is +unset, a copy of the forwarded message will be included. If you have +specified a $signature, it will +be appended to the message.

Once you have finished editing the body of your mail message, you are returned to the compose menu providing the functions -shown in Table 2.11, “Most common compose menu keys” to modify, send or postpone the +shown in Table 2.12, “Most common compose menu keys” to modify, send or postpone the message. -

Table 2.11. Most common compose menu keys

KeyFunctionDescription
a<attach-file>attach a file
A<attach-message>attach message(s) to the message
Esc k<attach-key>attach a PGP public key
d<edit-description>edit description on attachment
D<detach-file>detach a file
t<edit-to>edit the To field
Esc f<edit-from>edit the From field
r<edit-reply-to>edit the Reply-To field
c<edit-cc>edit the Cc field
b<edit-bcc>edit the Bcc field
y<send-message>send the message
s<edit-subject>edit the Subject
S<smime-menu>select S/MIME options
f<edit-fcc>specify an “Fcc” mailbox
p<pgp-menu>select PGP options
P<postpone-message>postpone this message until later
q<quit>quit (abort) sending the message
w<write-fcc>write the message to a folder
i<ispell>check spelling (if available on your system)
^F<forget-passphrase>wipe passphrase(s) from memory

+

Table 2.12. Most common compose menu keys

KeyFunctionDescription
a<attach-file>attach a file
A<attach-message>attach message(s) to the message
Esc k<attach-key>attach a PGP public key
d<edit-description>edit description on attachment
D<detach-file>detach a file
t<edit-to>edit the To field
Esc f<edit-from>edit the From field
r<edit-reply-to>edit the Reply-To field
c<edit-cc>edit the Cc field
b<edit-bcc>edit the Bcc field
y<send-message>send the message
s<edit-subject>edit the Subject
S<smime-menu>select S/MIME options
f<edit-fcc>specify an “Fcc” mailbox
p<pgp-menu>select PGP options
P<postpone-message>postpone this message until later
q<quit>quit (abort) sending the message
w<write-fcc>write the message to a folder
i<ispell>check spelling (if available on your system)
^F<forget-passphrase>wipe passphrase(s) from memory

The compose menu is also used to edit the attachments for a message which can be either files or other messages. The <attach-message> function to will prompt you for a folder to attach messages from. You can now tag messages in that folder and they @@ -432,27 +545,31 @@ will be attached to the message you are sending. Note that certain operations like composing a new mail, replying, forwarding, etc. are not permitted when you are in that folder. The %r in -$status_format will change to +$status_format will change to a “A” to indicate that you are in attach-message mode. -

5.2. Editing the message header

-When editing the header because of $edit_headers +

6.2. Editing the Message Header

+When editing the header because of $edit_headers being set, there are a several pseudo headers available which -will not be included in sent messages. -

5.2.1. Fcc: pseudo header

+will not be included in sent messages but trigger special Mutt behavior. +

6.2.1. Fcc: Pseudo Header

If you specify - +

Fcc: filename - +

as a header, Mutt will pick up filename just as if you had used the <edit-fcc> function in the compose menu. -

5.2.2. Attach: pseudo header

+It can later be changed from the compose menu. +

6.2.2. Attach: Pseudo Header

You can also attach files to your message by specifying - -Attach: filename [ description ] - +

+Attach: filename +[ description ] +

where filename is the file to attach and description is an -optional string to use as the description of the attached file. -

5.2.3. Pgp: pseudo header

+optional string to use as the description of the attached file. Spaces +in filenames have to be escaped using backslash (“\”). +The file can be removed as well as more added from the compose menu. +

6.2.3. Pgp: Pseudo Header

If you want to use PGP, you can specify

Pgp: [ E | S | S<id> ] @@ -460,15 +577,15 @@ If you want to use PGP, you can specify

“E” selects encryption, “S” selects signing and “S<id>” selects signing with the given key, setting -$pgp_sign_as -permanently. -

5.2.4. In-Reply-To: header

+$pgp_sign_as +permanently. The selection can later be changed in the compose menu. +

6.2.4. In-Reply-To: Header

When replying to messages, the In-Reply-To: header contains the -Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a +Message-Id of the message(s) you reply to. If you remove or modify its value, Mutt will not generate a References: field, which allows you to create a new message thread, for example to create a new message to a mailing list without having to enter the mailing list's address. -

5.3. Sending cryptographically signed/encrypted messages

-If you have told mutt to PGP or S/MIME encrypt a message, it will guide you +

6.3. Sending Cryptographically Signed/Encrypted Messages

+If you have told Mutt to PGP or S/MIME encrypt a message, it will guide you through a key selection process when you try to send the message. Mutt will not ask you any questions about keys which have a certified user ID matching one of the message recipients' mail @@ -477,22 +594,22 @@ several keys, weakly certified user ID fields, or where no matching keys can be found.

In these cases, you are dropped into a menu with a list of keys from -which you can select one. When you quit this menu, or mutt can't +which you can select one. When you quit this menu, or Mutt can't find any matching keys, you are prompted for a user ID. You can, as -usually, abort this prompt using ^G. When you do so, mutt will +usually, abort this prompt using ^G. When you do so, Mutt will return to the compose screen.

Once you have successfully finished the key selection, the message will be encrypted using the selected public keys when sent out.

-Most fields of the entries in the key selection menu (see also $pgp_entry_format) +Most fields of the entries in the key selection menu (see also $pgp_entry_format) have obvious meanings. But some explanations on the capabilities, flags, and validity fields are in order.

-The flags sequence (%f) will expand to one of the flags in -Table 2.12, “PGP key menu flags”. -

Table 2.12. PGP key menu flags

FlagDescription
RThe key has been revoked and can't be used.
XThe key is expired and can't be used.
dYou have marked the key as disabled.
cThere are unknown critical self-signature packets.

-The capabilities field (%c) expands to a two-character sequence +The flags sequence (“%f”) will expand to one of the flags in +Table 2.13, “PGP key menu flags”. +

Table 2.13. PGP key menu flags

FlagDescription
RThe key has been revoked and can't be used.
XThe key is expired and can't be used.
dYou have marked the key as disabled.
cThere are unknown critical self-signature packets.

+The capabilities field (“%c”) expands to a two-character sequence representing a key's capabilities. The first character gives the key's encryption capabilities: A minus sign (“-”) means that the key cannot be used for encryption. A dot (“.”) means that @@ -505,47 +622,12 @@ again, a “-” implies “not f that the key is marked as an encryption key in one of the user-ids, and “s” denotes a key which can be used for signing.

-Finally, the validity field (%t) indicates how well-certified a user-id +Finally, the validity field (“%t”) indicates how well-certified a user-id is. A question mark (“?”) indicates undefined validity, a minus character (“-”) marks an untrusted association, a space character means a partially trusted association, and a plus character (“+”) indicates complete validity. -

5.4. Sending anonymous messages via mixmaster

-You may also have compiled mutt to co-operate with Mixmaster, an -anonymous remailer. Mixmaster permits you to send your messages -anonymously using a chain of remailers. Mixmaster support in mutt is for -mixmaster version 2.04 (beta 45 appears to be the latest) and 2.03. -It does not support earlier versions or the later so-called version 3 betas, -of which the latest appears to be called 2.9b23. -

-To use it, you'll have to obey certain restrictions. Most -important, you cannot use the Cc and Bcc headers. To tell -Mutt to use mixmaster, you have to select a remailer chain, using -the mix function on the compose menu. -

-The chain selection screen is divided into two parts. In the -(larger) upper part, you get a list of remailers you may use. In -the lower part, you see the currently selected chain of remailers. -

-You can navigate in the chain using the <chain-prev> and -<chain-next> functions, which are by default bound to the left -and right arrows and to the h and l keys (think vi -keyboard bindings). To insert a remailer at the current chain -position, use the <insert> function. To append a remailer behind -the current chain position, use <select-entry> or <append>. -You can also delete entries from the chain, using the corresponding -function. Finally, to abandon your changes, leave the menu, or -<accept> them pressing (by default) the Return key. -

-Note that different remailers do have different capabilities, -indicated in the %c entry of the remailer menu lines (see -$mix_entry_format). Most important is -the “middleman” capability, indicated by a capital “M”: This -means that the remailer in question cannot be used as the final -element of a chain, but will only forward messages to other -mixmaster remailers. For details on the other capabilities, please -have a look at the mixmaster documentation. -

5.5. Sending format=flowed messages

5.5.1. Concept

+

6.4. Sending Format=Flowed Messages

6.4.1. Concept

format=flowed-style messages (or f=f for short) are text/plain messages that consist of paragraphs which a receiver's mail client may reformat to its own needs which mostly means to @@ -553,17 +635,17 @@ customize line lengths regardless of what the sender sent. Technically this is achieved by letting lines of a “flowable” paragraph end in spaces except for the last line.

-While for text-mode clients like mutt it's the best way to assume only a +While for text-mode clients like Mutt it's the best way to assume only a standard 80x25 character cell terminal, it may be desired to let the receiver decide completely how to view a message. -

5.5.2. Mutt support

+

6.4.2. Mutt Support

Mutt only supports setting the required format=flowed -MIME parameter on outgoing messages if the $text_flowed +MIME parameter on outgoing messages if the $text_flowed variable is set, specifically it does not add the trailing spaces.

After editing the initial message text and before entering -the compose menu, mutt properly space-stuffes the message. +the compose menu, Mutt properly space-stuffes the message. Space-stuffing is required by RfC3676 defining format=flowed and means to prepend a space to:

  • all lines starting with a space

  • lines starting with the word “From” @@ -577,8 +659,8 @@ quote or not. Furthermore, Mutt only applies space-stuffing

All leading spaces are to be removed by receiving clients to restore the original message prior to further processing. -

5.5.3. Editor considerations

-As mutt provides no additional features to compose f=f +

6.4.3. Editor Considerations

+As Mutt provides no additional features to compose f=f messages, it's completely up to the user and his editor to produce proper messages. Please consider your editor's documentation if you intend to send f=f messages. @@ -591,7 +673,7 @@ For example, vim provides the formatoptions setting to assist in creating f=f messages, see :help fo-table for details. -

6. Forwarding and Bouncing Mail

+

7. Forwarding and Bouncing Mail

Bouncing and forwarding let you send an existing message to recipients that you specify. Bouncing a message sends a verbatim copy of a message to alternative addresses as if they were the message's original @@ -604,22 +686,22 @@ respectively.

Forwarding can be done by including the original message in the new message's body (surrounded by indicating lines) or including it as a MIME -attachment, depending on the value of the $mime_forward variable. Decoding of attachments, -like in the pager, can be controlled by the $forward_decode and $mime_forward_decode variables, +attachment, depending on the value of the $mime_forward variable. Decoding of attachments, +like in the pager, can be controlled by the $forward_decode and $mime_forward_decode variables, respectively. The desired forwarding format may depend on the content, -therefore $mime_forward is a quadoption which, for +therefore $mime_forward is a quadoption which, for example, can be set to “ask-no”.

The inclusion of headers is controlled by the current setting of the -$weed variable, unless $mime_forward is set. +$weed variable, unless $mime_forward is set.

Editing the message to forward follows the same procedure as sending or replying to a message does. -

7. Postponing Mail

+

8. Postponing Mail

At times it is desirable to delay sending a message that you have already begun to compose. When the <postpone-message> function is used in the compose menu, the body of your message and attachments -are stored in the mailbox specified by the $postponed variable. This means that you can recall the +are stored in the mailbox specified by the $postponed variable. This means that you can recall the message even if you exit Mutt and then restart it at a later time.

Once a message is postponed, there are several ways to resume it. From the @@ -634,55 +716,55 @@ the message is only updated when you actually finish the message and send it. Also, you must be in the same folder with the message you replied to for the status of the message to be updated.

-See also the $postpone quad-option. -

Chapter 3. Configuration

Table of Contents

1. Location of initialization files
2. Syntax of Initialization Files
3. Address groups
4. Defining/Using aliases
5. Changing the default key bindings
6. Defining aliases for character sets
7. Setting variables based upon mailbox
8. Keyboard macros
9. Using color and mono video attributes
10. Message header display
11. Alternative addresses
12. Mailing lists
13. Using Multiple spool mailboxes
14. Monitoring incoming mail
15. User defined headers
16. Specify default save mailbox
17. Specify default Fcc: mailbox when composing
18. Specify default save filename and default Fcc: mailbox at once
19. Change settings based upon message recipients
20. Change settings before formatting a message
21. Choosing the cryptographic key of the recipient
22. Adding key sequences to the keyboard buffer
23. Executing functions
24. Message Scoring
25. Spam detection
26. Setting and Querying Variables
26.1. Commands
26.2. User-defined variables
27. Reading initialization commands from another file
28. Removing hooks
29. Format Strings
29.1. Basic usage
29.2. Filters

1. Location of initialization files

+See also the $postpone quad-option. +

Chapter 3. Configuration

Table of Contents

1. Location of Initialization Files
2. Syntax of Initialization Files
3. Address Groups
4. Defining/Using Aliases
5. Changing the Default Key Bindings
6. Defining Aliases for Character Sets
7. Setting Variables Based Upon Mailbox
8. Keyboard Macros
9. Using Color and Mono Video Attributes
10. Message Header Display
10.1. Selecting Headers
10.2. Ordering Displayed Headers
11. Alternative Addresses
12. Mailing Lists
13. Using Multiple Spool Mailboxes
14. Monitoring Incoming Mail
15. User-Defined Headers
16. Specify Default Save Mailbox
17. Specify Default Fcc: Mailbox When Composing
18. Specify Default Save Filename and Default Fcc: Mailbox at Once
19. Change Settings Based Upon Message Recipients
20. Change Settings Before Formatting a Message
21. Choosing the Cryptographic Key of the Recipient
22. Adding Key Sequences to the Keyboard Buffer
23. Executing Functions
24. Message Scoring
25. Spam Detection
26. Setting and Querying Variables
26.1. Variable Types
26.2. Commands
26.3. User-Defined Variables
27. Reading Initialization Commands From Another File
28. Removing Hooks
29. Format Strings
29.1. Basic usage
29.2. Conditionals
29.3. Filters
29.4. Padding

1. Location of Initialization Files

While the default configuration (or “preferences”) make Mutt usable right out of the box, it is often desirable to tailor Mutt to suit your own tastes. When Mutt is first invoked, it will attempt to read the “system” configuration file (defaults set by your local -system administrator), unless the “-n” command line option is specified. This file is typically +system administrator), unless the “-n” command line option is specified. This file is typically /usr/local/share/mutt/Muttrc or /etc/Muttrc. Mutt will next look for a file named .muttrc in your home directory. If this file does not exist and your home directory has -a subdirectory named .mutt, mutt try to load a file named +a subdirectory named .mutt, Mutt tries to load a file named .mutt/muttrc.

.muttrc is the file where you will usually place your commands to configure Mutt.

-In addition, mutt supports version specific configuration files that are +In addition, Mutt supports version specific configuration files that are parsed instead of the default files as explained above. For instance, if your system has a Muttrc-0.88 file in the system configuration -directory, and you are running version 0.88 of mutt, this file will be +directory, and you are running version 0.88 of Mutt, this file will be sourced instead of the Muttrc file. The same is true of the user configuration file, if you have a file .muttrc-0.88.6 in your home -directory, when you run mutt version 0.88.6, it will source this file +directory, when you run Mutt version 0.88.6, it will source this file instead of the default .muttrc file. The version number is the -same which is visible using the “-v” command line switch or using the show-version key (default: +same which is visible using the “-v” command line switch or using the show-version key (default: V) from the index menu.

2. Syntax of Initialization Files

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 -(;). +(“;”).

Example 3.1. Multiple configuration commands per line

 set realname='Mutt user' ; ignore x-

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, +to the end of the line is ignored.

Example 3.2. Commenting configuration files

 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 +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 shell programs, namely that a single quote is used to specify a literal string (one that is not interpreted for shell variables or quoting with a backslash [see next paragraph]), while double quotes indicate a string for which should be evaluated. For example, backticks are evaluated inside of double -quotes, but not for single quotes. +quotes, but not for single quotes.

-\ quotes the next character, just as in shells such as bash and zsh. +“\” quotes the next character, just as in shells such as bash and zsh. For example, if want to put quotes “"” inside of a string, you can use “\” to force the next character to be a literal instead of interpreted character. @@ -693,30 +775,34 @@ set realname="Michael \"MuttDude\" Elkins" “\n” and “\r” have their usual C meanings of linefeed and carriage-return, respectively.

-A \ at the end of a line can be used to split commands over -multiple lines, provided that the split points don't appear in the -middle of command names. -

+A “\” at the end of a line can be used to split commands over +multiple lines as it “escapes” the line end, provided that the split points don't appear in the +middle of command names. Lines are first concatenated before +interpretation so that a multi-line can be commented by commenting out +the first line only. +

Example 3.4. Splitting long configuration commands over several lines

+set status_format="some very \
+long value split \
+over several lines"
+

It is also possible to substitute the output of a Unix command in an initialization file. This is accomplished by enclosing the command in -backticks (``). For example, -

Example 3.4. Using external command's output in configuration files

-my_hdr X-Operating-System: `uname -a`
-

-The output of the Unix command “uname -a” will be substituted before the +backticks (``). In Example 3.5, “Using external command's output in configuration files”, the output of the +Unix command “uname -a” will be substituted before the line is parsed. -

Note

Since initialization files are line oriented, only the first line of output from the Unix command will be substituted. -

-Both environment variables and mutt variables can be accessed by +

Example 3.5. Using external command's output in configuration files

+my_hdr X-Operating-System: `uname -a`
+

+Both environment variables and Mutt variables can be accessed by prepending “$” to the name of the variable. For example, -

Example 3.5. Using environment variables in configuration files

+
Example 3.6. Using environment variables in configuration files
 set record=+sent_on_$HOSTNAME
 


-will cause mutt to save outgoing messages to a folder named
-“sent_on_kremvax” if the environment variable HOSTNAME is set to
-“kremvax.” (See $record for
+will cause Mutt to save outgoing messages to a folder named
+“sent_on_kremvax” if the environment variable $HOSTNAME is set to
+“kremvax.” (See $record for
 details.)
 

 Mutt expands the variable when it is assigned, not when it is used. If
@@ -724,7 +810,7 @@ the value of a variable on the right-hand side of an assignment
 changes after the assignment, the variable on the left-hand side will
 not be affected.
 

-The commands understood by mutt are explained in the next paragraphs.
+The commands understood by Mutt are explained in the next paragraphs.
 For a complete list, see the command reference.
 

 All configuration files are expected to be in the current locale as
@@ -733,19 +819,21 @@ which doesn't have a default value since it's determined by Mutt at startup.
 If a configuration file is not encoded in the same character set the
 $config_charset
 variable should be used: all lines starting with the next are recoded
-from $config_charset to $charset.
+from $config_charset
+to $charset.
 

 This mechanism should be avoided if possible as it has the
 following implications:
 
  • These variables should be set early in a configuration
-file with $charset preceding $config_charset so Mutt
-know what character set to convert to.
  • If $config_charset is set, it should be set
+file with $charset preceding
+$config_charset so Mutt
+knows what character set to convert to.
  • If $config_charset is set, it should be set
 in each configuration file because the value is global and not
 per configuration file.
  • Because Mutt first recodes a line before it attempts to parse it,
 a conversion introducing question marks or other characters as
 part of errors (unconvertable characters, transliteration) may introduce syntax
 errors or silently change the meaning of certain tokens (e.g. inserting
-question marks into regular expressions).

3. Address groups

Usage:

group [ +question marks into regular expressions).

3. Address Groups

Usage:

group [ -group name ...] { @@ -754,7 +842,7 @@ question marks into regular expressions).

-addr expr -... }

ungroup [ +... }
ungroup [ -group name ...] { @@ -766,30 +854,30 @@ question marks into regular expressions).

-addr expr ... }

-group is used to directly add either addresses or +group is used to directly add either addresses or regular expressions to the specified group or groups. The different -categories of arguments to the group command can be +categories of arguments to the group command can be in any order. The flags -rx and -addr specify what the following strings (that cannot begin with a hyphen) should be interpreted as: either a regular expression or an email address, respectively.

These address groups can also be created implicitly by the -alias, lists, -subscribe and -alternates commands by specifying the +alias, lists, +subscribe and +alternates commands by specifying the optional -group option.

Once defined, these address groups can be used in patterns to search for and limit the display to messages matching a group.

-ungroup is used to remove addresses or regular +ungroup is used to remove addresses or regular expressions from the specified group or groups. The syntax is similar to -the group command, however the special character +the group command, however the special character * can be used to empty a group of all of its contents. -

4. Defining/Using aliases

Usage:

alias [ +

4. Defining/Using Aliases

Usage:

alias [ -group name ...] @@ -798,63 +886,61 @@ contents. address [ address -...]

+...]
unalias [ +-group +name +...] { +* + | +key +... }

It's usually very cumbersome to remember or type out the address of someone you are communicating with. Mutt allows you to create “aliases” which map a short string to a full address.

Note

If you want to create an alias for more than -one address, you must separate the addresses with a comma (“,”). +one address, you must separate the addresses with a comma (“,”).

The optional -group argument to -alias causes the aliased address(es) to be added to +alias causes the aliased address(es) to be added to the named group.

To remove an alias or aliases (“*” means all aliases): -

unalias [ --group -name -...] { -* - | -key -... }

+
 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.  Consequently, you can have multiple alias files, or
-you can have all aliases defined in your muttrc.
+in a special file.  The alias command can appear anywhere in
+a configuration file, as long as this file is sourced.  Consequently, you can have multiple alias files, or
+you can have all aliases defined in your .muttrc.
 

 On the other hand, the <create-alias>
 function can use only one file, the one pointed to by the $alias_file variable (which is
 ˜/.muttrc by default). This file is not special either,
 in the sense that Mutt will happily append aliases to any file, but in
-order for the new aliases to take effect you need to explicitly source this file too.
-

-For example:
-
Example 3.6. Configuring external alias files
+order for the new aliases to take effect you need to explicitly source this file too.
+
Example 3.7. Configuring external alias files
 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
+To use aliases, you merely use the alias at any place in Mutt where Mutt
 prompts for addresses, such as the To: or Cc: prompt.  You can
 also enter aliases in your editor at the appropriate headers if you have the
-$edit_headers variable set.
+$edit_headers variable set.
 

 In addition, at the various address prompts, you can use the tab character
 to expand a partial alias to the full alias.  If there are multiple matches,
-mutt will bring up a menu with the matching aliases.  In order to be
-presented with the full list of aliases, you must hit tab with out a partial
+Mutt will bring up a menu with the matching aliases.  In order to be
+presented with the full list of aliases, you must hit tab without a partial
 alias, such as at the beginning of the prompt or after a comma denoting
 multiple addresses.
 

 In the alias menu, you can select as many aliases as you want with the
 select-entry key (default: <Return>), and use the
 exit key (default: q) to return to the address prompt.
-
5. Changing the default key bindings
Usage:
bind   
+
5. Changing the Default Key Bindings
Usage:
bind   
 map
    
 key
@@ -872,10 +958,10 @@ This is not a real menu, but is used as a fallback for all of the other
 menus except for the pager and editor modes.  If a key is not defined in
 another menu, Mutt will look for a binding to use in this menu.  This allows
 you to bind a key to a certain function in multiple menus instead of having
-multiple bind statements to accomplish the same task.
+multiple bind statements to accomplish the same task.
 
alias

 The alias menu is the list of your personal aliases as defined in your
-muttrc.  It is the mapping from a short alias name to the full email
+.muttrc.  It is the mapping from a short alias name to the full email
 address(es) of the recipient(s).
 
attach

 The attachment menu is used to access the attachments on received messages.
@@ -902,7 +988,7 @@ The postpone menu is similar to the index menu, except is used when
 recalling a message the user was composing, but saved until later.
 
query

 The query menu is the browser for results returned by
-$query_command.
+$query_command.
 
mix

 The mixmaster screen is used to select remailer options for outgoing
 messages (if Mutt is compiled with Mixmaster support).
@@ -923,56 +1009,59 @@ space (“ ”) or semi-colon (“function specifies which action to take when key is pressed.
 For a complete list of functions, see the reference.  The special function <noop> unbinds the specified key
 sequence.
-
6. Defining aliases for character sets 
Usage:
charset-hook   
+
6. Defining Aliases for Character Sets
Usage:
charset-hook   
 alias
    
 charset
- 
iconv-hook   
+ 
iconv-hook   
 charset
    
 local-charset
  

-The charset-hook command defines an alias for a character set.
+The charset-hook command defines an alias for a character set.
 This is useful to properly display messages which are tagged with a
-character set name not known to mutt.
+character set name not known to Mutt.
 

-The iconv-hook command defines a system-specific name for a
+The iconv-hook command defines a system-specific name for a
 character set.  This is helpful when your systems character
 conversion library insists on using strange, system-specific names
 for character sets.
-
7. Setting variables based upon mailbox
Usage:
folder-hook   
+
7. Setting Variables Based Upon Mailbox
Usage:
folder-hook   
 [!]regexp
    
 command
  

 It is often desirable to change settings based on which mailbox you are
-reading.  The folder-hook command provides a method by which you can execute
+reading.  The folder-hook command provides a method by which you can execute
 any configuration command.  regexp is a regular expression specifying
 in which mailboxes to execute command before loading.  If a mailbox
-matches multiple folder-hook's, they are executed in the order given in the
-muttrc.
+matches multiple folder-hooks, they are executed in the order given in the
+.muttrc.
 
Note

-If you use the “!” shortcut for $spoolfile at the beginning of the pattern, you must place it
+If you use the “!” shortcut for $spoolfile at the beginning of the pattern, you must place it
 inside of double or single quotes in order to distinguish it from the
 logical not operator for the expression.
 
Note

 Settings are not restored when you leave the mailbox.
 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
-

+
+
+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 default command, use the
-pattern “.” before other folder-hooks adjusting a value on a per-folder basis
-because folder-hooks are evaluated in the order given in the configuration file.
-The following example will set the sort variable
+pattern “.” before other folder-hooks adjusting a value on a per-folder basis
+because folder-hooks are evaluated in the order given in the
+configuration file.
+

+The following example will set the sort variable
 to date-sent for all folders but to threads
 for all folders containing “mutt” in their name.
-
Example 3.7. Setting sort method based on mailbox name
-folder-hook . set sort=date-sent
-folder-hook mutt set sort=threads
-

8. Keyboard macros
Usage:
macro   
+
Example 3.8. Setting sort method based on mailbox name
+folder-hook . "set sort=date-sent"
+folder-hook mutt "set sort=threads"
+

8. Keyboard Macros
Usage:
macro   
 menu
    
 key
@@ -993,13 +1082,13 @@ commas. Whitespace may not be used in between the menu arguments and the
 commas separating them.
 

 key and sequence are expanded by the same rules as the
-key bindings with some additions.  The
+key bindings with some additions.  The
 first is that control characters in sequence can also be specified
 as ^x.  In order to get a caret (“^”) you need to use
 ^^.  Secondly, to specify a certain key such as up
 or to invoke a function directly, you can use the format
 <key name> and <function name>.  For a listing of key
-names see the section on key bindings.  Functions
+names see the section on key bindings.  Functions
 are listed in the reference.
 

 The advantage with using function names directly is that the macros will
@@ -1009,17 +1098,17 @@ and portable, and also facilitates defining of macros in files used by more
 than one user (e.g., the system Muttrc).
 

 Optionally you can specify a descriptive text after sequence,
-which is shown in the help screens.
+which is shown in the help screens if they contain a description.
 
Note

 Macro definitions (if any) listed in the help screen(s), are
 silently truncated at the screen width, and are not wrapped.
-
9. Using color and mono video attributes
Usage:
color   
+
9. Using Color and Mono Video Attributes
Usage:
color   
 object
    
 foreground
    
 background
- 
color  { 
+ 
color  { 
 header
   |   
 body
@@ -1029,7 +1118,7 @@ silently truncated at the screen width, and are not wrapped.
 background
    
 regexp
- 
color   
+ 
color   
 index
    
 foreground
@@ -1037,16 +1126,20 @@ silently truncated at the screen width, and are not wrapped.
 background
    
 pattern
- 
uncolor   
+ 
uncolor  { 
 index
-  { 
+  |   
+header
+  |   
+body
+ } { 
 *
   |   
 pattern
 ... }

 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 information), you
-must specify both a foreground color and a background color (it is not
+must specify both a foreground color and a background color (it is not
 possible to only specify one or the other).
 

 header and body match regexp
@@ -1054,7 +1147,7 @@ in the header/body of a message, index ma
 (see Section 2, “Patterns: Searching, Limiting and Tagging”) in the message index.
 

 object can be one of:
-
  • attachment
  • bold (hiliting bold patterns in the body of messages)
  • error (error messages printed by Mutt)
  • hdrdefault (default color of the message header in the pager)
  • indicator (arrow or bar used to indicate the current item in a menu)
  • markers (the “+” markers at the beginning of wrapped lines in the pager)
  • message (informational messages)
  • normal
  • quoted (text matching $quote_regexp in the body of a message)
  • quoted1, quoted2, ..., quotedN (higher levels of quoting)
  • search (hiliting of words in the pager)
  • signature
  • status (mode lines used to display info about the mailbox or message)
  • tilde (the “˜” used to pad blank lines in the pager)
  • tree (thread tree drawn in the message index and attachment menu)
  • underline (hiliting underlined patterns in the body of messages)

+
  • attachment
  • bold (hiliting bold patterns in the body of messages)
  • error (error messages printed by Mutt)
  • hdrdefault (default color of the message header in the pager)
  • indicator (arrow or bar used to indicate the current item in a menu)
  • markers (the “+” markers at the beginning of wrapped lines in the pager)
  • message (informational messages)
  • normal
  • quoted (text matching $quote_regexp in the body of a message)
  • quoted1, quoted2, ..., quotedN (higher levels of quoting)
  • search (hiliting of words in the pager)
  • signature
  • status (mode lines used to display info about the mailbox or message)
  • tilde (the “˜” used to pad blank lines in the pager)
  • tree (thread tree drawn in the message index and attachment menu)
  • underline (hiliting underlined patterns in the body of messages)

 foreground and background can be one of the following:
 
  • white
  • black
  • green
  • magenta
  • blue
  • cyan
  • yellow
  • red
  • default
  • colorx

 foreground can optionally be prefixed with the keyword bright to make
@@ -1063,7 +1156,7 @@ the foreground color boldfaced (e.g., brightred).
 If your terminal supports it, the special keyword default can be
 used as a transparent color.  The value brightdefault is also valid.
 If Mutt is linked against the S-Lang library, you also need to set
-the COLORFGBG environment variable to the default colors of your
+the $COLORFGBG environment variable to the default colors of your
 terminal for this to work; for example (for Bourne-like shells):
 
 set COLORFGBG="green;black"
@@ -1073,24 +1166,24 @@ The S-Lang library requires you to use th
 and brown keywords instead of white and yellow when
 setting this variable.
 
Note

-The uncolor command can be applied to the index object only.  It
-removes entries from the list. You must 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.
+The uncolor command can be applied to the index, header and body objects only.  It
+removes entries from the list. You must 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 list of all entries.
 

 Mutt also recognizes the keywords color0, color1, …,
-colorN-1 (N being the number of colors supported
+colorN-1 (N being the number of colors supported
 by your terminal).  This is useful when you remap the colors for your
 display (for example by changing the color associated with color2
 for your xterm), since color names may then lose their normal meaning.
-

+

 If your terminal does not support color, it is still possible change the video
-attributes through the use of the “mono” command:
-
Usage:
mono   
+attributes through the use of the “mono” command. Usage:
+
mono   
 object
    
 attribute
- 
mono  { 
+ 
mono  { 
 header
   |   
 body
@@ -1098,26 +1191,30 @@ attributes through the use of the “mono” command:
 attribute
    
 regexp
- 
mono   
+ 
mono   
 index
    
 attribute
    
 pattern
- 
unmono   
+ 
unmono  { 
 index
-  { 
+  |   
+header
+  |   
+body
+ } { 
 *
   |   
 pattern
 ... }

-For object, see the color command. attribute
+For object, see the color command. attribute
 can be one of the following:
-
  • none
  • bold
  • underline
  • reverse
  • standout
10. Message header display
Usage:
ignore   
+
  • none
  • bold
  • underline
  • reverse
  • standout
10. Message Header Display
10.1. Selecting Headers
Usage:
ignore   
 pattern
   [
 pattern
-...]
unignore  { 
+...]
unignore  { 
 *
   |   
 pattern
@@ -1135,38 +1232,36 @@ The “unignore” command will make Mutt display hea
 For example, if you do “ignore x-” it is possible to “unignore x-mailer”.
 

 “unignore *” will remove all tokens from the ignore list.
-

-For example:
-
Example 3.8. Header weeding
+
Example 3.9. Header weeding
 # 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:
-

Usage:
hdr_order   
+

10.2. Ordering Displayed Headers
Usage:
hdr_order   
 header
   [
 header
-...]
unhdr_order  { 
+...]
unhdr_order  { 
 *
   |   
 header
 ... }

-With the hdr_order command you can specify an order in
-which mutt will attempt to present these headers to you when viewing messages.
+With the hdr_order command you can specify an order in
+which Mutt will attempt to present these headers to you when viewing messages.
 

-“unhdr_order *” will clear all previous headers from the order list,
+“unhdr_order *” will clear all previous headers from the order list,
 thus removing the header order effects set by the system-wide startup file.
-
Example 3.9. Configuring header display order
+
Example 3.10. Configuring header display order
 hdr_order From Date: From: To: Cc: Subject:
-

11. Alternative addresses
Usage:
alternates  [
+

11. Alternative Addresses

Usage:

alternates [ -group name ...] regexp [ regexp -...]

unalternates [ +...]
unalternates [ -group name ...] { @@ -1174,17 +1269,17 @@ hdr_order From Date: From: To: Cc: Subject: | regexp ... }

-With various functions, mutt will treat messages differently, +With various functions, Mutt will treat messages differently, depending on whether you sent them or whether you received them from someone else. For instance, when replying to a message that you -sent to a different party, mutt will automatically suggest to send -the response to the original message's recipients -- responding to -yourself won't make much sense in many cases. (See $reply_to.) +sent to a different party, Mutt will automatically suggest to send +the response to the original message's recipients — responding to +yourself won't make much sense in many cases. (See $reply_to.)

Many users receive e-mail under a number of different addresses. To -fully use mutt's features here, the program must be able to +fully use Mutt's features here, the program must be able to recognize what e-mail addresses you receive mail under. That's the -purpose of the alternates command: It takes a list of regular +purpose of the alternates command: It takes a list of regular expressions, each of which can identify an address under which you receive e-mail.

@@ -1194,7 +1289,7 @@ as possible to avoid mismatches. For example, if you specify: 

 alternates user@example

-mutt will consider “some-user@example” as +Mutt will consider “some-user@example” as being your address, too which may not be desired. As a solution, in such cases addresses should be specified as: 

@@ -1203,40 +1298,40 @@ alternates '^user@example$'
 The -group flag causes all of the subsequent regular expressions
 to be added to the named group.
 

-The unalternates command can be used to write exceptions to
-alternates patterns. If an address matches something in an
-alternates command, but you nonetheless do not think it is
-from you, you can list a more precise pattern under an unalternates
+The unalternates command can be used to write exceptions to
+alternates patterns. If an address matches something in an
+alternates command, but you nonetheless do not think it is
+from you, you can list a more precise pattern under an unalternates
 command.
 

-To remove a regular expression from the alternates list, use the
-unalternates command with exactly the same regexp.
-Likewise, if the regexp for an alternates command matches
-an entry on the unalternates list, that unalternates
-entry will be removed. If the regexp for unalternates
-is “*”, all entries on alternates will be removed.
-

12. Mailing lists

Usage:

lists [ +To remove a regular expression from the alternates list, use the +unalternates command with exactly the same regexp. +Likewise, if the regexp for an alternates command matches +an entry on the unalternates list, that unalternates +entry will be removed. If the regexp for unalternates +is “*”, all entries on alternates will be removed. +

12. Mailing Lists

Usage:

lists [ -group name ...] regexp [ regexp -...]

unlists [ +...]
unlists [ -group name ...] { * | regexp -... }

subscribe [ +... }
subscribe [ -group name ...] regexp [ regexp -...]

unsubscribe [ +...]
unsubscribe [ -group name ...] { @@ -1246,8 +1341,15 @@ is “*”, all entries

Mutt has a few nice features for handling mailing lists. In order to take advantage of them, you must specify which addresses belong to mailing lists, and which mailing -lists you are subscribed to. Once you have done this, the <list-reply> function will work for all known lists. -Additionally, when you send a message to a subscribed list, mutt will +lists you are subscribed to. Mutt also has limited support for +auto-detecting mailing lists: it supports parsing +mailto: links in the common +List-Post: header which has the same effect as +specifying the list address via the lists command +(except the group feature). Once you have done this, the +<list-reply> +function will work for all known lists. +Additionally, when you send a message to a subscribed list, Mutt will add a Mail-Followup-To header to tell other users' mail user agents not to send copies of replies to your personal address.

Note

@@ -1255,30 +1357,32 @@ The Mail-Followup-To header is a non-standard extension which is not supported by all mail user agents. Adding it is not bullet-proof against receiving personal CCs of list messages. Also note that the generation of the Mail-Followup-To header is controlled by the -$followup_to -configuration variable. +$followup_to +configuration variable since it's common practice on some mailing lists +to send Cc upons replies (which is more a group- than a list-reply).

More precisely, Mutt maintains lists of patterns for the addresses of known and subscribed mailing lists. Every subscribed mailing -list is known. To mark a mailing list as known, use the “lists” -command. To mark it as subscribed, use “subscribe”. +list is known. To mark a mailing list as known, use the list +command. To mark it as subscribed, use subscribe.

-You can use regular expressions with both commands. To mark all -messages sent to a specific bug report's address on mutt's bug +You can use regular expressions with both commands. To mark all +messages sent to a specific bug report's address on Debian's bug tracking system as list mail, for instance, you could say -“subscribe [0-9]*@bugs.guug.de”. Often, it's sufficient to just -give a portion of the list's e-mail address. +

+subscribe [0-9]*.*@bugs.debian.org

+as it's often, it's sufficient to just give a portion of the list's e-mail address.

Specify as much of the address as you need to to remove ambiguity. For example, if you've subscribed to the Mutt mailing list, you will receive mail -addressed to mutt-users@mutt.org. So, to tell Mutt -that this is a mailing list, you could add “lists mutt-users@” to your -initialization file. To tell mutt that you are subscribed to it, -add “subscribe mutt-users” to your initialization file instead. +addressed to mutt-users@mutt.org. So, to tell Mutt +that this is a mailing list, you could add lists mutt-users@ to your +initialization file. To tell Mutt that you are subscribed to it, +add subscribe mutt-users to your initialization file instead. If you also happen to get mail from someone whose address is -mutt-users@example.com, you could use -“lists ^mutt-users@mutt\\.org$” -or “subscribe ^mutt-users@mutt\\.org$” to +mutt-users@example.com, you could use +lists ^mutt-users@mutt\\.org$ +or subscribe ^mutt-users@mutt\\.org$ to match only mail from the actual list.

The -group flag adds all of the subsequent regular expressions @@ -1289,8 +1393,8 @@ known and subscribed mailing-lists. Use “unlists * tokens.

To remove a mailing list from the list of subscribed mailing lists, -but keep it on the list of known mailing lists, use “unsubscribe”. -

13. Using Multiple spool mailboxes

Usage:

mbox-hook +but keep it on the list of known mailing lists, use unsubscribe. +

13. Using Multiple Spool Mailboxes

Usage:

mbox-hook [!]pattern mailbox @@ -1304,11 +1408,11 @@ read. Unlike some of the other hook commands, only the first matching pattern is used (it is not possible to save read mail in more than a single mailbox). -

14. Monitoring incoming mail

Usage:

mailboxes +

14. Monitoring Incoming Mail

Usage:

mailboxes mailbox [ mailbox -...]

unmailboxes { +...]
unmailboxes { * | mailbox @@ -1319,7 +1423,7 @@ which will be checked for new messages periodically. folder can either be a local file or directory (Mbox/Mmdf or Maildir/Mh). If Mutt was built with POP and/or IMAP support, folder can also be a POP/IMAP folder -URL. The URL syntax is described in Section 1.2, “URL syntax”, +URL. The URL syntax is described in Section 1.2, “URL Syntax”, POP and IMAP are described in Section 3, “POP3 Support” and Section 4, “IMAP Support” respectively.

@@ -1332,13 +1436,13 @@ The “unmailboxes” command is used to remove a tok of folders which receive mail. Use “unmailboxes *” to remove all tokens.

Note

-The folders in the mailboxes command are resolved when +The folders 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 affects these characters (like $folder and $spoolfile) -should be set before the mailboxes command. If +definition that affects these characters (like $folder and $spoolfile) +should be set before the mailboxes command. If none of these shorcuts are used, a local path should be absolute as -otherwise mutt tries to find it relative to the directory -from where mutt was started which may not always be desired. +otherwise Mutt tries to find it relative to the directory +from where Mutt was started which may not always be desired.

For Mbox and Mmdf folders, new mail is detected by comparing access and/or modification times of files: Mutt assumes a folder has new mail if it wasn't @@ -1351,42 +1455,42 @@ access time update support.

In cases where new mail detection for Mbox or Mmdf folders appears to be unreliable, the -$check_mbox_size +$check_mbox_size option can be used to make Mutt track and consult file sizes for new -mail detection instead. -

15. User defined headers

Usage:

my_hdr +mail detection instead which won't work for size-neutral changes. +

15. User-Defined Headers

Usage:

my_hdr string -

unmy_hdr { +
unmy_hdr { * | field ... }

-The my_hdr command allows you to create your own header -fields which will be added to every message you send. +The my_hdr command allows you to create your own header +fields which will be added to every message you send and appear in the +editor if $edit_headers is set.

For example, if you would like to add an “Organization:” header field to -all of your outgoing messages, you can put the command -

Example 3.10. Defining custom headers

+all of your outgoing messages, you can put the command something like
+shown in Example 3.11, “Defining custom headers” in your .muttrc.
+
Example 3.11. Defining custom headers
 my_hdr Organization: A Really Big Company, Anytown, USA
-


-in your .muttrc.
-
Note

+

Note

Space characters are not allowed between the keyword and the colon (“:”). The standard for electronic mail (RFC2822) says that space is illegal there, so Mutt enforces the rule.

If you would like to add a header field to a single message, you should -either set the $edit_headers variable, +either set the $edit_headers variable, or use the <edit-headers> function (default: “E”) in the compose 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 +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
-

16. Specify default save mailbox

Usage:

save-hook +

16. Specify Default Save Mailbox

Usage:

save-hook [!]pattern mailbox @@ -1397,11 +1501,9 @@ matches pattern, see

To provide more flexibility and good defaults, Mutt applies the -expandos of $index_format to +expandos of $index_format to mailbox after it was expanded. -

-Examples: -

Example 3.11. Using %-expandos in save-hook

+
Example 3.12. Using %-expandos in save-hook
 # default: save all to ~/Mail/<author name>
 save-hook . ~/Mail/%F
 
@@ -1411,46 +1513,44 @@ save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
 # save from aol.com to $folder/spam
 save-hook aol\\.com$ +spam
 


-Also see the fcc-save-hook command.
-

17. Specify default Fcc: mailbox when composing

Usage:

fcc-hook +Also see the fcc-save-hook command. +

17. Specify Default Fcc: Mailbox When Composing

Usage:

fcc-hook [!]pattern mailbox

This command is used to save outgoing mail in a mailbox other than -$record. Mutt searches the initial list of +$record. Mutt searches the initial list of message recipients for the first matching regexp and uses mailbox as the default Fcc: mailbox. If no match is found the message will be saved -to $record mailbox. +to $record mailbox.

To provide more flexibility and good defaults, Mutt applies the -expandos of $index_format to +expandos of $index_format to mailbox after it was expanded.

See Message Matching in Hooks for information on the exact format of pattern. -

-Example: fcc-hook [@.]aol\\.com$ +spammers -

-The above will save a copy of all messages going to the aol.com domain to -the `+spammers' mailbox by default. Also see the fcc-save-hook command. -

18. Specify default save filename and default Fcc: mailbox at once

Usage:

fcc-save-hook +

fcc-hook [@.]aol\\.com$ +spammers

+...will save a copy of all messages going to the aol.com domain to +the `+spammers' mailbox by default. Also see the fcc-save-hook command. +

18. Specify Default Save Filename and Default Fcc: Mailbox at Once

Usage:

fcc-save-hook [!]pattern mailbox

-This command is a shortcut, equivalent to doing both a fcc-hook -and a save-hook with its arguments, +This command is a shortcut, equivalent to doing both a fcc-hook +and a save-hook with its arguments, including %-expansion on mailbox according -to $index_format. -

19. Change settings based upon message recipients

Usage:

reply-hook +to $index_format. +

19. Change Settings Based Upon Message Recipients

Usage:

reply-hook [!]pattern command -

send-hook +
send-hook [!]pattern command -

send2-hook +
send2-hook [!]pattern command @@ -1460,38 +1560,40 @@ upon recipients of the message. pattern the message, see Message Matching in Hooks for details. command is executed when pattern matches.

-reply-hook is matched against the message you are replying to, -instead of the message you are sending. send-hook is +reply-hook is matched against the message you are replying to, +instead of the message you are sending. send-hook is matched against all messages, both new and replies.

Note

-reply-hooks are matched before the send-hook, regardless +reply-hooks are matched before the send-hook, regardless of the order specified in the user's configuration file.

-send2-hook is matched every time a message is changed, either +send2-hook is matched every time a message is changed, either by editing it, or by using the compose menu to change its recipients -or subject. send2-hook is executed after send-hook, and -can, e.g., be used to set parameters such as the $sendmail variable depending on the message's sender +or subject. send2-hook is executed after send-hook, and +can, e.g., be used to set parameters such as the $sendmail variable depending on the message's sender address.

-For each type of send-hook or reply-hook, when multiple matches -occur, commands are executed in the order they are specified in the muttrc +For each type of send-hook or reply-hook, when multiple matches +occur, commands are executed in the order they are specified in the .muttrc (for that type of hook).

-Example: send-hook mutt "set mime_forward 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 +$attribution, $signature and $locale variables in order to change the language of the attributions and signatures based upon the recipients.

Note

-send-hook's are only executed once after getting the initial -list of recipients. Adding a recipient after replying or editing the -message will not cause any send-hook to be executed. Also note that -my_hdr commands which modify recipient headers, or the message's -subject, don't have any effect on the current message when executed -from a send-hook. -

20. Change settings before formatting a message

Usage:

message-hook +send-hook's are only executed once after getting the +initial list of recipients. Adding a recipient after replying or +editing the message will not cause any send-hook to be executed, +similarily if $autoedit is set +(as then the initial list of recipients is empty). Also note that my_hdr commands which +modify recipient headers, or the message's subject, don't have any +effect on the current message when executed from a +send-hook. +

20. Change Settings Before Formatting a Message

Usage:

message-hook [!]pattern command @@ -1500,7 +1602,7 @@ This command can be used to execute arbitrary configuration commands before viewing or formatting a message based upon information about the message. command is executed if the pattern matches the message to be displayed. When multiple matches occur, commands are executed in the order -they are specified in the muttrc. +they are specified in the .muttrc.

See Message Matching in Hooks for information on the exact format of pattern. @@ -1509,7 +1611,7 @@ Example: 

 message-hook ~A 'set pager=builtin'
 message-hook '~f freshmeat-news' 'set pager="less \"+/^  subject: .*\""'
-

21. Choosing the cryptographic key of the recipient

Usage:

crypt-hook +

21. Choosing the Cryptographic Key of the Recipient

Usage:

crypt-hook pattern keyid @@ -1518,76 +1620,77 @@ When encrypting messages with PGP/GnuPG or OpenSSL, you may want to associate a key with a given e-mail address automatically, either because the recipient's public key can't be deduced from the destination address, or because, for some reasons, you need to override the key Mutt would -normally use. The crypt-hook command provides a +normally use. The crypt-hook command provides a method by which you can specify the ID of the public key to be used when encrypting messages to a certain recipient.

The meaning of keyid is to be taken broadly in this context: You can either put a numerical key ID here, an e-mail address, or even just a real name. -

22. Adding key sequences to the keyboard buffer

Usage:

push +

22. Adding Key Sequences to the Keyboard Buffer

Usage:

push string

This command adds the named string to the keyboard buffer. The string may contain control characters, key names and function names like the sequence -string in the macro command. You may use it to +string in the macro command. You may use it to automatically run a sequence of commands at startup, or when entering -certain folders. For example, the following command will automatically -collapse all threads when entering a folder: -

Example 3.12. Embedding push in folder-hook

+certain folders. For example, Example 3.13, “Embedding push in folder-hook”
+shows how to automatically collapse all threads when entering a folder.
+
Example 3.13. Embedding push in folder-hook
 folder-hook . 'push <collapse-all>'
-

23. Executing functions

Usage:

exec +


23. Executing Functions

Usage:

exec function [ function ...]

This command can be used to execute any function. Functions are listed in the function reference. -“exec function” is equivalent to “push <function>”. +“execfunction” is equivalent to +“push <function>”.

24. Message Scoring

Usage:

score pattern value -

unscore { +
unscore { * | pattern ... }

-The score commands adds value to a message's score if pattern +The score commands adds value to a message's score if pattern matches it. pattern is a string in the format described in the patterns section (note: For efficiency reasons, patterns which scan information not available in the index, such as ˜b, ˜B or ˜h, may not be used). value is a positive or negative integer. A message's final score is the sum total of all -matching score entries. However, you may optionally prefix value with -an equal sign (=) to cause evaluation to stop at a particular entry if there is +matching score entries. However, you may optionally prefix value with +an equal sign (“=”) to cause evaluation to stop at a particular entry if there is a match. Negative final scores are rounded up to 0.

-The unscore command removes score entries from the list. You must -specify the same pattern specified in the score command for it to be +The unscore command removes score entries from the list. You must +specify the same pattern specified in the score command for it to be removed. The pattern “*” is a special token which means to clear the list of all score entries. -

25. Spam detection

Usage:

spam +

25. Spam Detection

Usage:

spam pattern format -

nospam { +
nospam { * | pattern }

Mutt has generalized support for external spam-scoring filters. -By defining your spam patterns with the spam and nospam +By defining your spam patterns with the spam and nospam commands, you can limit, search, and sort your mail based on its spam attributes, as determined by the external filter. You also can display the spam attributes in your index -display using the %H selector in the $index_format variable. (Tip: try %?H?[%H] ? +display using the %H selector in the $index_format variable. (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a given message.)

Your first step is to define your external filter's spam patterns using -the spam command. pattern should be a regular expression +the spam command. pattern should be a regular expression that matches a header in a mail message. If any message in the mailbox matches this regular expression, it will receive a “spam tag” or -“spam attribute” (unless it also matches a nospam pattern -- see +“spam attribute” (unless it also matches a nospam pattern — see below.) The appearance of this attribute is entirely up to you, and is governed by the format parameter. format can be any static text, but it also can include back-references from the pattern @@ -1595,96 +1698,134 @@ expression. (A regular expression “back-reference sub-expression contained within parentheses.) %1 is replaced with the first back-reference in the regex, %2 with the second, etc.

+To match spam tags, mutt needs the corresponding header information +which is always the case for local and POP folders but not for IMAP in +the default configuration. Depending on the spam header to be analyzed, +$imap_headers may need +to be adjusted. +

If you're using multiple spam filters, a message can have more than -one spam-related header. You can define spam patterns for each +one spam-related header. You can define spam patterns for each filter you use. If a message matches two or more of these patterns, and -the $spam_separator variable is set to a string, then the +the $spam_separator variable is set to a string, then the message's spam tag will consist of all the format strings joined -together, with the value of $spam_separator separating +together, with the value of $spam_separator separating them.

-For example, suppose I use DCC, SpamAssassin, and PureMessage. I might -define these spam settings: -

Example 3.13. Configuring spam detection

+For example, suppose one uses DCC, SpamAssassin, and PureMessage, then
+the configuration might look like in Example 3.14, “Configuring spam detection”.
+
Example 3.14. Configuring spam detection
 spam "X-DCC-.*-Metrics:.*(....)=many"         "90+/DCC-%1"
 spam "X-Spam-Status: Yes"                     "90+/SA"
 spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
 set spam_separator=", "
 


-If I then received a message that DCC registered with “many” hits
+If then a message is received that DCC registered with “many” hits
 under the “Fuz2” checksum, and that PureMessage registered with a
 97% probability of being spam, that message's spam tag would read
 90+/DCC-Fuz2, 97/PM. (The four characters before “=many” in a
-DCC report indicate the checksum used -- in this case, “Fuz2”.)
+DCC report indicate the checksum used — in this case, “Fuz2”.)
 

-If the $spam_separator variable is unset, then each
+If the $spam_separator variable is unset, then each
 spam pattern match supersedes the previous one. Instead of getting
 joined format strings, you'll get only the last one to match.
 

 The spam tag is what will be displayed in the index when you use
-%H in the $index_format variable. It's also the
+%H in the $index_format variable. It's also the
 string that the ˜H pattern-matching expression matches against for
 <search> and <limit> functions. And it's what sorting by spam
 attribute will use as a sort key.
 

 That's a pretty complicated example, and most people's actual
 environments will have only one spam filter. The simpler your
-configuration, the more effective mutt can be, especially when it comes
+configuration, the more effective Mutt can be, especially when it comes
 to sorting.
 

-Generally, when you sort by spam tag, mutt will sort lexically --
+Generally, when you sort by spam tag, Mutt will sort lexically —
 that is, by ordering strings alphanumerically. However, if a spam tag
-begins with a number, mutt will sort numerically first, and lexically
+begins with a number, Mutt will sort numerically first, and lexically
 only when two numbers are equal in value. (This is like UNIX's
-sort -n.) A message with no spam attributes at all -- that is, one
-that didn't match any of your spam patterns -- is sorted at
+sort -n.) A message with no spam attributes at all — that is, one
+that didn't match any of your spam patterns — is sorted at
 lowest priority. Numbers are sorted next, beginning with 0 and ranging
 upward. Finally, non-numeric strings are sorted, with “a” taking lower
 priority than “z”. Clearly, in general, sorting by spam tags is most
 effective when you can coerce your filter to give you a raw number. But
-in case you can't, mutt can still do something useful.
+in case you can't, Mutt can still do something useful.
 

-The nospam command can be used to write exceptions to spam
-patterns. If a header pattern matches something in a spam command,
+The nospam command can be used to write exceptions to spam
+patterns. If a header pattern matches something in a spam command,
 but you nonetheless do not want it to receive a spam tag, you can list a
-more precise pattern under a nospam command.
+more precise pattern under a nospam command.
 

-If the pattern given to nospam is exactly the same as the
-pattern on an existing spam list entry, the effect will be to
+If the pattern given to nospam is exactly the same as the
+pattern on an existing spam list entry, the effect will be to
 remove the entry from the spam list, instead of adding an exception.
-Likewise, if the pattern for a spam command matches an entry
-on the nospam list, that nospam entry will be removed. If the
-pattern for nospam is “*”, all entries on both lists
-will be removed. This might be the default action if you use spam
-and nospam in conjunction with a folder-hook.
-

-You can have as many spam or nospam commands as you like.
-You can even do your own primitive spam detection within mutt -- for
+Likewise, if the pattern for a spam command matches an entry
+on the nospam list, that nospam entry will be removed. If the
+pattern for nospam is “*”, all entries on both lists
+will be removed. This might be the default action if you use spam
+and nospam in conjunction with a folder-hook.
+

+You can have as many spam or nospam commands as you like.
+You can even do your own primitive spam detection within Mutt — for
 example, if you consider all mail from MAILER-DAEMON to be spam,
-you can use a spam command like this:
+you can use a spam command like this:
 
 spam "^From: .*MAILER-DAEMON"       "999"
-

26. Setting and Querying Variables

26.1. Commands

+

26. Setting and Querying Variables

26.1. Variable Types

+Mutt supports these types of configuration variables: +

boolean

+A boolean expression, either “yes” or “no”. +

number

+A signed integer number in the range -32768 to 32767. +

string

+Arbitrary text. +

path

+A specialized string for representing paths including support for +mailbox shortcuts (see Section 7, “Mailbox Shortcuts”) as well as tilde +(“˜”) for a user's home directory and more. +

quadoption

+Like a boolean but triggers a prompt when set to “ask-yes” +or “ask-no” with “yes” and “no” +preselected respectively. +

sort order

+A specialized string allowing only particular words as values depending +on the variable. +

regular expression

+A regular expression, see Section 1, “Regular Expressions” for an introduction. +

folder magic

+Specifies the type of folder to use: mbox, +mmdf, mh +or maildir. +Currently only used to determine the type for newly created folders. +

e-mail address

+An e-mail address either with or without +realname. The older “user@example.org (Joe User)” +form is supported but strongly deprecated. +

user-defined

+Arbitrary text, see Section 26.3, “User-Defined Variables” for details. +

26.2. Commands

The following commands are available to manipulate and query variables:

Usage:

set { [ no | inv ] variable | variable=value - } [...]

toggle + } [...]
toggle variable [ variable -...]

unset +...]
unset variable [ variable -...]

reset +...]
reset variable [ variable ...]

-This command is used to set (and unset) configuration variables. There are four basic types of variables: +This command is used to set (and unset) configuration variables. There are four basic types of variables: boolean, number, string and quadoption. boolean variables can be set (true) or unset (false). number variables can be assigned a positive integer value. @@ -1699,16 +1840,16 @@ action to be carried out as if you had answered “no.ask-yes will cause a prompt with a default answer of “yes” and ask-no will provide a default answer of “no.”

-Prefixing a variable with “no” will unset it. Example: set noaskbcc. +Prefixing a variable with “no” will unset it. Example: set noaskbcc.

For boolean variables, you may optionally prefix the variable name with inv to toggle the value (on or off). This is useful when writing -macros. Example: set invsmart_wrap. +macros. Example: set invsmart_wrap.

-The toggle command automatically prepends the inv prefix to all +The toggle command automatically prepends the inv prefix to all specified variables.

-The unset command automatically prepends the no prefix to all +The unset command automatically prepends the no prefix to all specified variables.

Using the <enter-command> function in the index menu, you can query the @@ -1720,23 +1861,23 @@ set ?allow_8bit The question mark is actually only required for boolean and quadoption variables.

-The reset command resets all given variables to the compile time +The reset command resets all given variables to the compile time defaults (hopefully mentioned in this manual). If you use the command -set and prefix the variable with “&” this has the same -behavior as the reset command. +set and prefix the variable with “&” this has the same +behavior as the reset command.

-With the reset command there exists the special variable “all”, +With the reset command there exists the special variable “all”, which allows you to reset all variables to their system defaults. -

26.2. User-defined variables

26.2.1. Introduction

+

26.3. User-Defined Variables

26.3.1. Introduction

Along with the variables listed in the -Configuration variables section, mutt +Configuration variables section, Mutt supports user-defined variables with names starting with my_ as in, for example, my_cfgdir.

-The set command either creates a +The set command either creates a custom my_ variable or changes its -value if it does exist already. The unset and reset +value if it does exist already. The unset and reset commands remove the variable entirely.

Since user-defined variables are expanded in the same way that @@ -1744,10 +1885,10 @@ environment variables are (except for the shell-escape command and backtick expansion), this feature can be used to make configuration files more readable. -

26.2.2. Examples

+

26.3.2. Examples

The following example defines and uses the variable my_cfgdir -to abbreviate the calls of the source command: -

Example 3.14. Using user-defined variables for config file readability

+to abbreviate the calls of the source command:
+
Example 3.15. Using user-defined variables for config file readability
 set my_cfgdir = $HOME/mutt/config
 
 source $my_cfgdir/hooks
@@ -1756,26 +1897,26 @@ source $my_cfgdir/macros
 


 A custom variable can also be used in macros to backup the current value
 of another variable. In the following example, the value of the
-$delete is changed temporarily
+$delete is changed temporarily
 while its original value is saved as my_delete.
-After the macro has executed all commands, the original value of $delete is restored.
-
Example 3.15. Using user-defined variables for backing up other config option values
+After the macro has executed all commands, the original value of $delete is restored.
+
Example 3.16. Using user-defined variables for backing up other config option values
 macro pager ,x '\
 <enter-command>set my_delete=$delete<enter>\
 <enter-command>set delete=yes<enter>\
 ...\
 <enter-command>set delete=$my_delete<enter>'
 


-Since mutt expands such values already when parsing the configuration
+Since Mutt expands such values already when parsing the configuration
 file(s), the value of $my_delete in the
-last example would be the value of $delete exactly
+last example would be the value of $delete exactly
 as it was at that point during parsing the configuration file. If
-another statement would change the value for $delete
+another statement would change the value for $delete
 later in the same or another file, it would have no effect on
 $my_delete. However, the expansion can
 be deferred to runtime, as shown in the next example, when escaping the
 dollar sign.
-
Example 3.16. Deferring user-defined variable expansion to runtime
+
Example 3.17. Deferring user-defined variable expansion to runtime
 macro pager <PageDown> "\
 <enter-command> set my_old_pager_stop=\$pager_stop pager_stop<Enter>\
 <next-page>\
@@ -1784,9 +1925,9 @@ macro pager <PageDown> "\
 


 Note that there is a space
 between <enter-command> and
-the set configuration command, preventing mutt from
-recording the macro's commands into its history.
-
27. Reading initialization commands from another file
Usage:
source   
+the set configuration command, preventing Mutt from
+recording the macro's commands into its history.
+
27. Reading Initialization Commands From Another File
Usage:
source   
 filename
  

 This command allows the inclusion of initialization commands
@@ -1797,10 +1938,10 @@ from other files.  For example, I place all of my aliases in
 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 filename is
+If the filename ends with a vertical bar (“|”), then filename is
 considered to be an executable program from which to read input (eg.
-source ˜/bin/myscript|).
-
28. Removing hooks
Usage:
unhook  { 
+source ˜/bin/myscript|).
+
28. Removing Hooks
Usage:
unhook  { 
 *
   |   
 hook-type
@@ -1808,58 +1949,82 @@ considered to be an executable program from which to read input (eg.
 This command permits you to flush hooks you have previously defined.
 You can either remove all hooks by giving the “*” character as an
 argument, or you can remove all hooks of a specific type by saying
-something like unhook send-hook.
+something like unhook send-hook.
 
29. Format Strings
29.1. Basic usage

 Format strings are a general concept you'll find in several locations
-through the mutt configuration, especially in the
-$index_format,
-$pager_format,
-$status_format,
-and other “*_format” variables. These can be very straightforward,
+through the Mutt configuration, especially in the
+$index_format,
+$pager_format,
+$status_format,
+and other related variables. These can be very straightforward,
 and it's quite possible you already know how to use them.
 

 The most basic format string element is a percent symbol followed
 by another character. For example, %s
-represents a message's Subject: header in the $index_format variable. The
+represents a message's Subject: header in the $index_format variable. The
 “expandos” available are documented with each format variable, but
 there are general modifiers available with all formatting expandos,
 too. Those are our concern here.
 

 Some of the modifiers are borrowed right out of C (though you might
 know them from Perl, Python, shell, or another language). These are
-the [-]m.n modifiers, as in %-12.12s. As with
+the [-]m.n modifiers, as in %-12.12s. As with
 such programming languages, these modifiers allow you to specify the
 minimum and maximum size of the resulting string, as well as its
 justification. If the “-” sign follows the percent, the string will
 be left-justified instead of right-justified. If there's a number
 immediately following that, it's the minimum amount of space the
-formatted string will occupy -- if it's naturally smaller than that, it
+formatted string will occupy — if it's naturally smaller than that, it
 will be padded out with spaces.  If a decimal point and another number
-follow, that's the maximum space allowable -- the string will not be
+follow, that's the maximum space allowable — the string will not be
 permitted to exceed that width, no matter its natural size. Each of
 these three elements is optional, so that all these are legal format
-strings:
-%-12s
-%4c
-%.15F
-%-12.15L
+strings: %-12s, %4c,
+%.15F and %-12.15L.
 

 Mutt adds some other modifiers to format strings. If you use an equals
 symbol (=) as a numeric prefix (like the minus
 above), it will force the string to be centered within its minimum
 space range. For example, %=14y will reserve 14
-characters for the %y expansion -- that's the X-Label: header, in
-$index_format. If the expansion
+characters for the %y expansion — that's the X-Label: header, in
+$index_format. If the expansion
 results in a string less than 14 characters, it will be centered in a
-14-character space.  If the X-Label for a message were "test", that
-expansion would look like “     test     ”.
+14-character space.  If the X-Label for a message were “test”, that
+expansion would look like “     test     ”.
 

 There are two very little-known modifiers that affect the way that an
 expando is replaced. If there is an underline (“_”) character
 between any format modifiers (as above) and the expando letter, it will
 expands in all lower case. And if you use a colon (“:”), it will
 replace all decimal points with underlines.
-
29.2. Filters

+
29.2. Conditionals

+Depending on the format string variable, some of its 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:
+
+%?<sequence_char>?<optional_string>?

+where sequence_char is an expando, and
+optional_string is the string you would like printed if
+sequence_char is nonzero.
+optional_string may contain other
+sequences as well as normal text, but you may not nest optional
+strings.
+

+Here is an example illustrating how to optionally print the number of
+new messages in a mailbox in
+$status_format:
+
+%?n?%n new messages.?

+You can also switch between two strings using the following construct:
+
+%?<sequence_char>?<if_string>&<else_string>?

+If the value of sequence_char is
+non-zero, if_string will be expanded,
+otherwise else_string will be expanded.
+
29.3. Filters

 Any format string ending in a vertical bar (“|”) will be
 expanded and piped through the first word in the string, using spaces
 as separator. The string returned will be used for display.
@@ -1869,10 +2034,10 @@ replacement format string including % expandos.
 

 All % expandos in a format string are expanded before the script
 is called so that:
-
Example 3.17. Using external filters in format strings
+
Example 3.18. Using external filters in format strings
 set status_format="script.sh '%r %f (%L)'|"
 


-will make mutt expand %r,
+will make Mutt expand %r,
 %f and %L
 before calling the script. The example also shows that arguments can be
 quoted: the script will receive the expanded string between the single quotes
@@ -1880,10 +2045,43 @@ as the only argument.
 

 A practical example is the mutt_xtitle
 script installed in the samples
-subdirectory of the mutt documentation: it can be used as filter for
-$status_format to set the current
+subdirectory of the Mutt documentation: it can be used as filter for
+$status_format to set the current
 terminal's title, if supported.
-
Chapter 4. Advanced Usage
Table of Contents
1. Regular Expressions
2. Patterns: Searching, Limiting and Tagging
2.1. Pattern Modifier
2.2. Simple Patterns
2.3. Complex Patterns
2.4. Searching by Date
3. Using Tags
4. Using Hooks
4.1. Message Matching in Hooks
5. External Address Queries
6. Mailbox Formats
7. Mailbox Shortcuts
8. Handling Mailing Lists
9. Handling multiple folders
10. Editing threads
10.1. Linking threads
10.2. Breaking threads
11. Delivery Status Notification (DSN) Support
12. Start a WWW Browser on URLs
1. Regular Expressions

+
29.4. Padding

+In most format strings, Mutt supports different types of padding using
+special %-expandos:
+
%|X

+When this occurs, Mutt will fill the rest of the
+line with the character X. For
+example, filling the rest of the line with dashes is
+done by setting:
+
+set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"

+%>X
+

+Since the previous expando stops at the end of line, there must be a way
+to fill the gap between two items via the %>X
+expando: it puts as many characters X in between two
+items so that the rest of the line will be right-justified. For example,
+to not put the version string and hostname the above example on the left
+but on the right and fill the gap with spaces, one might use (note the
+space after %>):
+
+set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
%*X
+

+Normal right-justification will print everything to the left of the
+%>, displaying padding and whatever lies to the
+right only if there's room. By contrast, “soft-fill” gives
+priority to the right-hand side, guaranteeing space to display it and
+showing padding only if there's still room. If necessary, soft-fill will
+eat text leftwards to make room for rightward text. For example, to
+right-justify the subject making sure as much as possible of it fits on
+screen, one might use (note two spaces after %*
+: the second ensures there's a space between the truncated
+right-hand side and the subject):
+
+set index_format="%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?)%*  %s"
Chapter 4. Advanced Usage
Table of Contents
1. Regular Expressions
2. Patterns: Searching, Limiting and Tagging
2.1. Pattern Modifier
2.2. Simple Searches
2.3. Nesting and Boolean Operators
2.4. Searching by Date
3. Using Tags
4. Using Hooks
4.1. Message Matching in Hooks
5. External Address Queries
6. Mailbox Formats
7. Mailbox Shortcuts
8. Handling Mailing Lists
9. Handling multiple folders
10. Editing Threads
10.1. Linking Threads
10.2. Breaking Threads
11. Delivery Status Notification (DSN) Support
12. Start a WWW Browser on URLs
13. Miscellany
1. Regular Expressions

 All string patterns in Mutt including those in more complex
 patterns must be specified
 using regular expressions (regexp) in the “POSIX extended” syntax (which
@@ -1893,7 +2091,7 @@ convenience, we have included below a brief description of this syntax.
 The search is case sensitive if the pattern contains at least one upper
 case letter, and case insensitive otherwise.
 
Note

-Note that “\”
+“\”
 must be quoted if used for a regular expression in an initialization
 command: “\\”.
 

@@ -1901,7 +2099,7 @@ A regular expression is a pattern that describes a set of strings.
 Regular expressions are constructed analogously to arithmetic
 expressions, by using various operators to combine smaller expressions.
 
Note

-Note that the regular expression can be enclosed/delimited by either "
+The regular expression can be enclosed/delimited by either "
 or ' which is useful if the regular expression includes a white-space
 character.  See Syntax of Initialization Files
 for more information on " and ' delimiter processing.  To match a
@@ -1918,8 +2116,8 @@ the empty string at the beginning and end of a line.
 

 A list of characters enclosed by “[” and “]” matches any
 single character in that list; if the first character of the list
-is a caret “^” then it matches any character not in the
-list.  For example, the regular expression [0123456789]
+is a caret “^” then it matches any character not in the
+list.  For example, the regular expression [0123456789]
 matches any single digit.  A range of ASCII characters may be specified
 by giving the first and last characters, separated by a hyphen
 “-”.  Most metacharacters lose their special meaning inside
@@ -1938,8 +2136,8 @@ brackets of a character list.
 Note that the brackets in these
 class names are part of the symbolic names, and must be included
 in addition to the brackets delimiting the bracket list. For
-example, [[:digit:]] is equivalent to
-[0-9].
+example, [[:digit:]] is equivalent to
+[0-9].
 

 Two additional special sequences can appear in character lists.  These
 apply to non-ASCII character sets, which can have single symbols (called
@@ -1949,15 +2147,15 @@ sorting purposes:
 
Collating Symbols

 A collating symbol is a multi-character collating element enclosed in
 “[.” and “.]”.  For example, if “ch” is a collating
-element, then [[.ch.]] is a regexp that matches
-this collating element, while [ch] is a regexp that
+element, then [[.ch.]] is a regexp that matches
+this collating element, while [ch] is a regexp that
 matches either “c” or “h”.
 
Equivalence Classes

 An equivalence class is a locale-specific name for a list of
 characters that are equivalent. The name is enclosed in “[=”
 and “=]”.  For example, the name “e” might be used to
 represent all of “è” “é” and “e”.  In this case,
-[[=e=]] is a regexp that matches any of
+[[=e=]] is a regexp that matches any of
 “è”, “é” and “e”.
 

 A regular expression matching a single character may be followed by one
@@ -1975,52 +2173,56 @@ Repetition takes precedence over concatenation, which in turn takes
 precedence over alternation.  A whole subexpression may be enclosed in
 parentheses to override these precedence rules.
 
Note

-If you compile Mutt with the GNU rx package, the
+If you compile Mutt with the included regular expression engine, the
 following operators may also be used in regular expressions as described in Table 4.3, “GNU regular expression extensions”.
 
Table 4.3. GNU regular expression extensions
ExpressionDescription
\\yMatches the empty string at either the beginning or the end of a word
\\BMatches the empty string within a word
\\<Matches the empty string at the beginning of a word
\\>Matches the empty string at the end of a word
\\wMatches any word-constituent character (letter, digit, or underscore)
\\WMatches any character that is not word-constituent
\\`Matches the empty string at the beginning of a buffer (string)
\\'Matches the empty string at the end of a buffer


 Please note however that these operators are not defined by POSIX, so
 they may or may not be available in stock libraries on various systems.
-
2. Patterns: Searching, Limiting and Tagging

+
2. Patterns: Searching, Limiting and Tagging
2.1. Pattern Modifier

 Many of Mutt's commands allow you to specify a pattern to match
 (limit, tag-pattern,
 delete-pattern, etc.). Table 4.4, “Pattern modifiers”
 shows several ways to select messages.
-
Table 4.4. Pattern modifiers
Pattern modifierDescription
~Aall messages
~b EXPRmessages which contain EXPR in the message body
=b STRINGmessages which contain STRING in the message body. If IMAP is enabled, searches for STRING on the server, rather than downloading each message and searching it locally.
~B EXPRmessages which contain EXPR in the whole message
~c EXPRmessages carbon-copied to EXPR
%c GROUPmessages carbon-copied to any member of GROUP
~C EXPRmessages either to: or cc: EXPR
%C GROUPmessages either to: or cc: to any member of GROUP
~d [MIN]-[MAX]messages with “date-sent” in a Date range
~Ddeleted messages
~e EXPRmessages which contains EXPR in the “Sender” field
%e GROUPmessages which contain a member of GROUP in the “Sender” field
~Eexpired messages
~Fflagged messages
~f EXPRmessages originating from EXPR
%f GROUPmessages originating from any member of GROUP
~gcryptographically signed messages
~Gcryptographically encrypted messages
~h EXPRmessages which contain EXPR in the message header
~H EXPRmessages with a spam attribute matching EXPR
~i EXPRmessages which match EXPR in the “Message-ID” field
~kmessages which contain PGP key material
~L EXPRmessages either originated or received by EXPR
%L GROUPmessage either originated or received by any member of GROUP
~lmessages addressed to a known mailing list
~m [MIN]-[MAX]messages in the range MIN to MAX *)
~n [MIN]-[MAX]messages with a score in the range MIN to MAX *)
~Nnew messages
~Oold messages
~pmessages addressed to you (consults alternates)
~Pmessages from you (consults alternates)
~Qmessages which have been replied to
~r [MIN]-[MAX]messages with “date-received” in a Date range
~Rread messages
~s EXPRmessages having EXPR in the “Subject” field.
~Ssuperseded messages
~t EXPRmessages addressed to EXPR
~Ttagged messages
~umessages addressed to a subscribed mailing list
~Uunread messages
~vmessages part of a collapsed thread.
~Vcryptographically verified messages
~x EXPRmessages which contain EXPR in the “References” field
~X [MIN]-[MAX]messages with MIN to MAX attachments *)
~y EXPRmessages which contain EXPR in the “X-Label” field
~z [MIN]-[MAX]messages with a size in the range MIN to MAX *)
~=duplicated messages (see $duplicate_threads)
~$unreferenced messages (requires threaded view)
~(PATTERN)messages in threads
+
Table 4.4. Pattern modifiers
Pattern modifierDescription
~Aall messages
~b EXPRmessages which contain EXPR in the message body
=b STRINGmessages which contain STRING in the message body. If IMAP is enabled, searches for STRING on the server, rather than downloading each message and searching it locally.
~B EXPRmessages which contain EXPR in the whole message
~c EXPRmessages carbon-copied to EXPR
%c GROUPmessages carbon-copied to any member of GROUP
~C EXPRmessages either to: or cc: EXPR
%C GROUPmessages either to: or cc: to any member of GROUP
~d [MIN]-[MAX]messages with “date-sent” in a Date range
~Ddeleted messages
~e EXPRmessages which contains EXPR in the “Sender” field
%e GROUPmessages which contain a member of GROUP in the “Sender” field
~Eexpired messages
~Fflagged messages
~f EXPRmessages originating from EXPR
%f GROUPmessages originating from any member of GROUP
~gcryptographically signed messages
~Gcryptographically encrypted messages
~h EXPRmessages which contain EXPR in the message header
~H EXPRmessages with a spam attribute matching EXPR
~i EXPRmessages which match EXPR in the “Message-ID” field
~kmessages which contain PGP key material
~L EXPRmessages either originated or received by EXPR
%L GROUPmessage either originated or received by any member of GROUP
~lmessages addressed to a known mailing list
~m [MIN]-[MAX]messages in the range MIN to MAX *)
~n [MIN]-[MAX]messages with a score in the range MIN to MAX *)
~Nnew messages
~Oold messages
~pmessages addressed to you (consults alternates)
~Pmessages from you (consults alternates)
~Qmessages which have been replied to
~r [MIN]-[MAX]messages with “date-received” in a Date range
~Rread messages
~s EXPRmessages having EXPR in the “Subject” field.
~Ssuperseded messages
~t EXPRmessages addressed to EXPR
~Ttagged messages
~umessages addressed to a subscribed mailing list
~Uunread messages
~vmessages part of a collapsed thread.
~Vcryptographically verified messages
~x EXPRmessages which contain EXPR in the “References” or “In-Reply-To” field
~X [MIN]-[MAX]messages with MIN to MAX attachments *)
~y EXPRmessages which contain EXPR in the “X-Label” field
~z [MIN]-[MAX]messages with a size in the range MIN to MAX *) **)
~=duplicated messages (see $duplicate_threads)
~$unreferenced messages (requires threaded view)
~(PATTERN)messages in threads
 containing messages matching PATTERN, e.g. all
 threads containing messages from you: ~(~P)


 Where EXPR is a
-regular expression.  Special attention has to be
-made when using regular expressions inside of patterns.  Specifically,
+regular expression. 
+

+*) The forms “<[MAX]”, “>[MIN]”,
+“[MIN]-” and “-[MAX]”
+are allowed, too.
+

+**) The suffixes “K” and “M” are allowed to specify kilobyte and megabyte respectively.
+

+Special attention has to be
+payed when using regular expressions inside of patterns.  Specifically,
 Mutt's parser for these patterns will strip one level of backslash (“\”),
 which is normally used for quoting.  If it is your intention to use a
 backslash in the regular expression, you will need to use two backslashes
-instead (“\\”). You can force mutt to treat EXPR as a simple string
+instead (“\\”). You can force Mutt to treat EXPR as a simple string
 instead of a regular expression by using = instead of ˜ in the
 pattern name. For example, =b *.* will find all messages that contain
 the literal string “*.*”. Simple string matches are less powerful than
 regular expressions but can be considerably faster. This is especially
 true for IMAP folders, because string matches can be performed on the
 server instead of by fetching every message. IMAP treats =h specially:
-it must be of the form "header: substring" and will not partially
+it must be of the form “header: substring” and will not partially
 match header names. The substring part may be omitted if you simply
 wish to find messages containing a particular header without regard to
 its value.
 

-*) The forms “<[MAX]”, “>[MIN]”,
-“[MIN]-” and “-[MAX]”
-are allowed, too.
-
2.1. Pattern Modifier
Note

-Note that patterns matching 'lists' of addresses (notably c, C, p, P and t)
+Patterns matching lists of addresses (notably c, C, p, P and t)
 match if there is at least one match in the whole list. If you want to
 make sure that all elements of that list match, you need to prefix your
 pattern with “^”.
 This example matches all mails which only has recipients from Germany.
-
+
Example 4.1. Matching all addresses in address lists
 ^~C \.de$
-
2.2. Simple Patterns

-Mutt supports two versions of so called “simple searches” which are
+

2.2. Simple Searches

+Mutt supports two versions of so called “simple searches”. These are
 issued if the query entered for searching, limiting and similar
-operations does not seem to be a valid pattern (i.e. it does not contain
+operations does not seem to contain a valid pattern modifier (i.e. it does not contain
 one of these characters: “˜”, “=” or “%”). If the query is
 supposed to contain one of these special characters, they must be escaped
 by prepending a backslash (“\”).
@@ -2031,37 +2233,37 @@ If that is the case, Mutt will use the shown pattern modifier instead.
 If a keyword would conflict with your search keyword, you need to turn
 it into a regular expression to avoid matching the keyword table. For
 example, if you want to find all messages matching “flag”
-(using $simple_search)
+(using $simple_search)
 but don't want to match flagged messages, simply search for
 “[f]lag”.
 
Table 4.5. Simple search keywords
KeywordPattern modifier
all~A
.~A
^~A
del~D
flag~F
new~N
old~O
repl~Q
read~R
tag~T
unread~U


 The second type of simple search is to build a complex search
-pattern using $simple_search
+pattern using $simple_search
 as a template. Mutt will insert your query properly quoted and search
 for the composed complex query.
-
2.3. Complex Patterns

+
2.3. Nesting and Boolean Operators

 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 and that have the word “elkins” in the “From” header
+recipients and that have the word “elkins” in the “From” header
 field.
 

 Mutt also recognizes the following operators to create more complex search
 patterns:
 
  • 
-! -- logical NOT operator
+! — logical NOT operator
 
  • 
-| -- logical OR operator
+| — logical OR operator
 
  • 
-() -- logical grouping operator
+() — 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”.
-
Example 4.1. Using boolean operators in patterns
+
Example 4.2. Using boolean operators in patterns
 !(~t mutt|~c mutt) ~f elkins
 


 Here is an example using white space in the regular expression (note
@@ -2072,17 +2274,16 @@ or “Ed +SomeoneElse”:
  '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
 
Note

 If a regular expression contains parenthesis, or a vertical bar
-("|"), you must enclose the expression in double or single quotes since
+("|"), you must enclose the expression in double or single quotes since
 those characters are also used to separate different parts of Mutt's
 pattern language.  For example: ~f "me@(mutt\.org|cs\.hmc\.edu)"
-

 Without the quotes, the parenthesis wouldn't end.
 This would be separated to two OR'd patterns: ˜f me@(mutt\.org
 and cs\.hmc\.edu). They are never what you want.
-
2.4. Searching by Date

+
2.4. Searching by Date

 Mutt supports two types of dates, absolute and relative.
-

-Absolute.  Dates must be in DD/MM/YY format (month and year are
+
2.4.1. Absolute Dates

+Dates must be in DD/MM/YY format (month and year are
 optional, defaulting to the current month and year).  An example of a valid
 range of dates is:
 
@@ -2094,7 +2295,7 @@ messages before the given date will be se
 date will be selected.  If you specify a single date with no dash (“-”),
 only messages sent on the given date will be selected.
 

-Error Margins.  You can add error margins to absolute dates.
+You can add error margins to absolute dates.
 An error margin is a sign (+ or -), followed by a digit, followed by
 one of the units in Table 4.6, “Date units”. As a special case, you can replace the
 sign by a “*” character, which is equivalent to giving identical plus and minus error margins.
@@ -2103,15 +2304,15 @@ Example: To select any messages two weeks around January 15, 2001,
 you'd use the following pattern:
 
 Limit to messages matching: ~d 15/1/2001*2w
-

-Relative.  This type of date is relative to the current date, and may
+
2.4.2. Relative Dates

+This type of date is relative to the current date, and may
 be specified as:
 
  • 
->offset (messages older than offset units)
+>offset for messages older than offset units
 
  • 
-<offset (messages newer than offset units)
+<offset for messages newer than offset units
 
  • 
-=offset (messages exactly offset units old)
+=offset for messages exactly offset units old
 

 offset is specified as a positive number with one of the units from Table 4.6, “Date units”.
 

@@ -2120,10 +2321,10 @@ Example: to select messages less than 1 month old, you would use
 Limit to messages matching: ~d <1m
 
Note

 All dates used when searching are relative to the
-local time zone, so unless you change the setting of your $index_format to include a
-%[...] format, these are not the dates shown
+local time zone, so unless you change the setting of your $index_format to include a
+%[...] format, these are not the dates shown
 in the main index.
-
3. Using Tags

+
3. Using Tags

 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
@@ -2136,17 +2337,17 @@ matching syntax.
 

 Once you have tagged the desired messages, you can use the
 “tag-prefix” operator, which is the “;” (semicolon) key by default.
-When the “tag-prefix” operator is used, the next operation will
+When the “tag-prefix” operator is used, the next operation will
 be applied to all tagged messages if that operation can be used in that
-manner.  If the $auto_tag
+manner.  If the $auto_tag
 variable is set, the next operation applies to the tagged messages
 automatically, without requiring the “tag-prefix”.
 

-In macros or push commands,
-you can use the “tag-prefix-cond” operator.  If there are no tagged
-messages, mutt will "eat" the rest of the macro to abort it's execution.
-Mutt will stop "eating" the macro when it encounters the “end-cond”
-operator;  after this operator the rest of the macro will be executed as
+In macros or push commands,
+you can use the <tag-prefix-cond> operator.  If there are no tagged
+messages, Mutt will “eat” the rest of the macro to abort it's execution.
+Mutt will stop “eating” the macro when it encounters the <end-cond>
+operator; after this operator the rest of the macro will be executed as
 normal.
 
4. Using Hooks

 A hook is a concept found in many other programs which allows you to
@@ -2155,37 +2356,55 @@ you may wish to tailor your configuration based upon which mailbox you are
 reading, or to whom you are sending mail.  In the Mutt world, a hook
 consists of a regular expression or
 pattern along with a
-configuration option/command.  See
+configuration option/command.  See:
 
 

 
 for specific details on each type of hook available.
 
Note

 If a hook changes configuration settings, these changes remain
-effective until the end of the current mutt session. As this is generally
-not desired, a default hook needs to be added before all other hooks to
-restore configuration defaults. Here is an example with send-hook and the
-my_hdr directive:
-
Example 4.2. Combining send-hook and my_hdr
+effective until the end of the current Mutt session. As this is generally
+not desired, a “default” hook needs to be added before all
+other hooks  of that type to restore configuration defaults.
+
Example 4.3. Specifying a “default” hook
 send-hook . 'unmy_hdr From:'
 send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
-

4.1. Message Matching in Hooks

-Hooks that act upon messages (message-hook, reply-hook,
-send-hook, send2-hook, save-hook, fcc-hook) are evaluated in a
+


+In Example 4.3, “Specifying a default hook”, by default the value of
+$from
+and $realname
+is not overridden. When sending messages either To: or Cc:
+to <b@b.b>, the From: header is changed to
+<c@c.c>.
+
4.1. Message Matching in Hooks

+Hooks that act upon messages (message-hook, reply-hook,
+send-hook, send2-hook, save-hook, fcc-hook) are evaluated in a
 slightly different manner. For the other
 types of hooks, a regular expression is
 sufficient.  But in dealing with messages a finer grain of control is
@@ -2196,7 +2415,7 @@ Mutt allows the use of the limiting or
 searching the mailbox, except that you are restricted to those
-operators which match information mutt extracts from the header of
+operators which match information Mutt extracts from the header of
 the message (i.e., from, to, cc, date, subject, etc.).
 

 For example, if you wanted to set your return address based upon sending
@@ -2211,14 +2430,14 @@ However, it is not required that you write the pattern to match using the
 full searching language.  You can still specify a simple regular
 expression like the other hooks, in which case Mutt will translate your
 pattern into the full language, using the translation specified by the
-$default_hook variable.  The
+$default_hook variable.  The
 pattern is translated at the time the hook is declared, so the value of
-$default_hook that is in effect
+$default_hook that is in effect
 at that time will be used.
 
5. External Address Queries

 Mutt supports connecting to external directory databases such as LDAP,
-ph/qi, bbdb, or NIS through a wrapper script which connects to mutt
-using a simple interface.  Using the $query_command variable, you specify the wrapper
+ph/qi, bbdb, or NIS through a wrapper script which connects to Mutt
+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'"
@@ -2236,7 +2455,7 @@ me@cs.hmc.edu           Michael Elkins  mutt dude
 blong@fiction.net       Brandon Long    mutt and more
 roessler@does-not-exist.org        Thomas Roessler mutt pgp
 

-There are two mechanisms for accessing the query function of mutt.  One
+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 menu which will
 list the matching responses.  From the query menu, you can select
@@ -2247,80 +2466,107 @@ responses.
 The other mechanism for accessing the query function is for address
 completion, similar to the alias completion.  In any prompt for address
 entry, you can use the <complete-query> function (default: ^T) to run a
-query based on the current address you have typed.  Like aliases, mutt
+query based on the current address you have typed.  Like aliases, Mutt
 will look for what you have typed back to the last space or comma.  If
-there is a single response for that query, mutt will expand the address
-in place.  If there are multiple responses, mutt will activate the query
+there is a single response for that query, Mutt will expand the address
+in place.  If there are multiple responses, Mutt will activate the query
 menu.  At the query menu, you can select one or more addresses to be
 added to the prompt.
 
6. Mailbox Formats

-Mutt supports reading and writing of four different mailbox formats:
+Mutt supports reading and writing of four different local mailbox formats:
 mbox, MMDF, MH and Maildir.  The mailbox type is autodetected, so there
 is no need to use a flag for different mailbox types.  When creating new
-mailboxes, Mutt uses the default specified with the $mbox_type variable.
+mailboxes, Mutt uses the default specified with the
+$mbox_type variable. A
+short description of the formats follows.
 

-mbox.  This is the most widely used mailbox format for UNIX.  All
+mbox.  This is a widely used mailbox format for UNIX.  All
 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).
-

-MMDF.  This is a variant of the mbox format.  Each message is
-surrounded by lines containing “^A^A^A^A” (four control-A's).
-

-MH. A radical departure from mbox and MMDF, a mailbox
+“From_” line). The mbox format requires mailbox
+locking, is prone to mailbox corruption with concurrently writing
+clients or misinterpreted From_ lines. Depending on the
+environment, new mail detection can be unreliable. Mbox folders are fast
+to open and easy to archive.
+

+MMDF.  This is a variant of
+the mbox format.  Each message is surrounded by
+lines containing “^A^A^A^A” (four
+control-A's). The same problems as for mbox apply (also with finding the
+right message separator as four control-A's may appear in message
+bodies).
+

+MH. A radical departure from mbox and MMDF, a mailbox
 consists of a directory and each message is stored in a separate file.
 The filename indicates the message number (however, this is may not
 correspond to the message number Mutt displays). Deleted messages are
-renamed with a comma (,) prepended to the filename. Mutt
+renamed with a comma (“,”) prepended to the filename. Mutt
 detects this type of mailbox by looking for either .mh_sequences
-or .xmhcache (needed to distinguish normal directories from MH
-mailboxes).
-

-Maildir.  The newest of the mailbox formats, used by the Qmail MTA (a
+or .xmhcache files (needed to distinguish normal directories from MH
+mailboxes). MH is more robust with concurrent clients writing the mailbox,
+but still may suffer from lost flags; message corruption is less likely
+to occur than with mbox/mmdf. It's usually slower to open compared to
+mbox/mmdf since many small files have to be read (Mutt provides
+Section 7.1, “Header Caching” to greatly speed this process up).
+Depending on the environment, MH is not very disk-space efficient.
+

+Maildir.  The newest of the mailbox formats, used by the Qmail MTA (a
 replacement for sendmail).  Similar to MH, except that it adds three
 subdirectories of the mailbox: tmp, new and cur.  Filenames
 for the messages are chosen in such a way they are unique, even when two
 programs are writing the mailbox over NFS, which means that no file locking
-is needed.
+is needed and corruption is very unlikely. Maildir maybe
+slower to open without caching in Mutt, it too is not very
+disk-space efficient depending on the environment. Since no additional
+files are used for metadata (which is embedded in the message filenames)
+and Maildir is locking-free, it's easy to sync across different machines
+using file-level synchronization tools.
 
7. Mailbox Shortcuts

 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.
+path or in path-related configuration variables. Note that these only
+work at the beginning of a string.
 
  • 
-! -- refers to your $spoolfile (incoming) mailbox
+! — refers to your $spoolfile (incoming) mailbox
 
  • 
-> -- refers to your $mbox file
+> — refers to your $mbox file
 
  • 
-< -- refers to your $record file
+< — refers to your $record file
 
  • 
-^ -- refers to the current mailbox
+^ — refers to the current mailbox
 
  • 
-- or !! -- refers to the file you've last visited
+- or !! — refers to the file you've last visited
 
  • 
-˜ -- refers to your home directory
+˜ — refers to your home directory
 
  • 
-= or + -- refers to your $folder directory
+= or + — refers to your $folder directory
 
  • 
-@alias -- refers to the default save folder as determined by the address of the alias
-
8. Handling Mailing Lists

+@alias — refers to the default save folder as determined by the address of the alias
+

+For example, to store a copy of outgoing messages in the folder they
+were composed in,
+a folder-hook can
+be used to set $record:
+
+folder-hook . 'set record=^'
8. Handling Mailing Lists

 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 does not have to be a mailing list, but that is what it is most
 often used for), and what lists you are subscribed to.  This is
-accomplished through the use of the lists and subscribe commands in your muttrc.
+accomplished through the use of the lists and subscribe commands in your .muttrc.
 

 Now that Mutt knows what your mailing lists are, it can do several
 things, the first of which is the ability to show the name of a list
 through which you received a message (i.e., of a subscribed list) in
 the index menu display.  This is useful to distinguish between
-personal and list mail in the same mailbox.  In the $index_format variable, the escape “%L”
-will return the string “To <list>” when “list” appears in the
+personal and list mail in the same mailbox.  In the $index_format variable, the expando “%L”
+will print the string “To <list>” when “list” appears in the
 “To” field, and “Cc <list>” when it appears in the “Cc”
-field (otherwise it returns the name of the author).
+field (otherwise it prints 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
@@ -2333,7 +2579,7 @@ specified by Mail-Followup-To, see below).
 

 Mutt also supports the Mail-Followup-To header.  When you send
 a message to a list of recipients which includes one or several
-subscribed mailing lists, and if the $followup_to option is set, mutt will generate
+subscribed mailing lists, and if the $followup_to option is set, Mutt will generate
 a Mail-Followup-To header which contains all the recipients to whom
 you send this message, but not your address. This indicates that
 group-replies or list-replies (also known as “followups”) to this
@@ -2342,9 +2588,9 @@ message, and not separately to you - you'll receive your copy through
 one of the mailing lists you are subscribed to.
 

 Conversely, when group-replying or list-replying to a message which
-has a Mail-Followup-To header, mutt will respect this header if
-the $honor_followup_to configuration
-variable is set.  Using list-reply will in this case also make sure
+has a Mail-Followup-To header, Mutt will respect this header if
+the $honor_followup_to configuration
+variable is set.  Using list-reply will in this case also make sure
 that the reply goes to the mailing list, even if it's not specified
 in the list of recipients in the Mail-Followup-To.
 
Note

@@ -2357,7 +2603,7 @@ The other method some mailing list admins use is to generate a
 than the author of the message.  This can create problems when trying
 to reply directly to the author in private, since most mail clients
 will automatically reply to the address given in the “Reply-To”
-field.  Mutt uses the $reply_to
+field.  Mutt uses the $reply_to
 variable to help decide which address to use.  If set to ask-yes or
 ask-no, you will be
 prompted as to whether or not you would like to use the address given in
@@ -2367,15 +2613,15 @@ present.
 

 The “X-Label:” header field can be used to further identify mailing
 lists or list subject matter (or just to annotate messages
-individually).  The $index_format variable's “%y” and
-“%Y” escapes can be used to expand “X-Label:” fields in the
+individually).  The $index_format variable's “%y” and
+“%Y” expandos can be used to expand “X-Label:” fields in the
 index, and Mutt's pattern-matcher can match regular expressions to
 “X-Label:” fields with the “˜y” selector.  “X-Label:” is not a
 standard message header field, but it can easily be inserted by procmail
 and other mail filtering agents.
 

-Lastly, Mutt has the ability to sort the mailbox into
-threads.  A thread is a group of messages which all relate to the same
+Lastly, Mutt has the ability to sort the mailbox into
+threads.  A thread is a group of messages which all relate to the same
 subject.  This is usually organized into a tree-like structure where a
 message and all of its replies are represented graphically.  If you've ever
 used a threaded news client, this is the same concept.  It makes dealing
@@ -2383,21 +2629,21 @@ with large volume mailing lists easier because you can easily delete
 uninteresting threads and quickly find topics of value.
 
9. Handling multiple folders

 Mutt supports setups with multiple folders, allowing all of them to
-be monitored for new mail (see Section 14, “Monitoring incoming mail” for details).
+be monitored for new mail (see Section 14, “Monitoring Incoming Mail” for details).
 

 When in the index menu and being idle (also see
-$timeout), Mutt periodically checks
+$timeout), Mutt periodically checks
 for new mail in all folders which have been configured via the
-mailboxes command. The interval depends on the folder
+mailboxes command. The interval depends on the folder
 type: for local/IMAP folders it consults
-$mail_check and
-$pop_checkinterval
+$mail_check and
+$pop_checkinterval
 for POP folders.
 

 Outside the index menu the directory browser supports checking
 for new mail using the <check-new> function which is
 unbound by default. Pressing TAB will bring up a
-menu showing the files specified by the mailboxes command,
+menu showing the files specified by the mailboxes command,
 and indicate which contain new messages. Mutt will automatically enter this
 mode when invoked from the command line with the -y option.
 

@@ -2408,31 +2654,31 @@ the bottom of the screen.
 

 For the index, by default Mutt displays the number of mailboxes with new
 mail in the status bar, please refer to the
-$index_format
+$status_format
 variable for details.
 

 When changing folders, Mutt fills the prompt with the first folder from
 the mailboxes list containing new mail (if any), pressing
 space will cycle through folders with new mail.
-
10. Editing threads

+
10. Editing Threads

 Mutt has the ability to dynamically restructure threads that are broken
 either by misconfigured software or bad behavior from some
-correspondents. This allows to clean your mailboxes formats) from these
+correspondents. This allows to clean your mailboxes from these
 annoyances which make it hard to follow a discussion.
-
10.1. Linking threads

-Some mailers tend to "forget" to correctly set the "In-Reply-To:" and
-"References:" headers when replying to a message. This results in broken
+
10.1. Linking Threads

+Some mailers tend to “forget” to correctly set the “In-Reply-To:” and
+“References:” headers when replying to a message. This results in broken
 discussions because Mutt has not enough information to guess the correct
 threading.
 You can fix this by tagging the reply, then moving to the parent message
 and using the <link-threads> function (bound to & by default). The
-reply will then be connected to this "parent" message.
+reply will then be connected to this parent message.
 

 You can also connect multiple children at once, tagging them and using the
-tag-prefix command (';') or the auto_tag option.
-
10.2. Breaking threads

+<tag-prefix> command (';') or the $auto_tag option.
+
10.2. Breaking Threads

 On mailing lists, some people are in the bad habit of starting a new
-discussion by hitting "reply" to any message from the list and changing
+discussion by hitting “reply” to any message from the list and changing
 the subject to a totally unrelated one.
 You can fix such threads by using the <break-thread> function (bound
 by default to #), which will turn the subthread starting from the
@@ -2442,21 +2688,21 @@ RFC1894 defines a set of MIME content types for relaying information
 about the status of electronic mail messages.  These can be thought of as
 “return receipts.”
 

-To support DSN, there are two variables. $dsn_notify is used to request receipts for
+To support DSN, there are two variables. $dsn_notify is used to request receipts for
 different results (such as failed message, message delivered, etc.).
-$dsn_return requests how much
+$dsn_return requests how much
 of your message should be returned with the receipt (headers or full
 message).
 

-When using $sendmail for mail
+When using $sendmail for mail
 delivery, you need to use either Berkeley sendmail 8.8.x (or greater) a MTA
 supporting DSN command line options compatible to Sendmail: The -N and -R
 options can be used by the mail client to make requests as to what type of
 status messages should be returned. Please consider your MTA documentation
 whether DSN is supported.
 

-For SMTP delivery using $smtp_url, it depends on the
-capabilities announced by the server whether mutt will attempt to
+For SMTP delivery using $smtp_url, it depends on the
+capabilities announced by the server whether Mutt will attempt to
 request DSN or not.
 
12. Start a WWW Browser on URLs

 If a message contains URLs, it is efficient to get
@@ -2468,7 +2714,31 @@ and the configuration commands:
 
 macro index \cb |urlview\n
 macro pager \cb |urlview\n
-
Chapter 5. Mutt's MIME Support
Table of Contents
1. Using MIME in Mutt
1.1. Viewing MIME messages in the pager
1.2. The Attachment Menu
1.3. The Compose Menu
2. MIME Type configuration with mime.types
3. MIME Viewer configuration with mailcap
3.1. The Basics of the mailcap file
3.2. Secure use of mailcap
3.3. Advanced mailcap Usage
3.4. Example mailcap files
4. MIME Autoview
5. MIME Multipart/Alternative
6. Attachment Searching and Counting
7. MIME Lookup

+
13. Miscellany

+This section documents various features that fit nowhere else.
+

+Address normalization
+

+Mutt normalizes all e-mail addresses to the simplest form possible. If
+an address contains a realname, the form
+Joe User <joe@example.com> is used and the
+pure e-mail address without angle brackets otherwise, i.e. just
+joe@example.com.
+

+This normalization affects all headers Mutt generates including aliases.
+

+Initial folder selection
+

+The folder Mutt opens at startup is determined as follows: the folder
+specified in the $MAIL environment variable if
+present. Otherwise, the value of $MAILDIR is taken
+into account. If that isn't present either, Mutt takes the user's
+mailbox in the mailspool as determined at compile-time (which may also
+reside in the home directory). The
+$spoolfile setting overrides
+this selection. Highest priority has the mailbox given with the
+-f command line option.
+
Chapter 5. Mutt's MIME Support
Table of Contents
1. Using MIME in Mutt
1.1. Viewing MIME Messages in the Pager
1.2. The Attachment Menu
1.3. The Compose Menu
2. MIME Type Configuration with mime.types
3. MIME Viewer Configuration with Mailcap
3.1. The Basics of the Mailcap File
3.2. Secure Use of Mailcap
3.3. Advanced Mailcap Usage
3.4. Example Mailcap Files
4. MIME Autoview
5. MIME Multipart/Alternative
6. Attachment Searching and Counting
7. MIME Lookup

 Quite a bit of effort has been made to make Mutt the premier text-mode
 MIME MUA.  Every effort has been made to provide the functionality that
 the discerning MIME user requires, and the conformance to the standards
@@ -2481,7 +2751,7 @@ the external commands to use for handling specific MIME types.
 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.
-
1.1. Viewing MIME messages in the pager

+
1.1. Viewing MIME Messages in the Pager

 When you select a message from the index and view it in the pager, Mutt
 decodes the message to a text representation.  Mutt internally supports
 a number of MIME types, including text/plain, text/enriched,
@@ -2503,12 +2773,12 @@ If Mutt cannot deal with a MIME type, it will display a message like:
 
 [-- image/gif is unsupported (use 'v' to view this part) --]
 
1.2. The Attachment Menu

-The default binding for view-attachments is `v', which displays the
+The default binding for <view-attachments> is “v”, which displays the
 attachment menu for a message.  The attachment menu displays a list of
 the attachments in a message.  From the attachment menu, you can save,
 print, pipe, delete, and view attachments.  You can apply these
 operations to a group of attachments at once, by tagging the attachments
-and by using the “tag-prefix” operator.  You can also reply to the
+and by using the <tag-prefix> operator.  You can also reply to the
 current message from this menu, and only the current attachment (or the
 attachments tagged) will be quoted in your reply.  You can view
 attachments as text, or view them using the mailcap viewer definition.
@@ -2535,23 +2805,23 @@ Attachments appear as follows:
 

 The '-' denotes that Mutt will delete the file after sending (or
 postponing, or canceling) 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 the edit-type command
+<toggle-unlink> command (default: u).  The next field is the MIME
+content-type, and can be changed with the <edit-type> command
 (default: ^T).  The next field is the encoding for the attachment,
 which allows a binary message to be encoded for transmission on 7bit
-links.  It can be changed with the edit-encoding command
+links.  It can be changed with the <edit-encoding> command
 (default: ^E).  The next field is the size of the attachment,
 rounded to kilobytes or megabytes.  The next field is the filename,
-which can be changed with the rename-file command (default: R).
+which can be changed with the <rename-file> command (default: R).
 The final field is the description of the attachment, and can be
-changed with the edit-description command (default: d).
-
2. MIME Type configuration with mime.types

+changed with the <edit-description> command (default: d).
+
2. MIME Type Configuration with mime.types

 When you add an attachment to your mail message, Mutt searches your
-personal mime.types file at ${HOME}/.mime.types, and then
-the system mime.types file at /usr/local/share/mutt/mime.types or
+personal mime.types file at ${HOME}/.mime.types, and then
+the system mime.types file at /usr/local/share/mutt/mime.types or
 /etc/mime.types
 

-The mime.types file consist of lines containing a MIME type and a space
+The mime.types file consist of lines containing a MIME type and a space
 separated list of extensions.  For example:
 
 application/postscript          ps eps
@@ -2566,23 +2836,23 @@ 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
 as text/plain.  If the file contains binary information, then Mutt will
 mark it as application/octet-stream.  You can change the MIME
-type that Mutt assigns to an attachment by using the edit-type
+type that Mutt assigns to an attachment by using the <edit-type>
 command from the compose menu (default: ^T). The MIME type is actually a
 major mime type followed by the sub-type, separated by a '/'. 6 major
 types: application, text, image, video, audio, and model have been approved
 after various internet discussions. Mutt recognizes all of these if the
-appropriate entry is found in the mime.types file. It also recognizes other
+appropriate entry is found in the mime.types file. It also recognizes other
 major mime types, such as the chemical type that is widely used in the
 molecular modeling community to pass molecular data in various forms to
 various molecular viewers. Non-recognized mime types should only be used
 if the recipient of the message is likely to be expecting such attachments.
-
3. MIME Viewer configuration with mailcap

+
3. MIME Viewer Configuration with Mailcap

 Mutt supports RFC 1524 MIME Configuration, in particular the Unix
 specific format specified in Appendix A of RFC 1524.  This file format
 is commonly referred to as the mailcap format.  Many MIME compliant
 programs utilize the mailcap format, allowing you to specify handling
 for all MIME types in one place for all programs.  Programs known to
-use this format include Netscape, XMosaic, lynx and metamail.
+use this format include Firefox, lynx and metamail.
 

 In order to handle various MIME types that Mutt can not handle
 internally, Mutt parses a series of external configuration files to
@@ -2591,7 +2861,7 @@ is a colon delimited list containing the following files:
 
  1. $HOME/.mailcap
  2. $PKGDATADIR/mailcap
  3. $SYSCONFDIR/mailcap
  4. /etc/mailcap
  5. /usr/etc/mailcap
  6. /usr/local/etc/mailcap

 where $HOME is your home directory. The
 $PKGDATADIR and the
-$SYSCONFDIR directories depend on where mutt
+$SYSCONFDIR directories depend on where Mutt
 is installed: the former is the default for shared data, the
 latter for system configuration files.
 

@@ -2603,7 +2873,7 @@ mutt -nF /dev/null -Q mailcap_path
 In particular, the metamail distribution will install a mailcap file,
 usually as /usr/local/etc/mailcap, which contains some baseline
 entries.
-
3.1. The Basics of the mailcap file

+
3.1. The Basics of the Mailcap File

 A mailcap file consists of a series of lines which are comments, blank,
 or definitions.
 

@@ -2669,13 +2939,13 @@ text/html; lynx %s
 text/*; more
 

 This is the simplest form of a mailcap file.
-
3.2. Secure use of mailcap

+
3.2. Secure Use of Mailcap

 The interpretation of shell meta-characters embedded in MIME parameters
 can lead to security problems in general.  Mutt tries to quote parameters
 in expansion of %s syntaxes properly, and avoids risky characters by
-substituting them, see the $mailcap_sanitize variable.
+substituting them, see the $mailcap_sanitize variable.
 

-Although mutt's procedures to invoke programs with mailcap seem to be
+Although Mutt's procedures to invoke programs with mailcap seem to be
 safe, there are other applications parsing mailcap, maybe taking less care
 of it.  Therefore you should pay attention to the following rules:
 

@@ -2695,7 +2965,7 @@ since it is not itself subject to any further expansion):
 
 text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
         && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
-
3.3. Advanced mailcap Usage
3.3.1. Optional Fields

+
3.3. Advanced Mailcap Usage
3.3.1. Optional Fields

 In addition to the required content-type and view command fields, you
 can add semi-colon ';' separated fields to set flags and other options.
 Mutt recognizes the following optional fields:
@@ -2712,11 +2982,11 @@ 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.
 
needsterminal

-Mutt uses this flag when viewing attachments with auto_view, in order to decide whether it should honor the setting
-of the $wait_key variable or
+Mutt uses this flag when viewing attachments with auto_view, in order to decide whether it should honor the setting
+of the $wait_key variable or
 not.  When an attachment is viewed using an interactive program, and the
 corresponding mailcap entry has a needsterminal flag, Mutt will use
-$wait_key and the exit status
+$wait_key and the exit status
 of the program to decide if it will ask you to press a key after the
 external program has exited.  In all other situations it will not prompt
 you for a key.
@@ -2726,7 +2996,7 @@ specific MIME type.  Mutt supports this from the compose menu.
 
composetyped=<command>

 This flag specifies the command to use to create a new attachment of a
 specific MIME type.  This command differs from the compose command in
-that mutt will expect standard MIME headers on the data.  This can be
+that Mutt will expect standard MIME headers on the data.  This can be
 used to specify parameters, filename, description, etc. for a new
 attachment.   Mutt supports this from the compose menu.
 
print=<command>

@@ -2755,14 +3025,14 @@ then the test failed, and Mutt continues searching for the right entry.
 Note that the content-type must match before Mutt performs the test.
 For example:
 
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
+text/html; firefox -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 display the
-text/html object.  If RunningX doesn't return 0, then Mutt will go on
-to the next entry and use lynx to display the text/html object.
+RunningX returns 0, then Mutt will call firefox to display the
+text/html object.  If RunningX doesn't return 0, then Mutt will go on
+to the next entry and use lynx to display the text/html object.
 
3.3.2. Search Order

 When searching for an entry in the mailcap file, Mutt will search for
 the most useful entry for its purpose.  For instance, if you are
@@ -2777,24 +3047,24 @@ image/gif;      ; print= anytopnm %s | pnmtops | lpr; \
 Mutt will skip the image/* entry and use the image/gif
 entry with the print command.
 

-In addition, you can use this with auto_view
+In addition, you can use this with auto_view
 to denote two commands for viewing an attachment, one to be viewed
 automatically, the other to be viewed interactively from the attachment
 menu.  In addition, you 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;      firefox -remote 'openURL(%s)' ; test=RunningX
 text/html;      lynx %s; nametemplate=%s.html
 text/html;      lynx -dump %s; nametemplate=%s.html; copiousoutput
 

-For auto_view, Mutt will choose the third
+For auto_view, 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 program returns non-zero, Mutt will use the second entry
 for interactive viewing.
 
3.3.3. Command Expansion

 The various commands defined in the mailcap files are passed to the
-/bin/sh shell using the system() function.  Before the
+/bin/sh shell using the system(3) function.  Before the
 command is passed to /bin/sh -c, it is parsed to expand
 various special parameters with information from Mutt.  The keywords
 Mutt expands are:
@@ -2826,15 +3096,15 @@ 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 messages, which is handled internally by Mutt.
-
3.4. Example mailcap files

+
3.4. Example Mailcap Files

 This mailcap file is fairly simple and standard:
 
 # I'm always running X :)
 video/*;        xanim %s > /dev/null
 image/*;        xv %s > /dev/null
 
-# I'm always running netscape (if my computer had more memory, maybe)
-text/html;      netscape -remote 'openURL(%s)'
+# I'm always running firefox (if my computer had more memory, maybe)
+text/html;      firefox -remote 'openURL(%s)'
 

 This mailcap file shows quite a number of examples:
 
@@ -2842,12 +3112,12 @@ This mailcap file shows quite a number of examples:
 # send that to /dev/null so I don't see it
 video/*;        xanim %s > /dev/null
 
-# Send html to a running netscape by remote
-text/html;      netscape -remote 'openURL(%s)'; test=RunningNetscape
+# Send html to a running firefox by remote
+text/html;      firefox -remote 'openURL(%s)'; test=RunningFirefox
 
-# If I'm not running netscape but I am running X, start netscape on the
+# If I'm not running firefox but I am running X, start firefox on the
 # object
-text/html;      netscape %s; test=RunningX
+text/html;      firefox %s; test=RunningX
 
 # Else use lynx to view it as text
 text/html;      lynx %s
@@ -2858,7 +3128,7 @@ text/html;      lynx -dump %s; copiousoutput
 # I use enscript to print text in two columns to a page
 text/*;         more %s; print=enscript -2Gr %s
 
-# Netscape adds a flag to tell itself to view jpegs internally
+# Firefox adds a flag to tell itself to view jpegs internally
 image/jpeg;xv %s; x-mozilla-flags=internal
 
 # Use xv to view images if I'm running X
@@ -2874,6 +3144,16 @@ pbmtoascii -1x2 ) 2>&1 ; copiousoutput
 # Send excel spreadsheets to my NT box
 application/ms-excel; open.pl %s
 
4. MIME Autoview

+Usage:
+
auto-view   
+mimetype
+  [
+mimetype
+...]
unauto-view  { 
+*
+  |   
+mimetype
+... }

 In addition to explicitly telling Mutt to view an attachment with the
 MIME viewer defined in the mailcap file, Mutt has support for
 automatically viewing MIME attachments while in the pager.
@@ -2883,10 +3163,9 @@ To work, you must define a viewer in the mailcap file which uses the
 Usually, you also use the entry to convert the attachment to a text
 representation which you can view in the pager.
 

-You then use the auto_view muttrc command to list the
-content-types that you wish to view automatically.
-

-For instance, if you set auto_view to:
+You then use the auto_view .muttrc command to list the
+content-types that you wish to view automatically.  For instance, if you
+set it to:
 
 auto_view text/html application/x-gunzip \
   application/postscript image/gif application/x-tar-gz
@@ -2901,47 +3180,53 @@ application/x-gunzip;   gzcat; copiousoutput
 application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
 application/postscript; ps2ascii %s; copiousoutput
 

-“unauto_view” can be used to remove previous entries from the autoview list.
-This can be used with message-hook to autoview messages based on size, etc.
-“unauto_view *” will remove all previous entries.
+unauto_view can be used to remove previous entries from the autoview list.
+This can be used with message-hook to autoview messages based on size, etc.
+“unauto_view *” will remove all previous entries.
 
5. MIME Multipart/Alternative

 Mutt has some heuristics for determining which attachment of a
-multipart/alternative type to display.  First, mutt will check the
-alternative_order list to determine if one of the available types
-is preferred.  The alternative_order list consists of a number of
-mimetypes in order, including support for implicit and explicit
-wildcards, for example:
+multipart/alternative type to display.  First, Mutt will check the
+alternative_order list
+to determine if one of the available types is preferred.  It consists of
+a number of 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
+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.
 

-To remove a MIME type from the alternative_order list, use the
-unalternative_order command.
+To remove a MIME type from the alternative_order list, use the
+unalternative_order command.
 
6. Attachment Searching and Counting

 If you ever lose track of attachments in your mailboxes, Mutt's
 attachment-counting and -searching support might be for you.  You can
 make your message index display the number of qualifying attachments in
 each message, or search for messages by attachment count.  You also can
 configure what kinds of attachments qualify for this feature with the
-attachments and unattachments commands.
+attachments and unattachments commands.
 

-In order to provide this information, mutt needs to fully MIME-parse
+In order to provide this information, Mutt needs to fully MIME-parse
 all messages affected first. This can slow down operation especially for
 remote mail folders such as IMAP because all messages have to be
 downloaded first regardless whether the user really wants to view them
 or not.
 

 The syntax is:
-
-attachments   {+|-}disposition mime-type
-unattachments {+|-}disposition mime-type
-attachments   ?
-

-Disposition is the attachment's Content-disposition type -- either
+
attachments   
+{ + | - }disposition
+   
+mime-type
+ 
unattachments   
+{ + | - }disposition
+   
+mime-type
+ 
attachments   
+?
+ 

+disposition is the attachment's Content-Disposition type — either
 inline or attachment.
 You can abbreviate this to I or A.
 

@@ -2951,7 +3236,7 @@ type to qualify.  If it's a -, you're saying that this disposition
 and MIME type is an exception to previous + rules.  There are examples
 below of how this is useful.
 

-Mime-type is, unsurprisingly, the MIME type of the attachment you want
+mime-type is, unsurprisingly, the MIME type of the attachment you want
 to affect.  A MIME type is always of the format major/minor, where
 major describes the broad category of document you're looking at, and
 minor describes the specific type within that category.  The major
@@ -2959,11 +3244,11 @@ part of mime-type must be literal text (or the special token “*/.*” matches
 any MIME type.)
 

-The MIME types you give to the attachments directive are a kind of
-pattern.  When you use the attachments directive, the patterns you
-specify are added to a list.  When you use unattachments, the pattern
+The MIME types you give to the attachments directive are a kind of
+pattern.  When you use the attachments directive, the patterns you
+specify are added to a list.  When you use unattachments, the pattern
 is removed from the list.  The patterns are not expanded and matched
-to specific MIME types at this time -- they're just text in a list.
+to specific MIME types at this time — they're just text in a list.
 They're only matched when actually evaluating a message.
 

 Some examples might help to illustrate.  The examples that are not
@@ -3016,25 +3301,35 @@ attachments   +I text/plain
 attachments   -A message/external-body
 attachments   -I message/external-body
 


-Entering the command “attachments ?”
+Entering the command “attachments ?”
 as a command will list your current settings in Muttrc format, so that
 it can be pasted elsewhere.
 
7. MIME Lookup

+Usage:
+
mime-lookup   
+mimetype
+  [
+mimetype
+...]
unmime-lookup  { 
+*
+  |   
+mimetype
+... }

 Mutt's mime_lookup list specifies a list of mime-types that should not
 be treated according to their mailcap entry.  This option is designed to
-deal with binary types such as application/octet-stream.  When an attachment's
+deal with binary types such as application/octet-stream.  When an attachment's
 mime-type is listed in mime_lookup, then the extension of the filename will
-be compared to the list of extensions in the mime.types file.  The mime-type
+be compared to the list of extensions in the mime.types file.  The mime-type
 associated with this extension will then be used to process the attachment
 according to the rules in the mailcap file and according to any other configuration
-options (such as auto_view) specified.  Common usage would be:
+options (such as auto_view) specified.  Common usage would be:
 
 mime_lookup application/octet-stream application/X-Lotus-Manuscript
 

-In addition, the unmime_lookup command may be used to disable this feature
-for any particular mime-type if it had been set, for example, in a global
-muttrc.
-
Chapter 6. Optional features
Table of Contents
1. General notes
1.1. Enabling/disabling features
1.2. URL syntax
2. SSL/TLS Support
3. POP3 Support
4. IMAP Support
4.1. The Folder Browser
4.2. Authentication
5. SMTP Support
6. Managing multiple accounts
7. Local caching
7.1. Header caching
7.2. Body caching
7.3. Maintenance
8. Exact address generation
1. General notes
1.1. Enabling/disabling features

+In addition, the unmime_lookup command may be
+used to disable this feature for any particular mime-type if it had been
+set, for example, in a global .muttrc.
+
Chapter 6. Optional Features
Table of Contents
1. General Notes
1.1. Enabling/Disabling Features
1.2. URL Syntax
2. SSL/TLS Support
3. POP3 Support
4. IMAP Support
4.1. The IMAP Folder Browser
4.2. Authentication
5. SMTP Support
6. Managing Multiple Accounts
7. Local Caching
7.1. Header Caching
7.2. Body Caching
7.3. Maintenance
8. Exact Address Generation
9. Sending Anonymous Messages via Mixmaster
1. General Notes
1.1. Enabling/Disabling Features

 Mutt supports several of optional features which can be enabled or
 disabled at compile-time by giving the configure script
 certain arguments. These are listed in the “Optional features” section of
@@ -3043,42 +3338,42 @@ the configure --help output.
 Which features are enabled or disabled can later be determined from the
 output of mutt -v. If a compile option starts with
 “+” it is enabled and disabled if prefixed with “-”. For example, if
-mutt was compiled using GnuTLS for encrypted communication instead of
+Mutt was compiled using GnuTLS for encrypted communication instead of
 OpenSSL, mutt -v would contain:
 
--USE_SSL_OPENSSL +USE_SSL_GNUTLS
1.2. URL syntax

+-USE_SSL_OPENSSL +USE_SSL_GNUTLS
1.2. URL Syntax

 Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
 to access servers using URLs. The canonical syntax for specifying URLs
-in mutt is (an item enclosed in [] means it is optional and
+in Mutt is (an item enclosed in [] means it is optional and
 may be omitted):
 
 proto[s]://[username[:password]@]server[:port]/[path]
 

-proto is the communication protocol:
+proto is the communication protocol:
 imap for IMAP, pop for POP3 and
-smtp for SMTP. If “s” for “secure communication”
-is appended, mutt will attempt to establish an encrypted communication
-using SSL or TLS. If no explicit port is given, mutt will use the
-system's default for the given protocol.
-

-Since all protocols by mutt support authentication, the username may be
-given directly in the URL instead of using the pop_user or
-imap_user variables. It may contain the “@” symbol
-being used by many mail systems as part of the login name. A password can be
-given, too but is not recommended if the URL is specified in a configuration
-file on disk.
+smtp for SMTP. If “s” for “secure
+communication” is appended, Mutt will attempt to establish an
+encrypted communication using SSL or TLS.
+

+Since all protocols supported by Mutt support/require authentication,
+login credentials may be specified in the URL. This has the advantage
+that multiple IMAP, POP3 or SMTP servers may be specified (which isn't
+possible using, for example,
+$imap_user). The username
+may contain the “@” symbol being used by many mail systems
+as part of the login name. A password can be given, too but is not
+recommended if the URL is specified in a configuration file on disk.
+

+If no port number is given, Mutt will use the system's default for the
+given protocol (usually consulting /etc/services).
 

 The optional path is only relevant for IMAP.
-

-For IMAP for example, you can select an alternative port by specifying it with the
-server: imap://imapserver:port/INBOX. You can also specify different
-username for each folder: imap://username@imapserver[:port]/INBOX
-or imap://username2@imapserver[:port]/path/to/folder.
-Replacing imap:// by imaps://
-would make mutt attempt to connect using SSL or TLS on a different port
-to encrypt the communication.
-
2. SSL/TLS Support

-If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
+
Example 6.1. URLs
+pops://host/
+imaps://user@host/INBOX/Sent
+smtp://user@host:587/
+

2. SSL/TLS Support

+If Mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
 compiled with support for SSL or TLS using either OpenSSL or GnuTLS (
 by running the configure script with the
 --enable-ssl=... option for OpenSSL or
@@ -3086,36 +3381,45 @@ by running the configure script with the
 attempt to encrypt communication with remote servers if these protocols
 are suffixed with “s” for “secure communication”.
 
3. POP3 Support

-If Mutt was compiled with POP3 support (by running the configure
+If Mutt is compiled with POP3 support (by running the configure
 script with the --enable-pop flag), it has the ability to work
 with mailboxes located on a remote POP3 server and fetch mail for local
 browsing.
 

 Remote POP3 servers can be accessed using URLs with the pop protocol
 for unencrypted and pops for encrypted
-communication, see Section 1.2, “URL syntax” for details.
+communication, see Section 1.2, “URL Syntax” for details.
 

 Polling for new mail is more expensive over POP3 than locally. For this
 reason the frequency at which Mutt will check for mail remotely can be
 controlled by the
-$pop_checkinterval
+$pop_checkinterval
 variable, which defaults to every 60 seconds.
+

+POP is read-only which doesn't allow for some features like editing
+messages or changing flags. However, using
+Section 7.1, “Header Caching” and Section 7.2, “Body Caching”
+Mutt simulates the new/old/read flags as well as flagged and replied.
+Mutt applies some logic on top of remote messages but cannot change
+them so that modifications of flags are lost when
+messages are downloaded from the POP server (either by Mutt or other
+tools).
 

-Another way to access your POP3 mail is the <fetch-mail$ function
-(default: G).  It allows to connect to $pop_host, fetch all your new mail and place it in the
-local $spoolfile.  After this
+Another way to access your POP3 mail is the <fetch-mail> function
+(default: G).  It allows to connect to $pop_host, 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.
 
Note

 If you only need to fetch all messages to a
 local mailbox you should consider using a specialized program, such as
-fetchmail, getmail or similar.
+fetchmail(1), getmail(1) or similar.
 
4. IMAP Support

 If Mutt was compiled with IMAP support (by running the configure
 script with the --enable-imap flag), it has the ability to work
 with folders located on a remote IMAP server.
 

 You can access the remote inbox by selecting the folder by its URL
-(see Section 1.2, “URL syntax” for details) using the
+(see Section 1.2, “URL Syntax” for details) using the
 imap or imaps protocol.
 Alternatively, a pine-compatible notation is also supported, ie
 {[username@]imapserver[:port][/ssl]}path/to/folder
@@ -3127,30 +3431,30 @@ paths accordingly.
 When browsing folders on an IMAP server, you can toggle whether to look
 at only the folders you are subscribed to, or all folders with the
 toggle-subscribed command.  See also the
-$imap_list_subscribed variable.
+$imap_list_subscribed variable.
 

 Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
 want to carefully tune the
-$mail_check
+$mail_check
 and
-$timeout
-variables. Personally I use
+$timeout
+variables. Reasonable values are:
 
 set mail_check=90
 set timeout=15
 

-with relatively good results over my slow modem line.
+with relatively good results even over slow modem lines.
 
Note

 Note that if you are using mbox as the mail store on UW servers prior to
 v12.250, the server has been reported to disconnect a client if another client
 selects the same folder.
-
4.1. The Folder Browser

-As of version 1.2, mutt supports browsing mailboxes on an IMAP
+
4.1. The IMAP Folder Browser

+As of version 1.2, Mutt supports browsing mailboxes on an IMAP
 server. This is mostly the same as the local file browser, with the
 following differences:
 
  • 
-In lieu of file permissions, mutt displays the string "IMAP",
-possibly followed by the symbol "+", indicating
+In lieu of file permissions, Mutt displays the string “IMAP”,
+possibly followed by the symbol “+”, indicating
 that the entry contains both messages and subfolders. On
 Cyrus-like servers folders will often contain both messages and
 subfolders.
@@ -3162,10 +3466,10 @@ the messages in that folder, you must use view-file
 (bound to space by default).
 
  • 
 You can create, delete and rename mailboxes with the
-create-mailbox, delete-mailbox, and
-rename-mailbox commands (default bindings: C,
+<create-mailbox>, <delete-mailbox>, and
+<rename-mailbox> commands (default bindings: C,
 d and r, respectively). You may also
-subscribe and unsubscribe to mailboxes (normally
+<subscribe> and <unsubscribe> to mailboxes (normally
 these are bound to s and u, respectively).
 
4.2. Authentication

 Mutt supports four authentication methods with IMAP servers: SASL,
@@ -3174,7 +3478,7 @@ NTLM authentication for you poor exchange users out there, but it has
 yet to be integrated into the main tree). There is also support for
 the pseudo-protocol ANONYMOUS, which allows you to log in to a public
 IMAP server without having an account. To use ANONYMOUS, simply make
-your username blank or "anonymous".
+your username blank or “anonymous”.
 

 SASL is a special super-authenticator, which selects among several protocols
 (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure
@@ -3182,56 +3486,62 @@ method available on your host and the server. Using some of these methods
 (including DIGEST-MD5 and possibly GSSAPI), your entire session will be
 encrypted and invisible to those teeming network snoops. It is the best
 option if you have it. To use it, you must have the Cyrus SASL library
-installed on your system and compile mutt with the --with-sasl flag.
+installed on your system and compile Mutt with the --with-sasl flag.
 

 Mutt will try whichever methods are compiled in and available on the server,
 in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
 

 There are a few variables which control authentication:
 
  • 
-$imap_user - controls
+$imap_user - controls
 the username under which you request authentication on the IMAP server,
 for all authenticators. This is overridden by an explicit username in
 the mailbox path (ie by using a mailbox name of the form
 {user@host}).
 
  • 
-$imap_pass - a
+$imap_pass - a
 password which you may preset, used by all authentication methods where
 a password is needed.
 
  • 
-$imap_authenticators - a colon-delimited list of IMAP
+$imap_authenticators - a colon-delimited list of IMAP
 authentication methods to try, in the order you wish to try them. If
-specified, this overrides mutt's default (attempt everything, in the order
+specified, this overrides Mutt's default (attempt everything, in the order
 listed above).
 
5. SMTP Support

 Besides supporting traditional mail delivery through a
-sendmail-compatible program, mutt supports delivery through SMTP if it
+sendmail-compatible program, Mutt supports delivery through SMTP if it
 was configured and built with --enable-smtp.
 

 If the configuration variable
-$smtp_url is set, mutt
+$smtp_url is set, Mutt
 will contact the given SMTP server to deliver messages; if it is unset,
-mutt will use the program specified by $sendmail.
+Mutt will use the program specified by $sendmail.
 

-For details on the URL syntax, please see Section 1.2, “URL syntax”.
+For details on the URL syntax, please see Section 1.2, “URL Syntax”.
 

 The built-in SMTP support supports encryption (the smtps protocol
 using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms
-for SASL are specified in $smtp_authenticators
-defaulting to an empty list which makes mutt try all available methods
+for SASL are specified in $smtp_authenticators
+defaulting to an empty list which makes Mutt try all available methods
 from most-secure to least-secure.
-
6. Managing multiple accounts

+
6. Managing Multiple Accounts

+Usage:
+
account-hook   
+pattern
+   
+command
+ 

 If you happen to have accounts on multiple IMAP, POP and/or SMTP servers,
 you may find managing all the authentication settings inconvenient and
-error-prone. The account-hook command may help. This hook works like
-folder-hook but is invoked whenever you access a remote mailbox
+error-prone. The account-hook command may help. This hook works like
+folder-hook but is invoked whenever Mutt needs to access a remote mailbox
 (including inside the folder browser), not just when you open the
-mailbox which includes (for example) polling for new mail, storing Fcc
+mailbox. This includes (for example) polling for new mail, storing Fcc
 messages and saving messages to a folder. As a consequence,
-account-hook should only be used to set connection-related settings such
+account-hook should only be used to set connection-related settings such
 as passwords or tunnel commands but not settings such as sender
 address or name (because in general it should be considered unpredictable
-which account-hook was last used).
+which account-hook was last used).
 

 Some examples:
 
@@ -3239,15 +3549,45 @@ account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
 account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
 account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
 account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
-
7. Local caching

+

+To manage multiple accounts with, for example, different values of
+$record or sender addresses,
+folder-hook
+has to be be used together with
+the mailboxes command.
+
Example 6.2. Managing multiple accounts
+mailboxes imap://user@host1/INBOX
+folder-hook imap://user@host1/ 'set folder=imap://host1/ ; set record=+INBOX/Sent'
+
+mailboxes imap://user@host2/INBOX
+folder-hook imap://user@host2/ 'set folder=imap://host2/ ; set record=+INBOX/Sent'
+


+In example
+Example 6.2, “Managing multiple accounts” the folders are defined using
+mailboxes so Mutt polls them for new
+mail. Each folder-hook triggers when
+one mailbox below each IMAP account is opened and sets
+$folder to the account's root
+folder. Next, it sets $record to
+the INBOX/Sent folder below the newly
+set $folder. Please notice that the
+value the “+”
+mailbox shortcut refers to depends on
+the current value
+of $folder and therefore has to be set
+separatedly per account. Setting other values
+like $from
+or $signature is analogous to setting
+$record.
+
7. Local Caching

 Mutt contains two types of local caching: (1)
 the so-called “header caching” and (2) the
 so-called “body caching” which are both described in this section.
 

 Header caching is optional as it depends on external libraries, body
-caching is always enabled if mutt is compiled with POP and/or IMAP
+caching is always enabled if Mutt is compiled with POP and/or IMAP
 support as these use it (body caching requires no external library).
-
7.1. Header caching

+
7.1. Header Caching

 Mutt provides optional support for caching message headers for the
 following types of folders: IMAP, POP, Maildir and MH. Header caching
 greatly improves speed because for remote folders, headers
@@ -3260,87 +3600,168 @@ Header caching can be enabled via the configure script and the
 by default because external database libraries are required: one
 of tokyocabinet, qdbm, gdbm or bdb must be present.
 

-If enabled, $header_cache can be
+If enabled, $header_cache can be
 used to either point to a file or a directory. If set to point to
 a file, one database file for all folders will be used (which may
 result in lower performance), but one file per folder if it points
 to a directory.
-

-For the one-file-per-folder case, database files for remote folders
-will be named according to their URL while database files for local
-folders will be named by the MD5 checksums of their path. These database
-files may be safely removed if a system is short on space. You
-can compute the name of the header cache file for a particular local folder
-through a command like the following:
-
-$ printf '%s' '/path/to/folder' | md5sum
-

-The md5sum command may also be
-named md5, depending on your operating system.
-
7.2. Body caching

+
7.2. Body Caching

 Both cache methods can be combined using the same directory for storage
 (and for IMAP/POP even provide meaningful file names) which simplifies
 manual maintenance tasks.
 

-In addition to caching message headers only, mutt can also cache
+In addition to caching message headers only, Mutt can also cache
 whole message bodies. This results in faster display of messages
 for POP and IMAP folders because messages usually have to be
 downloaded only once.
 

-For configuration, the variable $message_cachedir must point to a
-directory. There, mutt will create a hierarchy of subdirectories
+For configuration, the variable $message_cachedir must point to a
+directory. There, Mutt will create a hierarchy of subdirectories
 named like: proto:user@hostname where
 proto is either “pop” or “imap.” Within
-there for each folder, mutt stores messages in single files (just
-like Maildir) so that with manual symlink creation these cache
-directories can be examined with mutt as read-only Maildir folders.
-

+there for each folder, Mutt stores messages in single files.
 All files can be removed as needed if the consumed disk space
-becomes an issue as mutt will silently fetch missing items again.
+becomes an issue as Mutt will silently fetch missing items again.
 
7.3. Maintenance

 Mutt does not (yet) support maintenance features for header cache
 database files so that files have to be removed in case they grow too
 big. It depends on the database library used for header caching whether
 disk space freed by removing messages is re-used.
 

-For body caches, mutt can keep the local cache in sync with the
+For body caches, Mutt can keep the local cache in sync with the
 remote mailbox if the
-$message_cache_clean
+$message_cache_clean
 variable is set. Cleaning means to remove messages from the cache which
 are no longer present in the mailbox which only happens when other mail
-clients or instances of mutt using a different body cache location
+clients or instances of Mutt using a different body cache location
 delete messages (Mutt itself removes deleted messages from the cache
 when syncing a mailbox). As cleaning can take a noticeable amount of time,
 it should not be set in general but only occasionally.
-
8. Exact address generation

+
8. Exact Address Generation

 Mutt supports the “Name <user@host>” address syntax for reading and
 writing messages, the older “user@host (Name)” syntax is only supported when
 reading messages. The --enable-exact-address
 switch can be given to configure to build it with write-support
 for the latter syntax. EXACT_ADDRESS in the output of
 mutt -v indicates whether it's supported.
-
Chapter 7. Performance tuning
Table of Contents
1. Reading and writing mailboxes
2. Reading messages from remote folders
3. Searching and limiting
1. Reading and writing mailboxes

+
9. Sending Anonymous Messages via Mixmaster

+You may also have compiled Mutt to co-operate with Mixmaster, an
+anonymous remailer.  Mixmaster permits you to send your messages
+anonymously using a chain of remailers. Mixmaster support in Mutt is for
+mixmaster version 2.04 (beta 45 appears to be the latest) and 2.03.
+It does not support earlier versions or the later so-called version 3 betas,
+of which the latest appears to be called 2.9b23.
+

+To use it, you'll have to obey certain restrictions.  Most
+important, you cannot use the Cc and Bcc headers.  To tell
+Mutt to use mixmaster, you have to select a remailer chain, using
+the mix function on the compose menu.
+

+The chain selection screen is divided into two parts.  In the
+(larger) upper part, you get a list of remailers you may use.  In
+the lower part, you see the currently selected chain of remailers.
+

+You can navigate in the chain using the <chain-prev> and
+<chain-next> functions, which are by default bound to the left
+and right arrows and to the h and l keys (think vi
+keyboard bindings).  To insert a remailer at the current chain
+position, use the <insert> function.  To append a remailer behind
+the current chain position, use <select-entry> or <append>.
+You can also delete entries from the chain, using the corresponding
+function.  Finally, to abandon your changes, leave the menu, or
+<accept> them pressing (by default) the Return key.
+

+Note that different remailers do have different capabilities,
+indicated in the %c entry of the remailer menu lines (see
+$mix_entry_format).  Most important is
+the “middleman” capability, indicated by a capital “M”: This
+means that the remailer in question cannot be used as the final
+element of a chain, but will only forward messages to other
+mixmaster remailers.  For details on the other capabilities, please
+have a look at the mixmaster documentation.
+
Chapter 7. Security Considerations
Table of Contents
1. Passwords
2. Temporary Files
3. Information Leaks
3.1. Message-Id: headers
3.2. mailto:-style Links
4. External Applications

+First of all, Mutt contains no security holes included by intention but
+may contain unknown security holes. As a consequence, please run Mutt
+only with as few permissions as possible. Especially, do not run Mutt as
+the super user.
+

+When configuring Mutt, there're some points to note about secure setups
+so please read this chapter carefully.
+
1. Passwords

+Although Mutt can be told the various passwords for accounts, please
+never store passwords in configuration files. Besides the fact that the
+system's operator can always read them, you could forget to mask it out
+when reporting a bug or asking for help via a mailing list. Even worse,
+your mail including your password could be archived by internet search
+engines, mail-to-news gateways etc. It may already be too late before
+you notice your mistake.
+
2. Temporary Files

+Mutt uses many temporary files for viewing messages, verifying digital
+signatures, etc. As long as being used, these files are visible by other
+users and maybe even readable in case of misconfiguration.  Also, a
+different location for these files may be desired which can be changed
+via the $tmpdir variable.
+
3. Information Leaks
3.1. Message-Id: headers

+Message-Id: headers contain a local part that is to be created in a
+unique fashion. In order to do so, Mutt will “leak” some
+information to the outside world when sending messages: the generation
+of this header includes a step counter which is increased (and rotated)
+with every message sent. In a longer running mutt session, others can
+make assumptions about your mailing habbits depending on the number of
+messages sent. If this is not desired, the header can be manually
+provided using $edit_headers (though not
+recommended).
+
3.2. mailto:-style Links

+As Mutt be can be set up to be the mail client to handle
+mailto: style links in websites, there're security
+considerations, too. Arbitrary header fields can be embedded in these
+links which could override existing header fields or attach arbitrary
+files using the Attach:
+psuedoheader. This may be problematic if the $edit-headers variable is
+unset, i.e. the user doesn't want to see header
+fields while editing the message and doesn't pay enough attention to the
+compose menu's listing of attachments.
+

+For example, following a link like
+
+mailto:joe@host?Attach=~/.gnupg/secring.gpg

+will send out the user's private gnupg keyring to
+joe@host if the user doesn't follow the information
+on screen carefully enough.
+
4. External Applications

+Mutt in many places has to rely on external applications or for
+convenience supports mechanisms involving external applications.
+

+One of these is the mailcap mechanism as defined by
+RfC1524. Details about a secure use of the mailcap mechanisms is given
+in Section 3.2, “Secure Use of Mailcap”.
+

+Besides the mailcap mechanism, Mutt uses a number of other external
+utilities for operation, for example to provide crypto support, in
+backtick expansion in configuration files or format string filters.  The
+same security considerations apply for these as for tools involved via
+mailcap.
+
Chapter 8. Performance Tuning
Table of Contents
1. Reading and Writing Mailboxes
2. Reading Messages from Remote Folders
3. Searching and Limiting
1. Reading and Writing Mailboxes

 Mutt's performance when reading mailboxes can be improved in two ways:
 
  1. 
 For remote folders (IMAP and POP) as well as folders using
-one-file-per message storage (Maildir and MH), mutt's
+one-file-per message storage (Maildir and MH), Mutt's
 performance can be greatly improved using
-header caching.
-Using a single database per folder may further increase
-performance.
+header caching.
+using a single database per folder.
 
  2. 
-Mutt provides the $read_inc
-and $write_inc
+Mutt provides the $read_inc
+and $write_inc
 variables to specify at which rate to update progress
-counters. If these values are too low, mutt may spend more
+counters. If these values are too low, Mutt may spend more
 time on updating the progress counter than it spends on
 actually reading/writing folders.
 
    
 For example, when opening a maildir folder with a few
 thousand messages, the default value for
-$read_inc
+$read_inc
 may be too low. It can be tuned on on a folder-basis using
-folder-hooks:
+folder-hooks:
 
     # use very high $read_inc to speed up reading hcache'd maildirs
 folder-hook . 'set read_inc=1000'
@@ -3353,18 +3774,18 @@ even per-folder settings of the increment variables may not be
 desirable as they produce either too few or too much progress updates.
 Thus, Mutt allows to limit the number of progress updates per second it'll
 actually send to the terminal using the
-$time_inc variable.
2. Reading messages from remote folders

+$time_inc variable.
2. Reading Messages from Remote Folders

 Reading messages from remote folders such as IMAP an POP can be
-slow especially for large mailboxes since mutt only caches a very
+slow especially for large mailboxes since Mutt only caches a very
 limited number of recently viewed messages (usually 10) per
 session (so that it will be gone for the next session.)
 

 To improve performance and permanently cache whole messages,
-please refer to mutt's so-called
-body caching for details.
-
3. Searching and limiting

+please refer to Mutt's so-called
+body caching for details.
+
3. Searching and Limiting

 When searching mailboxes either via a search or a limit action, for
-some patterns mutt distinguishes between regular expression and string
+some patterns Mutt distinguishes between regular expression and string
 searches. For regular expressions, patterns are prefixed with
 “˜” and with “=” for string searches.
 

@@ -3380,14 +3801,14 @@ address via =Luser@ instead of
 ˜Luser@. This is especially true for searching
 message bodies since a larger amount of input has to be searched.
 

-Please note that string search is an exact case-sensitive search
-while a regular expression search with only lower-case letters performs
-a case-insensitive search.
-
Chapter 8. Reference
Table of Contents
1. Command line options
2. Configuration Commands
3. Configuration variables
3.1. abort_nosubject
3.2. abort_unmodified
3.3. alias_file
3.4. alias_format
3.5. allow_8bit
3.6. allow_ansi
3.7. arrow_cursor
3.8. ascii_chars
3.9. askbcc
3.10. askcc
3.11. assumed_charset
3.12. attach_charset
3.13. attach_format
3.14. attach_sep
3.15. attach_split
3.16. attribution
3.17. autoedit
3.18. auto_tag
3.19. beep
3.20. beep_new
3.21. bounce
3.22. bounce_delivered
3.23. braille_friendly
3.24. check_mbox_size
3.25. charset
3.26. check_new
3.27. collapse_unread
3.28. uncollapse_jump
3.29. compose_format
3.30. config_charset
3.31. confirmappend
3.32. confirmcreate
3.33. connect_timeout
3.34. content_type
3.35. copy
3.36. crypt_use_gpgme
3.37. crypt_use_pka
3.38. crypt_autopgp
3.39. crypt_autosmime
3.40. date_format
3.41. default_hook
3.42. delete
3.43. delete_untag
3.44. digest_collapse
3.45. display_filter
3.46. dotlock_program
3.47. dsn_notify
3.48. dsn_return
3.49. duplicate_threads
3.50. edit_headers
3.51. editor
3.52. encode_from
3.53. envelope_from_address
3.54. escape
3.55. fast_reply
3.56. fcc_attach
3.57. fcc_clear
3.58. folder
3.59. folder_format
3.60. followup_to
3.61. force_name
3.62. forward_decode
3.63. forward_edit
3.64. forward_format
3.65. forward_quote
3.66. from
3.67. gecos_mask
3.68. hdrs
3.69. header
3.70. help
3.71. hidden_host
3.72. hide_limited
3.73. hide_missing
3.74. hide_thread_subject
3.75. hide_top_limited
3.76. hide_top_missing
3.77. history
3.78. history_file
3.79. honor_followup_to
3.80. hostname
3.81. ignore_linear_white_space
3.82. ignore_list_reply_to
3.83. imap_authenticators
3.84. imap_check_subscribed
3.85. imap_delim_chars
3.86. imap_headers
3.87. imap_idle
3.88. imap_keepalive
3.89. imap_list_subscribed
3.90. imap_login
3.91. imap_pass
3.92. imap_passive
3.93. imap_peek
3.94. imap_pipeline_depth
3.95. imap_servernoise
3.96. imap_user
3.97. implicit_autoview
3.98. include
3.99. include_onlyfirst
3.100. indent_string
3.101. index_format
3.102. ispell
3.103. keep_flagged
3.104. locale
3.105. mail_check
3.106. mailcap_path
3.107. mailcap_sanitize
3.108. header_cache
3.109. maildir_header_cache_verify
3.110. header_cache_pagesize
3.111. header_cache_compress
3.112. maildir_trash
3.113. mark_old
3.114. markers
3.115. mask
3.116. mbox
3.117. mbox_type
3.118. metoo
3.119. menu_context
3.120. menu_move_off
3.121. menu_scroll
3.122. meta_key
3.123. mh_purge
3.124. mh_seq_flagged
3.125. mh_seq_replied
3.126. mh_seq_unseen
3.127. mime_forward
3.128. mime_forward_decode
3.129. mime_forward_rest
3.130. mix_entry_format
3.131. mixmaster
3.132. move
3.133. message_cachedir
3.134. message_cache_clean
3.135. message_format
3.136. narrow_tree
3.137. net_inc
3.138. pager
3.139. pager_context
3.140. pager_format
3.141. pager_index_lines
3.142. pager_stop
3.143. crypt_autosign
3.144. crypt_autoencrypt
3.145. pgp_ignore_subkeys
3.146. crypt_replyencrypt
3.147. crypt_replysign
3.148. crypt_replysignencrypted
3.149. crypt_timestamp
3.150. pgp_use_gpg_agent
3.151. crypt_verify_sig
3.152. smime_is_default
3.153. smime_ask_cert_label
3.154. smime_decrypt_use_default_key
3.155. pgp_entry_format
3.156. pgp_good_sign
3.157. pgp_check_exit
3.158. pgp_long_ids
3.159. pgp_retainable_sigs
3.160. pgp_autoinline
3.161. pgp_replyinline
3.162. pgp_show_unusable
3.163. pgp_sign_as
3.164. pgp_strict_enc
3.165. pgp_timeout
3.166. pgp_sort_keys
3.167. pgp_mime_auto
3.168. pgp_auto_decode
3.169. pgp_decode_command
3.170. pgp_getkeys_command
3.171. pgp_verify_command
3.172. pgp_decrypt_command
3.173. pgp_clearsign_command
3.174. pgp_sign_command
3.175. pgp_encrypt_sign_command
3.176. pgp_encrypt_only_command
3.177. pgp_import_command
3.178. pgp_export_command
3.179. pgp_verify_key_command
3.180. pgp_list_secring_command
3.181. pgp_list_pubring_command
3.182. forward_decrypt
3.183. smime_timeout
3.184. smime_encrypt_with
3.185. smime_keys
3.186. smime_ca_location
3.187. smime_certificates
3.188. smime_decrypt_command
3.189. smime_verify_command
3.190. smime_verify_opaque_command
3.191. smime_sign_command
3.192. smime_sign_opaque_command
3.193. smime_encrypt_command
3.194. smime_pk7out_command
3.195. smime_get_cert_command
3.196. smime_get_signer_cert_command
3.197. smime_import_cert_command
3.198. smime_get_cert_email_command
3.199. smime_default_key
3.200. ssl_client_cert
3.201. ssl_force_tls
3.202. ssl_starttls
3.203. certificate_file
3.204. ssl_usesystemcerts
3.205. entropy_file
3.206. ssl_use_sslv2
3.207. ssl_use_sslv3
3.208. ssl_use_tlsv1
3.209. ssl_min_dh_prime_bits
3.210. ssl_ca_certificates_file
3.211. pipe_split
3.212. pipe_decode
3.213. pipe_sep
3.214. pop_authenticators
3.215. pop_auth_try_all
3.216. pop_checkinterval
3.217. pop_delete
3.218. pop_host
3.219. pop_last
3.220. pop_reconnect
3.221. pop_user
3.222. pop_pass
3.223. post_indent_string
3.224. postpone
3.225. postponed
3.226. preconnect
3.227. print
3.228. print_command
3.229. print_decode
3.230. print_split
3.231. prompt_after
3.232. query_command
3.233. query_format
3.234. quit
3.235. quote_regexp
3.236. read_inc
3.237. read_only
3.238. realname
3.239. recall
3.240. record
3.241. reply_regexp
3.242. reply_self
3.243. reply_to
3.244. resolve
3.245. reverse_alias
3.246. reverse_name
3.247. reverse_realname
3.248. rfc2047_parameters
3.249. save_address
3.250. save_empty
3.251. save_history
3.252. save_name
3.253. score
3.254. score_threshold_delete
3.255. score_threshold_flag
3.256. score_threshold_read
3.257. send_charset
3.258. sendmail
3.259. sendmail_wait
3.260. shell
3.261. sig_dashes
3.262. sig_on_top
3.263. signature
3.264. simple_search
3.265. smart_wrap
3.266. smileys
3.267. sleep_time
3.268. smtp_authenticators
3.269. smtp_pass
3.270. smtp_url
3.271. sort
3.272. sort_alias
3.273. sort_aux
3.274. sort_browser
3.275. sort_re
3.276. spam_separator
3.277. spoolfile
3.278. status_chars
3.279. status_format
3.280. status_on_top
3.281. strict_threads
3.282. suspend
3.283. text_flowed
3.284. thread_received
3.285. thorough_search
3.286. tilde
3.287. time_inc
3.288. timeout
3.289. tmpdir
3.290. to_chars
3.291. tunnel
3.292. use_8bitmime
3.293. use_domain
3.294. use_envelope_from
3.295. use_from
3.296. use_idn
3.297. use_ipv6
3.298. user_agent
3.299. visual
3.300. wait_key
3.301. weed
3.302. wrap
3.303. wrap_search
3.304. wrapmargin
3.305. write_inc
3.306. write_bcc
4. Functions
4.1. generic menu
4.2. index menu
4.3. pager menu
4.4. alias menu
4.5. query menu
4.6. attach menu
4.7. compose menu
4.8. postpone menu
4.9. browser menu
4.10. pgp menu
4.11. smime menu
4.12. mix menu
4.13. editor menu
1. Command line options

+As for regular expressions, a lower case string search pattern makes
+Mutt perform a case-insensitive search except for IMAP (because for IMAP
+Mutt performs server-side searches which don't support case-insensivity).
+
Chapter 9. Reference
Table of Contents
1. Command-Line Options
2. Configuration Commands
3. Configuration Variables
3.1. abort_nosubject
3.2. abort_unmodified
3.3. alias_file
3.4. alias_format
3.5. allow_8bit
3.6. allow_ansi
3.7. arrow_cursor
3.8. ascii_chars
3.9. askbcc
3.10. askcc
3.11. assumed_charset
3.12. attach_charset
3.13. attach_format
3.14. attach_sep
3.15. attach_split
3.16. attribution
3.17. auto_tag
3.18. autoedit
3.19. beep
3.20. beep_new
3.21. bounce
3.22. bounce_delivered
3.23. braille_friendly
3.24. certificate_file
3.25. charset
3.26. check_mbox_size
3.27. check_new
3.28. collapse_unread
3.29. compose_format
3.30. config_charset
3.31. confirmappend
3.32. confirmcreate
3.33. connect_timeout
3.34. content_type
3.35. copy
3.36. crypt_autoencrypt
3.37. crypt_autopgp
3.38. crypt_autosign
3.39. crypt_autosmime
3.40. crypt_replyencrypt
3.41. crypt_replysign
3.42. crypt_replysignencrypted
3.43. crypt_timestamp
3.44. crypt_use_gpgme
3.45. crypt_use_pka
3.46. crypt_verify_sig
3.47. date_format
3.48. default_hook
3.49. delete
3.50. delete_untag
3.51. digest_collapse
3.52. display_filter
3.53. dotlock_program
3.54. dsn_notify
3.55. dsn_return
3.56. duplicate_threads
3.57. edit_headers
3.58. editor
3.59. encode_from
3.60. entropy_file
3.61. envelope_from_address
3.62. escape
3.63. fast_reply
3.64. fcc_attach
3.65. fcc_clear
3.66. folder
3.67. folder_format
3.68. followup_to
3.69. force_name
3.70. forward_decode
3.71. forward_decrypt
3.72. forward_edit
3.73. forward_format
3.74. forward_quote
3.75. from
3.76. gecos_mask
3.77. hdrs
3.78. header
3.79. header_cache
3.80. header_cache_compress
3.81. header_cache_pagesize
3.82. help
3.83. hidden_host
3.84. hide_limited
3.85. hide_missing
3.86. hide_thread_subject
3.87. hide_top_limited
3.88. hide_top_missing
3.89. history
3.90. history_file
3.91. honor_disposition
3.92. honor_followup_to
3.93. hostname
3.94. ignore_linear_white_space
3.95. ignore_list_reply_to
3.96. imap_authenticators
3.97. imap_check_subscribed
3.98. imap_delim_chars
3.99. imap_headers
3.100. imap_idle
3.101. imap_keepalive
3.102. imap_list_subscribed
3.103. imap_login
3.104. imap_pass
3.105. imap_passive
3.106. imap_peek
3.107. imap_pipeline_depth
3.108. imap_servernoise
3.109. imap_user
3.110. implicit_autoview
3.111. include
3.112. include_onlyfirst
3.113. indent_string
3.114. index_format
3.115. ispell
3.116. keep_flagged
3.117. locale
3.118. mail_check
3.119. mailcap_path
3.120. mailcap_sanitize
3.121. maildir_header_cache_verify
3.122. maildir_trash
3.123. mark_old
3.124. markers
3.125. mask
3.126. mbox
3.127. mbox_type
3.128. menu_context
3.129. menu_move_off
3.130. menu_scroll
3.131. message_cache_clean
3.132. message_cachedir
3.133. message_format
3.134. meta_key
3.135. metoo
3.136. mh_purge
3.137. mh_seq_flagged
3.138. mh_seq_replied
3.139. mh_seq_unseen
3.140. mime_forward
3.141. mime_forward_decode
3.142. mime_forward_rest
3.143. mix_entry_format
3.144. mixmaster
3.145. move
3.146. narrow_tree
3.147. net_inc
3.148. pager
3.149. pager_context
3.150. pager_format
3.151. pager_index_lines
3.152. pager_stop
3.153. pgp_auto_decode
3.154. pgp_autoinline
3.155. pgp_check_exit
3.156. pgp_clearsign_command
3.157. pgp_decode_command
3.158. pgp_decrypt_command
3.159. pgp_encrypt_only_command
3.160. pgp_encrypt_sign_command
3.161. pgp_entry_format
3.162. pgp_export_command
3.163. pgp_getkeys_command
3.164. pgp_good_sign
3.165. pgp_ignore_subkeys
3.166. pgp_import_command
3.167. pgp_list_pubring_command
3.168. pgp_list_secring_command
3.169. pgp_long_ids
3.170. pgp_mime_auto
3.171. pgp_replyinline
3.172. pgp_retainable_sigs
3.173. pgp_show_unusable
3.174. pgp_sign_as
3.175. pgp_sign_command
3.176. pgp_sort_keys
3.177. pgp_strict_enc
3.178. pgp_timeout
3.179. pgp_use_gpg_agent
3.180. pgp_verify_command
3.181. pgp_verify_key_command
3.182. pipe_decode
3.183. pipe_sep
3.184. pipe_split
3.185. pop_auth_try_all
3.186. pop_authenticators
3.187. pop_checkinterval
3.188. pop_delete
3.189. pop_host
3.190. pop_last
3.191. pop_pass
3.192. pop_reconnect
3.193. pop_user
3.194. post_indent_string
3.195. postpone
3.196. postponed
3.197. preconnect
3.198. print
3.199. print_command
3.200. print_decode
3.201. print_split
3.202. prompt_after
3.203. query_command
3.204. query_format
3.205. quit
3.206. quote_regexp
3.207. read_inc
3.208. read_only
3.209. realname
3.210. recall
3.211. record
3.212. reply_regexp
3.213. reply_self
3.214. reply_to
3.215. resolve
3.216. reverse_alias
3.217. reverse_name
3.218. reverse_realname
3.219. rfc2047_parameters
3.220. save_address
3.221. save_empty
3.222. save_history
3.223. save_name
3.224. score
3.225. score_threshold_delete
3.226. score_threshold_flag
3.227. score_threshold_read
3.228. search_context
3.229. send_charset
3.230. sendmail
3.231. sendmail_wait
3.232. shell
3.233. sig_dashes
3.234. sig_on_top
3.235. signature
3.236. simple_search
3.237. sleep_time
3.238. smart_wrap
3.239. smileys
3.240. smime_ask_cert_label
3.241. smime_ca_location
3.242. smime_certificates
3.243. smime_decrypt_command
3.244. smime_decrypt_use_default_key
3.245. smime_default_key
3.246. smime_encrypt_command
3.247. smime_encrypt_with
3.248. smime_get_cert_command
3.249. smime_get_cert_email_command
3.250. smime_get_signer_cert_command
3.251. smime_import_cert_command
3.252. smime_is_default
3.253. smime_keys
3.254. smime_pk7out_command
3.255. smime_sign_command
3.256. smime_sign_opaque_command
3.257. smime_timeout
3.258. smime_verify_command
3.259. smime_verify_opaque_command
3.260. smtp_authenticators
3.261. smtp_pass
3.262. smtp_url
3.263. sort
3.264. sort_alias
3.265. sort_aux
3.266. sort_browser
3.267. sort_re
3.268. spam_separator
3.269. spoolfile
3.270. ssl_ca_certificates_file
3.271. ssl_client_cert
3.272. ssl_force_tls
3.273. ssl_min_dh_prime_bits
3.274. ssl_starttls
3.275. ssl_use_sslv2
3.276. ssl_use_sslv3
3.277. ssl_use_tlsv1
3.278. ssl_usesystemcerts
3.279. ssl_verify_dates
3.280. ssl_verify_host
3.281. status_chars
3.282. status_format
3.283. status_on_top
3.284. strict_threads
3.285. suspend
3.286. text_flowed
3.287. thorough_search
3.288. thread_received
3.289. tilde
3.290. time_inc
3.291. timeout
3.292. tmpdir
3.293. to_chars
3.294. tunnel
3.295. uncollapse_jump
3.296. use_8bitmime
3.297. use_domain
3.298. use_envelope_from
3.299. use_from
3.300. use_idn
3.301. use_ipv6
3.302. user_agent
3.303. visual
3.304. wait_key
3.305. weed
3.306. wrap
3.307. wrap_search
3.308. wrapmargin
3.309. write_bcc
3.310. write_inc
4. Functions
4.1. Generic Menu
4.2. Index Menu
4.3. Pager Menu
4.4. Alias Menu
4.5. Query Menu
4.6. Attach Menu
4.7. Compose Menu
4.8. Postpone Menu
4.9. Browser Menu
4.10. Pgp Menu
4.11. Smime Menu
4.12. Mix Menu
4.13. Editor Menu
1. Command-Line Options

 Running mutt with no arguments will make Mutt attempt to read your spool
 mailbox.  However, it is possible to read other mailboxes and
 to send messages from the command line as well.
-
Table 8.1. Command line options
OptionDescription
-Aexpand an alias
-aattach a file to a message
-bspecify a blind carbon-copy (BCC) address
-cspecify a carbon-copy (Cc) address
-Dprint the value of all mutt variables to stdout
-especify a config command to be run after initialization files are read
-fspecify a mailbox to load
-Fspecify an alternate file to read initialization commands
-hprint help on command line options
-Hspecify a draft file from which to read a header and body
-ispecify a file to include in a message composition
-mspecify a default mailbox type
-ndo not read the system Muttrc
-precall a postponed message
-Qquery a configuration variable
-Ropen mailbox in read-only mode
-sspecify a subject (enclose in quotes if it contains spaces)
-vshow version number and compile-time definitions
-xsimulate the mailx(1) compose mode
-yshow a menu containing the files specified by the mailboxes command
-zexit immediately if there are no messages in the mailbox
-Zopen the first folder with new message,exit immediately if none


+
Table 9.1. Command line options
OptionDescription
-Aexpand an alias
-aattach a file to a message
-bspecify a blind carbon-copy (BCC) address
-cspecify a carbon-copy (Cc) address
-Dprint the value of all Mutt variables to stdout
-especify a config command to be run after initialization files are read
-fspecify a mailbox to load
-Fspecify an alternate file to read initialization commands
-hprint help on command line options
-Hspecify a draft file from which to read a header and body
-ispecify a file to include in a message composition
-mspecify a default mailbox type
-ndo not read the system Muttrc
-precall a postponed message
-Qquery a configuration variable
-Ropen mailbox in read-only mode
-sspecify a subject (enclose in quotes if it contains spaces)
-vshow version number and compile-time definitions
-xsimulate the mailx(1) compose mode
-yshow a menu containing the files specified by the mailboxes command
-zexit immediately if there are no messages in the mailbox
-Zopen the first folder with new message, exit immediately if none


 To read messages in a mailbox
 
mutt  [-nz] [-F
 muttrc
@@ -3399,8 +3820,6 @@ To read messages in a mailbox
 To compose a new message
 
mutt  [-n] [-F
 muttrc
-] [-a
-file
 ] [-c
 address
 ] [-i
@@ -3408,34 +3827,36 @@ To compose a new message
 ] [-s
 subject
 ] [
-[
+-a
 file
-...]
-  -- 
+ [...]
+--
 ]  
 address
-  [
-address
-...]

+... 

 Mutt also supports a “batch” mode to send prepared messages.  Simply redirect
 input from the file you wish to send.  For example,
-

-mutt -s "data set for run #2" professor@bigschool.edu
-< ˜/run2.dat
-

-This command will send a message to “professor@bigschool.edu” with a subject
+
+mutt -s "data set for run #2" professor@bigschool.edu < ˜/run2.dat

+will send a message to <professor@bigschool.edu> with a subject
 of “data set for run #2”.  In the body of the message will be the contents
 of the file “˜/run2.dat”.
 

-All files passed with -a file will be attached as a MIME
-part to the message. To attach several files, use “--” to separate files and
-recipient addresses: mutt -a *.png -- some@one.org
-
2. Configuration Commands

-The following are the commands understood by mutt.
-
  • account-hook   
+All files passed with -a file will be attached as a MIME
+part to the message. To attach a single or several files, use “--” to separate files and
+recipient addresses:
+
    +mutt -a image.png -- some@one.org
    
+or
+
    +mutt -a *.png -- some@one.org
    Note
    
+The -a option must be last in the option list.
+
    2. Configuration Commands
    
+The following are the commands understood by Mutt:
+
    3. Configuration variables
    3.1. abort_nosubject
    Type: quadoption
    
+ }
3. Configuration Variables
3.1. abort_nosubject
Type: quadoption

 Default: ask-yes

 If set to yes, when composing messages and no subject is given
 at the subject prompt, composition will be aborted.  If set to
@@ -3746,22 +4185,22 @@ encoded in the character set specified by set or the current character set otherwise.
 

 Note: Mutt will not automatically source this file; you must
-explicitly use the “source” command for it to be executed in case
+explicitly use the “source” command for it to be executed in case
 this option points to a dedicated alias file.
 

 The default for this option is the currently used muttrc file, or
 “˜/.muttrc” if no user muttrc was found.
 
3.4. alias_format
Type: string

 Default: “%4n %2f %t %-10a   %r”

-Specifies the format of the data displayed for the “alias” menu.  The
+Specifies the format of the data displayed for the “alias” menu.  The
 following printf(3)-style sequences are available:
 
-
%a 
alias name
-
%f 
flags - currently, a “d” for an alias marked for deletion
-
%n 
index number
-
%r 
address which alias expands to
-
%t 
character which indicates if the alias is tagged for inclusion
-
3.5. allow_8bit
Type: boolean

+
%a alias name
+
%f flags - currently, a “d” for an alias marked for deletion
+
%n index number
+
%r address which alias expands to
+
%t character which indicates if the alias is tagged for inclusion
+
3.5. allow_8bit
Type: boolean

 Default: yes

 Controls whether 8-bit data is converted to 7-bit using either Quoted-
 Printable or Base64 encoding when sending mail.
@@ -3776,10 +4215,9 @@ message could include a line like
 
 
 [-- PGP output follows ...
-
 

 and give it the same color as your attachment color (see also
-$crypt_timestamp).
+$crypt_timestamp).
 
3.7. arrow_cursor
Type: boolean

 Default: no

 When set, an arrow (“->”) will be used to indicate the current entry
@@ -3812,20 +4250,21 @@ For example, Japanese users might prefer this:
 
 
 set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
 

 However, only the first content is valid for the message body.
 
3.12. attach_charset
Type: string

 Default: (empty)

 This variable is a colon-separated list of character encoding
-schemes for text file attachments.
+schemes for text file attachments. Mutt uses this setting to guess
+which encoding files being attached are encoded in to convert them to
+a proper character set given in $send_charset.
+

 If unset, the value of $charset will be used instead.
 For example, the following configuration would work for Japanese
 text handling:
 
 
 set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
 

 Note: for Japanese users, “iso-2022-*” must be put at the head
 of the value as shown above if included.
@@ -3834,28 +4273,28 @@ Default: “%u%D%I %t%4n %T%.40d%&g
 This variable describes the format of the “attachment” menu.  The
 following printf(3)-style sequences are understood:
 
-
%C  
charset
-
%c  
requires charset conversion (“n” or “c”)
-
%D  
deleted flag
-
%d  
description
-
%e  
MIME content-transfer-encoding
-
%f  
filename
-
%I  
disposition (“I” for inline, “A” for attachment)
-
%m  
major MIME type
-
%M  
MIME subtype
-
%n  
attachment number
-
%Q  
“Q”, if MIME part qualifies for attachment counting
-
%s  
size
-
%t  
tagged flag
-
%T  
graphic tree characters
-
%u  
unlink (=to delete) flag
-
%X  
number of qualifying MIME parts in this part and its children
+
%C  charset
+
%c  requires charset conversion (“n” or “c”)
+
%D  deleted flag
+
%d  description
+
%e  MIME content-transfer-encoding
+
%f  filename
+
%I  disposition (“I” for inline, “A” for attachment)
+
%m  major MIME type
+
%M  MIME subtype
+
%n  attachment number
+
%Q  “Q”, if MIME part qualifies for attachment counting
+
%s  size
+
%t  tagged flag
+
%T  graphic tree characters
+
%u  unlink (=to delete) flag
+
%X  number of qualifying MIME parts in this part and its children
 (please see the “attachments” section for possible speed effects)
-
%>X 
right justify the rest of the string and pad with character “X”
-
%|X 
pad to the end of the line with character “X”
-
%*X 
soft-fill with character “X” as pad
-

-For an explanation of “soft-fill”, see the $index_format documentation.
+
%>X right justify the rest of the string and pad with character “X”
+
%|X pad to the end of the line with character “X”
+
%*X soft-fill with character “X” as pad
+

+For an explanation of “soft-fill”, see the $index_format documentation.
 
3.14. attach_sep
Type: string

 Default: “\n”

 The separator to add between attachments when operating (saving,
@@ -3871,22 +4310,26 @@ Mutt will operate on the attachments one by one.
 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 printf(3)-like sequences see
-the section on $index_format.
-
3.17. autoedit
Type: boolean

+the section on $index_format.
+
3.17. auto_tag
Type: boolean

+Default: no

+When set, functions in the index menu which affect a message
+will be applied to all tagged messages (if there are any).  When
+unset, you must first use the <tag-prefix> function (bound to “;”
+by default) to make the next function apply to all tagged messages.
+
3.18. autoedit
Type: boolean

 Default: no

-When set along with $edit_headers, Mutt will skip the initial
+When set along with $edit_headers, Mutt will skip the initial
 send-menu (prompting for subject and recipients) and allow you to
 immediately begin editing the body of your
 message.  The send-menu may still be accessed once you have finished
 editing the body of your message.
 

-Also see $fast_reply.
-
3.18. auto_tag
Type: boolean

-Default: no

-When set, functions in the index menu which affect a message
-will be applied to all tagged messages (if there are any).  When
-unset, you must first use the <tag-prefix> function (bound to “;”
-by default) to make the next function apply to all tagged messages.
+Note: when this option is set, you cannot use send-hooks that depend
+on the recipients when composing a new (non-reply) message, as the initial
+list of recipients is empty.
+

+Also see $fast_reply.
 
3.19. beep
Type: boolean

 Default: yes

 When this variable is set, mutt will beep when an error occurs.
@@ -3912,30 +4355,46 @@ of the current line in menus, even when the unset, making it easier for blind persons using Braille displays to
 follow these menus.  The option is unset by default because many
 visual terminals don't permit making the cursor invisible.
-
3.24. check_mbox_size
Type: boolean

-Default: no

-When this variable is set, mutt will use file size attribute instead of
-access time when checking for new mail in mbox and mmdf folders.
+
3.24. certificate_file
Type: path

+Default: “˜/.mutt_certificates”

+This variable specifies the file where the certificates you trust
+are saved. When an unknown certificate is encountered, you are asked
+if you accept it or not. If you accept it, the certificate can also
+be saved in this file and further connections are automatically
+accepted.
 

-This variable is unset by default and should only be enabled when
-new mail detection for these folder types is unreliable or doesn't work.
+You can also manually add CA certificates in this file. Any server
+certificate that is signed with one of these CA certificates is
+also automatically accepted.
 

-Note that enabling this variable should happen before any “mailboxes”
-directives occur in configuration files regarding mbox or mmdf folders
-because mutt needs to determine the initial new mail status of such a
-mailbox by performing a fast mailbox scan when it is defined.
-Afterwards the new mail status is tracked by file size changes.
-
3.25. charset
Type: string

+Example:
+
+
+set certificate_file=~/.mutt/certificates
+
3.25. charset
Type: string

 Default: (empty)

 Character set your terminal uses to display and enter textual data.
-It is also the fallback for $send_charset.
+It is also the fallback for $send_charset.
 

 Upon startup Mutt tries to derive this value from environment variables
 such as $LC_CTYPE or $LANG.
 

 Note: It should only be set in case Mutt isn't abled to determine the
 character set used correctly.
-
3.26. check_new
Type: boolean

+
3.26. check_mbox_size
Type: boolean

+Default: no

+When this variable is set, mutt will use file size attribute instead of
+access time when checking for new mail in mbox and mmdf folders.
+

+This variable is unset by default and should only be enabled when
+new mail detection for these folder types is unreliable or doesn't work.
+

+Note that enabling this variable should happen before any “mailboxes”
+directives occur in configuration files regarding mbox or mmdf folders
+because mutt needs to determine the initial new mail status of such a
+mailbox by performing a fast mailbox scan when it is defined.
+Afterwards the new mail status is tracked by file size changes.
+
3.27. check_new
Type: boolean

 Default: yes

 Note: this option only affects maildir and MH style
 mailboxes.
@@ -3946,26 +4405,22 @@ take quite some time since it involves scanning the directory and
 checking each file to see if it has already been looked at.  If
 this variable is unset, no check for new mail is performed
 while the mailbox is open.
-
3.27. collapse_unread
Type: boolean

+
3.28. collapse_unread
Type: boolean

 Default: yes

 When unset, Mutt will not collapse a thread if it contains any
 unread messages.
-
3.28. uncollapse_jump
Type: boolean

-Default: no

-When set, Mutt will jump to the next unread message, if any,
-when the current thread is uncollapsed.
 
3.29. compose_format
Type: string

 Default: “-- Mutt: Compose  [Approx. msg size: %l   Atts: %a]%>-”

 Controls the format of the status line displayed in the “compose”
-menu.  This string is similar to $status_format, but has its own
+menu.  This string is similar to $status_format, but has its own
 set of printf(3)-like sequences:
 
-
%a 
total number of attachments
-
%h 
local hostname
-
%l 
approximate size (in bytes) of the current message
-
%v 
Mutt version string
-

-See the text describing the $status_format option for more
+
%a total number of attachments
+
%h local hostname
+
%l approximate size (in bytes) of the current message
+
%v Mutt version string
+

+See the text describing the $status_format option for more
 information on how to set $compose_format.
 
3.30. config_charset
Type: string

 Default: (empty)

@@ -3998,48 +4453,102 @@ Sets the default Content-Type for the body of newly composed messages.
 
3.35. copy
Type: quadoption

 Default: yes

 This variable controls whether or not copies of your outgoing messages
-will be saved for later references.  Also see $record,
-$save_name, $force_name and “fcc-hook”.
-
3.36. crypt_use_gpgme
Type: boolean

+will be saved for later references.  Also see $record,
+$save_name, $force_name and “fcc-hook”.
+
3.36. crypt_autoencrypt
Type: boolean

+Default: no

+Setting this variable will cause Mutt to always attempt to PGP
+encrypt outgoing messages.  This is probably only useful in
+connection to the “send-hook” command.  It can be overridden
+by use of the pgp menu, when encryption is not required or
+signing is requested as well.  If $smime_is_default is set,
+then OpenSSL is used instead to create S/MIME messages and
+settings can be overridden by use of the smime menu instead.
+(Crypto only)
+
3.37. crypt_autopgp
Type: boolean

+Default: yes

+This variable controls whether or not mutt may automatically enable
+PGP encryption/signing for messages.  See also $crypt_autoencrypt,
+$crypt_replyencrypt,
+$crypt_autosign, $crypt_replysign and $smime_is_default.
+
3.38. crypt_autosign
Type: boolean

+Default: no

+Setting this variable will cause Mutt to always attempt to
+cryptographically sign outgoing messages.  This can be overridden
+by use of the pgp menu, when signing is not required or
+encryption is requested as well. If $smime_is_default is set,
+then OpenSSL is used instead to create S/MIME messages and settings can
+be overridden by use of the smime menu instead of the pgp menu.
+(Crypto only)
+
3.39. crypt_autosmime
Type: boolean

+Default: yes

+This variable controls whether or not mutt may automatically enable
+S/MIME encryption/signing for messages. See also $crypt_autoencrypt,
+$crypt_replyencrypt,
+$crypt_autosign, $crypt_replysign and $smime_is_default.
+
3.40. crypt_replyencrypt
Type: boolean

+Default: yes

+If set, automatically PGP or OpenSSL encrypt replies to messages which are
+encrypted.
+(Crypto only)
+
3.41. crypt_replysign
Type: boolean

+Default: no

+If set, automatically PGP or OpenSSL sign replies to messages which are
+signed.
+

+Note: this does not work on messages that are encrypted
+and signed!
+(Crypto only)
+
3.42. crypt_replysignencrypted
Type: boolean

+Default: no

+If set, automatically PGP or OpenSSL sign replies to messages
+which are encrypted. This makes sense in combination with
+$crypt_replyencrypt, because it allows you to sign all
+messages which are automatically encrypted.  This works around
+the problem noted in $crypt_replysign, that mutt is not able
+to find out whether an encrypted message is also signed.
+(Crypto only)
+
3.43. crypt_timestamp
Type: boolean

+Default: yes

+If set, mutt will include a time stamp in the lines surrounding
+PGP or S/MIME output, so spoofing such lines is more difficult.
+If you are using colors to mark these lines, and rely on these,
+you may unset this setting.
+(Crypto only)
+
3.44. crypt_use_gpgme
Type: boolean

 Default: no

 This variable controls the use of the GPGME-enabled crypto backends.
 If it is set and Mutt was built with gpgme support, the gpgme code for
 S/MIME and PGP will be used instead of the classic code.  Note that
 you need to set this option in .muttrc; it won't have any effect when
 used interactively.
-
3.37. crypt_use_pka
Type: boolean

+
3.45. crypt_use_pka
Type: boolean

 Default: no

 Controls whether mutt uses PKA
 (see http://www.g10code.de/docs/pka-intro.de.pdf) during signature
 verification (only supported by the GPGME backend).
-
3.38. crypt_autopgp
Type: boolean

-Default: yes

-This variable controls whether or not mutt may automatically enable
-PGP encryption/signing for messages.  See also $crypt_autoencrypt,
-$crypt_replyencrypt,
-$crypt_autosign, $crypt_replysign and $smime_is_default.
-
3.39. crypt_autosmime
Type: boolean

+
3.46. crypt_verify_sig
Type: quadoption

 Default: yes

-This variable controls whether or not mutt may automatically enable
-S/MIME encryption/signing for messages. See also $crypt_autoencrypt,
-$crypt_replyencrypt,
-$crypt_autosign, $crypt_replysign and $smime_is_default.
-
3.40. date_format
Type: string

+If “yes”, always attempt to verify PGP or S/MIME signatures.
+If “ask-*”, ask whether or not to verify the signature.
+If \Fi“no”, never attempt to verify cryptographic signatures.
+(Crypto only)
+
3.47. date_format
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 $index_format.  This is passed to the strftime(3)
+sequence in $index_format.  This is passed to the strftime(3)
 function to process the date, see the man page for the proper syntax.
 

 Unless the first character in the string is a bang (“!”), the month
 and week day names are expanded according to the locale specified in
-the variable $locale. If the first character in the string is a
+the variable $locale. If the first character in the string is a
 bang, the bang is discarded, and the month and week day names in the
 rest of the string are expanded in the C locale (that is in US
 English).
-
3.41. default_hook
Type: string

+
3.48. default_hook
Type: string

 Default: “˜f %s !˜P | (˜P ˜C %s)”

-This variable controls how “message-hook”, “reply-hook”, “send-hook”,
-“send2-hook”, “save-hook”, and “fcc-hook” will
+This variable controls how “message-hook”, “reply-hook”, “send-hook”,
+“send2-hook”, “save-hook”, and “fcc-hook” will
 be interpreted if they are specified with only a simple regexp,
 instead of a matching pattern.  The hooks are expanded when they are
 declared, so a hook will be interpreted according to the value of this
@@ -4048,33 +4557,33 @@ variable at the time the hook is declared.
 The default value matches
 if the message is either from a user matching the regular expression
 given, or if it is from you (if the from address matches
-“alternates”) and is to or cc'ed to a user matching the given
+“alternates”) and is to or cc'ed to a user matching the given
 regular expression.
-
3.42. delete
Type: quadoption

+
3.49. delete
Type: quadoption

 Default: ask-yes

 Controls whether or not messages are really deleted when closing or
 synchronizing a mailbox.  If set to yes, messages marked for
 deleting will automatically be purged without prompting.  If set to
 no, messages marked for deletion will be kept in the mailbox.
-
3.43. delete_untag
Type: boolean

+
3.50. delete_untag
Type: boolean

 Default: yes

 If this option is set, mutt will untag messages when marking them
 for deletion.  This applies when you either explicitly delete a message,
 or when you save it to another folder.
-
3.44. digest_collapse
Type: boolean

+
3.51. digest_collapse
Type: boolean

 Default: yes

 If this option is set, mutt's received-attachments menu will not show the subparts of
 individual messages in a multipart/digest.  To see these subparts, press “v” on that menu.
-
3.45. display_filter
Type: path

+
3.52. display_filter
Type: path

 Default: (empty)

 When set, specifies a command used to filter messages.  When a message
-is viewed it is passed as standard input to $display_filter, and the
+is viewed it is passed as standard input to $display_filter, and the
 filtered message is read from the standard output.
-
3.46. dotlock_program
Type: path

+
3.53. dotlock_program
Type: path

 Default: “/usr/local/bin/mutt_dotlock”

 Contains the path of the mutt_dotlock(8) binary to be used by
 mutt.
-
3.47. dsn_notify
Type: string

+
3.54. dsn_notify
Type: string

 Default: (empty)

 This variable sets the request for when notification is returned.  The
 string consists of a comma separated list (no spaces!) of one or more
@@ -4087,14 +4596,13 @@ Example:
 
 
 set dsn_notify="failure,delay"
-
 

-Note: when using $sendmail for delivery, you should not enable
+Note: when using $sendmail for delivery, you should not enable
 this unless you are either using Sendmail 8.8.x or greater or a MTA
 providing a sendmail(1)-compatible interface supporting the -N option
 for DSN. For SMTP delivery, DSN support is autodetected so that it
 depends on the server whether DSN will be used or not.
-
3.48. dsn_return
Type: string

+
3.55. dsn_return
Type: string

 Default: (empty)

 This variable controls how much of your message is returned in DSN
 messages.  It may be set to either hdrs to return just the
@@ -4104,98 +4612,103 @@ Example:
 
 
 set dsn_return=hdrs
-
 

-Note: when using $sendmail for delivery, you should not enable
+Note: when using $sendmail for delivery, you should not enable
 this unless you are either using Sendmail 8.8.x or greater or a MTA
 providing a sendmail(1)-compatible interface supporting the -R option
 for DSN. For SMTP delivery, DSN support is autodetected so that it
 depends on the server whether DSN will be used or not.
-
3.49. duplicate_threads
Type: boolean

+
3.56. duplicate_threads
Type: boolean

 Default: yes

-This variable controls whether mutt, when $sort is set to threads, threads
+This variable controls whether mutt, when $sort is set to threads, threads
 messages with the same Message-Id together.  If it is set, it will indicate
 that it thinks they are duplicates of each other with an equals sign
 in the thread tree.
-
3.50. edit_headers
Type: boolean

+
3.57. edit_headers
Type: boolean

 Default: no

 This option allows you to edit the header of your outgoing messages
 along with the body of your message.
 

 Note that changes made to the References: and Date: headers are
 ignored for interoperability reasons.
-
3.51. editor
Type: path

+
3.58. editor
Type: path

 Default: (empty)

 This variable specifies which editor is used by mutt.
 It defaults to the value of the $VISUAL, or $EDITOR, environment
 variable, or to the string “vi” if neither of those are set.
-
3.52. encode_from
Type: boolean

+
3.59. encode_from
Type: boolean

 Default: no

 When set, mutt will quoted-printable encode messages when
 they contain the string “From ” (note the trailing space) in the beginning of a line.
 This is useful to avoid the tampering certain mail delivery and transport
 agents tend to do with messages (in order to prevent tools from
 misinterpreting the line as a mbox message separator).
-
3.53. envelope_from_address
Type: e-mail address

+
3.60. entropy_file
Type: path

+Default: (empty)

+The file which includes random data that is used to initialize SSL
+library functions.
+
3.61. envelope_from_address
Type: e-mail address

 Default: (empty)

 Manually sets the envelope sender for outgoing messages.
-This value is ignored if $use_envelope_from is unset.
-
3.54. escape
Type: string

+This value is ignored if $use_envelope_from is unset.
+
3.62. escape
Type: string

 Default: “˜”

 Escape character to use for functions in the builtin editor.
-
3.55. fast_reply
Type: boolean

+
3.63. fast_reply
Type: boolean

 Default: no

 When set, the initial prompt for recipients and subject are skipped
 when replying to messages, and the initial prompt for subject is
 skipped when forwarding messages.
 

-Note: this variable has no effect when the $autoedit
+Note: this variable has no effect when the $autoedit
 variable is set.
-
3.56. fcc_attach
Type: boolean

+
3.64. fcc_attach
Type: quadoption

 Default: yes

 This variable controls whether or not attachments on outgoing messages
 are saved along with the main body of your message.
-
3.57. fcc_clear
Type: boolean

+
3.65. fcc_clear
Type: boolean

 Default: no

 When this variable is set, FCCs will be stored unencrypted and
 unsigned, even when the actual message is encrypted and/or
 signed.
 (PGP only)
-
3.58. folder
Type: path

+
3.66. folder
Type: path

 Default: “˜/Mail”

 Specifies the default location of your mailboxes.  A “+” or “=” at the
 beginning of a pathname will be expanded to the value of this
 variable.  Note that if you change this variable (from the default)
 value you need to make sure that the assignment occurs before
 you use “+” or “=” for any other variables since expansion takes place
-when handling the “mailboxes” command.
-
3.59. folder_format
Type: string

+when handling the “mailboxes” command.
+
3.67. folder_format
Type: string

 Default: “%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f”

 This variable allows you to customize the file browser display to your
-personal taste.  This string is similar to $index_format, but has
+personal taste.  This string is similar to $index_format, but has
 its own set of printf(3)-like sequences:
 
-
%C  
current file number
-
%d  
date/time folder was last modified
-
%f  
filename
-
%F  
file permissions
-
%g  
group name (or numeric gid, if missing)
-
%l  
number of hard links
-
%N  
N if folder has new mail, blank otherwise
-
%s  
size in bytes
-
%t  
“*” if the file is tagged, blank otherwise
-
%u  
owner name (or numeric uid, if missing)
-
%>X 
right justify the rest of the string and pad with character “X”
-
%|X 
pad to the end of the line with character “X”
-
%*X 
soft-fill with character “X” as pad
-

-For an explanation of “soft-fill”, see the $index_format documentation.
-
3.60. followup_to
Type: boolean

+
%C  current file number
+
%d  date/time folder was last modified
+
%f  filename (“/” is appended to directory names,
+“@” to symbolic links and “*” to executable
+files)
+
%F  file permissions
+
%g  group name (or numeric gid, if missing)
+
%l  number of hard links
+
%N  N if folder has new mail, blank otherwise
+
%s  size in bytes
+
%t  “*” if the file is tagged, blank otherwise
+
%u  owner name (or numeric uid, if missing)
+
%>X right justify the rest of the string and pad with character “X”
+
%|X pad to the end of the line with character “X”
+
%*X soft-fill with character “X” as pad
+

+For an explanation of “soft-fill”, see the $index_format documentation.
+
3.68. followup_to
Type: boolean

 Default: yes

 Controls whether or not the “Mail-Followup-To:” header field is
 generated when sending mail.  When set, Mutt will generate this
 field when you are replying to a known mailing list, specified with
-the “subscribe” or “lists” commands.
+the “subscribe” or “lists” commands.
 

 This field has two purposes.  First, preventing you from
 receiving duplicate copies of replies to messages which you send
@@ -4209,41 +4722,48 @@ email address for unsubscribed lists.  Without this header, a
 group reply to your message sent to a subscribed list will be
 sent to both the list and your address, resulting in two copies
 of the same email for you.
-
3.61. force_name
Type: boolean

+
3.69. force_name
Type: boolean

 Default: no

-This variable is similar to $save_name, except that Mutt will
+This variable is similar to $save_name, except that Mutt will
 store a copy of your outgoing message by the username of the address
 you are sending to even if that mailbox does not exist.
 

-Also see the $record variable.
-
3.62. forward_decode
Type: boolean

+Also see the $record variable.
+
3.70. forward_decode
Type: boolean

 Default: yes

 Controls the decoding of complex MIME messages into text/plain when
 forwarding a message.  The message header is also RFC2047 decoded.
-This variable is only used, if $mime_forward is unset,
-otherwise $mime_forward_decode is used instead.
-
3.63. forward_edit
Type: quadoption

+This variable is only used, if $mime_forward is unset,
+otherwise $mime_forward_decode is used instead.
+
3.71. forward_decrypt
Type: boolean

+Default: yes

+Controls the handling of encrypted messages when forwarding a message.
+When set, the outer layer of encryption is stripped off.  This
+variable is only used if $mime_forward is set and
+$mime_forward_decode is unset.
+(PGP only)
+
3.72. forward_edit
Type: quadoption

 Default: yes

 This quadoption controls whether or not the user is automatically
 placed in the editor when forwarding messages.  For those who always want
 to forward with no modification, use a setting of “no”.
-
3.64. forward_format
Type: string

+
3.73. forward_format
Type: string

 Default: “[%a: %s]”

 This variable controls the default subject when forwarding a message.
-It uses the same format sequences as the $index_format variable.
-
3.65. forward_quote
Type: boolean

+It uses the same format sequences as the $index_format variable.
+
3.74. forward_quote
Type: boolean

 Default: no

 When set, forwarded messages included in the main body of the
-message (when $mime_forward is unset) will be quoted using
-$indent_string.
-
3.66. from
Type: e-mail address

+message (when $mime_forward is unset) will be quoted using
+$indent_string.
+
3.75. from
Type: e-mail address

 Default: (empty)

 When set, this variable contains a default from address.  It
-can be overridden using “my_hdr” (including from a “send-hook”) and
-$reverse_name.  This variable is ignored if $use_from is unset.
+can be overridden using “my_hdr” (including from a “send-hook”) and
+$reverse_name.  This variable is ignored if $use_from is unset.
 

 This setting defaults to the contents of the environment variable $EMAIL.
-
3.67. gecos_mask
Type: regular expression

+
3.76. gecos_mask
Type: regular expression

 Default: “^[^,]*”

 A regular expression used by mutt to parse the GECOS field of a password
 entry when expanding the alias.  The default value
@@ -4251,23 +4771,47 @@ will return the string up to the first “,” encoun
 If the GECOS field contains a string like “lastname, firstname” then you
 should set it to “.*”.
 

-This can be useful if you see the following behavior: you address a e-mail
+This can be useful if you see the following behavior: you address an e-mail
 to user ID “stevef” whose full name is “Steve Franklin”.  If mutt expands
-“stevef” to “"Franklin" stevef@foo.bar” then you should set the $gecos_mask to
+“stevef” to “"Franklin" stevef@foo.bar” then you should set the $gecos_mask to
 a regular expression that will match the whole name so mutt will expand
 “Franklin” to “Franklin, Steve”.
-
3.68. hdrs
Type: boolean

+
3.77. hdrs
Type: boolean

 Default: yes

-When unset, the header fields normally added by the “my_hdr”
+When unset, the header fields normally added by the “my_hdr”
 command are not created.  This variable must 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.
-
3.69. header
Type: boolean

+
3.78. header
Type: boolean

 Default: no

 When set, this variable causes Mutt to include the header
 of the message you are replying to into the edit buffer.
-The $weed setting applies.
-
3.70. help
Type: boolean

+The $weed setting applies.
+
3.79. header_cache
Type: path

+Default: (empty)

+This variable points to the header cache database.
+If pointing to a directory Mutt will contain a header cache
+database file per folder, if pointing to a file that file will
+be a single global header cache. By default it is unset so no header
+caching will be used.
+

+Header caching can greatly improve speed when opening POP, IMAP
+MH or Maildir folders, see “caching” for details.
+
3.80. header_cache_compress
Type: boolean

+Default: yes

+When mutt is compiled with qdbm or tokyocabinet as header cache backend,
+this option determines whether the database will be compressed.
+Compression results in database files roughly being one fifth
+of the usual diskspace, but the uncompression can result in a
+slower opening of cached folder(s) which in general is still
+much faster than opening non header cached folders.
+
3.81. header_cache_pagesize
Type: string

+Default: “16384”

+When mutt is compiled with either gdbm or bdb4 as the header cache backend,
+this option changes the database page size.  Too large or too small
+values can waste space, memory, or CPU time. The default should be more
+or less optimal for most use cases.
+
3.82. help
Type: boolean

 Default: yes

 When set, help lines describing the bindings for the major functions
 provided by each menu are displayed on the first line of the screen.
@@ -4277,48 +4821,57 @@ function is bound to a sequence rather than a single keystroke.  Also,
 the help line may not be updated if a binding is changed while Mutt is
 running.  Since this variable is primarily aimed at new users, neither
 of these should present a major problem.
-
3.71. hidden_host
Type: boolean

+
3.83. hidden_host
Type: boolean

 Default: no

-When set, mutt will skip the host name part of $hostname variable
+When set, mutt will skip the host name part of $hostname variable
 when adding the domain part to addresses.  This variable does not
 affect the generation of Message-IDs, and it will not lead to the
 cut-off of first-level domains.
-
3.72. hide_limited
Type: boolean

+
3.84. hide_limited
Type: boolean

 Default: no

 When set, mutt will not show the presence of messages that are hidden
 by limiting, in the thread tree.
-
3.73. hide_missing
Type: boolean

+
3.85. hide_missing
Type: boolean

 Default: yes

 When set, mutt will not show the presence of missing messages in the
 thread tree.
-
3.74. hide_thread_subject
Type: boolean

+
3.86. hide_thread_subject
Type: boolean

 Default: yes

 When set, mutt will not show the subject of messages in the thread
 tree that have the same subject as their parent or closest previously
 displayed sibling.
-
3.75. hide_top_limited
Type: boolean

+
3.87. hide_top_limited
Type: boolean

 Default: no

 When set, mutt will not show the presence of messages that are hidden
 by limiting, at the top of threads in the thread tree.  Note that when
-$hide_limited is set, this option will have no effect.
-
3.76. hide_top_missing
Type: boolean

+$hide_limited is set, this option will have no effect.
+
3.88. hide_top_missing
Type: boolean

 Default: yes

 When set, mutt will not show the presence of missing messages at the
-top of threads in the thread tree.  Note that when $hide_missing is
+top of threads in the thread tree.  Note that when $hide_missing is
 set, this option will have no effect.
-
3.77. history
Type: number

+
3.89. history
Type: number

 Default: 10

 This variable controls the size (in number of strings remembered) of
 the string history buffer per category. The buffer is cleared each time the
 variable is set.
-
3.78. history_file
Type: path

+
3.90. history_file
Type: path

 Default: “˜/.mutthistory”

 The file in which Mutt will save its history.
-
3.79. honor_followup_to
Type: quadoption

+
3.91. honor_disposition
Type: boolean

+Default: no

+When set, Mutt will not display attachments with a
+disposition of “attachment” inline even if it could
+render the part to plain text. These MIME parts can only
+be viewed from the attachment menu.
+

+If unset, Mutt will render all MIME parts it can
+properly transform to plain text.
+
3.92. honor_followup_to
Type: quadoption

 Default: yes

 This variable controls whether or not a Mail-Followup-To header is
 honored when group-replying to a message.
-
3.80. hostname
Type: string

+
3.93. hostname
Type: string

 Default: (empty)

 Specifies the fully-qualified hostname of the system mutt is running on
 containing the host's name and the DNS domain it belongs to. It is used
@@ -4327,30 +4880,30 @@ Message-Id headers.
 

 Its value is determined at startup as follows: If the node's name
 as returned by the uname(3) function contains the hostname and the
-domain, these are used to construct $hostname. If there is no
+domain, these are used to construct $hostname. If there is no
 domain part returned, Mutt will look for a “domain” or “search”
 line in /etc/resolv.conf to determine the domain. Optionally, Mutt
 can be compiled with a fixed domain name in which case a detected
 one is not used.
 

-Also see $use_domain and $hidden_host.
-
3.81. ignore_linear_white_space
Type: boolean

+Also see $use_domain and $hidden_host.
+
3.94. ignore_linear_white_space
Type: boolean

 Default: no

 This option replaces linear-white-space between encoded-word
 and text to a single space to prevent the display of MIME-encoded
 “Subject:” field from being divided into multiple lines.
-
3.82. ignore_list_reply_to
Type: boolean

+
3.95. ignore_list_reply_to
Type: boolean

 Default: no

 Affects the behaviour of the <reply> function when replying to
 messages from mailing lists (as defined by the “subscribe” or
-“lists” commands).  When set, if the “Reply-To:” field is
+“lists” commands).  When set, if the “Reply-To:” field is
 set to the same value as the “To:” field, Mutt assumes that the
 “Reply-To:” field was set by the mailing list to automate responses
 to the list, and will ignore this field.  To direct a response to the
 mailing list when this option is set, use the <list-reply>
 function; <group-reply> will reply to both the sender and the
 list.
-
3.83. imap_authenticators
Type: string

+
3.96. imap_authenticators
Type: string

 Default: (empty)

 This is a colon-delimited list of authentication methods mutt may
 attempt to use to log in to an IMAP server, in the order mutt should
@@ -4364,23 +4917,22 @@ Example:
 
 
 set imap_authenticators="gssapi:cram-md5:login"
-
 

 Note: Mutt will only fall back to other authentication methods if
 the previous methods are unavailable. If a method is available but
 authentication fails, mutt will not connect to the IMAP server.
-
3.84. imap_check_subscribed
Type: boolean

+
3.97. imap_check_subscribed
Type: boolean

 Default: no

 When set, mutt will fetch the set of subscribed folders from
 your server on connection, and add them to the set of mailboxes
-it polls for new mail just as if you had issued individual “mailboxes”
+it polls for new mail just as if you had issued individual “mailboxes”
 commands.
-
3.85. imap_delim_chars
Type: string

+
3.98. imap_delim_chars
Type: string

 Default: “/.”

 This contains the list of characters which you would like to treat
 as folder separators for displaying IMAP paths. In particular it
 helps in using the “=” shortcut for your folder variable.
-
3.86. imap_headers
Type: string

+
3.99. imap_headers
Type: string

 Default: (empty)

 Mutt requests these header fields in addition to the default headers
 (“Date:”, “From:”, “Subject:”, “To:”, “Cc:”, “Message-Id:”,
@@ -4392,14 +4944,14 @@ headers for spam detection.
 Note: This is a space separated list, items should be uppercase
 and not contain the colon, e.g. “X-BOGOSITY X-SPAM-STATUS” for the
 “X-Bogosity:” and “X-Spam-Status:” header fields.
-
3.87. imap_idle
Type: boolean

+
3.100. imap_idle
Type: boolean

 Default: no

 When set, mutt will attempt to use the IMAP IDLE extension
 to check for new mail in the current mailbox. Some servers
 (dovecot was the inspiration for this option) react badly
 to mutt's implementation. If your connection seems to freeze
 up periodically, try unsetting this.
-
3.88. imap_keepalive
Type: number

+
3.101. imap_keepalive
Type: number

 Default: 900

 This variable specifies the maximum amount of time in seconds that mutt
 will wait before polling open IMAP connections, to prevent the server
@@ -4408,39 +4960,39 @@ well within the RFC-specified minimum amount of time (30 minutes) before
 a server is allowed to do this, but in practice the RFC does get
 violated every now and then. Reduce this number if you find yourself
 getting disconnected from your IMAP server due to inactivity.
-
3.89. imap_list_subscribed
Type: boolean

+
3.102. imap_list_subscribed
Type: boolean

 Default: no

 This variable configures whether IMAP folder browsing will look for
 only subscribed folders or all folders.  This can be toggled in the
 IMAP browser with the <toggle-subscribed> function.
-
3.90. imap_login
Type: string

+
3.103. imap_login
Type: string

 Default: (empty)

 Your login name on the IMAP server.
 

-This variable defaults to the value of $imap_user.
-
3.91. imap_pass
Type: string

+This variable defaults to the value of $imap_user.
+
3.104. imap_pass
Type: string

 Default: (empty)

 Specifies the password for your IMAP account.  If unset, Mutt will
-prompt you for your password when you invoke the <fetch-mail> function
+prompt you for your password when you invoke the <imap-fetch-mail> function
 or try to open an IMAP folder.
 

 Warning: you should only use this option when you are on a
 fairly secure machine, because the superuser can read your muttrc even
 if you are the only one who can read the file.
-
3.92. imap_passive
Type: boolean

+
3.105. imap_passive
Type: boolean

 Default: yes

 When set, mutt will not open new IMAP connections to check for new
 mail.  Mutt will only check for new mail over existing IMAP
 connections.  This is useful if you don't want to be prompted to
 user/password pairs on mutt invocation, or if opening the connection
 is slow.
-
3.93. imap_peek
Type: boolean

+
3.106. imap_peek
Type: boolean

 Default: yes

 When set, mutt will avoid implicitly marking your mail as read whenever
 you fetch a message from the server. This is generally a good thing,
 but can make closing an IMAP folder somewhat slower. This option
 exists to appease speed freaks.
-
3.94. imap_pipeline_depth
Type: number

+
3.107. imap_pipeline_depth
Type: number

 Default: 15

 Controls the number of IMAP commands that may be queued up before they
 are sent to the server. A deeper pipeline reduces the amount of time
@@ -4449,47 +5001,46 @@ more responsive. But not all servers correctly handle pipelined commands,
 so if you have problems you might want to try setting this variable to 0.
 

 Note: Changes to this variable have no effect on open connections.
-
3.95. imap_servernoise
Type: boolean

+
3.108. imap_servernoise
Type: boolean

 Default: yes

 When set, mutt will display warning messages from the IMAP
 server as error messages. Since these messages are often
 harmless, or generated due to configuration problems on the
 server which are out of the users' hands, you may wish to suppress
 them at some point.
-
3.96. imap_user
Type: string

+
3.109. imap_user
Type: string

 Default: (empty)

 The name of the user whose mail you intend to access on the IMAP
 server.
 

 This variable defaults to your user name on the local machine.
-
3.97. implicit_autoview
Type: boolean

+
3.110. implicit_autoview
Type: boolean

 Default: no

 If set to “yes”, mutt will look for a mailcap entry with the
 “copiousoutput” flag set for every MIME attachment it doesn't have
 an internal viewer defined for.  If such an entry is found, mutt will
 use the viewer defined in that entry to convert the body part to text
 form.
-
3.98. include
Type: quadoption

+
3.111. include
Type: quadoption

 Default: ask-yes

 Controls whether or not a copy of the message(s) you are replying to
 is included in your reply.
-
3.99. include_onlyfirst
Type: boolean

+
3.112. include_onlyfirst
Type: boolean

 Default: no

 Controls whether or not Mutt includes only the first attachment
 of the message you are replying.
-
3.100. indent_string
Type: string

+
3.113. indent_string
Type: string

 Default: “> ”

 Specifies the string to prepend to each line of text quoted in a
 message to which you are replying.  You are strongly encouraged not to
 change this value, as it tends to agitate the more fanatical netizens.
 

-This option is a format string, please see the description of
-$index_format for supported printf(3)-style sequences.
+The value of this option is ignored if $text_flowed is set, too because
+the quoting mechanism is strictly defined for format=flowed.
 

-Because for format=lowed style messages the quoting mechanism
-is strictly defined, this setting is ignored if $text_flowed is
-set.
-
3.101. index_format
Type: string

+This option is a format string, please see the description of
+$index_format for supported printf(3)-style sequences.
+
3.114. index_format
Type: string

 Default: “%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s”

 This variable allows you to customize the message index display to
 your personal taste.
@@ -4498,63 +5049,63 @@ your personal taste.
 function printf(3) to format output (see the man page for more details).
 The following sequences are defined in Mutt:
 
-
%a 
address of the author
-
%A 
reply-to address (if present; otherwise: address of 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 converted to sender's time zone
-
%D 
date and time of the message in the format specified by
-$date_format converted to the local time zone
-
%e 
current message number in thread
-
%E 
number of messages in current thread
-
%f 
sender (address + real name), either From: or Return-Path:
-
%F 
author name, or recipient name if the message is from you
-
%H 
spam attribute(s) of this message
-
%i 
message-id of the current message
-
%l 
number of lines in the message (does not work with maildir,
+
%a address of the author
+
%A reply-to address (if present; otherwise: address of 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 converted to sender's time zone
+
%D date and time of the message in the format specified by
+$date_format converted to the local time zone
+
%e current message number in thread
+
%E number of messages in current thread
+
%f sender (address + real name), either From: or Return-Path:
+
%F author name, or recipient name if the message is from you
+
%H spam attribute(s) of this message
+
%i message-id of the current message
+
%l number of lines in the message (does not work with maildir,
 mh, and possibly IMAP folders)
-
%L 
If an address in the “To:” or “Cc:” header field matches an address
+
%L If an address in the “To:” or “Cc:” header field matches an address
 defined by the users “subscribe” command, this displays
 "To <list-name>", otherwise the same as %F.
-
%m 
total number of message in the mailbox
-
%M 
number of hidden messages if the thread is collapsed.
-
%N 
message score
-
%n 
author's real name (or address if missing)
-
%O 
original save folder where mutt would formerly have
+
%m total number of message in the mailbox
+
%M number of hidden messages if the thread is collapsed.
+
%N message score
+
%n author's real name (or address if missing)
+
%O original save folder where mutt would formerly have
 stashed the message: list name or recipient name
 if not sent to a list
-
%P 
progress indicator for the builtin pager (how much of the file has been displayed)
-
%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
-
%v 
first name of the author, or the recipient if the message is from you
-
%X 
number of attachments
+
%P progress indicator for the builtin pager (how much of the file has been displayed)
+
%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
+
%v first name of the author, or the recipient if the message is from you
+
%X number of attachments
 (please see the “attachments” section for possible speed effects)
-
%y 
“X-Label:” field, if present
-
%Y 
“X-Label:” field, if present, and (1) not at part of a thread tree,
+
%y “X-Label:” field, if present
+
%Y “X-Label:” field, if present, and (1) not at part of a thread tree,
 (2) at the top of a thread, or (3) “X-Label:” is different from
 preceding message's “X-Label:”.
-
%Z 
message status flags
-
%{fmt} 
the date and time of the message is converted to sender's
+
%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 library function
 strftime(3); a leading bang disables locales
-
%[fmt] 
the date and time of the message is converted to the local
+
%[fmt] the date and time of the message is converted to the local
 time zone, and “fmt” is expanded by the library function
 strftime(3); a leading bang disables locales
-
%(fmt) 
the local date and time when the message was received.
+
%(fmt) the local date and time when the message was received.
 “fmt” is expanded by the library function strftime(3);
 a leading bang disables locales
-
%<fmt> 
the current local time. “fmt” is expanded by the library
+
%<fmt> the current local time. “fmt” is expanded by the library
 function strftime(3); 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”
-
%*X    
soft-fill with character “X” as pad
-

+
%>X    right justify the rest of the string and pad with character “X”
+
%|X    pad to the end of the line with character “X”
+
%*X    soft-fill with character “X” as pad
+

 “Soft-fill” deserves some explanation: Normal right-justification
 will print everything to the left of the “%>”, displaying padding and
 whatever lies to the right only if there's room. By contrast,
@@ -4564,28 +5115,28 @@ necessary, soft-fill will eat text leftwards to make room for
 rightward text.
 

 Note that these expandos are supported in
-“save-hook”, “fcc-hook” and “fcc-save-hook”, too.
-
3.102. ispell
Type: path

+“save-hook”, “fcc-hook” and “fcc-save-hook”, too.
+
3.115. ispell
Type: path

 Default: “ispell”

 How to invoke ispell (GNU's spell-checking software).
-
3.103. keep_flagged
Type: boolean

+
3.116. keep_flagged
Type: boolean

 Default: no

 If set, read messages marked as flagged will not be moved
-from your spool mailbox to your $mbox mailbox, or as a result of
-a “mbox-hook” command.
-
3.104. locale
Type: string

+from your spool mailbox to your $mbox mailbox, or as a result of
+a “mbox-hook” command.
+
3.117. locale
Type: string

 Default: “C”

 The locale used by strftime(3) to format dates. Legal values are
 the strings your system accepts for the locale environment variable $LC_TIME.
-
3.105. mail_check
Type: number

+
3.118. mail_check
Type: number

 Default: 5

 This variable configures how often (in seconds) mutt should look for
-new mail. Also see the $timeout variable.
-
3.106. mailcap_path
Type: string

+new mail. Also see the $timeout variable.
+
3.119. mailcap_path
Type: string

 Default: (empty)

 This variable specifies which files to consult when attempting to
 display MIME bodies not directly supported by Mutt.
-
3.107. mailcap_sanitize
Type: boolean

+
3.120. mailcap_sanitize
Type: boolean

 Default: yes

 If set, mutt will restrict possible characters in mailcap % expandos
 to a well-defined set of safe characters.  This is the safe setting,
@@ -4593,90 +5144,85 @@ but we are not sure it doesn't break some more advanced MIME stuff.
 

 DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
 DOING!
-
3.108. header_cache
Type: path

-Default: (empty)

-This variable points to the header cache database.
-If pointing to a directory Mutt will contain a header cache
-database file per folder, if pointing to a file that file will
-be a single global header cache. By default it is unset so no header
-caching will be used.
-

-Header caching can greatly improve speed when opening POP, IMAP
-MH or Maildir folders, see “caching” for details.
-
3.109. maildir_header_cache_verify
Type: boolean

+
3.121. maildir_header_cache_verify
Type: boolean

 Default: yes

 Check for Maildir unaware programs other than mutt having modified maildir
 files when the header cache is in use.  This incurs one stat(2) per
 message every time the folder is opened (which can be very slow for NFS
 folders).
-
3.110. header_cache_pagesize
Type: string

-Default: “16384”

-When mutt is compiled with either gdbm or bdb4 as the header cache backend,
-this option changes the database page size.  Too large or too small
-values can waste space, memory, or CPU time. The default should be more
-or less optimal for most use cases.
-
3.111. header_cache_compress
Type: boolean

-Default: yes

-When mutt is compiled with qdbm or tokyocabinet as header cache backend,
-this option determines whether the database will be compressed.
-Compression results in database files roughly being one fifth
-of the usual diskspace, but the uncompression can result in a
-slower opening of cached folder(s) which in general is still
-much faster than opening non header cached folders.
-
3.112. maildir_trash
Type: boolean

+
3.122. maildir_trash
Type: boolean

 Default: no

 If set, messages marked as deleted will be saved with the maildir
 trashed flag instead of unlinked.  Note: this only applies
 to maildir-style mailboxes.  Setting it will have no effect on other
 mailbox types.
-
3.113. mark_old
Type: boolean

+
3.123. mark_old
Type: boolean

 Default: yes

 Controls whether or not mutt marks new unread
 messages as old if you exit a mailbox without reading them.
 With this option set, the next time you start mutt, the messages
 will show up with an “O” next to them in the index menu,
 indicating that they are old.
-
3.114. markers
Type: boolean

+
3.124. markers
Type: boolean

 Default: yes

 Controls the display of wrapped lines in the internal pager. If set, a
 “+” marker is displayed at the beginning of wrapped lines.
 

-Also see the $smart_wrap variable.
-
3.115. mask
Type: regular expression

+Also see the $smart_wrap variable.
+
3.125. mask
Type: regular expression

 Default: “!^\.[^.]”

 A regular expression used in the file browser, optionally preceded by
 the not operator “!”.  Only files whose names match this mask
 will be shown. The match is always case-sensitive.
-
3.116. mbox
Type: path

+
3.126. mbox
Type: path

 Default: “˜/mbox”

-This specifies the folder into which read mail in your $spoolfile
+This specifies the folder into which read mail in your $spoolfile
 folder will be appended.
 

-Also see the $move variable.
-
3.117. mbox_type
Type: folder magic

+Also see the $move variable.
+
3.127. mbox_type
Type: folder magic

 Default: mbox

 The default mailbox type used when creating new folders. May be any of
-“mbox”, “MMDF”, “MH” and “Maildir”.
-
3.118. metoo
Type: boolean

-Default: no

-If unset, Mutt will remove your address (see the “alternates”
-command) from the list of recipients when replying to a message.
-
3.119. menu_context
Type: number

+“mbox”, “MMDF”, “MH” and “Maildir”. This is overriden by the
+-m command-line option.
+
3.128. menu_context
Type: number

 Default: 0

 This variable controls the number of lines of context that are given
-when scrolling through menus. (Similar to $pager_context.)
-
3.120. menu_move_off
Type: boolean

+when scrolling through menus. (Similar to $pager_context.)
+
3.129. menu_move_off
Type: boolean

 Default: yes

 When unset, the bottom entry of menus will never scroll up past
 the bottom of the screen, unless there are less entries than lines.
 When set, the bottom entry may move off the bottom.
-
3.121. menu_scroll
Type: boolean

+
3.130. menu_scroll
Type: boolean

 Default: no

 When set, menus will be scrolled up or down one line when you
 attempt to move across a screen boundary.  If unset, the screen
 is cleared and the next or previous page of the menu is displayed
 (useful for slow links to avoid many redraws).
-
3.122. meta_key
Type: boolean

+
3.131. message_cache_clean
Type: boolean

+Default: no

+If set, mutt will clean out obsolete entries from the message cache when
+the mailbox is synchronized. You probably only want to set it
+every once in a while, since it can be a little slow
+(especially for large folders).
+
3.132. message_cachedir
Type: path

+Default: (empty)

+Set this to a directory and mutt will cache copies of messages from
+your IMAP and POP servers here. You are free to remove entries at any
+time.
+

+When setting this variable to a directory, mutt needs to fetch every
+remote message only once and can perform regular expression searches
+as fast as for local folders.
+

+Also see the $message_cache_clean variable.
+
3.133. message_format
Type: string

+Default: “%s”

+This is the string displayed in the “attachment” menu for
+attachments of type message/rfc822.  For a full listing of defined
+printf(3)-like sequences see the section on $index_format.
+
3.134. meta_key
Type: boolean

 Default: no

 If set, forces Mutt to interpret keystrokes with the high bit (bit 8)
 set as if the user had pressed the Esc key and whatever key remains
@@ -4685,7 +5231,11 @@ has an ASCII value of 0xf8, then this is treated as
 pressed Esc then “x”.  This is because the result of removing the
 high bit from 0xf8 is 0x78, which is the ASCII character
 “x”.
-
3.123. mh_purge
Type: boolean

+
3.135. metoo
Type: boolean

+Default: no

+If unset, Mutt will remove your address (see the “alternates”
+command) from the list of recipients when replying to a message.
+
3.136. mh_purge
Type: boolean

 Default: no

 When unset, mutt will mimic mh's behaviour and rename deleted messages
 to ,<old file name> in mh folders instead of really deleting
@@ -4693,17 +5243,17 @@ them. This leaves the message on disk but makes programs reading the folder
 ignore it. If the variable is set, the message files will simply be
 deleted.
 

-This option is similar to $maildir_trash for Maildir folders.
-
3.124. mh_seq_flagged
Type: string

+This option is similar to $maildir_trash for Maildir folders.
+
3.137. mh_seq_flagged
Type: string

 Default: “flagged”

 The name of the MH sequence used for flagged messages.
-
3.125. mh_seq_replied
Type: string

+
3.138. mh_seq_replied
Type: string

 Default: “replied”

 The name of the MH sequence used to tag replied messages.
-
3.126. mh_seq_unseen
Type: string

+
3.139. mh_seq_unseen
Type: string

 Default: “unseen”

 The name of the MH sequence used for unseen messages.
-
3.127. mime_forward
Type: quadoption

+
3.140. mime_forward
Type: quadoption

 Default: no

 When set, the message you are forwarding will be attached as a
 separate message/rfc822 MIME part instead of included in the main body of the
@@ -4712,72 +5262,50 @@ can properly view the message as it was delivered to you. If you like
 to switch between MIME and not MIME from mail to mail, set this
 variable to “ask-no” or “ask-yes”.
 

-Also see $forward_decode and $mime_forward_decode.
-
3.128. mime_forward_decode
Type: boolean

+Also see $forward_decode and $mime_forward_decode.
+
3.141. mime_forward_decode
Type: boolean

 Default: no

 Controls the decoding of complex MIME messages into text/plain when
-forwarding a message while $mime_forward is set. Otherwise
-$forward_decode is used instead.
-
3.129. mime_forward_rest
Type: quadoption

+forwarding a message while $mime_forward is set. Otherwise
+$forward_decode is used instead.
+
3.142. mime_forward_rest
Type: quadoption

 Default: yes

 When forwarding multiple attachments of a MIME message from the attachment
 menu, attachments which cannot be decoded in a reasonable manner will
 be attached to the newly composed message if this option is set.
-
3.130. mix_entry_format
Type: string

+
3.143. mix_entry_format
Type: string

 Default: “%4n %c %-16s %a”

 This variable describes the format of a remailer line on the mixmaster
 chain selection screen.  The following printf(3)-like sequences are
 supported:
 
-
%n 
The running number on the menu.
-
%c 
Remailer capabilities.
-
%s 
The remailer's short name.
-
%a 
The remailer's e-mail address.
-
3.131. mixmaster
Type: path

+
%n The running number on the menu.
+
%c Remailer capabilities.
+
%s The remailer's short name.
+
%a The remailer's e-mail address.
+
3.144. mixmaster
Type: path

 Default: “mixmaster”

 This variable contains the path to the Mixmaster binary on your
 system.  It is used with various sets of parameters to gather the
 list of known remailers, and to finally send a message through the
 mixmaster chain.
-
3.132. move
Type: quadoption

+
3.145. move
Type: quadoption

 Default: no

 Controls whether or not Mutt will move read messages
-from your spool mailbox to your $mbox mailbox, or as a result of
-a “mbox-hook” command.
-
3.133. message_cachedir
Type: path

-Default: (empty)

-Set this to a directory and mutt will cache copies of messages from
-your IMAP and POP servers here. You are free to remove entries at any
-time.
-

-When setting this variable to a directory, mutt needs to fetch every
-remote message only once and can perform regular expression searches
-as fast as for local folders.
-

-Also see the $message_cache_clean variable.
-
3.134. message_cache_clean
Type: boolean

-Default: no

-If set, mutt will clean out obsolete entries from the message cache when
-the mailbox is synchronized. You probably only want to set it
-every once in a while, since it can be a little slow
-(especially for large folders).
-
3.135. message_format
Type: string

-Default: “%s”

-This is the string displayed in the “attachment” menu for
-attachments of type message/rfc822.  For a full listing of defined
-printf(3)-like sequences see the section on $index_format.
-
3.136. narrow_tree
Type: boolean

+from your spool mailbox to your $mbox mailbox, or as a result of
+a “mbox-hook” command.
+
3.146. narrow_tree
Type: boolean

 Default: no

 This variable, when set, makes the thread tree narrower, allowing
 deeper threads to fit on the screen.
-
3.137. net_inc
Type: number

+
3.147. net_inc
Type: number

 Default: 10

 Operations that expect to transfer a large amount of data over the
-network will update their progress every $net_inc kilobytes.
+network will update their progress every $net_inc kilobytes.
 If set to 0, no progress messages will be displayed.
 

-See also $read_inc, $write_inc and $net_inc.
-
3.138. pager
Type: path

+See also $read_inc, $write_inc and $net_inc.
+
3.148. pager
Type: path

 Default: “builtin”

 This variable specifies which pager you would like to use to view
 messages. The value “builtin” means to use the builtin pager, otherwise this
@@ -4788,19 +5316,23 @@ Using an external pager may have some disadvantages: Additional
 keystrokes are necessary because you can't call mutt functions
 directly from the pager, and screen resizes cause lines longer than
 the screen width to be badly formatted in the help menu.
-
3.139. pager_context
Type: number

+
3.149. pager_context
Type: number

 Default: 0

 This variable controls the number of lines of context that are given
 when displaying the next or previous page in the internal pager.  By
 default, Mutt will display the line after the last one on the screen
 at the top of the next page (0 lines of context).
-
3.140. pager_format
Type: string

+

+This variable also specifies the amount of context given for search
+results. If positive, this many lines will be given before a match,
+if 0, the match will be top-aligned.
+
3.150. pager_format
Type: string

 Default: “-%Z- %C/%m: %-20.20n   %s%*  -- (%P)”

 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 $index_format
+pager.  The valid sequences are listed in the $index_format
 section.
-
3.141. pager_index_lines
Type: number

+
3.151. pager_index_lines
Type: number

 Default: 0

 Determines the number of lines of a mini-index which is shown when in
 the pager.  The current message, unless near the top or bottom of the
@@ -4811,593 +5343,305 @@ remain to be read in the current thread.  One of the lines is reserved
 for the status bar from the index, so a setting of 6
 will only show 5 lines of the actual index.  A value of 0 results in
 no index being shown.  If the number of messages in the current folder
-is less than $pager_index_lines, then the index will only use as
+is less than $pager_index_lines, then the index will only use as
 many lines as it needs.
-
3.142. pager_stop
Type: boolean

+
3.152. pager_stop
Type: boolean

 Default: no

 When set, the internal-pager will not move to the next message
 when you are at the end of a message and invoke the <next-page>
 function.
-
3.143. crypt_autosign
Type: boolean

+
3.153. pgp_auto_decode
Type: boolean

 Default: no

-Setting this variable will cause Mutt to always attempt to
-cryptographically sign outgoing messages.  This can be overridden
-by use of the pgp menu, when signing is not required or
-encryption is requested as well. If $smime_is_default is set,
-then OpenSSL is used instead to create S/MIME messages and settings can
-be overridden by use of the smime menu instead of the pgp menu.
-(Crypto only)
-
3.144. crypt_autoencrypt
Type: boolean

+If set, mutt will automatically attempt to decrypt traditional PGP
+messages whenever the user performs an operation which ordinarily would
+result in the contents of the message being operated on.  For example,
+if the user displays a pgp-traditional message which has not been manually
+checked with the <check-traditional-pgp> function, mutt will automatically
+check the message for traditional pgp.
+
3.154. pgp_autoinline
Type: boolean

 Default: no

-Setting this variable will cause Mutt to always attempt to PGP
-encrypt outgoing messages.  This is probably only useful in
-connection to the “send-hook” command.  It can be overridden
-by use of the pgp menu, when encryption is not required or
-signing is requested as well.  If $smime_is_default is set,
-then OpenSSL is used instead to create S/MIME messages and
-settings can be overridden by use of the smime menu instead.
-(Crypto only)
-
3.145. pgp_ignore_subkeys
Type: boolean

-Default: yes

-Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead,
-the principal key will inherit the subkeys' capabilities.  Unset this
-if you want to play interesting key selection games.
+This option controls whether Mutt generates old-style inline
+(traditional) PGP encrypted or signed messages under certain
+circumstances.  This can be overridden by use of the pgp menu,
+when inline is not required.
+

+Note that Mutt might automatically use PGP/MIME for messages
+which consist of more than a single MIME part.  Mutt can be
+configured to ask before sending PGP/MIME messages when inline
+(traditional) would not work.
+

+Also see the $pgp_mime_auto variable.
+

+Also note that using the old-style PGP message format is strongly
+deprecated.
 (PGP only)
-
3.146. crypt_replyencrypt
Type: boolean

+
3.155. pgp_check_exit
Type: boolean

 Default: yes

-If set, automatically PGP or OpenSSL encrypt replies to messages which are
-encrypted.
-(Crypto only)
-
3.147. crypt_replysign
Type: boolean

-Default: no

-If set, automatically PGP or OpenSSL sign replies to messages which are
-signed.
+If set, mutt will check the exit code of the PGP subprocess when
+signing or encrypting.  A non-zero exit code means that the
+subprocess failed.
+(PGP only)
+
3.156. pgp_clearsign_command
Type: string

+Default: (empty)

+This format is used to create an old-style “clearsigned” PGP
+message.  Note that the use of this format is strongly
+deprecated.
 

-Note: this does not work on messages that are encrypted
-and signed!
-(Crypto only)
-
3.148. crypt_replysignencrypted
Type: boolean

-Default: no

-If set, automatically PGP or OpenSSL sign replies to messages
-which are encrypted. This makes sense in combination with
-$crypt_replyencrypt, because it allows you to sign all
-messages which are automatically encrypted.  This works around
-the problem noted in $crypt_replysign, that mutt is not able
-to find out whether an encrypted message is also signed.
-(Crypto only)
-
3.149. crypt_timestamp
Type: boolean

-Default: yes

-If set, mutt will include a time stamp in the lines surrounding
-PGP or S/MIME output, so spoofing such lines is more difficult.
-If you are using colors to mark these lines, and rely on these,
-you may unset this setting.
-(Crypto only)
-
3.150. pgp_use_gpg_agent
Type: boolean

-Default: no

-If set, mutt will use a possibly-running gpg-agent(1) process.
+This is a format string, see the $pgp_decode_command command for
+possible printf(3)-like sequences.
 (PGP only)
-
3.151. crypt_verify_sig
Type: quadoption

-Default: yes

-If “yes”, always attempt to verify PGP or S/MIME signatures.
-If “ask-*”, ask whether or not to verify the signature.
-If \Fi“no”, never attempt to verify cryptographic signatures.
-(Crypto only)
-
3.152. smime_is_default
Type: boolean

-Default: no

-The default behaviour of mutt is to use PGP on all auto-sign/encryption
-operations. To override and to use OpenSSL instead this must be set.
-However, this has no effect while replying, since mutt will automatically
-select the same application that was used to sign/encrypt the original
-message.  (Note that this variable can be overridden by unsetting $crypt_autosmime.)
-(S/MIME only)
-
3.153. smime_ask_cert_label
Type: boolean

-Default: yes

-This flag controls whether you want to be asked to enter a label
-for a certificate about to be added to the database or not. It is
-set by default.
-(S/MIME only)
-
3.154. smime_decrypt_use_default_key
Type: boolean

-Default: yes

-If set (default) this tells mutt to use the default key for decryption. Otherwise,
-if managing multiple certificate-key-pairs, mutt will try to use the mailbox-address
-to determine the key to use. It will ask you to supply a key, if it can't find one.
-(S/MIME only)
-
3.155. pgp_entry_format
Type: string

-Default: “%4n %t%f %4l/0x%k %-4a %2c %u”

-This variable allows you to customize the PGP key selection menu to
-your personal taste. This string is similar to $index_format, but
-has its own set of printf(3)-like sequences:
-
-
%n     
number
-
%k     
key id
-
%u     
user id
-
%a     
algorithm
-
%l     
key length
-
%f     
flags
-
%c     
capabilities
-
%t     
trust/validity of the key-uid association
-
%[<s>] 
date of the key where <s> is an strftime(3) expression
-

-(PGP only)
-
3.156. pgp_good_sign
Type: regular expression

-Default: (empty)

-If you assign a text to this variable, then a PGP signature is only
-considered verified if the output from $pgp_verify_command contains
-the text. Use this variable if the exit code from the command is 0
-even for bad signatures.
-(PGP only)
-
3.157. pgp_check_exit
Type: boolean

-Default: yes

-If set, mutt will check the exit code of the PGP subprocess when
-signing or encrypting.  A non-zero exit code means that the
-subprocess failed.
-(PGP only)
-
3.158. pgp_long_ids
Type: boolean

-Default: no

-If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs.
-(PGP only)
-
3.159. pgp_retainable_sigs
Type: boolean

-Default: no

-If set, signed and encrypted messages will consist of nested
-multipart/signed and multipart/encrypted body parts.
-

-This is useful for applications like encrypted and signed mailing
-lists, where the outer layer (multipart/encrypted) can be easily
-removed, while the inner multipart/signed part is retained.
-(PGP only)
-
3.160. pgp_autoinline
Type: boolean

-Default: no

-This option controls whether Mutt generates old-style inline
-(traditional) PGP encrypted or signed messages under certain
-circumstances.  This can be overridden by use of the pgp menu,
-when inline is not required.
-

-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part.  Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-

-Also see the $pgp_mime_auto variable.
-

-Also note that using the old-style PGP message format is strongly
-deprecated.
-(PGP only)
-
3.161. pgp_replyinline
Type: boolean

-Default: no

-Setting this variable will cause Mutt to always attempt to
-create an inline (traditional) message when replying to a
-message which is PGP encrypted/signed inline.  This can be
-overridden by use of the pgp menu, when inline is not
-required.  This option does not automatically detect if the
-(replied-to) message is inline; instead it relies on Mutt
-internals for previously checked/flagged messages.
-

-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part.  Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-

-Also see the $pgp_mime_auto variable.
-

-Also note that using the old-style PGP message format is strongly
-deprecated.
-(PGP only)
-
3.162. pgp_show_unusable
Type: boolean

-Default: yes

-If set, mutt will display non-usable keys on the PGP key selection
-menu.  This includes keys which have been revoked, have expired, or
-have been marked as “disabled” by the user.
-(PGP only)
-
3.163. pgp_sign_as
Type: string

-Default: (empty)

-If you have more than one key pair, this option allows you to specify
-which of your private keys to use.  It is recommended that you use the
-keyid form to specify your key (e.g. 0x00112233).
-(PGP only)
-
3.164. pgp_strict_enc
Type: boolean

-Default: yes

-If set, Mutt will automatically encode PGP/MIME signed messages as
-quoted-printable.  Please note that unsetting this variable may
-lead to problems with non-verifyable PGP signatures, so only change
-this if you know what you are doing.
-(PGP only)
-
3.165. pgp_timeout
Type: number

-Default: 300

-The number of seconds after which a cached passphrase will expire if
-not used.
-(PGP only)
-
3.166. pgp_sort_keys
Type: sort order

-Default: address

-Specifies how the entries in the pgp menu are sorted. The
-following are legal values:
-
-
address 
sort alphabetically by user id
-
keyid   
sort alphabetically by key id
-
date    
sort by key creation date
-
trust   
sort by the trust of the key
-

-If you prefer reverse order of the above values, prefix it with
-“reverse-”.
-(PGP only)
-
3.167. pgp_mime_auto
Type: quadoption

-Default: ask-yes

-This option controls whether Mutt will prompt you for
-automatically sending a (signed/encrypted) message using
-PGP/MIME when inline (traditional) fails (for any reason).
-

-Also note that using the old-style PGP message format is strongly
-deprecated.
-(PGP only)
-
3.168. pgp_auto_decode
Type: boolean

-Default: no

-If set, mutt will automatically attempt to decrypt traditional PGP
-messages whenever the user performs an operation which ordinarily would
-result in the contents of the message being operated on.  For example,
-if the user displays a pgp-traditional message which has not been manually
-checked with the <check-traditional-pgp> function, mutt will automatically
-check the message for traditional pgp.
-
3.169. pgp_decode_command
Type: string

+
3.157. pgp_decode_command
Type: string

 Default: (empty)

 This format strings specifies a command which is used to decode
 application/pgp attachments.
 

 The PGP command formats have their own set of printf(3)-like sequences:
 
-
%p 
Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
+
%p Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
 string otherwise. Note: This may be used with a %? construct.
-
%f 
Expands to the name of a file containing a message.
-
%s 
Expands to the name of a file containing the signature part
+
%f Expands to the name of a file containing a message.
+
%s Expands to the name of a file containing the signature part
            of a multipart/signed attachment when verifying it.
-
%a 
The value of $pgp_sign_as.
-
%r 
One or more key IDs.
-

+
%a The value of $pgp_sign_as.
+
%r One or more key IDs.
+

 For examples on how to configure these formats for the various versions
 of PGP which are floating around, see the pgp and gpg sample configuration files in
 the samples/ subdirectory which has been installed on your system
 alongside the documentation.
 (PGP only)
-
3.170. pgp_getkeys_command
Type: string

-Default: (empty)

-This command is invoked whenever mutt will need public key information.
-Of the sequences supported by $pgp_decode_command, %r is the only
-printf(3)-like sequence used with this format.
-(PGP only)
-
3.171. pgp_verify_command
Type: string

-Default: (empty)

-This command is used to verify PGP signatures.
-

-This is a format string, see the $pgp_decode_command command for
-possible printf(3)-like sequences.
-(PGP only)
-
3.172. pgp_decrypt_command
Type: string

+
3.158. pgp_decrypt_command
Type: string

 Default: (empty)

 This command is used to decrypt a PGP encrypted message.
 

-This is a format string, see the $pgp_decode_command command for
-possible printf(3)-like sequences.
-(PGP only)
-
3.173. pgp_clearsign_command
Type: string

-Default: (empty)

-This format is used to create a old-style “clearsigned” PGP
-message.  Note that the use of this format is strongly
-deprecated.
-

-This is a format string, see the $pgp_decode_command command for
+This is a format string, see the $pgp_decode_command command for
 possible printf(3)-like sequences.
 (PGP only)
-
3.174. pgp_sign_command
Type: string

+
3.159. pgp_encrypt_only_command
Type: string

 Default: (empty)

-This command is used to create the detached PGP signature for a
-multipart/signed PGP/MIME body part.
+This command is used to encrypt a body part without signing it.
 

-This is a format string, see the $pgp_decode_command command for
+This is a format string, see the $pgp_decode_command command for
 possible printf(3)-like sequences.
 (PGP only)
-
3.175. pgp_encrypt_sign_command
Type: string

+
3.160. pgp_encrypt_sign_command
Type: string

 Default: (empty)

 This command is used to both sign and encrypt a body part.
 

-This is a format string, see the $pgp_decode_command command for
+This is a format string, see the $pgp_decode_command command for
 possible printf(3)-like sequences.
 (PGP only)
-
3.176. pgp_encrypt_only_command
Type: string

+
3.161. pgp_entry_format
Type: string

+Default: “%4n %t%f %4l/0x%k %-4a %2c %u”

+This variable allows you to customize the PGP key selection menu to
+your personal taste. This string is similar to $index_format, but
+has its own set of printf(3)-like sequences:
+
+
%n     number
+
%k     key id
+
%u     user id
+
%a     algorithm
+
%l     key length
+
%f     flags
+
%c     capabilities
+
%t     trust/validity of the key-uid association
+
%[<s>] date of the key where <s> is an strftime(3) expression
+

+(PGP only)
+
3.162. pgp_export_command
Type: string

 Default: (empty)

-This command is used to encrypt a body part without signing it.
+This command is used to export a public key from the user's
+key ring.
 

-This is a format string, see the $pgp_decode_command command for
+This is a format string, see the $pgp_decode_command command for
 possible printf(3)-like sequences.
 (PGP only)
-
3.177. pgp_import_command
Type: string

+
3.163. pgp_getkeys_command
Type: string

 Default: (empty)

-This command is used to import a key from a message into
-the user's public key ring.
-

-This is a format string, see the $pgp_decode_command command for
-possible printf(3)-like sequences.
+This command is invoked whenever mutt will need public key information.
+Of the sequences supported by $pgp_decode_command, %r is the only
+printf(3)-like sequence used with this format.
 (PGP only)
-
3.178. pgp_export_command
Type: string

+
3.164. pgp_good_sign
Type: regular expression

 Default: (empty)

-This command is used to export a public key from the user's
-key ring.
-

-This is a format string, see the $pgp_decode_command command for
-possible printf(3)-like sequences.
+If you assign a text to this variable, then a PGP signature is only
+considered verified if the output from $pgp_verify_command contains
+the text. Use this variable if the exit code from the command is 0
+even for bad signatures.
 (PGP only)
-
3.179. pgp_verify_key_command
Type: string

+
3.165. pgp_ignore_subkeys
Type: boolean

+Default: yes

+Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead,
+the principal key will inherit the subkeys' capabilities.  Unset this
+if you want to play interesting key selection games.
+(PGP only)
+
3.166. pgp_import_command
Type: string

 Default: (empty)

-This command is used to verify key information from the key selection
-menu.
+This command is used to import a key from a message into
+the user's public key ring.
 

-This is a format string, see the $pgp_decode_command command for
+This is a format string, see the $pgp_decode_command command for
 possible printf(3)-like sequences.
 (PGP only)
-
3.180. pgp_list_secring_command
Type: string

+
3.167. pgp_list_pubring_command
Type: string

 Default: (empty)

-This command is used to list the secret key ring's contents.  The
-output format must be analogous to the one used by:
+This command is used to list the public key ring's contents.  The
+output format must be analogous to the one used by
 
 
 gpg --list-keys --with-colons.
-
 

 This format is also generated by the pgpring utility which comes
 with mutt.
 

-This is a format string, see the $pgp_decode_command command for
+This is a format string, see the $pgp_decode_command command for
 possible printf(3)-like sequences.
 (PGP only)
-
3.181. pgp_list_pubring_command
Type: string

+
3.168. pgp_list_secring_command
Type: string

 Default: (empty)

-This command is used to list the public key ring's contents.  The
-output format must be analogous to the one used by
+This command is used to list the secret key ring's contents.  The
+output format must be analogous to the one used by:
 
 
 gpg --list-keys --with-colons.
-
 

 This format is also generated by the pgpring utility which comes
 with mutt.
 

-This is a format string, see the $pgp_decode_command command for
+This is a format string, see the $pgp_decode_command command for
 possible printf(3)-like sequences.
 (PGP only)
-
3.182. forward_decrypt
Type: boolean

-Default: yes

-Controls the handling of encrypted messages when forwarding a message.
-When set, the outer layer of encryption is stripped off.  This
-variable is only used if $mime_forward is set and
-$mime_forward_decode is unset.
+
3.169. pgp_long_ids
Type: boolean

+Default: no

+If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs.
 (PGP only)
-
3.183. smime_timeout
Type: number

-Default: 300

-The number of seconds after which a cached passphrase will expire if
-not used.
-(S/MIME only)
-
3.184. smime_encrypt_with
Type: string

-Default: (empty)

-This sets the algorithm that should be used for encryption.
-Valid choices are “des”, “des3”, “rc2-40”, “rc2-64”, “rc2-128”.
-If unset, “3des” (TripleDES) is used.
-(S/MIME only)
-
3.185. smime_keys
Type: path

-Default: (empty)

-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-storage and retrieval of keys/certs by itself. This is very basic right now,
-and stores keys and certificates in two different directories, both
-named as the hash-value retrieved from OpenSSL. There is an index file
-which contains mailbox-address keyid pair, and which can be manually
-edited. This option points to the location of the private keys.
-(S/MIME only)
-
3.186. smime_ca_location
Type: path

-Default: (empty)

-This variable contains the name of either a directory, or a file which
-contains trusted certificates for use with OpenSSL.
-(S/MIME only)
-
3.187. smime_certificates
Type: path

-Default: (empty)

-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-storage and retrieval of keys by itself. This is very basic right
-now, and keys and certificates are stored in two different
-directories, both named as the hash-value retrieved from
-OpenSSL. There is an index file which contains mailbox-address
-keyid pairs, and which can be manually edited. This option points to
-the location of the certificates.
-(S/MIME only)
-
3.188. smime_decrypt_command
Type: string

-Default: (empty)

-This format string specifies a command which is used to decrypt
-application/x-pkcs7-mime attachments.
-

-The OpenSSL command formats have their own set of printf(3)-like sequences
-similar to PGP's:
-
-
%f 
Expands to the name of a file containing a message.
-
%s 
Expands to the name of a file containing the signature part
-           of a multipart/signed attachment when verifying it.
-
%k 
The key-pair specified with $smime_default_key
-
%c 
One or more certificate IDs.
-
%a 
The algorithm used for encryption.
-
%C 
CA location:  Depending on whether $smime_ca_location
-           points to a directory or file, this expands to
-           “-CApath $smime_ca_location” or “-CAfile $smime_ca_location”.
-

-For examples on how to configure these formats, see the smime.rc in
-the samples/ subdirectory which has been installed on your system
-alongside the documentation.
-(S/MIME only)
-
3.189. smime_verify_command
Type: string

-Default: (empty)

-This command is used to verify S/MIME signatures of type multipart/signed.
-

-This is a format string, see the $smime_decrypt_command command for
-possible printf(3)-like sequences.
-(S/MIME only)
-
3.190. smime_verify_opaque_command
Type: string

-Default: (empty)

-This command is used to verify S/MIME signatures of type
-application/x-pkcs7-mime.
-

-This is a format string, see the $smime_decrypt_command command for
-possible printf(3)-like sequences.
-(S/MIME only)
-
3.191. smime_sign_command
Type: string

-Default: (empty)

-This command is used to created S/MIME signatures of type
-multipart/signed, which can be read by all mail clients.
-

-This is a format string, see the $smime_decrypt_command command for
-possible printf(3)-like sequences.
-(S/MIME only)
-
3.192. smime_sign_opaque_command
Type: string

-Default: (empty)

-This command is used to created S/MIME signatures of type
-application/x-pkcs7-signature, which can only be handled by mail
-clients supporting the S/MIME extension.
+
3.170. pgp_mime_auto
Type: quadoption

+Default: ask-yes

+This option controls whether Mutt will prompt you for
+automatically sending a (signed/encrypted) message using
+PGP/MIME when inline (traditional) fails (for any reason).
 

-This is a format string, see the $smime_decrypt_command command for
-possible printf(3)-like sequences.
-(S/MIME only)
-
3.193. smime_encrypt_command
Type: string

-Default: (empty)

-This command is used to create encrypted S/MIME messages.
+Also note that using the old-style PGP message format is strongly
+deprecated.
+(PGP only)
+
3.171. pgp_replyinline
Type: boolean

+Default: no

+Setting this variable will cause Mutt to always attempt to
+create an inline (traditional) message when replying to a
+message which is PGP encrypted/signed inline.  This can be
+overridden by use of the pgp menu, when inline is not
+required.  This option does not automatically detect if the
+(replied-to) message is inline; instead it relies on Mutt
+internals for previously checked/flagged messages.
 

-This is a format string, see the $smime_decrypt_command command for
-possible printf(3)-like sequences.
-(S/MIME only)
-
3.194. smime_pk7out_command
Type: string

-Default: (empty)

-This command is used to extract PKCS7 structures of S/MIME signatures,
-in order to extract the public X509 certificate(s).
+Note that Mutt might automatically use PGP/MIME for messages
+which consist of more than a single MIME part.  Mutt can be
+configured to ask before sending PGP/MIME messages when inline
+(traditional) would not work.
 

-This is a format string, see the $smime_decrypt_command command for
-possible printf(3)-like sequences.
-(S/MIME only)
-
3.195. smime_get_cert_command
Type: string

-Default: (empty)

-This command is used to extract X509 certificates from a PKCS7 structure.
+Also see the $pgp_mime_auto variable.
 

-This is a format string, see the $smime_decrypt_command command for
-possible printf(3)-like sequences.
-(S/MIME only)
-
3.196. smime_get_signer_cert_command
Type: string

-Default: (empty)

-This command is used to extract only the signers X509 certificate from a S/MIME
-signature, so that the certificate's owner may get compared to the
-email's “From:” field.
+Also note that using the old-style PGP message format is strongly
+deprecated.
+(PGP only)
+
3.172. pgp_retainable_sigs
Type: boolean

+Default: no

+If set, signed and encrypted messages will consist of nested
+multipart/signed and multipart/encrypted body parts.
 

-This is a format string, see the $smime_decrypt_command command for
-possible printf(3)-like sequences.
-(S/MIME only)
-
3.197. smime_import_cert_command
Type: string

+This is useful for applications like encrypted and signed mailing
+lists, where the outer layer (multipart/encrypted) can be easily
+removed, while the inner multipart/signed part is retained.
+(PGP only)
+
3.173. pgp_show_unusable
Type: boolean

+Default: yes

+If set, mutt will display non-usable keys on the PGP key selection
+menu.  This includes keys which have been revoked, have expired, or
+have been marked as “disabled” by the user.
+(PGP only)
+
3.174. pgp_sign_as
Type: string

 Default: (empty)

-This command is used to import a certificate via smime_keys.
-

-This is a format string, see the $smime_decrypt_command command for
-possible printf(3)-like sequences.
-(S/MIME only)
-
3.198. smime_get_cert_email_command
Type: string

+If you have more than one key pair, this option allows you to specify
+which of your private keys to use.  It is recommended that you use the
+keyid form to specify your key (e.g. 0x00112233).
+(PGP only)
+
3.175. pgp_sign_command
Type: string

 Default: (empty)

-This command is used to extract the mail address(es) used for storing
-X509 certificates, and for verification purposes (to check whether the
-certificate was issued for the sender's mailbox).
+This command is used to create the detached PGP signature for a
+multipart/signed PGP/MIME body part.
 

-This is a format string, see the $smime_decrypt_command command for
+This is a format string, see the $pgp_decode_command command for
 possible printf(3)-like sequences.
-(S/MIME only)
-
3.199. smime_default_key
Type: string

-Default: (empty)

-This is the default key-pair to use for signing. This must be set to the
-keyid (the hash-value that OpenSSL generates) to work properly
-(S/MIME only)
-
3.200. ssl_client_cert
Type: path

-Default: (empty)

-The file containing a client certificate and its associated private
-key.
-
3.201. ssl_force_tls
Type: boolean

-Default: no

-If this variable is set, Mutt will require that all connections
-to remote servers be encrypted. Furthermore it will attempt to
-negotiate TLS even if the server does not advertise the capability,
-since it would otherwise have to abort the connection anyway. This
-option supersedes $ssl_starttls.
-
3.202. ssl_starttls
Type: quadoption

-Default: yes

-If set (the default), mutt will attempt to use STARTTLS on servers
-advertising the capability. When unset, mutt will not attempt to
-use STARTTLS regardless of the server's capabilities.
-
3.203. certificate_file
Type: path

-Default: “˜/.mutt_certificates”

-This variable specifies the file where the certificates you trust
-are saved. When an unknown certificate is encountered, you are asked
-if you accept it or not. If you accept it, the certificate can also
-be saved in this file and further connections are automatically
-accepted.
-

-You can also manually add CA certificates in this file. Any server
-certificate that is signed with one of these CA certificates is
-also automatically accepted.
-

-Example:
-
-
-set certificate_file=~/.mutt/certificates
+(PGP only)
+
3.176. pgp_sort_keys
Type: sort order

+Default: address

+Specifies how the entries in the pgp menu are sorted. The
+following are legal values:
 
-
3.204. ssl_usesystemcerts
Type: boolean

+
address sort alphabetically by user id
+
keyid   sort alphabetically by key id
+
date    sort by key creation date
+
trust   sort by the trust of the key
+

+If you prefer reverse order of the above values, prefix it with
+“reverse-”.
+(PGP only)
+
3.177. pgp_strict_enc
Type: boolean

 Default: yes

-If set to yes, mutt will use CA certificates in the
-system-wide certificate store when checking if a server certificate
-is signed by a trusted CA.
-
3.205. entropy_file
Type: path

+If set, Mutt will automatically encode PGP/MIME signed messages as
+quoted-printable.  Please note that unsetting this variable may
+lead to problems with non-verifyable PGP signatures, so only change
+this if you know what you are doing.
+(PGP only)
+
3.178. pgp_timeout
Type: number

+Default: 300

+The number of seconds after which a cached passphrase will expire if
+not used.
+(PGP only)
+
3.179. pgp_use_gpg_agent
Type: boolean

+Default: no

+If set, mutt will use a possibly-running gpg-agent(1) process.
+(PGP only)
+
3.180. pgp_verify_command
Type: string

 Default: (empty)

-The file which includes random data that is used to initialize SSL
-library functions.
-
3.206. ssl_use_sslv2
Type: boolean

-Default: yes

-This variables specifies whether to attempt to use SSLv2 in the
-SSL authentication process.
-
3.207. ssl_use_sslv3
Type: boolean

-Default: yes

-This variables specifies whether to attempt to use SSLv3 in the
-SSL authentication process.
-
3.208. ssl_use_tlsv1
Type: boolean

-Default: yes

-This variables specifies whether to attempt to use TLSv1 in the
-SSL authentication process.
-
3.209. ssl_min_dh_prime_bits
Type: number

-Default: 0

-This variable specifies the minimum acceptable prime size (in bits)
-for use in any Diffie-Hellman key exchange. A value of 0 will use
-the default from the GNUTLS library.
-
3.210. ssl_ca_certificates_file
Type: path

+This command is used to verify PGP signatures.
+

+This is a format string, see the $pgp_decode_command command for
+possible printf(3)-like sequences.
+(PGP only)
+
3.181. pgp_verify_key_command
Type: string

 Default: (empty)

-This variable specifies a file containing trusted CA certificates.
-Any server certificate that is signed with one of these CA
-certificates is also automatically accepted.
+This command is used to verify key information from the key selection
+menu.
 

-Example:
-
-
-set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-
-
3.211. pipe_split
Type: boolean

-Default: no

-Used in connection with the <pipe-message> function following
-<tag-prefix>.  If this variable is unset, when piping a list of
-tagged messages Mutt will concatenate the messages and will pipe them
-all concatenated.  When set, Mutt will pipe the messages one by one.
-In both cases the messages are piped in the current sorted order,
-and the $pipe_sep separator is added after each message.
-
3.212. pipe_decode
Type: boolean

+This is a format string, see the $pgp_decode_command command for
+possible printf(3)-like sequences.
+(PGP only)
+
3.182. pipe_decode
Type: boolean

 Default: no

 Used in connection with the <pipe-message> command.  When unset,
 Mutt will pipe the messages without any preprocessing. When set, Mutt
 will weed headers and will attempt to decode the messages
 first.
-
3.213. pipe_sep
Type: string

+
3.183. pipe_sep
Type: string

 Default: “\n”

 The separator to add between messages when piping a list of tagged
 messages to an external Unix command.
-
3.214. pop_authenticators
Type: string

+
3.184. pipe_split
Type: boolean

+Default: no

+Used in connection with the <pipe-message> function following
+<tag-prefix>.  If this variable is unset, when piping a list of
+tagged messages Mutt will concatenate the messages and will pipe them
+all concatenated.  When set, Mutt will pipe the messages one by one.
+In both cases the messages are piped in the current sorted order,
+and the $pipe_sep separator is added after each message.
+
3.185. pop_auth_try_all
Type: boolean

+Default: yes

+If set, Mutt will try all available authentication methods.
+When unset, Mutt will only fall back to other authentication
+methods if the previous methods are unavailable. If a method is
+available but authentication fails, Mutt will not connect to the POP server.
+
3.186. pop_authenticators
Type: string

 Default: (empty)

 This is a colon-delimited list of authentication methods mutt may
 attempt to use to log in to an POP server, in the order mutt should
@@ -5411,47 +5655,30 @@ Example:
 
 
 set pop_authenticators="digest-md5:apop:user"
-
-
3.215. pop_auth_try_all
Type: boolean

-Default: yes

-If set, Mutt will try all available authentication methods.
-When unset, Mutt will only fall back to other authentication
-methods if the previous methods are unavailable. If a method is
-available but authentication fails, Mutt will not connect to the POP server.
-
3.216. pop_checkinterval
Type: number

+
3.187. pop_checkinterval
Type: number

 Default: 60

 This variable configures how often (in seconds) mutt should look for
 new mail in the currently selected mailbox if it is a POP mailbox.
-
3.217. pop_delete
Type: quadoption

+
3.188. pop_delete
Type: quadoption

 Default: ask-no

 If set, Mutt will delete successfully downloaded messages from the POP
 server when using the <fetch-mail> function.  When unset, Mutt will
 download messages but also leave them on the POP server.
-
3.218. pop_host
Type: string

+
3.189. pop_host
Type: string

 Default: (empty)

 The name of your POP server for the <fetch-mail> function.  You
 can also specify an alternative port, username and password, ie:
 
 
 [pop[s]://][username[:password]@]popserver[:port]
-
 

 where “[...]” denotes an optional part.
-
3.219. pop_last
Type: boolean

+
3.190. pop_last
Type: boolean

 Default: no

 If this variable is set, mutt will try to use the “LAST” POP command
 for retrieving only unread messages from the POP server when using
 the <fetch-mail> function.
-
3.220. pop_reconnect
Type: quadoption

-Default: ask-yes

-Controls whether or not Mutt will try to reconnect to the POP server if
-the connection is lost.
-
3.221. pop_user
Type: string

-Default: (empty)

-Your login name on the POP server.
-

-This variable defaults to your user name on the local machine.
-
3.222. pop_pass
Type: string

+
3.191. pop_pass
Type: string

 Default: (empty)

 Specifies the password for your POP account.  If unset, Mutt will
 prompt you for your password when you open a POP mailbox.
@@ -5459,24 +5686,33 @@ prompt you for your password when you open a POP mailbox.
 Warning: you should only use this option when you are on a
 fairly secure machine, because the superuser can read your muttrc
 even if you are the only one who can read the file.
-
3.223. post_indent_string
Type: string

+
3.192. pop_reconnect
Type: quadoption

+Default: ask-yes

+Controls whether or not Mutt will try to reconnect to the POP server if
+the connection is lost.
+
3.193. pop_user
Type: string

+Default: (empty)

+Your login name on the POP server.
+

+This variable defaults to your user name on the local machine.
+
3.194. post_indent_string
Type: string

 Default: (empty)

 Similar to the $attribution variable, Mutt will append this
 string after the inclusion of a message which is being replied to.
-
3.224. postpone
Type: quadoption

+
3.195. postpone
Type: quadoption

 Default: ask-yes

-Controls whether or not messages are saved in the $postponed
+Controls whether or not messages are saved in the $postponed
 mailbox when you elect not to send immediately.
 

-Also see the $recall variable.
-
3.225. postponed
Type: path

+Also see the $recall variable.
+
3.196. postponed
Type: path

 Default: “˜/postponed”

-Mutt allows you to indefinitely “postpone sending a message” which
+Mutt allows you to indefinitely “postpone sending a message” which
 you are editing.  When you choose to postpone a message, Mutt saves it
 in the mailbox specified by this variable.
 

-Also see the $postpone variable.
-
3.226. preconnect
Type: string

+Also see the $postpone variable.
+
3.197. preconnect
Type: string

 Default: (empty)

 If set, a shell command to be executed if mutt fails to establish
 a connection to the server. This is useful for setting up secure
@@ -5486,77 +5722,76 @@ status, mutt gives up opening the server. Example:
 
 set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \
 sleep 20 < /dev/null > /dev/null"
-
 

 Mailbox “foo” on “mailhost.net” can now be reached
 as “{localhost:1234}foo”.
 

 Note: For this example to work, you must be able to log in to the
 remote machine without having to enter a password.
-
3.227. print
Type: quadoption

+
3.198. print
Type: quadoption

 Default: ask-no

 Controls whether or not Mutt really prints messages.
 This is set to “ask-no” by default, because some people
 accidentally hit “p” often.
-
3.228. print_command
Type: path

+
3.199. print_command
Type: path

 Default: “lpr”

 This specifies the command pipe that should be used to print messages.
-
3.229. print_decode
Type: boolean

+
3.200. print_decode
Type: boolean

 Default: yes

 Used in connection with the <print-message> command.  If this
 option is set, the message is decoded before it is passed to the
-external command specified by $print_command.  If this option
+external command specified by $print_command.  If this option
 is unset, no processing will be applied to the message when
 printing it.  The latter setting may be useful if you are using
 some advanced printer filter which is able to properly format
 e-mail messages for printing.
-
3.230. print_split
Type: boolean

+
3.201. print_split
Type: boolean

 Default: no

 Used in connection with the <print-message> command.  If this option
-is set, the command specified by $print_command is executed once for
+is set, the command specified by $print_command is executed once for
 each message which is to be printed.  If this option is unset,
-the command specified by $print_command is executed only once, and
+the command specified by $print_command is executed only once, and
 all the messages are concatenated, with a form feed as the message
 separator.
 

 Those who use the enscript(1) program's mail-printing mode will
 most likely want to set this option.
-
3.231. prompt_after
Type: boolean

+
3.202. prompt_after
Type: boolean

 Default: yes

-If you use an external $pager, setting this variable will
+If you use an external $pager, setting this variable will
 cause Mutt to prompt you for a command when the pager exits rather
 than returning to the index menu.  If unset, Mutt will return to the
 index menu when the external pager exits.
-
3.232. query_command
Type: path

+
3.203. query_command
Type: path

 Default: (empty)

 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.
-
3.233. query_format
Type: string

+
3.204. query_format
Type: string

 Default: “%4c %t %-25.25a %-25.25n %?e?(%e)?”

 This variable describes the format of the “query” menu. The
 following printf(3)-style sequences are understood:
 
-
%a  
destination address
-
%c  
current entry number
-
%e  
extra information *
-
%n  
destination name
-
%t  
“*” if current entry is tagged, a space otherwise
-
%>X 
right justify the rest of the string and pad with “X”
-
%|X 
pad to the end of the line with “X”
-
%*X 
soft-fill with character “X” as pad
-

-For an explanation of “soft-fill”, see the $index_format documentation.
-

-* = can be optionally printed if nonzero, see the $status_format documentation.
-
3.234. quit
Type: quadoption

+
%a  destination address
+
%c  current entry number
+
%e  extra information *
+
%n  destination name
+
%t  “*” if current entry is tagged, a space otherwise
+
%>X right justify the rest of the string and pad with “X”
+
%|X pad to the end of the line with “X”
+
%*X soft-fill with character “X” as pad
+

+For an explanation of “soft-fill”, see the $index_format documentation.
+

+* = can be optionally printed if nonzero, see the $status_format documentation.
+
3.205. quit
Type: quadoption

 Default: yes

 This variable controls whether “quit” and “exit” actually quit
 from mutt.  If this option is set, they do quit, if it is unset, 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.
-
3.235. quote_regexp
Type: regular expression

+
3.206. quote_regexp
Type: regular expression

 Default: “^([ \t]*[|>:}#])+”

 A regular expression used in the internal pager to determine quoted
 sections of text in the body of a message. Quoted text may be filtered
@@ -5568,8 +5803,8 @@ Higher levels of quoting may be colored differently (“colo
 the last character from the matched text and recursively reapplying
 the regular expression until it fails to produce a match.
 

-Match detection may be overridden by the $smileys regular expression.
-
3.236. read_inc
Type: number

+Match detection may be overridden by the $smileys regular expression.
+
3.207. read_inc
Type: number

 Default: 10

 If set to a value greater than 0, Mutt will display which message it
 is currently on when reading a mailbox or when performing search actions
@@ -5581,20 +5816,20 @@ reading or searching large mailboxes which may take some time.
 When set to 0, only a single message will appear before the reading
 the mailbox.
 

-Also see the $write_inc, $net_inc and $time_inc variables and the
-“tuning” section of the manual for performance considerations.
-
3.237. read_only
Type: boolean

+Also see the $write_inc, $net_inc and $time_inc variables and the
+“tuning” section of the manual for performance considerations.
+
3.208. read_only
Type: boolean

 Default: no

 If set, all folders are opened in read-only mode.
-
3.238. realname
Type: string

+
3.209. realname
Type: string

 Default: (empty)

 This variable specifies what “real” or “personal” name should be used
 when sending messages.
 

 By default, this is the GECOS field from /etc/passwd.  Note that this
 variable will not be used when the user has set a real name
-in the $from variable.
-
3.239. recall
Type: quadoption

+in the $from variable.
+
3.210. recall
Type: quadoption

 Default: ask-yes

 Controls whether or not Mutt recalls postponed messages
 when composing a new message.
@@ -5602,29 +5837,29 @@ when composing a new message.
 Setting this variable to is not generally useful, and thus not
 recommended.
 

-Also see $postponed variable.
-
3.240. record
Type: path

+Also see $postponed variable.
+
3.211. record
Type: path

 Default: “˜/sent”

 This specifies the file into which your outgoing messages should be
 appended.  (This is meant as the primary method for saving a copy of
-your messages, but another way to do this is using the “my_hdr”
+your messages, but another way to do this is using the “my_hdr”
 command to create a “Bcc:” field with your email address in it.)
 

-The value of $record is overridden by the $force_name and
-$save_name variables, and the “fcc-hook” command.
-
3.241. reply_regexp
Type: regular expression

+The value of $record is overridden by the $force_name and
+$save_name variables, and the “fcc-hook” command.
+
3.212. reply_regexp
Type: regular expression

 Default: “^(re([\[0-9\]+])*|aw):[ \t]*”

 A regular expression used to recognize reply messages when threading
 and replying. The default value corresponds to the English "Re:" and
 the German "Aw:".
-
3.242. reply_self
Type: boolean

+
3.213. reply_self
Type: boolean

 Default: no

 If unset and you are replying to a message sent by you, Mutt will
 assume that you want to reply to the recipients of that message rather
 than to yourself.
 

-Also see the “alternates” command.
-
3.243. reply_to
Type: quadoption

+Also see the “alternates” command.
+
3.214. reply_to
Type: quadoption

 Default: ask-yes

 If set, when replying to a message, Mutt will use the address listed
 in the Reply-to: header as the recipient of the reply.  If unset,
@@ -5632,12 +5867,12 @@ it will use the address in the From: header field instead.  This
 option is useful for reading a mailing list that sets the Reply-To:
 header field to the list address and you want to send a private
 message to the author of a message.
-
3.244. resolve
Type: boolean

+
3.215. resolve
Type: boolean

 Default: yes

 When set, the cursor will be automatically advanced to the next
 (possibly undeleted) message whenever a command that modifies the
 current message is executed.
-
3.245. reverse_alias
Type: boolean

+
3.216. reverse_alias
Type: boolean

 Default: no

 This variable controls whether or not Mutt will display the “personal”
 name from your aliases in the index menu if it finds an alias that
@@ -5646,36 +5881,34 @@ alias:
 
 
 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.
-
3.246. reverse_name
Type: boolean

+
3.217. reverse_name
Type: boolean

 Default: no

 It may sometimes arrive that you receive mail to a certain machine,
 move the messages to another machine, and reply to some the messages
 from there.  If this variable is set, the default From: line of
 the reply messages is built using the address where you received the
 messages you are replying to if that address matches your
-“alternates”.  If the variable is unset, or the address that would be
-used doesn't match your “alternates”, the From: line will use
+“alternates”.  If the variable is unset, or the address that would be
+used doesn't match your “alternates”, the From: line will use
 your address on the current machine.
 

-Also see the “alternates” command.
-
3.247. reverse_realname
Type: boolean

+Also see the “alternates” command.
+
3.218. reverse_realname
Type: boolean

 Default: yes

-This variable fine-tunes the behaviour of the $reverse_name feature.
+This variable fine-tunes the behaviour of the $reverse_name feature.
 When it is set, mutt will use the address from incoming messages as-is,
 possibly including eventual real names.  When it is unset, mutt will
-override any such real names with the setting of the $realname variable.
-
3.248. rfc2047_parameters
Type: boolean

+override any such real names with the setting of the $realname variable.
+
3.219. rfc2047_parameters
Type: boolean

 Default: no

 When this variable is set, Mutt will decode RFC2047-encoded MIME
 parameters. You want to set this variable when mutt suggests you
@@ -5683,7 +5916,6 @@ to save attachments to files named like:
 
 
 =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
-
 

 When this variable is set interactively, the change won't be
 active until you change folders.
@@ -5695,56 +5927,60 @@ wild.
 Also note that setting this parameter will not have the effect
 that mutt generates this kind of encoding.  Instead, mutt will
 unconditionally use the encoding specified in RFC2231.
-
3.249. save_address
Type: boolean

+
3.220. save_address
Type: boolean

 Default: no

 If set, mutt will take the sender's full address when choosing a
-default folder for saving a mail. If $save_name or $force_name
+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.
-
3.250. save_empty
Type: boolean

+
3.221. save_empty
Type: boolean

 Default: yes

 When unset, mailboxes which contain no saved messages will be removed
-when closed (the exception is $spoolfile which is never removed).
+when closed (the exception is $spoolfile which is never removed).
 If set, mailboxes are never removed.
 

 Note: This only applies to mbox and MMDF folders, Mutt does not
 delete MH and Maildir directories.
-
3.251. save_history
Type: number

+
3.222. save_history
Type: number

 Default: 0

 This variable controls the size of the history (per category) saved in the
-$history_file file.
-
3.252. save_name
Type: boolean

+$history_file file.
+
3.223. save_name
Type: boolean

 Default: no

 This variable controls how copies of outgoing messages are saved.
 When set, a check is made to see if a mailbox specified by the
 recipient address exists (this is done by searching for a mailbox in
-the $folder directory with the username part of the
+the $folder directory with the username part of the
 recipient address).  If the mailbox exists, the outgoing message will
 be saved to that mailbox, otherwise the message is saved to the
-$record mailbox.
+$record mailbox.
 

-Also see the $force_name variable.
-
3.253. score
Type: boolean

+Also see the $force_name variable.
+
3.224. score
Type: boolean

 Default: yes

 When this variable is unset, scoring is turned off.  This can
 be useful to selectively disable scoring for certain folders when the
-$score_threshold_delete variable and related are used.
-
3.254. score_threshold_delete
Type: number

+$score_threshold_delete variable and related are used.
+
3.225. score_threshold_delete
Type: number

 Default: -1

 Messages which have been assigned a score equal to or lower than the value
 of this variable are automatically marked for deletion by mutt.  Since
 mutt scores are always greater than or equal to zero, the default setting
 of this variable will never mark a message for deletion.
-
3.255. score_threshold_flag
Type: number

+
3.226. score_threshold_flag
Type: number

 Default: 9999

 Messages which have been assigned a score greater than or equal to this
 variable's value are automatically marked "flagged".
-
3.256. score_threshold_read
Type: number

+
3.227. score_threshold_read
Type: number

 Default: -1

 Messages which have been assigned a score equal to or lower than the value
 of this variable are automatically marked as read by mutt.  Since
 mutt scores are always greater than or equal to zero, the default setting
 of this variable will never mark a message read.
-
3.257. send_charset
Type: string

+
3.228. search_context
Type: number

+Default: 0

+For the pager, this variable specifies the number of lines shown
+before search results. By default, search results will be top-aligned.
+
3.229. send_charset
Type: string

 Default: “us-ascii:iso-8859-1:utf-8”

 A colon-delimited list of character sets for outgoing messages. Mutt will use the
 first character set into which the text can be converted exactly.
@@ -5756,50 +5992,50 @@ appropriate widely used standard character set (such as
 

 In case the text cannot be converted into one of these exactly,
 mutt uses $charset as a fallback.
-
3.258. sendmail
Type: path

+
3.230. sendmail
Type: path

 Default: “/usr/sbin/sendmail -oem -oi”

 Specifies the program and arguments used to deliver mail sent by Mutt.
 Mutt expects that the specified program interprets additional
 arguments as recipient addresses.
-
3.259. sendmail_wait
Type: number

+
3.231. sendmail_wait
Type: number

 Default: 0

-Specifies the number of seconds to wait for the $sendmail process
+Specifies the number of seconds to wait for the $sendmail process
 to finish before giving up and putting delivery in the background.
 

 Mutt interprets the value of this variable as follows:
 
-
>0 
number of seconds to wait for sendmail to finish before continuing
-
0  
wait forever for sendmail to finish
-
<0 
always put sendmail in the background without waiting
-

+
>0 number of seconds to wait for sendmail to finish before continuing
+
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.
-
3.260. shell
Type: path

+
3.232. shell
Type: path

 Default: (empty)

 Command to use when spawning a subshell.  By default, the user's login
 shell from /etc/passwd is used.
-
3.261. sig_dashes
Type: boolean

+
3.233. sig_dashes
Type: boolean

 Default: yes

 If set, a line containing “-- ” (note the trailing space) will be inserted before your
-$signature.  It is strongly recommended that you not unset
+$signature.  It is strongly recommended that you not unset
 this variable unless your signature contains just your name.  The
 reason for this is because many software packages use “-- \n” to
 detect your signature.  For example, Mutt has the ability to highlight
 the signature in a different color in the builtin pager.
-
3.262. sig_on_top
Type: boolean

+
3.234. sig_on_top
Type: boolean

 Default: no

 If set, the signature will be included before any quoted or forwarded
 text.  It is strongly recommended that you do not set this variable
 unless you really know what you are doing, and are prepared to take
 some heat from netiquette guardians.
-
3.263. signature
Type: path

+
3.235. signature
Type: path

 Default: “˜/.signature”

 Specifies the filename of your signature, which is appended to all
 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 standard output.
-
3.264. simple_search
Type: string

+
3.236. simple_search
Type: string

 Default: “˜f %s | ˜s %s”

 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 “˜” pattern
@@ -5809,25 +6045,186 @@ For example, if you simply type “joe” at a search
 will automatically expand it to the value specified by this variable by
 replacing “%s” with the supplied string.
 For the default value, “joe” would be expanded to: “˜f joe | ˜s joe”.
-
3.265. smart_wrap
Type: boolean

+
3.237. sleep_time
Type: number

+Default: 1

+Specifies time, in seconds, to pause while displaying certain informational
+messages, while moving from folder to folder and after expunging
+messages from the current folder.  The default is to pause one second, so
+a value of zero for this option suppresses the pause.
+
3.238. smart_wrap
Type: boolean

 Default: yes

 Controls the display of lines longer than the screen width in the
 internal pager. If set, long lines are wrapped at a word boundary.  If
 unset, lines are simply wrapped at the screen edge. Also see the
-$markers variable.
-
3.266. smileys
Type: regular expression

+$markers variable.
+
3.239. smileys
Type: regular expression

 Default: “(>From )|(:[-^]?[][)(><}{|/DP])”

 The pager uses this variable to catch some common false
-positives of $quote_regexp, most notably smileys and not consider
-a line quoted text if it also matches $smileys. This mostly
+positives of $quote_regexp, most notably smileys and not consider
+a line quoted text if it also matches $smileys. This mostly
 happens at the beginning of a line.
-
3.267. sleep_time
Type: number

-Default: 1

-Specifies time, in seconds, to pause while displaying certain informational
-messages, while moving from folder to folder and after expunging
-messages from the current folder.  The default is to pause one second, so
-a value of zero for this option suppresses the pause.
-
3.268. smtp_authenticators
Type: string

+
3.240. smime_ask_cert_label
Type: boolean

+Default: yes

+This flag controls whether you want to be asked to enter a label
+for a certificate about to be added to the database or not. It is
+set by default.
+(S/MIME only)
+
3.241. smime_ca_location
Type: path

+Default: (empty)

+This variable contains the name of either a directory, or a file which
+contains trusted certificates for use with OpenSSL.
+(S/MIME only)
+
3.242. smime_certificates
Type: path

+Default: (empty)

+Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
+storage and retrieval of keys by itself. This is very basic right
+now, and keys and certificates are stored in two different
+directories, both named as the hash-value retrieved from
+OpenSSL. There is an index file which contains mailbox-address
+keyid pairs, and which can be manually edited. This option points to
+the location of the certificates.
+(S/MIME only)
+
3.243. smime_decrypt_command
Type: string

+Default: (empty)

+This format string specifies a command which is used to decrypt
+application/x-pkcs7-mime attachments.
+

+The OpenSSL command formats have their own set of printf(3)-like sequences
+similar to PGP's:
+
+
%f Expands to the name of a file containing a message.
+
%s Expands to the name of a file containing the signature part
+           of a multipart/signed attachment when verifying it.
+
%k The key-pair specified with $smime_default_key
+
%c One or more certificate IDs.
+
%a The algorithm used for encryption.
+
%C CA location:  Depending on whether $smime_ca_location
+           points to a directory or file, this expands to
+           “-CApath $smime_ca_location” or “-CAfile $smime_ca_location”.
+

+For examples on how to configure these formats, see the smime.rc in
+the samples/ subdirectory which has been installed on your system
+alongside the documentation.
+(S/MIME only)
+
3.244. smime_decrypt_use_default_key
Type: boolean

+Default: yes

+If set (default) this tells mutt to use the default key for decryption. Otherwise,
+if managing multiple certificate-key-pairs, mutt will try to use the mailbox-address
+to determine the key to use. It will ask you to supply a key, if it can't find one.
+(S/MIME only)
+
3.245. smime_default_key
Type: string

+Default: (empty)

+This is the default key-pair to use for signing. This must be set to the
+keyid (the hash-value that OpenSSL generates) to work properly
+(S/MIME only)
+
3.246. smime_encrypt_command
Type: string

+Default: (empty)

+This command is used to create encrypted S/MIME messages.
+

+This is a format string, see the $smime_decrypt_command command for
+possible printf(3)-like sequences.
+(S/MIME only)
+
3.247. smime_encrypt_with
Type: string

+Default: (empty)

+This sets the algorithm that should be used for encryption.
+Valid choices are “des”, “des3”, “rc2-40”, “rc2-64”, “rc2-128”.
+If unset, “3des” (TripleDES) is used.
+(S/MIME only)
+
3.248. smime_get_cert_command
Type: string

+Default: (empty)

+This command is used to extract X509 certificates from a PKCS7 structure.
+

+This is a format string, see the $smime_decrypt_command command for
+possible printf(3)-like sequences.
+(S/MIME only)
+
3.249. smime_get_cert_email_command
Type: string

+Default: (empty)

+This command is used to extract the mail address(es) used for storing
+X509 certificates, and for verification purposes (to check whether the
+certificate was issued for the sender's mailbox).
+

+This is a format string, see the $smime_decrypt_command command for
+possible printf(3)-like sequences.
+(S/MIME only)
+
3.250. smime_get_signer_cert_command
Type: string

+Default: (empty)

+This command is used to extract only the signers X509 certificate from a S/MIME
+signature, so that the certificate's owner may get compared to the
+email's “From:” field.
+

+This is a format string, see the $smime_decrypt_command command for
+possible printf(3)-like sequences.
+(S/MIME only)
+
3.251. smime_import_cert_command
Type: string

+Default: (empty)

+This command is used to import a certificate via smime_keys.
+

+This is a format string, see the $smime_decrypt_command command for
+possible printf(3)-like sequences.
+(S/MIME only)
+
3.252. smime_is_default
Type: boolean

+Default: no

+The default behaviour of mutt is to use PGP on all auto-sign/encryption
+operations. To override and to use OpenSSL instead this must be set.
+However, this has no effect while replying, since mutt will automatically
+select the same application that was used to sign/encrypt the original
+message.  (Note that this variable can be overridden by unsetting $crypt_autosmime.)
+(S/MIME only)
+
3.253. smime_keys
Type: path

+Default: (empty)

+Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
+storage and retrieval of keys/certs by itself. This is very basic right now,
+and stores keys and certificates in two different directories, both
+named as the hash-value retrieved from OpenSSL. There is an index file
+which contains mailbox-address keyid pair, and which can be manually
+edited. This option points to the location of the private keys.
+(S/MIME only)
+
3.254. smime_pk7out_command
Type: string

+Default: (empty)

+This command is used to extract PKCS7 structures of S/MIME signatures,
+in order to extract the public X509 certificate(s).
+

+This is a format string, see the $smime_decrypt_command command for
+possible printf(3)-like sequences.
+(S/MIME only)
+
3.255. smime_sign_command
Type: string

+Default: (empty)

+This command is used to created S/MIME signatures of type
+multipart/signed, which can be read by all mail clients.
+

+This is a format string, see the $smime_decrypt_command command for
+possible printf(3)-like sequences.
+(S/MIME only)
+
3.256. smime_sign_opaque_command
Type: string

+Default: (empty)

+This command is used to created S/MIME signatures of type
+application/x-pkcs7-signature, which can only be handled by mail
+clients supporting the S/MIME extension.
+

+This is a format string, see the $smime_decrypt_command command for
+possible printf(3)-like sequences.
+(S/MIME only)
+
3.257. smime_timeout
Type: number

+Default: 300

+The number of seconds after which a cached passphrase will expire if
+not used.
+(S/MIME only)
+
3.258. smime_verify_command
Type: string

+Default: (empty)

+This command is used to verify S/MIME signatures of type multipart/signed.
+

+This is a format string, see the $smime_decrypt_command command for
+possible printf(3)-like sequences.
+(S/MIME only)
+
3.259. smime_verify_opaque_command
Type: string

+Default: (empty)

+This command is used to verify S/MIME signatures of type
+application/x-pkcs7-mime.
+

+This is a format string, see the $smime_decrypt_command command for
+possible printf(3)-like sequences.
+(S/MIME only)
+
3.260. smtp_authenticators
Type: string

 Default: (empty)

 This is a colon-delimited list of authentication methods mutt may
 attempt to use to log in to an SMTP server, in the order mutt should
@@ -5841,29 +6238,27 @@ Example:
 
 
 set smtp_authenticators="digest-md5:cram-md5"
-
-
3.269. smtp_pass
Type: string

+
3.261. smtp_pass
Type: string

 Default: (empty)

 Specifies the password for your SMTP account.  If unset, Mutt will
 prompt you for your password when you first send mail via SMTP.
-See $smtp_url to configure mutt to send mail via SMTP.
+See $smtp_url to configure mutt to send mail via SMTP.
 

 Warning: you should only use this option when you are on a
 fairly secure machine, because the superuser can read your muttrc even
 if you are the only one who can read the file.
-
3.270. smtp_url
Type: string

+
3.262. smtp_url
Type: string

 Default: (empty)

 Defines the SMTP smarthost where sent messages should relayed for
 delivery. This should take the form of an SMTP URL, eg:
 
 
 smtp[s]://[user[:pass]@]host[:port]/
-
 

-... where “[...]” denotes an optional part.
-Setting this variable overrides the value of the $sendmail
+where “[...]” denotes an optional part.
+Setting this variable overrides the value of the $sendmail
 variable.
-
3.271. sort
Type: sort order

+
3.263. sort
Type: sort order

 Default: date

 Specifies how to sort messages in the “index” menu.  Valid values
 are:
@@ -5881,7 +6276,7 @@ are:
 

 You may optionally use the “reverse-” prefix to specify reverse sorting
 order (example: “set sort=reverse-date-sent”).
-
3.272. sort_alias
Type: sort order

+
3.264. sort_alias
Type: sort order

 Default: alias

 Specifies how the entries in the “alias” menu are sorted.  The
 following are legal values:
@@ -5889,29 +6284,28 @@ following are legal values:
 
  • address (sort alphabetically by email address)
 
  • alias (sort alphabetically by alias name)
 
  • unsorted (leave in order specified in .muttrc)
-
3.273. sort_aux
Type: sort order

+
3.265. sort_aux
Type: sort order

 Default: date

 When sorting by threads, this variable controls how threads are sorted
 in relation to other threads, and how the branches of the thread trees
-are sorted.  This can be set to any value that $sort can, except
+are sorted.  This can be set to any value that $sort can, except
 “threads” (in that case, mutt will just use “date-sent”).  You can also
 specify the “last-” prefix in addition to the “reverse-” prefix, but “last-”
 must come after “reverse-”.  The “last-” prefix causes messages to be
 sorted against its siblings by which has the last descendant, using
-the rest of $sort_aux as an ordering.  For instance,
+the rest of $sort_aux as an ordering.  For instance,
 
 
 set sort_aux=last-date-received
-
 

 would mean that if a new message is received in a
 thread, that thread becomes the last one displayed (or the first, if
 you have “set sort=reverse-threads”.)
 

-Note: For reversed $sort
-order $sort_aux is reversed again (which is not the right thing to do,
+Note: For reversed $sort
+order $sort_aux is reversed again (which is not the right thing to do,
 but kept to not break any existing configuration setting).
-
3.274. sort_browser
Type: sort order

+
3.266. sort_browser
Type: sort order

 Default: alpha

 Specifies how to sort entries in the file browser.  By default, the
 entries are sorted alphabetically.  Valid values:
@@ -5923,33 +6317,93 @@ entries are sorted alphabetically.  Valid values:
 

 You may optionally use the “reverse-” prefix to specify reverse sorting
 order (example: “set sort_browser=reverse-date”).
-
3.275. sort_re
Type: boolean

+
3.267. sort_re
Type: boolean

 Default: yes

 This variable is only useful when sorting by threads with
-$strict_threads unset.  In that case, it changes the heuristic
-mutt uses to thread messages by subject.  With $sort_re set, mutt will
+$strict_threads unset.  In that case, it changes the heuristic
+mutt uses to thread messages by subject.  With $sort_re set, mutt will
 only attach a message as the child of another message by subject if
 the subject of the child message starts with a substring matching the
-setting of $reply_regexp.  With $sort_re unset, mutt will attach
+setting of $reply_regexp.  With $sort_re unset, mutt will attach
 the message whether or not this is the case, as long as the
-non-$reply_regexp parts of both messages are identical.
-
3.276. spam_separator
Type: string

+non-$reply_regexp parts of both messages are identical.
+
3.268. spam_separator
Type: string

 Default: “,”

 This variable controls what happens when multiple spam headers
 are matched: if unset, each successive header will overwrite any
 previous matches value for the spam label. If set, each successive
 match will append to the previous, using this variable's value as a
 separator.
-
3.277. spoolfile
Type: path

+
3.269. spoolfile
Type: path

 Default: (empty)

 If your spool mailbox is in a non-default place where Mutt cannot find
 it, you can specify its location with this variable.  Mutt will
-automatically set this variable to the value of the environment
-variable $MAIL if it is not set.
-
3.278. status_chars
Type: string

+initially set this variable to the value of the environment
+variable $MAIL or $MAILDIR if either is defined.
+
3.270. ssl_ca_certificates_file
Type: path

+Default: (empty)

+This variable specifies a file containing trusted CA certificates.
+Any server certificate that is signed with one of these CA
+certificates is also automatically accepted.
+

+Example:
+
+
+set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
+
3.271. ssl_client_cert
Type: path

+Default: (empty)

+The file containing a client certificate and its associated private
+key.
+
3.272. ssl_force_tls
Type: boolean

+Default: no

+If this variable is set, Mutt will require that all connections
+to remote servers be encrypted. Furthermore it will attempt to
+negotiate TLS even if the server does not advertise the capability,
+since it would otherwise have to abort the connection anyway. This
+option supersedes $ssl_starttls.
+
3.273. ssl_min_dh_prime_bits
Type: number

+Default: 0

+This variable specifies the minimum acceptable prime size (in bits)
+for use in any Diffie-Hellman key exchange. A value of 0 will use
+the default from the GNUTLS library.
+
3.274. ssl_starttls
Type: quadoption

+Default: yes

+If set (the default), mutt will attempt to use STARTTLS on servers
+advertising the capability. When unset, mutt will not attempt to
+use STARTTLS regardless of the server's capabilities.
+
3.275. ssl_use_sslv2
Type: boolean

+Default: no

+This variable specifies whether to attempt to use SSLv2 in the
+SSL authentication process.
+
3.276. ssl_use_sslv3
Type: boolean

+Default: yes

+This variable specifies whether to attempt to use SSLv3 in the
+SSL authentication process.
+
3.277. ssl_use_tlsv1
Type: boolean

+Default: yes

+This variable specifies whether to attempt to use TLSv1 in the
+SSL authentication process.
+
3.278. ssl_usesystemcerts
Type: boolean

+Default: yes

+If set to yes, mutt will use CA certificates in the
+system-wide certificate store when checking if a server certificate
+is signed by a trusted CA.
+
3.279. ssl_verify_dates
Type: boolean

+Default: yes

+If set (the default), mutt will not automatically accept a server
+certificate that is either not yet valid or already expired. You should
+only unset this for particular known hosts, using the
+<account-hook> function.
+
3.280. ssl_verify_host
Type: boolean

+Default: yes

+If set (the default), mutt will not automatically accept a server
+certificate whose host name does not match the host used in your folder
+URL. You should only unset this for particular known hosts, using
+the <account-hook> function.
+
3.281. status_chars
Type: string

 Default: “-*%A”

 Controls the characters used by the “%r” indicator in
-$status_format. The first character is used when the mailbox is
+$status_format. The first character is used when the mailbox is
 unchanged. The second is used when the mailbox has been changed, and
 it needs to be resynchronized. The third is used if the mailbox is in
 read-only mode, or if the mailbox will not be written when exiting
@@ -5958,39 +6412,39 @@ with the <toggle-write> operation, bound by d
 is used to indicate that the current folder has been opened in attach-
 message mode (Certain operations like composing a new mail, replying,
 forwarding, etc. are not permitted in this mode).
-
3.279. status_format
Type: string

+
3.282. status_format
Type: string

 Default: “-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---”

 Controls the format of the status line displayed in the “index”
-menu.  This string is similar to $index_format, but has its own
+menu.  This string is similar to $index_format, but has its own
 set of printf(3)-like sequences:
 
-
%b  
number of mailboxes with new mail *
-
%d  
number of deleted messages *
-
%f  
the full pathname of the current mailbox
-
%F  
number of flagged messages *
-
%h  
local hostname
-
%l  
size (in bytes) of the current mailbox *
-
%L  
size (in bytes) of the messages shown
+
%b  number of mailboxes with new mail *
+
%d  number of deleted messages *
+
%f  the full pathname of the current mailbox
+
%F  number of flagged messages *
+
%h  local hostname
+
%l  size (in bytes) of the current mailbox *
+
%L  size (in bytes) of the messages shown
 (i.e., which match the current limit) *
-
%m  
the number of messages in the mailbox *
-
%M  
the number of messages shown (i.e., which match the current limit) *
-
%n  
number of new messages in the mailbox *
-
%o  
number of old unread messages *
-
%p  
number of postponed messages *
-
%P  
percentage of the way through the index
-
%r  
modified/read-only/won't-write/attach-message indicator,
-according to $status_chars
-
%s  
current sorting mode ($sort)
-
%S  
current aux sorting method ($sort_aux)
-
%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”
-
%*X 
soft-fill with character “X” as pad
-

-For an explanation of “soft-fill”, see the $index_format documentation.
+
%m  the number of messages in the mailbox *
+
%M  the number of messages shown (i.e., which match the current limit) *
+
%n  number of new messages in the mailbox *
+
%o  number of old unread messages *
+
%p  number of postponed messages *
+
%P  percentage of the way through the index
+
%r  modified/read-only/won't-write/attach-message indicator,
+according to $status_chars
+
%s  current sorting mode ($sort)
+
%S  current aux sorting method ($sort_aux)
+
%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”
+
%*X soft-fill with character “X” as pad
+

+For an explanation of “soft-fill”, see the $index_format documentation.
 

 * = can be optionally printed if nonzero
 

@@ -6028,27 +6482,27 @@ you would use: “%_h”
 If you prefix the sequence character with a colon (“:”) character, mutt
 will replace any dots in the expansion by underscores. This might be helpful
 with IMAP folders that don't like dots in folder names.
-
3.280. status_on_top
Type: boolean

+
3.283. status_on_top
Type: boolean

 Default: no

 Setting this variable causes the “status bar” to be displayed on
-the first line of the screen rather than near the bottom. If $help
+the first line of the screen rather than near the bottom. If $help
 is set, too it'll be placed at the bottom.
-
3.281. strict_threads
Type: boolean

+
3.284. strict_threads
Type: boolean

 Default: no

 If set, threading will only make use of the “In-Reply-To” and
-“References:” fields when you $sort by message threads.  By
+“References:” fields when you $sort by message threads.  By
 default, messages with the same subject are grouped together in
 “pseudo threads.”. This may not always be desirable, such as in a
 personal mailbox where you might have several unrelated messages with
 the subjects like “hi” which will get grouped together. See also
-$sort_re for a less drastic way of controlling this
+$sort_re for a less drastic way of controlling this
 behaviour.
-
3.282. suspend
Type: boolean

+
3.285. suspend
Type: boolean

 Default: yes

 When unset, mutt won't stop when the user presses the terminal's
 susp key, usually “^Z”. This is useful if you run mutt
 inside an xterm using a command like “xterm -e mutt”.
-
3.283. text_flowed
Type: boolean

+
3.286. text_flowed
Type: boolean

 Default: no

 When set, mutt will generate “format=flowed” bodies with a content type
 of “text/plain; format=flowed”.
@@ -6056,12 +6510,8 @@ This format is easier to handle for some mailing software, and generally
 just looks like ordinary text.  To actually make use of this format's
 features, you'll need support in your editor.
 

-Note that $indent_string is ignored when this option is set.
-
3.284. thread_received
Type: boolean

-Default: no

-When set, mutt uses the date received rather than the date sent
-to thread messages by subject.
-
3.285. thorough_search
Type: boolean

+Note that $indent_string is ignored when this option is set.
+
3.287. thorough_search
Type: boolean

 Default: no

 Affects the ˜b and ˜h search operations described in
 section “patterns”.  If set, the headers and body/attachments of
@@ -6073,20 +6523,24 @@ this value because decoding also includes MIME parsing/decoding and possible
 character set conversions. Otherwise mutt will attempt to match against the
 raw message received (for example quoted-printable encoded or with encoded
 headers) which may lead to incorrect search results.
-
3.286. tilde
Type: boolean

+
3.288. thread_received
Type: boolean

+Default: no

+When set, mutt uses the date received rather than the date sent
+to thread messages by subject.
+
3.289. tilde
Type: boolean

 Default: no

 When set, the internal-pager will pad blank lines to the bottom of the
 screen with a tilde (“˜”).
-
3.287. time_inc
Type: number

+
3.290. time_inc
Type: number

 Default: 0

-Along with $read_inc, $write_inc, and $net_inc, this
+Along with $read_inc, $write_inc, and $net_inc, this
 variable controls the frequency with which progress updates are
-displayed. It suppresses updates less than $time_inc milliseconds
+displayed. It suppresses updates less than $time_inc milliseconds
 apart. This can improve throughput on systems with slow terminals,
 or when running mutt on a remote system.
 

-Also see the “tuning” section of the manual for performance considerations.
-
3.288. timeout
Type: number

+Also see the “tuning” section of the manual for performance considerations.
+
3.291. timeout
Type: number

 Default: 600

 When Mutt is waiting for user input either idleing in menus or
 in an interactive prompt, Mutt would block until input is
@@ -6099,13 +6553,13 @@ until it aborts waiting for input, performs these operations and
 continues to wait for input.
 

 A value of zero or less will cause Mutt to never time out.
-
3.289. tmpdir
Type: path

+
3.292. tmpdir
Type: path

 Default: (empty)

 This variable allows you to specify where Mutt will place its
 temporary files needed for displaying and composing messages.  If
 this variable is not set, the environment variable $TMPDIR is
 used.  If $TMPDIR is not set then “/tmp” is used.
-
3.290. to_chars
Type: string

+
3.293. to_chars
Type: string

 Default: “ +TCFL”

 Controls the character used to indicate mail addressed to you.  The
 first character is the one used when the mail is not addressed to your
@@ -6117,7 +6571,7 @@ address is specified in the “Cc:” header field, b
 recipient.  The fifth character is used to indicate mail that was sent
 by you.  The sixth character is used to indicate when a mail
 was sent to a mailing-list you subscribe to.
-
3.291. tunnel
Type: string

+
3.294. tunnel
Type: string

 Default: (empty)

 Setting this variable will cause mutt to open a pipe to a command
 instead of a raw socket. You may be able to use this to set up
@@ -6125,60 +6579,67 @@ preauthenticated connections to your IMAP/POP3/SMTP server. Example:
 
 
 set tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
-
 

 Note: For this example to work you must be able to log in to the remote
 machine without having to enter a password.
-
3.292. use_8bitmime
Type: boolean

+

+When set, Mutt uses the tunnel for all remote connections.
+Please see “account-hook” in the manual for how to use different
+tunnel commands per connection.
+
3.295. uncollapse_jump
Type: boolean

+Default: no

+When set, Mutt will jump to the next unread message, if any,
+when the current thread is uncollapsed.
+
3.296. use_8bitmime
Type: boolean

 Default: no

 Warning: do not set this variable unless you are using a version
 of sendmail which supports the -B8BITMIME flag (such as sendmail
 8.8.x) or you may not be able to send mail.
 

-When set, Mutt will invoke $sendmail with the -B8BITMIME
+When set, Mutt will invoke $sendmail with the -B8BITMIME
 flag when sending 8-bit messages to enable ESMTP negotiation.
-
3.293. use_domain
Type: boolean

+
3.297. use_domain
Type: boolean

 Default: yes

 When set, Mutt will qualify all local addresses (ones without the
-“@host” portion) with the value of $hostname.  If unset, no
+“@host” portion) with the value of $hostname.  If unset, no
 addresses will be qualified.
-
3.294. use_envelope_from
Type: boolean

+
3.298. use_envelope_from
Type: boolean

 Default: no

 When set, mutt will set the envelope sender of the message.
-If $envelope_from_address is set, it will be used as the sender
+If $envelope_from_address is set, it will be used as the sender
 address. If unset, mutt will attempt to derive the sender from the
 “From:” header.
 

 Note that this information is passed to sendmail command using the
 -f command line switch. Therefore setting this option is not useful
-if the $sendmail variable already contains -f or if the
-executable pointed to by $sendmail doesn't support the -f switch.
-
3.295. use_from
Type: boolean

+if the $sendmail variable already contains -f or if the
+executable pointed to by $sendmail doesn't support the -f switch.
+
3.299. use_from
Type: boolean

 Default: yes

 When set, Mutt will generate the “From:” header field when
 sending messages.  If unset, no “From:” header field will be
-generated unless the user explicitly sets one using the “my_hdr”
+generated unless the user explicitly sets one using the “my_hdr”
 command.
-
3.296. use_idn
Type: boolean

+
3.300. use_idn
Type: boolean

 Default: yes

 When set, Mutt will show you international domain names decoded.
 Note: You can use IDNs for addresses even if this is unset.
 This variable only affects decoding.
-
3.297. use_ipv6
Type: boolean

+
3.301. use_ipv6
Type: boolean

 Default: yes

 When set, Mutt will look for IPv6 addresses of hosts it tries to
 contact.  If this option is unset, Mutt will restrict itself to IPv4 addresses.
 Normally, the default should work.
-
3.298. user_agent
Type: boolean

+
3.302. user_agent
Type: boolean

 Default: yes

 When set, mutt will add a “User-Agent:” header to outgoing
 messages, indicating which version of mutt was used for composing
 them.
-
3.299. visual
Type: path

+
3.303. visual
Type: path

 Default: (empty)

 Specifies the visual editor to invoke when the “˜v” command is
 given in the builtin editor.
-
3.300. wait_key
Type: boolean

+
3.304. wait_key
Type: boolean

 Default: yes

 Controls whether Mutt will ask you to press a key after an external command
 has been invoked by these functions: <shell-escape>,
@@ -6191,56 +6652,56 @@ and the external program is interactive.
 

 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.
-
3.301. weed
Type: boolean

+
3.305. weed
Type: boolean

 Default: yes

 When set, mutt will weed headers when displaying, forwarding,
 printing, or replying to messages.
-
3.302. wrap
Type: number

+
3.306. wrap
Type: number

 Default: 0

-When set to a positive value, mutt will wrap text at $wrap characters.
-When set to a negative value, mutt will wrap text so that there are $wrap
+When set to a positive value, mutt will wrap text at $wrap characters.
+When set to a negative value, mutt will wrap text so that there are $wrap
 characters of empty space on the right side of the terminal.
-
3.303. wrap_search
Type: boolean

+
3.307. wrap_search
Type: boolean

 Default: yes

 Controls whether searches wrap around the end.
 

 When set, searches will wrap around the first (or last) item. When
 unset, incremental searches will not wrap.
-
3.304. wrapmargin
Type: number

+
3.308. wrapmargin
Type: number

 Default: 0

-(DEPRECATED) Equivalent to setting $wrap with a negative value.
-
3.305. write_inc
Type: number

-Default: 10

-When writing a mailbox, a message will be printed every
-$write_inc messages to indicate progress.  If set to 0, only a
-single message will be displayed before writing a mailbox.
-

-Also see the $read_inc, $net_inc and $time_inc variables and the
-“tuning” section of the manual for performance considerations.
-
3.306. write_bcc
Type: boolean

+(DEPRECATED) Equivalent to setting $wrap with a negative value.
+
3.309. write_bcc
Type: boolean

 Default: yes

 Controls whether mutt writes out the “Bcc:” header when preparing
 messages to be sent.  Exim users may wish to unset this. If mutt
-is set to deliver directly via SMTP (see $smtp_url), this
+is set to deliver directly via SMTP (see $smtp_url), this
 option does nothing: mutt will never write out the “Bcc:” header
 in this case.
+
3.310. write_inc
Type: number

+Default: 10

+When writing a mailbox, a message will be printed every
+$write_inc messages to indicate progress.  If set to 0, only a
+single message will be displayed before writing a mailbox.
+

+Also see the $read_inc, $net_inc and $time_inc variables and the
+“tuning” section of the manual for performance considerations.
 
4. Functions

 The following is the list of available functions listed by the mapping
 in which they are available.  The default key setting is given, and an
 explanation of what the function does.  The key bindings of these
-functions can be changed with the bind
+functions can be changed with the bind
 command.
-
4.1. generic menu

+
4.1. Generic Menu

 The generic menu is not a real menu, but specifies common functions
 (such as movement) available in all menus except for pager and
 editor.  Changing settings for this menu will affect the default
 bindings for all menus (except as noted).
-
Table 8.2. Default generic function bindings
FunctionDefault keyDescription
<top-page>Hmove to the top of the page
<next-entry>jmove to the next entry
<previous-entry>kmove to the previous entry
<bottom-page>Lmove to the bottom of the page
<refresh>^Lclear and redraw the screen
<middle-page>Mmove to the middle of the page
<search-next>nsearch for next match
<exit>qexit this menu
<tag-entry>ttag the current entry
<next-page>zmove to the next page
<previous-page>Zmove to the previous page
<last-entry>*move to the last entry
<first-entry>=move to the first entry
<enter-command>:enter a muttrc command
<next-line>>scroll down one line
<previous-line><scroll up one line
<half-up>[scroll up 1/2 page
<half-down>]scroll down 1/2 page
<help>?this screen
<tag-prefix>;apply next function to tagged messages
<tag-prefix-cond> apply next function ONLY to tagged messages
<end-cond> end of conditional execution (noop)
<shell-escape>!invoke a command in a subshell
<select-entry><Return>select the current entry
<search>/search for a regular expression
<search-reverse>Esc /search backwards for a regular expression
<search-opposite> search for next match in opposite direction
<jump> jump to an index number
<current-top> move entry to top of screen
<current-middle> move entry to middle of screen
<current-bottom> move entry to bottom of screen
<what-key> display the keycode for a key press

4.2. index menu
Table 8.3. Default index function bindings
FunctionDefault keyDescription
<create-alias>acreate an alias from a message sender
<bounce-message>bremail a message to another user
<break-thread>#break the thread in two
<change-folder>copen a different folder
<change-folder-readonly>Esc copen a different folder in read only mode
<next-unread-mailbox> open next mailbox with new mail
<collapse-thread>Esc vcollapse/uncollapse current thread
<collapse-all>Esc Vcollapse/uncollapse all threads
<copy-message>Ccopy a message to a file/mailbox
<decode-copy>Esc Cmake decoded (text/plain) copy
<decode-save>Esc smake decoded copy (text/plain) and delete
<delete-message>ddelete the current entry
<delete-pattern>Ddelete messages matching a pattern
<delete-thread>^Ddelete all messages in thread
<delete-subthread>Esc ddelete all messages in subthread
<edit>eedit the raw message
<edit-type>^Eedit attachment content type
<forward-message>fforward a message with comments
<flag-message>Ftoggle a message's 'important' flag
<group-reply>greply to all recipients
<fetch-mail>Gretrieve mail from POP server
<imap-fetch-mail> force retrieval of mail from IMAP server
<display-toggle-weed>hdisplay message and toggle header weeding
<next-undeleted>jmove to the next undeleted message
<previous-undeleted>kmove to the previous undeleted message
<limit>lshow only messages matching a pattern
<link-threads>&link tagged message to the current one
<list-reply>Lreply to specified mailing list
<mail>mcompose a new mail message
<toggle-new>Ntoggle a message's 'new' flag
<toggle-write>%toggle whether the mailbox will be rewritten
<next-thread>^Njump to the next thread
<next-subthread>Esc njump to the next subthread
<query>Qquery external program for addresses
<quit>qsave changes to mailbox and quit
<reply>rreply to a message
<show-limit>Esc lshow currently active limit pattern
<sort-mailbox>osort messages
<sort-reverse>Osort messages in reverse order
<print-message>pprint the current entry
<previous-thread>^Pjump to previous thread
<previous-subthread>Esc pjump to previous subthread
<recall-message>Rrecall a postponed message
<read-thread>^Rmark the current thread as read
<read-subthread>Esc rmark the current subthread as read
<resend-message>Esc euse the current message as a template for a new one
<save-message>ssave message/attachment to a file
<tag-pattern>Ttag messages matching a pattern
<tag-subthread> tag the current subthread
<tag-thread>Esc ttag the current thread
<untag-pattern>^Tuntag messages matching a pattern
<undelete-message>uundelete the current entry
<undelete-pattern>Uundelete messages matching a pattern
<undelete-subthread>Esc uundelete all messages in subthread
<undelete-thread>^Uundelete all messages in thread
<view-attachments>vshow MIME attachments
<show-version>Vshow the Mutt version number and date
<set-flag>wset a status flag on a message
<clear-flag>Wclear a status flag from a message
<display-message><Return>display a message
<buffy-list>.list mailboxes with new mail
<sync-mailbox>$save changes to mailbox
<display-address>@display full address of sender
<pipe-message>|pipe message/attachment to a shell command
<next-new> jump to the next new message
<next-new-then-unread><Tab>jump to the next new or unread message
<previous-new> jump to the previous new message
<previous-new-then-unread>Esc <Tab>jump to the previous new or unread message
<next-unread> jump to the next unread message
<previous-unread> jump to the previous unread message
<parent-message>Pjump to parent message in thread
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory
<check-traditional-pgp>Esc Pcheck for classic PGP
<mail-key>Esc kmail a PGP public key
<decrypt-copy> make decrypted copy
<decrypt-save> make decrypted copy and delete

4.3. pager menu
Table 8.4. Default pager function bindings
FunctionDefault keyDescription
<break-thread>#break the thread in two
<create-alias>acreate an alias from a message sender
<bounce-message>bremail a message to another user
<change-folder>copen a different folder
<change-folder-readonly>Esc copen a different folder in read only mode
<next-unread-mailbox> open next mailbox with new mail
<copy-message>Ccopy a message to a file/mailbox
<decode-copy>Esc Cmake decoded (text/plain) copy
<delete-message>ddelete the current entry
<delete-thread>^Ddelete all messages in thread
<delete-subthread>Esc ddelete all messages in subthread
<edit>eedit the raw message
<edit-type>^Eedit attachment content type
<forward-message>fforward a message with comments
<flag-message>Ftoggle a message's 'important' flag
<group-reply>greply to all recipients
<imap-fetch-mail> force retrieval of mail from IMAP server
<display-toggle-weed>hdisplay message and toggle header weeding
<next-undeleted>jmove to the next undeleted message
<next-entry>Jmove to the next entry
<previous-undeleted>kmove to the previous undeleted message
<previous-entry>Kmove to the previous entry
<link-threads>&link tagged message to the current one
<list-reply>Lreply to specified mailing list
<redraw-screen>^Lclear and redraw the screen
<mail>mcompose a new mail message
<mark-as-new>Ntoggle a message's 'new' flag
<search-next>nsearch for next match
<next-thread>^Njump to the next thread
<next-subthread>Esc njump to the next subthread
<print-message>pprint the current entry
<previous-thread>^Pjump to previous thread
<previous-subthread>Esc pjump to previous subthread
<quit>Qsave changes to mailbox and quit
<exit>qexit this menu
<reply>rreply to a message
<recall-message>Rrecall a postponed message
<read-thread>^Rmark the current thread as read
<read-subthread>Esc rmark the current subthread as read
<resend-message>Esc euse the current message as a template for a new one
<save-message>ssave message/attachment to a file
<skip-quoted>Sskip beyond quoted text
<decode-save>Esc smake decoded copy (text/plain) and delete
<tag-message>ttag the current entry
<toggle-quoted>Ttoggle display of quoted text
<undelete-message>uundelete the current entry
<undelete-subthread>Esc uundelete all messages in subthread
<undelete-thread>^Uundelete all messages in thread
<view-attachments>vshow MIME attachments
<show-version>Vshow the Mutt version number and date
<search-toggle>\\toggle search pattern coloring
<display-address>@display full address of sender
<next-new> jump to the next new message
<pipe-message>|pipe message/attachment to a shell command
<help>?this screen
<next-page><Space>move to the next page
<previous-page>-move to the previous page
<top>^jump to the top of the message
<sync-mailbox>$save changes to mailbox
<shell-escape>!invoke a command in a subshell
<enter-command>:enter a muttrc command
<buffy-list>.list mailboxes with new mail
<search>/search for a regular expression
<search-reverse>Esc /search backwards for a regular expression
<search-opposite> search for next match in opposite direction
<next-line><Return>scroll down one line
<jump> jump to an index number
<next-unread> jump to the next unread message
<previous-new> jump to the previous new message
<previous-unread> jump to the previous unread message
<half-up> scroll up 1/2 page
<half-down> scroll down 1/2 page
<previous-line> scroll up one line
<bottom> jump to the bottom of the message
<parent-message>Pjump to parent message in thread
<check-traditional-pgp>Esc Pcheck for classic PGP
<mail-key>Esc kmail a PGP public key
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory
<decrypt-copy> make decrypted copy
<decrypt-save> make decrypted copy and delete
<what-key> display the keycode for a key press

4.4. alias menu
Table 8.5. Default alias function bindings
FunctionDefault keyDescription
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry

4.5. query menu
Table 8.6. Default query function bindings
FunctionDefault keyDescription
<create-alias>acreate an alias from a message sender
<mail>mcompose a new mail message
<query>Qquery external program for addresses
<query-append>Aappend new query results to current results

4.6. attach menu
Table 8.7. Default attach function bindings
FunctionDefault keyDescription
<bounce-message>bremail a message to another user
<display-toggle-weed>hdisplay message and toggle header weeding
<edit-type>^Eedit attachment content type
<print-entry>pprint the current entry
<save-entry>ssave message/attachment to a file
<pipe-entry>|pipe message/attachment to a shell command
<view-mailcap>mforce viewing of attachment using mailcap
<reply>rreply to a message
<resend-message>Esc euse the current message as a template for a new one
<group-reply>greply to all recipients
<list-reply>Lreply to specified mailing list
<forward-message>fforward a message with comments
<view-text>Tview attachment as text
<view-attach><Return>view attachment using mailcap entry if necessary
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry
<collapse-parts>vToggle display of subparts
<check-traditional-pgp>Esc Pcheck for classic PGP
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory

4.7. compose menu
Table 8.8. Default compose function bindings
FunctionDefault keyDescription
<attach-file>aattach file(s) to this message
<attach-message>Aattach message(s) to this message
<edit-bcc>bedit the BCC list
<edit-cc>cedit the CC list
<copy-file>Csave message/attachment to a file
<detach-file>Ddelete the current entry
<toggle-disposition>^Dtoggle disposition between inline/attachment
<edit-description>dedit attachment description
<edit-message>eedit the message
<edit-headers>Eedit the message with headers
<edit-file>^X eedit the file to be attached
<edit-encoding>^Eedit attachment transfer-encoding
<edit-from>Esc fedit the from field
<edit-fcc>fenter a file to save a copy of this message in
<filter-entry>Ffilter attachment through a shell command
<get-attachment>Gget a temporary copy of an attachment
<display-toggle-weed>hdisplay message and toggle header weeding
<ispell>irun ispell on the message
<print-entry>lprint the current entry
<edit-mime>medit attachment using mailcap entry
<new-mime>ncompose new attachment using mailcap entry
<postpone-message>Psave this message to send later
<edit-reply-to>redit the Reply-To field
<rename-file>Rrename/move an attached file
<edit-subject>sedit the subject of this message
<edit-to>tedit the TO list
<edit-type>^Tedit attachment content type
<write-fcc>wwrite the message to a folder
<toggle-unlink>utoggle whether to delete file after sending it
<toggle-recode> toggle recoding of this attachment
<update-encoding>Uupdate an attachment's encoding info
<view-attach><Return>view attachment using mailcap entry if necessary
<send-message>ysend the message
<pipe-entry>|pipe message/attachment to a shell command
<attach-key>Esc kattach a PGP public key
<pgp-menu>pshow PGP options
<forget-passphrase>^Fwipe passphrase(s) from memory
<smime-menu>Sshow S/MIME options
<mix>Msend the message through a mixmaster remailer chain

4.8. postpone menu
Table 8.9. Default postpone function bindings
FunctionDefault keyDescription
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry

4.9. browser menu
Table 8.10. Default browser function bindings
FunctionDefault keyDescription
<change-dir>cchange directories
<display-filename>@display the currently selected file's name
<enter-mask>menter a file mask
<sort>osort messages
<sort-reverse>Osort messages in reverse order
<select-new>Nselect a new file in this directory
<check-new> check mailboxes for new mail
<toggle-mailboxes><Tab>toggle whether to browse mailboxes or all files
<view-file><Space>view file
<buffy-list>.list mailboxes with new mail
<create-mailbox>Ccreate a new mailbox (IMAP only)
<delete-mailbox>ddelete the current mailbox (IMAP only)
<rename-mailbox>rrename the current mailbox (IMAP only)
<subscribe>ssubscribe to current mailbox (IMAP only)
<unsubscribe>uunsubscribe from current mailbox (IMAP only)
<toggle-subscribed>Ttoggle view all/subscribed mailboxes (IMAP only)

4.10. pgp menu
Table 8.11. Default pgp function bindings
FunctionDefault keyDescription
<verify-key>cverify a PGP public key
<view-name>%view the key's user id

4.11. smime menu
Table 8.12. Default smime function bindings
FunctionDefault keyDescription
<verify-key>cverify a PGP public key
<view-name>%view the key's user id

4.12. mix menu
Table 8.13. Default mix function bindings
FunctionDefault keyDescription
<accept><Return>Accept the chain constructed
<append>aAppend a remailer to the chain
<insert>iInsert a remailer into the chain
<delete>dDelete a remailer from the chain
<chain-prev><Left>Select the previous element of the chain
<chain-next><Right>Select the next element of the chain

4.13. editor menu
Table 8.14. Default editor function bindings
FunctionDefault keyDescription
<bol>^Ajump to the beginning of the line
<backward-char>^Bmove the cursor one character to the left
<backward-word>Esc bmove the cursor to the beginning of the word
<capitalize-word>Esc ccapitalize the word
<downcase-word>Esc lconvert the word to lower case
<upcase-word>Esc uconvert the word to upper case
<delete-char>^Ddelete the char under the cursor
<eol>^Ejump to the end of the line
<forward-char>^Fmove the cursor one character to the right
<forward-word>Esc fmove the cursor to the end of the word
<backspace><Backspace>delete the char in front of the cursor
<kill-eol>^Kdelete chars from cursor to end of line
<kill-eow>Esc ddelete chars from the cursor to the end of the word
<kill-line>^Udelete all chars on the line
<quote-char>^Vquote the next typed key
<kill-word>^Wdelete the word in front of the cursor
<complete><Tab>complete filename or alias
<complete-query>^Tcomplete address with query
<buffy-cycle><Space>cycle among incoming mailboxes
<history-up> scroll up through the history list
<history-down> scroll down through the history list
<transpose-chars> transpose character under cursor with previous

Chapter 9. Miscellany
Table of Contents
1. Acknowledgements
2. About this document
1. Acknowledgements

+
Table 9.2. Default generic Function Bindings
FunctionDefault keyDescription
<top-page>Hmove to the top of the page
<next-entry>jmove to the next entry
<previous-entry>kmove to the previous entry
<bottom-page>Lmove to the bottom of the page
<refresh>^Lclear and redraw the screen
<middle-page>Mmove to the middle of the page
<search-next>nsearch for next match
<exit>qexit this menu
<tag-entry>ttag the current entry
<next-page>zmove to the next page
<previous-page>Zmove to the previous page
<last-entry>*move to the last entry
<first-entry>=move to the first entry
<enter-command>:enter a muttrc command
<next-line>>scroll down one line
<previous-line><scroll up one line
<half-up>[scroll up 1/2 page
<half-down>]scroll down 1/2 page
<help>?this screen
<tag-prefix>;apply next function to tagged messages
<tag-prefix-cond> apply next function ONLY to tagged messages
<end-cond> end of conditional execution (noop)
<shell-escape>!invoke a command in a subshell
<select-entry><Return>select the current entry
<search>/search for a regular expression
<search-reverse>Esc /search backwards for a regular expression
<search-opposite> search for next match in opposite direction
<jump> jump to an index number
<current-top> move entry to top of screen
<current-middle> move entry to middle of screen
<current-bottom> move entry to bottom of screen
<what-key> display the keycode for a key press

4.2. Index Menu
Table 9.3. Default index Function Bindings
FunctionDefault keyDescription
<create-alias>acreate an alias from a message sender
<bounce-message>bremail a message to another user
<break-thread>#break the thread in two
<change-folder>copen a different folder
<change-folder-readonly>Esc copen a different folder in read only mode
<next-unread-mailbox> open next mailbox with new mail
<collapse-thread>Esc vcollapse/uncollapse current thread
<collapse-all>Esc Vcollapse/uncollapse all threads
<copy-message>Ccopy a message to a file/mailbox
<decode-copy>Esc Cmake decoded (text/plain) copy
<decode-save>Esc smake decoded copy (text/plain) and delete
<delete-message>ddelete the current entry
<delete-pattern>Ddelete messages matching a pattern
<delete-thread>^Ddelete all messages in thread
<delete-subthread>Esc ddelete all messages in subthread
<edit>eedit the raw message
<edit-type>^Eedit attachment content type
<forward-message>fforward a message with comments
<flag-message>Ftoggle a message's 'important' flag
<group-reply>greply to all recipients
<fetch-mail>Gretrieve mail from POP server
<imap-fetch-mail> force retrieval of mail from IMAP server
<display-toggle-weed>hdisplay message and toggle header weeding
<next-undeleted>jmove to the next undeleted message
<previous-undeleted>kmove to the previous undeleted message
<limit>lshow only messages matching a pattern
<link-threads>&link tagged message to the current one
<list-reply>Lreply to specified mailing list
<mail>mcompose a new mail message
<toggle-new>Ntoggle a message's 'new' flag
<toggle-write>%toggle whether the mailbox will be rewritten
<next-thread>^Njump to the next thread
<next-subthread>Esc njump to the next subthread
<query>Qquery external program for addresses
<quit>qsave changes to mailbox and quit
<reply>rreply to a message
<show-limit>Esc lshow currently active limit pattern
<sort-mailbox>osort messages
<sort-reverse>Osort messages in reverse order
<print-message>pprint the current entry
<previous-thread>^Pjump to previous thread
<previous-subthread>Esc pjump to previous subthread
<recall-message>Rrecall a postponed message
<read-thread>^Rmark the current thread as read
<read-subthread>Esc rmark the current subthread as read
<resend-message>Esc euse the current message as a template for a new one
<save-message>ssave message/attachment to a mailbox/file
<tag-pattern>Ttag messages matching a pattern
<tag-subthread> tag the current subthread
<tag-thread>Esc ttag the current thread
<untag-pattern>^Tuntag messages matching a pattern
<undelete-message>uundelete the current entry
<undelete-pattern>Uundelete messages matching a pattern
<undelete-subthread>Esc uundelete all messages in subthread
<undelete-thread>^Uundelete all messages in thread
<view-attachments>vshow MIME attachments
<show-version>Vshow the Mutt version number and date
<set-flag>wset a status flag on a message
<clear-flag>Wclear a status flag from a message
<display-message><Return>display a message
<buffy-list>.list mailboxes with new mail
<sync-mailbox>$save changes to mailbox
<display-address>@display full address of sender
<pipe-message>|pipe message/attachment to a shell command
<next-new> jump to the next new message
<next-new-then-unread><Tab>jump to the next new or unread message
<previous-new> jump to the previous new message
<previous-new-then-unread>Esc <Tab>jump to the previous new or unread message
<next-unread> jump to the next unread message
<previous-unread> jump to the previous unread message
<parent-message>Pjump to parent message in thread
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory
<check-traditional-pgp>Esc Pcheck for classic PGP
<mail-key>Esc kmail a PGP public key
<decrypt-copy> make decrypted copy
<decrypt-save> make decrypted copy and delete

4.3. Pager Menu
Table 9.4. Default pager Function Bindings
FunctionDefault keyDescription
<break-thread>#break the thread in two
<create-alias>acreate an alias from a message sender
<bounce-message>bremail a message to another user
<change-folder>copen a different folder
<change-folder-readonly>Esc copen a different folder in read only mode
<next-unread-mailbox> open next mailbox with new mail
<copy-message>Ccopy a message to a file/mailbox
<decode-copy>Esc Cmake decoded (text/plain) copy
<delete-message>ddelete the current entry
<delete-thread>^Ddelete all messages in thread
<delete-subthread>Esc ddelete all messages in subthread
<set-flag>wset a status flag on a message
<clear-flag>Wclear a status flag from a message
<edit>eedit the raw message
<edit-type>^Eedit attachment content type
<forward-message>fforward a message with comments
<flag-message>Ftoggle a message's 'important' flag
<group-reply>greply to all recipients
<imap-fetch-mail> force retrieval of mail from IMAP server
<display-toggle-weed>hdisplay message and toggle header weeding
<next-undeleted>jmove to the next undeleted message
<next-entry>Jmove to the next entry
<previous-undeleted>kmove to the previous undeleted message
<previous-entry>Kmove to the previous entry
<link-threads>&link tagged message to the current one
<list-reply>Lreply to specified mailing list
<redraw-screen>^Lclear and redraw the screen
<mail>mcompose a new mail message
<mark-as-new>Ntoggle a message's 'new' flag
<search-next>nsearch for next match
<next-thread>^Njump to the next thread
<next-subthread>Esc njump to the next subthread
<print-message>pprint the current entry
<previous-thread>^Pjump to previous thread
<previous-subthread>Esc pjump to previous subthread
<quit>Qsave changes to mailbox and quit
<exit>qexit this menu
<reply>rreply to a message
<recall-message>Rrecall a postponed message
<read-thread>^Rmark the current thread as read
<read-subthread>Esc rmark the current subthread as read
<resend-message>Esc euse the current message as a template for a new one
<save-message>ssave message/attachment to a mailbox/file
<skip-quoted>Sskip beyond quoted text
<decode-save>Esc smake decoded copy (text/plain) and delete
<tag-message>ttag the current entry
<toggle-quoted>Ttoggle display of quoted text
<undelete-message>uundelete the current entry
<undelete-subthread>Esc uundelete all messages in subthread
<undelete-thread>^Uundelete all messages in thread
<view-attachments>vshow MIME attachments
<show-version>Vshow the Mutt version number and date
<search-toggle>\\toggle search pattern coloring
<display-address>@display full address of sender
<next-new> jump to the next new message
<pipe-message>|pipe message/attachment to a shell command
<help>?this screen
<next-page><Space>move to the next page
<previous-page>-move to the previous page
<top>^jump to the top of the message
<sync-mailbox>$save changes to mailbox
<shell-escape>!invoke a command in a subshell
<enter-command>:enter a muttrc command
<buffy-list>.list mailboxes with new mail
<search>/search for a regular expression
<search-reverse>Esc /search backwards for a regular expression
<search-opposite> search for next match in opposite direction
<next-line><Return>scroll down one line
<jump> jump to an index number
<next-unread> jump to the next unread message
<previous-new> jump to the previous new message
<previous-unread> jump to the previous unread message
<half-up> scroll up 1/2 page
<half-down> scroll down 1/2 page
<previous-line> scroll up one line
<bottom> jump to the bottom of the message
<parent-message>Pjump to parent message in thread
<check-traditional-pgp>Esc Pcheck for classic PGP
<mail-key>Esc kmail a PGP public key
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory
<decrypt-copy> make decrypted copy
<decrypt-save> make decrypted copy and delete
<what-key> display the keycode for a key press

4.4. Alias Menu
Table 9.5. Default alias Function Bindings
FunctionDefault keyDescription
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry

4.5. Query Menu
Table 9.6. Default query Function Bindings
FunctionDefault keyDescription
<create-alias>acreate an alias from a message sender
<mail>mcompose a new mail message
<query>Qquery external program for addresses
<query-append>Aappend new query results to current results

4.6. Attach Menu
Table 9.7. Default attach Function Bindings
FunctionDefault keyDescription
<bounce-message>bremail a message to another user
<display-toggle-weed>hdisplay message and toggle header weeding
<edit-type>^Eedit attachment content type
<print-entry>pprint the current entry
<save-entry>ssave message/attachment to a mailbox/file
<pipe-entry>|pipe message/attachment to a shell command
<view-mailcap>mforce viewing of attachment using mailcap
<reply>rreply to a message
<resend-message>Esc euse the current message as a template for a new one
<group-reply>greply to all recipients
<list-reply>Lreply to specified mailing list
<forward-message>fforward a message with comments
<view-text>Tview attachment as text
<view-attach><Return>view attachment using mailcap entry if necessary
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry
<collapse-parts>vToggle display of subparts
<check-traditional-pgp>Esc Pcheck for classic PGP
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory

4.7. Compose Menu
Table 9.8. Default compose Function Bindings
FunctionDefault keyDescription
<attach-file>aattach file(s) to this message
<attach-message>Aattach message(s) to this message
<edit-bcc>bedit the BCC list
<edit-cc>cedit the CC list
<copy-file>Csave message/attachment to a mailbox/file
<detach-file>Ddelete the current entry
<toggle-disposition>^Dtoggle disposition between inline/attachment
<edit-description>dedit attachment description
<edit-message>eedit the message
<edit-headers>Eedit the message with headers
<edit-file>^X eedit the file to be attached
<edit-encoding>^Eedit attachment transfer-encoding
<edit-from>Esc fedit the from field
<edit-fcc>fenter a file to save a copy of this message in
<filter-entry>Ffilter attachment through a shell command
<get-attachment>Gget a temporary copy of an attachment
<display-toggle-weed>hdisplay message and toggle header weeding
<ispell>irun ispell on the message
<print-entry>lprint the current entry
<edit-mime>medit attachment using mailcap entry
<new-mime>ncompose new attachment using mailcap entry
<postpone-message>Psave this message to send later
<edit-reply-to>redit the Reply-To field
<rename-file>Rrename/move an attached file
<edit-subject>sedit the subject of this message
<edit-to>tedit the TO list
<edit-type>^Tedit attachment content type
<write-fcc>wwrite the message to a folder
<toggle-unlink>utoggle whether to delete file after sending it
<toggle-recode> toggle recoding of this attachment
<update-encoding>Uupdate an attachment's encoding info
<view-attach><Return>view attachment using mailcap entry if necessary
<send-message>ysend the message
<pipe-entry>|pipe message/attachment to a shell command
<attach-key>Esc kattach a PGP public key
<pgp-menu>pshow PGP options
<forget-passphrase>^Fwipe passphrase(s) from memory
<smime-menu>Sshow S/MIME options
<mix>Msend the message through a mixmaster remailer chain

4.8. Postpone Menu
Table 9.9. Default postpone Function Bindings
FunctionDefault keyDescription
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry

4.9. Browser Menu
Table 9.10. Default browser Function Bindings
FunctionDefault keyDescription
<change-dir>cchange directories
<display-filename>@display the currently selected file's name
<enter-mask>menter a file mask
<sort>osort messages
<sort-reverse>Osort messages in reverse order
<select-new>Nselect a new file in this directory
<check-new> check mailboxes for new mail
<toggle-mailboxes><Tab>toggle whether to browse mailboxes or all files
<view-file><Space>view file
<buffy-list>.list mailboxes with new mail
<create-mailbox>Ccreate a new mailbox (IMAP only)
<delete-mailbox>ddelete the current mailbox (IMAP only)
<rename-mailbox>rrename the current mailbox (IMAP only)
<subscribe>ssubscribe to current mailbox (IMAP only)
<unsubscribe>uunsubscribe from current mailbox (IMAP only)
<toggle-subscribed>Ttoggle view all/subscribed mailboxes (IMAP only)

4.10. Pgp Menu
Table 9.11. Default pgp Function Bindings
FunctionDefault keyDescription
<verify-key>cverify a PGP public key
<view-name>%view the key's user id

4.11. Smime Menu
Table 9.12. Default smime Function Bindings
FunctionDefault keyDescription
<verify-key>cverify a PGP public key
<view-name>%view the key's user id

4.12. Mix Menu
Table 9.13. Default mix Function Bindings
FunctionDefault keyDescription
<accept><Return>Accept the chain constructed
<append>aAppend a remailer to the chain
<insert>iInsert a remailer into the chain
<delete>dDelete a remailer from the chain
<chain-prev><Left>Select the previous element of the chain
<chain-next><Right>Select the next element of the chain

4.13. Editor Menu
Table 9.14. Default editor Function Bindings
FunctionDefault keyDescription
<bol>^Ajump to the beginning of the line
<backward-char>^Bmove the cursor one character to the left
<backward-word>Esc bmove the cursor to the beginning of the word
<capitalize-word>Esc ccapitalize the word
<downcase-word>Esc lconvert the word to lower case
<upcase-word>Esc uconvert the word to upper case
<delete-char>^Ddelete the char under the cursor
<eol>^Ejump to the end of the line
<forward-char>^Fmove the cursor one character to the right
<forward-word>Esc fmove the cursor to the end of the word
<backspace><Backspace>delete the char in front of the cursor
<kill-eol>^Kdelete chars from cursor to end of line
<kill-eow>Esc ddelete chars from the cursor to the end of the word
<kill-line>^Udelete all chars on the line
<quote-char>^Vquote the next typed key
<kill-word>^Wdelete the word in front of the cursor
<complete><Tab>complete filename or alias
<complete-query>^Tcomplete address with query
<buffy-cycle><Space>cycle among incoming mailboxes
<history-up> scroll up through the history list
<history-down> scroll down through the history list
<transpose-chars> transpose character under cursor with previous

Chapter 10. Miscellany
Table of Contents
1. Acknowledgements
2. About This Document
1. Acknowledgements

 Kari Hurtta 
 co-developed the original MIME parsing code back in the ELM-ME days.
 

 The following people have been very helpful to the development of Mutt:
-
2. About this document

+
2. About This Document

 This document was written in DocBook,
 and then rendered using the Gnome XSLT toolkit.
 

diff --git a/doc/manual.txt b/doc/manual.txt
index 1a01e39..668b97c 100644
--- a/doc/manual.txt
+++ b/doc/manual.txt
@@ -4,11 +4,11 @@ Michael Elkins
 
 
 
-version 1.5.19 (2009-01-05)
+version 1.5.20 (2009-06-14)
 
 Abstract
 
-?All mail clients suck. This one just sucks less.? -me, circa 1995
+?All mail clients suck. This one just sucks less.? ? me, circa 1995
 
 -------------------------------------------------------------------------------
 
@@ -18,77 +18,93 @@ Table of Contents
 
     1. Mutt Home Page
     2. Mailing Lists
-    3. Software Distribution Sites
-    4. Mutt online resources
+    3. Getting Mutt
+    4. Mutt Online Resources
     5. Contributing to Mutt
-    6. Typograhical conventions
+    6. Typograhical Conventions
     7. Copyright
 
 2. Getting Started
 
-    1. Core concepts
-    2. Moving Around in Menus
-    3. Editing Input Fields
+    1. Core Concepts
+    2. Screens and Menus
 
-        3.1. Introduction
-        3.2. History
+        2.1. Index
+        2.2. Pager
+        2.3. File Browser
+        2.4. Help
+        2.5. Compose Menu
+        2.6. Alias Menu
+        2.7. Attachment Menu
 
-    4. Reading Mail - The Index and Pager
+    3. Moving Around in Menus
+    4. Editing Input Fields
 
-        4.1. The Message Index
-        4.2. The Pager
-        4.3. Threaded Mode
-        4.4. Miscellaneous Functions
+        4.1. Introduction
+        4.2. History
 
-    5. Sending Mail
+    5. Reading Mail
 
-        5.1. Introduction
-        5.2. Editing the message header
-        5.3. Sending cryptographically signed/encrypted messages
-        5.4. Sending anonymous messages via mixmaster
-        5.5. Sending format=flowed messages
+        5.1. The Message Index
+        5.2. The Pager
+        5.3. Threaded Mode
+        5.4. Miscellaneous Functions
 
-    6. Forwarding and Bouncing Mail
-    7. Postponing Mail
+    6. Sending Mail
+
+        6.1. Introduction
+        6.2. Editing the Message Header
+        6.3. Sending Cryptographically Signed/Encrypted Messages
+        6.4. Sending Format=Flowed Messages
+
+    7. Forwarding and Bouncing Mail
+    8. Postponing Mail
 
 3. Configuration
 
-    1. Location of initialization files
+    1. Location of Initialization Files
     2. Syntax of Initialization Files
-    3. Address groups
-    4. Defining/Using aliases
-    5. Changing the default key bindings
-    6. Defining aliases for character sets
-    7. Setting variables based upon mailbox
-    8. Keyboard macros
-    9. Using color and mono video attributes
-    10. Message header display
-    11. Alternative addresses
-    12. Mailing lists
-    13. Using Multiple spool mailboxes
-    14. Monitoring incoming mail
-    15. User defined headers
-    16. Specify default save mailbox
-    17. Specify default Fcc: mailbox when composing
-    18. Specify default save filename and default Fcc: mailbox at once
-    19. Change settings based upon message recipients
-    20. Change settings before formatting a message
-    21. Choosing the cryptographic key of the recipient
-    22. Adding key sequences to the keyboard buffer
-    23. Executing functions
+    3. Address Groups
+    4. Defining/Using Aliases
+    5. Changing the Default Key Bindings
+    6. Defining Aliases for Character Sets
+    7. Setting Variables Based Upon Mailbox
+    8. Keyboard Macros
+    9. Using Color and Mono Video Attributes
+    10. Message Header Display
+
+        10.1. Selecting Headers
+        10.2. Ordering Displayed Headers
+
+    11. Alternative Addresses
+    12. Mailing Lists
+    13. Using Multiple Spool Mailboxes
+    14. Monitoring Incoming Mail
+    15. User-Defined Headers
+    16. Specify Default Save Mailbox
+    17. Specify Default Fcc: Mailbox When Composing
+    18. Specify Default Save Filename and Default Fcc: Mailbox at Once
+    19. Change Settings Based Upon Message Recipients
+    20. Change Settings Before Formatting a Message
+    21. Choosing the Cryptographic Key of the Recipient
+    22. Adding Key Sequences to the Keyboard Buffer
+    23. Executing Functions
     24. Message Scoring
-    25. Spam detection
+    25. Spam Detection
     26. Setting and Querying Variables
 
-        26.1. Commands
-        26.2. User-defined variables
+        26.1. Variable Types
+        26.2. Commands
+        26.3. User-Defined Variables
 
-    27. Reading initialization commands from another file
-    28. Removing hooks
+    27. Reading Initialization Commands From Another File
+    28. Removing Hooks
     29. Format Strings
 
         29.1. Basic usage
-        29.2. Filters
+        29.2. Conditionals
+        29.3. Filters
+        29.4. Padding
 
 4. Advanced Usage
 
@@ -96,8 +112,8 @@ Table of Contents
     2. Patterns: Searching, Limiting and Tagging
 
         2.1. Pattern Modifier
-        2.2. Simple Patterns
-        2.3. Complex Patterns
+        2.2. Simple Searches
+        2.3. Nesting and Boolean Operators
         2.4. Searching by Date
 
     3. Using Tags
@@ -110,70 +126,83 @@ Table of Contents
     7. Mailbox Shortcuts
     8. Handling Mailing Lists
     9. Handling multiple folders
-    10. Editing threads
+    10. Editing Threads
 
-        10.1. Linking threads
-        10.2. Breaking threads
+        10.1. Linking Threads
+        10.2. Breaking Threads
 
     11. Delivery Status Notification (DSN) Support
     12. Start a WWW Browser on URLs
+    13. Miscellany
 
 5. Mutt's MIME Support
 
     1. Using MIME in Mutt
 
-        1.1. Viewing MIME messages in the pager
+        1.1. Viewing MIME Messages in the Pager
         1.2. The Attachment Menu
         1.3. The Compose Menu
 
-    2. MIME Type configuration with mime.types
-    3. MIME Viewer configuration with mailcap
+    2. MIME Type Configuration with mime.types
+    3. MIME Viewer Configuration with Mailcap
 
-        3.1. The Basics of the mailcap file
-        3.2. Secure use of mailcap
-        3.3. Advanced mailcap Usage
-        3.4. Example mailcap files
+        3.1. The Basics of the Mailcap File
+        3.2. Secure Use of Mailcap
+        3.3. Advanced Mailcap Usage
+        3.4. Example Mailcap Files
 
     4. MIME Autoview
     5. MIME Multipart/Alternative
     6. Attachment Searching and Counting
     7. MIME Lookup
 
-6. Optional features
+6. Optional Features
 
-    1. General notes
+    1. General Notes
 
-        1.1. Enabling/disabling features
-        1.2. URL syntax
+        1.1. Enabling/Disabling Features
+        1.2. URL Syntax
 
     2. SSL/TLS Support
     3. POP3 Support
     4. IMAP Support
 
-        4.1. The Folder Browser
+        4.1. The IMAP Folder Browser
         4.2. Authentication
 
     5. SMTP Support
-    6. Managing multiple accounts
-    7. Local caching
+    6. Managing Multiple Accounts
+    7. Local Caching
 
-        7.1. Header caching
-        7.2. Body caching
+        7.1. Header Caching
+        7.2. Body Caching
         7.3. Maintenance
 
-    8. Exact address generation
+    8. Exact Address Generation
+    9. Sending Anonymous Messages via Mixmaster
+
+7. Security Considerations
+
+    1. Passwords
+    2. Temporary Files
+    3. Information Leaks
 
-7. Performance tuning
+        3.1. Message-Id: headers
+        3.2. mailto:-style Links
 
-    1. Reading and writing mailboxes
-    2. Reading messages from remote folders
-    3. Searching and limiting
+    4. External Applications
 
-8. Reference
+8. Performance Tuning
 
-    1. Command line options
+    1. Reading and Writing Mailboxes
+    2. Reading Messages from Remote Folders
+    3. Searching and Limiting
+
+9. Reference
+
+    1. Command-Line Options
     2. Configuration Commands
-    3. Configuration variables
+    3. Configuration Variables
 
         3.1. abort_nosubject
         3.2. abort_unmodified
@@ -191,18 +220,18 @@ Table of Contents
         3.14. attach_sep
         3.15. attach_split
         3.16. attribution
-        3.17. autoedit
-        3.18. auto_tag
+        3.17. auto_tag
+        3.18. autoedit
         3.19. beep
         3.20. beep_new
         3.21. bounce
         3.22. bounce_delivered
         3.23. braille_friendly
-        3.24. check_mbox_size
+        3.24. certificate_file
         3.25. charset
-        3.26. check_new
-        3.27. collapse_unread
-        3.28. uncollapse_jump
+        3.26. check_mbox_size
+        3.27. check_new
+        3.28. collapse_unread
         3.29. compose_format
         3.30. config_charset
         3.31. confirmappend
@@ -210,314 +239,319 @@ Table of Contents
         3.33. connect_timeout
         3.34. content_type
         3.35. copy
-        3.36. crypt_use_gpgme
-        3.37. crypt_use_pka
-        3.38. crypt_autopgp
+        3.36. crypt_autoencrypt
+        3.37. crypt_autopgp
+        3.38. crypt_autosign
         3.39. crypt_autosmime
-        3.40. date_format
-        3.41. default_hook
-        3.42. delete
-        3.43. delete_untag
-        3.44. digest_collapse
-        3.45. display_filter
-        3.46. dotlock_program
-        3.47. dsn_notify
-        3.48. dsn_return
-        3.49. duplicate_threads
-        3.50. edit_headers
-        3.51. editor
-        3.52. encode_from
-        3.53. envelope_from_address
-        3.54. escape
-        3.55. fast_reply
-        3.56. fcc_attach
-        3.57. fcc_clear
-        3.58. folder
-        3.59. folder_format
-        3.60. followup_to
-        3.61. force_name
-        3.62. forward_decode
-        3.63. forward_edit
-        3.64. forward_format
-        3.65. forward_quote
-        3.66. from
-        3.67. gecos_mask
-        3.68. hdrs
-        3.69. header
-        3.70. help
-        3.71. hidden_host
-        3.72. hide_limited
-        3.73. hide_missing
-        3.74. hide_thread_subject
-        3.75. hide_top_limited
-        3.76. hide_top_missing
-        3.77. history
-        3.78. history_file
-        3.79. honor_followup_to
-        3.80. hostname
-        3.81. ignore_linear_white_space
-        3.82. ignore_list_reply_to
-        3.83. imap_authenticators
-        3.84. imap_check_subscribed
-        3.85. imap_delim_chars
-        3.86. imap_headers
-        3.87. imap_idle
-        3.88. imap_keepalive
-        3.89. imap_list_subscribed
-        3.90. imap_login
-        3.91. imap_pass
-        3.92. imap_passive
-        3.93. imap_peek
-        3.94. imap_pipeline_depth
-        3.95. imap_servernoise
-        3.96. imap_user
-        3.97. implicit_autoview
-        3.98. include
-        3.99. include_onlyfirst
-        3.100. indent_string
-        3.101. index_format
-        3.102. ispell
-        3.103. keep_flagged
-        3.104. locale
-        3.105. mail_check
-        3.106. mailcap_path
-        3.107. mailcap_sanitize
-        3.108. header_cache
-        3.109. maildir_header_cache_verify
-        3.110. header_cache_pagesize
-        3.111. header_cache_compress
-        3.112. maildir_trash
-        3.113. mark_old
-        3.114. markers
-        3.115. mask
-        3.116. mbox
-        3.117. mbox_type
-        3.118. metoo
-        3.119. menu_context
-        3.120. menu_move_off
-        3.121. menu_scroll
-        3.122. meta_key
-        3.123. mh_purge
-        3.124. mh_seq_flagged
-        3.125. mh_seq_replied
-        3.126. mh_seq_unseen
-        3.127. mime_forward
-        3.128. mime_forward_decode
-        3.129. mime_forward_rest
-        3.130. mix_entry_format
-        3.131. mixmaster
-        3.132. move
-        3.133. message_cachedir
-        3.134. message_cache_clean
-        3.135. message_format
-        3.136. narrow_tree
-        3.137. net_inc
-        3.138. pager
-        3.139. pager_context
-        3.140. pager_format
-        3.141. pager_index_lines
-        3.142. pager_stop
-        3.143. crypt_autosign
-        3.144. crypt_autoencrypt
-        3.145. pgp_ignore_subkeys
-        3.146. crypt_replyencrypt
-        3.147. crypt_replysign
-        3.148. crypt_replysignencrypted
-        3.149. crypt_timestamp
-        3.150. pgp_use_gpg_agent
-        3.151. crypt_verify_sig
-        3.152. smime_is_default
-        3.153. smime_ask_cert_label
-        3.154. smime_decrypt_use_default_key
-        3.155. pgp_entry_format
-        3.156. pgp_good_sign
-        3.157. pgp_check_exit
-        3.158. pgp_long_ids
-        3.159. pgp_retainable_sigs
-        3.160. pgp_autoinline
-        3.161. pgp_replyinline
-        3.162. pgp_show_unusable
-        3.163. pgp_sign_as
-        3.164. pgp_strict_enc
-        3.165. pgp_timeout
-        3.166. pgp_sort_keys
-        3.167. pgp_mime_auto
-        3.168. pgp_auto_decode
-        3.169. pgp_decode_command
-        3.170. pgp_getkeys_command
-        3.171. pgp_verify_command
-        3.172. pgp_decrypt_command
-        3.173. pgp_clearsign_command
-        3.174. pgp_sign_command
-        3.175. pgp_encrypt_sign_command
-        3.176. pgp_encrypt_only_command
-        3.177. pgp_import_command
-        3.178. pgp_export_command
-        3.179. pgp_verify_key_command
-        3.180. pgp_list_secring_command
-        3.181. pgp_list_pubring_command
-        3.182. forward_decrypt
-        3.183. smime_timeout
-        3.184. smime_encrypt_with
-        3.185. smime_keys
-        3.186. smime_ca_location
-        3.187. smime_certificates
-        3.188. smime_decrypt_command
-        3.189. smime_verify_command
-        3.190. smime_verify_opaque_command
-        3.191. smime_sign_command
-        3.192. smime_sign_opaque_command
-        3.193. smime_encrypt_command
-        3.194. smime_pk7out_command
-        3.195. smime_get_cert_command
-        3.196. smime_get_signer_cert_command
-        3.197. smime_import_cert_command
-        3.198. smime_get_cert_email_command
-        3.199. smime_default_key
-        3.200. ssl_client_cert
-        3.201. ssl_force_tls
-        3.202. ssl_starttls
-        3.203. certificate_file
-        3.204. ssl_usesystemcerts
-        3.205. entropy_file
-        3.206. ssl_use_sslv2
-        3.207. ssl_use_sslv3
-        3.208. ssl_use_tlsv1
-        3.209. ssl_min_dh_prime_bits
-        3.210. ssl_ca_certificates_file
-        3.211. pipe_split
-        3.212. pipe_decode
-        3.213. pipe_sep
-        3.214. pop_authenticators
-        3.215. pop_auth_try_all
-        3.216. pop_checkinterval
-        3.217. pop_delete
-        3.218. pop_host
-        3.219. pop_last
-        3.220. pop_reconnect
-        3.221. pop_user
-        3.222. pop_pass
-        3.223. post_indent_string
-        3.224. postpone
-        3.225. postponed
-        3.226. preconnect
-        3.227. print
-        3.228. print_command
-        3.229. print_decode
-        3.230. print_split
-        3.231. prompt_after
-        3.232. query_command
-        3.233. query_format
-        3.234. quit
-        3.235. quote_regexp
-        3.236. read_inc
-        3.237. read_only
-        3.238. realname
-        3.239. recall
-        3.240. record
-        3.241. reply_regexp
-        3.242. reply_self
-        3.243. reply_to
-        3.244. resolve
-        3.245. reverse_alias
-        3.246. reverse_name
-        3.247. reverse_realname
-        3.248. rfc2047_parameters
-        3.249. save_address
-        3.250. save_empty
-        3.251. save_history
-        3.252. save_name
-        3.253. score
-        3.254. score_threshold_delete
-        3.255. score_threshold_flag
-        3.256. score_threshold_read
-        3.257. send_charset
-        3.258. sendmail
-        3.259. sendmail_wait
-        3.260. shell
-        3.261. sig_dashes
-        3.262. sig_on_top
-        3.263. signature
-        3.264. simple_search
-        3.265. smart_wrap
-        3.266. smileys
-        3.267. sleep_time
-        3.268. smtp_authenticators
-        3.269. smtp_pass
-        3.270. smtp_url
-        3.271. sort
-        3.272. sort_alias
-        3.273. sort_aux
-        3.274. sort_browser
-        3.275. sort_re
-        3.276. spam_separator
-        3.277. spoolfile
-        3.278. status_chars
-        3.279. status_format
-        3.280. status_on_top
-        3.281. strict_threads
-        3.282. suspend
-        3.283. text_flowed
-        3.284. thread_received
-        3.285. thorough_search
-        3.286. tilde
-        3.287. time_inc
-        3.288. timeout
-        3.289. tmpdir
-        3.290. to_chars
-        3.291. tunnel
-        3.292. use_8bitmime
-        3.293. use_domain
-        3.294. use_envelope_from
-        3.295. use_from
-        3.296. use_idn
-        3.297. use_ipv6
-        3.298. user_agent
-        3.299. visual
-        3.300. wait_key
-        3.301. weed
-        3.302. wrap
-        3.303. wrap_search
-        3.304. wrapmargin
-        3.305. write_inc
-        3.306. write_bcc
+        3.40. crypt_replyencrypt
+        3.41. crypt_replysign
+        3.42. crypt_replysignencrypted
+        3.43. crypt_timestamp
+        3.44. crypt_use_gpgme
+        3.45. crypt_use_pka
+        3.46. crypt_verify_sig
+        3.47. date_format
+        3.48. default_hook
+        3.49. delete
+        3.50. delete_untag
+        3.51. digest_collapse
+        3.52. display_filter
+        3.53. dotlock_program
+        3.54. dsn_notify
+        3.55. dsn_return
+        3.56. duplicate_threads
+        3.57. edit_headers
+        3.58. editor
+        3.59. encode_from
+        3.60. entropy_file
+        3.61. envelope_from_address
+        3.62. escape
+        3.63. fast_reply
+        3.64. fcc_attach
+        3.65. fcc_clear
+        3.66. folder
+        3.67. folder_format
+        3.68. followup_to
+        3.69. force_name
+        3.70. forward_decode
+        3.71. forward_decrypt
+        3.72. forward_edit
+        3.73. forward_format
+        3.74. forward_quote
+        3.75. from
+        3.76. gecos_mask
+        3.77. hdrs
+        3.78. header
+        3.79. header_cache
+        3.80. header_cache_compress
+        3.81. header_cache_pagesize
+        3.82. help
+        3.83. hidden_host
+        3.84. hide_limited
+        3.85. hide_missing
+        3.86. hide_thread_subject
+        3.87. hide_top_limited
+        3.88. hide_top_missing
+        3.89. history
+        3.90. history_file
+        3.91. honor_disposition
+        3.92. honor_followup_to
+        3.93. hostname
+        3.94. ignore_linear_white_space
+        3.95. ignore_list_reply_to
+        3.96. imap_authenticators
+        3.97. imap_check_subscribed
+        3.98. imap_delim_chars
+        3.99. imap_headers
+        3.100. imap_idle
+        3.101. imap_keepalive
+        3.102. imap_list_subscribed
+        3.103. imap_login
+        3.104. imap_pass
+        3.105. imap_passive
+        3.106. imap_peek
+        3.107. imap_pipeline_depth
+        3.108. imap_servernoise
+        3.109. imap_user
+        3.110. implicit_autoview
+        3.111. include
+        3.112. include_onlyfirst
+        3.113. indent_string
+        3.114. index_format
+        3.115. ispell
+        3.116. keep_flagged
+        3.117. locale
+        3.118. mail_check
+        3.119. mailcap_path
+        3.120. mailcap_sanitize
+        3.121. maildir_header_cache_verify
+        3.122. maildir_trash
+        3.123. mark_old
+        3.124. markers
+        3.125. mask
+        3.126. mbox
+        3.127. mbox_type
+        3.128. menu_context
+        3.129. menu_move_off
+        3.130. menu_scroll
+        3.131. message_cache_clean
+        3.132. message_cachedir
+        3.133. message_format
+        3.134. meta_key
+        3.135. metoo
+        3.136. mh_purge
+        3.137. mh_seq_flagged
+        3.138. mh_seq_replied
+        3.139. mh_seq_unseen
+        3.140. mime_forward
+        3.141. mime_forward_decode
+        3.142. mime_forward_rest
+        3.143. mix_entry_format
+        3.144. mixmaster
+        3.145. move
+        3.146. narrow_tree
+        3.147. net_inc
+        3.148. pager
+        3.149. pager_context
+        3.150. pager_format
+        3.151. pager_index_lines
+        3.152. pager_stop
+        3.153. pgp_auto_decode
+        3.154. pgp_autoinline
+        3.155. pgp_check_exit
+        3.156. pgp_clearsign_command
+        3.157. pgp_decode_command
+        3.158. pgp_decrypt_command
+        3.159. pgp_encrypt_only_command
+        3.160. pgp_encrypt_sign_command
+        3.161. pgp_entry_format
+        3.162. pgp_export_command
+        3.163. pgp_getkeys_command
+        3.164. pgp_good_sign
+        3.165. pgp_ignore_subkeys
+        3.166. pgp_import_command
+        3.167. pgp_list_pubring_command
+        3.168. pgp_list_secring_command
+        3.169. pgp_long_ids
+        3.170. pgp_mime_auto
+        3.171. pgp_replyinline
+        3.172. pgp_retainable_sigs
+        3.173. pgp_show_unusable
+        3.174. pgp_sign_as
+        3.175. pgp_sign_command
+        3.176. pgp_sort_keys
+        3.177. pgp_strict_enc
+        3.178. pgp_timeout
+        3.179. pgp_use_gpg_agent
+        3.180. pgp_verify_command
+        3.181. pgp_verify_key_command
+        3.182. pipe_decode
+        3.183. pipe_sep
+        3.184. pipe_split
+        3.185. pop_auth_try_all
+        3.186. pop_authenticators
+        3.187. pop_checkinterval
+        3.188. pop_delete
+        3.189. pop_host
+        3.190. pop_last
+        3.191. pop_pass
+        3.192. pop_reconnect
+        3.193. pop_user
+        3.194. post_indent_string
+        3.195. postpone
+        3.196. postponed
+        3.197. preconnect
+        3.198. print
+        3.199. print_command
+        3.200. print_decode
+        3.201. print_split
+        3.202. prompt_after
+        3.203. query_command
+        3.204. query_format
+        3.205. quit
+        3.206. quote_regexp
+        3.207. read_inc
+        3.208. read_only
+        3.209. realname
+        3.210. recall
+        3.211. record
+        3.212. reply_regexp
+        3.213. reply_self
+        3.214. reply_to
+        3.215. resolve
+        3.216. reverse_alias
+        3.217. reverse_name
+        3.218. reverse_realname
+        3.219. rfc2047_parameters
+        3.220. save_address
+        3.221. save_empty
+        3.222. save_history
+        3.223. save_name
+        3.224. score
+        3.225. score_threshold_delete
+        3.226. score_threshold_flag
+        3.227. score_threshold_read
+        3.228. search_context
+        3.229. send_charset
+        3.230. sendmail
+        3.231. sendmail_wait
+        3.232. shell
+        3.233. sig_dashes
+        3.234. sig_on_top
+        3.235. signature
+        3.236. simple_search
+        3.237. sleep_time
+        3.238. smart_wrap
+        3.239. smileys
+        3.240. smime_ask_cert_label
+        3.241. smime_ca_location
+        3.242. smime_certificates
+        3.243. smime_decrypt_command
+        3.244. smime_decrypt_use_default_key
+        3.245. smime_default_key
+        3.246. smime_encrypt_command
+        3.247. smime_encrypt_with
+        3.248. smime_get_cert_command
+        3.249. smime_get_cert_email_command
+        3.250. smime_get_signer_cert_command
+        3.251. smime_import_cert_command
+        3.252. smime_is_default
+        3.253. smime_keys
+        3.254. smime_pk7out_command
+        3.255. smime_sign_command
+        3.256. smime_sign_opaque_command
+        3.257. smime_timeout
+        3.258. smime_verify_command
+        3.259. smime_verify_opaque_command
+        3.260. smtp_authenticators
+        3.261. smtp_pass
+        3.262. smtp_url
+        3.263. sort
+        3.264. sort_alias
+        3.265. sort_aux
+        3.266. sort_browser
+        3.267. sort_re
+        3.268. spam_separator
+        3.269. spoolfile
+        3.270. ssl_ca_certificates_file
+        3.271. ssl_client_cert
+        3.272. ssl_force_tls
+        3.273. ssl_min_dh_prime_bits
+        3.274. ssl_starttls
+        3.275. ssl_use_sslv2
+        3.276. ssl_use_sslv3
+        3.277. ssl_use_tlsv1
+        3.278. ssl_usesystemcerts
+        3.279. ssl_verify_dates
+        3.280. ssl_verify_host
+        3.281. status_chars
+        3.282. status_format
+        3.283. status_on_top
+        3.284. strict_threads
+        3.285. suspend
+        3.286. text_flowed
+        3.287. thorough_search
+        3.288. thread_received
+        3.289. tilde
+        3.290. time_inc
+        3.291. timeout
+        3.292. tmpdir
+        3.293. to_chars
+        3.294. tunnel
+        3.295. uncollapse_jump
+        3.296. use_8bitmime
+        3.297. use_domain
+        3.298. use_envelope_from
+        3.299. use_from
+        3.300. use_idn
+        3.301. use_ipv6
+        3.302. user_agent
+        3.303. visual
+        3.304. wait_key
+        3.305. weed
+        3.306. wrap
+        3.307. wrap_search
+        3.308. wrapmargin
+        3.309. write_bcc
+        3.310. write_inc
 
     4. Functions
 
-        4.1. generic menu
-        4.2. index menu
-        4.3. pager menu
-        4.4. alias menu
-        4.5. query menu
-        4.6. attach menu
-        4.7. compose menu
-        4.8. postpone menu
-        4.9. browser menu
-        4.10. pgp menu
-        4.11. smime menu
-        4.12. mix menu
-        4.13. editor menu
-
-9. Miscellany
+        4.1. Generic Menu
+        4.2. Index Menu
+        4.3. Pager Menu
+        4.4. Alias Menu
+        4.5. Query Menu
+        4.6. Attach Menu
+        4.7. Compose Menu
+        4.8. Postpone Menu
+        4.9. Browser Menu
+        4.10. Pgp Menu
+        4.11. Smime Menu
+        4.12. Mix Menu
+        4.13. Editor Menu
+
+10. Miscellany
 
     1. Acknowledgements
-    2. About this document
+    2. About This Document
 
 List of Tables
 
 1.1. Typographical conventions for special terms
-2.1. Most common navigation keys
-2.2. Most common line editor keys
-2.3. Most common message index keys
-2.4. Message status flags
-2.5. Message recipient flags
-2.6. Most common pager keys
-2.7. ANSI escape sequences
-2.8. Color sequences
-2.9. Most common thread mode keys
-2.10. Most common mail sending keys
-2.11. Most common compose menu keys
-2.12. PGP key menu flags
+2.1. Most common navigation keys in entry-based menus
+2.2. Most common navigation keys in page-based menus
+2.3. Most common line editor keys
+2.4. Most common message index keys
+2.5. Message status flags
+2.6. Message recipient flags
+2.7. Most common pager keys
+2.8. ANSI escape sequences
+2.9. Color sequences
+2.10. Most common thread mode keys
+2.11. Most common mail sending keys
+2.12. Most common compose menu keys
+2.13. PGP key menu flags
 3.1. Symbolic key names
 4.1. POSIX regular expression character classes
 4.2. Regular expression repetition operators
@@ -525,43 +559,47 @@ List of Tables
 4.4. Pattern modifiers
 4.5. Simple search keywords
 4.6. Date units
-8.1. Command line options
-8.2. Default generic function bindings
-8.3. Default index function bindings
-8.4. Default pager function bindings
-8.5. Default alias function bindings
-8.6. Default query function bindings
-8.7. Default attach function bindings
-8.8. Default compose function bindings
-8.9. Default postpone function bindings
-8.10. Default browser function bindings
-8.11. Default pgp function bindings
-8.12. Default smime function bindings
-8.13. Default mix function bindings
-8.14. Default editor function bindings
+9.1. Command line options
+9.2. Default generic Function Bindings
+9.3. Default index Function Bindings
+9.4. Default pager Function Bindings
+9.5. Default alias Function Bindings
+9.6. Default query Function Bindings
+9.7. Default attach Function Bindings
+9.8. Default compose Function Bindings
+9.9. Default postpone Function Bindings
+9.10. Default browser Function Bindings
+9.11. Default pgp Function Bindings
+9.12. Default smime Function Bindings
+9.13. Default mix Function Bindings
+9.14. Default editor Function Bindings
 
 List of Examples
 
 3.1. Multiple configuration commands per line
 3.2. Commenting configuration files
 3.3. Escaping quotes in congfiguration files
-3.4. Using external command's output in configuration files
-3.5. Using environment variables in configuration files
-3.6. Configuring external alias files
-3.7. Setting sort method based on mailbox name
-3.8. Header weeding
-3.9. Configuring header display order
-3.10. Defining custom headers
-3.11. Using %-expandos in save-hook
-3.12. Embedding push in folder-hook
-3.13. Configuring spam detection
-3.14. Using user-defined variables for config file readability
-3.15. Using user-defined variables for backing up other config option values
-3.16. Deferring user-defined variable expansion to runtime
-3.17. Using external filters in format strings
-4.1. Using boolean operators in patterns
-4.2. Combining send-hook and my_hdr
+3.4. Splitting long configuration commands over several lines
+3.5. Using external command's output in configuration files
+3.6. Using environment variables in configuration files
+3.7. Configuring external alias files
+3.8. Setting sort method based on mailbox name
+3.9. Header weeding
+3.10. Configuring header display order
+3.11. Defining custom headers
+3.12. Using %-expandos in save-hook
+3.13. Embedding push in folder-hook
+3.14. Configuring spam detection
+3.15. Using user-defined variables for config file readability
+3.16. Using user-defined variables for backing up other config option values
+3.17. Deferring user-defined variable expansion to runtime
+3.18. Using external filters in format strings
+4.1. Matching all addresses in address lists
+4.2. Using boolean operators in patterns
+4.3. Specifying a default hook
 5.1. Attachment counting
+6.1. URLs
+6.2. Managing multiple accounts
 
 Chapter 1. Introduction
 
@@ -569,10 +607,10 @@ Table of Contents
 
 1. Mutt Home Page
 2. Mailing Lists
-3. Software Distribution Sites
-4. Mutt online resources
+3. Getting Mutt
+4. Mutt Online Resources
 5. Contributing to Mutt
-6. Typograhical conventions
+6. Typograhical Conventions
 7. Copyright
 
 Mutt is a small but very powerful text-based MIME mail client. Mutt is highly
@@ -600,16 +638,19 @@ Note
 All messages posted to mutt-announce are automatically forwarded to mutt-users,
 so you do not need to be subscribed to both lists.
 
-3. Software Distribution Sites
+3. Getting Mutt
 
 Mutt releases can be downloaded from ftp://ftp.mutt.org/mutt/. For a list of
 mirror sites, please refer to http://www.mutt.org/download.html.
 
-4. Mutt online resources
+For nightly tarballs and version control access, please refer to the Mutt
+development site.
+
+4. Mutt Online Resources
 
 Bug Tracking System
 
-    The official mutt bug tracking system can be found at http://dev.mutt.org/
+    The official Mutt bug tracking system can be found at http://bugs.mutt.org/
 
 Wiki
 
@@ -631,13 +672,13 @@ Especially for new users it may be helpful to meet other new and experienced
 users to chat about Mutt, talk about problems and share tricks.
 
 Since translations of Mutt into other languages are highly appreciated, the
-mutt developers always look for skilled translators that help improve and
+Mutt developers always look for skilled translators that help improve and
 continue to maintain stale translations.
 
 For contributing code patches for new features and bug fixes, please refer to
 the developer pages at http://dev.mutt.org/ for more details.
 
-6. Typograhical conventions
+6. Typograhical Conventions
 
 This section lists typographical conventions followed throughout this manual.
 See table Table 1.1, ?Typographical conventions for special terms? for
@@ -657,6 +698,8 @@ Table 1.1. Typographical conventions for special terms
 |^G            |Control+G key combination              |
 |--------------+---------------------------------------|
 |$mail_check   |Mutt configuration option              |
+|--------------+---------------------------------------|
+|$HOME         |environment variable                   |
 +------------------------------------------------------+
 
 
@@ -670,7 +713,7 @@ denote that the argument may be repeated arbitrary times.
 
 7. Copyright
 
-Mutt is Copyright (C) 1996-2009 Michael R. Elkins  and others.
+Mutt is Copyright ? 1996-2009 Michael R. Elkins  and others.
 
 This program is free software; you can redistribute it and/or modify it under
 the terms of the GNU General Public License as published by the Free Software
@@ -689,30 +732,39 @@ Chapter 2. Getting Started
 
 Table of Contents
 
-1. Core concepts
-2. Moving Around in Menus
-3. Editing Input Fields
+1. Core Concepts
+2. Screens and Menus
 
-    3.1. Introduction
-    3.2. History
+    2.1. Index
+    2.2. Pager
+    2.3. File Browser
+    2.4. Help
+    2.5. Compose Menu
+    2.6. Alias Menu
+    2.7. Attachment Menu
 
-4. Reading Mail - The Index and Pager
+3. Moving Around in Menus
+4. Editing Input Fields
 
-    4.1. The Message Index
-    4.2. The Pager
-    4.3. Threaded Mode
-    4.4. Miscellaneous Functions
+    4.1. Introduction
+    4.2. History
 
-5. Sending Mail
+5. Reading Mail
 
-    5.1. Introduction
-    5.2. Editing the message header
-    5.3. Sending cryptographically signed/encrypted messages
-    5.4. Sending anonymous messages via mixmaster
-    5.5. Sending format=flowed messages
+    5.1. The Message Index
+    5.2. The Pager
+    5.3. Threaded Mode
+    5.4. Miscellaneous Functions
 
-6. Forwarding and Bouncing Mail
-7. Postponing Mail
+6. Sending Mail
+
+    6.1. Introduction
+    6.2. Editing the Message Header
+    6.3. Sending Cryptographically Signed/Encrypted Messages
+    6.4. Sending Format=Flowed Messages
+
+7. Forwarding and Bouncing Mail
+8. Postponing Mail
 
 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
@@ -723,11 +775,11 @@ The keybindings described in this section are the defaults as distributed. Your
 local system administrator may have altered the defaults for your site. You can
 always type ??? in any menu to display the current bindings.
 
-The first thing you need to do is invoke mutt, simply by typing mutt at the
-command line. There are various command-line options, see either the mutt man
+The first thing you need to do is invoke Mutt, simply by typing mutt at the
+command line. There are various command-line options, see either the Mutt man
 page or the reference.
 
-1. Core concepts
+1. Core Concepts
 
 Mutt is a text-based application which interacts with users through different
 menus which are mostly line-/entry-based or page-based. A line-based menu is
@@ -741,6 +793,11 @@ menu's contents followed by a context sensitive status line and finally the
 command line. The command line is used to display informational and error
 messages as well as for prompts and for entering interactive commands.
 
+Mutt is configured through variables which, if the user wants to permanently
+use a non-default value, are written to configuration files. Mutt supports a
+rich config file syntax to make even complex configuration files readable and
+commentable.
+
 Because Mutt allows for customizing almost all key bindings, there are
 so-called ?functions? which can be executed manually (using the command line)
 or in macros. Macros allow the user to bind a sequence of commands to a single
@@ -762,12 +819,95 @@ be used to highly customize Mutt's behaviour including managing multiple
 identities, customizing the display for a folder or even implementing
 auto-archiving based on a per-folder basis and much more.
 
-2. Moving Around in Menus
+Besides an interactive mode, Mutt can also be used as a command-line tool only
+send messages. It also supports a mailx(1)-compatible interface, see Table 9.1,
+?Command line options? for a complete list of command-line options.
+
+2. Screens and Menus
+
+2.1. Index
+
+The index is the screen that you usually see first when you start Mutt. It
+gives an overview over your emails in the currently opened mailbox. By default,
+this is your system mailbox. The information you see in the index is a list of
+emails, each with its number on the left, its flags (new email, important
+email, email that has been forwarded or replied to, tagged email, ...), the
+date when email was sent, its sender, the email size, and the subject.
+Additionally, the index also shows thread hierarchies: when you reply to an
+email, and the other person replies back, you can see the other's person email
+in a "sub-tree" below. This is especially useful for personal email between a
+group of people or when you've subscribed to mailing lists.
+
+2.2. Pager
+
+The pager is responsible for showing the email content. On the top of the pager
+you have an overview over the most important email headers like the sender, the
+recipient, the subject, and much more information. How much information you
+actually see depends on your configuration, which we'll describe below.
 
-The most important navigation keys common to all menus are shown in Table 2.1,
-?Most common navigation keys?.
+Below the headers, you see the email body which usually contains the message.
+If the email contains any attachments, you will see more information about them
+below the email body, or, if the attachments are text files, you can view them
+directly in the pager.
 
-Table 2.1. Most common navigation keys
+To give the user a good overview, it is possible to configure Mutt to show
+different things in the pager with different colors. Virtually everything that
+can be described with a regular expression can be colored, e.g. URLs, email
+addresses or smileys.
+
+2.3. File Browser
+
+The file browser is the interface to the local or remote file system. When
+selecting a mailbox to open, the browser allows custom sorting of items,
+limiting the items shown by a regular expression and a freely adjustable format
+of what to display in which way. It also allows for easy navigation through the
+file system when selecting file(s) to attach to a message, select multiple
+files to attach and many more.
+
+2.4. Help
+
+The help screen is meant to offer a quick help to the user. It lists the
+current configuration of key bindings and their associated commands including a
+short description, and currently unbound functions that still need to be
+associated with a key binding (or alternatively, they can be called via the
+Mutt command prompt).
+
+2.5. Compose Menu
+
+The compose menu features a split screen containing the information which
+really matter before actually sending a message by mail: who gets the message
+as what (recipients and who gets what kind of copy). Additionally, users may
+set security options like deciding whether to sign, encrypt or sign and encrypt
+a message with/for what keys. Also, it's used to attach messages, to re-edit
+any attachment including the message itself.
+
+2.6. Alias Menu
+
+The alias menu is used to help users finding the recipients of messages. For
+users who need to contact many people, there's no need to remember addresses or
+names completely because it allows for searching, too. The alias mechanism and
+thus the alias menu also features grouping several addresses by a shorter
+nickname, the actual alias, so that users don't have to select each single
+recipient manually.
+
+2.7. Attachment Menu
+
+As will be later discussed in detail, Mutt features a good and stable MIME
+implementation, that is, it supports sending and receiving messages of
+arbitrary MIME types. The attachment menu displays a message's structure in
+detail: what content parts are attached to which parent part (which gives a
+true tree structure), which type is of what type and what size. Single parts
+may saved, deleted or modified to offer great and easy access to message's
+internals.
+
+3. Moving Around in Menus
+
+The most important navigation keys common to line- or entry-based menus are
+shown in Table 2.1, ?Most common navigation keys in entry-based menus? and in
+Table 2.2, ?Most common navigation keys in page-based menus? for page-based
+menus.
+
+Table 2.1. Most common navigation keys in entry-based menus
 
 +------------------------------------------------------------------------+
 |     Key     |    Function    |               Description               |
@@ -790,16 +930,35 @@ Table 2.1. Most common navigation keys
 +------------------------------------------------------------------------+
 
 
-3. Editing Input Fields
+Table 2.2. Most common navigation keys in page-based menus
+
++-------------------------------------------------------------+
+|         Key          |   Function    |     Description      |
+|----------------------+---------------+----------------------|
+|J or          |    |scroll down one line  |
+|----------------------+---------------+----------------------|
+|           ||sroll up one line     |
+|----------------------+---------------+----------------------|
+|K,  or |    |move to the next page |
+|----------------------+---------------+----------------------|
+|- or          ||move the previous page|
+|----------------------+---------------+----------------------|
+|                |          |move to the top       |
+|----------------------+---------------+----------------------|
+|                 |       |move to the bottom    |
++-------------------------------------------------------------+
+
+
+4. Editing Input Fields
 
-3.1. Introduction
+4.1. Introduction
 
 Mutt has a built-in line editor for inputting text, e.g. email addresses or
 filenames. The keys used to manipulate text input are very similar to those of
-Emacs. See Table 2.2, ?Most common line editor keys? for a full reference of
+Emacs. See Table 2.3, ?Most common line editor keys? for a full reference of
 available functions, their default key bindings, and short descriptions.
 
-Table 2.2. Most common line editor keys
+Table 2.3. Most common line editor keys
 
 +---------------------------------------------------------------------+
 |     Key      |    Function     |            Description             |
@@ -856,17 +1015,19 @@ you could use:
 
 bind editor  backspace
 
-3.2. History
+4.2. History
 
 Mutt maintains a history for the built-in editor. The number of items is
 controlled by the $history variable and can be made persistent using an
 external file specified using $history_file. You may cycle through them at an
-editor prompt by using the  and/or  commands.
+editor prompt by using the  and/or  commands. But
+notice that Mutt does not remember the currently entered text, it only cycles
+through history and wraps around at the end or beginning.
 
 Mutt maintains several distinct history lists, one for each of the following
 categories:
 
-  * muttrc commands
+  * .muttrc commands
 
   * addresses and aliases
 
@@ -878,27 +1039,27 @@ categories:
 
   * everything else
 
-Mutt automatically filters out repeated items from the history. It also mimics
-the behavior of some shells by ignoring items starting with a space. The latter
-feature can be useful in macros to not clobber the history's valuable entries
-with unwanted entries.
+Mutt automatically filters out consecutively repeated items from the history.
+It also mimics the behavior of some shells by ignoring items starting with a
+space. The latter feature can be useful in macros to not clobber the history's
+valuable entries with unwanted entries.
 
-4. Reading Mail - The Index and Pager
+5. Reading Mail
 
 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 of the message contents. This
-is called the ?pager.?
+in Mutt. The first is a list of messages in the mailbox, which is called the
+?index? menu in Mutt. The second mode is the display of the message contents.
+This is called the ?pager.?
 
 The next few sections describe the functions provided in each of these modes.
 
-4.1. The Message Index
+5.1. The Message Index
 
 Common keys used to navigate through and manage messages in the index are shown
-in Table 2.3, ?Most common message index keys?. How messages are presented in
+in Table 2.4, ?Most common message index keys?. How messages are presented in
 the index menu can be customized using the $index_format variable.
 
-Table 2.3. Most common message index keys
+Table 2.4. Most common message index keys
 
 +----------------------------------------------------+
 |  Key   |                Description                |
@@ -965,14 +1126,14 @@ Table 2.3. Most common message index keys
 
 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 ?flags? in Table 2.4, ?Message status flags? may appear, some of which
+of the ?flags? in Table 2.5, ?Message status flags? may appear, some of which
 can be turned on or off using these functions:  and 
 bound by default to ?w? and ?W? respectively.
 
-Furthermore, the flags in Table 2.5, ?Message recipient flags? reflect who the
+Furthermore, the flags in Table 2.6, ?Message recipient flags? reflect who the
 message is addressed to. They can be customized with the $to_chars variable.
 
-Table 2.4. Message status flags
+Table 2.5. Message status flags
 
 +------------------------------------------------------------------+
 |Flag|                         Description                         |
@@ -1001,7 +1162,7 @@ Table 2.4. Message status flags
 +------------------------------------------------------------------+
 
 
-Table 2.5. Message recipient flags
+Table 2.6. Message recipient flags
 
 +------------------------------------------------------+
 |Flag|                   Description                   |
@@ -1018,13 +1179,14 @@ Table 2.5. Message recipient flags
 +------------------------------------------------------+
 
 
-4.2. The Pager
+5.2. The Pager
 
-By default, Mutt uses its builtin pager to display the contents of messages.
-The pager is very similar to the Unix program less though not nearly as
+By default, Mutt uses its builtin pager to display the contents of messages (an
+external pager such as less(1) can be configured, see $pager variable). The
+pager is very similar to the Unix program less(1) though not nearly as
 featureful.
 
-Table 2.6. Most common pager keys
+Table 2.7. Most common pager keys
 
 +---------------------------------------------------------------------------+
 |  Key   |                           Description                            |
@@ -1053,14 +1215,14 @@ Table 2.6. Most common pager keys
 +---------------------------------------------------------------------------+
 
 
-In addition to key bindings in Table 2.6, ?Most common pager keys?, many of the
+In addition to key bindings in Table 2.7, ?Most common pager keys?, many of the
 functions from the index menu are also available in the pager, such as
  or  (this is one advantage over using an
 external pager to view messages).
 
 Also, the internal pager supports a couple other advanced features. For one, it
 will accept and translate the ?standard? nroff sequences for bold and
-underline. These sequences are a series of either the letter, backspace (^H),
+underline. These sequences are a series of either the letter, backspace (?^H?),
 the letter again for bold or the letter, backspace, ?_? for denoting underline.
 Mutt will attempt to display these in bold and underline respectively if your
 terminal supports them. If not, you can use the bold and underline color
@@ -1072,9 +1234,9 @@ settings. The sequences Mutt supports are:
 
 \e[Ps;Ps;..Ps;m
 
-where Ps can be one of the codes shown in Table 2.7, ?ANSI escape sequences?.
+where Ps can be one of the codes shown in Table 2.8, ?ANSI escape sequences?.
 
-Table 2.7. ANSI escape sequences
+Table 2.8. ANSI escape sequences
 
 +--------------------------------------------------------------------------+
 |Escape code|                         Description                          |
@@ -1089,13 +1251,13 @@ Table 2.7. ANSI escape sequences
 |-----------+--------------------------------------------------------------|
 |7          |Reverse video on                                              |
 |-----------+--------------------------------------------------------------|
-|3   |Foreground color is  (see Table 2.8, ?Color sequences?)|
+|3   |Foreground color is  (see Table 2.9, ?Color sequences?)|
 |-----------+--------------------------------------------------------------|
-|4   |Background color is  (see Table 2.8, ?Color sequences?)|
+|4   |Background color is  (see Table 2.9, ?Color sequences?)|
 +--------------------------------------------------------------------------+
 
 
-Table 2.8. Color sequences
+Table 2.9. Color sequences
 
 +-------------------+
 |Color code | Color |
@@ -1131,16 +1293,21 @@ Note
 
 Note that the search commands in the pager take regular expressions, which are
 not quite the same as the more complex patterns used by the search command in
-the index. This is because the pager only performs simple text search, whereas
-the index provides boolean filtering on several aspects of messages.
+the index. This is because patterns are used to select messages by criteria
+whereas the pager already displays a selected message.
 
-4.3. Threaded Mode
+5.3. Threaded Mode
 
-When the mailbox is sorted by threads, there are a few additional functions
-available in the index and pager modes as shown in Table 2.9, ?Most common
-thread mode keys?.
+So-called ?threads? provide a hierarchy of messages where replies are linked to
+their parent message(s). This organizational form is extremely useful in
+mailing lists where different parts of the discussion diverge. Mutt displays
+threads as a tree structure.
 
-Table 2.9. Most common thread mode keys
+In Mutt, when a mailbox is sorted by threads, there are a few additional
+functions available in the index and pager modes as shown in Table 2.10, ?Most
+common thread mode keys?.
+
+Table 2.10. Most common thread mode keys
 
 +-------------------------------------------------------------------------+
 | Key |      Function      |                 Description                  |
@@ -1175,17 +1342,18 @@ Table 2.9. Most common thread mode keys
 +-------------------------------------------------------------------------+
 
 
-Note
-
 Collapsing a thread displays only the first message in the thread and hides the
 others. This is useful when threads contain so many messages that you can only
 see a handful of threads on the screen. See %M in $index_format. For example,
-you could use "%?M?(#%03M)&(%4l)?" in $index_format to optionally display the
-number of hidden messages if the thread is collapsed.
+you could use ?%?M?(#%03M)&(%4l)?? in $index_format to optionally display the
+number of hidden messages if the thread is collapsed. The %??&
+? syntax is explained in detail in format string conditionals.
 
-See also: $strict_threads.
+Technically, every reply should contain a list of its parent messages in the
+thread tree, but not all do. In these cases, Mutt groups them by subject which
+can be controlled using the $strict_threads variable.
 
-4.4. Miscellaneous Functions
+5.4. Miscellaneous Functions
 
 In addition, the index and pager menus have these interesting functions:
 
@@ -1293,14 +1461,14 @@ In addition, the index and pager menus have these interesting functions:
     This function will go to the next line of non-quoted text which comes after
     a line of quoted text in the internal pager.
 
-5. Sending Mail
+6. Sending Mail
 
-5.1. Introduction
+6.1. Introduction
 
-The bindings shown in Table 2.10, ?Most common mail sending keys? are available
+The bindings shown in Table 2.11, ?Most common mail sending keys? are available
 in the index and pager to start a new message.
 
-Table 2.10. Most common mail sending keys
+Table 2.11. Most common mail sending keys
 
 +----------------------------------------------------+
 | Key |  Function   |          Description           |
@@ -1323,28 +1491,49 @@ Table 2.10. Most common mail sending keys
 
 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. These items are discussed in greater detail in the next chapter ?
+forwarding. These items are discussed in greater detail in the next section ?
 Forwarding and Bouncing Mail.?
 
 Mutt will then enter the compose menu and prompt you for the recipients to
-place on the ?To:? header field. Next, it will ask you for the ?Subject:? field
-for the message, providing a default if you are replying to or forwarding a
-message. See also $askcc, $askbcc, $autoedit, $bounce, $fast_reply, and
-$include for changing how Mutt asks these questions.
-
-Mutt will then automatically start your $editor on the message body. If the
-$edit_headers variable is set, the headers will be at the top of the message in
-your editor. Any messages you are replying to will be added in sort order to
-the message, with appropriate $attribution, $indent_string and
-$post_indent_string. When forwarding a message, if the $mime_forward variable
-is unset, a copy of the forwarded message will be included. If you have
-specified a $signature, it will be appended to the message.
+place on the ?To:? header field when you hit m to start a new message. Next, it
+will ask you for the ?Subject:? field for the message, providing a default if
+you are replying to or forwarding a message. You again have the chance to
+adjust recipients, subject, and security settings right before actually sending
+the message. See also $askcc, $askbcc, $autoedit, $bounce, $fast_reply, and
+$include for changing how and if Mutt asks these questions.
+
+When replying, Mutt fills these fields with proper values depending on the
+reply type. The types of replying supported are:
+
+Simple reply
+
+    Reply to the author directly.
+
+Group reply
+
+    Reply to the author as well to all recipients except you; this consults
+    alternates.
+
+List reply
+
+    Reply to all mailing list addresses found, either specified via
+    configuration or auto-detected. See Section 12, ?Mailing Lists? for
+    details.
+
+After getting recipients for new messages, forwards or replies, Mutt will then
+automatically start your $editor on the message body. If the $edit_headers
+variable is set, the headers will be at the top of the message in your editor.
+Any messages you are replying to will be added in sort order to the message,
+with appropriate $attribution, $indent_string and $post_indent_string. When
+forwarding a message, if the $mime_forward variable is unset, a copy of the
+forwarded message will be included. If you have specified a $signature, it will
+be appended to the message.
 
 Once you have finished editing the body of your mail message, you are returned
-to the compose menu providing the functions shown in Table 2.11, ?Most common
+to the compose menu providing the functions shown in Table 2.12, ?Most common
 compose menu keys? to modify, send or postpone the message.
 
-Table 2.11. Most common compose menu keys
+Table 2.12. Most common compose menu keys
 
 +----------------------------------------------------------------------+
 | Key |     Function      |                Description                 |
@@ -1402,42 +1591,53 @@ Note that certain operations like composing a new mail, replying, forwarding,
 etc. are not permitted when you are in that folder. The %r in $status_format
 will change to a ?A? to indicate that you are in attach-message mode.
 
-5.2. Editing the message header
+6.2. Editing the Message Header
 
 When editing the header because of $edit_headers being set, there are a several
-pseudo headers available which will not be included in sent messages.
+pseudo headers available which will not be included in sent messages but
+trigger special Mutt behavior.
+
+6.2.1. Fcc: Pseudo Header
 
-5.2.1. Fcc: pseudo header
+If you specify
 
-If you specify Fcc: filename as a header, Mutt will pick up filename just as if
-you had used the  function in the compose menu.
+Fcc: filename
 
-5.2.2. Attach: pseudo header
+as a header, Mutt will pick up filename just as if you had used the 
+function in the compose menu. It can later be changed from the compose menu.
 
-You can also attach files to your message by specifying Attach: filename [
-description ] where filename is the file to attach and description is an
-optional string to use as the description of the attached file.
+6.2.2. Attach: Pseudo Header
 
-5.2.3. Pgp: pseudo header
+You can also attach files to your message by specifying
+
+Attach: filename [ description ]
+
+where filename is the file to attach and description is an optional string to
+use as the description of the attached file. Spaces in filenames have to be
+escaped using backslash (?\?). The file can be removed as well as more added
+from the compose menu.
+
+6.2.3. Pgp: Pseudo Header
 
 If you want to use PGP, you can specify
 
 Pgp: [ E | S | S ]
 
 ?E? selects encryption, ?S? selects signing and ?S? selects signing with
-the given key, setting $pgp_sign_as permanently.
+the given key, setting $pgp_sign_as permanently. The selection can later be
+changed in the compose menu.
 
-5.2.4. In-Reply-To: header
+6.2.4. In-Reply-To: Header
 
 When replying to messages, the In-Reply-To: header contains the Message-Id of
-the message(s) you reply to. If you remove its value, Mutt will not generate a
-References: field, which allows you to create a new message thread, for example
-to create a new message to a mailing list without having to enter the mailing
-list's address.
+the message(s) you reply to. If you remove or modify its value, Mutt will not
+generate a References: field, which allows you to create a new message thread,
+for example to create a new message to a mailing list without having to enter
+the mailing list's address.
 
-5.3. Sending cryptographically signed/encrypted messages
+6.3. Sending Cryptographically Signed/Encrypted Messages
 
-If you have told mutt to PGP or S/MIME encrypt a message, it will guide you
+If you have told Mutt to PGP or S/MIME encrypt a message, it will guide you
 through a key selection process when you try to send the message. Mutt will not
 ask you any questions about keys which have a certified user ID matching one of
 the message recipients' mail addresses. However, there may be situations in
@@ -1445,9 +1645,9 @@ which there are several keys, weakly certified user ID fields, or where no
 matching keys can be found.
 
 In these cases, you are dropped into a menu with a list of keys from which you
-can select one. When you quit this menu, or mutt can't find any matching keys,
+can select one. When you quit this menu, or Mutt can't find any matching keys,
 you are prompted for a user ID. You can, as usually, abort this prompt using ^
-G. When you do so, mutt will return to the compose screen.
+G. When you do so, Mutt will return to the compose screen.
 
 Once you have successfully finished the key selection, the message will be
 encrypted using the selected public keys when sent out.
@@ -1456,10 +1656,10 @@ Most fields of the entries in the key selection menu (see also
 $pgp_entry_format) have obvious meanings. But some explanations on the
 capabilities, flags, and validity fields are in order.
 
-The flags sequence (%f) will expand to one of the flags in Table 2.12, ?PGP key
-menu flags?.
+The flags sequence (?%f?) will expand to one of the flags in Table 2.13, ?PGP
+key menu flags?.
 
-Table 2.12. PGP key menu flags
+Table 2.13. PGP key menu flags
 
 +-------------------------------------------------------+
 |Flag|                   Description                    |
@@ -1474,8 +1674,8 @@ Table 2.12. PGP key menu flags
 +-------------------------------------------------------+
 
 
-The capabilities field (%c) expands to a two-character sequence representing a
-key's capabilities. The first character gives the key's encryption
+The capabilities field (?%c?) expands to a two-character sequence representing
+a key's capabilities. The first character gives the key's encryption
 capabilities: A minus sign (?-?) means that the key cannot be used for
 encryption. A dot (?.?) means that it's marked as a signature key in one of the
 user IDs, but may also be used for encryption. The letter ?e? indicates that
@@ -1486,47 +1686,14 @@ The second character indicates the key's signing capabilities. Once again, a
 encryption key in one of the user-ids, and ?s? denotes a key which can be used
 for signing.
 
-Finally, the validity field (%t) indicates how well-certified a user-id is. A
+Finally, the validity field (?%t?) indicates how well-certified a user-id is. A
 question mark (???) indicates undefined validity, a minus character (?-?) marks
 an untrusted association, a space character means a partially trusted
 association, and a plus character (?+?) indicates complete validity.
 
-5.4. Sending anonymous messages via mixmaster
-
-You may also have compiled mutt to co-operate with Mixmaster, an anonymous
-remailer. Mixmaster permits you to send your messages anonymously using a chain
-of remailers. Mixmaster support in mutt is for mixmaster version 2.04 (beta 45
-appears to be the latest) and 2.03. It does not support earlier versions or the
-later so-called version 3 betas, of which the latest appears to be called
-2.9b23.
-
-To use it, you'll have to obey certain restrictions. Most important, you cannot
-use the Cc and Bcc headers. To tell Mutt to use mixmaster, you have to select a
-remailer chain, using the mix function on the compose menu.
-
-The chain selection screen is divided into two parts. In the (larger) upper
-part, you get a list of remailers you may use. In the lower part, you see the
-currently selected chain of remailers.
-
-You can navigate in the chain using the  and 
-functions, which are by default bound to the left and right arrows and to the h
-and l keys (think vi keyboard bindings). To insert a remailer at the current
-chain position, use the  function. To append a remailer behind the
-current chain position, use  or . You can also delete
-entries from the chain, using the corresponding function. Finally, to abandon
-your changes, leave the menu, or  them pressing (by default) the Return
-key.
-
-Note that different remailers do have different capabilities, indicated in the
-%c entry of the remailer menu lines (see $mix_entry_format). Most important is
-the ?middleman? capability, indicated by a capital ?M?: This means that the
-remailer in question cannot be used as the final element of a chain, but will
-only forward messages to other mixmaster remailers. For details on the other
-capabilities, please have a look at the mixmaster documentation.
-
-5.5. Sending format=flowed messages
+6.4. Sending Format=Flowed Messages
 
-5.5.1. Concept
+6.4.1. Concept
 
 format=flowed-style messages (or f=f for short) are text/plain messages that
 consist of paragraphs which a receiver's mail client may reformat to its own
@@ -1534,18 +1701,18 @@ needs which mostly means to customize line lengths regardless of what the
 sender sent. Technically this is achieved by letting lines of a ?flowable?
 paragraph end in spaces except for the last line.
 
-While for text-mode clients like mutt it's the best way to assume only a
+While for text-mode clients like Mutt it's the best way to assume only a
 standard 80x25 character cell terminal, it may be desired to let the receiver
 decide completely how to view a message.
 
-5.5.2. Mutt support
+6.4.2. Mutt Support
 
 Mutt only supports setting the required format=flowed MIME parameter on
 outgoing messages if the $text_flowed variable is set, specifically it does not
 add the trailing spaces.
 
 After editing the initial message text and before entering the compose menu,
-mutt properly space-stuffes the message. Space-stuffing is required by RfC3676
+Mutt properly space-stuffes the message. Space-stuffing is required by RfC3676
 defining format=flowed and means to prepend a space to:
 
   * all lines starting with a space
@@ -1564,9 +1731,9 @@ the initial edit is finished.
 All leading spaces are to be removed by receiving clients to restore the
 original message prior to further processing.
 
-5.5.3. Editor considerations
+6.4.3. Editor Considerations
 
-As mutt provides no additional features to compose f=f messages, it's
+As Mutt provides no additional features to compose f=f messages, it's
 completely up to the user and his editor to produce proper messages. Please
 consider your editor's documentation if you intend to send f=f messages.
 
@@ -1577,7 +1744,7 @@ properly space-stuffed.
 For example, vim provides the w flag for its formatoptions setting to assist in
 creating f=f messages, see :help fo-table for details.
 
-6. Forwarding and Bouncing Mail
+7. Forwarding and Bouncing Mail
 
 Bouncing and forwarding let you send an existing message to recipients that you
 specify. Bouncing a message sends a verbatim copy of a message to alternative
@@ -1601,7 +1768,7 @@ variable, unless $mime_forward is set.
 Editing the message to forward follows the same procedure as sending or
 replying to a message does.
 
-7. Postponing Mail
+8. Postponing Mail
 
 At times it is desirable to delay sending a message that you have already begun
 to compose. When the  function is used in the compose menu,
@@ -1628,44 +1795,51 @@ Chapter 3. Configuration
 
 Table of Contents
 
-1. Location of initialization files
+1. Location of Initialization Files
 2. Syntax of Initialization Files
-3. Address groups
-4. Defining/Using aliases
-5. Changing the default key bindings
-6. Defining aliases for character sets
-7. Setting variables based upon mailbox
-8. Keyboard macros
-9. Using color and mono video attributes
-10. Message header display
-11. Alternative addresses
-12. Mailing lists
-13. Using Multiple spool mailboxes
-14. Monitoring incoming mail
-15. User defined headers
-16. Specify default save mailbox
-17. Specify default Fcc: mailbox when composing
-18. Specify default save filename and default Fcc: mailbox at once
-19. Change settings based upon message recipients
-20. Change settings before formatting a message
-21. Choosing the cryptographic key of the recipient
-22. Adding key sequences to the keyboard buffer
-23. Executing functions
+3. Address Groups
+4. Defining/Using Aliases
+5. Changing the Default Key Bindings
+6. Defining Aliases for Character Sets
+7. Setting Variables Based Upon Mailbox
+8. Keyboard Macros
+9. Using Color and Mono Video Attributes
+10. Message Header Display
+
+    10.1. Selecting Headers
+    10.2. Ordering Displayed Headers
+
+11. Alternative Addresses
+12. Mailing Lists
+13. Using Multiple Spool Mailboxes
+14. Monitoring Incoming Mail
+15. User-Defined Headers
+16. Specify Default Save Mailbox
+17. Specify Default Fcc: Mailbox When Composing
+18. Specify Default Save Filename and Default Fcc: Mailbox at Once
+19. Change Settings Based Upon Message Recipients
+20. Change Settings Before Formatting a Message
+21. Choosing the Cryptographic Key of the Recipient
+22. Adding Key Sequences to the Keyboard Buffer
+23. Executing Functions
 24. Message Scoring
-25. Spam detection
+25. Spam Detection
 26. Setting and Querying Variables
 
-    26.1. Commands
-    26.2. User-defined variables
+    26.1. Variable Types
+    26.2. Commands
+    26.3. User-Defined Variables
 
-27. Reading initialization commands from another file
-28. Removing hooks
+27. Reading Initialization Commands From Another File
+28. Removing Hooks
 29. Format Strings
 
     29.1. Basic usage
-    29.2. Filters
+    29.2. Conditionals
+    29.3. Filters
+    29.4. Padding
 
-1. Location of initialization files
+1. Location of Initialization Files
 
 While the default configuration (or ?preferences?) make Mutt usable right out
 of the box, it is often desirable to tailor Mutt to suit your own tastes. When
@@ -1674,17 +1848,17 @@ Mutt is first invoked, it will attempt to read the ?system? configuration file
 option is specified. This file is typically /usr/local/share/mutt/Muttrc or /
 etc/Muttrc. Mutt will next look for a file named .muttrc in your home
 directory. If this file does not exist and your home directory has a
-subdirectory named .mutt, mutt try to load a file named .mutt/muttrc.
+subdirectory named .mutt, Mutt tries to load a file named .mutt/muttrc.
 
 .muttrc is the file where you will usually place your commands to configure
 Mutt.
 
-In addition, mutt supports version specific configuration files that are parsed
+In addition, Mutt supports version specific configuration files that are parsed
 instead of the default files as explained above. For instance, if your system
 has a Muttrc-0.88 file in the system configuration directory, and you are
-running version 0.88 of mutt, this file will be sourced instead of the Muttrc
+running version 0.88 of Mutt, this file will be sourced instead of the Muttrc
 file. The same is true of the user configuration file, if you have a file
-.muttrc-0.88.6 in your home directory, when you run mutt version 0.88.6, it
+.muttrc-0.88.6 in your home directory, when you run Mutt version 0.88.6, it
 will source this file instead of the default .muttrc file. The version 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.
@@ -1693,7 +1867,7 @@ show-version key (default: V) from the index menu.
 
 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 (;).
+separated by a semicolon (?;?).
 
 Example 3.1. Multiple configuration commands per line
 
@@ -1702,14 +1876,14 @@ set realname='Mutt user' ; ignore x-
 
 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,
+character to the end of the line is ignored.
 
 Example 3.2. Commenting configuration files
 
 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
+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 shell programs, namely that
 a single quote is used to specify a literal string (one that is not interpreted
@@ -1717,7 +1891,7 @@ for shell variables or quoting with a backslash [see next paragraph]), while
 double quotes indicate a string for which should be evaluated. For example,
 backticks are evaluated inside of double quotes, but not for single quotes.
 
-\ quotes the next character, just as in shells such as bash and zsh. For
+?\? quotes the next character, just as in shells such as bash and zsh. For
 example, if want to put quotes ?"? inside of a string, you can use ?\? to force
 the next character to be a literal instead of interpreted character.
 
@@ -1729,43 +1903,47 @@ 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.
 
-A \ at the end of a line can be used to split commands over multiple lines,
-provided that the split points don't appear in the middle of command names.
+A ?\? at the end of a line can be used to split commands over multiple lines as
+it ?escapes? the line end, provided that the split points don't appear in the
+middle of command names. Lines are first concatenated before interpretation so
+that a multi-line can be commented by commenting out the first line only.
 
-It is also possible to substitute the output of a Unix command in an
-initialization file. This is accomplished by enclosing the command in backticks
-(``). For example,
+Example 3.4. Splitting long configuration commands over several lines
 
-Example 3.4. Using external command's output in configuration files
+set status_format="some very \
+long value split \
+over several lines"
 
-my_hdr X-Operating-System: `uname -a`
 
+It is also possible to substitute the output of a Unix command in an
+initialization file. This is accomplished by enclosing the command in backticks
+(``). In Example 3.5, ?Using external command's output in configuration files?,
+the output of the Unix command ?uname -a? will be substituted before the line
+is parsed. Since initialization files are line oriented, only the first line of
+output from the Unix command will be substituted.
 
-The output of the Unix command ?uname -a? will be substituted before the line
-is parsed.
+Example 3.5. Using external command's output in configuration files
 
-Note
+my_hdr X-Operating-System: `uname -a`
 
-Since initialization files are line oriented, only the first line of output
-from the Unix command will be substituted.
 
-Both environment variables and mutt variables can be accessed by prepending ?$?
+Both environment variables and Mutt variables can be accessed by prepending ?$?
 to the name of the variable. For example,
 
-Example 3.5. Using environment variables in configuration files
+Example 3.6. Using environment variables in configuration files
 
 set record=+sent_on_$HOSTNAME
 
 
-will cause mutt to save outgoing messages to a folder named ?sent_on_kremvax?
-if the environment variable HOSTNAME is set to ?kremvax.? (See $record for
+will cause Mutt to save outgoing messages to a folder named ?sent_on_kremvax?
+if the environment variable $HOSTNAME is set to ?kremvax.? (See $record for
 details.)
 
 Mutt expands the variable when it is assigned, not when it is used. If the
 value of a variable on the right-hand side of an assignment changes after the
 assignment, the variable on the left-hand side will not be affected.
 
-The commands understood by mutt are explained in the next paragraphs. For a
+The commands understood by Mutt are explained in the next paragraphs. For a
 complete list, see the command reference.
 
 All configuration files are expected to be in the current locale as specified
@@ -1778,7 +1956,7 @@ This mechanism should be avoided if possible as it has the following
 implications:
 
   * These variables should be set early in a configuration file with $charset
-    preceding $config_charset so Mutt know what character set to convert to.
+    preceding $config_charset so Mutt knows what character set to convert to.
 
   * If $config_charset is set, it should be set in each configuration file
     because the value is global and not per configuration file.
@@ -1789,12 +1967,11 @@ implications:
     silently change the meaning of certain tokens (e.g. inserting question
     marks into regular expressions).
 
-3. Address groups
+3. Address Groups
 
 Usage:
 
 group [ -group name ...] { -rx expr ... | -addr expr ... }
-
 ungroup [ -group name ...] { * | -rx expr ... | -addr expr ... }
 
 group is used to directly add either addresses or regular expressions to the
@@ -1813,11 +1990,12 @@ ungroup is used to remove addresses or regular expressions from the specified
 group or groups. The syntax is similar to the group command, however the
 special character * can be used to empty a group of all of its contents.
 
-4. Defining/Using aliases
+4. Defining/Using Aliases
 
 Usage:
 
 alias [ -group name ...] key address [ address ...]
+unalias [ -group name ...] { * | key ... }
 
 It's usually very cumbersome to remember or type out the address of someone you
 are communicating with. Mutt allows you to create ?aliases? which map a short
@@ -1833,15 +2011,13 @@ added to the named group.
 
 To remove an alias or aliases (?*? means all aliases):
 
-unalias [ -group name ...] { * | key ... }
-
 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. Consequently, you can have multiple alias files, or you
-can have all aliases defined in your muttrc.
+can have all aliases defined in your .muttrc.
 
 On the other hand, the  function can use only one file, the one
 pointed to by the $alias_file variable (which is ?/.muttrc by default). This
@@ -1849,31 +2025,29 @@ file is not special either, in the sense that Mutt will happily append aliases
 to any file, but in order for the new aliases to take effect you need to
 explicitly source this file too.
 
-For example:
-
-Example 3.6. Configuring external alias files
+Example 3.7. Configuring external alias files
 
 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
+To use aliases, you merely use the alias at any place in Mutt where Mutt
 prompts for addresses, such as the To: or Cc: prompt. You can also enter
 aliases in your editor at the appropriate headers if you have the $edit_headers
 variable set.
 
 In addition, at the various address prompts, you can use the tab character to
-expand a partial alias to the full alias. If there are multiple matches, mutt
+expand a partial alias to the full alias. If there are multiple matches, Mutt
 will bring up a menu with the matching aliases. In order to be presented with
-the full list of aliases, you must hit tab with out a partial alias, such as at
+the full list of aliases, you must hit tab without a partial alias, such as at
 the beginning of the prompt or after a comma denoting multiple addresses.
 
 In the alias menu, you can select as many aliases as you want with the
 select-entry key (default: ), and use the exit key (default: q) to
 return to the address prompt.
 
-5. Changing the default key bindings
+5. Changing the Default Key Bindings
 
 Usage:
 
@@ -1897,8 +2071,8 @@ generic
 alias
 
     The alias menu is the list of your personal aliases as defined in your
-    muttrc. It is the mapping from a short alias name to the full email address
-    (es) of the recipient(s).
+    .muttrc. It is the mapping from a short alias name to the full email
+    address(es) of the recipient(s).
 
 attach
 
@@ -2018,23 +2192,22 @@ function specifies which action to take when key is pressed. For a complete
 list of functions, see the reference. The special function  unbinds the
 specified key sequence.
 
-6. Defining aliases for character sets
+6. Defining Aliases for Character Sets
 
 Usage:
 
 charset-hook alias charset
-
 iconv-hook charset local-charset
 
 The charset-hook command defines an alias for a character set. This is useful
 to properly display messages which are tagged with a character set name not
-known to mutt.
+known to Mutt.
 
 The iconv-hook command defines a system-specific name for a character set. This
 is helpful when your systems character conversion library insists on using
 strange, system-specific names for character sets.
 
-7. Setting variables based upon mailbox
+7. Setting Variables Based Upon Mailbox
 
 Usage:
 
@@ -2044,7 +2217,7 @@ It is often desirable to change settings based on which mailbox you are
 reading. The folder-hook command provides a method by which you can execute any
 configuration command. regexp is a regular expression specifying in which
 mailboxes to execute command before loading. If a mailbox matches multiple
-folder-hook's, they are executed in the order given in the muttrc.
+folder-hooks, they are executed in the order given in the .muttrc.
 
 Note
 
@@ -2058,22 +2231,23 @@ Settings are not restored when you leave the mailbox. 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
+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 default command, use the pattern ?.? before
 other folder-hooks adjusting a value on a per-folder basis because folder-hooks
-are evaluated in the order given in the configuration file. The following
-example will set the sort variable to date-sent for all folders but to threads
-for all folders containing ?mutt? in their name.
+are evaluated in the order given in the configuration file.
 
-Example 3.7. Setting sort method based on mailbox name
+The following example will set the sort variable to date-sent for all folders
+but to threads for all folders containing ?mutt? in their name.
 
-folder-hook . set sort=date-sent
-folder-hook mutt set sort=threads
+Example 3.8. Setting sort method based on mailbox name
 
+folder-hook . "set sort=date-sent"
+folder-hook mutt "set sort=threads"
 
-8. Keyboard macros
+
+8. Keyboard Macros
 
 Usage:
 
@@ -2102,24 +2276,21 @@ and also facilitates defining of macros in files used by more than one user
 (e.g., the system Muttrc).
 
 Optionally you can specify a descriptive text after sequence, which is shown in
-the help screens.
+the help screens if they contain a description.
 
 Note
 
 Macro definitions (if any) listed in the help screen(s), are silently truncated
 at the screen width, and are not wrapped.
 
-9. Using color and mono video attributes
+9. Using Color and Mono Video Attributes
 
 Usage:
 
 color object foreground background
-
 color { header | body } foreground background regexp
-
 color index foreground background pattern
-
-uncolor index { * | pattern ... }
+uncolor { index | header | body } { * | pattern ... }
 
 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 information), you must
@@ -2191,7 +2362,7 @@ foreground color boldfaced (e.g., brightred).
 
 If your terminal supports it, the special keyword default can be used as a
 transparent color. The value brightdefault is also valid. If Mutt is linked
-against the S-Lang library, you also need to set the COLORFGBG environment
+against the S-Lang library, you also need to set the $COLORFGBG environment
 variable to the default colors of your terminal for this to work; for example
 (for Bourne-like shells):
 
@@ -2205,10 +2376,10 @@ of white and yellow when setting this variable.
 
 Note
 
-The uncolor command can be applied to the index object only. It removes entries
-from the list. You must 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.
+The uncolor command can be applied to the index, header and body objects only.
+It removes entries from the list. You must 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 list of all entries.
 
 Mutt also recognizes the keywords color0, color1, ?, colorN-1 (N being the
 number of colors supported by your terminal). This is useful when you remap the
@@ -2216,17 +2387,12 @@ colors for your display (for example by changing the color associated with
 color2 for your xterm), since color names may then lose their normal meaning.
 
 If your terminal does not support color, it is still possible change the video
-attributes through the use of the ?mono? command:
-
-Usage:
+attributes through the use of the ?mono? command. Usage:
 
 mono object attribute
-
 mono { header | body } attribute regexp
-
 mono index attribute pattern
-
-unmono index { * | pattern ... }
+unmono { index | header | body } { * | pattern ... }
 
 For object, see the color command. attribute can be one of the following:
 
@@ -2240,12 +2406,13 @@ For object, see the color command. attribute can be one of the following:
 
   * standout
 
-10. Message header display
+10. Message Header Display
+
+10.1. Selecting Headers
 
 Usage:
 
 ignore pattern [ pattern ...]
-
 unignore { * | pattern ... }
 
 Messages often have many header fields added by automatic processing systems,
@@ -2262,9 +2429,7 @@ For example, if you do ?ignore x-? it is possible to ?unignore x-mailer?.
 
 ?unignore *? will remove all tokens from the ignore list.
 
-For example:
-
-Example 3.8. Header weeding
+Example 3.9. Header weeding
 
 # Sven's draconian header weeding
 ignore *
@@ -2273,40 +2438,40 @@ unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
 unignore posted-to:
 
 
+10.2. Ordering Displayed Headers
+
 Usage:
 
 hdr_order header [ header ...]
-
 unhdr_order { * | header ... }
 
-With the hdr_order command you can specify an order in which mutt will attempt
+With the hdr_order command you can specify an order in which Mutt will attempt
 to present these headers to you when viewing messages.
 
 ?unhdr_order *? will clear all previous headers from the order list, thus
 removing the header order effects set by the system-wide startup file.
 
-Example 3.9. Configuring header display order
+Example 3.10. Configuring header display order
 
 hdr_order From Date: From: To: Cc: Subject:
 
 
-11. Alternative addresses
+11. Alternative Addresses
 
 Usage:
 
 alternates [ -group name ...] regexp [ regexp ...]
-
 unalternates [ -group name ...] { * | regexp ... }
 
-With various functions, mutt will treat messages differently, depending on
+With various functions, Mutt will treat messages differently, depending on
 whether you sent them or whether you received them from someone else. For
-instance, when replying to a message that you sent to a different party, mutt
+instance, when replying to a message that you sent to a different party, Mutt
 will automatically suggest to send the response to the original message's
-recipients -- responding to yourself won't make much sense in many cases. (See
+recipients ? responding to yourself won't make much sense in many cases. (See
 $reply_to.)
 
 Many users receive e-mail under a number of different addresses. To fully use
-mutt's features here, the program must be able to recognize what e-mail
+Mutt's features here, the program must be able to recognize what e-mail
 addresses you receive mail under. That's the purpose of the alternates command:
 It takes a list of regular expressions, each of which can identify an address
 under which you receive e-mail.
@@ -2317,7 +2482,7 @@ possible to avoid mismatches. For example, if you specify:
 
 alternates user@example
 
-mutt will consider ?some-user@example? as being your address, too which may not
+Mutt will consider ?some-user@example? as being your address, too which may not
 be desired. As a solution, in such cases addresses should be specified as:
 
 alternates '^user@example$'
@@ -2336,25 +2501,25 @@ command matches an entry on the unalternates list, that unalternates entry will
 be removed. If the regexp for unalternates is ?*?, all entries on alternates
 will be removed.
 
-12. Mailing lists
+12. Mailing Lists
 
 Usage:
 
 lists [ -group name ...] regexp [ regexp ...]
-
 unlists [ -group name ...] { * | regexp ... }
-
 subscribe [ -group name ...] regexp [ regexp ...]
-
 unsubscribe [ -group name ...] { * | regexp ... }
 
 Mutt has a few nice features for handling mailing lists. In order to take
 advantage of them, you must specify which addresses belong to mailing lists,
-and which mailing lists you are subscribed to. Once you have done this, the
- function will work for all known lists. Additionally, when you
-send a message to a subscribed list, mutt will add a Mail-Followup-To header to
-tell other users' mail user agents not to send copies of replies to your
-personal address.
+and which mailing lists you are subscribed to. Mutt also has limited support
+for auto-detecting mailing lists: it supports parsing mailto: links in the
+common List-Post: header which has the same effect as specifying the list
+address via the lists command (except the group feature). Once you have done
+this, the  function will work for all known lists. Additionally,
+when you send a message to a subscribed list, Mutt will add a Mail-Followup-To
+header to tell other users' mail user agents not to send copies of replies to
+your personal address.
 
 Note
 
@@ -2362,26 +2527,31 @@ The Mail-Followup-To header is a non-standard extension which is not supported
 by all mail user agents. Adding it is not bullet-proof against receiving
 personal CCs of list messages. Also note that the generation of the
 Mail-Followup-To header is controlled by the $followup_to configuration
-variable.
+variable since it's common practice on some mailing lists to send Cc upons
+replies (which is more a group- than a list-reply).
 
 More precisely, Mutt maintains lists of patterns for the addresses of known and
 subscribed mailing lists. Every subscribed mailing list is known. To mark a
-mailing list as known, use the ?lists? command. To mark it as subscribed, use
-?subscribe?.
+mailing list as known, use the list command. To mark it as subscribed, use
+subscribe.
 
 You can use regular expressions with both commands. To mark all messages sent
-to a specific bug report's address on mutt's bug tracking system as list mail,
-for instance, you could say ?subscribe [0-9]*@bugs.guug.de?. Often, it's
-sufficient to just give a portion of the list's e-mail address.
+to a specific bug report's address on Debian's bug tracking system as list
+mail, for instance, you could say
+
+subscribe [0-9]*.*@bugs.debian.org
+
+as it's often, it's sufficient to just give a portion of the list's e-mail
+address.
 
 Specify as much of the address as you need to to remove ambiguity. For example,
 if you've subscribed to the Mutt mailing list, you will receive mail addressed
 to mutt-users@mutt.org. So, to tell Mutt that this is a mailing list, you could
-add ?lists mutt-users@? to your initialization file. To tell mutt that you are
-subscribed to it, add ?subscribe mutt-users? to your initialization file
-instead. If you also happen to get mail from someone whose address is
-mutt-users@example.com, you could use ?lists ^mutt-users@mutt\\.org$? or
-?subscribe ^mutt-users@mutt\\.org$? to match only mail from the actual list.
+add lists mutt-users@ to your initialization file. To tell Mutt that you are
+subscribed to it, add subscribe mutt-users to your initialization file instead.
+If you also happen to get mail from someone whose address is
+mutt-users@example.com, you could use lists ^mutt-users@mutt\\.org$ or
+subscribe ^mutt-users@mutt\\.org$ to match only mail from the actual list.
 
 The -group flag adds all of the subsequent regular expressions to the named
 group.
@@ -2390,9 +2560,9 @@ The ?unlists? command is used to remove a token from the list of known and
 subscribed mailing-lists. Use ?unlists *? to remove all tokens.
 
 To remove a mailing list from the list of subscribed mailing lists, but keep it
-on the list of known mailing lists, use ?unsubscribe?.
+on the list of known mailing lists, use unsubscribe.
 
-13. Using Multiple spool mailboxes
+13. Using Multiple Spool Mailboxes
 
 Usage:
 
@@ -2406,12 +2576,11 @@ mailbox specifies where mail should be saved when read.
 Unlike some of the other hook commands, only the first matching pattern is used
 (it is not possible to save read mail in more than a single mailbox).
 
-14. Monitoring incoming mail
+14. Monitoring Incoming Mail
 
 Usage:
 
 mailboxes mailbox [ mailbox ...]
-
 unmailboxes { * | mailbox ... }
 
 This command specifies folders which can receive mail and which will be checked
@@ -2419,7 +2588,7 @@ for new messages periodically.
 
 folder can either be a local file or directory (Mbox/Mmdf or Maildir/Mh). If
 Mutt was built with POP and/or IMAP support, folder can also be a POP/IMAP
-folder URL. The URL syntax is described in Section 1.2, ?URL syntax?, POP and
+folder URL. The URL syntax is described in Section 1.2, ?URL Syntax?, POP and
 IMAP are described in Section 3, ?POP3 Support? and Section 4, ?IMAP Support?
 respectively.
 
@@ -2437,8 +2606,8 @@ The folders 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 affects these characters (like $folder and $spoolfile)
 should be set before the mailboxes command. If none of these shorcuts are used,
-a local path should be absolute as otherwise mutt tries to find it relative to
-the directory from where mutt was started which may not always be desired.
+a local path should be absolute as otherwise Mutt tries to find it relative to
+the directory from where Mutt was started which may not always be desired.
 
 For Mbox and Mmdf folders, new mail is detected by comparing access and/or
 modification times of files: Mutt assumes a folder has new mail if it wasn't
@@ -2451,29 +2620,29 @@ support.
 
 In cases where new mail detection for Mbox or Mmdf folders appears to be
 unreliable, the $check_mbox_size option can be used to make Mutt track and
-consult file sizes for new mail detection instead.
+consult file sizes for new mail detection instead which won't work for
+size-neutral changes.
 
-15. User defined headers
+15. User-Defined Headers
 
 Usage:
 
 my_hdr string
-
 unmy_hdr { * | field ... }
 
 The my_hdr command allows you to create your own header fields which will be
-added to every message you send.
+added to every message you send and appear in the editor if $edit_headers is
+set.
 
 For example, if you would like to add an ?Organization:? header field to all of
-your outgoing messages, you can put the command
+your outgoing messages, you can put the command something like shown in
+Example 3.11, ?Defining custom headers? in your .muttrc.
 
-Example 3.10. Defining custom headers
+Example 3.11. Defining custom headers
 
 my_hdr Organization: A Really Big Company, Anytown, USA
 
 
-in your .muttrc.
-
 Note
 
 Space characters are not allowed between the keyword and the colon (?:?). The
@@ -2491,7 +2660,7 @@ example, to remove all ?To? and ?Cc? header fields, you could use:
 
 unmy_hdr to cc
 
-16. Specify default save mailbox
+16. Specify Default Save Mailbox
 
 Usage:
 
@@ -2504,9 +2673,7 @@ Matching in Hooks for information on the exact format.
 To provide more flexibility and good defaults, Mutt applies the expandos of
 $index_format to mailbox after it was expanded.
 
-Examples:
-
-Example 3.11. Using %-expandos in save-hook
+Example 3.12. Using %-expandos in save-hook
 
 # default: save all to ~/Mail/
 save-hook . ~/Mail/%F
@@ -2520,7 +2687,7 @@ save-hook aol\\.com$ +spam
 
 Also see the fcc-save-hook command.
 
-17. Specify default Fcc: mailbox when composing
+17. Specify Default Fcc: Mailbox When Composing
 
 Usage:
 
@@ -2536,12 +2703,12 @@ $index_format to mailbox after it was expanded.
 
 See Message Matching in Hooks for information on the exact format of pattern.
 
-Example: fcc-hook [@.]aol\\.com$ +spammers
+fcc-hook [@.]aol\\.com$ +spammers
 
-The above will save a copy of all messages going to the aol.com domain to the
+...will save a copy of all messages going to the aol.com domain to the
 `+spammers' mailbox by default. Also see the fcc-save-hook command.
 
-18. Specify default save filename and default Fcc: mailbox at once
+18. Specify Default Save Filename and Default Fcc: Mailbox at Once
 
 Usage:
 
@@ -2551,14 +2718,12 @@ This command is a shortcut, equivalent to doing both a fcc-hook and a save-hook
 with its arguments, including %-expansion on mailbox according to $index_format
 .
 
-19. Change settings based upon message recipients
+19. Change Settings Based Upon Message Recipients
 
 Usage:
 
 reply-hook [!]pattern command
-
 send-hook [!]pattern command
-
 send2-hook [!]pattern command
 
 These commands can be used to execute arbitrary configuration commands based
@@ -2581,7 +2746,7 @@ executed after send-hook, and can, e.g., be used to set parameters such as the
 $sendmail variable depending on the message's sender address.
 
 For each type of send-hook or reply-hook, when multiple matches occur, commands
-are executed in the order they are specified in the muttrc (for that type of
+are executed in the order they are specified in the .muttrc (for that type of
 hook).
 
 Example: send-hook mutt "set mime_forward signature=''"
@@ -2594,11 +2759,12 @@ Note
 
 send-hook's are only executed once after getting the initial list of
 recipients. Adding a recipient after replying or editing the message will not
-cause any send-hook to be executed. Also note that my_hdr commands which modify
-recipient headers, or the message's subject, don't have any effect on the
-current message when executed from a send-hook.
+cause any send-hook to be executed, similarily if $autoedit is set (as then the
+initial list of recipients is empty). Also note that my_hdr commands which
+modify recipient headers, or the message's subject, don't have any effect on
+the current message when executed from a send-hook.
 
-20. Change settings before formatting a message
+20. Change Settings Before Formatting a Message
 
 Usage:
 
@@ -2608,7 +2774,7 @@ This command can be used to execute arbitrary configuration commands before
 viewing or formatting a message based upon information about the message.
 command is executed if the pattern matches the message to be displayed. When
 multiple matches occur, commands are executed in the order they are specified
-in the muttrc.
+in the .muttrc.
 
 See Message Matching in Hooks for information on the exact format of pattern.
 
@@ -2617,7 +2783,7 @@ Example:
 message-hook ~A 'set pager=builtin'
 message-hook '~f freshmeat-news' 'set pager="less \"+/^  subject: .*\""'
 
-21. Choosing the cryptographic key of the recipient
+21. Choosing the Cryptographic Key of the Recipient
 
 Usage:
 
@@ -2633,7 +2799,7 @@ of the public key to be used when encrypting messages to a certain recipient.
 The meaning of keyid is to be taken broadly in this context: You can either put
 a numerical key ID here, an e-mail address, or even just a real name.
 
-22. Adding key sequences to the keyboard buffer
+22. Adding Key Sequences to the Keyboard Buffer
 
 Usage:
 
@@ -2642,30 +2808,29 @@ push string
 This command adds the named string to the keyboard buffer. The string may
 contain control characters, key names and function names like the sequence
 string in the macro command. You may use it to automatically run a sequence of
-commands at startup, or when entering certain folders. For example, the
-following command will automatically collapse all threads when entering a
-folder:
+commands at startup, or when entering certain folders. For example,
+Example 3.13, ?Embedding push in folder-hook? shows how to automatically
+collapse all threads when entering a folder.
 
-Example 3.12. Embedding push in folder-hook
+Example 3.13. Embedding push in folder-hook
 
 folder-hook . 'push '
 
 
-23. Executing functions
+23. Executing Functions
 
 Usage:
 
 exec function [ function ...]
 
 This command can be used to execute any function. Functions are listed in the
-function reference. ?exec function? is equivalent to ?push ?.
+function reference. ?execfunction? is equivalent to ?push ?.
 
 24. Message Scoring
 
 Usage:
 
 score pattern value
-
 unscore { * | pattern ... }
 
 The score commands adds value to a message's score if pattern matches it.
@@ -2673,7 +2838,7 @@ pattern is a string in the format described in the patterns section (note: For
 efficiency reasons, patterns which scan information not available in the index,
 such as ?b, ?B or ?h, may not be used). value is a positive or negative
 integer. A message's final score is the sum total of all matching score
-entries. However, you may optionally prefix value with an equal sign (=) to
+entries. However, you may optionally prefix value with an equal sign (?=?) to
 cause evaluation to stop at a particular entry if there is a match. Negative
 final scores are rounded up to 0.
 
@@ -2681,12 +2846,11 @@ The unscore command removes score entries from the list. You must specify the
 same pattern specified in the score command for it to be removed. The pattern
 ?*? is a special token which means to clear the list of all score entries.
 
-25. Spam detection
+25. Spam Detection
 
 Usage:
 
 spam pattern format
-
 nospam { * | pattern }
 
 Mutt has generalized support for external spam-scoring filters. By defining
@@ -2700,23 +2864,28 @@ Your first step is to define your external filter's spam patterns using the
 spam command. pattern should be a regular expression that matches a header in a
 mail message. If any message in the mailbox matches this regular expression, it
 will receive a ?spam tag? or ?spam attribute? (unless it also matches a nospam
-pattern -- see below.) The appearance of this attribute is entirely up to you,
+pattern ? see below.) The appearance of this attribute is entirely up to you,
 and is governed by the format parameter. format can be any static text, but it
 also can include back-references from the pattern expression. (A regular
 expression ?back-reference? refers to a sub-expression contained within
 parentheses.) %1 is replaced with the first back-reference in the regex, %2
 with the second, etc.
 
+To match spam tags, mutt needs the corresponding header information which is
+always the case for local and POP folders but not for IMAP in the default
+configuration. Depending on the spam header to be analyzed, $imap_headers may
+need to be adjusted.
+
 If you're using multiple spam filters, a message can have more than one
 spam-related header. You can define spam patterns for each filter you use. If a
 message matches two or more of these patterns, and the $spam_separator variable
 is set to a string, then the message's spam tag will consist of all the format
 strings joined together, with the value of $spam_separator separating them.
 
-For example, suppose I use DCC, SpamAssassin, and PureMessage. I might define
-these spam settings:
+For example, suppose one uses DCC, SpamAssassin, and PureMessage, then the
+configuration might look like in Example 3.14, ?Configuring spam detection?.
 
-Example 3.13. Configuring spam detection
+Example 3.14. Configuring spam detection
 
 spam "X-DCC-.*-Metrics:.*(....)=many"         "90+/DCC-%1"
 spam "X-Spam-Status: Yes"                     "90+/SA"
@@ -2724,10 +2893,10 @@ spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
 set spam_separator=", "
 
 
-If I then received a message that DCC registered with ?many? hits under the
+If then a message is received that DCC registered with ?many? hits under the
 ?Fuz2? checksum, and that PureMessage registered with a 97% probability of
 being spam, that message's spam tag would read 90+/DCC-Fuz2, 97/PM. (The four
-characters before ?=many? in a DCC report indicate the checksum used -- in this
+characters before ?=many? in a DCC report indicate the checksum used ? in this
 case, ?Fuz2?.)
 
 If the $spam_separator variable is unset, then each spam pattern match
@@ -2741,17 +2910,17 @@ sorting by spam attribute will use as a sort key.
 
 That's a pretty complicated example, and most people's actual environments will
 have only one spam filter. The simpler your configuration, the more effective
-mutt can be, especially when it comes to sorting.
+Mutt can be, especially when it comes to sorting.
 
-Generally, when you sort by spam tag, mutt will sort lexically -- that is, by
+Generally, when you sort by spam tag, Mutt will sort lexically ? that is, by
 ordering strings alphanumerically. However, if a spam tag begins with a number,
-mutt will sort numerically first, and lexically only when two numbers are equal
+Mutt will sort numerically first, and lexically only when two numbers are equal
 in value. (This is like UNIX's sort -n.) A message with no spam attributes at
-all -- that is, one that didn't match any of your spam patterns -- is sorted at
+all ? that is, one that didn't match any of your spam patterns ? is sorted at
 lowest priority. Numbers are sorted next, beginning with 0 and ranging upward.
 Finally, non-numeric strings are sorted, with ?a? taking lower priority than
 ?z?. Clearly, in general, sorting by spam tags is most effective when you can
-coerce your filter to give you a raw number. But in case you can't, mutt can
+coerce your filter to give you a raw number. But in case you can't, Mutt can
 still do something useful.
 
 The nospam command can be used to write exceptions to spam patterns. If a
@@ -2768,25 +2937,73 @@ This might be the default action if you use spam and nospam in conjunction with
 a folder-hook.
 
 You can have as many spam or nospam commands as you like. You can even do your
-own primitive spam detection within mutt -- for example, if you consider all
+own primitive spam detection within Mutt ? for example, if you consider all
 mail from MAILER-DAEMON to be spam, you can use a spam command like this:
 
 spam "^From: .*MAILER-DAEMON"       "999"
 
 26. Setting and Querying Variables
 
-26.1. Commands
+26.1. Variable Types
+
+Mutt supports these types of configuration variables:
+
+boolean
+
+    A boolean expression, either ?yes? or ?no?.
+
+number
+
+    A signed integer number in the range -32768 to 32767.
+
+string
+
+    Arbitrary text.
+
+path
+
+    A specialized string for representing paths including support for mailbox
+    shortcuts (see Section 7, ?Mailbox Shortcuts?) as well as tilde (???) for a
+    user's home directory and more.
+
+quadoption
+
+    Like a boolean but triggers a prompt when set to ?ask-yes? or ?ask-no? with
+    ?yes? and ?no? preselected respectively.
+
+sort order
+
+    A specialized string allowing only particular words as values depending on
+    the variable.
+
+regular expression
+
+    A regular expression, see Section 1, ?Regular Expressions? for an
+    introduction.
+
+folder magic
+
+    Specifies the type of folder to use: mbox, mmdf, mh or maildir. Currently
+    only used to determine the type for newly created folders.
+
+e-mail address
+
+    An e-mail address either with or without realname. The older
+    ?user@example.org (Joe User)? form is supported but strongly deprecated.
+
+user-defined
+
+    Arbitrary text, see Section 26.3, ?User-Defined Variables? for details.
+
+26.2. Commands
 
 The following commands are available to manipulate and query variables:
 
 Usage:
 
 set { [ no | inv ] variable | variable=value } [...]
-
 toggle variable [ variable ...]
-
 unset variable [ variable ...]
-
 reset variable [ variable ...]
 
 This command is used to set (and unset) configuration variables. There are four
@@ -2830,11 +3047,11 @@ variable with ?&? this has the same behavior as the reset command.
 With the reset command there exists the special variable ?all?, which allows
 you to reset all variables to their system defaults.
 
-26.2. User-defined variables
+26.3. User-Defined Variables
 
-26.2.1. Introduction
+26.3.1. Introduction
 
-Along with the variables listed in the Configuration variables section, mutt
+Along with the variables listed in the Configuration variables section, Mutt
 supports user-defined variables with names starting with my_ as in, for
 example, my_cfgdir.
 
@@ -2845,12 +3062,12 @@ Since user-defined variables are expanded in the same way that environment
 variables are (except for the shell-escape command and backtick expansion),
 this feature can be used to make configuration files more readable.
 
-26.2.2. Examples
+26.3.2. Examples
 
 The following example defines and uses the variable my_cfgdir to abbreviate the
 calls of the source command:
 
-Example 3.14. Using user-defined variables for config file readability
+Example 3.15. Using user-defined variables for config file readability
 
 set my_cfgdir = $HOME/mutt/config
 
@@ -2864,7 +3081,7 @@ another variable. In the following example, the value of the $delete is changed
 temporarily while its original value is saved as my_delete. After the macro has
 executed all commands, the original value of $delete is restored.
 
-Example 3.15. Using user-defined variables for backing up other config option
+Example 3.16. Using user-defined variables for backing up other config option
 values
 
 macro pager ,x '\
@@ -2874,7 +3091,7 @@ macro pager ,x '\
 set delete=$my_delete'
 
 
-Since mutt expands such values already when parsing the configuration file(s),
+Since Mutt expands such values already when parsing the configuration file(s),
 the value of $my_delete in the last example would be the value of $delete
 exactly as it was at that point during parsing the configuration file. If
 another statement would change the value for $delete later in the same or
@@ -2882,7 +3099,7 @@ another file, it would have no effect on $my_delete. However, the expansion can
 be deferred to runtime, as shown in the next example, when escaping the dollar
 sign.
 
-Example 3.16. Deferring user-defined variable expansion to runtime
+Example 3.17. Deferring user-defined variable expansion to runtime
 
 macro pager  "\
  set my_old_pager_stop=\$pager_stop pager_stop\
@@ -2892,9 +3109,9 @@ macro pager  "\
 
 
 Note that there is a space between  and the set configuration
-command, preventing mutt from recording the macro's commands into its history.
+command, preventing Mutt from recording the macro's commands into its history.
 
-27. Reading initialization commands from another file
+27. Reading Initialization Commands From Another File
 
 Usage:
 
@@ -2907,10 +3124,10 @@ For example, I place all of my aliases in ?/.mail_aliases so that I can make my
 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 filename is considered to be
-an executable program from which to read input (eg. source ?/bin/myscript|).
+If the filename ends with a vertical bar (?|?), then filename is considered to
+be an executable program from which to read input (eg. source ?/bin/myscript|).
 
-28. Removing hooks
+28. Removing Hooks
 
 Usage:
 
@@ -2925,9 +3142,9 @@ remove all hooks of a specific type by saying something like unhook send-hook.
 29.1. Basic usage
 
 Format strings are a general concept you'll find in several locations through
-the mutt configuration, especially in the $index_format, $pager_format,
-$status_format, and other ?*_format? variables. These can be very
-straightforward, and it's quite possible you already know how to use them.
+the Mutt configuration, especially in the $index_format, $pager_format,
+$status_format, and other related variables. These can be very straightforward,
+and it's quite possible you already know how to use them.
 
 The most basic format string element is a percent symbol followed by another
 character. For example, %s represents a message's Subject: header in the
@@ -2942,19 +3159,19 @@ to specify the minimum and maximum size of the resulting string, as well as its
 justification. If the ?-? sign follows the percent, the string will be
 left-justified instead of right-justified. If there's a number immediately
 following that, it's the minimum amount of space the formatted string will
-occupy -- if it's naturally smaller than that, it will be padded out with
+occupy ? if it's naturally smaller than that, it will be padded out with
 spaces. If a decimal point and another number follow, that's the maximum space
-allowable -- the string will not be permitted to exceed that width, no matter
+allowable ? the string will not be permitted to exceed that width, no matter
 its natural size. Each of these three elements is optional, so that all these
-are legal format strings: %-12s %4c %.15F %-12.15L
+are legal format strings: %-12s, %4c, %.15F and %-12.15L.
 
 Mutt adds some other modifiers to format strings. If you use an equals symbol
 (=) as a numeric prefix (like the minus above), it will force the string to be
 centered within its minimum space range. For example, %=14y will reserve 14
-characters for the %y expansion -- that's the X-Label: header, in
-$index_format. If the expansion results in a string less than 14 characters, it
-will be centered in a 14-character space. If the X-Label for a message were
-"test", that expansion would look like ? test ?.
+characters for the %y expansion ? that's the X-Label: header, in $index_format.
+If the expansion results in a string less than 14 characters, it will be
+centered in a 14-character space. If the X-Label for a message were ?test?,
+that expansion would look like ?     test     ?.
 
 There are two very little-known modifiers that affect the way that an expando
 is replaced. If there is an underline (?_?) character between any format
@@ -2962,7 +3179,33 @@ modifiers (as above) and the expando letter, it will expands in all lower case.
 And if you use a colon (?:?), it will replace all decimal points with
 underlines.
 
-29.2. Filters
+29.2. Conditionals
+
+Depending on the format string variable, some of its 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 sequence_char is an expando, and optional_string is the string you would
+like printed if sequence_char is nonzero. optional_string may contain other
+sequences as well as normal text, but you may not nest optional strings.
+
+Here is an example illustrating how to optionally print the number of new
+messages in a mailbox in $status_format:
+
+%?n?%n new messages.?
+
+You can also switch between two strings using the following construct:
+
+%??&?
+
+If the value of sequence_char is non-zero, if_string will be expanded,
+otherwise else_string will be expanded.
+
+29.3. Filters
 
 Any format string ending in a vertical bar (?|?) will be expanded and piped
 through the first word in the string, using spaces as separator. The string
@@ -2973,19 +3216,56 @@ a replacement format string including % expandos.
 All % expandos in a format string are expanded before the script is called so
 that:
 
-Example 3.17. Using external filters in format strings
+Example 3.18. Using external filters in format strings
 
 set status_format="script.sh '%r %f (%L)'|"
 
 
-will make mutt expand %r, %f and %L before calling the script. The example also
+will make Mutt expand %r, %f and %L before calling the script. The example also
 shows that arguments can be quoted: the script will receive the expanded string
 between the single quotes as the only argument.
 
 A practical example is the mutt_xtitle script installed in the samples
-subdirectory of the mutt documentation: it can be used as filter for
+subdirectory of the Mutt documentation: it can be used as filter for
 $status_format to set the current terminal's title, if supported.
 
+29.4. Padding
+
+In most format strings, Mutt supports different types of padding using special
+%-expandos:
+
+%|X
+
+    When this occurs, Mutt will fill the rest of the line with the character X.
+    For example, filling the rest of the line with dashes is done by setting:
+
+    set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
+
+%>X
+
+    Since the previous expando stops at the end of line, there must be a way to
+    fill the gap between two items via the %>X expando: it puts as many
+    characters X in between two items so that the rest of the line will be
+    right-justified. For example, to not put the version string and hostname
+    the above example on the left but on the right and fill the gap with
+    spaces, one might use (note the space after %>):
+
+    set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
+
+%*X
+
+    Normal right-justification will print everything to the left of the %>,
+    displaying padding and whatever lies to the right only if there's room. By
+    contrast, ?soft-fill? gives priority to the right-hand side, guaranteeing
+    space to display it and showing padding only if there's still room. If
+    necessary, soft-fill will eat text leftwards to make room for rightward
+    text. For example, to right-justify the subject making sure as much as
+    possible of it fits on screen, one might use (note two spaces after %* :
+    the second ensures there's a space between the truncated right-hand side
+    and the subject):
+
+    set index_format="%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?)%*  %s"
+
 Chapter 4. Advanced Usage
 
 Table of Contents
@@ -2994,8 +3274,8 @@ Table of Contents
 2. Patterns: Searching, Limiting and Tagging
 
     2.1. Pattern Modifier
-    2.2. Simple Patterns
-    2.3. Complex Patterns
+    2.2. Simple Searches
+    2.3. Nesting and Boolean Operators
     2.4. Searching by Date
 
 3. Using Tags
@@ -3008,13 +3288,14 @@ Table of Contents
 7. Mailbox Shortcuts
 8. Handling Mailing Lists
 9. Handling multiple folders
-10. Editing threads
+10. Editing Threads
 
-    10.1. Linking threads
-    10.2. Breaking threads
+    10.1. Linking Threads
+    10.2. Breaking Threads
 
 11. Delivery Status Notification (DSN) Support
 12. Start a WWW Browser on URLs
+13. Miscellany
 
 1. Regular Expressions
 
@@ -3028,8 +3309,8 @@ letter, and case insensitive otherwise.
 
 Note
 
-Note that ?\? must be quoted if used for a regular expression in an
-initialization command: ?\\?.
+?\? must be quoted if used for a regular expression in an initialization
+command: ?\\?.
 
 A regular expression is a pattern that describes a set of strings. Regular
 expressions are constructed analogously to arithmetic expressions, by using
@@ -3037,10 +3318,10 @@ various operators to combine smaller expressions.
 
 Note
 
-Note that the regular expression can be enclosed/delimited by either " or '
-which is useful if the regular expression includes a white-space character. See
-Syntax of Initialization Files for more information on " and ' delimiter
-processing. To match a literal " or ' you must preface it with \ (backslash).
+The regular expression can be enclosed/delimited by either " or ' which is
+useful if the regular expression includes a white-space character. See Syntax
+of Initialization Files for more information on " and ' delimiter processing.
+To match a literal " or ' you must preface it with \ (backslash).
 
 The fundamental building blocks are the regular expressions that match a single
 character. Most characters, including all letters and digits, are regular
@@ -3166,9 +3447,9 @@ override these precedence rules.
 
 Note
 
-If you compile Mutt with the GNU rx package, the following operators may also
-be used in regular expressions as described in Table 4.3, ?GNU regular
-expression extensions?.
+If you compile Mutt with the included regular expression engine, the following
+operators may also be used in regular expressions as described in Table 4.3,
+?GNU regular expression extensions?.
 
 Table 4.3. GNU regular expression extensions
 
@@ -3200,6 +3481,8 @@ or may not be available in stock libraries on various systems.
 
 2. Patterns: Searching, Limiting and Tagging
 
+2.1. Pattern Modifier
+
 Many of Mutt's commands allow you to specify a pattern to match (limit,
 tag-pattern, delete-pattern, etc.). Table 4.4, ?Pattern modifiers? shows
 several ways to select messages.
@@ -3300,14 +3583,15 @@ Table 4.4. Pattern modifiers
 |---------+-------------------------------------------------------------------|
 |~V       |cryptographically verified messages                                |
 |---------+-------------------------------------------------------------------|
-|~x EXPR  |messages which contain EXPR in the ?References? field              |
+|~x EXPR  |messages which contain EXPR in the ?References? or ?In-Reply-To?   |
+|         |field                                                              |
 |---------+-------------------------------------------------------------------|
 |~X [MIN]-|messages with MIN to MAX attachments *)                            |
 |[MAX]    |                                                                   |
 |---------+-------------------------------------------------------------------|
 |~y EXPR  |messages which contain EXPR in the ?X-Label? field                 |
 |---------+-------------------------------------------------------------------|
-|~z [MIN]-|messages with a size in the range MIN to MAX *)                    |
+|~z [MIN]-|messages with a size in the range MIN to MAX *) **)                |
 |[MAX]    |                                                                   |
 |---------+-------------------------------------------------------------------|
 |~=       |duplicated messages (see $duplicate_threads)                       |
@@ -3319,41 +3603,45 @@ Table 4.4. Pattern modifiers
 +-----------------------------------------------------------------------------+
 
 
-Where EXPR is a regular expression. Special attention has to be made when using
-regular expressions inside of patterns. Specifically, Mutt's parser for these
-patterns will strip one level of backslash (?\?), which is normally used for
-quoting. If it is your intention to use a backslash in the regular expression,
-you will need to use two backslashes instead (?\\?). You can force mutt to
-treat EXPR as a simple string instead of a regular expression by using =
-instead of ? in the pattern name. For example, =b *.* will find all messages
-that contain the literal string ?*.*?. Simple string matches are less powerful
-than regular expressions but can be considerably faster. This is especially
-true for IMAP folders, because string matches can be performed on the server
-instead of by fetching every message. IMAP treats =h specially: it must be of
-the form "header: substring" and will not partially match header names. The
-substring part may be omitted if you simply wish to find messages containing a
-particular header without regard to its value.
+Where EXPR is a regular expression.
 
 *) The forms ?<[MAX]?, ?>[MIN]?, ?[MIN]-? and ?-[MAX]? are allowed, too.
 
-2.1. Pattern Modifier
-
-Note
+**) The suffixes ?K? and ?M? are allowed to specify kilobyte and megabyte
+respectively.
 
-Note that patterns matching 'lists' of addresses (notably c, C, p, P and t)
-match if there is at least one match in the whole list. If you want to make
-sure that all elements of that list match, you need to prefix your pattern with
-?^?. This example matches all mails which only has recipients from Germany.
+Special attention has to be payed when using regular expressions inside of
+patterns. Specifically, Mutt's parser for these patterns will strip one level
+of backslash (?\?), which is normally used for quoting. If it is your intention
+to use a backslash in the regular expression, you will need to use two
+backslashes instead (?\\?). You can force Mutt to treat EXPR as a simple string
+instead of a regular expression by using = instead of ? in the pattern name.
+For example, =b *.* will find all messages that contain the literal string
+?*.*?. Simple string matches are less powerful than regular expressions but can
+be considerably faster. This is especially true for IMAP folders, because
+string matches can be performed on the server instead of by fetching every
+message. IMAP treats =h specially: it must be of the form ?header: substring?
+and will not partially match header names. The substring part may be omitted if
+you simply wish to find messages containing a particular header without regard
+to its value.
+
+Patterns matching lists of addresses (notably c, C, p, P and t) match if there
+is at least one match in the whole list. If you want to make sure that all
+elements of that list match, you need to prefix your pattern with ?^?. This
+example matches all mails which only has recipients from Germany.
+
+Example 4.1. Matching all addresses in address lists
 
 ^~C \.de$
 
-2.2. Simple Patterns
 
-Mutt supports two versions of so called ?simple searches? which are issued if
+2.2. Simple Searches
+
+Mutt supports two versions of so called ?simple searches?. These are issued if
 the query entered for searching, limiting and similar operations does not seem
-to be a valid pattern (i.e. it does not contain one of these characters: ???, ?
-=? or ?%?). If the query is supposed to contain one of these special
-characters, they must be escaped by prepending a backslash (?\?).
+to contain a valid pattern modifier (i.e. it does not contain one of these
+characters: ???, ?=? or ?%?). If the query is supposed to contain one of these
+special characters, they must be escaped by prepending a backslash (?\?).
 
 The first type is by checking whether the query string equals a keyword
 case-insensitively from Table 4.5, ?Simple search keywords?: If that is the
@@ -3396,7 +3684,7 @@ The second type of simple search is to build a complex search pattern using
 $simple_search as a template. Mutt will insert your query properly quoted and
 search for the composed complex query.
 
-2.3. Complex Patterns
+2.3. Nesting and Boolean Operators
 
 Logical AND is performed by specifying more than one criterion. For example:
 
@@ -3408,17 +3696,17 @@ and that have the word ?elkins? in the ?From? header field.
 Mutt also recognizes the following operators to create more complex search
 patterns:
 
-  * ! -- logical NOT operator
+  * ! ? logical NOT operator
 
-  * | -- logical OR operator
+  * | ? logical OR operator
 
-  * () -- logical grouping operator
+  * () ? 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?.
 
-Example 4.1. Using boolean operators in patterns
+Example 4.2. Using boolean operators in patterns
 
 !(~t mutt|~c mutt) ~f elkins
 
@@ -3434,19 +3722,18 @@ Note
 If a regular expression contains parenthesis, or a vertical bar ("|"), you must
 enclose the expression in double or single quotes since those characters are
 also used to separate different parts of Mutt's pattern language. For example:
-~f "me@(mutt\.org|cs\.hmc\.edu)"
-
-Without the quotes, the parenthesis wouldn't end. This would be separated to
-two OR'd patterns: ?f me@(mutt\.org and cs\.hmc\.edu). They are never what you
-want.
+~f "me@(mutt\.org|cs\.hmc\.edu)" Without the quotes, the parenthesis wouldn't
+end. This would be separated to two OR'd patterns: ?f me@(mutt\.org and cs\.hmc
+\.edu). They are never what you want.
 
 2.4. Searching by Date
 
 Mutt supports two types of dates, absolute and relative.
 
-Absolute. Dates must be in DD/MM/YY format (month and year are optional,
-defaulting to the current month and year). An example of a valid range of dates
-is:
+2.4.1. Absolute Dates
+
+Dates must be in DD/MM/YY format (month and year are 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
 
@@ -3456,11 +3743,10 @@ messages before the given date will be selected. If you omit the maximum
 be selected. If you specify a single date with no dash (?-?), only messages
 sent on the given date will be selected.
 
-Error Margins. You can add error margins to absolute dates. An error margin is
-a sign (+ or -), followed by a digit, followed by one of the units in
-Table 4.6, ?Date units?. As a special case, you can replace the sign by a ?*?
-character, which is equivalent to giving identical plus and minus error
-margins.
+You can add error margins to absolute dates. An error margin is a sign (+ or
+-), followed by a digit, followed by one of the units in Table 4.6, ?Date
+units?. As a special case, you can replace the sign by a ?*? character, which
+is equivalent to giving identical plus and minus error margins.
 
 Table 4.6. Date units
 
@@ -3482,14 +3768,15 @@ the following pattern:
 
 Limit to messages matching: ~d 15/1/2001*2w
 
-Relative. This type of date is relative to the current date, and may be
-specified as:
+2.4.2. Relative Dates
+
+This type of date is relative to the current date, and may be specified as:
 
-  * >offset (messages older than offset units)
+  * >offset for messages older than offset units
 
-  *  operator. If
+there are no tagged messages, Mutt will ?eat? the rest of the macro to abort
+it's execution. Mutt will stop ?eating? the macro when it encounters the
+ operator; after this operator the rest of the macro will be executed
 as normal.
 
 4. Using Hooks
@@ -3533,37 +3820,53 @@ A hook is a concept found in many other programs which allows you to execute
 arbitrary commands before performing some operation. For example, you may wish
 to tailor your configuration based upon which mailbox you are reading, or to
 whom you are sending mail. In the Mutt world, a hook consists of a regular
-expression or pattern along with a configuration option/command. See
+expression or pattern along with a configuration option/command. See:
+
+  * account-hook
+
+  * charset-hook
+
+  * crypt-hook
+
+  * fcc-hook
+
+  * fcc-save-hook
 
   * folder-hook
 
-  * send-hook
+  * iconv-hook
+
+  * mbox-hook
 
   * message-hook
 
-  * save-hook
+  * reply-hook
 
-  * mbox-hook
+  * save-hook
 
-  * fcc-hook
+  * send-hook
 
-  * fcc-save-hook
+  * send2-hook
 
 for specific details on each type of hook available.
 
 Note
 
 If a hook changes configuration settings, these changes remain effective until
-the end of the current mutt session. As this is generally not desired, a
-default hook needs to be added before all other hooks to restore configuration
-defaults. Here is an example with send-hook and the my_hdr directive:
+the end of the current Mutt session. As this is generally not desired, a
+?default? hook needs to be added before all other hooks of that type to restore
+configuration defaults.
 
-Example 4.2. Combining send-hook and my_hdr
+Example 4.3. Specifying a ?default? hook
 
 send-hook . 'unmy_hdr From:'
 send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
 
 
+In Example 4.3, ?Specifying a default hook?, by default the value of $from and
+$realname is not overridden. When sending messages either To: or Cc: to
+, the From: header is changed to .
+
 4.1. Message Matching in Hooks
 
 Hooks that act upon messages (message-hook, reply-hook, send-hook, send2-hook,
@@ -3575,7 +3878,7 @@ purposes you want to match different criteria.
 Mutt allows the use of the search pattern language for matching messages in
 hook commands. This works in exactly the same way as it would when limiting or
 searching the mailbox, except that you are restricted to those operators which
-match information mutt extracts from the header of the message (i.e., from, to,
+match information Mutt extracts from the header of the message (i.e., from, to,
 cc, date, subject, etc.).
 
 For example, if you wanted to set your return address based upon sending mail
@@ -3595,7 +3898,7 @@ $default_hook that is in effect at that time will be used.
 5. External Address Queries
 
 Mutt supports connecting to external directory databases such as LDAP, ph/qi,
-bbdb, or NIS through a wrapper script which connects to mutt using a simple
+bbdb, or NIS through a wrapper script which connects to Mutt using a simple
 interface. Using the $query_command variable, you specify the wrapper command
 to use. For example:
 
@@ -3614,7 +3917,7 @@ me@cs.hmc.edu           Michael Elkins  mutt dude
 blong@fiction.net       Brandon Long    mutt and more
 roessler@does-not-exist.org        Thomas Roessler mutt pgp
 
-There are two mechanisms for accessing the query function of mutt. One is to do
+There are two mechanisms for accessing the query function of Mutt. One is to do
 a query from the index menu using the  function (default: Q). This will
 prompt for a query, then bring up the query menu which will list the matching
 responses. From the query menu, you can select addresses to create aliases, or
@@ -3624,66 +3927,89 @@ new query appended to the current responses.
 The other mechanism for accessing the query function is for address completion,
 similar to the alias completion. In any prompt for address entry, you can use
 the  function (default: ^T) to run a query based on the current
-address you have typed. Like aliases, mutt will look for what you have typed
+address you have typed. Like aliases, Mutt will look for what you have typed
 back to the last space or comma. If there is a single response for that query,
-mutt will expand the address in place. If there are multiple responses, mutt
+Mutt will expand the address in place. If there are multiple responses, Mutt
 will activate the query menu. At the query menu, you can select one or more
 addresses to be added to the prompt.
 
 6. Mailbox Formats
 
-Mutt supports reading and writing of four different mailbox formats: mbox,
-MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to
-use a flag for different mailbox types. When creating new mailboxes, Mutt uses
-the default specified with the $mbox_type variable.
+Mutt supports reading and writing of four different local mailbox formats:
+mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there is no
+need to use a flag for different mailbox types. When creating new mailboxes,
+Mutt uses the default specified with the $mbox_type variable. A short
+description of the formats follows.
 
-mbox. This is the most widely used mailbox format for UNIX. All messages are
-stored in a single file. Each message has a line of the form:
+mbox. This is a widely used mailbox format for UNIX. All 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).
+line). The mbox format requires mailbox locking, is prone to mailbox corruption
+with concurrently writing clients or misinterpreted From_ lines. Depending on
+the environment, new mail detection can be unreliable. Mbox folders are fast to
+open and easy to archive.
 
 MMDF. This is a variant of the mbox format. Each message is surrounded by lines
-containing ?^A^A^A^A? (four control-A's).
+containing ?^A^A^A^A? (four control-A's). The same problems as for mbox apply
+(also with finding the right message separator as four control-A's may appear
+in message bodies).
 
 MH. A radical departure from mbox and MMDF, a mailbox consists of a directory
 and each message is stored in a separate file. The filename indicates the
 message number (however, this is may not correspond to the message number Mutt
-displays). Deleted messages are renamed with a comma (,) prepended to the
+displays). Deleted messages are renamed with a comma (?,?) prepended to the
 filename. Mutt detects this type of mailbox by looking for either .mh_sequences
-or .xmhcache (needed to distinguish normal directories from MH mailboxes).
+or .xmhcache files (needed to distinguish normal directories from MH
+mailboxes). MH is more robust with concurrent clients writing the mailbox, but
+still may suffer from lost flags; message corruption is less likely to occur
+than with mbox/mmdf. It's usually slower to open compared to mbox/mmdf since
+many small files have to be read (Mutt provides Section 7.1, ?Header Caching?
+to greatly speed this process up). Depending on the environment, MH is not very
+disk-space efficient.
 
 Maildir. The newest of the mailbox formats, used by the Qmail MTA (a
 replacement for sendmail). Similar to MH, except that it adds three
 subdirectories of the mailbox: tmp, new and cur. Filenames for the messages are
 chosen in such a way they are unique, even when two programs are writing the
-mailbox over NFS, which means that no file locking is needed.
+mailbox over NFS, which means that no file locking is needed and corruption is
+very unlikely. Maildir maybe slower to open without caching in Mutt, it too is
+not very disk-space efficient depending on the environment. Since no additional
+files are used for metadata (which is embedded in the message filenames) and
+Maildir is locking-free, it's easy to sync across different machines using
+file-level synchronization tools.
 
 7. Mailbox Shortcuts
 
 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.
+path or in path-related configuration variables. Note that these only work at
+the beginning of a string.
 
-  * ! -- refers to your $spoolfile (incoming) mailbox
+  * ! ? refers to your $spoolfile (incoming) mailbox
 
-  * > -- refers to your $mbox file
+  * > ? refers to your $mbox file
 
-  * < -- refers to your $record file
+  * < ? refers to your $record file
 
-  * ^ -- refers to the current mailbox
+  * ^ ? refers to the current mailbox
 
-  * - or !! -- refers to the file you've last visited
+  * - or !! ? refers to the file you've last visited
 
-  * ? -- refers to your home directory
+  * ? ? refers to your home directory
 
-  * = or + -- refers to your $folder directory
+  * = or + ? refers to your $folder directory
 
-  * @alias -- refers to the default save folder as determined by the address of
+  * @alias ? refers to the default save folder as determined by the address of
     the alias
 
+For example, to store a copy of outgoing messages in the folder they were
+composed in, a folder-hook can be used to set $record:
+
+folder-hook . 'set record=^'
+
 8. Handling Mailing Lists
 
 Mutt has a few configuration options that make dealing with large amounts of
@@ -3691,15 +4017,15 @@ mail easier. The first thing you must do is to let Mutt know what addresses you
 consider to be mailing lists (technically this does not have to be a mailing
 list, but that is what it is most often used for), and what lists you are
 subscribed to. This is accomplished through the use of the lists and subscribe
-commands in your muttrc.
+commands in your .muttrc.
 
 Now that Mutt knows what your mailing lists are, it can do several things, the
 first of which is the ability to show the name of a list through which you
 received a message (i.e., of a subscribed list) in the index menu display. This
 is useful to distinguish between personal and list mail in the same mailbox. In
-the $index_format variable, the escape ?%L? will return the string ?To ?
+the $index_format variable, the expando ?%L? will print 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).
+?Cc? field (otherwise it prints 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 the message they reply
@@ -3711,7 +4037,7 @@ see below).
 
 Mutt also supports the Mail-Followup-To header. When you send a message to a
 list of recipients which includes one or several subscribed mailing lists, and
-if the $followup_to option is set, mutt will generate a Mail-Followup-To header
+if the $followup_to option is set, Mutt will generate a Mail-Followup-To header
 which contains all the recipients to whom you send this message, but not your
 address. This indicates that group-replies or list-replies (also known as
 ?followups?) to this message should only be sent to the original recipients of
@@ -3719,7 +4045,7 @@ the message, and not separately to you - you'll receive your copy through one
 of the mailing lists you are subscribed to.
 
 Conversely, when group-replying or list-replying to a message which has a
-Mail-Followup-To header, mutt will respect this header if the
+Mail-Followup-To header, Mutt will respect this header if the
 $honor_followup_to configuration variable is set. Using list-reply will in this
 case also make sure that the reply goes to the mailing list, even if it's not
 specified in the list of recipients in the Mail-Followup-To.
@@ -3742,11 +4068,11 @@ the ?Reply-To? field will be used when present.
 
 The ?X-Label:? header field can be used to further identify mailing lists or
 list subject matter (or just to annotate messages individually). The
-$index_format variable's ?%y? and ?%Y? escapes can be used to expand ?X-Label:?
-fields in the index, and Mutt's pattern-matcher can match regular expressions
-to ?X-Label:? fields with the ??y? selector. ?X-Label:? is not a standard
-message header field, but it can easily be inserted by procmail and other mail
-filtering agents.
+$index_format variable's ?%y? and ?%Y? expandos can be used to expand
+?X-Label:? fields in the index, and Mutt's pattern-matcher can match regular
+expressions to ?X-Label:? fields with the ??y? selector. ?X-Label:? is not a
+standard message header field, but it can easily be inserted by procmail and
+other mail filtering agents.
 
 Lastly, Mutt has the ability to sort the mailbox into threads. A thread is a
 group of messages which all relate to the same subject. This is usually
@@ -3759,7 +4085,7 @@ value.
 9. Handling multiple folders
 
 Mutt supports setups with multiple folders, allowing all of them to be
-monitored for new mail (see Section 14, ?Monitoring incoming mail? for
+monitored for new mail (see Section 14, ?Monitoring Incoming Mail? for
 details).
 
 When in the index menu and being idle (also see $timeout), Mutt periodically
@@ -3778,35 +4104,35 @@ For the pager, index and directory browser menus, Mutt contains the
 folders with new mail in the command line at the bottom of the screen.
 
 For the index, by default Mutt displays the number of mailboxes with new mail
-in the status bar, please refer to the $index_format variable for details.
+in the status bar, please refer to the $status_format variable for details.
 
 When changing folders, Mutt fills the prompt with the first folder from the
 mailboxes list containing new mail (if any), pressing space will cycle through
 folders with new mail.
 
-10. Editing threads
+10. Editing Threads
 
 Mutt has the ability to dynamically restructure threads that are broken either
 by misconfigured software or bad behavior from some correspondents. This allows
-to clean your mailboxes formats) from these annoyances which make it hard to
-follow a discussion.
+to clean your mailboxes from these annoyances which make it hard to follow a
+discussion.
 
-10.1. Linking threads
+10.1. Linking Threads
 
-Some mailers tend to "forget" to correctly set the "In-Reply-To:" and
-"References:" headers when replying to a message. This results in broken
+Some mailers tend to ?forget? to correctly set the ?In-Reply-To:? and
+?References:? headers when replying to a message. This results in broken
 discussions because Mutt has not enough information to guess the correct
 threading. You can fix this by tagging the reply, then moving to the parent
 message and using the  function (bound to & by default). The
-reply will then be connected to this "parent" message.
+reply will then be connected to this parent message.
 
 You can also connect multiple children at once, tagging them and using the
-tag-prefix command (';') or the auto_tag option.
+ command (';') or the $auto_tag option.
 
-10.2. Breaking threads
+10.2. Breaking Threads
 
 On mailing lists, some people are in the bad habit of starting a new discussion
-by hitting "reply" to any message from the list and changing the subject to a
+by hitting ?reply? to any message from the list and changing the subject to a
 totally unrelated one. You can fix such threads by using the 
 function (bound by default to #), which will turn the subthread starting from
 the current message into a whole different thread.
@@ -3829,7 +4155,7 @@ make requests as to what type of status messages should be returned. Please
 consider your MTA documentation whether DSN is supported.
 
 For SMTP delivery using $smtp_url, it depends on the capabilities announced by
-the server whether mutt will attempt to request DSN or not.
+the server whether Mutt will attempt to request DSN or not.
 
 12. Start a WWW Browser on URLs
 
@@ -3841,23 +4167,46 @@ contrib/ and the configuration commands:
 macro index \cb |urlview\n
 macro pager \cb |urlview\n
 
+13. Miscellany
+
+This section documents various features that fit nowhere else.
+
+Address normalization
+
+    Mutt normalizes all e-mail addresses to the simplest form possible. If an
+    address contains a realname, the form Joe User  is used
+    and the pure e-mail address without angle brackets otherwise, i.e. just
+    joe@example.com.
+
+    This normalization affects all headers Mutt generates including aliases.
+
+Initial folder selection
+
+    The folder Mutt opens at startup is determined as follows: the folder
+    specified in the $MAIL environment variable if present. Otherwise, the
+    value of $MAILDIR is taken into account. If that isn't present either, Mutt
+    takes the user's mailbox in the mailspool as determined at compile-time
+    (which may also reside in the home directory). The $spoolfile setting
+    overrides this selection. Highest priority has the mailbox given with the
+    -f command line option.
+
 Chapter 5. Mutt's MIME Support
 
 Table of Contents
 
 1. Using MIME in Mutt
 
-    1.1. Viewing MIME messages in the pager
+    1.1. Viewing MIME Messages in the Pager
     1.2. The Attachment Menu
     1.3. The Compose Menu
 
-2. MIME Type configuration with mime.types
-3. MIME Viewer configuration with mailcap
+2. MIME Type Configuration with mime.types
+3. MIME Viewer Configuration with Mailcap
 
-    3.1. The Basics of the mailcap file
-    3.2. Secure use of mailcap
-    3.3. Advanced mailcap Usage
-    3.4. Example mailcap files
+    3.1. The Basics of the Mailcap File
+    3.2. Secure Use of Mailcap
+    3.3. Advanced Mailcap Usage
+    3.4. Example Mailcap Files
 
 4. MIME Autoview
 5. MIME Multipart/Alternative
@@ -3878,7 +4227,7 @@ types.
 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.
 
-1.1. Viewing MIME messages in the pager
+1.1. Viewing MIME Messages in the Pager
 
 When you select a message from the index and view it in the pager, Mutt decodes
 the message to a text representation. Mutt internally supports a number of MIME
@@ -3901,14 +4250,15 @@ If Mutt cannot deal with a MIME type, it will display a message like:
 
 1.2. The Attachment Menu
 
-The default binding for view-attachments is `v', which displays the attachment
-menu for a message. The attachment menu displays a list of the attachments in a
-message. From the attachment menu, you can save, print, pipe, delete, and view
-attachments. You can apply these operations to a group of attachments at once,
-by tagging the attachments and by using the ?tag-prefix? operator. You can also
-reply to the current message from this menu, and only the current attachment
-(or the attachments tagged) will be quoted in your reply. You can view
-attachments as text, or view them using the mailcap viewer definition.
+The default binding for  is ?v?, which displays the
+attachment menu for a message. The attachment menu displays a list of the
+attachments in a message. From the attachment menu, you can save, print, pipe,
+delete, and view attachments. You can apply these operations to a group of
+attachments at once, by tagging the attachments and by using the 
+operator. You can also reply to the current message from this menu, and only
+the current attachment (or the attachments tagged) will be quoted in your
+reply. You can view attachments as text, or view them using the mailcap viewer
+definition.
 
 Finally, you can apply the usual message-related functions (like
 , and the  and  functions) to attachments of
@@ -3932,17 +4282,18 @@ Attachments appear as follows:
   2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz 
 
 The '-' denotes that Mutt will delete the file after sending (or postponing, or
-canceling) the message. It can be toggled with the toggle-unlink command
+canceling) the message. It can be toggled with the  command
 (default: u). The next field is the MIME content-type, and can be changed with
-the edit-type command (default: ^T). The next field is the encoding for the
+the  command (default: ^T). The next field is the encoding for the
 attachment, which allows a binary message to be encoded for transmission on
-7bit links. It can be changed with the edit-encoding command (default: ^E). The
-next field is the size of the attachment, rounded to kilobytes or megabytes.
-The next field is the filename, which can be changed with the rename-file
-command (default: R). The final field is the description of the attachment, and
-can be changed with the edit-description command (default: d).
+7bit links. It can be changed with the  command (default: ^E).
+The next field is the size of the attachment, rounded to kilobytes or
+megabytes. The next field is the filename, which can be changed with the
+ command (default: R). The final field is the description of the
+attachment, and can be changed with the  command (default:
+d).
 
-2. MIME Type configuration with mime.types
+2. MIME Type Configuration with mime.types
 
 When you add an attachment to your mail message, Mutt searches your personal
 mime.types file at ${HOME}/.mime.types, and then the system mime.types file at
@@ -3963,7 +4314,7 @@ 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 as text/plain. If the
 file contains binary information, then Mutt will mark it as application/
 octet-stream. You can change the MIME type that Mutt assigns to an attachment
-by using the edit-type command from the compose menu (default: ^T). The MIME
+by using the  command from the compose menu (default: ^T). The MIME
 type is actually a major mime type followed by the sub-type, separated by a '/
 '. 6 major types: application, text, image, video, audio, and model have been
 approved after various internet discussions. Mutt recognizes all of these if
@@ -3973,14 +4324,14 @@ molecular modeling community to pass molecular data in various forms to various
 molecular viewers. Non-recognized mime types should only be used if the
 recipient of the message is likely to be expecting such attachments.
 
-3. MIME Viewer configuration with mailcap
+3. MIME Viewer Configuration with Mailcap
 
 Mutt supports RFC 1524 MIME Configuration, in particular the Unix specific
 format specified in Appendix A of RFC 1524. This file format is commonly
 referred to as the mailcap format. Many MIME compliant programs utilize the
 mailcap format, allowing you to specify handling for all MIME types in one
-place for all programs. Programs known to use this format include Netscape,
-XMosaic, lynx and metamail.
+place for all programs. Programs known to use this format include Firefox, lynx
+and metamail.
 
 In order to handle various MIME types that Mutt can not handle internally, Mutt
 parses a series of external configuration files to find an external handler.
@@ -4000,7 +4351,7 @@ the following files:
  6. /usr/local/etc/mailcap
 
 where $HOME is your home directory. The $PKGDATADIR and the $SYSCONFDIR
-directories depend on where mutt is installed: the former is the default for
+directories depend on where Mutt is installed: the former is the default for
 shared data, the latter for system configuration files.
 
 The default search path can be obtained by running the following command:
@@ -4010,7 +4361,7 @@ mutt -nF /dev/null -Q mailcap_path
 In particular, the metamail distribution will install a mailcap file, usually
 as /usr/local/etc/mailcap, which contains some baseline entries.
 
-3.1. The Basics of the mailcap file
+3.1. The Basics of the Mailcap File
 
 A mailcap file consists of a series of lines which are comments, blank, or
 definitions.
@@ -4073,14 +4424,14 @@ text/*; more
 
 This is the simplest form of a mailcap file.
 
-3.2. Secure use of mailcap
+3.2. Secure Use of Mailcap
 
 The interpretation of shell meta-characters embedded in MIME parameters can
 lead to security problems in general. Mutt tries to quote parameters in
 expansion of %s syntaxes properly, and avoids risky characters by substituting
 them, see the $mailcap_sanitize variable.
 
-Although mutt's procedures to invoke programs with mailcap seem to be safe,
+Although Mutt's procedures to invoke programs with mailcap seem to be safe,
 there are other applications parsing mailcap, maybe taking less care of it.
 Therefore you should pay attention to the following rules:
 
@@ -4100,7 +4451,7 @@ further expansion):
 text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
         && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
 
-3.3. Advanced mailcap Usage
+3.3. Advanced Mailcap Usage
 
 3.3.1. Optional Fields
 
@@ -4141,7 +4492,7 @@ composetyped=
 
     This flag specifies the command to use to create a new attachment of a
     specific MIME type. This command differs from the compose command in that
-    mutt will expect standard MIME headers on the data. This can be used to
+    Mutt will expect standard MIME headers on the data. This can be used to
     specify parameters, filename, description, etc. for a new attachment. Mutt
     supports this from the compose menu.
 
@@ -4175,12 +4526,12 @@ test=
     test failed, and Mutt continues searching for the right entry. Note that
     the content-type must match before Mutt performs the test. For example:
 
-    text/html; netscape -remote 'openURL(%s)' ; test=RunningX
+    text/html; firefox -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 display the text/html object. If
+    returns 0, then Mutt will call firefox to display the text/html object. If
     RunningX doesn't return 0, then Mutt will go on to the next entry and use
     lynx to display the text/html object.
 
@@ -4204,7 +4555,7 @@ interactively from the attachment menu. In addition, you 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;      firefox -remote 'openURL(%s)' ; test=RunningX
 text/html;      lynx %s; nametemplate=%s.html
 text/html;      lynx -dump %s; nametemplate=%s.html; copiousoutput
 
@@ -4216,7 +4567,7 @@ use the second entry for interactive viewing.
 3.3.3. Command Expansion
 
 The various commands defined in the mailcap files are passed to the /bin/sh
-shell using the system() function. Before the command is passed to /bin/sh -c,
+shell using the system(3) function. Before the command is passed to /bin/sh -c,
 it is parsed to expand various special parameters with information from Mutt.
 The keywords Mutt expands are:
 
@@ -4255,7 +4606,7 @@ Mutt does not currently support the %F and %n keywords specified in RFC 1524.
 The main purpose of these parameters is for multipart messages, which is
 handled internally by Mutt.
 
-3.4. Example mailcap files
+3.4. Example Mailcap Files
 
 This mailcap file is fairly simple and standard:
 
@@ -4263,8 +4614,8 @@ This mailcap file is fairly simple and standard:
 video/*;        xanim %s > /dev/null
 image/*;        xv %s > /dev/null
 
-# I'm always running netscape (if my computer had more memory, maybe)
-text/html;      netscape -remote 'openURL(%s)'
+# I'm always running firefox (if my computer had more memory, maybe)
+text/html;      firefox -remote 'openURL(%s)'
 
 This mailcap file shows quite a number of examples:
 
@@ -4272,12 +4623,12 @@ This mailcap file shows quite a number of examples:
 # send that to /dev/null so I don't see it
 video/*;        xanim %s > /dev/null
 
-# Send html to a running netscape by remote
-text/html;      netscape -remote 'openURL(%s)'; test=RunningNetscape
+# Send html to a running firefox by remote
+text/html;      firefox -remote 'openURL(%s)'; test=RunningFirefox
 
-# If I'm not running netscape but I am running X, start netscape on the
+# If I'm not running firefox but I am running X, start firefox on the
 # object
-text/html;      netscape %s; test=RunningX
+text/html;      firefox %s; test=RunningX
 
 # Else use lynx to view it as text
 text/html;      lynx %s
@@ -4288,7 +4639,7 @@ text/html;      lynx -dump %s; copiousoutput
 # I use enscript to print text in two columns to a page
 text/*;         more %s; print=enscript -2Gr %s
 
-# Netscape adds a flag to tell itself to view jpegs internally
+# Firefox adds a flag to tell itself to view jpegs internally
 image/jpeg;xv %s; x-mozilla-flags=internal
 
 # Use xv to view images if I'm running X
@@ -4306,6 +4657,11 @@ application/ms-excel; open.pl %s
 
 4. MIME Autoview
 
+Usage:
+
+auto-view mimetype [ mimetype ...]
+unauto-view { * | mimetype ... }
+
 In addition to explicitly telling Mutt to view an attachment with the MIME
 viewer defined in the mailcap file, Mutt has support for automatically viewing
 MIME attachments while in the pager.
@@ -4315,10 +4671,8 @@ copiousoutput option to denote that it is non-interactive. Usually, you also
 use the entry to convert the attachment to a text representation which you can
 view in the pager.
 
-You then use the auto_view muttrc command to list the content-types that you
-wish to view automatically.
-
-For instance, if you set auto_view to:
+You then use the auto_view .muttrc command to list the content-types that you
+wish to view automatically. For instance, if you set it to:
 
 auto_view text/html application/x-gunzip \
   application/postscript image/gif application/x-tar-gz
@@ -4333,22 +4687,22 @@ application/x-gunzip;   gzcat; copiousoutput
 application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
 application/postscript; ps2ascii %s; copiousoutput
 
-?unauto_view? can be used to remove previous entries from the autoview list.
-This can be used with message-hook to autoview messages based on size, etc.
-?unauto_view *? will remove all previous entries.
+unauto_view can be used to remove previous entries from the autoview list. This
+can be used with message-hook to autoview messages based on size, etc. ?
+unauto_view *? will remove all previous entries.
 
 5. MIME Multipart/Alternative
 
 Mutt has some heuristics for determining which attachment of a multipart/
-alternative type to display. First, mutt will check the alternative_order list
-to determine if one of the available types is preferred. The alternative_order
-list consists of a number of mimetypes in order, including support for implicit
-and explicit wildcards, for example:
+alternative type to display. First, Mutt will check the alternative_order list
+to determine if one of the available types is preferred. It consists of a
+number of 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
+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.
 
 To remove a MIME type from the alternative_order list, use the
@@ -4363,18 +4717,18 @@ search for messages by attachment count. You also can configure what kinds of
 attachments qualify for this feature with the attachments and unattachments
 commands.
 
-In order to provide this information, mutt needs to fully MIME-parse all
+In order to provide this information, Mutt needs to fully MIME-parse all
 messages affected first. This can slow down operation especially for remote
 mail folders such as IMAP because all messages have to be downloaded first
 regardless whether the user really wants to view them or not.
 
 The syntax is:
 
-attachments   {+|-}disposition mime-type
-unattachments {+|-}disposition mime-type
-attachments   ?
+attachments { + | - }disposition mime-type
+unattachments { + | - }disposition mime-type
+attachments ?
 
-Disposition is the attachment's Content-disposition type -- either inline or
+disposition is the attachment's Content-Disposition type ? either inline or
 attachment. You can abbreviate this to I or A.
 
 Disposition is prefixed by either a + symbol or a - symbol. If it's a +, you're
@@ -4382,7 +4736,7 @@ saying that you want to allow this disposition and MIME type to qualify. If
 it's a -, you're saying that this disposition and MIME type is an exception to
 previous + rules. There are examples below of how this is useful.
 
-Mime-type is, unsurprisingly, the MIME type of the attachment you want to
+mime-type is, unsurprisingly, the MIME type of the attachment you want to
 affect. A MIME type is always of the format major/minor, where major describes
 the broad category of document you're looking at, and minor describes the
 specific type within that category. The major part of mime-type must be literal
@@ -4392,7 +4746,7 @@ expression. (Therefore, ?*/.*? matches any MIME type.)
 The MIME types you give to the attachments directive are a kind of pattern.
 When you use the attachments directive, the patterns you specify are added to a
 list. When you use unattachments, the pattern is removed from the list. The
-patterns are not expanded and matched to specific MIME types at this time --
+patterns are not expanded and matched to specific MIME types at this time ?
 they're just text in a list. They're only matched when actually evaluating a
 message.
 
@@ -4454,6 +4808,11 @@ settings in Muttrc format, so that it can be pasted elsewhere.
 
 7. MIME Lookup
 
+Usage:
+
+mime-lookup mimetype [ mimetype ...]
+unmime-lookup { * | mimetype ... }
+
 Mutt's mime_lookup list specifies a list of mime-types that should not be
 treated according to their mailcap entry. This option is designed to deal with
 binary types such as application/octet-stream. When an attachment's mime-type
@@ -4466,37 +4825,38 @@ rules in the mailcap file and according to any other configuration options
 mime_lookup application/octet-stream application/X-Lotus-Manuscript
 
 In addition, the unmime_lookup command may be used to disable this feature for
-any particular mime-type if it had been set, for example, in a global muttrc.
+any particular mime-type if it had been set, for example, in a global .muttrc.
 
-Chapter 6. Optional features
+Chapter 6. Optional Features
 
 Table of Contents
 
-1. General notes
+1. General Notes
 
-    1.1. Enabling/disabling features
-    1.2. URL syntax
+    1.1. Enabling/Disabling Features
+    1.2. URL Syntax
 
 2. SSL/TLS Support
 3. POP3 Support
 4. IMAP Support
 
-    4.1. The Folder Browser
+    4.1. The IMAP Folder Browser
     4.2. Authentication
 
 5. SMTP Support
-6. Managing multiple accounts
-7. Local caching
+6. Managing Multiple Accounts
+7. Local Caching
 
-    7.1. Header caching
-    7.2. Body caching
+    7.1. Header Caching
+    7.2. Body Caching
     7.3. Maintenance
 
-8. Exact address generation
+8. Exact Address Generation
+9. Sending Anonymous Messages via Mixmaster
 
-1. General notes
+1. General Notes
 
-1.1. Enabling/disabling features
+1.1. Enabling/Disabling Features
 
 Mutt supports several of optional features which can be enabled or disabled at
 compile-time by giving the configure script certain arguments. These are listed
@@ -4504,42 +4864,45 @@ in the ?Optional features? section of the configure --help output.
 
 Which features are enabled or disabled can later be determined from the output
 of mutt -v. If a compile option starts with ?+? it is enabled and disabled if
-prefixed with ?-?. For example, if mutt was compiled using GnuTLS for encrypted
+prefixed with ?-?. For example, if Mutt was compiled using GnuTLS for encrypted
 communication instead of OpenSSL, mutt -v would contain:
 
 -USE_SSL_OPENSSL +USE_SSL_GNUTLS
 
-1.2. URL syntax
+1.2. URL Syntax
 
 Mutt optionally supports the IMAP, POP3 and SMTP protocols which require to
-access servers using URLs. The canonical syntax for specifying URLs in mutt is
+access servers using URLs. The canonical syntax for specifying URLs in Mutt is
 (an item enclosed in [] means it is optional and may be omitted):
 
 proto[s]://[username[:password]@]server[:port]/[path]
 
 proto is the communication protocol: imap for IMAP, pop for POP3 and smtp for
-SMTP. If ?s? for ?secure communication? is appended, mutt will attempt to
-establish an encrypted communication using SSL or TLS. If no explicit port is
-given, mutt will use the system's default for the given protocol.
+SMTP. If ?s? for ?secure communication? is appended, Mutt will attempt to
+establish an encrypted communication using SSL or TLS.
+
+Since all protocols supported by Mutt support/require authentication, login
+credentials may be specified in the URL. This has the advantage that multiple
+IMAP, POP3 or SMTP servers may be specified (which isn't possible using, for
+example, $imap_user). The username may contain the ?@? symbol being used by
+many mail systems as part of the login name. A password can be given, too but
+is not recommended if the URL is specified in a configuration file on disk.
 
-Since all protocols by mutt support authentication, the username may be given
-directly in the URL instead of using the pop_user or imap_user variables. It
-may contain the ?@? symbol being used by many mail systems as part of the login
-name. A password can be given, too but is not recommended if the URL is
-specified in a configuration file on disk.
+If no port number is given, Mutt will use the system's default for the given
+protocol (usually consulting /etc/services).
 
 The optional path is only relevant for IMAP.
 
-For IMAP for example, you can select an alternative port by specifying it with
-the server: imap://imapserver:port/INBOX. You can also specify different
-username for each folder: imap://username@imapserver[:port]/INBOX or imap://
-username2@imapserver[:port]/path/to/folder. Replacing imap:// by imaps:// would
-make mutt attempt to connect using SSL or TLS on a different port to encrypt
-the communication.
+Example 6.1. URLs
+
+pops://host/
+imaps://user@host/INBOX/Sent
+smtp://user@host:587/
+
 
 2. SSL/TLS Support
 
-If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
+If Mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
 compiled with support for SSL or TLS using either OpenSSL or GnuTLS ( by
 running the configure script with the --enable-ssl=... option for OpenSSL or
 --enable-gnutls=... for GnuTLS). Mutt can then attempt to encrypt communication
@@ -4548,19 +4911,26 @@ communication?.
 
 3. POP3 Support
 
-If Mutt was compiled with POP3 support (by running the configure script with
-the --enable-pop flag), it has the ability to work with mailboxes located on a
+If Mutt is compiled with POP3 support (by running the configure script with the
+--enable-pop flag), it has the ability to work with mailboxes located on a
 remote POP3 server and fetch mail for local browsing.
 
 Remote POP3 servers can be accessed using URLs with the pop protocol for
-unencrypted and pops for encrypted communication, see Section 1.2, ?URL syntax?
+unencrypted and pops for encrypted communication, see Section 1.2, ?URL Syntax?
 for details.
 
 Polling for new mail is more expensive over POP3 than locally. For this reason
 the frequency at which Mutt will check for mail remotely can be controlled by
 the $pop_checkinterval variable, which defaults to every 60 seconds.
 
-Another way to access your POP3 mail is the  function (default: G).
 It allows to connect to $pop_host, 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.
@@ -4568,7 +4938,7 @@ been local.
 Note
 
 If you only need to fetch all messages to a local mailbox you should consider
-using a specialized program, such as fetchmail, getmail or similar.
+using a specialized program, such as fetchmail(1), getmail(1) or similar.
 
 4. IMAP Support
 
@@ -4577,7 +4947,7 @@ the --enable-imap flag), it has the ability to work with folders located on a
 remote IMAP server.
 
 You can access the remote inbox by selecting the folder by its URL (see
-Section 1.2, ?URL syntax? for details) using the imap or imaps protocol.
+Section 1.2, ?URL Syntax? for details) using the imap or imaps protocol.
 Alternatively, a pine-compatible notation is also supported, ie {[username@]
 imapserver[:port][/ssl]}path/to/folder
 
@@ -4590,12 +4960,13 @@ the folders you are subscribed to, or all folders with the toggle-subscribed
 command. See also the $imap_list_subscribed variable.
 
 Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
-want to carefully tune the $mail_check and $timeout variables. Personally I use
+want to carefully tune the $mail_check and $timeout variables. Reasonable
+values are:
 
 set mail_check=90
 set timeout=15
 
-with relatively good results over my slow modem line.
+with relatively good results even over slow modem lines.
 
 Note
 
@@ -4603,13 +4974,13 @@ Note that if you are using mbox as the mail store on UW servers prior to
 v12.250, the server has been reported to disconnect a client if another client
 selects the same folder.
 
-4.1. The Folder Browser
+4.1. The IMAP Folder Browser
 
-As of version 1.2, mutt supports browsing mailboxes on an IMAP server. This is
+As of version 1.2, Mutt supports browsing mailboxes on an IMAP server. This is
 mostly the same as the local file browser, with the following differences:
 
-  * In lieu of file permissions, mutt displays the string "IMAP", possibly
-    followed by the symbol "+", indicating that the entry contains both
+  * In lieu of file permissions, Mutt displays the string ?IMAP?, possibly
+    followed by the symbol ?+?, indicating that the entry contains both
     messages and subfolders. On Cyrus-like servers folders will often contain
     both messages and subfolders.
 
@@ -4618,9 +4989,9 @@ mostly the same as the local file browser, with the following differences:
     subfolder view. If you wish to view the messages in that folder, you must
     use view-file instead (bound to space by default).
 
-  * You can create, delete and rename mailboxes with the create-mailbox,
-    delete-mailbox, and rename-mailbox commands (default bindings: C, d and r,
-    respectively). You may also subscribe and unsubscribe to mailboxes
+  * You can create, delete and rename mailboxes with the ,
+    , and  commands (default bindings: C, d and
+    r, respectively). You may also  and  to mailboxes
     (normally these are bound to s and u, respectively).
 
 4.2. Authentication
@@ -4630,7 +5001,7 @@ CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM
 authentication for you poor exchange users out there, but it has yet to be
 integrated into the main tree). There is also support for the pseudo-protocol
 ANONYMOUS, which allows you to log in to a public IMAP server without having an
-account. To use ANONYMOUS, simply make your username blank or "anonymous".
+account. To use ANONYMOUS, simply make your username blank or ?anonymous?.
 
 SASL is a special super-authenticator, which selects among several protocols
 (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method
@@ -4638,7 +5009,7 @@ available on your host and the server. Using some of these methods (including
 DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and
 invisible to those teeming network snoops. It is the best option if you have
 it. To use it, you must have the Cyrus SASL library installed on your system
-and compile mutt with the --with-sasl flag.
+and compile Mutt with the --with-sasl flag.
 
 Mutt will try whichever methods are compiled in and available on the server, in
 the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
@@ -4655,37 +5026,41 @@ There are a few variables which control authentication:
 
   * $imap_authenticators - a colon-delimited list of IMAP authentication
     methods to try, in the order you wish to try them. If specified, this
-    overrides mutt's default (attempt everything, in the order listed above).
+    overrides Mutt's default (attempt everything, in the order listed above).
 
 5. SMTP Support
 
 Besides supporting traditional mail delivery through a sendmail-compatible
-program, mutt supports delivery through SMTP if it was configured and built
+program, Mutt supports delivery through SMTP if it was configured and built
 with --enable-smtp.
 
-If the configuration variable $smtp_url is set, mutt will contact the given
-SMTP server to deliver messages; if it is unset, mutt will use the program
+If the configuration variable $smtp_url is set, Mutt will contact the given
+SMTP server to deliver messages; if it is unset, Mutt will use the program
 specified by $sendmail.
 
-For details on the URL syntax, please see Section 1.2, ?URL syntax?.
+For details on the URL syntax, please see Section 1.2, ?URL Syntax?.
 
 The built-in SMTP support supports encryption (the smtps protocol using SSL or
 TLS) as well as SMTP authentication using SASL. The authentication mechanisms
 for SASL are specified in $smtp_authenticators defaulting to an empty list
-which makes mutt try all available methods from most-secure to least-secure.
+which makes Mutt try all available methods from most-secure to least-secure.
+
+6. Managing Multiple Accounts
 
-6. Managing multiple accounts
+Usage:
+
+account-hook pattern command
 
 If you happen to have accounts on multiple IMAP, POP and/or SMTP servers, you
 may find managing all the authentication settings inconvenient and error-prone.
 The account-hook command may help. This hook works like folder-hook but is
-invoked whenever you access a remote mailbox (including inside the folder
-browser), not just when you open the mailbox which includes (for example)
-polling for new mail, storing Fcc messages and saving messages to a folder. As
-a consequence, account-hook should only be used to set connection-related
-settings such as passwords or tunnel commands but not settings such as sender
-address or name (because in general it should be considered unpredictable which
-account-hook was last used).
+invoked whenever Mutt needs to access a remote mailbox (including inside the
+folder browser), not just when you open the mailbox. This includes (for
+example) polling for new mail, storing Fcc messages and saving messages to a
+folder. As a consequence, account-hook should only be used to set
+connection-related settings such as passwords or tunnel commands but not
+settings such as sender address or name (because in general it should be
+considered unpredictable which account-hook was last used).
 
 Some examples:
 
@@ -4694,16 +5069,38 @@ account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
 account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
 account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
 
-7. Local caching
+To manage multiple accounts with, for example, different values of $record or
+sender addresses, folder-hook has to be be used together with the mailboxes
+command.
+
+Example 6.2. Managing multiple accounts
+
+mailboxes imap://user@host1/INBOX
+folder-hook imap://user@host1/ 'set folder=imap://host1/ ; set record=+INBOX/Sent'
+
+mailboxes imap://user@host2/INBOX
+folder-hook imap://user@host2/ 'set folder=imap://host2/ ; set record=+INBOX/Sent'
+
+
+In example Example 6.2, ?Managing multiple accounts? the folders are defined
+using mailboxes so Mutt polls them for new mail. Each folder-hook triggers when
+one mailbox below each IMAP account is opened and sets $folder to the account's
+root folder. Next, it sets $record to the INBOX/Sent folder below the newly set
+$folder. Please notice that the value the ?+? mailbox shortcut refers to
+depends on the current value of $folder and therefore has to be set separatedly
+per account. Setting other values like $from or $signature is analogous to
+setting $record.
+
+7. Local Caching
 
 Mutt contains two types of local caching: (1) the so-called ?header caching?
 and (2) the so-called ?body caching? which are both described in this section.
 
 Header caching is optional as it depends on external libraries, body caching is
-always enabled if mutt is compiled with POP and/or IMAP support as these use it
+always enabled if Mutt is compiled with POP and/or IMAP support as these use it
 (body caching requires no external library).
 
-7.1. Header caching
+7.1. Header Caching
 
 Mutt provides optional support for caching message headers for the following
 types of folders: IMAP, POP, Maildir and MH. Header caching greatly improves
@@ -4721,35 +5118,22 @@ If set to point to a file, one database file for all folders will be used
 (which may result in lower performance), but one file per folder if it points
 to a directory.
 
-For the one-file-per-folder case, database files for remote folders will be
-named according to their URL while database files for local folders will be
-named by the MD5 checksums of their path. These database files may be safely
-removed if a system is short on space. You can compute the name of the header
-cache file for a particular local folder through a command like the following:
-
-$ printf '%s' '/path/to/folder' | md5sum
-
-The md5sum command may also be named md5, depending on your operating system.
-
-7.2. Body caching
+7.2. Body Caching
 
 Both cache methods can be combined using the same directory for storage (and
 for IMAP/POP even provide meaningful file names) which simplifies manual
 maintenance tasks.
 
-In addition to caching message headers only, mutt can also cache whole message
+In addition to caching message headers only, Mutt can also cache whole message
 bodies. This results in faster display of messages for POP and IMAP folders
 because messages usually have to be downloaded only once.
 
 For configuration, the variable $message_cachedir must point to a directory.
-There, mutt will create a hierarchy of subdirectories named like:
+There, Mutt will create a hierarchy of subdirectories named like:
 proto:user@hostname where proto is either ?pop? or ?imap.? Within there for
-each folder, mutt stores messages in single files (just like Maildir) so that
-with manual symlink creation these cache directories can be examined with mutt
-as read-only Maildir folders.
-
-All files can be removed as needed if the consumed disk space becomes an issue
-as mutt will silently fetch missing items again.
+each folder, Mutt stores messages in single files. All files can be removed as
+needed if the consumed disk space becomes an issue as Mutt will silently fetch
+missing items again.
 
 7.3. Maintenance
 
@@ -4758,15 +5142,15 @@ files so that files have to be removed in case they grow too big. It depends on
 the database library used for header caching whether disk space freed by
 removing messages is re-used.
 
-For body caches, mutt can keep the local cache in sync with the remote mailbox
+For body caches, Mutt can keep the local cache in sync with the remote mailbox
 if the $message_cache_clean variable is set. Cleaning means to remove messages
 from the cache which are no longer present in the mailbox which only happens
-when other mail clients or instances of mutt using a different body cache
+when other mail clients or instances of Mutt using a different body cache
 location delete messages (Mutt itself removes deleted messages from the cache
 when syncing a mailbox). As cleaning can take a noticeable amount of time, it
 should not be set in general but only occasionally.
 
-8. Exact address generation
+8. Exact Address Generation
 
 Mutt supports the ?Name ? address syntax for reading and writing
 messages, the older ?user@host (Name)? syntax is only supported when reading
@@ -4774,27 +5158,138 @@ messages. The --enable-exact-address switch can be given to configure to build
 it with write-support for the latter syntax. EXACT_ADDRESS in the output of
 mutt -v indicates whether it's supported.
 
-Chapter 7. Performance tuning
-
-Table of Contents
-
-1. Reading and writing mailboxes
-2. Reading messages from remote folders
-3. Searching and limiting
+9. Sending Anonymous Messages via Mixmaster
 
-1. Reading and writing mailboxes
-
-Mutt's performance when reading mailboxes can be improved in two ways:
+You may also have compiled Mutt to co-operate with Mixmaster, an anonymous
+remailer. Mixmaster permits you to send your messages anonymously using a chain
+of remailers. Mixmaster support in Mutt is for mixmaster version 2.04 (beta 45
+appears to be the latest) and 2.03. It does not support earlier versions or the
+later so-called version 3 betas, of which the latest appears to be called
+2.9b23.
 
- 1. For remote folders (IMAP and POP) as well as folders using one-file-per
-    message storage (Maildir and MH), mutt's performance can be greatly
-    improved using header caching. Using a single database per folder may
-    further increase performance.
+To use it, you'll have to obey certain restrictions. Most important, you cannot
+use the Cc and Bcc headers. To tell Mutt to use mixmaster, you have to select a
+remailer chain, using the mix function on the compose menu.
 
- 2. Mutt provides the $read_inc and $write_inc variables to specify at which
-    rate to update progress counters. If these values are too low, mutt may
-    spend more time on updating the progress counter than it spends on actually
-    reading/writing folders.
+The chain selection screen is divided into two parts. In the (larger) upper
+part, you get a list of remailers you may use. In the lower part, you see the
+currently selected chain of remailers.
+
+You can navigate in the chain using the  and 
+functions, which are by default bound to the left and right arrows and to the h
+and l keys (think vi keyboard bindings). To insert a remailer at the current
+chain position, use the  function. To append a remailer behind the
+current chain position, use  or . You can also delete
+entries from the chain, using the corresponding function. Finally, to abandon
+your changes, leave the menu, or  them pressing (by default) the Return
+key.
+
+Note that different remailers do have different capabilities, indicated in the
+%c entry of the remailer menu lines (see $mix_entry_format). Most important is
+the ?middleman? capability, indicated by a capital ?M?: This means that the
+remailer in question cannot be used as the final element of a chain, but will
+only forward messages to other mixmaster remailers. For details on the other
+capabilities, please have a look at the mixmaster documentation.
+
+Chapter 7. Security Considerations
+
+Table of Contents
+
+1. Passwords
+2. Temporary Files
+3. Information Leaks
+
+    3.1. Message-Id: headers
+    3.2. mailto:-style Links
+
+4. External Applications
+
+First of all, Mutt contains no security holes included by intention but may
+contain unknown security holes. As a consequence, please run Mutt only with as
+few permissions as possible. Especially, do not run Mutt as the super user.
+
+When configuring Mutt, there're some points to note about secure setups so
+please read this chapter carefully.
+
+1. Passwords
+
+Although Mutt can be told the various passwords for accounts, please never
+store passwords in configuration files. Besides the fact that the system's
+operator can always read them, you could forget to mask it out when reporting a
+bug or asking for help via a mailing list. Even worse, your mail including your
+password could be archived by internet search engines, mail-to-news gateways
+etc. It may already be too late before you notice your mistake.
+
+2. Temporary Files
+
+Mutt uses many temporary files for viewing messages, verifying digital
+signatures, etc. As long as being used, these files are visible by other users
+and maybe even readable in case of misconfiguration. Also, a different location
+for these files may be desired which can be changed via the $tmpdir variable.
+
+3. Information Leaks
+
+3.1. Message-Id: headers
+
+Message-Id: headers contain a local part that is to be created in a unique
+fashion. In order to do so, Mutt will ?leak? some information to the outside
+world when sending messages: the generation of this header includes a step
+counter which is increased (and rotated) with every message sent. In a longer
+running mutt session, others can make assumptions about your mailing habbits
+depending on the number of messages sent. If this is not desired, the header
+can be manually provided using $edit_headers (though not recommended).
+
+3.2. mailto:-style Links
+
+As Mutt be can be set up to be the mail client to handle mailto: style links in
+websites, there're security considerations, too. Arbitrary header fields can be
+embedded in these links which could override existing header fields or attach
+arbitrary files using the Attach: psuedoheader. This may be problematic if the
+$edit-headers variable is unset, i.e. the user doesn't want to see header
+fields while editing the message and doesn't pay enough attention to the
+compose menu's listing of attachments.
+
+For example, following a link like
+
+mailto:joe@host?Attach=~/.gnupg/secring.gpg
+
+will send out the user's private gnupg keyring to joe@host if the user doesn't
+follow the information on screen carefully enough.
+
+4. External Applications
+
+Mutt in many places has to rely on external applications or for convenience
+supports mechanisms involving external applications.
+
+One of these is the mailcap mechanism as defined by RfC1524. Details about a
+secure use of the mailcap mechanisms is given in Section 3.2, ?Secure Use of
+Mailcap?.
+
+Besides the mailcap mechanism, Mutt uses a number of other external utilities
+for operation, for example to provide crypto support, in backtick expansion in
+configuration files or format string filters. The same security considerations
+apply for these as for tools involved via mailcap.
+
+Chapter 8. Performance Tuning
+
+Table of Contents
+
+1. Reading and Writing Mailboxes
+2. Reading Messages from Remote Folders
+3. Searching and Limiting
+
+1. Reading and Writing Mailboxes
+
+Mutt's performance when reading mailboxes can be improved in two ways:
+
+ 1. For remote folders (IMAP and POP) as well as folders using one-file-per
+    message storage (Maildir and MH), Mutt's performance can be greatly
+    improved using header caching. using a single database per folder.
+
+ 2. Mutt provides the $read_inc and $write_inc variables to specify at which
+    rate to update progress counters. If these values are too low, Mutt may
+    spend more time on updating the progress counter than it spends on actually
+    reading/writing folders.
 
     For example, when opening a maildir folder with a few thousand messages,
     the default value for $read_inc may be too low. It can be tuned on on a
@@ -4814,20 +5309,20 @@ produce either too few or too much progress updates. Thus, Mutt allows to limit
 the number of progress updates per second it'll actually send to the terminal
 using the $time_inc variable.
 
-2. Reading messages from remote folders
+2. Reading Messages from Remote Folders
 
 Reading messages from remote folders such as IMAP an POP can be slow especially
-for large mailboxes since mutt only caches a very limited number of recently
+for large mailboxes since Mutt only caches a very limited number of recently
 viewed messages (usually 10) per session (so that it will be gone for the next
 session.)
 
 To improve performance and permanently cache whole messages, please refer to
-mutt's so-called body caching for details.
+Mutt's so-called body caching for details.
 
-3. Searching and limiting
+3. Searching and Limiting
 
 When searching mailboxes either via a search or a limit action, for some
-patterns mutt distinguishes between regular expression and string searches. For
+patterns Mutt distinguishes between regular expression and string searches. For
 regular expressions, patterns are prefixed with ??? and with ?=? for string
 searches.
 
@@ -4841,17 +5336,17 @@ author, it's much faster to search for the initial part of an e-mail address
 via =Luser@ instead of ?Luser@. This is especially true for searching message
 bodies since a larger amount of input has to be searched.
 
-Please note that string search is an exact case-sensitive search while a
-regular expression search with only lower-case letters performs a
-case-insensitive search.
+As for regular expressions, a lower case string search pattern makes Mutt
+perform a case-insensitive search except for IMAP (because for IMAP Mutt
+performs server-side searches which don't support case-insensivity).
 
-Chapter 8. Reference
+Chapter 9. Reference
 
 Table of Contents
 
-1. Command line options
+1. Command-Line Options
 2. Configuration Commands
-3. Configuration variables
+3. Configuration Variables
 
     3.1. abort_nosubject
     3.2. abort_unmodified
@@ -4869,18 +5364,18 @@ Table of Contents
     3.14. attach_sep
     3.15. attach_split
     3.16. attribution
-    3.17. autoedit
-    3.18. auto_tag
+    3.17. auto_tag
+    3.18. autoedit
     3.19. beep
     3.20. beep_new
     3.21. bounce
     3.22. bounce_delivered
     3.23. braille_friendly
-    3.24. check_mbox_size
+    3.24. certificate_file
     3.25. charset
-    3.26. check_new
-    3.27. collapse_unread
-    3.28. uncollapse_jump
+    3.26. check_mbox_size
+    3.27. check_new
+    3.28. collapse_unread
     3.29. compose_format
     3.30. config_charset
     3.31. confirmappend
@@ -4888,301 +5383,305 @@ Table of Contents
     3.33. connect_timeout
     3.34. content_type
     3.35. copy
-    3.36. crypt_use_gpgme
-    3.37. crypt_use_pka
-    3.38. crypt_autopgp
+    3.36. crypt_autoencrypt
+    3.37. crypt_autopgp
+    3.38. crypt_autosign
     3.39. crypt_autosmime
-    3.40. date_format
-    3.41. default_hook
-    3.42. delete
-    3.43. delete_untag
-    3.44. digest_collapse
-    3.45. display_filter
-    3.46. dotlock_program
-    3.47. dsn_notify
-    3.48. dsn_return
-    3.49. duplicate_threads
-    3.50. edit_headers
-    3.51. editor
-    3.52. encode_from
-    3.53. envelope_from_address
-    3.54. escape
-    3.55. fast_reply
-    3.56. fcc_attach
-    3.57. fcc_clear
-    3.58. folder
-    3.59. folder_format
-    3.60. followup_to
-    3.61. force_name
-    3.62. forward_decode
-    3.63. forward_edit
-    3.64. forward_format
-    3.65. forward_quote
-    3.66. from
-    3.67. gecos_mask
-    3.68. hdrs
-    3.69. header
-    3.70. help
-    3.71. hidden_host
-    3.72. hide_limited
-    3.73. hide_missing
-    3.74. hide_thread_subject
-    3.75. hide_top_limited
-    3.76. hide_top_missing
-    3.77. history
-    3.78. history_file
-    3.79. honor_followup_to
-    3.80. hostname
-    3.81. ignore_linear_white_space
-    3.82. ignore_list_reply_to
-    3.83. imap_authenticators
-    3.84. imap_check_subscribed
-    3.85. imap_delim_chars
-    3.86. imap_headers
-    3.87. imap_idle
-    3.88. imap_keepalive
-    3.89. imap_list_subscribed
-    3.90. imap_login
-    3.91. imap_pass
-    3.92. imap_passive
-    3.93. imap_peek
-    3.94. imap_pipeline_depth
-    3.95. imap_servernoise
-    3.96. imap_user
-    3.97. implicit_autoview
-    3.98. include
-    3.99. include_onlyfirst
-    3.100. indent_string
-    3.101. index_format
-    3.102. ispell
-    3.103. keep_flagged
-    3.104. locale
-    3.105. mail_check
-    3.106. mailcap_path
-    3.107. mailcap_sanitize
-    3.108. header_cache
-    3.109. maildir_header_cache_verify
-    3.110. header_cache_pagesize
-    3.111. header_cache_compress
-    3.112. maildir_trash
-    3.113. mark_old
-    3.114. markers
-    3.115. mask
-    3.116. mbox
-    3.117. mbox_type
-    3.118. metoo
-    3.119. menu_context
-    3.120. menu_move_off
-    3.121. menu_scroll
-    3.122. meta_key
-    3.123. mh_purge
-    3.124. mh_seq_flagged
-    3.125. mh_seq_replied
-    3.126. mh_seq_unseen
-    3.127. mime_forward
-    3.128. mime_forward_decode
-    3.129. mime_forward_rest
-    3.130. mix_entry_format
-    3.131. mixmaster
-    3.132. move
-    3.133. message_cachedir
-    3.134. message_cache_clean
-    3.135. message_format
-    3.136. narrow_tree
-    3.137. net_inc
-    3.138. pager
-    3.139. pager_context
-    3.140. pager_format
-    3.141. pager_index_lines
-    3.142. pager_stop
-    3.143. crypt_autosign
-    3.144. crypt_autoencrypt
-    3.145. pgp_ignore_subkeys
-    3.146. crypt_replyencrypt
-    3.147. crypt_replysign
-    3.148. crypt_replysignencrypted
-    3.149. crypt_timestamp
-    3.150. pgp_use_gpg_agent
-    3.151. crypt_verify_sig
-    3.152. smime_is_default
-    3.153. smime_ask_cert_label
-    3.154. smime_decrypt_use_default_key
-    3.155. pgp_entry_format
-    3.156. pgp_good_sign
-    3.157. pgp_check_exit
-    3.158. pgp_long_ids
-    3.159. pgp_retainable_sigs
-    3.160. pgp_autoinline
-    3.161. pgp_replyinline
-    3.162. pgp_show_unusable
-    3.163. pgp_sign_as
-    3.164. pgp_strict_enc
-    3.165. pgp_timeout
-    3.166. pgp_sort_keys
-    3.167. pgp_mime_auto
-    3.168. pgp_auto_decode
-    3.169. pgp_decode_command
-    3.170. pgp_getkeys_command
-    3.171. pgp_verify_command
-    3.172. pgp_decrypt_command
-    3.173. pgp_clearsign_command
-    3.174. pgp_sign_command
-    3.175. pgp_encrypt_sign_command
-    3.176. pgp_encrypt_only_command
-    3.177. pgp_import_command
-    3.178. pgp_export_command
-    3.179. pgp_verify_key_command
-    3.180. pgp_list_secring_command
-    3.181. pgp_list_pubring_command
-    3.182. forward_decrypt
-    3.183. smime_timeout
-    3.184. smime_encrypt_with
-    3.185. smime_keys
-    3.186. smime_ca_location
-    3.187. smime_certificates
-    3.188. smime_decrypt_command
-    3.189. smime_verify_command
-    3.190. smime_verify_opaque_command
-    3.191. smime_sign_command
-    3.192. smime_sign_opaque_command
-    3.193. smime_encrypt_command
-    3.194. smime_pk7out_command
-    3.195. smime_get_cert_command
-    3.196. smime_get_signer_cert_command
-    3.197. smime_import_cert_command
-    3.198. smime_get_cert_email_command
-    3.199. smime_default_key
-    3.200. ssl_client_cert
-    3.201. ssl_force_tls
-    3.202. ssl_starttls
-    3.203. certificate_file
-    3.204. ssl_usesystemcerts
-    3.205. entropy_file
-    3.206. ssl_use_sslv2
-    3.207. ssl_use_sslv3
-    3.208. ssl_use_tlsv1
-    3.209. ssl_min_dh_prime_bits
-    3.210. ssl_ca_certificates_file
-    3.211. pipe_split
-    3.212. pipe_decode
-    3.213. pipe_sep
-    3.214. pop_authenticators
-    3.215. pop_auth_try_all
-    3.216. pop_checkinterval
-    3.217. pop_delete
-    3.218. pop_host
-    3.219. pop_last
-    3.220. pop_reconnect
-    3.221. pop_user
-    3.222. pop_pass
-    3.223. post_indent_string
-    3.224. postpone
-    3.225. postponed
-    3.226. preconnect
-    3.227. print
-    3.228. print_command
-    3.229. print_decode
-    3.230. print_split
-    3.231. prompt_after
-    3.232. query_command
-    3.233. query_format
-    3.234. quit
-    3.235. quote_regexp
-    3.236. read_inc
-    3.237. read_only
-    3.238. realname
-    3.239. recall
-    3.240. record
-    3.241. reply_regexp
-    3.242. reply_self
-    3.243. reply_to
-    3.244. resolve
-    3.245. reverse_alias
-    3.246. reverse_name
-    3.247. reverse_realname
-    3.248. rfc2047_parameters
-    3.249. save_address
-    3.250. save_empty
-    3.251. save_history
-    3.252. save_name
-    3.253. score
-    3.254. score_threshold_delete
-    3.255. score_threshold_flag
-    3.256. score_threshold_read
-    3.257. send_charset
-    3.258. sendmail
-    3.259. sendmail_wait
-    3.260. shell
-    3.261. sig_dashes
-    3.262. sig_on_top
-    3.263. signature
-    3.264. simple_search
-    3.265. smart_wrap
-    3.266. smileys
-    3.267. sleep_time
-    3.268. smtp_authenticators
-    3.269. smtp_pass
-    3.270. smtp_url
-    3.271. sort
-    3.272. sort_alias
-    3.273. sort_aux
-    3.274. sort_browser
-    3.275. sort_re
-    3.276. spam_separator
-    3.277. spoolfile
-    3.278. status_chars
-    3.279. status_format
-    3.280. status_on_top
-    3.281. strict_threads
-    3.282. suspend
-    3.283. text_flowed
-    3.284. thread_received
-    3.285. thorough_search
-    3.286. tilde
-    3.287. time_inc
-    3.288. timeout
-    3.289. tmpdir
-    3.290. to_chars
-    3.291. tunnel
-    3.292. use_8bitmime
-    3.293. use_domain
-    3.294. use_envelope_from
-    3.295. use_from
-    3.296. use_idn
-    3.297. use_ipv6
-    3.298. user_agent
-    3.299. visual
-    3.300. wait_key
-    3.301. weed
-    3.302. wrap
-    3.303. wrap_search
-    3.304. wrapmargin
-    3.305. write_inc
-    3.306. write_bcc
+    3.40. crypt_replyencrypt
+    3.41. crypt_replysign
+    3.42. crypt_replysignencrypted
+    3.43. crypt_timestamp
+    3.44. crypt_use_gpgme
+    3.45. crypt_use_pka
+    3.46. crypt_verify_sig
+    3.47. date_format
+    3.48. default_hook
+    3.49. delete
+    3.50. delete_untag
+    3.51. digest_collapse
+    3.52. display_filter
+    3.53. dotlock_program
+    3.54. dsn_notify
+    3.55. dsn_return
+    3.56. duplicate_threads
+    3.57. edit_headers
+    3.58. editor
+    3.59. encode_from
+    3.60. entropy_file
+    3.61. envelope_from_address
+    3.62. escape
+    3.63. fast_reply
+    3.64. fcc_attach
+    3.65. fcc_clear
+    3.66. folder
+    3.67. folder_format
+    3.68. followup_to
+    3.69. force_name
+    3.70. forward_decode
+    3.71. forward_decrypt
+    3.72. forward_edit
+    3.73. forward_format
+    3.74. forward_quote
+    3.75. from
+    3.76. gecos_mask
+    3.77. hdrs
+    3.78. header
+    3.79. header_cache
+    3.80. header_cache_compress
+    3.81. header_cache_pagesize
+    3.82. help
+    3.83. hidden_host
+    3.84. hide_limited
+    3.85. hide_missing
+    3.86. hide_thread_subject
+    3.87. hide_top_limited
+    3.88. hide_top_missing
+    3.89. history
+    3.90. history_file
+    3.91. honor_disposition
+    3.92. honor_followup_to
+    3.93. hostname
+    3.94. ignore_linear_white_space
+    3.95. ignore_list_reply_to
+    3.96. imap_authenticators
+    3.97. imap_check_subscribed
+    3.98. imap_delim_chars
+    3.99. imap_headers
+    3.100. imap_idle
+    3.101. imap_keepalive
+    3.102. imap_list_subscribed
+    3.103. imap_login
+    3.104. imap_pass
+    3.105. imap_passive
+    3.106. imap_peek
+    3.107. imap_pipeline_depth
+    3.108. imap_servernoise
+    3.109. imap_user
+    3.110. implicit_autoview
+    3.111. include
+    3.112. include_onlyfirst
+    3.113. indent_string
+    3.114. index_format
+    3.115. ispell
+    3.116. keep_flagged
+    3.117. locale
+    3.118. mail_check
+    3.119. mailcap_path
+    3.120. mailcap_sanitize
+    3.121. maildir_header_cache_verify
+    3.122. maildir_trash
+    3.123. mark_old
+    3.124. markers
+    3.125. mask
+    3.126. mbox
+    3.127. mbox_type
+    3.128. menu_context
+    3.129. menu_move_off
+    3.130. menu_scroll
+    3.131. message_cache_clean
+    3.132. message_cachedir
+    3.133. message_format
+    3.134. meta_key
+    3.135. metoo
+    3.136. mh_purge
+    3.137. mh_seq_flagged
+    3.138. mh_seq_replied
+    3.139. mh_seq_unseen
+    3.140. mime_forward
+    3.141. mime_forward_decode
+    3.142. mime_forward_rest
+    3.143. mix_entry_format
+    3.144. mixmaster
+    3.145. move
+    3.146. narrow_tree
+    3.147. net_inc
+    3.148. pager
+    3.149. pager_context
+    3.150. pager_format
+    3.151. pager_index_lines
+    3.152. pager_stop
+    3.153. pgp_auto_decode
+    3.154. pgp_autoinline
+    3.155. pgp_check_exit
+    3.156. pgp_clearsign_command
+    3.157. pgp_decode_command
+    3.158. pgp_decrypt_command
+    3.159. pgp_encrypt_only_command
+    3.160. pgp_encrypt_sign_command
+    3.161. pgp_entry_format
+    3.162. pgp_export_command
+    3.163. pgp_getkeys_command
+    3.164. pgp_good_sign
+    3.165. pgp_ignore_subkeys
+    3.166. pgp_import_command
+    3.167. pgp_list_pubring_command
+    3.168. pgp_list_secring_command
+    3.169. pgp_long_ids
+    3.170. pgp_mime_auto
+    3.171. pgp_replyinline
+    3.172. pgp_retainable_sigs
+    3.173. pgp_show_unusable
+    3.174. pgp_sign_as
+    3.175. pgp_sign_command
+    3.176. pgp_sort_keys
+    3.177. pgp_strict_enc
+    3.178. pgp_timeout
+    3.179. pgp_use_gpg_agent
+    3.180. pgp_verify_command
+    3.181. pgp_verify_key_command
+    3.182. pipe_decode
+    3.183. pipe_sep
+    3.184. pipe_split
+    3.185. pop_auth_try_all
+    3.186. pop_authenticators
+    3.187. pop_checkinterval
+    3.188. pop_delete
+    3.189. pop_host
+    3.190. pop_last
+    3.191. pop_pass
+    3.192. pop_reconnect
+    3.193. pop_user
+    3.194. post_indent_string
+    3.195. postpone
+    3.196. postponed
+    3.197. preconnect
+    3.198. print
+    3.199. print_command
+    3.200. print_decode
+    3.201. print_split
+    3.202. prompt_after
+    3.203. query_command
+    3.204. query_format
+    3.205. quit
+    3.206. quote_regexp
+    3.207. read_inc
+    3.208. read_only
+    3.209. realname
+    3.210. recall
+    3.211. record
+    3.212. reply_regexp
+    3.213. reply_self
+    3.214. reply_to
+    3.215. resolve
+    3.216. reverse_alias
+    3.217. reverse_name
+    3.218. reverse_realname
+    3.219. rfc2047_parameters
+    3.220. save_address
+    3.221. save_empty
+    3.222. save_history
+    3.223. save_name
+    3.224. score
+    3.225. score_threshold_delete
+    3.226. score_threshold_flag
+    3.227. score_threshold_read
+    3.228. search_context
+    3.229. send_charset
+    3.230. sendmail
+    3.231. sendmail_wait
+    3.232. shell
+    3.233. sig_dashes
+    3.234. sig_on_top
+    3.235. signature
+    3.236. simple_search
+    3.237. sleep_time
+    3.238. smart_wrap
+    3.239. smileys
+    3.240. smime_ask_cert_label
+    3.241. smime_ca_location
+    3.242. smime_certificates
+    3.243. smime_decrypt_command
+    3.244. smime_decrypt_use_default_key
+    3.245. smime_default_key
+    3.246. smime_encrypt_command
+    3.247. smime_encrypt_with
+    3.248. smime_get_cert_command
+    3.249. smime_get_cert_email_command
+    3.250. smime_get_signer_cert_command
+    3.251. smime_import_cert_command
+    3.252. smime_is_default
+    3.253. smime_keys
+    3.254. smime_pk7out_command
+    3.255. smime_sign_command
+    3.256. smime_sign_opaque_command
+    3.257. smime_timeout
+    3.258. smime_verify_command
+    3.259. smime_verify_opaque_command
+    3.260. smtp_authenticators
+    3.261. smtp_pass
+    3.262. smtp_url
+    3.263. sort
+    3.264. sort_alias
+    3.265. sort_aux
+    3.266. sort_browser
+    3.267. sort_re
+    3.268. spam_separator
+    3.269. spoolfile
+    3.270. ssl_ca_certificates_file
+    3.271. ssl_client_cert
+    3.272. ssl_force_tls
+    3.273. ssl_min_dh_prime_bits
+    3.274. ssl_starttls
+    3.275. ssl_use_sslv2
+    3.276. ssl_use_sslv3
+    3.277. ssl_use_tlsv1
+    3.278. ssl_usesystemcerts
+    3.279. ssl_verify_dates
+    3.280. ssl_verify_host
+    3.281. status_chars
+    3.282. status_format
+    3.283. status_on_top
+    3.284. strict_threads
+    3.285. suspend
+    3.286. text_flowed
+    3.287. thorough_search
+    3.288. thread_received
+    3.289. tilde
+    3.290. time_inc
+    3.291. timeout
+    3.292. tmpdir
+    3.293. to_chars
+    3.294. tunnel
+    3.295. uncollapse_jump
+    3.296. use_8bitmime
+    3.297. use_domain
+    3.298. use_envelope_from
+    3.299. use_from
+    3.300. use_idn
+    3.301. use_ipv6
+    3.302. user_agent
+    3.303. visual
+    3.304. wait_key
+    3.305. weed
+    3.306. wrap
+    3.307. wrap_search
+    3.308. wrapmargin
+    3.309. write_bcc
+    3.310. write_inc
 
 4. Functions
 
-    4.1. generic menu
-    4.2. index menu
-    4.3. pager menu
-    4.4. alias menu
-    4.5. query menu
-    4.6. attach menu
-    4.7. compose menu
-    4.8. postpone menu
-    4.9. browser menu
-    4.10. pgp menu
-    4.11. smime menu
-    4.12. mix menu
-    4.13. editor menu
-
-1. Command line options
+    4.1. Generic Menu
+    4.2. Index Menu
+    4.3. Pager Menu
+    4.4. Alias Menu
+    4.5. Query Menu
+    4.6. Attach Menu
+    4.7. Compose Menu
+    4.8. Postpone Menu
+    4.9. Browser Menu
+    4.10. Pgp Menu
+    4.11. Smime Menu
+    4.12. Mix Menu
+    4.13. Editor Menu
+
+1. Command-Line Options
 
 Running mutt with no arguments will make Mutt attempt to read your spool
 mailbox. However, it is possible to read other mailboxes and to send messages
 from the command line as well.
 
-Table 8.1. Command line options
+Table 9.1. Command line options
 
 +-----------------------------------------------------------------------------+
 |Option|                             Description                              |
@@ -5195,7 +5694,7 @@ Table 8.1. Command line options
 |------+----------------------------------------------------------------------|
 |-c    |specify a carbon-copy (Cc) address                                    |
 |------+----------------------------------------------------------------------|
-|-D    |print the value of all mutt variables to stdout                       |
+|-D    |print the value of all Mutt variables to stdout                       |
 |------+----------------------------------------------------------------------|
 |-e    |specify a config command to be run after initialization files are read|
 |------+----------------------------------------------------------------------|
@@ -5229,7 +5728,7 @@ Table 8.1. Command line options
 |------+----------------------------------------------------------------------|
 |-z    |exit immediately if there are no messages in the mailbox              |
 |------+----------------------------------------------------------------------|
-|-Z    |open the first folder with new message,exit immediately if none       |
+|-Z    |open the first folder with new message, exit immediately if none      |
 +-----------------------------------------------------------------------------+
 
 
@@ -5239,43 +5738,52 @@ mutt [-nz] [-F muttrc ] [-m type ] [-f mailbox ]
 
 To compose a new message
 
-mutt [-n] [-F muttrc ] [-a file ] [-c address ] [-i filename ] [-s subject ] [
-[ file ...] -- ] address [ address ...]
+mutt [-n] [-F muttrc ] [-c address ] [-i filename ] [-s subject ] [ -a file
+[...] -- ] address ...
 
 Mutt also supports a ?batch? mode to send prepared messages. Simply redirect
 input from the file you wish to send. For example,
 
 mutt -s "data set for run #2" professor@bigschool.edu < ?/run2.dat
 
-This command will send a message to ?professor@bigschool.edu? with a subject of
-?data set for run #2?. In the body of the message will be the contents of the
-file ??/run2.dat?.
+will send a message to  with a subject of ?data set
+for run #2?. In the body of the message will be the contents of the file ??/
+run2.dat?.
 
 All files passed with -a file will be attached as a MIME part to the message.
-To attach several files, use ?--? to separate files and recipient addresses:
+To attach a single or several files, use ?--? to separate files and recipient
+addresses:
+
+mutt -a image.png -- some@one.org
+
+or
+
 mutt -a *.png -- some@one.org
 
+Note
+
+The -a option must be last in the option list.
+
 2. Configuration Commands
 
-The following are the commands understood by mutt.
+The following are the commands understood by Mutt:
 
   * account-hook pattern command
 
   * alias [ -group name ...] key address [ address ...]
-
-  * unalias [ -group name ...] { * | key ... }
+    unalias [ -group name ...] { * | key ... }
 
   * alternates [ -group name ...] regexp [ regexp ...]
-
-  * unalternates [ -group name ...] { * | regexp ... }
+    unalternates [ -group name ...] { * | regexp ... }
 
   * alternative-order mimetype [ mimetype ...]
+    unalternative-order { * | mimetype ... }
 
-  * unalternative-order { * | mimetype ... }
+  * attachments { + | - }disposition mime-type
+    unattachments { + | - }disposition mime-type
 
   * auto-view mimetype [ mimetype ...]
-
-  * unauto-view { * | mimetype ... }
+    unauto-view { * | mimetype ... }
 
   * bind map key function
 
@@ -5284,12 +5792,11 @@ The following are the commands understood by mutt.
   * iconv-hook charset local-charset
 
   * color object foreground background
-
     color { header | body } foreground background regexp
-
     color index foreground background pattern
+    uncolor { index | header | body } { * | pattern ... }
 
-  * uncolor index pattern ...
+  * crypt-hook pattern keyid
 
   * exec function [ function ...]
 
@@ -5300,58 +5807,43 @@ The following are the commands understood by mutt.
   * folder-hook [!]regexp command
 
   * group [ -group name ...] { -rx expr ... | -addr expr ... }
-
-  * ungroup [ -group name ...] { * | -rx expr ... | -addr expr ... }
+    ungroup [ -group name ...] { * | -rx expr ... | -addr expr ... }
 
   * hdr_order header [ header ...]
-
-  * unhdr_order { * | header ... }
+    unhdr_order { * | header ... }
 
   * ignore pattern [ pattern ...]
-
-  * unignore { * | pattern ... }
+    unignore { * | pattern ... }
 
   * lists [ -group name ] regexp [ regexp ...]
-
-  * unlists [ -group name ...] { * | regexp ... }
+    unlists [ -group name ...] { * | regexp ... }
 
   * macro menu key sequence [ description ]
 
   * mailboxes mailbox [ mailbox ...]
-
-  * unmailboxes { * | mailbox ... }
+    unmailboxes { * | mailbox ... }
 
   * mbox-hook [!]pattern mailbox
 
   * message-hook [!]pattern command
 
   * mime-lookup mimetype [ mimetype ...]
-
-  * unmime-lookup { * | mimetype ... }
+    unmime-lookup { * | mimetype ... }
 
   * mono object attribute
-
     mono { header | body } attribute regexp
-
     mono index attribute pattern
-
-  * unmono index { * | pattern ... }
+    unmono { index | header | body } { * | pattern ... }
 
   * my_hdr string
-
-  * unmy_hdr { * | field ... }
-
-  * crypt-hook pattern keyid
+    unmy_hdr { * | field ... }
 
   * push string
 
-  * reset variable [ variable ...]
-
   * save-hook [!]pattern mailbox
 
   * score pattern value
-
-  * unscore { * | pattern ... }
+    unscore { * | pattern ... }
 
   * reply-hook [!]pattern command
 
@@ -5360,24 +5852,21 @@ The following are the commands understood by mutt.
   * send2-hook [!]pattern command
 
   * set { [ no | inv ] variable | variable=value } [...]
-
-  * unset variable [ variable ...]
+    toggle variable [ variable ...]
+    unset variable [ variable ...]
+    reset variable [ variable ...]
 
   * source filename
 
   * spam pattern format
-
-  * nospam { * | pattern }
+    nospam { * | pattern }
 
   * subscribe [ -group name ...] regexp [ regexp ...]
-
-  * unsubscribe [ -group name ...] { * | regexp ... }
-
-  * toggle variable [ variable ...]
+    unsubscribe [ -group name ...] { * | regexp ... }
 
   * unhook { * | hook-type }
 
-3. Configuration variables
+3. Configuration Variables
 
 3.1. abort_nosubject
 
@@ -5421,25 +5910,17 @@ Default: ?%4n %2f %t %-10a   %r?
 Specifies the format of the data displayed for the ?alias? menu. The following
 printf(3)-style sequences are available:
 
-%a
-
-    alias name
-
-%f
-
-    flags - currently, a ?d? for an alias marked for deletion
-
-%n
-
-    index number
-
-%r
-
-    address which alias expands to
-
-%t
-
-    character which indicates if the alias is tagged for inclusion
++-----------------------------------------------------------------+
+|%a|alias name                                                    |
+|--+--------------------------------------------------------------|
+|%f|flags - currently, a ?d? for an alias marked for deletion     |
+|--+--------------------------------------------------------------|
+|%n|index number                                                  |
+|--+--------------------------------------------------------------|
+|%r|address which alias expands to                                |
+|--+--------------------------------------------------------------|
+|%t|character which indicates if the alias is tagged for inclusion|
++-----------------------------------------------------------------+
 
 3.5. allow_8bit
 
@@ -5462,7 +5943,6 @@ message could include a line like
 
 [-- PGP output follows ...
 
-
 and give it the same color as your attachment color (see also $crypt_timestamp
 ).
 
@@ -5515,7 +5995,6 @@ For example, Japanese users might prefer this:
 
 set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
 
-
 However, only the first content is valid for the message body.
 
 3.12. attach_charset
@@ -5524,11 +6003,14 @@ Type: string
 Default: (empty)
 
 This variable is a colon-separated list of character encoding schemes for text
-file attachments. If unset, the value of $charset will be used instead. For
-example, the following configuration would work for Japanese text handling:
+file attachments. Mutt uses this setting to guess which encoding files being
+attached are encoded in to convert them to a proper character set given in
+$send_charset.
 
-set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
+If unset, the value of $charset will be used instead. For example, the
+following configuration would work for Japanese text handling:
 
+set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
 
 Note: for Japanese users, ?iso-2022-*? must be put at the head of the value as
 shown above if included.
@@ -5541,82 +6023,46 @@ Default: ?%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] ?
 This variable describes the format of the ?attachment? menu. The following
 printf(3)-style sequences are understood:
 
-%C
-
-    charset
-
-%c
-
-    requires charset conversion (?n? or ?c?)
-
-%D
-
-    deleted flag
-
-%d
-
-    description
-
-%e
-
-    MIME content-transfer-encoding
-
-%f
-
-    filename
-
-%I
-
-    disposition (?I? for inline, ?A? for attachment)
-
-%m
-
-    major MIME type
-
-%M
-
-    MIME subtype
-
-%n
-
-    attachment number
-
-%Q
-
-    ?Q?, if MIME part qualifies for attachment counting
-
-%s
-
-    size
-
-%t
-
-    tagged flag
-
-%T
-
-    graphic tree characters
-
-%u
-
-    unlink (=to delete) flag
-
-%X
-
-    number of qualifying MIME parts in this part and its children (please see
-    the ?attachments? section for possible speed effects)
-
-%>X
-
-    right justify the rest of the string and pad with character ?X?
-
-%|X
-
-    pad to the end of the line with character ?X?
-
-%*X
-
-    soft-fill with character ?X? as pad
++-----------------------------------------------------------------------------+
+|%C |charset                                                                  |
+|---+-------------------------------------------------------------------------|
+|%c |requires charset conversion (?n? or ?c?)                                 |
+|---+-------------------------------------------------------------------------|
+|%D |deleted flag                                                             |
+|---+-------------------------------------------------------------------------|
+|%d |description                                                              |
+|---+-------------------------------------------------------------------------|
+|%e |MIME content-transfer-encoding                                           |
+|---+-------------------------------------------------------------------------|
+|%f |filename                                                                 |
+|---+-------------------------------------------------------------------------|
+|%I |disposition (?I? for inline, ?A? for attachment)                         |
+|---+-------------------------------------------------------------------------|
+|%m |major MIME type                                                          |
+|---+-------------------------------------------------------------------------|
+|%M |MIME subtype                                                             |
+|---+-------------------------------------------------------------------------|
+|%n |attachment number                                                        |
+|---+-------------------------------------------------------------------------|
+|%Q |?Q?, if MIME part qualifies for attachment counting                      |
+|---+-------------------------------------------------------------------------|
+|%s |size                                                                     |
+|---+-------------------------------------------------------------------------|
+|%t |tagged flag                                                              |
+|---+-------------------------------------------------------------------------|
+|%T |graphic tree characters                                                  |
+|---+-------------------------------------------------------------------------|
+|%u |unlink (=to delete) flag                                                 |
+|---+-------------------------------------------------------------------------|
+|%X |number of qualifying MIME parts in this part and its children (please see|
+|   |the ?attachments? section for possible speed effects)                    |
+|---+-------------------------------------------------------------------------|
+|%>X|right justify the rest of the string and pad with character ?X?          |
+|---+-------------------------------------------------------------------------|
+|%|X|pad to the end of the line with character ?X?                            |
+|---+-------------------------------------------------------------------------|
+|%*X|soft-fill with character ?X? as pad                                      |
++-----------------------------------------------------------------------------+
 
 For an explanation of ?soft-fill?, see the $index_format documentation.
 
@@ -5648,7 +6094,17 @@ This is the string that will precede a message which has been included in a
 reply. For a full listing of defined printf(3)-like sequences see the section
 on $index_format.
 
-3.17. autoedit
+3.17. auto_tag
+
+Type: boolean
+Default: no
+
+When set, functions in the index menu which affect a message will be applied to
+all tagged messages (if there are any). When unset, you must first use the
+ function (bound to ?;? by default) to make the next function apply
+to all tagged messages.
+
+3.18. autoedit
 
 Type: boolean
 Default: no
@@ -5658,17 +6114,11 @@ When set along with $edit_headers, Mutt will skip the initial send-menu
 editing the body of your message. The send-menu may still be accessed once you
 have finished editing the body of your message.
 
-Also see $fast_reply.
-
-3.18. auto_tag
-
-Type: boolean
-Default: no
+Note: when this option is set, you cannot use send-hooks that depend on the
+recipients when composing a new (non-reply) message, as the initial list of
+recipients is empty.
 
-When set, functions in the index menu which affect a message will be applied to
-all tagged messages (if there are any). When unset, you must first use the
- function (bound to ?;? by default) to make the next function apply
-to all tagged messages.
+Also see $fast_reply.
 
 3.19. beep
 
@@ -5715,22 +6165,23 @@ easier for blind persons using Braille displays to follow these menus. The
 option is unset by default because many visual terminals don't permit making
 the cursor invisible.
 
-3.24. check_mbox_size
+3.24. certificate_file
 
-Type: boolean
-Default: no
+Type: path
+Default: ??/.mutt_certificates?
 
-When this variable is set, mutt will use file size attribute instead of access
-time when checking for new mail in mbox and mmdf folders.
+This variable specifies the file where the certificates you trust are saved.
+When an unknown certificate is encountered, you are asked if you accept it or
+not. If you accept it, the certificate can also be saved in this file and
+further connections are automatically accepted.
 
-This variable is unset by default and should only be enabled when new mail
-detection for these folder types is unreliable or doesn't work.
+You can also manually add CA certificates in this file. Any server certificate
+that is signed with one of these CA certificates is also automatically
+accepted.
 
-Note that enabling this variable should happen before any ?mailboxes?
-directives occur in configuration files regarding mbox or mmdf folders because
-mutt needs to determine the initial new mail status of such a mailbox by
-performing a fast mailbox scan when it is defined. Afterwards the new mail
-status is tracked by file size changes.
+Example:
+
+set certificate_file=~/.mutt/certificates
 
 3.25. charset
 
@@ -5746,7 +6197,24 @@ $LC_CTYPE or $LANG.
 Note: It should only be set in case Mutt isn't abled to determine the character
 set used correctly.
 
-3.26. check_new
+3.26. check_mbox_size
+
+Type: boolean
+Default: no
+
+When this variable is set, mutt will use file size attribute instead of access
+time when checking for new mail in mbox and mmdf folders.
+
+This variable is unset by default and should only be enabled when new mail
+detection for these folder types is unreliable or doesn't work.
+
+Note that enabling this variable should happen before any ?mailboxes?
+directives occur in configuration files regarding mbox or mmdf folders because
+mutt needs to determine the initial new mail status of such a mailbox by
+performing a fast mailbox scan when it is defined. Afterwards the new mail
+status is tracked by file size changes.
+
+3.27. check_new
 
 Type: boolean
 Default: yes
@@ -5759,21 +6227,13 @@ involves scanning the directory and checking each file to see if it has already
 been looked at. If this variable is unset, no check for new mail is performed
 while the mailbox is open.
 
-3.27. collapse_unread
+3.28. collapse_unread
 
 Type: boolean
 Default: yes
 
 When unset, Mutt will not collapse a thread if it contains any unread messages.
 
-3.28. uncollapse_jump
-
-Type: boolean
-Default: no
-
-When set, Mutt will jump to the next unread message, if any, when the current
-thread is uncollapsed.
-
 3.29. compose_format
 
 Type: string
@@ -5783,21 +6243,15 @@ Controls the format of the status line displayed in the ?compose? menu. This
 string is similar to $status_format, but has its own set of printf(3)-like
 sequences:
 
-%a
-
-    total number of attachments
-
-%h
-
-    local hostname
-
-%l
-
-    approximate size (in bytes) of the current message
-
-%v
-
-    Mutt version string
++-----------------------------------------------------+
+|%a|total number of attachments                       |
+|--+--------------------------------------------------|
+|%h|local hostname                                    |
+|--+--------------------------------------------------|
+|%l|approximate size (in bytes) of the current message|
+|--+--------------------------------------------------|
+|%v|Mutt version string                               |
++-----------------------------------------------------+
 
 See the text describing the $status_format option for more information on how
 to set $compose_format.
@@ -5859,26 +6313,19 @@ This variable controls whether or not copies of your outgoing messages will be
 saved for later references. Also see $record, $save_name, $force_name and ?
 fcc-hook?.
 
-3.36. crypt_use_gpgme
-
-Type: boolean
-Default: no
-
-This variable controls the use of the GPGME-enabled crypto backends. If it is
-set and Mutt was built with gpgme support, the gpgme code for S/MIME and PGP
-will be used instead of the classic code. Note that you need to set this option
-in .muttrc; it won't have any effect when used interactively.
-
-3.37. crypt_use_pka
+3.36. crypt_autoencrypt
 
 Type: boolean
 Default: no
 
-Controls whether mutt uses PKA (see http://www.g10code.de/docs/
-pka-intro.de.pdf) during signature verification (only supported by the GPGME
-backend).
+Setting this variable will cause Mutt to always attempt to PGP encrypt outgoing
+messages. This is probably only useful in connection to the ?send-hook?
+command. It can be overridden by use of the pgp menu, when encryption is not
+required or signing is requested as well. If $smime_is_default is set, then
+OpenSSL is used instead to create S/MIME messages and settings can be
+overridden by use of the smime menu instead. (Crypto only)
 
-3.38. crypt_autopgp
+3.37. crypt_autopgp
 
 Type: boolean
 Default: yes
@@ -5887,6 +6334,18 @@ This variable controls whether or not mutt may automatically enable PGP
 encryption/signing for messages. See also $crypt_autoencrypt,
 $crypt_replyencrypt, $crypt_autosign, $crypt_replysign and $smime_is_default.
 
+3.38. crypt_autosign
+
+Type: boolean
+Default: no
+
+Setting this variable will cause Mutt to always attempt to cryptographically
+sign outgoing messages. This can be overridden by use of the pgp menu, when
+signing is not required or encryption is requested as well. If
+$smime_is_default is set, then OpenSSL is used instead to create S/MIME
+messages and settings can be overridden by use of the smime menu instead of the
+pgp menu. (Crypto only)
+
 3.39. crypt_autosmime
 
 Type: boolean
@@ -5896,22 +6355,88 @@ This variable controls whether or not mutt may automatically enable S/MIME
 encryption/signing for messages. See also $crypt_autoencrypt,
 $crypt_replyencrypt, $crypt_autosign, $crypt_replysign and $smime_is_default.
 
-3.40. date_format
+3.40. crypt_replyencrypt
 
-Type: string
-Default: ?!%a, %b %d, %Y at %I:%M:%S%p %Z?
+Type: boolean
+Default: yes
 
-This variable controls the format of the date printed by the ?%d? sequence in
-$index_format. This is passed to the strftime(3) function to process the date,
-see the man page for the proper syntax.
+If set, automatically PGP or OpenSSL encrypt replies to messages which are
+encrypted. (Crypto only)
 
-Unless the first character in the string is a bang (?!?), the month and week
-day names are expanded according to the locale specified in the variable
-$locale. If the first character in the string is a bang, the bang is discarded,
+3.41. crypt_replysign
+
+Type: boolean
+Default: no
+
+If set, automatically PGP or OpenSSL sign replies to messages which are signed.
+
+Note: this does not work on messages that are encrypted and signed! (Crypto
+only)
+
+3.42. crypt_replysignencrypted
+
+Type: boolean
+Default: no
+
+If set, automatically PGP or OpenSSL sign replies to messages which are
+encrypted. This makes sense in combination with $crypt_replyencrypt, because it
+allows you to sign all messages which are automatically encrypted. This works
+around the problem noted in $crypt_replysign, that mutt is not able to find out
+whether an encrypted message is also signed. (Crypto only)
+
+3.43. crypt_timestamp
+
+Type: boolean
+Default: yes
+
+If set, mutt will include a time stamp in the lines surrounding PGP or S/MIME
+output, so spoofing such lines is more difficult. If you are using colors to
+mark these lines, and rely on these, you may unset this setting. (Crypto only)
+
+3.44. crypt_use_gpgme
+
+Type: boolean
+Default: no
+
+This variable controls the use of the GPGME-enabled crypto backends. If it is
+set and Mutt was built with gpgme support, the gpgme code for S/MIME and PGP
+will be used instead of the classic code. Note that you need to set this option
+in .muttrc; it won't have any effect when used interactively.
+
+3.45. crypt_use_pka
+
+Type: boolean
+Default: no
+
+Controls whether mutt uses PKA (see http://www.g10code.de/docs/
+pka-intro.de.pdf) during signature verification (only supported by the GPGME
+backend).
+
+3.46. crypt_verify_sig
+
+Type: quadoption
+Default: yes
+
+If ?yes?, always attempt to verify PGP or S/MIME signatures. If ?ask-*?, ask
+whether or not to verify the signature. If \Fi?no?, never attempt to verify
+cryptographic signatures. (Crypto only)
+
+3.47. date_format
+
+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
+$index_format. This is passed to the strftime(3) function to process the date,
+see the man page for the proper syntax.
+
+Unless the first character in the string is a bang (?!?), the month and week
+day names are expanded according to the locale specified in the variable
+$locale. If the first character in the string is a bang, the bang is discarded,
 and the month and week day names in the rest of the string are expanded in the
 C locale (that is in US English).
 
-3.41. default_hook
+3.48. default_hook
 
 Type: string
 Default: ??f %s !?P | (?P ?C %s)?
@@ -5927,7 +6452,7 @@ regular expression given, or if it is from you (if the from address matches ?
 alternates?) and is to or cc'ed to a user matching the given regular
 expression.
 
-3.42. delete
+3.49. delete
 
 Type: quadoption
 Default: ask-yes
@@ -5937,7 +6462,7 @@ synchronizing a mailbox. If set to yes, messages marked for deleting will
 automatically be purged without prompting. If set to no, messages marked for
 deletion will be kept in the mailbox.
 
-3.43. delete_untag
+3.50. delete_untag
 
 Type: boolean
 Default: yes
@@ -5946,7 +6471,7 @@ If this option is set, mutt will untag messages when marking them for deletion.
 This applies when you either explicitly delete a message, or when you save it
 to another folder.
 
-3.44. digest_collapse
+3.51. digest_collapse
 
 Type: boolean
 Default: yes
@@ -5955,7 +6480,7 @@ If this option is set, mutt's received-attachments menu will not show the
 subparts of individual messages in a multipart/digest. To see these subparts,
 press ?v? on that menu.
 
-3.45. display_filter
+3.52. display_filter
 
 Type: path
 Default: (empty)
@@ -5964,14 +6489,14 @@ When set, specifies a command used to filter messages. When a message is viewed
 it is passed as standard input to $display_filter, and the filtered message is
 read from the standard output.
 
-3.46. dotlock_program
+3.53. dotlock_program
 
 Type: path
 Default: ?/usr/local/bin/mutt_dotlock?
 
 Contains the path of the mutt_dotlock(8) binary to be used by mutt.
 
-3.47. dsn_notify
+3.54. dsn_notify
 
 Type: string
 Default: (empty)
@@ -5986,14 +6511,13 @@ Example:
 
 set dsn_notify="failure,delay"
 
-
 Note: when using $sendmail for delivery, you should not enable this unless you
 are either using Sendmail 8.8.x or greater or a MTA providing a sendmail(1)
 -compatible interface supporting the -N option for DSN. For SMTP delivery, DSN
 support is autodetected so that it depends on the server whether DSN will be
 used or not.
 
-3.48. dsn_return
+3.55. dsn_return
 
 Type: string
 Default: (empty)
@@ -6006,14 +6530,13 @@ Example:
 
 set dsn_return=hdrs
 
-
 Note: when using $sendmail for delivery, you should not enable this unless you
 are either using Sendmail 8.8.x or greater or a MTA providing a sendmail(1)
 -compatible interface supporting the -R option for DSN. For SMTP delivery, DSN
 support is autodetected so that it depends on the server whether DSN will be
 used or not.
 
-3.49. duplicate_threads
+3.56. duplicate_threads
 
 Type: boolean
 Default: yes
@@ -6023,7 +6546,7 @@ messages with the same Message-Id together. If it is set, it will indicate that
 it thinks they are duplicates of each other with an equals sign in the thread
 tree.
 
-3.50. edit_headers
+3.57. edit_headers
 
 Type: boolean
 Default: no
@@ -6034,7 +6557,7 @@ the body of your message.
 Note that changes made to the References: and Date: headers are ignored for
 interoperability reasons.
 
-3.51. editor
+3.58. editor
 
 Type: path
 Default: (empty)
@@ -6043,7 +6566,7 @@ This variable specifies which editor is used by mutt. It defaults to the value
 of the $VISUAL, or $EDITOR, environment variable, or to the string ?vi? if
 neither of those are set.
 
-3.52. encode_from
+3.59. encode_from
 
 Type: boolean
 Default: no
@@ -6054,7 +6577,15 @@ useful to avoid the tampering certain mail delivery and transport agents tend
 to do with messages (in order to prevent tools from misinterpreting the line as
 a mbox message separator).
 
-3.53. envelope_from_address
+3.60. entropy_file
+
+Type: path
+Default: (empty)
+
+The file which includes random data that is used to initialize SSL library
+functions.
+
+3.61. envelope_from_address
 
 Type: e-mail address
 Default: (empty)
@@ -6062,14 +6593,14 @@ Default: (empty)
 Manually sets the envelope sender for outgoing messages. This value is ignored
 if $use_envelope_from is unset.
 
-3.54. escape
+3.62. escape
 
 Type: string
 Default: ???
 
 Escape character to use for functions in the builtin editor.
 
-3.55. fast_reply
+3.63. fast_reply
 
 Type: boolean
 Default: no
@@ -6080,15 +6611,15 @@ forwarding messages.
 
 Note: this variable has no effect when the $autoedit variable is set.
 
-3.56. fcc_attach
+3.64. fcc_attach
 
-Type: boolean
+Type: quadoption
 Default: yes
 
 This variable controls whether or not attachments on outgoing messages are
 saved along with the main body of your message.
 
-3.57. fcc_clear
+3.65. fcc_clear
 
 Type: boolean
 Default: no
@@ -6096,7 +6627,7 @@ Default: no
 When this variable is set, FCCs will be stored unencrypted and unsigned, even
 when the actual message is encrypted and/or signed. (PGP only)
 
-3.58. folder
+3.66. folder
 
 Type: path
 Default: ??/Mail?
@@ -6107,7 +6638,7 @@ change this variable (from the default) value you need to make sure that the
 assignment occurs before you use ?+? or ?=? for any other variables since
 expansion takes place when handling the ?mailboxes? command.
 
-3.59. folder_format
+3.67. folder_format
 
 Type: string
 Default: ?%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f?
@@ -6116,61 +6647,38 @@ This variable allows you to customize the file browser display to your personal
 taste. This string is similar to $index_format, but has its own set of printf
 (3)-like sequences:
 
-%C
-
-    current file number
-
-%d
-
-    date/time folder was last modified
-
-%f
-
-    filename
-
-%F
-
-    file permissions
-
-%g
-
-    group name (or numeric gid, if missing)
-
-%l
-
-    number of hard links
-
-%N
-
-    N if folder has new mail, blank otherwise
-
-%s
-
-    size in bytes
-
-%t
-
-    ?*? if the file is tagged, blank otherwise
-
-%u
-
-    owner name (or numeric uid, if missing)
-
-%>X
-
-    right justify the rest of the string and pad with character ?X?
-
-%|X
-
-    pad to the end of the line with character ?X?
-
-%*X
-
-    soft-fill with character ?X? as pad
++-----------------------------------------------------------------------------+
+|%C |current file number                                                      |
+|---+-------------------------------------------------------------------------|
+|%d |date/time folder was last modified                                       |
+|---+-------------------------------------------------------------------------|
+|%f |filename (?/? is appended to directory names, ?@? to symbolic links and  |
+|   |?*? to executable files)                                                 |
+|---+-------------------------------------------------------------------------|
+|%F |file permissions                                                         |
+|---+-------------------------------------------------------------------------|
+|%g |group name (or numeric gid, if missing)                                  |
+|---+-------------------------------------------------------------------------|
+|%l |number of hard links                                                     |
+|---+-------------------------------------------------------------------------|
+|%N |N if folder has new mail, blank otherwise                                |
+|---+-------------------------------------------------------------------------|
+|%s |size in bytes                                                            |
+|---+-------------------------------------------------------------------------|
+|%t |?*? if the file is tagged, blank otherwise                               |
+|---+-------------------------------------------------------------------------|
+|%u |owner name (or numeric uid, if missing)                                  |
+|---+-------------------------------------------------------------------------|
+|%>X|right justify the rest of the string and pad with character ?X?          |
+|---+-------------------------------------------------------------------------|
+|%|X|pad to the end of the line with character ?X?                            |
+|---+-------------------------------------------------------------------------|
+|%*X|soft-fill with character ?X? as pad                                      |
++-----------------------------------------------------------------------------+
 
 For an explanation of ?soft-fill?, see the $index_format documentation.
 
-3.60. followup_to
+3.68. followup_to
 
 Type: boolean
 Default: yes
@@ -6190,7 +6698,7 @@ this header, a group reply to your message sent to a subscribed list will be
 sent to both the list and your address, resulting in two copies of the same
 email for you.
 
-3.61. force_name
+3.69. force_name
 
 Type: boolean
 Default: no
@@ -6201,7 +6709,7 @@ that mailbox does not exist.
 
 Also see the $record variable.
 
-3.62. forward_decode
+3.70. forward_decode
 
 Type: boolean
 Default: yes
@@ -6211,7 +6719,16 @@ a message. The message header is also RFC2047 decoded. This variable is only
 used, if $mime_forward is unset, otherwise $mime_forward_decode is used
 instead.
 
-3.63. forward_edit
+3.71. forward_decrypt
+
+Type: boolean
+Default: yes
+
+Controls the handling of encrypted messages when forwarding a message. When set
+, the outer layer of encryption is stripped off. This variable is only used if
+$mime_forward is set and $mime_forward_decode is unset. (PGP only)
+
+3.72. forward_edit
 
 Type: quadoption
 Default: yes
@@ -6220,7 +6737,7 @@ This quadoption controls whether or not the user is automatically placed in the
 editor when forwarding messages. For those who always want to forward with no
 modification, use a setting of ?no?.
 
-3.64. forward_format
+3.73. forward_format
 
 Type: string
 Default: ?[%a: %s]?
@@ -6228,7 +6745,7 @@ Default: ?[%a: %s]?
 This variable controls the default subject when forwarding a message. It uses
 the same format sequences as the $index_format variable.
 
-3.65. forward_quote
+3.74. forward_quote
 
 Type: boolean
 Default: no
@@ -6236,7 +6753,7 @@ Default: no
 When set, forwarded messages included in the main body of the message (when
 $mime_forward is unset) will be quoted using $indent_string.
 
-3.66. from
+3.75. from
 
 Type: e-mail address
 Default: (empty)
@@ -6247,7 +6764,7 @@ is ignored if $use_from is unset.
 
 This setting defaults to the contents of the environment variable $EMAIL.
 
-3.67. gecos_mask
+3.76. gecos_mask
 
 Type: regular expression
 Default: ?^[^,]*?
@@ -6257,13 +6774,13 @@ when expanding the alias. The default value will return the string up to the
 first ?,? encountered. If the GECOS field contains a string like ?lastname,
 firstname? then you should set it to ?.*?.
 
-This can be useful if you see the following behavior: you address a e-mail to
+This can be useful if you see the following behavior: you address an e-mail to
 user ID ?stevef? whose full name is ?Steve Franklin?. If mutt expands ?stevef?
 to ?"Franklin" stevef@foo.bar? then you should set the $gecos_mask to a regular
 expression that will match the whole name so mutt will expand ?Franklin? to
 ?Franklin, Steve?.
 
-3.68. hdrs
+3.77. hdrs
 
 Type: boolean
 Default: yes
@@ -6273,7 +6790,7 @@ created. This variable must 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.
 
-3.69. header
+3.78. header
 
 Type: boolean
 Default: no
@@ -6281,7 +6798,41 @@ Default: no
 When set, this variable causes Mutt to include the header of the message you
 are replying to into the edit buffer. The $weed setting applies.
 
-3.70. help
+3.79. header_cache
+
+Type: path
+Default: (empty)
+
+This variable points to the header cache database. If pointing to a directory
+Mutt will contain a header cache database file per folder, if pointing to a
+file that file will be a single global header cache. By default it is unset so
+no header caching will be used.
+
+Header caching can greatly improve speed when opening POP, IMAP MH or Maildir
+folders, see ?caching? for details.
+
+3.80. header_cache_compress
+
+Type: boolean
+Default: yes
+
+When mutt is compiled with qdbm or tokyocabinet as header cache backend, this
+option determines whether the database will be compressed. Compression results
+in database files roughly being one fifth of the usual diskspace, but the
+uncompression can result in a slower opening of cached folder(s) which in
+general is still much faster than opening non header cached folders.
+
+3.81. header_cache_pagesize
+
+Type: string
+Default: ?16384?
+
+When mutt is compiled with either gdbm or bdb4 as the header cache backend,
+this option changes the database page size. Too large or too small values can
+waste space, memory, or CPU time. The default should be more or less optimal
+for most use cases.
+
+3.82. help
 
 Type: boolean
 Default: yes
@@ -6294,7 +6845,7 @@ sequence rather than a single keystroke. Also, the help line may not be updated
 if a binding is changed while Mutt is running. Since this variable is primarily
 aimed at new users, neither of these should present a major problem.
 
-3.71. hidden_host
+3.83. hidden_host
 
 Type: boolean
 Default: no
@@ -6303,7 +6854,7 @@ When set, mutt will skip the host name part of $hostname variable when adding
 the domain part to addresses. This variable does not affect the generation of
 Message-IDs, and it will not lead to the cut-off of first-level domains.
 
-3.72. hide_limited
+3.84. hide_limited
 
 Type: boolean
 Default: no
@@ -6311,7 +6862,7 @@ Default: no
 When set, mutt will not show the presence of messages that are hidden by
 limiting, in the thread tree.
 
-3.73. hide_missing
+3.85. hide_missing
 
 Type: boolean
 Default: yes
@@ -6319,7 +6870,7 @@ Default: yes
 When set, mutt will not show the presence of missing messages in the thread
 tree.
 
-3.74. hide_thread_subject
+3.86. hide_thread_subject
 
 Type: boolean
 Default: yes
@@ -6327,7 +6878,7 @@ Default: yes
 When set, mutt will not show the subject of messages in the thread tree that
 have the same subject as their parent or closest previously displayed sibling.
 
-3.75. hide_top_limited
+3.87. hide_top_limited
 
 Type: boolean
 Default: no
@@ -6336,7 +6887,7 @@ When set, mutt will not show the presence of messages that are hidden by
 limiting, at the top of threads in the thread tree. Note that when
 $hide_limited is set, this option will have no effect.
 
-3.76. hide_top_missing
+3.88. hide_top_missing
 
 Type: boolean
 Default: yes
@@ -6345,7 +6896,7 @@ When set, mutt will not show the presence of missing messages at the top of
 threads in the thread tree. Note that when $hide_missing is set, this option
 will have no effect.
 
-3.77. history
+3.89. history
 
 Type: number
 Default: 10
@@ -6354,14 +6905,26 @@ This variable controls the size (in number of strings remembered) of the string
 history buffer per category. The buffer is cleared each time the variable is
 set.
 
-3.78. history_file
+3.90. history_file
 
 Type: path
 Default: ??/.mutthistory?
 
 The file in which Mutt will save its history.
 
-3.79. honor_followup_to
+3.91. honor_disposition
+
+Type: boolean
+Default: no
+
+When set, Mutt will not display attachments with a disposition of ?attachment?
+inline even if it could render the part to plain text. These MIME parts can
+only be viewed from the attachment menu.
+
+If unset, Mutt will render all MIME parts it can properly transform to plain
+text.
+
+3.92. honor_followup_to
 
 Type: quadoption
 Default: yes
@@ -6369,7 +6932,7 @@ Default: yes
 This variable controls whether or not a Mail-Followup-To header is honored when
 group-replying to a message.
 
-3.80. hostname
+3.93. hostname
 
 Type: string
 Default: (empty)
@@ -6388,7 +6951,7 @@ detected one is not used.
 
 Also see $use_domain and $hidden_host.
 
-3.81. ignore_linear_white_space
+3.94. ignore_linear_white_space
 
 Type: boolean
 Default: no
@@ -6397,7 +6960,7 @@ This option replaces linear-white-space between encoded-word and text to a
 single space to prevent the display of MIME-encoded ?Subject:? field from being
 divided into multiple lines.
 
-3.82. ignore_list_reply_to
+3.95. ignore_list_reply_to
 
 Type: boolean
 Default: no
@@ -6410,7 +6973,7 @@ the list, and will ignore this field. To direct a response to the mailing list
 when this option is set, use the  function;  will
 reply to both the sender and the list.
 
-3.83. imap_authenticators
+3.96. imap_authenticators
 
 Type: string
 Default: (empty)
@@ -6426,12 +6989,11 @@ Example:
 
 set imap_authenticators="gssapi:cram-md5:login"
 
-
 Note: Mutt will only fall back to other authentication methods if the previous
 methods are unavailable. If a method is available but authentication fails,
 mutt will not connect to the IMAP server.
 
-3.84. imap_check_subscribed
+3.97. imap_check_subscribed
 
 Type: boolean
 Default: no
@@ -6440,7 +7002,7 @@ When set, mutt will fetch the set of subscribed folders from your server on
 connection, and add them to the set of mailboxes it polls for new mail just as
 if you had issued individual ?mailboxes? commands.
 
-3.85. imap_delim_chars
+3.98. imap_delim_chars
 
 Type: string
 Default: ?/.?
@@ -6449,7 +7011,7 @@ This contains the list of characters which you would like to treat as folder
 separators for displaying IMAP paths. In particular it helps in using the ?=?
 shortcut for your folder variable.
 
-3.86. imap_headers
+3.99. imap_headers
 
 Type: string
 Default: (empty)
@@ -6464,7 +7026,7 @@ Note: This is a space separated list, items should be uppercase and not contain
 the colon, e.g. ?X-BOGOSITY X-SPAM-STATUS? for the ?X-Bogosity:? and
 ?X-Spam-Status:? header fields.
 
-3.87. imap_idle
+3.100. imap_idle
 
 Type: boolean
 Default: no
@@ -6474,7 +7036,7 @@ mail in the current mailbox. Some servers (dovecot was the inspiration for this
 option) react badly to mutt's implementation. If your connection seems to
 freeze up periodically, try unsetting this.
 
-3.88. imap_keepalive
+3.101. imap_keepalive
 
 Type: number
 Default: 900
@@ -6487,7 +7049,7 @@ do this, but in practice the RFC does get violated every now and then. Reduce
 this number if you find yourself getting disconnected from your IMAP server due
 to inactivity.
 
-3.89. imap_list_subscribed
+3.102. imap_list_subscribed
 
 Type: boolean
 Default: no
@@ -6496,7 +7058,7 @@ This variable configures whether IMAP folder browsing will look for only
 subscribed folders or all folders. This can be toggled in the IMAP browser with
 the  function.
 
-3.90. imap_login
+3.103. imap_login
 
 Type: string
 Default: (empty)
@@ -6505,20 +7067,20 @@ Your login name on the IMAP server.
 
 This variable defaults to the value of $imap_user.
 
-3.91. imap_pass
+3.104. imap_pass
 
 Type: string
 Default: (empty)
 
 Specifies the password for your IMAP account. If unset, Mutt will prompt you
-for your password when you invoke the  function or try to open an
-IMAP folder.
+for your password when you invoke the  function or try to open
+an IMAP folder.
 
 Warning: you should only use this option when you are on a fairly secure
 machine, because the superuser can read your muttrc even if you are the only
 one who can read the file.
 
-3.92. imap_passive
+3.105. imap_passive
 
 Type: boolean
 Default: yes
@@ -6528,7 +7090,7 @@ will only check for new mail over existing IMAP connections. This is useful if
 you don't want to be prompted to user/password pairs on mutt invocation, or if
 opening the connection is slow.
 
-3.93. imap_peek
+3.106. imap_peek
 
 Type: boolean
 Default: yes
@@ -6538,7 +7100,7 @@ fetch a message from the server. This is generally a good thing, but can make
 closing an IMAP folder somewhat slower. This option exists to appease speed
 freaks.
 
-3.94. imap_pipeline_depth
+3.107. imap_pipeline_depth
 
 Type: number
 Default: 15
@@ -6551,7 +7113,7 @@ want to try setting this variable to 0.
 
 Note: Changes to this variable have no effect on open connections.
 
-3.95. imap_servernoise
+3.108. imap_servernoise
 
 Type: boolean
 Default: yes
@@ -6561,7 +7123,7 @@ messages. Since these messages are often harmless, or generated due to
 configuration problems on the server which are out of the users' hands, you may
 wish to suppress them at some point.
 
-3.96. imap_user
+3.109. imap_user
 
 Type: string
 Default: (empty)
@@ -6570,7 +7132,7 @@ The name of the user whose mail you intend to access on the IMAP server.
 
 This variable defaults to your user name on the local machine.
 
-3.97. implicit_autoview
+3.110. implicit_autoview
 
 Type: boolean
 Default: no
@@ -6580,7 +7142,7 @@ flag set for every MIME attachment it doesn't have an internal viewer defined
 for. If such an entry is found, mutt will use the viewer defined in that entry
 to convert the body part to text form.
 
-3.98. include
+3.111. include
 
 Type: quadoption
 Default: ask-yes
@@ -6588,7 +7150,7 @@ Default: ask-yes
 Controls whether or not a copy of the message(s) you are replying to is
 included in your reply.
 
-3.99. include_onlyfirst
+3.112. include_onlyfirst
 
 Type: boolean
 Default: no
@@ -6596,7 +7158,7 @@ Default: no
 Controls whether or not Mutt includes only the first attachment of the message
 you are replying.
 
-3.100. indent_string
+3.113. indent_string
 
 Type: string
 Default: ?> ?
@@ -6605,13 +7167,13 @@ Specifies the string to prepend to each line of text quoted in a message to
 which you are replying. You are strongly encouraged not to change this value,
 as it tends to agitate the more fanatical netizens.
 
+The value of this option is ignored if $text_flowed is set, too because the
+quoting mechanism is strictly defined for format=flowed.
+
 This option is a format string, please see the description of $index_format for
 supported printf(3)-style sequences.
 
-Because for format=lowed style messages the quoting mechanism is strictly
-defined, this setting is ignored if $text_flowed is set.
-
-3.101. index_format
+3.114. index_format
 
 Type: string
 Default: ?%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s?
@@ -6623,177 +7185,102 @@ personal taste.
 format output (see the man page for more details). The following sequences are
 defined in Mutt:
 
-%a
-
-    address of the author
-
-%A
-
-    reply-to address (if present; otherwise: address of 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
-    converted to sender's time zone
-
-%D
-
-    date and time of the message in the format specified by $date_format
-    converted to the local time zone
-
-%e
-
-    current message number in thread
-
-%E
-
-    number of messages in current thread
-
-%f
-
-    sender (address + real name), either From: or Return-Path:
-
-%F
-
-    author name, or recipient name if the message is from you
-
-%H
-
-    spam attribute(s) of this message
-
-%i
-
-    message-id of the current message
-
-%l
-
-    number of lines in the message (does not work with maildir, mh, and
-    possibly IMAP folders)
-
-%L
-
-    If an address in the ?To:? or ?Cc:? header field matches an address defined
-    by the users ?subscribe? command, this displays "To ", otherwise
-    the same as %F.
-
-%m
-
-    total number of message in the mailbox
-
-%M
-
-    number of hidden messages if the thread is collapsed.
-
-%N
-
-    message score
-
-%n
-
-    author's real name (or address if missing)
-
-%O
-
-    original save folder where mutt would formerly have stashed the message:
-    list name or recipient name if not sent to a list
-
-%P
-
-    progress indicator for the builtin pager (how much of the file has been
-    displayed)
-
-%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
-
-%v
-
-    first name of the author, or the recipient if the message is from you
-
-%X
-
-    number of attachments (please see the ?attachments? section for possible
-    speed effects)
-
-%y
-
-    ?X-Label:? field, if present
-
-%Y
-
-    ?X-Label:? field, if present, and (1) not at part of a thread tree, (2) at
-    the top of a thread, or (3) ?X-Label:? is different from preceding
-    message's ?X-Label:?.
-
-%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 library function strftime(3); 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 library function strftime(3); a leading bang
-    disables locales
-
-%(fmt)
-
-    the local date and time when the message was received. ?fmt? is expanded by
-    the library function strftime(3); a leading bang disables locales
-
-%
-
-    the current local time. ?fmt? is expanded by the library function strftime
-    (3); 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?
-
-%*X
-
-    soft-fill with character ?X? as pad
++-----------------------------------------------------------------------------+
+|%a   |address of the author                                                  |
+|-----+-----------------------------------------------------------------------|
+|%A   |reply-to address (if present; otherwise: address of 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   |
+|     |converted to sender's time zone                                        |
+|-----+-----------------------------------------------------------------------|
+|%D   |date and time of the message in the format specified by $date_format   |
+|     |converted to the local time zone                                       |
+|-----+-----------------------------------------------------------------------|
+|%e   |current message number in thread                                       |
+|-----+-----------------------------------------------------------------------|
+|%E   |number of messages in current thread                                   |
+|-----+-----------------------------------------------------------------------|
+|%f   |sender (address + real name), either From: or Return-Path:             |
+|-----+-----------------------------------------------------------------------|
+|%F   |author name, or recipient name if the message is from you              |
+|-----+-----------------------------------------------------------------------|
+|%H   |spam attribute(s) of this message                                      |
+|-----+-----------------------------------------------------------------------|
+|%i   |message-id of the current message                                      |
+|-----+-----------------------------------------------------------------------|
+|%l   |number of lines in the message (does not work with maildir, mh, and    |
+|     |possibly IMAP folders)                                                 |
+|-----+-----------------------------------------------------------------------|
+|     |If an address in the ?To:? or ?Cc:? header field matches an address    |
+|%L   |defined by the users ?subscribe? command, this displays "To |
+|     |", otherwise the same as %F.                                           |
+|-----+-----------------------------------------------------------------------|
+|%m   |total number of message in the mailbox                                 |
+|-----+-----------------------------------------------------------------------|
+|%M   |number of hidden messages if the thread is collapsed.                  |
+|-----+-----------------------------------------------------------------------|
+|%N   |message score                                                          |
+|-----+-----------------------------------------------------------------------|
+|%n   |author's real name (or address if missing)                             |
+|-----+-----------------------------------------------------------------------|
+|%O   |original save folder where mutt would formerly have stashed the        |
+|     |message: list name or recipient name if not sent to a list             |
+|-----+-----------------------------------------------------------------------|
+|%P   |progress indicator for the builtin pager (how much of the file has been|
+|     |displayed)                                                             |
+|-----+-----------------------------------------------------------------------|
+|%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                                        |
+|-----+-----------------------------------------------------------------------|
+|%v   |first name of the author, or the recipient if the message is from you  |
+|-----+-----------------------------------------------------------------------|
+|%X   |number of attachments (please see the ?attachments? section for        |
+|     |possible speed effects)                                                |
+|-----+-----------------------------------------------------------------------|
+|%y   |?X-Label:? field, if present                                           |
+|-----+-----------------------------------------------------------------------|
+|     |?X-Label:? field, if present, and (1) not at part of a thread tree, (2)|
+|%Y   |at the top of a thread, or (3) ?X-Label:? is different from preceding  |
+|     |message's ?X-Label:?.                                                  |
+|-----+-----------------------------------------------------------------------|
+|%Z   |message status flags                                                   |
+|-----+-----------------------------------------------------------------------|
+|%    |the date and time of the message is converted to sender's time zone,   |
+|{fmt}|and ?fmt? is expanded by the library function strftime(3); a leading   |
+|     |bang disables locales                                                  |
+|-----+-----------------------------------------------------------------------|
+|%    |the date and time of the message is converted to the local time zone,  |
+|[fmt]|and ?fmt? is expanded by the library function strftime(3); a leading   |
+|     |bang disables locales                                                  |
+|-----+-----------------------------------------------------------------------|
+|%    |the local date and time when the message was received. ?fmt? is        |
+|(fmt)|expanded by the library function strftime(3); a leading bang disables  |
+|     |locales                                                                |
+|-----+-----------------------------------------------------------------------|
+|%    |the current local time. ?fmt? is expanded by the library function      |
+||strftime(3); 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?                          |
+|-----+-----------------------------------------------------------------------|
+|%*X  |soft-fill with character ?X? as pad                                    |
++-----------------------------------------------------------------------------+
 
 ?Soft-fill? deserves some explanation: Normal right-justification will print
 everything to the left of the ?%>?, displaying padding and whatever lies to the
@@ -6805,14 +7292,14 @@ room for rightward text.
 Note that these expandos are supported in ?save-hook?, ?fcc-hook? and ?
 fcc-save-hook?, too.
 
-3.102. ispell
+3.115. ispell
 
 Type: path
 Default: ?ispell?
 
 How to invoke ispell (GNU's spell-checking software).
 
-3.103. keep_flagged
+3.116. keep_flagged
 
 Type: boolean
 Default: no
@@ -6820,7 +7307,7 @@ Default: no
 If set, read messages marked as flagged will not be moved from your spool
 mailbox to your $mbox mailbox, or as a result of a ?mbox-hook? command.
 
-3.104. locale
+3.117. locale
 
 Type: string
 Default: ?C?
@@ -6828,7 +7315,7 @@ Default: ?C?
 The locale used by strftime(3) to format dates. Legal values are the strings
 your system accepts for the locale environment variable $LC_TIME.
 
-3.105. mail_check
+3.118. mail_check
 
 Type: number
 Default: 5
@@ -6836,7 +7323,7 @@ Default: 5
 This variable configures how often (in seconds) mutt should look for new mail.
 Also see the $timeout variable.
 
-3.106. mailcap_path
+3.119. mailcap_path
 
 Type: string
 Default: (empty)
@@ -6844,7 +7331,7 @@ Default: (empty)
 This variable specifies which files to consult when attempting to display MIME
 bodies not directly supported by Mutt.
 
-3.107. mailcap_sanitize
+3.120. mailcap_sanitize
 
 Type: boolean
 Default: yes
@@ -6855,20 +7342,7 @@ sure it doesn't break some more advanced MIME stuff.
 
 DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE DOING!
 
-3.108. header_cache
-
-Type: path
-Default: (empty)
-
-This variable points to the header cache database. If pointing to a directory
-Mutt will contain a header cache database file per folder, if pointing to a
-file that file will be a single global header cache. By default it is unset so
-no header caching will be used.
-
-Header caching can greatly improve speed when opening POP, IMAP MH or Maildir
-folders, see ?caching? for details.
-
-3.109. maildir_header_cache_verify
+3.121. maildir_header_cache_verify
 
 Type: boolean
 Default: yes
@@ -6877,37 +7351,16 @@ Check for Maildir unaware programs other than mutt having modified maildir
 files when the header cache is in use. This incurs one stat(2) per message
 every time the folder is opened (which can be very slow for NFS folders).
 
-3.110. header_cache_pagesize
+3.122. maildir_trash
 
-Type: string
-Default: ?16384?
-
-When mutt is compiled with either gdbm or bdb4 as the header cache backend,
-this option changes the database page size. Too large or too small values can
-waste space, memory, or CPU time. The default should be more or less optimal
-for most use cases.
-
-3.111. header_cache_compress
-
-Type: boolean
-Default: yes
-
-When mutt is compiled with qdbm or tokyocabinet as header cache backend, this
-option determines whether the database will be compressed. Compression results
-in database files roughly being one fifth of the usual diskspace, but the
-uncompression can result in a slower opening of cached folder(s) which in
-general is still much faster than opening non header cached folders.
-
-3.112. maildir_trash
-
-Type: boolean
-Default: no
+Type: boolean
+Default: no
 
 If set, messages marked as deleted will be saved with the maildir trashed flag
 instead of unlinked. Note: this only applies to maildir-style mailboxes.
 Setting it will have no effect on other mailbox types.
 
-3.113. mark_old
+3.123. mark_old
 
 Type: boolean
 Default: yes
@@ -6917,7 +7370,7 @@ mailbox without reading them. With this option set, the next time you start
 mutt, the messages will show up with an ?O? next to them in the index menu,
 indicating that they are old.
 
-3.114. markers
+3.124. markers
 
 Type: boolean
 Default: yes
@@ -6927,7 +7380,7 @@ marker is displayed at the beginning of wrapped lines.
 
 Also see the $smart_wrap variable.
 
-3.115. mask
+3.125. mask
 
 Type: regular expression
 Default: ?!^\.[^.]?
@@ -6936,7 +7389,7 @@ A regular expression used in the file browser, optionally preceded by the not
 operator ?!?. Only files whose names match this mask will be shown. The match
 is always case-sensitive.
 
-3.116. mbox
+3.126. mbox
 
 Type: path
 Default: ??/mbox?
@@ -6946,23 +7399,15 @@ be appended.
 
 Also see the $move variable.
 
-3.117. mbox_type
+3.127. mbox_type
 
 Type: folder magic
 Default: mbox
 
 The default mailbox type used when creating new folders. May be any of ?mbox?,
-?MMDF?, ?MH? and ?Maildir?.
-
-3.118. metoo
-
-Type: boolean
-Default: no
-
-If unset, Mutt will remove your address (see the ?alternates? command) from the
-list of recipients when replying to a message.
+?MMDF?, ?MH? and ?Maildir?. This is overriden by the -m command-line option.
 
-3.119. menu_context
+3.128. menu_context
 
 Type: number
 Default: 0
@@ -6970,7 +7415,7 @@ Default: 0
 This variable controls the number of lines of context that are given when
 scrolling through menus. (Similar to $pager_context.)
 
-3.120. menu_move_off
+3.129. menu_move_off
 
 Type: boolean
 Default: yes
@@ -6979,7 +7424,7 @@ When unset, the bottom entry of menus will never scroll up past the bottom of
 the screen, unless there are less entries than lines. When set, the bottom
 entry may move off the bottom.
 
-3.121. menu_scroll
+3.130. menu_scroll
 
 Type: boolean
 Default: no
@@ -6989,7 +7434,39 @@ across a screen boundary. If unset, the screen is cleared and the next or
 previous page of the menu is displayed (useful for slow links to avoid many
 redraws).
 
-3.122. meta_key
+3.131. message_cache_clean
+
+Type: boolean
+Default: no
+
+If set, mutt will clean out obsolete entries from the message cache when the
+mailbox is synchronized. You probably only want to set it every once in a
+while, since it can be a little slow (especially for large folders).
+
+3.132. message_cachedir
+
+Type: path
+Default: (empty)
+
+Set this to a directory and mutt will cache copies of messages from your IMAP
+and POP servers here. You are free to remove entries at any time.
+
+When setting this variable to a directory, mutt needs to fetch every remote
+message only once and can perform regular expression searches as fast as for
+local folders.
+
+Also see the $message_cache_clean variable.
+
+3.133. message_format
+
+Type: string
+Default: ?%s?
+
+This is the string displayed in the ?attachment? menu for attachments of type
+message/rfc822. For a full listing of defined printf(3)-like sequences see the
+section on $index_format.
+
+3.134. meta_key
 
 Type: boolean
 Default: no
@@ -7001,7 +7478,15 @@ this is treated as if the user had pressed Esc then ?x?. This is because the
 result of removing the high bit from 0xf8 is 0x78, which is the ASCII character
 ?x?.
 
-3.123. mh_purge
+3.135. metoo
+
+Type: boolean
+Default: no
+
+If unset, Mutt will remove your address (see the ?alternates? command) from the
+list of recipients when replying to a message.
+
+3.136. mh_purge
 
 Type: boolean
 Default: no
@@ -7013,28 +7498,28 @@ variable is set, the message files will simply be deleted.
 
 This option is similar to $maildir_trash for Maildir folders.
 
-3.124. mh_seq_flagged
+3.137. mh_seq_flagged
 
 Type: string
 Default: ?flagged?
 
 The name of the MH sequence used for flagged messages.
 
-3.125. mh_seq_replied
+3.138. mh_seq_replied
 
 Type: string
 Default: ?replied?
 
 The name of the MH sequence used to tag replied messages.
 
-3.126. mh_seq_unseen
+3.139. mh_seq_unseen
 
 Type: string
 Default: ?unseen?
 
 The name of the MH sequence used for unseen messages.
 
-3.127. mime_forward
+3.140. mime_forward
 
 Type: quadoption
 Default: no
@@ -7047,7 +7532,7 @@ MIME from mail to mail, set this variable to ?ask-no? or ?ask-yes?.
 
 Also see $forward_decode and $mime_forward_decode.
 
-3.128. mime_forward_decode
+3.141. mime_forward_decode
 
 Type: boolean
 Default: no
@@ -7056,7 +7541,7 @@ Controls the decoding of complex MIME messages into text/plain when forwarding
 a message while $mime_forward is set. Otherwise $forward_decode is used
 instead.
 
-3.129. mime_forward_rest
+3.142. mime_forward_rest
 
 Type: quadoption
 Default: yes
@@ -7065,7 +7550,7 @@ When forwarding multiple attachments of a MIME message from the attachment
 menu, attachments which cannot be decoded in a reasonable manner will be
 attached to the newly composed message if this option is set.
 
-3.130. mix_entry_format
+3.143. mix_entry_format
 
 Type: string
 Default: ?%4n %c %-16s %a?
@@ -7073,23 +7558,17 @@ Default: ?%4n %c %-16s %a?
 This variable describes the format of a remailer line on the mixmaster chain
 selection screen. The following printf(3)-like sequences are supported:
 
-%n
-
-    The running number on the menu.
-
-%c
-
-    Remailer capabilities.
-
-%s
-
-    The remailer's short name.
-
-%a
-
-    The remailer's e-mail address.
++----------------------------------+
+|%n|The running number on the menu.|
+|--+-------------------------------|
+|%c|Remailer capabilities.         |
+|--+-------------------------------|
+|%s|The remailer's short name.     |
+|--+-------------------------------|
+|%a|The remailer's e-mail address. |
++----------------------------------+
 
-3.131. mixmaster
+3.144. mixmaster
 
 Type: path
 Default: ?mixmaster?
@@ -7098,7 +7577,7 @@ This variable contains the path to the Mixmaster binary on your system. It is
 used with various sets of parameters to gather the list of known remailers, and
 to finally send a message through the mixmaster chain.
 
-3.132. move
+3.145. move
 
 Type: quadoption
 Default: no
@@ -7106,39 +7585,7 @@ Default: no
 Controls whether or not Mutt will move read messages from your spool mailbox to
 your $mbox mailbox, or as a result of a ?mbox-hook? command.
 
-3.133. message_cachedir
-
-Type: path
-Default: (empty)
-
-Set this to a directory and mutt will cache copies of messages from your IMAP
-and POP servers here. You are free to remove entries at any time.
-
-When setting this variable to a directory, mutt needs to fetch every remote
-message only once and can perform regular expression searches as fast as for
-local folders.
-
-Also see the $message_cache_clean variable.
-
-3.134. message_cache_clean
-
-Type: boolean
-Default: no
-
-If set, mutt will clean out obsolete entries from the message cache when the
-mailbox is synchronized. You probably only want to set it every once in a
-while, since it can be a little slow (especially for large folders).
-
-3.135. message_format
-
-Type: string
-Default: ?%s?
-
-This is the string displayed in the ?attachment? menu for attachments of type
-message/rfc822. For a full listing of defined printf(3)-like sequences see the
-section on $index_format.
-
-3.136. narrow_tree
+3.146. narrow_tree
 
 Type: boolean
 Default: no
@@ -7146,7 +7593,7 @@ Default: no
 This variable, when set, makes the thread tree narrower, allowing deeper
 threads to fit on the screen.
 
-3.137. net_inc
+3.147. net_inc
 
 Type: number
 Default: 10
@@ -7157,7 +7604,7 @@ messages will be displayed.
 
 See also $read_inc, $write_inc and $net_inc.
 
-3.138. pager
+3.148. pager
 
 Type: path
 Default: ?builtin?
@@ -7171,7 +7618,7 @@ necessary because you can't call mutt functions directly from the pager, and
 screen resizes cause lines longer than the screen width to be badly formatted
 in the help menu.
 
-3.139. pager_context
+3.149. pager_context
 
 Type: number
 Default: 0
@@ -7181,7 +7628,11 @@ displaying the next or previous page in the internal pager. By default, Mutt
 will display the line after the last one on the screen at the top of the next
 page (0 lines of context).
 
-3.140. pager_format
+This variable also specifies the amount of context given for search results. If
+positive, this many lines will be given before a match, if 0, the match will be
+top-aligned.
+
+3.150. pager_format
 
 Type: string
 Default: ?-%Z- %C/%m: %-20.20n   %s%*  -- (%P)?
@@ -7190,7 +7641,7 @@ 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 $index_format section.
 
-3.141. pager_index_lines
+3.151. pager_index_lines
 
 Type: number
 Default: 0
@@ -7206,7 +7657,7 @@ in no index being shown. If the number of messages in the current folder is
 less than $pager_index_lines, then the index will only use as many lines as it
 needs.
 
-3.142. pager_stop
+3.152. pager_stop
 
 Type: boolean
 Default: no
@@ -7214,124 +7665,115 @@ Default: no
 When set, the internal-pager will not move to the next message when you are at
 the end of a message and invoke the  function.
 
-3.143. crypt_autosign
+3.153. pgp_auto_decode
 
 Type: boolean
 Default: no
 
-Setting this variable will cause Mutt to always attempt to cryptographically
-sign outgoing messages. This can be overridden by use of the pgp menu, when
-signing is not required or encryption is requested as well. If
-$smime_is_default is set, then OpenSSL is used instead to create S/MIME
-messages and settings can be overridden by use of the smime menu instead of the
-pgp menu. (Crypto only)
+If set, mutt will automatically attempt to decrypt traditional PGP messages
+whenever the user performs an operation which ordinarily would result in the
+contents of the message being operated on. For example, if the user displays a
+pgp-traditional message which has not been manually checked with the
+ function, mutt will automatically check the message for
+traditional pgp.
 
-3.144. crypt_autoencrypt
+3.154. pgp_autoinline
 
 Type: boolean
 Default: no
 
-Setting this variable will cause Mutt to always attempt to PGP encrypt outgoing
-messages. This is probably only useful in connection to the ?send-hook?
-command. It can be overridden by use of the pgp menu, when encryption is not
-required or signing is requested as well. If $smime_is_default is set, then
-OpenSSL is used instead to create S/MIME messages and settings can be
-overridden by use of the smime menu instead. (Crypto only)
+This option controls whether Mutt generates old-style inline (traditional) PGP
+encrypted or signed messages under certain circumstances. This can be
+overridden by use of the pgp menu, when inline is not required.
 
-3.145. pgp_ignore_subkeys
+Note that Mutt might automatically use PGP/MIME for messages which consist of
+more than a single MIME part. Mutt can be configured to ask before sending PGP/
+MIME messages when inline (traditional) would not work.
 
-Type: boolean
-Default: yes
+Also see the $pgp_mime_auto variable.
 
-Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, the
-principal key will inherit the subkeys' capabilities. Unset this if you want to
-play interesting key selection games. (PGP only)
+Also note that using the old-style PGP message format is strongly deprecated.
+(PGP only)
 
-3.146. crypt_replyencrypt
+3.155. pgp_check_exit
 
 Type: boolean
 Default: yes
 
-If set, automatically PGP or OpenSSL encrypt replies to messages which are
-encrypted. (Crypto only)
-
-3.147. crypt_replysign
-
-Type: boolean
-Default: no
-
-If set, automatically PGP or OpenSSL sign replies to messages which are signed.
+If set, mutt will check the exit code of the PGP subprocess when signing or
+encrypting. A non-zero exit code means that the subprocess failed. (PGP only)
 
-Note: this does not work on messages that are encrypted and signed! (Crypto
-only)
+3.156. pgp_clearsign_command
 
-3.148. crypt_replysignencrypted
+Type: string
+Default: (empty)
 
-Type: boolean
-Default: no
+This format is used to create an old-style ?clearsigned? PGP message. Note that
+the use of this format is strongly deprecated.
 
-If set, automatically PGP or OpenSSL sign replies to messages which are
-encrypted. This makes sense in combination with $crypt_replyencrypt, because it
-allows you to sign all messages which are automatically encrypted. This works
-around the problem noted in $crypt_replysign, that mutt is not able to find out
-whether an encrypted message is also signed. (Crypto only)
+This is a format string, see the $pgp_decode_command command for possible
+printf(3)-like sequences. (PGP only)
 
-3.149. crypt_timestamp
+3.157. pgp_decode_command
 
-Type: boolean
-Default: yes
+Type: string
+Default: (empty)
 
-If set, mutt will include a time stamp in the lines surrounding PGP or S/MIME
-output, so spoofing such lines is more difficult. If you are using colors to
-mark these lines, and rely on these, you may unset this setting. (Crypto only)
+This format strings specifies a command which is used to decode application/pgp
+attachments.
 
-3.150. pgp_use_gpg_agent
+The PGP command formats have their own set of printf(3)-like sequences:
 
-Type: boolean
-Default: no
++-----------------------------------------------------------------------------+
+|%p|Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty string   |
+|  |otherwise. Note: This may be used with a %? construct.                    |
+|--+--------------------------------------------------------------------------|
+|%f|Expands to the name of a file containing a message.                       |
+|--+--------------------------------------------------------------------------|
+|%s|Expands to the name of a file containing the signature part of a multipart|
+|  |/signed attachment when verifying it.                                     |
+|--+--------------------------------------------------------------------------|
+|%a|The value of $pgp_sign_as.                                                |
+|--+--------------------------------------------------------------------------|
+|%r|One or more key IDs.                                                      |
++-----------------------------------------------------------------------------+
 
-If set, mutt will use a possibly-running gpg-agent(1) process. (PGP only)
+For examples on how to configure these formats for the various versions of PGP
+which are floating around, see the pgp and gpg sample configuration files in
+the samples/ subdirectory which has been installed on your system alongside the
+documentation. (PGP only)
 
-3.151. crypt_verify_sig
+3.158. pgp_decrypt_command
 
-Type: quadoption
-Default: yes
+Type: string
+Default: (empty)
 
-If ?yes?, always attempt to verify PGP or S/MIME signatures. If ?ask-*?, ask
-whether or not to verify the signature. If \Fi?no?, never attempt to verify
-cryptographic signatures. (Crypto only)
+This command is used to decrypt a PGP encrypted message.
 
-3.152. smime_is_default
+This is a format string, see the $pgp_decode_command command for possible
+printf(3)-like sequences. (PGP only)
 
-Type: boolean
-Default: no
+3.159. pgp_encrypt_only_command
 
-The default behaviour of mutt is to use PGP on all auto-sign/encryption
-operations. To override and to use OpenSSL instead this must be set. However,
-this has no effect while replying, since mutt will automatically select the
-same application that was used to sign/encrypt the original message. (Note that
-this variable can be overridden by unsetting $crypt_autosmime.) (S/MIME only)
+Type: string
+Default: (empty)
 
-3.153. smime_ask_cert_label
+This command is used to encrypt a body part without signing it.
 
-Type: boolean
-Default: yes
+This is a format string, see the $pgp_decode_command command for possible
+printf(3)-like sequences. (PGP only)
 
-This flag controls whether you want to be asked to enter a label for a
-certificate about to be added to the database or not. It is set by default. (S/
-MIME only)
+3.160. pgp_encrypt_sign_command
 
-3.154. smime_decrypt_use_default_key
+Type: string
+Default: (empty)
 
-Type: boolean
-Default: yes
+This command is used to both sign and encrypt a body part.
 
-If set (default) this tells mutt to use the default key for decryption.
-Otherwise, if managing multiple certificate-key-pairs, mutt will try to use the
-mailbox-address to determine the key to use. It will ask you to supply a key,
-if it can't find one. (S/MIME only)
+This is a format string, see the $pgp_decode_command command for possible
+printf(3)-like sequences. (PGP only)
 
-3.155. pgp_entry_format
+3.161. pgp_entry_format
 
 Type: string
 Default: ?%4n %t%f %4l/0x%k %-4a %2c %u?
@@ -7340,45 +7782,48 @@ This variable allows you to customize the PGP key selection menu to your
 personal taste. This string is similar to $index_format, but has its own set of
 printf(3)-like sequences:
 
-%n
-
-    number
-
-%k
-
-    key id
-
-%u
-
-    user id
++-------------------------------------------------------------+
+|%n    |number                                                |
+|------+------------------------------------------------------|
+|%k    |key id                                                |
+|------+------------------------------------------------------|
+|%u    |user id                                               |
+|------+------------------------------------------------------|
+|%a    |algorithm                                             |
+|------+------------------------------------------------------|
+|%l    |key length                                            |
+|------+------------------------------------------------------|
+|%f    |flags                                                 |
+|------+------------------------------------------------------|
+|%c    |capabilities                                          |
+|------+------------------------------------------------------|
+|%t    |trust/validity of the key-uid association             |
+|------+------------------------------------------------------|
+|%[]|date of the key where  is an strftime(3) expression|
++-------------------------------------------------------------+
 
-%a
-
-    algorithm
-
-%l
-
-    key length
-
-%f
-
-    flags
+(PGP only)
 
-%c
+3.162. pgp_export_command
 
-    capabilities
+Type: string
+Default: (empty)
 
-%t
+This command is used to export a public key from the user's key ring.
 
-    trust/validity of the key-uid association
+This is a format string, see the $pgp_decode_command command for possible
+printf(3)-like sequences. (PGP only)
 
-%[]
+3.163. pgp_getkeys_command
 
-    date of the key where  is an strftime(3) expression
+Type: string
+Default: (empty)
 
-(PGP only)
+This command is invoked whenever mutt will need public key information. Of the
+sequences supported by $pgp_decode_command, %r is the only printf(3)-like
+sequence used with this format. (PGP only)
 
-3.156. pgp_good_sign
+3.164. pgp_good_sign
 
 Type: regular expression
 Default: (empty)
@@ -7388,53 +7833,77 @@ verified if the output from $pgp_verify_command contains the text. Use this
 variable if the exit code from the command is 0 even for bad signatures. (PGP
 only)
 
-3.157. pgp_check_exit
+3.165. pgp_ignore_subkeys
 
 Type: boolean
 Default: yes
 
-If set, mutt will check the exit code of the PGP subprocess when signing or
-encrypting. A non-zero exit code means that the subprocess failed. (PGP only)
+Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, the
+principal key will inherit the subkeys' capabilities. Unset this if you want to
+play interesting key selection games. (PGP only)
 
-3.158. pgp_long_ids
+3.166. pgp_import_command
 
-Type: boolean
-Default: no
+Type: string
+Default: (empty)
 
-If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs. (PGP
-only)
+This command is used to import a key from a message into the user's public key
+ring.
 
-3.159. pgp_retainable_sigs
+This is a format string, see the $pgp_decode_command command for possible
+printf(3)-like sequences. (PGP only)
 
-Type: boolean
-Default: no
+3.167. pgp_list_pubring_command
 
-If set, signed and encrypted messages will consist of nested multipart/signed
-and multipart/encrypted body parts.
+Type: string
+Default: (empty)
 
-This is useful for applications like encrypted and signed mailing lists, where
-the outer layer (multipart/encrypted) can be easily removed, while the inner
-multipart/signed part is retained. (PGP only)
+This command is used to list the public key ring's contents. The output format
+must be analogous to the one used by
+
+gpg --list-keys --with-colons.
+
+This format is also generated by the pgpring utility which comes with mutt.
+
+This is a format string, see the $pgp_decode_command command for possible
+printf(3)-like sequences. (PGP only)
+
+3.168. pgp_list_secring_command
+
+Type: string
+Default: (empty)
+
+This command is used to list the secret key ring's contents. The output format
+must be analogous to the one used by:
+
+gpg --list-keys --with-colons.
+
+This format is also generated by the pgpring utility which comes with mutt.
+
+This is a format string, see the $pgp_decode_command command for possible
+printf(3)-like sequences. (PGP only)
 
-3.160. pgp_autoinline
+3.169. pgp_long_ids
 
 Type: boolean
 Default: no
 
-This option controls whether Mutt generates old-style inline (traditional) PGP
-encrypted or signed messages under certain circumstances. This can be
-overridden by use of the pgp menu, when inline is not required.
+If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs. (PGP
+only)
 
-Note that Mutt might automatically use PGP/MIME for messages which consist of
-more than a single MIME part. Mutt can be configured to ask before sending PGP/
-MIME messages when inline (traditional) would not work.
+3.170. pgp_mime_auto
 
-Also see the $pgp_mime_auto variable.
+Type: quadoption
+Default: ask-yes
+
+This option controls whether Mutt will prompt you for automatically sending a
+(signed/encrypted) message using PGP/MIME when inline (traditional) fails (for
+any reason).
 
 Also note that using the old-style PGP message format is strongly deprecated.
 (PGP only)
 
-3.161. pgp_replyinline
+3.171. pgp_replyinline
 
 Type: boolean
 Default: no
@@ -7455,7 +7924,19 @@ Also see the $pgp_mime_auto variable.
 Also note that using the old-style PGP message format is strongly deprecated.
 (PGP only)
 
-3.162. pgp_show_unusable
+3.172. pgp_retainable_sigs
+
+Type: boolean
+Default: no
+
+If set, signed and encrypted messages will consist of nested multipart/signed
+and multipart/encrypted body parts.
+
+This is useful for applications like encrypted and signed mailing lists, where
+the outer layer (multipart/encrypted) can be easily removed, while the inner
+multipart/signed part is retained. (PGP only)
+
+3.173. pgp_show_unusable
 
 Type: boolean
 Default: yes
@@ -7464,7 +7945,7 @@ If set, mutt will display non-usable keys on the PGP key selection menu. This
 includes keys which have been revoked, have expired, or have been marked as
 ?disabled? by the user. (PGP only)
 
-3.163. pgp_sign_as
+3.174. pgp_sign_as
 
 Type: string
 Default: (empty)
@@ -7473,25 +7954,18 @@ If you have more than one key pair, this option allows you to specify which of
 your private keys to use. It is recommended that you use the keyid form to
 specify your key (e.g. 0x00112233). (PGP only)
 
-3.164. pgp_strict_enc
-
-Type: boolean
-Default: yes
-
-If set, Mutt will automatically encode PGP/MIME signed messages as
-quoted-printable. Please note that unsetting this variable may lead to problems
-with non-verifyable PGP signatures, so only change this if you know what you
-are doing. (PGP only)
+3.175. pgp_sign_command
 
-3.165. pgp_timeout
+Type: string
+Default: (empty)
 
-Type: number
-Default: 300
+This command is used to create the detached PGP signature for a multipart/
+signed PGP/MIME body part.
 
-The number of seconds after which a cached passphrase will expire if not used.
-(PGP only)
+This is a format string, see the $pgp_decode_command command for possible
+printf(3)-like sequences. (PGP only)
 
-3.166. pgp_sort_keys
+3.176. pgp_sort_keys
 
 Type: sort order
 Default: address
@@ -7499,96 +7973,45 @@ Default: address
 Specifies how the entries in the pgp menu are sorted. The following are legal
 values:
 
-address
-
-    sort alphabetically by user id
-
-keyid
-
-    sort alphabetically by key id
-
-date
-
-    sort by key creation date
-
-trust
-
-    sort by the trust of the key
++--------------------------------------+
+|address|sort alphabetically by user id|
+|-------+------------------------------|
+|keyid  |sort alphabetically by key id |
+|-------+------------------------------|
+|date   |sort by key creation date     |
+|-------+------------------------------|
+|trust  |sort by the trust of the key  |
++--------------------------------------+
 
 If you prefer reverse order of the above values, prefix it with ?reverse-?.
 (PGP only)
 
-3.167. pgp_mime_auto
-
-Type: quadoption
-Default: ask-yes
-
-This option controls whether Mutt will prompt you for automatically sending a
-(signed/encrypted) message using PGP/MIME when inline (traditional) fails (for
-any reason).
-
-Also note that using the old-style PGP message format is strongly deprecated.
-(PGP only)
-
-3.168. pgp_auto_decode
+3.177. pgp_strict_enc
 
 Type: boolean
-Default: no
-
-If set, mutt will automatically attempt to decrypt traditional PGP messages
-whenever the user performs an operation which ordinarily would result in the
-contents of the message being operated on. For example, if the user displays a
-pgp-traditional message which has not been manually checked with the
- function, mutt will automatically check the message for
-traditional pgp.
-
-3.169. pgp_decode_command
-
-Type: string
-Default: (empty)
-
-This format strings specifies a command which is used to decode application/pgp
-attachments.
-
-The PGP command formats have their own set of printf(3)-like sequences:
-
-%p
-
-    Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty string
-    otherwise. Note: This may be used with a %? construct.
-
-%f
-
-    Expands to the name of a file containing a message.
-
-%s
-
-    Expands to the name of a file containing the signature part of a multipart/
-    signed attachment when verifying it.
-
-%a
+Default: yes
 
-    The value of $pgp_sign_as.
+If set, Mutt will automatically encode PGP/MIME signed messages as
+quoted-printable. Please note that unsetting this variable may lead to problems
+with non-verifyable PGP signatures, so only change this if you know what you
+are doing. (PGP only)
 
-%r
+3.178. pgp_timeout
 
-    One or more key IDs.
+Type: number
+Default: 300
 
-For examples on how to configure these formats for the various versions of PGP
-which are floating around, see the pgp and gpg sample configuration files in
-the samples/ subdirectory which has been installed on your system alongside the
-documentation. (PGP only)
+The number of seconds after which a cached passphrase will expire if not used.
+(PGP only)
 
-3.170. pgp_getkeys_command
+3.179. pgp_use_gpg_agent
 
-Type: string
-Default: (empty)
+Type: boolean
+Default: no
 
-This command is invoked whenever mutt will need public key information. Of the
-sequences supported by $pgp_decode_command, %r is the only printf(3)-like
-sequence used with this format. (PGP only)
+If set, mutt will use a possibly-running gpg-agent(1) process. (PGP only)
 
-3.171. pgp_verify_command
+3.180. pgp_verify_command
 
 Type: string
 Default: (empty)
@@ -7598,80 +8021,7 @@ This command is used to verify PGP signatures.
 This is a format string, see the $pgp_decode_command command for possible
 printf(3)-like sequences. (PGP only)
 
-3.172. pgp_decrypt_command
-
-Type: string
-Default: (empty)
-
-This command is used to decrypt a PGP encrypted message.
-
-This is a format string, see the $pgp_decode_command command for possible
-printf(3)-like sequences. (PGP only)
-
-3.173. pgp_clearsign_command
-
-Type: string
-Default: (empty)
-
-This format is used to create a old-style ?clearsigned? PGP message. Note that
-the use of this format is strongly deprecated.
-
-This is a format string, see the $pgp_decode_command command for possible
-printf(3)-like sequences. (PGP only)
-
-3.174. pgp_sign_command
-
-Type: string
-Default: (empty)
-
-This command is used to create the detached PGP signature for a multipart/
-signed PGP/MIME body part.
-
-This is a format string, see the $pgp_decode_command command for possible
-printf(3)-like sequences. (PGP only)
-
-3.175. pgp_encrypt_sign_command
-
-Type: string
-Default: (empty)
-
-This command is used to both sign and encrypt a body part.
-
-This is a format string, see the $pgp_decode_command command for possible
-printf(3)-like sequences. (PGP only)
-
-3.176. pgp_encrypt_only_command
-
-Type: string
-Default: (empty)
-
-This command is used to encrypt a body part without signing it.
-
-This is a format string, see the $pgp_decode_command command for possible
-printf(3)-like sequences. (PGP only)
-
-3.177. pgp_import_command
-
-Type: string
-Default: (empty)
-
-This command is used to import a key from a message into the user's public key
-ring.
-
-This is a format string, see the $pgp_decode_command command for possible
-printf(3)-like sequences. (PGP only)
-
-3.178. pgp_export_command
-
-Type: string
-Default: (empty)
-
-This command is used to export a public key from the user's key ring.
-
-This is a format string, see the $pgp_decode_command command for possible
-printf(3)-like sequences. (PGP only)
-
-3.179. pgp_verify_key_command
+3.181. pgp_verify_key_command
 
 Type: string
 Default: (empty)
@@ -7681,392 +8031,45 @@ This command is used to verify key information from the key selection menu.
 This is a format string, see the $pgp_decode_command command for possible
 printf(3)-like sequences. (PGP only)
 
-3.180. pgp_list_secring_command
-
-Type: string
-Default: (empty)
-
-This command is used to list the secret key ring's contents. The output format
-must be analogous to the one used by:
-
-gpg --list-keys --with-colons.
-
-
-This format is also generated by the pgpring utility which comes with mutt.
-
-This is a format string, see the $pgp_decode_command command for possible
-printf(3)-like sequences. (PGP only)
-
-3.181. pgp_list_pubring_command
-
-Type: string
-Default: (empty)
-
-This command is used to list the public key ring's contents. The output format
-must be analogous to the one used by
-
-gpg --list-keys --with-colons.
-
-
-This format is also generated by the pgpring utility which comes with mutt.
-
-This is a format string, see the $pgp_decode_command command for possible
-printf(3)-like sequences. (PGP only)
-
-3.182. forward_decrypt
+3.182. pipe_decode
 
 Type: boolean
-Default: yes
-
-Controls the handling of encrypted messages when forwarding a message. When set
-, the outer layer of encryption is stripped off. This variable is only used if
-$mime_forward is set and $mime_forward_decode is unset. (PGP only)
-
-3.183. smime_timeout
-
-Type: number
-Default: 300
+Default: no
 
-The number of seconds after which a cached passphrase will expire if not used.
-(S/MIME only)
+Used in connection with the  command. When unset, Mutt will pipe
+the messages without any preprocessing. When set, Mutt will weed headers and
+will attempt to decode the messages first.
 
-3.184. smime_encrypt_with
+3.183. pipe_sep
 
 Type: string
-Default: (empty)
+Default: ?\n?
 
-This sets the algorithm that should be used for encryption. Valid choices are
-?des?, ?des3?, ?rc2-40?, ?rc2-64?, ?rc2-128?. If unset, ?3des? (TripleDES) is
-used. (S/MIME only)
+The separator to add between messages when piping a list of tagged messages to
+an external Unix command.
 
-3.185. smime_keys
+3.184. pipe_split
 
-Type: path
-Default: (empty)
-
-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-storage and retrieval of keys/certs by itself. This is very basic right now,
-and stores keys and certificates in two different directories, both named as
-the hash-value retrieved from OpenSSL. There is an index file which contains
-mailbox-address keyid pair, and which can be manually edited. This option
-points to the location of the private keys. (S/MIME only)
-
-3.186. smime_ca_location
-
-Type: path
-Default: (empty)
-
-This variable contains the name of either a directory, or a file which contains
-trusted certificates for use with OpenSSL. (S/MIME only)
-
-3.187. smime_certificates
-
-Type: path
-Default: (empty)
-
-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-storage and retrieval of keys by itself. This is very basic right now, and keys
-and certificates are stored in two different directories, both named as the
-hash-value retrieved from OpenSSL. There is an index file which contains
-mailbox-address keyid pairs, and which can be manually edited. This option
-points to the location of the certificates. (S/MIME only)
-
-3.188. smime_decrypt_command
-
-Type: string
-Default: (empty)
-
-This format string specifies a command which is used to decrypt application/
-x-pkcs7-mime attachments.
-
-The OpenSSL command formats have their own set of printf(3)-like sequences
-similar to PGP's:
-
-%f
-
-    Expands to the name of a file containing a message.
-
-%s
-
-    Expands to the name of a file containing the signature part of a multipart/
-    signed attachment when verifying it.
-
-%k
-
-    The key-pair specified with $smime_default_key
-
-%c
-
-    One or more certificate IDs.
-
-%a
-
-    The algorithm used for encryption.
-
-%C
-
-    CA location: Depending on whether $smime_ca_location points to a directory
-    or file, this expands to ?-CApath $smime_ca_location? or ?-CAfile
-    $smime_ca_location?.
-
-For examples on how to configure these formats, see the smime.rc in the samples
-/ subdirectory which has been installed on your system alongside the
-documentation. (S/MIME only)
-
-3.189. smime_verify_command
-
-Type: string
-Default: (empty)
-
-This command is used to verify S/MIME signatures of type multipart/signed.
-
-This is a format string, see the $smime_decrypt_command command for possible
-printf(3)-like sequences. (S/MIME only)
-
-3.190. smime_verify_opaque_command
-
-Type: string
-Default: (empty)
-
-This command is used to verify S/MIME signatures of type application/
-x-pkcs7-mime.
-
-This is a format string, see the $smime_decrypt_command command for possible
-printf(3)-like sequences. (S/MIME only)
-
-3.191. smime_sign_command
-
-Type: string
-Default: (empty)
-
-This command is used to created S/MIME signatures of type multipart/signed,
-which can be read by all mail clients.
-
-This is a format string, see the $smime_decrypt_command command for possible
-printf(3)-like sequences. (S/MIME only)
-
-3.192. smime_sign_opaque_command
-
-Type: string
-Default: (empty)
-
-This command is used to created S/MIME signatures of type application/
-x-pkcs7-signature, which can only be handled by mail clients supporting the S/
-MIME extension.
-
-This is a format string, see the $smime_decrypt_command command for possible
-printf(3)-like sequences. (S/MIME only)
-
-3.193. smime_encrypt_command
-
-Type: string
-Default: (empty)
-
-This command is used to create encrypted S/MIME messages.
-
-This is a format string, see the $smime_decrypt_command command for possible
-printf(3)-like sequences. (S/MIME only)
-
-3.194. smime_pk7out_command
-
-Type: string
-Default: (empty)
-
-This command is used to extract PKCS7 structures of S/MIME signatures, in order
-to extract the public X509 certificate(s).
-
-This is a format string, see the $smime_decrypt_command command for possible
-printf(3)-like sequences. (S/MIME only)
-
-3.195. smime_get_cert_command
-
-Type: string
-Default: (empty)
-
-This command is used to extract X509 certificates from a PKCS7 structure.
-
-This is a format string, see the $smime_decrypt_command command for possible
-printf(3)-like sequences. (S/MIME only)
-
-3.196. smime_get_signer_cert_command
-
-Type: string
-Default: (empty)
-
-This command is used to extract only the signers X509 certificate from a S/MIME
-signature, so that the certificate's owner may get compared to the email's
-?From:? field.
-
-This is a format string, see the $smime_decrypt_command command for possible
-printf(3)-like sequences. (S/MIME only)
-
-3.197. smime_import_cert_command
-
-Type: string
-Default: (empty)
-
-This command is used to import a certificate via smime_keys.
-
-This is a format string, see the $smime_decrypt_command command for possible
-printf(3)-like sequences. (S/MIME only)
-
-3.198. smime_get_cert_email_command
-
-Type: string
-Default: (empty)
-
-This command is used to extract the mail address(es) used for storing X509
-certificates, and for verification purposes (to check whether the certificate
-was issued for the sender's mailbox).
-
-This is a format string, see the $smime_decrypt_command command for possible
-printf(3)-like sequences. (S/MIME only)
-
-3.199. smime_default_key
-
-Type: string
-Default: (empty)
-
-This is the default key-pair to use for signing. This must be set to the keyid
-(the hash-value that OpenSSL generates) to work properly (S/MIME only)
-
-3.200. ssl_client_cert
-
-Type: path
-Default: (empty)
-
-The file containing a client certificate and its associated private key.
-
-3.201. ssl_force_tls
-
-Type: boolean
-Default: no
-
-If this variable is set, Mutt will require that all connections to remote
-servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
-server does not advertise the capability, since it would otherwise have to
-abort the connection anyway. This option supersedes $ssl_starttls.
-
-3.202. ssl_starttls
-
-Type: quadoption
-Default: yes
-
-If set (the default), mutt will attempt to use STARTTLS on servers advertising
-the capability. When unset, mutt will not attempt to use STARTTLS regardless of
-the server's capabilities.
-
-3.203. certificate_file
-
-Type: path
-Default: ??/.mutt_certificates?
-
-This variable specifies the file where the certificates you trust are saved.
-When an unknown certificate is encountered, you are asked if you accept it or
-not. If you accept it, the certificate can also be saved in this file and
-further connections are automatically accepted.
-
-You can also manually add CA certificates in this file. Any server certificate
-that is signed with one of these CA certificates is also automatically
-accepted.
-
-Example:
-
-set certificate_file=~/.mutt/certificates
-
-
-3.204. ssl_usesystemcerts
-
-Type: boolean
-Default: yes
-
-If set to yes, mutt will use CA certificates in the system-wide certificate
-store when checking if a server certificate is signed by a trusted CA.
-
-3.205. entropy_file
-
-Type: path
-Default: (empty)
-
-The file which includes random data that is used to initialize SSL library
-functions.
-
-3.206. ssl_use_sslv2
-
-Type: boolean
-Default: yes
-
-This variables specifies whether to attempt to use SSLv2 in the SSL
-authentication process.
-
-3.207. ssl_use_sslv3
-
-Type: boolean
-Default: yes
-
-This variables specifies whether to attempt to use SSLv3 in the SSL
-authentication process.
-
-3.208. ssl_use_tlsv1
-
-Type: boolean
-Default: yes
-
-This variables specifies whether to attempt to use TLSv1 in the SSL
-authentication process.
-
-3.209. ssl_min_dh_prime_bits
-
-Type: number
-Default: 0
-
-This variable specifies the minimum acceptable prime size (in bits) for use in
-any Diffie-Hellman key exchange. A value of 0 will use the default from the
-GNUTLS library.
-
-3.210. ssl_ca_certificates_file
-
-Type: path
-Default: (empty)
-
-This variable specifies a file containing trusted CA certificates. Any server
-certificate that is signed with one of these CA certificates is also
-automatically accepted.
-
-Example:
-
-set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-
-
-3.211. pipe_split
-
-Type: boolean
-Default: no
+Type: boolean
+Default: no
 
 Used in connection with the  function following . If
 this variable is unset, when piping a list of tagged messages Mutt will
 concatenate the messages and will pipe them all concatenated. When set, Mutt
-will pipe the messages one by one. In both cases the messages are piped in the
-current sorted order, and the $pipe_sep separator is added after each message.
-
-3.212. pipe_decode
-
-Type: boolean
-Default: no
-
-Used in connection with the  command. When unset, Mutt will pipe
-the messages without any preprocessing. When set, Mutt will weed headers and
-will attempt to decode the messages first.
+will pipe the messages one by one. In both cases the messages are piped in the
+current sorted order, and the $pipe_sep separator is added after each message.
 
-3.213. pipe_sep
+3.185. pop_auth_try_all
 
-Type: string
-Default: ?\n?
+Type: boolean
+Default: yes
 
-The separator to add between messages when piping a list of tagged messages to
-an external Unix command.
+If set, Mutt will try all available authentication methods. When unset, Mutt
+will only fall back to other authentication methods if the previous methods are
+unavailable. If a method is available but authentication fails, Mutt will not
+connect to the POP server.
 
-3.214. pop_authenticators
+3.186. pop_authenticators
 
 Type: string
 Default: (empty)
@@ -8082,18 +8085,7 @@ Example:
 
 set pop_authenticators="digest-md5:apop:user"
 
-
-3.215. pop_auth_try_all
-
-Type: boolean
-Default: yes
-
-If set, Mutt will try all available authentication methods. When unset, Mutt
-will only fall back to other authentication methods if the previous methods are
-unavailable. If a method is available but authentication fails, Mutt will not
-connect to the POP server.
-
-3.216. pop_checkinterval
+3.187. pop_checkinterval
 
 Type: number
 Default: 60
@@ -8101,7 +8093,7 @@ Default: 60
 This variable configures how often (in seconds) mutt should look for new mail
 in the currently selected mailbox if it is a POP mailbox.
 
-3.217. pop_delete
+3.188. pop_delete
 
 Type: quadoption
 Default: ask-no
@@ -8110,7 +8102,7 @@ If set, Mutt will delete successfully downloaded messages from the POP server
 when using the  function. When unset, Mutt will download messages
 but also leave them on the POP server.
 
-3.218. pop_host
+3.189. pop_host
 
 Type: string
 Default: (empty)
@@ -8120,10 +8112,9 @@ an alternative port, username and password, ie:
 
 [pop[s]://][username[:password]@]popserver[:port]
 
-
 where ?[...]? denotes an optional part.
 
-3.219. pop_last
+3.190. pop_last
 
 Type: boolean
 Default: no
@@ -8132,7 +8123,19 @@ If this variable is set, mutt will try to use the ?LAST? POP command for
 retrieving only unread messages from the POP server when using the 
 function.
 
-3.220. pop_reconnect
+3.191. pop_pass
+
+Type: string
+Default: (empty)
+
+Specifies the password for your POP account. If unset, Mutt will prompt you for
+your password when you open a POP mailbox.
+
+Warning: you should only use this option when you are on a fairly secure
+machine, because the superuser can read your muttrc even if you are the only
+one who can read the file.
+
+3.192. pop_reconnect
 
 Type: quadoption
 Default: ask-yes
@@ -8140,7 +8143,7 @@ Default: ask-yes
 Controls whether or not Mutt will try to reconnect to the POP server if the
 connection is lost.
 
-3.221. pop_user
+3.193. pop_user
 
 Type: string
 Default: (empty)
@@ -8149,19 +8152,7 @@ Your login name on the POP server.
 
 This variable defaults to your user name on the local machine.
 
-3.222. pop_pass
-
-Type: string
-Default: (empty)
-
-Specifies the password for your POP account. If unset, Mutt will prompt you for
-your password when you open a POP mailbox.
-
-Warning: you should only use this option when you are on a fairly secure
-machine, because the superuser can read your muttrc even if you are the only
-one who can read the file.
-
-3.223. post_indent_string
+3.194. post_indent_string
 
 Type: string
 Default: (empty)
@@ -8169,7 +8160,7 @@ Default: (empty)
 Similar to the $attribution variable, Mutt will append this string after the
 inclusion of a message which is being replied to.
 
-3.224. postpone
+3.195. postpone
 
 Type: quadoption
 Default: ask-yes
@@ -8179,7 +8170,7 @@ elect not to send immediately.
 
 Also see the $recall variable.
 
-3.225. postponed
+3.196. postponed
 
 Type: path
 Default: ??/postponed?
@@ -8190,7 +8181,7 @@ specified by this variable.
 
 Also see the $postpone variable.
 
-3.226. preconnect
+3.197. preconnect
 
 Type: string
 Default: (empty)
@@ -8203,13 +8194,12 @@ Example:
 set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \
 sleep 20 < /dev/null > /dev/null"
 
-
 Mailbox ?foo? on ?mailhost.net? can now be reached as ?{localhost:1234}foo?.
 
 Note: For this example to work, you must be able to log in to the remote
 machine without having to enter a password.
 
-3.227. print
+3.198. print
 
 Type: quadoption
 Default: ask-no
@@ -8217,14 +8207,14 @@ Default: ask-no
 Controls whether or not Mutt really prints messages. This is set to ?ask-no? by
 default, because some people accidentally hit ?p? often.
 
-3.228. print_command
+3.199. print_command
 
 Type: path
 Default: ?lpr?
 
 This specifies the command pipe that should be used to print messages.
 
-3.229. print_decode
+3.200. print_decode
 
 Type: boolean
 Default: yes
@@ -8236,7 +8226,7 @@ message when printing it. The latter setting may be useful if you are using
 some advanced printer filter which is able to properly format e-mail messages
 for printing.
 
-3.230. print_split
+3.201. print_split
 
 Type: boolean
 Default: no
@@ -8250,7 +8240,7 @@ as the message separator.
 Those who use the enscript(1) program's mail-printing mode will most likely
 want to set this option.
 
-3.231. prompt_after
+3.202. prompt_after
 
 Type: boolean
 Default: yes
@@ -8259,7 +8249,7 @@ If you use an external $pager, setting this variable will cause Mutt to prompt
 you for a command when the pager exits rather than returning to the index menu.
 If unset, Mutt will return to the index menu when the external pager exits.
 
-3.232. query_command
+3.203. query_command
 
 Type: path
 Default: (empty)
@@ -8268,7 +8258,7 @@ 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.
 
-3.233. query_format
+3.204. query_format
 
 Type: string
 Default: ?%4c %t %-25.25a %-25.25n %?e?(%e)??
@@ -8276,43 +8266,29 @@ Default: ?%4c %t %-25.25a %-25.25n %?e?(%e)??
 This variable describes the format of the ?query? menu. The following printf(3)
 -style sequences are understood:
 
-%a
-
-    destination address
-
-%c
-
-    current entry number
-
-%e
-
-    extra information *
-
-%n
-
-    destination name
-
-%t
-
-    ?*? if current entry is tagged, a space otherwise
-
-%>X
-
-    right justify the rest of the string and pad with ?X?
-
-%|X
-
-    pad to the end of the line with ?X?
-
-%*X
-
-    soft-fill with character ?X? as pad
++---------------------------------------------------------+
+|%a |destination address                                  |
+|---+-----------------------------------------------------|
+|%c |current entry number                                 |
+|---+-----------------------------------------------------|
+|%e |extra information *                                  |
+|---+-----------------------------------------------------|
+|%n |destination name                                     |
+|---+-----------------------------------------------------|
+|%t |?*? if current entry is tagged, a space otherwise    |
+|---+-----------------------------------------------------|
+|%>X|right justify the rest of the string and pad with ?X?|
+|---+-----------------------------------------------------|
+|%|X|pad to the end of the line with ?X?                  |
+|---+-----------------------------------------------------|
+|%*X|soft-fill with character ?X? as pad                  |
++---------------------------------------------------------+
 
 For an explanation of ?soft-fill?, see the $index_format documentation.
 
 * = can be optionally printed if nonzero, see the $status_format documentation.
 
-3.234. quit
+3.205. quit
 
 Type: quadoption
 Default: yes
@@ -8322,7 +8298,7 @@ this option is set, they do quit, if it is unset, 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.
 
-3.235. quote_regexp
+3.206. quote_regexp
 
 Type: regular expression
 Default: ?^([ \t]*[|>:}#])+?
@@ -8339,7 +8315,7 @@ it fails to produce a match.
 
 Match detection may be overridden by the $smileys regular expression.
 
-3.236. read_inc
+3.207. read_inc
 
 Type: number
 Default: 10
@@ -8356,14 +8332,14 @@ the mailbox.
 Also see the $write_inc, $net_inc and $time_inc variables and the ?tuning?
 section of the manual for performance considerations.
 
-3.237. read_only
+3.208. read_only
 
 Type: boolean
 Default: no
 
 If set, all folders are opened in read-only mode.
 
-3.238. realname
+3.209. realname
 
 Type: string
 Default: (empty)
@@ -8374,7 +8350,7 @@ sending messages.
 By default, this is the GECOS field from /etc/passwd. Note that this variable
 will not be used when the user has set a real name in the $from variable.
 
-3.239. recall
+3.210. recall
 
 Type: quadoption
 Default: ask-yes
@@ -8386,7 +8362,7 @@ Setting this variable to is not generally useful, and thus not recommended.
 
 Also see $postponed variable.
 
-3.240. record
+3.211. record
 
 Type: path
 Default: ??/sent?
@@ -8399,7 +8375,7 @@ with your email address in it.)
 The value of $record is overridden by the $force_name and $save_name variables,
 and the ?fcc-hook? command.
 
-3.241. reply_regexp
+3.212. reply_regexp
 
 Type: regular expression
 Default: ?^(re([\[0-9\]+])*|aw):[ \t]*?
@@ -8408,7 +8384,7 @@ A regular expression used to recognize reply messages when threading and
 replying. The default value corresponds to the English "Re:" and the German
 "Aw:".
 
-3.242. reply_self
+3.213. reply_self
 
 Type: boolean
 Default: no
@@ -8418,7 +8394,7 @@ you want to reply to the recipients of that message rather than to yourself.
 
 Also see the ?alternates? command.
 
-3.243. reply_to
+3.214. reply_to
 
 Type: quadoption
 Default: ask-yes
@@ -8429,7 +8405,7 @@ address in the From: header field instead. This option is useful for reading a
 mailing list that sets the Reply-To: header field to the list address and you
 want to send a private message to the author of a message.
 
-3.244. resolve
+3.215. resolve
 
 Type: boolean
 Default: yes
@@ -8438,7 +8414,7 @@ When set, the cursor will be automatically advanced to the next (possibly
 undeleted) message whenever a command that modifies the current message is
 executed.
 
-3.245. reverse_alias
+3.216. reverse_alias
 
 Type: boolean
 Default: no
@@ -8449,17 +8425,15 @@ message's sender. For example, if you have the following alias:
 
 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.
 
-3.246. reverse_name
+3.217. reverse_name
 
 Type: boolean
 Default: no
@@ -8474,7 +8448,7 @@ on the current machine.
 
 Also see the ?alternates? command.
 
-3.247. reverse_realname
+3.218. reverse_realname
 
 Type: boolean
 Default: yes
@@ -8484,7 +8458,7 @@ set, mutt will use the address from incoming messages as-is, possibly including
 eventual real names. When it is unset, mutt will override any such real names
 with the setting of the $realname variable.
 
-3.248. rfc2047_parameters
+3.219. rfc2047_parameters
 
 Type: boolean
 Default: no
@@ -8495,7 +8469,6 @@ files named like:
 
 =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
 
-
 When this variable is set interactively, the change won't be active until you
 change folders.
 
@@ -8506,7 +8479,7 @@ Also note that setting this parameter will not have the effect that mutt
 generates this kind of encoding. Instead, mutt will unconditionally use the
 encoding specified in RFC2231.
 
-3.249. save_address
+3.220. save_address
 
 Type: boolean
 Default: no
@@ -8515,7 +8488,7 @@ If set, mutt will take the sender's full address when choosing a 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.
 
-3.250. save_empty
+3.221. save_empty
 
 Type: boolean
 Default: yes
@@ -8527,7 +8500,7 @@ are never removed.
 Note: This only applies to mbox and MMDF folders, Mutt does not delete MH and
 Maildir directories.
 
-3.251. save_history
+3.222. save_history
 
 Type: number
 Default: 0
@@ -8535,7 +8508,7 @@ Default: 0
 This variable controls the size of the history (per category) saved in the
 $history_file file.
 
-3.252. save_name
+3.223. save_name
 
 Type: boolean
 Default: no
@@ -8549,7 +8522,7 @@ $record mailbox.
 
 Also see the $force_name variable.
 
-3.253. score
+3.224. score
 
 Type: boolean
 Default: yes
@@ -8558,7 +8531,7 @@ When this variable is unset, scoring is turned off. This can be useful to
 selectively disable scoring for certain folders when the
 $score_threshold_delete variable and related are used.
 
-3.254. score_threshold_delete
+3.225. score_threshold_delete
 
 Type: number
 Default: -1
@@ -8568,7 +8541,7 @@ this variable are automatically marked for deletion by mutt. Since mutt scores
 are always greater than or equal to zero, the default setting of this variable
 will never mark a message for deletion.
 
-3.255. score_threshold_flag
+3.226. score_threshold_flag
 
 Type: number
 Default: 9999
@@ -8576,7 +8549,7 @@ Default: 9999
 Messages which have been assigned a score greater than or equal to this
 variable's value are automatically marked "flagged".
 
-3.256. score_threshold_read
+3.227. score_threshold_read
 
 Type: number
 Default: -1
@@ -8586,7 +8559,15 @@ this variable are automatically marked as read by mutt. Since mutt scores are
 always greater than or equal to zero, the default setting of this variable will
 never mark a message read.
 
-3.257. send_charset
+3.228. search_context
+
+Type: number
+Default: 0
+
+For the pager, this variable specifies the number of lines shown before search
+results. By default, search results will be top-aligned.
+
+3.229. send_charset
 
 Type: string
 Default: ?us-ascii:iso-8859-1:utf-8?
@@ -8601,7 +8582,7 @@ after ?iso-8859-1?.
 In case the text cannot be converted into one of these exactly, mutt uses
 $charset as a fallback.
 
-3.258. sendmail
+3.230. sendmail
 
 Type: path
 Default: ?/usr/sbin/sendmail -oem -oi?
@@ -8610,114 +8591,338 @@ Specifies the program and arguments used to deliver mail sent by Mutt. Mutt
 expects that the specified program interprets additional arguments as recipient
 addresses.
 
-3.259. sendmail_wait
+3.231. sendmail_wait
+
+Type: number
+Default: 0
+
+Specifies the number of seconds to wait for the $sendmail process to finish
+before giving up and putting delivery in the background.
+
+Mutt interprets the value of this variable as follows:
+
++---------------------------------------------------------------------+
+|>0|number of seconds to wait for sendmail to finish before continuing|
+|--+------------------------------------------------------------------|
+|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.
+
+3.232. shell
+
+Type: path
+Default: (empty)
+
+Command to use when spawning a subshell. By default, the user's login shell
+from /etc/passwd is used.
+
+3.233. sig_dashes
+
+Type: boolean
+Default: yes
+
+If set, a line containing ?-- ? (note the trailing space) will be inserted
+before your $signature. It is strongly recommended that you not unset this
+variable unless your signature contains just your name. The reason for this is
+because many software packages use ?-- \n? to detect your signature. For
+example, Mutt has the ability to highlight the signature in a different color
+in the builtin pager.
+
+3.234. sig_on_top
+
+Type: boolean
+Default: no
+
+If set, the signature will be included before any quoted or forwarded text. It
+is strongly recommended that you do not set this variable unless you really
+know what you are doing, and are prepared to take some heat from netiquette
+guardians.
+
+3.235. signature
+
+Type: path
+Default: ??/.signature?
+
+Specifies the filename of your signature, which is appended to all 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 standard output.
+
+3.236. simple_search
+
+Type: string
+Default: ??f %s | ?s %s?
+
+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 ??? pattern operators.
+See ?patterns? 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 by replacing
+?%s? with the supplied string. For the default value, ?joe? would be expanded
+to: ??f joe | ?s joe?.
+
+3.237. sleep_time
+
+Type: number
+Default: 1
+
+Specifies time, in seconds, to pause while displaying certain informational
+messages, while moving from folder to folder and after expunging messages from
+the current folder. The default is to pause one second, so a value of zero for
+this option suppresses the pause.
+
+3.238. smart_wrap
+
+Type: boolean
+Default: yes
+
+Controls the display of lines longer than the screen width in the internal
+pager. If set, long lines are wrapped at a word boundary. If unset, lines are
+simply wrapped at the screen edge. Also see the $markers variable.
+
+3.239. smileys
+
+Type: regular expression
+Default: ?(>From )|(:[-^]?[][)(><}{|/DP])?
+
+The pager uses this variable to catch some common false positives of
+$quote_regexp, most notably smileys and not consider a line quoted text if it
+also matches $smileys. This mostly happens at the beginning of a line.
+
+3.240. smime_ask_cert_label
+
+Type: boolean
+Default: yes
+
+This flag controls whether you want to be asked to enter a label for a
+certificate about to be added to the database or not. It is set by default. (S/
+MIME only)
+
+3.241. smime_ca_location
+
+Type: path
+Default: (empty)
+
+This variable contains the name of either a directory, or a file which contains
+trusted certificates for use with OpenSSL. (S/MIME only)
+
+3.242. smime_certificates
+
+Type: path
+Default: (empty)
+
+Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
+storage and retrieval of keys by itself. This is very basic right now, and keys
+and certificates are stored in two different directories, both named as the
+hash-value retrieved from OpenSSL. There is an index file which contains
+mailbox-address keyid pairs, and which can be manually edited. This option
+points to the location of the certificates. (S/MIME only)
+
+3.243. smime_decrypt_command
+
+Type: string
+Default: (empty)
+
+This format string specifies a command which is used to decrypt application/
+x-pkcs7-mime attachments.
+
+The OpenSSL command formats have their own set of printf(3)-like sequences
+similar to PGP's:
+
++-----------------------------------------------------------------------------+
+|%f|Expands to the name of a file containing a message.                       |
+|--+--------------------------------------------------------------------------|
+|%s|Expands to the name of a file containing the signature part of a multipart|
+|  |/signed attachment when verifying it.                                     |
+|--+--------------------------------------------------------------------------|
+|%k|The key-pair specified with $smime_default_key                            |
+|--+--------------------------------------------------------------------------|
+|%c|One or more certificate IDs.                                              |
+|--+--------------------------------------------------------------------------|
+|%a|The algorithm used for encryption.                                        |
+|--+--------------------------------------------------------------------------|
+|  |CA location: Depending on whether $smime_ca_location points to a directory|
+|%C|or file, this expands to ?-CApath $smime_ca_location? or ?-CAfile         |
+|  |$smime_ca_location?.                                                      |
++-----------------------------------------------------------------------------+
+
+For examples on how to configure these formats, see the smime.rc in the samples
+/ subdirectory which has been installed on your system alongside the
+documentation. (S/MIME only)
+
+3.244. smime_decrypt_use_default_key
+
+Type: boolean
+Default: yes
+
+If set (default) this tells mutt to use the default key for decryption.
+Otherwise, if managing multiple certificate-key-pairs, mutt will try to use the
+mailbox-address to determine the key to use. It will ask you to supply a key,
+if it can't find one. (S/MIME only)
+
+3.245. smime_default_key
+
+Type: string
+Default: (empty)
+
+This is the default key-pair to use for signing. This must be set to the keyid
+(the hash-value that OpenSSL generates) to work properly (S/MIME only)
+
+3.246. smime_encrypt_command
+
+Type: string
+Default: (empty)
+
+This command is used to create encrypted S/MIME messages.
+
+This is a format string, see the $smime_decrypt_command command for possible
+printf(3)-like sequences. (S/MIME only)
+
+3.247. smime_encrypt_with
+
+Type: string
+Default: (empty)
+
+This sets the algorithm that should be used for encryption. Valid choices are
+?des?, ?des3?, ?rc2-40?, ?rc2-64?, ?rc2-128?. If unset, ?3des? (TripleDES) is
+used. (S/MIME only)
+
+3.248. smime_get_cert_command
+
+Type: string
+Default: (empty)
+
+This command is used to extract X509 certificates from a PKCS7 structure.
+
+This is a format string, see the $smime_decrypt_command command for possible
+printf(3)-like sequences. (S/MIME only)
+
+3.249. smime_get_cert_email_command
+
+Type: string
+Default: (empty)
+
+This command is used to extract the mail address(es) used for storing X509
+certificates, and for verification purposes (to check whether the certificate
+was issued for the sender's mailbox).
+
+This is a format string, see the $smime_decrypt_command command for possible
+printf(3)-like sequences. (S/MIME only)
+
+3.250. smime_get_signer_cert_command
 
-Type: number
-Default: 0
+Type: string
+Default: (empty)
 
-Specifies the number of seconds to wait for the $sendmail process to finish
-before giving up and putting delivery in the background.
+This command is used to extract only the signers X509 certificate from a S/MIME
+signature, so that the certificate's owner may get compared to the email's
+?From:? field.
 
-Mutt interprets the value of this variable as follows:
+This is a format string, see the $smime_decrypt_command command for possible
+printf(3)-like sequences. (S/MIME only)
 
->0
+3.251. smime_import_cert_command
 
-    number of seconds to wait for sendmail to finish before continuing
+Type: string
+Default: (empty)
 
-0
+This command is used to import a certificate via smime_keys.
 
-    wait forever for sendmail to finish
+This is a format string, see the $smime_decrypt_command command for possible
+printf(3)-like sequences. (S/MIME only)
 
-<0
+3.252. smime_is_default
 
-    always put sendmail in the background without waiting
+Type: boolean
+Default: no
 
-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.
+The default behaviour of mutt is to use PGP on all auto-sign/encryption
+operations. To override and to use OpenSSL instead this must be set. However,
+this has no effect while replying, since mutt will automatically select the
+same application that was used to sign/encrypt the original message. (Note that
+this variable can be overridden by unsetting $crypt_autosmime.) (S/MIME only)
 
-3.260. shell
+3.253. smime_keys
 
 Type: path
 Default: (empty)
 
-Command to use when spawning a subshell. By default, the user's login shell
-from /etc/passwd is used.
-
-3.261. sig_dashes
+Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
+storage and retrieval of keys/certs by itself. This is very basic right now,
+and stores keys and certificates in two different directories, both named as
+the hash-value retrieved from OpenSSL. There is an index file which contains
+mailbox-address keyid pair, and which can be manually edited. This option
+points to the location of the private keys. (S/MIME only)
 
-Type: boolean
-Default: yes
+3.254. smime_pk7out_command
 
-If set, a line containing ?-- ? (note the trailing space) will be inserted
-before your $signature. It is strongly recommended that you not unset this
-variable unless your signature contains just your name. The reason for this is
-because many software packages use ?-- \n? to detect your signature. For
-example, Mutt has the ability to highlight the signature in a different color
-in the builtin pager.
+Type: string
+Default: (empty)
 
-3.262. sig_on_top
+This command is used to extract PKCS7 structures of S/MIME signatures, in order
+to extract the public X509 certificate(s).
 
-Type: boolean
-Default: no
+This is a format string, see the $smime_decrypt_command command for possible
+printf(3)-like sequences. (S/MIME only)
 
-If set, the signature will be included before any quoted or forwarded text. It
-is strongly recommended that you do not set this variable unless you really
-know what you are doing, and are prepared to take some heat from netiquette
-guardians.
+3.255. smime_sign_command
 
-3.263. signature
+Type: string
+Default: (empty)
 
-Type: path
-Default: ??/.signature?
+This command is used to created S/MIME signatures of type multipart/signed,
+which can be read by all mail clients.
 
-Specifies the filename of your signature, which is appended to all 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 standard output.
+This is a format string, see the $smime_decrypt_command command for possible
+printf(3)-like sequences. (S/MIME only)
 
-3.264. simple_search
+3.256. smime_sign_opaque_command
 
 Type: string
-Default: ??f %s | ?s %s?
+Default: (empty)
 
-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 ??? pattern operators.
-See ?patterns? for more information on search patterns.
+This command is used to created S/MIME signatures of type application/
+x-pkcs7-signature, which can only be handled by mail clients supporting the S/
+MIME extension.
 
-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 by replacing
-?%s? with the supplied string. For the default value, ?joe? would be expanded
-to: ??f joe | ?s joe?.
+This is a format string, see the $smime_decrypt_command command for possible
+printf(3)-like sequences. (S/MIME only)
 
-3.265. smart_wrap
+3.257. smime_timeout
 
-Type: boolean
-Default: yes
+Type: number
+Default: 300
 
-Controls the display of lines longer than the screen width in the internal
-pager. If set, long lines are wrapped at a word boundary. If unset, lines are
-simply wrapped at the screen edge. Also see the $markers variable.
+The number of seconds after which a cached passphrase will expire if not used.
+(S/MIME only)
 
-3.266. smileys
+3.258. smime_verify_command
 
-Type: regular expression
-Default: ?(>From )|(:[-^]?[][)(><}{|/DP])?
+Type: string
+Default: (empty)
 
-The pager uses this variable to catch some common false positives of
-$quote_regexp, most notably smileys and not consider a line quoted text if it
-also matches $smileys. This mostly happens at the beginning of a line.
+This command is used to verify S/MIME signatures of type multipart/signed.
 
-3.267. sleep_time
+This is a format string, see the $smime_decrypt_command command for possible
+printf(3)-like sequences. (S/MIME only)
 
-Type: number
-Default: 1
+3.259. smime_verify_opaque_command
 
-Specifies time, in seconds, to pause while displaying certain informational
-messages, while moving from folder to folder and after expunging messages from
-the current folder. The default is to pause one second, so a value of zero for
-this option suppresses the pause.
+Type: string
+Default: (empty)
+
+This command is used to verify S/MIME signatures of type application/
+x-pkcs7-mime.
+
+This is a format string, see the $smime_decrypt_command command for possible
+printf(3)-like sequences. (S/MIME only)
 
-3.268. smtp_authenticators
+3.260. smtp_authenticators
 
 Type: string
 Default: (empty)
@@ -8732,8 +8937,7 @@ Example:
 
 set smtp_authenticators="digest-md5:cram-md5"
 
-
-3.269. smtp_pass
+3.261. smtp_pass
 
 Type: string
 Default: (empty)
@@ -8746,7 +8950,7 @@ Warning: you should only use this option when you are on a fairly secure
 machine, because the superuser can read your muttrc even if you are the only
 one who can read the file.
 
-3.270. smtp_url
+3.262. smtp_url
 
 Type: string
 Default: (empty)
@@ -8756,11 +8960,10 @@ This should take the form of an SMTP URL, eg:
 
 smtp[s]://[user[:pass]@]host[:port]/
 
-
-... where ?[...]? denotes an optional part. Setting this variable overrides the
+where ?[...]? denotes an optional part. Setting this variable overrides the
 value of the $sendmail variable.
 
-3.271. sort
+3.263. sort
 
 Type: sort order
 Default: date
@@ -8790,7 +8993,7 @@ Specifies how to sort messages in the ?index? menu. Valid values are:
 You may optionally use the ?reverse-? prefix to specify reverse sorting order
 (example: ?set sort=reverse-date-sent?).
 
-3.272. sort_alias
+3.264. sort_alias
 
 Type: sort order
 Default: alias
@@ -8804,7 +9007,7 @@ legal values:
 
   * unsorted (leave in order specified in .muttrc)
 
-3.273. sort_aux
+3.265. sort_aux
 
 Type: sort order
 Default: date
@@ -8819,14 +9022,13 @@ the last descendant, using the rest of $sort_aux as an ordering. For instance,
 
 set sort_aux=last-date-received
 
-
 would mean that if a new message is received in a thread, that thread becomes
 the last one displayed (or the first, if you have ?set sort=reverse-threads?.)
 
 Note: For reversed $sort order $sort_aux is reversed again (which is not the
 right thing to do, but kept to not break any existing configuration setting).
 
-3.274. sort_browser
+3.266. sort_browser
 
 Type: sort order
 Default: alpha
@@ -8845,7 +9047,7 @@ sorted alphabetically. Valid values:
 You may optionally use the ?reverse-? prefix to specify reverse sorting order
 (example: ?set sort_browser=reverse-date?).
 
-3.275. sort_re
+3.267. sort_re
 
 Type: boolean
 Default: yes
@@ -8858,7 +9060,7 @@ substring matching the setting of $reply_regexp. With $sort_re unset, mutt will
 attach the message whether or not this is the case, as long as the non-
 $reply_regexp parts of both messages are identical.
 
-3.276. spam_separator
+3.268. spam_separator
 
 Type: string
 Default: ?,?
@@ -8868,133 +9070,188 @@ unset, each successive header will overwrite any previous matches value for the
 spam label. If set, each successive match will append to the previous, using
 this variable's value as a separator.
 
-3.277. spoolfile
+3.269. spoolfile
 
 Type: path
 Default: (empty)
 
 If your spool mailbox is in a non-default place where Mutt cannot find it, you
-can specify its location with this variable. Mutt will automatically set this
-variable to the value of the environment variable $MAIL if it is not set.
-
-3.278. status_chars
-
-Type: string
-Default: ?-*%A?
-
-Controls the characters used by the ?%r? indicator in $status_format. The first
-character is used when the mailbox is unchanged. The second is used when the
-mailbox has been changed, and it needs to be resynchronized. The third is used
-if the mailbox is in 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  operation, bound by default to ?%?). The fourth is used to
-indicate that the current folder has been opened in attach- message mode
-(Certain operations like composing a new mail, replying, forwarding, etc. are
-not permitted in this mode).
-
-3.279. status_format
-
-Type: string
-Default: ?-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F?
- Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---?
-
-Controls the format of the status line displayed in the ?index? menu. This
-string is similar to $index_format, but has its own set of printf(3)-like
-sequences:
-
-%b
-
-    number of mailboxes with new mail *
+can specify its location with this variable. Mutt will initially set this
+variable to the value of the environment variable $MAIL or $MAILDIR if either
+is defined.
 
-%d
+3.270. ssl_ca_certificates_file
 
-    number of deleted messages *
-
-%f
-
-    the full pathname of the current mailbox
+Type: path
+Default: (empty)
 
-%F
+This variable specifies a file containing trusted CA certificates. Any server
+certificate that is signed with one of these CA certificates is also
+automatically accepted.
 
-    number of flagged messages *
+Example:
 
-%h
+set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
 
-    local hostname
+3.271. ssl_client_cert
 
-%l
+Type: path
+Default: (empty)
 
-    size (in bytes) of the current mailbox *
+The file containing a client certificate and its associated private key.
 
-%L
+3.272. ssl_force_tls
 
-    size (in bytes) of the messages shown (i.e., which match the current limit)
-    *
+Type: boolean
+Default: no
 
-%m
+If this variable is set, Mutt will require that all connections to remote
+servers be encrypted. Furthermore it will attempt to negotiate TLS even if the
+server does not advertise the capability, since it would otherwise have to
+abort the connection anyway. This option supersedes $ssl_starttls.
 
-    the number of messages in the mailbox *
+3.273. ssl_min_dh_prime_bits
 
-%M
+Type: number
+Default: 0
 
-    the number of messages shown (i.e., which match the current limit) *
+This variable specifies the minimum acceptable prime size (in bits) for use in
+any Diffie-Hellman key exchange. A value of 0 will use the default from the
+GNUTLS library.
 
-%n
+3.274. ssl_starttls
 
-    number of new messages in the mailbox *
+Type: quadoption
+Default: yes
 
-%o
+If set (the default), mutt will attempt to use STARTTLS on servers advertising
+the capability. When unset, mutt will not attempt to use STARTTLS regardless of
+the server's capabilities.
 
-    number of old unread messages *
+3.275. ssl_use_sslv2
 
-%p
+Type: boolean
+Default: no
 
-    number of postponed messages *
+This variable specifies whether to attempt to use SSLv2 in the SSL
+authentication process.
 
-%P
+3.276. ssl_use_sslv3
 
-    percentage of the way through the index
+Type: boolean
+Default: yes
 
-%r
+This variable specifies whether to attempt to use SSLv3 in the SSL
+authentication process.
 
-    modified/read-only/won't-write/attach-message indicator, according to
-    $status_chars
+3.277. ssl_use_tlsv1
 
-%s
+Type: boolean
+Default: yes
 
-    current sorting mode ($sort)
+This variable specifies whether to attempt to use TLSv1 in the SSL
+authentication process.
 
-%S
+3.278. ssl_usesystemcerts
 
-    current aux sorting method ($sort_aux)
+Type: boolean
+Default: yes
 
-%t
+If set to yes, mutt will use CA certificates in the system-wide certificate
+store when checking if a server certificate is signed by a trusted CA.
 
-    number of tagged messages *
+3.279. ssl_verify_dates
 
-%u
+Type: boolean
+Default: yes
 
-    number of unread messages *
+If set (the default), mutt will not automatically accept a server certificate
+that is either not yet valid or already expired. You should only unset this for
+particular known hosts, using the  function.
 
-%v
+3.280. ssl_verify_host
 
-    Mutt version string
+Type: boolean
+Default: yes
 
-%V
+If set (the default), mutt will not automatically accept a server certificate
+whose host name does not match the host used in your folder URL. You should
+only unset this for particular known hosts, using the  function.
 
-    currently active limit pattern, if any *
+3.281. status_chars
 
-%>X
+Type: string
+Default: ?-*%A?
 
-    right justify the rest of the string and pad with ?X?
+Controls the characters used by the ?%r? indicator in $status_format. The first
+character is used when the mailbox is unchanged. The second is used when the
+mailbox has been changed, and it needs to be resynchronized. The third is used
+if the mailbox is in 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  operation, bound by default to ?%?). The fourth is used to
+indicate that the current folder has been opened in attach- message mode
+(Certain operations like composing a new mail, replying, forwarding, etc. are
+not permitted in this mode).
 
-%|X
+3.282. status_format
 
-    pad to the end of the line with ?X?
+Type: string
+Default: ?-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F?
+ Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---?
 
-%*X
+Controls the format of the status line displayed in the ?index? menu. This
+string is similar to $index_format, but has its own set of printf(3)-like
+sequences:
 
-    soft-fill with character ?X? as pad
++-----------------------------------------------------------------------------+
+|%b |number of mailboxes with new mail *                                      |
+|---+-------------------------------------------------------------------------|
+|%d |number of deleted messages *                                             |
+|---+-------------------------------------------------------------------------|
+|%f |the full pathname of the current mailbox                                 |
+|---+-------------------------------------------------------------------------|
+|%F |number of flagged messages *                                             |
+|---+-------------------------------------------------------------------------|
+|%h |local hostname                                                           |
+|---+-------------------------------------------------------------------------|
+|%l |size (in bytes) of the current mailbox *                                 |
+|---+-------------------------------------------------------------------------|
+|%L |size (in bytes) of the messages shown (i.e., which match the current     |
+|   |limit) *                                                                 |
+|---+-------------------------------------------------------------------------|
+|%m |the number of messages in the mailbox *                                  |
+|---+-------------------------------------------------------------------------|
+|%M |the number of messages shown (i.e., which match the current limit) *     |
+|---+-------------------------------------------------------------------------|
+|%n |number of new messages in the mailbox *                                  |
+|---+-------------------------------------------------------------------------|
+|%o |number of old unread messages *                                          |
+|---+-------------------------------------------------------------------------|
+|%p |number of postponed messages *                                           |
+|---+-------------------------------------------------------------------------|
+|%P |percentage of the way through the index                                  |
+|---+-------------------------------------------------------------------------|
+|%r |modified/read-only/won't-write/attach-message indicator, according to    |
+|   |$status_chars                                                            |
+|---+-------------------------------------------------------------------------|
+|%s |current sorting mode ($sort)                                             |
+|---+-------------------------------------------------------------------------|
+|%S |current aux sorting method ($sort_aux)                                   |
+|---+-------------------------------------------------------------------------|
+|%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?                                      |
+|---+-------------------------------------------------------------------------|
+|%*X|soft-fill with character ?X? as pad                                      |
++-----------------------------------------------------------------------------+
 
 For an explanation of ?soft-fill?, see the $index_format documentation.
 
@@ -9033,7 +9290,7 @@ If you prefix the sequence character with a colon (?:?) character, mutt will
 replace any dots in the expansion by underscores. This might be helpful with
 IMAP folders that don't like dots in folder names.
 
-3.280. status_on_top
+3.283. status_on_top
 
 Type: boolean
 Default: no
@@ -9042,7 +9299,7 @@ Setting this variable causes the ?status bar? to be displayed on the first line
 of the screen rather than near the bottom. If $help is set, too it'll be placed
 at the bottom.
 
-3.281. strict_threads
+3.284. strict_threads
 
 Type: boolean
 Default: no
@@ -9054,7 +9311,7 @@ desirable, such as in a personal mailbox where you might have several unrelated
 messages with the subjects like ?hi? which will get grouped together. See also
 $sort_re for a less drastic way of controlling this behaviour.
 
-3.282. suspend
+3.285. suspend
 
 Type: boolean
 Default: yes
@@ -9063,7 +9320,7 @@ When unset, mutt won't stop when the user presses the terminal's susp key,
 usually ?^Z?. This is useful if you run mutt inside an xterm using a command
 like ?xterm -e mutt?.
 
-3.283. text_flowed
+3.286. text_flowed
 
 Type: boolean
 Default: no
@@ -9075,15 +9332,7 @@ this format's features, you'll need support in your editor.
 
 Note that $indent_string is ignored when this option is set.
 
-3.284. thread_received
-
-Type: boolean
-Default: no
-
-When set, mutt uses the date received rather than the date sent to thread
-messages by subject.
-
-3.285. thorough_search
+3.287. thorough_search
 
 Type: boolean
 Default: no
@@ -9098,7 +9347,15 @@ conversions. Otherwise mutt will attempt to match against the raw message
 received (for example quoted-printable encoded or with encoded headers) which
 may lead to incorrect search results.
 
-3.286. tilde
+3.288. thread_received
+
+Type: boolean
+Default: no
+
+When set, mutt uses the date received rather than the date sent to thread
+messages by subject.
+
+3.289. tilde
 
 Type: boolean
 Default: no
@@ -9106,7 +9363,7 @@ Default: no
 When set, the internal-pager will pad blank lines to the bottom of the screen
 with a tilde (???).
 
-3.287. time_inc
+3.290. time_inc
 
 Type: number
 Default: 0
@@ -9118,7 +9375,7 @@ slow terminals, or when running mutt on a remote system.
 
 Also see the ?tuning? section of the manual for performance considerations.
 
-3.288. timeout
+3.291. timeout
 
 Type: number
 Default: 600
@@ -9133,7 +9390,7 @@ waiting for input, performs these operations and continues to wait for input.
 
 A value of zero or less will cause Mutt to never time out.
 
-3.289. tmpdir
+3.292. tmpdir
 
 Type: path
 Default: (empty)
@@ -9143,7 +9400,7 @@ needed for displaying and composing messages. If this variable is not set, the
 environment variable $TMPDIR is used. If $TMPDIR is not set then ?/tmp? is
 used.
 
-3.290. to_chars
+3.293. to_chars
 
 Type: string
 Default: ? +TCFL?
@@ -9158,7 +9415,7 @@ fifth character is used to indicate mail that was sent by you. The sixth
 character is used to indicate when a mail was sent to a mailing-list you
 subscribe to.
 
-3.291. tunnel
+3.294. tunnel
 
 Type: string
 Default: (empty)
@@ -9169,11 +9426,22 @@ to your IMAP/POP3/SMTP server. Example:
 
 set tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
 
-
 Note: For this example to work you must be able to log in to the remote machine
 without having to enter a password.
 
-3.292. use_8bitmime
+When set, Mutt uses the tunnel for all remote connections. Please see ?
+account-hook? in the manual for how to use different tunnel commands per
+connection.
+
+3.295. uncollapse_jump
+
+Type: boolean
+Default: no
+
+When set, Mutt will jump to the next unread message, if any, when the current
+thread is uncollapsed.
+
+3.296. use_8bitmime
 
 Type: boolean
 Default: no
@@ -9185,7 +9453,7 @@ able to send mail.
 When set, Mutt will invoke $sendmail with the -B8BITMIME flag when sending
 8-bit messages to enable ESMTP negotiation.
 
-3.293. use_domain
+3.297. use_domain
 
 Type: boolean
 Default: yes
@@ -9193,7 +9461,7 @@ Default: yes
 When set, Mutt will qualify all local addresses (ones without the ?@host?
 portion) with the value of $hostname. If unset, no addresses will be qualified.
 
-3.294. use_envelope_from
+3.298. use_envelope_from
 
 Type: boolean
 Default: no
@@ -9207,7 +9475,7 @@ line switch. Therefore setting this option is not useful if the $sendmail
 variable already contains -f or if the executable pointed to by $sendmail
 doesn't support the -f switch.
 
-3.295. use_from
+3.299. use_from
 
 Type: boolean
 Default: yes
@@ -9216,7 +9484,7 @@ When set, Mutt will generate the ?From:? header field when sending messages. If
 unset, no ?From:? header field will be generated unless the user explicitly
 sets one using the ?my_hdr? command.
 
-3.296. use_idn
+3.300. use_idn
 
 Type: boolean
 Default: yes
@@ -9225,7 +9493,7 @@ When set, Mutt will show you international domain names decoded. Note: You can
 use IDNs for addresses even if this is unset. This variable only affects
 decoding.
 
-3.297. use_ipv6
+3.301. use_ipv6
 
 Type: boolean
 Default: yes
@@ -9234,7 +9502,7 @@ When set, Mutt will look for IPv6 addresses of hosts it tries to contact. If
 this option is unset, Mutt will restrict itself to IPv4 addresses. Normally,
 the default should work.
 
-3.298. user_agent
+3.302. user_agent
 
 Type: boolean
 Default: yes
@@ -9242,7 +9510,7 @@ Default: yes
 When set, mutt will add a ?User-Agent:? header to outgoing messages, indicating
 which version of mutt was used for composing them.
 
-3.299. visual
+3.303. visual
 
 Type: path
 Default: (empty)
@@ -9250,7 +9518,7 @@ Default: (empty)
 Specifies the visual editor to invoke when the ??v? command is given in the
 builtin editor.
 
-3.300. wait_key
+3.304. wait_key
 
 Type: boolean
 Default: yes
@@ -9266,7 +9534,7 @@ is interactive.
 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.
 
-3.301. weed
+3.305. weed
 
 Type: boolean
 Default: yes
@@ -9274,7 +9542,7 @@ Default: yes
 When set, mutt will weed headers when displaying, forwarding, printing, or
 replying to messages.
 
-3.302. wrap
+3.306. wrap
 
 Type: number
 Default: 0
@@ -9283,7 +9551,7 @@ When set to a positive value, mutt will wrap text at $wrap characters. When set
 to a negative value, mutt will wrap text so that there are $wrap characters of
 empty space on the right side of the terminal.
 
-3.303. wrap_search
+3.307. wrap_search
 
 Type: boolean
 Default: yes
@@ -9293,14 +9561,24 @@ Controls whether searches wrap around the end.
 When set, searches will wrap around the first (or last) item. When unset,
 incremental searches will not wrap.
 
-3.304. wrapmargin
+3.308. wrapmargin
 
 Type: number
 Default: 0
 
 (DEPRECATED) Equivalent to setting $wrap with a negative value.
 
-3.305. write_inc
+3.309. write_bcc
+
+Type: boolean
+Default: yes
+
+Controls whether mutt writes out the ?Bcc:? header when preparing messages to
+be sent. Exim users may wish to unset this. If mutt is set to deliver directly
+via SMTP (see $smtp_url), this option does nothing: mutt will never write out
+the ?Bcc:? header in this case.
+
+3.310. write_inc
 
 Type: number
 Default: 10
@@ -9312,16 +9590,6 @@ writing a mailbox.
 Also see the $read_inc, $net_inc and $time_inc variables and the ?tuning?
 section of the manual for performance considerations.
 
-3.306. write_bcc
-
-Type: boolean
-Default: yes
-
-Controls whether mutt writes out the ?Bcc:? header when preparing messages to
-be sent. Exim users may wish to unset this. If mutt is set to deliver directly
-via SMTP (see $smtp_url), this option does nothing: mutt will never write out
-the ?Bcc:? header in this case.
-
 4. Functions
 
 The following is the list of available functions listed by the mapping in which
@@ -9329,13 +9597,13 @@ they are available. The default key setting is given, and an explanation of
 what the function does. The key bindings of these functions can be changed with
 the bind command.
 
-4.1. generic menu
+4.1. Generic Menu
 
 The generic menu is not a real menu, but specifies common functions (such as
 movement) available in all menus except for pager and editor. Changing settings
 for this menu will affect the default bindings for all menus (except as noted).
 
-Table 8.2. Default generic function bindings
+Table 9.2. Default generic Function Bindings
 
 +-------------------------------------------------------------------------+
 |    Function     |Default key|                Description                |
@@ -9406,9 +9674,9 @@ Table 8.2. Default generic function bindings
 +-------------------------------------------------------------------------+
 
 
-4.2. index menu
+4.2. Index Menu
 
-Table 8.3. Default index function bindings
+Table 9.3. Default index Function Bindings
 
 +-----------------------------------------------------------------------------+
 |         Function         | Default |              Description               |
@@ -9511,7 +9779,8 @@ Table 8.3. Default index function bindings
 |          |Esc e    |use the current message as a template   |
 |                          |         |for a new one                           |
 |--------------------------+---------+----------------------------------------|
-|            |s        |save message/attachment to a file       |
+|            |s        |save message/attachment to a mailbox/   |
+|                          |         |file                                    |
 |--------------------------+---------+----------------------------------------|
 |             |T        |tag messages matching a pattern         |
 |--------------------------+---------+----------------------------------------|
@@ -9577,9 +9846,9 @@ Table 8.3. Default index function bindings
 +-----------------------------------------------------------------------------+
 
 
-4.3. pager menu
+4.3. Pager Menu
 
-Table 8.4. Default pager function bindings
+Table 9.4. Default pager Function Bindings
 
 +-----------------------------------------------------------------------------+
 |        Function        | Default |               Description                |
@@ -9607,6 +9876,10 @@ Table 8.4. Default pager function bindings
 |------------------------+---------+------------------------------------------|
 |      |Esc d    |delete all messages in subthread          |
 |------------------------+---------+------------------------------------------|
+|              |w        |set a status flag on a message            |
+|------------------------+---------+------------------------------------------|
+|            |W        |clear a status flag from a message        |
+|------------------------+---------+------------------------------------------|
 |                  |e        |edit the raw message                      |
 |------------------------+---------+------------------------------------------|
 |             |^E       |edit attachment content type              |
@@ -9666,7 +9939,7 @@ Table 8.4. Default pager function bindings
 |        |Esc e    |use the current message as a template for |
 |                        |         |a new one                                 |
 |------------------------+---------+------------------------------------------|
-|          |s        |save message/attachment to a file         |
+|          |s        |save message/attachment to a mailbox/file |
 |------------------------+---------+------------------------------------------|
 |           |S        |skip beyond quoted text                   |
 |------------------------+---------+------------------------------------------|
@@ -9753,9 +10026,9 @@ Table 8.4. Default pager function bindings
 +-----------------------------------------------------------------------------+
 
 
-4.4. alias menu
+4.4. Alias Menu
 
-Table 8.5. Default alias function bindings
+Table 9.5. Default alias Function Bindings
 
 +-------------------------------------------------------+
 |    Function    |Default key|       Description        |
@@ -9766,9 +10039,9 @@ Table 8.5. Default alias function bindings
 +-------------------------------------------------------+
 
 
-4.5. query menu
+4.5. Query Menu
 
-Table 8.6. Default query function bindings
+Table 9.6. Default query Function Bindings
 
 +----------------------------------------------------------------------+
 |   Function   |Default key|                Description                |
@@ -9783,9 +10056,9 @@ Table 8.6. Default query function bindings
 +----------------------------------------------------------------------+
 
 
-4.6. attach menu
+4.6. Attach Menu
 
-Table 8.7. Default attach function bindings
+Table 9.7. Default attach Function Bindings
 
 +-----------------------------------------------------------------------------+
 |       Function        | Default |                Description                |
@@ -9799,7 +10072,7 @@ Table 8.7. Default attach function bindings
 |-----------------------+---------+-------------------------------------------|
 |          |p        |print the current entry                    |
 |-----------------------+---------+-------------------------------------------|
-|           |s        |save message/attachment to a file          |
+|           |s        |save message/attachment to a mailbox/file  |
 |-----------------------+---------+-------------------------------------------|
 |           ||        |pipe message/attachment to a shell command |
 |-----------------------+---------+-------------------------------------------|
@@ -9835,9 +10108,9 @@ Table 8.7. Default attach function bindings
 +-----------------------------------------------------------------------------+
 
 
-4.7. compose menu
+4.7. Compose Menu
 
-Table 8.8. Default compose function bindings
+Table 9.8. Default compose Function Bindings
 
 +-----------------------------------------------------------------------------+
 |      Function       | Default  |                Description                 |
@@ -9851,7 +10124,7 @@ Table 8.8. Default compose function bindings
 |---------------------+----------+--------------------------------------------|
 |            |c         |edit the CC list                            |
 |---------------------+----------+--------------------------------------------|
-|          |C         |save message/attachment to a file           |
+|          |C         |save message/attachment to a mailbox/file   |
 |---------------------+----------+--------------------------------------------|
 |        |D         |delete the current entry                    |
 |---------------------+----------+--------------------------------------------|
@@ -9927,9 +10200,9 @@ Table 8.8. Default compose function bindings
 +-----------------------------------------------------------------------------+
 
 
-4.8. postpone menu
+4.8. Postpone Menu
 
-Table 8.9. Default postpone function bindings
+Table 9.9. Default postpone Function Bindings
 
 +-------------------------------------------------------+
 |    Function    |Default key|       Description        |
@@ -9940,9 +10213,9 @@ Table 8.9. Default postpone function bindings
 +-------------------------------------------------------+
 
 
-4.9. browser menu
+4.9. Browser Menu
 
-Table 8.10. Default browser function bindings
+Table 9.10. Default browser Function Bindings
 
 +-----------------------------------------------------------------------------+
 |     Function      | Default  |                 Description                  |
@@ -9984,9 +10257,9 @@ Table 8.10. Default browser function bindings
 +-----------------------------------------------------------------------------+
 
 
-4.10. pgp menu
+4.10. Pgp Menu
 
-Table 8.11. Default pgp function bindings
+Table 9.11. Default pgp Function Bindings
 
 +------------------------------------------------+
 |  Function  |Default key|      Description      |
@@ -9997,9 +10270,9 @@ Table 8.11. Default pgp function bindings
 +------------------------------------------------+
 
 
-4.11. smime menu
+4.11. Smime Menu
 
-Table 8.12. Default smime function bindings
+Table 9.12. Default smime Function Bindings
 
 +------------------------------------------------+
 |  Function  |Default key|      Description      |
@@ -10010,9 +10283,9 @@ Table 8.12. Default smime function bindings
 +------------------------------------------------+
 
 
-4.12. mix menu
+4.12. Mix Menu
 
-Table 8.13. Default mix function bindings
+Table 9.13. Default mix Function Bindings
 
 +-----------------------------------------------------------------+
 |  Function  |Default key|              Description               |
@@ -10031,9 +10304,9 @@ Table 8.13. Default mix function bindings
 +-----------------------------------------------------------------+
 
 
-4.13. editor menu
+4.13. Editor Menu
 
-Table 8.14. Default editor function bindings
+Table 9.14. Default editor Function Bindings
 
 +-----------------------------------------------------------------------------+
 |    Function     |Default key|                  Description                  |
@@ -10085,12 +10358,12 @@ Table 8.14. Default editor function bindings
 +-----------------------------------------------------------------------------+
 
 
-Chapter 9. Miscellany
+Chapter 10. Miscellany
 
 Table of Contents
 
 1. Acknowledgements
-2. About this document
+2. About This Document
 
 1. Acknowledgements
 
@@ -10183,7 +10456,7 @@ The following people have been very helpful to the development of Mutt:
 
   * Ken Weinert 
 
-2. About this document
+2. About This Document
 
 This document was written in DocBook, and then rendered using the Gnome XSLT
 toolkit.
diff --git a/doc/manual.xml.head b/doc/manual.xml.head
index 012eaeb..e8dd169 100644
--- a/doc/manual.xml.head
+++ b/doc/manual.xml.head
@@ -13,7 +13,7 @@
 
 
 
-All mail clients suck.  This one just sucks less. -me, circa 1995
+All mail clients suck.  This one just sucks less. — me, circa 1995
 
 
 
@@ -82,7 +82,7 @@ both lists.
 
 
 
-Software Distribution Sites
+Getting Mutt
 
 
 Mutt releases can be downloaded from
@@ -91,10 +91,15 @@ For a list of mirror sites, please refer to
 http://www.mutt.org/download.html.
 
 
+
+For nightly tarballs and version control access, please refer to the
+Mutt development site.
+
+
 
 
 
-Mutt online resources
+Mutt Online Resources
 
 
 
@@ -102,8 +107,8 @@ For a list of mirror sites, please refer to
 Bug Tracking System
 
 
-The official mutt bug tracking system can be found at
-http://dev.mutt.org/
+The official Mutt bug tracking system can be found at
+http://bugs.mutt.org/
 
 
 
@@ -156,7 +161,7 @@ tricks.
 
 
 Since translations of Mutt into other languages are highly appreciated,
-the mutt developers always look for skilled translators that help
+the Mutt developers always look for skilled translators that help
 improve and continue to maintain stale translations.
 
 
@@ -169,7 +174,7 @@ refer to the developer pages at
 
 
 
-Typograhical conventions
+Typograhical Conventions
 
 
 This section lists typographical conventions followed throughout this
@@ -188,7 +193,8 @@ conventions for special terms.
 <PageUp>named keys
 <create-alias>named Mutt function
 ˆGControl+G key combination
-$mail_checkMutt configuration option
+$mail_checkMutt configuration option
+$HOMEenvironment variable
 

 
 

@@ -214,7 +220,7 @@ denote that the argument may be repeated arbitrary times.
 Copyright
 
 
-Mutt is Copyright (C) 1996-2009 Michael R. Elkins
+Mutt is Copyright © 1996-2009 Michael R. Elkins
 me@mutt.org and others.
 
 
@@ -259,13 +265,13 @@ You can always type ? in any menu to display the current bindings
 
 
 
-The first thing you need to do is invoke mutt, simply by typing mutt
+The first thing you need to do is invoke Mutt, simply by typing mutt
 at the command line.  There are various command-line options, see
-either the mutt man page or the reference.
+either the Mutt man page or the reference.
 
 
 
-Core concepts
+Core Concepts
 
 
 Mutt is a text-based application which interacts with users through
@@ -285,6 +291,13 @@ informational and error messages as well as for prompts and for entering
 interactive commands.
 
 
+
+Mutt is configured through variables which, if the user wants to
+permanently use a non-default value, are written to configuration
+files. Mutt supports a rich config file syntax to make even complex
+configuration files readable and commentable.
+
+
 
 Because Mutt allows for customizing almost all key bindings, there are
 so-called functions which can be executed manually (using the
@@ -315,18 +328,149 @@ display for a folder or even implementing auto-archiving based on a
 per-folder basis and much more.
 
 
+
+Besides an interactive mode, Mutt can also be used as a command-line
+tool only send messages. It also supports a
+mailx(1)-compatible interface, see  for a complete list of command-line
+options.
+
+
+
+
+
+Screens and Menus
+
+
+Index
+
+
+The index is the screen that you usually see first when you start
+Mutt. It gives an overview over your emails in the currently opened
+mailbox. By default, this is your system mailbox.  The information you
+see in the index is a list of emails, each with its number on the left,
+its flags (new email, important email, email that has been forwarded or
+replied to, tagged email, ...), the date when email was sent, its
+sender, the email size, and the subject. Additionally, the index also
+shows thread hierarchies: when you reply to an email, and the other
+person replies back, you can see the other's person email in a
+"sub-tree" below.  This is especially useful for personal email between
+a group of people or when you've subscribed to mailing lists.
+
+
+
+
+
+Pager
+
+
+The pager is responsible for showing the email content. On the top of
+the pager you have an overview over the most important email headers
+like the sender, the recipient, the subject, and much more
+information. How much information you actually see depends on your
+configuration, which we'll describe below.
+
+
+
+Below the headers, you see the email body which usually contains the
+message. If the email contains any attachments, you will see more
+information about them below the email body, or, if the attachments are
+text files, you can view them directly in the pager.
+
+
+
+To give the user a good overview, it is possible to configure Mutt to
+show different things in the pager with different colors. Virtually
+everything that can be described with a regular expression can be
+colored, e.g. URLs, email addresses or smileys.
+
+
+
+
+
+File Browser
+
+
+The file browser is the interface to the local or remote file
+system. When selecting a mailbox to open, the browser allows custom
+sorting of items, limiting the items shown by a regular expression and a
+freely adjustable format of what to display in which way. It also allows
+for easy navigation through the file system when selecting file(s) to
+attach to a message, select multiple files to attach and many more.
+
+
+
+
+
+Help
+
+
+The help screen is meant to offer a quick help to the user. It lists the
+current configuration of key bindings and their associated commands
+including a short description, and currently unbound functions that
+still need to be associated with a key binding (or alternatively, they
+can be called via the Mutt command prompt).
+
+
+
+
+
+Compose Menu
+
+
+The compose menu features a split screen containing the information
+which really matter before actually sending a message by mail: who gets
+the message as what (recipients and who gets what kind of
+copy). Additionally, users may set security options like deciding
+whether to sign, encrypt or sign and encrypt a message with/for what
+keys. Also, it's used to attach messages, to re-edit any attachment
+including the message itself.
+
+
+
+
+
+Alias Menu
+
+
+The alias menu is used to help users finding the recipients of
+messages. For users who need to contact many people, there's no need to
+remember addresses or names completely because it allows for searching,
+too. The alias mechanism and thus the alias menu also features grouping
+several addresses by a shorter nickname, the actual alias, so that users
+don't have to select each single recipient manually.
+
+
+
+
+
+Attachment Menu
+
+
+As will be later discussed in detail, Mutt features a good and stable
+MIME implementation, that is, it supports sending and receiving messages
+of arbitrary MIME types. The attachment menu displays a message's
+structure in detail: what content parts are attached to which parent
+part (which gives a true tree structure), which type is of what type and
+what size.  Single parts may saved, deleted or modified to offer great
+and easy access to message's internals.
+
+
+
+
 
 
 
 Moving Around in Menus
 
 
-The most important navigation keys common to all menus are shown in
-.
+The most important navigation keys common to line- or entry-based menus
+are shown in  and in
+ for page-based menus.
 
 
-
-Most common navigation keys
+

+Most common navigation keys in entry-based menus
 KeyFunctionDescription
@@ -344,6 +488,23 @@ The most important navigation keys common to all menus are shown in
 

 
 
 

 
+
+Most common navigation keys in page-based menus
+
+
+KeyFunctionDescription
+
+
+J or <Return><next-line>scroll down one line
+<Backspace><previous-line>sroll up one line
+K, <Space> or <PageDn><next-page>move to the next page
+- or <PageUp><previous-page>move the previous page
+<Home><top>move to the top
+<End><bottom>move to the bottom
+
+
+

+
 
 
 
@@ -395,7 +556,7 @@ short descriptions.
 
 
 You can remap the editor functions using the
-bind command.  For example, to make
+bind command.  For example, to make
 the <Delete> key delete the character in front of
 the cursor rather than under, you could use:
 
@@ -416,7 +577,9 @@ variable and can be made persistent using an external file specified
 using $history_file.
 You may cycle through them at an editor prompt by using the
 <history-up> and/or
-<history-down> commands.
+<history-down> commands. But notice that Mutt
+does not remember the currently entered text, it only cycles through
+history and wraps around at the end or beginning.
 
 
 
@@ -425,7 +588,7 @@ following categories:
 
 
 
-muttrc commands
+.muttrc commands
 addresses and aliases
 shell commands
 filenames
@@ -434,7 +597,7 @@ following categories:
 
 
 
-Mutt automatically filters out repeated items from the history.  It
+Mutt automatically filters out consecutively repeated items from the history. It
 also mimics the behavior of some shells by ignoring items starting
 with a space. The latter feature can be useful in macros to not clobber
 the history's valuable entries with unwanted entries.
@@ -445,12 +608,12 @@ the history's valuable entries with unwanted entries.
 
 
 
-Reading Mail - The Index and Pager
+Reading Mail
 
 
 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 of the
+read in Mutt.  The first is a list of messages in the mailbox, which is
+called the index menu in Mutt.  The second mode is the display of the
 message contents.  This is called the pager.
 
 
@@ -569,9 +732,11 @@ who the message is addressed to. They can be customized with the
 The Pager
 
 
-By default, Mutt uses its builtin pager to display the contents of messages.
-The pager is very similar to the Unix program less though not nearly as
-featureful.
+By default, Mutt uses its builtin pager to display the contents of
+messages (an external pager such as less(1) can be
+configured, see $pager variable).
+The pager is very similar to the Unix program less(1)
+though not nearly as featureful.
 
 
 
@@ -607,11 +772,11 @@ the pager, such as <delete-message> or <cop
 Also, the internal pager supports a couple other advanced features. For
 one, it will accept and translate the standard nroff sequences for
 bold and underline. These sequences are a series of either the letter,
-backspace (ˆH), the letter again for bold or the letter, backspace,
+backspace (ˆH), the letter again for bold or the letter, backspace,
 _ for denoting underline. Mutt will attempt to display these
 in bold and underline respectively if your terminal supports them. If
 not, you can use the bold and underline color
-objects to specify a color or mono attribute for them.
+objects to specify a color or mono attribute for them.
 
 
 
@@ -686,9 +851,8 @@ your xterm, then that color will be used instead of green.
 Note that the search commands in the pager take regular expressions,
 which are not quite the same as the more
 complex patterns used by the search
-command in the index. This is because the pager only performs simple
-text search, whereas the index provides boolean filtering on several
-aspects of messages.
+command in the index. This is because patterns are used to select messages by
+criteria whereas the pager already displays a selected message.
 
 
 
@@ -698,9 +862,18 @@ aspects of messages.
 Threaded Mode
 
 
-When the mailbox is sorted by threads, there are
-a few additional functions available in the index and pager modes
-as shown in .
+So-called threads provide a hierarchy of messages where
+replies are linked to their parent message(s). This organizational form
+is extremely useful in mailing lists where different parts of the
+discussion diverge. Mutt displays threads as a tree structure.
+
+
+
+In Mutt, when a mailbox is sorted
+by threads, there are a few additional functions
+available in the index
+and pager modes as shown in
+.
 
 
 

@@ -728,19 +901,23 @@ as shown in .
 
 

 
-
 
 Collapsing a thread displays only the first message
 in the thread and hides the others. This is useful when threads
 contain so many messages that you can only see a handful of threads on
 the screen. See %M in $index_format.
-For example, you could use "%?M?(#%03M)&(%4l)?" in $index_format to optionally
-display the number of hidden messages if the thread is collapsed.
+For example, you could use %?M?(#%03M)&(%4l)? in $index_format to optionally
+display the number of hidden messages if the thread is
+collapsed. The %?<char>?<if-part>&<else-part>?
+syntax is explained in detail in
+format string conditionals.
 
-
 
 
-See also: $strict_threads.
+Technically, every reply should contain a list of its parent messages in
+the thread tree, but not all do. In these cases, Mutt groups them by
+subject which can be controlled using the
+$strict_threads variable.
 
 
 
@@ -762,7 +939,7 @@ menus have these interesting functions:
 
 
 Creates a new alias based upon the current message (or prompts for a
-new one).  Once editing is complete, an alias
+new one).  Once editing is complete, an alias
 command is added to the file specified by
 the $alias_file variable
 for future use
@@ -771,7 +948,7 @@ for future use
 
 
 Mutt does not read the $alias_file
-upon startup so you must explicitly source the file.
+upon startup so you must explicitly source the file.
 
 
 
@@ -879,7 +1056,7 @@ you misspelled the passphrase.
 
 
 Reply to the current or tagged message(s) by extracting any addresses which
-match the regular expressions given by the lists or subscribe
+match the regular expressions given by the lists or subscribe
 commands, but also honor any Mail-Followup-To header(s) if the
 $honor_followup_to
 configuration variable is set.  Using this when replying to messages posted
@@ -1005,36 +1182,77 @@ The bindings shown in  are available in the
 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.  These items are discussed
-in greater detail in the next chapter Forwarding
+in greater detail in the next section Forwarding
 and Bouncing Mail.
 
 
 
 Mutt will then enter the compose menu and prompt you for the
-recipients to place on the To: header field.  Next, it will ask
+recipients to place on the To: header field when you hit m to start a new message. Next, it will ask
 you for the Subject: field for the message, providing a default if
-you are replying to or forwarding a message.  See also
+you are replying to or forwarding a message. You again
+have the chance to adjust recipients, subject, and security settings
+right before actually sending the message. See also
 $askcc,
 $askbcc,
 $autoedit,
 $bounce,
 $fast_reply,
 and $include
-for changing how Mutt asks these questions.
+for changing how and if Mutt asks these questions.
+
+
+
+When replying, Mutt fills these fields with proper values depending on
+the reply type.  The types of replying supported are:
+
+
+
+
+Simple reply
+
+
+Reply to the author directly.
+
+
+
+
+Group reply
+
+
+Reply to the author as well to all recipients except you; this consults
+alternates.
+
+
+
+
+List reply
+
+
+Reply to all mailing list addresses found, either specified via
+configuration or auto-detected.  See  for
+details.
 
+
+
+
 
 
-Mutt will then automatically start your $editor
-on the message body. If the $edit_headers
-variable is set, the headers will be at the top of the message in your editor.
-Any messages you are replying to will be added in sort order to the message,
+After getting recipients for new messages, forwards or replies, Mutt
+will then automatically start your $editor on the message body. If the $edit_headers variable is
+set, the headers will be at the top of the message in your editor.  Any
+messages you are replying to will be added in sort order to the message,
 with appropriate $attribution,
 $indent_string and
-$post_indent_string.
-When forwarding a message, if the $mime_forward
-variable is unset, a copy of the forwarded message will be included.  If
-you have specified a $signature, it
-will be appended to the message.
+$post_indent_string.
+When forwarding a message, if the $mime_forward variable is
+unset, a copy of the forwarded message will be included.  If you have
+specified a $signature, it will
+be appended to the message.
 
 
 
@@ -1095,44 +1313,56 @@ a A to indicate that you are in attach-message mode.
 
 
 
-Editing the message header
+Editing the Message Header
 
 
 When editing the header because of $edit_headers
 being set, there are a several pseudo headers available which
-will not be included in sent messages.
+will not be included in sent messages but trigger special Mutt behavior.
 
 
 
-Fcc: pseudo header
+Fcc: Pseudo Header
 
 
 If you specify
+
 
+
 Fcc: filename
+
 
+
 as a header, Mutt will pick up filename
 just as if you had used the <edit-fcc> function in the compose menu.
+It can later be changed from the compose menu.
 
 
 
 
 
-Attach: pseudo header
+Attach: Pseudo Header
 
 
 You can also attach files to your message by specifying
+
 
-Attach: filename  [ description ]
+
+Attach: filename
+[ description ]
+
 
+
 where filename is the file to attach and description is an
-optional string to use as the description of the attached file.
+optional string to use as the description of the attached file. Spaces
+in filenames have to be escaped using backslash (\).
+The file can be removed as well as more added from the compose menu.
 
 
 
 
 
-Pgp: pseudo header
+Pgp: Pseudo Header
 
 
 If you want to use PGP, you can specify
@@ -1147,17 +1377,17 @@ If you want to use PGP, you can specify
 E selects encryption, S selects signing and
 S<id> selects signing with the given key, setting
 $pgp_sign_as
-permanently.
+permanently. The selection can later be changed in the compose menu.
 
 
 
 
 
-In-Reply-To: header
+In-Reply-To: Header
 
 
 When replying to messages, the In-Reply-To: header contains the
-Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a
+Message-Id of the message(s) you reply to. If you remove or modify its value, Mutt will not generate a
 References: field, which allows you to create a new message thread, for example
 to create a new message to a mailing list without having to enter the mailing list's address.
 
@@ -1167,10 +1397,10 @@ to create a new message to a mailing list without having to enter the mailing li
 
 
 
-Sending cryptographically signed/encrypted messages
+Sending Cryptographically Signed/Encrypted Messages
 
 
-If you have told mutt to PGP or S/MIME encrypt a message, it will guide you
+If you have told Mutt to PGP or S/MIME encrypt a message, it will guide you
 through a key selection process when you try to send the message.
 Mutt will not ask you any questions about keys which have a
 certified user ID matching one of the message recipients' mail
@@ -1181,9 +1411,9 @@ keys can be found.
 
 
 In these cases, you are dropped into a menu with a list of keys from
-which you can select one.  When you quit this menu, or mutt can't
+which you can select one.  When you quit this menu, or Mutt can't
 find any matching keys, you are prompted for a user ID.  You can, as
-usually, abort this prompt using ˆG.  When you do so, mutt will
+usually, abort this prompt using ˆG.  When you do so, Mutt will
 return to the compose screen.
 
 
@@ -1199,7 +1429,7 @@ and validity fields are in order.
 
 
 
-The flags sequence (%f) will expand to one of the flags in
+The flags sequence (%f) will expand to one of the flags in
 .
 
 
@@ -1219,7 +1449,7 @@ The flags sequence (%f) will expand to one of the flags in
 
 
 
-The capabilities field (%c) expands to a two-character sequence
+The capabilities field (%c) expands to a two-character sequence
 representing a key's capabilities.  The first character gives
 the key's encryption capabilities: A minus sign (-) means
 that the key cannot be used for encryption.  A dot (.) means that
@@ -1236,7 +1466,7 @@ that the key is marked as an encryption key in one of the user-ids, and
 
 
 
-Finally, the validity field (%t) indicates how well-certified a user-id
+Finally, the validity field (%t) indicates how well-certified a user-id
 is.  A question mark (?) indicates undefined validity, a minus
 character (-) marks an untrusted association, a space character
 means a partially trusted association, and a plus character (+)
@@ -1245,58 +1475,8 @@ indicates complete validity.
 
 
 
-
-Sending anonymous messages via mixmaster
-
-
-You may also have compiled mutt to co-operate with Mixmaster, an
-anonymous remailer.  Mixmaster permits you to send your messages
-anonymously using a chain of remailers. Mixmaster support in mutt is for
-mixmaster version 2.04 (beta 45 appears to be the latest) and 2.03.
-It does not support earlier versions or the later so-called version 3 betas,
-of which the latest appears to be called 2.9b23.
-
-
-
-To use it, you'll have to obey certain restrictions.  Most
-important, you cannot use the Cc and Bcc headers.  To tell
-Mutt to use mixmaster, you have to select a remailer chain, using
-the mix function on the compose menu.
-
-
-
-The chain selection screen is divided into two parts.  In the
-(larger) upper part, you get a list of remailers you may use.  In
-the lower part, you see the currently selected chain of remailers.
-
-
-
-You can navigate in the chain using the <chain-prev> and
-<chain-next> functions, which are by default bound to the left
-and right arrows and to the h and l keys (think vi
-keyboard bindings).  To insert a remailer at the current chain
-position, use the <insert> function.  To append a remailer behind
-the current chain position, use <select-entry> or <append>.
-You can also delete entries from the chain, using the corresponding
-function.  Finally, to abandon your changes, leave the menu, or
-<accept> them pressing (by default) the Return key.
-
-
-
-Note that different remailers do have different capabilities,
-indicated in the %c entry of the remailer menu lines (see
-$mix_entry_format).  Most important is
-the middleman capability, indicated by a capital M: This
-means that the remailer in question cannot be used as the final
-element of a chain, but will only forward messages to other
-mixmaster remailers.  For details on the other capabilities, please
-have a look at the mixmaster documentation.
-
-
-
-
 
-Sending format=flowed messages
+Sending Format=Flowed Messages
 
 
 Concept
@@ -1311,7 +1491,7 @@ except for the last line.
 
 
 
-While for text-mode clients like mutt it's the best way to assume only a
+While for text-mode clients like Mutt it's the best way to assume only a
 standard 80x25 character cell terminal, it may be desired to let the
 receiver decide completely how to view a message.
 
@@ -1319,7 +1499,7 @@ receiver decide completely how to view a message.
 
 
 
-Mutt support
+Mutt Support
 
 
 Mutt only supports setting the required format=flowed
@@ -1331,7 +1511,7 @@ trailing spaces.
 
 
 After editing the initial message text and before entering
-the compose menu, mutt properly space-stuffes the message.
+the compose menu, Mutt properly space-stuffes the message.
 Space-stuffing is required by RfC3676 defining
 format=flowed and means to prepend a space to:
 
@@ -1362,10 +1542,10 @@ the original message prior to further processing.
 
 
 
-Editor considerations
+Editor Considerations
 
 
-As mutt provides no additional features to compose f=f
+As Mutt provides no additional features to compose f=f
 messages, it's completely up to the user and his editor to produce
 proper messages. Please consider your editor's documentation if you
 intend to send f=f messages.
@@ -1411,7 +1591,7 @@ message's body (surrounded by indicating lines) or including it as a MIME
 attachment, depending on the value of the $mime_forward variable.  Decoding of attachments,
 like in the pager, can be controlled by the $forward_decode and $mime_forward_decode variables,
 respectively.  The desired forwarding format may depend on the content,
-therefore $mime_forward is a quadoption which, for
+therefore $mime_forward is a quadoption which, for
 example, can be set to ask-no.
 
 
@@ -1468,7 +1648,7 @@ See also the $postpone quad-option.
 Configuration
 
 
-Location of initialization files
+Location of Initialization Files
 
 
 While the default configuration (or preferences) make Mutt
@@ -1479,7 +1659,7 @@ system administrator), unless the -n 
 /usr/local/share/mutt/Muttrc or /etc/Muttrc. Mutt
 will next look for a file named .muttrc in your home
 directory.  If this file does not exist and your home directory has
-a subdirectory named .mutt, mutt try to load a file named
+a subdirectory named .mutt, Mutt tries to load a file named
 .mutt/muttrc.
 
 
@@ -1488,13 +1668,13 @@ a subdirectory named .mutt, mutt try to load a file named
 
 
 
-In addition, mutt supports version specific configuration files that are
+In addition, Mutt supports version specific configuration files that are
 parsed instead of the default files as explained above.  For instance, if
 your system has a Muttrc-0.88 file in the system configuration
-directory, and you are running version 0.88 of mutt, this file will be
+directory, and you are running version 0.88 of Mutt, this file will be
 sourced instead of the Muttrc file.  The same is true of the user
 configuration file, if you have a file .muttrc-0.88.6 in your home
-directory, when you run mutt version 0.88.6, it will source this file
+directory, when you run Mutt version 0.88.6, it will source this file
 instead of the default .muttrc file.  The version 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.
@@ -1508,7 +1688,7 @@ V) from the index menu.
 
 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
-(;).
+(;).
 
 
 
@@ -1522,7 +1702,7 @@ set realname='Mutt user' ; ignore x-
 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,
+to the end of the line is ignored.
 
 
 
@@ -1533,18 +1713,18 @@ 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
+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 shell programs,
 namely that a single quote is used to specify a literal string (one that is
 not interpreted for shell variables or quoting with a backslash [see
 next paragraph]), while double quotes indicate a string for which
 should be evaluated.  For example, backticks are evaluated inside of double
-quotes, but not for single quotes.
+quotes, but not for single quotes.
 
 
 
-\ quotes the next character, just as in shells such as bash and zsh.
+\ quotes the next character, just as in shells such as bash and zsh.
 For example, if want to put quotes " inside of a string, you can use
 \ to force the next character to be a literal instead of interpreted
 character.
@@ -1564,15 +1744,30 @@ carriage-return, respectively.
 
 
 
-A \ at the end of a line can be used to split commands over
-multiple lines, provided that the split points don't appear in the
-middle of command names.
+A \ at the end of a line can be used to split commands over
+multiple lines as it escapes the line end, provided that the split points don't appear in the
+middle of command names. Lines are first concatenated before
+interpretation so that a multi-line can be commented by commenting out
+the first line only.
 
 
+
+Splitting long configuration commands over several lines
+
+set status_format="some very \
+long value split \
+over several lines"
+
+
+
 
 It is also possible to substitute the output of a Unix command in an
 initialization file.  This is accomplished by enclosing the command in
-backticks (``).  For example,
+backticks (``). In , the output of the
+Unix command uname -a will be substituted before the
+line is parsed.
+Since initialization files are line oriented, only
+the first line of output from the Unix command will be substituted.
 
 
 
@@ -1583,19 +1778,7 @@ my_hdr X-Operating-System: `uname -a`
 
 
 
-The output of the Unix command uname -a will be substituted before the
-line is parsed.
-
-
-
-
-Since initialization files are line oriented, only
-the first line of output from the Unix command will be substituted.
-
-
-
-
-Both environment variables and mutt variables can be accessed by
+Both environment variables and Mutt variables can be accessed by
 prepending $ to the name of the variable. For example,
 
 
@@ -1607,8 +1790,8 @@ set record=+sent_on_$HOSTNAME
 
 
 
-will cause mutt to save outgoing messages to a folder named
-sent_on_kremvax if the environment variable HOSTNAME is set to
+will cause Mutt to save outgoing messages to a folder named
+sent_on_kremvax if the environment variable $HOSTNAME is set to
 kremvax. (See $record for
 details.)
 
@@ -1621,7 +1804,7 @@ not be affected.
 
 
 
-The commands understood by mutt are explained in the next paragraphs.
+The commands understood by Mutt are explained in the next paragraphs.
 For a complete list, see the command reference.
 
 
@@ -1632,7 +1815,8 @@ which doesn't have a default value since it's determined by Mutt at startup.
 If a configuration file is not encoded in the same character set the
 $config_charset
 variable should be used: all lines starting with the next are recoded
-from $config_charset to $charset.
+from $config_charset
+to $charset.
 
 
 
@@ -1643,10 +1827,11 @@ following implications:
 
 
 These variables should be set early in a configuration
-file with $charset preceding $config_charset so Mutt
-know what character set to convert to.
+file with $charset preceding
+$config_charset so Mutt
+knows what character set to convert to.
 
-If $config_charset is set, it should be set
+If $config_charset is set, it should be set
 in each configuration file because the value is global and not
 per configuration file.
 
@@ -1661,7 +1846,7 @@ question marks into regular expressions).
 
 
 
-Address groups
+Address Groups
 
 Usage:
 
@@ -1681,9 +1866,7 @@ question marks into regular expressions).
 expr
 
 
-
 
-
 ungroup
 
 
@@ -1705,9 +1888,9 @@ question marks into regular expressions).
 
 
 
-group is used to directly add either addresses or
+group is used to directly add either addresses or
 regular expressions to the specified group or groups. The different
-categories of arguments to the group command can be
+categories of arguments to the group command can be
 in any order. The flags -rx and
 -addr specify what the following strings (that cannot
 begin with a hyphen) should be interpreted as: either a regular
@@ -1716,9 +1899,9 @@ expression or an email address, respectively.
 
 
 These address groups can also be created implicitly by the
-alias, lists,
+alias, lists,
 subscribe and
-alternates commands by specifying the
+alternates commands by specifying the
 optional -group option.
 
 
@@ -1729,9 +1912,9 @@ display to messages matching a group.
 
 
 
-ungroup is used to remove addresses or regular
+ungroup is used to remove addresses or regular
 expressions from the specified group or groups. The syntax is similar to
-the group command, however the special character
+the group command, however the special character
 * can be used to empty a group of all of its
 contents.
 
@@ -1739,7 +1922,7 @@ contents.
 
 
 
-Defining/Using aliases
+Defining/Using Aliases
 
 Usage:
 
@@ -1758,6 +1941,20 @@ contents.
 
 address
 
+
+unalias
+
+
+name
+
+
+
+*
+
+
+key
+
+
 
 
 
@@ -1769,13 +1966,13 @@ a short string to a full address.
 
 
 If you want to create an alias for more than
-one address, you must separate the addresses with a comma (,).
+one address, you must separate the addresses with a comma (,).
 
 
 
 
 The optional -group argument to
-alias causes the aliased address(es) to be added to
+alias causes the aliased address(es) to be added to
 the named group.
 
 
@@ -1783,22 +1980,6 @@ the named group.
 To remove an alias or aliases (* means all aliases):
 
 
-
-unalias
-
-
-name
-
-
-
-*
-
-
-key
-
-
-
-
 
 alias muttdude me@cs.hmc.edu (Michael Elkins)
 alias theguys manny, moe, jack
@@ -1806,9 +1987,9 @@ 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.  Consequently, you can have multiple alias files, or
-you can have all aliases defined in your muttrc.
+in a special file.  The alias command can appear anywhere in
+a configuration file, as long as this file is sourced.  Consequently, you can have multiple alias files, or
+you can have all aliases defined in your .muttrc.
 
 
 
@@ -1816,11 +1997,7 @@ On the other hand, the <create-alias>
 function can use only one file, the one pointed to by the $alias_file variable (which is
 ˜/.muttrc by default). This file is not special either,
 in the sense that Mutt will happily append aliases to any file, but in
-order for the new aliases to take effect you need to explicitly source this file too.
-
-
-
-For example:
+order for the new aliases to take effect you need to explicitly source this file too.
 
 
 
@@ -1833,7 +2010,7 @@ set alias_file=~/.mail_aliases
 
 
 
-To use aliases, you merely use the alias at any place in mutt where mutt
+To use aliases, you merely use the alias at any place in Mutt where Mutt
 prompts for addresses, such as the To: or Cc: prompt.  You can
 also enter aliases in your editor at the appropriate headers if you have the
 $edit_headers variable set.
@@ -1842,8 +2019,8 @@ also enter aliases in your editor at the appropriate headers if you have the
 
 In addition, at the various address prompts, you can use the tab character
 to expand a partial alias to the full alias.  If there are multiple matches,
-mutt will bring up a menu with the matching aliases.  In order to be
-presented with the full list of aliases, you must hit tab with out a partial
+Mutt will bring up a menu with the matching aliases.  In order to be
+presented with the full list of aliases, you must hit tab without a partial
 alias, such as at the beginning of the prompt or after a comma denoting
 multiple addresses.
 
@@ -1857,7 +2034,7 @@ In the alias menu, you can select as many aliases as you want with the
 
 
 
-Changing the default key bindings
+Changing the Default Key Bindings
 
 Usage:
 
@@ -1896,7 +2073,7 @@ This is not a real menu, but is used as a fallback for all of the other
 menus except for the pager and editor modes.  If a key is not defined in
 another menu, Mutt will look for a binding to use in this menu.  This allows
 you to bind a key to a certain function in multiple menus instead of having
-multiple bind statements to accomplish the same task.
+multiple bind statements to accomplish the same task.
 
 
 
@@ -1905,7 +2082,7 @@ multiple bind statements to accomplish the same task.
 
 
 The alias menu is the list of your personal aliases as defined in your
-muttrc.  It is the mapping from a short alias name to the full email
+.muttrc.  It is the mapping from a short alias name to the full email
 address(es) of the recipient(s).
 
 
@@ -2067,7 +2244,7 @@ sequence.
 
 
 
-Defining aliases for character sets 
+Defining Aliases for Character Sets
 
 Usage:
 
@@ -2079,10 +2256,8 @@ sequence.
 
 charset
 
-
 
-
-iconv-hook
+iconv-hook
 
 charset
 
@@ -2092,13 +2267,13 @@ sequence.
 
 
 
-The charset-hook command defines an alias for a character set.
+The charset-hook command defines an alias for a character set.
 This is useful to properly display messages which are tagged with a
-character set name not known to mutt.
+character set name not known to Mutt.
 
 
 
-The iconv-hook command defines a system-specific name for a
+The iconv-hook command defines a system-specific name for a
 character set.  This is helpful when your systems character
 conversion library insists on using strange, system-specific names
 for character sets.
@@ -2107,7 +2282,7 @@ for character sets.
 
 
 
-Setting variables based upon mailbox
+Setting Variables Based Upon Mailbox
 
 Usage:
 
@@ -2123,11 +2298,11 @@ for character sets.
 
 
 It is often desirable to change settings based on which mailbox you are
-reading.  The folder-hook command provides a method by which you can execute
+reading.  The folder-hook command provides a method by which you can execute
 any configuration command.  regexp is a regular expression specifying
 in which mailboxes to execute command before loading.  If a mailbox
-matches multiple folder-hook's, they are executed in the order given in the
-muttrc.
+matches multiple folder-hooks, they are executed in the order given in the
+.muttrc.
 
 
 
@@ -2143,18 +2318,19 @@ logical not operator for the expression.
 Settings are not restored when you leave the mailbox.
 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
-
+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 default command, use the
-pattern . before other folder-hooks adjusting a value on a per-folder basis
-because folder-hooks are evaluated in the order given in the configuration file.
+pattern . before other folder-hooks adjusting a value on a per-folder basis
+because folder-hooks are evaluated in the order given in the
+configuration file.
+
+
+
+
 The following example will set the sort variable
 to date-sent for all folders but to threads
 for all folders containing mutt in their name.
@@ -2163,15 +2339,15 @@ for all folders containing mutt in their name.
 
 Setting sort method based on mailbox name
 
-folder-hook . set sort=date-sent
-folder-hook mutt set sort=threads
+folder-hook . "set sort=date-sent"
+folder-hook mutt "set sort=threads"
 
 
 
 
 
 
-Keyboard macros
+Keyboard Macros
 
 Usage:
 
@@ -2228,7 +2404,7 @@ than one user (e.g., the system Muttrc).
 
 
 Optionally you can specify a descriptive text after sequence,
-which is shown in the help screens.
+which is shown in the help screens if they contain a description.
 
 
 
@@ -2241,7 +2417,7 @@ silently truncated at the screen width, and are not wrapped.
 
 
 
-Using color and mono video attributes
+Using Color and Mono Video Attributes
 
 Usage:
 
@@ -2256,9 +2432,7 @@ silently truncated at the screen width, and are not wrapped.
 
 background
 
-
 
-
 color
 
 
@@ -2277,9 +2451,7 @@ silently truncated at the screen width, and are not wrapped.
 
 regexp
 
-
 
-
 color
 
 
@@ -2293,13 +2465,19 @@ silently truncated at the screen width, and are not wrapped.
 
 pattern
 
-
 
-
 uncolor
+
 
 
 
+
+
+
+
+
+
+
 
 
 *
@@ -2313,7 +2491,7 @@ silently truncated at the screen width, and are not wrapped.
 
 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 information), you
-must specify both a foreground color and a background color (it is not
+must specify both a foreground color and a background color (it is not
 possible to only specify one or the other).
 
 
@@ -2337,7 +2515,7 @@ in the header/body of a message, index matches pa
 message (informational messages)
 normal
 quoted (text matching $quote_regexp in the body of a message)
-quoted1, quoted2, ..., quotedN (higher levels of quoting)
+quoted1, quoted2, ..., quotedN (higher levels of quoting)
 search (hiliting of words in the pager)
 signaturestatus (mode lines used to display info about the mailbox or message)
 tilde (the ˜ used to pad blank lines in the pager)
@@ -2372,7 +2550,7 @@ the foreground color boldfaced (e.g., brightred).
 If your terminal supports it, the special keyword default can be
 used as a transparent color.  The value brightdefault is also valid.
 If Mutt is linked against the S-Lang library, you also need to set
-the COLORFGBG environment variable to the default colors of your
+the $COLORFGBG environment variable to the default colors of your
 terminal for this to work; for example (for Bourne-like shells):
 
 
@@ -2391,29 +2569,27 @@ setting this variable.
 
 
 
-The uncolor command can be applied to the index object only.  It
-removes entries from the list. You must 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.
+The uncolor command can be applied to the index, header and body objects only.  It
+removes entries from the list. You must 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 list of all entries.
 
 
 
 
 Mutt also recognizes the keywords color0, color1, …,
-colorN-1 (N being the number of colors supported
+colorN-1 (N being the number of colors supported
 by your terminal).  This is useful when you remap the colors for your
 display (for example by changing the color associated with color2
 for your xterm), since color names may then lose their normal meaning.
 
 
+
 
 If your terminal does not support color, it is still possible change the video
-attributes through the use of the mono command:
+attributes through the use of the mono command. Usage:
 
 
-
-Usage:
-
 
 mono
 
@@ -2422,9 +2598,7 @@ attributes through the use of the mono command:
 
 attribute
 
-
 
-
 mono
 
 
@@ -2440,9 +2614,7 @@ attributes through the use of the mono command:
 
 regexp
 
-
 
-
 mono
 
 
@@ -2453,13 +2625,19 @@ attributes through the use of the mono command:
 
 pattern
 
-
 
-
 unmono
+
 
 
 
+
+
+
+
+
+
+
 
 
 *
@@ -2471,7 +2649,7 @@ attributes through the use of the mono command:
 
 
 
-For object, see the color command. attribute
+For object, see the color command. attribute
 can be one of the following:
 
 
@@ -2485,8 +2663,11 @@ can be one of the following:
 
 
 
-
-Message header display
+
+Message Header Display
+
+
+Selecting Headers
 
 Usage:
 
@@ -2498,9 +2679,7 @@ can be one of the following:
 
 pattern
 
-
 
-
 unignore
 
 
@@ -2534,10 +2713,6 @@ For example, if you do ignore x- it is possible to unignor
 unignore * will remove all tokens from the ignore list.
 
 
-
-For example:
-
-
 
 Header weeding
 
@@ -2549,8 +2724,12 @@ unignore posted-to:
 
 
 
-
-Usage:
+
+
+
+Ordering Displayed Headers
+
+Usage:
 
 
 hdr_order
@@ -2560,9 +2739,7 @@ unignore posted-to:
 
 header
 
-
 
-
 unhdr_order
 
 
@@ -2575,12 +2752,12 @@ unignore posted-to:
 
 
 
-With the hdr_order command you can specify an order in
-which mutt will attempt to present these headers to you when viewing messages.
+With the hdr_order command you can specify an order in
+which Mutt will attempt to present these headers to you when viewing messages.
 
 
 
-unhdr_order * will clear all previous headers from the order list,
+unhdr_order * will clear all previous headers from the order list,
 thus removing the header order effects set by the system-wide startup file.
 
 
@@ -2591,10 +2768,11 @@ hdr_order From Date: From: To: Cc: Subject:
 
 
 
+
 
 
 
-Alternative addresses
+Alternative Addresses
 
 Usage:
 
@@ -2610,9 +2788,7 @@ hdr_order From Date: From: To: Cc: Subject:
 
 regexp
 
-
 
-
 unalternates
 
 
@@ -2629,19 +2805,19 @@ hdr_order From Date: From: To: Cc: Subject:
 
 
 
-With various functions, mutt will treat messages differently,
+With various functions, Mutt will treat messages differently,
 depending on whether you sent them or whether you received them from
 someone else.  For instance, when replying to a message that you
-sent to a different party, mutt will automatically suggest to send
-the response to the original message's recipients -- responding to
+sent to a different party, Mutt will automatically suggest to send
+the response to the original message's recipients — responding to
 yourself won't make much sense in many cases.  (See $reply_to.)
 
 
 
 Many users receive e-mail under a number of different addresses. To
-fully use mutt's features here, the program must be able to
+fully use Mutt's features here, the program must be able to
 recognize what e-mail addresses you receive mail under. That's the
-purpose of the alternates command: It takes a list of regular
+purpose of the alternates command: It takes a list of regular
 expressions, each of which can identify an address under which you
 receive e-mail.
 
@@ -2657,7 +2833,7 @@ alternates user@example
 
 
 
-mutt will consider some-user@example as
+Mutt will consider some-user@example as
 being your address, too which may not be desired. As a solution, in such
 cases addresses should be specified as:
 
@@ -2672,26 +2848,26 @@ to be added to the named group.
 
 
 
-The unalternates command can be used to write exceptions to
-alternates patterns. If an address matches something in an
-alternates command, but you nonetheless do not think it is
-from you, you can list a more precise pattern under an unalternates
+The unalternates command can be used to write exceptions to
+alternates patterns. If an address matches something in an
+alternates command, but you nonetheless do not think it is
+from you, you can list a more precise pattern under an unalternates
 command.
 
 
 
-To remove a regular expression from the alternates list, use the
-unalternates command with exactly the same regexp.
-Likewise, if the regexp for an alternates command matches
-an entry on the unalternates list, that unalternates
-entry will be removed. If the regexp for unalternates
-is *, all entries on alternates will be removed.
+To remove a regular expression from the alternates list, use the
+unalternates command with exactly the same regexp.
+Likewise, if the regexp for an alternates command matches
+an entry on the unalternates list, that unalternates
+entry will be removed. If the regexp for unalternates
+is *, all entries on alternates will be removed.
 
 
 
 
 
-Mailing lists
+Mailing Lists
 
 
 Usage:
@@ -2708,9 +2884,7 @@ is *, all entries on alternates
 regexp
 
-
 
-
 unlists
 
 
@@ -2724,9 +2898,7 @@ is *, all entries on alternatesregexp
 
 
-
 
-
 subscribe
 
 
@@ -2738,9 +2910,7 @@ is *, all entries on alternates
 regexp
 
-
 
-
 unsubscribe
 
 
@@ -2759,8 +2929,15 @@ is *, all entries on alternates
 Mutt has a few nice features for handling mailing lists.  In order to take advantage of them, you must
 specify which addresses belong to mailing lists, and which mailing
-lists you are subscribed to.  Once you have done this, the <list-reply> function will work for all known lists.
-Additionally, when you send a message to a subscribed list, mutt will
+lists you are subscribed to. Mutt also has limited support for
+auto-detecting mailing lists: it supports parsing
+mailto: links in the common
+List-Post: header which has the same effect as
+specifying the list address via the lists command
+(except the group feature). Once you have done this, the
+<list-reply>
+function will work for all known lists.
+Additionally, when you send a message to a subscribed list, Mutt will
 add a Mail-Followup-To header to tell other users' mail user agents
 not to send copies of replies to your personal address.
 
@@ -2772,36 +2949,42 @@ supported by all mail user agents.  Adding it is not bullet-proof against
 receiving personal CCs of list messages.  Also note that the generation
 of the Mail-Followup-To header is controlled by the
 $followup_to
-configuration variable.
+configuration variable since it's common practice on some mailing lists
+to send Cc upons replies (which is more a group- than a list-reply).
 
 
 
 
 More precisely, Mutt maintains lists of patterns for the addresses
 of known and subscribed mailing lists.  Every subscribed mailing
-list is known. To mark a mailing list as known, use the lists
-command.  To mark it as subscribed, use subscribe.
+list is known. To mark a mailing list as known, use the list
+command.  To mark it as subscribed, use subscribe.
 
 
 
-You can use regular expressions with both commands.  To mark all
-messages sent to a specific bug report's address on mutt's bug
+You can use regular expressions with both commands. To mark all
+messages sent to a specific bug report's address on Debian's bug
 tracking system as list mail, for instance, you could say
-subscribe [0-9]*@bugs.guug.de.  Often, it's sufficient to just
-give a portion of the list's e-mail address.
+
+
+
+subscribe [0-9]*.*@bugs.debian.org
+
+
+as it's often, it's sufficient to just give a portion of the list's e-mail address.
 
 
 
 Specify as much of the address as you need to to remove ambiguity.  For
 example, if you've subscribed to the Mutt mailing list, you will receive mail
-addressed to mutt-users@mutt.org.  So, to tell Mutt
-that this is a mailing list, you could add lists mutt-users@ to your
-initialization file.  To tell mutt that you are subscribed to it,
-add subscribe mutt-users to your initialization file instead.
+addressed to mutt-users@mutt.org.  So, to tell Mutt
+that this is a mailing list, you could add lists mutt-users@ to your
+initialization file.  To tell Mutt that you are subscribed to it,
+add subscribe mutt-users to your initialization file instead.
 If you also happen to get mail from someone whose address is
-mutt-users@example.com, you could use
-lists ^mutt-users@mutt\\.org$
-or subscribe ^mutt-users@mutt\\.org$ to
+mutt-users@example.com, you could use
+lists ^mutt-users@mutt\\.org$
+or subscribe ^mutt-users@mutt\\.org$ to
 match only mail from the actual list.
 
 
@@ -2818,13 +3001,13 @@ tokens.
 
 
 To remove a mailing list from the list of subscribed mailing lists,
-but keep it on the list of known mailing lists, use unsubscribe.
+but keep it on the list of known mailing lists, use unsubscribe.
 
 
 
 
 
-Using Multiple spool mailboxes
+Using Multiple Spool Mailboxes
 
 Usage:
 
@@ -2855,7 +3038,7 @@ mailbox).
 
 
 
-Monitoring incoming mail
+Monitoring Incoming Mail
 
 Usage:
 
@@ -2867,9 +3050,7 @@ mailbox).
 
 mailbox
 
-
 
-
 unmailboxes
 
 
@@ -2910,13 +3091,13 @@ tokens.
 
 
 
-The folders in the mailboxes command are resolved when
+The folders 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 affects these characters (like $folder and $spoolfile)
-should be set before the mailboxes command. If
+should be set before the mailboxes command. If
 none of these shorcuts are used, a local path should be absolute as
-otherwise mutt tries to find it relative to the directory
-from where mutt was started which may not always be desired.
+otherwise Mutt tries to find it relative to the directory
+from where Mutt was started which may not always be desired.
 
 
 
@@ -2936,13 +3117,13 @@ In cases where new mail detection for Mbox or Mmdf folders appears to be
 unreliable, the
 $check_mbox_size
 option can be used to make Mutt track and consult file sizes for new
-mail detection instead.
+mail detection instead which won't work for size-neutral changes.
 
 
 
 
 
-User defined headers
+User-Defined Headers
 
 Usage:
 
@@ -2951,9 +3132,7 @@ mail detection instead.
 
 string
 
-
 
-
 unmy_hdr
 
 
@@ -2966,13 +3145,15 @@ mail detection instead.
 
 
 
-The my_hdr command allows you to create your own header
-fields which will be added to every message you send.
+The my_hdr command allows you to create your own header
+fields which will be added to every message you send and appear in the
+editor if $edit_headers is set.
 
 
 
 For example, if you would like to add an Organization: header field to
-all of your outgoing messages, you can put the command
+all of your outgoing messages, you can put the command something like
+shown in  in your .muttrc.
 
 
 
@@ -2982,10 +3163,6 @@ my_hdr Organization: A Really Big Company, Anytown, USA
 
 
 
-
-in your .muttrc.
-
-
 
 
 Space characters are not allowed between the keyword and
@@ -3002,7 +3179,7 @@ that you can edit the header of your message along with the body.
 
 
 
-To remove user defined header fields, use the unmy_hdr
+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:
@@ -3015,7 +3192,7 @@ unmy_hdr to cc
 
 
 
-Specify default save mailbox
+Specify Default Save Mailbox
 
 Usage:
 
@@ -3042,12 +3219,8 @@ expandos of $index_format to
 mailbox after it was expanded.
 
 
-
-Examples:
-
-
 
-Using %-expandos in <literal>save-hook</literal>
+Using %-expandos in <command>save-hook</command>
 
 # default: save all to ~/Mail/<author name>
 save-hook . ~/Mail/%F
@@ -3061,13 +3234,13 @@ save-hook aol\\.com$ +spam
 
 
 
-Also see the fcc-save-hook command.
+Also see the fcc-save-hook command.
 
 
 
 
 
-Specify default Fcc: mailbox when composing
+Specify Default Fcc: Mailbox When Composing
 
 Usage:
 
@@ -3099,19 +3272,17 @@ expandos of $index_format to
 See  for information on the exact format of pattern.
 
 
-
-Example: fcc-hook [@.]aol\\.com$ +spammers
-
+fcc-hook [@.]aol\\.com$ +spammers
 
 
-The above will save a copy of all messages going to the aol.com domain to
-the `+spammers' mailbox by default.  Also see the fcc-save-hook command.
+...will save a copy of all messages going to the aol.com domain to
+the `+spammers' mailbox by default.  Also see the fcc-save-hook command.
 
 
 
 
 
-Specify default save filename and default Fcc: mailbox at once
+Specify Default Save Filename and Default Fcc: Mailbox at Once
 
 Usage:
 
@@ -3126,8 +3297,8 @@ the `+spammers' mailbox by default.  Also see the 
 
 
 
-This command is a shortcut, equivalent to doing both a fcc-hook
-and a save-hook with its arguments,
+This command is a shortcut, equivalent to doing both a fcc-hook
+and a save-hook with its arguments,
 including %-expansion on mailbox according
 to $index_format.
 
@@ -3135,7 +3306,7 @@ to $index_format.
 
 
 
-Change settings based upon message recipients
+Change Settings Based Upon Message Recipients
 
 
 
@@ -3150,9 +3321,7 @@ to $index_format.
 
 command
 
-
 
-
 send-hook
 
 [!]pattern
@@ -3160,9 +3329,7 @@ to $index_format.
 
 command
 
-
 
-
 send2-hook
 
 [!]pattern
@@ -3180,35 +3347,35 @@ is executed when pattern matches.
 
 
 
-reply-hook is matched against the message you are replying to,
-instead of the message you are sending.  send-hook is
+reply-hook is matched against the message you are replying to,
+instead of the message you are sending.  send-hook is
 matched against all messages, both new
 and replies.
 
 
 
 
-reply-hooks are matched before the send-hook, regardless
+reply-hooks are matched before the send-hook, regardless
 of the order specified in the user's configuration file.
 
 
 
 
-send2-hook is matched every time a message is changed, either
+send2-hook is matched every time a message is changed, either
 by editing it, or by using the compose menu to change its recipients
-or subject.  send2-hook is executed after send-hook, and
+or subject.  send2-hook is executed after send-hook, and
 can, e.g., be used to set parameters such as the $sendmail variable depending on the message's sender
 address.
 
 
 
-For each type of send-hook or reply-hook, when multiple matches
-occur, commands are executed in the order they are specified in the muttrc
+For each type of send-hook or reply-hook, when multiple matches
+occur, commands are executed in the order they are specified in the .muttrc
 (for that type of hook).
 
 
 
-Example: send-hook mutt "set mime_forward signature=''"
+Example: send-hook mutt "set mime_forward signature=''"
 
 
 
@@ -3220,19 +3387,22 @@ signatures based upon the recipients.
 
 
 
-send-hook's are only executed once after getting the initial
-list of recipients.  Adding a recipient after replying or editing the
-message will not cause any send-hook to be executed.  Also note that
-my_hdr commands which modify recipient headers, or the message's
-subject, don't have any effect on the current message when executed
-from a send-hook.
+send-hook's are only executed once after getting the
+initial list of recipients.  Adding a recipient after replying or
+editing the message will not cause any send-hook to be executed,
+similarily if $autoedit is set
+(as then the initial list of recipients is empty). Also note that my_hdr commands which
+modify recipient headers, or the message's subject, don't have any
+effect on the current message when executed from a
+send-hook.
 
 
 
 
 
 
-Change settings before formatting a message
+Change Settings Before Formatting a Message
 
 Usage:
 
@@ -3251,7 +3421,7 @@ This command can be used to execute arbitrary configuration commands
 before viewing or formatting a message based upon information about the message.
 command is executed if the pattern matches the message to be
 displayed. When multiple matches occur, commands are executed in the order
-they are specified in the muttrc.
+they are specified in the .muttrc.
 
 
 
@@ -3271,7 +3441,7 @@ message-hook '~f freshmeat-news' 'set pager="less \"+/^  subject: .*\""'
 
 
 
-Choosing the cryptographic key of the recipient
+Choosing the Cryptographic Key of the Recipient
 
 Usage:
 
@@ -3290,7 +3460,7 @@ When encrypting messages with PGP/GnuPG or OpenSSL, you may want to associate a
 key with a given e-mail address automatically, either because the
 recipient's public key can't be deduced from the destination address,
 or because, for some reasons, you need to override the key Mutt would
-normally use.  The crypt-hook command provides a
+normally use.  The crypt-hook command provides a
 method by which you can specify the ID of the public key to be used
 when encrypting messages to a certain recipient.
 
@@ -3304,7 +3474,7 @@ just a real name.
 
 
 
-Adding key sequences to the keyboard buffer
+Adding Key Sequences to the Keyboard Buffer
 
 Usage:
 
@@ -3320,12 +3490,12 @@ This command adds the named string to the keyboard buffer. The string may
 contain control characters, key names and function names like the sequence
 string in the macro command. You may use it to
 automatically run a sequence of commands at startup, or when entering
-certain folders. For example, the following command will automatically
-collapse all threads when entering a folder:
+certain folders. For example, 
+shows how to automatically collapse all threads when entering a folder.
 
 
 
-Embedding <literal>push</literal> in <literal>folder-hook</literal>
+Embedding <command>push</command> in <command>folder-hook</command>
 
 folder-hook . 'push <collapse-all>'
 
@@ -3334,7 +3504,7 @@ folder-hook . 'push <collapse-all>'
 
 
 
-Executing functions
+Executing Functions
 
 Usage:
 
@@ -3351,7 +3521,8 @@ folder-hook . 'push <collapse-all>'
 
 This command can be used to execute any function. Functions are
 listed in the function reference.
-exec function is equivalent to push <function>.
+execfunction is equivalent to
+push <function>.
 
 
 
@@ -3369,9 +3540,7 @@ listed in the function reference.
 
 value
 
-
 
-
 unscore
 
 
@@ -3384,19 +3553,19 @@ listed in the function reference.
 
 
 
-The score commands adds value to a message's score if pattern
+The score commands adds value to a message's score if pattern
 matches it.  pattern is a string in the format described in the patterns section (note: For efficiency reasons, patterns
 which scan information not available in the index, such as ˜b,
 ˜B or ˜h, may not be used).  value is a
 positive or negative integer.  A message's final score is the sum total of all
-matching score entries.  However, you may optionally prefix value with
-an equal sign (=) to cause evaluation to stop at a particular entry if there is
+matching score entries.  However, you may optionally prefix value with
+an equal sign (=) to cause evaluation to stop at a particular entry if there is
 a match.  Negative final scores are rounded up to 0.
 
 
 
-The unscore command removes score entries from the list.  You must
-specify the same pattern specified in the score command for it to be
+The unscore command removes score entries from the list.  You must
+specify the same pattern specified in the score command for it to be
 removed.  The pattern * is a special token which means to clear the list
 of all score entries.
 
@@ -3404,7 +3573,7 @@ of all score entries.
 
 
 
-Spam detection
+Spam Detection
 
 Usage:
 
@@ -3416,9 +3585,7 @@ of all score entries.
 
 format
 
-
 
-
 nospam
 
 
@@ -3432,7 +3599,7 @@ of all score entries.
 
 
 Mutt has generalized support for external spam-scoring filters.
-By defining your spam patterns with the spam and nospam
+By defining your spam patterns with the spam and nospam
 commands, you can limit, search, and sort your
 mail based on its spam attributes, as determined by the external
 filter. You also can display the spam attributes in your index
@@ -3442,10 +3609,10 @@ to display spam tags only when they are defined for a given message.)
 
 
 Your first step is to define your external filter's spam patterns using
-the spam command. pattern should be a regular expression
+the spam command. pattern should be a regular expression
 that matches a header in a mail message. If any message in the mailbox
 matches this regular expression, it will receive a spam tag or
-spam attribute (unless it also matches a nospam pattern -- see
+spam attribute (unless it also matches a nospam pattern — see
 below.) The appearance of this attribute is entirely up to you, and is
 governed by the format parameter. format can be any static
 text, but it also can include back-references from the pattern
@@ -3454,19 +3621,27 @@ sub-expression contained within parentheses.) %1 is re
 the first back-reference in the regex, %2 with the second, etc.
 
 
+
+To match spam tags, mutt needs the corresponding header information
+which is always the case for local and POP folders but not for IMAP in
+the default configuration. Depending on the spam header to be analyzed,
+$imap_headers may need
+to be adjusted.
+
+
 
 If you're using multiple spam filters, a message can have more than
-one spam-related header. You can define spam patterns for each
+one spam-related header. You can define spam patterns for each
 filter you use. If a message matches two or more of these patterns, and
-the $spam_separator variable is set to a string, then the
+the $spam_separator variable is set to a string, then the
 message's spam tag will consist of all the format strings joined
-together, with the value of $spam_separator separating
+together, with the value of $spam_separator separating
 them.
 
 
 
-For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
-define these spam settings:
+For example, suppose one uses DCC, SpamAssassin, and PureMessage, then
+the configuration might look like in .
 
 
 
@@ -3480,22 +3655,22 @@ set spam_separator=", "
 
 
 
-If I then received a message that DCC registered with many hits
+If then a message is received that DCC registered with many hits
 under the Fuz2 checksum, and that PureMessage registered with a
 97% probability of being spam, that message's spam tag would read
 90+/DCC-Fuz2, 97/PM. (The four characters before =many in a
-DCC report indicate the checksum used -- in this case, Fuz2.)
+DCC report indicate the checksum used — in this case, Fuz2.)
 
 
 
-If the $spam_separator variable is unset, then each
+If the $spam_separator variable is unset, then each
 spam pattern match supersedes the previous one. Instead of getting
 joined format strings, you'll get only the last one to match.
 
 
 
 The spam tag is what will be displayed in the index when you use
-%H in the $index_format variable. It's also the
+%H in the $index_format variable. It's also the
 string that the ˜H pattern-matching expression matches against for
 <search> and <limit> functions. And it's what sorting by spam
 attribute will use as a sort key.
@@ -3504,47 +3679,47 @@ attribute will use as a sort key.
 
 That's a pretty complicated example, and most people's actual
 environments will have only one spam filter. The simpler your
-configuration, the more effective mutt can be, especially when it comes
+configuration, the more effective Mutt can be, especially when it comes
 to sorting.
 
 
 
-Generally, when you sort by spam tag, mutt will sort lexically --
+Generally, when you sort by spam tag, Mutt will sort lexically —
 that is, by ordering strings alphanumerically. However, if a spam tag
-begins with a number, mutt will sort numerically first, and lexically
+begins with a number, Mutt will sort numerically first, and lexically
 only when two numbers are equal in value. (This is like UNIX's
-sort -n.) A message with no spam attributes at all -- that is, one
-that didn't match any of your spam patterns -- is sorted at
+sort -n.) A message with no spam attributes at all — that is, one
+that didn't match any of your spam patterns — is sorted at
 lowest priority. Numbers are sorted next, beginning with 0 and ranging
 upward. Finally, non-numeric strings are sorted, with a taking lower
 priority than z. Clearly, in general, sorting by spam tags is most
 effective when you can coerce your filter to give you a raw number. But
-in case you can't, mutt can still do something useful.
+in case you can't, Mutt can still do something useful.
 
 
 
-The nospam command can be used to write exceptions to spam
-patterns. If a header pattern matches something in a spam command,
+The nospam command can be used to write exceptions to spam
+patterns. If a header pattern matches something in a spam command,
 but you nonetheless do not want it to receive a spam tag, you can list a
-more precise pattern under a nospam command.
+more precise pattern under a nospam command.
 
 
 
-If the pattern given to nospam is exactly the same as the
-pattern on an existing spam list entry, the effect will be to
+If the pattern given to nospam is exactly the same as the
+pattern on an existing spam list entry, the effect will be to
 remove the entry from the spam list, instead of adding an exception.
-Likewise, if the pattern for a spam command matches an entry
-on the nospam list, that nospam entry will be removed. If the
-pattern for nospam is *, all entries on both lists
-will be removed. This might be the default action if you use spam
-and nospam in conjunction with a folder-hook.
+Likewise, if the pattern for a spam command matches an entry
+on the nospam list, that nospam entry will be removed. If the
+pattern for nospam is *, all entries on both lists
+will be removed. This might be the default action if you use spam
+and nospam in conjunction with a folder-hook.
 
 
 
-You can have as many spam or nospam commands as you like.
-You can even do your own primitive spam detection within mutt -- for
+You can have as many spam or nospam commands as you like.
+You can even do your own primitive spam detection within Mutt — for
 example, if you consider all mail from MAILER-DAEMON to be spam,
-you can use a spam command like this:
+you can use a spam command like this:
 
 
 
@@ -3556,6 +3731,108 @@ spam "^From: .*MAILER-DAEMON"       "999"
 
 Setting and Querying Variables
 
+
+Variable Types
+
+
+Mutt supports these types of configuration variables:
+
+
+
+
+boolean
+
+
+A boolean expression, either yes or no.
+
+
+
+
+number
+
+
+A signed integer number in the range -32768 to 32767.
+
+
+
+
+string
+
+
+Arbitrary text.
+
+
+
+
+path
+
+
+A specialized string for representing paths including support for
+mailbox shortcuts (see ) as well as tilde
+(˜) for a user's home directory and more.
+
+
+
+
+quadoption
+
+
+Like a boolean but triggers a prompt when set to ask-yes
+or ask-no with yes and no
+preselected respectively.
+
+
+
+
+sort order
+
+
+A specialized string allowing only particular words as values depending
+on the variable.
+
+
+
+
+regular expression
+
+
+A regular expression, see  for an introduction.
+
+
+
+
+folder magic
+
+
+Specifies the type of folder to use: mbox,
+mmdf, mh
+or maildir.
+Currently only used to determine the type for newly created folders.
+
+
+
+
+e-mail address
+
+
+An e-mail address either with or without
+realname. The older user@example.org (Joe User)
+form is supported but strongly deprecated.
+
+
+
+
+user-defined
+
+
+Arbitrary text, see  for details.
+
+
+
+
+
+
+
 
 Commands
 
@@ -3579,10 +3856,8 @@ The following commands are available to manipulate and query variables:
 variable=value
 
 
-
-
+
 
-
 toggle
 
 variable
@@ -3590,9 +3865,7 @@ The following commands are available to manipulate and query variables:
 
 variable
 
-
 
-
 unset
 
 variable
@@ -3600,9 +3873,7 @@ The following commands are available to manipulate and query variables:
 
 variable
 
-
 
-
 reset
 
 variable
@@ -3630,22 +3901,22 @@ action to be carried out as if you had answered no.  A value of
 
 
 
-Prefixing a variable with no will unset it.  Example: set noaskbcc.
+Prefixing a variable with no will unset it.  Example: set noaskbcc.
 
 
 
 For boolean variables, you may optionally prefix the variable name with
 inv to toggle the value (on or off).  This is useful when writing
-macros.  Example: set invsmart_wrap.
+macros.  Example: set invsmart_wrap.
 
 
 
-The toggle command automatically prepends the inv prefix to all
+The toggle command automatically prepends the inv prefix to all
 specified variables.
 
 
 
-The unset command automatically prepends the no prefix to all
+The unset command automatically prepends the no prefix to all
 specified variables.
 
 
@@ -3665,37 +3936,37 @@ variables.
 
 
 
-The reset command resets all given variables to the compile time
+The reset command resets all given variables to the compile time
 defaults (hopefully mentioned in this manual). If you use the command
-set and prefix the variable with & this has the same
-behavior as the reset command.
+set and prefix the variable with & this has the same
+behavior as the reset command.
 
 
 
-With the reset command there exists the special variable all,
+With the reset command there exists the special variable all,
 which allows you to reset all variables to their system defaults.
 
 
 
 
 
-User-defined variables
+User-Defined Variables
 
 
 Introduction
 
 
 Along with the variables listed in the
-Configuration variables section, mutt
+Configuration variables section, Mutt
 supports user-defined variables with names starting
 with my_ as in, for
 example, my_cfgdir.
 
 
 
-The set command either creates a
+The set command either creates a
 custom my_ variable or changes its
-value if it does exist already. The unset and reset
+value if it does exist already. The unset and reset
 commands remove the variable entirely.
 
 
@@ -3714,7 +3985,7 @@ files more readable.
 
 
 The following example defines and uses the variable my_cfgdir
-to abbreviate the calls of the source command:
+to abbreviate the calls of the source command:
 
 
 
@@ -3749,11 +4020,11 @@ macro pager ,x '\
 
 
 
-Since mutt expands such values already when parsing the configuration
+Since Mutt expands such values already when parsing the configuration
 file(s), the value of $my_delete in the
-last example would be the value of $delete exactly
+last example would be the value of $delete exactly
 as it was at that point during parsing the configuration file. If
-another statement would change the value for $delete
+another statement would change the value for $delete
 later in the same or another file, it would have no effect on
 $my_delete. However, the expansion can
 be deferred to runtime, as shown in the next example, when escaping the
@@ -3774,8 +4045,8 @@ macro pager <PageDown> "\
 
 Note that there is a space
 between <enter-command> and
-the set configuration command, preventing mutt from
-recording the macro's commands into its history.
+the set configuration command, preventing Mutt from
+recording the macro's commands into its history.
 
 
 
@@ -3785,7 +4056,7 @@ recording the macro's commands into its history.
 
 
 
-Reading initialization commands from another file
+Reading Initialization Commands From Another File
 
 Usage:
 
@@ -3809,15 +4080,15 @@ path of your home directory.
 
 
 
-If the filename ends with a vertical bar (|), then filename is
+If the filename ends with a vertical bar (|), then filename is
 considered to be an executable program from which to read input (eg.
-source ˜/bin/myscript|).
+source ˜/bin/myscript|).
 
 
 
 
 
-Removing hooks
+Removing Hooks
 
 Usage:
 
@@ -3837,7 +4108,7 @@ considered to be an executable program from which to read input (eg.
 This command permits you to flush hooks you have previously defined.
 You can either remove all hooks by giving the * character as an
 argument, or you can remove all hooks of a specific type by saying
-something like unhook send-hook.
+something like unhook send-hook.
 
 
 
@@ -3850,11 +4121,11 @@ something like unhook send-hook.
 
 
 Format strings are a general concept you'll find in several locations
-through the mutt configuration, especially in the
+through the Mutt configuration, especially in the
 $index_format,
 $pager_format,
 $status_format,
-and other *_format variables. These can be very straightforward,
+and other related variables. These can be very straightforward,
 and it's quite possible you already know how to use them.
 
 
@@ -3871,22 +4142,19 @@ too. Those are our concern here.
 
 Some of the modifiers are borrowed right out of C (though you might
 know them from Perl, Python, shell, or another language). These are
-the [-]m.n modifiers, as in %-12.12s. As with
+the [-]m.n modifiers, as in %-12.12s. As with
 such programming languages, these modifiers allow you to specify the
 minimum and maximum size of the resulting string, as well as its
 justification. If the - sign follows the percent, the string will
 be left-justified instead of right-justified. If there's a number
 immediately following that, it's the minimum amount of space the
-formatted string will occupy -- if it's naturally smaller than that, it
+formatted string will occupy — if it's naturally smaller than that, it
 will be padded out with spaces.  If a decimal point and another number
-follow, that's the maximum space allowable -- the string will not be
+follow, that's the maximum space allowable — the string will not be
 permitted to exceed that width, no matter its natural size. Each of
 these three elements is optional, so that all these are legal format
-strings:
-%-12s
-%4c
-%.15F
-%-12.15L
+strings: %-12s, %4c,
+%.15F and %-12.15L.
 
 
 
@@ -3894,11 +4162,11 @@ Mutt adds some other modifiers to format strings. If you use an equals
 symbol (=) as a numeric prefix (like the minus
 above), it will force the string to be centered within its minimum
 space range. For example, %=14y will reserve 14
-characters for the %y expansion -- that's the X-Label: header, in
-$index_format. If the expansion
+characters for the %y expansion — that's the X-Label: header, in
+$index_format. If the expansion
 results in a string less than 14 characters, it will be centered in a
-14-character space.  If the X-Label for a message were "test", that
-expansion would look like      test     .
+14-character space.  If the X-Label for a message were test, that
+expansion would look like      test     .
 
 
 
@@ -3911,6 +4179,54 @@ replace all decimal points with underlines.
 
 
 
+
+Conditionals
+
+
+Depending on the format string variable, some of its 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:
+
+
+
+%?<sequence_char>?<optional_string>?
+
+
+where sequence_char is an expando, and
+optional_string is the string you would like printed if
+sequence_char is nonzero.
+optional_string may contain other
+sequences as well as normal text, but you may not nest optional
+strings.
+
+
+
+Here is an example illustrating how to optionally print the number of
+new messages in a mailbox in
+$status_format:
+
+
+
+%?n?%n new messages.?
+
+
+You can also switch between two strings using the following construct:
+
+
+
+%?<sequence_char>?<if_string>&<else_string>?
+
+
+If the value of sequence_char is
+non-zero, if_string will be expanded,
+otherwise else_string will be expanded.
+
+
+
+
 
 Filters
 
@@ -3936,7 +4252,7 @@ set status_format="script.sh '%r %f (%L)'|"
 
 
 
-will make mutt expand %r,
+will make Mutt expand %r,
 %f and %L
 before calling the script. The example also shows that arguments can be
 quoted: the script will receive the expanded string between the single quotes
@@ -3946,13 +4262,77 @@ as the only argument.
 
 A practical example is the mutt_xtitle
 script installed in the samples
-subdirectory of the mutt documentation: it can be used as filter for
-$status_format to set the current
+subdirectory of the Mutt documentation: it can be used as filter for
+$status_format to set the current
 terminal's title, if supported.
 
 
 
 
+
+Padding
+
+
+In most format strings, Mutt supports different types of padding using
+special %-expandos:
+
+
+
+
+%|X
+
+
+When this occurs, Mutt will fill the rest of the
+line with the character X. For
+example, filling the rest of the line with dashes is
+done by setting:
+
+
+set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-"
+
+
+
+
+%>X
+
+
+
+Since the previous expando stops at the end of line, there must be a way
+to fill the gap between two items via the %>X
+expando: it puts as many characters X in between two
+items so that the rest of the line will be right-justified. For example,
+to not put the version string and hostname the above example on the left
+but on the right and fill the gap with spaces, one might use (note the
+space after %>):
+
+
+set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"
+
+
+
+%*X
+
+
+
+Normal right-justification will print everything to the left of the
+%>, displaying padding and whatever lies to the
+right only if there's room. By contrast, soft-fill gives
+priority to the right-hand side, guaranteeing space to display it and
+showing padding only if there's still room. If necessary, soft-fill will
+eat text leftwards to make room for rightward text. For example, to
+right-justify the subject making sure as much as possible of it fits on
+screen, one might use (note two spaces after %*
+: the second ensures there's a space between the truncated
+right-hand side and the subject):
+
+
+set index_format="%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?)%*  %s"
+
+
+
+
+
+
 
 
 
@@ -3978,7 +4358,7 @@ case letter, and case insensitive otherwise.
 
 
 
-Note that \
+\
 must be quoted if used for a regular expression in an initialization
 command: \\.
 
@@ -3992,7 +4372,7 @@ expressions, by using various operators to combine smaller expressions.
 
 
 
-Note that the regular expression can be enclosed/delimited by either "
+The regular expression can be enclosed/delimited by either "
 or ' which is useful if the regular expression includes a white-space
 character.  See 
 for more information on " and ' delimiter processing.  To match a
@@ -4016,8 +4396,8 @@ the empty string at the beginning and end of a line.
 
 A list of characters enclosed by [ and ] matches any
 single character in that list; if the first character of the list
-is a caret ˆ then it matches any character not in the
-list.  For example, the regular expression [0123456789]
+is a caret ˆ then it matches any character not in the
+list.  For example, the regular expression [0123456789]
 matches any single digit.  A range of ASCII characters may be specified
 by giving the first and last characters, separated by a hyphen
 -.  Most metacharacters lose their special meaning inside
@@ -4066,8 +4446,8 @@ brackets of a character list.
 Note that the brackets in these
 class names are part of the symbolic names, and must be included
 in addition to the brackets delimiting the bracket list. For
-example, [[:digit:]] is equivalent to
-[0-9].
+example, [[:digit:]] is equivalent to
+[0-9].
 
 
 
@@ -4087,8 +4467,8 @@ sorting purposes:
 
 A collating symbol is a multi-character collating element enclosed in
 [. and .].  For example, if ch is a collating
-element, then [[.ch.]] is a regexp that matches
-this collating element, while [ch] is a regexp that
+element, then [[.ch.]] is a regexp that matches
+this collating element, while [ch] is a regexp that
 matches either c or h.
 
 
@@ -4101,7 +4481,7 @@ An equivalence class is a locale-specific name for a list of
 characters that are equivalent. The name is enclosed in [=
 and =].  For example, the name e might be used to
 represent all of è é and e.  In this case,
-[[=e=]] is a regexp that matches any of
+[[=e=]] is a regexp that matches any of
 è, é and e.
 
 
@@ -4151,7 +4531,7 @@ parentheses to override these precedence rules.
 
 
 
-If you compile Mutt with the GNU rx package, the
+If you compile Mutt with the included regular expression engine, the
 following operators may also be used in regular expressions as described in .
 
 
@@ -4185,6 +4565,9 @@ they may or may not be available in stock libraries on various systems.
 
 Patterns: Searching, Limiting and Tagging
 
+
+Pattern Modifier
+
 
 Many of Mutt's commands allow you to specify a pattern to match
 (limit, tag-pattern,
@@ -4228,8 +4611,8 @@ shows several ways to select messages.
 ~n [MIN]-[MAX]messages with a score in the range MIN to MAX *)
 ~Nnew messages
 ~Oold messages
-~pmessages addressed to you (consults alternates)
-~Pmessages from you (consults alternates)
+~pmessages addressed to you (consults alternates)
+~Pmessages from you (consults alternates)
 ~Qmessages which have been replied to
 ~r [MIN]-[MAX]messages with date-received in a Date range
 ~Rread messages
@@ -4241,10 +4624,10 @@ shows several ways to select messages.
 ~Uunread messages
 ~vmessages part of a collapsed thread.
 ~Vcryptographically verified messages
-~x EXPRmessages which contain EXPR in the References field
+~x EXPRmessages which contain EXPR in the References or In-Reply-To field
 ~X [MIN]-[MAX]messages with MIN to MAX attachments *)
 ~y EXPRmessages which contain EXPR in the X-Label field
-~z [MIN]-[MAX]messages with a size in the range MIN to MAX *)
+~z [MIN]-[MAX]messages with a size in the range MIN to MAX *) **)
 ~=duplicated messages (see $duplicate_threads)
 ~$unreferenced messages (requires threaded view)
 ~(PATTERN)messages in threads
@@ -4256,56 +4639,62 @@ threads containing messages from you: ~(~P)
 
 
 Where EXPR is a
-regular expression.  Special attention has to be
-made when using regular expressions inside of patterns.  Specifically,
+regular expression. 
+
+
+
+*) The forms <[MAX], >[MIN],
+[MIN]- and -[MAX]
+are allowed, too.
+
+
+
+**) The suffixes K and M are allowed to specify kilobyte and megabyte respectively.
+
+
+
+Special attention has to be
+payed when using regular expressions inside of patterns.  Specifically,
 Mutt's parser for these patterns will strip one level of backslash (\),
 which is normally used for quoting.  If it is your intention to use a
 backslash in the regular expression, you will need to use two backslashes
-instead (\\). You can force mutt to treat EXPR as a simple string
+instead (\\). You can force Mutt to treat EXPR as a simple string
 instead of a regular expression by using = instead of ˜ in the
 pattern name. For example, =b *.* will find all messages that contain
 the literal string *.*. Simple string matches are less powerful than
 regular expressions but can be considerably faster. This is especially
 true for IMAP folders, because string matches can be performed on the
 server instead of by fetching every message. IMAP treats =h specially:
-it must be of the form "header: substring" and will not partially
+it must be of the form header: substring and will not partially
 match header names. The substring part may be omitted if you simply
 wish to find messages containing a particular header without regard to
 its value.
 
 
 
-*) The forms <[MAX], >[MIN],
-[MIN]- and -[MAX]
-are allowed, too.
-
-
-
-Pattern Modifier
-
-
-
-Note that patterns matching 'lists' of addresses (notably c, C, p, P and t)
+Patterns matching lists of addresses (notably c, C, p, P and t)
 match if there is at least one match in the whole list. If you want to
 make sure that all elements of that list match, you need to prefix your
 pattern with ˆ.
 This example matches all mails which only has recipients from Germany.
 
-
 
+
+Matching all addresses in address lists
 
 ^~C \.de$
 
+
 
 
 
-
-Simple Patterns
+
+Simple Searches
 
 
-Mutt supports two versions of so called simple searches which are
+Mutt supports two versions of so called simple searches. These are
 issued if the query entered for searching, limiting and similar
-operations does not seem to be a valid pattern (i.e. it does not contain
+operations does not seem to contain a valid pattern modifier (i.e. it does not contain
 one of these characters: ˜, = or %). If the query is
 supposed to contain one of these special characters, they must be escaped
 by prepending a backslash (\).
@@ -4355,7 +4744,7 @@ for the composed complex query.
 
 
 
-Complex Patterns
+Nesting and Boolean Operators
 
 
 Logical AND is performed by specifying more than one criterion.  For
@@ -4368,7 +4757,7 @@ example:
 
 
 would select messages which contain the word mutt in the list of
-recipients and that have the word elkins in the From header
+recipients and that have the word elkins in the From header
 field.
 
 
@@ -4381,19 +4770,19 @@ patterns:
 
 
 
-! -- logical NOT operator
+! — logical NOT operator
 
 
 
 
 
-| -- logical OR operator
+| — logical OR operator
 
 
 
 
 
-() -- logical grouping operator
+() — logical grouping operator
 
 
 
@@ -4426,17 +4815,14 @@ or Ed +SomeoneElse:
 
 
 If a regular expression contains parenthesis, or a vertical bar
-("|"), you must enclose the expression in double or single quotes since
+("|"), you must enclose the expression in double or single quotes since
 those characters are also used to separate different parts of Mutt's
 pattern language.  For example: ~f "me@(mutt\.org|cs\.hmc\.edu)"
-
-
-
-
 Without the quotes, the parenthesis wouldn't end.
 This would be separated to two OR'd patterns: ˜f me@(mutt\.org
 and cs\.hmc\.edu). They are never what you want.
 
+
 
 
 
@@ -4447,8 +4833,11 @@ and cs\.hmc\.edu). They are never what you want.
 Mutt supports two types of dates, absolute and relative.
 
 
+
+Absolute Dates
+
 
-Absolute.  Dates must be in DD/MM/YY format (month and year are
+Dates must be in DD/MM/YY format (month and year are
 optional, defaulting to the current month and year).  An example of a valid
 range of dates is:
 
@@ -4466,7 +4855,7 @@ only messages sent on the given date will be selected.
 
 
 
-Error Margins.  You can add error margins to absolute dates.
+You can add error margins to absolute dates.
 An error margin is a sign (+ or -), followed by a digit, followed by
 one of the units in . As a special case, you can replace the
 sign by a * character, which is equivalent to giving identical plus and minus error margins.
@@ -4496,8 +4885,13 @@ you'd use the following pattern:
 Limit to messages matching: ~d 15/1/2001*2w
 
 
+
+
+
+Relative Dates
+
 
-Relative.  This type of date is relative to the current date, and may
+This type of date is relative to the current date, and may
 be specified as:
 
 
@@ -4505,19 +4899,19 @@ be specified as:
 
 
 
->offset (messages older than offset units)
+>offset for messages older than offset units
 
 
 
 
 
-<offset (messages newer than offset units)
+<offset for messages newer than offset units
 
 
 
 
 
-=offset (messages exactly offset units old)
+=offset for messages exactly offset units old
 
 
 
@@ -4538,12 +4932,14 @@ Limit to messages matching: ~d <1m
 
 
 All dates used when searching are relative to the
-local time zone, so unless you change the setting of your $index_format to include a
-%[...] format, these are not the dates shown
+local time zone, so unless you change the setting of your $index_format to include a
+%[...] format, these are not the dates shown
 in the main index.
 
 
 
+
+
 
 
 
@@ -4566,7 +4962,7 @@ matching syntax.
 
 Once you have tagged the desired messages, you can use the
 tag-prefix operator, which is the ; (semicolon) key by default.
-When the tag-prefix operator is used, the next operation will
+When the tag-prefix operator is used, the next operation will
 be applied to all tagged messages if that operation can be used in that
 manner.  If the $auto_tag
 variable is set, the next operation applies to the tagged messages
@@ -4574,11 +4970,11 @@ automatically, without requiring the tag-prefix.
 
 
 
-In macros or push commands,
-you can use the tag-prefix-cond operator.  If there are no tagged
-messages, mutt will "eat" the rest of the macro to abort it's execution.
-Mutt will stop "eating" the macro when it encounters the end-cond
-operator;  after this operator the rest of the macro will be executed as
+In macros or push commands,
+you can use the <tag-prefix-cond> operator.  If there are no tagged
+messages, Mutt will eat the rest of the macro to abort it's execution.
+Mutt will stop eating the macro when it encounters the <end-cond>
+operator; after this operator the rest of the macro will be executed as
 normal.
 
 
@@ -4594,49 +4990,85 @@ you may wish to tailor your configuration based upon which mailbox you are
 reading, or to whom you are sending mail.  In the Mutt world, a hook
 consists of a regular expression or
 pattern along with a
-configuration option/command.  See
+configuration option/command.  See:
 
 
-
 
+
 
-folder-hook
+account-hook
 
 
+
 
+
+charset-hook
+
+
 
+
 
-send-hook
+crypt-hook
 
 
+
 
+
+fcc-hook
+
+
 
+
 
-message-hook
+fcc-save-hook
 
 
+
 
+
+folder-hook
+
+
 
+
 
-save-hook
+iconv-hook
 
 
+
 
+
+mbox-hook
+
+
 
+
 
-mbox-hook
+message-hook
 
 
+
 
+
+reply-hook
+
+
 
+
 
-fcc-hook
+save-hook
 
 
+
 
+
+send-hook
+
+
 
+
 
-fcc-save-hook
+send2-hook
 
 
 
@@ -4648,27 +5080,35 @@ for specific details on each type of hook available.
 
 
 If a hook changes configuration settings, these changes remain
-effective until the end of the current mutt session. As this is generally
-not desired, a default hook needs to be added before all other hooks to
-restore configuration defaults. Here is an example with send-hook and the
-my_hdr directive:
+effective until the end of the current Mutt session. As this is generally
+not desired, a default hook needs to be added before all
+other hooks  of that type to restore configuration defaults.
 
 
 
-
-Combining <literal>send-hook</literal> and <literal>my_hdr</literal>
+
+Specifying a <quote>default</quote> hook
 
 send-hook . 'unmy_hdr From:'
 send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
 
 
 
+
+In , by default the value of
+$from
+and $realname
+is not overridden. When sending messages either To: or Cc:
+to <b@b.b>, the From: header is changed to
+<c@c.c>.
+
+
 
 Message Matching in Hooks
 
 
-Hooks that act upon messages (message-hook, reply-hook,
-send-hook, send2-hook, save-hook, fcc-hook) are evaluated in a
+Hooks that act upon messages (message-hook, reply-hook,
+send-hook, send2-hook, save-hook, fcc-hook) are evaluated in a
 slightly different manner. For the other
 types of hooks, a regular expression is
 sufficient.  But in dealing with messages a finer grain of control is
@@ -4681,7 +5121,7 @@ Mutt allows the use of the search pattern
 language for matching messages in hook commands.  This works in
 exactly the same way as it would when limiting or
 searching the mailbox, except that you are restricted to those
-operators which match information mutt extracts from the header of
+operators which match information Mutt extracts from the header of
 the message (i.e., from, to, cc, date, subject, etc.).
 
 
@@ -4719,7 +5159,7 @@ at that time will be used.
 
 
 Mutt supports connecting to external directory databases such as LDAP,
-ph/qi, bbdb, or NIS through a wrapper script which connects to mutt
+ph/qi, bbdb, or NIS through a wrapper script which connects to Mutt
 using a simple interface.  Using the $query_command variable, you specify the wrapper
 command to use.  For example:
 
@@ -4748,7 +5188,7 @@ roessler@does-not-exist.org        Thomas Roessler mutt pgp
 
 
 
-There are two mechanisms for accessing the query function of mutt.  One
+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 menu which will
 list the matching responses.  From the query menu, you can select
@@ -4761,10 +5201,10 @@ responses.
 The other mechanism for accessing the query function is for address
 completion, similar to the alias completion.  In any prompt for address
 entry, you can use the <complete-query> function (default: ˆT) to run a
-query based on the current address you have typed.  Like aliases, mutt
+query based on the current address you have typed.  Like aliases, Mutt
 will look for what you have typed back to the last space or comma.  If
-there is a single response for that query, mutt will expand the address
-in place.  If there are multiple responses, mutt will activate the query
+there is a single response for that query, Mutt will expand the address
+in place.  If there are multiple responses, Mutt will activate the query
 menu.  At the query menu, you can select one or more addresses to be
 added to the prompt.
 
@@ -4775,14 +5215,16 @@ added to the prompt.
 Mailbox Formats
 
 
-Mutt supports reading and writing of four different mailbox formats:
+Mutt supports reading and writing of four different local mailbox formats:
 mbox, MMDF, MH and Maildir.  The mailbox type is autodetected, so there
 is no need to use a flag for different mailbox types.  When creating new
-mailboxes, Mutt uses the default specified with the $mbox_type variable.
+mailboxes, Mutt uses the default specified with the
+$mbox_type variable. A
+short description of the formats follows.
 
 
 
-mbox.  This is the most widely used mailbox format for UNIX.  All
+mbox.  This is a widely used mailbox format for UNIX.  All
 messages are stored in a single file.  Each message has a line of the form:
 
 
@@ -4792,32 +5234,50 @@ 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).
+From_ line). The mbox format requires mailbox
+locking, is prone to mailbox corruption with concurrently writing
+clients or misinterpreted From_ lines. Depending on the
+environment, new mail detection can be unreliable. Mbox folders are fast
+to open and easy to archive.
 
 
 
-MMDF.  This is a variant of the mbox format.  Each message is
-surrounded by lines containing ˆAˆAˆAˆA (four control-A's).
+MMDF.  This is a variant of
+the mbox format.  Each message is surrounded by
+lines containing ˆAˆAˆAˆA (four
+control-A's). The same problems as for mbox apply (also with finding the
+right message separator as four control-A's may appear in message
+bodies).
 
 
 
-MH. A radical departure from mbox and MMDF, a mailbox
+MH. A radical departure from mbox and MMDF, a mailbox
 consists of a directory and each message is stored in a separate file.
 The filename indicates the message number (however, this is may not
 correspond to the message number Mutt displays). Deleted messages are
-renamed with a comma (,) prepended to the filename. Mutt
+renamed with a comma (,) prepended to the filename. Mutt
 detects this type of mailbox by looking for either .mh_sequences
-or .xmhcache (needed to distinguish normal directories from MH
-mailboxes).
+or .xmhcache files (needed to distinguish normal directories from MH
+mailboxes). MH is more robust with concurrent clients writing the mailbox,
+but still may suffer from lost flags; message corruption is less likely
+to occur than with mbox/mmdf. It's usually slower to open compared to
+mbox/mmdf since many small files have to be read (Mutt provides
+ to greatly speed this process up).
+Depending on the environment, MH is not very disk-space efficient.
 
 
 
-Maildir.  The newest of the mailbox formats, used by the Qmail MTA (a
+Maildir.  The newest of the mailbox formats, used by the Qmail MTA (a
 replacement for sendmail).  Similar to MH, except that it adds three
 subdirectories of the mailbox: tmp, new and cur.  Filenames
 for the messages are chosen in such a way they are unique, even when two
 programs are writing the mailbox over NFS, which means that no file locking
-is needed.
+is needed and corruption is very unlikely. Maildir maybe
+slower to open without caching in Mutt, it too is not very
+disk-space efficient depending on the environment. Since no additional
+files are used for metadata (which is embedded in the message filenames)
+and Maildir is locking-free, it's easy to sync across different machines
+using file-level synchronization tools.
 
 
 
@@ -4828,61 +5288,72 @@ is needed.
 
 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.
+path or in path-related configuration variables. Note that these only
+work at the beginning of a string.
 
 
 
 
 
 
-! -- refers to your $spoolfile (incoming) mailbox
+! — refers to your $spoolfile (incoming) mailbox
 
 
 
 
 
-> -- refers to your $mbox file
+> — refers to your $mbox file
 
 
 
 
 
-< -- refers to your $record file
+< — refers to your $record file
 
 
 
 
 
-ˆ -- refers to the current mailbox
+ˆ — refers to the current mailbox
 
 
 
 
 
-- or !! -- refers to the file you've last visited
+- or !! — refers to the file you've last visited
 
 
 
 
 
-˜ -- refers to your home directory
+˜ — refers to your home directory
 
 
 
 
 
-= or + -- refers to your $folder directory
+= or + — refers to your $folder directory
 
 
 
 
 
-@alias -- refers to the default save folder as determined by the address of the alias
+@alias — refers to the default save folder as determined by the address of the alias
 
 
 
 
 
+
+For example, to store a copy of outgoing messages in the folder they
+were composed in,
+a folder-hook can
+be used to set $record:
+
+
+
+folder-hook . 'set record=ˆ'
+
 
 
 
@@ -4894,7 +5365,7 @@ 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 does not have to be a mailing list, but that is what it is most
 often used for), and what lists you are subscribed to.  This is
-accomplished through the use of the lists and subscribe commands in your muttrc.
+accomplished through the use of the lists and subscribe commands in your .muttrc.
 
 
 
@@ -4902,10 +5373,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 name of a list
 through which you received a message (i.e., of a subscribed list) in
 the index menu display.  This is useful to distinguish between
-personal and list mail in the same mailbox.  In the $index_format variable, the escape %L
-will return the string To <list> when list appears in the
+personal and list mail in the same mailbox.  In the $index_format variable, the expando %L
+will print the string To <list> when list appears in the
 To field, and Cc <list> when it appears in the Cc
-field (otherwise it returns the name of the author).
+field (otherwise it prints the name of the author).
 
 
 
@@ -4922,7 +5393,7 @@ specified by Mail-Followup-To, see below).
 
 Mutt also supports the Mail-Followup-To header.  When you send
 a message to a list of recipients which includes one or several
-subscribed mailing lists, and if the $followup_to option is set, mutt will generate
+subscribed mailing lists, and if the $followup_to option is set, Mutt will generate
 a Mail-Followup-To header which contains all the recipients to whom
 you send this message, but not your address. This indicates that
 group-replies or list-replies (also known as followups) to this
@@ -4933,9 +5404,9 @@ one of the mailing lists you are subscribed to.
 
 
 Conversely, when group-replying or list-replying to a message which
-has a Mail-Followup-To header, mutt will respect this header if
+has a Mail-Followup-To header, Mutt will respect this header if
 the $honor_followup_to configuration
-variable is set.  Using list-reply will in this case also make sure
+variable is set.  Using list-reply will in this case also make sure
 that the reply goes to the mailing list, even if it's not specified
 in the list of recipients in the Mail-Followup-To.
 
@@ -4967,7 +5438,7 @@ present.
 The X-Label: header field can be used to further identify mailing
 lists or list subject matter (or just to annotate messages
 individually).  The $index_format variable's %y and
-%Y escapes can be used to expand X-Label: fields in the
+%Y expandos can be used to expand X-Label: fields in the
 index, and Mutt's pattern-matcher can match regular expressions to
 X-Label: fields with the ˜y selector.  X-Label: is not a
 standard message header field, but it can easily be inserted by procmail
@@ -4998,7 +5469,7 @@ be monitored for new mail (see  for details).
 When in the index menu and being idle (also see
 $timeout), Mutt periodically checks
 for new mail in all folders which have been configured via the
-mailboxes command. The interval depends on the folder
+mailboxes command. The interval depends on the folder
 type: for local/IMAP folders it consults
 $mail_check and
 $pop_checkinterval
@@ -5009,7 +5480,7 @@ for POP folders.
 Outside the index menu the directory browser supports checking
 for new mail using the <check-new> function which is
 unbound by default. Pressing TAB will bring up a
-menu showing the files specified by the mailboxes command,
+menu showing the files specified by the mailboxes command,
 and indicate which contain new messages. Mutt will automatically enter this
 mode when invoked from the command line with the -y option.
 
@@ -5024,7 +5495,7 @@ the bottom of the screen.
 
 For the index, by default Mutt displays the number of mailboxes with new
 mail in the status bar, please refer to the
-$index_format
+$status_format
 variable for details.
 
 
@@ -5037,41 +5508,41 @@ the mailboxes list containing new mail (if any), pressing
 
 
 
-Editing threads
+Editing Threads
 
 
 Mutt has the ability to dynamically restructure threads that are broken
 either by misconfigured software or bad behavior from some
-correspondents. This allows to clean your mailboxes formats) from these
+correspondents. This allows to clean your mailboxes from these
 annoyances which make it hard to follow a discussion.
 
 
 
-Linking threads
+Linking Threads
 
 
-Some mailers tend to "forget" to correctly set the "In-Reply-To:" and
-"References:" headers when replying to a message. This results in broken
+Some mailers tend to forget to correctly set the In-Reply-To: and
+References: headers when replying to a message. This results in broken
 discussions because Mutt has not enough information to guess the correct
 threading.
 You can fix this by tagging the reply, then moving to the parent message
 and using the <link-threads> function (bound to & by default). The
-reply will then be connected to this "parent" message.
+reply will then be connected to this parent message.
 
 
 
 You can also connect multiple children at once, tagging them and using the
-tag-prefix command (';') or the auto_tag option.
+<tag-prefix> command (';') or the $auto_tag option.
 
 
 
 
 
-Breaking threads
+Breaking Threads
 
 
 On mailing lists, some people are in the bad habit of starting a new
-discussion by hitting "reply" to any message from the list and changing
+discussion by hitting reply to any message from the list and changing
 the subject to a totally unrelated one.
 You can fix such threads by using the <break-thread> function (bound
 by default to #), which will turn the subthread starting from the
@@ -5111,7 +5582,7 @@ whether DSN is supported.
 
 For SMTP delivery using $smtp_url, it depends on the
-capabilities announced by the server whether mutt will attempt to
+capabilities announced by the server whether Mutt will attempt to
 request DSN or not.
 
 
@@ -5136,7 +5607,54 @@ macro pager \cb |urlview\n
 
 
 
-
+
+Miscellany
+
+
+This section documents various features that fit nowhere else.
+
+
+
+
+
+Address normalization
+
+
+
+Mutt normalizes all e-mail addresses to the simplest form possible. If
+an address contains a realname, the form
+Joe User <joe@example.com> is used and the
+pure e-mail address without angle brackets otherwise, i.e. just
+joe@example.com.
+
+
+This normalization affects all headers Mutt generates including aliases.
+
+
+
+
+
+Initial folder selection
+
+
+
+The folder Mutt opens at startup is determined as follows: the folder
+specified in the $MAIL environment variable if
+present. Otherwise, the value of $MAILDIR is taken
+into account. If that isn't present either, Mutt takes the user's
+mailbox in the mailspool as determined at compile-time (which may also
+reside in the home directory). The
+$spoolfile setting overrides
+this selection. Highest priority has the mailbox given with the
+-f command line option.
+
+
+
+
+
+
+
+
 
 
 Mutt's MIME Support
@@ -5162,7 +5680,7 @@ menu.
 
 
 
-Viewing MIME messages in the pager
+Viewing MIME Messages in the Pager
 
 
 When you select a message from the index and view it in the pager, Mutt
@@ -5203,12 +5721,12 @@ If Mutt cannot deal with a MIME type, it will display a message like:
 The Attachment Menu
 
 
-The default binding for view-attachments is `v', which displays the
+The default binding for <view-attachments> is v, which displays the
 attachment menu for a message.  The attachment menu displays a list of
 the attachments in a message.  From the attachment menu, you can save,
 print, pipe, delete, and view attachments.  You can apply these
 operations to a group of attachments at once, by tagging the attachments
-and by using the tag-prefix operator.  You can also reply to the
+and by using the <tag-prefix> operator.  You can also reply to the
 current message from this menu, and only the current attachment (or the
 attachments tagged) will be quoted in your reply.  You can view
 attachments as text, or view them using the mailcap viewer definition.
@@ -5252,16 +5770,16 @@ Attachments appear as follows:
 
 The '-' denotes that Mutt will delete the file after sending (or
 postponing, or canceling) 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 the edit-type command
+<toggle-unlink> command (default: u).  The next field is the MIME
+content-type, and can be changed with the <edit-type> command
 (default: ˆT).  The next field is the encoding for the attachment,
 which allows a binary message to be encoded for transmission on 7bit
-links.  It can be changed with the edit-encoding command
+links.  It can be changed with the <edit-encoding> command
 (default: ˆE).  The next field is the size of the attachment,
 rounded to kilobytes or megabytes.  The next field is the filename,
-which can be changed with the rename-file command (default: R).
+which can be changed with the <rename-file> command (default: R).
 The final field is the description of the attachment, and can be
-changed with the edit-description command (default: d).
+changed with the <edit-description> command (default: d).
 
 
 
@@ -5269,17 +5787,17 @@ changed with the edit-description command (default: d).
 
 
 
-MIME Type configuration with <literal>mime.types</literal>
+MIME Type Configuration with <literal>mime.types</literal>
 
 
 When you add an attachment to your mail message, Mutt searches your
-personal mime.types file at ${HOME}/.mime.types, and then
-the system mime.types file at /usr/local/share/mutt/mime.types or
+personal mime.types file at ${HOME}/.mime.types, and then
+the system mime.types file at /usr/local/share/mutt/mime.types or
 /etc/mime.types
 
 
 
-The mime.types file consist of lines containing a MIME type and a space
+The mime.types file consist of lines containing a MIME type and a space
 separated list of extensions.  For example:
 
 
@@ -5300,12 +5818,12 @@ 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
 as text/plain.  If the file contains binary information, then Mutt will
 mark it as application/octet-stream.  You can change the MIME
-type that Mutt assigns to an attachment by using the edit-type
+type that Mutt assigns to an attachment by using the <edit-type>
 command from the compose menu (default: ˆT). The MIME type is actually a
 major mime type followed by the sub-type, separated by a '/'. 6 major
 types: application, text, image, video, audio, and model have been approved
 after various internet discussions. Mutt recognizes all of these if the
-appropriate entry is found in the mime.types file. It also recognizes other
+appropriate entry is found in the mime.types file. It also recognizes other
 major mime types, such as the chemical type that is widely used in the
 molecular modeling community to pass molecular data in various forms to
 various molecular viewers. Non-recognized mime types should only be used
@@ -5315,7 +5833,7 @@ if the recipient of the message is likely to be expecting such attachments.
 
 
 
-MIME Viewer configuration with <literal>mailcap</literal>
+MIME Viewer Configuration with Mailcap
 
 
 Mutt supports RFC 1524 MIME Configuration, in particular the Unix
@@ -5323,7 +5841,7 @@ specific format specified in Appendix A of RFC 1524.  This file format
 is commonly referred to as the mailcap format.  Many MIME compliant
 programs utilize the mailcap format, allowing you to specify handling
 for all MIME types in one place for all programs.  Programs known to
-use this format include Netscape, XMosaic, lynx and metamail.
+use this format include Firefox, lynx and metamail.
 
 
 
@@ -5345,7 +5863,7 @@ is a colon delimited list containing the following files:
 
 where $HOME is your home directory. The
 $PKGDATADIR and the
-$SYSCONFDIR directories depend on where mutt
+$SYSCONFDIR directories depend on where Mutt
 is installed: the former is the default for shared data, the
 latter for system configuration files.
 
@@ -5366,7 +5884,7 @@ entries.
 
 
 
-The Basics of the mailcap file
+The Basics of the Mailcap File
 
 
 A mailcap file consists of a series of lines which are comments, blank,
@@ -5477,7 +5995,7 @@ This is the simplest form of a mailcap file.
 
 
 
-Secure use of mailcap
+Secure Use of Mailcap
 
 
 The interpretation of shell meta-characters embedded in MIME parameters
@@ -5487,7 +6005,7 @@ substituting them, see the $mailcap&lowb
 
 
 
-Although mutt's procedures to invoke programs with mailcap seem to be
+Although Mutt's procedures to invoke programs with mailcap seem to be
 safe, there are other applications parsing mailcap, maybe taking less care
 of it.  Therefore you should pay attention to the following rules:
 
@@ -5518,7 +6036,7 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
 
 
 
-Advanced mailcap Usage
+Advanced Mailcap Usage
 
 
 Optional Fields
@@ -5557,7 +6075,7 @@ and Mutt will use your standard pager to display the results.
 needsterminal
 
 
-Mutt uses this flag when viewing attachments with auto_view, in order to decide whether it should honor the setting
+Mutt uses this flag when viewing attachments with auto_view, in order to decide whether it should honor the setting
 of the $wait_key variable or
 not.  When an attachment is viewed using an interactive program, and the
 corresponding mailcap entry has a needsterminal flag, Mutt will use
@@ -5583,7 +6101,7 @@ specific MIME type.  Mutt supports this from the compose menu.
 
 This flag specifies the command to use to create a new attachment of a
 specific MIME type.  This command differs from the compose command in
-that mutt will expect standard MIME headers on the data.  This can be
+that Mutt will expect standard MIME headers on the data.  This can be
 used to specify parameters, filename, description, etc. for a new
 attachment.   Mutt supports this from the compose menu.
 
@@ -5641,16 +6159,16 @@ For example:
 
 
 
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
+text/html; firefox -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 display the
-text/html object.  If RunningX doesn't return 0, then Mutt will go on
-to the next entry and use lynx to display the text/html object.
+RunningX returns 0, then Mutt will call firefox to display the
+text/html object.  If RunningX doesn't return 0, then Mutt will go on
+to the next entry and use lynx to display the text/html object.
 
 
 
@@ -5681,7 +6199,7 @@ entry with the print command.
 
 
 
-In addition, you can use this with auto_view
+In addition, you can use this with auto_view
 to denote two commands for viewing an attachment, one to be viewed
 automatically, the other to be viewed interactively from the attachment
 menu.  In addition, you can then use the test feature to determine which
@@ -5689,13 +6207,13 @@ viewer to use interactively depending on your environment.
 
 
 
-text/html;      netscape -remote 'openURL(%s)' ; test=RunningX
+text/html;      firefox -remote 'openURL(%s)' ; test=RunningX
 text/html;      lynx %s; nametemplate=%s.html
 text/html;      lynx -dump %s; nametemplate=%s.html; copiousoutput
 
 
 
-For auto_view, Mutt will choose the third
+For auto_view, 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 program returns non-zero, Mutt will use the second entry
@@ -5709,7 +6227,7 @@ for interactive viewing.
 
 
 The various commands defined in the mailcap files are passed to the
-/bin/sh shell using the system() function.  Before the
+/bin/sh shell using the system(3) function.  Before the
 command is passed to /bin/sh -c, it is parsed to expand
 various special parameters with information from Mutt.  The keywords
 Mutt expands are:
@@ -5782,7 +6300,7 @@ multipart messages, which is handled internally by Mutt.
 
 
 
-Example mailcap files
+Example Mailcap Files
 
 
 This mailcap file is fairly simple and standard:
@@ -5793,8 +6311,8 @@ This mailcap file is fairly simple and standard:
 video/*;        xanim %s > /dev/null
 image/*;        xv %s > /dev/null
 
-# I'm always running netscape (if my computer had more memory, maybe)
-text/html;      netscape -remote 'openURL(%s)'
+# I'm always running firefox (if my computer had more memory, maybe)
+text/html;      firefox -remote 'openURL(%s)'
 
 
 
@@ -5806,12 +6324,12 @@ This mailcap file shows quite a number of examples:
 # send that to /dev/null so I don't see it
 video/*;        xanim %s > /dev/null
 
-# Send html to a running netscape by remote
-text/html;      netscape -remote 'openURL(%s)'; test=RunningNetscape
+# Send html to a running firefox by remote
+text/html;      firefox -remote 'openURL(%s)'; test=RunningFirefox
 
-# If I'm not running netscape but I am running X, start netscape on the
+# If I'm not running firefox but I am running X, start firefox on the
 # object
-text/html;      netscape %s; test=RunningX
+text/html;      firefox %s; test=RunningX
 
 # Else use lynx to view it as text
 text/html;      lynx %s
@@ -5822,7 +6340,7 @@ text/html;      lynx -dump %s; copiousoutput
 # I use enscript to print text in two columns to a page
 text/*;         more %s; print=enscript -2Gr %s
 
-# Netscape adds a flag to tell itself to view jpegs internally
+# Firefox adds a flag to tell itself to view jpegs internally
 image/jpeg;xv %s; x-mozilla-flags=internal
 
 # Use xv to view images if I'm running X
@@ -5846,6 +6364,30 @@ application/ms-excel; open.pl %s
 
 MIME Autoview
 
+
+Usage:
+
+
+
+auto-view
+
+mimetype
+
+
+mimetype
+
+
+unauto-view
+
+
+*
+
+
+mimetype
+
+
+
+
 
 In addition to explicitly telling Mutt to view an attachment with the
 MIME viewer defined in the mailcap file, Mutt has support for
@@ -5860,12 +6402,9 @@ representation which you can view in the pager.
 
 
 
-You then use the auto_view muttrc command to list the
-content-types that you wish to view automatically.
-
-
-
-For instance, if you set auto_view to:
+You then use the auto_view .muttrc command to list the
+content-types that you wish to view automatically.  For instance, if you
+set it to:
 
 
 
@@ -5888,9 +6427,9 @@ application/postscript; ps2ascii %s; copiousoutput
 
 
 
-unauto_view can be used to remove previous entries from the autoview list.
-This can be used with message-hook to autoview messages based on size, etc.
-unauto_view * will remove all previous entries.
+unauto_view can be used to remove previous entries from the autoview list.
+This can be used with message-hook to autoview messages based on size, etc.
+unauto_view * will remove all previous entries.
 
 
 
@@ -5900,11 +6439,11 @@ This can be used with message-hook to autoview messages based on size, etc.
 
 
 Mutt has some heuristics for determining which attachment of a
-multipart/alternative type to display.  First, mutt will check the
-alternative_order list to determine if one of the available types
-is preferred.  The alternative_order list consists of a number of
-mimetypes in order, including support for implicit and explicit
-wildcards, for example:
+multipart/alternative type to display.  First, Mutt will check the
+alternative_order list
+to determine if one of the available types is preferred.  It consists of
+a number of mimetypes in order, including support for implicit and
+explicit wildcards, for example:
 
 
 
@@ -5912,15 +6451,15 @@ 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
+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.
 
 
 
-To remove a MIME type from the alternative_order list, use the
-unalternative_order command.
+To remove a MIME type from the alternative_order list, use the
+unalternative_order command.
 
 
 
@@ -5934,11 +6473,11 @@ attachment-counting and -searching support might be for you.  You can
 make your message index display the number of qualifying attachments in
 each message, or search for messages by attachment count.  You also can
 configure what kinds of attachments qualify for this feature with the
-attachments and unattachments commands.
+attachments and unattachments commands.
 
 
 
-In order to provide this information, mutt needs to fully MIME-parse
+In order to provide this information, Mutt needs to fully MIME-parse
 all messages affected first. This can slow down operation especially for
 remote mail folders such as IMAP because all messages have to be
 downloaded first regardless whether the user really wants to view them
@@ -5949,14 +6488,31 @@ or not.
 The syntax is:
 
 
-
-attachments   {+|-}disposition mime-type
-unattachments {+|-}disposition mime-type
-attachments   ?
-
+
+attachments
+
+{ + | - }disposition
+
+
+mime-type
+
+
+unattachments
+
+{ + | - }disposition
+
+
+mime-type
+
+
+attachments
+
+?
+
+
 
 
-Disposition is the attachment's Content-disposition type -- either
+disposition is the attachment's Content-Disposition type — either
 inline or attachment.
 You can abbreviate this to I or A.
 
@@ -5970,7 +6526,7 @@ below of how this is useful.
 
 
 
-Mime-type is, unsurprisingly, the MIME type of the attachment you want
+mime-type is, unsurprisingly, the MIME type of the attachment you want
 to affect.  A MIME type is always of the format major/minor, where
 major describes the broad category of document you're looking at, and
 minor describes the specific type within that category.  The major
@@ -5980,11 +6536,11 @@ any MIME type.)
 
 
 
-The MIME types you give to the attachments directive are a kind of
-pattern.  When you use the attachments directive, the patterns you
-specify are added to a list.  When you use unattachments, the pattern
+The MIME types you give to the attachments directive are a kind of
+pattern.  When you use the attachments directive, the patterns you
+specify are added to a list.  When you use unattachments, the pattern
 is removed from the list.  The patterns are not expanded and matched
-to specific MIME types at this time -- they're just text in a list.
+to specific MIME types at this time — they're just text in a list.
 They're only matched when actually evaluating a message.
 
 
@@ -6046,7 +6602,7 @@ attachments   -I message/external-body
 
 
 
-Entering the command attachments ?
+Entering the command attachments ?
 as a command will list your current settings in Muttrc format, so that
 it can be pasted elsewhere.
 
@@ -6056,15 +6612,39 @@ it can be pasted elsewhere.
 
 MIME Lookup
 
+
+Usage:
+
+
+
+mime-lookup
+
+mimetype
+
+
+mimetype
+
+
+unmime-lookup
+
+
+*
+
+
+mimetype
+
+
+
+
 
 Mutt's mime_lookup list specifies a list of mime-types that should not
 be treated according to their mailcap entry.  This option is designed to
-deal with binary types such as application/octet-stream.  When an attachment's
+deal with binary types such as application/octet-stream.  When an attachment's
 mime-type is listed in mime_lookup, then the extension of the filename will
-be compared to the list of extensions in the mime.types file.  The mime-type
+be compared to the list of extensions in the mime.types file.  The mime-type
 associated with this extension will then be used to process the attachment
 according to the rules in the mailcap file and according to any other configuration
-options (such as auto_view) specified.  Common usage would be:
+options (such as auto_view) specified.  Common usage would be:
 
 
 
@@ -6072,9 +6652,9 @@ mime_lookup application/octet-stream application/X-Lotus-Manuscript
 
 
 
-In addition, the unmime_lookup command may be used to disable this feature
-for any particular mime-type if it had been set, for example, in a global
-muttrc.
+In addition, the unmime_lookup command may be
+used to disable this feature for any particular mime-type if it had been
+set, for example, in a global .muttrc.
 
 
 
@@ -6082,13 +6662,13 @@ muttrc.
 
 
 
-Optional features
+Optional Features
 
 
-General notes
+General Notes
 
 
-Enabling/disabling features
+Enabling/Disabling Features
 
 
 Mutt supports several of optional features which can be enabled or
@@ -6101,7 +6681,7 @@ the configure --help output.
 Which features are enabled or disabled can later be determined from the
 output of mutt -v. If a compile option starts with
 + it is enabled and disabled if prefixed with -. For example, if
-mutt was compiled using GnuTLS for encrypted communication instead of
+Mutt was compiled using GnuTLS for encrypted communication instead of
 OpenSSL, mutt -v would contain:
 
 
@@ -6111,12 +6691,12 @@ OpenSSL, mutt -v would contain:
 
 
 
-URL syntax
+URL Syntax
 
 
 Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
 to access servers using URLs. The canonical syntax for specifying URLs
-in mutt is (an item enclosed in [] means it is optional and
+in Mutt is (an item enclosed in [] means it is optional and
 may be omitted):
 
 
@@ -6125,37 +6705,42 @@ proto[s]://[username[:password]@]server[:port]/[path]
 
 
 
-proto is the communication protocol:
+proto is the communication protocol:
 imap for IMAP, pop for POP3 and
-smtp for SMTP. If s for secure communication
-is appended, mutt will attempt to establish an encrypted communication
-using SSL or TLS. If no explicit port is given, mutt will use the
-system's default for the given protocol.
+smtp for SMTP. If s for secure
+communication is appended, Mutt will attempt to establish an
+encrypted communication using SSL or TLS.
 
 
 
-Since all protocols by mutt support authentication, the username may be
-given directly in the URL instead of using the pop_user or
-imap_user variables. It may contain the @ symbol
-being used by many mail systems as part of the login name. A password can be
-given, too but is not recommended if the URL is specified in a configuration
-file on disk.
+Since all protocols supported by Mutt support/require authentication,
+login credentials may be specified in the URL. This has the advantage
+that multiple IMAP, POP3 or SMTP servers may be specified (which isn't
+possible using, for example,
+$imap_user). The username
+may contain the @ symbol being used by many mail systems
+as part of the login name. A password can be given, too but is not
+recommended if the URL is specified in a configuration file on disk.
 
 
 
-The optional path is only relevant for IMAP.
+If no port number is given, Mutt will use the system's default for the
+given protocol (usually consulting /etc/services).
 
 
 
-For IMAP for example, you can select an alternative port by specifying it with the
-server: imap://imapserver:port/INBOX. You can also specify different
-username for each folder: imap://username@imapserver[:port]/INBOX
-or imap://username2@imapserver[:port]/path/to/folder.
-Replacing imap:// by imaps://
-would make mutt attempt to connect using SSL or TLS on a different port
-to encrypt the communication.
+The optional path is only relevant for IMAP.
 
 
+
+URLs
+
+pops://host/
+imaps://user@host/INBOX/Sent
+smtp://user@host:587/
+
+
+
 
 
 
@@ -6164,7 +6749,7 @@ to encrypt the communication.
 SSL/TLS Support
 
 
-If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
+If Mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
 compiled with support for SSL or TLS using either OpenSSL or GnuTLS (
 by running the configure script with the
 --enable-ssl=... option for OpenSSL or
@@ -6179,7 +6764,7 @@ are suffixed with s for secure communication.
 POP3 Support
 
 
-If Mutt was compiled with POP3 support (by running the configure
+If Mutt is compiled with POP3 support (by running the configure
 script with the --enable-pop flag), it has the ability to work
 with mailboxes located on a remote POP3 server and fetch mail for local
 browsing.
@@ -6199,9 +6784,20 @@ controlled by the
 variable, which defaults to every 60 seconds.
 
 
+
+POP is read-only which doesn't allow for some features like editing
+messages or changing flags. However, using
+ and 
+Mutt simulates the new/old/read flags as well as flagged and replied.
+Mutt applies some logic on top of remote messages but cannot change
+them so that modifications of flags are lost when
+messages are downloaded from the POP server (either by Mutt or other
+tools).
+
+
 
 
-Another way to access your POP3 mail is the <fetch-mail$ function
+Another way to access your POP3 mail is the <fetch-mail> function
 (default: G).  It allows to connect to $pop_host, 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.
@@ -6211,7 +6807,7 @@ point, Mutt runs exactly as if the mail had always been local.
 
 If you only need to fetch all messages to a
 local mailbox you should consider using a specialized program, such as
-fetchmail, getmail or similar.
+fetchmail(1), getmail(1) or similar.
 
 
 
@@ -6253,7 +6849,7 @@ want to carefully tune the
 $mail_check
 and
 $timeout
-variables. Personally I use
+variables. Reasonable values are:
 
 
 
@@ -6262,7 +6858,7 @@ set timeout=15
 
 
 
-with relatively good results over my slow modem line.
+with relatively good results even over slow modem lines.
 
 
 
@@ -6274,10 +6870,10 @@ selects the same folder.
 
 
 
-The Folder Browser
+The IMAP Folder Browser
 
 
-As of version 1.2, mutt supports browsing mailboxes on an IMAP
+As of version 1.2, Mutt supports browsing mailboxes on an IMAP
 server. This is mostly the same as the local file browser, with the
 following differences:
 
@@ -6286,8 +6882,8 @@ following differences:
 
 
 
-In lieu of file permissions, mutt displays the string "IMAP",
-possibly followed by the symbol "+", indicating
+In lieu of file permissions, Mutt displays the string IMAP,
+possibly followed by the symbol +, indicating
 that the entry contains both messages and subfolders. On
 Cyrus-like servers folders will often contain both messages and
 subfolders.
@@ -6307,10 +6903,10 @@ the messages in that folder, you must use view-file instead
 
 
 You can create, delete and rename mailboxes with the
-create-mailbox, delete-mailbox, and
-rename-mailbox commands (default bindings: C,
+<create-mailbox>, <delete-mailbox>, and
+<rename-mailbox> commands (default bindings: C,
 d and r, respectively). You may also
-subscribe and unsubscribe to mailboxes (normally
+<subscribe> and <unsubscribe> to mailboxes (normally
 these are bound to s and u, respectively).
 
 
@@ -6329,7 +6925,7 @@ NTLM authentication for you poor exchange users out there, but it has
 yet to be integrated into the main tree). There is also support for
 the pseudo-protocol ANONYMOUS, which allows you to log in to a public
 IMAP server without having an account. To use ANONYMOUS, simply make
-your username blank or "anonymous".
+your username blank or anonymous.
 
 
 
@@ -6339,7 +6935,7 @@ method available on your host and the server. Using some of these methods
 (including DIGEST-MD5 and possibly GSSAPI), your entire session will be
 encrypted and invisible to those teeming network snoops. It is the best
 option if you have it. To use it, you must have the Cyrus SASL library
-installed on your system and compile mutt with the --with-sasl flag.
+installed on your system and compile Mutt with the --with-sasl flag.
 
 
 
@@ -6375,7 +6971,7 @@ a password is needed.
 
 $imap_authenticators - a colon-delimited list of IMAP
 authentication methods to try, in the order you wish to try them. If
-specified, this overrides mutt's default (attempt everything, in the order
+specified, this overrides Mutt's default (attempt everything, in the order
 listed above).
 
 
@@ -6391,15 +6987,15 @@ listed above).
 
 
 Besides supporting traditional mail delivery through a
-sendmail-compatible program, mutt supports delivery through SMTP if it
+sendmail-compatible program, Mutt supports delivery through SMTP if it
 was configured and built with --enable-smtp.
 
 
 
 If the configuration variable
-$smtp_url is set, mutt
+$smtp_url is set, Mutt
 will contact the given SMTP server to deliver messages; if it is unset,
-mutt will use the program specified by $sendmail.
+Mutt will use the program specified by $sendmail.
 
 
 
@@ -6410,27 +7006,41 @@ For details on the URL syntax, please see .
 The built-in SMTP support supports encryption (the smtps protocol
 using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms
 for SASL are specified in $smtp_authenticators
-defaulting to an empty list which makes mutt try all available methods
+defaulting to an empty list which makes Mutt try all available methods
 from most-secure to least-secure.
 
 
 
 
 
-Managing multiple accounts
+Managing Multiple Accounts
+
+
+Usage:
+
+
+
+account-hook
+
+pattern
+
+
+command
+
+
 
 
 If you happen to have accounts on multiple IMAP, POP and/or SMTP servers,
 you may find managing all the authentication settings inconvenient and
-error-prone. The account-hook command may help. This hook works like
-folder-hook but is invoked whenever you access a remote mailbox
+error-prone. The account-hook command may help. This hook works like
+folder-hook but is invoked whenever Mutt needs to access a remote mailbox
 (including inside the folder browser), not just when you open the
-mailbox which includes (for example) polling for new mail, storing Fcc
+mailbox. This includes (for example) polling for new mail, storing Fcc
 messages and saving messages to a folder. As a consequence,
-account-hook should only be used to set connection-related settings such
+account-hook should only be used to set connection-related settings such
 as passwords or tunnel commands but not settings such as sender
 address or name (because in general it should be considered unpredictable
-which account-hook was last used).
+which account-hook was last used).
 
 
 
@@ -6444,10 +7054,49 @@ account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
 account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
 
 
+
+To manage multiple accounts with, for example, different values of
+$record or sender addresses,
+folder-hook
+has to be be used together with
+the mailboxes command.
+
+
+
+Managing multiple accounts
+
+mailboxes imap://user@host1/INBOX
+folder-hook imap://user@host1/ 'set folder=imap://host1/ ; set record=+INBOX/Sent'
+
+mailboxes imap://user@host2/INBOX
+folder-hook imap://user@host2/ 'set folder=imap://host2/ ; set record=+INBOX/Sent'
+
+
+
+
+In example
+ the folders are defined using
+mailboxes so Mutt polls them for new
+mail. Each folder-hook triggers when
+one mailbox below each IMAP account is opened and sets
+$folder to the account's root
+folder. Next, it sets $record to
+the INBOX/Sent folder below the newly
+set $folder. Please notice that the
+value the +
+mailbox shortcut refers to depends on
+the current value
+of $folder and therefore has to be set
+separatedly per account. Setting other values
+like $from
+or $signature is analogous to setting
+$record.
+
+
 
 
 
-Local caching
+Local Caching
 
 
 Mutt contains two types of local caching: (1)
@@ -6457,12 +7106,12 @@ so-called body caching which are both described in this section.
 
 
 Header caching is optional as it depends on external libraries, body
-caching is always enabled if mutt is compiled with POP and/or IMAP
+caching is always enabled if Mutt is compiled with POP and/or IMAP
 support as these use it (body caching requires no external library).
 
 
 
-Header caching
+Header Caching
 
 
 Mutt provides optional support for caching message headers for the
@@ -6489,28 +7138,10 @@ result in lower performance), but one file per folder if it points
 to a directory.
 
 
-
-For the one-file-per-folder case, database files for remote folders
-will be named according to their URL while database files for local
-folders will be named by the MD5 checksums of their path. These database
-files may be safely removed if a system is short on space. You
-can compute the name of the header cache file for a particular local folder
-through a command like the following:
-
-
-
-$ printf '%s' '/path/to/folder' | md5sum
-
-
-
-The md5sum command may also be
-named md5, depending on your operating system.
-
-
 
 
 
-Body caching
+Body Caching
 
 
 Both cache methods can be combined using the same directory for storage
@@ -6520,7 +7151,7 @@ manual maintenance tasks.
 
 
 
-In addition to caching message headers only, mutt can also cache
+In addition to caching message headers only, Mutt can also cache
 whole message bodies. This results in faster display of messages
 for POP and IMAP folders because messages usually have to be
 downloaded only once.
@@ -6529,17 +7160,12 @@ downloaded only once.
 
 For configuration, the variable $message_cachedir must point to a
-directory. There, mutt will create a hierarchy of subdirectories
+directory. There, Mutt will create a hierarchy of subdirectories
 named like: proto:user@hostname where
 proto is either pop or imap. Within
-there for each folder, mutt stores messages in single files (just
-like Maildir) so that with manual symlink creation these cache
-directories can be examined with mutt as read-only Maildir folders.
-
-
-
+there for each folder, Mutt stores messages in single files.
 All files can be removed as needed if the consumed disk space
-becomes an issue as mutt will silently fetch missing items again.
+becomes an issue as Mutt will silently fetch missing items again.
 
 
 
@@ -6555,12 +7181,12 @@ disk space freed by removing messages is re-used.
 
 
 
-For body caches, mutt can keep the local cache in sync with the
+For body caches, Mutt can keep the local cache in sync with the
 remote mailbox if the
 $message_cache_clean
 variable is set. Cleaning means to remove messages from the cache which
 are no longer present in the mailbox which only happens when other mail
-clients or instances of mutt using a different body cache location
+clients or instances of Mutt using a different body cache location
 delete messages (Mutt itself removes deleted messages from the cache
 when syncing a mailbox). As cleaning can take a noticeable amount of time,
 it should not be set in general but only occasionally.
@@ -6571,7 +7197,7 @@ it should not be set in general but only occasionally.
 
 
 
-Exact address generation
+Exact Address Generation
 
 
 Mutt supports the Name <user@host> address syntax for reading and
@@ -6584,13 +7210,187 @@ for the latter syntax. EXACT_ADDRESS in the output of
 
 
 
+
+Sending Anonymous Messages via Mixmaster
+
+
+You may also have compiled Mutt to co-operate with Mixmaster, an
+anonymous remailer.  Mixmaster permits you to send your messages
+anonymously using a chain of remailers. Mixmaster support in Mutt is for
+mixmaster version 2.04 (beta 45 appears to be the latest) and 2.03.
+It does not support earlier versions or the later so-called version 3 betas,
+of which the latest appears to be called 2.9b23.
+
+
+
+To use it, you'll have to obey certain restrictions.  Most
+important, you cannot use the Cc and Bcc headers.  To tell
+Mutt to use mixmaster, you have to select a remailer chain, using
+the mix function on the compose menu.
+
+
+
+The chain selection screen is divided into two parts.  In the
+(larger) upper part, you get a list of remailers you may use.  In
+the lower part, you see the currently selected chain of remailers.
+
+
+
+You can navigate in the chain using the <chain-prev> and
+<chain-next> functions, which are by default bound to the left
+and right arrows and to the h and l keys (think vi
+keyboard bindings).  To insert a remailer at the current chain
+position, use the <insert> function.  To append a remailer behind
+the current chain position, use <select-entry> or <append>.
+You can also delete entries from the chain, using the corresponding
+function.  Finally, to abandon your changes, leave the menu, or
+<accept> them pressing (by default) the Return key.
+
+
+
+Note that different remailers do have different capabilities,
+indicated in the %c entry of the remailer menu lines (see
+$mix_entry_format).  Most important is
+the middleman capability, indicated by a capital M: This
+means that the remailer in question cannot be used as the final
+element of a chain, but will only forward messages to other
+mixmaster remailers.  For details on the other capabilities, please
+have a look at the mixmaster documentation.
+
+
+
+
+
+
+
+Security Considerations
+
+
+First of all, Mutt contains no security holes included by intention but
+may contain unknown security holes. As a consequence, please run Mutt
+only with as few permissions as possible. Especially, do not run Mutt as
+the super user.
+
+
+
+When configuring Mutt, there're some points to note about secure setups
+so please read this chapter carefully.
+
+
+
+Passwords
+
+
+Although Mutt can be told the various passwords for accounts, please
+never store passwords in configuration files. Besides the fact that the
+system's operator can always read them, you could forget to mask it out
+when reporting a bug or asking for help via a mailing list. Even worse,
+your mail including your password could be archived by internet search
+engines, mail-to-news gateways etc. It may already be too late before
+you notice your mistake.
+
+
+
+
+
+Temporary Files
+
+
+Mutt uses many temporary files for viewing messages, verifying digital
+signatures, etc. As long as being used, these files are visible by other
+users and maybe even readable in case of misconfiguration.  Also, a
+different location for these files may be desired which can be changed
+via the $tmpdir variable.
+
+
+
+
+
+Information Leaks
+
+
+Message-Id: headers
+
+
+Message-Id: headers contain a local part that is to be created in a
+unique fashion. In order to do so, Mutt will leak some
+information to the outside world when sending messages: the generation
+of this header includes a step counter which is increased (and rotated)
+with every message sent. In a longer running mutt session, others can
+make assumptions about your mailing habbits depending on the number of
+messages sent. If this is not desired, the header can be manually
+provided using $edit_headers (though not
+recommended).
+
+
+
+
+
+<literal>mailto:</literal>-style Links
+
+
+As Mutt be can be set up to be the mail client to handle
+mailto: style links in websites, there're security
+considerations, too. Arbitrary header fields can be embedded in these
+links which could override existing header fields or attach arbitrary
+files using the Attach:
+psuedoheader. This may be problematic if the $edit-headers variable is
+unset, i.e. the user doesn't want to see header
+fields while editing the message and doesn't pay enough attention to the
+compose menu's listing of attachments.
+
+
+
+For example, following a link like
+
+
+
+mailto:joe@host?Attach=~/.gnupg/secring.gpg
+
+
+will send out the user's private gnupg keyring to
+joe@host if the user doesn't follow the information
+on screen carefully enough.
+
+
+
+
+
+
+
+External Applications
+
+
+Mutt in many places has to rely on external applications or for
+convenience supports mechanisms involving external applications.
+
+
+
+One of these is the mailcap mechanism as defined by
+RfC1524. Details about a secure use of the mailcap mechanisms is given
+in .
+
+
+
+Besides the mailcap mechanism, Mutt uses a number of other external
+utilities for operation, for example to provide crypto support, in
+backtick expansion in configuration files or format string filters.  The
+same security considerations apply for these as for tools involved via
+mailcap.
+
+
+
+
 
 
+
 
-Performance tuning
+Performance Tuning
 
 
-Reading and writing mailboxes
+Reading and Writing Mailboxes
 
 
 Mutt's performance when reading mailboxes can be improved in two ways:
@@ -6601,11 +7401,10 @@ Mutt's performance when reading mailboxes can be improved in two ways:
 
 
 For remote folders (IMAP and POP) as well as folders using
-one-file-per message storage (Maildir and MH), mutt's
+one-file-per message storage (Maildir and MH), Mutt's
 performance can be greatly improved using
 header caching.
-Using a single database per folder may further increase
-performance.
+using a single database per folder.
 
 
 
@@ -6614,7 +7413,7 @@ performance.
 Mutt provides the $read_inc
 and $write_inc
 variables to specify at which rate to update progress
-counters. If these values are too low, mutt may spend more
+counters. If these values are too low, Mutt may spend more
 time on updating the progress counter than it spends on
 actually reading/writing folders.
 
@@ -6623,7 +7422,7 @@ For example, when opening a maildir folder with a few
 thousand messages, the default value for
 $read_inc
 may be too low. It can be tuned on on a folder-basis using
-folder-hooks:
+folder-hooks:
 
 
 
@@ -6648,29 +7447,29 @@ actually send to the terminal using the
 
 
 
-Reading messages from remote folders
+Reading Messages from Remote Folders
 
 
 Reading messages from remote folders such as IMAP an POP can be
-slow especially for large mailboxes since mutt only caches a very
+slow especially for large mailboxes since Mutt only caches a very
 limited number of recently viewed messages (usually 10) per
 session (so that it will be gone for the next session.)
 
 
 
 To improve performance and permanently cache whole messages,
-please refer to mutt's so-called
+please refer to Mutt's so-called
 body caching for details.
 
 
 
 
 
-Searching and limiting
+Searching and Limiting
 
 
 When searching mailboxes either via a search or a limit action, for
-some patterns mutt distinguishes between regular expression and string
+some patterns Mutt distinguishes between regular expression and string
 searches. For regular expressions, patterns are prefixed with
 ˜ and with = for string searches.
 
@@ -6692,9 +7491,9 @@ message bodies since a larger amount of input has to be searched.
 
 
 
-Please note that string search is an exact case-sensitive search
-while a regular expression search with only lower-case letters performs
-a case-insensitive search.
+As for regular expressions, a lower case string search pattern makes
+Mutt perform a case-insensitive search except for IMAP (because for IMAP
+Mutt performs server-side searches which don't support case-insensivity).
 
 
 
@@ -6705,7 +7504,7 @@ a case-insensitive search.
 Reference
 
 
-Command line options
+Command-Line Options
 
 
 Running mutt with no arguments will make Mutt attempt to read your spool
@@ -6724,7 +7523,7 @@ to send messages from the command line as well.
 -aattach a file to a message
 -bspecify a blind carbon-copy (BCC) address
 -cspecify a carbon-copy (Cc) address
--Dprint the value of all mutt variables to stdout
+-Dprint the value of all Mutt variables to stdout
 -especify a config command to be run after initialization files are read
 -fspecify a mailbox to load
 -Fspecify an alternate file to read initialization commands
@@ -6739,9 +7538,9 @@ to send messages from the command line as well.
 -sspecify a subject (enclose in quotes if it contains spaces)
 -vshow version number and compile-time definitions
 -xsimulate the mailx(1) compose mode
--yshow a menu containing the files specified by the mailboxes command
+-yshow a menu containing the files specified by the mailboxes command
 -zexit immediately if there are no messages in the mailbox
--Zopen the first folder with new message,exit immediately if none
+-Zopen the first folder with new message, exit immediately if none
 
 
 
@@ -6774,9 +7573,6 @@ To compose a new message
 
 muttrc
 
-
-file
-
 
 address
 
@@ -6787,15 +7583,12 @@ To compose a new message
 subject
 
 
-
+
 file
+
+--
 
---
-
-
-address
-
-
+
 address
 
 
@@ -6805,22 +7598,36 @@ Mutt also supports a batch mode to send prepared messages.  Simpl
 input from the file you wish to send.  For example,
 
 
-
-mutt -s "data set for run #2" professor@bigschool.edu
-< ˜/run2.dat
-
+
+mutt -s "data set for run #2" professor@bigschool.edu < ˜/run2.dat
 
 
-This command will send a message to professor@bigschool.edu with a subject
+will send a message to <professor@bigschool.edu> with a subject
 of data set for run #2.  In the body of the message will be the contents
 of the file ˜/run2.dat.
 
 
 
-All files passed with -a file will be attached as a MIME
-part to the message. To attach several files, use -- to separate files and
-recipient addresses: mutt -a *.png -- some@one.org
+All files passed with -a file will be attached as a MIME
+part to the message. To attach a single or several files, use -- to separate files and
+recipient addresses:
+
+
+
+mutt -a image.png -- some@one.org
+
+
+or
+
+
+
+mutt -a *.png -- some@one.org
+
+
+
+The -a option must be last in the option list.
 
+
 
 
 
@@ -6828,7 +7635,7 @@ recipient addresses: mutt -a *.png -- some@one.org
 Configuration Commands
 
 
-The following are the commands understood by mutt.
+The following are the commands understood by Mutt:
 
 
 
@@ -6859,11 +7666,7 @@ The following are the commands understood by mutt.
 
 address
 
-
-
 
-
-
 unalias
 
 
@@ -6893,11 +7696,7 @@ The following are the commands understood by mutt.
 
 regexp
 
-
-
 
-
-
 unalternates
 
 
@@ -6923,11 +7722,7 @@ The following are the commands understood by mutt.
 
 mimetype
 
-
-
 
-
-
 unalternative-order
 
 
@@ -6940,6 +7735,26 @@ The following are the commands understood by mutt.
 
 
 
+
+
+attachments
+
+{ + | - }disposition
+
+
+mime-type
+
+
+unattachments
+
+{ + | - }disposition
+
+
+mime-type
+
+
+
+
 
 
 auto-view
@@ -6949,11 +7764,7 @@ The following are the commands understood by mutt.
 
 mimetype
 
-
-
-
 
-
 unauto-view
 
 
@@ -6995,7 +7806,7 @@ The following are the commands understood by mutt.
 
 
 
-iconv-hook
+iconv-hook
 
 charset
 
@@ -7017,8 +7828,7 @@ The following are the commands understood by mutt.
 
 background
 
-
-
+
 color
 
 
@@ -7037,8 +7847,7 @@ The following are the commands understood by mutt.
 
 regexp
 
-
-
+
 color
 
 
@@ -7052,18 +7861,39 @@ The following are the commands understood by mutt.
 
 pattern
 
-
-
 
-
-
 uncolor
+
 
 
 
+
+
+
+
+
+
+
+
+
+*
+
 
+pattern
+
+
+
+
+
+
+
+crypt-hook
+
 pattern
 
+
+keyid
+
 
 
 
@@ -7132,11 +7962,7 @@ The following are the commands understood by mutt.
 expr
 
 
-
-
 
-
-
 ungroup
 
 
@@ -7167,11 +7993,7 @@ The following are the commands understood by mutt.
 
 header
 
-
-
 
-
-
 unhdr_order
 
 
@@ -7193,11 +8015,7 @@ The following are the commands understood by mutt.
 
 pattern
 
-
-
 
-
-
 unignore
 
 
@@ -7223,11 +8041,7 @@ The following are the commands understood by mutt.
 
 regexp
 
-
-
 
-
-
 unlists
 
 
@@ -7271,11 +8085,7 @@ The following are the commands understood by mutt.
 
 mailbox
 
-
-
 
-
-
 unmailboxes
 
 
@@ -7321,11 +8131,7 @@ The following are the commands understood by mutt.
 
 mimetype
 
-
-
 
-
-
 unmime-lookup
 
 
@@ -7347,8 +8153,7 @@ The following are the commands understood by mutt.
 
 attribute
 
-
-
+
 mono
 
 
@@ -7364,8 +8169,7 @@ The following are the commands understood by mutt.
 
 regexp
 
-
-
+
 mono
 
 
@@ -7376,15 +8180,19 @@ The following are the commands understood by mutt.
 
 pattern
 
-
-
 
-
-
 unmono
+
 
 
 
+
+
+
+
+
+
+
 
 
 *
@@ -7402,11 +8210,7 @@ The following are the commands understood by mutt.
 
 string
 
-
-
 
-
-
 unmy_hdr
 
 
@@ -7419,18 +8223,6 @@ The following are the commands understood by mutt.
 
 
 
-
-
-crypt-hook
-
-pattern
-
-
-keyid
-
-
-
-
 
 
 push
@@ -7440,18 +8232,6 @@ The following are the commands understood by mutt.
 
 
 
-
-
-reset
-
-variable
-
-
-variable
-
-
-
-
 
 
 save-hook
@@ -7473,11 +8253,7 @@ The following are the commands understood by mutt.
 
 value
 
-
-
 
-
-
 unscore
 
 
@@ -7541,12 +8317,16 @@ The following are the commands understood by mutt.
 variable=value
 
 
-
-
-
+
+
+toggle
+
+variable
+
+
+variable
+
 
-
-
 unset
 
 variable
@@ -7554,6 +8334,14 @@ The following are the commands understood by mutt.
 
 variable
 
+
+reset
+
+variable
+
+
+variable
+
 
 
 
@@ -7575,11 +8363,7 @@ The following are the commands understood by mutt.
 
 format
 
-
-
 
-
-
 nospam
 
 
@@ -7605,11 +8389,7 @@ The following are the commands understood by mutt.
 
 regexp
 
-
-
 
-
-
 unsubscribe
 
 
@@ -7626,18 +8406,6 @@ The following are the commands understood by mutt.
 
 
 
-
-
-toggle
-
-variable
-
-
-variable
-
-
-
-
 
 
 unhook
@@ -7657,4 +8425,4 @@ The following are the commands understood by mutt.
 
 
 
-Configuration variables
+Configuration Variables
diff --git a/doc/manual.xml.tail b/doc/manual.xml.tail
index 4a69ae3..c2c955f 100644
--- a/doc/manual.xml.tail
+++ b/doc/manual.xml.tail
@@ -92,7 +92,7 @@ The following people have been very helpful to the development of Mutt:
 
 
 
-About this document
+About This Document
 
 
 This document was written in DocBook,
diff --git a/doc/mbox.man b/doc/mbox.man
index 1980d0d..09eaf91 100644
--- a/doc/mbox.man
+++ b/doc/mbox.man
@@ -60,15 +60,15 @@ line; the second (\fBMBOXRD\fP) also quotes already quoted "From "
 lines by prepending a '>' (i.e. ">From ", ">>From ", ...). The later
 has the advantage that lines like
 .IP "" 1
->From the command line you can use the '-p' option
+>From the command line you can use the '\-p' option
 .PP
 aren't dequoted wrongly as a \fBMBOXRD\fP-MDA would turn the line
 into
 .IP "" 1
->>From the command line you can use the '-p' option
+>>From the command line you can use the '\-p' option
 .PP
 before storing it. Besides \fBMBOXO\fP and \fBMBOXRD\fP there is also
-\fBMBOXCL\fP which is \fBMBOXO\fP with a "Content-Length:"-field with the
+\fBMBOXCL\fP which is \fBMBOXO\fP with a "Content-Length:"\-field with the
 number of bytes in the message body; some MUAs (like
 .BR mutt (1))
 do automatically transform \fBMBOXO\fP mailboxes into \fBMBOXCL\fP ones when
diff --git a/doc/mimesupport.html b/doc/mimesupport.html
index 44fda22..21fcf0f 100644
--- a/doc/mimesupport.html
+++ b/doc/mimesupport.html
@@ -1,27 +1,31 @@
 
 
-Chapter 5. Mutt's MIME Support
Chapter 5. Mutt's MIME Support
Prev   Next
Chapter 5. Mutt's MIME Support
Table of Contents
1. Using MIME in Mutt
1.1. Viewing MIME messages in the pager
1.2. The Attachment Menu
1.3. The Compose Menu
2. MIME Type configuration with mime.types
3. MIME Viewer configuration with mailcap
3.1. The Basics of the mailcap file
3.2. Secure use of mailcap
3.3. Advanced mailcap Usage
3.4. Example mailcap files
4. MIME Autoview
5. MIME Multipart/Alternative
6. Attachment Searching and Counting
7. MIME Lookup

+    
Chapter 5. Mutt's MIME Support
Prev   Next
Chapter 5. Mutt's MIME Support
Table of Contents
1. Using MIME in Mutt
1.1. Viewing MIME Messages in the Pager
1.2. The Attachment Menu
1.3. The Compose Menu
2. MIME Type Configuration with mime.types
3. MIME Viewer Configuration with Mailcap
3.1. The Basics of the Mailcap File
3.2. Secure Use of Mailcap
3.3. Advanced Mailcap Usage
3.4. Example Mailcap Files
4. MIME Autoview
5. MIME Multipart/Alternative
6. Attachment Searching and Counting
7. MIME Lookup

 Quite a bit of effort has been made to make Mutt the premier text-mode
 MIME MUA.  Every effort has been made to provide the functionality that
 the discerning MIME user requires, and the conformance to the standards
@@ -34,7 +38,7 @@ the external commands to use for handling specific MIME types.
 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.
-
1.1. Viewing MIME messages in the pager

+
1.1. Viewing MIME Messages in the Pager

 When you select a message from the index and view it in the pager, Mutt
 decodes the message to a text representation.  Mutt internally supports
 a number of MIME types, including text/plain, text/enriched,
@@ -56,12 +60,12 @@ If Mutt cannot deal with a MIME type, it will display a message like:
 
 [-- image/gif is unsupported (use 'v' to view this part) --]
 
1.2. The Attachment Menu

-The default binding for view-attachments is `v', which displays the
+The default binding for <view-attachments> is “v”, which displays the
 attachment menu for a message.  The attachment menu displays a list of
 the attachments in a message.  From the attachment menu, you can save,
 print, pipe, delete, and view attachments.  You can apply these
 operations to a group of attachments at once, by tagging the attachments
-and by using the “tag-prefix” operator.  You can also reply to the
+and by using the <tag-prefix> operator.  You can also reply to the
 current message from this menu, and only the current attachment (or the
 attachments tagged) will be quoted in your reply.  You can view
 attachments as text, or view them using the mailcap viewer definition.
@@ -88,23 +92,23 @@ Attachments appear as follows:

The '-' denotes that Mutt will delete the file after sending (or postponing, or canceling) 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 the edit-type command +<toggle-unlink> command (default: u). The next field is the MIME +content-type, and can be changed with the <edit-type> command (default: ^T). The next field is the encoding for the attachment, which allows a binary message to be encoded for transmission on 7bit -links. It can be changed with the edit-encoding command +links. It can be changed with the <edit-encoding> command (default: ^E). The next field is the size of the attachment, rounded to kilobytes or megabytes. The next field is the filename, -which can be changed with the rename-file command (default: R). +which can be changed with the <rename-file> command (default: R). The final field is the description of the attachment, and can be -changed with the edit-description command (default: d). -

2. MIME Type configuration with mime.types

+changed with the <edit-description> command (default: d). +

2. MIME Type Configuration with mime.types

When you add an attachment to your mail message, Mutt searches your -personal mime.types file at ${HOME}/.mime.types, and then -the system mime.types file at /usr/local/share/mutt/mime.types or +personal mime.types file at ${HOME}/.mime.types, and then +the system mime.types file at /usr/local/share/mutt/mime.types or /etc/mime.types

-The mime.types file consist of lines containing a MIME type and a space +The mime.types file consist of lines containing a MIME type and a space separated list of extensions. For example: 

 application/postscript          ps eps
@@ -119,23 +123,23 @@ 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
 as text/plain.  If the file contains binary information, then Mutt will
 mark it as application/octet-stream.  You can change the MIME
-type that Mutt assigns to an attachment by using the edit-type
+type that Mutt assigns to an attachment by using the <edit-type>
 command from the compose menu (default: ^T). The MIME type is actually a
 major mime type followed by the sub-type, separated by a '/'. 6 major
 types: application, text, image, video, audio, and model have been approved
 after various internet discussions. Mutt recognizes all of these if the
-appropriate entry is found in the mime.types file. It also recognizes other
+appropriate entry is found in the mime.types file. It also recognizes other
 major mime types, such as the chemical type that is widely used in the
 molecular modeling community to pass molecular data in various forms to
 various molecular viewers. Non-recognized mime types should only be used
 if the recipient of the message is likely to be expecting such attachments.
-

3. MIME Viewer configuration with mailcap

+

3. MIME Viewer Configuration with Mailcap

Mutt supports RFC 1524 MIME Configuration, in particular the Unix specific format specified in Appendix A of RFC 1524. This file format is commonly referred to as the mailcap format. Many MIME compliant programs utilize the mailcap format, allowing you to specify handling for all MIME types in one place for all programs. Programs known to -use this format include Netscape, XMosaic, lynx and metamail. +use this format include Firefox, lynx and metamail.

In order to handle various MIME types that Mutt can not handle internally, Mutt parses a series of external configuration files to @@ -144,7 +148,7 @@ is a colon delimited list containing the following files:

  1. $HOME/.mailcap

  2. $PKGDATADIR/mailcap

  3. $SYSCONFDIR/mailcap

  4. /etc/mailcap

  5. /usr/etc/mailcap

  6. /usr/local/etc/mailcap

where $HOME is your home directory. The $PKGDATADIR and the -$SYSCONFDIR directories depend on where mutt +$SYSCONFDIR directories depend on where Mutt is installed: the former is the default for shared data, the latter for system configuration files.

@@ -156,7 +160,7 @@ mutt -nF /dev/null -Q mailcap_path In particular, the metamail distribution will install a mailcap file, usually as /usr/local/etc/mailcap, which contains some baseline entries. -

3.1. The Basics of the mailcap file

+

3.1. The Basics of the Mailcap File

A mailcap file consists of a series of lines which are comments, blank, or definitions.

@@ -222,13 +226,13 @@ text/html; lynx %s text/*; more

This is the simplest form of a mailcap file. -

3.2. Secure use of mailcap

+

3.2. Secure Use of Mailcap

The interpretation of shell meta-characters embedded in MIME parameters can lead to security problems in general. Mutt tries to quote parameters in expansion of %s syntaxes properly, and avoids risky characters by -substituting them, see the $mailcap_sanitize variable. +substituting them, see the $mailcap_sanitize variable.

-Although mutt's procedures to invoke programs with mailcap seem to be +Although Mutt's procedures to invoke programs with mailcap seem to be safe, there are other applications parsing mailcap, maybe taking less care of it. Therefore you should pay attention to the following rules:

@@ -248,7 +252,7 @@ since it is not itself subject to any further expansion): 

 text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
         && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
-

3.3. Advanced mailcap Usage

3.3.1. Optional Fields

+

3.3. Advanced Mailcap Usage

3.3.1. Optional Fields

In addition to the required content-type and view command fields, you can add semi-colon ';' separated fields to set flags and other options. Mutt recognizes the following optional fields: @@ -265,11 +269,11 @@ 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.

needsterminal

-Mutt uses this flag when viewing attachments with auto_view, in order to decide whether it should honor the setting -of the $wait_key variable or +Mutt uses this flag when viewing attachments with auto_view, in order to decide whether it should honor the setting +of the $wait_key variable or not. When an attachment is viewed using an interactive program, and the corresponding mailcap entry has a needsterminal flag, Mutt will use -$wait_key and the exit status +$wait_key and the exit status of the program to decide if it will ask you to press a key after the external program has exited. In all other situations it will not prompt you for a key. @@ -279,7 +283,7 @@ specific MIME type. Mutt supports this from the compose menu.

composetyped=<command>

This flag specifies the command to use to create a new attachment of a specific MIME type. This command differs from the compose command in -that mutt will expect standard MIME headers on the data. This can be +that Mutt will expect standard MIME headers on the data. This can be used to specify parameters, filename, description, etc. for a new attachment. Mutt supports this from the compose menu.

print=<command>

@@ -308,14 +312,14 @@ then the test failed, and Mutt continues searching for the right entry. Note that the content-type must match before Mutt performs the test. For example: 

-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
+text/html; firefox -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 display the -text/html object. If RunningX doesn't return 0, then Mutt will go on -to the next entry and use lynx to display the text/html object. +RunningX returns 0, then Mutt will call firefox to display the +text/html object. If RunningX doesn't return 0, then Mutt will go on +to the next entry and use lynx to display the text/html object.

3.3.2. Search Order

When searching for an entry in the mailcap file, Mutt will search for the most useful entry for its purpose. For instance, if you are @@ -330,24 +334,24 @@ image/gif; ; print= anytopnm %s | pnmtops | lpr; \ Mutt will skip the image/* entry and use the image/gif entry with the print command.

-In addition, you can use this with auto_view +In addition, you can use this with auto_view to denote two commands for viewing an attachment, one to be viewed automatically, the other to be viewed interactively from the attachment menu. In addition, you 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;      firefox -remote 'openURL(%s)' ; test=RunningX
 text/html;      lynx %s; nametemplate=%s.html
 text/html;      lynx -dump %s; nametemplate=%s.html; copiousoutput

-For auto_view, Mutt will choose the third +For auto_view, 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 program returns non-zero, Mutt will use the second entry for interactive viewing.

3.3.3. Command Expansion

The various commands defined in the mailcap files are passed to the -/bin/sh shell using the system() function. Before the +/bin/sh shell using the system(3) function. Before the command is passed to /bin/sh -c, it is parsed to expand various special parameters with information from Mutt. The keywords Mutt expands are: @@ -379,15 +383,15 @@ 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 messages, which is handled internally by Mutt. -

3.4. Example mailcap files

+

3.4. Example Mailcap Files

This mailcap file is fairly simple and standard: 

 # I'm always running X :)
 video/*;        xanim %s > /dev/null
 image/*;        xv %s > /dev/null
 
-# I'm always running netscape (if my computer had more memory, maybe)
-text/html;      netscape -remote 'openURL(%s)'
+# I'm always running firefox (if my computer had more memory, maybe)
+text/html;      firefox -remote 'openURL(%s)'

This mailcap file shows quite a number of examples: 

@@ -395,12 +399,12 @@ This mailcap file shows quite a number of examples:
 # send that to /dev/null so I don't see it
 video/*;        xanim %s > /dev/null
 
-# Send html to a running netscape by remote
-text/html;      netscape -remote 'openURL(%s)'; test=RunningNetscape
+# Send html to a running firefox by remote
+text/html;      firefox -remote 'openURL(%s)'; test=RunningFirefox
 
-# If I'm not running netscape but I am running X, start netscape on the
+# If I'm not running firefox but I am running X, start firefox on the
 # object
-text/html;      netscape %s; test=RunningX
+text/html;      firefox %s; test=RunningX
 
 # Else use lynx to view it as text
 text/html;      lynx %s
@@ -411,7 +415,7 @@ text/html;      lynx -dump %s; copiousoutput
 # I use enscript to print text in two columns to a page
 text/*;         more %s; print=enscript -2Gr %s
 
-# Netscape adds a flag to tell itself to view jpegs internally
+# Firefox adds a flag to tell itself to view jpegs internally
 image/jpeg;xv %s; x-mozilla-flags=internal
 
 # Use xv to view images if I'm running X
@@ -427,6 +431,16 @@ pbmtoascii -1x2 ) 2>&1 ; copiousoutput
 # Send excel spreadsheets to my NT box
 application/ms-excel; open.pl %s

4. MIME Autoview

+Usage: +

auto-view +mimetype + [ +mimetype +...]
unauto-view { +* + | +mimetype +... }

In addition to explicitly telling Mutt to view an attachment with the MIME viewer defined in the mailcap file, Mutt has support for automatically viewing MIME attachments while in the pager. @@ -436,10 +450,9 @@ To work, you must define a viewer in the mailcap file which uses the Usually, you also use the entry to convert the attachment to a text representation which you can view in the pager.

-You then use the auto_view muttrc command to list the -content-types that you wish to view automatically. -

-For instance, if you set auto_view to: +You then use the auto_view .muttrc command to list the +content-types that you wish to view automatically. For instance, if you +set it to: 

 auto_view text/html application/x-gunzip \
   application/postscript image/gif application/x-tar-gz
@@ -454,47 +467,53 @@ application/x-gunzip;   gzcat; copiousoutput
 application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
 application/postscript; ps2ascii %s; copiousoutput

-“unauto_view” can be used to remove previous entries from the autoview list. -This can be used with message-hook to autoview messages based on size, etc. -“unauto_view *” will remove all previous entries. +unauto_view can be used to remove previous entries from the autoview list. +This can be used with message-hook to autoview messages based on size, etc. +“unauto_view *” will remove all previous entries.

5. MIME Multipart/Alternative

Mutt has some heuristics for determining which attachment of a -multipart/alternative type to display. First, mutt will check the -alternative_order list to determine if one of the available types -is preferred. The alternative_order list consists of a number of -mimetypes in order, including support for implicit and explicit -wildcards, for example: +multipart/alternative type to display. First, Mutt will check the +alternative_order list +to determine if one of the available types is preferred. It consists of +a number of 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 +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.

-To remove a MIME type from the alternative_order list, use the -unalternative_order command. +To remove a MIME type from the alternative_order list, use the +unalternative_order command.

6. Attachment Searching and Counting

If you ever lose track of attachments in your mailboxes, Mutt's attachment-counting and -searching support might be for you. You can make your message index display the number of qualifying attachments in each message, or search for messages by attachment count. You also can configure what kinds of attachments qualify for this feature with the -attachments and unattachments commands. +attachments and unattachments commands.

-In order to provide this information, mutt needs to fully MIME-parse +In order to provide this information, Mutt needs to fully MIME-parse all messages affected first. This can slow down operation especially for remote mail folders such as IMAP because all messages have to be downloaded first regardless whether the user really wants to view them or not.

The syntax is: -

-attachments   {+|-}disposition mime-type
-unattachments {+|-}disposition mime-type
-attachments   ?
-

-Disposition is the attachment's Content-disposition type -- either +

attachments +{ + | - }disposition + +mime-type +
unattachments +{ + | - }disposition + +mime-type +
attachments +? +

+disposition is the attachment's Content-Disposition type — either inline or attachment. You can abbreviate this to I or A.

@@ -504,7 +523,7 @@ type to qualify. If it's a -, you're saying that this disposition and MIME type is an exception to previous + rules. There are examples below of how this is useful.

-Mime-type is, unsurprisingly, the MIME type of the attachment you want +mime-type is, unsurprisingly, the MIME type of the attachment you want to affect. A MIME type is always of the format major/minor, where major describes the broad category of document you're looking at, and minor describes the specific type within that category. The major @@ -512,11 +531,11 @@ part of mime-type must be literal text (or the special token “*/.*” matches any MIME type.)

-The MIME types you give to the attachments directive are a kind of -pattern. When you use the attachments directive, the patterns you -specify are added to a list. When you use unattachments, the pattern +The MIME types you give to the attachments directive are a kind of +pattern. When you use the attachments directive, the patterns you +specify are added to a list. When you use unattachments, the pattern is removed from the list. The patterns are not expanded and matched -to specific MIME types at this time -- they're just text in a list. +to specific MIME types at this time — they're just text in a list. They're only matched when actually evaluating a message.

Some examples might help to illustrate. The examples that are not @@ -569,22 +588,32 @@ attachments +I text/plain attachments -A message/external-body attachments -I message/external-body


-Entering the command “attachments ?” +Entering the command “attachments ?” as a command will list your current settings in Muttrc format, so that it can be pasted elsewhere.

7. MIME Lookup

+Usage: +

mime-lookup +mimetype + [ +mimetype +...]
unmime-lookup { +* + | +mimetype +... }

Mutt's mime_lookup list specifies a list of mime-types that should not be treated according to their mailcap entry. This option is designed to -deal with binary types such as application/octet-stream. When an attachment's +deal with binary types such as application/octet-stream. When an attachment's mime-type is listed in mime_lookup, then the extension of the filename will -be compared to the list of extensions in the mime.types file. The mime-type +be compared to the list of extensions in the mime.types file. The mime-type associated with this extension will then be used to process the attachment according to the rules in the mailcap file and according to any other configuration -options (such as auto_view) specified. Common usage would be: +options (such as auto_view) specified. Common usage would be: 

 mime_lookup application/octet-stream application/X-Lotus-Manuscript

-In addition, the unmime_lookup command may be used to disable this feature -for any particular mime-type if it had been set, for example, in a global -muttrc. -

Prev   Next
Chapter 4. Advanced Usage Home Chapter 6. Optional features
+In addition, the unmime_lookup command may be +used to disable this feature for any particular mime-type if it had been +set, for example, in a global .muttrc. +

Prev   Next
Chapter 4. Advanced Usage Home Chapter 6. Optional Features
diff --git a/doc/miscellany.html b/doc/miscellany.html index 2e47100..a1d901b 100644 --- a/doc/miscellany.html +++ b/doc/miscellany.html @@ -1,32 +1,36 @@ -Chapter 9. Miscellany
Chapter 9. Miscellany
Prev   

Chapter 9. Miscellany

Table of Contents

1. Acknowledgements
2. About this document

1. Acknowledgements

+

Chapter 10. Miscellany
Prev   

Chapter 10. Miscellany

Table of Contents

1. Acknowledgements
2. About This Document

1. Acknowledgements

Kari Hurtta co-developed the original MIME parsing code back in the ELM-ME days.

The following people have been very helpful to the development of Mutt: -

2. About this document

+

2. About This Document

This document was written in DocBook, and then rendered using the Gnome XSLT toolkit. -

Prev   
Chapter 8. Reference Home 
+

Prev   
Chapter 9. Reference Home 
diff --git a/doc/mmdf.man b/doc/mmdf.man index fb7b9f0..e14d72b 100644 --- a/doc/mmdf.man +++ b/doc/mmdf.man @@ -42,7 +42,6 @@ Subject: test .br >From what I learned about the MMDF-format: .br -... .br ^A^A^A^A .br @@ -65,7 +64,7 @@ bar In contrast to most other single file mailbox formats like MBOXO and MBOXRD (see .BR mbox (5)) -there is no need to quote/dequote "From "-lines in +there is no need to quote/dequote "From "\-lines in .B MMDF mailboxes as such lines have no special meaning in this format. .PP diff --git a/doc/mutt.css b/doc/mutt.css index cd432be..468bf6c 100644 --- a/doc/mutt.css +++ b/doc/mutt.css @@ -1,19 +1,23 @@ body { margin-left:2%; margin-right:2%; font-family:serif; } .toc, .list-of-tables, .list-of-examples { font-family:sans-serif; } h1, h2, h3, h4, h5, h6 { font-family:sans-serif; } -em.replaceable code { font-family:sans-serif; } p { text-align:justify; } div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; } .email, .email a { font-family:monospace; } -div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; } -div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; } -div.table-contents table th { +div.table-contents table, div.informaltable table { border-collapse:collapse; border:1px solid #c0c0c0; } +div.table-contents table td, div.informaltable td, div.table-contents table th, div.informaltable table th { padding:5px; text-align:left; } +div.table-contents table th, div.informaltable table th { font-family:sans-serif; background:#d0d0d0; font-weight:normal; vertical-align:top; } -pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; } +div.cmdsynopsis { border-left:1px solid #707070; padding-left:5px; } +li div.cmdsynopsis { border-left:none; padding-left:0px; } +pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; margin-left:2%; margin-right:2%; } +div.example p.title { margin-left:2%; } div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; } div.note h3:after { content: ":" } div.note { margin-bottom: 5px; } +strong.command { font-family: monospace; font-weight: normal; } +tr { vertical-align: top; } diff --git a/doc/mutt.man b/doc/mutt.man index b4318c4..18ad76a 100644 --- a/doc/mutt.man +++ b/doc/mutt.man @@ -24,41 +24,39 @@ mutt \- The Mutt Mail User Agent .PP .B mutt [-nRyzZ] -[-e \fIcmd\fP] [-F \fIfile\fP] [-m \fItype\fP] [-f \fIfile\fP] +[\-e \fIcmd\fP] [\-F \fIfile\fP] [\-m \fItype\fP] [\-f \fIfile\fP] .PP .B mutt -[-nx] -[-e \fIcmd\fP] -[-F \fIfile\fP] -[-H \fIfile\fP] -[-i \fIfile\fP] -[-s \fIsubj\fP] -[-b \fIaddr\fP] -[-c \fIaddr\fP] -[\-a \fIfile\fP [...]] -[\-\-] +[\-nx] +[\-e \fIcmd\fP] +[\-F \fIfile\fP] +[\-H \fIfile\fP] +[\-i \fIfile\fP] +[\-s \fIsubj\fP] +[\-b \fIaddr\fP] +[\-c \fIaddr\fP] +[\-a \fIfile\fP [...] \-\-] \fIaddr\fP [...] .PP .B mutt -[-nx] -[-e \fIcmd\fP] -[-F \fIfile\fP] -[-s \fIsubj\fP] -[-b \fIaddr\fP] -[-c \fIaddr\fP] -[\-a \fIfile\fP [...]] -[\-\-] +[\-nx] +[\-e \fIcmd\fP] +[\-F \fIfile\fP] +[\-s \fIsubj\fP] +[\-b \fIaddr\fP] +[\-c \fIaddr\fP] +[\-a \fIfile\fP [...] \-\-] \fIaddr\fP [...] < message .PP .B mutt -[-n] [-e \fIcmd\fP] [-F \fIfile\fP] -p +[\-n] [\-e \fIcmd\fP] [\-F \fIfile\fP] \-p .PP .B mutt -[-n] [-e \fIcmd\fP] [-F \fIfile\fP] -A \fIalias\fP +[\-n] [\-e \fIcmd\fP] [\-F \fIfile\fP] \-A \fIalias\fP .PP .B mutt -[-n] [-e \fIcmd\fP] [-F \fIfile\fP] -Q \fIquery\fP +[\-n] [\-e \fIcmd\fP] [\-F \fIfile\fP] \-Q \fIquery\fP .PP .B mutt -v[v] @@ -82,8 +80,10 @@ text, HTML, and/or PDF format. An expanded version of the given alias is passed to stdout. .IP "-a \fIfile\fP [...]" Attach a file to your message using MIME. -To attach multiple files, separating filenames and recipient addresses with -"\-\-" is mandatory, e.g. \fBmutt \-a img.jpg *.png \-\- addr1 addr2\fP. +When attaching single or multiple files, separating filenames and recipient addresses with +"\-\-" is mandatory, e.g. \fBmutt -a image.jpg \-\- addr1\fP or +\fBmutt \-a img.jpg *.png \-\- addr1 addr2\fP. +The \-a option must be placed at the end of command line options. .IP "-b \fIaddress\fP" Specify a blind-carbon-copy (BCC) recipient .IP "-c \fIaddress\fP" @@ -109,7 +109,7 @@ message. .IP "-i \fIinclude\fP" Specify a file to include into the body of a message. .IP "-m \fItype\fP " -specify a default mailbox type +specify a default mailbox type for newly created folders. .IP "-n" Causes Mutt to bypass the system configuration file. .IP "-p" @@ -132,12 +132,12 @@ Emulate the mailx compose mode. Start Mutt with a listing of all mailboxes specified by the \fImailboxes\fP command. .IP "-z" -When used with -f, causes Mutt not to start if there are no messages in the +When used with \-f, causes Mutt not to start if there are no messages in the mailbox. .IP "-Z" Causes Mutt to open the first mailbox specified by the \fImailboxes\fP command which contains new mail. -.IP "\-\-" +.IP "--" Treat remaining arguments as \fIaddr\fP even if they start with a dash. See also "\-a" above. .SH ENVIRONMENT @@ -151,8 +151,8 @@ Full path of the user's home directory. .IP "MAIL" Full path of the user's spool mailbox. .IP "MAILDIR" -Full path of the user's spool mailbox. Commonly used when the spool -mailbox is a +Full path of the user's spool mailbox if MAIL is unset. Commonly used when the spool +mailbox is a .B maildir (5) folder. .IP "MAILCAPS" diff --git a/doc/muttrc.man.head b/doc/muttrc.man.head index 529f573..6df8c69 100644 --- a/doc/muttrc.man.head +++ b/doc/muttrc.man.head @@ -558,7 +558,7 @@ message is part of a collapsed thread. cryptographically verified messages .TP ~x \fIEXPR\fP -messages which contain \fIEXPR\fP in the \(lqReferences\(rq field +messages which contain \fIEXPR\fP in the \(lqReferences\(rq or \(lqIn-Reply-To\(rq field .TP ~X \fIMIN\fP-\fIMAX\fP messages with MIN - MAX attachments @@ -582,9 +582,12 @@ messages in threads containing messages matching a certain pattern, e.g. all thr .PP In the above, \fIEXPR\fP is a regular expression. .PP -With the \fB~m\fP, \fB~n\fP, \fB~X\fP, and \fB~z\fP operators, you can also +With the \fB~d\fP, \fB~m\fP, \fB~n\fP, \fB~r\fP, \fB~X\fP, and \fB~z\fP operators, you can also specify ranges in the forms \fB<\fP\fIMAX\fP, \fB>\fP\fIMIN\fP, \fIMIN\fP\fB-\fP, and \fB-\fP\fIMAX\fP. +.PP +With the \fB~z\fP operator, the suffixes \(lqK\(rq and \(lqM\(rq are allowed to specify +kilobyte and megabyte respectively. .SS Matching dates .PP The \fB~d\fP and \fB~r\fP operators are used to match date ranges, diff --git a/doc/optionalfeatures.html b/doc/optionalfeatures.html index c5fa468..1e245a4 100644 --- a/doc/optionalfeatures.html +++ b/doc/optionalfeatures.html @@ -1,27 +1,31 @@ -Chapter 6. Optional features
Chapter 6. Optional features
Prev   Next

Chapter 6. Optional features

Table of Contents

1. General notes
1.1. Enabling/disabling features
1.2. URL syntax
2. SSL/TLS Support
3. POP3 Support
4. IMAP Support
4.1. The Folder Browser
4.2. Authentication
5. SMTP Support
6. Managing multiple accounts
7. Local caching
7.1. Header caching
7.2. Body caching
7.3. Maintenance
8. Exact address generation

1. General notes

1.1. Enabling/disabling features

+

Chapter 6. Optional Features
Prev   Next

Chapter 6. Optional Features

Table of Contents

1. General Notes
1.1. Enabling/Disabling Features
1.2. URL Syntax
2. SSL/TLS Support
3. POP3 Support
4. IMAP Support
4.1. The IMAP Folder Browser
4.2. Authentication
5. SMTP Support
6. Managing Multiple Accounts
7. Local Caching
7.1. Header Caching
7.2. Body Caching
7.3. Maintenance
8. Exact Address Generation
9. Sending Anonymous Messages via Mixmaster

1. General Notes

1.1. Enabling/Disabling Features

Mutt supports several of optional features which can be enabled or disabled at compile-time by giving the configure script certain arguments. These are listed in the “Optional features” section of @@ -30,42 +34,42 @@ the configure --help output. Which features are enabled or disabled can later be determined from the output of mutt -v. If a compile option starts with “+” it is enabled and disabled if prefixed with “-”. For example, if -mutt was compiled using GnuTLS for encrypted communication instead of +Mutt was compiled using GnuTLS for encrypted communication instead of OpenSSL, mutt -v would contain: 

--USE_SSL_OPENSSL +USE_SSL_GNUTLS

1.2. URL syntax

+-USE_SSL_OPENSSL +USE_SSL_GNUTLS

1.2. URL Syntax

Mutt optionally supports the IMAP, POP3 and SMTP protocols which require to access servers using URLs. The canonical syntax for specifying URLs -in mutt is (an item enclosed in [] means it is optional and +in Mutt is (an item enclosed in [] means it is optional and may be omitted): 

 proto[s]://[username[:password]@]server[:port]/[path]

-proto is the communication protocol: +proto is the communication protocol: imap for IMAP, pop for POP3 and -smtp for SMTP. If “s” for “secure communication” -is appended, mutt will attempt to establish an encrypted communication -using SSL or TLS. If no explicit port is given, mutt will use the -system's default for the given protocol. +smtp for SMTP. If “s” for “secure +communication” is appended, Mutt will attempt to establish an +encrypted communication using SSL or TLS.

-Since all protocols by mutt support authentication, the username may be -given directly in the URL instead of using the pop_user or -imap_user variables. It may contain the “@” symbol -being used by many mail systems as part of the login name. A password can be -given, too but is not recommended if the URL is specified in a configuration -file on disk. +Since all protocols supported by Mutt support/require authentication, +login credentials may be specified in the URL. This has the advantage +that multiple IMAP, POP3 or SMTP servers may be specified (which isn't +possible using, for example, +$imap_user). The username +may contain the “@” symbol being used by many mail systems +as part of the login name. A password can be given, too but is not +recommended if the URL is specified in a configuration file on disk.

-The optional path is only relevant for IMAP. +If no port number is given, Mutt will use the system's default for the +given protocol (usually consulting /etc/services).

-For IMAP for example, you can select an alternative port by specifying it with the -server: imap://imapserver:port/INBOX. You can also specify different -username for each folder: imap://username@imapserver[:port]/INBOX -or imap://username2@imapserver[:port]/path/to/folder. -Replacing imap:// by imaps:// -would make mutt attempt to connect using SSL or TLS on a different port -to encrypt the communication. -

2. SSL/TLS Support

-If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be +The optional path is only relevant for IMAP. +

Example 6.1. URLs

+pops://host/
+imaps://user@host/INBOX/Sent
+smtp://user@host:587/
+

2. SSL/TLS Support

+If Mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be compiled with support for SSL or TLS using either OpenSSL or GnuTLS ( by running the configure script with the --enable-ssl=... option for OpenSSL or @@ -73,36 +77,45 @@ by running the configure script with the attempt to encrypt communication with remote servers if these protocols are suffixed with “s” for “secure communication”.

3. POP3 Support

-If Mutt was compiled with POP3 support (by running the configure +If Mutt is compiled with POP3 support (by running the configure script with the --enable-pop flag), it has the ability to work with mailboxes located on a remote POP3 server and fetch mail for local browsing.

Remote POP3 servers can be accessed using URLs with the pop protocol for unencrypted and pops for encrypted -communication, see Section 1.2, “URL syntax” for details. +communication, see Section 1.2, “URL Syntax” for details.

Polling for new mail is more expensive over POP3 than locally. For this reason the frequency at which Mutt will check for mail remotely can be controlled by the -$pop_checkinterval +$pop_checkinterval variable, which defaults to every 60 seconds. +

+POP is read-only which doesn't allow for some features like editing +messages or changing flags. However, using +Section 7.1, “Header Caching” and Section 7.2, “Body Caching” +Mutt simulates the new/old/read flags as well as flagged and replied. +Mutt applies some logic on top of remote messages but cannot change +them so that modifications of flags are lost when +messages are downloaded from the POP server (either by Mutt or other +tools).

-Another way to access your POP3 mail is the <fetch-mail$ function -(default: G). It allows to connect to $pop_host, fetch all your new mail and place it in the -local $spoolfile. After this +Another way to access your POP3 mail is the <fetch-mail> function +(default: G). It allows to connect to $pop_host, 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.

Note

If you only need to fetch all messages to a local mailbox you should consider using a specialized program, such as -fetchmail, getmail or similar. +fetchmail(1), getmail(1) or similar.

4. IMAP Support

If Mutt was compiled with IMAP support (by running the configure script with the --enable-imap flag), it has the ability to work with folders located on a remote IMAP server.

You can access the remote inbox by selecting the folder by its URL -(see Section 1.2, “URL syntax” for details) using the +(see Section 1.2, “URL Syntax” for details) using the imap or imaps protocol. Alternatively, a pine-compatible notation is also supported, ie {[username@]imapserver[:port][/ssl]}path/to/folder @@ -114,30 +127,30 @@ paths accordingly. When browsing folders on an IMAP server, you can toggle whether to look at only the folders you are subscribed to, or all folders with the toggle-subscribed command. See also the -$imap_list_subscribed variable. +$imap_list_subscribed variable.

Polling for new mail on an IMAP server can cause noticeable delays. So, you'll want to carefully tune the -$mail_check +$mail_check and -$timeout -variables. Personally I use +$timeout +variables. Reasonable values are: 

 set mail_check=90
 set timeout=15

-with relatively good results over my slow modem line. +with relatively good results even over slow modem lines.

Note

Note that if you are using mbox as the mail store on UW servers prior to v12.250, the server has been reported to disconnect a client if another client selects the same folder. -

4.1. The Folder Browser

-As of version 1.2, mutt supports browsing mailboxes on an IMAP +

4.1. The IMAP Folder Browser

+As of version 1.2, Mutt supports browsing mailboxes on an IMAP server. This is mostly the same as the local file browser, with the following differences:

  • -In lieu of file permissions, mutt displays the string "IMAP", -possibly followed by the symbol "+", indicating +In lieu of file permissions, Mutt displays the string “IMAP”, +possibly followed by the symbol “+”, indicating that the entry contains both messages and subfolders. On Cyrus-like servers folders will often contain both messages and subfolders. @@ -149,10 +162,10 @@ the messages in that folder, you must use view-file (bound to space by default).

  • You can create, delete and rename mailboxes with the -create-mailbox, delete-mailbox, and -rename-mailbox commands (default bindings: C, +<create-mailbox>, <delete-mailbox>, and +<rename-mailbox> commands (default bindings: C, d and r, respectively). You may also -subscribe and unsubscribe to mailboxes (normally +<subscribe> and <unsubscribe> to mailboxes (normally these are bound to s and u, respectively).

4.2. Authentication

Mutt supports four authentication methods with IMAP servers: SASL, @@ -161,7 +174,7 @@ NTLM authentication for you poor exchange users out there, but it has yet to be integrated into the main tree). There is also support for the pseudo-protocol ANONYMOUS, which allows you to log in to a public IMAP server without having an account. To use ANONYMOUS, simply make -your username blank or "anonymous". +your username blank or “anonymous”.

SASL is a special super-authenticator, which selects among several protocols (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure @@ -169,56 +182,62 @@ method available on your host and the server. Using some of these methods (including DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and invisible to those teeming network snoops. It is the best option if you have it. To use it, you must have the Cyrus SASL library -installed on your system and compile mutt with the --with-sasl flag. +installed on your system and compile Mutt with the --with-sasl flag.

Mutt will try whichever methods are compiled in and available on the server, in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.

There are a few variables which control authentication:

  • -$imap_user - controls +$imap_user - controls the username under which you request authentication on the IMAP server, for all authenticators. This is overridden by an explicit username in the mailbox path (ie by using a mailbox name of the form {user@host}).

  • -$imap_pass - a +$imap_pass - a password which you may preset, used by all authentication methods where a password is needed.

  • -$imap_authenticators - a colon-delimited list of IMAP +$imap_authenticators - a colon-delimited list of IMAP authentication methods to try, in the order you wish to try them. If -specified, this overrides mutt's default (attempt everything, in the order +specified, this overrides Mutt's default (attempt everything, in the order listed above).

5. SMTP Support

Besides supporting traditional mail delivery through a -sendmail-compatible program, mutt supports delivery through SMTP if it +sendmail-compatible program, Mutt supports delivery through SMTP if it was configured and built with --enable-smtp.

If the configuration variable -$smtp_url is set, mutt +$smtp_url is set, Mutt will contact the given SMTP server to deliver messages; if it is unset, -mutt will use the program specified by $sendmail. +Mutt will use the program specified by $sendmail.

-For details on the URL syntax, please see Section 1.2, “URL syntax”. +For details on the URL syntax, please see Section 1.2, “URL Syntax”.

The built-in SMTP support supports encryption (the smtps protocol using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms -for SASL are specified in $smtp_authenticators -defaulting to an empty list which makes mutt try all available methods +for SASL are specified in $smtp_authenticators +defaulting to an empty list which makes Mutt try all available methods from most-secure to least-secure. -

6. Managing multiple accounts

+

6. Managing Multiple Accounts

+Usage: +

account-hook +pattern + +command +

If you happen to have accounts on multiple IMAP, POP and/or SMTP servers, you may find managing all the authentication settings inconvenient and -error-prone. The account-hook command may help. This hook works like -folder-hook but is invoked whenever you access a remote mailbox +error-prone. The account-hook command may help. This hook works like +folder-hook but is invoked whenever Mutt needs to access a remote mailbox (including inside the folder browser), not just when you open the -mailbox which includes (for example) polling for new mail, storing Fcc +mailbox. This includes (for example) polling for new mail, storing Fcc messages and saving messages to a folder. As a consequence, -account-hook should only be used to set connection-related settings such +account-hook should only be used to set connection-related settings such as passwords or tunnel commands but not settings such as sender address or name (because in general it should be considered unpredictable -which account-hook was last used). +which account-hook was last used).

Some examples: 

@@ -226,15 +245,45 @@ account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
 account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
 account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
 account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
-

7. Local caching

+

+To manage multiple accounts with, for example, different values of +$record or sender addresses, +folder-hook +has to be be used together with +the mailboxes command. +

Example 6.2. Managing multiple accounts

+mailboxes imap://user@host1/INBOX
+folder-hook imap://user@host1/ 'set folder=imap://host1/ ; set record=+INBOX/Sent'
+
+mailboxes imap://user@host2/INBOX
+folder-hook imap://user@host2/ 'set folder=imap://host2/ ; set record=+INBOX/Sent'
+

+In example +Example 6.2, “Managing multiple accounts” the folders are defined using +mailboxes so Mutt polls them for new +mail. Each folder-hook triggers when +one mailbox below each IMAP account is opened and sets +$folder to the account's root +folder. Next, it sets $record to +the INBOX/Sent folder below the newly +set $folder. Please notice that the +value the “+” +mailbox shortcut refers to depends on +the current value +of $folder and therefore has to be set +separatedly per account. Setting other values +like $from +or $signature is analogous to setting +$record. +

7. Local Caching

Mutt contains two types of local caching: (1) the so-called “header caching” and (2) the so-called “body caching” which are both described in this section.

Header caching is optional as it depends on external libraries, body -caching is always enabled if mutt is compiled with POP and/or IMAP +caching is always enabled if Mutt is compiled with POP and/or IMAP support as these use it (body caching requires no external library). -

7.1. Header caching

+

7.1. Header Caching

Mutt provides optional support for caching message headers for the following types of folders: IMAP, POP, Maildir and MH. Header caching greatly improves speed because for remote folders, headers @@ -247,63 +296,83 @@ Header caching can be enabled via the configure script and the by default because external database libraries are required: one of tokyocabinet, qdbm, gdbm or bdb must be present.

-If enabled, $header_cache can be +If enabled, $header_cache can be used to either point to a file or a directory. If set to point to a file, one database file for all folders will be used (which may result in lower performance), but one file per folder if it points to a directory. -

-For the one-file-per-folder case, database files for remote folders -will be named according to their URL while database files for local -folders will be named by the MD5 checksums of their path. These database -files may be safely removed if a system is short on space. You -can compute the name of the header cache file for a particular local folder -through a command like the following: -

-$ printf '%s' '/path/to/folder' | md5sum
-

-The md5sum command may also be -named md5, depending on your operating system. -

7.2. Body caching

+

7.2. Body Caching

Both cache methods can be combined using the same directory for storage (and for IMAP/POP even provide meaningful file names) which simplifies manual maintenance tasks.

-In addition to caching message headers only, mutt can also cache +In addition to caching message headers only, Mutt can also cache whole message bodies. This results in faster display of messages for POP and IMAP folders because messages usually have to be downloaded only once.

-For configuration, the variable $message_cachedir must point to a -directory. There, mutt will create a hierarchy of subdirectories +For configuration, the variable $message_cachedir must point to a +directory. There, Mutt will create a hierarchy of subdirectories named like: proto:user@hostname where proto is either “pop” or “imap.” Within -there for each folder, mutt stores messages in single files (just -like Maildir) so that with manual symlink creation these cache -directories can be examined with mutt as read-only Maildir folders. -

+there for each folder, Mutt stores messages in single files. All files can be removed as needed if the consumed disk space -becomes an issue as mutt will silently fetch missing items again. +becomes an issue as Mutt will silently fetch missing items again.

7.3. Maintenance

Mutt does not (yet) support maintenance features for header cache database files so that files have to be removed in case they grow too big. It depends on the database library used for header caching whether disk space freed by removing messages is re-used.

-For body caches, mutt can keep the local cache in sync with the +For body caches, Mutt can keep the local cache in sync with the remote mailbox if the -$message_cache_clean +$message_cache_clean variable is set. Cleaning means to remove messages from the cache which are no longer present in the mailbox which only happens when other mail -clients or instances of mutt using a different body cache location +clients or instances of Mutt using a different body cache location delete messages (Mutt itself removes deleted messages from the cache when syncing a mailbox). As cleaning can take a noticeable amount of time, it should not be set in general but only occasionally. -

8. Exact address generation

+

8. Exact Address Generation

Mutt supports the “Name <user@host>” address syntax for reading and writing messages, the older “user@host (Name)” syntax is only supported when reading messages. The --enable-exact-address switch can be given to configure to build it with write-support for the latter syntax. EXACT_ADDRESS in the output of mutt -v indicates whether it's supported. -

Prev   Next
Chapter 5. Mutt's MIME Support Home Chapter 7. Performance tuning
+

9. Sending Anonymous Messages via Mixmaster

+You may also have compiled Mutt to co-operate with Mixmaster, an +anonymous remailer. Mixmaster permits you to send your messages +anonymously using a chain of remailers. Mixmaster support in Mutt is for +mixmaster version 2.04 (beta 45 appears to be the latest) and 2.03. +It does not support earlier versions or the later so-called version 3 betas, +of which the latest appears to be called 2.9b23. +

+To use it, you'll have to obey certain restrictions. Most +important, you cannot use the Cc and Bcc headers. To tell +Mutt to use mixmaster, you have to select a remailer chain, using +the mix function on the compose menu. +

+The chain selection screen is divided into two parts. In the +(larger) upper part, you get a list of remailers you may use. In +the lower part, you see the currently selected chain of remailers. +

+You can navigate in the chain using the <chain-prev> and +<chain-next> functions, which are by default bound to the left +and right arrows and to the h and l keys (think vi +keyboard bindings). To insert a remailer at the current chain +position, use the <insert> function. To append a remailer behind +the current chain position, use <select-entry> or <append>. +You can also delete entries from the chain, using the corresponding +function. Finally, to abandon your changes, leave the menu, or +<accept> them pressing (by default) the Return key. +

+Note that different remailers do have different capabilities, +indicated in the %c entry of the remailer menu lines (see +$mix_entry_format). Most important is +the “middleman” capability, indicated by a capital “M”: This +means that the remailer in question cannot be used as the final +element of a chain, but will only forward messages to other +mixmaster remailers. For details on the other capabilities, please +have a look at the mixmaster documentation. +

Prev   Next
Chapter 5. Mutt's MIME Support Home Chapter 7. Security Considerations
diff --git a/doc/reference.html b/doc/reference.html index 4bdd6ba..03e316d 100644 --- a/doc/reference.html +++ b/doc/reference.html @@ -1,31 +1,35 @@ -Chapter 8. Reference
Chapter 8. Reference
Prev   Next

Chapter 8. Reference

Table of Contents

1. Command line options
2. Configuration Commands
3. Configuration variables
3.1. abort_nosubject
3.2. abort_unmodified
3.3. alias_file
3.4. alias_format
3.5. allow_8bit
3.6. allow_ansi
3.7. arrow_cursor
3.8. ascii_chars
3.9. askbcc
3.10. askcc
3.11. assumed_charset
3.12. attach_charset
3.13. attach_format
3.14. attach_sep
3.15. attach_split
3.16. attribution
3.17. autoedit
3.18. auto_tag
3.19. beep
3.20. beep_new
3.21. bounce
3.22. bounce_delivered
3.23. braille_friendly
3.24. check_mbox_size
3.25. charset
3.26. check_new
3.27. collapse_unread
3.28. uncollapse_jump
3.29. compose_format
3.30. config_charset
3.31. confirmappend
3.32. confirmcreate
3.33. connect_timeout
3.34. content_type
3.35. copy
3.36. crypt_use_gpgme
3.37. crypt_use_pka
3.38. crypt_autopgp
3.39. crypt_autosmime
3.40. date_format
3.41. default_hook
3.42. delete
3.43. delete_untag
3.44. digest_collapse
3.45. display_filter
3.46. dotlock_program
3.47. dsn_notify
3.48. dsn_return
3.49. duplicate_threads
3.50. edit_headers
3.51. editor
3.52. encode_from
3.53. envelope_from_address
3.54. escape
3.55. fast_reply
3.56. fcc_attach
3.57. fcc_clear
3.58. folder
3.59. folder_format
3.60. followup_to
3.61. force_name
3.62. forward_decode
3.63. forward_edit
3.64. forward_format
3.65. forward_quote
3.66. from
3.67. gecos_mask
3.68. hdrs
3.69. header
3.70. help
3.71. hidden_host
3.72. hide_limited
3.73. hide_missing
3.74. hide_thread_subject
3.75. hide_top_limited
3.76. hide_top_missing
3.77. history
3.78. history_file
3.79. honor_followup_to
3.80. hostname
3.81. ignore_linear_white_space
3.82. ignore_list_reply_to
3.83. imap_authenticators
3.84. imap_check_subscribed
3.85. imap_delim_chars
3.86. imap_headers
3.87. imap_idle
3.88. imap_keepalive
3.89. imap_list_subscribed
3.90. imap_login
3.91. imap_pass
3.92. imap_passive
3.93. imap_peek
3.94. imap_pipeline_depth
3.95. imap_servernoise
3.96. imap_user
3.97. implicit_autoview
3.98. include
3.99. include_onlyfirst
3.100. indent_string
3.101. index_format
3.102. ispell
3.103. keep_flagged
3.104. locale
3.105. mail_check
3.106. mailcap_path
3.107. mailcap_sanitize
3.108. header_cache
3.109. maildir_header_cache_verify
3.110. header_cache_pagesize
3.111. header_cache_compress
3.112. maildir_trash
3.113. mark_old
3.114. markers
3.115. mask
3.116. mbox
3.117. mbox_type
3.118. metoo
3.119. menu_context
3.120. menu_move_off
3.121. menu_scroll
3.122. meta_key
3.123. mh_purge
3.124. mh_seq_flagged
3.125. mh_seq_replied
3.126. mh_seq_unseen
3.127. mime_forward
3.128. mime_forward_decode
3.129. mime_forward_rest
3.130. mix_entry_format
3.131. mixmaster
3.132. move
3.133. message_cachedir
3.134. message_cache_clean
3.135. message_format
3.136. narrow_tree
3.137. net_inc
3.138. pager
3.139. pager_context
3.140. pager_format
3.141. pager_index_lines
3.142. pager_stop
3.143. crypt_autosign
3.144. crypt_autoencrypt
3.145. pgp_ignore_subkeys
3.146. crypt_replyencrypt
3.147. crypt_replysign
3.148. crypt_replysignencrypted
3.149. crypt_timestamp
3.150. pgp_use_gpg_agent
3.151. crypt_verify_sig
3.152. smime_is_default
3.153. smime_ask_cert_label
3.154. smime_decrypt_use_default_key
3.155. pgp_entry_format
3.156. pgp_good_sign
3.157. pgp_check_exit
3.158. pgp_long_ids
3.159. pgp_retainable_sigs
3.160. pgp_autoinline
3.161. pgp_replyinline
3.162. pgp_show_unusable
3.163. pgp_sign_as
3.164. pgp_strict_enc
3.165. pgp_timeout
3.166. pgp_sort_keys
3.167. pgp_mime_auto
3.168. pgp_auto_decode
3.169. pgp_decode_command
3.170. pgp_getkeys_command
3.171. pgp_verify_command
3.172. pgp_decrypt_command
3.173. pgp_clearsign_command
3.174. pgp_sign_command
3.175. pgp_encrypt_sign_command
3.176. pgp_encrypt_only_command
3.177. pgp_import_command
3.178. pgp_export_command
3.179. pgp_verify_key_command
3.180. pgp_list_secring_command
3.181. pgp_list_pubring_command
3.182. forward_decrypt
3.183. smime_timeout
3.184. smime_encrypt_with
3.185. smime_keys
3.186. smime_ca_location
3.187. smime_certificates
3.188. smime_decrypt_command
3.189. smime_verify_command
3.190. smime_verify_opaque_command
3.191. smime_sign_command
3.192. smime_sign_opaque_command
3.193. smime_encrypt_command
3.194. smime_pk7out_command
3.195. smime_get_cert_command
3.196. smime_get_signer_cert_command
3.197. smime_import_cert_command
3.198. smime_get_cert_email_command
3.199. smime_default_key
3.200. ssl_client_cert
3.201. ssl_force_tls
3.202. ssl_starttls
3.203. certificate_file
3.204. ssl_usesystemcerts
3.205. entropy_file
3.206. ssl_use_sslv2
3.207. ssl_use_sslv3
3.208. ssl_use_tlsv1
3.209. ssl_min_dh_prime_bits
3.210. ssl_ca_certificates_file
3.211. pipe_split
3.212. pipe_decode
3.213. pipe_sep
3.214. pop_authenticators
3.215. pop_auth_try_all
3.216. pop_checkinterval
3.217. pop_delete
3.218. pop_host
3.219. pop_last
3.220. pop_reconnect
3.221. pop_user
3.222. pop_pass
3.223. post_indent_string
3.224. postpone
3.225. postponed
3.226. preconnect
3.227. print
3.228. print_command
3.229. print_decode
3.230. print_split
3.231. prompt_after
3.232. query_command
3.233. query_format
3.234. quit
3.235. quote_regexp
3.236. read_inc
3.237. read_only
3.238. realname
3.239. recall
3.240. record
3.241. reply_regexp
3.242. reply_self
3.243. reply_to
3.244. resolve
3.245. reverse_alias
3.246. reverse_name
3.247. reverse_realname
3.248. rfc2047_parameters
3.249. save_address
3.250. save_empty
3.251. save_history
3.252. save_name
3.253. score
3.254. score_threshold_delete
3.255. score_threshold_flag
3.256. score_threshold_read
3.257. send_charset
3.258. sendmail
3.259. sendmail_wait
3.260. shell
3.261. sig_dashes
3.262. sig_on_top
3.263. signature
3.264. simple_search
3.265. smart_wrap
3.266. smileys
3.267. sleep_time
3.268. smtp_authenticators
3.269. smtp_pass
3.270. smtp_url
3.271. sort
3.272. sort_alias
3.273. sort_aux
3.274. sort_browser
3.275. sort_re
3.276. spam_separator
3.277. spoolfile
3.278. status_chars
3.279. status_format
3.280. status_on_top
3.281. strict_threads
3.282. suspend
3.283. text_flowed
3.284. thread_received
3.285. thorough_search
3.286. tilde
3.287. time_inc
3.288. timeout
3.289. tmpdir
3.290. to_chars
3.291. tunnel
3.292. use_8bitmime
3.293. use_domain
3.294. use_envelope_from
3.295. use_from
3.296. use_idn
3.297. use_ipv6
3.298. user_agent
3.299. visual
3.300. wait_key
3.301. weed
3.302. wrap
3.303. wrap_search
3.304. wrapmargin
3.305. write_inc
3.306. write_bcc
4. Functions
4.1. generic menu
4.2. index menu
4.3. pager menu
4.4. alias menu
4.5. query menu
4.6. attach menu
4.7. compose menu
4.8. postpone menu
4.9. browser menu
4.10. pgp menu
4.11. smime menu
4.12. mix menu
4.13. editor menu

1. Command line options

+

Chapter 9. Reference
Prev   Next

Chapter 9. Reference

Table of Contents

1. Command-Line Options
2. Configuration Commands
3. Configuration Variables
3.1. abort_nosubject
3.2. abort_unmodified
3.3. alias_file
3.4. alias_format
3.5. allow_8bit
3.6. allow_ansi
3.7. arrow_cursor
3.8. ascii_chars
3.9. askbcc
3.10. askcc
3.11. assumed_charset
3.12. attach_charset
3.13. attach_format
3.14. attach_sep
3.15. attach_split
3.16. attribution
3.17. auto_tag
3.18. autoedit
3.19. beep
3.20. beep_new
3.21. bounce
3.22. bounce_delivered
3.23. braille_friendly
3.24. certificate_file
3.25. charset
3.26. check_mbox_size
3.27. check_new
3.28. collapse_unread
3.29. compose_format
3.30. config_charset
3.31. confirmappend
3.32. confirmcreate
3.33. connect_timeout
3.34. content_type
3.35. copy
3.36. crypt_autoencrypt
3.37. crypt_autopgp
3.38. crypt_autosign
3.39. crypt_autosmime
3.40. crypt_replyencrypt
3.41. crypt_replysign
3.42. crypt_replysignencrypted
3.43. crypt_timestamp
3.44. crypt_use_gpgme
3.45. crypt_use_pka
3.46. crypt_verify_sig
3.47. date_format
3.48. default_hook
3.49. delete
3.50. delete_untag
3.51. digest_collapse
3.52. display_filter
3.53. dotlock_program
3.54. dsn_notify
3.55. dsn_return
3.56. duplicate_threads
3.57. edit_headers
3.58. editor
3.59. encode_from
3.60. entropy_file
3.61. envelope_from_address
3.62. escape
3.63. fast_reply
3.64. fcc_attach
3.65. fcc_clear
3.66. folder
3.67. folder_format
3.68. followup_to
3.69. force_name
3.70. forward_decode
3.71. forward_decrypt
3.72. forward_edit
3.73. forward_format
3.74. forward_quote
3.75. from
3.76. gecos_mask
3.77. hdrs
3.78. header
3.79. header_cache
3.80. header_cache_compress
3.81. header_cache_pagesize
3.82. help
3.83. hidden_host
3.84. hide_limited
3.85. hide_missing
3.86. hide_thread_subject
3.87. hide_top_limited
3.88. hide_top_missing
3.89. history
3.90. history_file
3.91. honor_disposition
3.92. honor_followup_to
3.93. hostname
3.94. ignore_linear_white_space
3.95. ignore_list_reply_to
3.96. imap_authenticators
3.97. imap_check_subscribed
3.98. imap_delim_chars
3.99. imap_headers
3.100. imap_idle
3.101. imap_keepalive
3.102. imap_list_subscribed
3.103. imap_login
3.104. imap_pass
3.105. imap_passive
3.106. imap_peek
3.107. imap_pipeline_depth
3.108. imap_servernoise
3.109. imap_user
3.110. implicit_autoview
3.111. include
3.112. include_onlyfirst
3.113. indent_string
3.114. index_format
3.115. ispell
3.116. keep_flagged
3.117. locale
3.118. mail_check
3.119. mailcap_path
3.120. mailcap_sanitize
3.121. maildir_header_cache_verify
3.122. maildir_trash
3.123. mark_old
3.124. markers
3.125. mask
3.126. mbox
3.127. mbox_type
3.128. menu_context
3.129. menu_move_off
3.130. menu_scroll
3.131. message_cache_clean
3.132. message_cachedir
3.133. message_format
3.134. meta_key
3.135. metoo
3.136. mh_purge
3.137. mh_seq_flagged
3.138. mh_seq_replied
3.139. mh_seq_unseen
3.140. mime_forward
3.141. mime_forward_decode
3.142. mime_forward_rest
3.143. mix_entry_format
3.144. mixmaster
3.145. move
3.146. narrow_tree
3.147. net_inc
3.148. pager
3.149. pager_context
3.150. pager_format
3.151. pager_index_lines
3.152. pager_stop
3.153. pgp_auto_decode
3.154. pgp_autoinline
3.155. pgp_check_exit
3.156. pgp_clearsign_command
3.157. pgp_decode_command
3.158. pgp_decrypt_command
3.159. pgp_encrypt_only_command
3.160. pgp_encrypt_sign_command
3.161. pgp_entry_format
3.162. pgp_export_command
3.163. pgp_getkeys_command
3.164. pgp_good_sign
3.165. pgp_ignore_subkeys
3.166. pgp_import_command
3.167. pgp_list_pubring_command
3.168. pgp_list_secring_command
3.169. pgp_long_ids
3.170. pgp_mime_auto
3.171. pgp_replyinline
3.172. pgp_retainable_sigs
3.173. pgp_show_unusable
3.174. pgp_sign_as
3.175. pgp_sign_command
3.176. pgp_sort_keys
3.177. pgp_strict_enc
3.178. pgp_timeout
3.179. pgp_use_gpg_agent
3.180. pgp_verify_command
3.181. pgp_verify_key_command
3.182. pipe_decode
3.183. pipe_sep
3.184. pipe_split
3.185. pop_auth_try_all
3.186. pop_authenticators
3.187. pop_checkinterval
3.188. pop_delete
3.189. pop_host
3.190. pop_last
3.191. pop_pass
3.192. pop_reconnect
3.193. pop_user
3.194. post_indent_string
3.195. postpone
3.196. postponed
3.197. preconnect
3.198. print
3.199. print_command
3.200. print_decode
3.201. print_split
3.202. prompt_after
3.203. query_command
3.204. query_format
3.205. quit
3.206. quote_regexp
3.207. read_inc
3.208. read_only
3.209. realname
3.210. recall
3.211. record
3.212. reply_regexp
3.213. reply_self
3.214. reply_to
3.215. resolve
3.216. reverse_alias
3.217. reverse_name
3.218. reverse_realname
3.219. rfc2047_parameters
3.220. save_address
3.221. save_empty
3.222. save_history
3.223. save_name
3.224. score
3.225. score_threshold_delete
3.226. score_threshold_flag
3.227. score_threshold_read
3.228. search_context
3.229. send_charset
3.230. sendmail
3.231. sendmail_wait
3.232. shell
3.233. sig_dashes
3.234. sig_on_top
3.235. signature
3.236. simple_search
3.237. sleep_time
3.238. smart_wrap
3.239. smileys
3.240. smime_ask_cert_label
3.241. smime_ca_location
3.242. smime_certificates
3.243. smime_decrypt_command
3.244. smime_decrypt_use_default_key
3.245. smime_default_key
3.246. smime_encrypt_command
3.247. smime_encrypt_with
3.248. smime_get_cert_command
3.249. smime_get_cert_email_command
3.250. smime_get_signer_cert_command
3.251. smime_import_cert_command
3.252. smime_is_default
3.253. smime_keys
3.254. smime_pk7out_command
3.255. smime_sign_command
3.256. smime_sign_opaque_command
3.257. smime_timeout
3.258. smime_verify_command
3.259. smime_verify_opaque_command
3.260. smtp_authenticators
3.261. smtp_pass
3.262. smtp_url
3.263. sort
3.264. sort_alias
3.265. sort_aux
3.266. sort_browser
3.267. sort_re
3.268. spam_separator
3.269. spoolfile
3.270. ssl_ca_certificates_file
3.271. ssl_client_cert
3.272. ssl_force_tls
3.273. ssl_min_dh_prime_bits
3.274. ssl_starttls
3.275. ssl_use_sslv2
3.276. ssl_use_sslv3
3.277. ssl_use_tlsv1
3.278. ssl_usesystemcerts
3.279. ssl_verify_dates
3.280. ssl_verify_host
3.281. status_chars
3.282. status_format
3.283. status_on_top
3.284. strict_threads
3.285. suspend
3.286. text_flowed
3.287. thorough_search
3.288. thread_received
3.289. tilde
3.290. time_inc
3.291. timeout
3.292. tmpdir
3.293. to_chars
3.294. tunnel
3.295. uncollapse_jump
3.296. use_8bitmime
3.297. use_domain
3.298. use_envelope_from
3.299. use_from
3.300. use_idn
3.301. use_ipv6
3.302. user_agent
3.303. visual
3.304. wait_key
3.305. weed
3.306. wrap
3.307. wrap_search
3.308. wrapmargin
3.309. write_bcc
3.310. write_inc
4. Functions
4.1. Generic Menu
4.2. Index Menu
4.3. Pager Menu
4.4. Alias Menu
4.5. Query Menu
4.6. Attach Menu
4.7. Compose Menu
4.8. Postpone Menu
4.9. Browser Menu
4.10. Pgp Menu
4.11. Smime Menu
4.12. Mix Menu
4.13. Editor Menu

1. Command-Line Options

Running mutt with no arguments will make Mutt attempt to read your spool mailbox. However, it is possible to read other mailboxes and to send messages from the command line as well. -

Table 8.1. Command line options

OptionDescription
-Aexpand an alias
-aattach a file to a message
-bspecify a blind carbon-copy (BCC) address
-cspecify a carbon-copy (Cc) address
-Dprint the value of all mutt variables to stdout
-especify a config command to be run after initialization files are read
-fspecify a mailbox to load
-Fspecify an alternate file to read initialization commands
-hprint help on command line options
-Hspecify a draft file from which to read a header and body
-ispecify a file to include in a message composition
-mspecify a default mailbox type
-ndo not read the system Muttrc
-precall a postponed message
-Qquery a configuration variable
-Ropen mailbox in read-only mode
-sspecify a subject (enclose in quotes if it contains spaces)
-vshow version number and compile-time definitions
-xsimulate the mailx(1) compose mode
-yshow a menu containing the files specified by the mailboxes command
-zexit immediately if there are no messages in the mailbox
-Zopen the first folder with new message,exit immediately if none

+

Table 9.1. Command line options

OptionDescription
-Aexpand an alias
-aattach a file to a message
-bspecify a blind carbon-copy (BCC) address
-cspecify a carbon-copy (Cc) address
-Dprint the value of all Mutt variables to stdout
-especify a config command to be run after initialization files are read
-fspecify a mailbox to load
-Fspecify an alternate file to read initialization commands
-hprint help on command line options
-Hspecify a draft file from which to read a header and body
-ispecify a file to include in a message composition
-mspecify a default mailbox type
-ndo not read the system Muttrc
-precall a postponed message
-Qquery a configuration variable
-Ropen mailbox in read-only mode
-sspecify a subject (enclose in quotes if it contains spaces)
-vshow version number and compile-time definitions
-xsimulate the mailx(1) compose mode
-yshow a menu containing the files specified by the mailboxes command
-zexit immediately if there are no messages in the mailbox
-Zopen the first folder with new message, exit immediately if none

To read messages in a mailbox

mutt [-nz] [-F muttrc @@ -37,8 +41,6 @@ To read messages in a mailbox To compose a new message

mutt [-n] [-F muttrc -] [-a -file ] [-c address ] [-i @@ -46,34 +48,36 @@ To compose a new message ] [-s subject ] [ -[ +-a file -...] - -- + [...] +-- ] address - [ -address -...]

+...

Mutt also supports a “batch” mode to send prepared messages. Simply redirect input from the file you wish to send. For example, -

-mutt -s "data set for run #2" professor@bigschool.edu -< ˜/run2.dat -

-This command will send a message to “professor@bigschool.edu” with a subject +

+mutt -s "data set for run #2" professor@bigschool.edu < ˜/run2.dat

+will send a message to <professor@bigschool.edu> with a subject of “data set for run #2”. In the body of the message will be the contents of the file “˜/run2.dat”.

-All files passed with -a file will be attached as a MIME -part to the message. To attach several files, use “--” to separate files and -recipient addresses: mutt -a *.png -- some@one.org -

2. Configuration Commands

-The following are the commands understood by mutt. -

  • account-hook +All files passed with -a file will be attached as a MIME +part to the message. To attach a single or several files, use “--” to separate files and +recipient addresses: +

    +mutt -a image.png -- some@one.org

    +or +

    +mutt -a *.png -- some@one.org

    Note

    +The -a option must be last in the option list. +

    2. Configuration Commands

    +The following are the commands understood by Mutt: +

    3. Configuration variables

    3.1. abort_nosubject

    Type: quadoption
    + }

3. Configuration Variables

3.1. abort_nosubject

Type: quadoption
Default: ask-yes

If set to yes, when composing messages and no subject is given at the subject prompt, composition will be aborted. If set to @@ -384,22 +406,22 @@ encoded in the character set specified by set or the current character set otherwise.

Note: Mutt will not automatically source this file; you must -explicitly use the “source” command for it to be executed in case +explicitly use the “source” command for it to be executed in case this option points to a dedicated alias file.

The default for this option is the currently used muttrc file, or “˜/.muttrc” if no user muttrc was found.

3.4. alias_format

Type: string
Default: “%4n %2f %t %-10a   %r”

-Specifies the format of the data displayed for the “alias” menu. The +Specifies the format of the data displayed for the “alias” menu. The following printf(3)-style sequences are available: -

%a

alias name -

%f

flags - currently, a “d” for an alias marked for deletion -

%n

index number -

%r

address which alias expands to -

%t

character which indicates if the alias is tagged for inclusion -

3.5. allow_8bit

Type: boolean
+

%a alias name +
%f flags - currently, a “d” for an alias marked for deletion +
%n index number +
%r address which alias expands to +
%t character which indicates if the alias is tagged for inclusion +

3.5. allow_8bit

Type: boolean
Default: yes

Controls whether 8-bit data is converted to 7-bit using either Quoted- Printable or Base64 encoding when sending mail. @@ -414,10 +436,9 @@ message could include a line like 

 [-- PGP output follows ...
-

and give it the same color as your attachment color (see also -$crypt_timestamp). +$crypt_timestamp).

3.7. arrow_cursor

Type: boolean
Default: no

When set, an arrow (“->”) will be used to indicate the current entry @@ -450,20 +471,21 @@ For example, Japanese users might prefer this: 

 set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-

However, only the first content is valid for the message body.

3.12. attach_charset

Type: string
Default: (empty)

This variable is a colon-separated list of character encoding -schemes for text file attachments. +schemes for text file attachments. Mutt uses this setting to guess +which encoding files being attached are encoded in to convert them to +a proper character set given in $send_charset. +

If unset, the value of $charset will be used instead. For example, the following configuration would work for Japanese text handling: 

 set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-

Note: for Japanese users, “iso-2022-*” must be put at the head of the value as shown above if included. @@ -472,28 +494,28 @@ Default: “%u%D%I %t%4n %T%.40d%&g This variable describes the format of the “attachment” menu. The following printf(3)-style sequences are understood: -

%C

charset -

%c

requires charset conversion (“n” or “c”) -

%D

deleted flag -

%d

description -

%e

MIME content-transfer-encoding -

%f

filename -

%I

disposition (“I” for inline, “A” for attachment) -

%m

major MIME type -

%M

MIME subtype -

%n

attachment number -

%Q

“Q”, if MIME part qualifies for attachment counting -

%s

size -

%t

tagged flag -

%T

graphic tree characters -

%u

unlink (=to delete) flag -

%X

number of qualifying MIME parts in this part and its children +

%C charset +
%c requires charset conversion (“n” or “c”) +
%D deleted flag +
%d description +
%e MIME content-transfer-encoding +
%f filename +
%I disposition (“I” for inline, “A” for attachment) +
%m major MIME type +
%M MIME subtype +
%n attachment number +
%Q “Q”, if MIME part qualifies for attachment counting +
%s size +
%t tagged flag +
%T graphic tree characters +
%u unlink (=to delete) flag +
%X number of qualifying MIME parts in this part and its children (please see the “attachments” section for possible speed effects) -

%>X

right justify the rest of the string and pad with character “X” -

%|X

pad to the end of the line with character “X” -

%*X

soft-fill with character “X” as pad -

-For an explanation of “soft-fill”, see the $index_format documentation. +

%>X right justify the rest of the string and pad with character “X” +
%|X pad to the end of the line with character “X” +
%*X soft-fill with character “X” as pad +

+For an explanation of “soft-fill”, see the $index_format documentation.

3.14. attach_sep

Type: string
Default: “\n”

The separator to add between attachments when operating (saving, @@ -509,22 +531,26 @@ Mutt will operate on the attachments one by one. 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 printf(3)-like sequences see -the section on $index_format. -

3.17. autoedit

Type: boolean
+the section on $index_format. +

3.17. auto_tag

Type: boolean
+Default: no

+When set, functions in the index menu which affect a message +will be applied to all tagged messages (if there are any). When +unset, you must first use the <tag-prefix> function (bound to “;” +by default) to make the next function apply to all tagged messages. +

3.18. autoedit

Type: boolean
Default: no

-When set along with $edit_headers, Mutt will skip the initial +When set along with $edit_headers, Mutt will skip the initial send-menu (prompting for subject and recipients) and allow you to immediately begin editing the body of your message. The send-menu may still be accessed once you have finished editing the body of your message.

-Also see $fast_reply. -

3.18. auto_tag

Type: boolean
-Default: no

-When set, functions in the index menu which affect a message -will be applied to all tagged messages (if there are any). When -unset, you must first use the <tag-prefix> function (bound to “;” -by default) to make the next function apply to all tagged messages. +Note: when this option is set, you cannot use send-hooks that depend +on the recipients when composing a new (non-reply) message, as the initial +list of recipients is empty. +

+Also see $fast_reply.

3.19. beep

Type: boolean
Default: yes

When this variable is set, mutt will beep when an error occurs. @@ -550,7 +576,33 @@ of the current line in menus, even when the unset, making it easier for blind persons using Braille displays to follow these menus. The option is unset by default because many visual terminals don't permit making the cursor invisible. -

3.24. check_mbox_size

Type: boolean
+

3.24. certificate_file

Type: path
+Default: “˜/.mutt_certificates”

+This variable specifies the file where the certificates you trust +are saved. When an unknown certificate is encountered, you are asked +if you accept it or not. If you accept it, the certificate can also +be saved in this file and further connections are automatically +accepted. +

+You can also manually add CA certificates in this file. Any server +certificate that is signed with one of these CA certificates is +also automatically accepted. +

+Example: + +

+set certificate_file=~/.mutt/certificates
+

3.25. charset

Type: string
+Default: (empty)

+Character set your terminal uses to display and enter textual data. +It is also the fallback for $send_charset. +

+Upon startup Mutt tries to derive this value from environment variables +such as $LC_CTYPE or $LANG. +

+Note: It should only be set in case Mutt isn't abled to determine the +character set used correctly. +

3.26. check_mbox_size

Type: boolean
Default: no

When this variable is set, mutt will use file size attribute instead of access time when checking for new mail in mbox and mmdf folders. @@ -558,22 +610,12 @@ access time when checking for new mail in mbox and mmdf folders. This variable is unset by default and should only be enabled when new mail detection for these folder types is unreliable or doesn't work.

-Note that enabling this variable should happen before any “mailboxes” +Note that enabling this variable should happen before any “mailboxes” directives occur in configuration files regarding mbox or mmdf folders because mutt needs to determine the initial new mail status of such a mailbox by performing a fast mailbox scan when it is defined. Afterwards the new mail status is tracked by file size changes. -

3.25. charset

Type: string
-Default: (empty)

-Character set your terminal uses to display and enter textual data. -It is also the fallback for $send_charset. -

-Upon startup Mutt tries to derive this value from environment variables -such as $LC_CTYPE or $LANG. -

-Note: It should only be set in case Mutt isn't abled to determine the -character set used correctly. -

3.26. check_new

Type: boolean
+

3.27. check_new

Type: boolean
Default: yes

Note: this option only affects maildir and MH style mailboxes. @@ -584,26 +626,22 @@ take quite some time since it involves scanning the directory and checking each file to see if it has already been looked at. If this variable is unset, no check for new mail is performed while the mailbox is open. -

3.27. collapse_unread

Type: boolean
+

3.28. collapse_unread

Type: boolean
Default: yes

When unset, Mutt will not collapse a thread if it contains any unread messages. -

3.28. uncollapse_jump

Type: boolean
-Default: no

-When set, Mutt will jump to the next unread message, if any, -when the current thread is uncollapsed.

3.29. compose_format

Type: string
Default: “-- Mutt: Compose  [Approx. msg size: %l   Atts: %a]%>-”

Controls the format of the status line displayed in the “compose” -menu. This string is similar to $status_format, but has its own +menu. This string is similar to $status_format, but has its own set of printf(3)-like sequences: -

%a

total number of attachments -

%h

local hostname -

%l

approximate size (in bytes) of the current message -

%v

Mutt version string -

-See the text describing the $status_format option for more +

%a total number of attachments +
%h local hostname +
%l approximate size (in bytes) of the current message +
%v Mutt version string +

+See the text describing the $status_format option for more information on how to set $compose_format.

3.30. config_charset

Type: string
Default: (empty)

@@ -636,48 +674,102 @@ Sets the default Content-Type for the body of newly composed messages.

3.35. copy

Type: quadoption
Default: yes

This variable controls whether or not copies of your outgoing messages -will be saved for later references. Also see $record, -$save_name, $force_name and “fcc-hook”. -

3.36. crypt_use_gpgme

Type: boolean
+will be saved for later references. Also see $record, +$save_name, $force_name and “fcc-hook”. +

3.36. crypt_autoencrypt

Type: boolean
+Default: no

+Setting this variable will cause Mutt to always attempt to PGP +encrypt outgoing messages. This is probably only useful in +connection to the “send-hook” command. It can be overridden +by use of the pgp menu, when encryption is not required or +signing is requested as well. If $smime_is_default is set, +then OpenSSL is used instead to create S/MIME messages and +settings can be overridden by use of the smime menu instead. +(Crypto only) +

3.37. crypt_autopgp

Type: boolean
+Default: yes

+This variable controls whether or not mutt may automatically enable +PGP encryption/signing for messages. See also $crypt_autoencrypt, +$crypt_replyencrypt, +$crypt_autosign, $crypt_replysign and $smime_is_default. +

3.38. crypt_autosign

Type: boolean
+Default: no

+Setting this variable will cause Mutt to always attempt to +cryptographically sign outgoing messages. This can be overridden +by use of the pgp menu, when signing is not required or +encryption is requested as well. If $smime_is_default is set, +then OpenSSL is used instead to create S/MIME messages and settings can +be overridden by use of the smime menu instead of the pgp menu. +(Crypto only) +

3.39. crypt_autosmime

Type: boolean
+Default: yes

+This variable controls whether or not mutt may automatically enable +S/MIME encryption/signing for messages. See also $crypt_autoencrypt, +$crypt_replyencrypt, +$crypt_autosign, $crypt_replysign and $smime_is_default. +

3.40. crypt_replyencrypt

Type: boolean
+Default: yes

+If set, automatically PGP or OpenSSL encrypt replies to messages which are +encrypted. +(Crypto only) +

3.41. crypt_replysign

Type: boolean
+Default: no

+If set, automatically PGP or OpenSSL sign replies to messages which are +signed. +

+Note: this does not work on messages that are encrypted +and signed! +(Crypto only) +

3.42. crypt_replysignencrypted

Type: boolean
+Default: no

+If set, automatically PGP or OpenSSL sign replies to messages +which are encrypted. This makes sense in combination with +$crypt_replyencrypt, because it allows you to sign all +messages which are automatically encrypted. This works around +the problem noted in $crypt_replysign, that mutt is not able +to find out whether an encrypted message is also signed. +(Crypto only) +

3.43. crypt_timestamp

Type: boolean
+Default: yes

+If set, mutt will include a time stamp in the lines surrounding +PGP or S/MIME output, so spoofing such lines is more difficult. +If you are using colors to mark these lines, and rely on these, +you may unset this setting. +(Crypto only) +

3.44. crypt_use_gpgme

Type: boolean
Default: no

This variable controls the use of the GPGME-enabled crypto backends. If it is set and Mutt was built with gpgme support, the gpgme code for S/MIME and PGP will be used instead of the classic code. Note that you need to set this option in .muttrc; it won't have any effect when used interactively. -

3.37. crypt_use_pka

Type: boolean
+

3.45. crypt_use_pka

Type: boolean
Default: no

Controls whether mutt uses PKA (see http://www.g10code.de/docs/pka-intro.de.pdf) during signature verification (only supported by the GPGME backend). -

3.38. crypt_autopgp

Type: boolean
-Default: yes

-This variable controls whether or not mutt may automatically enable -PGP encryption/signing for messages. See also $crypt_autoencrypt, -$crypt_replyencrypt, -$crypt_autosign, $crypt_replysign and $smime_is_default. -

3.39. crypt_autosmime

Type: boolean
+

3.46. crypt_verify_sig

Type: quadoption
Default: yes

-This variable controls whether or not mutt may automatically enable -S/MIME encryption/signing for messages. See also $crypt_autoencrypt, -$crypt_replyencrypt, -$crypt_autosign, $crypt_replysign and $smime_is_default. -

3.40. date_format

Type: string
+If “yes”, always attempt to verify PGP or S/MIME signatures. +If “ask-*”, ask whether or not to verify the signature. +If \Fi“no”, never attempt to verify cryptographic signatures. +(Crypto only) +

3.47. date_format

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 $index_format. This is passed to the strftime(3) +sequence in $index_format. This is passed to the strftime(3) function to process the date, see the man page for the proper syntax.

Unless the first character in the string is a bang (“!”), the month and week day names are expanded according to the locale specified in -the variable $locale. If the first character in the string is a +the variable $locale. If the first character in the string is a bang, the bang is discarded, and the month and week day names in the rest of the string are expanded in the C locale (that is in US English). -

3.41. default_hook

Type: string
+

3.48. default_hook

Type: string
Default: “˜f %s !˜P | (˜P ˜C %s)”

-This variable controls how “message-hook”, “reply-hook”, “send-hook”, -“send2-hook”, “save-hook”, and “fcc-hook” will +This variable controls how “message-hook”, “reply-hook”, “send-hook”, +“send2-hook”, “save-hook”, and “fcc-hook” will be interpreted if they are specified with only a simple regexp, instead of a matching pattern. The hooks are expanded when they are declared, so a hook will be interpreted according to the value of this @@ -686,33 +778,33 @@ variable at the time the hook is declared. The default value matches if the message is either from a user matching the regular expression given, or if it is from you (if the from address matches -“alternates”) and is to or cc'ed to a user matching the given +“alternates”) and is to or cc'ed to a user matching the given regular expression. -

3.42. delete

Type: quadoption
+

3.49. delete

Type: quadoption
Default: ask-yes

Controls whether or not messages are really deleted when closing or synchronizing a mailbox. If set to yes, messages marked for deleting will automatically be purged without prompting. If set to no, messages marked for deletion will be kept in the mailbox. -

3.43. delete_untag

Type: boolean
+

3.50. delete_untag

Type: boolean
Default: yes

If this option is set, mutt will untag messages when marking them for deletion. This applies when you either explicitly delete a message, or when you save it to another folder. -

3.44. digest_collapse

Type: boolean
+

3.51. digest_collapse

Type: boolean
Default: yes

If this option is set, mutt's received-attachments menu will not show the subparts of individual messages in a multipart/digest. To see these subparts, press “v” on that menu. -

3.45. display_filter

Type: path
+

3.52. display_filter

Type: path
Default: (empty)

When set, specifies a command used to filter messages. When a message -is viewed it is passed as standard input to $display_filter, and the +is viewed it is passed as standard input to $display_filter, and the filtered message is read from the standard output. -

3.46. dotlock_program

Type: path
+

3.53. dotlock_program

Type: path
Default: “/usr/local/bin/mutt_dotlock”

Contains the path of the mutt_dotlock(8) binary to be used by mutt. -

3.47. dsn_notify

Type: string
+

3.54. dsn_notify

Type: string
Default: (empty)

This variable sets the request for when notification is returned. The string consists of a comma separated list (no spaces!) of one or more @@ -725,14 +817,13 @@ Example: 

 set dsn_notify="failure,delay"
-

-Note: when using $sendmail for delivery, you should not enable +Note: when using $sendmail for delivery, you should not enable this unless you are either using Sendmail 8.8.x or greater or a MTA providing a sendmail(1)-compatible interface supporting the -N option for DSN. For SMTP delivery, DSN support is autodetected so that it depends on the server whether DSN will be used or not. -

3.48. dsn_return

Type: string
+

3.55. dsn_return

Type: string
Default: (empty)

This variable controls how much of your message is returned in DSN messages. It may be set to either hdrs to return just the @@ -742,98 +833,103 @@ Example: 

 set dsn_return=hdrs
-

-Note: when using $sendmail for delivery, you should not enable +Note: when using $sendmail for delivery, you should not enable this unless you are either using Sendmail 8.8.x or greater or a MTA providing a sendmail(1)-compatible interface supporting the -R option for DSN. For SMTP delivery, DSN support is autodetected so that it depends on the server whether DSN will be used or not. -

3.49. duplicate_threads

Type: boolean
+

3.56. duplicate_threads

Type: boolean
Default: yes

-This variable controls whether mutt, when $sort is set to threads, threads +This variable controls whether mutt, when $sort is set to threads, threads messages with the same Message-Id together. If it is set, it will indicate that it thinks they are duplicates of each other with an equals sign in the thread tree. -

3.50. edit_headers

Type: boolean
+

3.57. edit_headers

Type: boolean
Default: no

This option allows you to edit the header of your outgoing messages along with the body of your message.

Note that changes made to the References: and Date: headers are ignored for interoperability reasons. -

3.51. editor

Type: path
+

3.58. editor

Type: path
Default: (empty)

This variable specifies which editor is used by mutt. It defaults to the value of the $VISUAL, or $EDITOR, environment variable, or to the string “vi” if neither of those are set. -

3.52. encode_from

Type: boolean
+

3.59. encode_from

Type: boolean
Default: no

When set, mutt will quoted-printable encode messages when they contain the string “From ” (note the trailing space) in the beginning of a line. This is useful to avoid the tampering certain mail delivery and transport agents tend to do with messages (in order to prevent tools from misinterpreting the line as a mbox message separator). -

3.53. envelope_from_address

Type: e-mail address
+

3.60. entropy_file

Type: path
+Default: (empty)

+The file which includes random data that is used to initialize SSL +library functions. +

3.61. envelope_from_address

Type: e-mail address
Default: (empty)

Manually sets the envelope sender for outgoing messages. -This value is ignored if $use_envelope_from is unset. -

3.54. escape

Type: string
+This value is ignored if $use_envelope_from is unset. +

3.62. escape

Type: string
Default: “˜”

Escape character to use for functions in the builtin editor. -

3.55. fast_reply

Type: boolean
+

3.63. fast_reply

Type: boolean
Default: no

When set, the initial prompt for recipients and subject are skipped when replying to messages, and the initial prompt for subject is skipped when forwarding messages.

-Note: this variable has no effect when the $autoedit +Note: this variable has no effect when the $autoedit variable is set. -

3.56. fcc_attach

Type: boolean
+

3.64. fcc_attach

Type: quadoption
Default: yes

This variable controls whether or not attachments on outgoing messages are saved along with the main body of your message. -

3.57. fcc_clear

Type: boolean
+

3.65. fcc_clear

Type: boolean
Default: no

When this variable is set, FCCs will be stored unencrypted and unsigned, even when the actual message is encrypted and/or signed. (PGP only) -

3.58. folder

Type: path
+

3.66. folder

Type: path
Default: “˜/Mail”

Specifies the default location of your mailboxes. A “+” or “=” at the beginning of a pathname will be expanded to the value of this variable. Note that if you change this variable (from the default) value you need to make sure that the assignment occurs before you use “+” or “=” for any other variables since expansion takes place -when handling the “mailboxes” command. -

3.59. folder_format

Type: string
+when handling the “mailboxes” command. +

3.67. folder_format

Type: string
Default: “%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f”

This variable allows you to customize the file browser display to your -personal taste. This string is similar to $index_format, but has +personal taste. This string is similar to $index_format, but has its own set of printf(3)-like sequences: -

%C

current file number -

%d

date/time folder was last modified -

%f

filename -

%F

file permissions -

%g

group name (or numeric gid, if missing) -

%l

number of hard links -

%N

N if folder has new mail, blank otherwise -

%s

size in bytes -

%t

“*” if the file is tagged, blank otherwise -

%u

owner name (or numeric uid, if missing) -

%>X

right justify the rest of the string and pad with character “X” -

%|X

pad to the end of the line with character “X” -

%*X

soft-fill with character “X” as pad -

-For an explanation of “soft-fill”, see the $index_format documentation. -

3.60. followup_to

Type: boolean
+

%C current file number +
%d date/time folder was last modified +
%f filename (“/” is appended to directory names, +“@” to symbolic links and “*” to executable +files) +
%F file permissions +
%g group name (or numeric gid, if missing) +
%l number of hard links +
%N N if folder has new mail, blank otherwise +
%s size in bytes +
%t “*” if the file is tagged, blank otherwise +
%u owner name (or numeric uid, if missing) +
%>X right justify the rest of the string and pad with character “X” +
%|X pad to the end of the line with character “X” +
%*X soft-fill with character “X” as pad +

+For an explanation of “soft-fill”, see the $index_format documentation. +

3.68. followup_to

Type: boolean
Default: yes

Controls whether or not the “Mail-Followup-To:” header field is generated when sending mail. When set, Mutt will generate this field when you are replying to a known mailing list, specified with -the “subscribe” or “lists” commands. +the “subscribe” or “lists” commands.

This field has two purposes. First, preventing you from receiving duplicate copies of replies to messages which you send @@ -847,41 +943,48 @@ email address for unsubscribed lists. Without this header, a group reply to your message sent to a subscribed list will be sent to both the list and your address, resulting in two copies of the same email for you. -

3.61. force_name

Type: boolean
+

3.69. force_name

Type: boolean
Default: no

-This variable is similar to $save_name, except that Mutt will +This variable is similar to $save_name, except that Mutt will store a copy of your outgoing message by the username of the address you are sending to even if that mailbox does not exist.

-Also see the $record variable. -

3.62. forward_decode

Type: boolean
+Also see the $record variable. +

3.70. forward_decode

Type: boolean
Default: yes

Controls the decoding of complex MIME messages into text/plain when forwarding a message. The message header is also RFC2047 decoded. -This variable is only used, if $mime_forward is unset, -otherwise $mime_forward_decode is used instead. -

3.63. forward_edit

Type: quadoption
+This variable is only used, if $mime_forward is unset, +otherwise $mime_forward_decode is used instead. +

3.71. forward_decrypt

Type: boolean
+Default: yes

+Controls the handling of encrypted messages when forwarding a message. +When set, the outer layer of encryption is stripped off. This +variable is only used if $mime_forward is set and +$mime_forward_decode is unset. +(PGP only) +

3.72. forward_edit

Type: quadoption
Default: yes

This quadoption controls whether or not the user is automatically placed in the editor when forwarding messages. For those who always want to forward with no modification, use a setting of “no”. -

3.64. forward_format

Type: string
+

3.73. forward_format

Type: string
Default: “[%a: %s]”

This variable controls the default subject when forwarding a message. -It uses the same format sequences as the $index_format variable. -

3.65. forward_quote

Type: boolean
+It uses the same format sequences as the $index_format variable. +

3.74. forward_quote

Type: boolean
Default: no

When set, forwarded messages included in the main body of the -message (when $mime_forward is unset) will be quoted using -$indent_string. -

3.66. from

Type: e-mail address
+message (when $mime_forward is unset) will be quoted using +$indent_string. +

3.75. from

Type: e-mail address
Default: (empty)

When set, this variable contains a default from address. It -can be overridden using “my_hdr” (including from a “send-hook”) and -$reverse_name. This variable is ignored if $use_from is unset. +can be overridden using “my_hdr” (including from a “send-hook”) and +$reverse_name. This variable is ignored if $use_from is unset.

This setting defaults to the contents of the environment variable $EMAIL. -

3.67. gecos_mask

Type: regular expression
+

3.76. gecos_mask

Type: regular expression
Default: “^[^,]*”

A regular expression used by mutt to parse the GECOS field of a password entry when expanding the alias. The default value @@ -889,23 +992,47 @@ will return the string up to the first “,” encoun If the GECOS field contains a string like “lastname, firstname” then you should set it to “.*”.

-This can be useful if you see the following behavior: you address a e-mail +This can be useful if you see the following behavior: you address an e-mail to user ID “stevef” whose full name is “Steve Franklin”. If mutt expands -“stevef” to “"Franklin" stevef@foo.bar” then you should set the $gecos_mask to +“stevef” to “"Franklin" stevef@foo.bar” then you should set the $gecos_mask to a regular expression that will match the whole name so mutt will expand “Franklin” to “Franklin, Steve”. -

3.68. hdrs

Type: boolean
+

3.77. hdrs

Type: boolean
Default: yes

-When unset, the header fields normally added by the “my_hdr” +When unset, the header fields normally added by the “my_hdr” command are not created. This variable must 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. -

3.69. header

Type: boolean
+

3.78. header

Type: boolean
Default: no

When set, this variable causes Mutt to include the header of the message you are replying to into the edit buffer. -The $weed setting applies. -

3.70. help

Type: boolean
+The $weed setting applies. +

3.79. header_cache

Type: path
+Default: (empty)

+This variable points to the header cache database. +If pointing to a directory Mutt will contain a header cache +database file per folder, if pointing to a file that file will +be a single global header cache. By default it is unset so no header +caching will be used. +

+Header caching can greatly improve speed when opening POP, IMAP +MH or Maildir folders, see “caching” for details. +

3.80. header_cache_compress

Type: boolean
+Default: yes

+When mutt is compiled with qdbm or tokyocabinet as header cache backend, +this option determines whether the database will be compressed. +Compression results in database files roughly being one fifth +of the usual diskspace, but the uncompression can result in a +slower opening of cached folder(s) which in general is still +much faster than opening non header cached folders. +

3.81. header_cache_pagesize

Type: string
+Default: “16384”

+When mutt is compiled with either gdbm or bdb4 as the header cache backend, +this option changes the database page size. Too large or too small +values can waste space, memory, or CPU time. The default should be more +or less optimal for most use cases. +

3.82. help

Type: boolean
Default: yes

When set, help lines describing the bindings for the major functions provided by each menu are displayed on the first line of the screen. @@ -915,48 +1042,57 @@ function is bound to a sequence rather than a single keystroke. Also, the help line may not be updated if a binding is changed while Mutt is running. Since this variable is primarily aimed at new users, neither of these should present a major problem. -

3.71. hidden_host

Type: boolean
+

3.83. hidden_host

Type: boolean
Default: no

-When set, mutt will skip the host name part of $hostname variable +When set, mutt will skip the host name part of $hostname variable when adding the domain part to addresses. This variable does not affect the generation of Message-IDs, and it will not lead to the cut-off of first-level domains. -

3.72. hide_limited

Type: boolean
+

3.84. hide_limited

Type: boolean
Default: no

When set, mutt will not show the presence of messages that are hidden by limiting, in the thread tree. -

3.73. hide_missing

Type: boolean
+

3.85. hide_missing

Type: boolean
Default: yes

When set, mutt will not show the presence of missing messages in the thread tree. -

3.74. hide_thread_subject

Type: boolean
+

3.86. hide_thread_subject

Type: boolean
Default: yes

When set, mutt will not show the subject of messages in the thread tree that have the same subject as their parent or closest previously displayed sibling. -

3.75. hide_top_limited

Type: boolean
+

3.87. hide_top_limited

Type: boolean
Default: no

When set, mutt will not show the presence of messages that are hidden by limiting, at the top of threads in the thread tree. Note that when -$hide_limited is set, this option will have no effect. -

3.76. hide_top_missing

Type: boolean
+$hide_limited is set, this option will have no effect. +

3.88. hide_top_missing

Type: boolean
Default: yes

When set, mutt will not show the presence of missing messages at the -top of threads in the thread tree. Note that when $hide_missing is +top of threads in the thread tree. Note that when $hide_missing is set, this option will have no effect. -

3.77. history

Type: number
+

3.89. history

Type: number
Default: 10

This variable controls the size (in number of strings remembered) of the string history buffer per category. The buffer is cleared each time the variable is set. -

3.78. history_file

Type: path
+

3.90. history_file

Type: path
Default: “˜/.mutthistory”

The file in which Mutt will save its history. -

3.79. honor_followup_to

Type: quadoption
+

3.91. honor_disposition

Type: boolean
+Default: no

+When set, Mutt will not display attachments with a +disposition of “attachment” inline even if it could +render the part to plain text. These MIME parts can only +be viewed from the attachment menu. +

+If unset, Mutt will render all MIME parts it can +properly transform to plain text. +

3.92. honor_followup_to

Type: quadoption
Default: yes

This variable controls whether or not a Mail-Followup-To header is honored when group-replying to a message. -

3.80. hostname

Type: string
+

3.93. hostname

Type: string
Default: (empty)

Specifies the fully-qualified hostname of the system mutt is running on containing the host's name and the DNS domain it belongs to. It is used @@ -965,30 +1101,30 @@ Message-Id headers.

Its value is determined at startup as follows: If the node's name as returned by the uname(3) function contains the hostname and the -domain, these are used to construct $hostname. If there is no +domain, these are used to construct $hostname. If there is no domain part returned, Mutt will look for a “domain” or “search” line in /etc/resolv.conf to determine the domain. Optionally, Mutt can be compiled with a fixed domain name in which case a detected one is not used.

-Also see $use_domain and $hidden_host. -

3.81. ignore_linear_white_space

Type: boolean
+Also see $use_domain and $hidden_host. +

3.94. ignore_linear_white_space

Type: boolean
Default: no

This option replaces linear-white-space between encoded-word and text to a single space to prevent the display of MIME-encoded “Subject:” field from being divided into multiple lines. -

3.82. ignore_list_reply_to

Type: boolean
+

3.95. ignore_list_reply_to

Type: boolean
Default: no

Affects the behaviour of the <reply> function when replying to messages from mailing lists (as defined by the “subscribe” or -“lists” commands). When set, if the “Reply-To:” field is +“lists” commands). When set, if the “Reply-To:” field is set to the same value as the “To:” field, Mutt assumes that the “Reply-To:” field was set by the mailing list to automate responses to the list, and will ignore this field. To direct a response to the mailing list when this option is set, use the <list-reply> function; <group-reply> will reply to both the sender and the list. -

3.83. imap_authenticators

Type: string
+

3.96. imap_authenticators

Type: string
Default: (empty)

This is a colon-delimited list of authentication methods mutt may attempt to use to log in to an IMAP server, in the order mutt should @@ -1002,23 +1138,22 @@ Example: 

 set imap_authenticators="gssapi:cram-md5:login"
-

Note: Mutt will only fall back to other authentication methods if the previous methods are unavailable. If a method is available but authentication fails, mutt will not connect to the IMAP server. -

3.84. imap_check_subscribed

Type: boolean
+

3.97. imap_check_subscribed

Type: boolean
Default: no

When set, mutt will fetch the set of subscribed folders from your server on connection, and add them to the set of mailboxes -it polls for new mail just as if you had issued individual “mailboxes” +it polls for new mail just as if you had issued individual “mailboxes” commands. -

3.85. imap_delim_chars

Type: string
+

3.98. imap_delim_chars

Type: string
Default: “/.”

This contains the list of characters which you would like to treat as folder separators for displaying IMAP paths. In particular it helps in using the “=” shortcut for your folder variable. -

3.86. imap_headers

Type: string
+

3.99. imap_headers

Type: string
Default: (empty)

Mutt requests these header fields in addition to the default headers (“Date:”, “From:”, “Subject:”, “To:”, “Cc:”, “Message-Id:”, @@ -1030,14 +1165,14 @@ headers for spam detection. Note: This is a space separated list, items should be uppercase and not contain the colon, e.g. “X-BOGOSITY X-SPAM-STATUS” for the “X-Bogosity:” and “X-Spam-Status:” header fields. -

3.87. imap_idle

Type: boolean
+

3.100. imap_idle

Type: boolean
Default: no

When set, mutt will attempt to use the IMAP IDLE extension to check for new mail in the current mailbox. Some servers (dovecot was the inspiration for this option) react badly to mutt's implementation. If your connection seems to freeze up periodically, try unsetting this. -

3.88. imap_keepalive

Type: number
+

3.101. imap_keepalive

Type: number
Default: 900

This variable specifies the maximum amount of time in seconds that mutt will wait before polling open IMAP connections, to prevent the server @@ -1046,39 +1181,39 @@ well within the RFC-specified minimum amount of time (30 minutes) before a server is allowed to do this, but in practice the RFC does get violated every now and then. Reduce this number if you find yourself getting disconnected from your IMAP server due to inactivity. -

3.89. imap_list_subscribed

Type: boolean
+

3.102. imap_list_subscribed

Type: boolean
Default: no

This variable configures whether IMAP folder browsing will look for only subscribed folders or all folders. This can be toggled in the IMAP browser with the <toggle-subscribed> function. -

3.90. imap_login

Type: string
+

3.103. imap_login

Type: string
Default: (empty)

Your login name on the IMAP server.

-This variable defaults to the value of $imap_user. -

3.91. imap_pass

Type: string
+This variable defaults to the value of $imap_user. +

3.104. imap_pass

Type: string
Default: (empty)

Specifies the password for your IMAP account. If unset, Mutt will -prompt you for your password when you invoke the <fetch-mail> function +prompt you for your password when you invoke the <imap-fetch-mail> function or try to open an IMAP folder.

Warning: you should only use this option when you are on a fairly secure machine, because the superuser can read your muttrc even if you are the only one who can read the file. -

3.92. imap_passive

Type: boolean
+

3.105. imap_passive

Type: boolean
Default: yes

When set, mutt will not open new IMAP connections to check for new mail. Mutt will only check for new mail over existing IMAP connections. This is useful if you don't want to be prompted to user/password pairs on mutt invocation, or if opening the connection is slow. -

3.93. imap_peek

Type: boolean
+

3.106. imap_peek

Type: boolean
Default: yes

When set, mutt will avoid implicitly marking your mail as read whenever you fetch a message from the server. This is generally a good thing, but can make closing an IMAP folder somewhat slower. This option exists to appease speed freaks. -

3.94. imap_pipeline_depth

Type: number
+

3.107. imap_pipeline_depth

Type: number
Default: 15

Controls the number of IMAP commands that may be queued up before they are sent to the server. A deeper pipeline reduces the amount of time @@ -1087,47 +1222,46 @@ more responsive. But not all servers correctly handle pipelined commands, so if you have problems you might want to try setting this variable to 0.

Note: Changes to this variable have no effect on open connections. -

3.95. imap_servernoise

Type: boolean
+

3.108. imap_servernoise

Type: boolean
Default: yes

When set, mutt will display warning messages from the IMAP server as error messages. Since these messages are often harmless, or generated due to configuration problems on the server which are out of the users' hands, you may wish to suppress them at some point. -

3.96. imap_user

Type: string
+

3.109. imap_user

Type: string
Default: (empty)

The name of the user whose mail you intend to access on the IMAP server.

This variable defaults to your user name on the local machine. -

3.97. implicit_autoview

Type: boolean
+

3.110. implicit_autoview

Type: boolean
Default: no

If set to “yes”, mutt will look for a mailcap entry with the “copiousoutput” flag set for every MIME attachment it doesn't have an internal viewer defined for. If such an entry is found, mutt will use the viewer defined in that entry to convert the body part to text form. -

3.98. include

Type: quadoption
+

3.111. include

Type: quadoption
Default: ask-yes

Controls whether or not a copy of the message(s) you are replying to is included in your reply. -

3.99. include_onlyfirst

Type: boolean
+

3.112. include_onlyfirst

Type: boolean
Default: no

Controls whether or not Mutt includes only the first attachment of the message you are replying. -

3.100. indent_string

Type: string
+

3.113. indent_string

Type: string
Default: “> ”

Specifies the string to prepend to each line of text quoted in a message to which you are replying. You are strongly encouraged not to change this value, as it tends to agitate the more fanatical netizens.

-This option is a format string, please see the description of -$index_format for supported printf(3)-style sequences. +The value of this option is ignored if $text_flowed is set, too because +the quoting mechanism is strictly defined for format=flowed.

-Because for format=lowed style messages the quoting mechanism -is strictly defined, this setting is ignored if $text_flowed is -set. -

3.101. index_format

Type: string
+This option is a format string, please see the description of +$index_format for supported printf(3)-style sequences. +

3.114. index_format

Type: string
Default: “%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s”

This variable allows you to customize the message index display to your personal taste. @@ -1136,63 +1270,63 @@ your personal taste. function printf(3) to format output (see the man page for more details). The following sequences are defined in Mutt: -

%a

address of the author -

%A

reply-to address (if present; otherwise: address of 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 converted to sender's time zone -

%D

date and time of the message in the format specified by -$date_format converted to the local time zone -

%e

current message number in thread -

%E

number of messages in current thread -

%f

sender (address + real name), either From: or Return-Path: -

%F

author name, or recipient name if the message is from you -

%H

spam attribute(s) of this message -

%i

message-id of the current message -

%l

number of lines in the message (does not work with maildir, +

%a address of the author +
%A reply-to address (if present; otherwise: address of 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 converted to sender's time zone +
%D date and time of the message in the format specified by +$date_format converted to the local time zone +
%e current message number in thread +
%E number of messages in current thread +
%f sender (address + real name), either From: or Return-Path: +
%F author name, or recipient name if the message is from you +
%H spam attribute(s) of this message +
%i message-id of the current message +
%l number of lines in the message (does not work with maildir, mh, and possibly IMAP folders) -

%L

If an address in the “To:” or “Cc:” header field matches an address +

%L If an address in the “To:” or “Cc:” header field matches an address defined by the users “subscribe” command, this displays "To <list-name>", otherwise the same as %F. -

%m

total number of message in the mailbox -

%M

number of hidden messages if the thread is collapsed. -

%N

message score -

%n

author's real name (or address if missing) -

%O

original save folder where mutt would formerly have +

%m total number of message in the mailbox +
%M number of hidden messages if the thread is collapsed. +
%N message score +
%n author's real name (or address if missing) +
%O original save folder where mutt would formerly have stashed the message: list name or recipient name if not sent to a list -

%P

progress indicator for the builtin pager (how much of the file has been displayed) -

%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 -

%v

first name of the author, or the recipient if the message is from you -

%X

number of attachments +

%P progress indicator for the builtin pager (how much of the file has been displayed) +
%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 +
%v first name of the author, or the recipient if the message is from you +
%X number of attachments (please see the “attachments” section for possible speed effects) -

%y

“X-Label:” field, if present -

%Y

“X-Label:” field, if present, and (1) not at part of a thread tree, +

%y “X-Label:” field, if present +
%Y “X-Label:” field, if present, and (1) not at part of a thread tree, (2) at the top of a thread, or (3) “X-Label:” is different from preceding message's “X-Label:”. -

%Z

message status flags -

%{fmt}

the date and time of the message is converted to sender's +

%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 library function strftime(3); a leading bang disables locales -

%[fmt]

the date and time of the message is converted to the local +

%[fmt] the date and time of the message is converted to the local time zone, and “fmt” is expanded by the library function strftime(3); a leading bang disables locales -

%(fmt)

the local date and time when the message was received. +

%(fmt) the local date and time when the message was received. “fmt” is expanded by the library function strftime(3); a leading bang disables locales -

%<fmt>

the current local time. “fmt” is expanded by the library +

%<fmt> the current local time. “fmt” is expanded by the library function strftime(3); 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” -

%*X

soft-fill with character “X” as pad -

+

%>X right justify the rest of the string and pad with character “X” +
%|X pad to the end of the line with character “X” +
%*X soft-fill with character “X” as pad +

“Soft-fill” deserves some explanation: Normal right-justification will print everything to the left of the “%>”, displaying padding and whatever lies to the right only if there's room. By contrast, @@ -1202,28 +1336,28 @@ necessary, soft-fill will eat text leftwards to make room for rightward text.

Note that these expandos are supported in -“save-hook”, “fcc-hook” and “fcc-save-hook”, too. -

3.102. ispell

Type: path
+“save-hook”, “fcc-hook” and “fcc-save-hook”, too. +

3.115. ispell

Type: path
Default: “ispell”

How to invoke ispell (GNU's spell-checking software). -

3.103. keep_flagged

Type: boolean
+

3.116. keep_flagged

Type: boolean
Default: no

If set, read messages marked as flagged will not be moved -from your spool mailbox to your $mbox mailbox, or as a result of -a “mbox-hook” command. -

3.104. locale

Type: string
+from your spool mailbox to your $mbox mailbox, or as a result of +a “mbox-hook” command. +

3.117. locale

Type: string
Default: “C”

The locale used by strftime(3) to format dates. Legal values are the strings your system accepts for the locale environment variable $LC_TIME. -

3.105. mail_check

Type: number
+

3.118. mail_check

Type: number
Default: 5

This variable configures how often (in seconds) mutt should look for -new mail. Also see the $timeout variable. -

3.106. mailcap_path

Type: string
+new mail. Also see the $timeout variable. +

3.119. mailcap_path

Type: string
Default: (empty)

This variable specifies which files to consult when attempting to display MIME bodies not directly supported by Mutt. -

3.107. mailcap_sanitize

Type: boolean
+

3.120. mailcap_sanitize

Type: boolean
Default: yes

If set, mutt will restrict possible characters in mailcap % expandos to a well-defined set of safe characters. This is the safe setting, @@ -1231,90 +1365,85 @@ but we are not sure it doesn't break some more advanced MIME stuff.

DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE DOING! -

3.108. header_cache

Type: path
-Default: (empty)

-This variable points to the header cache database. -If pointing to a directory Mutt will contain a header cache -database file per folder, if pointing to a file that file will -be a single global header cache. By default it is unset so no header -caching will be used. -

-Header caching can greatly improve speed when opening POP, IMAP -MH or Maildir folders, see “caching” for details. -

3.109. maildir_header_cache_verify

Type: boolean
+

3.121. maildir_header_cache_verify

Type: boolean
Default: yes

Check for Maildir unaware programs other than mutt having modified maildir files when the header cache is in use. This incurs one stat(2) per message every time the folder is opened (which can be very slow for NFS folders). -

3.110. header_cache_pagesize

Type: string
-Default: “16384”

-When mutt is compiled with either gdbm or bdb4 as the header cache backend, -this option changes the database page size. Too large or too small -values can waste space, memory, or CPU time. The default should be more -or less optimal for most use cases. -

3.111. header_cache_compress

Type: boolean
-Default: yes

-When mutt is compiled with qdbm or tokyocabinet as header cache backend, -this option determines whether the database will be compressed. -Compression results in database files roughly being one fifth -of the usual diskspace, but the uncompression can result in a -slower opening of cached folder(s) which in general is still -much faster than opening non header cached folders. -

3.112. maildir_trash

Type: boolean
+

3.122. maildir_trash

Type: boolean
Default: no

If set, messages marked as deleted will be saved with the maildir trashed flag instead of unlinked. Note: this only applies to maildir-style mailboxes. Setting it will have no effect on other mailbox types. -

3.113. mark_old

Type: boolean
+

3.123. mark_old

Type: boolean
Default: yes

Controls whether or not mutt marks new unread messages as old if you exit a mailbox without reading them. With this option set, the next time you start mutt, the messages will show up with an “O” next to them in the index menu, indicating that they are old. -

3.114. markers

Type: boolean
+

3.124. markers

Type: boolean
Default: yes

Controls the display of wrapped lines in the internal pager. If set, a “+” marker is displayed at the beginning of wrapped lines.

-Also see the $smart_wrap variable. -

3.115. mask

Type: regular expression
+Also see the $smart_wrap variable. +

3.125. mask

Type: regular expression
Default: “!^\.[^.]”

A regular expression used in the file browser, optionally preceded by the not operator “!”. Only files whose names match this mask will be shown. The match is always case-sensitive. -

3.116. mbox

Type: path
+

3.126. mbox

Type: path
Default: “˜/mbox”

-This specifies the folder into which read mail in your $spoolfile +This specifies the folder into which read mail in your $spoolfile folder will be appended.

-Also see the $move variable. -

3.117. mbox_type

Type: folder magic
+Also see the $move variable. +

3.127. mbox_type

Type: folder magic
Default: mbox

The default mailbox type used when creating new folders. May be any of -“mbox”, “MMDF”, “MH” and “Maildir”. -

3.118. metoo

Type: boolean
-Default: no

-If unset, Mutt will remove your address (see the “alternates” -command) from the list of recipients when replying to a message. -

3.119. menu_context

Type: number
+“mbox”, “MMDF”, “MH” and “Maildir”. This is overriden by the +-m command-line option. +

3.128. menu_context

Type: number
Default: 0

This variable controls the number of lines of context that are given -when scrolling through menus. (Similar to $pager_context.) -

3.120. menu_move_off

Type: boolean
+when scrolling through menus. (Similar to $pager_context.) +

3.129. menu_move_off

Type: boolean
Default: yes

When unset, the bottom entry of menus will never scroll up past the bottom of the screen, unless there are less entries than lines. When set, the bottom entry may move off the bottom. -

3.121. menu_scroll

Type: boolean
+

3.130. menu_scroll

Type: boolean
Default: no

When set, menus will be scrolled up or down one line when you attempt to move across a screen boundary. If unset, the screen is cleared and the next or previous page of the menu is displayed (useful for slow links to avoid many redraws). -

3.122. meta_key

Type: boolean
+

3.131. message_cache_clean

Type: boolean
+Default: no

+If set, mutt will clean out obsolete entries from the message cache when +the mailbox is synchronized. You probably only want to set it +every once in a while, since it can be a little slow +(especially for large folders). +

3.132. message_cachedir

Type: path
+Default: (empty)

+Set this to a directory and mutt will cache copies of messages from +your IMAP and POP servers here. You are free to remove entries at any +time. +

+When setting this variable to a directory, mutt needs to fetch every +remote message only once and can perform regular expression searches +as fast as for local folders. +

+Also see the $message_cache_clean variable. +

3.133. message_format

Type: string
+Default: “%s”

+This is the string displayed in the “attachment” menu for +attachments of type message/rfc822. For a full listing of defined +printf(3)-like sequences see the section on $index_format. +

3.134. meta_key

Type: boolean
Default: no

If set, forces Mutt to interpret keystrokes with the high bit (bit 8) set as if the user had pressed the Esc key and whatever key remains @@ -1323,7 +1452,11 @@ has an ASCII value of 0xf8, then this is treated as pressed Esc then “x”. This is because the result of removing the high bit from 0xf8 is 0x78, which is the ASCII character “x”. -

3.123. mh_purge

Type: boolean
+

3.135. metoo

Type: boolean
+Default: no

+If unset, Mutt will remove your address (see the “alternates” +command) from the list of recipients when replying to a message. +

3.136. mh_purge

Type: boolean
Default: no

When unset, mutt will mimic mh's behaviour and rename deleted messages to ,<old file name> in mh folders instead of really deleting @@ -1331,17 +1464,17 @@ them. This leaves the message on disk but makes programs reading the folder ignore it. If the variable is set, the message files will simply be deleted.

-This option is similar to $maildir_trash for Maildir folders. -

3.124. mh_seq_flagged

Type: string
+This option is similar to $maildir_trash for Maildir folders. +

3.137. mh_seq_flagged

Type: string
Default: “flagged”

The name of the MH sequence used for flagged messages. -

3.125. mh_seq_replied

Type: string
+

3.138. mh_seq_replied

Type: string
Default: “replied”

The name of the MH sequence used to tag replied messages. -

3.126. mh_seq_unseen

Type: string
+

3.139. mh_seq_unseen

Type: string
Default: “unseen”

The name of the MH sequence used for unseen messages. -

3.127. mime_forward

Type: quadoption
+

3.140. mime_forward

Type: quadoption
Default: no

When set, the message you are forwarding will be attached as a separate message/rfc822 MIME part instead of included in the main body of the @@ -1350,72 +1483,50 @@ can properly view the message as it was delivered to you. If you like to switch between MIME and not MIME from mail to mail, set this variable to “ask-no” or “ask-yes”.

-Also see $forward_decode and $mime_forward_decode. -

3.128. mime_forward_decode

Type: boolean
+Also see $forward_decode and $mime_forward_decode. +

3.141. mime_forward_decode

Type: boolean
Default: no

Controls the decoding of complex MIME messages into text/plain when -forwarding a message while $mime_forward is set. Otherwise -$forward_decode is used instead. -

3.129. mime_forward_rest

Type: quadoption
+forwarding a message while $mime_forward is set. Otherwise +$forward_decode is used instead. +

3.142. mime_forward_rest

Type: quadoption
Default: yes

When forwarding multiple attachments of a MIME message from the attachment menu, attachments which cannot be decoded in a reasonable manner will be attached to the newly composed message if this option is set. -

3.130. mix_entry_format

Type: string
+

3.143. mix_entry_format

Type: string
Default: “%4n %c %-16s %a”

This variable describes the format of a remailer line on the mixmaster chain selection screen. The following printf(3)-like sequences are supported: -

%n

The running number on the menu. -

%c

Remailer capabilities. -

%s

The remailer's short name. -

%a

The remailer's e-mail address. -

3.131. mixmaster

Type: path
+

%n The running number on the menu. +
%c Remailer capabilities. +
%s The remailer's short name. +
%a The remailer's e-mail address. +

3.144. mixmaster

Type: path
Default: “mixmaster”

This variable contains the path to the Mixmaster binary on your system. It is used with various sets of parameters to gather the list of known remailers, and to finally send a message through the mixmaster chain. -

3.132. move

Type: quadoption
+

3.145. move

Type: quadoption
Default: no

Controls whether or not Mutt will move read messages -from your spool mailbox to your $mbox mailbox, or as a result of -a “mbox-hook” command. -

3.133. message_cachedir

Type: path
-Default: (empty)

-Set this to a directory and mutt will cache copies of messages from -your IMAP and POP servers here. You are free to remove entries at any -time. -

-When setting this variable to a directory, mutt needs to fetch every -remote message only once and can perform regular expression searches -as fast as for local folders. -

-Also see the $message_cache_clean variable. -

3.134. message_cache_clean

Type: boolean
-Default: no

-If set, mutt will clean out obsolete entries from the message cache when -the mailbox is synchronized. You probably only want to set it -every once in a while, since it can be a little slow -(especially for large folders). -

3.135. message_format

Type: string
-Default: “%s”

-This is the string displayed in the “attachment” menu for -attachments of type message/rfc822. For a full listing of defined -printf(3)-like sequences see the section on $index_format. -

3.136. narrow_tree

Type: boolean
+from your spool mailbox to your $mbox mailbox, or as a result of +a “mbox-hook” command. +

3.146. narrow_tree

Type: boolean
Default: no

This variable, when set, makes the thread tree narrower, allowing deeper threads to fit on the screen. -

3.137. net_inc

Type: number
+

3.147. net_inc

Type: number
Default: 10

Operations that expect to transfer a large amount of data over the -network will update their progress every $net_inc kilobytes. +network will update their progress every $net_inc kilobytes. If set to 0, no progress messages will be displayed.

-See also $read_inc, $write_inc and $net_inc. -

3.138. pager

Type: path
+See also $read_inc, $write_inc and $net_inc. +

3.148. pager

Type: path
Default: “builtin”

This variable specifies which pager you would like to use to view messages. The value “builtin” means to use the builtin pager, otherwise this @@ -1426,19 +1537,23 @@ Using an external pager may have some disadvantages: Additional keystrokes are necessary because you can't call mutt functions directly from the pager, and screen resizes cause lines longer than the screen width to be badly formatted in the help menu. -

3.139. pager_context

Type: number
+

3.149. pager_context

Type: number
Default: 0

This variable controls the number of lines of context that are given when displaying the next or previous page in the internal pager. By default, Mutt will display the line after the last one on the screen at the top of the next page (0 lines of context). -

3.140. pager_format

Type: string
+

+This variable also specifies the amount of context given for search +results. If positive, this many lines will be given before a match, +if 0, the match will be top-aligned. +

3.150. pager_format

Type: string
Default: “-%Z- %C/%m: %-20.20n   %s%*  -- (%P)”

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 $index_format +pager. The valid sequences are listed in the $index_format section. -

3.141. pager_index_lines

Type: number
+

3.151. pager_index_lines

Type: number
Default: 0

Determines the number of lines of a mini-index which is shown when in the pager. The current message, unless near the top or bottom of the @@ -1449,141 +1564,22 @@ remain to be read in the current thread. One of the lines is reserved for the status bar from the index, so a setting of 6 will only show 5 lines of the actual index. A value of 0 results in no index being shown. If the number of messages in the current folder -is less than $pager_index_lines, then the index will only use as +is less than $pager_index_lines, then the index will only use as many lines as it needs. -

3.142. pager_stop

Type: boolean
+

3.152. pager_stop

Type: boolean
Default: no

When set, the internal-pager will not move to the next message when you are at the end of a message and invoke the <next-page> function. -

3.143. crypt_autosign

Type: boolean
+

3.153. pgp_auto_decode

Type: boolean
Default: no

-Setting this variable will cause Mutt to always attempt to -cryptographically sign outgoing messages. This can be overridden -by use of the pgp menu, when signing is not required or -encryption is requested as well. If $smime_is_default is set, -then OpenSSL is used instead to create S/MIME messages and settings can -be overridden by use of the smime menu instead of the pgp menu. -(Crypto only) -

3.144. crypt_autoencrypt

Type: boolean
-Default: no

-Setting this variable will cause Mutt to always attempt to PGP -encrypt outgoing messages. This is probably only useful in -connection to the “send-hook” command. It can be overridden -by use of the pgp menu, when encryption is not required or -signing is requested as well. If $smime_is_default is set, -then OpenSSL is used instead to create S/MIME messages and -settings can be overridden by use of the smime menu instead. -(Crypto only) -

3.145. pgp_ignore_subkeys

Type: boolean
-Default: yes

-Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, -the principal key will inherit the subkeys' capabilities. Unset this -if you want to play interesting key selection games. -(PGP only) -

3.146. crypt_replyencrypt

Type: boolean
-Default: yes

-If set, automatically PGP or OpenSSL encrypt replies to messages which are -encrypted. -(Crypto only) -

3.147. crypt_replysign

Type: boolean
-Default: no

-If set, automatically PGP or OpenSSL sign replies to messages which are -signed. -

-Note: this does not work on messages that are encrypted -and signed! -(Crypto only) -

3.148. crypt_replysignencrypted

Type: boolean
-Default: no

-If set, automatically PGP or OpenSSL sign replies to messages -which are encrypted. This makes sense in combination with -$crypt_replyencrypt, because it allows you to sign all -messages which are automatically encrypted. This works around -the problem noted in $crypt_replysign, that mutt is not able -to find out whether an encrypted message is also signed. -(Crypto only) -

3.149. crypt_timestamp

Type: boolean
-Default: yes

-If set, mutt will include a time stamp in the lines surrounding -PGP or S/MIME output, so spoofing such lines is more difficult. -If you are using colors to mark these lines, and rely on these, -you may unset this setting. -(Crypto only) -

3.150. pgp_use_gpg_agent

Type: boolean
-Default: no

-If set, mutt will use a possibly-running gpg-agent(1) process. -(PGP only) -

3.151. crypt_verify_sig

Type: quadoption
-Default: yes

-If “yes”, always attempt to verify PGP or S/MIME signatures. -If “ask-*”, ask whether or not to verify the signature. -If \Fi“no”, never attempt to verify cryptographic signatures. -(Crypto only) -

3.152. smime_is_default

Type: boolean
-Default: no

-The default behaviour of mutt is to use PGP on all auto-sign/encryption -operations. To override and to use OpenSSL instead this must be set. -However, this has no effect while replying, since mutt will automatically -select the same application that was used to sign/encrypt the original -message. (Note that this variable can be overridden by unsetting $crypt_autosmime.) -(S/MIME only) -

3.153. smime_ask_cert_label

Type: boolean
-Default: yes

-This flag controls whether you want to be asked to enter a label -for a certificate about to be added to the database or not. It is -set by default. -(S/MIME only) -

3.154. smime_decrypt_use_default_key

Type: boolean
-Default: yes

-If set (default) this tells mutt to use the default key for decryption. Otherwise, -if managing multiple certificate-key-pairs, mutt will try to use the mailbox-address -to determine the key to use. It will ask you to supply a key, if it can't find one. -(S/MIME only) -

3.155. pgp_entry_format

Type: string
-Default: “%4n %t%f %4l/0x%k %-4a %2c %u”

-This variable allows you to customize the PGP key selection menu to -your personal taste. This string is similar to $index_format, but -has its own set of printf(3)-like sequences: - -

%n

number -

%k

key id -

%u

user id -

%a

algorithm -

%l

key length -

%f

flags -

%c

capabilities -

%t

trust/validity of the key-uid association -

%[<s>]

date of the key where <s> is an strftime(3) expression -

-(PGP only) -

3.156. pgp_good_sign

Type: regular expression
-Default: (empty)

-If you assign a text to this variable, then a PGP signature is only -considered verified if the output from $pgp_verify_command contains -the text. Use this variable if the exit code from the command is 0 -even for bad signatures. -(PGP only) -

3.157. pgp_check_exit

Type: boolean
-Default: yes

-If set, mutt will check the exit code of the PGP subprocess when -signing or encrypting. A non-zero exit code means that the -subprocess failed. -(PGP only) -

3.158. pgp_long_ids

Type: boolean
-Default: no

-If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs. -(PGP only) -

3.159. pgp_retainable_sigs

Type: boolean
-Default: no

-If set, signed and encrypted messages will consist of nested -multipart/signed and multipart/encrypted body parts. -

-This is useful for applications like encrypted and signed mailing -lists, where the outer layer (multipart/encrypted) can be easily -removed, while the inner multipart/signed part is retained. -(PGP only) -

3.160. pgp_autoinline

Type: boolean
+If set, mutt will automatically attempt to decrypt traditional PGP +messages whenever the user performs an operation which ordinarily would +result in the contents of the message being operated on. For example, +if the user displays a pgp-traditional message which has not been manually +checked with the <check-traditional-pgp> function, mutt will automatically +check the message for traditional pgp. +

3.154. pgp_autoinline

Type: boolean
Default: no

This option controls whether Mutt generates old-style inline (traditional) PGP encrypted or signed messages under certain @@ -1595,447 +1591,278 @@ which consist of more than a single MIME part. Mutt can be configured to ask before sending PGP/MIME messages when inline (traditional) would not work.

-Also see the $pgp_mime_auto variable. +Also see the $pgp_mime_auto variable.

Also note that using the old-style PGP message format is strongly deprecated. (PGP only) -

3.161. pgp_replyinline

Type: boolean
-Default: no

-Setting this variable will cause Mutt to always attempt to -create an inline (traditional) message when replying to a -message which is PGP encrypted/signed inline. This can be -overridden by use of the pgp menu, when inline is not -required. This option does not automatically detect if the -(replied-to) message is inline; instead it relies on Mutt -internals for previously checked/flagged messages. -

-Note that Mutt might automatically use PGP/MIME for messages -which consist of more than a single MIME part. Mutt can be -configured to ask before sending PGP/MIME messages when inline -(traditional) would not work. -

-Also see the $pgp_mime_auto variable. -

-Also note that using the old-style PGP message format is strongly -deprecated. -(PGP only) -

3.162. pgp_show_unusable

Type: boolean
+

3.155. pgp_check_exit

Type: boolean
Default: yes

-If set, mutt will display non-usable keys on the PGP key selection -menu. This includes keys which have been revoked, have expired, or -have been marked as “disabled” by the user. +If set, mutt will check the exit code of the PGP subprocess when +signing or encrypting. A non-zero exit code means that the +subprocess failed. (PGP only) -

3.163. pgp_sign_as

Type: string
+

3.156. pgp_clearsign_command

Type: string
Default: (empty)

-If you have more than one key pair, this option allows you to specify -which of your private keys to use. It is recommended that you use the -keyid form to specify your key (e.g. 0x00112233). -(PGP only) -

3.164. pgp_strict_enc

Type: boolean
-Default: yes

-If set, Mutt will automatically encode PGP/MIME signed messages as -quoted-printable. Please note that unsetting this variable may -lead to problems with non-verifyable PGP signatures, so only change -this if you know what you are doing. -(PGP only) -

3.165. pgp_timeout

Type: number
-Default: 300

-The number of seconds after which a cached passphrase will expire if -not used. -(PGP only) -

3.166. pgp_sort_keys

Type: sort order
-Default: address

-Specifies how the entries in the pgp menu are sorted. The -following are legal values: - -

address

sort alphabetically by user id -

keyid

sort alphabetically by key id -

date

sort by key creation date -

trust

sort by the trust of the key -

-If you prefer reverse order of the above values, prefix it with -“reverse-”. -(PGP only) -

3.167. pgp_mime_auto

Type: quadoption
-Default: ask-yes

-This option controls whether Mutt will prompt you for -automatically sending a (signed/encrypted) message using -PGP/MIME when inline (traditional) fails (for any reason). -

-Also note that using the old-style PGP message format is strongly +This format is used to create an old-style “clearsigned” PGP +message. Note that the use of this format is strongly deprecated. +

+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. (PGP only) -

3.168. pgp_auto_decode

Type: boolean
-Default: no

-If set, mutt will automatically attempt to decrypt traditional PGP -messages whenever the user performs an operation which ordinarily would -result in the contents of the message being operated on. For example, -if the user displays a pgp-traditional message which has not been manually -checked with the <check-traditional-pgp> function, mutt will automatically -check the message for traditional pgp. -

3.169. pgp_decode_command

Type: string
+

3.157. pgp_decode_command

Type: string
Default: (empty)

This format strings specifies a command which is used to decode application/pgp attachments.

The PGP command formats have their own set of printf(3)-like sequences: -

%p

Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty +

%p Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty string otherwise. Note: This may be used with a %? construct. -

%f

Expands to the name of a file containing a message. -

%s

Expands to the name of a file containing the signature part +

%f Expands to the name of a file containing a message. +
%s Expands to the name of a file containing the signature part of a multipart/signed attachment when verifying it. -

%a

The value of $pgp_sign_as. -

%r

One or more key IDs. -

+

%a The value of $pgp_sign_as. +
%r One or more key IDs. +

For examples on how to configure these formats for the various versions of PGP which are floating around, see the pgp and gpg sample configuration files in the samples/ subdirectory which has been installed on your system alongside the documentation. (PGP only) -

3.170. pgp_getkeys_command

Type: string
-Default: (empty)

-This command is invoked whenever mutt will need public key information. -Of the sequences supported by $pgp_decode_command, %r is the only -printf(3)-like sequence used with this format. -(PGP only) -

3.171. pgp_verify_command

Type: string
-Default: (empty)

-This command is used to verify PGP signatures. -

-This is a format string, see the $pgp_decode_command command for -possible printf(3)-like sequences. -(PGP only) -

3.172. pgp_decrypt_command

Type: string
+

3.158. pgp_decrypt_command

Type: string
Default: (empty)

This command is used to decrypt a PGP encrypted message.

-This is a format string, see the $pgp_decode_command command for -possible printf(3)-like sequences. -(PGP only) -

3.173. pgp_clearsign_command

Type: string
-Default: (empty)

-This format is used to create a old-style “clearsigned” PGP -message. Note that the use of this format is strongly -deprecated. -

-This is a format string, see the $pgp_decode_command command for +This is a format string, see the $pgp_decode_command command for possible printf(3)-like sequences. (PGP only) -

3.174. pgp_sign_command

Type: string
+

3.159. pgp_encrypt_only_command

Type: string
Default: (empty)

-This command is used to create the detached PGP signature for a -multipart/signed PGP/MIME body part. +This command is used to encrypt a body part without signing it.

-This is a format string, see the $pgp_decode_command command for +This is a format string, see the $pgp_decode_command command for possible printf(3)-like sequences. (PGP only) -

3.175. pgp_encrypt_sign_command

Type: string
+

3.160. pgp_encrypt_sign_command

Type: string
Default: (empty)

This command is used to both sign and encrypt a body part.

-This is a format string, see the $pgp_decode_command command for +This is a format string, see the $pgp_decode_command command for possible printf(3)-like sequences. (PGP only) -

3.176. pgp_encrypt_only_command

Type: string
+

3.161. pgp_entry_format

Type: string
+Default: “%4n %t%f %4l/0x%k %-4a %2c %u”

+This variable allows you to customize the PGP key selection menu to +your personal taste. This string is similar to $index_format, but +has its own set of printf(3)-like sequences: + +

%n number +
%k key id +
%u user id +
%a algorithm +
%l key length +
%f flags +
%c capabilities +
%t trust/validity of the key-uid association +
%[<s>] date of the key where <s> is an strftime(3) expression +

+(PGP only) +

3.162. pgp_export_command

Type: string
Default: (empty)

-This command is used to encrypt a body part without signing it. +This command is used to export a public key from the user's +key ring.

-This is a format string, see the $pgp_decode_command command for +This is a format string, see the $pgp_decode_command command for possible printf(3)-like sequences. (PGP only) -

3.177. pgp_import_command

Type: string
+

3.163. pgp_getkeys_command

Type: string
Default: (empty)

-This command is used to import a key from a message into -the user's public key ring. -

-This is a format string, see the $pgp_decode_command command for -possible printf(3)-like sequences. +This command is invoked whenever mutt will need public key information. +Of the sequences supported by $pgp_decode_command, %r is the only +printf(3)-like sequence used with this format. (PGP only) -

3.178. pgp_export_command

Type: string
+

3.164. pgp_good_sign

Type: regular expression
Default: (empty)

-This command is used to export a public key from the user's -key ring. -

-This is a format string, see the $pgp_decode_command command for -possible printf(3)-like sequences. +If you assign a text to this variable, then a PGP signature is only +considered verified if the output from $pgp_verify_command contains +the text. Use this variable if the exit code from the command is 0 +even for bad signatures. +(PGP only) +

3.165. pgp_ignore_subkeys

Type: boolean
+Default: yes

+Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, +the principal key will inherit the subkeys' capabilities. Unset this +if you want to play interesting key selection games. (PGP only) -

3.179. pgp_verify_key_command

Type: string
+

3.166. pgp_import_command

Type: string
Default: (empty)

-This command is used to verify key information from the key selection -menu. +This command is used to import a key from a message into +the user's public key ring.

-This is a format string, see the $pgp_decode_command command for +This is a format string, see the $pgp_decode_command command for possible printf(3)-like sequences. (PGP only) -

3.180. pgp_list_secring_command

Type: string
+

3.167. pgp_list_pubring_command

Type: string
Default: (empty)

-This command is used to list the secret key ring's contents. The -output format must be analogous to the one used by: +This command is used to list the public key ring's contents. The +output format must be analogous to the one used by 

 gpg --list-keys --with-colons.
-

This format is also generated by the pgpring utility which comes with mutt.

-This is a format string, see the $pgp_decode_command command for +This is a format string, see the $pgp_decode_command command for possible printf(3)-like sequences. (PGP only) -

3.181. pgp_list_pubring_command

Type: string
+

3.168. pgp_list_secring_command

Type: string
Default: (empty)

-This command is used to list the public key ring's contents. The -output format must be analogous to the one used by +This command is used to list the secret key ring's contents. The +output format must be analogous to the one used by: 

 gpg --list-keys --with-colons.
-

This format is also generated by the pgpring utility which comes with mutt.

-This is a format string, see the $pgp_decode_command command for +This is a format string, see the $pgp_decode_command command for possible printf(3)-like sequences. (PGP only) -

3.182. forward_decrypt

Type: boolean
-Default: yes

-Controls the handling of encrypted messages when forwarding a message. -When set, the outer layer of encryption is stripped off. This -variable is only used if $mime_forward is set and -$mime_forward_decode is unset. +

3.169. pgp_long_ids

Type: boolean
+Default: no

+If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs. (PGP only) -

3.183. smime_timeout

Type: number
-Default: 300

-The number of seconds after which a cached passphrase will expire if -not used. -(S/MIME only) -

3.184. smime_encrypt_with

Type: string
-Default: (empty)

-This sets the algorithm that should be used for encryption. -Valid choices are “des”, “des3”, “rc2-40”, “rc2-64”, “rc2-128”. -If unset, “3des” (TripleDES) is used. -(S/MIME only) -

3.185. smime_keys

Type: path
-Default: (empty)

-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle -storage and retrieval of keys/certs by itself. This is very basic right now, -and stores keys and certificates in two different directories, both -named as the hash-value retrieved from OpenSSL. There is an index file -which contains mailbox-address keyid pair, and which can be manually -edited. This option points to the location of the private keys. -(S/MIME only) -

3.186. smime_ca_location

Type: path
-Default: (empty)

-This variable contains the name of either a directory, or a file which -contains trusted certificates for use with OpenSSL. -(S/MIME only) -

3.187. smime_certificates

Type: path
-Default: (empty)

-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle -storage and retrieval of keys by itself. This is very basic right -now, and keys and certificates are stored in two different -directories, both named as the hash-value retrieved from -OpenSSL. There is an index file which contains mailbox-address -keyid pairs, and which can be manually edited. This option points to -the location of the certificates. -(S/MIME only) -

3.188. smime_decrypt_command

Type: string
-Default: (empty)

-This format string specifies a command which is used to decrypt -application/x-pkcs7-mime attachments. -

-The OpenSSL command formats have their own set of printf(3)-like sequences -similar to PGP's: - -

%f

Expands to the name of a file containing a message. -

%s

Expands to the name of a file containing the signature part - of a multipart/signed attachment when verifying it. -

%k

The key-pair specified with $smime_default_key -

%c

One or more certificate IDs. -

%a

The algorithm used for encryption. -

%C

CA location: Depending on whether $smime_ca_location - points to a directory or file, this expands to - “-CApath $smime_ca_location” or “-CAfile $smime_ca_location”. -

-For examples on how to configure these formats, see the smime.rc in -the samples/ subdirectory which has been installed on your system -alongside the documentation. -(S/MIME only) -

3.189. smime_verify_command

Type: string
-Default: (empty)

-This command is used to verify S/MIME signatures of type multipart/signed. -

-This is a format string, see the $smime_decrypt_command command for -possible printf(3)-like sequences. -(S/MIME only) -

3.190. smime_verify_opaque_command

Type: string
-Default: (empty)

-This command is used to verify S/MIME signatures of type -application/x-pkcs7-mime. -

-This is a format string, see the $smime_decrypt_command command for -possible printf(3)-like sequences. -(S/MIME only) -

3.191. smime_sign_command

Type: string
-Default: (empty)

-This command is used to created S/MIME signatures of type -multipart/signed, which can be read by all mail clients. -

-This is a format string, see the $smime_decrypt_command command for -possible printf(3)-like sequences. -(S/MIME only) -

3.192. smime_sign_opaque_command

Type: string
-Default: (empty)

-This command is used to created S/MIME signatures of type -application/x-pkcs7-signature, which can only be handled by mail -clients supporting the S/MIME extension. +

3.170. pgp_mime_auto

Type: quadoption
+Default: ask-yes

+This option controls whether Mutt will prompt you for +automatically sending a (signed/encrypted) message using +PGP/MIME when inline (traditional) fails (for any reason).

-This is a format string, see the $smime_decrypt_command command for -possible printf(3)-like sequences. -(S/MIME only) -

3.193. smime_encrypt_command

Type: string
-Default: (empty)

-This command is used to create encrypted S/MIME messages. +Also note that using the old-style PGP message format is strongly +deprecated. +(PGP only) +

3.171. pgp_replyinline

Type: boolean
+Default: no

+Setting this variable will cause Mutt to always attempt to +create an inline (traditional) message when replying to a +message which is PGP encrypted/signed inline. This can be +overridden by use of the pgp menu, when inline is not +required. This option does not automatically detect if the +(replied-to) message is inline; instead it relies on Mutt +internals for previously checked/flagged messages.

-This is a format string, see the $smime_decrypt_command command for -possible printf(3)-like sequences. -(S/MIME only) -

3.194. smime_pk7out_command

Type: string
-Default: (empty)

-This command is used to extract PKCS7 structures of S/MIME signatures, -in order to extract the public X509 certificate(s). +Note that Mutt might automatically use PGP/MIME for messages +which consist of more than a single MIME part. Mutt can be +configured to ask before sending PGP/MIME messages when inline +(traditional) would not work.

-This is a format string, see the $smime_decrypt_command command for -possible printf(3)-like sequences. -(S/MIME only) -

3.195. smime_get_cert_command

Type: string
-Default: (empty)

-This command is used to extract X509 certificates from a PKCS7 structure. +Also see the $pgp_mime_auto variable.

-This is a format string, see the $smime_decrypt_command command for -possible printf(3)-like sequences. -(S/MIME only) -

3.196. smime_get_signer_cert_command

Type: string
-Default: (empty)

-This command is used to extract only the signers X509 certificate from a S/MIME -signature, so that the certificate's owner may get compared to the -email's “From:” field. +Also note that using the old-style PGP message format is strongly +deprecated. +(PGP only) +

3.172. pgp_retainable_sigs

Type: boolean
+Default: no

+If set, signed and encrypted messages will consist of nested +multipart/signed and multipart/encrypted body parts.

-This is a format string, see the $smime_decrypt_command command for -possible printf(3)-like sequences. -(S/MIME only) -

3.197. smime_import_cert_command

Type: string
+This is useful for applications like encrypted and signed mailing +lists, where the outer layer (multipart/encrypted) can be easily +removed, while the inner multipart/signed part is retained. +(PGP only) +

3.173. pgp_show_unusable

Type: boolean
+Default: yes

+If set, mutt will display non-usable keys on the PGP key selection +menu. This includes keys which have been revoked, have expired, or +have been marked as “disabled” by the user. +(PGP only) +

3.174. pgp_sign_as

Type: string
Default: (empty)

-This command is used to import a certificate via smime_keys. -

-This is a format string, see the $smime_decrypt_command command for -possible printf(3)-like sequences. -(S/MIME only) -

3.198. smime_get_cert_email_command

Type: string
+If you have more than one key pair, this option allows you to specify +which of your private keys to use. It is recommended that you use the +keyid form to specify your key (e.g. 0x00112233). +(PGP only) +

3.175. pgp_sign_command

Type: string
Default: (empty)

-This command is used to extract the mail address(es) used for storing -X509 certificates, and for verification purposes (to check whether the -certificate was issued for the sender's mailbox). +This command is used to create the detached PGP signature for a +multipart/signed PGP/MIME body part.

-This is a format string, see the $smime_decrypt_command command for +This is a format string, see the $pgp_decode_command command for possible printf(3)-like sequences. -(S/MIME only) -

3.199. smime_default_key

Type: string
-Default: (empty)

-This is the default key-pair to use for signing. This must be set to the -keyid (the hash-value that OpenSSL generates) to work properly -(S/MIME only) -

3.200. ssl_client_cert

Type: path
-Default: (empty)

-The file containing a client certificate and its associated private -key. -

3.201. ssl_force_tls

Type: boolean
-Default: no

-If this variable is set, Mutt will require that all connections -to remote servers be encrypted. Furthermore it will attempt to -negotiate TLS even if the server does not advertise the capability, -since it would otherwise have to abort the connection anyway. This -option supersedes $ssl_starttls. -

3.202. ssl_starttls

Type: quadoption
-Default: yes

-If set (the default), mutt will attempt to use STARTTLS on servers -advertising the capability. When unset, mutt will not attempt to -use STARTTLS regardless of the server's capabilities. -

3.203. certificate_file

Type: path
-Default: “˜/.mutt_certificates”

-This variable specifies the file where the certificates you trust -are saved. When an unknown certificate is encountered, you are asked -if you accept it or not. If you accept it, the certificate can also -be saved in this file and further connections are automatically -accepted. -

-You can also manually add CA certificates in this file. Any server -certificate that is signed with one of these CA certificates is -also automatically accepted. -

-Example: - -

-set certificate_file=~/.mutt/certificates
+(PGP only)
+

3.176. pgp_sort_keys

Type: sort order
+Default: address

+Specifies how the entries in the pgp menu are sorted. The +following are legal values: -

3.204. ssl_usesystemcerts

Type: boolean
-Default: yes

-If set to yes, mutt will use CA certificates in the -system-wide certificate store when checking if a server certificate -is signed by a trusted CA. -

3.205. entropy_file

Type: path
-Default: (empty)

-The file which includes random data that is used to initialize SSL -library functions. -

3.206. ssl_use_sslv2

Type: boolean
-Default: yes

-This variables specifies whether to attempt to use SSLv2 in the -SSL authentication process. -

3.207. ssl_use_sslv3

Type: boolean
-Default: yes

-This variables specifies whether to attempt to use SSLv3 in the -SSL authentication process. -

3.208. ssl_use_tlsv1

Type: boolean
+

address sort alphabetically by user id +
keyid sort alphabetically by key id +
date sort by key creation date +
trust sort by the trust of the key +

+If you prefer reverse order of the above values, prefix it with +“reverse-”. +(PGP only) +

3.177. pgp_strict_enc

Type: boolean
Default: yes

-This variables specifies whether to attempt to use TLSv1 in the -SSL authentication process. -

3.209. ssl_min_dh_prime_bits

Type: number
-Default: 0

-This variable specifies the minimum acceptable prime size (in bits) -for use in any Diffie-Hellman key exchange. A value of 0 will use -the default from the GNUTLS library. -

3.210. ssl_ca_certificates_file

Type: path
+If set, Mutt will automatically encode PGP/MIME signed messages as +quoted-printable. Please note that unsetting this variable may +lead to problems with non-verifyable PGP signatures, so only change +this if you know what you are doing. +(PGP only) +

3.178. pgp_timeout

Type: number
+Default: 300

+The number of seconds after which a cached passphrase will expire if +not used. +(PGP only) +

3.179. pgp_use_gpg_agent

Type: boolean
+Default: no

+If set, mutt will use a possibly-running gpg-agent(1) process. +(PGP only) +

3.180. pgp_verify_command

Type: string
Default: (empty)

-This variable specifies a file containing trusted CA certificates. -Any server certificate that is signed with one of these CA -certificates is also automatically accepted. +This command is used to verify PGP signatures.

-Example: - -

-set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-
-

3.211. pipe_split

Type: boolean
-Default: no

-Used in connection with the <pipe-message> function following -<tag-prefix>. If this variable is unset, when piping a list of -tagged messages Mutt will concatenate the messages and will pipe them -all concatenated. When set, Mutt will pipe the messages one by one. -In both cases the messages are piped in the current sorted order, -and the $pipe_sep separator is added after each message. -

3.212. pipe_decode

Type: boolean
+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. +(PGP only) +

3.181. pgp_verify_key_command

Type: string
+Default: (empty)

+This command is used to verify key information from the key selection +menu. +

+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. +(PGP only) +

3.182. pipe_decode

Type: boolean
Default: no

Used in connection with the <pipe-message> command. When unset, Mutt will pipe the messages without any preprocessing. When set, Mutt will weed headers and will attempt to decode the messages first. -

3.213. pipe_sep

Type: string
+

3.183. pipe_sep

Type: string
Default: “\n”

The separator to add between messages when piping a list of tagged messages to an external Unix command. -

3.214. pop_authenticators

Type: string
+

3.184. pipe_split

Type: boolean
+Default: no

+Used in connection with the <pipe-message> function following +<tag-prefix>. If this variable is unset, when piping a list of +tagged messages Mutt will concatenate the messages and will pipe them +all concatenated. When set, Mutt will pipe the messages one by one. +In both cases the messages are piped in the current sorted order, +and the $pipe_sep separator is added after each message. +

3.185. pop_auth_try_all

Type: boolean
+Default: yes

+If set, Mutt will try all available authentication methods. +When unset, Mutt will only fall back to other authentication +methods if the previous methods are unavailable. If a method is +available but authentication fails, Mutt will not connect to the POP server. +

3.186. pop_authenticators

Type: string
Default: (empty)

This is a colon-delimited list of authentication methods mutt may attempt to use to log in to an POP server, in the order mutt should @@ -2049,47 +1876,30 @@ Example: 

 set pop_authenticators="digest-md5:apop:user"
-
-

3.215. pop_auth_try_all

Type: boolean
-Default: yes

-If set, Mutt will try all available authentication methods. -When unset, Mutt will only fall back to other authentication -methods if the previous methods are unavailable. If a method is -available but authentication fails, Mutt will not connect to the POP server. -

3.216. pop_checkinterval

Type: number
+

3.187. pop_checkinterval

Type: number
Default: 60

This variable configures how often (in seconds) mutt should look for new mail in the currently selected mailbox if it is a POP mailbox. -

3.217. pop_delete

Type: quadoption
+

3.188. pop_delete

Type: quadoption
Default: ask-no

If set, Mutt will delete successfully downloaded messages from the POP server when using the <fetch-mail> function. When unset, Mutt will download messages but also leave them on the POP server. -

3.218. pop_host

Type: string
+

3.189. pop_host

Type: string
Default: (empty)

The name of your POP server for the <fetch-mail> function. You can also specify an alternative port, username and password, ie: 

 [pop[s]://][username[:password]@]popserver[:port]
-

where “[...]” denotes an optional part. -

3.219. pop_last

Type: boolean
+

3.190. pop_last

Type: boolean
Default: no

If this variable is set, mutt will try to use the “LAST” POP command for retrieving only unread messages from the POP server when using the <fetch-mail> function. -

3.220. pop_reconnect

Type: quadoption
-Default: ask-yes

-Controls whether or not Mutt will try to reconnect to the POP server if -the connection is lost. -

3.221. pop_user

Type: string
-Default: (empty)

-Your login name on the POP server. -

-This variable defaults to your user name on the local machine. -

3.222. pop_pass

Type: string
+

3.191. pop_pass

Type: string
Default: (empty)

Specifies the password for your POP account. If unset, Mutt will prompt you for your password when you open a POP mailbox. @@ -2097,24 +1907,33 @@ prompt you for your password when you open a POP mailbox. Warning: you should only use this option when you are on a fairly secure machine, because the superuser can read your muttrc even if you are the only one who can read the file. -

3.223. post_indent_string

Type: string
+

3.192. pop_reconnect

Type: quadoption
+Default: ask-yes

+Controls whether or not Mutt will try to reconnect to the POP server if +the connection is lost. +

3.193. pop_user

Type: string
+Default: (empty)

+Your login name on the POP server. +

+This variable defaults to your user name on the local machine. +

3.194. post_indent_string

Type: string
Default: (empty)

Similar to the $attribution variable, Mutt will append this string after the inclusion of a message which is being replied to. -

3.224. postpone

Type: quadoption
+

3.195. postpone

Type: quadoption
Default: ask-yes

-Controls whether or not messages are saved in the $postponed +Controls whether or not messages are saved in the $postponed mailbox when you elect not to send immediately.

-Also see the $recall variable. -

3.225. postponed

Type: path
+Also see the $recall variable. +

3.196. postponed

Type: path
Default: “˜/postponed”

-Mutt allows you to indefinitely “postpone sending a message” which +Mutt allows you to indefinitely “postpone sending a message” which you are editing. When you choose to postpone a message, Mutt saves it in the mailbox specified by this variable.

-Also see the $postpone variable. -

3.226. preconnect

Type: string
+Also see the $postpone variable. +

3.197. preconnect

Type: string
Default: (empty)

If set, a shell command to be executed if mutt fails to establish a connection to the server. This is useful for setting up secure @@ -2124,77 +1943,76 @@ status, mutt gives up opening the server. Example: 

 set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \
 sleep 20 < /dev/null > /dev/null"
-

Mailbox “foo” on “mailhost.net” can now be reached as “{localhost:1234}foo”.

Note: For this example to work, you must be able to log in to the remote machine without having to enter a password. -

3.227. print

Type: quadoption
+

3.198. print

Type: quadoption
Default: ask-no

Controls whether or not Mutt really prints messages. This is set to “ask-no” by default, because some people accidentally hit “p” often. -

3.228. print_command

Type: path
+

3.199. print_command

Type: path
Default: “lpr”

This specifies the command pipe that should be used to print messages. -

3.229. print_decode

Type: boolean
+

3.200. print_decode

Type: boolean
Default: yes

Used in connection with the <print-message> command. If this option is set, the message is decoded before it is passed to the -external command specified by $print_command. If this option +external command specified by $print_command. If this option is unset, no processing will be applied to the message when printing it. The latter setting may be useful if you are using some advanced printer filter which is able to properly format e-mail messages for printing. -

3.230. print_split

Type: boolean
+

3.201. print_split

Type: boolean
Default: no

Used in connection with the <print-message> command. If this option -is set, the command specified by $print_command is executed once for +is set, the command specified by $print_command is executed once for each message which is to be printed. If this option is unset, -the command specified by $print_command is executed only once, and +the command specified by $print_command is executed only once, and all the messages are concatenated, with a form feed as the message separator.

Those who use the enscript(1) program's mail-printing mode will most likely want to set this option. -

3.231. prompt_after

Type: boolean
+

3.202. prompt_after

Type: boolean
Default: yes

-If you use an external $pager, setting this variable will +If you use an external $pager, setting this variable will cause Mutt to prompt you for a command when the pager exits rather than returning to the index menu. If unset, Mutt will return to the index menu when the external pager exits. -

3.232. query_command

Type: path
+

3.203. query_command

Type: path
Default: (empty)

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. -

3.233. query_format

Type: string
+

3.204. query_format

Type: string
Default: “%4c %t %-25.25a %-25.25n %?e?(%e)?”

This variable describes the format of the “query” menu. The following printf(3)-style sequences are understood: -

%a

destination address -

%c

current entry number -

%e

extra information * -

%n

destination name -

%t

“*” if current entry is tagged, a space otherwise -

%>X

right justify the rest of the string and pad with “X” -

%|X

pad to the end of the line with “X” -

%*X

soft-fill with character “X” as pad -

-For an explanation of “soft-fill”, see the $index_format documentation. -

-* = can be optionally printed if nonzero, see the $status_format documentation. -

3.234. quit

Type: quadoption
+

%a destination address +
%c current entry number +
%e extra information * +
%n destination name +
%t “*” if current entry is tagged, a space otherwise +
%>X right justify the rest of the string and pad with “X” +
%|X pad to the end of the line with “X” +
%*X soft-fill with character “X” as pad +

+For an explanation of “soft-fill”, see the $index_format documentation. +

+* = can be optionally printed if nonzero, see the $status_format documentation. +

3.205. quit

Type: quadoption
Default: yes

This variable controls whether “quit” and “exit” actually quit from mutt. If this option is set, they do quit, if it is unset, 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. -

3.235. quote_regexp

Type: regular expression
+

3.206. quote_regexp

Type: regular expression
Default: “^([ \t]*[|>:}#])+”

A regular expression used in the internal pager to determine quoted sections of text in the body of a message. Quoted text may be filtered @@ -2206,8 +2024,8 @@ Higher levels of quoting may be colored differently (“colo the last character from the matched text and recursively reapplying the regular expression until it fails to produce a match.

-Match detection may be overridden by the $smileys regular expression. -

3.236. read_inc

Type: number
+Match detection may be overridden by the $smileys regular expression. +

3.207. read_inc

Type: number
Default: 10

If set to a value greater than 0, Mutt will display which message it is currently on when reading a mailbox or when performing search actions @@ -2219,20 +2037,20 @@ reading or searching large mailboxes which may take some time. When set to 0, only a single message will appear before the reading the mailbox.

-Also see the $write_inc, $net_inc and $time_inc variables and the -“tuning” section of the manual for performance considerations. -

3.237. read_only

Type: boolean
+Also see the $write_inc, $net_inc and $time_inc variables and the +“tuning” section of the manual for performance considerations. +

3.208. read_only

Type: boolean
Default: no

If set, all folders are opened in read-only mode. -

3.238. realname

Type: string
+

3.209. realname

Type: string
Default: (empty)

This variable specifies what “real” or “personal” name should be used when sending messages.

By default, this is the GECOS field from /etc/passwd. Note that this variable will not be used when the user has set a real name -in the $from variable. -

3.239. recall

Type: quadoption
+in the $from variable. +

3.210. recall

Type: quadoption
Default: ask-yes

Controls whether or not Mutt recalls postponed messages when composing a new message. @@ -2240,29 +2058,29 @@ when composing a new message. Setting this variable to is not generally useful, and thus not recommended.

-Also see $postponed variable. -

3.240. record

Type: path
+Also see $postponed variable. +

3.211. record

Type: path
Default: “˜/sent”

This specifies the file into which your outgoing messages should be appended. (This is meant as the primary method for saving a copy of -your messages, but another way to do this is using the “my_hdr” +your messages, but another way to do this is using the “my_hdr” command to create a “Bcc:” field with your email address in it.)

-The value of $record is overridden by the $force_name and -$save_name variables, and the “fcc-hook” command. -

3.241. reply_regexp

Type: regular expression
+The value of $record is overridden by the $force_name and +$save_name variables, and the “fcc-hook” command. +

3.212. reply_regexp

Type: regular expression
Default: “^(re([\[0-9\]+])*|aw):[ \t]*”

A regular expression used to recognize reply messages when threading and replying. The default value corresponds to the English "Re:" and the German "Aw:". -

3.242. reply_self

Type: boolean
+

3.213. reply_self

Type: boolean
Default: no

If unset and you are replying to a message sent by you, Mutt will assume that you want to reply to the recipients of that message rather than to yourself.

-Also see the “alternates” command. -

3.243. reply_to

Type: quadoption
+Also see the “alternates” command. +

3.214. reply_to

Type: quadoption
Default: ask-yes

If set, when replying to a message, Mutt will use the address listed in the Reply-to: header as the recipient of the reply. If unset, @@ -2270,12 +2088,12 @@ it will use the address in the From: header field instead. This option is useful for reading a mailing list that sets the Reply-To: header field to the list address and you want to send a private message to the author of a message. -

3.244. resolve

Type: boolean
+

3.215. resolve

Type: boolean
Default: yes

When set, the cursor will be automatically advanced to the next (possibly undeleted) message whenever a command that modifies the current message is executed. -

3.245. reverse_alias

Type: boolean
+

3.216. reverse_alias

Type: boolean
Default: no

This variable controls whether or not Mutt will display the “personal” name from your aliases in the index menu if it finds an alias that @@ -2284,36 +2102,34 @@ alias: 

 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. -

3.246. reverse_name

Type: boolean
+

3.217. reverse_name

Type: boolean
Default: no

It may sometimes arrive that you receive mail to a certain machine, move the messages to another machine, and reply to some the messages from there. If this variable is set, the default From: line of the reply messages is built using the address where you received the messages you are replying to if that address matches your -“alternates”. If the variable is unset, or the address that would be -used doesn't match your “alternates”, the From: line will use +“alternates”. If the variable is unset, or the address that would be +used doesn't match your “alternates”, the From: line will use your address on the current machine.

-Also see the “alternates” command. -

3.247. reverse_realname

Type: boolean
+Also see the “alternates” command. +

3.218. reverse_realname

Type: boolean
Default: yes

-This variable fine-tunes the behaviour of the $reverse_name feature. +This variable fine-tunes the behaviour of the $reverse_name feature. When it is set, mutt will use the address from incoming messages as-is, possibly including eventual real names. When it is unset, mutt will -override any such real names with the setting of the $realname variable. -

3.248. rfc2047_parameters

Type: boolean
+override any such real names with the setting of the $realname variable. +

3.219. rfc2047_parameters

Type: boolean
Default: no

When this variable is set, Mutt will decode RFC2047-encoded MIME parameters. You want to set this variable when mutt suggests you @@ -2321,7 +2137,6 @@ to save attachments to files named like: 

 =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
-

When this variable is set interactively, the change won't be active until you change folders. @@ -2333,56 +2148,60 @@ wild. Also note that setting this parameter will not have the effect that mutt generates this kind of encoding. Instead, mutt will unconditionally use the encoding specified in RFC2231. -

3.249. save_address

Type: boolean
+

3.220. save_address

Type: boolean
Default: no

If set, mutt will take the sender's full address when choosing a -default folder for saving a mail. If $save_name or $force_name +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. -

3.250. save_empty

Type: boolean
+

3.221. save_empty

Type: boolean
Default: yes

When unset, mailboxes which contain no saved messages will be removed -when closed (the exception is $spoolfile which is never removed). +when closed (the exception is $spoolfile which is never removed). If set, mailboxes are never removed.

Note: This only applies to mbox and MMDF folders, Mutt does not delete MH and Maildir directories. -

3.251. save_history

Type: number
+

3.222. save_history

Type: number
Default: 0

This variable controls the size of the history (per category) saved in the -$history_file file. -

3.252. save_name

Type: boolean
+$history_file file. +

3.223. save_name

Type: boolean
Default: no

This variable controls how copies of outgoing messages are saved. When set, a check is made to see if a mailbox specified by the recipient address exists (this is done by searching for a mailbox in -the $folder directory with the username part of the +the $folder directory with the username part of the recipient address). If the mailbox exists, the outgoing message will be saved to that mailbox, otherwise the message is saved to the -$record mailbox. +$record mailbox.

-Also see the $force_name variable. -

3.253. score

Type: boolean
+Also see the $force_name variable. +

3.224. score

Type: boolean
Default: yes

When this variable is unset, scoring is turned off. This can be useful to selectively disable scoring for certain folders when the -$score_threshold_delete variable and related are used. -

3.254. score_threshold_delete

Type: number
+$score_threshold_delete variable and related are used. +

3.225. score_threshold_delete

Type: number
Default: -1

Messages which have been assigned a score equal to or lower than the value of this variable are automatically marked for deletion by mutt. Since mutt scores are always greater than or equal to zero, the default setting of this variable will never mark a message for deletion. -

3.255. score_threshold_flag

Type: number
+

3.226. score_threshold_flag

Type: number
Default: 9999

Messages which have been assigned a score greater than or equal to this variable's value are automatically marked "flagged". -

3.256. score_threshold_read

Type: number
+

3.227. score_threshold_read

Type: number
Default: -1

Messages which have been assigned a score equal to or lower than the value of this variable are automatically marked as read by mutt. Since mutt scores are always greater than or equal to zero, the default setting of this variable will never mark a message read. -

3.257. send_charset

Type: string
+

3.228. search_context

Type: number
+Default: 0

+For the pager, this variable specifies the number of lines shown +before search results. By default, search results will be top-aligned. +

3.229. send_charset

Type: string
Default: “us-ascii:iso-8859-1:utf-8”

A colon-delimited list of character sets for outgoing messages. Mutt will use the first character set into which the text can be converted exactly. @@ -2394,50 +2213,50 @@ appropriate widely used standard character set (such as

In case the text cannot be converted into one of these exactly, mutt uses $charset as a fallback. -

3.258. sendmail

Type: path
+

3.230. sendmail

Type: path
Default: “/usr/sbin/sendmail -oem -oi”

Specifies the program and arguments used to deliver mail sent by Mutt. Mutt expects that the specified program interprets additional arguments as recipient addresses. -

3.259. sendmail_wait

Type: number
+

3.231. sendmail_wait

Type: number
Default: 0

-Specifies the number of seconds to wait for the $sendmail process +Specifies the number of seconds to wait for the $sendmail process to finish before giving up and putting delivery in the background.

Mutt interprets the value of this variable as follows: -

>0

number of seconds to wait for sendmail to finish before continuing -

0

wait forever for sendmail to finish -

<0

always put sendmail in the background without waiting -

+

>0 number of seconds to wait for sendmail to finish before continuing +
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. -

3.260. shell

Type: path
+

3.232. shell

Type: path
Default: (empty)

Command to use when spawning a subshell. By default, the user's login shell from /etc/passwd is used. -

3.261. sig_dashes

Type: boolean
+

3.233. sig_dashes

Type: boolean
Default: yes

If set, a line containing “-- ” (note the trailing space) will be inserted before your -$signature. It is strongly recommended that you not unset +$signature. It is strongly recommended that you not unset this variable unless your signature contains just your name. The reason for this is because many software packages use “-- \n” to detect your signature. For example, Mutt has the ability to highlight the signature in a different color in the builtin pager. -

3.262. sig_on_top

Type: boolean
+

3.234. sig_on_top

Type: boolean
Default: no

If set, the signature will be included before any quoted or forwarded text. It is strongly recommended that you do not set this variable unless you really know what you are doing, and are prepared to take some heat from netiquette guardians. -

3.263. signature

Type: path
+

3.235. signature

Type: path
Default: “˜/.signature”

Specifies the filename of your signature, which is appended to all 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 standard output. -

3.264. simple_search

Type: string
+

3.236. simple_search

Type: string
Default: “˜f %s | ˜s %s”

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 “˜” pattern @@ -2447,25 +2266,186 @@ For example, if you simply type “joe” at a search will automatically expand it to the value specified by this variable by replacing “%s” with the supplied string. For the default value, “joe” would be expanded to: “˜f joe | ˜s joe”. -

3.265. smart_wrap

Type: boolean
+

3.237. sleep_time

Type: number
+Default: 1

+Specifies time, in seconds, to pause while displaying certain informational +messages, while moving from folder to folder and after expunging +messages from the current folder. The default is to pause one second, so +a value of zero for this option suppresses the pause. +

3.238. smart_wrap

Type: boolean
Default: yes

Controls the display of lines longer than the screen width in the internal pager. If set, long lines are wrapped at a word boundary. If unset, lines are simply wrapped at the screen edge. Also see the -$markers variable. -

3.266. smileys

Type: regular expression
+$markers variable. +

3.239. smileys

Type: regular expression
Default: “(>From )|(:[-^]?[][)(><}{|/DP])”

The pager uses this variable to catch some common false -positives of $quote_regexp, most notably smileys and not consider -a line quoted text if it also matches $smileys. This mostly +positives of $quote_regexp, most notably smileys and not consider +a line quoted text if it also matches $smileys. This mostly happens at the beginning of a line. -

3.267. sleep_time

Type: number
-Default: 1

-Specifies time, in seconds, to pause while displaying certain informational -messages, while moving from folder to folder and after expunging -messages from the current folder. The default is to pause one second, so -a value of zero for this option suppresses the pause. -

3.268. smtp_authenticators

Type: string
+

3.240. smime_ask_cert_label

Type: boolean
+Default: yes

+This flag controls whether you want to be asked to enter a label +for a certificate about to be added to the database or not. It is +set by default. +(S/MIME only) +

3.241. smime_ca_location

Type: path
+Default: (empty)

+This variable contains the name of either a directory, or a file which +contains trusted certificates for use with OpenSSL. +(S/MIME only) +

3.242. smime_certificates

Type: path
+Default: (empty)

+Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle +storage and retrieval of keys by itself. This is very basic right +now, and keys and certificates are stored in two different +directories, both named as the hash-value retrieved from +OpenSSL. There is an index file which contains mailbox-address +keyid pairs, and which can be manually edited. This option points to +the location of the certificates. +(S/MIME only) +

3.243. smime_decrypt_command

Type: string
+Default: (empty)

+This format string specifies a command which is used to decrypt +application/x-pkcs7-mime attachments. +

+The OpenSSL command formats have their own set of printf(3)-like sequences +similar to PGP's: + +

%f Expands to the name of a file containing a message. +
%s Expands to the name of a file containing the signature part + of a multipart/signed attachment when verifying it. +
%k The key-pair specified with $smime_default_key +
%c One or more certificate IDs. +
%a The algorithm used for encryption. +
%C CA location: Depending on whether $smime_ca_location + points to a directory or file, this expands to + “-CApath $smime_ca_location” or “-CAfile $smime_ca_location”. +

+For examples on how to configure these formats, see the smime.rc in +the samples/ subdirectory which has been installed on your system +alongside the documentation. +(S/MIME only) +

3.244. smime_decrypt_use_default_key

Type: boolean
+Default: yes

+If set (default) this tells mutt to use the default key for decryption. Otherwise, +if managing multiple certificate-key-pairs, mutt will try to use the mailbox-address +to determine the key to use. It will ask you to supply a key, if it can't find one. +(S/MIME only) +

3.245. smime_default_key

Type: string
+Default: (empty)

+This is the default key-pair to use for signing. This must be set to the +keyid (the hash-value that OpenSSL generates) to work properly +(S/MIME only) +

3.246. smime_encrypt_command

Type: string
+Default: (empty)

+This command is used to create encrypted S/MIME messages. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.247. smime_encrypt_with

Type: string
+Default: (empty)

+This sets the algorithm that should be used for encryption. +Valid choices are “des”, “des3”, “rc2-40”, “rc2-64”, “rc2-128”. +If unset, “3des” (TripleDES) is used. +(S/MIME only) +

3.248. smime_get_cert_command

Type: string
+Default: (empty)

+This command is used to extract X509 certificates from a PKCS7 structure. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.249. smime_get_cert_email_command

Type: string
+Default: (empty)

+This command is used to extract the mail address(es) used for storing +X509 certificates, and for verification purposes (to check whether the +certificate was issued for the sender's mailbox). +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.250. smime_get_signer_cert_command

Type: string
+Default: (empty)

+This command is used to extract only the signers X509 certificate from a S/MIME +signature, so that the certificate's owner may get compared to the +email's “From:” field. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.251. smime_import_cert_command

Type: string
+Default: (empty)

+This command is used to import a certificate via smime_keys. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.252. smime_is_default

Type: boolean
+Default: no

+The default behaviour of mutt is to use PGP on all auto-sign/encryption +operations. To override and to use OpenSSL instead this must be set. +However, this has no effect while replying, since mutt will automatically +select the same application that was used to sign/encrypt the original +message. (Note that this variable can be overridden by unsetting $crypt_autosmime.) +(S/MIME only) +

3.253. smime_keys

Type: path
+Default: (empty)

+Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle +storage and retrieval of keys/certs by itself. This is very basic right now, +and stores keys and certificates in two different directories, both +named as the hash-value retrieved from OpenSSL. There is an index file +which contains mailbox-address keyid pair, and which can be manually +edited. This option points to the location of the private keys. +(S/MIME only) +

3.254. smime_pk7out_command

Type: string
+Default: (empty)

+This command is used to extract PKCS7 structures of S/MIME signatures, +in order to extract the public X509 certificate(s). +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.255. smime_sign_command

Type: string
+Default: (empty)

+This command is used to created S/MIME signatures of type +multipart/signed, which can be read by all mail clients. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.256. smime_sign_opaque_command

Type: string
+Default: (empty)

+This command is used to created S/MIME signatures of type +application/x-pkcs7-signature, which can only be handled by mail +clients supporting the S/MIME extension. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.257. smime_timeout

Type: number
+Default: 300

+The number of seconds after which a cached passphrase will expire if +not used. +(S/MIME only) +

3.258. smime_verify_command

Type: string
+Default: (empty)

+This command is used to verify S/MIME signatures of type multipart/signed. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.259. smime_verify_opaque_command

Type: string
+Default: (empty)

+This command is used to verify S/MIME signatures of type +application/x-pkcs7-mime. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.260. smtp_authenticators

Type: string
Default: (empty)

This is a colon-delimited list of authentication methods mutt may attempt to use to log in to an SMTP server, in the order mutt should @@ -2479,29 +2459,27 @@ Example: 

 set smtp_authenticators="digest-md5:cram-md5"
-
-

3.269. smtp_pass

Type: string
+

3.261. smtp_pass

Type: string
Default: (empty)

Specifies the password for your SMTP account. If unset, Mutt will prompt you for your password when you first send mail via SMTP. -See $smtp_url to configure mutt to send mail via SMTP. +See $smtp_url to configure mutt to send mail via SMTP.

Warning: you should only use this option when you are on a fairly secure machine, because the superuser can read your muttrc even if you are the only one who can read the file. -

3.270. smtp_url

Type: string
+

3.262. smtp_url

Type: string
Default: (empty)

Defines the SMTP smarthost where sent messages should relayed for delivery. This should take the form of an SMTP URL, eg: 

 smtp[s]://[user[:pass]@]host[:port]/
-

-... where “[...]” denotes an optional part. -Setting this variable overrides the value of the $sendmail +where “[...]” denotes an optional part. +Setting this variable overrides the value of the $sendmail variable. -

3.271. sort

Type: sort order
+

3.263. sort

Type: sort order
Default: date

Specifies how to sort messages in the “index” menu. Valid values are: @@ -2519,7 +2497,7 @@ are:

You may optionally use the “reverse-” prefix to specify reverse sorting order (example: “set sort=reverse-date-sent”). -

3.272. sort_alias

Type: sort order
+

3.264. sort_alias

Type: sort order
Default: alias

Specifies how the entries in the “alias” menu are sorted. The following are legal values: @@ -2527,29 +2505,28 @@ following are legal values:

  • address (sort alphabetically by email address)

  • alias (sort alphabetically by alias name)

  • unsorted (leave in order specified in .muttrc) -

3.273. sort_aux

Type: sort order
+

3.265. sort_aux

Type: sort order
Default: date

When sorting by threads, this variable controls how threads are sorted in relation to other threads, and how the branches of the thread trees -are sorted. This can be set to any value that $sort can, except +are sorted. This can be set to any value that $sort can, except “threads” (in that case, mutt will just use “date-sent”). You can also specify the “last-” prefix in addition to the “reverse-” prefix, but “last-” must come after “reverse-”. The “last-” prefix causes messages to be sorted against its siblings by which has the last descendant, using -the rest of $sort_aux as an ordering. For instance, +the rest of $sort_aux as an ordering. For instance, 

 set sort_aux=last-date-received
-

would mean that if a new message is received in a thread, that thread becomes the last one displayed (or the first, if you have “set sort=reverse-threads”.)

-Note: For reversed $sort -order $sort_aux is reversed again (which is not the right thing to do, +Note: For reversed $sort +order $sort_aux is reversed again (which is not the right thing to do, but kept to not break any existing configuration setting). -

3.274. sort_browser

Type: sort order
+

3.266. sort_browser

Type: sort order
Default: alpha

Specifies how to sort entries in the file browser. By default, the entries are sorted alphabetically. Valid values: @@ -2561,33 +2538,93 @@ entries are sorted alphabetically. Valid values:

You may optionally use the “reverse-” prefix to specify reverse sorting order (example: “set sort_browser=reverse-date”). -

3.275. sort_re

Type: boolean
+

3.267. sort_re

Type: boolean
Default: yes

This variable is only useful when sorting by threads with -$strict_threads unset. In that case, it changes the heuristic -mutt uses to thread messages by subject. With $sort_re set, mutt will +$strict_threads unset. In that case, it changes the heuristic +mutt uses to thread messages by subject. With $sort_re set, mutt will only attach a message as the child of another message by subject if the subject of the child message starts with a substring matching the -setting of $reply_regexp. With $sort_re unset, mutt will attach +setting of $reply_regexp. With $sort_re unset, mutt will attach the message whether or not this is the case, as long as the -non-$reply_regexp parts of both messages are identical. -

3.276. spam_separator

Type: string
+non-$reply_regexp parts of both messages are identical. +

3.268. spam_separator

Type: string
Default: “,”

This variable controls what happens when multiple spam headers are matched: if unset, each successive header will overwrite any previous matches value for the spam label. If set, each successive match will append to the previous, using this variable's value as a separator. -

3.277. spoolfile

Type: path
+

3.269. spoolfile

Type: path
Default: (empty)

If your spool mailbox is in a non-default place where Mutt cannot find it, you can specify its location with this variable. Mutt will -automatically set this variable to the value of the environment -variable $MAIL if it is not set. -

3.278. status_chars

Type: string
+initially set this variable to the value of the environment +variable $MAIL or $MAILDIR if either is defined. +

3.270. ssl_ca_certificates_file

Type: path
+Default: (empty)

+This variable specifies a file containing trusted CA certificates. +Any server certificate that is signed with one of these CA +certificates is also automatically accepted. +

+Example: + +

+set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
+

3.271. ssl_client_cert

Type: path
+Default: (empty)

+The file containing a client certificate and its associated private +key. +

3.272. ssl_force_tls

Type: boolean
+Default: no

+If this variable is set, Mutt will require that all connections +to remote servers be encrypted. Furthermore it will attempt to +negotiate TLS even if the server does not advertise the capability, +since it would otherwise have to abort the connection anyway. This +option supersedes $ssl_starttls. +

3.273. ssl_min_dh_prime_bits

Type: number
+Default: 0

+This variable specifies the minimum acceptable prime size (in bits) +for use in any Diffie-Hellman key exchange. A value of 0 will use +the default from the GNUTLS library. +

3.274. ssl_starttls

Type: quadoption
+Default: yes

+If set (the default), mutt will attempt to use STARTTLS on servers +advertising the capability. When unset, mutt will not attempt to +use STARTTLS regardless of the server's capabilities. +

3.275. ssl_use_sslv2

Type: boolean
+Default: no

+This variable specifies whether to attempt to use SSLv2 in the +SSL authentication process. +

3.276. ssl_use_sslv3

Type: boolean
+Default: yes

+This variable specifies whether to attempt to use SSLv3 in the +SSL authentication process. +

3.277. ssl_use_tlsv1

Type: boolean
+Default: yes

+This variable specifies whether to attempt to use TLSv1 in the +SSL authentication process. +

3.278. ssl_usesystemcerts

Type: boolean
+Default: yes

+If set to yes, mutt will use CA certificates in the +system-wide certificate store when checking if a server certificate +is signed by a trusted CA. +

3.279. ssl_verify_dates

Type: boolean
+Default: yes

+If set (the default), mutt will not automatically accept a server +certificate that is either not yet valid or already expired. You should +only unset this for particular known hosts, using the +<account-hook> function. +

3.280. ssl_verify_host

Type: boolean
+Default: yes

+If set (the default), mutt will not automatically accept a server +certificate whose host name does not match the host used in your folder +URL. You should only unset this for particular known hosts, using +the <account-hook> function. +

3.281. status_chars

Type: string
Default: “-*%A”

Controls the characters used by the “%r” indicator in -$status_format. The first character is used when the mailbox is +$status_format. The first character is used when the mailbox is unchanged. The second is used when the mailbox has been changed, and it needs to be resynchronized. The third is used if the mailbox is in read-only mode, or if the mailbox will not be written when exiting @@ -2596,39 +2633,39 @@ with the <toggle-write> operation, bound by d is used to indicate that the current folder has been opened in attach- message mode (Certain operations like composing a new mail, replying, forwarding, etc. are not permitted in this mode). -

3.279. status_format

Type: string
+

3.282. status_format

Type: string
Default: “-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---”

Controls the format of the status line displayed in the “index” -menu. This string is similar to $index_format, but has its own +menu. This string is similar to $index_format, but has its own set of printf(3)-like sequences: -

%b

number of mailboxes with new mail * -

%d

number of deleted messages * -

%f

the full pathname of the current mailbox -

%F

number of flagged messages * -

%h

local hostname -

%l

size (in bytes) of the current mailbox * -

%L

size (in bytes) of the messages shown +

%b number of mailboxes with new mail * +
%d number of deleted messages * +
%f the full pathname of the current mailbox +
%F number of flagged messages * +
%h local hostname +
%l size (in bytes) of the current mailbox * +
%L size (in bytes) of the messages shown (i.e., which match the current limit) * -

%m

the number of messages in the mailbox * -

%M

the number of messages shown (i.e., which match the current limit) * -

%n

number of new messages in the mailbox * -

%o

number of old unread messages * -

%p

number of postponed messages * -

%P

percentage of the way through the index -

%r

modified/read-only/won't-write/attach-message indicator, -according to $status_chars -

%s

current sorting mode ($sort) -

%S

current aux sorting method ($sort_aux) -

%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” -

%*X

soft-fill with character “X” as pad -

-For an explanation of “soft-fill”, see the $index_format documentation. +

%m the number of messages in the mailbox * +
%M the number of messages shown (i.e., which match the current limit) * +
%n number of new messages in the mailbox * +
%o number of old unread messages * +
%p number of postponed messages * +
%P percentage of the way through the index +
%r modified/read-only/won't-write/attach-message indicator, +according to $status_chars +
%s current sorting mode ($sort) +
%S current aux sorting method ($sort_aux) +
%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” +
%*X soft-fill with character “X” as pad +

+For an explanation of “soft-fill”, see the $index_format documentation.

* = can be optionally printed if nonzero

@@ -2666,27 +2703,27 @@ you would use: “%_h” If you prefix the sequence character with a colon (“:”) character, mutt will replace any dots in the expansion by underscores. This might be helpful with IMAP folders that don't like dots in folder names. -

3.280. status_on_top

Type: boolean
+

3.283. status_on_top

Type: boolean
Default: no

Setting this variable causes the “status bar” to be displayed on -the first line of the screen rather than near the bottom. If $help +the first line of the screen rather than near the bottom. If $help is set, too it'll be placed at the bottom. -

3.281. strict_threads

Type: boolean
+

3.284. strict_threads

Type: boolean
Default: no

If set, threading will only make use of the “In-Reply-To” and -“References:” fields when you $sort by message threads. By +“References:” fields when you $sort by message threads. By default, messages with the same subject are grouped together in “pseudo threads.”. This may not always be desirable, such as in a personal mailbox where you might have several unrelated messages with the subjects like “hi” which will get grouped together. See also -$sort_re for a less drastic way of controlling this +$sort_re for a less drastic way of controlling this behaviour. -

3.282. suspend

Type: boolean
+

3.285. suspend

Type: boolean
Default: yes

When unset, mutt won't stop when the user presses the terminal's susp key, usually “^Z”. This is useful if you run mutt inside an xterm using a command like “xterm -e mutt”. -

3.283. text_flowed

Type: boolean
+

3.286. text_flowed

Type: boolean
Default: no

When set, mutt will generate “format=flowed” bodies with a content type of “text/plain; format=flowed”. @@ -2694,12 +2731,8 @@ This format is easier to handle for some mailing software, and generally just looks like ordinary text. To actually make use of this format's features, you'll need support in your editor.

-Note that $indent_string is ignored when this option is set. -

3.284. thread_received

Type: boolean
-Default: no

-When set, mutt uses the date received rather than the date sent -to thread messages by subject. -

3.285. thorough_search

Type: boolean
+Note that $indent_string is ignored when this option is set. +

3.287. thorough_search

Type: boolean
Default: no

Affects the ˜b and ˜h search operations described in section “patterns”. If set, the headers and body/attachments of @@ -2711,20 +2744,24 @@ this value because decoding also includes MIME parsing/decoding and possible character set conversions. Otherwise mutt will attempt to match against the raw message received (for example quoted-printable encoded or with encoded headers) which may lead to incorrect search results. -

3.286. tilde

Type: boolean
+

3.288. thread_received

Type: boolean
+Default: no

+When set, mutt uses the date received rather than the date sent +to thread messages by subject. +

3.289. tilde

Type: boolean
Default: no

When set, the internal-pager will pad blank lines to the bottom of the screen with a tilde (“˜”). -

3.287. time_inc

Type: number
+

3.290. time_inc

Type: number
Default: 0

-Along with $read_inc, $write_inc, and $net_inc, this +Along with $read_inc, $write_inc, and $net_inc, this variable controls the frequency with which progress updates are -displayed. It suppresses updates less than $time_inc milliseconds +displayed. It suppresses updates less than $time_inc milliseconds apart. This can improve throughput on systems with slow terminals, or when running mutt on a remote system.

-Also see the “tuning” section of the manual for performance considerations. -

3.288. timeout

Type: number
+Also see the “tuning” section of the manual for performance considerations. +

3.291. timeout

Type: number
Default: 600

When Mutt is waiting for user input either idleing in menus or in an interactive prompt, Mutt would block until input is @@ -2737,13 +2774,13 @@ until it aborts waiting for input, performs these operations and continues to wait for input.

A value of zero or less will cause Mutt to never time out. -

3.289. tmpdir

Type: path
+

3.292. tmpdir

Type: path
Default: (empty)

This variable allows you to specify where Mutt will place its temporary files needed for displaying and composing messages. If this variable is not set, the environment variable $TMPDIR is used. If $TMPDIR is not set then “/tmp” is used. -

3.290. to_chars

Type: string
+

3.293. to_chars

Type: string
Default: “ +TCFL”

Controls the character used to indicate mail addressed to you. The first character is the one used when the mail is not addressed to your @@ -2755,7 +2792,7 @@ address is specified in the “Cc:” header field, b recipient. The fifth character is used to indicate mail that was sent by you. The sixth character is used to indicate when a mail was sent to a mailing-list you subscribe to. -

3.291. tunnel

Type: string
+

3.294. tunnel

Type: string
Default: (empty)

Setting this variable will cause mutt to open a pipe to a command instead of a raw socket. You may be able to use this to set up @@ -2763,60 +2800,67 @@ preauthenticated connections to your IMAP/POP3/SMTP server. Example: 

 set tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
-

Note: For this example to work you must be able to log in to the remote machine without having to enter a password. -

3.292. use_8bitmime

Type: boolean
+

+When set, Mutt uses the tunnel for all remote connections. +Please see “account-hook” in the manual for how to use different +tunnel commands per connection. +

3.295. uncollapse_jump

Type: boolean
+Default: no

+When set, Mutt will jump to the next unread message, if any, +when the current thread is uncollapsed. +

3.296. use_8bitmime

Type: boolean
Default: no

Warning: do not set this variable unless you are using a version of sendmail which supports the -B8BITMIME flag (such as sendmail 8.8.x) or you may not be able to send mail.

-When set, Mutt will invoke $sendmail with the -B8BITMIME +When set, Mutt will invoke $sendmail with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP negotiation. -

3.293. use_domain

Type: boolean
+

3.297. use_domain

Type: boolean
Default: yes

When set, Mutt will qualify all local addresses (ones without the -“@host” portion) with the value of $hostname. If unset, no +“@host” portion) with the value of $hostname. If unset, no addresses will be qualified. -

3.294. use_envelope_from

Type: boolean
+

3.298. use_envelope_from

Type: boolean
Default: no

When set, mutt will set the envelope sender of the message. -If $envelope_from_address is set, it will be used as the sender +If $envelope_from_address is set, it will be used as the sender address. If unset, mutt will attempt to derive the sender from the “From:” header.

Note that this information is passed to sendmail command using the -f command line switch. Therefore setting this option is not useful -if the $sendmail variable already contains -f or if the -executable pointed to by $sendmail doesn't support the -f switch. -

3.295. use_from

Type: boolean
+if the $sendmail variable already contains -f or if the +executable pointed to by $sendmail doesn't support the -f switch. +

3.299. use_from

Type: boolean
Default: yes

When set, Mutt will generate the “From:” header field when sending messages. If unset, no “From:” header field will be -generated unless the user explicitly sets one using the “my_hdr” +generated unless the user explicitly sets one using the “my_hdr” command. -

3.296. use_idn

Type: boolean
+

3.300. use_idn

Type: boolean
Default: yes

When set, Mutt will show you international domain names decoded. Note: You can use IDNs for addresses even if this is unset. This variable only affects decoding. -

3.297. use_ipv6

Type: boolean
+

3.301. use_ipv6

Type: boolean
Default: yes

When set, Mutt will look for IPv6 addresses of hosts it tries to contact. If this option is unset, Mutt will restrict itself to IPv4 addresses. Normally, the default should work. -

3.298. user_agent

Type: boolean
+

3.302. user_agent

Type: boolean
Default: yes

When set, mutt will add a “User-Agent:” header to outgoing messages, indicating which version of mutt was used for composing them. -

3.299. visual

Type: path
+

3.303. visual

Type: path
Default: (empty)

Specifies the visual editor to invoke when the “˜v” command is given in the builtin editor. -

3.300. wait_key

Type: boolean
+

3.304. wait_key

Type: boolean
Default: yes

Controls whether Mutt will ask you to press a key after an external command has been invoked by these functions: <shell-escape>, @@ -2829,48 +2873,48 @@ and the external program is interactive.

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. -

3.301. weed

Type: boolean
+

3.305. weed

Type: boolean
Default: yes

When set, mutt will weed headers when displaying, forwarding, printing, or replying to messages. -

3.302. wrap

Type: number
+

3.306. wrap

Type: number
Default: 0

-When set to a positive value, mutt will wrap text at $wrap characters. -When set to a negative value, mutt will wrap text so that there are $wrap +When set to a positive value, mutt will wrap text at $wrap characters. +When set to a negative value, mutt will wrap text so that there are $wrap characters of empty space on the right side of the terminal. -

3.303. wrap_search

Type: boolean
+

3.307. wrap_search

Type: boolean
Default: yes

Controls whether searches wrap around the end.

When set, searches will wrap around the first (or last) item. When unset, incremental searches will not wrap. -

3.304. wrapmargin

Type: number
+

3.308. wrapmargin

Type: number
Default: 0

-(DEPRECATED) Equivalent to setting $wrap with a negative value. -

3.305. write_inc

Type: number
-Default: 10

-When writing a mailbox, a message will be printed every -$write_inc messages to indicate progress. If set to 0, only a -single message will be displayed before writing a mailbox. -

-Also see the $read_inc, $net_inc and $time_inc variables and the -“tuning” section of the manual for performance considerations. -

3.306. write_bcc

Type: boolean
+(DEPRECATED) Equivalent to setting $wrap with a negative value. +

3.309. write_bcc

Type: boolean
Default: yes

Controls whether mutt writes out the “Bcc:” header when preparing messages to be sent. Exim users may wish to unset this. If mutt -is set to deliver directly via SMTP (see $smtp_url), this +is set to deliver directly via SMTP (see $smtp_url), this option does nothing: mutt will never write out the “Bcc:” header in this case. +

3.310. write_inc

Type: number
+Default: 10

+When writing a mailbox, a message will be printed every +$write_inc messages to indicate progress. If set to 0, only a +single message will be displayed before writing a mailbox. +

+Also see the $read_inc, $net_inc and $time_inc variables and the +“tuning” section of the manual for performance considerations.

4. Functions

The following is the list of available functions listed by the mapping in which they are available. The default key setting is given, and an explanation of what the function does. The key bindings of these -functions can be changed with the bind +functions can be changed with the bind command. -

4.1. generic menu

+

4.1. Generic Menu

The generic menu is not a real menu, but specifies common functions (such as movement) available in all menus except for pager and editor. Changing settings for this menu will affect the default bindings for all menus (except as noted). -

Table 8.2. Default generic function bindings

FunctionDefault keyDescription
<top-page>Hmove to the top of the page
<next-entry>jmove to the next entry
<previous-entry>kmove to the previous entry
<bottom-page>Lmove to the bottom of the page
<refresh>^Lclear and redraw the screen
<middle-page>Mmove to the middle of the page
<search-next>nsearch for next match
<exit>qexit this menu
<tag-entry>ttag the current entry
<next-page>zmove to the next page
<previous-page>Zmove to the previous page
<last-entry>*move to the last entry
<first-entry>=move to the first entry
<enter-command>:enter a muttrc command
<next-line>>scroll down one line
<previous-line><scroll up one line
<half-up>[scroll up 1/2 page
<half-down>]scroll down 1/2 page
<help>?this screen
<tag-prefix>;apply next function to tagged messages
<tag-prefix-cond> apply next function ONLY to tagged messages
<end-cond> end of conditional execution (noop)
<shell-escape>!invoke a command in a subshell
<select-entry><Return>select the current entry
<search>/search for a regular expression
<search-reverse>Esc /search backwards for a regular expression
<search-opposite> search for next match in opposite direction
<jump> jump to an index number
<current-top> move entry to top of screen
<current-middle> move entry to middle of screen
<current-bottom> move entry to bottom of screen
<what-key> display the keycode for a key press

4.2. index menu

Table 8.3. Default index function bindings

FunctionDefault keyDescription
<create-alias>acreate an alias from a message sender
<bounce-message>bremail a message to another user
<break-thread>#break the thread in two
<change-folder>copen a different folder
<change-folder-readonly>Esc copen a different folder in read only mode
<next-unread-mailbox> open next mailbox with new mail
<collapse-thread>Esc vcollapse/uncollapse current thread
<collapse-all>Esc Vcollapse/uncollapse all threads
<copy-message>Ccopy a message to a file/mailbox
<decode-copy>Esc Cmake decoded (text/plain) copy
<decode-save>Esc smake decoded copy (text/plain) and delete
<delete-message>ddelete the current entry
<delete-pattern>Ddelete messages matching a pattern
<delete-thread>^Ddelete all messages in thread
<delete-subthread>Esc ddelete all messages in subthread
<edit>eedit the raw message
<edit-type>^Eedit attachment content type
<forward-message>fforward a message with comments
<flag-message>Ftoggle a message's 'important' flag
<group-reply>greply to all recipients
<fetch-mail>Gretrieve mail from POP server
<imap-fetch-mail> force retrieval of mail from IMAP server
<display-toggle-weed>hdisplay message and toggle header weeding
<next-undeleted>jmove to the next undeleted message
<previous-undeleted>kmove to the previous undeleted message
<limit>lshow only messages matching a pattern
<link-threads>&link tagged message to the current one
<list-reply>Lreply to specified mailing list
<mail>mcompose a new mail message
<toggle-new>Ntoggle a message's 'new' flag
<toggle-write>%toggle whether the mailbox will be rewritten
<next-thread>^Njump to the next thread
<next-subthread>Esc njump to the next subthread
<query>Qquery external program for addresses
<quit>qsave changes to mailbox and quit
<reply>rreply to a message
<show-limit>Esc lshow currently active limit pattern
<sort-mailbox>osort messages
<sort-reverse>Osort messages in reverse order
<print-message>pprint the current entry
<previous-thread>^Pjump to previous thread
<previous-subthread>Esc pjump to previous subthread
<recall-message>Rrecall a postponed message
<read-thread>^Rmark the current thread as read
<read-subthread>Esc rmark the current subthread as read
<resend-message>Esc euse the current message as a template for a new one
<save-message>ssave message/attachment to a file
<tag-pattern>Ttag messages matching a pattern
<tag-subthread> tag the current subthread
<tag-thread>Esc ttag the current thread
<untag-pattern>^Tuntag messages matching a pattern
<undelete-message>uundelete the current entry
<undelete-pattern>Uundelete messages matching a pattern
<undelete-subthread>Esc uundelete all messages in subthread
<undelete-thread>^Uundelete all messages in thread
<view-attachments>vshow MIME attachments
<show-version>Vshow the Mutt version number and date
<set-flag>wset a status flag on a message
<clear-flag>Wclear a status flag from a message
<display-message><Return>display a message
<buffy-list>.list mailboxes with new mail
<sync-mailbox>$save changes to mailbox
<display-address>@display full address of sender
<pipe-message>|pipe message/attachment to a shell command
<next-new> jump to the next new message
<next-new-then-unread><Tab>jump to the next new or unread message
<previous-new> jump to the previous new message
<previous-new-then-unread>Esc <Tab>jump to the previous new or unread message
<next-unread> jump to the next unread message
<previous-unread> jump to the previous unread message
<parent-message>Pjump to parent message in thread
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory
<check-traditional-pgp>Esc Pcheck for classic PGP
<mail-key>Esc kmail a PGP public key
<decrypt-copy> make decrypted copy
<decrypt-save> make decrypted copy and delete

4.3. pager menu

Table 8.4. Default pager function bindings

FunctionDefault keyDescription
<break-thread>#break the thread in two
<create-alias>acreate an alias from a message sender
<bounce-message>bremail a message to another user
<change-folder>copen a different folder
<change-folder-readonly>Esc copen a different folder in read only mode
<next-unread-mailbox> open next mailbox with new mail
<copy-message>Ccopy a message to a file/mailbox
<decode-copy>Esc Cmake decoded (text/plain) copy
<delete-message>ddelete the current entry
<delete-thread>^Ddelete all messages in thread
<delete-subthread>Esc ddelete all messages in subthread
<edit>eedit the raw message
<edit-type>^Eedit attachment content type
<forward-message>fforward a message with comments
<flag-message>Ftoggle a message's 'important' flag
<group-reply>greply to all recipients
<imap-fetch-mail> force retrieval of mail from IMAP server
<display-toggle-weed>hdisplay message and toggle header weeding
<next-undeleted>jmove to the next undeleted message
<next-entry>Jmove to the next entry
<previous-undeleted>kmove to the previous undeleted message
<previous-entry>Kmove to the previous entry
<link-threads>&link tagged message to the current one
<list-reply>Lreply to specified mailing list
<redraw-screen>^Lclear and redraw the screen
<mail>mcompose a new mail message
<mark-as-new>Ntoggle a message's 'new' flag
<search-next>nsearch for next match
<next-thread>^Njump to the next thread
<next-subthread>Esc njump to the next subthread
<print-message>pprint the current entry
<previous-thread>^Pjump to previous thread
<previous-subthread>Esc pjump to previous subthread
<quit>Qsave changes to mailbox and quit
<exit>qexit this menu
<reply>rreply to a message
<recall-message>Rrecall a postponed message
<read-thread>^Rmark the current thread as read
<read-subthread>Esc rmark the current subthread as read
<resend-message>Esc euse the current message as a template for a new one
<save-message>ssave message/attachment to a file
<skip-quoted>Sskip beyond quoted text
<decode-save>Esc smake decoded copy (text/plain) and delete
<tag-message>ttag the current entry
<toggle-quoted>Ttoggle display of quoted text
<undelete-message>uundelete the current entry
<undelete-subthread>Esc uundelete all messages in subthread
<undelete-thread>^Uundelete all messages in thread
<view-attachments>vshow MIME attachments
<show-version>Vshow the Mutt version number and date
<search-toggle>\\toggle search pattern coloring
<display-address>@display full address of sender
<next-new> jump to the next new message
<pipe-message>|pipe message/attachment to a shell command
<help>?this screen
<next-page><Space>move to the next page
<previous-page>-move to the previous page
<top>^jump to the top of the message
<sync-mailbox>$save changes to mailbox
<shell-escape>!invoke a command in a subshell
<enter-command>:enter a muttrc command
<buffy-list>.list mailboxes with new mail
<search>/search for a regular expression
<search-reverse>Esc /search backwards for a regular expression
<search-opposite> search for next match in opposite direction
<next-line><Return>scroll down one line
<jump> jump to an index number
<next-unread> jump to the next unread message
<previous-new> jump to the previous new message
<previous-unread> jump to the previous unread message
<half-up> scroll up 1/2 page
<half-down> scroll down 1/2 page
<previous-line> scroll up one line
<bottom> jump to the bottom of the message
<parent-message>Pjump to parent message in thread
<check-traditional-pgp>Esc Pcheck for classic PGP
<mail-key>Esc kmail a PGP public key
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory
<decrypt-copy> make decrypted copy
<decrypt-save> make decrypted copy and delete
<what-key> display the keycode for a key press

4.4. alias menu

Table 8.5. Default alias function bindings

FunctionDefault keyDescription
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry

4.5. query menu

Table 8.6. Default query function bindings

FunctionDefault keyDescription
<create-alias>acreate an alias from a message sender
<mail>mcompose a new mail message
<query>Qquery external program for addresses
<query-append>Aappend new query results to current results

4.6. attach menu

Table 8.7. Default attach function bindings

FunctionDefault keyDescription
<bounce-message>bremail a message to another user
<display-toggle-weed>hdisplay message and toggle header weeding
<edit-type>^Eedit attachment content type
<print-entry>pprint the current entry
<save-entry>ssave message/attachment to a file
<pipe-entry>|pipe message/attachment to a shell command
<view-mailcap>mforce viewing of attachment using mailcap
<reply>rreply to a message
<resend-message>Esc euse the current message as a template for a new one
<group-reply>greply to all recipients
<list-reply>Lreply to specified mailing list
<forward-message>fforward a message with comments
<view-text>Tview attachment as text
<view-attach><Return>view attachment using mailcap entry if necessary
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry
<collapse-parts>vToggle display of subparts
<check-traditional-pgp>Esc Pcheck for classic PGP
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory

4.7. compose menu

Table 8.8. Default compose function bindings

FunctionDefault keyDescription
<attach-file>aattach file(s) to this message
<attach-message>Aattach message(s) to this message
<edit-bcc>bedit the BCC list
<edit-cc>cedit the CC list
<copy-file>Csave message/attachment to a file
<detach-file>Ddelete the current entry
<toggle-disposition>^Dtoggle disposition between inline/attachment
<edit-description>dedit attachment description
<edit-message>eedit the message
<edit-headers>Eedit the message with headers
<edit-file>^X eedit the file to be attached
<edit-encoding>^Eedit attachment transfer-encoding
<edit-from>Esc fedit the from field
<edit-fcc>fenter a file to save a copy of this message in
<filter-entry>Ffilter attachment through a shell command
<get-attachment>Gget a temporary copy of an attachment
<display-toggle-weed>hdisplay message and toggle header weeding
<ispell>irun ispell on the message
<print-entry>lprint the current entry
<edit-mime>medit attachment using mailcap entry
<new-mime>ncompose new attachment using mailcap entry
<postpone-message>Psave this message to send later
<edit-reply-to>redit the Reply-To field
<rename-file>Rrename/move an attached file
<edit-subject>sedit the subject of this message
<edit-to>tedit the TO list
<edit-type>^Tedit attachment content type
<write-fcc>wwrite the message to a folder
<toggle-unlink>utoggle whether to delete file after sending it
<toggle-recode> toggle recoding of this attachment
<update-encoding>Uupdate an attachment's encoding info
<view-attach><Return>view attachment using mailcap entry if necessary
<send-message>ysend the message
<pipe-entry>|pipe message/attachment to a shell command
<attach-key>Esc kattach a PGP public key
<pgp-menu>pshow PGP options
<forget-passphrase>^Fwipe passphrase(s) from memory
<smime-menu>Sshow S/MIME options
<mix>Msend the message through a mixmaster remailer chain

4.8. postpone menu

Table 8.9. Default postpone function bindings

FunctionDefault keyDescription
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry

4.9. browser menu

Table 8.10. Default browser function bindings

FunctionDefault keyDescription
<change-dir>cchange directories
<display-filename>@display the currently selected file's name
<enter-mask>menter a file mask
<sort>osort messages
<sort-reverse>Osort messages in reverse order
<select-new>Nselect a new file in this directory
<check-new> check mailboxes for new mail
<toggle-mailboxes><Tab>toggle whether to browse mailboxes or all files
<view-file><Space>view file
<buffy-list>.list mailboxes with new mail
<create-mailbox>Ccreate a new mailbox (IMAP only)
<delete-mailbox>ddelete the current mailbox (IMAP only)
<rename-mailbox>rrename the current mailbox (IMAP only)
<subscribe>ssubscribe to current mailbox (IMAP only)
<unsubscribe>uunsubscribe from current mailbox (IMAP only)
<toggle-subscribed>Ttoggle view all/subscribed mailboxes (IMAP only)

4.10. pgp menu

Table 8.11. Default pgp function bindings

FunctionDefault keyDescription
<verify-key>cverify a PGP public key
<view-name>%view the key's user id

4.11. smime menu

Table 8.12. Default smime function bindings

FunctionDefault keyDescription
<verify-key>cverify a PGP public key
<view-name>%view the key's user id

4.12. mix menu

Table 8.13. Default mix function bindings

FunctionDefault keyDescription
<accept><Return>Accept the chain constructed
<append>aAppend a remailer to the chain
<insert>iInsert a remailer into the chain
<delete>dDelete a remailer from the chain
<chain-prev><Left>Select the previous element of the chain
<chain-next><Right>Select the next element of the chain

4.13. editor menu

Table 8.14. Default editor function bindings

FunctionDefault keyDescription
<bol>^Ajump to the beginning of the line
<backward-char>^Bmove the cursor one character to the left
<backward-word>Esc bmove the cursor to the beginning of the word
<capitalize-word>Esc ccapitalize the word
<downcase-word>Esc lconvert the word to lower case
<upcase-word>Esc uconvert the word to upper case
<delete-char>^Ddelete the char under the cursor
<eol>^Ejump to the end of the line
<forward-char>^Fmove the cursor one character to the right
<forward-word>Esc fmove the cursor to the end of the word
<backspace><Backspace>delete the char in front of the cursor
<kill-eol>^Kdelete chars from cursor to end of line
<kill-eow>Esc ddelete chars from the cursor to the end of the word
<kill-line>^Udelete all chars on the line
<quote-char>^Vquote the next typed key
<kill-word>^Wdelete the word in front of the cursor
<complete><Tab>complete filename or alias
<complete-query>^Tcomplete address with query
<buffy-cycle><Space>cycle among incoming mailboxes
<history-up> scroll up through the history list
<history-down> scroll down through the history list
<transpose-chars> transpose character under cursor with previous

Prev   Next
Chapter 7. Performance tuning Home Chapter 9. Miscellany
+

Table 9.2. Default generic Function Bindings

FunctionDefault keyDescription
<top-page>Hmove to the top of the page
<next-entry>jmove to the next entry
<previous-entry>kmove to the previous entry
<bottom-page>Lmove to the bottom of the page
<refresh>^Lclear and redraw the screen
<middle-page>Mmove to the middle of the page
<search-next>nsearch for next match
<exit>qexit this menu
<tag-entry>ttag the current entry
<next-page>zmove to the next page
<previous-page>Zmove to the previous page
<last-entry>*move to the last entry
<first-entry>=move to the first entry
<enter-command>:enter a muttrc command
<next-line>>scroll down one line
<previous-line><scroll up one line
<half-up>[scroll up 1/2 page
<half-down>]scroll down 1/2 page
<help>?this screen
<tag-prefix>;apply next function to tagged messages
<tag-prefix-cond> apply next function ONLY to tagged messages
<end-cond> end of conditional execution (noop)
<shell-escape>!invoke a command in a subshell
<select-entry><Return>select the current entry
<search>/search for a regular expression
<search-reverse>Esc /search backwards for a regular expression
<search-opposite> search for next match in opposite direction
<jump> jump to an index number
<current-top> move entry to top of screen
<current-middle> move entry to middle of screen
<current-bottom> move entry to bottom of screen
<what-key> display the keycode for a key press

4.2. Index Menu

Table 9.3. Default index Function Bindings

FunctionDefault keyDescription
<create-alias>acreate an alias from a message sender
<bounce-message>bremail a message to another user
<break-thread>#break the thread in two
<change-folder>copen a different folder
<change-folder-readonly>Esc copen a different folder in read only mode
<next-unread-mailbox> open next mailbox with new mail
<collapse-thread>Esc vcollapse/uncollapse current thread
<collapse-all>Esc Vcollapse/uncollapse all threads
<copy-message>Ccopy a message to a file/mailbox
<decode-copy>Esc Cmake decoded (text/plain) copy
<decode-save>Esc smake decoded copy (text/plain) and delete
<delete-message>ddelete the current entry
<delete-pattern>Ddelete messages matching a pattern
<delete-thread>^Ddelete all messages in thread
<delete-subthread>Esc ddelete all messages in subthread
<edit>eedit the raw message
<edit-type>^Eedit attachment content type
<forward-message>fforward a message with comments
<flag-message>Ftoggle a message's 'important' flag
<group-reply>greply to all recipients
<fetch-mail>Gretrieve mail from POP server
<imap-fetch-mail> force retrieval of mail from IMAP server
<display-toggle-weed>hdisplay message and toggle header weeding
<next-undeleted>jmove to the next undeleted message
<previous-undeleted>kmove to the previous undeleted message
<limit>lshow only messages matching a pattern
<link-threads>&link tagged message to the current one
<list-reply>Lreply to specified mailing list
<mail>mcompose a new mail message
<toggle-new>Ntoggle a message's 'new' flag
<toggle-write>%toggle whether the mailbox will be rewritten
<next-thread>^Njump to the next thread
<next-subthread>Esc njump to the next subthread
<query>Qquery external program for addresses
<quit>qsave changes to mailbox and quit
<reply>rreply to a message
<show-limit>Esc lshow currently active limit pattern
<sort-mailbox>osort messages
<sort-reverse>Osort messages in reverse order
<print-message>pprint the current entry
<previous-thread>^Pjump to previous thread
<previous-subthread>Esc pjump to previous subthread
<recall-message>Rrecall a postponed message
<read-thread>^Rmark the current thread as read
<read-subthread>Esc rmark the current subthread as read
<resend-message>Esc euse the current message as a template for a new one
<save-message>ssave message/attachment to a mailbox/file
<tag-pattern>Ttag messages matching a pattern
<tag-subthread> tag the current subthread
<tag-thread>Esc ttag the current thread
<untag-pattern>^Tuntag messages matching a pattern
<undelete-message>uundelete the current entry
<undelete-pattern>Uundelete messages matching a pattern
<undelete-subthread>Esc uundelete all messages in subthread
<undelete-thread>^Uundelete all messages in thread
<view-attachments>vshow MIME attachments
<show-version>Vshow the Mutt version number and date
<set-flag>wset a status flag on a message
<clear-flag>Wclear a status flag from a message
<display-message><Return>display a message
<buffy-list>.list mailboxes with new mail
<sync-mailbox>$save changes to mailbox
<display-address>@display full address of sender
<pipe-message>|pipe message/attachment to a shell command
<next-new> jump to the next new message
<next-new-then-unread><Tab>jump to the next new or unread message
<previous-new> jump to the previous new message
<previous-new-then-unread>Esc <Tab>jump to the previous new or unread message
<next-unread> jump to the next unread message
<previous-unread> jump to the previous unread message
<parent-message>Pjump to parent message in thread
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory
<check-traditional-pgp>Esc Pcheck for classic PGP
<mail-key>Esc kmail a PGP public key
<decrypt-copy> make decrypted copy
<decrypt-save> make decrypted copy and delete

4.3. Pager Menu

Table 9.4. Default pager Function Bindings

FunctionDefault keyDescription
<break-thread>#break the thread in two
<create-alias>acreate an alias from a message sender
<bounce-message>bremail a message to another user
<change-folder>copen a different folder
<change-folder-readonly>Esc copen a different folder in read only mode
<next-unread-mailbox> open next mailbox with new mail
<copy-message>Ccopy a message to a file/mailbox
<decode-copy>Esc Cmake decoded (text/plain) copy
<delete-message>ddelete the current entry
<delete-thread>^Ddelete all messages in thread
<delete-subthread>Esc ddelete all messages in subthread
<set-flag>wset a status flag on a message
<clear-flag>Wclear a status flag from a message
<edit>eedit the raw message
<edit-type>^Eedit attachment content type
<forward-message>fforward a message with comments
<flag-message>Ftoggle a message's 'important' flag
<group-reply>greply to all recipients
<imap-fetch-mail> force retrieval of mail from IMAP server
<display-toggle-weed>hdisplay message and toggle header weeding
<next-undeleted>jmove to the next undeleted message
<next-entry>Jmove to the next entry
<previous-undeleted>kmove to the previous undeleted message
<previous-entry>Kmove to the previous entry
<link-threads>&link tagged message to the current one
<list-reply>Lreply to specified mailing list
<redraw-screen>^Lclear and redraw the screen
<mail>mcompose a new mail message
<mark-as-new>Ntoggle a message's 'new' flag
<search-next>nsearch for next match
<next-thread>^Njump to the next thread
<next-subthread>Esc njump to the next subthread
<print-message>pprint the current entry
<previous-thread>^Pjump to previous thread
<previous-subthread>Esc pjump to previous subthread
<quit>Qsave changes to mailbox and quit
<exit>qexit this menu
<reply>rreply to a message
<recall-message>Rrecall a postponed message
<read-thread>^Rmark the current thread as read
<read-subthread>Esc rmark the current subthread as read
<resend-message>Esc euse the current message as a template for a new one
<save-message>ssave message/attachment to a mailbox/file
<skip-quoted>Sskip beyond quoted text
<decode-save>Esc smake decoded copy (text/plain) and delete
<tag-message>ttag the current entry
<toggle-quoted>Ttoggle display of quoted text
<undelete-message>uundelete the current entry
<undelete-subthread>Esc uundelete all messages in subthread
<undelete-thread>^Uundelete all messages in thread
<view-attachments>vshow MIME attachments
<show-version>Vshow the Mutt version number and date
<search-toggle>\\toggle search pattern coloring
<display-address>@display full address of sender
<next-new> jump to the next new message
<pipe-message>|pipe message/attachment to a shell command
<help>?this screen
<next-page><Space>move to the next page
<previous-page>-move to the previous page
<top>^jump to the top of the message
<sync-mailbox>$save changes to mailbox
<shell-escape>!invoke a command in a subshell
<enter-command>:enter a muttrc command
<buffy-list>.list mailboxes with new mail
<search>/search for a regular expression
<search-reverse>Esc /search backwards for a regular expression
<search-opposite> search for next match in opposite direction
<next-line><Return>scroll down one line
<jump> jump to an index number
<next-unread> jump to the next unread message
<previous-new> jump to the previous new message
<previous-unread> jump to the previous unread message
<half-up> scroll up 1/2 page
<half-down> scroll down 1/2 page
<previous-line> scroll up one line
<bottom> jump to the bottom of the message
<parent-message>Pjump to parent message in thread
<check-traditional-pgp>Esc Pcheck for classic PGP
<mail-key>Esc kmail a PGP public key
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory
<decrypt-copy> make decrypted copy
<decrypt-save> make decrypted copy and delete
<what-key> display the keycode for a key press

4.4. Alias Menu

Table 9.5. Default alias Function Bindings

FunctionDefault keyDescription
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry

4.5. Query Menu

Table 9.6. Default query Function Bindings

FunctionDefault keyDescription
<create-alias>acreate an alias from a message sender
<mail>mcompose a new mail message
<query>Qquery external program for addresses
<query-append>Aappend new query results to current results

4.6. Attach Menu

Table 9.7. Default attach Function Bindings

FunctionDefault keyDescription
<bounce-message>bremail a message to another user
<display-toggle-weed>hdisplay message and toggle header weeding
<edit-type>^Eedit attachment content type
<print-entry>pprint the current entry
<save-entry>ssave message/attachment to a mailbox/file
<pipe-entry>|pipe message/attachment to a shell command
<view-mailcap>mforce viewing of attachment using mailcap
<reply>rreply to a message
<resend-message>Esc euse the current message as a template for a new one
<group-reply>greply to all recipients
<list-reply>Lreply to specified mailing list
<forward-message>fforward a message with comments
<view-text>Tview attachment as text
<view-attach><Return>view attachment using mailcap entry if necessary
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry
<collapse-parts>vToggle display of subparts
<check-traditional-pgp>Esc Pcheck for classic PGP
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory

4.7. Compose Menu

Table 9.8. Default compose Function Bindings

FunctionDefault keyDescription
<attach-file>aattach file(s) to this message
<attach-message>Aattach message(s) to this message
<edit-bcc>bedit the BCC list
<edit-cc>cedit the CC list
<copy-file>Csave message/attachment to a mailbox/file
<detach-file>Ddelete the current entry
<toggle-disposition>^Dtoggle disposition between inline/attachment
<edit-description>dedit attachment description
<edit-message>eedit the message
<edit-headers>Eedit the message with headers
<edit-file>^X eedit the file to be attached
<edit-encoding>^Eedit attachment transfer-encoding
<edit-from>Esc fedit the from field
<edit-fcc>fenter a file to save a copy of this message in
<filter-entry>Ffilter attachment through a shell command
<get-attachment>Gget a temporary copy of an attachment
<display-toggle-weed>hdisplay message and toggle header weeding
<ispell>irun ispell on the message
<print-entry>lprint the current entry
<edit-mime>medit attachment using mailcap entry
<new-mime>ncompose new attachment using mailcap entry
<postpone-message>Psave this message to send later
<edit-reply-to>redit the Reply-To field
<rename-file>Rrename/move an attached file
<edit-subject>sedit the subject of this message
<edit-to>tedit the TO list
<edit-type>^Tedit attachment content type
<write-fcc>wwrite the message to a folder
<toggle-unlink>utoggle whether to delete file after sending it
<toggle-recode> toggle recoding of this attachment
<update-encoding>Uupdate an attachment's encoding info
<view-attach><Return>view attachment using mailcap entry if necessary
<send-message>ysend the message
<pipe-entry>|pipe message/attachment to a shell command
<attach-key>Esc kattach a PGP public key
<pgp-menu>pshow PGP options
<forget-passphrase>^Fwipe passphrase(s) from memory
<smime-menu>Sshow S/MIME options
<mix>Msend the message through a mixmaster remailer chain

4.8. Postpone Menu

Table 9.9. Default postpone Function Bindings

FunctionDefault keyDescription
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry

4.9. Browser Menu

Table 9.10. Default browser Function Bindings

FunctionDefault keyDescription
<change-dir>cchange directories
<display-filename>@display the currently selected file's name
<enter-mask>menter a file mask
<sort>osort messages
<sort-reverse>Osort messages in reverse order
<select-new>Nselect a new file in this directory
<check-new> check mailboxes for new mail
<toggle-mailboxes><Tab>toggle whether to browse mailboxes or all files
<view-file><Space>view file
<buffy-list>.list mailboxes with new mail
<create-mailbox>Ccreate a new mailbox (IMAP only)
<delete-mailbox>ddelete the current mailbox (IMAP only)
<rename-mailbox>rrename the current mailbox (IMAP only)
<subscribe>ssubscribe to current mailbox (IMAP only)
<unsubscribe>uunsubscribe from current mailbox (IMAP only)
<toggle-subscribed>Ttoggle view all/subscribed mailboxes (IMAP only)

4.10. Pgp Menu

Table 9.11. Default pgp Function Bindings

FunctionDefault keyDescription
<verify-key>cverify a PGP public key
<view-name>%view the key's user id

4.11. Smime Menu

Table 9.12. Default smime Function Bindings

FunctionDefault keyDescription
<verify-key>cverify a PGP public key
<view-name>%view the key's user id

4.12. Mix Menu

Table 9.13. Default mix Function Bindings

FunctionDefault keyDescription
<accept><Return>Accept the chain constructed
<append>aAppend a remailer to the chain
<insert>iInsert a remailer into the chain
<delete>dDelete a remailer from the chain
<chain-prev><Left>Select the previous element of the chain
<chain-next><Right>Select the next element of the chain

4.13. Editor Menu

Table 9.14. Default editor Function Bindings

FunctionDefault keyDescription
<bol>^Ajump to the beginning of the line
<backward-char>^Bmove the cursor one character to the left
<backward-word>Esc bmove the cursor to the beginning of the word
<capitalize-word>Esc ccapitalize the word
<downcase-word>Esc lconvert the word to lower case
<upcase-word>Esc uconvert the word to upper case
<delete-char>^Ddelete the char under the cursor
<eol>^Ejump to the end of the line
<forward-char>^Fmove the cursor one character to the right
<forward-word>Esc fmove the cursor to the end of the word
<backspace><Backspace>delete the char in front of the cursor
<kill-eol>^Kdelete chars from cursor to end of line
<kill-eow>Esc ddelete chars from the cursor to the end of the word
<kill-line>^Udelete all chars on the line
<quote-char>^Vquote the next typed key
<kill-word>^Wdelete the word in front of the cursor
<complete><Tab>complete filename or alias
<complete-query>^Tcomplete address with query
<buffy-cycle><Space>cycle among incoming mailboxes
<history-up> scroll up through the history list
<history-down> scroll down through the history list
<transpose-chars> transpose character under cursor with previous

Prev   Next
Chapter 8. Performance Tuning Home Chapter 10. Miscellany
diff --git a/doc/security.html b/doc/security.html new file mode 100644 index 0000000..918f140 --- /dev/null +++ b/doc/security.html @@ -0,0 +1,90 @@ + + +Chapter 7. Security Considerations
Chapter 7. Security Considerations
Prev   Next

Chapter 7. Security Considerations

Table of Contents

1. Passwords
2. Temporary Files
3. Information Leaks
3.1. Message-Id: headers
3.2. mailto:-style Links
4. External Applications

+First of all, Mutt contains no security holes included by intention but +may contain unknown security holes. As a consequence, please run Mutt +only with as few permissions as possible. Especially, do not run Mutt as +the super user. +

+When configuring Mutt, there're some points to note about secure setups +so please read this chapter carefully. +

1. Passwords

+Although Mutt can be told the various passwords for accounts, please +never store passwords in configuration files. Besides the fact that the +system's operator can always read them, you could forget to mask it out +when reporting a bug or asking for help via a mailing list. Even worse, +your mail including your password could be archived by internet search +engines, mail-to-news gateways etc. It may already be too late before +you notice your mistake. +

2. Temporary Files

+Mutt uses many temporary files for viewing messages, verifying digital +signatures, etc. As long as being used, these files are visible by other +users and maybe even readable in case of misconfiguration. Also, a +different location for these files may be desired which can be changed +via the $tmpdir variable. +

3. Information Leaks

3.1. Message-Id: headers

+Message-Id: headers contain a local part that is to be created in a +unique fashion. In order to do so, Mutt will “leak” some +information to the outside world when sending messages: the generation +of this header includes a step counter which is increased (and rotated) +with every message sent. In a longer running mutt session, others can +make assumptions about your mailing habbits depending on the number of +messages sent. If this is not desired, the header can be manually +provided using $edit_headers (though not +recommended). +

3.2. mailto:-style Links

+As Mutt be can be set up to be the mail client to handle +mailto: style links in websites, there're security +considerations, too. Arbitrary header fields can be embedded in these +links which could override existing header fields or attach arbitrary +files using the Attach: +psuedoheader. This may be problematic if the $edit-headers variable is +unset, i.e. the user doesn't want to see header +fields while editing the message and doesn't pay enough attention to the +compose menu's listing of attachments. +

+For example, following a link like +

+mailto:joe@host?Attach=~/.gnupg/secring.gpg

+will send out the user's private gnupg keyring to +joe@host if the user doesn't follow the information +on screen carefully enough. +

4. External Applications

+Mutt in many places has to rely on external applications or for +convenience supports mechanisms involving external applications. +

+One of these is the mailcap mechanism as defined by +RfC1524. Details about a secure use of the mailcap mechanisms is given +in Section 3.2, “Secure Use of Mailcap”. +

+Besides the mailcap mechanism, Mutt uses a number of other external +utilities for operation, for example to provide crypto support, in +backtick expansion in configuration files or format string filters. The +same security considerations apply for these as for tools involved via +mailcap. +

Prev   Next
Chapter 6. Optional Features Home Chapter 8. Performance Tuning
diff --git a/doc/tuning.html b/doc/tuning.html index 34ceca0..fa2efed 100644 --- a/doc/tuning.html +++ b/doc/tuning.html @@ -1,48 +1,51 @@ -Chapter 7. Performance tuning
Chapter 7. Performance tuning
Prev   Next

Chapter 7. Performance tuning

Table of Contents

1. Reading and writing mailboxes
2. Reading messages from remote folders
3. Searching and limiting

1. Reading and writing mailboxes

+

Chapter 8. Performance Tuning
Prev   Next

Chapter 8. Performance Tuning

Table of Contents

1. Reading and Writing Mailboxes
2. Reading Messages from Remote Folders
3. Searching and Limiting

1. Reading and Writing Mailboxes

Mutt's performance when reading mailboxes can be improved in two ways:

  1. For remote folders (IMAP and POP) as well as folders using -one-file-per message storage (Maildir and MH), mutt's +one-file-per message storage (Maildir and MH), Mutt's performance can be greatly improved using -header caching. -Using a single database per folder may further increase -performance. +header caching. +using a single database per folder.

  2. -Mutt provides the $read_inc -and $write_inc +Mutt provides the $read_inc +and $write_inc variables to specify at which rate to update progress -counters. If these values are too low, mutt may spend more +counters. If these values are too low, Mutt may spend more time on updating the progress counter than it spends on actually reading/writing folders.

    For example, when opening a maildir folder with a few thousand messages, the default value for -$read_inc +$read_inc may be too low. It can be tuned on on a folder-basis using -folder-hooks: +folder-hooks: 

     # use very high $read_inc to speed up reading hcache'd maildirs
 folder-hook . 'set read_inc=1000'
@@ -55,18 +58,18 @@ even per-folder settings of the increment variables may not be
 desirable as they produce either too few or too much progress updates.
 Thus, Mutt allows to limit the number of progress updates per second it'll
 actually send to the terminal using the
-$time_inc variable.

2. Reading messages from remote folders

+$time_inc variable.

2. Reading Messages from Remote Folders

Reading messages from remote folders such as IMAP an POP can be -slow especially for large mailboxes since mutt only caches a very +slow especially for large mailboxes since Mutt only caches a very limited number of recently viewed messages (usually 10) per session (so that it will be gone for the next session.)

To improve performance and permanently cache whole messages, -please refer to mutt's so-called -body caching for details. -

3. Searching and limiting

+please refer to Mutt's so-called +body caching for details. +

3. Searching and Limiting

When searching mailboxes either via a search or a limit action, for -some patterns mutt distinguishes between regular expression and string +some patterns Mutt distinguishes between regular expression and string searches. For regular expressions, patterns are prefixed with “˜” and with “=” for string searches.

@@ -82,7 +85,7 @@ address via =Luser@ instead of ˜Luser@. This is especially true for searching message bodies since a larger amount of input has to be searched.

-Please note that string search is an exact case-sensitive search -while a regular expression search with only lower-case letters performs -a case-insensitive search. -

Prev   Next
Chapter 6. Optional features Home Chapter 8. Reference
+As for regular expressions, a lower case string search pattern makes +Mutt perform a case-insensitive search except for IMAP (because for IMAP +Mutt performs server-side searches which don't support case-insensivity). +

Prev   Next
Chapter 7. Security Considerations Home Chapter 9. Reference
diff --git a/edit.c b/edit.c index d952e9a..4d74912 100644 --- a/edit.c +++ b/edit.c @@ -109,7 +109,7 @@ be_snarf_file (const char *path, char **buf, int *max, int *len, int verbose) snprintf(tmp, sizeof(tmp), "\"%s\" %lu bytes\n", path, (unsigned long) sb.st_size); addstr(tmp); } - fclose (f); + safe_fclose (&f); } else { @@ -153,8 +153,7 @@ be_include_messages (char *msg, char **buf, int *bufmax, int *buflen, while ((msg = strtok (msg, " ,")) != NULL) { - n = atoi (msg); - if (n > 0 && n <= Context->msgcount) + if (mutt_atoi (msg, &n) == 0 && n > 0 && n <= Context->msgcount) { n--; diff --git a/editmsg.c b/editmsg.c index 85b75e3..ecba754 100644 --- a/editmsg.c +++ b/editmsg.c @@ -191,7 +191,7 @@ static int edit_one_message (CONTEXT *ctx, HEADER *cur) mx_close_mailbox (&tmpctx, NULL); bail: - if (fp) fclose (fp); + if (fp) safe_fclose (&fp); if (rc >= 0) unlink (tmp); diff --git a/functions.h b/functions.h index f0add78..552a0a3 100644 --- a/functions.h +++ b/functions.h @@ -183,6 +183,8 @@ struct binding_t OpPager[] = { /* map: pager */ { "delete-message", OP_DELETE, "d" }, { "delete-thread", OP_DELETE_THREAD, "\004" }, { "delete-subthread", OP_DELETE_SUBTHREAD, "\033d" }, + { "set-flag", OP_MAIN_SET_FLAG, "w" }, + { "clear-flag", OP_MAIN_CLEAR_FLAG, "W" }, { "edit", OP_EDIT_MESSAGE, "e" }, { "edit-type", OP_EDIT_TYPE, "\005" }, { "forward-message", OP_FORWARD_MESSAGE, "f" }, diff --git a/globals.h b/globals.h index 5be0237..94aa457 100644 --- a/globals.h +++ b/globals.h @@ -113,6 +113,7 @@ WHERE char *PrintCmd; WHERE char *QueryCmd; WHERE char *QueryFormat; WHERE char *Realname; +WHERE short SearchContext; WHERE char *SendCharset; WHERE char *Sendmail; WHERE char *Shell; diff --git a/gnupgparse.c b/gnupgparse.c index 0bfb198..56f9061 100644 --- a/gnupgparse.c +++ b/gnupgparse.c @@ -123,13 +123,22 @@ static pgp_key_t parse_pub_line (char *buf, int *is_subkey, pgp_key_t k) char *pend, *p; int trust = 0; int flags = 0; + struct pgp_keyinfo tmp; *is_subkey = 0; if (!*buf) return NULL; - + + /* if we're given a key, merge our parsing results, else + * start with a fresh one to work with so that we don't + * mess up the real key in case we find parsing errors. */ + if (k) + memcpy (&tmp, k, sizeof (tmp)); + else + memset (&tmp, 0, sizeof (tmp)); + dprint (2, (debugfile, "parse_pub_line: buf = `%s'\n", buf)); - + for (p = buf; p; p = pend) { if ((pend = strchr (p, ':'))) @@ -143,7 +152,7 @@ static pgp_key_t parse_pub_line (char *buf, int *is_subkey, pgp_key_t k) case 1: /* record type */ { dprint (2, (debugfile, "record type: %s\n", p)); - + if (!mutt_strcmp (p, "pub")) ; else if (!mutt_strcmp (p, "sub")) @@ -156,16 +165,16 @@ static pgp_key_t parse_pub_line (char *buf, int *is_subkey, pgp_key_t k) is_uid = 1; else return NULL; - + if (!(is_uid || (*is_subkey && option (OPTPGPIGNORESUB)))) - k = safe_calloc (sizeof *k, 1); + memset (&tmp, 0, sizeof (tmp)); break; } case 2: /* trust info */ { dprint (2, (debugfile, "trust info: %s\n", p)); - + switch (*p) { /* look only at the first letter */ case 'e': @@ -192,37 +201,39 @@ static pgp_key_t parse_pub_line (char *buf, int *is_subkey, pgp_key_t k) } if (!is_uid && !(*is_subkey && option (OPTPGPIGNORESUB))) - k->flags |= flags; + tmp.flags |= flags; break; } case 3: /* key length */ { - dprint (2, (debugfile, "key len: %s\n", p)); - - if (!(*is_subkey && option (OPTPGPIGNORESUB))) - k->keylen = atoi (p); /* fixme: add validation checks */ + + if (!(*is_subkey && option (OPTPGPIGNORESUB)) && + mutt_atos (p, &tmp.keylen) < 0) + goto bail; break; } case 4: /* pubkey algo */ { - dprint (2, (debugfile, "pubkey algorithm: %s\n", p)); - + if (!(*is_subkey && option (OPTPGPIGNORESUB))) { - k->numalg = atoi (p); - k->algorithm = pgp_pkalgbytype (atoi (p)); + int x = 0; + if (mutt_atoi (p, &x) < 0) + goto bail; + tmp.numalg = x; + tmp.algorithm = pgp_pkalgbytype (x); } break; } case 5: /* 16 hex digits with the long keyid. */ { dprint (2, (debugfile, "key id: %s\n", p)); - + if (!(*is_subkey && option (OPTPGPIGNORESUB))) - mutt_str_replace (&k->keyid, p); + mutt_str_replace (&tmp.keyid, p); break; } @@ -230,9 +241,9 @@ static pgp_key_t parse_pub_line (char *buf, int *is_subkey, pgp_key_t k) { char tstr[11]; struct tm time; - + dprint (2, (debugfile, "time stamp: %s\n", p)); - + if (!p) break; time.tm_sec = 0; @@ -240,11 +251,25 @@ static pgp_key_t parse_pub_line (char *buf, int *is_subkey, pgp_key_t k) time.tm_hour = 12; strncpy (tstr, p, 11); tstr[4] = '\0'; - time.tm_year = atoi (tstr)-1900; tstr[7] = '\0'; - time.tm_mon = (atoi (tstr+5))-1; - time.tm_mday = atoi (tstr+8); - k->gen_time = mutt_mktime (&time, 0); + if (mutt_atoi (tstr, &time.tm_year) < 0) + { + p = tstr; + goto bail; + } + time.tm_year -= 1900; + if (mutt_atoi (tstr+5, &time.tm_mon) < 0) + { + p = tstr+5; + goto bail; + } + time.tm_mon -= 1; + if (mutt_atoi (tstr+8, &time.tm_mday) < 0) + { + p = tstr+8; + goto bail; + } + tmp.gen_time = mutt_mktime (&time, 0); break; } case 7: /* valid for n days */ @@ -261,22 +286,21 @@ static pgp_key_t parse_pub_line (char *buf, int *is_subkey, pgp_key_t k) /* ignore user IDs on subkeys */ if (!is_uid && (*is_subkey && option (OPTPGPIGNORESUB))) break; - + dprint (2, (debugfile, "user ID: %s\n", p)); - + uid = safe_calloc (sizeof (pgp_uid_t), 1); fix_uid (p); uid->addr = safe_strdup (p); uid->trust = trust; uid->flags |= flags; - uid->parent = k; - uid->next = k->address; - k->address = uid; - + uid->next = tmp.address; + tmp.address = uid; + if (strstr (p, "ENCR")) - k->flags |= KEYFLAG_PREFER_ENCRYPTION; + tmp.flags |= KEYFLAG_PREFER_ENCRYPTION; if (strstr (p, "SIGN")) - k->flags |= KEYFLAG_PREFER_SIGNING; + tmp.flags |= KEYFLAG_PREFER_SIGNING; break; } @@ -308,7 +332,7 @@ static pgp_key_t parse_pub_line (char *buf, int *is_subkey, pgp_key_t k) || !((flags & KEYFLAG_DISABLED) || (flags & KEYFLAG_REVOKED) || (flags & KEYFLAG_EXPIRED)))) - k->flags |= flags; + tmp.flags |= flags; break; @@ -316,7 +340,24 @@ static pgp_key_t parse_pub_line (char *buf, int *is_subkey, pgp_key_t k) break; } } + + /* merge temp key back into real key */ + if (!(is_uid || (*is_subkey && option (OPTPGPIGNORESUB)))) + k = safe_malloc (sizeof (*k)); + memcpy (k, &tmp, sizeof (*k)); + /* fixup parentship of uids after mering the temp key into + * the real key */ + if (tmp.address) + { + for (uid = k->address; uid; uid = uid->next) + uid->parent = k; + } + return k; + +bail: + dprint(5,(debugfile,"parse_pub_line: invalid number: '%s'\n", p)); + return NULL; } pgp_key_t pgp_get_candidates (pgp_ring_t keyring, LIST * hints) @@ -373,7 +414,7 @@ pgp_key_t pgp_get_candidates (pgp_ring_t keyring, LIST * hints) if (ferror (fp)) mutt_perror ("fgets"); - fclose (fp); + safe_fclose (&fp); mutt_wait_filter (thepid); close (devnull); diff --git a/group.c b/group.c index 030c451..7f8206b 100644 --- a/group.c +++ b/group.c @@ -86,7 +86,7 @@ void mutt_group_add_adrlist (group_t *g, ADDRESS *a) for (p = &g->as; *p; p = &((*p)->next)) ; - q = rfc822_cpy_adr (a); + q = rfc822_cpy_adr (a, 0); q = mutt_remove_xrefs (g->as, q); *p = q; } diff --git a/handler.c b/handler.c index 79543a2..57dab0f 100644 --- a/handler.c +++ b/handler.c @@ -173,9 +173,9 @@ static void qp_decode_line (char *dest, char *src, size_t *l, int last) { char *d, *s; - char c; + char c = 0; - int kind; + int kind = -1; int soft = 0; /* decode the line */ @@ -191,7 +191,15 @@ static void qp_decode_line (char *dest, char *src, size_t *l, } if (!soft && last == '\n') - *d++ = '\n'; + { + /* neither \r nor \n as part of line-terminating CRLF + * may be qp-encoded, so remove \r and \n-terminate; + * see RfC2045, sect. 6.7, (1): General 8bit representation */ + if (kind == 0 && c == '\r') + *(d-1) = '\n'; + else + *d++ = '\n'; + } *d = '\0'; *l = d - dest; @@ -427,23 +435,23 @@ enum { RICH_PARAM=0, RICH_BOLD, RICH_UNDERLINE, RICH_ITALIC, RICH_NOFILL, RICH_FLUSHRIGHT, RICH_COLOR, RICH_LAST_TAG }; static struct { - const char *tag_name; + const wchar_t *tag_name; int index; } EnrichedTags[] = { - { "param", RICH_PARAM }, - { "bold", RICH_BOLD }, - { "italic", RICH_ITALIC }, - { "underline", RICH_UNDERLINE }, - { "nofill", RICH_NOFILL }, - { "excerpt", RICH_EXCERPT }, - { "indent", RICH_INDENT }, - { "indentright", RICH_INDENT_RIGHT }, - { "center", RICH_CENTER }, - { "flushleft", RICH_FLUSHLEFT }, - { "flushright", RICH_FLUSHRIGHT }, - { "flushboth", RICH_FLUSHLEFT }, - { "color", RICH_COLOR }, - { "x-color", RICH_COLOR }, + { L"param", RICH_PARAM }, + { L"bold", RICH_BOLD }, + { L"italic", RICH_ITALIC }, + { L"underline", RICH_UNDERLINE }, + { L"nofill", RICH_NOFILL }, + { L"excerpt", RICH_EXCERPT }, + { L"indent", RICH_INDENT }, + { L"indentright", RICH_INDENT_RIGHT }, + { L"center", RICH_CENTER }, + { L"flushleft", RICH_FLUSHLEFT }, + { L"flushright", RICH_FLUSHRIGHT }, + { L"flushboth", RICH_FLUSHLEFT }, + { L"color", RICH_COLOR }, + { L"x-color", RICH_COLOR }, { NULL, -1 } }; @@ -466,27 +474,6 @@ struct enriched_state STATE *s; }; -static int enriched_cmp (const char *a, const wchar_t *b) -{ - register const char *p = a; - register const wchar_t *q = b; - int i; - - if (!a && !b) - return 0; - if (!a && b) - return -1; - if (a && !b) - return 1; - - for ( ; *p || *q; p++, q++) - { - if ((i = ascii_tolower (*p)) - ascii_tolower (((char) *q) & 0x7f)) - return i; - } - return 0; -} - static void enriched_wrap (struct enriched_state *stte) { int x; @@ -618,8 +605,9 @@ static void enriched_flush (struct enriched_state *stte, int wrap) stte->word_len = 0; stte->buff_used = 0; } - if (wrap) + if (wrap) enriched_wrap(stte); + fflush (stte->s->fpout); } @@ -716,7 +704,7 @@ static void enriched_set_flags (const wchar_t *tag, struct enriched_state *stte) tagptr++; for (i = 0, j = -1; EnrichedTags[i].tag_name; i++) - if (enriched_cmp (EnrichedTags[i].tag_name, tagptr) == 0) + if (wcscasecmp (EnrichedTags[i].tag_name, tagptr) == 0) { j = EnrichedTags[i].index; break; @@ -734,35 +722,35 @@ static void enriched_set_flags (const wchar_t *tag, struct enriched_state *stte) if ((stte->s->flags & M_DISPLAY) && j == RICH_PARAM && stte->tag_level[RICH_COLOR]) { stte->param[stte->param_used] = (wchar_t) '\0'; - if (!enriched_cmp("black", stte->param)) + if (!wcscasecmp(L"black", stte->param)) { enriched_puts("\033[30m", stte); } - else if (!enriched_cmp("red", stte->param)) + else if (!wcscasecmp(L"red", stte->param)) { enriched_puts("\033[31m", stte); } - else if (!enriched_cmp("green", stte->param)) + else if (!wcscasecmp(L"green", stte->param)) { enriched_puts("\033[32m", stte); } - else if (!enriched_cmp("yellow", stte->param)) + else if (!wcscasecmp(L"yellow", stte->param)) { enriched_puts("\033[33m", stte); } - else if (!enriched_cmp("blue", stte->param)) + else if (!wcscasecmp(L"blue", stte->param)) { enriched_puts("\033[34m", stte); } - else if (!enriched_cmp("magenta", stte->param)) + else if (!wcscasecmp(L"magenta", stte->param)) { enriched_puts("\033[35m", stte); } - else if (!enriched_cmp("cyan", stte->param)) + else if (!wcscasecmp(L"cyan", stte->param)) { enriched_puts("\033[36m", stte); } - else if (!enriched_cmp("white", stte->param)) + else if (!wcscasecmp(L"white", stte->param)) { enriched_puts("\033[37m", stte); } @@ -1101,7 +1089,8 @@ static int message_handler (BODY *a, STATE *s) { mutt_copy_hdr (s->fpin, s->fpout, off_start, b->parts->offset, (((s->flags & M_WEED) || ((s->flags & (M_DISPLAY|M_PRINTING)) && option (OPTWEED))) ? (CH_WEED | CH_REORDER) : 0) | - (s->prefix ? CH_PREFIX : 0) | CH_DECODE | CH_FROM, s->prefix); + (s->prefix ? CH_PREFIX : 0) | CH_DECODE | CH_FROM | + (s->flags & M_DISPLAY) ? CH_DISPLAY : 0, s->prefix); if (s->prefix) state_puts (s->prefix, s); @@ -1206,15 +1195,7 @@ static int multipart_handler (BODY *a, STATE *s) else state_putc ('\n', s); } - else - { - if (p->description && mutt_can_decode (p)) - state_printf (s, "Content-Description: %s\n", p->description); - - if (p->form_name) - state_printf(s, "%s: \n", p->form_name); - } rc = mutt_body_handler (p, s); state_putc ('\n', s); @@ -1444,7 +1425,7 @@ static int external_body_handler (BODY *b, STATE *s) mutt_copy_hdr(s->fpin, s->fpout, ftello (s->fpin), b->parts->offset, (option (OPTWEED) ? (CH_WEED | CH_REORDER) : 0) | - CH_DECODE, NULL); + CH_DECODE | CH_DISPLAY, NULL); } } else @@ -1461,7 +1442,7 @@ static int external_body_handler (BODY *b, STATE *s) access_type); mutt_copy_hdr (s->fpin, s->fpout, ftello (s->fpin), b->parts->offset, (option (OPTWEED) ? (CH_WEED | CH_REORDER) : 0) | - CH_DECODE , NULL); + CH_DECODE | CH_DISPLAY, NULL); } } @@ -1505,6 +1486,34 @@ void mutt_decode_attachment (BODY *b, STATE *s) iconv_close (cd); } +/* when generating format=flowed ($text_flowed is set) from format=fixed, + * strip all trailing spaces to improve interoperability; + * if $text_flowed is unset, simply verbatim copy input + */ +static int text_plain_handler (BODY *b, STATE *s) +{ + char buf[LONG_STRING]; + size_t l; + + while (fgets (buf, sizeof (buf), s->fpin)) + { + l = mutt_strlen (buf); + if (l > 0 && buf[l-1] == '\n') + buf[--l] = 0; + if (option (OPTTEXTFLOWED)) + { + while (l > 0 && buf[l-1] == ' ') + buf[--l] = 0; + } + if (s->prefix) + state_puts (s->prefix, s); + state_puts (buf, s); + state_putc ('\n', s); + } + + return 0; +} + int mutt_body_handler (BODY *b, STATE *s) { int decode = 0; @@ -1545,7 +1554,7 @@ int mutt_body_handler (BODY *b, STATE *s) else if (ascii_strcasecmp ("flowed", mutt_get_parameter ("format", b->parameter)) == 0) handler = rfc3676_handler; else - plaintext = 1; + handler = text_plain_handler; } else if (ascii_strcasecmp ("enriched", b->subtype) == 0) handler = text_enriched_handler; @@ -1612,8 +1621,11 @@ int mutt_body_handler (BODY *b, STATE *s) handler = crypt_smime_application_smime_handler; } - - if (plaintext || handler) + /* only respect disposition == attachment if we're not + displaying from the attachment menu (i.e. pager) */ + if ((!option (OPTHONORDISP) || (b->disposition != DISPATTACH || + option(OPTVIEWATTACH))) && + (plaintext || handler)) { fseeko (s->fpin, b->offset, 0); @@ -1663,7 +1675,7 @@ int mutt_body_handler (BODY *b, STATE *s) { b->length = ftello (s->fpout); b->offset = 0; - fclose (s->fpout); + safe_fclose (&s->fpout); /* restore final destination and substitute the tempfile for input */ s->fpout = fp; @@ -1694,16 +1706,24 @@ int mutt_body_handler (BODY *b, STATE *s) b->offset = tmpoffset; /* restore the original source stream */ - fclose (s->fpin); + safe_fclose (&s->fpin); s->fpin = fp; } } s->flags |= M_FIRSTDONE; } - else if (s->flags & M_DISPLAY) + /* print hint to use attachment menu for disposition == attachment + if we're not already being called from there */ + else if ((s->flags & M_DISPLAY) || (b->disposition == DISPATTACH && + !option (OPTVIEWATTACH) && + option (OPTHONORDISP) && + (plaintext || handler))) { state_mark_attach (s); - state_printf (s, _("[-- %s/%s is unsupported "), TYPE (b), b->subtype); + if (option (OPTHONORDISP) && b->disposition == DISPATTACH) + fputs (_("[-- This is an attachment "), s->fpout); + else + state_printf (s, _("[-- %s/%s is unsupported "), TYPE (b), b->subtype); if (!option (OPTVIEWATTACH)) { if (km_expand_key (type, sizeof(type), diff --git a/hash.c b/hash.c index 7e4e19f..08f7171 100644 --- a/hash.c +++ b/hash.c @@ -1,5 +1,5 @@ /* - * Copyright (C) 1996-2000 Michael R. Elkins + * Copyright (C) 1996-2009 Michael R. Elkins * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by @@ -23,12 +23,13 @@ #include #include #include +#include #include "mutt.h" #define SOMEPRIME 149711 -unsigned int hash_string (const unsigned char *s, unsigned int n) +static unsigned int hash_string (const unsigned char *s, unsigned int n) { unsigned int h = 0; @@ -39,13 +40,34 @@ unsigned int hash_string (const unsigned char *s, unsigned int n) return h; } -HASH *hash_create (int nelem) +static unsigned int hash_case_string (const unsigned char *s, unsigned int n) +{ + unsigned int h = 0; + + while (*s) + h += (h << 7) + tolower (*s++); + h = (h * SOMEPRIME) % n; + + return h; +} + +HASH *hash_create (int nelem, int lower) { HASH *table = safe_malloc (sizeof (HASH)); if (nelem == 0) nelem = 2; table->nelem = nelem; table->table = safe_calloc (nelem, sizeof (struct hash_elem *)); + if (lower) + { + table->hash_string = hash_case_string; + table->cmp_string = mutt_strcasecmp; + } + else + { + table->hash_string = hash_string; + table->cmp_string = mutt_strcmp; + } return table; } @@ -57,10 +79,10 @@ HASH *hash_create (int nelem) int hash_insert (HASH * table, const char *key, void *data, int allow_dup) { struct hash_elem *ptr; - int h; + unsigned int h; ptr = (struct hash_elem *) safe_malloc (sizeof (struct hash_elem)); - h = hash_string ((unsigned char *) key, table->nelem); + h = table->hash_string ((unsigned char *) key, table->nelem); ptr->key = key; ptr->data = data; @@ -76,7 +98,7 @@ int hash_insert (HASH * table, const char *key, void *data, int allow_dup) for (tmp = table->table[h], last = NULL; tmp; last = tmp, tmp = tmp->next) { - r = mutt_strcmp (tmp->key, key); + r = table->cmp_string (tmp->key, key); if (r == 0) { FREE (&ptr); @@ -99,7 +121,7 @@ void *hash_find_hash (const HASH * table, int hash, const char *key) struct hash_elem *ptr = table->table[hash]; for (; ptr; ptr = ptr->next) { - if (mutt_strcmp (key, ptr->key) == 0) + if (table->cmp_string (key, ptr->key) == 0) return (ptr->data); } return NULL; @@ -114,7 +136,7 @@ void hash_delete_hash (HASH * table, int hash, const char *key, const void *data while (ptr) { if ((data == ptr->data || !data) - && mutt_strcmp (ptr->key, key) == 0) + && table->cmp_string (ptr->key, key) == 0) { *last = ptr->next; if (destroy) diff --git a/hash.h b/hash.h index 5338aca..fb77d0c 100644 --- a/hash.h +++ b/hash.h @@ -1,5 +1,5 @@ /* - * Copyright (C) 1996-2000 Michael R. Elkins + * Copyright (C) 1996-2009 Michael R. Elkins * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by @@ -30,15 +30,16 @@ typedef struct { int nelem; struct hash_elem **table; + unsigned int (*hash_string)(const unsigned char *, unsigned int); + int (*cmp_string)(const char *, const char *); } HASH; -#define hash_find(table, key) hash_find_hash(table, hash_string ((unsigned char *)key, table->nelem), key) +#define hash_find(table, key) hash_find_hash(table, table->hash_string ((unsigned char *)key, table->nelem), key) -#define hash_delete(table,key,data,destroy) hash_delete_hash(table, hash_string ((unsigned char *)key, table->nelem), key, data, destroy) +#define hash_delete(table,key,data,destroy) hash_delete_hash(table, table->hash_string ((unsigned char *)key, table->nelem), key, data, destroy) -HASH *hash_create (int nelem); -unsigned int hash_string (const unsigned char *s, unsigned int n); +HASH *hash_create (int nelem, int lower); int hash_insert (HASH * table, const char *key, void *data, int allow_dup); void *hash_find_hash (const HASH * table, int hash, const char *key); void hash_delete_hash (HASH * table, int hash, const char *key, const void *data, diff --git a/hcache.c b/hcache.c index ece4ca9..8b14aef 100644 --- a/hcache.c +++ b/hcache.c @@ -836,7 +836,7 @@ static char* get_foldername(const char *folder) { * to ensure equivalent paths share the hcache */ if (stat (folder, &st) == 0) { - p = safe_malloc (_POSIX_PATH_MAX+1); + p = safe_malloc (PATH_MAX+1); if (!realpath (folder, p)) mutt_str_replace (&p, folder); } else @@ -940,7 +940,10 @@ mutt_hcache_delete(header_cache_t *h, const char *filename, static int hcache_open_gdbm (struct header_cache* h, const char* path) { - int pagesize = atoi(HeaderCachePageSize) ? atoi(HeaderCachePageSize) : 16384; + int pagesize; + + if (mutt_atoi (HeaderCachePageSize, &pagesize) < 0 || pagesize <= 0) + pagesize = 16384; h->db = gdbm_open((char *) path, pagesize, GDBM_WRCREAT, 00600, NULL); if (h->db) @@ -1008,7 +1011,10 @@ hcache_open_db4 (struct header_cache* h, const char* path) struct stat sb; int ret; u_int32_t createflags = DB_CREATE; - int pagesize = atoi (HeaderCachePageSize); + int pagesize; + + if (mutt_atoi (HeaderCachePageSize, &pagesize) < 0 || pagesize <= 0) + pagesize = 16384; snprintf (h->lockfile, _POSIX_PATH_MAX, "%s-lock-hack", path); diff --git a/hdrline.c b/hdrline.c index fe45096..21adc28 100644 --- a/hdrline.c +++ b/hdrline.c @@ -121,6 +121,8 @@ static void make_from (ENVELOPE *hdr, char *buf, size_t len, int do_lists) snprintf (buf, len, "To %s", mutt_get_name (hdr->to)); else if (me && hdr->cc) snprintf (buf, len, "Cc %s", mutt_get_name (hdr->cc)); + else if (me && hdr->bcc) + snprintf (buf, len, "Bcc %s", mutt_get_name (hdr->bcc)); else if (hdr->from) strfcpy (buf, mutt_get_name (hdr->from), len); else diff --git a/headers.c b/headers.c index 0aa7915..5d22489 100644 --- a/headers.c +++ b/headers.c @@ -1,5 +1,5 @@ /* - * Copyright (C) 1996-2000 Michael R. Elkins + * Copyright (C) 1996-2009 Michael R. Elkins * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by @@ -64,8 +64,8 @@ void mutt_edit_headers (const char *editor, mutt_copy_stream (ifp, ofp); - fclose (ifp); - fclose (ofp); + safe_fclose (&ifp); + safe_fclose (&ofp); if (stat (path, &st) == -1) { @@ -98,7 +98,7 @@ void mutt_edit_headers (const char *editor, if ((ofp = safe_fopen (body, "w")) == NULL) { /* intentionally leak a possible temporary file here */ - fclose (ifp); + safe_fclose (&ifp); mutt_perror (body); return; } @@ -106,20 +106,27 @@ void mutt_edit_headers (const char *editor, n = mutt_read_rfc822_header (ifp, NULL, 1, 0); while ((i = fread (buffer, 1, sizeof (buffer), ifp)) > 0) fwrite (buffer, 1, i, ofp); - fclose (ofp); - fclose (ifp); + safe_fclose (&ofp); + safe_fclose (&ifp); mutt_unlink (path); + /* in case the user modifies/removes the In-Reply-To header with + $edit_headers set, we remove References: as they're likely invalid; + we can simply compare strings as we don't generate References for + multiple Message-Ids in IRT anyways */ + if (!n->in_reply_to || (msg->env->in_reply_to && + mutt_strcmp (n->in_reply_to->data, + msg->env->in_reply_to->data) != 0)) + mutt_free_list (&msg->env->references); + /* restore old info. */ + mutt_free_list (&n->references); n->references = msg->env->references; msg->env->references = NULL; mutt_free_envelope (&msg->env); msg->env = n; n = NULL; - if (!msg->env->in_reply_to) - mutt_free_list (&msg->env->references); - mutt_expand_aliases_env (msg->env); /* search through the user defined headers added to see if @@ -147,23 +154,32 @@ void mutt_edit_headers (const char *editor, { BODY *body; BODY *parts; - char *q; + int l = 0; p = cur->data + 7; SKIPWS (p); if (*p) { - if ((q = strpbrk (p, " \t"))) + for ( ; *p && *p != ' ' && *p != '\t'; p++) { - mutt_substrcpy (path, p, q, sizeof (path)); - SKIPWS (q); + if (*p == '\\') + { + if (!*(p+1)) + break; + p++; + } + if (l < sizeof (path) - 1) + path[l++] = *p; } - else - strfcpy (path, p, sizeof (path)); + if (*p) + *p++ = 0; + SKIPWS (p); + path[l] = 0; + mutt_expand_path (path, sizeof (path)); if ((body = mutt_make_file_attach (path))) { - body->description = safe_strdup (q); + body->description = safe_strdup (p); for (parts = msg->content; parts->next; parts = parts->next) ; parts->next = body; } diff --git a/help.c b/help.c index 88f465a..10ad9cf 100644 --- a/help.c +++ b/help.c @@ -1,5 +1,5 @@ /* - * Copyright (C) 1996-2000 Michael R. Elkins + * Copyright (C) 1996-2000,2009 Michael R. Elkins * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by @@ -256,7 +256,7 @@ static void format_line (FILE *f, int ismacro, n = get_wrapped_width (t3, n); } - print_macro (f, n, &t3); + n = print_macro (f, n, &t3); if (*t3) { @@ -367,7 +367,7 @@ void mutt_help (int menu) if (menu != MENU_PAGER) dump_unbound (f, OpGeneric, Keymaps[MENU_GENERIC], Keymaps[menu]); - fclose (f); + safe_fclose (&f); snprintf (buf, sizeof (buf), _("Help for %s"), desc); } diff --git a/history.c b/history.c index f8702d4..6852816 100644 --- a/history.c +++ b/history.c @@ -68,7 +68,7 @@ void mutt_read_histfile (void) if ((f = fopen (HistFile, "r")) == NULL) return; - while ((linebuf = mutt_read_line (linebuf, &buflen, f, &line)) != NULL) + while ((linebuf = mutt_read_line (linebuf, &buflen, f, &line, 0)) != NULL) { read = 0; if (sscanf (linebuf, "%d:%n", &hclass, &read) < 1 || read == 0 || @@ -90,7 +90,7 @@ void mutt_read_histfile (void) } } - fclose (f); + safe_fclose (&f); FREE (&linebuf); } @@ -107,7 +107,7 @@ static void shrink_histfile (void) return; line = 0; - while ((linebuf = mutt_read_line (linebuf, &buflen, f, &line)) != NULL) + while ((linebuf = mutt_read_line (linebuf, &buflen, f, &line, 0)) != NULL) { if (sscanf (linebuf, "%d", &hclass) < 1 || hclass < 0) { @@ -133,7 +133,7 @@ static void shrink_histfile (void) { rewind (f); line = 0; - while ((linebuf = mutt_read_line (linebuf, &buflen, f, &line)) != NULL) + while ((linebuf = mutt_read_line (linebuf, &buflen, f, &line, 0)) != NULL) { if (sscanf (linebuf, "%d", &hclass) < 1 || hclass < 0) { @@ -149,7 +149,7 @@ static void shrink_histfile (void) } cleanup: - fclose (f); + safe_fclose (&f); FREE (&linebuf); if (tmp != NULL) { @@ -158,9 +158,9 @@ cleanup: { rewind (tmp); mutt_copy_stream (tmp, f); - fclose (f); + safe_fclose (&f); } - fclose (tmp); + safe_fclose (&tmp); unlink (tmpfname); } } @@ -196,7 +196,7 @@ static void save_history (history_class_t hclass, const char *s) } fputs ("|\n", f); - fclose (f); + safe_fclose (&f); FREE (&tmp); if (--n < 0) diff --git a/hook.c b/hook.c index 8df5781..d71cdf7 100644 --- a/hook.c +++ b/hook.c @@ -460,11 +460,19 @@ char *mutt_crypt_hook (ADDRESS *adr) #ifdef USE_SOCKET void mutt_account_hook (const char* url) { + /* parsing commands with URLs in an account hook can cause a recursive + * call. We just skip processing if this occurs. Typically such commands + * belong in a folder-hook -- perhaps we should warn the user. */ + static int inhook = 0; + HOOK* hook; BUFFER token; BUFFER err; char buf[STRING]; + if (inhook) + return; + err.data = buf; err.dsize = sizeof (buf); memset (&token, 0, sizeof (token)); @@ -476,14 +484,19 @@ void mutt_account_hook (const char* url) if ((regexec (hook->rx.rx, url, 0, NULL, 0) == 0) ^ hook->rx.not) { + inhook = 1; + if (mutt_parse_rc_line (hook->command, &token, &err) == -1) { FREE (&token.data); mutt_error ("%s", err.data); mutt_sleep (1); + inhook = 0; return; } + + inhook = 0; } } diff --git a/imap/Makefile.in b/imap/Makefile.in index 3eb1e68..43fba13 100644 --- a/imap/Makefile.in +++ b/imap/Makefile.in @@ -1,8 +1,9 @@ -# Makefile.in generated by automake 1.10.1 from Makefile.am. +# Makefile.in generated by automake 1.11 from Makefile.am. # @configure_input@ # Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, -# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. +# 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, +# Inc. # This Makefile.in is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. @@ -17,8 +18,9 @@ VPATH = @srcdir@ pkgdatadir = $(datadir)/@PACKAGE@ -pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkglibexecdir = $(libexecdir)/@PACKAGE@ am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd install_sh_DATA = $(install_sh) -c -m 644 install_sh_PROGRAM = $(install_sh) -c @@ -42,14 +44,14 @@ am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \ $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \ $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \ $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \ - $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/libgnutls.m4 \ - $(top_srcdir)/m4/progtest.m4 $(top_srcdir)/m4/types.m4 \ - $(top_srcdir)/configure.ac + $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \ + $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ $(ACLOCAL_M4) mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs CONFIG_HEADER = $(top_builddir)/config.h CONFIG_CLEAN_FILES = +CONFIG_CLEAN_VPATH_FILES = LIBRARIES = $(noinst_LIBRARIES) ARFLAGS = cru libimap_a_AR = $(AR) $(ARFLAGS) @@ -69,6 +71,7 @@ libimap_a_OBJECTS = $(am_libimap_a_OBJECTS) DEFAULT_INCLUDES = -I.@am__isrc@ -I$(top_builddir) depcomp = $(SHELL) $(top_srcdir)/depcomp am__depfiles_maybe = depfiles +am__mv = mv -f COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \ $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) CCLD = $(CC) @@ -133,9 +136,6 @@ INTL_LIBTOOL_SUFFIX_PREFIX = @INTL_LIBTOOL_SUFFIX_PREFIX@ ISPELL = @ISPELL@ KRB5CFGPATH = @KRB5CFGPATH@ LDFLAGS = @LDFLAGS@ -LIBGNUTLS_CFLAGS = @LIBGNUTLS_CFLAGS@ -LIBGNUTLS_CONFIG = @LIBGNUTLS_CONFIG@ -LIBGNUTLS_LIBS = @LIBGNUTLS_LIBS@ LIBICONV = @LIBICONV@ LIBIMAP = @LIBIMAP@ LIBIMAPDEPS = @LIBIMAPDEPS@ @@ -221,6 +221,7 @@ sharedstatedir = @sharedstatedir@ srcdir = @srcdir@ sysconfdir = @sysconfdir@ target_alias = @target_alias@ +top_build_prefix = @top_build_prefix@ top_builddir = @top_builddir@ top_srcdir = @top_srcdir@ AUTOMAKE_OPTIONS = 1.6 foreign @@ -242,14 +243,14 @@ $(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(am__configure_deps) @for dep in $?; do \ case '$(am__configure_deps)' in \ *$$dep*) \ - cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \ - && exit 0; \ + ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \ + && { if test -f $@; then exit 0; else break; fi; }; \ exit 1;; \ esac; \ done; \ - echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign imap/Makefile'; \ - cd $(top_srcdir) && \ - $(AUTOMAKE) --foreign imap/Makefile + echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign imap/Makefile'; \ + $(am__cd) $(top_srcdir) && \ + $(AUTOMAKE) --foreign imap/Makefile .PRECIOUS: Makefile Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status @case '$?' in \ @@ -267,6 +268,7 @@ $(top_srcdir)/configure: $(am__configure_deps) cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh $(ACLOCAL_M4): $(am__aclocal_m4_deps) cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(am__aclocal_m4_deps): clean-noinstLIBRARIES: -test -z "$(noinst_LIBRARIES)" || rm -f $(noinst_LIBRARIES) @@ -296,14 +298,14 @@ distclean-compile: .c.o: @am__fastdepCC_TRUE@ $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $< -@am__fastdepCC_TRUE@ mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po +@am__fastdepCC_TRUE@ $(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po @AMDEP_TRUE@@am__fastdepCC_FALSE@ source='$<' object='$@' libtool=no @AMDEPBACKSLASH@ @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(COMPILE) -c $< .c.obj: @am__fastdepCC_TRUE@ $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ `$(CYGPATH_W) '$<'` -@am__fastdepCC_TRUE@ mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po +@am__fastdepCC_TRUE@ $(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po @AMDEP_TRUE@@am__fastdepCC_FALSE@ source='$<' object='$@' libtool=no @AMDEPBACKSLASH@ @AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ @am__fastdepCC_FALSE@ $(COMPILE) -c `$(CYGPATH_W) '$<'` @@ -313,14 +315,14 @@ ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES) unique=`for i in $$list; do \ if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ done | \ - $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \ + $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ END { if (nonempty) { for (i in files) print i; }; }'`; \ mkid -fID $$unique tags: TAGS TAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \ $(TAGS_FILES) $(LISP) - tags=; \ + set x; \ here=`pwd`; \ list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ unique=`for i in $$list; do \ @@ -328,29 +330,34 @@ TAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \ done | \ $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ END { if (nonempty) { for (i in files) print i; }; }'`; \ - if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \ + shift; \ + if test -z "$(ETAGS_ARGS)$$*$$unique"; then :; else \ test -n "$$unique" || unique=$$empty_fix; \ - $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ - $$tags $$unique; \ + if test $$# -gt 0; then \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + "$$@" $$unique; \ + else \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + $$unique; \ + fi; \ fi ctags: CTAGS CTAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \ $(TAGS_FILES) $(LISP) - tags=; \ list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ unique=`for i in $$list; do \ if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ done | \ $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ END { if (nonempty) { for (i in files) print i; }; }'`; \ - test -z "$(CTAGS_ARGS)$$tags$$unique" \ + test -z "$(CTAGS_ARGS)$$unique" \ || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \ - $$tags $$unique + $$unique GTAGS: here=`$(am__cd) $(top_builddir) && pwd` \ - && cd $(top_srcdir) \ - && gtags -i $(GTAGS_ARGS) $$here + && $(am__cd) $(top_srcdir) \ + && gtags -i $(GTAGS_ARGS) "$$here" distclean-tags: -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags @@ -371,13 +378,17 @@ distdir: $(DISTFILES) if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ if test -d $$d/$$file; then \ dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d "$(distdir)/$$file"; then \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ - cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \ + cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ fi; \ - cp -pR $$d/$$file $(distdir)$$dir || exit 1; \ + cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \ else \ - test -f $(distdir)/$$file \ - || cp -p $$d/$$file $(distdir)/$$file \ + test -f "$(distdir)/$$file" \ + || cp -p $$d/$$file "$(distdir)/$$file" \ || exit 1; \ fi; \ done @@ -405,6 +416,7 @@ clean-generic: distclean-generic: -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES) maintainer-clean-generic: @echo "This command is intended for maintainers to use" @@ -425,6 +437,8 @@ dvi-am: html: html-am +html-am: + info: info-am info-am: @@ -433,18 +447,28 @@ install-data-am: install-dvi: install-dvi-am +install-dvi-am: + install-exec-am: install-html: install-html-am +install-html-am: + install-info: install-info-am +install-info-am: + install-man: install-pdf: install-pdf-am +install-pdf-am: + install-ps: install-ps-am +install-ps-am: + installcheck-am: maintainer-clean: maintainer-clean-am @@ -481,6 +505,7 @@ uninstall-am: mostlyclean-generic pdf pdf-am ps ps-am tags uninstall \ uninstall-am + # Tell versions [3.59,3.63) of GNU make to not export all variables. # Otherwise a system limit (for SysV at least) may be exceeded. .NOEXPORT: diff --git a/imap/auth.c b/imap/auth.c index c61237d..6ac2925 100644 --- a/imap/auth.c +++ b/imap/auth.c @@ -43,7 +43,7 @@ static imap_auth_t imap_authenticators[] = { #endif { imap_auth_login, "login" }, - { NULL } + { NULL, NULL } }; /* imap_authenticate: Attempt to authenticate using either user-specified diff --git a/imap/browse.c b/imap/browse.c index 0262e2f..8b60bc7 100644 --- a/imap/browse.c +++ b/imap/browse.c @@ -72,11 +72,13 @@ int imap_browse (char* path, struct browser_state* state) if (mx.mbox && mx.mbox[0] != '\0') { int rc; + char *ptr; imap_fix_path (idata, mx.mbox, mbox, sizeof (mbox)); - imap_munge_mbox_name (buf, sizeof (buf), mbox); - imap_unquote_string(buf); /* As kludgy as it gets */ + ptr = safe_strdup (mbox); + imap_utf7_encode (&ptr); mbox[sizeof (mbox) - 1] = '\0'; - strncpy (mbox, buf, sizeof (mbox) - 1); + strncpy (mbox, ptr, sizeof (mbox) - 1); + FREE (&ptr); n = mutt_strlen (mbox); dprint (3, (debugfile, "imap_browse: mbox: %s\n", mbox)); diff --git a/imap/imap.c b/imap/imap.c index e5cb675..f08b4ea 100644 --- a/imap/imap.c +++ b/imap/imap.c @@ -2,21 +2,21 @@ * Copyright (C) 1996-8 Michael R. Elkins * Copyright (C) 1996-9 Brandon Long * Copyright (C) 1999-2009 Brendan Cully - * + * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. - * + * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. - * + * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. - */ + */ /* Support for IMAP4rev1, with the occasional nod to IMAP 4. */ @@ -120,7 +120,7 @@ int imap_create_mailbox (IMAP_DATA* idata, char* mailbox) imap_munge_mbox_name (mbox, sizeof (mbox), mailbox); snprintf (buf, sizeof (buf), "CREATE %s", mbox); - + if (imap_exec (idata, buf, 0) != 0) { mutt_error (_("CREATE failed: %s"), imap_cmd_trailer (idata)); @@ -174,7 +174,7 @@ int imap_delete_mailbox (CONTEXT* ctx, IMAP_MBOX mx) /* imap_logout_all: close all open connections. Quick and dirty until we can * make sure we've got all the context we need. */ -void imap_logout_all (void) +void imap_logout_all (void) { CONNECTION* conn; CONNECTION* tmp; @@ -190,7 +190,6 @@ void imap_logout_all (void) mutt_message (_("Closing connection to %s..."), conn->account.host); imap_logout ((IMAP_DATA**) (void*) &conn->data); mutt_clear_error (); - mutt_socket_close (conn); mutt_socket_free (conn); } @@ -209,14 +208,14 @@ int imap_read_literal (FILE* fp, IMAP_DATA* idata, long bytes, progress_t* pbar) int r = 0; dprint (2, (debugfile, "imap_read_literal: reading %ld bytes\n", bytes)); - + for (pos = 0; pos < bytes; pos++) { if (mutt_socket_readchar (idata->conn, &c) != 1) { dprint (1, (debugfile, "imap_read_literal: error during read, %ld bytes read\n", pos)); idata->status = IMAP_FATAL; - + return -1; } @@ -233,7 +232,7 @@ int imap_read_literal (FILE* fp, IMAP_DATA* idata, long bytes, progress_t* pbar) r = 0; #endif fputc (c, fp); - + if (pbar && !(pos % 1024)) mutt_progress_update (pbar, pos, -1); #ifdef DEBUG @@ -382,7 +381,7 @@ IMAP_DATA* imap_conn_find (const ACCOUNT* account, int flags) } else mutt_account_unsetpass (&idata->conn->account); - + FREE (&idata->capstr); } if (new && idata->state == IMAP_AUTHENTICATED) @@ -427,7 +426,7 @@ int imap_open_connection (IMAP_DATA* idata) mutt_bit_isset (idata->capabilities, STARTTLS))) { int rc; - + if (option(OPTSSLFORCETLS)) rc = M_YES; else if ((rc = query_quadoption (OPT_SSLSTARTTLS, @@ -460,7 +459,7 @@ int imap_open_connection (IMAP_DATA* idata) mutt_sleep (1); goto err_close_conn; } -#endif +#endif } else if (ascii_strncasecmp ("* PREAUTH", idata->buf, 9) == 0) { @@ -468,7 +467,7 @@ int imap_open_connection (IMAP_DATA* idata) if (imap_check_capabilities (idata) != 0) goto bail; FREE (&idata->capstr); - } + } else { imap_error ("imap_open_connection()", buf); @@ -488,8 +487,11 @@ int imap_open_connection (IMAP_DATA* idata) void imap_close_connection(IMAP_DATA* idata) { - mutt_socket_close (idata->conn); - idata->state = IMAP_DISCONNECTED; + if (idata->state != IMAP_DISCONNECTED) + { + mutt_socket_close (idata->conn); + idata->state = IMAP_DISCONNECTED; + } idata->seqno = idata->nextcmd = idata->lastcmd = idata->status = 0; memset (idata->cmds, 0, sizeof (IMAP_COMMAND) * idata->cmdslots); } @@ -561,7 +563,7 @@ int imap_open_mailbox (CONTEXT* ctx) int count = 0; IMAP_MBOX mx, pmx; int rc; - + if (imap_parse_path (ctx->path, &mx)) { mutt_error (_("%s is an invalid IMAP path"), ctx->path); @@ -600,7 +602,7 @@ int imap_open_mailbox (CONTEXT* ctx) mutt_message (_("Selecting %s..."), idata->mailbox); imap_munge_mbox_name (buf, sizeof(buf), idata->mailbox); - + /* pipeline ACL test */ if (mutt_bit_isset (idata->capabilities, ACL)) { @@ -638,7 +640,7 @@ int imap_open_mailbox (CONTEXT* ctx) do { char *pc; - + if ((rc = imap_cmd_step (idata)) != IMAP_CMD_CONTINUE) break; @@ -828,6 +830,7 @@ void imap_logout (IMAP_DATA** idata) while (imap_cmd_step (*idata) == IMAP_CMD_CONTINUE) ; + mutt_socket_close ((*idata)->conn); imap_free_idata (idata); } @@ -847,19 +850,19 @@ int imap_has_flag (LIST* flag_list, const char* flag) { if (!flag_list) return 0; - + flag_list = flag_list->next; while (flag_list) { if (!ascii_strncasecmp (flag_list->data, flag, strlen (flag_list->data))) return 1; - + if (!ascii_strncmp (flag_list->data, "\\*", strlen (flag_list->data))) return 1; - + flag_list = flag_list->next; } - + return 0; } @@ -876,7 +879,7 @@ static int imap_make_msg_set (IMAP_DATA* idata, BUFFER* buf, int flag, int started = 0; hdrs = idata->ctx->hdrs; - + for (n = *pos; n < idata->ctx->msgcount && buf->dptr - buf->data < IMAP_MAX_CMDLEN; n++) @@ -1006,7 +1009,7 @@ int imap_exec_msgset (IMAP_DATA* idata, const char* pre, const char* post, } } while (rc > 0); - + rc = count; out: @@ -1061,7 +1064,7 @@ int imap_sync_message (IMAP_DATA *idata, HEADER *hdr, BUFFER *cmd, mutt_buffer_addstr (cmd, uid); flags[0] = '\0'; - + imap_set_flag (idata, M_ACL_SEEN, hdr->read, "\\Seen ", flags, sizeof (flags)); imap_set_flag (idata, M_ACL_WRITE, hdr->old, @@ -1147,7 +1150,7 @@ static int sync_helper (IMAP_DATA* idata, int right, int flag, const char* name) /* update the IMAP server to reflect message changes done within mutt. * Arguments * ctx: the current context - * expunge: 0 or 1 - do expunge? + * expunge: 0 or 1 - do expunge? */ int imap_sync_mailbox (CONTEXT* ctx, int expunge, int* index_hint) { @@ -1158,7 +1161,7 @@ int imap_sync_mailbox (CONTEXT* ctx, int expunge, int* index_hint) int oldsort; int n; int rc; - + idata = (IMAP_DATA*) ctx->data; if (idata->state < IMAP_SELECTED) @@ -1167,7 +1170,7 @@ int imap_sync_mailbox (CONTEXT* ctx, int expunge, int* index_hint) return -1; } - /* This function is only called when the calling code expects the context + /* This function is only called when the calling code expects the context * to be changed. */ imap_allow_reopen (ctx); @@ -1175,7 +1178,7 @@ int imap_sync_mailbox (CONTEXT* ctx, int expunge, int* index_hint) return rc; /* if we are expunging anyway, we can do deleted messages very quickly... */ - if (expunge && mutt_bit_isset (idata->ctx->rights, M_ACL_DELETE)) + if (expunge && mutt_bit_isset (ctx->rights, M_ACL_DELETE)) { if ((rc = imap_exec_msgset (idata, "UID STORE", "+FLAGS.SILENT (\\Deleted)", M_DELETED, 1, 0)) < 0) @@ -1212,9 +1215,12 @@ int imap_sync_mailbox (CONTEXT* ctx, int expunge, int* index_hint) imap_hcache_del (idata, HEADER_DATA(h)->uid); #endif } - + if (h->active && h->changed) { +#if USE_HCACHE + imap_hcache_put (idata, h); +#endif /* if the message has been rethreaded or attachments have been deleted * we delete the message and reupload it. * This works better if we're expunging, of course. */ @@ -1288,7 +1294,7 @@ int imap_sync_mailbox (CONTEXT* ctx, int expunge, int* index_hint) /* We must send an EXPUNGE command if we're not closing. */ if (expunge && !(ctx->closing) && - mutt_bit_isset(idata->ctx->rights, M_ACL_DELETE)) + mutt_bit_isset(ctx->rights, M_ACL_DELETE)) { mutt_message _("Expunging messages from server..."); /* Set expunge bit so we don't get spurious reopened messages */ @@ -1410,7 +1416,7 @@ int imap_check_mailbox (CONTEXT *ctx, int *index_hint, int force) } } - if ((force || + if ((force || (idata->state != IMAP_IDLE && time(NULL) >= idata->lastread + Timeout)) && imap_exec (idata, "NOOP", 0) != 0) return -1; @@ -1447,7 +1453,7 @@ static int imap_get_mailbox (const char* path, IMAP_DATA** hidata, char* buf, si FREE (&mx.mbox); return -1; } - + imap_fix_path (*hidata, mx.mbox, buf, blen); if (!*buf) strfcpy (buf, "INBOX", blen); @@ -1477,7 +1483,7 @@ int imap_buffy_check (int force) if (mx_is_imap (mailbox->path)) mailbox->magic = M_IMAP; } - + if (mailbox->magic != M_IMAP) continue; @@ -1487,8 +1493,10 @@ int imap_buffy_check (int force) continue; /* Don't issue STATUS on the selected mailbox, it will be NOOPed or - * IDLEd elsewhere */ - if (!imap_mxcmp (name, idata->mailbox)) + * IDLEd elsewhere. + * idata->mailbox may be NULL for connections other than the current + * mailbox's, and shouldn't expand to INBOX in that case. #3216. */ + if (idata->mailbox && !imap_mxcmp (name, idata->mailbox)) continue; if (!mutt_bit_isset (idata->capabilities, IMAP4REV1) && @@ -1580,7 +1588,7 @@ int imap_status (char* path, int queue) queued = 0; if ((status = imap_mboxcache_get (idata, mbox, 0))) return status->messages; - + return 0; } @@ -1595,7 +1603,7 @@ IMAP_STATUS* imap_mboxcache_get (IMAP_DATA* idata, const char* mbox, int create) unsigned int *uidvalidity = NULL; unsigned int *uidnext = NULL; #endif - + for (cur = idata->mboxcache; cur; cur = cur->next) { status = (IMAP_STATUS*)cur->data; @@ -1680,11 +1688,11 @@ static int do_search (const pattern_t* search, int allpats) if (pat->child && do_search (pat->child, 1)) rc++; } - + if (!allpats) break; } - + return rc; } @@ -1716,13 +1724,13 @@ static int imap_compile_search (const pattern_t* pat, BUFFER* buf) if (pat->op == M_OR && clauses > 1) mutt_buffer_addstr (buf, "OR "); clauses--; - + if (imap_compile_search (clause, buf) < 0) return -1; if (clauses) mutt_buffer_addch (buf, ' '); - + } clause = clause->next; } @@ -1750,7 +1758,7 @@ static int imap_compile_search (const pattern_t* pat, BUFFER* buf) imap_quote_string (term, sizeof (term), pat->p.str); mutt_buffer_addstr (buf, term); mutt_buffer_addch (buf, ' '); - + /* and field */ *delim = ':'; delim++; @@ -1820,7 +1828,7 @@ int imap_subscribe (char *path, int subscribe) } if (!(idata = imap_conn_find (&(mx.account), 0))) goto fail; - + conn = idata->conn; imap_fix_path (idata, mx.mbox, buf, sizeof (buf)); @@ -1838,7 +1846,7 @@ int imap_subscribe (char *path, int subscribe) dprint (1, (debugfile, "Error adding subscribed mailbox: %s\n", errstr)); FREE (&token.data); } - + if (subscribe) mutt_message (_("Subscribing to %s..."), buf); else @@ -1869,7 +1877,7 @@ static int longest_common_prefix (char *dest, const char* src, int start, size_t dlen) { int pos = start; - + while (pos < dlen && dest[pos] && dest[pos] == src[pos]) pos++; dest[pos] = '\0'; @@ -1886,7 +1894,7 @@ imap_complete_hosts (char *dest, size_t len) CONNECTION* conn; int rc = -1; int matchlen; - + matchlen = mutt_strlen (dest); for (mailbox = Incoming; mailbox; mailbox = mailbox->next) { @@ -1901,7 +1909,7 @@ imap_complete_hosts (char *dest, size_t len) longest_common_prefix (dest, mailbox->path, matchlen, len); } } - + for (conn = mutt_socket_head (); conn; conn = conn->next) { ciss_url_t url; @@ -2017,6 +2025,6 @@ int imap_complete(char* dest, size_t dlen, char* path) { FREE (&mx.mbox); return 0; } - + return -1; } diff --git a/imap/imap_private.h b/imap/imap_private.h index 9a861aa..618d8c5 100644 --- a/imap/imap_private.h +++ b/imap/imap_private.h @@ -272,7 +272,7 @@ int imap_continue (const char* msg, const char* resp); void imap_error (const char* where, const char* msg); IMAP_DATA* imap_new_idata (void); void imap_free_idata (IMAP_DATA** idata); -char* imap_fix_path (IMAP_DATA* idata, char* mailbox, char* path, +char* imap_fix_path (IMAP_DATA* idata, const char* mailbox, char* path, size_t plen); void imap_cachepath(IMAP_DATA* idata, const char* mailbox, char* dest, size_t dlen); diff --git a/imap/message.c b/imap/message.c index 5bcd6fb..3d64c0d 100644 --- a/imap/message.c +++ b/imap/message.c @@ -1,22 +1,22 @@ /* * Copyright (C) 1996-9 Brandon Long * Copyright (C) 1999-2009 Brendan Cully - * + * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. - * + * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. - * + * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. * - */ + */ /* message parsing/updating functions */ @@ -85,12 +85,12 @@ int imap_read_headers (IMAP_DATA* idata, int msgbegin, int msgend) if (mutt_bit_isset (idata->capabilities,IMAP4REV1)) { - snprintf (hdrreq, sizeof (hdrreq), "BODY.PEEK[HEADER.FIELDS (%s%s%s)]", - want_headers, ImapHeaders ? " " : "", ImapHeaders ? ImapHeaders : ""); - } + snprintf (hdrreq, sizeof (hdrreq), "BODY.PEEK[HEADER.FIELDS (%s%s%s)]", + want_headers, ImapHeaders ? " " : "", ImapHeaders ? ImapHeaders : ""); + } else if (mutt_bit_isset (idata->capabilities,IMAP4)) { - snprintf (hdrreq, sizeof (hdrreq), "RFC822.HEADER.LINES (%s%s%s)", + snprintf (hdrreq, sizeof (hdrreq), "RFC822.HEADER.LINES (%s%s%s)", want_headers, ImapHeaders ? " " : "", ImapHeaders ? ImapHeaders : ""); } else @@ -142,14 +142,14 @@ int imap_read_headers (IMAP_DATA* idata, int msgbegin, int msgend) snprintf (buf, sizeof (buf), "UID FETCH 1:%u (UID FLAGS)", uidnext - 1); - + imap_cmd_start (idata, buf); - + rc = IMAP_CMD_CONTINUE; for (msgno = msgbegin; rc == IMAP_CMD_CONTINUE; msgno++) { mutt_progress_update (&progress, msgno + 1, -1); - + memset (&h, 0, sizeof (h)); h.data = safe_calloc (1, sizeof (IMAP_HEADER_DATA)); do @@ -183,13 +183,13 @@ int imap_read_headers (IMAP_DATA* idata, int msgbegin, int msgend) mfhrc = -1; continue; } - + idx = h.sid - 1; ctx->hdrs[idx] = imap_hcache_get (idata, h.data->uid); if (ctx->hdrs[idx]) { ctx->hdrs[idx]->index = idx; - /* messages which have not been expunged are ACTIVE (borrowed from mh + /* messages which have not been expunged are ACTIVE (borrowed from mh * folders) */ ctx->hdrs[idx]->active = 1; ctx->hdrs[idx]->read = h.data->read; @@ -220,7 +220,7 @@ int imap_read_headers (IMAP_DATA* idata, int msgbegin, int msgend) if (h.data) imap_free_header_data ((void**) (void*) &h.data); imap_hcache_close (idata); - fclose (fp); + safe_fclose (&fp); return -1; } } @@ -287,11 +287,18 @@ int imap_read_headers (IMAP_DATA* idata, int msgbegin, int msgend) mfhrc = -1; continue; } + /* May receive FLAGS updates in a separate untagged response (#2935) */ + if (idx < ctx->msgcount) + { + dprint (2, (debugfile, "imap_read_headers: message %d is not new\n", + h.sid)); + continue; + } ctx->hdrs[idx] = mutt_new_header (); ctx->hdrs[idx]->index = h.sid - 1; - /* messages which have not been expunged are ACTIVE (borrowed from mh + /* messages which have not been expunged are ACTIVE (borrowed from mh * folders) */ ctx->hdrs[idx]->active = 1; ctx->hdrs[idx]->read = h.data->read; @@ -331,7 +338,7 @@ int imap_read_headers (IMAP_DATA* idata, int msgbegin, int msgend) #if USE_HCACHE imap_hcache_close (idata); #endif - fclose (fp); + safe_fclose (&fp); return -1; } @@ -364,7 +371,7 @@ int imap_read_headers (IMAP_DATA* idata, int msgbegin, int msgend) imap_hcache_close (idata); #endif /* USE_HCACHE */ - fclose(fp); + safe_fclose (&fp); if (ctx->msgcount > oldmsgcount) { @@ -443,7 +450,7 @@ int imap_fetch_message (MESSAGE *msg, CONTEXT *ctx, int msgno) * also try to update it. HACK until all this code can be moved into the * command handler */ h->active = 0; - + snprintf (buf, sizeof (buf), "UID FETCH %u %s", HEADER_DATA(h)->uid, (mutt_bit_isset (idata->capabilities, IMAP4REV1) ? (option (OPTIMAPPEEK) ? "BODY.PEEK[]" : "BODY[]") : @@ -516,7 +523,7 @@ int imap_fetch_message (MESSAGE *msg, CONTEXT *ctx, int msgno) mutt_perror (cache->path); goto bail; } - + if (rc != IMAP_CMD_OK) goto bail; @@ -586,7 +593,7 @@ int imap_append_message (CONTEXT *ctx, MESSAGE *msg) FILE *fp; char buf[LONG_STRING]; char mbox[LONG_STRING]; - char mailbox[LONG_STRING]; + char mailbox[LONG_STRING]; size_t len; progress_t progressbar; size_t sent; @@ -602,7 +609,7 @@ int imap_append_message (CONTEXT *ctx, MESSAGE *msg) imap_fix_path (idata, mx.mbox, mailbox, sizeof (mailbox)); if (!*mailbox) strfcpy (mailbox, "INBOX", sizeof (mailbox)); - + if ((fp = fopen (msg->path, "r")) == NULL) { mutt_perror (msg->path); @@ -654,7 +661,7 @@ int imap_append_message (CONTEXT *ctx, MESSAGE *msg) pc = imap_next_word (pc); mutt_error ("%s", pc); mutt_sleep (1); - fclose (fp); + safe_fclose (&fp); goto fail; } @@ -672,12 +679,12 @@ int imap_append_message (CONTEXT *ctx, MESSAGE *msg) mutt_progress_update (&progressbar, sent, -1); } } - + if (len) flush_buffer(buf, &len, idata->conn); mutt_socket_write (idata->conn, "\r\n"); - fclose (fp); + safe_fclose (&fp); do rc = imap_cmd_step (idata); @@ -745,7 +752,7 @@ int imap_copy_messages (CONTEXT* ctx, HEADER* h, char* dest, int delete) dprint (3, (debugfile, "imap_copy_messages: Message contains attachments to be deleted\n")); return 1; } - + imap_fix_path (idata, mx.mbox, mbox, sizeof (mbox)); if (!*mbox) strfcpy (mbox, "INBOX", sizeof (mbox)); @@ -778,7 +785,7 @@ int imap_copy_messages (CONTEXT* ctx, HEADER* h, char* dest, int delete) if (rc < 0) { dprint (1, (debugfile, "imap_copy_messages: could not sync\n")); - goto fail; + goto out; } } } @@ -787,12 +794,13 @@ int imap_copy_messages (CONTEXT* ctx, HEADER* h, char* dest, int delete) if (!rc) { dprint (1, (debugfile, "imap_copy_messages: No messages tagged\n")); - goto fail; + rc = -1; + goto out; } else if (rc < 0) { dprint (1, (debugfile, "could not queue copy\n")); - goto fail; + goto out; } else mutt_message (_("Copying %d messages to %s..."), rc, mbox); @@ -808,13 +816,13 @@ int imap_copy_messages (CONTEXT* ctx, HEADER* h, char* dest, int delete) if (rc < 0) { dprint (1, (debugfile, "imap_copy_messages: could not sync\n")); - goto fail; + goto out; } - } + } if ((rc = imap_exec (idata, cmd.data, IMAP_CMD_QUEUE)) < 0) { dprint (1, (debugfile, "could not queue copy\n")); - goto fail; + goto out; } } @@ -835,7 +843,7 @@ int imap_copy_messages (CONTEXT* ctx, HEADER* h, char* dest, int delete) if (option (OPTCONFIRMCREATE) && mutt_yesorno (prompt, 1) < 1) { mutt_clear_error (); - break; + goto out; } if (imap_create_mailbox (idata, mbox) < 0) break; @@ -847,7 +855,7 @@ int imap_copy_messages (CONTEXT* ctx, HEADER* h, char* dest, int delete) if (rc != 0) { imap_error ("imap_copy_messages", idata->buf); - goto fail; + goto out; } /* cleanup */ @@ -871,20 +879,16 @@ int imap_copy_messages (CONTEXT* ctx, HEADER* h, char* dest, int delete) } } - if (cmd.data) - FREE (&cmd.data); - if (sync_cmd.data) - FREE (&sync_cmd.data); - FREE (&mx.mbox); - return 0; + rc = 0; - fail: + out: if (cmd.data) FREE (&cmd.data); if (sync_cmd.data) FREE (&sync_cmd.data); FREE (&mx.mbox); - return -1; + + return rc < 0 ? -1 : rc; } static body_cache_t *msg_cache_open (IMAP_DATA *idata) @@ -1026,14 +1030,14 @@ char* imap_set_flags (IMAP_DATA* idata, HEADER* h, char* s) dprint (2, (debugfile, "imap_fetch_message: parsing FLAGS\n")); if ((s = msg_parse_flags (&newh, s)) == NULL) return NULL; - + /* YAUH (yet another ugly hack): temporarily set context to * read-write even if it's read-only, so *server* updates of * flags can be processed by mutt_set_flag. ctx->changed must * be restored afterwards */ readonly = ctx->readonly; ctx->readonly = 0; - + mutt_set_flag (ctx, h, M_NEW, !(hd->read || hd->old)); mutt_set_flag (ctx, h, M_OLD, hd->old); mutt_set_flag (ctx, h, M_READ, hd->read); @@ -1067,7 +1071,7 @@ static int msg_fetch_header (CONTEXT* ctx, IMAP_HEADER* h, char* buf, FILE* fp) if (buf[0] != '*') return rc; - + /* skip to message number */ buf = imap_next_word (buf); h->sid = atoi (buf); @@ -1086,7 +1090,7 @@ static int msg_fetch_header (CONTEXT* ctx, IMAP_HEADER* h, char* buf, FILE* fp) * read header lines and call it again. Silly. */ if ((rc = msg_parse_fetch (h, buf)) != -2 || !fp) return rc; - + if (imap_get_literal_count (buf, &bytes) == 0) { imap_read_literal (fp, idata, bytes, NULL); @@ -1097,13 +1101,13 @@ static int msg_fetch_header (CONTEXT* ctx, IMAP_HEADER* h, char* buf, FILE* fp) * interchangeably at any time. */ if (imap_cmd_step (idata) != IMAP_CMD_CONTINUE) return rc; - + if (msg_parse_fetch (h, idata->buf) == -1) return rc; } rc = 0; /* success */ - + /* subtract headers from message size - unfortunately only the subset of * headers we've requested. */ h->content_length -= bytes; diff --git a/imap/util.c b/imap/util.c index 45e5673..5fa71b9 100644 --- a/imap/util.c +++ b/imap/util.c @@ -1,22 +1,22 @@ /* * Copyright (C) 1996-8 Michael R. Elkins * Copyright (C) 1996-9 Brandon Long - * Copyright (C) 1999-2008 Brendan Cully - * + * Copyright (C) 1999-2009 Brendan Cully + * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. - * + * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. - * + * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. - */ + */ /* general IMAP utility functions */ @@ -54,6 +54,7 @@ int imap_expand_path (char* path, size_t len) { IMAP_MBOX mx; + IMAP_DATA* idata; ciss_url_t url; char fixedpath[LONG_STRING]; int rc; @@ -61,8 +62,9 @@ int imap_expand_path (char* path, size_t len) if (imap_parse_path (path, &mx) < 0) return -1; + idata = imap_conn_find (&mx.account, M_IMAP_CONN_NONEW); mutt_account_tourl (&mx.account, &url); - imap_fix_path(NULL, mx.mbox, fixedpath, sizeof (fixedpath)); + imap_fix_path (idata, mx.mbox, fixedpath, sizeof (fixedpath)); url.path = fixedpath; rc = url_ciss_tostring (&url, path, len, U_DECODE_PASSWD); @@ -224,7 +226,7 @@ int imap_parse_path (const char* path, IMAP_MBOX* mx) else /* walk past closing '}' */ mx->mbox = safe_strdup (c+1); - + if ((c = strrchr (tmp, '@'))) { *c = '\0'; @@ -232,14 +234,14 @@ int imap_parse_path (const char* path, IMAP_MBOX* mx) strfcpy (tmp, c+1, sizeof (tmp)); mx->account.flags |= M_ACCT_USER; } - + if ((n = sscanf (tmp, "%127[^:/]%127s", mx->account.host, tmp)) < 1) { dprint (1, (debugfile, "imap_parse_path: NULL host in %s\n", path)); FREE (&mx->mbox); return -1; } - + if (n > 1) { if (sscanf (tmp, ":%hu%127s", &(mx->account.port), tmp) >= 1) mx->account.flags |= M_ACCT_PORT; @@ -266,10 +268,28 @@ int imap_parse_path (const char* path, IMAP_MBOX* mx) /* silly helper for mailbox name string comparisons, because of INBOX */ int imap_mxcmp (const char* mx1, const char* mx2) { + char* b1; + char* b2; + int rc; + + if (!mx1 || !*mx1) + mx1 = "INBOX"; + if (!mx2 || !*mx2) + mx2 = "INBOX"; if (!ascii_strcasecmp (mx1, "INBOX") && !ascii_strcasecmp (mx2, "INBOX")) return 0; - - return mutt_strcmp (mx1, mx2); + + b1 = safe_malloc (strlen (mx1) + 1); + b2 = safe_malloc (strlen (mx2) + 1); + + imap_fix_path (NULL, mx1, b1, strlen (mx1) + 1); + imap_fix_path (NULL, mx2, b2, strlen (mx2) + 1); + + rc = mutt_strcmp (b1, b2); + FREE (&b1); + FREE (&b2); + + return rc; } /* imap_pretty_mailbox: called by mutt_pretty_mailbox to make IMAP paths @@ -389,23 +409,24 @@ void imap_free_idata (IMAP_DATA** idata) * are not required to do this. * Moreover, IMAP servers may dislike the path ending with the delimiter. */ -char *imap_fix_path (IMAP_DATA *idata, char *mailbox, char *path, +char *imap_fix_path (IMAP_DATA *idata, const char *mailbox, char *path, size_t plen) { int i = 0; - char delim; - + char delim = '\0'; + if (idata) delim = idata->delim; - else if (ImapDelimChars && ImapDelimChars[0]) - delim = ImapDelimChars[0]; - else - delim = '/'; while (mailbox && *mailbox && i < plen - 1) { - if (strchr(ImapDelimChars, *mailbox) || *mailbox == delim) + if ((ImapDelimChars && strchr(ImapDelimChars, *mailbox)) + || *mailbox == delim) { + /* use connection delimiter if known. Otherwise use user delimiter */ + if (!idata) + delim = *mailbox; + while (*mailbox && (strchr(ImapDelimChars, *mailbox) || *mailbox == delim)) mailbox++; @@ -514,7 +535,7 @@ time_t imap_parse_date (char *s) struct tm t; time_t tz; - t.tm_mday = (s[0] == ' '? s[1] - '0' : (s[0] - '0') * 10 + (s[1] - '0')); + t.tm_mday = (s[0] == ' '? s[1] - '0' : (s[0] - '0') * 10 + (s[1] - '0')); s += 2; if (*s != '-') return 0; @@ -582,7 +603,7 @@ void imap_quote_string (char *dest, size_t dlen, const char *src) *pt++ = '"'; /* save room for trailing quote-char */ dlen -= 2; - + for (; *s && dlen; s++) { if (strchr (quote, *s)) @@ -662,7 +683,7 @@ void imap_unmunge_mbox_name (char *s) imap_utf7_decode (&buf); strncpy (s, buf, strlen (s)); } - + FREE (&buf); } @@ -688,10 +709,10 @@ int imap_wordcasecmp(const char *a, const char *b) return ascii_strcasecmp(a, tmp); } -/* +/* * Imap keepalive: poll the current folder to keep the * connection alive. - * + * */ static RETSIGTYPE alrm_handler (int sig) @@ -740,7 +761,7 @@ int imap_wait_keepalive (pid_t pid) int rc; short imap_passive = option (OPTIMAPPASSIVE); - + set_option (OPTIMAPPASSIVE); set_option (OPTKEEPQUIET); @@ -765,7 +786,7 @@ int imap_wait_keepalive (pid_t pid) } alarm (0); /* cancel a possibly pending alarm */ - + sigaction (SIGALRM, &oldalrm, NULL); sigprocmask (SIG_SETMASK, &oldmask, NULL); diff --git a/init.c b/init.c index 9b98d77..d6980c0 100644 --- a/init.c +++ b/init.c @@ -253,8 +253,8 @@ int mutt_extract_token (BUFFER *dest, BUFFER *tok, int flags) /* read line */ memset (&expn, 0, sizeof (expn)); - expn.data = mutt_read_line (NULL, &expn.dsize, fp, &line); - fclose (fp); + expn.data = mutt_read_line (NULL, &expn.dsize, fp, &line, 0); + safe_fclose (&fp); mutt_wait_filter (pid); /* if we got output, make a new string consiting of the shell ouptput @@ -2069,8 +2069,8 @@ static int parse_set (BUFFER *tmp, BUFFER *s, unsigned long data, BUFFER *err) else if (DTYPE(MuttVars[idx].type) == DT_NUM) { short *ptr = (short *) MuttVars[idx].data; - int val; - char *t; + short val; + int rc; if (query || *s->dptr != '=') { @@ -2088,16 +2088,17 @@ static int parse_set (BUFFER *tmp, BUFFER *s, unsigned long data, BUFFER *err) s->dptr++; mutt_extract_token (tmp, s, 0); - val = strtol (tmp->data, &t, 0); + rc = mutt_atos (tmp->data, (short *) &val); - if (!*tmp->data || *t || (short) val != val) + if (rc < 0 || !*tmp->data) { - snprintf (err->data, err->dsize, _("%s: invalid value"), tmp->data); + snprintf (err->data, err->dsize, _("%s: invalid value (%s)"), tmp->data, + rc == -1 ? _("format error") : _("number overflow")); r = -1; break; } else - *ptr = (short) val; + *ptr = val; /* these ones need a sanity check */ if (mutt_strcmp (MuttVars[idx].option, "history") == 0) @@ -2268,7 +2269,7 @@ static int source_rc (const char *rcfile, BUFFER *err) } memset (&token, 0, sizeof (token)); - while ((linebuf = mutt_read_line (linebuf, &buflen, f, &line)) != NULL) + while ((linebuf = mutt_read_line (linebuf, &buflen, f, &line, M_CONT)) != NULL) { conv=ConfigCharset && (*ConfigCharset) && Charset; if (conv) @@ -2299,7 +2300,7 @@ static int source_rc (const char *rcfile, BUFFER *err) } FREE (&token.data); FREE (&linebuf); - fclose (f); + safe_fclose (&f); if (pid != -1) mutt_wait_filter (pid); if (rc) @@ -2885,8 +2886,8 @@ void mutt_init (int skip_sys_rc, LIST *commands) err.data = error; err.dsize = sizeof (error); - Groups = hash_create (1031); - ReverseAlias = hash_create (1031); + Groups = hash_create (1031, 0); + ReverseAlias = hash_create (1031, 1); mutt_menu_init (); diff --git a/init.h b/init.h index f9c5bba..98b26ec 100644 --- a/init.h +++ b/init.h @@ -1,21 +1,21 @@ /* * Copyright (C) 1996-2002,2007 Michael R. Elkins * Copyright (C) 2004 g10 Code GmbH - * + * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. - * + * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. - * + * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. - */ + */ #ifdef _MAKEDOC # include "config.h" @@ -197,7 +197,10 @@ struct option_t MuttVars[] = { /* ** .pp ** This variable is a colon-separated list of character encoding - ** schemes for text file attachments. + ** schemes for text file attachments. Mutt uses this setting to guess + ** which encoding files being attached are encoded in to convert them to + ** a proper character set given in $$send_charset. + ** .pp ** If \fIunset\fP, the value of $$charset will be used instead. ** For example, the following configuration would work for Japanese ** text handling: @@ -260,6 +263,14 @@ struct option_t MuttVars[] = { ** in a reply. For a full listing of defined \fCprintf(3)\fP-like sequences see ** the section on $$index_format. */ + { "auto_tag", DT_BOOL, R_NONE, OPTAUTOTAG, 0 }, + /* + ** .pp + ** When \fIset\fP, functions in the \fIindex\fP menu which affect a message + ** will be applied to all tagged messages (if there are any). When + ** unset, you must first use the \fC\fP function (bound to ``;'' + ** by default) to make the next function apply to all tagged messages. + */ { "autoedit", DT_BOOL, R_NONE, OPTAUTOEDIT, 0 }, /* ** .pp @@ -269,15 +280,12 @@ struct option_t MuttVars[] = { ** message. The send-menu may still be accessed once you have finished ** editing the body of your message. ** .pp - ** Also see $$fast_reply. - */ - { "auto_tag", DT_BOOL, R_NONE, OPTAUTOTAG, 0 }, - /* ** .pp - ** When \fIset\fP, functions in the \fIindex\fP menu which affect a message - ** will be applied to all tagged messages (if there are any). When - ** unset, you must first use the \fC\fP function (bound to ``;'' - ** by default) to make the next function apply to all tagged messages. + ** \fBNote:\fP when this option is \fIset\fP, you cannot use send-hooks that depend + ** on the recipients when composing a new (non-reply) message, as the initial + ** list of recipients is empty. + ** .pp + ** Also see $$fast_reply. */ { "beep", DT_BOOL, R_NONE, OPTBEEP, 1 }, /* @@ -314,21 +322,27 @@ struct option_t MuttVars[] = { ** follow these menus. The option is \fIunset\fP by default because many ** visual terminals don't permit making the cursor invisible. */ - { "check_mbox_size", DT_BOOL, R_NONE, OPTCHECKMBOXSIZE, 0 }, +#if defined(USE_SSL) + { "certificate_file", DT_PATH, R_NONE, UL &SslCertFile, UL "~/.mutt_certificates" }, /* ** .pp - ** When this variable is \fIset\fP, mutt will use file size attribute instead of - ** access time when checking for new mail in mbox and mmdf folders. + ** This variable specifies the file where the certificates you trust + ** are saved. When an unknown certificate is encountered, you are asked + ** if you accept it or not. If you accept it, the certificate can also + ** be saved in this file and further connections are automatically + ** accepted. ** .pp - ** This variable is \fIunset\fP by default and should only be enabled when - ** new mail detection for these folder types is unreliable or doesn't work. + ** You can also manually add CA certificates in this file. Any server + ** certificate that is signed with one of these CA certificates is + ** also automatically accepted. ** .pp - ** Note that enabling this variable should happen before any ``$mailboxes'' - ** directives occur in configuration files regarding mbox or mmdf folders - ** because mutt needs to determine the initial new mail status of such a - ** mailbox by performing a fast mailbox scan when it is defined. - ** Afterwards the new mail status is tracked by file size changes. + ** Example: + ** .ts + ** set certificate_file=~/.mutt/certificates + ** .te + ** */ +#endif { "charset", DT_STR, R_NONE, UL &Charset, UL 0 }, /* ** .pp @@ -341,6 +355,21 @@ struct option_t MuttVars[] = { ** \fBNote:\fP It should only be set in case Mutt isn't abled to determine the ** character set used correctly. */ + { "check_mbox_size", DT_BOOL, R_NONE, OPTCHECKMBOXSIZE, 0 }, + /* + ** .pp + ** When this variable is \fIset\fP, mutt will use file size attribute instead of + ** access time when checking for new mail in mbox and mmdf folders. + ** .pp + ** This variable is \fIunset\fP by default and should only be enabled when + ** new mail detection for these folder types is unreliable or doesn't work. + ** .pp + ** Note that enabling this variable should happen before any ``$mailboxes'' + ** directives occur in configuration files regarding mbox or mmdf folders + ** because mutt needs to determine the initial new mail status of such a + ** mailbox by performing a fast mailbox scan when it is defined. + ** Afterwards the new mail status is tracked by file size changes. + */ { "check_new", DT_BOOL, R_NONE, OPTCHECKNEW, 1 }, /* ** .pp @@ -360,12 +389,6 @@ struct option_t MuttVars[] = { ** When \fIunset\fP, Mutt will not collapse a thread if it contains any ** unread messages. */ - { "uncollapse_jump", DT_BOOL, R_NONE, OPTUNCOLLAPSEJUMP, 0 }, - /* - ** .pp - ** When \fIset\fP, Mutt will jump to the next unread message, if any, - ** when the current thread is \fIun\fPcollapsed. - */ { "compose_format", DT_STR, R_BOTH, UL &ComposeFormat, UL "-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-" }, /* ** .pp @@ -427,21 +450,18 @@ struct option_t MuttVars[] = { ** will be saved for later references. Also see $$record, ** $$save_name, $$force_name and ``$fcc-hook''. */ - { "crypt_use_gpgme", DT_BOOL, R_NONE, OPTCRYPTUSEGPGME, 0 }, - /* - ** .pp - ** This variable controls the use of the GPGME-enabled crypto backends. - ** If it is \fIset\fP and Mutt was built with gpgme support, the gpgme code for - ** S/MIME and PGP will be used instead of the classic code. Note that - ** you need to set this option in .muttrc; it won't have any effect when - ** used interactively. - */ - { "crypt_use_pka", DT_BOOL, R_NONE, OPTCRYPTUSEPKA, 0 }, + { "pgp_autoencrypt", DT_SYN, R_NONE, UL "crypt_autoencrypt", 0 }, + { "crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, 0 }, /* ** .pp - ** Controls whether mutt uses PKA - ** (see http://www.g10code.de/docs/pka-intro.de.pdf) during signature - ** verification (only supported by the GPGME backend). + ** Setting this variable will cause Mutt to always attempt to PGP + ** encrypt outgoing messages. This is probably only useful in + ** connection to the ``$send-hook'' command. It can be overridden + ** by use of the pgp menu, when encryption is not required or + ** signing is requested as well. If $$smime_is_default is \fIset\fP, + ** then OpenSSL is used instead to create S/MIME messages and + ** settings can be overridden by use of the smime menu instead. + ** (Crypto only) */ { "crypt_autopgp", DT_BOOL, R_NONE, OPTCRYPTAUTOPGP, 1 }, /* @@ -451,6 +471,18 @@ struct option_t MuttVars[] = { ** $$crypt_replyencrypt, ** $$crypt_autosign, $$crypt_replysign and $$smime_is_default. */ + { "pgp_autosign", DT_SYN, R_NONE, UL "crypt_autosign", 0 }, + { "crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, 0 }, + /* + ** .pp + ** Setting this variable will cause Mutt to always attempt to + ** cryptographically sign outgoing messages. This can be overridden + ** by use of the pgp menu, when signing is not required or + ** encryption is requested as well. If $$smime_is_default is \fIset\fP, + ** then OpenSSL is used instead to create S/MIME messages and settings can + ** be overridden by use of the smime menu instead of the pgp menu. + ** (Crypto only) + */ { "crypt_autosmime", DT_BOOL, R_NONE, OPTCRYPTAUTOSMIME, 1 }, /* ** .pp @@ -459,6 +491,71 @@ struct option_t MuttVars[] = { ** $$crypt_replyencrypt, ** $$crypt_autosign, $$crypt_replysign and $$smime_is_default. */ + { "pgp_replyencrypt", DT_SYN, R_NONE, UL "crypt_replyencrypt", 1 }, + { "crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, 1 }, + /* + ** .pp + ** If \fIset\fP, automatically PGP or OpenSSL encrypt replies to messages which are + ** encrypted. + ** (Crypto only) + */ + { "pgp_replysign", DT_SYN, R_NONE, UL "crypt_replysign", 0 }, + { "crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, 0 }, + /* + ** .pp + ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages which are + ** signed. + ** .pp + ** \fBNote:\fP this does not work on messages that are encrypted + ** \fIand\fP signed! + ** (Crypto only) + */ + { "pgp_replysignencrypted", DT_SYN, R_NONE, UL "crypt_replysignencrypted", 0}, + { "crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED, 0 }, + /* + ** .pp + ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages + ** which are encrypted. This makes sense in combination with + ** $$crypt_replyencrypt, because it allows you to sign all + ** messages which are automatically encrypted. This works around + ** the problem noted in $$crypt_replysign, that mutt is not able + ** to find out whether an encrypted message is also signed. + ** (Crypto only) + */ + { "crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, 1 }, + /* + ** .pp + ** If \fIset\fP, mutt will include a time stamp in the lines surrounding + ** PGP or S/MIME output, so spoofing such lines is more difficult. + ** If you are using colors to mark these lines, and rely on these, + ** you may \fIunset\fP this setting. + ** (Crypto only) + */ + { "crypt_use_gpgme", DT_BOOL, R_NONE, OPTCRYPTUSEGPGME, 0 }, + /* + ** .pp + ** This variable controls the use of the GPGME-enabled crypto backends. + ** If it is \fIset\fP and Mutt was built with gpgme support, the gpgme code for + ** S/MIME and PGP will be used instead of the classic code. Note that + ** you need to set this option in .muttrc; it won't have any effect when + ** used interactively. + */ + { "crypt_use_pka", DT_BOOL, R_NONE, OPTCRYPTUSEPKA, 0 }, + /* + ** .pp + ** Controls whether mutt uses PKA + ** (see http://www.g10code.de/docs/pka-intro.de.pdf) during signature + ** verification (only supported by the GPGME backend). + */ + { "pgp_verify_sig", DT_SYN, R_NONE, UL "crypt_verify_sig", 0}, + { "crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, M_YES }, + /* + ** .pp + ** If \fI``yes''\fP, always attempt to verify PGP or S/MIME signatures. + ** If \fI``ask-*''\fP, ask whether or not to verify the signature. + ** If \Fi``no''\fP, never attempt to verify cryptographic signatures. + ** (Crypto only) + */ { "date_format", DT_STR, R_BOTH, UL &DateFmt, UL "!%a, %b %d, %Y at %I:%M:%S%p %Z" }, /* ** .pp @@ -600,6 +697,14 @@ struct option_t MuttVars[] = { ** agents tend to do with messages (in order to prevent tools from ** misinterpreting the line as a mbox message separator). */ +#if defined(USE_SSL_OPENSSL) + { "entropy_file", DT_PATH, R_NONE, UL &SslEntropyFile, 0 }, + /* + ** .pp + ** The file which includes random data that is used to initialize SSL + ** library functions. + */ +#endif { "envelope_from_address", DT_ADDR, R_NONE, UL &EnvFrom, 0 }, /* ** .pp @@ -621,7 +726,7 @@ struct option_t MuttVars[] = { ** \fBNote:\fP this variable has no effect when the $$autoedit ** variable is \fIset\fP. */ - { "fcc_attach", DT_BOOL, R_NONE, OPTFCCATTACH, 1 }, + { "fcc_attach", DT_QUAD, R_NONE, OPT_FCCATTACH, M_YES }, /* ** .pp ** This variable controls whether or not attachments on outgoing messages @@ -654,7 +759,9 @@ struct option_t MuttVars[] = { ** .dl ** .dt %C .dd current file number ** .dt %d .dd date/time folder was last modified - ** .dt %f .dd filename + ** .dt %f .dd filename (``/'' is appended to directory names, + ** ``@'' to symbolic links and ``*'' to executable + ** files) ** .dt %F .dd file permissions ** .dt %g .dd group name (or numeric gid, if missing) ** .dt %l .dd number of hard links @@ -710,6 +817,18 @@ struct option_t MuttVars[] = { { "forw_decode", DT_SYN, R_NONE, UL "forward_decode", 0 }, /* */ + { "forward_decrypt", DT_BOOL, R_NONE, OPTFORWDECRYPT, 1 }, + /* + ** .pp + ** Controls the handling of encrypted messages when forwarding a message. + ** When \fIset\fP, the outer layer of encryption is stripped off. This + ** variable is only used if $$mime_forward is \fIset\fP and + ** $$mime_forward_decode is \fIunset\fP. + ** (PGP only) + */ + { "forw_decrypt", DT_SYN, R_NONE, UL "forward_decrypt", 0 }, + /* + */ { "forward_edit", DT_QUAD, R_NONE, OPT_FORWEDIT, M_YES }, /* ** .pp @@ -754,7 +873,7 @@ struct option_t MuttVars[] = { ** If the GECOS field contains a string like ``lastname, firstname'' then you ** should set it to ``\fC.*\fP''. ** .pp - ** This can be useful if you see the following behavior: you address a e-mail + ** This can be useful if you see the following behavior: you address an e-mail ** to user ID ``stevef'' whose full name is ``Steve Franklin''. If mutt expands ** ``stevef'' to ``"Franklin" stevef@foo.bar'' then you should set the $$gecos_mask to ** a regular expression that will match the whole name so mutt will expand @@ -778,6 +897,42 @@ struct option_t MuttVars[] = { ** of the message you are replying to into the edit buffer. ** The $$weed setting applies. */ +#ifdef USE_HCACHE + { "header_cache", DT_PATH, R_NONE, UL &HeaderCache, 0 }, + /* + ** .pp + ** This variable points to the header cache database. + ** If pointing to a directory Mutt will contain a header cache + ** database file per folder, if pointing to a file that file will + ** be a single global header cache. By default it is \fIunset\fP so no header + ** caching will be used. + ** .pp + ** Header caching can greatly improve speed when opening POP, IMAP + ** MH or Maildir folders, see ``$caching'' for details. + */ +#if defined(HAVE_QDBM) || defined(HAVE_TC) + { "header_cache_compress", DT_BOOL, R_NONE, OPTHCACHECOMPRESS, 1 }, + /* + ** .pp + ** When mutt is compiled with qdbm or tokyocabinet as header cache backend, + ** this option determines whether the database will be compressed. + ** Compression results in database files roughly being one fifth + ** of the usual diskspace, but the uncompression can result in a + ** slower opening of cached folder(s) which in general is still + ** much faster than opening non header cached folders. + */ +#endif /* HAVE_QDBM */ +#if defined(HAVE_GDBM) || defined(HAVE_DB4) + { "header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, UL "16384" }, + /* + ** .pp + ** When mutt is compiled with either gdbm or bdb4 as the header cache backend, + ** this option changes the database page size. Too large or too small + ** values can waste space, memory, or CPU time. The default should be more + ** or less optimal for most use cases. + */ +#endif /* HAVE_GDBM || HAVE_DB4 */ +#endif /* USE_HCACHE */ { "help", DT_BOOL, R_BOTH, OPTHELP, 1 }, /* ** .pp @@ -843,6 +998,17 @@ struct option_t MuttVars[] = { ** .pp ** The file in which Mutt will save its history. */ + { "honor_disposition", DT_BOOL, R_NONE, OPTHONORDISP, 0 }, + /* + ** .pp + ** When \fIset\fP, Mutt will not display attachments with a + ** disposition of ``attachment'' inline even if it could + ** render the part to plain text. These MIME parts can only + ** be viewed from the attachment menu. + ** .pp + ** If \fIunset\fP, Mutt will render all MIME parts it can + ** properly transform to plain text. + */ { "honor_followup_to", DT_QUAD, R_NONE, OPT_MFUPTO, M_YES }, /* ** .pp @@ -975,7 +1141,7 @@ struct option_t MuttVars[] = { /* ** .pp ** Specifies the password for your IMAP account. If \fIunset\fP, Mutt will - ** prompt you for your password when you invoke the \fC$\fP function + ** prompt you for your password when you invoke the \fC\fP function ** or try to open an IMAP folder. ** .pp ** \fBWarning\fP: you should only use this option when you are on a @@ -1056,12 +1222,11 @@ struct option_t MuttVars[] = { ** message to which you are replying. You are strongly encouraged not to ** change this value, as it tends to agitate the more fanatical netizens. ** .pp + ** The value of this option is ignored if $$text_flowed is set, too because + ** the quoting mechanism is strictly defined for format=flowed. + ** .pp ** This option is a format string, please see the description of ** $$index_format for supported \fCprintf(3)\fP-style sequences. - ** .pp - ** Because for \fCformat=lowed\fP style messages the quoting mechanism - ** is strictly defined, this setting is ignored if $$text_flowed is - ** \fIset\fP. */ { "indent_str", DT_SYN, R_NONE, UL "indent_string", 0 }, /* @@ -1186,18 +1351,6 @@ struct option_t MuttVars[] = { ** DOING!\fP */ #ifdef USE_HCACHE - { "header_cache", DT_PATH, R_NONE, UL &HeaderCache, 0 }, - /* - ** .pp - ** This variable points to the header cache database. - ** If pointing to a directory Mutt will contain a header cache - ** database file per folder, if pointing to a file that file will - ** be a single global header cache. By default it is \fIunset\fP so no header - ** caching will be used. - ** .pp - ** Header caching can greatly improve speed when opening POP, IMAP - ** MH or Maildir folders, see ``$caching'' for details. - */ { "maildir_header_cache_verify", DT_BOOL, R_NONE, OPTHCACHEVERIFY, 1 }, /* ** .pp @@ -1206,38 +1359,16 @@ struct option_t MuttVars[] = { ** message every time the folder is opened (which can be very slow for NFS ** folders). */ -#if defined(HAVE_GDBM) || defined(HAVE_DB4) - { "header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, UL "16384" }, +#endif + { "maildir_trash", DT_BOOL, R_NONE, OPTMAILDIRTRASH, 0 }, /* ** .pp - ** When mutt is compiled with either gdbm or bdb4 as the header cache backend, - ** this option changes the database page size. Too large or too small - ** values can waste space, memory, or CPU time. The default should be more - ** or less optimal for most use cases. + ** If \fIset\fP, messages marked as deleted will be saved with the maildir + ** trashed flag instead of unlinked. \fBNote:\fP this only applies + ** to maildir-style mailboxes. Setting it will have no effect on other + ** mailbox types. */ -#endif /* HAVE_GDBM || HAVE_DB4 */ -#if defined(HAVE_QDBM) || defined(HAVE_TC) - { "header_cache_compress", DT_BOOL, R_NONE, OPTHCACHECOMPRESS, 1 }, - /* - ** .pp - ** When mutt is compiled with qdbm or tokyocabinet as header cache backend, - ** this option determines whether the database will be compressed. - ** Compression results in database files roughly being one fifth - ** of the usual diskspace, but the uncompression can result in a - ** slower opening of cached folder(s) which in general is still - ** much faster than opening non header cached folders. - */ -#endif /* HAVE_QDBM */ -#endif /* USE_HCACHE */ - { "maildir_trash", DT_BOOL, R_NONE, OPTMAILDIRTRASH, 0 }, - /* - ** .pp - ** If \fIset\fP, messages marked as deleted will be saved with the maildir - ** trashed flag instead of unlinked. \fBNote:\fP this only applies - ** to maildir-style mailboxes. Setting it will have no effect on other - ** mailbox types. - */ - { "mark_old", DT_BOOL, R_BOTH, OPTMARKOLD, 1 }, + { "mark_old", DT_BOOL, R_BOTH, OPTMARKOLD, 1 }, /* ** .pp ** Controls whether or not mutt marks \fInew\fP \fBunread\fP @@ -1273,13 +1404,8 @@ struct option_t MuttVars[] = { /* ** .pp ** The default mailbox type used when creating new folders. May be any of - ** ``mbox'', ``MMDF'', ``MH'' and ``Maildir''. - */ - { "metoo", DT_BOOL, R_NONE, OPTMETOO, 0 }, - /* - ** .pp - ** If \fIunset\fP, Mutt will remove your address (see the ``$alternates'' - ** command) from the list of recipients when replying to a message. + ** ``mbox'', ``MMDF'', ``MH'' and ``Maildir''. This is overriden by the + ** \fC-m\fP command-line option. */ { "menu_context", DT_NUM, R_NONE, UL &MenuContext, 0 }, /* @@ -1302,6 +1428,39 @@ struct option_t MuttVars[] = { ** is cleared and the next or previous page of the menu is displayed ** (useful for slow links to avoid many redraws). */ +#if defined(USE_IMAP) || defined(USE_POP) + { "message_cache_clean", DT_BOOL, R_NONE, OPTMESSAGECACHECLEAN, 0 }, + /* + ** .pp + ** If \fIset\fP, mutt will clean out obsolete entries from the message cache when + ** the mailbox is synchronized. You probably only want to set it + ** every once in a while, since it can be a little slow + ** (especially for large folders). + */ + { "message_cachedir", DT_PATH, R_NONE, UL &MessageCachedir, 0 }, + /* + ** .pp + ** Set this to a directory and mutt will cache copies of messages from + ** your IMAP and POP servers here. You are free to remove entries at any + ** time. + ** .pp + ** When setting this variable to a directory, mutt needs to fetch every + ** remote message only once and can perform regular expression searches + ** as fast as for local folders. + ** .pp + ** Also see the $$message_cache_clean variable. + */ +#endif + { "message_format", DT_STR, R_NONE, UL &MsgFmt, UL "%s" }, + /* + ** .pp + ** This is the string displayed in the ``attachment'' menu for + ** attachments of type \fCmessage/rfc822\fP. For a full listing of defined + ** \fCprintf(3)\fP-like sequences see the section on $$index_format. + */ + { "msg_format", DT_SYN, R_NONE, UL "message_format", 0 }, + /* + */ { "meta_key", DT_BOOL, R_NONE, OPTMETAKEY, 0 }, /* ** .pp @@ -1313,6 +1472,12 @@ struct option_t MuttVars[] = { ** high bit from \fC0xf8\fP is \fC0x78\fP, which is the ASCII character ** ``x''. */ + { "metoo", DT_BOOL, R_NONE, OPTMETOO, 0 }, + /* + ** .pp + ** If \fIunset\fP, Mutt will remove your address (see the ``$alternates'' + ** command) from the list of recipients when replying to a message. + */ { "mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, 0 }, /* ** .pp @@ -1398,39 +1563,6 @@ struct option_t MuttVars[] = { ** from your spool mailbox to your $$mbox mailbox, or as a result of ** a ``$mbox-hook'' command. */ -#if defined(USE_IMAP) || defined(USE_POP) - { "message_cachedir", DT_PATH, R_NONE, UL &MessageCachedir, 0 }, - /* - ** .pp - ** Set this to a directory and mutt will cache copies of messages from - ** your IMAP and POP servers here. You are free to remove entries at any - ** time. - ** .pp - ** When setting this variable to a directory, mutt needs to fetch every - ** remote message only once and can perform regular expression searches - ** as fast as for local folders. - ** .pp - ** Also see the $$message_cache_clean variable. - */ - { "message_cache_clean", DT_BOOL, R_NONE, OPTMESSAGECACHECLEAN, 0 }, - /* - ** .pp - ** If \fIset\fP, mutt will clean out obsolete entries from the message cache when - ** the mailbox is synchronized. You probably only want to set it - ** every once in a while, since it can be a little slow - ** (especially for large folders). - */ -#endif - { "message_format", DT_STR, R_NONE, UL &MsgFmt, UL "%s" }, - /* - ** .pp - ** This is the string displayed in the ``attachment'' menu for - ** attachments of type \fCmessage/rfc822\fP. For a full listing of defined - ** \fCprintf(3)\fP-like sequences see the section on $$index_format. - */ - { "msg_format", DT_SYN, R_NONE, UL "message_format", 0 }, - /* - */ { "narrow_tree", DT_BOOL, R_TREE|R_INDEX, OPTNARROWTREE, 0 }, /* ** .pp @@ -1468,6 +1600,10 @@ struct option_t MuttVars[] = { ** when displaying the next or previous page in the internal pager. By ** default, Mutt will display the line after the last one on the screen ** at the top of the next page (0 lines of context). + ** .pp + ** This variable also specifies the amount of context given for search + ** results. If positive, this many lines will be given before a match, + ** if 0, the match will be top-aligned. */ { "pager_format", DT_STR, R_PAGER, UL &PagerFmt, UL "-%Z- %C/%m: %-20.20n %s%* -- (%P)" }, /* @@ -1499,119 +1635,104 @@ struct option_t MuttVars[] = { ** when you are at the end of a message and invoke the \fC\fP ** function. */ - { "pgp_autosign", DT_SYN, R_NONE, UL "crypt_autosign", 0 }, - { "crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, 0 }, + { "pgp_auto_decode", DT_BOOL, R_NONE, OPTPGPAUTODEC, 0 }, /* ** .pp - ** Setting this variable will cause Mutt to always attempt to - ** cryptographically sign outgoing messages. This can be overridden - ** by use of the pgp menu, when signing is not required or - ** encryption is requested as well. If $$smime_is_default is \fIset\fP, - ** then OpenSSL is used instead to create S/MIME messages and settings can - ** be overridden by use of the smime menu instead of the pgp menu. - ** (Crypto only) + ** If \fIset\fP, mutt will automatically attempt to decrypt traditional PGP + ** messages whenever the user performs an operation which ordinarily would + ** result in the contents of the message being operated on. For example, + ** if the user displays a pgp-traditional message which has not been manually + ** checked with the \fC$\fP function, mutt will automatically + ** check the message for traditional pgp. */ - { "pgp_autoencrypt", DT_SYN, R_NONE, UL "crypt_autoencrypt", 0 }, - { "crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, 0 }, + { "pgp_create_traditional", DT_SYN, R_NONE, UL "pgp_autoinline", 0 }, + { "pgp_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, 0 }, /* ** .pp - ** Setting this variable will cause Mutt to always attempt to PGP - ** encrypt outgoing messages. This is probably only useful in - ** connection to the ``$send-hook'' command. It can be overridden - ** by use of the pgp menu, when encryption is not required or - ** signing is requested as well. If $$smime_is_default is \fIset\fP, - ** then OpenSSL is used instead to create S/MIME messages and - ** settings can be overridden by use of the smime menu instead. - ** (Crypto only) - */ - { "pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, 1}, - /* + ** This option controls whether Mutt generates old-style inline + ** (traditional) PGP encrypted or signed messages under certain + ** circumstances. This can be overridden by use of the pgp menu, + ** when inline is not required. ** .pp - ** Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, - ** the principal key will inherit the subkeys' capabilities. \fIUnset\fP this - ** if you want to play interesting key selection games. + ** Note that Mutt might automatically use PGP/MIME for messages + ** which consist of more than a single MIME part. Mutt can be + ** configured to ask before sending PGP/MIME messages when inline + ** (traditional) would not work. + ** .pp + ** Also see the $$pgp_mime_auto variable. + ** .pp + ** Also note that using the old-style PGP message format is \fBstrongly\fP + ** \fBdeprecated\fP. ** (PGP only) */ - { "pgp_replyencrypt", DT_SYN, R_NONE, UL "crypt_replyencrypt", 1 }, - { "crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, 1 }, + { "pgp_check_exit", DT_BOOL, R_NONE, OPTPGPCHECKEXIT, 1 }, /* ** .pp - ** If \fIset\fP, automatically PGP or OpenSSL encrypt replies to messages which are - ** encrypted. - ** (Crypto only) + ** If \fIset\fP, mutt will check the exit code of the PGP subprocess when + ** signing or encrypting. A non-zero exit code means that the + ** subprocess failed. + ** (PGP only) */ - { "pgp_replysign", DT_SYN, R_NONE, UL "crypt_replysign", 0 }, - { "crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, 0 }, + { "pgp_clearsign_command", DT_STR, R_NONE, UL &PgpClearSignCommand, 0 }, /* ** .pp - ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages which are - ** signed. + ** This format is used to create an old-style ``clearsigned'' PGP + ** message. Note that the use of this format is \fBstrongly\fP + ** \fBdeprecated\fP. ** .pp - ** \fBNote:\fP this does not work on messages that are encrypted - ** \fIand\fP signed! - ** (Crypto only) + ** This is a format string, see the $$pgp_decode_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (PGP only) */ - { "pgp_replysignencrypted", DT_SYN, R_NONE, UL "crypt_replysignencrypted", 0}, - { "crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED, 0 }, + { "pgp_decode_command", DT_STR, R_NONE, UL &PgpDecodeCommand, 0}, /* ** .pp - ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages - ** which are encrypted. This makes sense in combination with - ** $$crypt_replyencrypt, because it allows you to sign all - ** messages which are automatically encrypted. This works around - ** the problem noted in $$crypt_replysign, that mutt is not able - ** to find out whether an encrypted message is also signed. - ** (Crypto only) - */ - { "crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, 1 }, - /* + ** This format strings specifies a command which is used to decode + ** application/pgp attachments. ** .pp - ** If \fIset\fP, mutt will include a time stamp in the lines surrounding - ** PGP or S/MIME output, so spoofing such lines is more difficult. - ** If you are using colors to mark these lines, and rely on these, - ** you may \fIunset\fP this setting. - ** (Crypto only) - */ - { "pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, 0}, - /* + ** The PGP command formats have their own set of \fCprintf(3)\fP-like sequences: + ** .dl + ** .dt %p .dd Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty + ** string otherwise. Note: This may be used with a %? construct. + ** .dt %f .dd Expands to the name of a file containing a message. + ** .dt %s .dd Expands to the name of a file containing the signature part + ** . of a \fCmultipart/signed\fP attachment when verifying it. + ** .dt %a .dd The value of $$pgp_sign_as. + ** .dt %r .dd One or more key IDs. + ** .de ** .pp - ** If \fIset\fP, mutt will use a possibly-running \fCgpg-agent(1)\fP process. + ** For examples on how to configure these formats for the various versions + ** of PGP which are floating around, see the pgp and gpg sample configuration files in + ** the \fCsamples/\fP subdirectory which has been installed on your system + ** alongside the documentation. ** (PGP only) */ - { "pgp_verify_sig", DT_SYN, R_NONE, UL "crypt_verify_sig", 0}, - { "crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, M_YES }, + { "pgp_decrypt_command", DT_STR, R_NONE, UL &PgpDecryptCommand, 0}, /* ** .pp - ** If \fI``yes''\fP, always attempt to verify PGP or S/MIME signatures. - ** If \fI``ask-*''\fP, ask whether or not to verify the signature. - ** If \Fi``no''\fP, never attempt to verify cryptographic signatures. - ** (Crypto only) - */ - { "smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, 0}, - /* + ** This command is used to decrypt a PGP encrypted message. ** .pp - ** The default behaviour of mutt is to use PGP on all auto-sign/encryption - ** operations. To override and to use OpenSSL instead this must be \fIset\fP. - ** However, this has no effect while replying, since mutt will automatically - ** select the same application that was used to sign/encrypt the original - ** message. (Note that this variable can be overridden by unsetting $$crypt_autosmime.) - ** (S/MIME only) + ** This is a format string, see the $$pgp_decode_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (PGP only) */ - { "smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, 1 }, + { "pgp_encrypt_only_command", DT_STR, R_NONE, UL &PgpEncryptOnlyCommand, 0}, /* ** .pp - ** This flag controls whether you want to be asked to enter a label - ** for a certificate about to be added to the database or not. It is - ** \fIset\fP by default. - ** (S/MIME only) + ** This command is used to encrypt a body part without signing it. + ** .pp + ** This is a format string, see the $$pgp_decode_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (PGP only) */ - { "smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY, 1 }, + { "pgp_encrypt_sign_command", DT_STR, R_NONE, UL &PgpEncryptSignCommand, 0}, /* ** .pp - ** If \fIset\fP (default) this tells mutt to use the default key for decryption. Otherwise, - ** if managing multiple certificate-key-pairs, mutt will try to use the mailbox-address - ** to determine the key to use. It will ask you to supply a key, if it can't find one. - ** (S/MIME only) + ** This command is used to both sign and encrypt a body part. + ** .pp + ** This is a format string, see the $$pgp_decode_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (PGP only) */ { "pgp_entry_format", DT_STR, R_NONE, UL &PgpEntryFormat, UL "%4n %t%f %4l/0x%k %-4a %2c %u" }, /* @@ -1633,55 +1754,95 @@ struct option_t MuttVars[] = { ** .pp ** (PGP only) */ - { "pgp_good_sign", DT_RX, R_NONE, UL &PgpGoodSign, 0 }, + { "pgp_export_command", DT_STR, R_NONE, UL &PgpExportCommand, 0}, /* ** .pp - ** If you assign a text to this variable, then a PGP signature is only - ** considered verified if the output from $$pgp_verify_command contains - ** the text. Use this variable if the exit code from the command is 0 - ** even for bad signatures. - ** (PGP only) - */ - { "pgp_check_exit", DT_BOOL, R_NONE, OPTPGPCHECKEXIT, 1 }, + ** This command is used to export a public key from the user's + ** key ring. + ** .pp + ** This is a format string, see the $$pgp_decode_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (PGP only) + */ + { "pgp_getkeys_command", DT_STR, R_NONE, UL &PgpGetkeysCommand, 0}, /* ** .pp - ** If \fIset\fP, mutt will check the exit code of the PGP subprocess when - ** signing or encrypting. A non-zero exit code means that the - ** subprocess failed. + ** This command is invoked whenever mutt will need public key information. + ** Of the sequences supported by $$pgp_decode_command, %r is the only + ** \fCprintf(3)\fP-like sequence used with this format. ** (PGP only) */ - { "pgp_long_ids", DT_BOOL, R_NONE, OPTPGPLONGIDS, 0 }, + { "pgp_good_sign", DT_RX, R_NONE, UL &PgpGoodSign, 0 }, /* ** .pp - ** If \fIset\fP, use 64 bit PGP key IDs, if \fIunset\fP use the normal 32 bit key IDs. + ** If you assign a text to this variable, then a PGP signature is only + ** considered verified if the output from $$pgp_verify_command contains + ** the text. Use this variable if the exit code from the command is 0 + ** even for bad signatures. ** (PGP only) */ - { "pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, 0 }, + { "pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, 1}, /* ** .pp - ** If \fIset\fP, signed and encrypted messages will consist of nested - ** \fCmultipart/signed\fP and \fCmultipart/encrypted\fP body parts. + ** Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, + ** the principal key will inherit the subkeys' capabilities. \fIUnset\fP this + ** if you want to play interesting key selection games. + ** (PGP only) + */ + { "pgp_import_command", DT_STR, R_NONE, UL &PgpImportCommand, 0}, + /* ** .pp - ** This is useful for applications like encrypted and signed mailing - ** lists, where the outer layer (\fCmultipart/encrypted\fP) can be easily - ** removed, while the inner \fCmultipart/signed\fP part is retained. + ** This command is used to import a key from a message into + ** the user's public key ring. + ** .pp + ** This is a format string, see the $$pgp_decode_command command for + ** possible \fCprintf(3)\fP-like sequences. ** (PGP only) */ - { "pgp_create_traditional", DT_SYN, R_NONE, UL "pgp_autoinline", 0 }, - { "pgp_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, 0 }, + { "pgp_list_pubring_command", DT_STR, R_NONE, UL &PgpListPubringCommand, 0}, /* ** .pp - ** This option controls whether Mutt generates old-style inline - ** (traditional) PGP encrypted or signed messages under certain - ** circumstances. This can be overridden by use of the pgp menu, - ** when inline is not required. + ** This command is used to list the public key ring's contents. The + ** output format must be analogous to the one used by + ** .ts + ** gpg --list-keys --with-colons. + ** .te ** .pp - ** Note that Mutt might automatically use PGP/MIME for messages - ** which consist of more than a single MIME part. Mutt can be - ** configured to ask before sending PGP/MIME messages when inline - ** (traditional) would not work. + ** This format is also generated by the \fCpgpring\fP utility which comes + ** with mutt. ** .pp - ** Also see the $$pgp_mime_auto variable. + ** This is a format string, see the $$pgp_decode_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (PGP only) + */ + { "pgp_list_secring_command", DT_STR, R_NONE, UL &PgpListSecringCommand, 0}, + /* + ** .pp + ** This command is used to list the secret key ring's contents. The + ** output format must be analogous to the one used by: + ** .ts + ** gpg --list-keys --with-colons. + ** .te + ** .pp + ** This format is also generated by the \fCpgpring\fP utility which comes + ** with mutt. + ** .pp + ** This is a format string, see the $$pgp_decode_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (PGP only) + */ + { "pgp_long_ids", DT_BOOL, R_NONE, OPTPGPLONGIDS, 0 }, + /* + ** .pp + ** If \fIset\fP, use 64 bit PGP key IDs, if \fIunset\fP use the normal 32 bit key IDs. + ** (PGP only) + */ + { "pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGPMIMEAUTO, M_ASKYES }, + /* + ** .pp + ** This option controls whether Mutt will prompt you for + ** automatically sending a (signed/encrypted) message using + ** PGP/MIME when inline (traditional) fails (for any reason). ** .pp ** Also note that using the old-style PGP message format is \fBstrongly\fP ** \fBdeprecated\fP. @@ -1711,6 +1872,17 @@ struct option_t MuttVars[] = { ** (PGP only) ** */ + { "pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, 0 }, + /* + ** .pp + ** If \fIset\fP, signed and encrypted messages will consist of nested + ** \fCmultipart/signed\fP and \fCmultipart/encrypted\fP body parts. + ** .pp + ** This is useful for applications like encrypted and signed mailing + ** lists, where the outer layer (\fCmultipart/encrypted\fP) can be easily + ** removed, while the inner \fCmultipart/signed\fP part is retained. + ** (PGP only) + */ { "pgp_show_unusable", DT_BOOL, R_NONE, OPTPGPSHOWUNUSABLE, 1 }, /* ** .pp @@ -1727,20 +1899,14 @@ struct option_t MuttVars[] = { ** keyid form to specify your key (e.g. \fC0x00112233\fP). ** (PGP only) */ - { "pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, 1 }, + { "pgp_sign_command", DT_STR, R_NONE, UL &PgpSignCommand, 0}, /* ** .pp - ** If \fIset\fP, Mutt will automatically encode PGP/MIME signed messages as - ** quoted-printable. Please note that unsetting this variable may - ** lead to problems with non-verifyable PGP signatures, so only change - ** this if you know what you are doing. - ** (PGP only) - */ - { "pgp_timeout", DT_NUM, R_NONE, UL &PgpTimeout, 300 }, - /* + ** This command is used to create the detached PGP signature for a + ** \fCmultipart/signed\fP PGP/MIME body part. ** .pp - ** The number of seconds after which a cached passphrase will expire if - ** not used. + ** This is a format string, see the $$pgp_decode_command command for + ** possible \fCprintf(3)\fP-like sequences. ** (PGP only) */ { "pgp_sort_keys", DT_SORT|DT_SORT_KEYS, R_NONE, UL &PgpSortKeys, SORT_ADDRESS }, @@ -1759,59 +1925,26 @@ struct option_t MuttVars[] = { ** ``reverse-''. ** (PGP only) */ - { "pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGPMIMEAUTO, M_ASKYES }, + { "pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, 1 }, /* ** .pp - ** This option controls whether Mutt will prompt you for - ** automatically sending a (signed/encrypted) message using - ** PGP/MIME when inline (traditional) fails (for any reason). - ** .pp - ** Also note that using the old-style PGP message format is \fBstrongly\fP - ** \fBdeprecated\fP. + ** If \fIset\fP, Mutt will automatically encode PGP/MIME signed messages as + ** quoted-printable. Please note that unsetting this variable may + ** lead to problems with non-verifyable PGP signatures, so only change + ** this if you know what you are doing. ** (PGP only) */ - { "pgp_auto_decode", DT_BOOL, R_NONE, OPTPGPAUTODEC, 0 }, - /* - ** .pp - ** If \fIset\fP, mutt will automatically attempt to decrypt traditional PGP - ** messages whenever the user performs an operation which ordinarily would - ** result in the contents of the message being operated on. For example, - ** if the user displays a pgp-traditional message which has not been manually - ** checked with the \fC$\fP function, mutt will automatically - ** check the message for traditional pgp. - */ - - /* XXX Default values! */ - - { "pgp_decode_command", DT_STR, R_NONE, UL &PgpDecodeCommand, 0}, + { "pgp_timeout", DT_NUM, R_NONE, UL &PgpTimeout, 300 }, /* ** .pp - ** This format strings specifies a command which is used to decode - ** application/pgp attachments. - ** .pp - ** The PGP command formats have their own set of \fCprintf(3)\fP-like sequences: - ** .dl - ** .dt %p .dd Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty - ** string otherwise. Note: This may be used with a %? construct. - ** .dt %f .dd Expands to the name of a file containing a message. - ** .dt %s .dd Expands to the name of a file containing the signature part - ** . of a \fCmultipart/signed\fP attachment when verifying it. - ** .dt %a .dd The value of $$pgp_sign_as. - ** .dt %r .dd One or more key IDs. - ** .de - ** .pp - ** For examples on how to configure these formats for the various versions - ** of PGP which are floating around, see the pgp and gpg sample configuration files in - ** the \fCsamples/\fP subdirectory which has been installed on your system - ** alongside the documentation. + ** The number of seconds after which a cached passphrase will expire if + ** not used. ** (PGP only) */ - { "pgp_getkeys_command", DT_STR, R_NONE, UL &PgpGetkeysCommand, 0}, + { "pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, 0}, /* ** .pp - ** This command is invoked whenever mutt will need public key information. - ** Of the sequences supported by $$pgp_decode_command, %r is the only - ** \fCprintf(3)\fP-like sequence used with this format. + ** If \fIset\fP, mutt will use a possibly-running \fCgpg-agent(1)\fP process. ** (PGP only) */ { "pgp_verify_command", DT_STR, R_NONE, UL &PgpVerifyCommand, 0}, @@ -1823,410 +1956,15 @@ struct option_t MuttVars[] = { ** possible \fCprintf(3)\fP-like sequences. ** (PGP only) */ - { "pgp_decrypt_command", DT_STR, R_NONE, UL &PgpDecryptCommand, 0}, - /* - ** .pp - ** This command is used to decrypt a PGP encrypted message. - ** .pp - ** This is a format string, see the $$pgp_decode_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (PGP only) - */ - { "pgp_clearsign_command", DT_STR, R_NONE, UL &PgpClearSignCommand, 0 }, - /* - ** .pp - ** This format is used to create a old-style ``clearsigned'' PGP - ** message. Note that the use of this format is \fBstrongly\fP - ** \fBdeprecated\fP. - ** .pp - ** This is a format string, see the $$pgp_decode_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (PGP only) - */ - { "pgp_sign_command", DT_STR, R_NONE, UL &PgpSignCommand, 0}, - /* - ** .pp - ** This command is used to create the detached PGP signature for a - ** \fCmultipart/signed\fP PGP/MIME body part. - ** .pp - ** This is a format string, see the $$pgp_decode_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (PGP only) - */ - { "pgp_encrypt_sign_command", DT_STR, R_NONE, UL &PgpEncryptSignCommand, 0}, - /* - ** .pp - ** This command is used to both sign and encrypt a body part. - ** .pp - ** This is a format string, see the $$pgp_decode_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (PGP only) - */ - { "pgp_encrypt_only_command", DT_STR, R_NONE, UL &PgpEncryptOnlyCommand, 0}, - /* - ** .pp - ** This command is used to encrypt a body part without signing it. - ** .pp - ** This is a format string, see the $$pgp_decode_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (PGP only) - */ - { "pgp_import_command", DT_STR, R_NONE, UL &PgpImportCommand, 0}, - /* - ** .pp - ** This command is used to import a key from a message into - ** the user's public key ring. - ** .pp - ** This is a format string, see the $$pgp_decode_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (PGP only) - */ - { "pgp_export_command", DT_STR, R_NONE, UL &PgpExportCommand, 0}, - /* - ** .pp - ** This command is used to export a public key from the user's - ** key ring. - ** .pp - ** This is a format string, see the $$pgp_decode_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (PGP only) - */ { "pgp_verify_key_command", DT_STR, R_NONE, UL &PgpVerifyKeyCommand, 0}, /* ** .pp ** This command is used to verify key information from the key selection - ** menu. - ** .pp - ** This is a format string, see the $$pgp_decode_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (PGP only) - */ - { "pgp_list_secring_command", DT_STR, R_NONE, UL &PgpListSecringCommand, 0}, - /* - ** .pp - ** This command is used to list the secret key ring's contents. The - ** output format must be analogous to the one used by: - ** .ts - ** gpg --list-keys --with-colons. - ** .te - ** .pp - ** This format is also generated by the \fCpgpring\fP utility which comes - ** with mutt. - ** .pp - ** This is a format string, see the $$pgp_decode_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (PGP only) - */ - { "pgp_list_pubring_command", DT_STR, R_NONE, UL &PgpListPubringCommand, 0}, - /* - ** .pp - ** This command is used to list the public key ring's contents. The - ** output format must be analogous to the one used by - ** .ts - ** gpg --list-keys --with-colons. - ** .te - ** .pp - ** This format is also generated by the \fCpgpring\fP utility which comes - ** with mutt. - ** .pp - ** This is a format string, see the $$pgp_decode_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (PGP only) - */ - { "forward_decrypt", DT_BOOL, R_NONE, OPTFORWDECRYPT, 1 }, - /* - ** .pp - ** Controls the handling of encrypted messages when forwarding a message. - ** When \fIset\fP, the outer layer of encryption is stripped off. This - ** variable is only used if $$mime_forward is \fIset\fP and - ** $$mime_forward_decode is \fIunset\fP. - ** (PGP only) - */ - { "forw_decrypt", DT_SYN, R_NONE, UL "forward_decrypt", 0 }, - /* - */ - { "smime_timeout", DT_NUM, R_NONE, UL &SmimeTimeout, 300 }, - /* - ** .pp - ** The number of seconds after which a cached passphrase will expire if - ** not used. - ** (S/MIME only) - */ - { "smime_encrypt_with", DT_STR, R_NONE, UL &SmimeCryptAlg, 0 }, - /* - ** .pp - ** This sets the algorithm that should be used for encryption. - ** Valid choices are ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``rc2-128''. - ** If \fIunset\fP, ``3des'' (TripleDES) is used. - ** (S/MIME only) - */ - { "smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, 0 }, - /* - ** .pp - ** Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle - ** storage and retrieval of keys/certs by itself. This is very basic right now, - ** and stores keys and certificates in two different directories, both - ** named as the hash-value retrieved from OpenSSL. There is an index file - ** which contains mailbox-address keyid pair, and which can be manually - ** edited. This option points to the location of the private keys. - ** (S/MIME only) - */ - { "smime_ca_location", DT_PATH, R_NONE, UL &SmimeCALocation, 0 }, - /* - ** .pp - ** This variable contains the name of either a directory, or a file which - ** contains trusted certificates for use with OpenSSL. - ** (S/MIME only) - */ - { "smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, 0 }, - /* - ** .pp - ** Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle - ** storage and retrieval of keys by itself. This is very basic right - ** now, and keys and certificates are stored in two different - ** directories, both named as the hash-value retrieved from - ** OpenSSL. There is an index file which contains mailbox-address - ** keyid pairs, and which can be manually edited. This option points to - ** the location of the certificates. - ** (S/MIME only) - */ - { "smime_decrypt_command", DT_STR, R_NONE, UL &SmimeDecryptCommand, 0}, - /* - ** .pp - ** This format string specifies a command which is used to decrypt - ** \fCapplication/x-pkcs7-mime\fP attachments. - ** .pp - ** The OpenSSL command formats have their own set of \fCprintf(3)\fP-like sequences - ** similar to PGP's: - ** .dl - ** .dt %f .dd Expands to the name of a file containing a message. - ** .dt %s .dd Expands to the name of a file containing the signature part - ** . of a \fCmultipart/signed\fP attachment when verifying it. - ** .dt %k .dd The key-pair specified with $$smime_default_key - ** .dt %c .dd One or more certificate IDs. - ** .dt %a .dd The algorithm used for encryption. - ** .dt %C .dd CA location: Depending on whether $$smime_ca_location - ** . points to a directory or file, this expands to - ** . ``-CApath $$smime_ca_location'' or ``-CAfile $$smime_ca_location''. - ** .de - ** .pp - ** For examples on how to configure these formats, see the \fCsmime.rc\fP in - ** the \fCsamples/\fP subdirectory which has been installed on your system - ** alongside the documentation. - ** (S/MIME only) - */ - { "smime_verify_command", DT_STR, R_NONE, UL &SmimeVerifyCommand, 0}, - /* - ** .pp - ** This command is used to verify S/MIME signatures of type \fCmultipart/signed\fP. - ** .pp - ** This is a format string, see the $$smime_decrypt_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (S/MIME only) - */ - { "smime_verify_opaque_command", DT_STR, R_NONE, UL &SmimeVerifyOpaqueCommand, 0}, - /* - ** .pp - ** This command is used to verify S/MIME signatures of type - ** \fCapplication/x-pkcs7-mime\fP. - ** .pp - ** This is a format string, see the $$smime_decrypt_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (S/MIME only) - */ - { "smime_sign_command", DT_STR, R_NONE, UL &SmimeSignCommand, 0}, - /* - ** .pp - ** This command is used to created S/MIME signatures of type - ** \fCmultipart/signed\fP, which can be read by all mail clients. - ** .pp - ** This is a format string, see the $$smime_decrypt_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (S/MIME only) - */ - { "smime_sign_opaque_command", DT_STR, R_NONE, UL &SmimeSignOpaqueCommand, 0}, - /* - ** .pp - ** This command is used to created S/MIME signatures of type - ** \fCapplication/x-pkcs7-signature\fP, which can only be handled by mail - ** clients supporting the S/MIME extension. - ** .pp - ** This is a format string, see the $$smime_decrypt_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (S/MIME only) - */ - { "smime_encrypt_command", DT_STR, R_NONE, UL &SmimeEncryptCommand, 0}, - /* - ** .pp - ** This command is used to create encrypted S/MIME messages. - ** .pp - ** This is a format string, see the $$smime_decrypt_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (S/MIME only) - */ - { "smime_pk7out_command", DT_STR, R_NONE, UL &SmimePk7outCommand, 0}, - /* - ** .pp - ** This command is used to extract PKCS7 structures of S/MIME signatures, - ** in order to extract the public X509 certificate(s). - ** .pp - ** This is a format string, see the $$smime_decrypt_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (S/MIME only) - */ - { "smime_get_cert_command", DT_STR, R_NONE, UL &SmimeGetCertCommand, 0}, - /* - ** .pp - ** This command is used to extract X509 certificates from a PKCS7 structure. - ** .pp - ** This is a format string, see the $$smime_decrypt_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (S/MIME only) - */ - { "smime_get_signer_cert_command", DT_STR, R_NONE, UL &SmimeGetSignerCertCommand, 0}, - /* - ** .pp - ** This command is used to extract only the signers X509 certificate from a S/MIME - ** signature, so that the certificate's owner may get compared to the - ** email's ``From:'' field. - ** .pp - ** This is a format string, see the $$smime_decrypt_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (S/MIME only) - */ - { "smime_import_cert_command", DT_STR, R_NONE, UL &SmimeImportCertCommand, 0}, - /* - ** .pp - ** This command is used to import a certificate via smime_keys. - ** .pp - ** This is a format string, see the $$smime_decrypt_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (S/MIME only) - */ - { "smime_get_cert_email_command", DT_STR, R_NONE, UL &SmimeGetCertEmailCommand, 0}, - /* - ** .pp - ** This command is used to extract the mail address(es) used for storing - ** X509 certificates, and for verification purposes (to check whether the - ** certificate was issued for the sender's mailbox). - ** .pp - ** This is a format string, see the $$smime_decrypt_command command for - ** possible \fCprintf(3)\fP-like sequences. - ** (S/MIME only) - */ - { "smime_sign_as", DT_SYN, R_NONE, UL "smime_default_key", 0 }, - { "smime_default_key", DT_STR, R_NONE, UL &SmimeDefaultKey, 0 }, - /* - ** .pp - ** This is the default key-pair to use for signing. This must be set to the - ** keyid (the hash-value that OpenSSL generates) to work properly - ** (S/MIME only) - */ -#if defined(USE_SSL) - { "ssl_client_cert", DT_PATH, R_NONE, UL &SslClientCert, 0 }, - /* - ** .pp - ** The file containing a client certificate and its associated private - ** key. - */ - { "ssl_force_tls", DT_BOOL, R_NONE, OPTSSLFORCETLS, 0 }, - /* - ** .pp - ** If this variable is \fIset\fP, Mutt will require that all connections - ** to remote servers be encrypted. Furthermore it will attempt to - ** negotiate TLS even if the server does not advertise the capability, - ** since it would otherwise have to abort the connection anyway. This - ** option supersedes $$ssl_starttls. - */ - { "ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, M_YES }, - /* - ** .pp - ** If \fIset\fP (the default), mutt will attempt to use \fCSTARTTLS\fP on servers - ** advertising the capability. When \fIunset\fP, mutt will not attempt to - ** use \fCSTARTTLS\fP regardless of the server's capabilities. - */ - { "certificate_file", DT_PATH, R_NONE, UL &SslCertFile, UL "~/.mutt_certificates" }, - /* - ** .pp - ** This variable specifies the file where the certificates you trust - ** are saved. When an unknown certificate is encountered, you are asked - ** if you accept it or not. If you accept it, the certificate can also - ** be saved in this file and further connections are automatically - ** accepted. - ** .pp - ** You can also manually add CA certificates in this file. Any server - ** certificate that is signed with one of these CA certificates is - ** also automatically accepted. - ** .pp - ** Example: - ** .ts - ** set certificate_file=~/.mutt/certificates - ** .te - */ -# ifdef USE_SSL_OPENSSL - { "ssl_usesystemcerts", DT_BOOL, R_NONE, OPTSSLSYSTEMCERTS, 1 }, - /* - ** .pp - ** If set to \fIyes\fP, mutt will use CA certificates in the - ** system-wide certificate store when checking if a server certificate - ** is signed by a trusted CA. - */ - { "entropy_file", DT_PATH, R_NONE, UL &SslEntropyFile, 0 }, - /* - ** .pp - ** The file which includes random data that is used to initialize SSL - ** library functions. - */ - { "ssl_use_sslv2", DT_BOOL, R_NONE, OPTSSLV2, 1 }, - /* - ** .pp - ** This variables specifies whether to attempt to use SSLv2 in the - ** SSL authentication process. - */ -# endif /* defined USE_SSL_OPENSSL */ - { "ssl_use_sslv3", DT_BOOL, R_NONE, OPTSSLV3, 1 }, - /* - ** .pp - ** This variables specifies whether to attempt to use SSLv3 in the - ** SSL authentication process. - */ - { "ssl_use_tlsv1", DT_BOOL, R_NONE, OPTTLSV1, 1 }, - /* - ** .pp - ** This variables specifies whether to attempt to use TLSv1 in the - ** SSL authentication process. - */ -# ifdef USE_SSL_GNUTLS - { "ssl_min_dh_prime_bits", DT_NUM, R_NONE, UL &SslDHPrimeBits, 0 }, - /* - ** .pp - ** This variable specifies the minimum acceptable prime size (in bits) - ** for use in any Diffie-Hellman key exchange. A value of 0 will use - ** the default from the GNUTLS library. - */ - { "ssl_ca_certificates_file", DT_PATH, R_NONE, UL &SslCACertFile, 0 }, - /* - ** .pp - ** This variable specifies a file containing trusted CA certificates. - ** Any server certificate that is signed with one of these CA - ** certificates is also automatically accepted. - ** .pp - ** Example: - ** .ts - ** set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt - ** .te - */ -# endif /* USE_SSL_GNUTLS */ -#endif /* defined(USE_SSL) */ - { "pipe_split", DT_BOOL, R_NONE, OPTPIPESPLIT, 0 }, - /* - ** .pp - ** Used in connection with the \fC\fP function following - ** \fC\fP. If this variable is \fIunset\fP, when piping a list of - ** tagged messages Mutt will concatenate the messages and will pipe them - ** all concatenated. When \fIset\fP, Mutt will pipe the messages one by one. - ** In both cases the messages are piped in the current sorted order, - ** and the $$pipe_sep separator is added after each message. + ** menu. + ** .pp + ** This is a format string, see the $$pgp_decode_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (PGP only) */ { "pipe_decode", DT_BOOL, R_NONE, OPTPIPEDECODE, 0 }, /* @@ -2242,7 +1980,25 @@ struct option_t MuttVars[] = { ** The separator to add between messages when piping a list of tagged ** messages to an external Unix command. */ + { "pipe_split", DT_BOOL, R_NONE, OPTPIPESPLIT, 0 }, + /* + ** .pp + ** Used in connection with the \fC\fP function following + ** \fC\fP. If this variable is \fIunset\fP, when piping a list of + ** tagged messages Mutt will concatenate the messages and will pipe them + ** all concatenated. When \fIset\fP, Mutt will pipe the messages one by one. + ** In both cases the messages are piped in the current sorted order, + ** and the $$pipe_sep separator is added after each message. + */ #ifdef USE_POP + { "pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, 1 }, + /* + ** .pp + ** If \fIset\fP, Mutt will try all available authentication methods. + ** When \fIunset\fP, Mutt will only fall back to other authentication + ** methods if the previous methods are unavailable. If a method is + ** available but authentication fails, Mutt will not connect to the POP server. + */ { "pop_authenticators", DT_STR, R_NONE, UL &PopAuthenticators, UL 0 }, /* ** .pp @@ -2259,14 +2015,6 @@ struct option_t MuttVars[] = { ** set pop_authenticators="digest-md5:apop:user" ** .te */ - { "pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, 1 }, - /* - ** .pp - ** If \fIset\fP, Mutt will try all available authentication methods. - ** When \fIunset\fP, Mutt will only fall back to other authentication - ** methods if the previous methods are unavailable. If a method is - ** available but authentication fails, Mutt will not connect to the POP server. - */ { "pop_checkinterval", DT_NUM, R_NONE, UL &PopCheckTimeout, 60 }, /* ** .pp @@ -2298,6 +2046,16 @@ struct option_t MuttVars[] = { ** for retrieving only unread messages from the POP server when using ** the \fC$\fP function. */ + { "pop_pass", DT_STR, R_NONE, UL &PopPass, UL "" }, + /* + ** .pp + ** Specifies the password for your POP account. If \fIunset\fP, Mutt will + ** prompt you for your password when you open a POP mailbox. + ** .pp + ** \fBWarning\fP: you should only use this option when you are on a + ** fairly secure machine, because the superuser can read your muttrc + ** even if you are the only one who can read the file. + */ { "pop_reconnect", DT_QUAD, R_NONE, OPT_POPRECONNECT, M_ASKYES }, /* ** .pp @@ -2311,16 +2069,6 @@ struct option_t MuttVars[] = { ** .pp ** This variable defaults to your user name on the local machine. */ - { "pop_pass", DT_STR, R_NONE, UL &PopPass, UL "" }, - /* - ** .pp - ** Specifies the password for your POP account. If \fIunset\fP, Mutt will - ** prompt you for your password when you open a POP mailbox. - ** .pp - ** \fBWarning\fP: you should only use this option when you are on a - ** fairly secure machine, because the superuser can read your muttrc - ** even if you are the only one who can read the file. - */ #endif /* USE_POP */ { "post_indent_string",DT_STR, R_NONE, UL &PostIndentString, UL "" }, /* @@ -2339,7 +2087,7 @@ struct option_t MuttVars[] = { ** .pp ** Also see the $$recall variable. */ - { "postponed", DT_PATH, R_NONE, UL &Postponed, UL "~/postponed" }, + { "postponed", DT_PATH, R_INDEX, UL &Postponed, UL "~/postponed" }, /* ** .pp ** Mutt allows you to indefinitely ``$postpone sending a message'' which @@ -2681,111 +2429,323 @@ struct option_t MuttVars[] = { ** mutt scores are always greater than or equal to zero, the default setting ** of this variable will never mark a message read. */ + { "search_context", DT_NUM, R_NONE, UL &SearchContext, UL 0 }, + /* + ** .pp + ** For the pager, this variable specifies the number of lines shown + ** before search results. By default, search results will be top-aligned. + */ { "send_charset", DT_STR, R_NONE, UL &SendCharset, UL "us-ascii:iso-8859-1:utf-8" }, /* ** .pp - ** A colon-delimited list of character sets for outgoing messages. Mutt will use the - ** first character set into which the text can be converted exactly. - ** If your $$charset is not ``iso-8859-1'' and recipients may not - ** understand ``UTF-8'', it is advisable to include in the list an - ** appropriate widely used standard character set (such as - ** ``iso-8859-2'', ``koi8-r'' or ``iso-2022-jp'') either instead of or after - ** ``iso-8859-1''. + ** A colon-delimited list of character sets for outgoing messages. Mutt will use the + ** first character set into which the text can be converted exactly. + ** If your $$charset is not ``iso-8859-1'' and recipients may not + ** understand ``UTF-8'', it is advisable to include in the list an + ** appropriate widely used standard character set (such as + ** ``iso-8859-2'', ``koi8-r'' or ``iso-2022-jp'') either instead of or after + ** ``iso-8859-1''. + ** .pp + ** In case the text cannot be converted into one of these exactly, + ** mutt uses $$charset as a fallback. + */ + { "sendmail", DT_PATH, R_NONE, UL &Sendmail, UL SENDMAIL " -oem -oi" }, + /* + ** .pp + ** Specifies the program and arguments used to deliver mail sent by Mutt. + ** Mutt expects that the specified program interprets additional + ** arguments as recipient addresses. + */ + { "sendmail_wait", DT_NUM, R_NONE, UL &SendmailWait, 0 }, + /* + ** .pp + ** Specifies the number of seconds to wait for the $$sendmail process + ** to finish before giving up and putting delivery in the background. + ** .pp + ** Mutt interprets the value of this variable as follows: + ** .dl + ** .dt >0 .dd number of seconds to wait for sendmail to finish before continuing + ** .dt 0 .dd wait forever for sendmail to finish + ** .dt <0 .dd always put sendmail in the background without waiting + ** .de + ** .pp + ** 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. + */ + { "shell", DT_PATH, R_NONE, UL &Shell, 0 }, + /* + ** .pp + ** Command to use when spawning a subshell. By default, the user's login + ** shell from \fC/etc/passwd\fP is used. + */ + { "sig_dashes", DT_BOOL, R_NONE, OPTSIGDASHES, 1 }, + /* + ** .pp + ** If \fIset\fP, a line containing ``-- '' (note the trailing space) will be inserted before your + ** $$signature. It is \fBstrongly\fP recommended that you not \fIunset\fP + ** this variable unless your signature contains just your name. The + ** reason for this is because many software packages use ``-- \n'' to + ** detect your signature. For example, Mutt has the ability to highlight + ** the signature in a different color in the builtin pager. + */ + { "sig_on_top", DT_BOOL, R_NONE, OPTSIGONTOP, 0}, + /* + ** .pp + ** If \fIset\fP, the signature will be included before any quoted or forwarded + ** text. It is \fBstrongly\fP recommended that you do not set this variable + ** unless you really know what you are doing, and are prepared to take + ** some heat from netiquette guardians. + */ + { "signature", DT_PATH, R_NONE, UL &Signature, UL "~/.signature" }, + /* + ** .pp + ** Specifies the filename of your signature, which is appended to all + ** 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 standard output. + */ + { "simple_search", DT_STR, R_NONE, UL &SimpleSearch, UL "~f %s | ~s %s" }, + /* + ** .pp + ** 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 ``~'' pattern + ** operators. See ``$patterns'' for more information on search patterns. + ** .pp + ** 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 by + ** replacing ``%s'' with the supplied string. + ** For the default value, ``joe'' would be expanded to: ``~f joe | ~s joe''. + */ + { "sleep_time", DT_NUM, R_NONE, UL &SleepTime, 1 }, + /* + ** .pp + ** Specifies time, in seconds, to pause while displaying certain informational + ** messages, while moving from folder to folder and after expunging + ** messages from the current folder. The default is to pause one second, so + ** a value of zero for this option suppresses the pause. + */ + { "smart_wrap", DT_BOOL, R_PAGER, OPTWRAP, 1 }, + /* + ** .pp + ** Controls the display of lines longer than the screen width in the + ** internal pager. If \fIset\fP, long lines are wrapped at a word boundary. If + ** \fIunset\fP, lines are simply wrapped at the screen edge. Also see the + ** $$markers variable. + */ + { "smileys", DT_RX, R_PAGER, UL &Smileys, UL "(>From )|(:[-^]?[][)(><}{|/DP])" }, + /* + ** .pp + ** The \fIpager\fP uses this variable to catch some common false + ** positives of $$quote_regexp, most notably smileys and not consider + ** a line quoted text if it also matches $$smileys. This mostly + ** happens at the beginning of a line. + */ + + + + { "smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, 1 }, + /* + ** .pp + ** This flag controls whether you want to be asked to enter a label + ** for a certificate about to be added to the database or not. It is + ** \fIset\fP by default. + ** (S/MIME only) + */ + { "smime_ca_location", DT_PATH, R_NONE, UL &SmimeCALocation, 0 }, + /* + ** .pp + ** This variable contains the name of either a directory, or a file which + ** contains trusted certificates for use with OpenSSL. + ** (S/MIME only) + */ + { "smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, 0 }, + /* + ** .pp + ** Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle + ** storage and retrieval of keys by itself. This is very basic right + ** now, and keys and certificates are stored in two different + ** directories, both named as the hash-value retrieved from + ** OpenSSL. There is an index file which contains mailbox-address + ** keyid pairs, and which can be manually edited. This option points to + ** the location of the certificates. + ** (S/MIME only) + */ + { "smime_decrypt_command", DT_STR, R_NONE, UL &SmimeDecryptCommand, 0}, + /* + ** .pp + ** This format string specifies a command which is used to decrypt + ** \fCapplication/x-pkcs7-mime\fP attachments. + ** .pp + ** The OpenSSL command formats have their own set of \fCprintf(3)\fP-like sequences + ** similar to PGP's: + ** .dl + ** .dt %f .dd Expands to the name of a file containing a message. + ** .dt %s .dd Expands to the name of a file containing the signature part + ** . of a \fCmultipart/signed\fP attachment when verifying it. + ** .dt %k .dd The key-pair specified with $$smime_default_key + ** .dt %c .dd One or more certificate IDs. + ** .dt %a .dd The algorithm used for encryption. + ** .dt %C .dd CA location: Depending on whether $$smime_ca_location + ** . points to a directory or file, this expands to + ** . ``-CApath $$smime_ca_location'' or ``-CAfile $$smime_ca_location''. + ** .de + ** .pp + ** For examples on how to configure these formats, see the \fCsmime.rc\fP in + ** the \fCsamples/\fP subdirectory which has been installed on your system + ** alongside the documentation. + ** (S/MIME only) + */ + { "smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY, 1 }, + /* + ** .pp + ** If \fIset\fP (default) this tells mutt to use the default key for decryption. Otherwise, + ** if managing multiple certificate-key-pairs, mutt will try to use the mailbox-address + ** to determine the key to use. It will ask you to supply a key, if it can't find one. + ** (S/MIME only) + */ + { "smime_sign_as", DT_SYN, R_NONE, UL "smime_default_key", 0 }, + { "smime_default_key", DT_STR, R_NONE, UL &SmimeDefaultKey, 0 }, + /* + ** .pp + ** This is the default key-pair to use for signing. This must be set to the + ** keyid (the hash-value that OpenSSL generates) to work properly + ** (S/MIME only) + */ + { "smime_encrypt_command", DT_STR, R_NONE, UL &SmimeEncryptCommand, 0}, + /* + ** .pp + ** This command is used to create encrypted S/MIME messages. + ** .pp + ** This is a format string, see the $$smime_decrypt_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (S/MIME only) + */ + { "smime_encrypt_with", DT_STR, R_NONE, UL &SmimeCryptAlg, 0 }, + /* + ** .pp + ** This sets the algorithm that should be used for encryption. + ** Valid choices are ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``rc2-128''. + ** If \fIunset\fP, ``3des'' (TripleDES) is used. + ** (S/MIME only) + */ + { "smime_get_cert_command", DT_STR, R_NONE, UL &SmimeGetCertCommand, 0}, + /* + ** .pp + ** This command is used to extract X509 certificates from a PKCS7 structure. + ** .pp + ** This is a format string, see the $$smime_decrypt_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (S/MIME only) + */ + { "smime_get_cert_email_command", DT_STR, R_NONE, UL &SmimeGetCertEmailCommand, 0}, + /* + ** .pp + ** This command is used to extract the mail address(es) used for storing + ** X509 certificates, and for verification purposes (to check whether the + ** certificate was issued for the sender's mailbox). ** .pp - ** In case the text cannot be converted into one of these exactly, - ** mutt uses $$charset as a fallback. + ** This is a format string, see the $$smime_decrypt_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (S/MIME only) */ - { "sendmail", DT_PATH, R_NONE, UL &Sendmail, UL SENDMAIL " -oem -oi" }, + { "smime_get_signer_cert_command", DT_STR, R_NONE, UL &SmimeGetSignerCertCommand, 0}, /* ** .pp - ** Specifies the program and arguments used to deliver mail sent by Mutt. - ** Mutt expects that the specified program interprets additional - ** arguments as recipient addresses. + ** This command is used to extract only the signers X509 certificate from a S/MIME + ** signature, so that the certificate's owner may get compared to the + ** email's ``From:'' field. + ** .pp + ** This is a format string, see the $$smime_decrypt_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (S/MIME only) */ - { "sendmail_wait", DT_NUM, R_NONE, UL &SendmailWait, 0 }, + { "smime_import_cert_command", DT_STR, R_NONE, UL &SmimeImportCertCommand, 0}, /* ** .pp - ** Specifies the number of seconds to wait for the $$sendmail process - ** to finish before giving up and putting delivery in the background. - ** .pp - ** Mutt interprets the value of this variable as follows: - ** .dl - ** .dt >0 .dd number of seconds to wait for sendmail to finish before continuing - ** .dt 0 .dd wait forever for sendmail to finish - ** .dt <0 .dd always put sendmail in the background without waiting - ** .de + ** This command is used to import a certificate via smime_keys. ** .pp - ** 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. + ** This is a format string, see the $$smime_decrypt_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (S/MIME only) */ - { "shell", DT_PATH, R_NONE, UL &Shell, 0 }, + { "smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, 0}, /* ** .pp - ** Command to use when spawning a subshell. By default, the user's login - ** shell from \fC/etc/passwd\fP is used. + ** The default behaviour of mutt is to use PGP on all auto-sign/encryption + ** operations. To override and to use OpenSSL instead this must be \fIset\fP. + ** However, this has no effect while replying, since mutt will automatically + ** select the same application that was used to sign/encrypt the original + ** message. (Note that this variable can be overridden by unsetting $$crypt_autosmime.) + ** (S/MIME only) */ - { "sig_dashes", DT_BOOL, R_NONE, OPTSIGDASHES, 1 }, + { "smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, 0 }, /* ** .pp - ** If \fIset\fP, a line containing ``-- '' (note the trailing space) will be inserted before your - ** $$signature. It is \fBstrongly\fP recommended that you not \fIunset\fP - ** this variable unless your signature contains just your name. The - ** reason for this is because many software packages use ``-- \n'' to - ** detect your signature. For example, Mutt has the ability to highlight - ** the signature in a different color in the builtin pager. + ** Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle + ** storage and retrieval of keys/certs by itself. This is very basic right now, + ** and stores keys and certificates in two different directories, both + ** named as the hash-value retrieved from OpenSSL. There is an index file + ** which contains mailbox-address keyid pair, and which can be manually + ** edited. This option points to the location of the private keys. + ** (S/MIME only) */ - { "sig_on_top", DT_BOOL, R_NONE, OPTSIGONTOP, 0}, + { "smime_pk7out_command", DT_STR, R_NONE, UL &SmimePk7outCommand, 0}, /* ** .pp - ** If \fIset\fP, the signature will be included before any quoted or forwarded - ** text. It is \fBstrongly\fP recommended that you do not set this variable - ** unless you really know what you are doing, and are prepared to take - ** some heat from netiquette guardians. + ** This command is used to extract PKCS7 structures of S/MIME signatures, + ** in order to extract the public X509 certificate(s). + ** .pp + ** This is a format string, see the $$smime_decrypt_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (S/MIME only) */ - { "signature", DT_PATH, R_NONE, UL &Signature, UL "~/.signature" }, + { "smime_sign_command", DT_STR, R_NONE, UL &SmimeSignCommand, 0}, /* ** .pp - ** Specifies the filename of your signature, which is appended to all - ** 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 standard output. + ** This command is used to created S/MIME signatures of type + ** \fCmultipart/signed\fP, which can be read by all mail clients. + ** .pp + ** This is a format string, see the $$smime_decrypt_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (S/MIME only) */ - { "simple_search", DT_STR, R_NONE, UL &SimpleSearch, UL "~f %s | ~s %s" }, + { "smime_sign_opaque_command", DT_STR, R_NONE, UL &SmimeSignOpaqueCommand, 0}, /* ** .pp - ** 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 ``~'' pattern - ** operators. See ``$patterns'' for more information on search patterns. + ** This command is used to created S/MIME signatures of type + ** \fCapplication/x-pkcs7-signature\fP, which can only be handled by mail + ** clients supporting the S/MIME extension. ** .pp - ** 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 by - ** replacing ``%s'' with the supplied string. - ** For the default value, ``joe'' would be expanded to: ``~f joe | ~s joe''. + ** This is a format string, see the $$smime_decrypt_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (S/MIME only) */ - { "smart_wrap", DT_BOOL, R_PAGER, OPTWRAP, 1 }, + { "smime_timeout", DT_NUM, R_NONE, UL &SmimeTimeout, 300 }, /* ** .pp - ** Controls the display of lines longer than the screen width in the - ** internal pager. If \fIset\fP, long lines are wrapped at a word boundary. If - ** \fIunset\fP, lines are simply wrapped at the screen edge. Also see the - ** $$markers variable. + ** The number of seconds after which a cached passphrase will expire if + ** not used. + ** (S/MIME only) */ - { "smileys", DT_RX, R_PAGER, UL &Smileys, UL "(>From )|(:[-^]?[][)(><}{|/DP])" }, + { "smime_verify_command", DT_STR, R_NONE, UL &SmimeVerifyCommand, 0}, /* ** .pp - ** The \fIpager\fP uses this variable to catch some common false - ** positives of $$quote_regexp, most notably smileys and not consider - ** a line quoted text if it also matches $$smileys. This mostly - ** happens at the beginning of a line. + ** This command is used to verify S/MIME signatures of type \fCmultipart/signed\fP. + ** .pp + ** This is a format string, see the $$smime_decrypt_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (S/MIME only) */ - { "sleep_time", DT_NUM, R_NONE, UL &SleepTime, 1 }, + { "smime_verify_opaque_command", DT_STR, R_NONE, UL &SmimeVerifyOpaqueCommand, 0}, /* ** .pp - ** Specifies time, in seconds, to pause while displaying certain informational - ** messages, while moving from folder to folder and after expunging - ** messages from the current folder. The default is to pause one second, so - ** a value of zero for this option suppresses the pause. + ** This command is used to verify S/MIME signatures of type + ** \fCapplication/x-pkcs7-mime\fP. + ** .pp + ** This is a format string, see the $$smime_decrypt_command command for + ** possible \fCprintf(3)\fP-like sequences. + ** (S/MIME only) */ #ifdef USE_SMTP # ifdef USE_SASL @@ -2826,7 +2786,7 @@ struct option_t MuttVars[] = { ** smtp[s]://[user[:pass]@]host[:port]/ ** .te ** .pp - ** ... where ``[...]'' denotes an optional part. + ** where ``[...]'' denotes an optional part. ** Setting this variable overrides the value of the $$sendmail ** variable. */ @@ -2927,9 +2887,101 @@ struct option_t MuttVars[] = { ** .pp ** If your spool mailbox is in a non-default place where Mutt cannot find ** it, you can specify its location with this variable. Mutt will - ** automatically set this variable to the value of the environment - ** variable \fC$$$MAIL\fP if it is not set. + ** initially set this variable to the value of the environment + ** variable \fC$$$MAIL\fP or \fC$$$MAILDIR\fP if either is defined. + */ +#if defined(USE_SSL) +#ifdef USE_SSL_GNUTLS + { "ssl_ca_certificates_file", DT_PATH, R_NONE, UL &SslCACertFile, 0 }, + /* + ** .pp + ** This variable specifies a file containing trusted CA certificates. + ** Any server certificate that is signed with one of these CA + ** certificates is also automatically accepted. + ** .pp + ** Example: + ** .ts + ** set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt + ** .te + */ +#endif /* USE_SSL_GNUTLS */ + { "ssl_client_cert", DT_PATH, R_NONE, UL &SslClientCert, 0 }, + /* + ** .pp + ** The file containing a client certificate and its associated private + ** key. + */ + { "ssl_force_tls", DT_BOOL, R_NONE, OPTSSLFORCETLS, 0 }, + /* + ** .pp + ** If this variable is \fIset\fP, Mutt will require that all connections + ** to remote servers be encrypted. Furthermore it will attempt to + ** negotiate TLS even if the server does not advertise the capability, + ** since it would otherwise have to abort the connection anyway. This + ** option supersedes $$ssl_starttls. + */ +# ifdef USE_SSL_GNUTLS + { "ssl_min_dh_prime_bits", DT_NUM, R_NONE, UL &SslDHPrimeBits, 0 }, + /* + ** .pp + ** This variable specifies the minimum acceptable prime size (in bits) + ** for use in any Diffie-Hellman key exchange. A value of 0 will use + ** the default from the GNUTLS library. + */ +# endif /* USE_SSL_GNUTLS */ + { "ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, M_YES }, + /* + ** .pp + ** If \fIset\fP (the default), mutt will attempt to use \fCSTARTTLS\fP on servers + ** advertising the capability. When \fIunset\fP, mutt will not attempt to + ** use \fCSTARTTLS\fP regardless of the server's capabilities. + */ +# ifdef USE_SSL_OPENSSL + { "ssl_use_sslv2", DT_BOOL, R_NONE, OPTSSLV2, 0 }, + /* + ** .pp + ** This variable specifies whether to attempt to use SSLv2 in the + ** SSL authentication process. */ +# endif /* defined USE_SSL_OPENSSL */ + { "ssl_use_sslv3", DT_BOOL, R_NONE, OPTSSLV3, 1 }, + /* + ** .pp + ** This variable specifies whether to attempt to use SSLv3 in the + ** SSL authentication process. + */ + { "ssl_use_tlsv1", DT_BOOL, R_NONE, OPTTLSV1, 1 }, + /* + ** .pp + ** This variable specifies whether to attempt to use TLSv1 in the + ** SSL authentication process. + */ +#ifdef USE_SSL_OPENSSL + { "ssl_usesystemcerts", DT_BOOL, R_NONE, OPTSSLSYSTEMCERTS, 1 }, + /* + ** .pp + ** If set to \fIyes\fP, mutt will use CA certificates in the + ** system-wide certificate store when checking if a server certificate + ** is signed by a trusted CA. + */ +#endif + { "ssl_verify_dates", DT_BOOL, R_NONE, OPTSSLVERIFYDATES, 1 }, + /* + ** .pp + ** If \fIset\fP (the default), mutt will not automatically accept a server + ** certificate that is either not yet valid or already expired. You should + ** only unset this for particular known hosts, using the + ** \fC$\fP function. + */ + { "ssl_verify_host", DT_BOOL, R_NONE, OPTSSLVERIFYHOST, 1 }, + /* + ** .pp + ** If \fIset\fP (the default), mutt will not automatically accept a server + ** certificate whose host name does not match the host used in your folder + ** URL. You should only unset this for particular known hosts, using + ** the \fC$\fP function. + */ +#endif /* defined(USE_SSL) */ { "status_chars", DT_STR, R_BOTH, UL &StChars, UL "-*%A" }, /* ** .pp @@ -3054,12 +3106,6 @@ struct option_t MuttVars[] = { ** .pp ** Note that $$indent_string is ignored when this option is \fIset\fP. */ - { "thread_received", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTTHREADRECEIVED, 0 }, - /* - ** .pp - ** When \fIset\fP, mutt uses the date received rather than the date sent - ** to thread messages by subject. - */ { "thorough_search", DT_BOOL, R_NONE, OPTTHOROUGHSRC, 0 }, /* ** .pp @@ -3074,6 +3120,12 @@ struct option_t MuttVars[] = { ** raw message received (for example quoted-printable encoded or with encoded ** headers) which may lead to incorrect search results. */ + { "thread_received", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTTHREADRECEIVED, 0 }, + /* + ** .pp + ** When \fIset\fP, mutt uses the date received rather than the date sent + ** to thread messages by subject. + */ { "tilde", DT_BOOL, R_PAGER, OPTTILDE, 0 }, /* ** .pp @@ -3141,8 +3193,18 @@ struct option_t MuttVars[] = { ** .pp ** Note: For this example to work you must be able to log in to the remote ** machine without having to enter a password. + ** .pp + ** When set, Mutt uses the tunnel for all remote connections. + ** Please see ``$account-hook'' in the manual for how to use different + ** tunnel commands per connection. */ #endif + { "uncollapse_jump", DT_BOOL, R_NONE, OPTUNCOLLAPSEJUMP, 0 }, + /* + ** .pp + ** When \fIset\fP, Mutt will jump to the next unread message, if any, + ** when the current thread is \fIun\fPcollapsed. + */ { "use_8bitmime", DT_BOOL, R_NONE, OPTUSE8BITMIME, 0 }, /* ** .pp @@ -3256,6 +3318,15 @@ struct option_t MuttVars[] = { ** .pp ** (DEPRECATED) Equivalent to setting $$wrap with a negative value. */ + { "write_bcc", DT_BOOL, R_NONE, OPTWRITEBCC, 1}, + /* + ** .pp + ** Controls whether mutt writes out the ``Bcc:'' header when preparing + ** messages to be sent. Exim users may wish to unset this. If mutt + ** is set to deliver directly via SMTP (see $$smtp_url), this + ** option does nothing: mutt will never write out the ``Bcc:'' header + ** in this case. + */ { "write_inc", DT_NUM, R_NONE, UL &WriteInc, 10 }, /* ** .pp @@ -3266,17 +3337,8 @@ struct option_t MuttVars[] = { ** Also see the $$read_inc, $$net_inc and $$time_inc variables and the ** ``$tuning'' section of the manual for performance considerations. */ - { "write_bcc", DT_BOOL, R_NONE, OPTWRITEBCC, 1}, - /* - ** .pp - ** Controls whether mutt writes out the ``Bcc:'' header when preparing - ** messages to be sent. Exim users may wish to unset this. If mutt - ** is set to deliver directly via SMTP (see $$smtp_url), this - ** option does nothing: mutt will never write out the ``Bcc:'' header - ** in this case. - */ /*--*/ - { NULL } + { NULL, 0, 0, 0, 0 } }; const struct mapping_t SortMethods[] = { @@ -3291,7 +3353,7 @@ const struct mapping_t SortMethods[] = { { "to", SORT_TO }, { "score", SORT_SCORE }, { "spam", SORT_SPAM }, - { NULL, 0 } + { NULL, 0 } }; /* same as SortMethods, but with "threads" replaced by "date" */ @@ -3305,28 +3367,28 @@ const struct mapping_t SortAuxMethods[] = { { "from", SORT_FROM }, { "size", SORT_SIZE }, { "threads", SORT_DATE }, /* note: sort_aux == threads - * isn't possible. + * isn't possible. */ { "to", SORT_TO }, { "score", SORT_SCORE }, { "spam", SORT_SPAM }, - { NULL, 0 } + { NULL, 0 } }; - + const struct mapping_t SortBrowserMethods[] = { { "alpha", SORT_SUBJECT }, { "date", SORT_DATE }, { "size", SORT_SIZE }, { "unsorted", SORT_ORDER }, - { NULL } + { NULL, 0 } }; const struct mapping_t SortAliasMethods[] = { { "alias", SORT_ALIAS }, { "address", SORT_ADDRESS }, { "unsorted", SORT_ORDER }, - { NULL } + { NULL, 0 } }; const struct mapping_t SortKeyMethods[] = { @@ -3334,7 +3396,7 @@ const struct mapping_t SortKeyMethods[] = { { "date", SORT_DATE }, { "keyid", SORT_KEYID }, { "trust", SORT_TRUST }, - { NULL } + { NULL, 0 } }; @@ -3402,7 +3464,7 @@ struct command_t Commands[] = { { "ungroup", parse_ungroup, 0 }, { "hdr_order", parse_list, UL &HeaderOrderList }, #ifdef HAVE_ICONV - { "iconv-hook", mutt_parse_hook, M_ICONVHOOK }, + { "iconv-hook", mutt_parse_hook, M_ICONVHOOK }, #endif { "ignore", parse_ignore, 0 }, { "lists", parse_lists, 0 }, @@ -3442,5 +3504,5 @@ struct command_t Commands[] = { { "unscore", mutt_parse_unscore, 0 }, { "unset", parse_set, M_SET_UNSET }, { "unsubscribe", parse_unsubscribe, 0 }, - { NULL } + { NULL, NULL, 0 } }; diff --git a/lib.c b/lib.c index 146f363..c1f124e 100644 --- a/lib.c +++ b/lib.c @@ -220,11 +220,10 @@ int safe_fsync_close (FILE **f) if (fflush (*f) || fsync (fileno (*f))) { r = -1; - fclose (*f); + safe_fclose (f); } else - r = fclose(*f); - *f = NULL; + r = safe_fclose (f); } return r; @@ -345,7 +344,7 @@ void mutt_unlink (const char *s) fwrite (buf, 1, MIN (sizeof (buf), sb.st_size), f); sb.st_size -= MIN (sizeof (buf), sb.st_size); } - fclose (f); + safe_fclose (&f); } } } @@ -739,7 +738,7 @@ int mutt_rx_sanitize_string (char *dest, size_t destlen, const char *src) * If a line ends with "\", this char and the linefeed is removed, * and the next line is read too. */ -char *mutt_read_line (char *s, size_t *size, FILE *fp, int *line) +char *mutt_read_line (char *s, size_t *size, FILE *fp, int *line, int flags) { size_t offset = 0; char *ch; @@ -760,10 +759,12 @@ char *mutt_read_line (char *s, size_t *size, FILE *fp, int *line) if ((ch = strchr (s + offset, '\n')) != NULL) { (*line)++; + if (flags & M_EOL) + return s; *ch = 0; if (ch > s && *(ch - 1) == '\r') *--ch = 0; - if (ch == s || *(ch - 1) != '\\') + if (!(flags & M_CONT) || ch == s || *(ch - 1) != '\\') return s; offset = ch - s - 1; } @@ -1005,3 +1006,58 @@ mutt_strsysexit(int e) return sysexits_h[i].str; } + +int mutt_atos (const char *str, short *dst) +{ + int rc; + long res; + short tmp; + short *t = dst ? dst : &tmp; + + *t = 0; + + if ((rc = mutt_atol (str, &res)) < 0) + return rc; + if ((short) res != res) + return -2; + + *t = (short) res; + return 0; +} + +int mutt_atoi (const char *str, int *dst) +{ + int rc; + long res; + int tmp; + int *t = dst ? dst : &tmp; + + *t = 0; + + if ((rc = mutt_atol (str, &res)) < 0) + return rc; + if ((int) res != res) + return -2; + + *t = (int) res; + return 0; +} + +int mutt_atol (const char *str, long *dst) +{ + long r; + long *res = dst ? dst : &r; + char *e = NULL; + + /* no input: 0 */ + if (!str || !*str) + { + *res = 0; + return 0; + } + + *res = strtol (str, &e, 10); + if (e && *e != '\0') + return -1; + return 0; +} diff --git a/lib.h b/lib.h index 24c7334..5ce9b80 100644 --- a/lib.h +++ b/lib.h @@ -139,13 +139,17 @@ MUTT_LIB_WHERE int debuglevel MUTT_LIB_INITVAL(0); #define S_ERR 127 #define S_BKG 126 +/* Flags for mutt_read_line() */ +#define M_CONT (1<<0) /* \-continuation */ +#define M_EOL (1<<1) /* don't strip \n/\r\n */ + /* The actual library functions. */ FILE *safe_fopen (const char *, const char *); char *mutt_concatn_path (char *, size_t, const char *, size_t, const char *, size_t); char *mutt_concat_path (char *, const char *, const char *, size_t); -char *mutt_read_line (char *, size_t *, FILE *, int *); +char *mutt_read_line (char *, size_t *, FILE *, int *, int); char *mutt_skip_whitespace (char *); char *mutt_strlower (char *); char *mutt_substrcpy (char *, const char *, const char *, size_t); @@ -154,6 +158,16 @@ char *safe_strcat (char *, size_t, const char *); char *safe_strncat (char *, size_t, const char *, size_t); char *safe_strdup (const char *); +/* strtol() wrappers with range checking; they return + * 0 success + * -1 format error + * -2 overflow (for int and short) + * the int pointer may be NULL to test only without conversion + */ +int mutt_atos (const char *, short *); +int mutt_atoi (const char *, int *); +int mutt_atol (const char *, long *); + const char *mutt_stristr (const char *, const char *); const char *mutt_basename (const char *); diff --git a/m4/Makefile.in b/m4/Makefile.in index 61ea7d9..c816925 100644 --- a/m4/Makefile.in +++ b/m4/Makefile.in @@ -1,8 +1,9 @@ -# Makefile.in generated by automake 1.10.1 from Makefile.am. +# Makefile.in generated by automake 1.11 from Makefile.am. # @configure_input@ # Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, -# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. +# 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, +# Inc. # This Makefile.in is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. @@ -15,8 +16,9 @@ @SET_MAKE@ VPATH = @srcdir@ pkgdatadir = $(datadir)/@PACKAGE@ -pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkglibexecdir = $(libexecdir)/@PACKAGE@ am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd install_sh_DATA = $(install_sh) -c -m 644 install_sh_PROGRAM = $(install_sh) -c @@ -39,14 +41,14 @@ am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \ $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \ $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \ $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \ - $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/libgnutls.m4 \ - $(top_srcdir)/m4/progtest.m4 $(top_srcdir)/m4/types.m4 \ - $(top_srcdir)/configure.ac + $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \ + $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ $(ACLOCAL_M4) mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs CONFIG_HEADER = $(top_builddir)/config.h CONFIG_CLEAN_FILES = +CONFIG_CLEAN_VPATH_FILES = SOURCES = DIST_SOURCES = DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) @@ -104,9 +106,6 @@ INTL_LIBTOOL_SUFFIX_PREFIX = @INTL_LIBTOOL_SUFFIX_PREFIX@ ISPELL = @ISPELL@ KRB5CFGPATH = @KRB5CFGPATH@ LDFLAGS = @LDFLAGS@ -LIBGNUTLS_CFLAGS = @LIBGNUTLS_CFLAGS@ -LIBGNUTLS_CONFIG = @LIBGNUTLS_CONFIG@ -LIBGNUTLS_LIBS = @LIBGNUTLS_LIBS@ LIBICONV = @LIBICONV@ LIBIMAP = @LIBIMAP@ LIBIMAPDEPS = @LIBIMAPDEPS@ @@ -192,6 +191,7 @@ sharedstatedir = @sharedstatedir@ srcdir = @srcdir@ sysconfdir = @sysconfdir@ target_alias = @target_alias@ +top_build_prefix = @top_build_prefix@ top_builddir = @top_builddir@ top_srcdir = @top_srcdir@ EXTRA_DIST = README @@ -202,14 +202,14 @@ $(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(am__configure_deps) @for dep in $?; do \ case '$(am__configure_deps)' in \ *$$dep*) \ - cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \ - && exit 0; \ + ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \ + && { if test -f $@; then exit 0; else break; fi; }; \ exit 1;; \ esac; \ done; \ - echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign m4/Makefile'; \ - cd $(top_srcdir) && \ - $(AUTOMAKE) --foreign m4/Makefile + echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu m4/Makefile'; \ + $(am__cd) $(top_srcdir) && \ + $(AUTOMAKE) --gnu m4/Makefile .PRECIOUS: Makefile Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status @case '$?' in \ @@ -227,6 +227,7 @@ $(top_srcdir)/configure: $(am__configure_deps) cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh $(ACLOCAL_M4): $(am__aclocal_m4_deps) cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(am__aclocal_m4_deps): tags: TAGS TAGS: @@ -250,13 +251,17 @@ distdir: $(DISTFILES) if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ if test -d $$d/$$file; then \ dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d "$(distdir)/$$file"; then \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ - cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \ + cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ fi; \ - cp -pR $$d/$$file $(distdir)$$dir || exit 1; \ + cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \ else \ - test -f $(distdir)/$$file \ - || cp -p $$d/$$file $(distdir)/$$file \ + test -f "$(distdir)/$$file" \ + || cp -p $$d/$$file "$(distdir)/$$file" \ || exit 1; \ fi; \ done @@ -287,6 +292,7 @@ clean-generic: distclean-generic: -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES) maintainer-clean-generic: @echo "This command is intended for maintainers to use" @@ -305,6 +311,8 @@ dvi-am: html: html-am +html-am: + info: info-am info-am: @@ -313,18 +321,28 @@ install-data-am: install-dvi: install-dvi-am +install-dvi-am: + install-exec-am: install-html: install-html-am +install-html-am: + install-info: install-info-am +install-info-am: + install-man: install-pdf: install-pdf-am +install-pdf-am: + install-ps: install-ps-am +install-ps-am: + installcheck-am: maintainer-clean: maintainer-clean-am @@ -363,6 +381,7 @@ dist-hook: for i in $(srcdir)/*.m4 ; do \ cp -f -p $$i $(distdir) ; \ done + # Tell versions [3.59,3.63) of GNU make to not export all variables. # Otherwise a system limit (for SysV at least) may be exceeded. .NOEXPORT: diff --git a/m4/libgnutls.m4 b/m4/libgnutls.m4 deleted file mode 100644 index fee4a58..0000000 --- a/m4/libgnutls.m4 +++ /dev/null @@ -1,162 +0,0 @@ -dnl Autoconf macros for libgnutls -dnl $id$ - -# Modified for mutt 20050210 Brendan Cully -# Modified for LIBGNUTLS -- nmav -# Configure paths for LIBGCRYPT -# Shamelessly stolen from the one of XDELTA by Owen Taylor -# Werner Koch 99-12-09 - -dnl MUTT_AM_PATH_GNUTLS([MINIMUM-VERSION, [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND ]]]) -dnl Test for libgnutls, and define LIBGNUTLS_CFLAGS and LIBGNUTLS_LIBS -dnl -AC_DEFUN([MUTT_AM_PATH_GNUTLS], -[dnl -dnl Get the cflags and libraries from the libgnutls-config script -dnl - libgnutls_config_prefix=$1 - min_libgnutls_version=0.1.0 - - if test x$libgnutls_config_prefix != x ; then - if test x${LIBGNUTLS_CONFIG+set} != xset ; then - LIBGNUTLS_CONFIG=$libgnutls_config_prefix/bin/libgnutls-config - fi - fi - - AC_PATH_PROG(LIBGNUTLS_CONFIG, libgnutls-config, no) - AC_MSG_CHECKING(for libgnutls - version >= $min_libgnutls_version) - no_libgnutls="" - if test "$LIBGNUTLS_CONFIG" = "no" ; then - no_libgnutls=yes - else - LIBGNUTLS_CFLAGS=`$LIBGNUTLS_CONFIG $libgnutls_config_args --cflags` - LIBGNUTLS_LIBS=`$LIBGNUTLS_CONFIG $libgnutls_config_args --libs` - libgnutls_config_version=`$LIBGNUTLS_CONFIG $libgnutls_config_args --version` - - - ac_save_CFLAGS="$CFLAGS" - ac_save_LIBS="$LIBS" - CFLAGS="$CFLAGS $LIBGNUTLS_CFLAGS" - LIBS="$LIBS $LIBGNUTLS_LIBS" - -dnl -dnl Now check if the installed libgnutls is sufficiently new. Also sanity -dnl checks the results of libgnutls-config to some extent -dnl - rm -f conf.libgnutlstest - AC_TRY_RUN([ -#include -#include -#include -#include - -int -main () -{ - system ("touch conf.libgnutlstest"); - - if( strcmp( gnutls_check_version(NULL), "$libgnutls_config_version" ) ) - { - printf("\n*** 'libgnutls-config --version' returned %s, but LIBGNUTLS (%s)\n", - "$libgnutls_config_version", gnutls_check_version(NULL) ); - printf("*** was found! If libgnutls-config was correct, then it is best\n"); - printf("*** to remove the old version of LIBGNUTLS. You may also be able to fix the error\n"); - printf("*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing\n"); - printf("*** /etc/ld.so.conf. Make sure you have run ldconfig if that is\n"); - printf("*** required on your system.\n"); - printf("*** If libgnutls-config was wrong, set the environment variable LIBGNUTLS_CONFIG\n"); - printf("*** to point to the correct copy of libgnutls-config, and remove the file config.cache\n"); - printf("*** before re-running configure\n"); - } - else if ( strcmp(gnutls_check_version(NULL), LIBGNUTLS_VERSION ) ) - { - printf("\n*** LIBGNUTLS header file (version %s) does not match\n", LIBGNUTLS_VERSION); - printf("*** library (version %s)\n", gnutls_check_version(NULL) ); - } - else - { - if ( gnutls_check_version( "$min_libgnutls_version" ) ) - { - return 0; - } - else - { - printf("no\n*** An old version of LIBGNUTLS (%s) was found.\n", - gnutls_check_version(NULL) ); - printf("*** You need a version of LIBGNUTLS newer than %s. The latest version of\n", - "$min_libgnutls_version" ); - printf("*** LIBGNUTLS is always available from ftp://gnutls.hellug.gr/pub/gnutls.\n"); - printf("*** \n"); - printf("*** If you have already installed a sufficiently new version, this error\n"); - printf("*** probably means that the wrong copy of the libgnutls-config shell script is\n"); - printf("*** being found. The easiest way to fix this is to remove the old version\n"); - printf("*** of LIBGNUTLS, but you can also set the LIBGNUTLS_CONFIG environment to point to the\n"); - printf("*** correct copy of libgnutls-config. (In this case, you will have to\n"); - printf("*** modify your LD_LIBRARY_PATH enviroment variable, or edit /etc/ld.so.conf\n"); - printf("*** so that the correct libraries are found at run-time))\n"); - } - } - return 1; -} -],, no_libgnutls=yes,[echo $ac_n "cross compiling; assumed OK... $ac_c"]) - CFLAGS="$ac_save_CFLAGS" - LIBS="$ac_save_LIBS" - fi - - if test "x$no_libgnutls" = x ; then - AC_MSG_RESULT(yes) - dnl some openssl compatibility code was moved in gnutls 1.2 - AC_CHECK_HEADERS([gnutls/openssl.h]) - ifelse([$2], , :, [$2]) - else - if test -f conf.libgnutlstest ; then - : - else - AC_MSG_RESULT(no) - fi - if test "$LIBGNUTLS_CONFIG" = "no" ; then - echo "*** The libgnutls-config script installed by LIBGNUTLS could not be found" - echo "*** If LIBGNUTLS was installed in PREFIX, make sure PREFIX/bin is in" - echo "*** your path, or set the LIBGNUTLS_CONFIG environment variable to the" - echo "*** full path to libgnutls-config." - else - if test -f conf.libgnutlstest ; then - : - else - echo "*** Could not run libgnutls test program, checking why..." - CFLAGS="$CFLAGS $LIBGNUTLS_CFLAGS" - LIBS="$LIBS $LIBGNUTLS_LIBS" - AC_TRY_LINK([ -#include -#include -#include -#include -], [ return !!gnutls_check_version(NULL); ], - [ echo "*** The test program compiled, but did not run. This usually means" - echo "*** that the run-time linker is not finding LIBGNUTLS or finding the wrong" - echo "*** version of LIBGNUTLS. If it is not finding LIBGNUTLS, you'll need to set your" - echo "*** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point" - echo "*** to the installed location Also, make sure you have run ldconfig if that" - echo "*** is required on your system" - echo "***" - echo "*** If you have an old version installed, it is best to remove it, although" - echo "*** you may also be able to get things to work by modifying LD_LIBRARY_PATH" - echo "***" ], - [ echo "*** The test program failed to compile or link. See the file config.log for the" - echo "*** exact error that occured. This usually means LIBGNUTLS was incorrectly installed" - echo "*** or that you have moved LIBGNUTLS since it was installed. In the latter case, you" - echo "*** may want to edit the libgnutls-config script: $LIBGNUTLS_CONFIG" ]) - CFLAGS="$ac_save_CFLAGS" - LIBS="$ac_save_LIBS" - fi - fi - LIBGNUTLS_CFLAGS="" - LIBGNUTLS_LIBS="" - ifelse([$3], , :, [$3]) - fi - rm -f conf.libgnutlstest - AC_SUBST(LIBGNUTLS_CFLAGS) - AC_SUBST(LIBGNUTLS_LIBS) -]) - -dnl *-*wedit:notab*-* Please keep this as the last line. diff --git a/mailbox.h b/mailbox.h index 542210b..91e5dc7 100644 --- a/mailbox.h +++ b/mailbox.h @@ -78,4 +78,7 @@ int mx_is_pop (const char *); int mx_access (const char*, int); int mx_check_empty (const char *); +int mx_is_maildir (const char *); +int mx_is_mh (const char *); + #endif diff --git a/main.c b/main.c index 25fc33d..baea582 100644 --- a/main.c +++ b/main.c @@ -78,7 +78,7 @@ Copyright (C) 1998-2005 Werner Koch \n\ Copyright (C) 1999-2009 Brendan Cully \n\ Copyright (C) 1999-2002 Tommi Komulainen \n\ Copyright (C) 2000-2002 Edmund Grimley Evans \n\ -Copyright (C) 2006-2008 Rocco Rutte \n\ +Copyright (C) 2006-2009 Rocco Rutte \n\ \n\ Many others not mentioned here contributed code, fixes,\n\ and suggestions.\n"); @@ -631,7 +631,11 @@ int main (int argc, char **argv) case 'd': #ifdef DEBUG - debuglevel = atoi (optarg); + if (mutt_atoi (optarg, &debuglevel) < 0 || debuglevel <= 0) + { + fprintf (stderr, _("Error: value '%s' is invalid for -d.\n"), optarg); + return 1; + } printf (_("Debugging at level %d.\n"), debuglevel); #else printf _("DEBUG was not defined during compilation. Ignored.\n"); @@ -741,6 +745,9 @@ int main (int argc, char **argv) /* Initialize crypto backends. */ crypt_init (); + if (newMagic) + mx_set_magic (newMagic); + if (queries) { for (; optind < argc; optind++) @@ -773,9 +780,6 @@ int main (int argc, char **argv) return rv; } - if (newMagic) - mx_set_magic (newMagic); - if (!option (OPTNOCURSES)) { SETCOLOR (MT_COLOR_NORMAL); @@ -909,7 +913,7 @@ int main (int argc, char **argv) if (!option (OPTNOCURSES)) mutt_endwin (NULL); perror (tempfile); - fclose (fin); + safe_fclose (&fin); FREE (&tempfile); exit (1); } @@ -917,9 +921,9 @@ int main (int argc, char **argv) mutt_copy_stream (fin, fout); else if (bodytext) fputs (bodytext, fout); - fclose (fout); + safe_fclose (&fout); if (fin && fin != stdin) - fclose (fin); + safe_fclose (&fin); } } diff --git a/mbox.c b/mbox.c index ec3a02f..36d496c 100644 --- a/mbox.c +++ b/mbox.c @@ -208,7 +208,7 @@ int mmdf_parse_mailbox (CONTEXT *ctx) hdr->env->return_path = rfc822_parse_adrlist (hdr->env->return_path, return_path); if (!hdr->env->from) - hdr->env->from = rfc822_cpy_adr (hdr->env->return_path); + hdr->env->from = rfc822_cpy_adr (hdr->env->return_path, 0); ctx->msgcount++; } @@ -383,7 +383,7 @@ int mbox_parse_mailbox (CONTEXT *ctx) curhdr->env->return_path = rfc822_parse_adrlist (curhdr->env->return_path, return_path); if (!curhdr->env->from) - curhdr->env->from = rfc822_cpy_adr (curhdr->env->return_path); + curhdr->env->from = rfc822_cpy_adr (curhdr->env->return_path, 0); lines = 0; } @@ -679,6 +679,26 @@ int mbox_check_mailbox (CONTEXT *ctx, int *index_hint) return (-1); } +/* if mailbox has at least 1 new message, sets mtime > atime of mailbox + * so buffy check reports new mail */ +static void reset_atime (CONTEXT *ctx) +{ + struct utimbuf utimebuf; + int i; + time_t now = time (NULL); + + for (i = 0; i < ctx->msgcount; i++) + { + if (!ctx->hdrs[i]->deleted && !ctx->hdrs[i]->read && !ctx->hdrs[i]->old) + { + utimebuf.actime = now - 1; + utimebuf.modtime = now; + utime (ctx->path, &utimebuf); + return; + } + } +} + /* return values: * 0 success * -1 failure @@ -692,8 +712,6 @@ int mbox_sync_mailbox (CONTEXT *ctx, int *index_hint) int need_sort = 0; /* flag to resort mailbox if new mail arrives */ int first = -1; /* first message to be written */ LOFF_T offset; /* location in mailbox to write changed messages */ - struct stat statbuf; - struct utimbuf utimebuf; struct m_update_t *newOffset = NULL; struct m_update_t *oldOffset = NULL; FILE *fp = NULL; @@ -877,7 +895,7 @@ int mbox_sync_mailbox (CONTEXT *ctx, int *index_hint) if (fclose (fp) != 0) { fp = NULL; - dprint(1, (debugfile, "mbox_sync_mailbox: fclose() returned non-zero.\n")); + dprint(1, (debugfile, "mbox_sync_mailbox: safe_fclose (&) returned non-zero.\n")); unlink (tempfile); mutt_perror (tempfile); mutt_sleep (5); @@ -885,15 +903,6 @@ int mbox_sync_mailbox (CONTEXT *ctx, int *index_hint) } fp = NULL; - /* Save the state of this folder. */ - if (stat (ctx->path, &statbuf) == -1) - { - mutt_perror (ctx->path); - mutt_sleep (5); - unlink (tempfile); - goto bail; - } - if ((fp = fopen (tempfile, "r")) == NULL) { mutt_unblock_signals (); @@ -926,7 +935,8 @@ int mbox_sync_mailbox (CONTEXT *ctx, int *index_hint) /* copy the temp mailbox back into place starting at the first * change/deleted message */ - mutt_message _("Committing changes..."); + if (!ctx->quiet) + mutt_message _("Committing changes..."); i = mutt_copy_stream (fp, ctx->fp); if (ferror (ctx->fp)) @@ -939,7 +949,7 @@ int mbox_sync_mailbox (CONTEXT *ctx, int *index_hint) } } - fclose (fp); + safe_fclose (&fp); fp = NULL; mbox_unlock_mailbox (ctx); @@ -962,11 +972,6 @@ int mbox_sync_mailbox (CONTEXT *ctx, int *index_hint) return (-1); } - /* Restore the previous access/modification times */ - utimebuf.actime = statbuf.st_atime; - utimebuf.modtime = statbuf.st_mtime; - utime (ctx->path, &utimebuf); - /* reopen the mailbox in read-only mode */ if ((ctx->fp = fopen (ctx->path, "r")) == NULL) { @@ -993,6 +998,11 @@ int mbox_sync_mailbox (CONTEXT *ctx, int *index_hint) unlink (tempfile); /* remove partial copy of the mailbox */ mutt_unblock_signals (); + /* if mailbox has new mail, mangle atime+mtime to make buffy check + * report new mail for it */ + if (!option (OPTCHECKMBOXSIZE)) + reset_atime (ctx); + return (0); /* signal success */ bail: /* Come here in case of disaster */ @@ -1056,7 +1066,8 @@ int mutt_reopen_mailbox (CONTEXT *ctx, int *index_hint) /* silent operations */ ctx->quiet = 1; - mutt_message _("Reopening mailbox..."); + if (!ctx->quiet) + mutt_message _("Reopening mailbox..."); /* our heuristics require the old mailbox to be unsorted */ if (Sort != SORT_ORDER) @@ -1109,17 +1120,13 @@ int mutt_reopen_mailbox (CONTEXT *ctx, int *index_hint) { case M_MBOX: case M_MMDF: - if (fseek (ctx->fp, 0, SEEK_SET) != 0) - { - dprint (1, (debugfile, "mutt_reopen_mailbox: fseek() failed\n")); - rc = -1; - } - else - { - cmp_headers = mbox_strict_cmp_headers; - rc = ((ctx->magic == M_MBOX) ? mbox_parse_mailbox - : mmdf_parse_mailbox) (ctx); - } + cmp_headers = mbox_strict_cmp_headers; + safe_fclose (&ctx->fp); + if (!(ctx->fp = safe_fopen (ctx->path, "r"))) + rc = -1; + else + rc = ((ctx->magic == M_MBOX) ? mbox_parse_mailbox + : mmdf_parse_mailbox) (ctx); break; default: diff --git a/mbyte.h b/mbyte.h index 5691fda..bb5601c 100644 --- a/mbyte.h +++ b/mbyte.h @@ -11,6 +11,12 @@ # endif # ifndef HAVE_WC_FUNCS +#ifdef towupper +# undef towupper +#endif +#ifdef towlower +# undef towlower +#endif #ifdef iswprint # undef iswprint #endif diff --git a/menu.c b/menu.c index 7fe7538..21f3e53 100644 --- a/menu.c +++ b/menu.c @@ -422,9 +422,9 @@ void menu_jump (MUTTMENU *menu) buf[0] = 0; if (mutt_get_field (_("Jump to: "), buf, sizeof (buf), 0) == 0 && buf[0]) { - n = atoi (buf) - 1; - if (n >= 0 && n < menu->max) + if (mutt_atoi (buf, &n) == 0 && n > 0 && n < menu->max + 1) { + n--; /* msg numbers are 0-based */ menu->current = n; menu->redraw = REDRAW_MOTION; } @@ -725,27 +725,21 @@ static int menu_search (MUTTMENU *menu, int op) char* searchBuf = menu->menu >= 0 && menu->menu < MENU_MAX ? SearchBuffers[menu->menu] : NULL; - if (op != OP_SEARCH_NEXT && op != OP_SEARCH_OPPOSITE) + if (!(searchBuf && *searchBuf) || + (op != OP_SEARCH_NEXT && op != OP_SEARCH_OPPOSITE)) { - strfcpy (buf, searchBuf ? searchBuf : "", sizeof (buf)); - if (mutt_get_field ((op == OP_SEARCH) ? _("Search for: ") : - _("Reverse search for: "), - buf, sizeof (buf), M_CLEAR) != 0 || !buf[0]) + strfcpy (buf, searchBuf && *searchBuf ? searchBuf : "", sizeof (buf)); + if (mutt_get_field ((op == OP_SEARCH || op == OP_SEARCH_NEXT) + ? _("Search for: ") : _("Reverse search for: "), + buf, sizeof (buf), M_CLEAR) != 0 || !buf[0]) return (-1); if (menu->menu >= 0 && menu->menu < MENU_MAX) { mutt_str_replace (&SearchBuffers[menu->menu], buf); searchBuf = SearchBuffers[menu->menu]; } - menu->searchDir = (op == OP_SEARCH) ? M_SEARCH_DOWN : M_SEARCH_UP; - } - else - { - if (!searchBuf || !*searchBuf) - { - mutt_error _("No search pattern."); - return (-1); - } + menu->searchDir = (op == OP_SEARCH || op == OP_SEARCH_NEXT) ? + M_SEARCH_DOWN : M_SEARCH_UP; } searchDir = (menu->searchDir == M_SEARCH_UP) ? -1 : 1; diff --git a/mh.c b/mh.c index 1f4d050..ebe8cd9 100644 --- a/mh.c +++ b/mh.c @@ -1,5 +1,5 @@ /* - * Copyright (C) 1996-2002,2007 Michael R. Elkins + * Copyright (C) 1996-2002,2007,2009 Michael R. Elkins * Copyright (C) 1999-2005 Thomas Roessler * * This program is free software; you can redistribute it and/or modify @@ -140,20 +140,25 @@ static short mhs_unset (struct mh_sequences *mhs, int i, short f) #endif -static void mh_read_token (char *t, int *first, int *last) +static int mh_read_token (char *t, int *first, int *last) { char *p; if ((p = strchr (t, '-'))) { *p++ = '\0'; - *first = atoi (t); - *last = atoi (p); + if (mutt_atoi (t, first) < 0 || mutt_atoi (t, last) < 0) + return -1; } else - *first = *last = atoi (t); + { + if (mutt_atoi (t, first) < 0) + return -1; + *last = *first; + } + return 0; } -static void mh_read_sequences (struct mh_sequences *mhs, const char *path) +static int mh_read_sequences (struct mh_sequences *mhs, const char *path) { FILE *fp; int line = 1; @@ -162,15 +167,15 @@ static void mh_read_sequences (struct mh_sequences *mhs, const char *path) size_t sz = 0; short f; - int first, last; + int first, last, rc; char pathname[_POSIX_PATH_MAX]; snprintf (pathname, sizeof (pathname), "%s/.mh_sequences", path); if (!(fp = fopen (pathname, "r"))) - return; + return 0; /* yes, ask callers to silently ignore the error */ - while ((buff = mutt_read_line (buff, &sz, fp, &line))) + while ((buff = mutt_read_line (buff, &sz, fp, &line, 0))) { if (!(t = strtok (buff, " \t:"))) continue; @@ -186,14 +191,23 @@ static void mh_read_sequences (struct mh_sequences *mhs, const char *path) while ((t = strtok (NULL, " \t:"))) { - mh_read_token (t, &first, &last); + if (mh_read_token (t, &first, &last) < 0) + { + mhs_free_sequences (mhs); + rc = -1; + goto out; + } for (; first <= last; first++) mhs_set (mhs, first, f); } } + rc = 0; + +out: FREE (&buff); safe_fclose (&fp); + return 0; } static inline mode_t mh_umask (CONTEXT* ctx) @@ -219,11 +233,11 @@ int mh_buffy (const char *path) struct mh_sequences mhs; memset (&mhs, 0, sizeof (mhs)); - mh_read_sequences (&mhs, path); + if (mh_read_sequences (&mhs, path) < 0) + return 0; for (i = 0; !r && i <= mhs.max; i++) if (mhs_check (&mhs, i) & MH_SEQ_UNSEEN) r = 1; - mhs_free_sequences (&mhs); return r; } @@ -350,7 +364,7 @@ static void mh_update_sequences (CONTEXT * ctx) /* first, copy unknown sequences */ if ((ofp = fopen (sequences, "r"))) { - while ((buff = mutt_read_line (buff, &s, ofp, &l))) + while ((buff = mutt_read_line (buff, &s, ofp, &l, 0))) { if (!mutt_strncmp (buff, seq_unseen, mutt_strlen (seq_unseen))) continue; @@ -375,7 +389,8 @@ static void mh_update_sequences (CONTEXT * ctx) else p = ctx->hdrs[l]->path; - i = atoi (p); + if (mutt_atoi (p, &i) < 0) + continue; if (!ctx->hdrs[l]->read) { @@ -448,7 +463,7 @@ static void mh_sequences_add_one (CONTEXT * ctx, int n, short unseen, snprintf (sequences, sizeof (sequences), "%s/.mh_sequences", ctx->path); if ((ofp = fopen (sequences, "r"))) { - while ((buff = mutt_read_line (buff, &sz, ofp, &line))) + while ((buff = mutt_read_line (buff, &sz, ofp, &line, 0))) { if (unseen && !strncmp (buff, seq_unseen, mutt_strlen (seq_unseen))) { @@ -503,7 +518,8 @@ static void mh_update_maildir (struct maildir *md, struct mh_sequences *mhs) else p = md->h->path; - i = atoi (p); + if (mutt_atoi (p, &i) < 0) + continue; f = mhs_check (mhs, i); md->h->read = (f & MH_SEQ_UNSEEN) ? 0 : 1; @@ -637,7 +653,7 @@ static HEADER *maildir_parse_message (int magic, const char *fname, h->env = mutt_read_rfc822_header (f, h, 0, 0); fstat (fileno (f), &st); - fclose (f); + safe_fclose (&f); if (!h->received) h->received = h->date_sent; @@ -1027,13 +1043,14 @@ static void maildir_delayed_parsing (CONTEXT * ctx, struct maildir **md, if (!ctx->quiet && progress) mutt_progress_update (progress, count, -1); + DO_SORT(); + snprintf (fn, sizeof (fn), "%s/%s", ctx->path, p->h->path); #if USE_HCACHE if (option(OPTHCACHEVERIFY)) { - DO_SORT(); - ret = stat(fn, &lastchanged); + ret = stat(fn, &lastchanged); } else { @@ -1057,7 +1074,6 @@ static void maildir_delayed_parsing (CONTEXT * ctx, struct maildir **md, { #endif /* USE_HCACHE */ - DO_SORT(); if (maildir_parse_message (ctx->magic, fn, p->h->old, p->h)) { p->header_parsed = 1; @@ -1139,7 +1155,8 @@ int mh_read_dir (CONTEXT * ctx, const char *subdir) if (ctx->magic == M_MH) { - mh_read_sequences (&mhs, ctx->path); + if (mh_read_sequences (&mhs, ctx->path) >= 0) + return -1; mh_update_maildir (md, &mhs); mhs_free_sequences (&mhs); } @@ -1148,7 +1165,7 @@ int mh_read_dir (CONTEXT * ctx, const char *subdir) if (!data->mh_umask) data->mh_umask = mh_umask (ctx); - + return 0; } @@ -1242,8 +1259,8 @@ int maildir_open_new_message (MESSAGE * msg, CONTEXT * dest, HEADER * hdr) omask = umask (mh_umask (dest)); FOREVER { - snprintf (path, _POSIX_PATH_MAX, "%s/tmp/%s.%ld.%u_%d.%s%s", - dest->path, subdir, time (NULL), (unsigned int)getpid (), + snprintf (path, _POSIX_PATH_MAX, "%s/tmp/%s.%lld.%u_%d.%s%s", + dest->path, subdir, (long long)time (NULL), (unsigned int)getpid (), Counter++, NONULL (Hostname), suffix); dprint (2, (debugfile, "maildir_open_new_message (): Trying %s.\n", @@ -1328,8 +1345,8 @@ int maildir_commit_message (CONTEXT * ctx, MESSAGE * msg, HEADER * hdr) /* construct a new file name. */ FOREVER { - snprintf (path, _POSIX_PATH_MAX, "%s/%ld.%u_%d.%s%s", subdir, - time (NULL), (unsigned int)getpid (), Counter++, + snprintf (path, _POSIX_PATH_MAX, "%s/%lld.%u_%d.%s%s", subdir, + (long long)time (NULL), (unsigned int)getpid (), Counter++, NONULL (Hostname), suffix); snprintf (full, _POSIX_PATH_MAX, "%s/%s", ctx->path, path); @@ -1690,6 +1707,18 @@ int mh_sync_mailbox (CONTEXT * ctx, int *index_hint) goto err; } } + +#if USE_HCACHE + if (ctx->hdrs[i]->changed) + { + if (ctx->magic == M_MAILDIR) + mutt_hcache_store (hc, ctx->hdrs[i]->path + 3, ctx->hdrs[i], + 0, &maildir_hcache_keylen); + else if (ctx->magic == M_MH) + mutt_hcache_store (hc, ctx->hdrs[i]->path, ctx->hdrs[i], 0, strlen); + } +#endif + } #if USE_HCACHE @@ -1870,7 +1899,7 @@ int maildir_check_mailbox (CONTEXT * ctx, int *index_hint) * of each message we scanned. This is used in the loop over the * existing messages below to do some correlation. */ - fnames = hash_create (1031); + fnames = hash_create (1031, 0); for (p = md; p; p = p->next) { @@ -2014,12 +2043,13 @@ int mh_check_mailbox (CONTEXT * ctx, int *index_hint) maildir_parse_dir (ctx, &last, NULL, NULL, NULL); maildir_delayed_parsing (ctx, &md, NULL); - mh_read_sequences (&mhs, ctx->path); + if (mh_read_sequences (&mhs, ctx->path) < 0) + return -1; mh_update_maildir (md, &mhs); mhs_free_sequences (&mhs); /* check for modifications and adjust flags */ - fnames = hash_create (1031); + fnames = hash_create (1031, 0); for (p = md; p; p = p->next) hash_insert (fnames, p->h->path, p, 0); @@ -2213,3 +2243,50 @@ int mh_check_empty (const char *path) return r; } + +int mx_is_maildir (const char *path) +{ + char tmp[_POSIX_PATH_MAX]; + struct stat st; + + snprintf (tmp, sizeof (tmp), "%s/cur", path); + if (stat (tmp, &st) == 0 && S_ISDIR (st.st_mode)) + return 1; + return 0; +} + +int mx_is_mh (const char *path) +{ + char tmp[_POSIX_PATH_MAX]; + + snprintf (tmp, sizeof (tmp), "%s/.mh_sequences", path); + if (access (tmp, F_OK) == 0) + return 1; + + snprintf (tmp, sizeof (tmp), "%s/.xmhcache", path); + if (access (tmp, F_OK) == 0) + return 1; + + snprintf (tmp, sizeof (tmp), "%s/.mew_cache", path); + if (access (tmp, F_OK) == 0) + return 1; + + snprintf (tmp, sizeof (tmp), "%s/.mew-cache", path); + if (access (tmp, F_OK) == 0) + return 1; + + snprintf (tmp, sizeof (tmp), "%s/.sylpheed_cache", path); + if (access (tmp, F_OK) == 0) + return 1; + + /* + * ok, this isn't an mh folder, but mh mode can be used to read + * Usenet news from the spool. ;-) + */ + + snprintf (tmp, sizeof (tmp), "%s/.overview", path); + if (access (tmp, F_OK) == 0) + return 1; + + return 0; +} diff --git a/mkdtemp.c b/mkdtemp.c new file mode 100644 index 0000000..0f5edcd --- /dev/null +++ b/mkdtemp.c @@ -0,0 +1,42 @@ +/* taken from XFCE's Xarchiver, made to work without glib for mutt */ + +#include +#include +#include +#include +#include + +/* mkdtemp fuction for systems which don't have one */ +char *mkdtemp (char *tmpl) +{ + static const char LETTERS[] = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789"; + static long value = 0; + long v; + int len; + int i, j; + + len = strlen (tmpl); + if (len < 6 || strcmp (&tmpl[len - 6], "XXXXXX") != 0) + { + errno = EINVAL; + return NULL; + } + + value += ((long) time (NULL)) ^ getpid (); + + for (i = 0; i < 7 ; ++i, value += 7777) + { + /* fill in the random bits */ + for (j = 0, v = value; j < 6; ++j) + tmpl[(len - 6) + j] = LETTERS[v % 62]; v /= 62; + + /* try to create the directory */ + if (mkdir (tmpl, 0700) == 0) + return tmpl; + else if (errno != EEXIST) + return NULL; + } + + errno = EEXIST; + return NULL; +} diff --git a/mutt.h b/mutt.h index 94a7d4f..a0e3354 100644 --- a/mutt.h +++ b/mutt.h @@ -35,6 +35,12 @@ #include #include #include +/* On OS X 10.5.x, wide char functions are inlined by default breaking + * --without-wc-funcs compilation + */ +#ifdef __APPLE_CC__ +#define _DONT_USE_CTYPE_INLINE_ +#endif #ifdef HAVE_WCHAR_H # include #endif @@ -258,6 +264,7 @@ enum OPT_COPY, OPT_DELETE, OPT_FORWEDIT, + OPT_FCCATTACH, OPT_INCLUDE, OPT_MFUPTO, OPT_MIMEFWD, @@ -331,7 +338,6 @@ enum OPTENCODEFROM, OPTENVFROM, OPTFASTREPLY, - OPTFCCATTACH, OPTFCCCLEAR, OPTFOLLOWUPTO, OPTFORCENAME, @@ -352,6 +358,7 @@ enum OPTHIDETHREADSUBJECT, OPTHIDETOPLIMITED, OPTHIDETOPMISSING, + OPTHONORDISP, OPTIGNORELWS, OPTIGNORELISTREPLYTO, #ifdef USE_IMAP @@ -370,6 +377,8 @@ enum OPTSSLV3, OPTTLSV1, OPTSSLFORCETLS, + OPTSSLVERIFYDATES, + OPTSSLVERIFYHOST, #endif /* defined(USE_SSL) */ OPTIMPLICITAUTOVIEW, OPTINCLUDEONLYFIRST, @@ -544,6 +553,7 @@ int mutt_matches_ignore (const char *, LIST *); /* add an element to a list */ LIST *mutt_add_list (LIST *, const char *); LIST *mutt_add_list_n (LIST*, const void *, size_t); +LIST *mutt_find_list (LIST *, const char *); void mutt_init (int, LIST *); @@ -809,6 +819,7 @@ typedef struct pattern_t unsigned int alladdr : 1; unsigned int stringmatch : 1; unsigned int groupmatch : 1; + unsigned int ign_case : 1; /* ignore case for local stringmatch searches */ int min; int max; struct pattern_t *next; diff --git a/mutt_idna.c b/mutt_idna.c index 40b207a..f720116 100644 --- a/mutt_idna.c +++ b/mutt_idna.c @@ -62,7 +62,7 @@ static int mutt_idna_to_local (const char *in, char **out, int flags) goto notrans; /* Is this the right function? Interesting effects with some bad identifiers! */ - if (idna_to_unicode_8z8z (in, out, 1) != IDNA_SUCCESS) + if (idna_to_unicode_8z8z (in, out, IDNA_ALLOW_UNASSIGNED) != IDNA_SUCCESS) goto notrans; /* we don't want charset-hook effects, so we set flags to 0 */ @@ -83,7 +83,7 @@ static int mutt_idna_to_local (const char *in, char **out, int flags) /* we don't want charset-hook effects, so we set flags to 0 */ if (mutt_convert_string (&tmp, Charset, "utf-8", 0) == -1) irrev = 1; - if (!irrev && idna_to_ascii_8z (tmp, &t2, 1) != IDNA_SUCCESS) + if (!irrev && idna_to_ascii_8z (tmp, &t2, IDNA_ALLOW_UNASSIGNED) != IDNA_SUCCESS) irrev = 1; if (!irrev && ascii_strcasecmp (t2, in)) { @@ -122,7 +122,7 @@ static int mutt_local_to_idna (const char *in, char **out) /* we don't want charset-hook effects, so we set flags to 0 */ if (mutt_convert_string (&tmp, Charset, "utf-8", 0) == -1) rv = -1; - if (!rv && idna_to_ascii_8z (tmp, out, 1) != IDNA_SUCCESS) + if (!rv && idna_to_ascii_8z (tmp, out, IDNA_ALLOW_UNASSIGNED) != IDNA_SUCCESS) rv = -2; FREE (&tmp); diff --git a/mutt_sasl.c b/mutt_sasl.c index 2bc3020..0f4454c 100644 --- a/mutt_sasl.c +++ b/mutt_sasl.c @@ -481,6 +481,7 @@ static int mutt_sasl_conn_close (CONNECTION* conn) conn->conn_close = sasldata->msasl_close; conn->conn_read = sasldata->msasl_read; conn->conn_write = sasldata->msasl_write; + conn->conn_poll = sasldata->msasl_poll; /* release sasl resources */ sasl_dispose (&sasldata->saslconn); diff --git a/mutt_ssl.c b/mutt_ssl.c index 7de574e..cb1b0cc 100644 --- a/mutt_ssl.c +++ b/mutt_ssl.c @@ -1,16 +1,16 @@ /* * Copyright (C) 1999-2001 Tommi Komulainen - * + * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. - * + * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. - * + * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. @@ -143,7 +143,7 @@ int mutt_ssl_starttls (CONNECTION* conn) return -1; } -/* +/* * OpenSSL library needs to be fed with sufficient entropy. On systems * with /dev/urandom, this is done transparently by the library itself, * on other systems we need to fill the entropy pool ourselves. @@ -166,7 +166,7 @@ static int ssl_init (void) /* load entropy from files */ add_entropy (SslEntropyFile); add_entropy (RAND_file_name (path, sizeof (path))); - + /* load entropy from egd sockets */ #ifdef HAVE_RAND_EGD add_entropy (getenv ("EGDSOCKET")); @@ -206,9 +206,9 @@ static int add_entropy (const char *file) mutt_message (_("Filling entropy pool: %s...\n"), file); - + /* check that the file permissions are secure */ - if (st.st_uid != getuid () || + if (st.st_uid != getuid () || ((st.st_mode & (S_IWGRP | S_IRGRP)) != 0) || ((st.st_mode & (S_IWOTH | S_IROTH)) != 0)) { @@ -280,15 +280,15 @@ static int ssl_socket_open (CONNECTION * conn) data->ctx = SSL_CTX_new (SSLv23_client_method ()); /* disable SSL protocols as needed */ - if (!option(OPTTLSV1)) + if (!option(OPTTLSV1)) { SSL_CTX_set_options(data->ctx, SSL_OP_NO_TLSv1); } - if (!option(OPTSSLV2)) + if (!option(OPTSSLV2)) { SSL_CTX_set_options(data->ctx, SSL_OP_NO_SSLv2); } - if (!option(OPTSSLV3)) + if (!option(OPTSSLV3)) { SSL_CTX_set_options(data->ctx, SSL_OP_NO_SSLv3); } @@ -303,7 +303,7 @@ static int ssl_socket_open (CONNECTION * conn) mutt_socket_close (conn); return -1; } - + conn->ssf = SSL_CIPHER_get_bits (SSL_get_current_cipher (data->ssl), &maxbits); @@ -336,7 +336,7 @@ static int ssl_negotiate (CONNECTION *conn, sslsockdata* ssldata) default: errmsg = _("unknown error"); } - + mutt_error (_("SSL failed: %s"), errmsg); mutt_sleep (1); @@ -354,7 +354,7 @@ static int ssl_negotiate (CONNECTION *conn, sslsockdata* ssldata) if (!ssl_check_certificate (conn, ssldata)) return -1; - mutt_message (_("SSL connection using %s (%s)"), + mutt_message (_("SSL connection using %s (%s)"), SSL_get_cipher_version (ssldata->ssl), SSL_get_cipher_name (ssldata->ssl)); mutt_sleep (0); @@ -442,7 +442,7 @@ static char *asn1time_to_string (ASN1_UTCTIME *tm) BIO *bio; strfcpy (buf, _("[invalid date]"), sizeof (buf)); - + bio = BIO_new (BIO_s_mem()); if (bio) { @@ -496,7 +496,7 @@ static int check_certificate_by_signer (X509 *peercert) int err; err = X509_STORE_CTX_get_error (&xsc); - snprintf (buf, sizeof (buf), "%s (%d)", + snprintf (buf, sizeof (buf), "%s (%d)", X509_verify_cert_error_string(err), err); dprint (2, (debugfile, "X509_verify_cert: %s\n", buf)); dprint (2, (debugfile, " [%s]\n", peercert->name)); @@ -513,17 +513,17 @@ static int compare_certificates (X509 *cert, X509 *peercert, { unsigned char md[EVP_MAX_MD_SIZE]; unsigned int mdlen; - + /* Avoid CPU-intensive digest calculation if the certificates are * not even remotely equal. */ if (X509_subject_name_cmp (cert, peercert) != 0 || X509_issuer_name_cmp (cert, peercert) != 0) return -1; - + if (!X509_digest (cert, EVP_sha1(), md, &mdlen) || peermdlen != mdlen) return -1; - + if (memcmp(peermd, md, mdlen) != 0) return -1; @@ -542,7 +542,7 @@ static int check_certificate_cache (X509 *peercert) { return 0; } - + for (i = sk_X509_num (SslSessionCerts); i-- > 0;) { cert = sk_X509_value (SslSessionCerts, i); @@ -551,7 +551,7 @@ static int check_certificate_cache (X509 *peercert) return 1; } } - + return 0; } @@ -564,19 +564,22 @@ static int check_certificate_by_digest (X509 *peercert) FILE *fp; /* expiration check */ - if (X509_cmp_current_time (X509_get_notBefore (peercert)) >= 0) - { - dprint (2, (debugfile, "Server certificate is not yet valid\n")); - mutt_error (_("Server certificate is not yet valid")); - mutt_sleep (2); - return 0; - } - if (X509_cmp_current_time (X509_get_notAfter (peercert)) <= 0) + if (option (OPTSSLVERIFYDATES) != M_NO) { - dprint (2, (debugfile, "Server certificate has expired")); - mutt_error (_("Server certificate has expired")); - mutt_sleep (2); - return 0; + if (X509_cmp_current_time (X509_get_notBefore (peercert)) >= 0) + { + dprint (2, (debugfile, "Server certificate is not yet valid\n")); + mutt_error (_("Server certificate is not yet valid")); + mutt_sleep (2); + return 0; + } + if (X509_cmp_current_time (X509_get_notAfter (peercert)) <= 0) + { + dprint (2, (debugfile, "Server certificate has expired")); + mutt_error (_("Server certificate has expired")); + mutt_sleep (2); + return 0; + } } if ((fp = fopen (SslCertFile, "rt")) == NULL) @@ -584,19 +587,19 @@ static int check_certificate_by_digest (X509 *peercert) if (!X509_digest (peercert, EVP_sha1(), peermd, &peermdlen)) { - fclose (fp); + safe_fclose (&fp); return 0; } while ((cert = READ_X509_KEY (fp, &cert)) != NULL) { pass = compare_certificates (cert, peercert, peermd, peermdlen) ? 0 : 1; - + if (pass) break; } X509_free (cert); - fclose (fp); + safe_fclose (&fp); return pass; } @@ -736,8 +739,10 @@ static int ssl_cache_trusted_cert (X509 *c) return (sk_X509_push (SslSessionCerts, X509_dup(c))); } -/* check whether cert is preauthorized */ -static int ssl_check_preauth (X509 *cert, CONNECTION *conn) +/* check whether cert is preauthorized. If host is not null, verify that + * it matches the certificate. + * Return > 0: authorized, < 0: problems, 0: unknown validity */ +static int ssl_check_preauth (X509 *cert, const char* host) { char buf[SHORT_STRING]; @@ -749,13 +754,16 @@ static int ssl_check_preauth (X509 *cert, CONNECTION *conn) } buf[0] = 0; - if (!check_host (cert, conn->account.host, buf, sizeof (buf))) + if (host && option (OPTSSLVERIFYHOST) != M_NO) { - mutt_error (_("Certificate host check failed: %s"), buf); - mutt_sleep (2); - return -1; + if (!check_host (cert, host, buf, sizeof (buf))) + { + mutt_error (_("Certificate host check failed: %s"), buf); + mutt_sleep (2); + return -1; + } + dprint (2, (debugfile, "ssl_check_preauth: hostname check passed\n")); } - dprint (2, (debugfile, "ssl_check_preauth: hostname check passed\n")); if (check_certificate_by_signer (cert)) { @@ -779,44 +787,30 @@ static int ssl_check_certificate (CONNECTION *conn, sslsockdata *data) STACK_OF(X509) *chain; X509 *cert; - if ((preauthrc = ssl_check_preauth (data->cert, conn)) > 0) + if ((preauthrc = ssl_check_preauth (data->cert, conn->account.host)) > 0) return preauthrc; chain = SSL_get_peer_cert_chain (data->ssl); chain_len = sk_X509_num (chain); - if (!chain || (chain_len < 1)) + /* negative preauthrc means the certificate won't be accepted without + * manual override. */ + if (preauthrc < 0 || !chain || (chain_len <= 1)) return interactive_check_cert (data->cert, 0, 0); - /* check the chain from root to peer */ + /* check the chain from root to peer. */ for (i = chain_len-1; i >= 0; i--) { cert = sk_X509_value (chain, i); - if (check_certificate_cache (cert)) - dprint (2, (debugfile, "ssl chain: already cached: %s\n", cert->name)); - else if (i /* 0 is the peer */ || !preauthrc) + + /* if the certificate validates or is manually accepted, then add it to + * the trusted set and recheck the peer certificate */ + if (ssl_check_preauth (cert, NULL) + || interactive_check_cert (cert, i, chain_len)) { - if (check_certificate_by_signer (cert)) - { - dprint (2, (debugfile, "ssl chain: checked by signer: %s\n", cert->name)); - ssl_cache_trusted_cert (cert); + ssl_cache_trusted_cert (cert); + if (ssl_check_preauth (data->cert, conn->account.host)) return 1; - } - else if (SslCertFile && check_certificate_by_digest (cert)) - { - dprint (2, (debugfile, "ssl chain: trusted with file: %s\n", cert->name)); - ssl_cache_trusted_cert (cert); - return 1; - } - else /* allow users to shoot their foot */ - { - dprint (2, (debugfile, "ssl chain: check failed: %s\n", cert->name)); - if (interactive_check_cert (cert, i, chain_len)) - return 1; - } } - else /* highly suspicious because (i==0 && preauthrc < 0) */ - if (interactive_check_cert (cert, i, chain_len)) - return 1; } return 0; @@ -847,7 +841,7 @@ static int interactive_check_cert (X509 *cert, int idx, int len) name = X509_NAME_oneline (X509_get_subject_name (cert), buf, sizeof (buf)); dprint (2, (debugfile, "oneline: %s\n", name)); - + for (i = 0; i < 5; i++) { c = x509_get_part (name, part[i]); @@ -867,9 +861,9 @@ static int interactive_check_cert (X509 *cert, int idx, int len) row++; snprintf (menu->dialog[row++], SHORT_STRING, _("This certificate is valid")); - snprintf (menu->dialog[row++], SHORT_STRING, _(" from %s"), + snprintf (menu->dialog[row++], SHORT_STRING, _(" from %s"), asn1time_to_string (X509_get_notBefore (cert))); - snprintf (menu->dialog[row++], SHORT_STRING, _(" to %s"), + snprintf (menu->dialog[row++], SHORT_STRING, _(" to %s"), asn1time_to_string (X509_get_notAfter (cert))); row++; @@ -881,8 +875,10 @@ static int interactive_check_cert (X509 *cert, int idx, int len) _("SSL Certificate check (certificate %d of %d in chain)"), len - idx, len); menu->title = title; - if (SslCertFile && X509_cmp_current_time (X509_get_notAfter (cert)) >= 0 - && X509_cmp_current_time (X509_get_notBefore (cert)) < 0) + if (SslCertFile + && (option (OPTSSLVERIFYDATES) == M_NO + || (X509_cmp_current_time (X509_get_notAfter (cert)) >= 0 + && X509_cmp_current_time (X509_get_notBefore (cert)) < 0))) { menu->prompt = _("(r)eject, accept (o)nce, (a)ccept always"); menu->keys = _("roa"); @@ -892,7 +888,7 @@ static int interactive_check_cert (X509 *cert, int idx, int len) menu->prompt = _("(r)eject, accept (o)nce"); menu->keys = _("ro"); } - + helpstr[0] = '\0'; mutt_make_help (buf, sizeof (buf), _("Exit "), MENU_GENERIC, OP_EXIT); safe_strcat (helpstr, sizeof (helpstr), buf); @@ -917,7 +913,7 @@ static int interactive_check_cert (X509 *cert, int idx, int len) { if (PEM_write_X509 (fp, cert)) done = 1; - fclose (fp); + safe_fclose (&fp); } if (!done) { @@ -951,7 +947,7 @@ static void ssl_get_client_cert(sslsockdata *ssldata, CONNECTION *conn) SSL_CTX_set_default_passwd_cb(ssldata->ctx, ssl_passwd_cb); SSL_CTX_use_certificate_file(ssldata->ctx, SslClientCert, SSL_FILETYPE_PEM); SSL_CTX_use_PrivateKey_file(ssldata->ctx, SslClientCert, SSL_FILETYPE_PEM); - + /* if we are using a client cert, SASL may expect an external auth name */ mutt_account_getuser (&conn->account); } @@ -966,7 +962,7 @@ static int ssl_passwd_cb(char *buf, int size, int rwflag, void *userdata) dprint (2, (debugfile, "ssl_passwd_cb: getting password for %s@%s:%u\n", account->user, account->host, account->port)); - + if (mutt_account_getpass (account)) return 0; diff --git a/mutt_ssl_gnutls.c b/mutt_ssl_gnutls.c index d189841..ed3d5dc 100644 --- a/mutt_ssl_gnutls.c +++ b/mutt_ssl_gnutls.c @@ -33,6 +33,16 @@ #include "mutt_ssl.h" #include "mutt_regex.h" +/* certificate error bitmap values */ +#define CERTERR_VALID 0 +#define CERTERR_EXPIRED 1 +#define CERTERR_NOTYETVALID 2 +#define CERTERR_REVOKED 4 +#define CERTERR_NOTTRUSTED 8 +#define CERTERR_HOSTNAME 16 +#define CERTERR_SIGNERNOTCA 32 +#define CERTERR_INSECUREALG 64 + typedef struct _tlssockdata { gnutls_session state; @@ -265,6 +275,12 @@ static int tls_negotiate (CONNECTION * conn) SslClientCert, GNUTLS_X509_FMT_PEM); } +#if HAVE_DECL_GNUTLS_VERIFY_DISABLE_TIME_CHECKS + /* disable checking certificate activation/expiration times + in gnutls, we do the checks ourselves */ + gnutls_certificate_set_verify_flags(data->xcred, GNUTLS_VERIFY_DISABLE_TIME_CHECKS); +#endif + gnutls_init(&data->state, GNUTLS_CLIENT); /* set socket */ @@ -408,7 +424,7 @@ static int tls_compare_certificates (const gnutls_datum *peercert) } b64_data.size = fread(b64_data.data, 1, b64_data.size, fd1); - fclose(fd1); + safe_fclose (&fd1); do { ret = gnutls_pem_base64_decode_alloc(NULL, &b64_data, &cert); @@ -504,7 +520,7 @@ static int tls_check_stored_hostname (const gnutls_datum *cert, buf[0] = '\0'; tls_fingerprint (GNUTLS_DIG_MD5, buf, sizeof (buf), cert); - while ((linestr = mutt_read_line(linestr, &linestrsize, fp, &linenum)) != NULL) + while ((linestr = mutt_read_line(linestr, &linestrsize, fp, &linenum, 0)) != NULL) { if(linestr[0] == '#' && linestr[1] == 'H') { @@ -517,7 +533,7 @@ static int tls_check_stored_hostname (const gnutls_datum *cert, { regfree(&preg); FREE(&linestr); - fclose(fp); + safe_fclose (&fp); return 1; } } @@ -525,50 +541,30 @@ static int tls_check_stored_hostname (const gnutls_datum *cert, } regfree(&preg); - fclose(fp); + safe_fclose (&fp); } /* not found a matching name */ return 0; } -static int tls_check_one_certificate (const gnutls_datum_t *certdata, - gnutls_certificate_status certstat, - const char* hostname, int idx, int len) +static int tls_check_preauth (const gnutls_datum_t *certdata, + gnutls_certificate_status certstat, + const char *hostname, int chainidx, int* certerr, + int* savedcert) { gnutls_x509_crt cert; - int certerr_hostname = 0; - int certerr_expired = 0; - int certerr_notyetvalid = 0; - int certerr_nottrusted = 0; - int certerr_revoked = 0; - int certerr_signernotca = 0; - char buf[SHORT_STRING]; - char fpbuf[SHORT_STRING]; - size_t buflen; - char dn_common_name[SHORT_STRING]; - char dn_email[SHORT_STRING]; - char dn_organization[SHORT_STRING]; - char dn_organizational_unit[SHORT_STRING]; - char dn_locality[SHORT_STRING]; - char dn_province[SHORT_STRING]; - char dn_country[SHORT_STRING]; - time_t t; - char datestr[30]; - MUTTMENU *menu; - char helpstr[LONG_STRING]; - char title[STRING]; - FILE *fp; - gnutls_datum pemdata; - int i, row, done, ret; + + *certerr = CERTERR_VALID; + *savedcert = 0; if (gnutls_x509_crt_init (&cert) < 0) { mutt_error (_("Error initialising gnutls certificate data")); mutt_sleep (2); - return 0; + return -1; } - + if (gnutls_x509_crt_import (cert, certdata, GNUTLS_X509_FMT_DER) < 0) { mutt_error (_("Error processing certificate data")); @@ -576,94 +572,166 @@ static int tls_check_one_certificate (const gnutls_datum_t *certdata, gnutls_x509_crt_deinit (cert); return -1; } - - if (gnutls_x509_crt_get_expiration_time (cert) < time(NULL)) - certerr_expired = 1; - if (gnutls_x509_crt_get_activation_time (cert) > time(NULL)) - certerr_notyetvalid = 1; - if (!idx) + if (option (OPTSSLVERIFYDATES) != M_NO) { - if (!gnutls_x509_crt_check_hostname (cert, hostname) && - !tls_check_stored_hostname (certdata, hostname)) - certerr_hostname = 1; + if (gnutls_x509_crt_get_expiration_time (cert) < time(NULL)) + *certerr |= CERTERR_EXPIRED; + if (gnutls_x509_crt_get_activation_time (cert) > time(NULL)) + *certerr |= CERTERR_NOTYETVALID; } - + + if (chainidx == 0 && option (OPTSSLVERIFYHOST) != M_NO + && !gnutls_x509_crt_check_hostname (cert, hostname) + && !tls_check_stored_hostname (certdata, hostname)) + *certerr |= CERTERR_HOSTNAME; + /* see whether certificate is in our cache (certificates file) */ if (tls_compare_certificates (certdata)) { - if (certstat & GNUTLS_CERT_INVALID) + *savedcert = 1; + + if (chainidx == 0 && certstat & GNUTLS_CERT_INVALID) { /* doesn't matter - have decided is valid because server certificate is in our trusted cache */ certstat ^= GNUTLS_CERT_INVALID; } - - if (certstat & GNUTLS_CERT_SIGNER_NOT_FOUND) + + if (chainidx == 0 && certstat & GNUTLS_CERT_SIGNER_NOT_FOUND) { /* doesn't matter that we haven't found the signer, since certificate is in our trusted cache */ certstat ^= GNUTLS_CERT_SIGNER_NOT_FOUND; } - - if (certstat & GNUTLS_CERT_SIGNER_NOT_CA) + + if (chainidx <= 1 && certstat & GNUTLS_CERT_SIGNER_NOT_CA) { /* Hmm. Not really sure how to handle this, but let's say that we don't care if the CA certificate hasn't got the - correct X.509 basic constraints if server certificate is - in our cache. */ + correct X.509 basic constraints if server or first signer + certificate is in our cache. */ certstat ^= GNUTLS_CERT_SIGNER_NOT_CA; } + + if (chainidx == 0 && certstat & GNUTLS_CERT_INSECURE_ALGORITHM) + { + /* doesn't matter that it was signed using an insecure + algorithm, since certificate is in our trusted cache */ + certstat ^= GNUTLS_CERT_INSECURE_ALGORITHM; + } } if (certstat & GNUTLS_CERT_REVOKED) { - certerr_revoked = 1; + *certerr |= CERTERR_REVOKED; certstat ^= GNUTLS_CERT_REVOKED; } - + if (certstat & GNUTLS_CERT_INVALID) { - certerr_nottrusted = 1; + *certerr |= CERTERR_NOTTRUSTED; certstat ^= GNUTLS_CERT_INVALID; } - + if (certstat & GNUTLS_CERT_SIGNER_NOT_FOUND) { /* NB: already cleared if cert in cache */ - certerr_nottrusted = 1; + *certerr |= CERTERR_NOTTRUSTED; certstat ^= GNUTLS_CERT_SIGNER_NOT_FOUND; } - + if (certstat & GNUTLS_CERT_SIGNER_NOT_CA) { /* NB: already cleared if cert in cache */ - certerr_signernotca = 1; + *certerr |= CERTERR_SIGNERNOTCA; certstat ^= GNUTLS_CERT_SIGNER_NOT_CA; } - /* OK if signed by (or is) a trusted certificate */ - /* we've been zeroing the interesting bits in certstat - + if (certstat & GNUTLS_CERT_INSECURE_ALGORITHM) + { + /* NB: already cleared if cert in cache */ + *certerr |= CERTERR_INSECUREALG; + certstat ^= GNUTLS_CERT_INSECURE_ALGORITHM; + } + + gnutls_x509_crt_deinit (cert); + + /* we've been zeroing the interesting bits in certstat - don't return OK if there are any unhandled bits we don't understand */ - if (!(certerr_expired || certerr_notyetvalid || - certerr_hostname || certerr_nottrusted) && certstat == 0) - { - gnutls_x509_crt_deinit (cert); + if (*certerr == CERTERR_VALID && certstat == 0) + return 0; + + return -1; +} + +static int tls_check_one_certificate (const gnutls_datum_t *certdata, + gnutls_certificate_status certstat, + const char* hostname, int idx, int len) +{ + int certerr, savedcert; + gnutls_x509_crt cert; + char buf[SHORT_STRING]; + char fpbuf[SHORT_STRING]; + size_t buflen; + char dn_common_name[SHORT_STRING]; + char dn_email[SHORT_STRING]; + char dn_organization[SHORT_STRING]; + char dn_organizational_unit[SHORT_STRING]; + char dn_locality[SHORT_STRING]; + char dn_province[SHORT_STRING]; + char dn_country[SHORT_STRING]; + time_t t; + char datestr[30]; + MUTTMENU *menu; + char helpstr[LONG_STRING]; + char title[STRING]; + FILE *fp; + gnutls_datum pemdata; + int i, row, done, ret; + + if (!tls_check_preauth (certdata, certstat, hostname, idx, &certerr, + &savedcert)) return 1; + + /* skip signers if insecure algorithm was used */ + if (idx && (certerr & CERTERR_INSECUREALG)) + { + if (idx == 1) + { + mutt_error (_("Warning: Server certificate was signed using an insecure algorithm")); + mutt_sleep (2); + } + return 0; } /* interactive check from user */ + if (gnutls_x509_crt_init (&cert) < 0) + { + mutt_error (_("Error initialising gnutls certificate data")); + mutt_sleep (2); + return 0; + } + + if (gnutls_x509_crt_import (cert, certdata, GNUTLS_X509_FMT_DER) < 0) + { + mutt_error (_("Error processing certificate data")); + mutt_sleep (2); + gnutls_x509_crt_deinit (cert); + return -1; + } + menu = mutt_new_menu (-1); menu->max = 25; menu->dialog = (char **) safe_calloc (1, menu->max * sizeof (char *)); for (i = 0; i < menu->max; i++) menu->dialog[i] = (char *) safe_calloc (1, SHORT_STRING * sizeof (char)); - + row = 0; strfcpy (menu->dialog[row], _("This certificate belongs to:"), SHORT_STRING); row++; - + buflen = sizeof (dn_common_name); if (gnutls_x509_crt_get_dn_by_oid (cert, GNUTLS_OID_X520_COMMON_NAME, 0, 0, dn_common_name, &buflen) != 0) @@ -692,17 +760,17 @@ static int tls_check_one_certificate (const gnutls_datum_t *certdata, if (gnutls_x509_crt_get_dn_by_oid (cert, GNUTLS_OID_X520_COUNTRY_NAME, 0, 0, dn_country, &buflen) != 0) dn_country[0] = '\0'; - + snprintf (menu->dialog[row++], SHORT_STRING, " %s %s", dn_common_name, dn_email); snprintf (menu->dialog[row++], SHORT_STRING, " %s", dn_organization); snprintf (menu->dialog[row++], SHORT_STRING, " %s", dn_organizational_unit); snprintf (menu->dialog[row++], SHORT_STRING, " %s %s %s", dn_locality, dn_province, dn_country); row++; - + strfcpy (menu->dialog[row], _("This certificate was issued by:"), SHORT_STRING); row++; - + buflen = sizeof (dn_common_name); if (gnutls_x509_crt_get_issuer_dn_by_oid (cert, GNUTLS_OID_X520_COMMON_NAME, 0, 0, dn_common_name, &buflen) != 0) @@ -731,52 +799,52 @@ static int tls_check_one_certificate (const gnutls_datum_t *certdata, if (gnutls_x509_crt_get_issuer_dn_by_oid (cert, GNUTLS_OID_X520_COUNTRY_NAME, 0, 0, dn_country, &buflen) != 0) dn_country[0] = '\0'; - + snprintf (menu->dialog[row++], SHORT_STRING, " %s %s", dn_common_name, dn_email); snprintf (menu->dialog[row++], SHORT_STRING, " %s", dn_organization); snprintf (menu->dialog[row++], SHORT_STRING, " %s", dn_organizational_unit); snprintf (menu->dialog[row++], SHORT_STRING, " %s %s %s", dn_locality, dn_province, dn_country); row++; - + snprintf (menu->dialog[row++], SHORT_STRING, _("This certificate is valid")); - + t = gnutls_x509_crt_get_activation_time (cert); - snprintf (menu->dialog[row++], SHORT_STRING, _(" from %s"), + snprintf (menu->dialog[row++], SHORT_STRING, _(" from %s"), tls_make_date (t, datestr, 30)); - + t = gnutls_x509_crt_get_expiration_time (cert); - snprintf (menu->dialog[row++], SHORT_STRING, _(" to %s"), + snprintf (menu->dialog[row++], SHORT_STRING, _(" to %s"), tls_make_date (t, datestr, 30)); - + fpbuf[0] = '\0'; tls_fingerprint (GNUTLS_DIG_SHA, fpbuf, sizeof (fpbuf), certdata); snprintf (menu->dialog[row++], SHORT_STRING, _("SHA1 Fingerprint: %s"), fpbuf); fpbuf[0] = '\0'; tls_fingerprint (GNUTLS_DIG_MD5, fpbuf, sizeof (fpbuf), certdata); snprintf (menu->dialog[row++], SHORT_STRING, _("MD5 Fingerprint: %s"), fpbuf); - - if (certerr_notyetvalid) + + if (certerr & CERTERR_NOTYETVALID) { row++; strfcpy (menu->dialog[row], _("WARNING: Server certificate is not yet valid"), SHORT_STRING); } - if (certerr_expired) + if (certerr & CERTERR_EXPIRED) { row++; strfcpy (menu->dialog[row], _("WARNING: Server certificate has expired"), SHORT_STRING); } - if (certerr_revoked) + if (certerr & CERTERR_REVOKED) { row++; strfcpy (menu->dialog[row], _("WARNING: Server certificate has been revoked"), SHORT_STRING); } - if (certerr_hostname) + if (certerr & CERTERR_HOSTNAME) { row++; strfcpy (menu->dialog[row], _("WARNING: Server hostname does not match certificate"), SHORT_STRING); } - if (certerr_signernotca) + if (certerr & CERTERR_SIGNERNOTCA) { row++; strfcpy (menu->dialog[row], _("WARNING: Signer of server certificate is not a CA"), SHORT_STRING); @@ -788,7 +856,9 @@ static int tls_check_one_certificate (const gnutls_datum_t *certdata, menu->title = title; /* certificates with bad dates, or that are revoked, must be accepted manually each and every time */ - if (SslCertFile && !certerr_expired && !certerr_notyetvalid && !certerr_revoked) + if (SslCertFile && !savedcert + && !(certerr & (CERTERR_EXPIRED | CERTERR_NOTYETVALID + | CERTERR_REVOKED))) { menu->prompt = _("(r)eject, accept (o)nce, (a)ccept always"); menu->keys = _("roa"); @@ -798,14 +868,14 @@ static int tls_check_one_certificate (const gnutls_datum_t *certdata, menu->prompt = _("(r)eject, accept (o)nce"); menu->keys = _("ro"); } - + helpstr[0] = '\0'; mutt_make_help (buf, sizeof (buf), _("Exit "), MENU_GENERIC, OP_EXIT); safe_strcat (helpstr, sizeof (helpstr), buf); mutt_make_help (buf, sizeof (buf), _("Help"), MENU_GENERIC, OP_HELP); safe_strcat (helpstr, sizeof (helpstr), buf); menu->help = helpstr; - + done = 0; set_option (OPTUNBUFFEREDINPUT); while (!done) @@ -822,12 +892,12 @@ static int tls_check_one_certificate (const gnutls_datum_t *certdata, if ((fp = fopen (SslCertFile, "a"))) { /* save hostname if necessary */ - if (certerr_hostname) + if (certerr & CERTERR_HOSTNAME) { fprintf(fp, "#H %s %s\n", hostname, fpbuf); done = 1; } - if (certerr_nottrusted) + if (certerr & CERTERR_NOTTRUSTED) { done = 0; ret = gnutls_pem_base64_encode_alloc ("CERTIFICATE", certdata, @@ -841,7 +911,7 @@ static int tls_check_one_certificate (const gnutls_datum_t *certdata, gnutls_free (pemdata.data); } } - fclose (fp); + safe_fclose (&fp); } if (!done) { @@ -866,23 +936,14 @@ static int tls_check_one_certificate (const gnutls_datum_t *certdata, return (done == 2); } -static int tls_check_certificate (CONNECTION* conn) +/* sanity-checking wrapper for gnutls_certificate_verify_peers */ +static gnutls_certificate_status tls_verify_peers (gnutls_session tlsstate) { - tlssockdata *data = conn->sockdata; - gnutls_session state = data->state; - const gnutls_datum *cert_list; - unsigned int cert_list_size = 0; gnutls_certificate_status certstat; - int i, rc; - - if (gnutls_auth_get_type (state) != GNUTLS_CRD_CERTIFICATE) - { - mutt_error (_("Unable to get certificate from peer")); - mutt_sleep (2); - return 0; - } - certstat = gnutls_certificate_verify_peers (state); + certstat = gnutls_certificate_verify_peers (tlsstate); + if (!certstat) + return certstat; if (certstat == GNUTLS_E_NO_CERTIFICATE_FOUND) { @@ -899,13 +960,34 @@ static int tls_check_certificate (CONNECTION* conn) } /* We only support X.509 certificates (not OpenPGP) at the moment */ - if (gnutls_certificate_type_get (state) != GNUTLS_CRT_X509) + if (gnutls_certificate_type_get (tlsstate) != GNUTLS_CRT_X509) { mutt_error (_("Certificate is not X.509")); mutt_sleep (2); return 0; } + return certstat; +} + +static int tls_check_certificate (CONNECTION* conn) +{ + tlssockdata *data = conn->sockdata; + gnutls_session state = data->state; + const gnutls_datum *cert_list; + unsigned int cert_list_size = 0; + gnutls_certificate_status certstat; + int certerr, i, preauthrc, savedcert, rc = 0; + + if (gnutls_auth_get_type (state) != GNUTLS_CRD_CERTIFICATE) + { + mutt_error (_("Unable to get certificate from peer")); + mutt_sleep (2); + return 0; + } + + certstat = tls_verify_peers (state); + cert_list = gnutls_certificate_get_peers (state, &cert_list_size); if (!cert_list) { @@ -914,13 +996,42 @@ static int tls_check_certificate (CONNECTION* conn) return 0; } + /* tls_verify_peers doesn't check hostname or expiration, so walk + * from most specific to least checking these. If we see a saved certificate, + * its status short-circuits the remaining checks. */ + preauthrc = 0; + for (i = 0; i < cert_list_size; i++) { + rc = tls_check_preauth(&cert_list[i], certstat, conn->account.host, i, + &certerr, &savedcert); + preauthrc += rc; + + if (savedcert) + { + if (!preauthrc) + return 1; + else + break; + } + } + + /* then check interactively, starting from chain root */ for (i = cert_list_size - 1; i >= 0; i--) { rc = tls_check_one_certificate (&cert_list[i], certstat, conn->account.host, i, cert_list_size); - if (rc) - return rc; + + /* add signers to trust set, then reverify */ + if (i && rc) { + rc = gnutls_certificate_set_x509_trust_mem (data->xcred, &cert_list[i], + GNUTLS_X509_FMT_DER); + if (rc != 1) + dprint (1, (debugfile, "error trusting certificate %d: %d\n", i, rc)); + + certstat = tls_verify_peers (state); + if (!certstat) + return 1; + } } - return 0; + return rc; } diff --git a/muttlib.c b/muttlib.c index d1ce40c..590bef7 100644 --- a/muttlib.c +++ b/muttlib.c @@ -252,6 +252,21 @@ LIST *mutt_add_list_n (LIST *head, const void *data, size_t len) return head; } +LIST *mutt_find_list (LIST *l, const char *data) +{ + LIST *p = l; + + while (p) + { + if (data == p->data) + return p; + if (data && p->data && mutt_strcmp (p->data, data) == 0) + return p; + p = p->next; + } + return NULL; +} + void mutt_free_list (LIST **list) { LIST *p; @@ -759,7 +774,7 @@ void mutt_pretty_mailbox (char *s, size_t buflen) char *p = s, *q = s; size_t len; url_scheme_t scheme; - char tmp[_POSIX_PATH_MAX]; + char tmp[PATH_MAX]; scheme = url_check_scheme (s); @@ -1093,7 +1108,7 @@ void mutt_FormatString (char *dest, /* output buffer */ if ((pid = mutt_create_filter(command->data, NULL, &filter, NULL))) { n = fread(dest, 1, destlen /* already decremented */, filter); - fclose(filter); + safe_fclose (&filter); dest[n] = '\0'; while (dest[n-1] == '\n' || dest[n-1] == '\r') dest[--n] = '\0'; diff --git a/mx.c b/mx.c index d135576..7c7c73a 100644 --- a/mx.c +++ b/mx.c @@ -251,7 +251,7 @@ int mx_lock_file (const char *path, int fd, int excl, int dot, int timeout) int mx_unlock_file (const char *path, int fd, int dot) { #ifdef USE_FCNTL - struct flock unlockit = { F_UNLCK, 0, 0, 0 }; + struct flock unlockit = { F_UNLCK, 0, 0, 0, 0 }; memset (&unlockit, 0, sizeof (struct flock)); unlockit.l_type = F_UNLCK; @@ -370,42 +370,12 @@ int mx_get_magic (const char *path) if (S_ISDIR (st.st_mode)) { /* check for maildir-style mailbox */ - - snprintf (tmp, sizeof (tmp), "%s/cur", path); - if (stat (tmp, &st) == 0 && S_ISDIR (st.st_mode)) - return (M_MAILDIR); + if (mx_is_maildir (path)) + return M_MAILDIR; /* check for mh-style mailbox */ - - snprintf (tmp, sizeof (tmp), "%s/.mh_sequences", path); - if (access (tmp, F_OK) == 0) - return (M_MH); - - snprintf (tmp, sizeof (tmp), "%s/.xmhcache", path); - if (access (tmp, F_OK) == 0) - return (M_MH); - - snprintf (tmp, sizeof (tmp), "%s/.mew_cache", path); - if (access (tmp, F_OK) == 0) - return (M_MH); - - snprintf (tmp, sizeof (tmp), "%s/.mew-cache", path); - if (access (tmp, F_OK) == 0) - return (M_MH); - - snprintf (tmp, sizeof (tmp), "%s/.sylpheed_cache", path); - if (access (tmp, F_OK) == 0) - return (M_MH); - - /* - * ok, this isn't an mh folder, but mh mode can be used to read - * Usenet news from the spool. ;-) - */ - - snprintf (tmp, sizeof (tmp), "%s/.overview", path); - if (access (tmp, F_OK) == 0) - return (M_MH); - + if (mx_is_mh (path)) + return M_MH; } else if (st.st_size == 0) { @@ -895,7 +865,8 @@ int mx_close_mailbox (CONTEXT *ctx, int *index_hint) if (move_messages) { - mutt_message (_("Moving read messages to %s..."), mbox); + if (!ctx->quiet) + mutt_message (_("Moving read messages to %s..."), mbox); #ifdef USE_IMAP /* try to use server-side copy first */ @@ -954,7 +925,8 @@ int mx_close_mailbox (CONTEXT *ctx, int *index_hint) } else if (!ctx->changed && ctx->deleted == 0) { - mutt_message _("Mailbox is unchanged."); + if (!ctx->quiet) + mutt_message _("Mailbox is unchanged."); mx_fastclose_mailbox (ctx); return 0; } @@ -989,12 +961,15 @@ int mx_close_mailbox (CONTEXT *ctx, int *index_hint) } } - if (move_messages) - mutt_message (_("%d kept, %d moved, %d deleted."), - ctx->msgcount - ctx->deleted, read_msgs, ctx->deleted); - else - mutt_message (_("%d kept, %d deleted."), - ctx->msgcount - ctx->deleted, ctx->deleted); + if (!ctx->quiet) + { + if (move_messages) + mutt_message (_("%d kept, %d moved, %d deleted."), + ctx->msgcount - ctx->deleted, read_msgs, ctx->deleted); + else + mutt_message (_("%d kept, %d deleted."), + ctx->msgcount - ctx->deleted, ctx->deleted); + } if (ctx->msgcount == ctx->deleted && (ctx->magic == M_MMDF || ctx->magic == M_MBOX) && @@ -1118,7 +1093,8 @@ int mx_sync_mailbox (CONTEXT *ctx, int *index_hint) if (!ctx->changed && !ctx->deleted) { - mutt_message _("Mailbox is unchanged."); + if (!ctx->quiet) + mutt_message _("Mailbox is unchanged."); return (0); } @@ -1164,11 +1140,17 @@ int mx_sync_mailbox (CONTEXT *ctx, int *index_hint) { #ifdef USE_IMAP if (ctx->magic == M_IMAP && !purge) - mutt_message _("Mailbox checkpointed."); + { + if (!ctx->quiet) + mutt_message _("Mailbox checkpointed."); + } else #endif - mutt_message (_("%d kept, %d deleted."), msgcount - deleted, - deleted); + { + if (!ctx->quiet) + mutt_message (_("%d kept, %d deleted."), msgcount - deleted, + deleted); + } mutt_sleep (0); diff --git a/obj-i486-linux-gnu-patched/Makefile b/obj-i486-linux-gnu-patched/Makefile new file mode 100644 index 0000000..6e4362c --- /dev/null +++ b/obj-i486-linux-gnu-patched/Makefile @@ -0,0 +1,1115 @@ +# Makefile.in generated by automake 1.10.1 from Makefile.am. +# Makefile. Generated from Makefile.in by configure. + +# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, +# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. +# This Makefile.in is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + + + + +VPATH = .. +pkgdatadir = $(datadir)/mutt +pkglibdir = $(libdir)/mutt +pkgincludedir = $(includedir)/mutt +am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd +install_sh_DATA = $(install_sh) -c -m 644 +install_sh_PROGRAM = $(install_sh) -c +install_sh_SCRIPT = $(install_sh) -c +INSTALL_HEADER = $(INSTALL_DATA) +transform = $(program_transform_name) +NORMAL_INSTALL = : +PRE_INSTALL = : +POST_INSTALL = : +NORMAL_UNINSTALL = : +PRE_UNINSTALL = : +POST_UNINSTALL = : +build_triplet = i486-pc-linux-gnu +host_triplet = i486-pc-linux-gnu +EXTRA_PROGRAMS = mutt_dotlock$(EXEEXT) pgpring$(EXEEXT) \ + pgpewrap$(EXEEXT) mutt_md5$(EXEEXT) +bin_PROGRAMS = mutt$(EXEEXT) mutt_dotlock$(EXEEXT) pgpring$(EXEEXT) pgpewrap$(EXEEXT) +subdir = . +DIST_COMMON = README $(am__configure_deps) $(srcdir)/Makefile.am \ + $(srcdir)/Makefile.in $(srcdir)/config.h.in \ + $(srcdir)/hcachever.sh.in $(srcdir)/muttbug.sh.in \ + $(top_srcdir)/configure $(top_srcdir)/intl/Makefile.in \ + ABOUT-NLS ChangeLog INSTALL NEWS TODO config.guess config.sub \ + depcomp install-sh missing mkinstalldirs regex.c setenv.c \ + snprintf.c strcasecmp.c strdup.c strsep.c strtok_r.c +ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 +am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \ + $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \ + $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \ + $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \ + $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \ + $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \ + $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac +am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ + $(ACLOCAL_M4) +am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \ + configure.lineno config.status.lineno +mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs +CONFIG_HEADER = config.h +CONFIG_CLEAN_FILES = intl/Makefile hcachever.sh muttbug.sh +am__installdirs = "$(DESTDIR)$(bindir)" "$(DESTDIR)$(bindir)" +binPROGRAMS_INSTALL = $(INSTALL_PROGRAM) +PROGRAMS = $(bin_PROGRAMS) $(noinst_PROGRAMS) +am_mutt_OBJECTS = addrbook.$(OBJEXT) alias.$(OBJEXT) attach.$(OBJEXT) \ + base64.$(OBJEXT) browser.$(OBJEXT) buffy.$(OBJEXT) \ + color.$(OBJEXT) crypt.$(OBJEXT) cryptglue.$(OBJEXT) \ + compress.$(OBJEXT) commands.$(OBJEXT) complete.$(OBJEXT) \ + compose.$(OBJEXT) copy.$(OBJEXT) curs_lib.$(OBJEXT) \ + curs_main.$(OBJEXT) date.$(OBJEXT) edit.$(OBJEXT) \ + enter.$(OBJEXT) flags.$(OBJEXT) init.$(OBJEXT) \ + filter.$(OBJEXT) from.$(OBJEXT) getdomain.$(OBJEXT) \ + group.$(OBJEXT) handler.$(OBJEXT) hash.$(OBJEXT) \ + hdrline.$(OBJEXT) headers.$(OBJEXT) help.$(OBJEXT) \ + hook.$(OBJEXT) keymap.$(OBJEXT) main.$(OBJEXT) mbox.$(OBJEXT) \ + menu.$(OBJEXT) mh.$(OBJEXT) mx.$(OBJEXT) pager.$(OBJEXT) \ + parse.$(OBJEXT) pattern.$(OBJEXT) postpone.$(OBJEXT) \ + query.$(OBJEXT) recvattach.$(OBJEXT) recvcmd.$(OBJEXT) \ + rfc822.$(OBJEXT) rfc1524.$(OBJEXT) rfc2047.$(OBJEXT) \ + rfc2231.$(OBJEXT) rfc3676.$(OBJEXT) score.$(OBJEXT) \ + send.$(OBJEXT) sendlib.$(OBJEXT) signal.$(OBJEXT) \ + sort.$(OBJEXT) status.$(OBJEXT) system.$(OBJEXT) \ + thread.$(OBJEXT) charset.$(OBJEXT) history.$(OBJEXT) \ + lib.$(OBJEXT) muttlib.$(OBJEXT) editmsg.$(OBJEXT) \ + mbyte.$(OBJEXT) url.$(OBJEXT) ascii.$(OBJEXT) \ + crypt-mod.$(OBJEXT) sidebar.$(OBJEXT) +am__objects_1 = patchlist.$(OBJEXT) +nodist_mutt_OBJECTS = $(am__objects_1) +mutt_OBJECTS = $(am_mutt_OBJECTS) $(nodist_mutt_OBJECTS) +am__DEPENDENCIES_1 = +am_mutt_dotlock_OBJECTS = mutt_dotlock.$(OBJEXT) +mutt_dotlock_OBJECTS = $(am_mutt_dotlock_OBJECTS) +am_mutt_md5_OBJECTS = mutt_md5-md5.$(OBJEXT) +mutt_md5_OBJECTS = $(am_mutt_md5_OBJECTS) +mutt_md5_DEPENDENCIES = +mutt_md5_LINK = $(CCLD) $(mutt_md5_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) \ + $(LDFLAGS) -o $@ +pgpewrap_SOURCES = pgpewrap.c +pgpewrap_OBJECTS = pgpewrap.$(OBJEXT) +pgpewrap_LDADD = $(LDADD) +pgpewrap_DEPENDENCIES = +am_pgpring_OBJECTS = pgppubring.$(OBJEXT) pgplib.$(OBJEXT) \ + lib.$(OBJEXT) extlib.$(OBJEXT) sha1.$(OBJEXT) md5.$(OBJEXT) \ + pgppacket.$(OBJEXT) ascii.$(OBJEXT) +pgpring_OBJECTS = $(am_pgpring_OBJECTS) +binSCRIPT_INSTALL = $(INSTALL_SCRIPT) +SCRIPTS = $(bin_SCRIPTS) +DEFAULT_INCLUDES = -I. -I$(srcdir) +depcomp = $(SHELL) $(top_srcdir)/depcomp +am__depfiles_maybe = depfiles +COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \ + $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) +CCLD = $(CC) +LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ +SOURCES = $(mutt_SOURCES) $(EXTRA_mutt_SOURCES) $(nodist_mutt_SOURCES) \ + $(mutt_dotlock_SOURCES) $(mutt_md5_SOURCES) pgpewrap.c \ + $(pgpring_SOURCES) +DIST_SOURCES = $(mutt_SOURCES) $(EXTRA_mutt_SOURCES) \ + $(mutt_dotlock_SOURCES) $(mutt_md5_SOURCES) pgpewrap.c \ + $(pgpring_SOURCES) +RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \ + html-recursive info-recursive install-data-recursive \ + install-dvi-recursive install-exec-recursive \ + install-html-recursive install-info-recursive \ + install-pdf-recursive install-ps-recursive install-recursive \ + installcheck-recursive installdirs-recursive pdf-recursive \ + ps-recursive uninstall-recursive +RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive \ + distclean-recursive maintainer-clean-recursive +ETAGS = etags +CTAGS = ctags +DIST_SUBDIRS = m4 po intl doc contrib imap +DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) +distdir = $(PACKAGE)-$(VERSION) +top_distdir = $(distdir) +am__remove_distdir = \ + { test ! -d $(distdir) \ + || { find $(distdir) -type d ! -perm -200 -exec chmod u+w {} ';' \ + && rm -fr $(distdir); }; } +DIST_ARCHIVES = $(distdir).tar.gz +GZIP_ENV = --best +distuninstallcheck_listfiles = find . -type f -print +distcleancheck_listfiles = find . -type f -print +ACLOCAL = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10 +ALLOCA = +AMTAR = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar +AR = ar +AUTOCONF = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf +AUTOHEADER = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader +AUTOMAKE = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10 +AWK = gawk +BUILD_INCLUDED_LIBINTL = no +CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo +CATOBJEXT = .gmo +CC = gcc +CCDEPMODE = depmode=none +CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2 +CONFIG_STATUS_DEPENDENCIES = $(top_srcdir)/VERSION +CPP = gcc -E +CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl +CYGPATH_W = echo +DATADIRNAME = share +DBX = no +DEBUGGER = /usr/bin/gdb +DEFS = -DPKGDATADIR=\"$(pkgdatadir)\" -DSYSCONFDIR=\"$(sysconfdir)\" \ + -DBINDIR=\"$(bindir)\" -DMUTTLOCALEDIR=\"$(datadir)/locale\" \ + -DHAVE_CONFIG_H=1 + +DEPDIR = .deps +DOTLOCK_GROUP = mail +DOTLOCK_PERMISSION = 2755 +DOTLOCK_TARGET = mutt_dotlock$(EXEEXT) +DSLROOT = +ECHO_C = +ECHO_N = -n +ECHO_T = +EGREP = /bin/grep -E +EXEEXT = +GDB = /usr/bin/gdb +GENCAT = gencat +GLIBC21 = yes +GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo +GMSGFMT = /usr/bin/msgfmt +GNUTLS_CFLAGS = +GNUTLS_LIBS = -lgnutls +GPGME_CFLAGS = +GPGME_CONFIG = /usr/bin/gpgme-config +GPGME_LIBS = -lgpgme -lgpg-error +GREP = /bin/grep +INSTALL = /usr/bin/install -c +INSTALL_DATA = ${INSTALL} -m 644 +INSTALL_PROGRAM = ${INSTALL} +INSTALL_SCRIPT = ${INSTALL} +INSTALL_STRIP_PROGRAM = $(install_sh) -c -s +INSTOBJEXT = .mo +INTLBISON = bison +INTLLIBS = +INTLOBJS = +INTL_LIBTOOL_SUFFIX_PREFIX = +ISPELL = no +KRB5CFGPATH = /usr/bin/krb5-config +LDFLAGS = -L/lib +LIBICONV = +LIBIMAP = -Limap -limap +LIBIMAPDEPS = $(top_srcdir)/imap/imap.h imap/libimap.a +LIBOBJS = +LIBS = -lidn +LTLIBOBJS = +MAINT = # +MAKEINFO = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo +MKDIR_P = /bin/mkdir -p +MKINSTALLDIRS = ../mkinstalldirs +MSGFMT = /usr/bin/msgfmt +MUTTLIBS = -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm +MUTT_LIB_OBJECTS = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o +MUTT_MD5 = mutt_md5 +OBJEXT = o +OPS = $(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT +OSPCAT = /usr/bin/ospcat +PACKAGE = mutt +PACKAGE_BUGREPORT = +PACKAGE_NAME = +PACKAGE_STRING = +PACKAGE_TARNAME = +PACKAGE_VERSION = +PATH_SEPARATOR = : +PGPAUX_TARGET = pgpring$(EXEEXT) pgpewrap$(EXEEXT) +PKG_CONFIG = /usr/bin/pkg-config +POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po +POSUB = po +RANLIB = ranlib +SDB = no +SENDMAIL = /usr/sbin/sendmail +SET_MAKE = +SHELL = /bin/sh +SMIMEAUX_TARGET = smime_keys +STRIP = +U = +USE_INCLUDED_LIBINTL = no +USE_NLS = yes +VERSION = 1.5.19 +XGETTEXT = /usr/bin/xgettext +abs_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched +abs_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/.. +abs_top_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched +abs_top_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/.. +ac_ct_CC = gcc +am__include = include +am__leading_dot = . +am__quote = +am__tar = ${AMTAR} chof - "$$tardir" +am__untar = ${AMTAR} xf - +bindir = ${exec_prefix}/bin +build = i486-pc-linux-gnu +build_alias = i486-linux-gnu +build_cpu = i486 +build_os = linux-gnu +build_vendor = pc +builddir = . +datadir = ${datarootdir} +datarootdir = ${prefix}/share +docdir = /usr/share/doc +dvidir = ${docdir} +exec_prefix = ${prefix} +host = i486-pc-linux-gnu +host_alias = +host_cpu = i486 +host_os = linux-gnu +host_vendor = pc +htmldir = ${docdir} +includedir = ${prefix}/include +infodir = ${datarootdir}/info +install_sh = $(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh +libdir = ${exec_prefix}/lib +libexecdir = ${exec_prefix}/libexec +localedir = ${datarootdir}/locale +localstatedir = ${prefix}/var +mandir = /usr/share/man +mkdir_p = /bin/mkdir -p +oldincludedir = /usr/include +pdfdir = ${docdir} +prefix = /usr +program_transform_name = s,x,x, +psdir = ${docdir} +sbindir = ${exec_prefix}/sbin +sharedstatedir = ${prefix}/com +srcdir = .. +sysconfdir = /etc +target_alias = +top_build_prefix = +top_builddir = . +top_srcdir = .. +AUTOMAKE_OPTIONS = 1.6 foreign +IMAP_SUBDIR = imap +IMAP_INCLUDES = -I$(top_srcdir)/imap +SUBDIRS = m4 po intl doc contrib $(IMAP_SUBDIR) +bin_SCRIPTS = muttbug flea smime_keys +BUILT_SOURCES = keymap_defs.h patchlist.c reldate.h hcversion.h +mutt_SOURCES = \ + addrbook.c alias.c attach.c base64.c browser.c buffy.c color.c \ + crypt.c cryptglue.c compress.c \ + commands.c complete.c compose.c copy.c curs_lib.c curs_main.c date.c \ + edit.c enter.c flags.c init.c filter.c from.c \ + getdomain.c group.c \ + handler.c hash.c hdrline.c headers.c help.c hook.c keymap.c \ + main.c mbox.c menu.c mh.c mx.c pager.c parse.c pattern.c \ + postpone.c query.c recvattach.c recvcmd.c \ + rfc822.c rfc1524.c rfc2047.c rfc2231.c rfc3676.c \ + score.c send.c sendlib.c signal.c sort.c \ + status.c system.c thread.c charset.c history.c lib.c \ + muttlib.c editmsg.c mbyte.c \ + url.c ascii.c crypt-mod.c crypt-mod.h \ + sidebar.c + +nodist_mutt_SOURCES = $(BUILT_SOURCES) +mutt_LDADD = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o $(LIBIMAP) $(MUTTLIBS) \ + $(INTLLIBS) $(LIBICONV) $(GPGME_LIBS) + +mutt_DEPENDENCIES = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o $(LIBIMAPDEPS) \ + $(INTLDEPS) + +AM_CPPFLAGS = -I. -I$(top_srcdir) $(IMAP_INCLUDES) $(GPGME_CFLAGS) -Iintl +EXTRA_mutt_SOURCES = account.c bcache.c crypt-gpgme.c crypt-mod-pgp-classic.c \ + crypt-mod-pgp-gpgme.c crypt-mod-smime-classic.c \ + crypt-mod-smime-gpgme.c dotlock.c gnupgparse.c hcache.c md5.c \ + mutt_idna.c mutt_sasl.c mutt_socket.c mutt_ssl.c mutt_ssl_gnutls.c \ + mutt_tunnel.c pgp.c pgpinvoke.c pgpkey.c pgplib.c pgpmicalg.c \ + pgppacket.c pop.c pop_auth.c pop_lib.c remailer.c resize.c sha1.c \ + smime.c smtp.c utf8.c wcwidth.c \ + bcache.h browser.h hcache.h mbyte.h mutt_idna.h remailer.h url.h + +EXTRA_DIST = COPYRIGHT GPL OPS OPS.PGP OPS.CRYPT OPS.SMIME TODO UPDATING \ + configure account.h compress.h \ + attach.h buffy.h charset.h copy.h crypthash.h dotlock.h functions.h gen_defs \ + globals.h hash.h history.h init.h keymap.h mutt_crypt.h \ + mailbox.h mapping.h md5.h mime.h mutt.h mutt_curses.h mutt_menu.h \ + mutt_regex.h mutt_sasl.h mutt_socket.h mutt_ssl.h mutt_tunnel.h \ + mx.h pager.h pgp.h pop.h protos.h rfc1524.h rfc2047.h \ + rfc2231.h rfc822.h rfc3676.h sha1.h sort.h mime.types VERSION prepare \ + _regex.h OPS.MIX README.SECURITY remailer.c remailer.h browser.h \ + mbyte.h lib.h extlib.c pgpewrap.c smime_keys.pl pgplib.h \ + README.SSL smime.h \ + muttbug pgppacket.h depcomp ascii.h BEWARE PATCHES patchlist.sh \ + ChangeLog mkchangelog.sh mutt_idna.h \ + snprintf.c regex.c crypt-gpgme.h hcachever.sh.in + +EXTRA_SCRIPTS = smime_keys +mutt_dotlock_SOURCES = mutt_dotlock.c +mutt_dotlock_LDADD = +mutt_dotlock_DEPENDENCIES = +pgpring_SOURCES = pgppubring.c pgplib.c lib.c extlib.c sha1.c md5.c pgppacket.c ascii.c +pgpring_LDADD = $(INTLLIBS) +pgpring_DEPENDENCIES = $(INTLDEPS) +mutt_md5_SOURCES = md5.c +mutt_md5_CFLAGS = -DMD5UTIL +mutt_md5_LDADD = +noinst_PROGRAMS = $(MUTT_MD5) +CLEANFILES = mutt_dotlock.c keymap_alldefs.h $(BUILT_SOURCES) +DISTCLEANFILES = flea smime_keys +ACLOCAL_AMFLAGS = -I m4 +LDADD = +all: $(BUILT_SOURCES) config.h + $(MAKE) $(AM_MAKEFLAGS) all-recursive + +.SUFFIXES: +.SUFFIXES: .c .o .obj +am--refresh: + @: +$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am $(am__configure_deps) + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + echo ' cd $(srcdir) && $(AUTOMAKE) --foreign '; \ + cd $(srcdir) && $(AUTOMAKE) --foreign \ + && exit 0; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --foreign Makefile +.PRECIOUS: Makefile +Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status + @case '$?' in \ + *config.status*) \ + echo ' $(SHELL) ./config.status'; \ + $(SHELL) ./config.status;; \ + *) \ + echo ' cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe)'; \ + cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe);; \ + esac; + +$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) + $(SHELL) ./config.status --recheck + +$(top_srcdir)/configure: # $(am__configure_deps) + cd $(srcdir) && $(AUTOCONF) +$(ACLOCAL_M4): # $(am__aclocal_m4_deps) + cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS) + +config.h: stamp-h1 + @if test ! -f $@; then \ + rm -f stamp-h1; \ + $(MAKE) $(AM_MAKEFLAGS) stamp-h1; \ + else :; fi + +stamp-h1: $(srcdir)/config.h.in $(top_builddir)/config.status + @rm -f stamp-h1 + cd $(top_builddir) && $(SHELL) ./config.status config.h +$(srcdir)/config.h.in: # $(am__configure_deps) + cd $(top_srcdir) && $(AUTOHEADER) + rm -f stamp-h1 + touch $@ + +distclean-hdr: + -rm -f config.h stamp-h1 +intl/Makefile: $(top_builddir)/config.status $(top_srcdir)/intl/Makefile.in + cd $(top_builddir) && $(SHELL) ./config.status $@ +hcachever.sh: $(top_builddir)/config.status $(srcdir)/hcachever.sh.in + cd $(top_builddir) && $(SHELL) ./config.status $@ +muttbug.sh: $(top_builddir)/config.status $(srcdir)/muttbug.sh.in + cd $(top_builddir) && $(SHELL) ./config.status $@ +install-binPROGRAMS: $(bin_PROGRAMS) + @$(NORMAL_INSTALL) + test -z "$(bindir)" || $(MKDIR_P) "$(DESTDIR)$(bindir)" + @list='$(bin_PROGRAMS)'; for p in $$list; do \ + p1=`echo $$p|sed 's/$(EXEEXT)$$//'`; \ + if test -f $$p \ + ; then \ + f=`echo "$$p1" | sed 's,^.*/,,;$(transform);s/$$/$(EXEEXT)/'`; \ + echo " $(INSTALL_PROGRAM_ENV) $(binPROGRAMS_INSTALL) '$$p' '$(DESTDIR)$(bindir)/$$f'"; \ + $(INSTALL_PROGRAM_ENV) $(binPROGRAMS_INSTALL) "$$p" "$(DESTDIR)$(bindir)/$$f" || exit 1; \ + else :; fi; \ + done + +uninstall-binPROGRAMS: + @$(NORMAL_UNINSTALL) + @list='$(bin_PROGRAMS)'; for p in $$list; do \ + f=`echo "$$p" | sed 's,^.*/,,;s/$(EXEEXT)$$//;$(transform);s/$$/$(EXEEXT)/'`; \ + echo " rm -f '$(DESTDIR)$(bindir)/$$f'"; \ + rm -f "$(DESTDIR)$(bindir)/$$f"; \ + done + +clean-binPROGRAMS: + -test -z "$(bin_PROGRAMS)" || rm -f $(bin_PROGRAMS) + +clean-noinstPROGRAMS: + -test -z "$(noinst_PROGRAMS)" || rm -f $(noinst_PROGRAMS) +mutt$(EXEEXT): $(mutt_OBJECTS) $(mutt_DEPENDENCIES) + @rm -f mutt$(EXEEXT) + $(LINK) $(mutt_OBJECTS) $(mutt_LDADD) $(LIBS) +mutt_dotlock$(EXEEXT): $(mutt_dotlock_OBJECTS) $(mutt_dotlock_DEPENDENCIES) + @rm -f mutt_dotlock$(EXEEXT) + $(LINK) $(mutt_dotlock_OBJECTS) $(mutt_dotlock_LDADD) $(LIBS) +mutt_md5$(EXEEXT): $(mutt_md5_OBJECTS) $(mutt_md5_DEPENDENCIES) + @rm -f mutt_md5$(EXEEXT) + $(mutt_md5_LINK) $(mutt_md5_OBJECTS) $(mutt_md5_LDADD) $(LIBS) +pgpewrap$(EXEEXT): $(pgpewrap_OBJECTS) $(pgpewrap_DEPENDENCIES) + @rm -f pgpewrap$(EXEEXT) + $(LINK) $(pgpewrap_OBJECTS) $(pgpewrap_LDADD) $(LIBS) +pgpring$(EXEEXT): $(pgpring_OBJECTS) $(pgpring_DEPENDENCIES) + @rm -f pgpring$(EXEEXT) + $(LINK) $(pgpring_OBJECTS) $(pgpring_LDADD) $(LIBS) +install-binSCRIPTS: $(bin_SCRIPTS) + @$(NORMAL_INSTALL) + test -z "$(bindir)" || $(MKDIR_P) "$(DESTDIR)$(bindir)" + @list='$(bin_SCRIPTS)'; for p in $$list; do \ + if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \ + if test -f $$d$$p; then \ + f=`echo "$$p" | sed 's|^.*/||;$(transform)'`; \ + echo " $(binSCRIPT_INSTALL) '$$d$$p' '$(DESTDIR)$(bindir)/$$f'"; \ + $(binSCRIPT_INSTALL) "$$d$$p" "$(DESTDIR)$(bindir)/$$f"; \ + else :; fi; \ + done + +uninstall-binSCRIPTS: + @$(NORMAL_UNINSTALL) + @list='$(bin_SCRIPTS)'; for p in $$list; do \ + f=`echo "$$p" | sed 's|^.*/||;$(transform)'`; \ + echo " rm -f '$(DESTDIR)$(bindir)/$$f'"; \ + rm -f "$(DESTDIR)$(bindir)/$$f"; \ + done + +mostlyclean-compile: + -rm -f *.$(OBJEXT) + +distclean-compile: + -rm -f *.tab.c + +#include $(DEPDIR)/regex.Po +#include $(DEPDIR)/setenv.Po +#include $(DEPDIR)/snprintf.Po +#include $(DEPDIR)/strcasecmp.Po +#include $(DEPDIR)/strdup.Po +#include $(DEPDIR)/strsep.Po +#include $(DEPDIR)/strtok_r.Po +#include ./$(DEPDIR)/account.Po +#include ./$(DEPDIR)/addrbook.Po +#include ./$(DEPDIR)/alias.Po +#include ./$(DEPDIR)/ascii.Po +#include ./$(DEPDIR)/attach.Po +#include ./$(DEPDIR)/base64.Po +#include ./$(DEPDIR)/bcache.Po +#include ./$(DEPDIR)/browser.Po +#include ./$(DEPDIR)/buffy.Po +#include ./$(DEPDIR)/charset.Po +#include ./$(DEPDIR)/color.Po +#include ./$(DEPDIR)/commands.Po +#include ./$(DEPDIR)/complete.Po +#include ./$(DEPDIR)/compose.Po +#include ./$(DEPDIR)/compress.Po +#include ./$(DEPDIR)/copy.Po +#include ./$(DEPDIR)/crypt-gpgme.Po +#include ./$(DEPDIR)/crypt-mod-pgp-classic.Po +#include ./$(DEPDIR)/crypt-mod-pgp-gpgme.Po +#include ./$(DEPDIR)/crypt-mod-smime-classic.Po +#include ./$(DEPDIR)/crypt-mod-smime-gpgme.Po +#include ./$(DEPDIR)/crypt-mod.Po +#include ./$(DEPDIR)/crypt.Po +#include ./$(DEPDIR)/cryptglue.Po +#include ./$(DEPDIR)/curs_lib.Po +#include ./$(DEPDIR)/curs_main.Po +#include ./$(DEPDIR)/date.Po +#include ./$(DEPDIR)/dotlock.Po +#include ./$(DEPDIR)/edit.Po +#include ./$(DEPDIR)/editmsg.Po +#include ./$(DEPDIR)/enter.Po +#include ./$(DEPDIR)/extlib.Po +#include ./$(DEPDIR)/filter.Po +#include ./$(DEPDIR)/flags.Po +#include ./$(DEPDIR)/from.Po +#include ./$(DEPDIR)/getdomain.Po +#include ./$(DEPDIR)/gnupgparse.Po +#include ./$(DEPDIR)/group.Po +#include ./$(DEPDIR)/handler.Po +#include ./$(DEPDIR)/hash.Po +#include ./$(DEPDIR)/hcache.Po +#include ./$(DEPDIR)/hdrline.Po +#include ./$(DEPDIR)/headers.Po +#include ./$(DEPDIR)/help.Po +#include ./$(DEPDIR)/history.Po +#include ./$(DEPDIR)/hook.Po +#include ./$(DEPDIR)/init.Po +#include ./$(DEPDIR)/keymap.Po +#include ./$(DEPDIR)/lib.Po +#include ./$(DEPDIR)/main.Po +#include ./$(DEPDIR)/mbox.Po +#include ./$(DEPDIR)/mbyte.Po +#include ./$(DEPDIR)/md5.Po +#include ./$(DEPDIR)/menu.Po +#include ./$(DEPDIR)/mh.Po +#include ./$(DEPDIR)/mutt_dotlock.Po +#include ./$(DEPDIR)/mutt_idna.Po +#include ./$(DEPDIR)/mutt_md5-md5.Po +#include ./$(DEPDIR)/mutt_sasl.Po +#include ./$(DEPDIR)/mutt_socket.Po +#include ./$(DEPDIR)/mutt_ssl.Po +#include ./$(DEPDIR)/mutt_ssl_gnutls.Po +#include ./$(DEPDIR)/mutt_tunnel.Po +#include ./$(DEPDIR)/muttlib.Po +#include ./$(DEPDIR)/mx.Po +#include ./$(DEPDIR)/pager.Po +#include ./$(DEPDIR)/parse.Po +#include ./$(DEPDIR)/patchlist.Po +#include ./$(DEPDIR)/pattern.Po +#include ./$(DEPDIR)/pgp.Po +#include ./$(DEPDIR)/pgpewrap.Po +#include ./$(DEPDIR)/pgpinvoke.Po +#include ./$(DEPDIR)/pgpkey.Po +#include ./$(DEPDIR)/pgplib.Po +#include ./$(DEPDIR)/pgpmicalg.Po +#include ./$(DEPDIR)/pgppacket.Po +#include ./$(DEPDIR)/pgppubring.Po +#include ./$(DEPDIR)/pop.Po +#include ./$(DEPDIR)/pop_auth.Po +#include ./$(DEPDIR)/pop_lib.Po +#include ./$(DEPDIR)/postpone.Po +#include ./$(DEPDIR)/query.Po +#include ./$(DEPDIR)/recvattach.Po +#include ./$(DEPDIR)/recvcmd.Po +#include ./$(DEPDIR)/remailer.Po +#include ./$(DEPDIR)/resize.Po +#include ./$(DEPDIR)/rfc1524.Po +#include ./$(DEPDIR)/rfc2047.Po +#include ./$(DEPDIR)/rfc2231.Po +#include ./$(DEPDIR)/rfc3676.Po +#include ./$(DEPDIR)/rfc822.Po +#include ./$(DEPDIR)/score.Po +#include ./$(DEPDIR)/send.Po +#include ./$(DEPDIR)/sendlib.Po +#include ./$(DEPDIR)/sha1.Po +#include ./$(DEPDIR)/sidebar.Po +#include ./$(DEPDIR)/signal.Po +#include ./$(DEPDIR)/smime.Po +#include ./$(DEPDIR)/smtp.Po +#include ./$(DEPDIR)/sort.Po +#include ./$(DEPDIR)/status.Po +#include ./$(DEPDIR)/system.Po +#include ./$(DEPDIR)/thread.Po +#include ./$(DEPDIR)/url.Po +#include ./$(DEPDIR)/utf8.Po +#include ./$(DEPDIR)/wcwidth.Po + +.c.o: +# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $< +# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po +# source='$<' object='$@' libtool=no +# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) + $(COMPILE) -c $< + +.c.obj: +# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ `$(CYGPATH_W) '$<'` +# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po +# source='$<' object='$@' libtool=no +# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) + $(COMPILE) -c `$(CYGPATH_W) '$<'` + +mutt_md5-md5.o: md5.c +# $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -MT mutt_md5-md5.o -MD -MP -MF $(DEPDIR)/mutt_md5-md5.Tpo -c -o mutt_md5-md5.o `test -f 'md5.c' || echo '$(srcdir)/'`md5.c +# mv -f $(DEPDIR)/mutt_md5-md5.Tpo $(DEPDIR)/mutt_md5-md5.Po +# source='md5.c' object='mutt_md5-md5.o' libtool=no +# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) + $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -c -o mutt_md5-md5.o `test -f 'md5.c' || echo '$(srcdir)/'`md5.c + +mutt_md5-md5.obj: md5.c +# $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -MT mutt_md5-md5.obj -MD -MP -MF $(DEPDIR)/mutt_md5-md5.Tpo -c -o mutt_md5-md5.obj `if test -f 'md5.c'; then $(CYGPATH_W) 'md5.c'; else $(CYGPATH_W) '$(srcdir)/md5.c'; fi` +# mv -f $(DEPDIR)/mutt_md5-md5.Tpo $(DEPDIR)/mutt_md5-md5.Po +# source='md5.c' object='mutt_md5-md5.obj' libtool=no +# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) + $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -c -o mutt_md5-md5.obj `if test -f 'md5.c'; then $(CYGPATH_W) 'md5.c'; else $(CYGPATH_W) '$(srcdir)/md5.c'; fi` + +# This directory's subdirectories are mostly independent; you can cd +# into them and run `make' without going through this Makefile. +# To change the values of `make' variables: instead of editing Makefiles, +# (1) if the variable is set in `config.status', edit `config.status' +# (which will cause the Makefiles to be regenerated when you run `make'); +# (2) otherwise, pass the desired values on the `make' command line. +$(RECURSIVE_TARGETS): + @failcom='exit 1'; \ + for f in x $$MAKEFLAGS; do \ + case $$f in \ + *=* | --[!k]*);; \ + *k*) failcom='fail=yes';; \ + esac; \ + done; \ + dot_seen=no; \ + target=`echo $@ | sed s/-recursive//`; \ + list='$(SUBDIRS)'; for subdir in $$list; do \ + echo "Making $$target in $$subdir"; \ + if test "$$subdir" = "."; then \ + dot_seen=yes; \ + local_target="$$target-am"; \ + else \ + local_target="$$target"; \ + fi; \ + (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \ + || eval $$failcom; \ + done; \ + if test "$$dot_seen" = "no"; then \ + $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \ + fi; test -z "$$fail" + +$(RECURSIVE_CLEAN_TARGETS): + @failcom='exit 1'; \ + for f in x $$MAKEFLAGS; do \ + case $$f in \ + *=* | --[!k]*);; \ + *k*) failcom='fail=yes';; \ + esac; \ + done; \ + dot_seen=no; \ + case "$@" in \ + distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \ + *) list='$(SUBDIRS)' ;; \ + esac; \ + rev=''; for subdir in $$list; do \ + if test "$$subdir" = "."; then :; else \ + rev="$$subdir $$rev"; \ + fi; \ + done; \ + rev="$$rev ."; \ + target=`echo $@ | sed s/-recursive//`; \ + for subdir in $$rev; do \ + echo "Making $$target in $$subdir"; \ + if test "$$subdir" = "."; then \ + local_target="$$target-am"; \ + else \ + local_target="$$target"; \ + fi; \ + (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \ + || eval $$failcom; \ + done && test -z "$$fail" +tags-recursive: + list='$(SUBDIRS)'; for subdir in $$list; do \ + test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \ + done +ctags-recursive: + list='$(SUBDIRS)'; for subdir in $$list; do \ + test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \ + done + +ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES) + list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | \ + $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \ + END { if (nonempty) { for (i in files) print i; }; }'`; \ + mkid -fID $$unique +tags: TAGS + +TAGS: tags-recursive $(HEADERS) $(SOURCES) config.h.in $(TAGS_DEPENDENCIES) \ + $(TAGS_FILES) $(LISP) + tags=; \ + here=`pwd`; \ + if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \ + include_option=--etags-include; \ + empty_fix=.; \ + else \ + include_option=--include; \ + empty_fix=; \ + fi; \ + list='$(SUBDIRS)'; for subdir in $$list; do \ + if test "$$subdir" = .; then :; else \ + test ! -f $$subdir/TAGS || \ + tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \ + fi; \ + done; \ + list='$(SOURCES) $(HEADERS) config.h.in $(LISP) $(TAGS_FILES)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | \ + $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ + END { if (nonempty) { for (i in files) print i; }; }'`; \ + if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \ + test -n "$$unique" || unique=$$empty_fix; \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + $$tags $$unique; \ + fi +ctags: CTAGS +CTAGS: ctags-recursive $(HEADERS) $(SOURCES) config.h.in $(TAGS_DEPENDENCIES) \ + $(TAGS_FILES) $(LISP) + tags=; \ + list='$(SOURCES) $(HEADERS) config.h.in $(LISP) $(TAGS_FILES)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | \ + $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ + END { if (nonempty) { for (i in files) print i; }; }'`; \ + test -z "$(CTAGS_ARGS)$$tags$$unique" \ + || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \ + $$tags $$unique + +GTAGS: + here=`$(am__cd) $(top_builddir) && pwd` \ + && cd $(top_srcdir) \ + && gtags -i $(GTAGS_ARGS) $$here + +distclean-tags: + -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags + +distdir: $(DISTFILES) + $(am__remove_distdir) + test -d $(distdir) || mkdir $(distdir) + @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + list='$(DISTFILES)'; \ + dist_files=`for file in $$list; do echo $$file; done | \ + sed -e "s|^$$srcdirstrip/||;t" \ + -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \ + case $$dist_files in \ + */*) $(MKDIR_P) `echo "$$dist_files" | \ + sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \ + sort -u` ;; \ + esac; \ + for file in $$dist_files; do \ + if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ + if test -d $$d/$$file; then \ + dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ + cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \ + fi; \ + cp -pR $$d/$$file $(distdir)$$dir || exit 1; \ + else \ + test -f $(distdir)/$$file \ + || cp -p $$d/$$file $(distdir)/$$file \ + || exit 1; \ + fi; \ + done + list='$(DIST_SUBDIRS)'; for subdir in $$list; do \ + if test "$$subdir" = .; then :; else \ + test -d "$(distdir)/$$subdir" \ + || $(MKDIR_P) "$(distdir)/$$subdir" \ + || exit 1; \ + distdir=`$(am__cd) $(distdir) && pwd`; \ + top_distdir=`$(am__cd) $(top_distdir) && pwd`; \ + (cd $$subdir && \ + $(MAKE) $(AM_MAKEFLAGS) \ + top_distdir="$$top_distdir" \ + distdir="$$distdir/$$subdir" \ + am__remove_distdir=: \ + am__skip_length_check=: \ + distdir) \ + || exit 1; \ + fi; \ + done + -find $(distdir) -type d ! -perm -777 -exec chmod a+rwx {} \; -o \ + ! -type d ! -perm -444 -links 1 -exec chmod a+r {} \; -o \ + ! -type d ! -perm -400 -exec chmod a+r {} \; -o \ + ! -type d ! -perm -444 -exec $(install_sh) -c -m a+r {} {} \; \ + || chmod -R a+r $(distdir) +dist-gzip: distdir + tardir=$(distdir) && $(am__tar) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz + $(am__remove_distdir) + +dist-bzip2: distdir + tardir=$(distdir) && $(am__tar) | bzip2 -9 -c >$(distdir).tar.bz2 + $(am__remove_distdir) + +dist-lzma: distdir + tardir=$(distdir) && $(am__tar) | lzma -9 -c >$(distdir).tar.lzma + $(am__remove_distdir) + +dist-tarZ: distdir + tardir=$(distdir) && $(am__tar) | compress -c >$(distdir).tar.Z + $(am__remove_distdir) + +dist-shar: distdir + shar $(distdir) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).shar.gz + $(am__remove_distdir) + +dist-zip: distdir + -rm -f $(distdir).zip + zip -rq $(distdir).zip $(distdir) + $(am__remove_distdir) + +dist dist-all: distdir + tardir=$(distdir) && $(am__tar) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz + $(am__remove_distdir) + +# This target untars the dist file and tries a VPATH configuration. Then +# it guarantees that the distribution is self-contained by making another +# tarfile. +distcheck: dist + case '$(DIST_ARCHIVES)' in \ + *.tar.gz*) \ + GZIP=$(GZIP_ENV) gunzip -c $(distdir).tar.gz | $(am__untar) ;;\ + *.tar.bz2*) \ + bunzip2 -c $(distdir).tar.bz2 | $(am__untar) ;;\ + *.tar.lzma*) \ + unlzma -c $(distdir).tar.lzma | $(am__untar) ;;\ + *.tar.Z*) \ + uncompress -c $(distdir).tar.Z | $(am__untar) ;;\ + *.shar.gz*) \ + GZIP=$(GZIP_ENV) gunzip -c $(distdir).shar.gz | unshar ;;\ + *.zip*) \ + unzip $(distdir).zip ;;\ + esac + chmod -R a-w $(distdir); chmod a+w $(distdir) + mkdir $(distdir)/_build + mkdir $(distdir)/_inst + chmod a-w $(distdir) + dc_install_base=`$(am__cd) $(distdir)/_inst && pwd | sed -e 's,^[^:\\/]:[\\/],/,'` \ + && dc_destdir="$${TMPDIR-/tmp}/am-dc-$$$$/" \ + && cd $(distdir)/_build \ + && ../configure --srcdir=.. --prefix="$$dc_install_base" \ + $(DISTCHECK_CONFIGURE_FLAGS) \ + && $(MAKE) $(AM_MAKEFLAGS) \ + && $(MAKE) $(AM_MAKEFLAGS) dvi \ + && $(MAKE) $(AM_MAKEFLAGS) check \ + && $(MAKE) $(AM_MAKEFLAGS) install \ + && $(MAKE) $(AM_MAKEFLAGS) installcheck \ + && $(MAKE) $(AM_MAKEFLAGS) uninstall \ + && $(MAKE) $(AM_MAKEFLAGS) distuninstallcheck_dir="$$dc_install_base" \ + distuninstallcheck \ + && chmod -R a-w "$$dc_install_base" \ + && ({ \ + (cd ../.. && umask 077 && mkdir "$$dc_destdir") \ + && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" install \ + && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" uninstall \ + && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" \ + distuninstallcheck_dir="$$dc_destdir" distuninstallcheck; \ + } || { rm -rf "$$dc_destdir"; exit 1; }) \ + && rm -rf "$$dc_destdir" \ + && $(MAKE) $(AM_MAKEFLAGS) dist \ + && rm -rf $(DIST_ARCHIVES) \ + && $(MAKE) $(AM_MAKEFLAGS) distcleancheck + $(am__remove_distdir) + @(echo "$(distdir) archives ready for distribution: "; \ + list='$(DIST_ARCHIVES)'; for i in $$list; do echo $$i; done) | \ + sed -e 1h -e 1s/./=/g -e 1p -e 1x -e '$$p' -e '$$x' +distuninstallcheck: + @cd $(distuninstallcheck_dir) \ + && test `$(distuninstallcheck_listfiles) | wc -l` -le 1 \ + || { echo "ERROR: files left after uninstall:" ; \ + if test -n "$(DESTDIR)"; then \ + echo " (check DESTDIR support)"; \ + fi ; \ + $(distuninstallcheck_listfiles) ; \ + exit 1; } >&2 +distcleancheck: distclean + @if test '$(srcdir)' = . ; then \ + echo "ERROR: distcleancheck can only run from a VPATH build" ; \ + exit 1 ; \ + fi + @test `$(distcleancheck_listfiles) | wc -l` -eq 0 \ + || { echo "ERROR: files left in build directory after distclean:" ; \ + $(distcleancheck_listfiles) ; \ + exit 1; } >&2 +check-am: all-am +check: $(BUILT_SOURCES) + $(MAKE) $(AM_MAKEFLAGS) check-recursive +all-am: Makefile $(PROGRAMS) $(SCRIPTS) config.h +installdirs: installdirs-recursive +installdirs-am: + for dir in "$(DESTDIR)$(bindir)" "$(DESTDIR)$(bindir)"; do \ + test -z "$$dir" || $(MKDIR_P) "$$dir"; \ + done +install: $(BUILT_SOURCES) + $(MAKE) $(AM_MAKEFLAGS) install-recursive +install-exec: install-exec-recursive +install-data: install-data-recursive +uninstall: uninstall-recursive + +install-am: all-am + @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am + +installcheck: installcheck-recursive +install-strip: + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + `test -z '$(STRIP)' || \ + echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install +mostlyclean-generic: + +clean-generic: + -test -z "$(CLEANFILES)" || rm -f $(CLEANFILES) + +distclean-generic: + -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test -z "$(DISTCLEANFILES)" || rm -f $(DISTCLEANFILES) + +maintainer-clean-generic: + @echo "This command is intended for maintainers to use" + @echo "it deletes files that may require special tools to rebuild." + -test -z "$(BUILT_SOURCES)" || rm -f $(BUILT_SOURCES) +clean: clean-recursive + +clean-am: clean-binPROGRAMS clean-generic clean-noinstPROGRAMS \ + mostlyclean-am + +distclean: distclean-recursive + -rm -f $(am__CONFIG_DISTCLEAN_FILES) + -rm -rf $(DEPDIR) ./$(DEPDIR) + -rm -f Makefile +distclean-am: clean-am distclean-compile distclean-generic \ + distclean-hdr distclean-tags + +dvi: dvi-recursive + +dvi-am: + +html: html-recursive + +info: info-recursive + +info-am: + +install-data-am: install-data-local + +install-dvi: install-dvi-recursive + +install-exec-am: install-binPROGRAMS install-binSCRIPTS + @$(NORMAL_INSTALL) + $(MAKE) $(AM_MAKEFLAGS) install-exec-hook + +install-html: install-html-recursive + +install-info: install-info-recursive + +install-man: + +install-pdf: install-pdf-recursive + +install-ps: install-ps-recursive + +installcheck-am: + +maintainer-clean: maintainer-clean-recursive + -rm -f $(am__CONFIG_DISTCLEAN_FILES) + -rm -rf $(top_srcdir)/autom4te.cache + -rm -rf $(DEPDIR) ./$(DEPDIR) + -rm -f Makefile +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-recursive + +mostlyclean-am: mostlyclean-compile mostlyclean-generic + +pdf: pdf-recursive + +pdf-am: + +ps: ps-recursive + +ps-am: + +uninstall-am: uninstall-binPROGRAMS uninstall-binSCRIPTS \ + uninstall-local + +.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \ + install-exec-am install-strip + +.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \ + all all-am am--refresh check check-am clean clean-binPROGRAMS \ + clean-generic clean-noinstPROGRAMS ctags ctags-recursive dist \ + dist-all dist-bzip2 dist-gzip dist-lzma dist-shar dist-tarZ \ + dist-zip distcheck distclean distclean-compile \ + distclean-generic distclean-hdr distclean-tags distcleancheck \ + distdir distuninstallcheck dvi dvi-am html html-am info \ + info-am install install-am install-binPROGRAMS \ + install-binSCRIPTS install-data install-data-am \ + install-data-local install-dvi install-dvi-am install-exec \ + install-exec-am install-exec-hook install-html install-html-am \ + install-info install-info-am install-man install-pdf \ + install-pdf-am install-ps install-ps-am install-strip \ + installcheck installcheck-am installdirs installdirs-am \ + maintainer-clean maintainer-clean-generic mostlyclean \ + mostlyclean-compile mostlyclean-generic pdf pdf-am ps ps-am \ + tags tags-recursive uninstall uninstall-am \ + uninstall-binPROGRAMS uninstall-binSCRIPTS uninstall-local + + +mutt_dotlock.c: dotlock.c + cp $(srcdir)/dotlock.c mutt_dotlock.c + +flea: muttbug.sh + cp muttbug.sh flea + chmod +x flea + +smime_keys: $(srcdir)/smime_keys.pl + cp $(srcdir)/smime_keys.pl smime_keys + chmod +x smime_keys + +keymap_defs.h: $(OPS) $(srcdir)/gen_defs + $(srcdir)/gen_defs $(OPS) > keymap_defs.h + +keymap_alldefs.h: $(srcdir)/OPS $(srcdir)/OPS.PGP $(srcdir)/OPS.MIX $(srcdir)/OPS.CRYPT $(srcdir)/OPS.SMIME $(srcdir)/gen_defs + rm -f $@ + $(srcdir)/gen_defs $(srcdir)/OPS $(srcdir)/OPS.PGP \ + $(srcdir)/OPS.MIX $(srcdir)/OPS.CRYPT $(srcdir)/OPS.SMIME \ + > keymap_alldefs.h + +reldate.h: $(srcdir)/ChangeLog + echo 'const char *ReleaseDate = "'`head -n 1 $(srcdir)/ChangeLog | LC_ALL=C cut -d ' ' -f 1`'";' > reldate.h.tmp; \ + cmp -s reldate.h.tmp reldate.h || cp reldate.h.tmp reldate.h; \ + rm reldate.h.tmp + +hcversion.h: $(srcdir)/mutt.h $(srcdir)/rfc822.h hcachever.sh $(MUTT_MD5) + ( echo '#include "config.h"'; echo '#include "mutt.h"'; ) \ + | $(CPP) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) - | sh ./hcachever.sh hcversion.h + +patchlist.c: $(srcdir)/PATCHES $(srcdir)/patchlist.sh + $(srcdir)/patchlist.sh < $(srcdir)/PATCHES > patchlist.c + +install-exec-hook: + if test -f $(DESTDIR)$(bindir)/mutt.dotlock && test -f $(DESTDIR)$(bindir)/mutt_dotlock ; then \ + rm -f $(DESTDIR)$(bindir)/mutt.dotlock ; \ + ln -sf $(DESTDIR)$(bindir)/mutt_dotlock $(DESTDIR)$(bindir)/mutt.dotlock ; \ + fi + if test -f $(DESTDIR)$(bindir)/mutt_dotlock && test xmail != x ; then \ + chgrp mail $(DESTDIR)$(bindir)/mutt_dotlock && \ + chmod 2755 $(DESTDIR)$(bindir)/mutt_dotlock || \ + { echo "Can't fix mutt_dotlock's permissions!" >&2 ; exit 1 ; } \ + fi + +install-data-local: + $(srcdir)/mkinstalldirs $(DESTDIR)$(sysconfdir) + $(INSTALL) -m 644 $(srcdir)/mime.types $(DESTDIR)$(sysconfdir)/mime.types.dist + -if [ ! -f $(DESTDIR)$(sysconfdir)/mime.types ]; then \ + $(INSTALL) -m 644 $(srcdir)/mime.types $(DESTDIR)$(sysconfdir); \ + fi + +uninstall-local: + for i in mime.types ; do \ + if cmp -s $(DESTDIR)$(sysconfdir)/$$i.dist $(DESTDIR)$(sysconfdir)/$$i ; then \ + rm $(DESTDIR)$(sysconfdir)/$$i ; \ + fi ; \ + rm $(DESTDIR)$(sysconfdir)/$${i}.dist ; \ + done + +pclean: + cat /dev/null > $(top_srcdir)/PATCHES + +check-security: + (cd $(top_srcdir) && ./check_sec.sh) + +commit: + @echo "make commit is obsolete; use hg-commit"; false + +update-changelog: + (cd $(top_srcdir); \ + sh ./mkchangelog.sh | cat - ChangeLog > ChangeLog.$$$$ && mv ChangeLog.$$$$ ChangeLog; \ + $${VISUAL:-vi} ChangeLog) + +mutt-dist: + (cd $(srcdir) && ./build-release ) + +update-doc: + (cd doc && $(MAKE) update-doc) + +.PHONY: commit pclean check-security +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: diff --git a/obj-i486-linux-gnu-patched/account.o b/obj-i486-linux-gnu-patched/account.o new file mode 100644 index 0000000000000000000000000000000000000000..283c445e4c2526300bc090ed7f140e103dec3f03 GIT binary patch literal 10648 zcma)C33OCdn!c~zOY({;NI}>^3=-U_5Q%$~#1J470z!g_U|C5j3nZzSdKJKN$rwP( z7$FVg(q|l())w21>9)~>+GfNSoauHvwsK}h=d`x%bmKCE+Cwv~HuHV={jZixPtUxQ zs_*{$fB(C@`(EYNn!3e?VJPo1l&Lb5QuobpCFL5f^!X!NErRkYR&y zsLCSyP!$Q)dZ;R-RN?;Hu7Jx5!&z0~bGj?c!fiVs9J*};->Iq~9{3#GLA-1o;*49-08GGq-!H?k5*Ek{T?#RjJu;HX+G;wWA{JA z9{qm9!Cj3nKy)(o@tV~GpM?gK!NCpo;F{p}w+puo!+vOBgfSMC*!{p%Ly48LN`Ctd zEM6a22oGv-v9*1~Ih7if)K~lIyBG^y|lh~b9L?42VQ|t z6+XWvR5sGO{cR`Y3Jg%G-K_k;YoTke(}f*+=?v;Nmc5<&_%A=(i)JeM&0x|_Z8%Z5 z|89mp{&#lr%EJ9SWN?>P_zJiEEA%SNn=K-i%IXkQL$e>RY7@7A8p9h)fV~emDoy zMy#Erg*vn1v>iBX?X~XEWb*k>|7w?)&+i6LVW(2b6P(jGe=~S3)NQ{aTL^rRRS%YaN7 z_hEZEYi?Op+ZBZ#)jyoLbool1lHo24R&eRfD?q_Hj>D1CZel?Te!L_I*W@q3vW?dGABVca)sFDidY&a@iGM!HQ-wU!eL{~WqH*SJx4u+slEvzl*QuE|CIb}E+{b(&o4f182M zGk&B!FYzCt@&(30O)mBSoURrccWLE1|4r=CQscXtZ14||tQB&t|4x!u3c21tOmdl! z*Zc1yS!c}Ewk`e!rcp0BxBJIZy3%+<$L&;Oeopao_94(g>j29T=%dPuZbejJ0a(^c zZb7U-h}4KX!nP`~dO#OgPaszC5qz;bV>!*p<($ymfA+X%fcr}j;~s%Rp;a*RQiKZ4 z!IughL_v(u9;D+7MbI`wXR}11i=m$v`WWr}P%GL6p-!~z(ATi?hpvO^m{1|C0--*% zgKGR3n&s!+Lf6F*sL(<*jZmd_y#i7*bQ*O+o59HoT?eQ6p)M#EgdT*Zt$hCuaej!& z*pi*erGbckBx)dxGdIEVFp_jq%g)U;&YQiGJKIe8YbZq-vHknB+r1m_Q zs??d-VN&LtenY2Xm)@(%5ku!<&u1>?oDpB(Q3SEeF4W|!zQD~S&vQwPr5-(+>M>pD z(vN%et;+XP7}^V%bdkYxl@UcM7!m!g)F%*3d7X1}i zEO3$WE;z;~MhNz&;Y%wXoZW&n9TkSc7QBrE}qb#%Jt@ZmQ|eKz;z9 zooSs5GdjAdW*&n42tKZli!*ZFICuxSZ?%72a<)Br_r5pGfbHxyyX<0f%r0MLk^Pk~Jl+g^ z`ER?;;DG^q^JX)C_&e~vtm>>y=0~@z9ggj~Y@0dl*JWm_U12|S{JAamx^)klG5dfS z{L(C3Yu-?C;yrttZzcw3Wi*l49Pe!@ZjJXA&rMX$O201~x%_ za2`ErDB~tOXjyllG84h`E^ahcYa z!diSgbKnILCX!~V)T)e7X*R@GMtqegW_8AEkB&tw za@#neyIXE{Bvx#;E4PSex^0`tEqAo;<(fCFh`+$cP^$@lM%AL~J6d%OK~#fYwjY4^ zAwH}Nk;eemg~*LNI|J&1fj`_LfUEE^)EdGX%}&}xnt|;_;HZw*o=^|qB)4r7xxHsc zpzb^^AJ*7`Hu^~D)$F8Aq#4*=1kQ`u+LL1u=eTW~$eTcR1nOR-dBYmJ(S|F+X3b98 zM4Dwq;LQ44Ep{y8kKDFRGvVn_&-ekIN?9FKpruTsA@a)8oZ>2@Q-Yt};9` z{SdCZl8zIRjWy!LdEPianw{)U#GD>%Li%`-W6|0h@1hOQ5;=l4vAE|?2$I;k^eJGp zMQ6ONqg&tOb0l3+r@38c&E3PzA34g!K6+OqazirO5^+?bxjohu%T3AcT_oPw5{b9A zqDyK?ePeNTvA(CN<&moD>V`1nsjFGJ zlnRZJxG@G# zE8{)f)N}Jg$#i9q$BM@K2IXa$Q;W=4L?VgvBAu~r9cpuLhZBqRIK3*;+8J$2C}u20 zU@A??)<{z{5ku0o%d1wdc5_~iZZuS_x+bUdtCu&d#BG-&;VMHnQRYTs0jgKj)m1gr zxE|`Ome;7#_IOvUw7a9N-HCU`OIu=19ntQ2J)7D}nY#NGZ`wF7_bf55hr=3cL9Fh! zV*SMm=_1!RF0WZtTdhw7=pYUOn_RWDMpa#1Rv$Sy&B@+KbG$Rz1%s|=@1|I9LPdJw z|Fg(?Cf9aF-64o1P#Y;n&Fa-vOKMOYRBUl=U5!GuJKDNqEyd04(O#5;wUOGbtXf&K z3gej(yM@p6CT+~58Lv(km1m!vf^$GJk#r9c-|d2m=()ob!{Jiz0Mx8A?2Tcnb9!Mm z@idS%5%f?;lHHh3E$3yF_59Fd$Z4+hZ1ZLZ9W_Q)u2`vbeRPMJwDz1c1-&)ztqc|E zj&0$<^+a3BTtG}x3tT97;e7aStY22Y;_7-?5jho-&Z!=(6?d?6#LUy3<;*m~#c@Ho zUX*Bgi?eFcqE#3~OosL-=C7Vh%WJAuH?FE#j^&92^sur|JUi*iG)0>?C40QpfdZ^X z1)O$SNa#sd97kP-*9CV=+vh}^I%D1nbti__(QDq-Y3;!3jJruR)MA~q#}iKOl6QAD zoO|O*CudG@92k-_ADvs><^1Ul!(FFpNp`7s)-(*`P+SJq=>r-K>xSWpe)_69Jr-B&hI8EuhEL@f? zZtZ1-#TNa@mh~i?Sbqe|xR3TmyW7ZeqrssHH^;lWVpu)l?zj^RW4oT0a4=lncK`pt zQ=!A74j#DlRf+HHI|k3py!bO7-&lCp$Z2@GgyCc`XwUl%50!I;#>qurC7xrUz5CKR zpsD|V>CJ}@{d*Vv^=C1><`q!z+SGj%_ix_Ay~~sFT}5_34$o1l5_d@UgQZ~IA;j$gk8$y4J015Hw7p!>RC~rNb%|H>EZI<2n|g2J0ceB`xjY{!(AjbO z5tsdBT$Css_hGa>8#LA3_*JQx4Y@qo1E910-2s2-vi3*x>bDPV+RVp?*E8_^a1I`NMZHhKbMowEt?9{xxE(EkGw{>EcYP=6`Vhnw(vBK?tHtngaKrC%fs`yiIK?=<`i z3~>(hfV58$5&vN#^4c$QzHFu*cK`!zzAQ1YoVo82Q38!fMe#pi;6meUBJQuJi+q9L zC4yCgO9fX5t`Tez@)r~Xd`xt>UWB>1JEf$=1t>xIZ4 z0*GP3%LMBLuNB-VxK)tv3Tbz*Am7T9=I@@w*97&OD$u_Y`U^qc9H>_)I7@JzV1?i^ z!F7UsD^ENA=t|^oD#Ss-`vpH2{7Ue@1WyX;7geweU|!LlZ>NY;1Wys1BY2izso?p7 z6@p6z>jfJG*9l%P*ecj5$X8m7yG8I;LH-I!{yl<^3jR=VMDR_)_XR%{{G*`7bpStO z1Ve({TgeX#RtPQ=ft J^4?Fo{{})De7XPt literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/addrbook.o b/obj-i486-linux-gnu-patched/addrbook.o new file mode 100644 index 0000000000000000000000000000000000000000..b00bdd6c250bebab38ef05bc482e16efc4c3146e GIT binary patch literal 25864 zcmaic30$1j)&6~FhA;#OWVxCJ6B5XtkX21InhY?6k%5^oLr7dQ5*QMc0EHnYT319x zj7`+mYPD6Xt=7FRwXU&7<5IP1-9Bx#YO6M}b*bBDZNBHZ_q@X-?Z5x|{f6hByPSLO zx#ymH?tNe8%wV|6aUA7-9OYF*lv1gcwq&t^8ES$W>sB?`F!1NtV9-BUTR0f?4+iu4 zpBfx<&cKrezdE*X%jnjD^1^~gUi#t8-yL_tW83a!g9STV``;+IZ0G((scCB4gVR|K zevPYRXYZZkQ))0+xI4I)x&1o}&aLz+byogJP=&jFrOf@{pZoUh8wh?p@YwDZOYT5} z-78iwe|Kf6Kg*&|6EmxOxApJ+X5YTS6Fx?@Jh!@_Pl3yTuhep`@Szrj80;zR-#Kv4 z+h|sBZXvWY*ibm=>3hN%tj`rzz-j(Heyf*(-x!Vq&R}_7-=n_%oxL9oG!z!x%WzAa$2XK;nzRCedawFFy<6T8BX>7zY! z7Gd9RO>_fxXWrSjZ(r}$Z7@Btm5hl#dlzl@xOEAb{AR`RotF1u5~3M-25a(6FBc3J zx&y)>{8$d7zR1df3RV=Hy9O%7IQl+tmOfgr?HDRJ;0#pcnb97}LJsCW3Mt+1Hvm)c zAEp2B7;5Mc^s?U?F?8k{@s;j-DRUTR5v}4mE%NJSnA5O~i z@2IIC+p zEOdD&y2RXYQH?D|78ckTqzenN1ZA8c{jBXW#`x}|Huvlr_+p4Z-50$?!M(vTeIGO} z8-2diG1!nH_YBCBDK}h^D|f*o_zh+Kb9^nV3|Rom_% zpiLg<4V_yh43_%`7MG@3K@7_WA{8-ve+{|nfxEM+`0pa4Bc;mljp4gUzJ~+pd5*$& z4ZfB59*?j4aYi~*M~u$(j+iiFq%+DX9Hx}#Amtr#MDCHfq0vftOI2>}(I{66E5;;Y z5?MB>)UX2NDV0rNb^mC`J0dritsRg#`Ic2yX!MfdN)2~8E0rrHXvLB|#|e#Qi~Pwd zG_6%WZutI`9_P6SEz z;74-O;{C|tAyTQyWzOjb7&Ytea;$^%L6vEhuAF7TZV{Y4kM(wlW9>+2tPbbD4+8l#_xOs7ysP?lcRnF zk@)ef1sBgN^O5xWvVR4K;&uF|qtNTg9*>9unKz@Y*BLgKlqYKp{D#k$)z*=MzOt4S zA=97TF&<2Ip~SnSiA-0ZU&K0wY1V}ZP&`u+J9#heL{643dzdfVcO46zVLfADr|Tf; zWm$9E&?=`8e|&|`u_*SGsGO<^AhmOqA$>W^QPX#jkp7%%aP=K5WM0l^B*zL_nDYh} zhi{yaV{#Z?`Nj)5Hs?+B?3*BDQO-$hTO?$0&LOaR-$Wrxa}J{zlZ2d+b2?XGv5<3e zo;wKS6zAs<-BU6@CkFNTN}XE`xj1J5WcN*z5iQASgvxxggj|;MAvw=+PBjBuk#i9= z>6`ByZOF=;2(`Vy2^+F1Cl~hNTj<ayX}pQdK)w z8Zw^q97hxqa!t-DEImfZ<8#g+StI0$IsGKV&Q#O3CFdh@t`nIz=8QwOFX}vH`fXRk zpWuM+_Fs>Q&hy<*HRS#Xw&;7nYDDF(roJAu3i0K>O6EK54Et5KuL}*beK&z=-gWrH z;pAVA1aoN6l?t)*wR7Jr4Q9rdhjDxhKNP zhfNnN$~^&#WY`Q5Aa@39&SWD`NnT;(U{JHT9(>LuPf20nViwP~855C#?mt16=S_@a z*j$smKO3UX38Kx&m$8D1vy)C6j4kIeSZj8hNz;~J$INH9JFMp^@#UP2xy|kr(w}oL z<~Fmi8k19uDabxc=4b4v5)3c?!e(D1IpdhKmU8}7a>gPD z3gN~!dLOis{WB+p0c86+G5#?=|0xdw^%}T#M?VbBdi3|QpjkZ^uE?)H#5@%06XBAI z^*jt=r_wiI&7S2b&$B43oH3y$w~Aeh_~geF>eLZl$Brr-Qvu{{#xl z(tm*s4%2b4%+}Xqe12U6Rpscd5N^1h1va_*hmbH&KMfA~S|ewK&H?8FJstB?sH^aI zq;5gaqjWtccC>y2OLUALhc%#eK6*JwUkqIytX~Gtv3el}G)_YVHD32%h!gZd=)Fik zkCl9go{EBr`U3PgNk0HdighV?PS!h+o}v%MDk;(Pz`0ca7QIZ>FJMH|^ikk5U1#I( z3_SuPnyF{OSY~OiyxDprR`MKOjJ9)i6K1STH{kC){e8^Le7y|m1^OK*c%j}04vX|U zv|X$(gM^3byHR?Wz8d+5>*pc)68(3im+Ge==Mnm7=;28HLrA_%FTfa&($}JwqqPF( z<$5)0Vu~KX@E%pV4CDBX((j_-V@kh_{&p#S76$RS(!YXMpHTV=h`U?q#n9!GN>70R zPbvK(cs&g+=;|4zCqlO0D*Zgv`mEBYLif)peJQBtm0pf^zf*cQI(k9rBFxu|O6P)l zN$Gx2zgPNy(fi9vr=Yc0l%9=tuPS{aWO+^LW0Co~(mhx?|D*KXfH#!>8p6M+^a)Vm zAC!I!+W4c=_hJIxQu_B`_O{ZeLoI(&+K=(Sqx3tN=;x9_C z#3FlN=^)BJP&x}-$(D?q6&2VFANNl?Nj<8^l+A=Kg8J2cJwJ|caEbwK=nC#B6N1HqpyWp z`yE{YEuH7+0gU#1N528;0!N#JzoQqThYKCO4!sXL`cf$QB1iuSQ?<>}*Fkj`J9;^o zeb3Q;^swF0KY>DaIC>R&zr@j(V|im;^=dcd5xn+E=Esd{R=#u5F_Ue zFz_!lY5L%!AdG*J=PIk^sqiUAE0{O%AjhOswJs#Td>qSshj*g-2aQ!*7m8%~>X`b>YU!@5vOpMh+pJup^B4};Bl^fM6EtB*p@K79hXX6c)e zGfanG62uYZc19Q_dHceuVCLgs1(t>x)s zz#(71jM5Q$JjPt0-v<9eeF{`EQXh_eVw7GC10St#ff0_;gRlv$&qw+oy$Ku+)_;Kt z$Le0x8K=Js(Z=gZ7{~en!wN&27QS*(8o6;0MPNKeskLCz9A z4whf4&&J=W`a=wPn*IYOWV*f`JmYiWqwhwYxjKf4Ez>Qi zGf(dXxA_{!1^DT0kZPfhp|3^y5VTsX{}=KcsxL;)VfraZd$?W!`IqPk(8*H04&08= z<*0e2o`^cj^g`(8DE%TzkJg>g%yK;fGVjDzij@XG-H0*4PxoVh@YC}lAN=&U5C?v` z46Wd&e~1R~(>FmM@Y8?6bihxy!2IB+Z-JQb)47lVe)3I*4?-mP=@H-pKfMcP1wXwS`h=gJ41k}04>JHi z{c9)+e!3b44L^M-n!`^gV8-y%cR&{S>1!b;{B#qT!B5|fn()&Xp*j5Y@z6H>bO)3L zKfMcc2tWN}3=@7j2ik?7b|5_b^f1(fpS~TE!B1a`2Jq7xp)>gDtyqKb(J z!B2N!wD8jv-~vDW2%5uB?}RL8Ir;`vfuHV%&fur#p$vYy1kB*4e+&WPr@zH8;ip?b z!B1zQ9sM*i2OND36aqheBUA@Jy$Y5AKOKQc@Y6dXJpA;VD1)C)LJ0WjhtLjwIt0DI zPv>Lo@Y83a41T%;8ib#I0&>Dne}d-l)32f?{PYCK2|xWA1caad5(Wl8eK-1ppN^pi z_~|xC20uLkZUBCI3_7~T(ceHz*J3*Ym+P>Rpvq4jJ&2)P@92%-d4r>W2DSbS`w3>{ z=Z?My#&Dyf|A^&wlcQgO+5E!M!=cZc9bF7&w>WwwdcW1t{{WZU96cJWZ^wu*V|O_E zaMZlh(fn?dW#__aLgo3b@zNQNXVpJs-Nh&(SYImR~!%8bi4s z`b6dfjvj&DA9VDSfQKA?Jkd;j{X$XZ=gC|9DUfELD_yD{C&aRB`UJiFJE;3Z**i>hi%CEKkRp2iuT#K0{-K3z^>-Q4dY?Rgs0p1+FS6nz3; z<}{ja*m;nD@cAdI9l}X)Rx>#VSra=zuME6+2YP2{0$8k4o|E@EvjwDmr~+ z{W5Y&pT(>>{UkppX(T+45}pVvpE?ZI>6}lVp5FFJkm3SLaV?4_wJB$S#M2{}bNR+|c2<$~-#^uP{ z=T${}Fi@w-sFQK(B+S=NG_8c#6PuKC;(H+W;yZD@5P7Io+=Zg`WLVsV{AQ*mL8C3~ zc@8S5qQkHXos$gTV(|PKzROW?z3^=#-;Cp^Y7%+3lX{92_-`Wr z_d%$c-@wf}^$s5(X2Z)(0DcDEQ+kxM%AJ^RXez5@VrT%XsQ8trI*~D`vx@9CfK)}l zfJ1Q>IJ_+3qXXXZF%sI1QIzx`;gq>d&%s!oGGRKUxwAb@`6qI2%B};yyU=7xPj@p& zvh?gIoY=Yv(>ssUODHVi{8-YnV{FMLtV5S7I)pyRnI8n7eXRO0HZo^EF9bY0N@t}u zp_7Fa%)8^`GiEilKrb$N`ZR{{&LYl-o$FUo&)f-}sqz?1zwgpnYU+yds9VY!SyZW- zy^YBoylrxv*?X}qWnE&4an2;Htnn0nj+#9h?smlJIb3T_wr>=0_DKi^MwC!Rj+1vd z;27l2RkJr^X^gm+myh6hG?ZVkIA$uTvEb!_S7FIFBl7XrJkKUwR;K3l_H@r{Z(Bca zLv!=Iw#7>ho7>*j(Ys~thK}BOi^~?3Et=QX(cIqKlC(92n76(y)w5p?pCmN3v~;iU z>^!*)v!PT^s--2_TDB3LtJK!6WDk-UJ^E_vL=s9y4L8}{+Pq}pLS&<1cXC5=i>>u6R>wn5KZ`{)5v)eA2 zzhuP`Eeo0t^{@56Hh<31bDn$9GwUG#9XEKl`rmuTd*U+hq-8bU=4DIU2K;NiaJPkr*%(DmL;?|DaiN*wRzCt0@DU)Jj%o%C<;zlwU>;m;grZD()s z#-`25;*QSZruMd`o@CEt6|f2Tys1-rdQ>qU0x{L1f?L{BsuD-ch7KMyW6Abpb4pbw z+q=|#P*4d6Pc5a17WcwWDeAl1n^Id=m!&*&$f=C5M`1?KO z`B{NJcvmUm267op#4QW;Wu50c->b0R%!i(L9#U?(%afk-yo~%x@O0bI^EGCaxqZ=n z4MHxLS9PE7Jg_$(WW(-LJ|gpw_7f?$NA+T{4t=nbAa92v{+DuJMme0=&_~+yHpsMh z)GD_S?m(5|>!|u!faNxczve?_u_^^6(qT|gB6s0TL0OmE8wB+erJVC*KA+?7OpF#i zEdk)!DwBj`OfpI^o2#lPth2d1mu z%G2G?LmuzZv1AC>+oUVW;px))q0+P&E=6hFG>Eda+a`Mf=h)YEjjEuU)u0Ez90b9iM0TPoR3D2cf_3rwwIpjpYZ48yAd@k0sHjdvqR~h!6gOGnK)P;6XDX3INQ#OT zky=yQ@Fc88_6GH&j&x>(OCdw80FyHW&}o1lOuW&qjnbJT-wa zD%1xW0Y><`;F@?M9ICT}3snZo1NBB8R;`NESCApjxVj_Ks+A6q;ROnrN$%miFiG< zXQrT{I#3_O^tLx`=%ECVsG>SpQ4_Ckh{Z9SEh)ulFp*MiEggyGjmhSdlPxNd=xl98 zo;$v(U>tp5sA1KW?C$C8XfpF`6qBfi<`SzKBJrRZb2$tTs$gfefi+|i53HnysxZ=u z2*!ylqk1-1ZLK}2Zp5zXzDyArBoN`AtZIXG4G9dz+A++nJ{S#itnr4ribyz2g&xyT z8)bXwH5Q80*?1Y^W400!#F^p{X2|M`?bpPE^|i5JJRXXNgE3_)GQXmJEttoG(V75T zVG)_W>w++bU@TH^)NiKUSifuEMo>%xmPt5R5l=wVJ1aHMW!s4`~D?X*%FNI+8o)6^{JMn5+h<25hgQ~$2bu+E+1D~jw8Az8l4s^6~WjF{sr6H%+ zBbRtpC~Sl_7GR9ku6MIM$|JP+xb34pSP=}Z#;T}IV0LN)@P%+mW*M_mZ47Rup6o@# zH82c!E)o?D_4RPV9I>ektEmjt*TRMDr!q=ZD|st}buhCE*8tNlT-ci>nxI2qpAB`Q zC(%bD5w6Jev98;#hAYE7Dfot_whoFC3$2XQiCBSHMJQx_3`;8D>Qrw>Puqr$WJ@tx zxGplxhIR$fqmo*U)i|VYqfN6HxPnz0E2a-HjwntyV`a^l>-}t?syd7E0$uZp z#{#P{2)lcjVTxtLS#xX@hAPAyHOh9#v4Bb1gv_o~8Cn^P#a*Anjxy&>_7UqnjQI!a zj3;5m>R{Nc)!-WIOH4taAs&gz+|l0{@p05o*nPl`8pD9OQhnScu_a){wE^oy!y#=f zM5}mAVK23Pq;0e|R9VSI(UofJ?4ScnuT5D-4RugY4Yn27nD|S0Hg{FjMX;tYHcA)` zMT6-*E^~=lYqdsUU0YYmSeI)8SS@f^>E-Eep&~&TbE#U|n%Xg{Z+ruEWAm`+4YxY5kXXmAFW2r_DsfTTM1$e|roACr8Hgi#Mtp;Kb|scgSCa|Z zDODXJUu*=}>mnvVXGBL&0&6B~iP49=pUg+VY$k530_9O1W>HvI5HiyaA6pr$tG3aW zZ5dlzSAm7>Xw^Nw(vX%*Jq=o7#Jm)`6shdB|r>I7A-+?VFer0*EXoJmTTR zECyMV?w$QAwkx^Eb z7%p0KopAvS*@2k>gldQuR9AQBrmmElx3P0ma$ZNxW^D#jwW&pMoe54iwCd{ z(h=GLS~jQQ;&h0{SHky?)~vs0mB6k$wFnUK(pH8uPkkmJmem>cqqCIhib8*RH~uPl&0LBY-+Jv1?%@DjiafHaMIB) zYhYEl=dAKbJRYfak0=?zAg4hBLSyR*209dn$2jY>NyQOeRN?Z&)-kJBeEyINHo39t zNF#g_1XhVnop=~UL2O)Pwl(9`?dZwZ-a>>M&D6P}{m^dUuJvj-IczI#Y(jq;sx*$- z_z?Hx#nU9jl8X=U&+rJclz1Ful-SEZ6bJcj96LMP+U=Lo=8$M6B^2CQ3z{{D2$s>!X7YC z6;UhVPaLxY)&wQ4$_yp(+%nnIV}c_fmWZ(@BbH6dS<@1bOSy+Vc-WOe+c#3oWJ<+XrLbZ4eJjXv0x9iRQZ9EnW zuU=$3iLT9PWrD_NFlb^Y29TU(oEkA{h)@?;SY%Rqt z53*niO{{}MBDsrs@?gm;J7&3uOrw3UvKywGYwSW|ST_%QGEXWSx;uO6j>H+t9jtq= z){|`NZr-R`no>=$Ri-Q3x^W}h(%p1Qh9vGz(-2i%O&jpsoa%MAbrax`HW$0Co!y(7 zQsxT#-yVjfRmG?$y(o?F@wL{w(N2xmOm8fe5GT=LBMI3-a2J;zk$nJ?pKDi%7!Vg+7VE=_XcUL%CgMhB6mQr1)kTc@puJGQhcrqkp~u9pN&q?Uxf_f z09CUg1aQy8a-jfKBC|Gt>jj%|A508IxAq!3y`ipw@VKdVL%QlfxXNz*#;VP0492X} zPeR=L0b@^T^D|r6zwcubEhP{gCa_`mZju!Qhi7g;C?q5NA@SsFXE%vWO(*mETGla5 z-tMAo=2|50!qZ~N?NT7tP#=Uji_@2?)^d{F-S(-CtcUbj4_i7Ojxm;NYCgHQOX5Ay zCi;_`ChKX?zuj|eXkf2n@pQx9@HXNZmsx;}?}h{xCzUZ&c|^v&(%Om<*-RkjjYgX= zPhHp@uRe!7SiBN0##~|}{KWZpC@f{1!7D8rXn>au3Su=Oh7|IEM(ma$7)KJRgT2$0 z^RdFvOxlpmEw&RQkC7I-uN#@j+1<3PJ0(j#Bne|vK>wm?t`4blA`e$WHf zMpg$SRaF$vEC#cr;*EIn!z}koJ{?!tI4wOGJWEQ4lJ?1=>g0R7kRn*O+Fb7%IkOAReIMv~WmFCA)EPmktixTL+nWdvbO4?(P%jCc~cm zWL`6ZR`+ax(BCM|?q1x6hgR0+6mQXn3=NvZbI1xj55kFhr+V>_nd43e zXYO>^Cukw;du$>z!HMLyB>J=uD-((D^y1`|!dsIS6-N}$s5A#@8}QCObf!eUs;p=0 zCP)WNbz9u%rn-~uWhp-4EMv;-NM-90)t2E*-n${uw0?bea%x zDfurbTVRWAR%X@KZr+**XT2~rmX(E`zpS})6M{{Mi%=|C zhWLJNPYUkHeW?Hc$4RJy*JPCYCcp}$GhYjE-;}^hl>9%P^yhaGrM93UUPLwR`BDL2 z$eJlMUTHC(x50S6qzT26o(jz5SB-b4W+0FJ*w*F8_sq!G|LxJ00mve%o7=IuUu~hgWdZ{4Pd1li%Vgct;E` zy0{;=?CJyRC8pyg8n;qL*%e4<_WLpVrCqS!k@&jfxD#oYHO*~Ycu8^G^b%(44n8Nbg6y7}EOG`>sde%yY4j|?}>vhUF#Gd^w^ z$K={Pi&^iz|4@(hT^nHWEj9Qj7-ZmOX>~BZ)CR zpX?hdA-~L0(wRMw&X{mC^rpRx<>ECfX^5j2Qo3)I1(EIfH~zT_@6jv1w8hs8Sq`%@ zAI=YdS8NWj80F^yS$;IoeP5L{hHYNz;yb7R&fo1FmGJQzi?(S?QuRVai?Ew0|1L%hj zpnrP+{q6xY-{f>ZlqV;{1W1oQfSz~&U3LJy`~bT80Q%Si=;j0H%=hK(Ii63nGf(tG z2NRoXu4>)ODn9?rcoJ%BWE`yye3Q<7UTyOEu8_IvX=&b&M3luBqxh~oHsvn78<#M* zi#<)PNgfG!dzW!d{2jhIZ>y6zA8aKB(n2o2ko| zm3)xaxmB5dTDy};TV#(drWVSZ@z}B%|B2Dm)7;jU$jC6t;a!BOS!IsRG5cVyr=trm zS*2QSk*gEVeHXqCUi#)<;DN&&APt|hUGN$r9L_C34;;}Wq+#E$l13mg6?5pp`-n|I z2Trnsi1xjL+gJ`C`!Ep!3jYh7^&ce`8=v6?^Or_QeofJG%@?Rz5Rr1dzKWCV&zlsQX6F~CqlKcw=p+1w(eUIf_Z$u2) zV6h;o8`y@W__MC2aFad3YkqD$pu+kKbii=^HWf&sy5!HA%VeNeweXoj6^ zZ|nnjn$Q;rZWFvg@E3yj3O+9Qd%<@FKNaM^+>k$ihm1H$kUoVpUoR(y1&sM^Q5^Rh&u$Y5xiaSVZmnw-xS;< z_^n_8?H_#jLOF4fU{J78uuJel!R>-S5WGt8I>8$SZxg&n@FBq$1YZ^WgW$V@9}50m z@N>a$1kE~yynOkaa_0;3C2rE=1Sbhj6=b~1@&$s23z~I~{0gB%f)T+6!Q%w^-{$1A zL2#2`kKk58`UlqQ7aSDaA$Ymq)q+12yh-qO!FvQB5PVc{x8SpaFA2Ub_?F?ShvJ{#ft^!CM6H61-pVQNbq#pBH>Z@DGCT3GNa6RPbv-hP#w6 zTX2M+7Az7h5u7EsKyZoRa=|LWTEV#Baf0gw+XTA=PZ2yruwU>Z!Ak|N6uegOMnV28 z4##n?;6sAD1fLP)FGaB4>w<3!zAyMU!OsQ%Dd@!p$9BU7M+%M=oFq6+aIWBD!6OCB z1^L4OY2W zSMaZbp9p>}I1GC}$D;*H1s4gH3w~E{yWkH5uM)gY@J7Mg1n(BSUvQ`36N0}Ld{OW< z!M6m>KWRh0uZ1qezr$1Bg9M8NrwGmvEE8NTc!b~z!79P9V7=fP!F7Tyf+q>`Cpp;v znS%X-gMvE*FBiO8@TY<|3EnPvk05{BihLgx+%5R5Ab(MU<*y6ACHQB-J%XPIeku5^ zpf}gH&k-yT)PfTPCksv&oGZ9UaH-&O!JuG`;3~mJLH=qMBZbCKvzq)#g3|=& z3N98rQm|YwBp4NJ6kI2m6l@pl5j<7!Y{3fzzbE(u!K($Y7ra@JzqrM5{92GdheLX| z;B$g63%)7H-@0SHzY6kqa7ce8xKD7{2%DcTI7V=S;1t1`g7XCr7d%=pC>R!u2_7rh zB)CzqQ*g83>4N794hmi(c!l6Kf1@9!{dp{BN`CD70Ul9DGAb%#7`NQ!%g!M)e z!AA>@Bcgo1lpifvE%~)VHww+4RU)5Op-&e2Y@sg}_&kQe=wbEM!z!R3NMBKnIG!6z=bM#|d+Hw&ICc!}Uo1aBaM&n-moxkK=7 zDSt}J-xB(7g8z{GeMGeLf(J312)PT1_)Zk8ko*$`lakLLUuM0t1qX>}zg_4D1wRn{ z2N7rfuZ13lizBu#7F;A)Be+Iz8t+FSA3sDKzYQX6HHhuSAk5MrSQ<3}q!i(qBO^?x%NF6#gQ literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/alias.o b/obj-i486-linux-gnu-patched/alias.o new file mode 100644 index 0000000000000000000000000000000000000000..8f8133cf10a3b8da68ed96bed37b89cf97e2b3b6 GIT binary patch literal 31952 zcmb__33yz^m2Ta>EvwsVt7Xf}#TbzHUGk21Tb5c@V{LRxUIIpFY1zWskh;CF*&qq% zC?+ynRu~v237G&x2&+Sg!3<`}5HJjoK!7A{iao?E0TUp8|6ljq)^)?YneTnCKezrm zRi{p!I(6#Qa=Y8RLuDm~VJPQiC{qnmN^RU=mn_gQO`W1fJFFUOl5ek1J`uhAXr5Q8 z-lyV~y@%uH?7ivu=O<1i%O>R{t0x7L<0c&{p5&ucpjUzMy)RCn{MlLzc3Y zc<!K9;Lu;*gf%TY4NNjTbeppIMHfpTz*y`c15w>?vOPj@7;)o~mS z(R(tax%38Q>#c1t@G11%8=t}+rAllylTV;e$q(N9%a`m)JU`XauTf>NCqHLLKMD4f zz%I%7q@00#wB6JXc{G%^(8=1c6%HflDxQ{e7W;7{3}(5#fXCh;Jd;R}*-mIOl{KxSYdGyN|QS zWj_b0`+%|HL@pG(au~Eh%=Pt^ctxBm03y>7xu5K*YF9-t2VJGf#|Bn2C*=F85IAQq zgRt#Zy`LnH1$*|x3+J9VGBjn^ZQ8E!55H>DH+oM5d!A>hmi2Xc;f4#e%6$scDCK{cfH^RZ!YUa+ob<6k zvpI@m+V#GgctBRAeu?*J56dA8#O9XU%`K!IqQ2h4iAjh-$UiM546OvzvsjJJeK)xQSz2)y=^Fg!eskAqA%rRQ;f#ktp&jaKw^6W=V)qUL9KB6!5Cfh%-idgaT+3qkO`69U8^AOn)QMZS(Eo z)WLl9fcv%X$7ksv2ID^zd}IiGB@<#&qs&nMV=Wg7B<`ig#_O~o1URAB*c?C$iJR>> zSpFt$xnq^AO!h+l}ZU#Zu7LTnf8DFyeyJ(wVUw752C?^B5zZ21E- z*eiDbaFrU_J5z{kh1upZljHPe}iZto;aS>d5`l;lcf3_tC}4%^xQZ z-il(COdLR7EQ%j>zWu(6wg1Qjy(4j{cL-k#zrt5FsFwenclBwcYHhz z=n4w(k$2E@$4poUkUVLBXV0(8k3I~g5d>uB(9M321yHZ*v_fjvk~|dbxf&&XYY`ZN zJ(nW6_okLlPn-a&k6U%Rs$-fbdbeR;ucfS}6j_5{1@j5iyRU`2{&ABa;3Jm+__Ust zlnC*<`go#i3yCr=1uVmQrcp;f(AxT}tF_^jPAMPky%ZYm`4!t$!JZDPJ9wbz&9QrI zS3K#k5noAxjxy&OUr|Qy+MR~Fk7Lcsh4Ak8j9|}LBv9K+ebEKfwS!LbAiO4NItnB) za^e|W^5S+atqW}J9#mKrb4SZ$*PU8NM(BMH_E4)4%Y(fiusxU7vq=AcFyRHJ%Y>Uj zU}a_;f}c4CK-4Vq1$%a)aBt`+Jp%3xwFb+BJyFI7eW2>wd^CB(`QibNjTfb9ix|g& zJYh3>Ct*(|8v&=oJwZt9JrQ5nmk9?eaLj@!Fp*}UH}qwGjUA6<(QZ%lYNv1;tSU_f zl>I;X+!E-@{%`c9#@ZZgPA{jndC-79?b=G(CrMqAXUvrMou8%_EEB*CLgz6GIh3&n z9CjeFWiXF!=gdF4W$$gsfpBL?ZbdoQ)Sgagi+GuQtZ#Jyw)>PkYXYg_Fp8;-o?MXY zbZO8jQ;K#%;{Vp+IGic5X>;}|yUa0-6C1pjBj0Hr9*4j*3l2vqA`K%B4%h5I2Ynv& z3%x!DuQ`ZJRss;cFyx6rrr_06Sm_e`jPCFdou>694~#!|gy1VNc;Kh3q0c*?WKc&BZUS(1VsCPE z{=hcSTn}pky@!GE`}-~p00(BW>UL)y4BU(mspE-WXWU(z#;%^+wG%H4OoG+iT=)Jr z25>Ap@Da8F4}wVz+=;C*yzDkjTnB=3P8vcdE*{wVLpyj6jptxUyij8(YB?U^qXbme zL`Up}>|KR$c;1ll(~dHE!br?Er9N6hYnhT|;y{1_j- z{M^J-(%W; z=^KK8y{PXd*1>k>#pHcV9r-Qo@<|5y^Mbv<1oUaKIO?M*J%yV3?Stb%j@D{$I3W&V z|7|dhg*MnThQr@W?fNXVGJN1h@MGVEb4jr0o0M+qm1^(+2qACYiUM@&GWRV{iN5pu z7Ua2adC;^lr!c77AKMyK_RtGa2-ke zv~`nap9k9oxL|UuQ_n7Wua(`~s}1>7yfe8r(0d}0Jx~XkvW-k0>O&^ty3hk5l(|~y zJzx)Su%`v0pr3DV?=htGlwpr0oZ_g<^6J4AU|<EL2qR|*0_SLDW-rZJmKDY! z!JMSBvR0xTx4@Fb@MPFYrG^AitW+j}?7m#X%+AVUZ3Co#m@O(JoVys&YUmhauq;c; zbiIIKgmYPA*mxDrEr7`ETo-R}ke70D91WEkJ_Y}aWi`h!)*cwH)3)6kW1I7Xc!xw_t1kt!WLH6Pt)BU1x;+5qD+Qmra= znv`Zt4TN)P?bSor_UXa{86KGbj0JWTl29~H8w6|X_Sr#lgCx%rOkPEyo-5D|^J<;EkrMXuk&NlhxC3%L z>xLtJO*?WjyqQD1nO^Qu(AGTI#PebfTAKSba(q9>EV$k~`^QN}%*^!kGkn=x8QpT7gW%NQeM!2bjEKEo0+$KQ#5W}G7ANdHPo9xJ5fUxP+7 zP8D*T|2edfF;2)l|565}(}kSmufo10;|w9E`Riejj65M{`4>X*j0wh6nrY%3KkrmB zCKrRm#E%yJ8r89(F?w`)Ovy6V-!PWjTFj>YNW2GjG{ZC?WGUgg(nk@0p zrjqlF`C9T?e=EDN$SBfesedaQT4nsRW-jwLvu>$zw=syz!mQf)(Z}rzu$tokP+ig)py+a~DMK`j%u>X+iIjEGi5H2!g zBXd=Nqy7+5!|p`FRN1~Em9K*gwxj-#DjDhER*dD4P4ofJM6dEx!m);YgVl1PsFrcB z??xyQ$k8B-?)U(#JtRiWeXpYVahdb~0={4$STYyb4yuAfkd?Vm+%?Es z%gjX=;jd?+FIbBSl6hvYrUJn$S+>~b%n5#h;mBNKQzL_arOHcf%7Q{n`TmZEM*1df z0B3M6+|xJ3W>CRxu)A-nO?iXAfaQGCr2j!)*7~Nil4oKd_daSrgCpcM&hSjk$^8u` zly9b;aXK>4*fDg$^Jf^_H=9Y{i?q9c%s)ZI$ZfG*%5TwFn4H1aQQ|+vb}+AQ$v>8C z=q%*W9kYG@)1L+gbD*OC3}>tlv0@$zIM$h7U136-I8}(3nA! z`!nE{Lz{J)!QnBowHV}s9RFE4AlrrX`ES5@4ec~u)vW~l{{;aD{^nUp=ri7$16xh7 z^3kn{)+*#ovd%-!WUCc9Q>+z`Io0CT{WPlvrPHk+qF*ztY0!42bra;wvI5|lZJh@B z`BpJ<3asU*JI6W(W6rfMN6tL!ACNHL8jt=iuzm%d7h095wa9uEIcHk$qja&g8|^N! zo<%E5EndYhvv%X}a_d8IuCV@qS}U#h!N1B{2#Xz1)}LUYN0qe|C66iV926Z?)+*TI zab@ATn)-KTmB1QLDC>_r_ut1twP7uQ=%itt zhi-n;uvVbGKEv7xVc#;Wqu|_YSV^dKjbY7&*55X)P3S|vVO@>t`wZ(gjLNl!wI9@V zhII;9t~ac6Ams+bS`5qIXjmg*g6|ksE;7GsSPw&`@1Y)4`o3X(6RrQiu-1X)hlX_@ z6uil>K14TfHmrBS`A>$`1ev!OYE&j>i7$}t`8$;I>kt+6NR0Ax4GZMxB741HWEpV< z+6WByFg>aZTKfVcJ!e9vv51O+Q98**LRTK`S%DI}@?>b5=?#D$QHDQ(F&?Hz?SP4_ zz+BH0Ap9@FCV_c6O&JWwf%&43*Z(EV5m?~i+KHvkZegJ?2mFtse}P3F?pm;*j%|#! zsKA**ju_jPXjOs5LXLzYm5`F@-3&{O7>Zs5mUx&m>MB^iDzMx$6ZY}nf}Fq#X;Ar> zQ=OGUddJ4wRbZ8)&De$p6<94)U~E0fLLqbfr=gR9HA0T`zs8Of32FJyqn(R|9Oqw1 z1Bay7dH$cVv_!~B{xD6nR>*1o5C%6;D&#ExLl~7nSjaj4Bd~ekEFl;8Uu3)Mgk0=@ z1$_;a>8^SvF8ANW(sBpXfJ%8VWSgI6&Ob$VC4 zQyFJ@xF?&1ywej7RYR)Lp}IhwQJ-j1Mwy58%zejp*s9ck%DWTACrmZo=!W+i8|=3B zAagI|?gL&At_gH}W4(5eUmQ6Z^v*~$YVd^r9KkB@RcO9}B<5=&Yu17oRdjGEL{g(B{8|TuR4;wm* z^=4zJ|AeCFSQkD1r7p>a3xW9sHnPvQ-5f9ugDrXR+zuhMUBAIWz63cFCL&sbrhB|e zdN0k@uWhN|ER%OMDC1hA5$vl$p3z#bjO&aJke+?#Pi|4h^_um3vUYA)#tqtZ*ORQT zgUi_T0ak77+~v@o#QAEPv4mZ^PwSln1+T?>C`R%*WKWN^LD;=TP-YRbW;DT>}cAlj0f0-mq4mnH&F1)#x1Bc4?GNpBhk(2+G$@R-y&qq&~Ee6 zWRSHWXTmP8ujzFD;1ay9jJ-Pr{Gx(^~c#B;)2y$jyYzMrOVlojCC{q*lAo8`^@7h!C zt?l{oR``@dwiQf)ZH;#yf?RXoTbIr0z<9mOZsf;0(cpVbdJ-)KFJN$u0TI$PvlDE8 z;ncX1&1ricp)$V)Irky*jx=T>D$N~(KSrM^;iA*oz;0yB_%0im&iucCEWpW488caGCf>Ys5ezTn zP-Nx97P`!n=$Hv3=`=5wW+Fb#Vrah_#2if9*_@?|bR@~===>P@XWjrM-oSfi2kL%f zB$|Aj*>_2H!E{*PIBzWSG5artfJ`rCW_mA%1U>I(piBqY6Yz=;Fyh8;-Nj=NF$=e2 z$04sBJh;&^E@LM=`}6?rVVa+NDA3)#T(3fjI9y~jg(QtRsLboNGr{v63eZk}HC+TE z)RJ2;vfh2Xj4+HP3?JTWZDOhM2-uggkIU7PmGGqO+-Hzu7@6Lm1D6~_%fZWZLpGoV}$jQLrF?e*XM|=C+2GL}Se66r!NMIo@?r&PhZ;8|G_QtP2ZdT}yLaS3c&8 zQeE-J##mGSR$iCJcXhRa!13~x=uT{V@IQ%=xl0OJZ~P-5Vp0h zYpb2=jBSbSv>93x@p!F6gNd}w)Y9Hi*Ahb-4Q^>^udi!i>tI2Xc0yDJfuY2P0!qTG zpY|Hhc=B_7qw81y#Ps{#x?=TJ7x{Y3F}}EYk?&@6)JC)VNz?CHZTRjo1HQM+QJz`G z(m7`39cHel)c9qr;B`-a5b&Ds9nZAUzU`hFxxPC+^TwF1o=r zF6dAAp8CyQD^^@)`p+_l#?9@^AKt$1f<$kv*^+Ob(*Iv(*M~ict9DH{@7{gI)3fH7 z*>SUTd71C&f!pVKCXVa{VGi#%CqOf7y70Kd(`Z2B{aa=inAuNi)@!ePd)bPuo(Z{+ zg%f7AFW(%Fcb6w@n5V?eU+?zqzhY(iwJ&=X1b3OuZ^c)Z-}18Wfn8=>Q+!3mvV!Uz zo@u#eRsZ#iTRMGXwwM>?uiWV=ALD!ZoZef^xG#T}Y5DTEnyq)3Lwzr8H`~uLhv&a- zwk$Wt+`PkV_l#!&D|fGi!sD2?=U~O z?8#npKDtu~dLD4ghvpXwL+_cCYet{^p*iwN-(CCu=9!Y~yY8316%=pYec68B1mAUu zWtVO*GoLklc^`FqW{ooAADZ`F>X~o627|Vk%YAu;E6hiB_ir^9!w9~OzcugQ?aTMw z(lcviGZZf~M|)-%E0?THn0YVx&N0h zt19HQ&8zELnx_gI8#`lNOoci-+dG%$O`Y5|HLn?^dDx`ng^MflRaLCBtG%tRC9kcn zH3rUeCU@nn$eY}?Ij^vxA=VLJrJ{A)V|nrRyr$+BGStnqrR8KdEdw&dwJp-b(M zfy!vw)&gOpF<piwW&RU3|f6x-d2uDonuJE=H@o2 zv!gk_H7~xkF0Kc2Jo>t!uCom`Uz%6FmBX$Fg#!(3cENJ-ydCYG+w$}BN}6}(HDj!` z{bD;i>e?D>HFvD5wsYF_rFkvw?H#U>YfrQ_<~6lSTg1b{5>h@jIvfc! z>WjL&k^7)1uY{rZX8>E-$ZJsaZLMtN3y7r>U~sB4jEu*dUPhc~r+q|TbhyWmyahUM zpGF?5(Jewc>pbN3>f)4JF(B>3n=KJ}@Ydb}WI%GaMBbZq-ad^#LK-a*{!M2md_T%Vc1;PcaKrTo#l6H_JMAO#*2+C{f8D8!q35_ucX8Ajy&om)@x*66%_8ZSZ`7AIVy zvlBkzRdzNZT|x!&cIo0MIj^*nj-9z<*@riEAzo*veMH_1x^*G%UAlaq#z&Bb{Rk!4 zPLP#&7T(Av^h!4ICOez(b%JdP`@D_>NDENJwRmG{dx@;e{6QJ}uw2-$AntG;z^x3* zJBa!MTU8OV>}nlzfTCzeJ<_6G2gThXJiI^@^-|+?6J*?rH#$YhujpiC*a)})-gE)L zSe;Dy@1`7l$QWhpNhDTpuFX&;fdr5tHT zfAW5UH}og`Lnqf0GI?R9qJ%7+Tu&Hg=MvW0xfOsv*h#{tIvFLfE!RrGrasj2BLtS3 zD)Aa`L-p%pWR~gL8z^&^uDyY9g-%uxdhJ{S?_8la!EPxvD8EPb54EJK4wTxGT-B@I zPSr_`_?6(dyAhp?()oD1!pI7g7TFSqpv2Opsk*dWj$Jx-kdY?v+Km4Uc<|&pJS%*F zHwTIMk)8GtdEe_Eq*0(Jb+{cD88Q7R%2kT1fK(BmHt931lT(XB?Y2aR zew3u^;7s4J%|7?m@|3Kf8|jiQvADi^z*U5Pq@pwJ>NdZAK4J^O2^|XQmK5*Mb?(V$ zYJG41HTku?3FnLFH`_p|c$E4?D$6UYs;kyk71mT&7Ke&dOI=r7)z$JzOL=W!bls*< zlpN8TXjQ19Sk-oIZSRcpX^QSt6K{!7TwNLo6&6QAMWOKe5V*pXFbMh|XJJh=w6&+ipoeRTC+ws4h7MFT~-<{4pmoHm4~CzaK&13mluZ1io=oe>Tr38bTnF4QW+@< zRhQ|mBE12Yh-|77b*suYMe*A(WQFd9W#K~2R}Qh2y0smh%@`%NmuTy1-oon>eq^^T zwll7HpH$n_-qO;(BhgVCZ&%H2@EKgPF>UuXS{(@&Rfj5yXasH6+NPGeE!q^?4&`eq zH%7zX2&t|_{ROcGZBz_RQ4s|cR#z7mm6k_!*EU27tD>R8NKvWMSLYajBHW;N#q5Eo zSW{C{5`x9U6;(CWN-o6gQK|}8h0tv{0i|xN4n@kNq3Y^zbs0RMnNPQB+gloI+nbsw zt+utUa~o!fcqFd`6`ZxDmMT&}b!cOCNm=CvcmpVH%}9ur#6Y2|w60xLSO%`bifEX8 z=td|K(F$;sLOMy;tS;33gXYzx#StjfRomRyM#kb$S*SWxQz0DDBDjI-inTPU+S;B z=UfxA3#uxs$_k^}Md)H>;qowhgy$ITctC}kwnvt2h-x3{!Y!M2ky?bG1iS+rH5Elr zfFpKRO}TEZ6tl?gbflzc-kb$zRux8|3YoRZ?5PB|U0YF;SCpq8&8V8T!qgQYIm-(p z>q4**k{b%c)$2l=R7*Q9OZA_VJTwwo8``KFUQ-EWF#ctjzwi&%m3csi*ouonW^p7q z1X5fC))Gv*Qqtk_!m6rJXq`R(>KYIYYwPO}Mp34R%yFH@Sbbtk3u0`GYV2yhNHbvS zt)ENI@=!%h5nKXBK$z15Ou^yeGVPY7Mey|yR1BAFg1^N(cR3RV7n^PE81jy~#`&tL zd1uU47_%f4sV*yA6Vd?(vt|vZjrI(*!clK*?qtJ7l@%q32}KA^)w-!@Wdu=gjUCyd zssoX(Lyy`91TEI6ii9iReR{^QANDk|!x;jF7J~6wye3>-&PY>RyS=U@5!3eJ&8uyl z+BNO%E%p_63Hkv4>BJ=~udiix>L+7us#ZsnK}Bh7#A9Y~E}@~Sb%i7gBazAtMKuxV zuLeE3ytJw&vNoie5Z+tyfeJ825jtw3wsV85id2@Pb_pgvOYP8X&!*Bsdx+6U3Ahv= z${_-@H|nvgsAOvh5}h$vKhDeOTEyR`n6|5qthQ0Y6~&>Ax@FoU94!u&6xNh!XBvzT z5*xIY>=>hKU@$PPzq%+wQ)q>!4=P?)5A&g6ID&pISc}!XRW;Vd>r`PemYHajgjN|5 zfBk$I-MKi&*dSagJG8gydjH*u+E9ny#cJCUb_9XCm>}9J+NsJzh0&Tw2yU$V#b{Sp z7F|sC|n<^5UYhNippw=LzNX}n=peBk=xq23aPG+ zI=we3$H-&zp(968S*Wl=HFw5q;lpiPU<`Xjq~D0cGTfALAEBRsbzxP9BimzJSrNkY z+NARH3-p#Ozk#~Q2E$nZkh2a;L`hlU+O>9|z~C2h5!JzIt_}0-?W0XBuwkKX`ja9w zq|v{t)-U?HVXGC*^iHOByPg70m_^N!q9S{DKs9x^idL1`(VKC$ymEc0vZO>|ph9Jp zRf8@_aflA~k~BCq>CDpM;!s6trM>vkUeQnlF}b2L9A%hmt?!C++ln1fd%U(D;SC=y z>QGqg^qQpYrT2@l@>!vxYE;?M+z58~H^LsaN)4#qi2c(JdTpRI#tc{576_H;RnryRs^DS~71>x@7KUB)E?I8^(IPwS zY(E=2@Bu;ev$ktjTfA;3It>QdkXA<+XC*?{)-_-c&Ul4oE`gAW*}K(t5Kc=So?3B) zsM`{QD>){^o(P_elZUIJ zn-|+w%MU<7!*Dqqrzos90PDk{4KNG>WtScC z31=^vcPNrmhuEFfBG~hlA)1DCdy`b0W(9X)Ka1Kp%yM-H-J{FPSd5IxQ7hp0*iz3(y zDmZhT3z+R5ER<~|yh`t%u~nsqmSA&i%Z#k6EQ1Q%>pBC8TDH>mbmuILVHOU~OSf{) ztS%0(#iVyOq}V#>mE7K$V1}ill3x5z5}jeAK*}jWv+D9B`FU1bn zQJ%A*vLoKy-lokR-GoEhNh>CNCe|5iYk&sYuX&- zHkj^{R$7`gmW+Bc(n9;hQlxLAk5!e~)ATvS?!jk*pQ<+VI& zmqMg{1Y{hCKQ~=yA9J{-oLv(RA-32jOg#?TCU%T-Ur*@luiQXrbFJ6QrX8PBW6Fqv zQfEgdr(c;PdShRRfx+H@Oo$jE>=ZZI1LD5TNFW#w#!rr|t(sh@ICmrv;<#B&1?Pc; zYS+g$FmMgnUUDDFHg%kJ)_ZOs&aSD%^ky(=Zo|%R3s-XRZHV9u#tpun9`-4E9t&_- z!@jDtImPBit_GH$gDfEdPD;Fkg zc#XZl>nz5*S`ONx1q?%pHd2h*Y`CYqOv1$Y3oi=WD zQk}7u{5WqA^7R%rzaG~``8syj*45X;q$-~*c209!Q@fkyx(T|SRVjOJ{@jzv1#a%9 zPF_%nC@dxJvW`SO&4IQDTdPAT+`=roamZKsSYlgaaHD)gn^-=Mr?asMXxPRJrvK&Z z4DjJDPvLQ@eyzq|=bO{azy-8^or=GBwlw%^!ska(X$*2$pSN7R0iG;09^>lQi?}#+ zznt5!naCvn|HL;3Je2ReD6iS6giNPwjVn#w6=U(_2UnBM%i-gJou)5eTc+!k|wZ>?^Z#F z@A3J#i+3qPc_jA;0`%+Zh4?;N8XpTT!P~9hE70#v2>;+ev#a-ZYza0J8gv%{8 z-=AHK4j<9J7q$ympQF@jI37RGLwDtPuwU$}Ti%{JJTzyayc~HB?Vvl~t3Ej4Es7GLh7Y4=bX&EejI_b`}h1p2cz zt^C3?8g7|-QQnm)${yEi(&!t~=$q5%+tcVf)944&=x5UCS3oI zB#-)MyBvx%fAq?Ek)E7J&rYM4q|u=?`fSj7`1lF!O8vH_mG4ZWd(!9|Ks%ogWc@qR z%K2-#`~*z7$p4SD^4CD~^CJA5AnSjaR_=FAR`z#z8f~S~XQa{7K=U&aS4jIy(#qGR z(VNm}ep%LevHjLG`f||xL_ip2)Sq9`bzbDZ4K$z9^RqfE=dT|)FP8s0js9&K{aPCR zUK)KOjUMF+DU?4Wjb4~WuTG^UHJ2i~L(a zJD(XPzkOK1of`I&X;z@2X#@68E2haNO z>6~fpLlSn+38im6n>u4LTW_Z1=`Xs(eKy{04IR7eVi3G5&#rLCQ~T54sFo4a<@web7ey1VXUr_R6w6aA=_2lKSM zBInLX+Xg}#ad)WeG_>Q+8F#_bd7XFC1%u9^8g6H5a6go9Y=9>Em{zNqsaI2TtVM3w z@#TZ|PCS>=P2;;qJX~o$-fY{C0NQyaREOIcerw5{jk~-$Wq;WTmw&kEM5(T0v*KnB zm!h_YEwNaK!)jlwP!O)2YY62>I)Y;OEz~$=@R72`T6PgZ2A?lz$It>Olnm zAEo>qmUFX<_0fZa#SkFnk0XMAIuZO;QodfwTZpG)zrcLh;ajA^|2-o3e=Oy{AmZ@; z7|@f4vma^j{U;H8ZxNv))cS$+d zTlS0VD#ztth!fEs^C#ge%UEALxCF=rGM~Tj;=v}LU)d(zCv?Bi|4Di(+Qm_W<>v!E z)4)%hj!&!${R^R=7v#_RcxK?ILx8L|9cL)YDJJ4_;d&tRe?l5^_**B$-w`4IU7@ow zZT_`DV>Uj@L>g!PHleqZE>P;1LjRWZT#PIFPX25l`A-#kB59o2_YoH=^)uok*w+t! zq?Z9baQ0f_V*K0)aS47iMQ}3406!L~_T%?OaJ3_4!LbY=^%g^Kcaaq<@l)(CDUqMZhyu?g~ssK1-}&~G0x zs?;xt(=d-@~Ot7k-h$&1KyJ@Js>OM-6;ek^Em-2)$gvx+!gaE{{}jQP;Dv&h2wpA7b1CKP^%Z!J&<6zdm&K6(n$RBz zekqvcmG%Uu3N92Z5j;<@S+HA>AERgccL_c$_`Kk2g6|4`EXZG>W4#fA;|1pkt`e*e z+$`8Gc)8$pf`K=3I+{+Juv`9yFECKTxACT!QTnK zDfq77`+|QH{6f&go`UW1R}6{#b{)|YJVS7bAio>O@&$s+1lI_L1*-%%2%aYx6KoOW zSKuh`BEicAuNM5a;EjSe3I2=V&jjxgX<$n@2en|wM59crHGmHq@5_+m2 z&v`752-XYkB!a)22>q`T?341F1#csQkH5!DIS&gyBlx_Oze0qZ*96~`a-I`e?>G^1 zJb0513XUe?J)VgAlLe;}!M9X!tzZQaZ~p!{`8Nq}CW601FhRt7x6s!J{y^{%BHnKc zeku6@o*yA+I1zak5$&8NwEl)8=-HA#S8xRp^}@neE%_S-&z164!A>INUn2D7LiY=P zU-Ew;ctG%3DSt)iKMxKTV(Dw@cpwQT^D+7NV#Prhr_&>WkrGfwe literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/ascii.o b/obj-i486-linux-gnu-patched/ascii.o new file mode 100644 index 0000000000000000000000000000000000000000..7b899abe272530e369098290c0bbf250f1048997 GIT binary patch literal 6812 zcmb7I3vg7`89sOSZnD>eJRv;A#e{%Lc0r=0m`ZpEM5BU=MJwIxW;e;gW;bTsR~spI%1tx$5vX~&giIp%wQjOI@FntW54g5|L)#M9j9mJ zobUhs|3Clv&*R>6cfWQ?_iD?slvgYjRAr{r)Ah#Eu3^4vQjMOg#tpmwxaX4arqRDF zAN^>0?Kh6r9y)q#><~?3&$BJr6Q6D05FT4`Kg>4;N8f#W_v@REjk&FA?8rQ?Kkd&O z`_Ch%+ebgB-tD&7dy3V&ceI4}+#23JtL2OTE>2l=bkD4oJ+wf*`vVhp*C*~ZyG}jL zDZ1}0`u$xe=b3D4581PK9(7+`^h)h>ult8PK6=bL=k?-Ka5xJNzo~uh_}FsE=9LJ$ zo&3evR)v_KpcMCxJ=My*Pd;ekV*dYcem6|WZ-L}DaoFc3&z_JZGW-z|HAxmLMmlCI z_x_7E)$MrM%V*rgkv#7zjv9XQTS{5=*4&!Ls$k8`ntH3js;f{c(4>MjORFxb>cVyh zTU1rm#jq=7ix^faWJIMZYGGEYl0f%xqZO>Fs$y>o)R|;Lg}NG-oT1biUSy@J#DZS5 zR9jY8BYRAmqq-Vn2wBq#L8;oPwXE8tGq1XO8X#kGe zhyRWd?g_PJAUpe^x9hCy*{NAM*lA@?vF_8gghrg(={#F#i}M&GpCxp@GejB@y1=O=J==N&5NKZL zOkt=N>j_QUogJjDGNUEVql|p6&<^JXS{GQ`0fFXD=Lyn<7LyA!uW~MClAAa!!Oj~J7L{`x)JqZcr_uz7)Rn^R*g)o2SO3`LDZMP zr$*7d27*X!Xsu2iX$0a71pXVa6Hj+jLRrhWFjO`rg{%XamQmJnj=^(0okP3{@(!xi z-HM)54@31VY-$FL|AG((v%0n6w=`hrkEyyw4;_KXcg88yH)ZInIrQ1699k1T_Bj^V>H;%v2Ujqs-6wjhTXD# zdGI=zTRVc+T}ns==1vMUV7iE1hsqBDOIbU@)wX>nl-~K}*p!#ogm(p2ObU7W$Y9g7f?uI^;~HtV)KzG8=|P)7 z<*>wFBZrAaEtiMw0ncgOxJKH2p+-P&(`MHujv6^kh3U~hr1K~(TG_h3Y+bKAqKUwnFH60Xz-A+diG1Ps*MYtlY2CQSwU9AkLbp~I z!$fxTt%I+Z&EBiD`C5YXsxJ2`tpj@{QL*M>;yx`G>xd7Cp7^-vi6-Ci(kcBCbe*VJ z%dY?!2I3unyN&o006RhJtp_tSeXi#B3&UFKYQL4qT53I`8Ea`R+1FUFDqBnYa2tXI zbfACW#l$;Lzscg6LUCv)J*@9HPm|5x1P$*rqjB@bhxeDKF+RMmjHciY_a+MI-oYV# zIhB+-Ps_3O=cY~qIY{9OcqJas_w~hH74Nz-KAcXZ;zRDRiuVpAGC5VqY){iv7|0L1 z$ztE>XMwxNXEJCIJPHCJqitc>Ves0QU= zIPs8_htJQbYx_5o+(o>hpv>Y-ZwJ=y+>Q!L^7N9mfh@X zF1-yqLEVMz{*$E-2{Y3()rrN25~)S-1z>7~#Rl39T%h8`T(OX*6&;g_-Yvx;S)|g+ z>bPpn%9Tqa^H=GeHe1(r!8x*rDq6UC5SaqqVS@vnOec%|@kBB? zoZhOU!|AMOGP%CIpW|~T?dN^Ni9sk#cPzKxHdIXJU`6zDyu@%K*H4w{fqYc7H$OO- z#@UbN@@_hcW7t-3F=y{#{d}AW7e3wi0joJqW0$tDLnB~*!=Nk%`p8LuM*XZ_f^PVABbulIvt@P#Y>f+*#3Aeh}Q!h<5BO$ zSkUUW~2a{&9Eu=1~osH|{>jULS_|5b+`uqV8z(`4JSsq8$`&uA0(4<=txL*79x{ z?+!Cpt;fs_WSH-hr=%#|U3}+RcsX!2EHpejMCMGKPQ)SMc_hvuVyRoj&N zzEM_$`8W3XTbWNAPjMLxL{}{#x)o!G8+!ea3O>1kVzT3i7L$ zcKsy^PaTPxU2#Dkm^-Y2+O^tTcb?@rP06}(IA4+wr& z^xqeJQuId!UnU~X8)82p_&c$m6#PgqgvXkB)ew#fxK#8jh#2Q`(XSWW zAof1Ng5ZeYnBacF2Z5y3;EKPvo1!Pi88f{1b76MTs04gIGPagXw+1NlPX?ZWl* g0DHIa9a&^L||Y$Im69@9F6T;D6oG+fj(tW<~v( zy;uDsdX?Q9IT4MdKxpswPY?LtWxWIbBMKZP==FaTj!>V~QGa@(=wAPkXzh`nm(#jE z(6s0EaDAWu-QKI-?JEB$y%*~DE>NmR{YPA_^7lm{7*e-?+I#e>{e7E^)ARk{Ax#%0 zv~_yTRLzmgF4pPPM2aB#DQ*_L*tjUxv@AXBzIHjw`okU+;ll|GR13t8qW= ziL0x65AQqT?Rqomrk-oz+}^`oZ>B9886LC9o7VkzH0^rlmabo9-*k0V)c;tt_VEKH zSyUu?^|Avc6Ikjk$&QvR>RmatHw-%$P3`sX5*?10T$UYKl=ehPm13B`$Q#Lz?(kBj zF>JR;xuj=b*ddKa@CCgkdfYN*Qvfh$KQ3%jZ&EGfJ^!dq?(UKt@d$!Rf`hL&8wC+z>L8vjE zLA9RQpI*22F1QsU;(-d`-OO1;JRpD=+ojj@H8u7VmW#GD_PiMl<+wJI8 zDLp6Cy3a*-MI%`~$HNn%moDr1d3apf6M?GUm%83;U$iW2FPfXy69w~VZDwEOFhjw5$b(fKEU_!Jgt9Sch7?r|$y){#9@w@J%-U(ClUuOr4 zMN$7B;(XHc4>Y*$IcnQ`_=>B8h-Ee0qD5Ze0Tt8Y>UXb!KREO{mqiP6cU5@OdrNX% z!Ag_9yK6px-w{k&4-wnDZK_SL8v#(vh3pf8FKdjHXI1DpfT z9J%v9%K9T|-QT6Ls2}wobydXR30L*`kHTQxwS7aQb}$1Xw0-F0v(a2ci-Lp4hq^wF z`X;DR*5q)sM=0oJkb(or$~y1VlfQ*nX?Qxxcbtwn8n|@_w@^-PdS6csbc9jjECyU} zX3SaLzeOcD&-FJoq6+jGp;84MjbQ)kzO*Oyk&osW3-sRoNQP&<7o_AT?h1a6tk7GZ?fHVkWoThww5z!04! z*7x~8a%p|H(HK`d*O0+J4i>Q!y(HZiYtgeWvgd{7NbCCv^;YAp>u6bY zduGqcuy5B=BdzBzxN*S$5`=RwvzoXj>bIE&u0zQ6oILH=(zAwUlZA?XSG@@xWLyD? zyL+!>$fdhh_CDWpJng2ZAtYLB_hEF^{z0s&O>r$om+b{Br39250VN}wkQOm-h+;ka z`ok0RUys+d>$x&_K+1fHY3a@5BSwRZH*#p`ri_JG z?*6{;xtOP3aupYRFoK%UgT^tsp#{3+e3as~ahnV-L2YS=T3INc1V81XbYh?mcNIcL z+*O+%bH?+7FLE$Iij4ExlxX3wp^o7E6U4_l^Hv~zR~OHiNv!G)gN(|xzG2AzJ9x~oFJ2IGDxdv{+AeqDx z8(o&=DoV4~LxLXMH^U)lBRNglLa1ac2^ZUq!o~wVZ~up$LLJ+nfBZ-Ko;dvWOUvkQpp9=b!XXE8HMT5>&k-E)j4 zoprc2NsD@WP~RB*IgEGL1%5l`I|}MYCk{S|KkmE=gV|=tjI{1f74IaAbCfPUVUQcU zo{@e?>uv?+YBpF0M6IV(9AYWqg@f0*957ET(czZX-OKJk_r|&#-GWr?cC|KZznf0= zZvT3P#RY6>Z`sS9ysLRHi!FfU)TF z+peeSxB;+rht70uOL(F-H;mxI>Ip1l`f}S5XVP><>1c{)b+*eYlXBUhh7I)euY**2 zA?Cjo(ByQ%c-tQ^9O!wsHN+t#KQMVQb9j$w(@@EEQB&}8a1i7H+7Qpt7C;LM@8g--tu^IP0vF>YWDzKs>P8{gic zyp7sJX?pM(RBG)1Q8z3eY@uM8x0xT9x3rCV?3f0h@_Kf{!LDL-8k!E9c3nrht+5!3 ze2ER15y^GIP@;O?{}&@RG6$!DvzqTuS-WmY5CY~Wf1CgM;Ad!pFn~qkO!U^^-5A%d zenSfb+=-7PSGmD9)K=y{3iDBg_UP3IGnRBV*_NPUzxHRX%w_ta=}N3X(w_8B=zHcc zszf8{2YOyXLEO^w3YfCg*xU2df1f;=zwhJkq8=rw@%a6vAAdK>)r6N(mi9y;pIu$$ z5V}3jp;h?I==PN8@@1H&($k(arkzYOjEB(^F93FZ?n&$3#_0YWPvBRekpDUvUgGUN zl=eh*73b3K1t7=gM##c!`U?8~|C&uP9rVm&pQ#n-jqr@9n#0*^E3m$2Xr9}(G{6n* z=X<#7moX*tpq?JOKDW}k8#N!ly=(MXxQ4TNZ03VF&QkX95uDb2D;n*Z#_AvLMVdW% zpywbQ1Jsc9Vfj%!o+ii5Fi536FNa6(dPce;t!FZYN*kszP8qnxz6qzo5h%DmzwSBq zr%t=kB-Z{FOc{IzfBK{T6t`Z_KCHvix^Drwv0ujaU=PY_{HWxyJ*Dq9`WW`PkGN{P zg3CQy>d=#EYPO7G6_VDyj>6$cD5Zy4{Q3sZ=I|_7VxgJVy+b>4XeA0slEW}vyLy5V z)S|$s|0B_av4DD*pocF=dVb8lzRKn*AY&vPJH!Ox2UEZYp%C9&^gmO+JXyKfI@U9? zCv*|>v=~G7vW|lnm17V;;3*8LR05;k{ZKLOiDlU@9hvleTF(TiG;9R_$@fWG_dGbS z=lFr1mk`I#H|j8#tt

Y8qxc;lXIR897qWc~%Jw_+O#pbzU3cus|%4h3fZ#fTm8D1&Rc zEQNJQ>PpZ1e`^eBH24z6V!!0FN;o-TtPf_uNZ2=&cus;X#r8lI*D1_0J>S6aVfUOS zU{6Uek=s95B=gR2%?4iskJHhgb?G`I4TZrKjCKhD*JchicWr>NiGi+Kyt55_{C~KgKJWFv67^?sOZ7>aRT{Y&jBREA z;qm*r-u&^1LO2C-Rf>6D%|X5U2VZ4m%KRP+eq<0-)jfgr>6vZ>c7F%`;I75H?*^jB zo}L;9d%>(W6S?Zx@iC!7a5^?j< z-ydAqulj}k9ItQJiIcqtkQh*BXn4ptcgGcU=4QfPCIgW_`0~G~=c#*RFQVG8?85bh zw2O<)+t66z;lGF*Heyee@y-7#WAI{dMmG#8%8W4Sgxg<(jkphgNubH}`xbcVBr4&C zK;gE(47DdIhrVJM=zKGHBRt-Z39|9WR;pK;Co}%yT3|3j9=my%jU!Bgl?=UUMd@hp=wL4v67(7TfN59*X!>e+A-{_I*E5KUk>0_GDwbx)+9%P>6k zBP#puIMj@8@6X@&)Hsx|=qtYuOA@*(WhzrbZ1(>)Zg-t9qva3oc@xEO8TK>x{F$Y~ zt`pXtV=OJ~I^o@Of~CB!6C?JpU&B+oPK?|$lBF}dP9*I~XDPkwguUl1mPYOw2Y~UJ z&IKN`2z|mW6Uif5(ffg8)v+TdN+k^}m?lQcxjB#$Ey!VytN;^?rC2VB`X9s^G`Vm4 zgYH<3`tK78+@!Ne^a?K*jz7m-(e>Om*`4p-waq*^Gp*+kXwbz@aF*;4OPoZL2Y-k< z{qFmSyST#fr(jVMJx}SH*1ZpfzGwItPLp;4qd#4JVl<{p9s4eXqUFa&U>RYgr*%II zaNTnh@FN&$h@PTm#EGe>^AXzpE}AMz4^j386&SV$H5`0>>4LbK7`tA-RWz$^-eBipM_we&Q-1sn*-i(3VVGJlkwrO!^ z4)xJKhL5h;wZ)tnUO?uqmRw(a9UYp#?}Nu>osRuH*`MffAfyrdh5+!>jKd7E#Fke{ z%fZdmc*0b+6GL|`N}8kRk;p@*Yd1}`TT0$)-(=YSW8X9Xz^K3OXfDZ87AJ_7&K^-uhh4m_8#5FD}S)*~)9h{$Ur zx%xkn=Z5IAbdsi!J-pi2^ARUab_^-H>-uh^j?ede2-!@QYI_l5iSJp_3e1MD=DQz5 z>-%XG2KcPl0G|Z*V1ybthHuegi&qQO_5kpTU*ds$1>PI!n zAMxX8unMly{qMdLPKr!Zo`7k5b)G`op@C@Ss_?;Gm?vY;Pp8h2SEA9dIg+VHZAT2# zi1YO+`xwoMjrBgpXauY5&#PS$)v3cRN9V)ivRy*Q7=v4BpseTM#khSU`ZHcZ`WRwk zv7|c_^Ue`GYJ3-52J^^jld-28)dt^>@jX?4&Is|mRWCAHv*0F>jyT%sX2ap5gEeqBT2VL@*TjuOpAM^8L`` zl#xdc|L4e)3a5@dBx*hKrcl+}XlzU$HS)Nz&zY5q4=qEwe@J(n5`;HH!T3&;u9Gp~ z?rd|^i87}hb(}DUy>}lr?nQWE{U>;+459l& zGDJO|v)GrbWuf*A?LjqpH8=d+Nm}XZ4lDcDkdr zN27&yZ;5@NP<8^Mg@_Z@i0%GJjg;P!lmmsbwG%Bw4rh&YH(^T+oHIy2P#D|XVoXE} zv!c}#5M0t#=rWxQkHQDYK=jxns78(XOsnqp@GeQPB{qy@W4rrV*dVO5d)%;fC+4^$ zjv``5$zc=W&8eqc`7icdzm>S^0{yt>S~d7Ox~%d4&X0UC6(3!YiHL}$2#K>{Z*AQD zvz_3r`dc82isU%>v}%XvEH$O*cpH3B(b>DyiyAP`4StPdW#~ON>4%4$ zFC7$f{aW(S>lryu20zOgG8^Z~aE453;|!Fy_orbe@vN6>m-a+ORrG4_@n`XVbs6NS zJbOM$SbJgbitojGYx%+>_PjuqB;!p`Cps|dK$4)B^;%q#?d$1>@8m8y{DPctxfXm)OdsJe{%zM&KmEh*boahdmG|KaU* zZbckgu-(x^ccOpNdLDsieuVs_o@WQ|RsGg`Fz$WhQ=r9-wh#7ei8=;8xYte0jr|{d z1@E56nA1`-lC9LUQpcEM&2&7McpSq@y(szO&(Oe-}xnXOHrzR`-+h|-LOqYPt|%h@oJ^&Pb0ofOk7&0veslZ?`gIbfN3 zE(&<1F;p)(d3170GHa)UXe$kgj>#~GM2?MVFoOIthBO#zpQ-hLT81&s8`s*&fx;7T zROAdz6((6)o;G9r5IV&3%rg`lX>it14a1l)&YYg2tUG&z7&TEVEOpPxGnb}_!$+`M zwm2?(M9gu9F)0sDg}HK{y|ip3O`AMa$AfO0GMvv)y{V{2Z$W$3o3>yGh4an@D$MDN z=|c#s<|Lc705i@u^E1eAb@CeIjhQ2ieAJ!Ao75vWjv;E#mL5dCyiuC-7>vU?ahxG_ zZk$d)^OF&WV^M8hyb(ht%pVeA7z^Uvq1<)e5Ie&-pX%0*RLWkk0LpqGVxbhE--Rp~ z#ziqn$#naWtcx`-L?(T(NGnbhY!=6%xVuCvrYkSiCMVP6WpVe=vLMcji0{H7MoUu` zA(Is`Oz6+zEaVLTB>XASbaj8ELbXfzk%jEGr`Kh20&emZcIAI~uiQR~&Y zC|cg6561(T_FnXe8$l25zntE<2!7S*^2F?^Xg zg*|ednGLFEir05PYL0X?YWrS*n2~2_G{v_G3XaUuXu9uXm^5;{Ml*eVm_0_GsnIN7 z7FnI8(FwkzWHmvf*}ly_pc6GZ)#s%e=V&y?w+^%76ojkb|h=4z4KY>YZdgCDmiARbai z?x7o!pQNwiT)JzY>R}sEaS~=Ec^L^Q3=o<#`ri;iDq}*Z8(ivi zP+NhdvTl-B*!&%%J?U~WJOl?OHGGK19&Ys7<)5Kw=V4IW_BDLhmu#bkeJ#ldu;lyD z9riYf)G1!WPQ{p7>&tx%BPaPi=;@o?qbt&#zB#I6?Bt(;iEqI}axW#h0M`00;897> zl=S2~A;q`wfMA))FF~|#alc?$$<*Ap$2U3YCQHWcHA+SV_o9&gN(+Rh^le z{28%JN5LY`lm*GRQhFu#Z#`2MCeMVjzSZ9VXU~*n$;%KjzBLM4k^CU#U9PaI~(uS&A?b1oRQT>A8>%7gjO5?Il;mvQK$<{RY4julGI?@{ zL=SR7O0FMjj?IFDvQt9lod_DA551bwBxR$Ck*M=ZZ*{)e-`s!dx$}T;GvNE1Wx=Xpij5%sT#{1ANWk69pXM3hh z$Vj5N+jN}?q@0mU=#*DOsSvAs3)l=65-o z9x@+-0b^1|&-xQQkh}wGjLy{^pWd;>7(JVGn4jL-7B)ubDHqfK_me&Yp)q>SZWPC) zr-t(3SLwCXMmKie1NYSRZtNU^8&Wq+6NlQ#nP{Baq&TJ+o|P~r^$QeYB6TM@SAk+XS3`ZDb2DU)a()d;vJ*x* z#W{@fXy@xNIMta64r$I(%&zGUSQ=xT91Mi9&Pue+a1NoI>Exq4&gp@Ej`KF!p5d%R zIm>B4pNw~|fW$MMnXu(7=X{tv!D#}|vz;PPCOY#Wii9qY0mE;{amL3{WINp6nAr+U&8nq&Mk<$nNBHepXIDTpXWN;pw(>W*U%x) zF~MPu^A^f;ohbh1JO2QmdCqjSo$ovV&I_C|_9n|LZP zoCy$bIFI5FYQQNTrxEV9oNK|_>pX)IF~V5_bw@fSsGj7sftT&v4CQ=I4tR}nzRZYm zI5VU;XG77^PCY28&ZE*vA3|!nb3W7^BHqjXiZs$0^gC^NdA9zl3eu(m9 zryS)e&R%ey>hwd(G-nhj=Q=ImGu^4e-yG)_xOIlpi%^*9T!L1!oQ?29uCq!y=^0p& z=RAbJbDW#dwR4?zl=Gdh!J>K2r{FN(`8C=uaCSk%^BfD5^PL~y?*$Ii=tAcx$`?9^ zpyx%-%V>46vl*JBlVIaw=NU*@;_$m`OPw1~bD!aS7tVdwaJ~*re`+{?N5lPw(~FkR z8O|4B#Lo=pH}LB7hO-fk4;aolxOdQSIJx}XaJ~s%FBr~J81W0k*$&-aG@N8~=PwPX z8@~UQ;XDW@|JrbV0I$7dI1|C_H-@tTRbDonFvR{A5`ev8IAh`J-x1iR7|zoOnm-xN+c4!#!#RKs zeamqE16|%WoSo?8cMRtu5Z{Hhu;@L*`2JuC&HiFIub_vH7|spgGH5tkA?SVR z0{4AjI1$)z)NnFT<*$ab5@P>mIJZFThlcYESbtTiQx=FvlE7M0%7wn!x;zgZ^LPV^8YcM-+}d~hBFgfJ~Nyx z@b%}0lLNn;G@Ldx-(@=EV8eB$Q-gNbo6bW}smpZIA*kDQjzesZ>EyvnH<-@1Q1eF9 zc>>r?rn4QU^qS5(NcfWJyou&f)A>1^e6#6{hkN===P1CJO=mus-C{cLqFuk~d<_m6 zFr5!!->s%&V3G3`(>a88Up1XHgxYPUb20S%n(2HSW_}%-LC@Pwryaq5hv`f}*nGou z-hw~xG@Y|i^Dfi*Ex_Fn1SRglJyf~Zbc!J1KGPWc4m!e4P4!#=`999-sc9ZHB^W*~ zAX3ximYS@YSu+0$g;U3PSRUI6*V(C=o-mLsOi8KZq{tas8atkAa7Q(M4++f|9`ZKjeqf>p` z5EiM+HJao56dq1pq0wC5RmdZ$r5c^<%cdVM(dYsn&sU~is?mkMHxS>cWn!vl$|7Gs z!YH-e^Bye6ve37el`Aw_?7NzBD>b?zV*z3y^)k;~cu1CUWf=pkP^~Fg$CbgQoa~dl zi(y|T4}GQvJh!4emOE=HsVhD6pn&gQ`ev0@3MkE8tx>P)y){x(E$KdidYLmR{c;b> zWADTm%1XW3bDYe60fDJOk6N7@z7NQ3twz1R{d7m2Ms447?A~=6P4Ugeph~URXnMv4 z7y+pbLl$OcY=F4b(2#|h84?kVnt~Ns=J*DzfKu0M3RYy9WY4$jyD7fujHxebG~M?E zjp@+FWcseA!!~=iA{%(7Wcdc!8Cx`(?YoACZPjgae0vxd+ccW%n}k%CdYwk+`snY} z>pkY#Mi*smXn^&-o}F+!W9oc%K-BZTpvArlMqHmKfPU~y zS>dZE=UY6th>~R)_b>pzqCDq?E2}b|V3&MVQ7kN6t1|i+@3$$6=L}MM7y)0?{&q-t zgnYiPDdR|ag|53(Q!+_;k(9eMC4-cM$SA4zXv$bpo~29g)s!)$@a%Bv1DcXf$~?;Y zo~ERcat^Xh>SLOcN=g%*@O@1gO^OYRQ-7!_DWp6}>5pqlGAI~E3(+k}UWR#+*Mr_3 zyBi&|R(m(&Bl>2KYLN^pjf|HWP0wf^u+qq=B<07N0xJ#WiJxc+tTZxu*a`bI1y&jv zhuEdhY6`40l(&AWDX`MW_!;Jx)cu+QD~*g&_QP|U0xOO2ZOsiv>d!Ori>z`h&_BzQ+%Yfv9ErvDK;s$F)_cODM_R}z<&6Jri>)zeb#wVQ$~=I zN6x?06fY?&==EP|ibYB#bMdb=#Y4(MM#1kCWdz2vH{%`3dR0+I!t>sY9uA;Gx)nU{ z&1fOz_nHFFdo!vys$SO=c;1_FIqiBwQ{Z{8ii@{21)le2R8Z%)H3gpc`kEMD?|7!k z7_xoO((Ui*A(i5r!XE#N=W@B5?)w_e8Pp>z)At7B_kE3KsU-1%&I%KJe`H2Es@qQW z{hUGiSB>WQ>M8ec8qM`>V&xAtI@h;?oIld&f~-*MCL{Ilo=;`mFH|YymjbmR_id)Ve`>VY*F^Uo_wd&hm?WMg=YMGf%Y6H()u(z|s`8c6Uc*xM)~I!a z*HYU9t9>s}$s|iHE3U*aS^{Qcm%{H^Ix8hJyQNJ~nikCAZ~Tcv3VvZawxM?a=(3L@3WxQG!p zMpLjAU}SuUt;Q;f2M_*6#sGbkq3a-{8opIjIup-y>;SKC8kvmKsI8Y*8cp#%a3=1a zq0w|-EnJYAWsQ}#nZ8Rng^kx}7OdyiTIQ8ZIkv^lNb-(E)y%K6&(E}YcWfEVNJ*V$ z@##IQt`pmMmR^u$bpV?#H>lWR=8hcQyWD-)#dQapr_QjZqIHtD9)HjDrY^SbL*Xp0 z6PH+Ark}MQOF65J#Lh5gtYyN*7+Wf#G0!T;xXEg3H&W+Y0U1ihcy4v1F3^5bIgq|Q zPg5iZcGBGQHHA4aqmS`Y&tx8r9ytNaSPhO!@v|jizTo zp#m!ct+}j7^3teGs+?LV29C9mtGZKHS#P3K)F@l6-D6}mqVXEJL*G5ac)HwDQ?KoN zn0ev~ji&h8>BB26wR%YR8N7RyMzeg}4@$jSGtTzi$1V?Ae}+uYl&QXZ7!Yf%qk`u6 z?q`0g(-DxX#`-$znB1M~yBLEZwca`*=mKAmVbGw_g}%dFCxW(4H{kHD`C27(rB4aRsdhnXjN8gXtR;JQKL1!xs0S{jjr~|;-E#N zSNddzY}M#mpG>N48g1|`q@Z?p1w`mFz!Iq43I5}_E6eNNz85bc6Qg>(y62X>?UotRvY6=p; zmWPiC~MGYOd21EUmU=Y-dkhuPI0kTQb_&9bKA&)UZY6*Bi8T+k9s*-fy&~ z;%U*EvdctB&V~s|-T(q7$;%{={nUCW3G_|DbMA+ObOJ zoz(ayi#Kh zzOG@bkugh6-F7 zW4xL34g;ofk(xPQ`2&N{NaKLdTo7}Rk;VmS=6Q<1x!4$!nK^sGM5qfTGV_!YMlzQ< znRAriy~!NgzC+pjC8s}pUHtI~KP3GIOR?7u_GBpQ&Im)%HH^uynx~;ZE z-da%p4GB8{pF9UK5C51eWx#$1Bz*fE7(4J2V2bxj8NW;;lLO?mN(OL-lAcg&z) zbHJ5fdosh;%mLstd+-OJDdtEFJ@aoKF$%lgMguayDzG|`t&RGthwkbEiAMcZmby;? zQ%3z&9JUG#l@V%H{S)9*8PcfFm_7^Xb`}PKaUrY-q3 z;Kh}>8(IzXGilz1=F>P{%+EbcZ@9f9x21EvVV?9HMs+?GPyYl%5I=0j{`wp6TnIM> zGco3koE7+!+s0m6D81ASYHsTg{s3#Kd`6bD{|)S91|o;iKgE29(Q%V% zn*3mrcGHdGrjfXXUoC#23D`cIbhv@d*7a{ZF*EZ)eq9tI>UTa!VYUDW6mWQ@#bR|D_R3@ zZlA;b4fFdheyy_U2NrGm8R{!#ekk115V6xay_pKHCLVzZ^Kn@`dnSC4^YrnUlgz!=3&5Wz6aHd?`LuMo4+GuE*@r*59rcDeTHcf| zCQGIpE-1>lvZ=Q1ng3^4@#Us;O5GUrhOeXt0xJ0@AA(Jk94Y)Y?e}w&6@Y3`s++;p1 z`2PUUdyKub*>eX*=d8m}?P|DB#fMj7J|Fj|zk>{8j!;2P{O{~)g{L6d8~Iz{+mCR~ z*-7s-dImV543yy=lbK3^HF!e=9=Bi!Y(s<3*hd(K0qK;7L76Ne8Zc?bE5N5Vhmc+Z zqUR`hG#7)e*5roq`M~BkA$`leoOCpp7H+{{y4vIet~GG`&RjGN%Iz9d#>=e`EH!7U zSTR>j!;3CSW;0|anlG(q34K2J%n~K$e=$~SZbc@`6@Drl*MNfxM+<@YhImjh?}ve} z!S)WwJ%(B|a+4T&4=BpWO(OLZ;52HB7{yn4bC`n6t>!1-VGSJJK_jmbspr#QoFdF# zb7mUY<}3qp!C5Gw;--buQP>I&7v`gI;l=oa&qZb>d+krc;Z5jNH3_R6choi?Rr*{-ef|Md^tqb)%*8afRP=dq7aWvxJ3P1ybI|p?X;$TMt-S=j^(AWY z5GpTWf{wlkA6^E%mxNs5d%=he@uR}*CV?HRRndBW0Sok~Sn=^J$ z0knJo$?S}s;xe=FAiCJeRFw-iLmkKAav9Zn$YvhLGLYXun$xb4i;<}|g|H%A&mb2_(nDnfJ9x;g9X>*q8rSa|;I=BC!jmf7oDBXbty z&Ci?f)*jw;T~k=M)y#(9Zmo}WbcQ++4t3#hUHyhU3G z*7i^*iU=Bzo7zwuffJcc>)fJS0qw#~Eg^MZ^FpJJ#`=Zx=79$r4}U<4cqJ1hdMN|uBmxl8wHS|hU=T# z*3~uB77$^8DrjE-LC+xEU{)B;BFneO+PtXHzI4gl zE9}dEV4Zu(!o}rJTWJTapX@wlcX&P4JKOBA*R;N8+5KO)-?t~(8Mm(AbW!J$i~jw7-L!l0#Y?R^JKIw{+S+Qb-fMlb!@g(F`Wvl$&lL0G#TVPVKe0bv zl6$LluAOJyztdi1rQ45Oym)cx(nFz-tpkSrh_!K#{WUvi7cHLMWv#Uvt`99uVym6kHQOfNY-%@+ORyO2Lvfs5M&pdj_ zUSNO4y1E@(Wk6apBeD7V6OD$icwK;5!zQpdDz25$wy~MLT(|X>x-tMtKwq7ufS;_qk zn>;z0=&%0BZhOgV1Fu<+>^S%lT)xKcTx^Z8$Ntj3^`cGPhptn+%+CCZHTL?a@5{e)s zKf_w%SzucG%zo>po#=Q(!@;ju^P#@I$y#lPHy^UTwbMRk4I1~@i;JwSuP!dMuDN7! z*ZSQX?71CQ`9aTuOlx7-T9Idcb>}128^$ra%vxjLQ)}>xVnx_E!w_<-p-J z-B#~TI_5DGfqBS!V~1y+xwy2;$|do6!?Vz|=6NnKt^0O*W}DXUc6b(<1EFO%)uE4_ zr|rGgD9;wtlRqx9J7TSW#G3Gk)!1*HjZoUN{tG?!t@hHVt@MM|=0?l6+SGdn%< zbNgDs^Q`sPTi@U5!O7dh_GUy3YA&jm$7q9wDRzJ7UhC^SJ@d^ev+`?~);BKQ zd*wIg{cV}&T)axkv@Tp^EnodTdmt1+W15_d9<_W76sG~;F;@KFBuqG z2YcVgvlnl;b@#xg2(C@L2e#Tj$A5!+ySjGUPovswbGMc1Ip4Il zz6;ZiA@Mw7-M;gnC+AFS9Q8P#8r6W~Ik{dhiuXv(DITG`6*45zCZq zbm)9-VEebzXsmB;>kJvII-0_v?8drCb9j;=b&Kj+r-!raJ3@85(bOCcb>QJ~4xS%t zJDXb9XSX2#*4MS?<>4z5;n0@woc88AZ0gsww>LM{*M*zfTIaO4b%s0ZJDS?VSbycs ziA_W$!cFsTKzqo-i-iPXvuDpPkg2OB)Ed4hds=5U{}`u`jk*Ztta!mjQw!z^qb1bY zDX^^})QmZ&Io#A<*AW(NjkfRx7__OWA=GA+mj^2<3j&uK`9`jR_qDJ#L|MLUxX49D z8UBurwvOzMNNX$YpFFK|@+708&2>a}sG%vG4OKg~W;dc9R4svvA|0XZa9egqsI{&| z{20okxo~YuUATTjHp$^o3!E1Yh zY~@M%g}kSA;<0d8eRiO#j_zxi-PYQ?6;+JV?1nZ<-q_l)x0_k=BO1?Ch0Iq0PKo2Sw25d4^G5TJBd$u?MlFXo6(a)Lps>4dT?zWA_!c zwY1c=Ho(KP=grNVH@7ppIHbY^K_h((U5D43KR0ha>J5(vSw;lwH-zdp2AkX3Hb&Zm z%}t#M6?RSb>?Puuauuf8{-NIK2z@cq)Dh~;o`ybh@7K4rAY4P*-eFbZ`;ngIXpl}t zG@-=?xH#0&317tZ_po|+xz^MkS1>hKp5kgD~Kzqn{BNVT2RpfxUqzM}uFSGYxZ_ zo#OTK5G5Y9VxMZ13R3MJPvPhh*_yf*@Ech0xb(`d5hXWxOK-%o&%oY=`T%Lb<<=?f z8gYXcHQf8$#Nv@S_kKyj{k3?sI*2-Qzj*YBiiG>z68RSK|Y`G_@ysbzr_1|MEYr*{8DjH7g}J+j>}_U%?C)Ip==Y< z*B*mUoI{^%6iuUQGQdJrya=F574bLr$wtXEs)s684^<>%`K-m?I$V@aSg*=9A-9v` zrLP6;PPsoI@CeGL5g_=dkRvu>8>|4CV87--NNymbf_&EEuV&^Y{2MOQSV^Fnr4XuC zD^ZfqTKs(im&X{e33b(ULhcukPN-F9EX!vt{%UC{gb(0?6A3hnOv3*tG6A<)V0j3X15gcYEr$~Gal)Z;srb9go~7zbiz6*57>lSPAszM1uZ9q z@Nry>8$vB7B~DIeoSc+6IhmBBcn=J-VUqA0NGH_1vj~+v17gn-u_uy6c)yef(g`UG zx?~Y5dj`ZFZ9^>9$PYg=23M|pAAoF7bTvZJ_34n{Nc;UznC~bsFdhNm*B>COop6o> zN`OF%YIiw2i>fE2RV)QDV0cCX9eE)nE9n6@FhF&K0YwW<+3~v5sUnJ>0#GiBlv%8b zm0CQguJkzloB7?A%f-?v0_C?z^N_D1&8KO$VLj@yKVde3Znhz=D>t~!IHP?L7l$BW zrz+cod|d-~+3|J%NA3?8ge$NK#QTKRQXUY6_A>4Z@!M{L3$YdYcS z83gI_!p*F$&xS(JP;hRtlWCE>U3gOovA7lch zQY3|NzakTy#6>2AJUfBf1X^iuR-a3uM!9HIl?5U-LCrTHPD!r13euWzfy!@meNz>G z1Fo;*0@dZj??=s4oCvhZ?Jig7(*8$q*H*O0c`z0kD~H-O$F*yIAMGd{JeuR$HM^qO z>y(F8#@m~ZqChhQVJk`$BnJw!69sYG&O_TpxDc!aTI~(5X)X}C!DYg7TtIAaS+Iwd z4+BvYe~1fyaXT2r*Py}Qam9Iym7Y@-+2wcR!rd!SiPBJ{quCBcHl-0LJ_YsZ0TkKE z>;@Fs6YOUc-9ARqRgcdX{9Yo*5aB{qwh8$v7G}l95bMss3kb$O;nPx%*o3cXIw8O1 z#dd^yq&y(-mT`(sxLe8t0{@2BG^|g^;|t_Z$Tu{k6Mjq63IC$$gi}Pv0fDE}_kOWw zz)Ps_!<*_ud-Q#qa3XX^G9~z;m=j4SqYHIHo*nTIq8HYxIiY*K1+9f26CLs(&@4fae+*r zyc9_%yaE@<1YZ~DMbZhMQ)B||CwOGYPfftkFPVhAk74rDh+E;;ApStS6rg9O<3fn} z0Y;0H0(8>XRgpfr2bQA(V?a3|K%)a#Gv@S~DS!Nh3WH z&~lOqYZaM5hf}l5VJ|o^V$eejnoKb;z@TBofXY5oE)FnKXdJT>u;nDE0v`j!<-UalMUjJ{aLw#VJ>i6DZK(g18KScg8P1*7PSMbVXmBEKZ9oV>~v2&yX%MG8A6;j=1U6!QX< zc`5S3kdt4EH|?c((_RwOC`a13k_2&O2@+@8OEJ^9CuZW3O#(nmm2E;ET|tb-<}}vb zDfb5img)P1s_uYm26hwhzpCpcyb^UVhzWwKSqdSW#f@#Y;T1D_LDF%|kB}a*$36QIb z>j0=2JWgwQz7~cP+^?tvuP7>k(k0d<++2MN7rTV;Jyo^|xv?7GC9Hc64t{X)L%0uz zZD1C`eq5|dSe-3of?8Z86Ovn;6UKu<1Q(Pg&??2YKN zJ9+L`4B82Qg$rZ?twPLy4^CFH=$OqtsE`NFf>6YlT;x|;p4>6?XE)lug9|?Kq2+lZ zCGaJHy{b3?t;i1*z6fxQD)s=7F{t+ed`lI74=_i^D&hF zBeJRp_`{pQ%P#a@^(P& z+}Nsts$L-KtvU?wdns1A95C^af$GNC#1rSqCn5GJ(V&VI=?nPG6@;Se628#*J}$-_ z;SW{WCgfQ#=od@ZtoyRu9}xI^lo3S)ZwWbK6S7%caJ>Z5E4biM0$sD6aMpAo6P%}H zwG);KgK7e;LM-Me{*S_J)njP&17T3*)`VMJyIAp%R1Ca?N-wL5D>chF2V|NwlAkwm zlV|qj2$Fh_8tkmw6bcT#LzP4MazF9L8`-*HdsF+c7C*p%k{0s%G@jQ>h<~}mH=pr0 zcotZ0obtlb;2BQ2)zlfRi-g=6b|AnY5YBU z1M`ITio1PP28)B&9C@j6_k1J zS={4Bko$Q!10yHXFxKiN>|DLBU4hlvN4U5GU&u06rLzFt4_8RpxK`rgYRdim2#(x< z$!-@e&X?}zInX&xzo6;60r%j#6&I)3)wtNM5LX#4PSNvlan|OP&B;6qkkdTpc=ywf zOfeTxl7+r!esDib=A>68&?N>=iOuq0O~G=bva04%zrX6T+ERZFk&>dKqB4I$wGoW8 zMmj?c^GK|!F0H63_7_za`;8#qKex8U&Qo-R!jX>FV0&G7gAr5!@BV|Kwq~PdO_jf( zVhuTzRuq-h7W*qJ%GQ*WRtIWu?4mP_*WG;ekE3}l2x@S^sghRKE+{LjTvbpJC^eu$ zki*TW>#T2TG8)@)s3cg}2Il3#RVymX{K4{o7*ShMSX)x!ul5(0R#es2;C4~tJKW2nIhc5Z0v2=lBp?x9h2!72bhnw6Iqml*zvmHx8IDnIX* zR8|*}FRD}(EcaI%ftrFEKhMkHWG3=JYdu(@VZdKejJu6I!(s5G1shi_uYv-V)&4+j zA@S1kf~tVOdZoX*qOvsLH#)brhVgAz)})UERb{0$aAR3fu-qRAKwLo1SO&uoz_xII zbKUw*&AMoXzv$AM>RR}-6$da3bj*5mLsLVmItW2SgKdqCXpYkfa<-(yXvgt{w$?hF zf!PvN$9+1(!Oo^@LS$NqSg7!?g0x~78Lajf`Ab*&i+QWOV71W+rv>@rb2wsAzme3E zf&d&>Rkj9A&@dRNEV>kt#6u3P>*Y`jYt>d1RhE^}^h;{Xs|@yN0~!=mRnck1ECw!J z17qb_DAWxGc{)k=&*~a~b$P&FQ&U<~hC1LUeOnvwS6y0wwt<3`{$M41x~jSqJ%jrd ze)N|=P+3h)g6o<$ihcEM&CPY~2x?YYQB(l;p;2kc8Ux3F+M5~-86$2~qE2CTL1|f; zzofbpYKn>FAQYEY8x2jJIHa=`HmWGEEiSDzf;^5xf$PBw%~w^U!vJ*zl|Z8vMzFLp zxS8jxf+2)HDz_qxHnLEU)3oTv=1>b8Rr^;~6qNgMU>E0Ijrt8dPSw=f5Za z8*q*Y=2NF4C8^k7=CASBR&ZqFMq%Y@H39sWsSaWS80$qVAk1IQaOB(qE!MZSHFP$u zrylU~!ot!Tp6mh3YCp$VMUg5muPsBS=!~rULXanY;YNx3_E2aePZ=3og3Wd7aN3GK zC@Lzbse#K4{0>5>87E?l8i*|@mh;BCC3+^J+z|{$ni>!XO|3X7+}^x3h#wjP7u6&d zl^EoegxYG^YMHYbC^_B-C2%t={Fi8>abcUsO`W>W*$36 zN8uQk8kGgbjH`fw@x=~-G$feHikeF4=z>5|X=%}lg6aTVRg1`GZ@`AeHrUm+8E2t{ zE@snfp?dWChPu}EDkK9%NE8MS0pUCnj@3ysbOTRsp;`yUsmNwBBDS*Bze>Bcp&eh^ z*I^md%#Fs5wibyv4p+DnO;(f^`;{A!k}mNV)fk)WI$GJ;ZpxG~QHoKCFUld6vrD&z z!p5fhwg`SsSFtGeSFET++G$W{wNzCDKL8Qj(1fGp$}Wr2VqWishxn0fQ-)X(ED|jNQZAg_TH%euM{dD`pm>xefy_T<4Cr1x0hJlPrv($#PtlVOSs>RBA%X!8u2?&`y`S z)VH##42c{zSJhT8SNUFLhSG|a1!bkk&}up|)_1hwWSxWoBEPsGumTx*Q&VTtI*h3D zpm5@+yuQ z3_e7D6W1_m<_M}e2@XV9Hesy?z!88rYy`#?h|XBFwG7%|!BlhsJxE_wlIx0^>NV`O za-|{t&=BPJ86|+!!T{fAa_k5vVwc)(a=gtoNflr83WF6jBa9o`JA z32=R0P!=dG+5Qjiy*XuY$Rx49aN+ik{V*dmiv7Bt% z%xu_(kx|zyk3e%aw6%ohv^K5Z5N>O3n}dFBs%xFyzH$8=K82}2ZR@@;d-zwoW}_{3 z0#u)_kQ_|23u;%(8kQcwLq{!!I5TJUYBi|TGDR)DSY@~?uj)!dgP| zCYL^7j#YWkT_~&cUJPL?kh9ACa0j}OGa^=ArBzrAtAWnpT7x0Rkb-anL$3}CB~iSl zl50?TR^;;#Mm{rYYa5p)V8pe4eOr4|Tci^m+OElZdFT5Yg=9CMnfKNuqfyVNAQ>#_gqhnt5%*b533A>VYXskk|lp^y}tsB3);!G zS_w7;pbN)cLsN%-2^3V1kxBI1r=<3TO# z8Bp@L0$B)kS;zTT!?NWSwb@14@~z8Z-&jFCI1v3Ws~u#t4urR?69S0ULOc?&r?7+< zjp~|ZInGBoJbdFTCtS}pcE%R|{F0?C>97jLQmcRu!Lp?i;x|lWGzBij1R^P}ssR0B zgzLE4YL9eq8kV??-z#jyYOTWzj4iA5urWI8+d2@4@--YRsQ5I1X9jB45Za^$YjsJ{ytxZ5z^sadZK$|`NY=v& zijPj{MVKGLqbt7A0y@`l94a!bIeie3)uI*@ZVRLHphIn~^16g1r!PO&WNW~!KGcNO zg?NgS9y39uJYJwT11l<5)mGF7WZFYwfMf_QuEjB3kc4$bu_= z4&^ojG>jL+YPVZ_23Mxu#*e&jJ zGRAoa!i`O_vck?>jmpWOYcgA6kEW(t=MVIStOD?~p;n);5|I()vP5DXf4G|DQx3vZ z?Nb#a(c;Mo8A*0F)P5L+vX3NSh8E!nnP4mDwRLswu8HbX?oF0sfl?;lN0K=N9Jt4Z zF2e(H4K@g>R$y62!LnWH4mDI;;V)w~>?L7n)ps;Es*&z~kBv3dTnR=+Tmc&pj$J$? z=*sGH%uV$h)LtP+jXVT}HwCdYQcjQUX_jJ}Vztr11xu$P;}#Fc)drGxEJI1+JT-f& za5MBXib~!=th|sKnjjiN zmuvFSl)et#Dy~F|k`&HaO?q8TK*JY&G@=ICfO(VS4cS&(pZGmN!~m8StdD4`Eyr$h zWl0Gh%R=pX!egB1r3@sM2PLZX6s0B$v|WXLXJiBHBO*MC^p=C(Ba@7;cST}*kn(^h z;T{QoF@l9HS-WuthIkPniwsep&(qj@!Z$?mkfol%zZhx4j)2x037AQB*b+yl3uIud zRb^cetgFW$Wy(X^axKy`BN(}lt_WUcBqm7=Ja&yyhaKuo_$DnMq!QmlVh5zsP>&o8 zo(^pNswEj%aubJdeyFEj`C^ks)*)ylYbQj>CL_2>7B+6!Yv;l(%}tF>7|5+{d=3>Z zb%KSKN~Ris__;It2+7Gv&xJ?*XPFaqN0nkbBg6@O|AH5 zpEpA<{fxZMtu4?DFx;Ww2Dj7^YR;2=r97EQ^44{B8hP?CAFNxqjz;CNilWGlZXC{i zCfsjhQ}WKw%O8#|h;QA<7dS3+B+vMJ?U8j{xI^}kG`#S^#&S%Z;TWVDc^q9Fe|cEA zgz~W3oekgMwa)+h2ghUZ(x1Ohs6NX8;@=>K5&3GG3JLm(~j_SBJC>lkzcw_B4Dehhc%JKa6{YKeEezec!ceQRa50IbV zUV)Qwu2R5Rl#>J8)n(#_uO6yKPW3J_o;paRj&cOI?rg#n1EG@f%tUa{XaF zUWYZ*Wa9`7!wdb`$L04HC~lcIN8AysA_eyzb&U&OsrUD|s%|~PxNbM>dl1ivKXwTY zKZw1wpFWA_cjQ5wg^W9);qpVZVV`)q*ZBL%_?y-+OUOT70&zFGR4a==FBJE&V%fyK z&yg_nv5ZmpPkpKZJg3ORF_5^AC6PKru<+yP@gIvvN8&z~M8pum5|72>I64ydu?!p& ziThZ_IAdxYPCw5{z%Ky47S}h>Nn@dZ?5q}OtRKSVeuy`_2q5uI3HS{O_&@^w%>?{W z;^-EB&!6)5C)|HA0e>d}Kaqfco`9#t1qk&$D*@-fLg;>Ye{KT4ECFAUfM1z_^E>SB zhx~RW;PJVV_aDIhc8mx9jsfleQ9}La67WL__>lzMj2mp^?@Pcl67cZ}_?!fsIeRSz z=RxR5{mK&V*Cyc23Has&{JI4ErUaaE=zggG4-)V_3HWak@INNtA0^=Nr^m=Y332Cs zh-W3>lM?X!1bj&XUXpzA_?Z-b99s3ZU zlYlP)&ZDgS9S`zfnQ(u705U|t8Enz7q z=xE?YF;3mMT(wf_5lR;M(ukY%YF|<95;o#wXs6($R* zX&ynmSJ#J>g#9V!Dmz<+)OgAciTYKd_*cF1SSTBwjcS+4-Bh9f^venN4APc%gwfFJ zAoNsgef!p!5WHXIeRsn|RMTp@OeLHY*P+cZ)jRm*NjyQTLzWBzHw- zo!YXI&)s-w%lEO3Ds1qqEC<@8#nuo`3}Vktki>UuLab}p6x3`4msd6tSM_*>A>9Fe za5PKt=&WnS);SJ$&};IpO2sNhimm|Vp_04zB0L+~^ebm}EJjFu$JX|++Tq8I&d&A? z*wNDMPd$&Fuz@Qap%PCnNLl~b6ptjRK_y33>BUypjZzO|BzBy8*lR@$D*oF*Xb^7W zLBI~YKXeCqB9p{z7rm=00_2`Vlb{F%?i$8#@CjXBw1~FxsYQYVxd^)mv5}*Grc7L| zOdU2BrG;$A3ER`0F&8@Qkt2LOOP~ojDiN<0@;6u1{IPK!a`xZ>C0FAMh~s9l#>+JR zKN|lYanwIVh-LWOggCLy2NLp2LjGs_GXRO7qwyt#c=)T-^vgA!^MwZwNpEZV`@}I1 zAJ_Qj8b1T`DCJEiguJzcm|w#hzX6c)zDgYJzoT)ktB60Z@m~;!(SOkRTN*z~2)^wy6&X+OLo@$O|a^Jp4B|QV%7h8 zd|$f$5ofjM$I!YzKmFA8V)gf?+r3}9UUO${_j1o3j~}ZV)>^-&VEX~*M>Ov?N%Q6M zWIY(ww$b+}eercWaWd>t-7m9`>DL2R^~cy0eZR5#d+exft0k^%s=o5+tFhtpnF1*%4r&()p==Wb$tD$ z`y1?>uC-a5AJ=(ueo)sT+xM{jknO0~9pyKjJL%UVcgWiMdrx{^{Ge3NOAo7K%=Y%q zIu2*`H_}7;PA3r#2zY44Usz*t+TT6QW zn_A7+!&dXv7CTzaR}bm=%5~O!jA#1{oMSbQ8>QQQ$643W9;@r*p!NJ(wSP{!-VbcQ z#`e(a!ScIgSQq_z##zVL*;(yn+b8r3N~`PPWpCH(d!1Fitu9x+Z=BWsW%4gpbyJ;$4!NhgM0ly8aj0RDBn)iMoDtE%@~~ zK>E1HI%}NI+vZxv!M4=(h~>7Y&bP+ud3{)VzYfltuS~0XonkevVsFIXQdeZe0ogdOdFXW-*x%Q8`Zfr08 z2+wN#r=-Vm!CB|&-_APU{>=0Eqol{*!K!|De9GHZZ#vw`hCI=$_iXx zINA2qbtyyp>+{7~$6IEf*546U*YPE9*LjT5xp4gltd6Ih)$z@de*L^^bzECruJP<8 zf8abo=aqcUS=VJ{U0d$&Zt49RIX|Pd+3diOkSwcy3a$Em!>YeSc971O{&w)|D@A($ z3}^K_(k5vSiZP)z7+Abj>Pg}k2@~mEW1yZYCa}ejWgfdH6P2Y z=Hs6>RqwCfu6}>A8ux!(u6|=1O3h1xZLjw)>3JFFtp1i;&EqDUre`ck_fz7m_qI!R zm|iz(J8Zb-%j$jbNt|YNuKp&y-%96Bx*o{eoz>3AR%80i>OJF2{MNS9S`BuDJ_j{s zw-YNp{&=fv@?op-KPE#*>iys9IQ^Se*L&aUcurGZPWf+E=O?DI>Z_0YtlDoay~V)gM5u$~Rm ze4;M5kkD|w|FK)!Top`OYsa| zzzV#Hfn`*6e9@u7@ifImOu}@`!W8$a0AIx|xDWk(&h3}sMZAF_m4e$N(aW*AegaNK-;Z|rLR^VOxDyZH=Xe?~ z;cpmmTd=)oY=nMPxBE%O4D5%wI0XxE39iHKxF7vJ((Rr^-`{n)_{hG)?C zQQXfZ^a>Kr*YPIaroSm%emmZY(RepDzy#FODgyhp#AHmx$I$+H?eZHU^|f*xUZyk zW5`}4)%_%3Gi;51vZA-Ap_gZM?upqr5QpPfoQTikES!sra5=8QjkpDOpjQ`h|9;A` z{R9K|x0JsmpT-O5MOa<`3jT(nzJI0i2&|6L7>kYYer$nBn2H@S1AAdV%)wk7hf{Dm z7T|nbf-7+yzJYJ!yZAmH#G_b>Wq1~Uz@IR1Ur+P$U-E6fzos0C^)LZbunP{wnYb8V z!)!|7OvtMM(|i^uR1UdPJ1pXTGNg$*$Y)3GNG!aSUg zg}55Gp;x+b`@do({cq!maoLmf(5(1tV$(`;Ec2*cAt09_Hf`+=#pJ2>uKGe+lz()x<{VM}WHA z_aAK^9E~sFLR^PC@DP55<@h^B>AR`hjl&k0hM71R$KecIfWFV^cDCR?{1nU3ONP2$ zxW1^`XpF~}==-7G-V+C59v0wYT#MUqKc2*&v1&B^Vgd&4pQ^vE<=M@i?Br!2MS3*Fg6c+|EOog#&R6&c#=76TXXw@C!VT zzW?g>{co1G2F77C?1uet6i&tEScJRqAf7*GV%0ej(a^tzwk z@2|KTx8aBQIR+L6RsGbvg8My*18@vZ!)3S{U&l9a8}7ut_#u9b$FLMn;y3smUcm_6 z`|)wr!UotJQ?M)c!4WtKU&N(YgnQ8UgWZo;7qdsP1i!-5cpl5K0&k)3BfA~18ER`_ z9gM|>I2pZ?nd@)BUHCCx#^3RF-Gg-fy4V<7VJGx`XxGcaJ~$AE;b@$I1^6;hMb$)DgctK&O^m+^{K{hQ=UalssARsSArXw_db_NROr=3BKh zpS%*+TJ5);{2`vPs(;C9{1teW?cw*TT>aO^!2NmEk0%H2(<`?kCtKxoaxWZ$BiWv3 z)!#&`am~Y3R{aI;^UEF1YVQN9`UmhZ^-keMylhqfCPp;~=6Y7`HN`~AlgKIL&g2Yo zFB_)67p%saL;0Wa1*>*vkqgO7tm?l`E@As=8>WAM!tbp1zk%TmgE`XbIO>p-$?4=S zRPpYNwohjqIgbU0&6y{aWODf_x?|0Lx ze&6_@!>#%qg@3ZDHxmo2>MtU%!S$3ETebfgo@M)0w%@X9zf$9%;a2T?TRaEn#H`|wi?EH|t2^VGXY`4w_#lVCel ztm;Kt^;^Sg9`40NtNtFvC$PKKemOYSYX9*#$!fpZIM1s7O7y=EIqzWmd*qMEhslAp zXw}X|XSM$$h9m^{zXO|KGIqo)9E4->Ih=z_aSQIjQd}1r>|cK-hJ@;#gg)*A<7rNA zNzNkoCQl$wAuk~>C+{HdCZ8aGMZQYDPOjx~sDJ;~%k$Ba{0KRV+?!m*`{}>_uckb( G-~RxTAG})t literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/base64.o b/obj-i486-linux-gnu-patched/base64.o new file mode 100644 index 0000000000000000000000000000000000000000..aa4cc82cfa941214672ba302b4abdeef754495a8 GIT binary patch literal 6284 zcmai23vg7`89rz4O|qA4vVnw`B8G=RE7=7JF+w6Q14IHMPm9XB$!?N`WH)5*2BbbH z3z$rd1CEYur%o*$+uEsP9c^l@tqG{0GtRW5Q|(x%4Am(rZG+CVBaWoscka2nH`u9X z_TKM*pa1;l+;i^T`x}~8ODTohq%cID6JjLjXsQ*=6H~-Q*Hq!wz7Mze-&?k=e|=zc zf2N}UPJedPw|CFc!=rug+B>tC%${!r2j$Q?UvO|JICy|Qy#^%1XUx76*|Q6>qcV8p zWk`dAD_~|?CxV0cDZ_!yzTQ=mis3W9?3p^(-#4(*_u5KX|C$iD?~L4ea=@M=vX{p7 z^doNeUq<$y=2!X~ucDlV!bGRYh5Z~<*|3LO*^6)ZtZ(RCVfHLK^6HWL3SV~E$evl| zX0Xc0o-{Gg;E{^a(a}#1wjRAa>lf+~{G(f;9e92Y`x$s?E`jyhwmEwql?wFV>kkeZ zry546I5ZUOy&9EA-~HxcO8OekWrt+&kfo%nBrU##oE8<@;(YevXzL2{i?q=?>@O=)?tQF>+RcsW6q6$;^-B#hD}#Y>AD%Y`szi{j!Np%=o`q+f^vhZLeP z2(=JJ1e*KHrBPa3Om7L+Dse&;G?v$n6JnejS%_k-ffqFaDI3e_Q8Gg`mWL6tbPfoV zBqWywoOI>}nBnq5nw1p@!|&wiL(1d9>XgY&D3)6R<<(=P72Z&d<@sO}Vdn-zE|cFpjgv-0BBCqtlzqe#*;N0 zu#VAqie}5KH8h^8*$QhSjjzz`6l)K)S88^eHAvrSnys{s(0ICLXIph-uh#55YX*HQ zH9OzBkL*nOQyBSXEwC2Tc(#06vDMb&WasD+)mod#ep9n`mPOzBazDT~Yq?dzG#1Dk z6?>DFr13)8q}bI~54G3H=Tzi1)+PGZ$dig)Yb_(YOg^ZLo2)l!yjFf+v0JRS$u?^C zHtRjIH*59|>nz!In!U^Vh-{O*M)}699ZX|`&bi%sg4&Jpb=7Z&822*O&--^n957#G z8H!KQmMDcWTFF6GHzsa%R{sip(xJ6q!$0C(v z3a0e9GPoZ1pnL>(S%bJj%v5(FwitK>QyE*x>JMN(AF8rM5*!uZCD#!r%Q14p9RE3P zaxvL|;F^F-l%K^-Hn5LbDr}Lt1Ky<+RLBDm$*rm?3qbObY6AWx*YOrE+kFtJj<;|K zzX3NxEpvJh_NyK?Mouwrr(?ghtKQ7I?CK;~hG2{5e0 zqd!GVz8CVsCI3b~QmP_Ob>xpwzO)n!-VDl+kxv|_m;9o%1b6ki0I3XxL^zY~4tFG) z!)+}s;Y4+9O;txCnb}v>mdu2!LyJO-!ii){M3B_bsD-Z| zX*(8+w}#reY1nsn#nT{>CHhIEKq4_%xMXLdGY%o#FiJRJ-&ibPY%>C_h8;2jp?&@t zPe1I>`olf-M%&RHE0)%N=zqum;rbhl{io}Viqpn8-#mHrbN?Ib^zWL_*6r}WJ3qXx z$^VXF-)xlC?S1PRWA|xeg5TcjD`rtd8M@&?B!#@kA27{c$fmJx-MGqDl==_*R+bd3 zc)(bjEjVJjdM<`d9{p-6AHev~AjY6=?ui^RX+M$id?JH$E8ixA^oe7FI31T1n+bCi zxsecYq=d90Hxc$ZQoJ>TxwE6f40fMG5_B*e z%T9Y70iMMr#l{Y(_bbcXxGKP|RHEGU)W8oCw7I4bAA{`7*mlHDMVv=UM6iIAsI@!Q z=?ZDj1?hOgQ8%XJwpk$V!R1FfoIbZjB6~8?Si}~QR7Wh5YHdx&ZLwy<*2-0t>X{dj z##t3q|5FWu|!+KUg*Ge4lHt@TE%P5 zw5r@iq%+#RJKmjE((X7CVK0}BIozJ=jE9qnwst$!kqXD+&53BTs%v*!n1;?R)x4`} z?3Pv46}4O1<1x|N9c}B3Bjt`%vaM3xIDiy)=151XWw)cCEYgzcj_*{lgy;! zvFq{`Vu5MIBC=X4mq;?c5BW#BqOpYzz=PZ(2T*r%i}ehS$xG!vMv~8g9YnY+YN|Qg zq=@Jf=c~#h+Oj*-<;*5Ga!6Y{qHSq(-eOj{({+}s`S5h0p5l0>o<`Q&*V zk#R4N)z%4tV~otax~@!f5?Vyh`$xN@$u^1{kFgvw6rq+>r&_+DWXg_*@Mu=0Z4}*o zfWIEEh6$f|e1fR99Cz>5!1IsoN?d$Jb=!P=NgMz(2^amjvGCC1YZG~%Wo)l_wi)v7 z26QcG+JBwh0@!$VBo*&^kH95YUS{_N0&|;mn`_4xYVSCHfpI*6961iwz#Rv7UDpSs zn2BU7JOY>80G&5p(-dc1jK}f0@tQ%qJ|IOcoVJkA%}sSDcyGKdh*t?23UDCUEO_`*`37a>JrG@=GyItz}v6w8Al0p?l>L>?fNjrmxxzMLN{0U5O{CA zdk~LniR0j3O>Vp&fp&dBimPxw!Zg=h-7}Do=6YaT47)cj8!z=Q;&OdxH;O+4t|FnE zt2+tarKy_6q&&^ljfc!#qg2!Gt^Z+1drvyzm-z5s4k2H8IBt%Y$eMWLja1+-8pzz{ z_UrO4dgZ3LFzU*QWB ztg=LDSv{iq^9IOTNZ4{+6K4>M^ala-tOf1)oD)}QT&wXGjoUQFH1gP>eV4{>YwXoH zpz%qKKi4>@@l}m)Yy6wWPc`y;it)=d@^4V`A&vDK`SDEo?HYG!RP}_M-(b`~rtv2l zf2Hvijc;i@tMP(HKB)8$YMidIN+bW|p?;l4{_8=0m&QFB`B_bQzsB!rJg@OHBCh{v z{DO!LpcIcMahk?!H7+0`-V)6(BVrNUq~#m5JgWH)B4T!Fw6&g}n2i6Z#-9-p_c@Kf z*LYg%-_-m&ntxyOA8Yhs`=I|78lT~OqF?UQ5?cj7FUZ$wp8FYjwT^LfkuZ Bz3Tt~ literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/bcache.o b/obj-i486-linux-gnu-patched/bcache.o new file mode 100644 index 0000000000000000000000000000000000000000..64817d5d26b652667fa45f66badc7bb49377d844 GIT binary patch literal 16084 zcmb_j3v^V~x!&i@gq%qRCXfIL1PCPIB_sqQB7!_4An!*6R2=h|gg}ysnHdCmY6zN! zSR!cE+N<8GwH903YODC7LVdKhTH9J%ty-&S7S^hzlv-`>_wD_k{m!NWMiPPfG`{47=&d%neEzgGbo(E>rOzPXAuYLw7>TD@?6+(OO0;g?V`g8O1 z9J&Vjvw$txu1fq@l-VL1+Eez3Sl*R)Hw3ErXnZJQX}LTvNJC^Hn3gqpjt;1`BnXYn z){-T zO4IS|mNS=K5#Dgj)Dz{<-hckPvlAhlEyj*NLe}>1X!?B`5pvim6rbK&ZxtNIv>WJO6BZFs^x0T$glNQhOKj+W$Atp)J)}gH>_vfpRm71yc zD3u7dmONkddTPn>L~_*u9icl0Zd{3QTL-c|95eGkHNXDoERgY}M`r*SOiSGOpGP{w z426zNsG3B2^O4y*ACE$<6RAK#n2okA%H$*AG@q7yoYDE<-~VGi&N2=p@(qk!CW1TO zJM@r>k5=CJ$6{#f{&aMIhW0*%ntG&$_WsZm_e@ivz2DO1wC1Csy?2Vcl)SN9jjY9feMBNB$4oyTDI(`;O(E_ziDEv_d>Dct*Am)(7PvhM-!rRT?& z#zWET-pSF1^qcWe;-Fn-e*C|U2PXX>n;|QP@S3>$*XSP4af|JN6Us&Er~NNJ3q(DHP|!}Yr?74oo3MMbqfO|{%-3Ar}_2x zA6u8E9eEIDn_oyI9XV|Lr6IX(Paa|qtjWt@7yJMMwn48EoQE^a+#~NXRuURZ`>}YT zJ4&vTQ4-plK&1lD0GFY?k3gZV`DT=9zR;uI^6bf>n73^g zS5GNg(L6dPwP&nO?yS!)3g=Te#Ny}?su|HZ%gCG0}3v~0*Z3A1Ep23VQC_377 zJnu4hAAtq1>p|V5Ym}Vv%G+SBD;Fn!s;vH2e!uioU%#RK`db66v_9C2<*C%v3&B## zCq+jo{~+b-H$C-&)J5q^B^ka_eL~PxDw#lmlWzI?rKVEP0vYJrRcTs^QYl)R0N5-UlI(rG2ljYO&bqft?*0sbCd)5oG>c3-73 z(yi1kZvzXgSwY=|q%pxo={Y*UK}jY+m{w|Vmqsczn2*_g7+oj;fMH8%-JEu>>+_m{p|Ru1j5yY>Z4&MX)r=;~h%5 z9*ZFJ#CvLg43B(o3%cVUU4Z;Btv#DH230kiRmXNmHY>=it0IKJwE%r@y$TJh0=wn| zDDe7Lz@Tk8Kf_+nwv*RD*Y+o;7#K{j`dope*mlxeQ1SVbYU<<4c9OUb*iP~n0RLv# z^G&;i#dGk-cRn{q{tj~YMOl2F-0P>XxBxbNH|XMd2*uYjo!m`u;roi#Jw@GCt?*Uq z?$<>ym9Om;{I&f_1+eT-u=b6W;3WBz{cn@Hnesko$)hlKwg79XHivOf*g(43V} z^-rbnRho8ALB&bBW-+9Jz9=Vc=kjLfsz4H{9olKGU!_b2nPK(Gypx)9K=c`QpJ+B9 z(mum~uPG0=}A@5Xu=Pz2NLVJ#Y z)9*IewERItn_TpBFr4);bSQaZD{DunHTC$%Oivw z8@i2tbA+4_x`mcUSuX(W+)1HqTF$dx(qwTcgO*22i>8H+(DHa8XM}c8I>CBQw|91E zH!V-HOp51+zM$nIYmSy)6ymeZnQZ-5TV4=)n5L#$?`d*jh#M?tmSs9?N$5eET4;T$ z>#hksOmdNs>q3u{yjaM~L(h<0Eaa7;cW7#fH5g#$R)(ITqh%8F#?UD$udq&PzqKlD z8KZpI*#ZbUN0^2{lq!##j9^T${u3r4{=l_VKWci|!SKBabh4i#L5~_XM~@nEIVLps zUoLkHxE8GU=LmC-p>>YUpI947wjmfd$Y>8BD`mB<_UmluVgspsV3IipRdPGFIaGTGMN2vv*e7Sop?J2de zSd&LB?J9K=UHNj4+JQ|dq!#6C@)tY{+A_891z}htn)W&v)tF%Ks8#OP%sV z)bjiBCph#{2vc5Qg00|?W)K0k#>zL#8pac}tkIkn2+mdmtz!_|$1OcIeBVcfLCeTF zW^ud@IuG_yCLg`m2X+Tr=h4IoT>)HG4O_gXB%>eJQub#S*}}|v*s$JR4RQ&|<*;VG z$N9V!cUGmc-d_*dJ(`Fp>w_?;XGk?xD64}L>}}jbqKP>6S{5Q$jzETL*EE{V7_;du zn?@l&ALV2}m+fRf9~*-$zKgPcp{q225km<7hU$AzG||4u`r{!QR)c_Eq{)jx4cB@5 zCG+NMKd^H|3?aP41c2JD<9nI$?T0*vdHxiI0NeNbk@tWcc`H)}|3AcE>q+e&`Bvw` z`~y%e#BetLpP+wk0JQ%n=$|v#_%h{M z4%5=@pfb0yQ#AQ3NMrcBuHoU!DgB<1+u^4_Gj@;mGYQ3Oaes<>Z^6$f-M`+fqB@i?KZ$>Ul`#Y>CG;?yJ+_`SlaF`+8u=I!{T+Yw2QsA4y19j z$GF+QQ@gpAZnomiiYeA(kTCPs30$Hk796l`NhF3*(g0j{XhG);XqgK@Ue`uz6NDvBvpmfHjWAxnN~} zLBr$Nsw+VbtK`TW&sYypdV<**&k6n}$l+Y)tO=%(zu7q=(O9djiCin~_BC0xk$Pnn zFd>7`0EEJ&Ww7-Y>#VRCR}SLfUUU`&f9Z;4Ib+!jmWgFKV|f(ha6LR$QqfLq9h1#K zuc$zEnC8MXb~QN3?R<<{*4XFaCix~I#)8*(7t;?(f7Ix^n{k0S0!hC`Y#-j2&qf^^ zA(Hr4zrOgZU!s#PC{TroSYu&LeMN1eGEx}Z7VF6>l1~=1yc&9xb=I~RjRzAtYTxN0Lv2Aka$_VU?bvC@of!}7>Won7O$*~RH2L} z#B1szC?U(0HI0#aDjSWOs9_@jwe{ z%Ln}7afz_7NWEuSH#;3CPT3a>vL|NvwmPr+QfK%QGkpD>0w>oVo#ET~sXZyfciE>- zzAt$3WxlJPf9k6V=LNs*`^a+M#fk6GE~jd#bHW$4S6fc5FL3dC-xj0eoM8P*C+_6g zQwQ4P((Q2>_V^5^$+t-xAC=)0`sO;=5E*gj^zGu%s5U=cXs(jn*b1h$~6Q42j?hy$Xj^8}) z7rr3{m-#B30nQ<3=Fv#P&danXWY~)b{oNO{FSP81nRa2;E%8|kw>eGDs>CGU)+0{F z+(+#YMvTem^qkt7SbTa8vNt_vOnwZfwE~4P)LUAalV6#GK5VRs#8Om!RBemIx|AYY zVIyYhPtVDRf?K^ZQtO({kL7pQsM})L;xa#0z*VWSt6p^kF)RAyoc$ul(oYN`u*I|^EBaJ+$_xL=QP`M`zBq~l(f%( zy{}8o$Ft8PU)1Ekh|dtWJ|CZaap~6YE$2h={r^VJhuKQ6e4p>4Ch%PQd`SJlEAQo> z51Vgz;#+mSZ=b&@NoAl8FRt_>fo^;`Wa63){+ph9i<^>4_W4WDax9=)!>qH{qwLn5 z-$W@^HQcs}>$ha&pzIKtM_VQENbbHEhppOmJZF>t*vS3F&vZEvBpTgzw7&a#2SwO& zh@zY3(e3if_U7WY)Qa&4iKZ-d2^jjCi@z1PA$tSY2T)pOvQWS`jLa zhO2P1^~9JdJ49~cysfA1JzCzb@oe&aM(!uJ;M71mAX9kvZsh=liysQM6Yj~GRFd~oHsO2>q;42+qwL*(|=8!L4WYk9lIv&mbG z+)r%9jrm2mU9%HG;&HETh_oZm!|bLrL>O&!FI27C_qw=S;mN)Kq(CENlR z;>L`>4DdHobQQTA_ScPz`-$nM>=3yj_BNWjLo}~lV>ZfY6rr~&SJOFK6(b!u&y*b^ zcgFLStIxATxq7^S8m^v#7O@>P_ zE>{warLMKnjg9L7V`N3fPW*~4w`=U(Cc2e2t--|EjvLJzj4-ows9hb!t@}vaoFK$p zQ+9~l(t8s{-2%;P*VuqET1{xw?1V$yZrFsIgiWM1PmXAen|{tF;wD{A1c}C4yPqgQ zbdAejpkuJI;W`(u#(#{_RF{ay!?Jhb&P3C@HX%JQhx!7p;3WuXr zRpGcQ4KJOuXvv!8sxnfZsIHA{LHOZ{jb%0UI8}rzaGFrza3XwFqO20yv6^clfN*SM zv@u?us8TT;OzI*~;TBMZ7cCDrMxfacZ-nJVOXsXutyA>MMhbFCH$_ z360iPGW{`hwTp!tqjizO`kLyE@n~(d5WP`TRzI;}b9EsNnm^I!(nEfJs*zgzu{_~{>rj=nbM;or$_CInpiB%gTHRDPFJjKOT_fOE98g@*W)a_ zS(k7|z}7xeR;O@0LA3N~`j6v4GCx_F9!ApnPGru!dCNMtk&vo)e|v)l1i` zpuCPF}Q-C%aAo)#Pza@2JX$Y>CURB8C4MN3L_9R|nv zkuSr;xZNxh=IXL~GyzS4u&%6ebEHv)8=^gjG$+0YV=57&3N2LB$EOym?Awy%#`BzLcNBv$|3{kcv4dg6sz)R<+iYXLE=3mLdq8*h@v|r6;9M6 zua%P-GehpK3O)KQFRR#`XfT7*%x^PnR_ld})83mB{Z!BcX|<}4T&>qO(_pNVdQs6i z(J9l7ZYYbzs3`-%%qrbzwP4=7={aNP>sfE+@5FP*$wXEKv2AteFkrmV;6}I97^y9Y zGqnYJ1{RdVLxCQ%;j;4bMl`a3Duz>2UlsMzm~j!%QC6kxqJpBHWU*Jfs*x*udfl%#8HU5KYh){ zU+-hh-AM9-QP0y(VZ5jnI05ie8P?}Rkz4V_=YnCgU3(751;KNRYI}i7AWfy|s4e8;jN?nOv7~8=dxb0YlvRem5H4O^$&*GQA zuXycczyaGudqmgX6)4l*WZb-VWMMS6kR={XBep+1&9?D`R-@{ZnlH% zVq3lT4i{k;?HYm1Qv}t0dHH_z34i46x_W+rBxM!mq-v?68aqV7|bNsp&=|AA+n;Eu)`ut6wZ(qnK%@2*-i~0`o#&-;S zS4ufQ3wAHc$MvEo^`fWtqUVBk->uT#nqKlNdeQa0=xck?e2?c|jOTXHIhZ`xqfGnX z=_Qvv4R%m+6xF+oFYQ9O#pPa5KWfb(jyo!_rWTt$3m(7q6?ogPHS~VAssXRh<5fx@ zQdrq*RknMvvZ@Gn->8bCmX?Fi$Di<49t2$L5*$xu3A0P}8Z+m(dhv%JrMQvsD#%gT z%i?ZWd#}>lcdv-Y#Bey$*od7d_8~Y@MR~+)tk{S)Z0>5wSpqTVF=Mtd68X|rT6>XS zz{2q;&n?_O>T^mQXC?mLpsMt~tw;PiL~XXBtd?6N#r=nk>CSzFg_q+qNMpLMC5;Dd znDijLjT3si(9NWwub*#tSlmS#E}%%?42OO-oJ(R zW3JOqkO({3MA*p#vfc#Z2&HZl{)41P;zJCfUlsZd(y;R`5q8dqoR0w7;rDR%D5aJI zY5z*nuoENZpnXKdcbbU!`eBVA&EL7HKb&+v;vx+{Q;6`xAH6AGB)DF%3`oBZ3H_Mh zD}pB|hyRa+K216wH})vBpF)KF;Y8RU4WzwEL@fHH#Ibm1CAb4fy}hJi=V>DP=^Y}T z-BvPiJoJIqM5XQ{jc4^sL_9S9NIv}X(-Zpr7ZLV+xal_wNctQi>dzH=8IbL$B#ru4 z6H&iatXw>ai-vW!Nr2>1+Ns02sQ|A z7u+YjzV_Z)PJ}>xNK|a4I|3L8Xf_MaIe!3u^U)0MLEEJq6$UQXW`hyRk z{vivP5Pp+jyWr!3KM{OU@HN5r1^E>a?Q%UJW(ejAP8OUaxI!>2STDF!aKGT!1s@Q6 zOpxDW&=0=@Byt@g{#{V7BcRhc?}4KPiv+o+Ab+{w6@qnw{PlE!kzdUbe<%2!;Aet; zF!m`A3Jws&=j)o!^^0=7egVe|JxOq?;7mb&?nwPLg5`qTJCVOjaK9jb)*=7ff=>$m zT=4gT9|-kSkv5nLh2-)<=1D7Z!NdcoTS?-hJZ@Hi1;<9WdsiC7$dEAqF5 zepl#^gx0?k!QU4`r*Iuay-dN;g4IOm>Gc$TwvYy1BXa#S3*>D=e_ik{BKXe=&Gnb{ zel7UE$UhbOwBTn%#KHBL_4^V*4;9Q2ev#k|BJ9o2dWX=r3Vnyrj|%;S n(60&ohR|n({#@uZ#sU9&AB%X3g`OtyVcIGSe_Z4ligEuJxO?1n literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/browser.o b/obj-i486-linux-gnu-patched/browser.o new file mode 100644 index 0000000000000000000000000000000000000000..81bf17b9a2a70a3cba3ad69e5caaf60f9efc319a GIT binary patch literal 68332 zcmeFad3;nw+CO@hPI8)VNJBzML4;-x5JiVNz5MHXkq!R5tuW>8Vdz&MDAxN^VWI(3o;dFP#b-+TYKpUx4Azk~X_#tSpkX3$)%&S6P;XJ`M-0aDg`* z@Qx_(o{HjNy}|hE-Ozz0yQ(%j?Jn8wI$wL!vBc1l)1h6V;CG>edox|6yEoG!8+&sG zx%>oOg9sk^?#!7pEvKsXW_vX)WHy+gnO1no=`aQ!Te53&Yr_x?^DSHu+EdhY%p1;h zwX`*4rk_b~tJ)me)wEaN@ljOhZ8N&5Ek5KLB#GHzq63sds=7u zoaWG2yQOKj_u@-Sm+Wd?!}*Ff9cut{t#{w`!h=+dzwDcTh6Q-6Z*R8 z13k2_>BFy@4(U4%neLr86!nYU_FCxk*ljz8?F=tD89ERSo(`|?)N5!*)8{%y9o^Tu zjeLZQ;-8f!`4&P$%|8!cKr}?RqU_SPBMgU+t!vkyGjF87e)K+@LhB#cBJBlhB~h5b zu~5n3Q2vpY_p0^=PJnkS_L=O&s!-rWIR9{XzH9P)E4KMVj0(F$`&!;>@KiNjJ=_)B z{0vb`EMP7UueWx57!{u73;hssbq@y)hZm-W7rDZ-X4CjN!W*8I5?+5eR4gn&F0&u3 zaT$h74#T~kOGG`C?F-Lx?Kl(_zQ*u<@yl?@;jj@dbj3asJP~>WWH7!e)LV2po~LO@}s=Tm>C6a6%_Sr`6!F=g7|Qp|Xp; zq)JZ;cZ@(pJ$Dwgt2J-~gD-5V(Blkp`ldF$VS706Qx!Fh5VxBQ!G;(aJi&XyW=k9M zO2ZlsYHhgzyiyMu#Bx})v4Hjju9qo`jgmemK7oeTR*nmurW8lq9gMfkf|hK#p@u79 zm-MzxyQwidy8vxoz73l=`4IL99YmH&f%3xz zuJBB6sPzb)V1aMq&W+KnGtPu&dRy9JZ&-#76KBre5VLpYY)q?Rn!PiNSwm~f*C<&$@5hi$yQwVO3Nqh8WFXG+U5f9_)~B;Aw9C#V&Me;Z%yRUnduL(^)3o%q z_Atalyvy`SXMTXBB1p4a`)D|dwC8sELwj6@--NeH^?-dUOR0&AkYs{pdk6Hxvn*7b zUq!WPm!AH5=@j(h7xko95rBsB&nKDOnD)0>_bKDm`E7yb2tMFE@G`<&8hPGOqSlXdA za2rh)YB+lxMIZd9>U8T6Dob9yT^+MQ?x2-mSGfih#8vtim!B{YI$4?8n@WM+(Q8Nd$8YlE>z2ix|M z8Mz@5`4>bL`3??)A8_8UWiEFO3QMzwTd21qC!w+Szo4ev>1@3zwa)wc%o*EU>21w6J#lw4Bo&|&!IExSNzT=32?Nq3x_{%eAVz<&3{SSm%E(4U_ zwl^p00DCsIxtdNVu09@qn!Q?1#WsJ`1>=KO<1`pN8g#>V%N8Vp-=L*&Dif;~Ou3(< z={{lXP$&lR%5bbof8G;yhP}hBoU~NCmi9$IXRp>;@b#u|9sq-D|8Zu}Rtg6DKZ{AV5t4vy%T|oN;|uU0aeHhZ zpkXG_kb&c^B?pdtbqaZwLG&mFV}|h4RE^CK#ygzA;f`DaHqfI}ne8hXS1(Fko{4RF ztyhOGe}-x}=tb(Y!ZWDSWaEY}iXY?6ubNFegIqnGq$HSS$42DZ!HFRj4 z1Xp_#8JVK|=>!-H9Pbz}y%(8(pyOjGsb6PliS)BgyBP>F5I48J_$&hEtU=J6liZ{? z>}h!hfe5Eqj#2FCES?`K@+c&Ev~e5GKJZsrcBDU;ywm;9N`JxlM#%$&yA0h`9>Ko0 zJBIw)7u(#OX`tkI)1iMoK-AtDa;0zo9(-4Az8@GFU%NQ=EMe#|jvz{gNbX}GCoPK4 z|HwT%ajXp9v$&6KDTLiY$M4XI-F7!s+Wa1Fi(;E=pffvKz6o1LV>dVL)MK~xZbq8u zf)I<{w(C?*mhKN8Y5cZ-Lr?f^`xi9u8nm>@mWD2JgwfmgSwA=TxTtJ`*$pgnad%eyoQ!oT*0<|+e@r4XQFJ`Sh2;Iy5i#@*N zc>8t8o!}4jrF+p!OAdrHZND};HX$%r`^D(Weq{UTL3^EnUFkl*_Qy7-#~`mB`uhWp zJHgA(G6+c|f`ok^l>cVS{@CUyz~@e>c&C&${~Y*tq!8{Wrrr;#a)o8;>2TdR@DyqM zmQ$f!vCV72QDm=QoWqe?0HrRFCvd+Nd);J=2_66H?W)0=Ugf4NGCnUse1Z?hSqs39 zEeE5T$}$57PG$DfV_TMjz>inCymP1K3P-`BDH!)TZ{h|Ae$xC3=0rm{{{XT}=v9zz zP14UgQ0Qx~{LKfLN6_bU^f{Fi-4A!*b3o0`h)gsO!K3U2pyjZw3h6@_V@How1}EDfFHPtyyJpiaSL^08Km72+R|op<-1K21J`L?( z?Q8@SvCWIAwZL)hbh&)jrW((Pmo)LH}2I&l>a{0Yn6uyFqI)*?N;Nh5Go=8CD7CMDDh=$igIGyaXonDGzbgyntxM>`01 zX#baVIeP`(I|GWrEOIT~JA<1h`lU1-s!A0{wtjBAX~&)*BKGgX61TZkCNm6^o*+ zs3iwp0Zu|Km!Q&-GomTxj}GqEfo%I;J3pu}{_}Y|`q}XwbgbI!NaZ*L^6Q!Qdd#K# zlbqAxBl|hrWBZE`0;F*l-2BZ+X)xTUbwpU_JzQ+dPDD44%9Pex7oBN&Z$nDsHPL5M zW1DZmCM^V z3XFm74)^+TveYU!eH{wN?ziO`tkh~pO#4J`hnqi#Je$+oxH0@2VvifcmLtT`-`bzS zUXkmdom1re%uY#AxE-(W9{C^Qbs~t;SLKemeKU2Ay#6DrmV>YM&k+oA-llzixnQ=x zV()`nx7MMFI|3djZJiA&9Rl9{6g*d+-a&&@g%hIpfn;QeVqNnh(6QE2t&M2K@i!w* ziX~NT<0Om|#@Oah5H&yM_0Q;b7GbVhtu5rEgDb3IGoVFf=QD#^Zi33_haK!4I)_So zGi7~B9;ct9@0OF;(lhzJ@F{NBWS(4#8f>QWBouRW9QE3H*akD*@S+;l!p?yM>8~Fd zVb}iq^m^kzq`B;j3ZsSP&4J3ZxaVPZwezexGZ;DDF8^+m~=G{nPe!dlH;u zmK;cLJF>``W&k!P?fWs8jDLHfJZFu!*LJl|+BX30i7a1$7+`1WBdny83LAuu7zY{WXe%A>_ah+*j z2iEt<^M0JJbES{nmSgt4;aVD}-4A`y-gkG{8+PD>rN5|j()<9U2xR8c!R_-(a2=sF zI{-UY=l0y=%D#@A=kCqUV>c>-BppSx7eIu0+Av8HT_ik061iLzIr@$ z$zkq>g8QhQOO+nw$_#1jO=;v^$A7;_J9>(YNv?5f@7I0}bP+B|3>nlC{jMWVEqSx$ zy->>{Fc{ms6AgGCc`Ci_XuNGFJe8cd{>{+o*z10UHf+8_JNf*|)g=`8X*j2gD-^g3 zg%t|ihXPN?eu2Ul3j8{JNtgK0l1Bg~h60bHNcs)Nqu)~vk054|C_&kg5qX(Qm~B1h z#_inwh;$KqXb10G$#%%~`=&j5=rs6@z5XJePDp9O!T3;g`?J_AsvAGdZ-<#Yvvg>{ zDX0!R{&2H6j>nS^62)|z{~?0JJ}UY-)^$589Qi(LLNU8$BYomb{DkF@HZgwX{zW&b-kn zT)PFynMH)*COExAyL~qz$N^ABKCQFO)Tv(;d0gN> zgB!~Gg?0U56Ie*+_Fc>(LnOGP!^2=y#5AP>mDe``>qhyB0Mn=)X<8 zufjPx5^wv**y!7N=5nN3$1D*V*a#-L1%gIXwf0{k66_}ksnV5j>m4QEJZhg#_c;I7 zp#2bUVoSVqV?5OiXT`&O9h(bmQGyOm)aJn^c8eGRixey}JPo3Zaq#yT9p}awI=j_}Pqsb9Wy>IZGd|%=B zk?$+u!P%x`HBd!3kP^Es7~gcr3bh=7@3hW*amwh}>*&|vlBCwV`J|fu`YZIM`Wi_d zH;{N{FI9lolU~{Z&b-{us69M0rqWROMG|enLz8|8kW+yat6>5K02R~A{cYWiSX z(~h-(MO)LM?M-c~PwjDqTH7!x)UumOYuShIdQgaMj#I;Z_HZm){-#g2HSLwdPc?nA zy=f1ITYFpn)G@@bhBQv$gzpWe+ctf)t!bAWvwzcvd^4@-gYC~&V1}k0t2ce4W#V~o zJYH7$M!QcQi{oCt>Cld*wwmx(3Ilbfg||uuiwC8Iw~|TVlEYicDE2^pxONgScnC~B zV9@y1CGD^Y4MJ=1@x67e(kq^Q&=G7Wz+%?^3>q9eB;)0*%#M8l^?HO0lJqb_OXc!} zUR6!&lAs`lt-N2g9V5TfG4km1elmbZmf*n(=X=2t-caZW-*X%T_ah~8ereCyoGCxT zkbXP$osFvLhajUb{IwI}wU%;ro6v1-JhhHQX<6FUJH&pW4if zVljj4Z~EZrrXA}-t&GI>*U1~#FSg@Blr-woO>OH!GAXs!N4964)y}wWf7xmO&;363 z8K@BQ*v@cnfVJmfCkVbFs+UU%7KZajVtZF~tb$%6;_cu1EyG`m_j*&?-1cUAzP&$^ z^R!nW+AuHPd+7ITz2QjHq39{m_8T=aw|&{vHi8)nY|(Y@pb24(A7!QsNG6i*VVmw* zeBP@@H!5466<=^R1W)@%&@A`~2O{Jg`R?=_%z*9Uit^O)WGbnCA7(0$RGW+Z54w@IGKp4>Q1GY4rN z&os1a8Zx@9;(#m4u4-CzEO43@!-CzdINj{#@o=;b(B0K06_p#8foCgS9Lk#JQ7st7 z7O$@7#&JZ~{#tHaDoA!4f(rItJ@uhpyU70W8FDC){DRX-%E zL-m?AbQGo_O}5j{nbDj%8GRHv1BM?qwgc3(;hlg1WsXo3Fhl3~l+HOgeq`q?oqa~B zJ}@-D0`O2re*9b{A!^?wBg4vrW?iHUlIzQ_V?jV$NBLBL&V@qm-_5J3&pmuoIZ>rPs{i z{Xt%TeC2meW;baMjzb!diNmFzPQnkK_9tuF(gcaowvMz*qYqveFb}2yGF>r$8;(M^ zUct*HrV-Nz@A3ip5XPE%^e93`)S3}UBCe?FRSod7s3edyt(dyOm}+GTS~AK&$yfn8 zu8GT8-Pjk^>#kz8Ka!5?dQN5BFbLHfWOdpwR6_w`>xQ6uqwKo}p5qG34t01D&UKTl zdU12%YW*wvny#oYwq8aZ6yW+vEih587-I)s>2hsld$h~A2n@S^LBJSH!oOv&7*`)y z2IAa+QwpOD88Iq-Brw(q@OfL*$bUj(?*GD9v`@c?LkDW^n=v}Nr`{9YjDarq8|WFG zpg_z06L1jSOMzZ@lK_~gK%YAu`6gN@Fy37akBsiEz(n^1lIo+tB==5|N>ZTT?ezid ztH43-jbx*r0+ZcokTu$`z!djsKfnR{2x!O{nC4yp6Gjix(S;{N$ifGPUxQr=AWR#-DSO`j&g9QVtxcyzj+C&8KS%b|wo(fR~Qd6xSbl+ok$ zSrVM>{xwCIt{;}2^V~o21DvgYFTrAWGE5nrtH4F>t!%weftR@NA~;8Zm$@G#n1?r6 zC{cyGfr_20cwX-A2Xu6So-gOE(YlO8Bt<`EZG%&Iqo1c5Jas*Q+HPw^^SG(67i@*N zJbHgXZMKCic*RMWJjO*&@X|pjPS<~73S#LK61&8~4h6OxKsWY{aY-^RFd8$P$N0vT zaNd}Uqz-mstd)NPSgRbNZ&_D8OV*On*}9r&IGE>An8Uh8dg?$I=)Ht4u~O1EQ1f+s zq3InUx?8yjwaeTodtD%vIRG9zvPF@i!riI1=`2qYT*f{2SF+9PxdGaDPmmlA^m$sM z0A=izZSkIkc$LRJb+d#LJ$>0W?M?|Ld3th&8TJf*4{hkqv1ds3@oe9}H+-7pTY>nBh4X4QSEL=x+?n^vr=%xfk2eY|jqPcaaShcs6l{l}|`2 zi=ekbnwHdM%y{(i+zyj=8EZ$P=6M;@bs4AP(sK#}x{S9)usnH)?=BN;5xkzu;XGY3 z?4CZ)4g^-0i8d7P*^LC$Ws(ggYSwN@>+_^s&FMD6%RD3PCe2fYgyI=xLoUyJ4D+Pg z6IdP%#`UCekTK8;JF%Bl1RmnO1CEeXUkL6U;*iRT1vJzl#VNhX${9V<-G*@xNcFg- zKiY<;K{l7(&lu?If#1Gr-VrvUFA$h)6Z^)q<49Jm7{s%;Yp*nDJnr(!E48kP^jvz{ z7nrH5_+F~kC1>i|o863o41%vQINs{o_hMi?uL9`W&t^*V9D^ub{cJ!AL{~ZJQ~aW+ z>wxh@-UyfPmJ$Hro=GsRzgwkVgXjJ3>!HDJ)w0f1+8aviR->~YQ)yrLakp9pTJ919 z;A*`_&f;}PR-o0laz($oG5)%#~m3O;N?@&}yLJQWdZd+`O zae*-~DZvBIx@}c`l8EVnbk*%=3e$&}G(RwRD@<=oM3@ZBxWg5BfqF--;cemFV)V zoef&zw{TQl#J~>>Q4WMl{0>W$C2oc~ePSxM2Yzu3x@^h4DbWQC&M&t zpy&(AgT%Mc=3wE5eTRsX_#P^P*vce}d7w5-v?OCoEyl-SCoLXAGDs08!Qn{pJMc3~ z+}0aAV-dnSlqUSZqznEUZ?q@@W{ju<<+0)w=zW|R3Hip0B{0qe(H|5t#2P4fqWA># zCy5$JI$694Zl{Q7@Htgn2Dh3<<$wPo!_!PoeA|5Qd#e7WMMNES2J>omi z^@=+|p{s}nrkmIX^06WcjQYfIe0LXP;RHRz1yE3&XaP6zq5_=t6#X$vg4hW4^%8qQ zGf`Xz#R&lxV5CPOSRZi=A)O??fcIV?7NDW8IEESfi3h-mUmStr`in-?2Z*atA1F40 z@*uGWvkVrzI~*b!L1(DA5Z}q-MW}U{xE-!AT>K8E9U(NBAw}$zM%w77k?QfCD#jww zq=^jF)5R7@G+JB+!;BGMV(eJ46&#Kee?#kd@i$POAa=k!8DbXtOca;GxhIKlF>127 zADmASPs4$xifgbmO%vmE+(d|FPDFmRV9He%#%O>~D4FTK;wJ1s3;e;!cFXJ`FdjnzmmPYry3zns@}p{G%pr1aE)R#BlidpEYq6`n;-%-B9vh zH1TGXrXA449WcUcnz#jBUf0B5Fzp+f$bj|U)Wpr0{l7HvF#O;koCo9H(u59P-qyqt zAm7o%5Ln|~@QLC*O?(38-`B)KsPM0v_$RdSH*k%d`gcuKgV-TW%!gV&&_pfd{}5eZ zHI-WH_dY zt}x<1ArXZBOcM`4k^j=fba=&aO*{t2{~Xf-I-!YyDR@Cc6Gf2rq$Y5Pp?#@|Wti`j zCU~3w6$Arkr#100+~#XdOoEqxqlp*6*|(aw0M`6Y6QiKk?=>+9y8b~EMEcot|9V~Q0Ca;c7DJSfE`nhG zMqNCP*~7Xx1SQ|3i<=QHt-1(7bwAO?+aPwcF5H-5vo0=zLbmAQO2~JMF2+K>TXpdn z#@(iiRJht!UAzYWx?LAMuen1PpQHGxE@|4bL4to>XUFGHVqVs`YrOBe4$u)B3p zhZ*kC1y_xGb+H-w}2PYVeEqm}bctwosGLrZbO7itGSdVdi237UEAB_dR zDaI)fcNanm-&Es4IaG5e!;5{>6zJ;HP^`?8oM?^$Gu-150=_&csxfeidndftmv4Lr$+0bV4})9y<|;79 zoyvLVDR6c|1$@9a-$;Xor+Jqu(CfaN{#33&U&8xHEWV0P3F8y?!f~+; zvSo&Z@d?r+suTwMy7;6D?4x|k6bAdc_@wgH*c2%QwsrAZuW_VYZCp(52O%vK`)Z7A zaO(aD7~jecRZOSXtm;q&wdSjpJ)sJBDq_o5r&_)4!!+g<3iP?xk<@A>OuYLiRM=YM zN{}!HCc3|7K&?}t-+h9DU8%+|6IFVz!gMDlhx|XNFg{{VA@TWsr!cX^)Xnqu z2oI#x61FgsUQ{$7rIzqKM)_V+7)Ytvn)rjlKuRs)9U7rcVIZZJaDpb?p)inAv$eHT zVIZZJaHc={>{1v=sU`f?1I%uPfs|TOZB2#dds$&1rIx_=PJDY522yGXg_L5i!gL|# zPgvZ1`xJ%=EukxIwO?T@Vs6E{e+SE@FzP z^;Z?fBqo!&_%8}$5c5lBiT|=OQHW<(LL(F9K^qed&ASrrVF10QMnUtggsX^oS7D%e zSHgZq)q4s9&ASr*iB#bGo5DczF553YP#9?5m5@Mx|4?C|d6#=P<@(4#d?TbR_pj;x zAFGh^y64m4pBfj*R-bz-#c5X&7Vi#F1OHH9qMam;s;rRY#@ip7@0c1p$Q?!3{-*+y z-7j(8&lH&AUdAQuUkXffFJojJSK!z_m8;fhzR!&~8TT1>3OQj22~Ke*Q#oI#1e580 zf(ycz3e0gYpeauoy|8sL2F`YWOUhp>0rT8vq5yuUmZbvsX3DFXw!FpmKEh=((HjF7 zx%*L~7}MTXT!JtvfwT8~9ePhxS;@of);-DQO!Mr8y1QRsQ*(L9Sogm6Xv^~~vUqoO zDB+D;6I`Zj~ni^WmKa}1QwlQJeLArtbb z4zJlUT1)6b|L&?VSa`Gq4~@}HVX*LM39oQetim8$Y6%0WN1wvLQ?-OY)5E$e3=R~u zgts}WhmA3Ce4r)VK|{u=KFFvzH{se5Z`uZMxqn6?Jr!uF?Ue$(?ly){F9rJC)1d-i zqB%?&FW&taQoBzmFcCWF2kCp=%#>r9G)9c;0(9;5TiU$0$=04sqWDt)<6oM!R_ zr0+6p<;?4dtZ%@Il_{xcJ>Q3{iN4Wh1=Q51wodbnF^i-xX-PaV@r_k_k~uKCH)a~A zFfs>zKyk+_40B+@MCRlP3d0=OXJz#&&6lA(*41Za8JL==K&9PDa((EJKEwWDm2QjgZB3WFER7V7Tr45N!od+D{@ zPcu(ktU#}OG(G7O)80M!+zD)5qQFEqPnCR^D#CvEGcG?tsO5*+K!qZ?ExFvI;lck7i3oYH5_XjrPsTn;63 zZ}Bah#kWjpF2}u#xox=uXS*AiuBsK7=axHw6$&iqv#N5f=DS>h#qO8rNi_;wuwx$opeYn4wmxU(5) zSDHPg_-hg}xn;guISUS4*V)VLH41}7urA^6=<8drFh~UJ68^v(vq52y2-YQZqhoGV z7$kyq2~Q0Nrcq-ew4%_fDx)@ohCFk0$bg+Xdqm#~E9Xi^xYhIMv+y-rDYje98l z{d#jUcrphz>TpT^@tzph3WQILi%B5Hl`6l>kiWbW;308`9@qFv%ud`F49(HbpyY#JjTfeTvVU%=0$5tYod;x16=DpKV{ zr-$-@?JWk9$c3i5i=Se`9^x26J5JmO6UK{InWDwjs3(YS%(voa&~KucPt%Am;W53% zTM(g-s6uO!_#1j&AbtYD`-+dCA{?+G=KW#<=ISqg5BdYdYv6OBxTHT1*mmN3u$Tqj zhKPqC*HEz+G?T?nC}Eg511W}!J7Dh-A|L8X5icTyMv4ny?@ED_rhIpz&0HG;ef3aIS>bIJuwOgY;h16 z2W&j(zyaHzU=AFx@f8&uu-yt~alrOH3LLQg8s@)*hYdu9I$;1nmAzN6Ac`&^?_tKVEYEdaKN?@ z!*Rft3C?i9b_Mi+1Gc{ai37F+u>2uSybZPBfUO7ghy%9qP!A5+Mnj)CVEZFfi37GI z*a`=1tA(;~z!n9|z;*}_4%jBcEpWj0EvVpttqE;7VAG+3MqM*gk@oIAC)Di32tb3c&%}Z=gCHuzie>#sOOaSi%9@e8dP2 z*gi%Z4%i+56F6Xd4(h=H+ZE6Y4%l3f9S3ZAXu|>9CvY_$u)&vbz;+#Y!2w$)%#Q=M zeQ+Bbuss9jalp0!qTqn74xWeuwo5Ss4%imK3vj@8F_^~z+aoZ}eY$uITDo5sg`o0) zF1Dk~gE-!UV877CwUFqSy7=8-P5YHDZiR^-(nT5!_iLOgB7yuy7q7r=eyfYOFzv&- z80gltM|6<|_kL6te1-lo3_$TaT`Wb^J+6zc@areQ3-t1PUAze&d{P&ap^&FAJM8zg zE+#;fZMtZOiJ#F0UlDy)7rSAH=X5a(qCAfR5wKksYr*vkx_ALhyomEoPF!CY^dE>aFOHfbNd>$`IC8XMI@t#8vAtB9%5VZ64y|+OiKtXmQbeWyWVKKuvS7jaShn}Cgj`m&Gvi=l_kuzp*+uNQkiE%1s-m! z5(;dnSnH?9fr5|I`!F?bEC{j{t2<-+LJH7e=YqyiNP6AH*^p18i z>tIV!H@3s<3G+FPH4-tD*6U4fuspooOq9pZ*nfMtw@vJAZ*A?z(20H64cl!GZ)Osc zY{=)~ra18edy5<&$1P)G-y&(`M9*_kXzOP~y*=D}CaRmkB+s8gEwR6?62B)KSv7Hh z4Gr?N!tD|V+T)Tv+zuuVvZ3Lg9WZO+U>iz-rug*9cm&cU4rSGvir#+FD;~+h!@pi7 z5?7hz+m=bl;Ktrw@-2GXe0$^S8<6}t2G8r|PDWf{dq=z{4}L4u{cWNYQ23`w0h2r{ zFryg2cT9|deS7pa01Zk*n@h)eOHz-S$RJ{{jlgkBQjY})RWZay;It*F2OUEs+Xx)C z@HzFnVApyT_D>Wk_fd*>;MQU!tCV6ebSg%11f^IHpAe}wWO;sup(5SZjo0&cSVoMt z#qjkwNN9{b6L!tDOU_@79?}VFx@%$aJ+`AVEQz46>GC{?k-e20 zTb?Umk>0&+6?i?9p@QChY}@&y!}m^7R@RK?VTs;-M}TPm9KFv73wz&2e@)hCTp0W>^2V=y#*f&_OOo@G!+pV2nB%dofA ziJ&C6)zdY@3)S@*a|d~uttVY@A$j4$qolsJADdRaZ{qu$=n~kc?*> z2h%)jp!dFg4@=1MOvW^QmG}ERcR|;E`%?^KU=Ppl5o~=2kc2TX&X(yI04dWMZD3Ar zp*EoLD_{oQf>fg?y85LrW_;vehDJkdgvU3!!~;kKjg~l#evLkH0BNYvFPh+)jcuC9 z#}ti?x>(_7X^0(gA6@i^poZ87L0#fG^sqGRDa>H$<2QkRTve5(Pf*b#52W-AJI}Z@ z<0^QbK9Ot;*7?eov0ImKb(zlsHRL)VRLu+VItyUP{jO zLT%_#4A(0qRX>Xz@^utY9r2I_s-?P~iOykM zpW%81BvW31rS(g7)_X(GDO{le9{`*I7@49sIE--xkq<|{jjEodZw8)g{{nR2dp)Bh zkxbIyFY;2$HGKxfxsL>f9-$>#Y&8L~6xWlu)^i{enchq@{2i!KT&ZmE1i;})-THM* zn&y_A;9(NH^DZ1$zwV$Jv{nhfTMYv&y$L}9m~^fJJf3T=KG{}X zj4Ky`J@R&HvsQ0Ib1WQ}Z+H9z-E9-Bq6xkLDiw^^@omQ>^wGwop{74!JGBp(Wymp; zP!1aDDCBX;auskk%a2QzZw5R8EdE}%tbNJF2aPUqWZ1DQK< zeSmST=)-_2pzC)9lCCd-kpQIY7k0RQ5o@Uks1kZ$K00V4_8~j!Cw2WkKzu@b8OqdA zj;JT3s5b#;`^E{Wil+&43#^}zZ^8YI@DUH-FZ976`U7Eu!SjV=nD1j{NdNs(w|(^3 z`pM|0jfZ~XJ0#21893m zoqiQybIVQF*j{pl^pby}eL91;4(wfzORv|bp!d3>Xm=|>*{Zr=w%A=YZ-z zwcq{SqD|dM9eyg4p0UMc=g3cG5(%RJSUw0uGkt9jFuXQpX!v?Lg5lLwphuyBiC=?{a8KQ>Q^H* z+`^56vBj5MwGz&8E1{uSUuXRi6&p0RB+eQI(hig~if>x!w*@fA<>)#}2KjA#J9iFF zdWKiQ9=F?ed~L&Usc;8epLQF(MZcYl8(YfKuvgdgJC;jm{_IiEr+x<|SqnO|1;L;4 z7IZ7XTp52qTZg`>by(4Vz5%r-(U7_fPJCxGpw|GUEhKMuQIlry!1~F{K`j-gc#>rQ zg$^paaZb7S?qX*<(v@&53`@Po;4i-Lo3HJAd8q$$r-w^RdjnepedLY6M46hwQv!O= zWV(KonMuT78Msqy1mhqrdJqs(6#`sb_!3+)YD+rRtY7#zIE%VP0sBE9HhmjnSl9dM zJ;vdLf@YbcT{s=a?-kb%7+sHXMWMWKE9mx$w^0}N1Yf-p@|lVB3;Q5Kddc4!0Qd`p z=_P+M0ANgi0JEqOU6&73t^lPx?ZW$z_j+xslH~J~<29TVL{XC%auY;L9L7x*fCZSQ zzr2ygpO$$Sd>UFJc-HlAyLH94{ChJbjz1}v8mwQPTD_{gCRkCKT7PA|ji{+!n!2pK zJhggk#`uvn)vJQ*MlM?wOdUIF%&0L=@3V(4t!_|b6)|m;HfmIA^~$okvpcRT53a7S ztjBhL>FV0G^_8nf!O7w94P_0ZmeW@C4HXrYRj5Oy4OiAx)}spL09{>+D$EV;oT}3S z;~J`0R@&`~76#R=t*}wcR@d2;)m7ygqer8TIhU8!FSl!}E0eTc_*v7Wy0Xf-bL3%%-KYA|SJrc{hhooc?b{_yW!NttH#|9JP+k2RSS z9(llJm@gRCKKv?m&w8tBnKjV-scBuiW%BmrR>50V^S#zY^U4!ey!n$2#sq!yc58s? zu||Em=9ZMHQz!4AHmUio`l;6REt41TpFH(s%CyJkm^J$zHP`O5?z5%^t((n-k%)Q_HqbwjMKv z#lQ7fMVfhegSnDZJ)s*J`hb+Q1=A{)@0>nyI))E;$4r0z?JY)1PqT})Z@V!(ZgSfG z2bTZUd~o9<=EvHUa`T>z4d#d1BliY_smtzNV+`xrI^BBL{JUvAZ}q&cd~GwdS7qL` z-bmNqf7Emv!}JHu?g!0(8qYVG{U5m(2V~}F>z}t?S+K@*SD680xo+NU95(;4!MfHM z6=y7pZ!@pjJi`oMQ)PZ-K5qrTw63#GTK7KssQEd5@2H!5*Pk$wyM6QVb>>Rz#G_`T zVT{zD!25d_=^r#<2|%s3Ev|B2}( zkkA;|b7K0$Tdk&_XPS5+N^iRF%E#`TyzGl6v)kr1l|l1b(-^B8L&%ib!+OMAd+H+t*u%&1omBd*3rAak^`bp>gJ2I*8q|!AR4s z%qH|Tdu+DSSoxx9dinH<`stH{=Jz^Sdwv7#xt&bBxZd)cBWc~1jTnc%)>QKb1LoLb zO|4AbzTf<_eoxcLFK!N+2egCcx`Xfj&1_mvFT4Pv{gZQ<<1ySA5oh+YE;NS4LEcBq zPfTNkZho))fP z&m-oi`iU?0Z=YIuar0yM)i2xLbi1{4x;3%cylJB`SwCs|PQX)NxtbCElFQoMY{r2N zk1`y3^KBc9A-XlK$^2@= zwXb0AWiO$_qvn5U#!%h7!-S&WGLLMy)_lmY?lJG#VBNz(-%;T=!c&^8{qXgJ_rcMRx1PINb_P4lb6g!>tb@utv2D<7xxF#ep?=`F*#J;}%g!zZ{kJOY;oH1g0%H$SfT>NVDq4g(rm{(4j ze~a0wKVl4yv)+AsnK7X!__h3B0yYO&qfSC0PZ+v6{IIp=Ju}tv8xwk&&u_GPoMZ<9 z%beU^X$7sfj*`FwC#_WT_Ko1+$YVxTFSGv%A}*|gK@Oe_E?jK&hfkZHhToZW`^*cj zH76RE>7+B17QT$82jGFGvQD%ZW8%${edbB+1d%z`C=`YdYk79rs-X>jduj5Q`I*N%7CDuBr5|EUUkKl7Dc$Hn`qjUGK*Y zNF)&~;rN?%b8G!o=v$A@4du)I4a+MfEXQJv$50JiaA-wkO=Ux+e|0VDRXAO*T&)#W zmetf;>9nl0S@I7UTt8sC!=P%c7}bI3qy=R5atP&bsGa230;^ZouJ+fLV>T?fox+aN zq%iqX7_Fl0s#RbLj90F;IbBt@vJ%5>U9G7GIzm&5YQyR)NwcBWFFR0TZSdg1^%dIS zrT)Pce*fUbsy2A`q`~=GrZyatP;=!!{-@>UXBGGdmrDvYAOS))P_G5nRX5l|LEiey zwb_+5by$6if=lbmS645stT?ZIwCvTDWza2*RJ#fatq<1KVKqnZDyT$Gr<7Y+52aJ$ z|EzD0ZL|N7?wU$$-u&E0_?KSkPp%jSo>KhDWy5OfmY1dY>#LKm8dm8CM-{cntA@cd z*>$>~^8G&;!!7OsT#w_nmcNe4#Km{u({Ne1ulpSP;kN(9b*Sh6Zv6S?zVH77n&+G6 zTpV8^_$iJl&c(Ok*8fMi|Ao%}|3Yise<=46_!6&wC)XjRuYAzt?>PC3Q6H{JxcFnq zS?c1iQ=R(x%0}Fzoe%%N#USnbVGrC4Oct3EFc--5{PbR+S;BxxUY;pyz!!4cDz8P&R zBid(N=epjU*%ZZNQTf5#OHpyg&uTI?zultodB^UEHVn(f;OlVf(?Oqi`D@Y78IL}k zp+lZF@G{S#k<&HG;fs$B7DkNAy57v?P)A<=Kd?}D2VFnv{M-lpQq1YhhjH20xiA!M z&RG7hZqorfeVjRYh}{}7R_X#nopv7T{sreoavXS_eU2Pgq#)1% zKM)aj+YR#nlOhInizRJ||K<)Hb$)0QL))UU{5S0`wv%UFD`26zB6#eNA4Pv$oR;N4 zyKb?ZChMKk`T=K1+!k5>n|2rbO~Hj}S*WfZ(`Evfg^Sa&%(m+m%do6>PMZmMH7<~1 z(JZTcBSC&L@ol#jvbY|Xt}Vc~{LrJf;Nm4K9}TcHLshhl!CC z+4nBlzD1V*rrpJUs=dPm5#uekKZ8rx7P9yV7pC&DnvYMQw zJrljb{x~zCuZy%oxF8-2HO$L08yC-aaIt*Zu3Ic)k;Wo5 zz`lRM1r4x>LbI;TXThGRIz&I{Xf5p8(c0lO%#Pi0(G6MhEkU{=OFnRooRWR{Xckkl zxCqTK?jndZrXxf~pyMLhTGZLvp&2IWD{zrbmi2bs zV#z12k!-T>9TK-imj9;R#eS;2!?%A19IuFI<66KMdpSMJ2kp8gOJvr_>DhN1E(~XJ zC|auKLlk_98=)n3d{TBSWbt>|aY1Lt4%M*ZF4=KD3z9Ll;F0x?h1q_9^x>~8B?)AF zhZOP7hkgG=BJfw18CXrgy_e-oS>NK4r7cy5QZ|Bai{!BAC3O27SA^qo9qcYgz>84E z*>#I0p9)9nhkYkW+!l*vJ}$U~!yuQ=`Leme#j?n*TP*opIFc0muD}IVvtTn6bJI1E zwCwi6i1r)K(>|Z=uSil0{)~cuJpwDi1{99kYXPF}FK`+bxgKRv@R9O#tS=u~qaXC7qY(s6? zES5?JUu64eJQD&>K9;V&tOpZWDq0sbELMza`<+clzD=HNna z77G-b<;^yl#Xq~-y;&CYkiA(1<7_m`O}LQCSsYSmmL6ysv{`&^E54590Nkkp%_3Ub zAXpcG-rvJxDRLDJUGwj0pbHDz9Kkx8U=Hqk*oEbCT$q!^EegFIF2{wTEL^sq*Rf2)1vHCs3eB>_Mzc_!QRjHZ%kUQbQ7(*{&tjdd z7QKkVHg>_QsD3Q51w67iX;<%nQGY4zTkrykKiE~ipTIw)iU^HCF+^4i_MrH)T^#{0 z8;1)4J{83ryUOE{jdt~66ffD;!zhm1)q1$i)wnS17bqULt1qJ1WmoxBc`hz=U|7Ck zS9zTApmdaizbZ#Thh`P4V3MIa8W)6TK@S4<3ET?o#)ZE0r=z&gfd$$AJ};NO5vt1;ayea$p4mL2+_mh2zk2OavzfRzz@eU_}Hc z2UbLIa$tqS37v(m0YY!DNKu(c0+BtUq_->_tJ)(r661mT9#_OFMPF4ppvI96L0IF6 z#=0XJ>yBWoJ94q^h{d`i73+>rtUEHX?l8>xFOmMgkWry{r;uy$9t?PA!T)g=fysir z0_(7fs>3O&WVDNPt%WT3cc?Io1r37^M5plcRng4MZ?+IMoJFW_=FvK(mFEtY)sDsoo#4a@c|vizB>2Q8Kd6`ti`g=cBg z*y2p5MbL1OmZIT}py7(3;fAH7d(hXP*w|AC@$hz{%)x3!GeE` z4MN4U+=dGSS$wb1EUz3U(JXf2VsDn|!zG%U zQpugfGE+{nC7xxeJz)|{r90##`xBu%KXs=hOlFx0(LmeJQi+(%@~2X+Eq<0t#$=X0 zdrm(~HD@x*I)!JcgimIfC?($FXQ`x5W?8E6EZ>p!U^2_&3eR#VR0C}#v&@k7Eq<2D zzranWe9EqaSl){Z<5DP}>I=o%AHHn55*M~KccXa7t~#y7056rOg3i_gr*$xR8i@;e zaWJfuFD=#4`aN2r?6FJGQhs(Te`bF`j-4MyCsN0@%b|=^437DEXdGfC75b6yDb?e_ zV0lBSd=Sc3BskTt!>Of&Y~yD}w0*2l7h}HwZey|Kw=|7+um^Cxjm!Bw&=o)b#Kl)X znd+IRxF|WFxxoJ%*WI|#&wNpSei;HMpEbg)0@4E@?9*Z-xNO z(wu`2Z`PqNA0#>-J_O=JBepTW-vIj0;&MLRHS=K_lQ@^YZdh!&;5whTa5HuT?zZ?g zD%V5j=E!N^hZUJLxh>$Hz*!K6`(Y07>U;v=u?`pWE!Rr6aogd13Sdb-J^ z)oLp%>+8#wRie2xKX*}SNl`#sUD*&^y{fdXtYJCPMIe(syL4Vb!Mvi};s8;3Sw+RA zfw{$ni_w{ndbLu!JD%W|R^ruGOqM%0JFg@sFmG<&;+eUHMdYfqpfIpNjjO3%S>3=v z4V9}`v42)x-n@lbbBl7>F(FQR+L?sJ0qYiuf_ZNq)2aqnR2C~9O0A_soB!fylh8KX+oHycwS*?aUsks zHIY3#tFTDE!CBg1zZH>RO2*)wHD$}{}WO?73f@gf8~ORK|+3$?4tYVf{fX?aa;eWg~pt_**sr?Ry3 zwTY6_f_Vi+c+<4BzWORgLh%fQ611sRlvX1|@=J5FiUXyEf$Tu;f)cqXE%Fi?=U z7&FqAMf0-fAe!xw@+BNjT{1U&US1xJcVS6>0lL~I17D~X%~>3fs)k*Qa_7xOc;XFL zXr#21Z^zoMYkRnDC{kQh94O2$3KSRT7U#*)#WGTm3JT_Afof6Kf- zMlYTlfR6@><`t65(xo+*D+St4DYJwVuz2CUrmPN`$d(!Y0Uyo_WEYphGa1fxW%c!I zE410QD=YEh4^`>76x{~SnNKGzo}G;t4S<>4nTrX}D9p;u%L~jb%!S`lb<`+hLTgx6 zyOwM%L!Q7Zva7G;FA}h@;eC49$@WH01QF=;pti6O&Sx8zpo+tp=r9`rIgtBd z(#ll~DH$)ha}gX;`c(+f%ZWaV?c#YvDaX&5w{UKD7BaxXd4)NA4Y`y*f&+`?c!^nC ziI=wE;5C&iIW;on+$@M(#`l{eXdn^gB3I^Kq^OiHFT)?5s$Nx5xz2X3^5xYv6?i9D zQ!frPv6Mr6CP?Td4+Ka*2g)xFl+5Mg5wYZ#)>oFTE=N?Ys;XRFU5h`;g;6u+Ez&9~ zWz?6>Dx6nBjnPfd6&8yQN!tqs1b`39#B!EKa*#|5bCH1Hol1!|FNBJ5$>4!fDEW`3 zKpMIbPNOZWt*xl9UdDENG!s&XS$o z5mOLk)-0?=Od|Mud6hM_b(Napgo&pVugTTat_{|e;t$XAt?fub)mW~9Tyd!=n;isC z@ceG(L>WYP5;il)%-lRIEL-=hnrVK?JmhFDC|X6ZuBN&iGnFbUqE`u) zOFF#c4svaZ*j+dqj@ei^;kFu<6vh?3Id|5)xr)!MqU_vUd(q18APJk)u3g2%<}AE) zBkrL=W7RS=l*mPmdAYbK8%wZOUc0gm8>f0iSuNvpX-ye&M{pH98if29_kUG(=5bb5 z^&h{?xPbdYuBeD8xPYJtE*K2V3^OvDv#^O?XJckyHfKQ~G&L72G&M5ZQj^ro(g>AG z(~Q)T)Czx^E163vKU1@xnr6Sx=bZO*=g#f-&+on%-uHW+^PF>@^PJ`T{hsqYHw=L8 zu0AOav(^SISwEqnHFfI+cgejB%2jfmg?cccx4XT5d78qc7WH&>gfYw$kD7y0Dv^Q` zZ*|hG&aLlpA$)s-vJ}SIQq3)T3{1M6`^56*zSPq2NCHU|7FCpZ1}jfjspcvx3d+*O z)s^Kg*PxD{1bVtqkBg&2NH?YDtkSJ*dj2EUxaOPW)`a^M211uN+#IUYxw~zsY0gEb zRfrSMj0B;^3rlAe)zl_)rc0IGHiNFFLIj1w_e#@UxJ8O5)h|p2Mf2ip7pkP7uC}r! zw8^MyC{K+m;o3CUrlaB%t5?^kp{L9@xZe9DL*5mdY+Wzq1)6b`8RJQRz*X-R$UnjAt6G4F#ZTBd2~=Z-zPbwCm)WUS zJ@C`1N@Db>sML6->Pxw*oK00}RZ&I(4MRTTS?ud!Mh`bFRHnvyx9QLa;ymu&qwbMA z{%T~>%o_*KUd{DVBUQv?T&0L*x^wDd_3d3PzLMVV`o>Tunq$bxMXZz^6FZ0P7vFNO zMh7*rt9e+rU!HCZ`+PmXchvVpgM^8+v|^6t`=DGV7KJY})zZ`D`NI{VF{-dYrbnWs`7&B*=nUOMy7jOp>!V#7pe*h`n^WmB+ zX*3}=x=UdT1SO}ZE6nzxIWeRr3PdnbtwOk(LYIiQCBzM?l$4iRwa|)`G>W2mReEHt zv)SswiqrK9=_V@xuZDi`jp8)-pxVVo`%oXi?o>AO|cYQ9Am2t%nV zHioGyrSvv%TU))F4zv}$vDveoHi?H3Oxm=%bTo+K5R=$}DwH}-v?L3|NN3&O3V%=# zY}zS`CqBP%# z=8|-4=2y&A&qxMqZZZl_P>CAbdVAA;$h)~+4`D`AG>jk7tW=-Va|Igbme#lTtKry& z(wI|_-1X4gOFby7jRhOL$@ktR=VF3YW{*=vs>240ZfY3h>zkUa>oSI_dV^XKbm*jt ztPIunG-nhQT@@p+n?ck_rH&NY22VniqMj%9laCq((;YIIbeHE<>5dl4q2pOYMbo@o zSn0kQ^m-{|x_9zORMeGQkyH$gjvBXcNJ-RmrOCNmRdD9LV~}ggbzmbdjAyC<-PUxkJRqv|f|)Zlp@-qg*BzY^jISDQYvR+UYP#y2 zwVs?An1i!7x@#&c>_>sSbu-MM1T^L%{{6GDeNX zSEOM)sB9heEp4u}sFe8TQ6vYnH_I&2bccf~9t{JoYKE~bnN{P3sK6>%XjX%3zox1{ zW?Z@#_r^dz11Y&!QVpehXU0fd@qIn@oxSbRD5;%WP%0Ob5Tw_<0)hMS}RUp4f&=EtP!5zc|pb{qIQW(lJ1E3yg?&=StWE^1BC~e~F zri2?1X2s}bO-5ze=W6V2eV&)1O9F*B)>)VsGLwOvpfc2a8H&uPM$c9ID~qmTx8g7; zW}0NUlTzeVNvUpG3f+BD*rc`E2YhU+d@{#&wzahOb+vaL+tl39R^K_Udr8Z&UNDIN zbu}y=H~6XXaXMG6GB%--Dr-L~QfBZD(D^*usiBgRM>_E@zsY9E~nSv~kmkM@#ocqYMrz zWmBj^Xb#bgs|r?CyKiLfw!EnJI(BHpmEN05hABH4W|mgTOBMRKPOMf(E3GJ)A)j06 ztdz#AdMQU)3ArXTBr%yOTi-R$K<=%f7ibE$a-n9wNNQDmi)_k8ZSo;?c`S8O=&EX* z9!CeOhbn>Eq?C{HG(N+q-|Ir6dr|XeUB&E*s1??_G$n<$j6L#Co}@ZiWR*`541v83*+7P-dx&V{s zqWUG-PJs1b)0AzmdlE_M<>xuYor<<36J%a(v6j!i5?u=ey9;I z*8N8&iAzkGM?Xun(`?%GN-MP=K(*4+n^qgt>oN3fY9@!`B6%g;#-zTwZ44TUmEP%f zMQWO?IZ3xoZirKjzE#gcO?Y5EodqXHaLCN6s2e$RWOy}+^9$=__!AN0K%#?Eb?mwg z#;?2|JsLNAHM+T6(SpVJ3LV_5it0)7&gr^>CLBr`zv6_9f{GI+$lRis6Zf|{DDlInu6yt=42;~MnqO@gwjz7;j@Xte}&ONyZGa8L`X zwEkGFG2Ui;cYjYb8)EOZs{~`PCbdWdrr*61PSUtsQCnJED!+8}woCt!-(Kr3#i0Xw z&FXO?WlHOfBbWP1mlbQ-Q!KYUj&pd9z zq$x6Zq#?N)21b$KyNK>%Evu;0st&c*AiYY>sXT3CJ~N3}MGGdOZ?FfYXn|<#2$}<> z>FerK$5fPxI@w8`(aTWT-ZU_IB!gj8#%Io#q2f|nQ7w`+?p5r@=C-9#S;IIY4L`gNqsVrGz$Y}Dx9MhoOqkif9JcwwCGNbk+zMn*MP*h?%BRNI1 zJg=#yE4Xb#zp7O`2_~!Ddd?lq!p+l5D%s@^H!Z4_SyvV2Dx0*S|7FM55|^Dg!4;v~ zVVyLZF0rK~s%YZtVsSDIQt`W$!!S{6>W;X- zgmEFG?6~CVPAlz+5)w7zhI$q`(P`q=mRL8@cahvh#=05xjZ6BYXJ1A^U?imEk5YRSvQOkCrKR3N2?H8kxiC{l8HeV6c$R-UTD`u(Ad+y zD0$;mvb89&98{W_p%!#mVW&mL?THUs_esSlFOWw%enIU_8h{RlC8_zLnMk=)T}zv{ zIH+7PqSoue+T1$W{==ycNy&_7_iszY{kjnD^a*aI&6!?xlA2H z&UJOv2Cv<@pusuCs+YHY#QjR)c5AqK$;>Sy!S+nJ-=zlHpn(`Z7$_E$=C&^{SMJSI8HYqywomsCiI** z^+i=*bFED2sJ19QZ~iIMw6E#cQ&Xv&W7-bT5{6`Tw>Y`csJxb>PT1*Q*pcjN2`;m+ zgUYWBWb_-~C@m#!O2JA}2GJ*@tCk+*KB<8>E)yvz+?~W-rn-u2Fa!2TLswI9t;AaN zjZ11Vv}Rpx%q^(ba`kx2kPU@UW%gJ{y;-KZLuxfmTGR2^%7z7B#(=X?Yl2eh!$ut6 zCa%A(YGCh=QgJUV*RHC{;$qt!y|N+O<$!ALM#*;n!N?3vCiFHm-l#z;=`g&7L9=$Q z_F`!o(bfm4eKT3>QWUvb!m0z-kX>9oZDDeE*+R`}?^og)RDTNl3}(c45&G>t(OIko zM{OiYpVKejj$3dtNa{+og)x{`p+>w^5#I+T?`pEX5e>cIxC)EL=k&K}p(t6D2#qb& zhgDeJ+UU0_vBf^fVoWB-%!+|05iE46T#50M*3PH?9$W94Rg)@2KUZ-RS36zI`bJ+| zThd_ZhN+!XeKH1gk%M+`C5lsU^GDaBdsUD20!1TOY1^%U5uG@8om=dXAo?r{@Afx=9iv zCn_N8<9Pl|(x1zbd>n6|`0^J!z0B zpPyPu&T$$qFV^p!IRc;Ln4cobPH$VDeiBMyNxdf5+n_L?bDaMC`B_g&KQI-)`+tA+ z-#IXecX6M7O)o2+)3bOn%oF`t+plf@No7iQJby0GUv~LERQa~5QMi11S|W43SLu6J zHmRY@RWDfqNqVbu(%Ujjk@U~$=?RETdN<{y_udNSr^hUlPm=WAIr09bf{aZfWgWXy z-?Oh{%T5FJyqAu-e6IIL^p~Wquc^bYPNhcr3!miJgOan;dr9fJPxw0gv{91Y)B2vA zqpztVrFTJAK=M`1Jj9#eNc#Nh8oi1j^QcZd=D2^+UviG)o$|1L>(F2LB*)&DoP778 zd5V|)NsjHQz^vOI;)NG76FG@zCT+!sUf-n0Rn(sKWJu}={rP%*{jQVj^oDQNs{(wG zPm*3DC(I7tF7^JulW;SC(3M!u&cX8b+0iAdfo6U3Q&}BP;rS}%&K%d1IJ&MOsga`p z64_mUy8dSC&&T~;O)I=3%yNak3*nt$ma{+kN_~L>lJ|o7c%vgYn*N5U1Rjj1t3uC} z?Bh!%KcdU36fJ*6?AB!+jeLXX7t_oozQoKYKebEh2a;}4e82O{=RY8My1whH{^jfU zB6YqR_%zYSpB1Yl`#oQl-;#W<2HzHre<->H%r2HuJm!}3#E9bZBDDLuQC^~v`SBW8W_^=7a`vWnn#d326E zB}XpEk*jm$g*kFdj_g-fB_HQ^UXFZuj(ly7?AK5wAD{o-9Qpnn`PVt}mK^z&9Qm&~ z^7}b*eCKv7f%D(XZHJF#{~BBJu{-JLn^p6WAA79TsIr2j}^3yr;%Q^D9Ir8T@@-A6j$oUP=kq^p|56_WL z$dL<UsZVY^@=WX#<7IKlt% z^0Em61yv^e3)8k=zDkyPj0VtTAo&I&k5_~UT+JL zv@~b;s~!>Rl+RI-)iBz6RA1qNMF;)o5=63u6%x=6a_xcC&erv%3S7FuMRc*9SSWrdq5=l)ajgHaRPS2$DtLU8bLy>a$&tDwE4a-{141^b2uJwX}Iv`;+rqv#=tiTlOf zdRojY)4>`KQC&{0bIR}MV(7ub5UQ-smFU(}DBn=1E?(&K&n3)bg#{5Vs`Pjk4=Z!l%( zo@2Varpk9Uyk5+cvGJTaU9UWFxZ;({=Ey7151*U5FISi|^qb(O%KZ~_rrt4RsvMu1 zg}PoDmU%_`NjTBz6j@ff^_EqhODrqhZy^8J@{xMYgXwyf?&te5M)Y|NX0iMrrt0Ne zrpkMl==SkbQ~5mRa9w}>&XRR~ZDxtiL%v+}{rEcat?+h->we#d{8P)y=W*m`;NRf1 zU39!u_NM4|R1KHFm8SAvBj%l^bj;a$VTi*I)Qd7yR+r;RvrO-I6CHmWe4pbVAs?Vu zR`~cR(dQLf*0Czf$LRXZa=mQL;c8#^!(W@K?{|D$=jF+1*u=ydiok5<2Tc(q=`W$Kk{Uvjw0@ilm}!)sHir!4Ed z=gm63FC2O2J#}2=Ib3u*orrv@IY<5whaaK-Wh%d0OvSs~$93NHy(FuC%0#!LT63;m zYDf5`@M{iNJ*+{##Z-CLJ6!GTMZ!OVDZP@z@pllN{wc85;q%nqke{?XU;R#Ha=epG zrF)v_ez*X6k!6+ldb3=w2r-rZ^Uh4ACLx~!r#oEvl_ED-K1(k)H7Ci=FxBp#( z*Kexbea+$OKmPS)U;mvP|Cwc7_am0;H7=SBYEN=CIQ%Hl<+}*^Hh8DQb-ni^zXiu0 zpztYrA*?xH{X%p)O9@|z{5{KKQmKbb)#DT9_*CjmA6NO`wXAgZR+-&?4~56VQ(?KO z^wY2h-Uja!eIK@(O7A06`Q?v@=M5Eo9lKjrzQYMW$l+?&MP?eQbz&nzqdyn|xC2Z_G^A0XdnS@EAVRlYx(s*jxyR{T>nABuU6nx~KtvV6K; zxQTqEW!>lFkf*>_Q}xr~a2>DO&O^2)Ahm6*r%DtOt{bRJ{e9aqh3Y-R4h|cF;vrTU} zb-1qoDO2gZ;BeiSw=652gAR{8M)dWcZtDDIQ|+MJ$94V%rp{mOaGignStk96@QvnT zy${mNQ~T5ykhetlS@e0eu+`yTRK36-I$ZI8Z&~r*wX8nBz51HZ+h272Gu75CcZil( zn`-xuJ6z|#V_D}Pq-$`ziK64pf!CVtdfzz5?<4$KxqCS+@q4C-5)N8Utr?&!r z6W$DOhY!NdqVxU8>`J8$R^2(B>7vsqvfQol-aIG%^m$&7=4p=K3csK_cKjnnr&k6S z65elF>0W_+E5|n>e*||N7tbFdI=vHMDd8Q+7b2%rmyS0S?g7IOV=8=yl#Xw&*O8fO zqf$!(H7y73Z|WQkhk@#bsUbVYwHU`go_HD(Li_?)0xRJh*aVkARb4pmOYl;7HM|kt z0oTKa;1lo+uo?Ek3!&{?$G4qpejok> zJ^{DD*Wi2bbGVDzzR$N^Y>tIf;7oWrOv4U%5xf%K2=9U$;bZVQ_&4}ZI9wgk`HzCr zV6e9p-hkWzm%&Tm8h9IA4}Srlf#LTPl-|3@Ub1w)d%@9gGAw}$U@yE3J^+6MpNDV4 z4`Ke$n9n|N1RMp&!trnt^lu-ydUz2$|l0k*907r|BVO1K7I4{w3D!@J>nxDoywZi2soe}u2XH{d()Q#fR&SZ_PR zUE$tve|QKy93BlP!YS}nI1`q_N>~Tafc3BicEDb^9DW&I0>1{YhV~P=o!}@Q?6S=%2fAKJUQy;YaXaFn{M5Zy4MiegPf`4~70I38y;_9uH4~ z(_j&t4gK>PK5s5O6E?!&7t`@BJM0$2cZI{@f$%Um0ZxN;upX|2YvEn+0r(j7mKv91cX%)y2dBc>Z~<(C ze%-LozYJarzY90OUqZhK-|=6E`S!Cqe>ejAHTMob8CF62aUI?U{ky4_FN4>@@4^l6 zF&O;2iocr-A)j{u90MoAB3KI>VGq0z2EVV;xf%I~(7!<9^f$v7;oESi{kS^5FFXRC z0B6DZa0xsQejVNle++*GpM!sepTb?`4|cwXz=?1UY=r*Z9ml&2UI)JqAA(QAKf%Al zedPo7`A5Q2U^z^~bKqCtH{l)dC-6!5GW;7HB16{s>EY=g_-W$-3=7u*ORgInNxaOl1<-;r<}oCZ&a zjj$hH2CswPhY!Kc@J0AG`~(iQKik&}C%~z&8GZ@+RpXBT2DJa%@-R6b%#&dFZ3@Xt zkk5q|!&~9K@L~8Ad>L+opTeE&?^e3|L;KGyPl3g-3HHK^;MMRR_;dJM_!4{v{u2(9 zPt5u32gkt4ummoE?eKhf75om|03UoUJ6&kYv5Y=ZMY8J1@DFT!w2D`@Co=7+yY;KTj85<8~gx%3_pi{{lDvJ zC+PJH%lp6)a1=by+!%_7qZt~obR9E+wgt(G5j~&!RslC@AVmTI6M%Jf=9v$a0>h) zEP`dQ1}=d0uoZT}rSLp>G5i|528MMZmG2hhJKzuDeegl}OZXf3JNP_&6}}1o8-55s zg?S@my$pkUzKgx`cW!rS0o@JDbX zd>B3ke+#$37vXF0ukbzi5&Rr(e`u_yux_UNv^Vkr@K87w9t$VKQ(+;T4XfdNcs2~{ zZ_1|=xgUo0IE8-&`K$117}n)<{AT3a;Sb;j_%rw@{55EJIo&%S`FT+dW6>tr_0e%O558ewm z!c8!&Ln^Fp24z!TtUunyM4E_fbX3&VP(%K9ksGw@IF1DJnA%=bVz z2A%+C!qZ_IcEI!D*Wn%TY4{3!8@>ns2Yv>uh>-l(_jV1{UcmHuN_`(D*kn*;@<>s<@jA3zYqDR$iG5<4*3;R z=f4Ku{t5C9N5}kkF_rJWrp`MM9>Vdl96t_u3UUE*Epm&g^OwN$3I8hcmGBx< z*L?%WZ%5t$ABDezubC>}+osZg7k=J*514$sTSo^Z0M>ncDlf?n@; zJuZMPa234L)OpvMD&O_++Z?}x|FsAb*6s<9OvaN_K{+ zd=G$QO_g_osd7yvd^#-Tcsa*=k(VQ1Vk*7M;T0UemgBb~-;Vqv?+w@zkVPzMV{!XLsbokS9VtjuYym z$W(n+6Mh5XcbNIw*NnUo`61+ABR_@w0`jZK+u$c~?-OEvN5JFZbXX1-z#jNzcm=#3 z9pCfEwwVK?l9%iv0Q0lXNlf~(`g*aTZ)JM4yia2Z?)FMt=rRd6-D3a)`` z;f?SXxDMV4?}qon4R9lT5IzDo!6)Em_zc_vpNB8Ot?+gD7q|_+2S0=#!_Qz!bs73U z4ErMWJ?z61!~RHdILE_2NqrxIJQ9wEW8pDy0-OX-gnlmF`A&z0FzoNs_cG)vSPSRD zh45_H1Y2P{?1p`C8C(f3fMMUDzOO=F4X=W0;97ViyaldJ8E2p@!xz)kQ8 zxEVeJx4`G&OK>ZE9sUJwgYUr);m7bZn9>{-?mrv~{oK66_kezG-tvBM1RM!R!?Exf zH~~(AC&H<4I`nh(PQL_}!75k_=fQ>WY}f=_VLRN<9sO-2@@V7}k*6XrL_Qn24|y5#8sxRe8<005 UhjBysCF8~pE{Fb0xCiC>UwEo52LJ#7 literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/buffy.o b/obj-i486-linux-gnu-patched/buffy.o new file mode 100644 index 0000000000000000000000000000000000000000..df437260e6692ee1b1bcebf08c93a2601d0c2508 GIT binary patch literal 33256 zcmb7t34B!5+5Wk6C&>&GCV>f;sEEOUge~mIDrA|EKsK`hZey0oBH5bEKtN?Ni5eps zRQlPv)upyytF61OVns#4om#cl-MS)fMQdHE{GaFC_a;NWe&6r+pC2>NecyA=d*1V& z_q=DhHgpZJ<(~h9FKBVo?rTW|xb&7-i$1`*9Ye_vp z=6m8{>V~X89y!w2`w3(mTC?LmW~uK!H$z4J_4{%%3=lI|m+=P*pM7M?7pTA^r3R}q zzHlmW(0HQ%^hDP6ye%+QMLw(Veu%A55s$86Ao@BRL=*L!qBeCAwe32d2!3fdmnut2 z?~$b5wP^B=9n`(w=zhe#W8lb-KmPcy0}~$I{`YP8L=OJz(QVt5igcQdrqRP-Xpf1B3bqObT7d$ zd$#Xox1D}g=*-6+`8c`z5!a#K|D}TDmC%rOqi-ZB zv>}mcywF~y`o`IgQ*Y=LZNJ_4)qxbBqS#o7Jf=$SSW{w|jNi~vsTEM99-ZC{V5?{YB zFI9+rc`1|-N$rn!dZ~9$QqNkn6S=0wD^WYCr;_G^s!2Voag}s`@zfnz-`974VJMH$S8F$S7u(`JkkqpWrl{}!)=cV|$U>L@0>Aa$2aO$(lT^~Bm!M~o?u%pp zbibXJ)N>AM?XPn8?YiR!IAoP)QRUvgUAN)-yujAXe$8D}xo2a#-LC%PalKC_^}fME zd2VFy>t#8+MAH3dP4Cakm<=%#`+5&({xg)Cm)c*I($~9RUnlqN+RKZo#J=7=yom4H zwHv4h6ttov&j9xI{sCOaK>K>{0R^@~*Np2g&F}A8%besOPv0&k>zL86Yp(A*YkJ?7 zw7$HI{#{xJU3(uCgEF=Py7s=Rlzv@(UtV&*-Il7ver>Bjr&^L z4wkzZmG=ktF3I!sSMEu=>>$mKPDb3>mv=0qk9I)={Xbnrtp4D8OMEqk?a_HzWD&-L8oB>f6SwK)iu`1iP4cW6ulyz2_m{ zlDw3p%L;JOmzUyL3Yz!kQHGx9`m53qzy^EC$!7(-I@-x7eIKMA%x*qUT>1!N|0FGUCFq8Gt1_ysdAHPS>zx|c3_ZPjm=&7X3 zAA$@9%zCagehFep<$FoJ*WzN)Qy8DUSK#V@hS-D50Q+d&4?gsbqep-6_5R8i7ad5t zd=qS>Lyqpxq@MFZF9||)1Q&}Ah#pD3Vdfh+xC+4Whk1u_;oy3k?%iXzFR5o47)RN2 zIv4{z(~|_eVxF{ood4qThBu zVaQ_c5^%bIbV#%NHIx)r#A}{uS9r+7Zcc}{Yh&&1R(;jnFHZY&aO*o?Zf{A_S zd!*)r=xC>Zb@}LHy3XifXtyuuf%=Y;c2?+RHxSw#Y((Mu0kpsS6VK7Di;Sr6UZ!0t znml{Yle&G6iT+R8k~XLvyC*}uLizIUPa=A06`8gpc&)Ab|Md3An0-06o91XY?cN(X z{mjP(`h)xXE1&7harc#@S!78?L-MQ2XTP@nlLM%1NAPMbK1hWb!eY!AJ=0mMN6L5H zyAX{#G=k%qE9yvAUj$>&{12tx>aV=IKX~oj-lZrpcNfcf4@95rul%Av_|@FtRdXu` zK>u-I`(7&0_sZ#KK|>u0cRUOR+pqT@OVg0r`{G;ZklqjRi#X%)g2#Bnd`>(k9~0pq zzke6Y^vP_}uO&En`*!VT+OF5}`^a}E^zC{E7g$x0+4~Bwuj4P14$OXR%41mQkg0$B z{x;R-4nT3*Lg8=x<5B4g)I7lGa#P^Q!CZ?YTql}S|wMv)=#0Kre*{* zO`oB*N85V)UiRSZJ@!He?yU{L-olDguV$dfGDi=rI+E=Ye}INZbRp(N`cTgv)t5)h z$3PtNZ|y&q(&!Ie%7AUpvz3Yc+3uwKRL`DhVEbMsJId+wrAs0Qm!?PFcWOoWV#E3? zJ&rHw6chui-xV8jy3bE`JrV53gmZ(VF0wg+ZktvDiJQ@|8`+>g@dwjY@}ac)0ZjDm ziTx`QVS&;8EW}!!PWU@TC-wXq`TOG$$b@!+>G#sFI3&Ow@^9#IZSC2BJj%(C2spm4ta7JB!Jc{?tvsYz(;}3Rd`8$G_(%q2Az2dOg6G`ZgKX?kY zitkT#G{Jm;{nCcj{r>*oANnhI_hq^JPW2p2hd4HB78~rI2;+!r$M-$vG_udcdSQh< z#;|`|ff@4PAEjIn1)M4{oO`!{AGziuPO{y5jL0U+K6|)qJ)dcL+AAmm+4^^}u;VX% zL9Tp~?py2H5&Xn4#tuwIvJ&mrRdv6c>M(k+mp(x^`d~KX*y&EvR}fe@La7msWTkwPf>KOLG>n1(ON^YL3Ia1B(ti>z5Mze&`FtaNi9Y5| z2Ge6}NODxb7^-sgpayZ27Z}oDsC{bR89*5(Su~LO-o;pMhi8&^K z%uCU2$BvB=aokW=rN)ghCMVi0J3dY~XuMRX?Q?=wHqJ3u8uXHODK#O}Se~dmB90=` zbb%A&1`VoIdM1p`vP0<;kv=G4(!3brBoKqWI{9eX?D-Y(G*^ZcL9<S4B_%1;)pXcu*FaG9+us zkdaw!ZvaWm98f~@>pH_ArW)mWgIFEgl`?u0BH2%3iHNlYiEE8#Ne24)J% znnwJMq+D?~B8%G{*VGz;568U$rA$x4m7`Hru7#9^)sW=+5_6P$Q6n$2l5lz9W?mi# zvF?jll`8`U+!yQ166Wn=baqXKH1{PsFXNrNUuWn>TytNlFW*E9+&kVtUeg`77SX`9 z80K+b)&@?TJHd4=TIb%y^mw=HVJPgrg@kJi1^XIY@EiT>B^gj((z-AG2pt=-QEu5jJJgJc*~(d{8%9qy>F3B6*Ad- zE7}o%jF2hbI81=?#|oM1{SivUA1CBE?|CdcPRKN`g@(tE7jmL^0o6D`$PDiiv^73W z$m!mPlR=(nOhW~(^jY2uVC(pa#%xW_^UkJ8PLdWa^txd4_^CoJ^*%t!(~TE&dsle> zfX<1ZWt^hPT<_cH@%Y(Bp(gXZf2XK9#>rapO7A2XEPjEpQj_`KMmAx&@t)3H=#5aT zeB%dAR(PA(q5>h;de3F*Dk0DCUO;lSkY{`QNERBCblE!Z0ZJ|wog2M8Yl<&5igdlr zYQ#uHxcGZK)o_Z$_y=eP-#4u7LE9qAH;wk%Z5zbx+fU(p>>l>OE51TA65RBJL^=qY zGxBp(K`wnlbI)|RlfkV8;b-0iw-)mu6i7HtH+&bko}$Aj>}mAk$Fuo%>T^2m>N%He zc$IGs`oMFZcF%OT@+`;bIomt^=jbIn!bY5A4=&}q6C-lOWEpC{YoO+c4Cy7`6U;e0 zNr_CGItwD*#tE+UZm0il- z_#LGAj=$M}WTRDB?Rof`e~An&L}i0%8NQ>Ov2~3wv&iC zxWGDSmbgpuj3Z|pMqA>~gmWA@Q((r#>x6SGITcVg@fX55hMe)#^Jd|sf&+t`j9e+T z974Am18Bgg#F5jUgav%PP-EnD>G{p3G~hK!u~U$`8V z><=FYO81(--tnC;(Z&7-$9F2>s{Y1F+MpiaACcYPWJ^p`uCZv0|D0DLYmD2!#8`u= z!g>T*l+}YD!@3u}HB5!P9d z=d+$zCl9SeY>R7;80Zv8*5A z3}dZnkdtb?gq+7%s8$_oO-9ciXFZ78$624E-s7#)q1$-tkH~p~l?_gsMNgbyrQ!NS zYad2kx|Ivb6Rn@3mPuABQctqJL+dA7Z{Rn>;w{K2)+2C$sn+9=Kg}9}Qq!&9;CF@< zMxIP-9e!t873kbq)@)qQwzAQpIo5^9Ki5itug$Yx=VGf1rIuKGq1#gH3bb*Vj26ww*ttyM_H%9tdA&b3p9OHS>GbVW6GM3 zl6#ePF&go>vVI1uKB27ppyEDdy$5Q)vQC7MCzZ7cT0R9P3Ouc>d(p0El=Tmo^;u=5 zpw8!%^=nYiD{Brcdq7!nDE?<<6`;RfP}b?F_Ako10o04iN`R?fQr6vQ$;-;BLAk%8 zdm#E1W%YsiH)YL6mRFT^3E(wlRY3XImBj;%HNI~uWhV@q%>r%t&gn4!t)+$h!8P*RFcDZ4lhjIgk6^5{#hV@evzrwI)qkUHz z*89kLm0{Ju)pi*c=c}I@7NgI98P-G;zZ&(SDL*riU8$cN)?Bpc8pHYo)U_D?C~%!& zJ&hW!H>~@?yuq->poU)PD)U^M*gkB_YVmDaxO$lkDk$ktO9ynAtzd z#p}_(MMWNeifa#uu?TwpG5V5ofG%vgoR;-b26enyP|?54^@=X4ygYmJpCY7tY@|*3mkZ??TU)FAD}+iMTSGES$Yk$xsM4P; zWQzAL2>0g*nd*HXw)W==InFx*p5hNmPlbgZGap3i(Iq8#lpjjc~|+1h0OJ? zW4$Fp<_9i<5BN`Y&4PvWLZL9Qiy6vpb!QDqw^BC7(?s^l~qd&lPqQAd)$Lk`NMoX^@%bMbog&9G0Z|14KF>i1qrLx)`U z`cHW$(RODG>GsZIv1%bb-rur&YlOu7Pep2lOb(>6SL%jZm=gF3y8FXJElde$kEj<8 z=KPe@I?S>D2H{}NPf4xqz=SCbO!+A)Jl=| z8;`Ky-y~%-yfZ24JRzrh%Mt4Q+l8FvrM>+ZxVAuHtX=I6y2#a|$%Wp_=>-=HxpZt} z9a`V#dKx0=Q-7d8_PhS7$z1O|dfX0IIr_nsp6~6Vo+bMv>#A{x=IJnVf5>^Y4X|M9vHbjXQ+nC+9sH;ZEUOr?8xasBz?qd9oz8hvdTdW(ni?(^dF5yEfRp1z!^C6LeR;s{F zY{8#|gH|fr5)TUptyF=Zv(z5ppp`1{9J}-p;h>euw$`J;xL}w zfhV2R2ahYr=u$-GK+#t~Z4P%e!sAct<#} zygTqFb^g0>V0pKYUuYmy#A9`6M-`};Da61`j4;~%>06?(EagH;@q5tib;jnY0A zGSv z;W~&mV~1;pki)LeHM!J#Cyn!^1eg`xN?Q1zLgsoOV!dCxK85NG5?4_2x6;5uZw^!c zEz?q|_gc1BnRa_C>~)0Ov^St@z0b2n38uZQI0M7z5@>zQt&nUaxc>}oQg{UGzt6?t zg*}!Ya6F6~O(n*O7Jr9Lx+VFp8BY2?ya!1=88j zWZ}S-RNzMT&nV$wH>d(9u+(Uq7SnR`g`uXLhpLLKoWB4*bQ^g zQ}t#eGI8=x;;?BD%jJ4aMvO)w^SwCZ$D&BcLa&~p&k?e8Y-@O<@~;=N!g~xosaeRi zUOjua2ziEAPhqV>p6%7MUYn40-ubMkUC2i7ZVuf}2@%cSuPHeqwrckVNNyCLig-70 zq-`<}>E>?;yhcl&E6#$`vMzfbJWn_X1YLoXID4Ki90Y={Kr?%1i*OJKx&qnkpsm6| zAm|FrV5e*o4gx`!Jr`^j4%R+hfg<+Q1;RmS=nCv*cXSH}p`ptTfEP;Z&hviD3HKs% z6pne#^lb)Q@|3GO&lo#5UKD<$%f>3g(QpV=B}oIWP@q44qiL9Rkw zj#*L;(IYQ5ZO&LEk9Q}H+Xl2&!Dz}_ff!;~9mwUfehI6Z)>GiPt&5;QoaIHO@zz5O zyB43s^;l8#i`N>3vLmeT@$0kRKx(4$Jb+@el3&a@7Cg=zqmGenqK~6s)Uoy;uumID z9mi}Km_CNRQR8eX*~j5C>UeuFr6kk2Mvb@QMyij`fR8%CrjGT|OGl;I^T{~h3s7X# z1e;3p-2+8OooG`NeHTK#QR#NM3?Ch5)I^(_>iZmBHENPgO^4lR7uPO~rBRc4Io>@w z?II{@HKT6B`VRJTStkZ)q;-f#ZtGfYq&HA|ymcBTzy#cDaowrAfM?(*%!jBHBar$L zg!rBUKX5!#5x#ssLO@{rdz$k2ehm`^((E(oWM4JR7ns0acBPN@T?!=wCsKqfJzyWr ze*;2y{t=ayTTrIPY%`C;jQJVL850a1uDkXc#%T~>&PT$DMHKaz!E?A1*CV##`Z9=6 z=>ssMQKNIJpCISNdSz5I>P_Mf!KkI{owN`oj5;n7P8v^d2~)6|Y+OpKd~DZ4&aueH z&nFO+5ou}1bH4_!r-L_zE@6CPuo>pgPtKq6TT1%WIE-}An=;zlI+gL6)?^j(Pc4Ui zjL$XQ2zuIi(8TzMttrl(Ax7V%F!7l0^v{t2e?u|D_y+bij_6EjP-YoA`$D8$cRbGZ z+Hqn0NY(Gc*VYdjq5cN+;>^w(g+DN1ubDe9-8!?grA`?xp>NxgQ5RN*X;9Dra!=ie zh-$cvn?b({+HPH(wCq6r6q?EbV64~l1)$ZuKVb~4 zfa5Gixr{n=#XhavZZ42u_)?NCneLl5H1A7I&#&t%FMrzJ1 zl-n-Z@6p+n&i@Pa+8^0-OOMK*;Jyl4C%Eai3k=%ZnB_87pnG`!IS*R6#^Vqb9xzj{ zFV6;N;SNM!(34OV1L#zX9yD98UEc$3_uw2CdvGLzl3HZ!MnjAVE^USt5WE3j?gAEL z8Hto@jcs7OfNu-P^{8|5S;u6Mx{gcjItI2b-wX>FJ8bffEh|{%r;wMx zmR|l2q{URL6`G8cWlX&)CPif}raR2j?cRpedlB*$qqZ76*|!8EdM-zFJ*(HFY(7J= zJNnAQTbJ{`jIn_E+&kZTcx$#7C5@9gNG_uCP0CnE;sX%&cEQND*avd&<0(t z@dOfbblanB`y^DmQ3sNaT4i)m$fU?7IM*g#=FZMTQ*(nQ_zj-MpD=##nPKe2ukjl# za}Si^o%@;S*5}e3)BZP)08a;N3EV{!JY34;(WLR;L6p85WL~%f;Y+8wb|%`L@LS3_ zgv9JyS;ueLCn@mlr8Q9~dz&4Zdd}Bfbi3UrJzI63G{U^yH1VM*M8sHrCCyPvX@_R_ z;4;4**9Dj3%8YJ1KX^4R3U0!WQM!_G_-f|7K({^r4(4S0UD5Uen!pupcC5gmLhY7s zW%o>D+=w$Vs?_py_WcY_SaBvU)$$3LKaEVA0S{EGZi3O`cJjurVXWE(|BAc9CRQ7n z6R<*H=M<_{^ARwTQ?IOLZC~zW0yBul{>J(wUiR zX0)?oW>afzbF?lzvvX6Y&1i0_nb}ZVJF{ut!UZ#$n_8n?Ga6c>Gv{T_&7AAxKDua4 z6aFqOR@hO*%+}gyM`yTmBgRIwzJ60Cd{e2;NOdH$5z67Jt}a}UYcv4f8t%j;)CRk$ z4VM@N(8#%TGN4?fsU>Wui!2oCsIOf(XAZcip|QHN(Z1>kH-x+FtS!+Gj+mUj3D8rDZ0&78$qx&aAo39DRW+-SV`WUG-<1 z@0@?z17_mVi@thr#!OFd!_F%|@XT&Gy^ z|LK}%tfd+Hc^$ng~KbYT~_g-W7W$MZMOgRZFo zwC$&t{?#=(#q_(D8)iqn>Cc2#t`m=`IiuY3Z1r688Fl#4`^_iRe)EB?p3EN4PESvM zp_y3!&!;_4c_x~P*PA0=ZfI!O{Jfd%S?byFRd@G&bF0nendUlA+Aq4-bwi)S#sJj0 zb&KbE*z~;~^RT+WT<^*BL~pplylLxxv%xcPqo=_&DX{T&GjN;PRBw)5ioU$Syn5?< zt^gxOcw<^ibyIU%Q)`-<&VQK*1d}@PZzh-ii|0(2%b7M4V^@tBk=N1IlBVq6sj8z! zAuuaEMT!NWah@m9?Y*>69@nW=OdYFJtDMvb zE_n0KP-~c)s#DiEskG<>e5nO7-M;n^xgL+zf_YEY={q&@CLh!wY)8~$R^lOi!6qz2 zU?ZE@gD=>GA~cL_;#kf@s+=$ZU$TjdZ8o7r*u>2?n-C}35s$|gLI}f^c0s!)tx;7o zfIgRa%F|$3GjgCW=jk@-7)-I-DRcskDJOudMzGOpeod$b$4XizYuc1yo4aF$}mrgxg7WeCV zN(npdODC0Du(hU&-gBgbK<2wsqdMh!$ubjlnew4BgQj9I%feS11DIo9dx+dh#TtVFZo8fCCi3wB z1{)%GSi|#jC*@K*^^WQxT+>qld}@_hi3e;pVYmc_%y;mmX2f^xYY&l|uh`m{*Qa?q zH4abz5a~ZbIy7*s%80vN7m2uu-S)MI$h}moc;>wtUkq9Tlie!%;=@}VVY9G3nZu2d zDqRTR;WmN-;Y@tvRn?X5vMb%ZE<;%)RRYe!*Gb~_MRw99fV=EVM?7T)G^?C29p89W zu4VFig{Dh2O~E|#Gp#~0RP)`dvGTzqH-QdMcxd2oexcT6TX+A4%YK2uFs9B@8`qP+%Z9$}3cTTSsjeJHeKw2s1~*9j(llRajWECabu-;6L{n4uWQ@>dxAxCKbwV zvqe`HXIJLs1n>EGZ2#HLs*BhXRqMG;3wBOkpXFopU%;-C7GFwr)pxSx30KjwMT1 zmKLlmE-4F^S7wtgD9S1=50+I0%Zf`1%7b=EJqlFkrq&4Vx3Lh-T3%XMPyx#o=7frZ z<>jchTyKd(5oky;Dl>DYE{P3ysJ^+np;Ic%$q(kNt|+U7Ra?Vd5ruAPKqoZSwTASl zV%tM)_4Sa1F;LwShOt$9xTCYJwYpigbcJf0+d9M8pocn}His!R8=g=cT*J$vthK5W zb_?<0=MYUvZeCV7Y*$*iPN7FaxC0(;ZfmEAj;7Xzmg-1tBXd<2=adu{(g3R}i%Q`k z*tSE7P>36R>4>!z!Lp+AU`0hiMIl;@QaNSoP_#T)x;l$waS;6wEH5dmpoTTg>$Q@# zZOzTq?eI%x$nDKKhrN&zc3hg&G7ELc^XRTNa!JiAb} zjn%lFir5qGvQ1Xo*wkEylLcnY4HgC~f|bP;Su5#r*(GbqEyoDU$%mL=8Jq+1DJjND z>`>Xz)>hZq)W8C;%fjq}ilPG4+8M1mC&W_`6=~G|*B%b9Z)_ zW;+naGO4P9;2JSVT|4f!*EMyvH&<^8(U=gf>ajD{en3}8qfsQkAU9|?7K3_KFsDLo ztnOefs-?35F^;z16ppA3wQW)Sjgw}o)@Vzpu?Z((c8jvAU~*|Ehq!hd$_5+p1y}4+ zxaArNui((_h%xlQ(W5e0tgl%_Uu0EQl$2|qvBLoPaHPDl zk|GYukR6Ha#=;lj9fcUAEp2t^DEM}yy0$S?XS`w?~@VT05ahZBu&_&fyTjTM?yHBaR8R z^-2p$gAyJG2Ppdvea7>{*zqDugiefK1UXbICS^<^Sz1zBh}fkA`le7Vx-KG~q(@>w zaaC4fL9S}(Xp6Sn27xo?W|ik7Hf?C?Y^rHSlw*|4D=5@cg`OYE#aSx~%d0RyMGyvS zFcuVCL&sC6$102U$g8bx4b_B0tIR9SFkaBV53*VZtf>Db)Zh9g_ue)Ksq<{|2mTvJw15zNlX zQMgmdDWVf@3^u2mf?PC^0kN}sLpW4ZjTr(d2>S&&GW2z{hN3nPK4(wr9G_TeVJJ0q zV4a6xXU725r8|pj16fV1ETv<@;V~~Yb-?9x3_@$+8JxobbV7JWJt$6j;_1|{P-a;4 zD5T_9l&wSasUn7JZm>AN1jf_dXirBQs+*&_1yERzk%HpFf?~8#PnmUWJPXUzt0xq$ ze~MKLLp!2Nv>7vNn|LHfPi_g?RqO;MD9=${S%gU_XV|h5V(EpaR+dx*^_1S(95N;hC*X4ULhu=C+x2 z;hLuE)*0>V8)kAww13)a&Y5xaO_UiZizSwA-u%+avXw!qpH;b5uUFWTiY$a$dp0Xu z8`4ACp8V{Y8#fs2-apzVda0T=IF<2FXNS#dI<9k8MGaV6g`AZUtb}TFQDc4<7C%84 z13lmj)iO9mL2*_#mRbcX6`Z-c!;T!V5LYI8O|N5bT?Ye)J)^a@aeB19I!DiOsDcK~ z&xJqfwdI0&cEy}43k!-6RdTgo(0A@CuxUVs`s(#VOA8%2I>Xf+x`T#Rb~=)UFfAcCLAw^U zxvjRg3G=ia`Sjwwa1G`#Zb%201)ORS%tOu`P-ky{XsT+gMCSk?ZuAV!Tp1zx)1vV84Mc4fEKx8?XK9~Cj6{gkaiKJ;6q8z{ znp1Rpw1ZPcJ=Pd4)$MjV>MpJ*$Sc5lxS*t%TIzYA9B)M(^g!(#O`X^XaS0j1@j^8- z4lbgcg;i&5TL*gHUK-hh1TGccU=M<_yqr0+=AB%cRfaHz2`~q9E|<7)QM4$G9YHO+ zgASpG2g7DI4cQ(Q%mG!HIJgv;ZNpp} z=Gidcc2+Hvo5iTT0fQ_aQsfn8tz2mbg!0PrQf%^+3@uodPiJgs>WD;PHD}3NX|iQ z$|^3Xpk19k3XIYLzhD-+YOt)LFe^J)$fb?2Wpz|hCZiZe)w3DalG^&~>{ZN=hj2#J zj>*F>L>(-Iu|3oKK-5B8>n_Ifs63~vAX__KsFeY{rrOy?+Cc}~wAi(?j(F6R+kf-} z=GqGET1)e>mLNMnSV%Uu(s1+Ij^=v1u+!svha#@XoRciJv?!QWURf3_vR6>Z$_1#NRcl)#dUnG?HXj`DHJM$K zyUvaq)wS!fny}{;XH2tKoOLi7t^)|B1;l6WgK^-Xj~NiA?eznDFXWsmaJw_K3#4zx zcx^5mPw(H$RU?8i#&!tNJZ4tKG7u+hdc@EhoPVRR?Npj%tnuPyrUBW40=tHVhV?PN#8qo;G$UV$?K zj($2A&jlK}!-%#H27i5S!i?yR%A%60U`bw{stbqPCF0V!GF74qiIa8=L!mV|FhX3z zQ3K*vjy~JLfC+cjb~NdoroB*JTLA^4p`S#tKG7}3`JbMzv|8LsV8@G-GOTFrZHJD~ z#r6sGPohosMu`d{iZC)9HBZWzKp1i6pip%!Je4E1BkUY_a?yk7fGu^_{pfdYRk>(} z57M-%8fQ)$u1lDN}j4xh<)YByX3U==%LA3!xv2%p03#hXHab@w;pR-7#YI%6j&PYZot?N0*F+ma z)ipJ2M<%n_9DUpqLvxjb^fnfy?Ae*KW3$)u=+lvgI1roG9%(oI1-z9^#8U%`LQ*SrnQGYCZCmz`Iv)I z!e*M~ z*yp3rzxpMYG3m2n9FqAL4WqM$(W{5iXAGmm!|2vwbaWVf-Y~jv7=1Hn=lMWw-(l$w zGaYWY0J<~%&!D$~=KMhVeb8@%=CgpL|23@qkHcs;9bZ1Q$H-wcAL4U9Oy}Q>Iv>&* z!)QKZ$Oka^EFtS(H7xziVRXYVx^o!4br{Weus9#qf5R~Pu3_|J!)SThxz^r3%JOyS zut8thM|%HZ8?SE$a*evlz7JVf+YrW`dMwYd{AtB;5s^n#gS!LGZ{K8Z46*KvL^e53 zTwvLa9jzAW>=fsGA&JN`h{ zxswDA?nbu`*6iHk9%Se$1|R#-YC!W^9K^RY+O;VPzyTUo>o}}x>R>&M_BqMmDTlso z&ODv1?YQq9si!&ck5Jo)rv$n}uoo)jF}kiq9$4YML2j_x@!$!LUHAyQwz7SR!}4l8 zzoO4KhtiyfUt;Arw}3S7sK*gn!Y%p^43B11eI$(2J+we~vA)p9d%75O)pwJq1g=}P z5l9SwTt??c-*;d?f}`{G==RR)`f#Y8_qg;Gp10?+T3Ma4fFwvexIt_nBKt%Zt!A*kvBQx?Z1-d5SB}77BO*|2Ap&~yW&rXwu+@)A9 zxF$kAkm+|4C*hGe$Z(y6H4kwz9w7pfZ(;dB`KJn25i^iqX#N>2)A>#@*AzU&Dc zSO>G*I3UX{C8E7&5m9b4)1hBCY1H#m(#ZcS(#U@=5%oMnME--4{twcqClPsB4_~cC zTq@WMqP8y?r9-Rpp^`FOO7I9{pUMA++HBK&9$<{#!O z1~Q#5XrEq4f2&mgBcp>>{-y@`9 zr}v1E_lfYoBaL?O?Io^ktUG|Dj}uH2eumJ+LZ2?Ul?c21ln8r2PRzk8)rh%x^%#)# zeM>rsC(uXP>3PIFjC0~j{4pLeA8R^d0oDM5Kd@ggt}~=RI*3?m!tE4a1qm}N14~n6 z*N7yIXafFR)!v5?F(mO9r+DgE(%}+1A55tcrql=(G?oZf3Dya&7izS`!kZ+|U-6N>uBdSXL5wR@S z$j3%Wj}x3KxKJ=pkZ(a`z8b-H!7YN93SJ}lE5UmO9~1nu;9G)U2=c{Vlphe}TbxKQ z5nL-+FL@hRV!;YQ{#iHqXA9N~@-?aC zcL?%bm87=__6S}gI3TF!G32{e=$i!j{sNZ&o!~u!4+!oN#Q!*>^Ksr|e*Uowk&hY^ z-xTBvElGbY_=Vutg8vqDA=WaVN6;^rB6zG|n&3%-(*@@UE)+aPFjsJuARmKfJyn8d z2-XNT3bqPH1UCzA6TDFHQo$<(uNJ&s@D@S7mz4G1A$Y&wp9CKld`9pug0Bj`BlwZv z=Yn4g{vgOVld>M4;Alav$anv;-nRum6#Pu^pMw7uG_hV`{t<$s1XBf15Y&GSg?uxFo+r3O zFk6ssOQpP0!L@>6!HD1`fr(E^f*%R$^*#7p-!q->T_w&E%oeN=tQYJTyjt)# zg1ZHu6MS3nu%H_Yamu#@`DZDl3kA;-Xe}N#^`=oCbh}SBlr`+ zZGx8zUN3mN;BLVe1m6_=TF}J(HOd_$I9YI!;A+7$1=|F-3tlOBli;0#dj$E;O3Hsz z@GHT1Y^=!V8_bAH1Wy&bOz=U$X9eF9Ov2d?%Z(Sz66F0P@=p`oD0rdZF2P#_?-qPi z@Xvy83w|#6qu@xK{ZRfm!Nr0Ff@=jE1bYRq61-XPF2P3x4+y>`_?h4jf{8e5((M(T zC73N(Ay_ZiC3uP8wSvDBd`K`A8(YeqBe+oT6v14fM+lY|cC+SxTeUsq5!rxDXKFJtK(7H(7AH@D~Vu1`%@47Tio^KMUR> zc!%IiMCktx5oa172z^-Se+g|)u+u$6VFEiRxSXw`y>h1T`8SU~9Ou2`x0{{M5HJ98({@B2n?e)l=cbDnd~ zbC$czu*RD=+cZtX`k02(2up?$f0d3&R~TztY+Pg|RV)jBQqp?L)v?Ik;p~{{YCYZU zcL!bZ$Io1c+UY$S%!!Zf^qvCT9bR{5+3{d$d`xHA=YY#9isd>@@4=4Mr`o&wwJk*z zIs!-AzwOs{8%~uqt(m2r*BSlV=P_>4u=aPibo$2_{n~D!3Ep8HvF&g5Yg-K=xF>k9 zbMTtI24!-2C4wijn71vpI2&Kn%l(~a9#k+%k7&0(E=zXuldpzhp z(gB;jhdRASU~-HqyCeU-_E!Uc=(SGgy(Mnr7 zym9Tj`?axQr0U^1??($D+yGsqWsRz-e^p0W9IQ~~P1zUR(~S0wW3p%2pU@jz2vd=j zMoJH%0+vDMqT}Nh9i>@NAIp4Tj4-lTDdfcBAG^Czb_cqyEGFpaK-Zxo!Q<>maBwiC z!+WrG@3gC~_AS~Y=A4K}JyX9u`HE_P_(SWdxxqzW!-Il>)4|ne+TZQhHU=iQ-stKM z#C13=TZ1okEc!Zlup@A~WA&NfsYQEK{*G2R+Ja5?C2XDA8Uv}{y1(GOv(@b|jMQ&~ z-j6zObO%*TP^Io@9jNoPGaX8JHWo5ll`X|id&WT4ai7!WI&&t59NPRGo}e=O%aMFA zQX3tugPGa;IkORQ`>*yD>S@}C!OkJ20X=F|G%YM23wAxiWMWacKm@2wDw0w=Ng)7y@oJ9;ays)EZ9Q6E?K-xdhs$#((O!m;qusR=ZC+ zf**8VZBAVj)11`djkUU(qj`Ai>FA9)Bf10c?{keXf~Q;e#wah6dbj>)4%z+P!F{d_ zW8{9s1y8HkEy|w;2Loq1Cb78SqSNi)`lDKYVgwTRM=>POoLI3x3Nb);GS_`b!MCFNe=n_u6X8A1Fo}`r~3@!cpq>ezS%bine+_aeDa;5YKCKs2L0BtqAb)VTW>>DO*f7f3e85?*D7P1vPT;I?p4u}&| z=;*55-RvjYIh=8!h6pU|%#J#-NXCP%CT3qX^Fo)NXTz26_mrazv%+b3VDRmwTl&4Q z+w!iB&elC@DSTO`1#3u$gp4HIP**bGN_c zPwo8G8CIoK*Mqwe%L(WN6dyW7&a$(_GHB(n4%y zIzTR`=m@kaTSc`arpVwv|FxKdIL1{_a8G9ompuDY2OkQmMQ6WSgjf+ehiVpaj-3od zqeSgg4X~BV8J(-y6?6uVu+!1?dd21Vbg4ba3#^!wdh$(nWOzPnJ+%OJKnJigtIzEB z9+|~rz3;K0{oap=j^P*tQ7u!Az=f&1SwPsgo>coptOjfaHofYzer<25Q#J%AIJSpv z#Rz&|$MV>(?NOB|c9$yAs;KmsY&WTP3zAt*6VjBfp^nwdpUbnJEoSwp(V2zdFaO*5}_le$UK(wdwkQ4ug!=qBW zU{<()&NiDXEw+`Z-9hic6Vo6p<$A}_gQ*5Rb3U?T^kDwhT{A2`G{K-PbQm^)Nb+5G z_df3rsw_4C$SiBMN&D{mX^Q_m3@xa}(1P~a2vIsz+{vQ`8~OkBG5edN&mYjodH&Gz z`^!W+m4Fk(5PYokV!ccOreh6c_-eU~HP1!Kc z8(=!m@6(4$OoT@F)f%I62V_PYMjxvH!-$a>=wM7=)65;f9OsXOx@2hTH^2<*iA8F+ zwv4I!yKHfuu_$90md*hQc$ zGK7q@rAPKlbOOT|#b~CB58Gk4Vst3DkG)1?#5lAyYm^|xi#S#aqlm)B*{TomQd`9! zjt?iE5i^ZfAv*@bag?*U%pK@Aa~g^`#GMR2KOle~$ER=^$6r%$>U8y9f%Gm{Z>OVo z3brv(uBh62ztPK8fY{z8Ok(yLfQ(Ml{mCGe;jRl+;KjJYbvmND&;U+%)Bt#<)7|?` z6z3R^>mq07bu8)qAvo>4Ta^^mhsO0ChLBs^5aM?Aa@5E-)WcqAPkb%8j~EM0d3JJcxrtjEUaE#DhhQjlLS!AW=g^ z92o7R=8Hre9R0)v5QmC5EP5nX$*5r>#zo(Nnnev4F+RE+Z5K5{#Ie!8Ww~)8PKe&^ zgm{VhJPL4(N{Kd5v#5A;j}p_PJD7Kj)F?ALm$8?MI4$~p)IDl~xmi_kX7o-pWmJmE z-L+#>PV^PDD%D)3#M#kTf>CMat4i~n==sb$+5DRl=SJ7Cpcy9DZ^x*-=n8a5)Le6i z5=*0(QOp%_L39Jfc_J>1evo-D7jbd)4vKl^XqC4rdM$h)sz7XB7Ci{P8C7I{sLHJ~ z`fQ+CPoDP-nm;CLCz~N=7hC9A-6BTJY36@UH;60d2MqkE-MWX}aJu!#(91eiuz-k0*Um+MLV?dLWp&qgQ3F0a1c zFf+6_88PSy!^{-l!i;v__yi0Z&tf!sON-mH3|tE~g6qIlU@O=Hwt+Di3+>=G$m_vM z)OiEA6X6@d8zBe5wcssaK|ie5;IAQX0v`aeEAeDw1l|f>4sHfZz%AfaU>8^k-UcoQ zw}Q>!?cj~z9bhZ?GjJfvy%Su9dff$H3;rCeL-^fb6Zi}8S&YbEg118c6?i-NYw&Jx z8+Z?R5BMAKUT_C^ANUsRzaRV?_yG73_#jw_N$EG>gXsV5;M1trLtr+_e;B+E@xKKh zf&55|dw{n%%h&<=kLZy{!Os!@7}x~gf1EP%KLNgt4*eZC3FZ7AL~j{?0FR-)p9I&z zh5ra{2A=|d2|f)z3_b%s1^x-#1MUQeVLo^kOaPw))4=D!>EH|CTyPgy0`3O)!JZev z@385633S1$_JIAtz2I>0WpF&W56lGjgI@3zuo!$5^nrf{Z$>>{12=)MgLi{(fV0qU ze*yEs1Kvz{~i3G zzhS%!=3?4-5Bwe0j`zU_FQrq2>cOq;QxRdk^W=w80`HAxEua(6dVVB z0>)uF_$PP`$~y*Lg=@v*;O~*|1egQ)Q}7b#KM9_P@KfLuDED8W4>R%qf-gb;XW(+M zr6tDmD2Di2a5(H)2R6e`TEX9-U)sP2&`<5)T=>O$uowJh0~kPiZvrVNa4X8~1YbtG+zO_`{>|VB=-&bkM!R-_Q&H}1;7OFT6-gLK{STZbJ!uJhKoIY7^^8!r%U$FEAZ@JlRbU}zjQ0$LcTMno zgEWbr1@MFE~%b4*pTM=JG4#oY((p&dpc3;NuFG^!(`93XvqxE z-(W+g=Ky?ail;BEz09)>mQ3|5LQSW6=0n?b&uN7J#Pe6!Jj3%Zl)KyTTmge#G(0Wn zyO#{lBp9&A@a#ej_Zpr@&@e9>o;;Mb&+u%A8}2te&jYU*p0|Nl4bKVS&xWTPc+K!! z0Lx!DJmY~k3{MvD7sK-l7=OUP-Z~s<#Z!Mo4cPo~M9AP=*G1$MEnr zYfDS4XFF=T7VM4k*MTpihOJ-`>~90(prakU7j;_?Eqls<T4TnKv}1)o7Z9s^6zzAY^-&vDpCehc4Q3;rJMLS{h!I?#{$wt_?8C2inR)Vm#g z0rss2--N!FmVutJXot1nm(aHk90xmF!B?TD4V;etZ3p9FXG_a4&!1F(5Ay_I?>fj; zU@KUw?27X&hMu)8ah|V{ZXK9|dbWc9Mmx5FQE0z*Faz~l51xU28^AQQV@pfC=SB4Y zTJU+;u@2mz^v8R)fo+icz=_+z>8S5|@MHMR2Jj)&Ya=)i^$CI#(QdbZ|3tbD@F|qP z349FtJHeyy=9ZSRo&yM93vPlP>%faud1F1x(GP8qtC6l991gjqWrAlY+HozIk96z6 ziI7`bQaqocz1M@99i!aQ?@~OYMCYiDt_vCs^FQWe=qE_-3mTRf z=8qz7a$isjv0KC~6zdGraEw-|Z+A!k7R_&(4sKwbqwaF+?d$|0uCn2ipePe9lZicOCG5V6zk1N3smq6WQO+{j*J{+fDjHq|~p z1!<Q;fu0$epwK*54fjq3K+HaU^^d&{0=;9yXd?G%=Xf|4lYBWcn5fa*Ltt74+ z#s*#|k;{fRFtSxe9zxa;`%pv?P8PwG;V5LYGGZhu5{DRLcZ8V;;tDZP1}_OLHOw)N$B=Rx!Um&_#;DxXrfnIcZ0Uq5=Y*KtmbHwyQwH;urb=a z0aJ+il{pg%u7OSm=tlgQKQsJG+M0x*F<;S7zZ?y*iQ;X(-Uth(L3IVP(#oOjm`Kc0 zWql{YhW-wEMShfW3MLlFY^FCLkNg3D%=xN@DDUQxM>u54EqV3DPBz;D)olNRq!)k8 zcrC{vYPf#|tiMvl`ydbF2)s&}W)^AV-+@``+IJ0XzYfi9USw+Lg58}sRwLg?jLgB! zhB-u8{xCwuRW1w3jxN{8kKnTAP?Oip&aSUlL)T7L?FQ|rTcBqO)}%wo$!kdJy52Dt zDGbC6eUStGdgUCmAP-0L->9S;DADGd9PD6BU3AJOR?<)!c9xLE4zTstx-hsWL{3UWnS5y{hr6 zA*<5&sm}TpL|yuRlZqW(MZ=-`71goNBQh=%rVXj9#)NS|DZmtDmoyS@(LwHbT7#Ickib1o3&yn&9N1_x=7;n9;;(wi zhEAK5WF!Zgo098lmn7FzRwmb`XHHJ6tE~^LO0205B&R1$Oq!TnTVGihsH)Z}MMz#! z>u-(-F^tM(6-~|6{v@~&CQ5%*RrS)OWxP}BzrL}$8KRaipdORTBo&@4fWUQ zP)o@&DygY!SW;2PtPtud>T7E2mr8Cl3p8WEeeN>-Gq$x(FL!RddFO32u1%ggUH`w( zkuc!O>5hbf-#SJQoZjx9Grgwf*_BhaH0R0HJ8rAWy2HKAJ@hN*T*m@)XO?5^ zKsFb zQ|BATm(KIHI9E<{o;S_8a;YPQ;!*s|6X_ekf8 zUpw1xc1$+!bBr1AtINM}58Uh+02iBK1pG@AGx;~u$jqEH#i(s=NaRW4=w=m=$Pg>W zXT?ZZBJNG>dOn;d)u^a%uJx^&n3SHFI%P8S;@t_pHKCH!HYHBxiEncHn=;3 zG6gxTc!VYfnvun*U9w{0CbCj#s?BsmO*XvQ`B{mnsp&>m zNq%8sMoOkp(NwXdw$i3GO9zD7E2D?%a37>i4jYhRc=HNNeN)mhtuiu=nx^XN<@#@? zt$;ZyIHW(bM+@jSrRfth!}>FgWz|cXs#n_d%+&!QMU#3cniOivbX!YJGAgfcs;#Sw zsB^Xz6jC;Y%4{P}pVF#yn^jYEzf3afpq67mIoqVL*{LbeGex_Yauf6_{8shMqzs*V zvQanLmYe677v^R*8Os}LGZUMP{1V^g74_HD8YRnWm->D4a!ZgxozJUnRzph-A&j)5 zQ8v^XvfvYg`GG*^(MHQ9H5iq->P>l=lhW5FQl12cE+5 zozQ`e0_DEKfx$}7d{KVj^l{%AHq+C z{}O%=n%J=MrM><*h6>>V#u%I@;vlnd%)@a7js-Xt;i$zC5Vi<;qmtpb;P@Gi`-Be* zcYwV9-79=e_!js9j!%VOf{S6pw;;I;{9v%nc=0JnsQ)x5dw1@62sQm=({<`%7)*=Sul;$iojWyt&)A z^yh7G=B{@k6~e6g&BVn>zLh4YZ`2%H{dmFpuoZ{8ds|)W;R50E&*Odmuzpky`os3~ zO0eEue-ysK*&1b)%`2lDZTVR?Kgfcs1;2}A2+rLk`@vxZU{&~oYaxVn8RRG&rcpxl zOvhxgJ+42@zZeJ1a+4Ati&OQn#m6j0 zh{Ur7>SK$KU5pTkw_43${5~AeKaj);?H@++h8e@j3<)Q-j;@F@u0s1F?O>95p(BnI z9fNH;;%quXcHDw&zr|r1MaG2e@15Dxm=hDq+d^P@WQd9!>;MxtRPAhiMcOCnT8sRtFQhZ32r) zzK?*^1a(sh$%-P_sxO0)QGI42DoZ8xyU1*P?k0Jw5@|zD%(OpM@m-1yI7i)x8&zOe-@#{3Uyk->>c`)*rZNFZppd2 z3kN3{a;rXfle~{>Z^Uf~dlLurza!B$2j{GwrE?oj{6?7@H0kb%~A`n+_PSKh#mFb+}3DK||Wq z#Zuk(I+)1U7R8c&97s(_A+c5=HkYTe2b6;Oe3OY8(P~yETLZE|?pFy*_{suR+0<}R zycP#Lifq>BZjyJY?H$FmFRA!0#s5pZi|Hgjea)fKT7q zHl$adyU9*Aa=YbeftLSo(k}uR*FCyNl)Rr)MvOcvuyjyakio+3; zqGF4!Sl)oo!l4=t|=dOt-4~N zhP5ebd>N_4fJRG^ExzuPaD3f4;+MUG_`j%>Np}7=K77B_wIpIg%FrJ{(_U zYl_fRK@0Phs`6h*Qn;X%(&mlaaZN>&8?exG_!V64KUTq}io_G<~v>e;MH2?ahpfT#%6`F-+CK|N4a zk(Cwo4fVB^6?LH~KE@1};A?2a(Rdz1}h$EjX;tEc6w-j$Tinv_8IqJYQ*UzSoDBM19_Z(&AiiiP2QuSl4VcHdQY* z7@u8wWs%ocSXP>oJ14hviZ6eb3NFY(w(PvR2g^_kA8yXsjL*)?DnT5|E6^JAy(J}CbC~`*f5nozYG1?BrRZcMYgSIy zmA+JAnsA~JH?mdyB%5lhol|MEj?OTAzU;E%VsAnAmA;ZI^Jf+2sSHI~Mc!gxd2UYW zTqWn`pa*kj=VoV><`x$CW@jxhVEWSPCKX$5*`my5=cyjdFIKVYTnFfi>0Y;bDZ}dZ zvzn_&weKt#R+N?Pg{8BLv$B1o zL+Ko?S9-J1bt@{GmRC15D=n52Mvh7~dM(wHEL$Q6b-D^xEk{SQJDJtsrCGD`yfXB& zv>|NX(yTn+?0lI3R8ggcd4=U(m}YeZhF{n{Li34b(L~FlvplPyhi8SdVm2r!$;&PE zp^FQPwO^n_X%alq$Ml255ekbUM>V1`9*_cKlW9drvkTfMBu0CL2-+V+fH#B{V5o+L zOuI0}m_5f^nq62hUxixD3U`_qa$X<$k*<607E_bXL~UZEhoxH%6B(?g5ZYt)S9W0; zruZv;xh1nOEE*fcZLBGiGhmO|51B1X$rA4sZ~;8S$E0o~B_+#TjVJyrCeo)ST1JJZ zmO0)6BP*{oG&{(A`(NtI37>gOA{tCB2K2+qK$EYsp)RnZUN zg`8Zh9Grf`!LxIVOG(*DVLY+9(MQ(U(^|Uq=lQpYlJCz>RT-j9NuUsbew-&4(!`hplm7AyDV$#hQs+^kmWDBX4mtytD=1W?v z+_sSLR6CFg)gw=x>TXu2vVbtHEFV0T#e=7^bntYFQKVaSPC;2*cAR=8OL>D{`fYnG zJ=8+IYBfM;hpl|H(cc7ziP#;V-CufhGP}4iU&X1}jemZMv8F=GRk!%E@{4qeuxsZR z%Y3aj1J+WF?E^;iPcda$S9anu+>YxCwS@Xo=0cD`3l2)ghb<@~kv7~(2G_lX{p zdd1+yhMwN7Gy9;nS|+rsm8m4sA9U5ddETPAsJ7nC6nkgqF0hqpd8^()q3Nwj$(vPD zR_x8khFqnVV6|gc0ebIljT<(D<=)mJoi$6Fe0I3@DfouI(&3)MTg-LBSB&c~BY9cF zit6P0+L~qlhPsC2s_G@R74?aY%WIN(?WzAXEV(8z@?F2gMh=kbD%%RmZ8|R?>`iA? zSj{FhTep39p-4^DOPsn=*O$XgCJj((HD`D}>*2LFP4-pG>ax(@_^fhe7L`FuJGm0e zs123t!R6>^SbG@VU31lRrTxOXXlBK%3un&P_T|%Rtk5;HwU;VT zmoG|@>>}}I4U4y=h+Qe(fni*z!?{n3xO}i07d9E3GN4Q$RYPZ&iiYP?naQjX%F&LE zj@`ShX3%?d-?ag(aaeAYoifv7yBcx1j16Suc8-fSYD2&dVxo2Ju5PMGt=V*9r@l^= ziBk(Qb!s8B`_{{&O@W?3BS$ehytp{Gw6OR}Wq6NDm*SeARaPr#;2Wub=6C?tLY}ib&_@u@pYLMRj!^hB$t45 zG-is`m|CMXI74H+M;qjDF2&_oVM%Uy`O!BUxEE84Y2;lYOCvTMYU{#o*JWA#ImI%; z@`ebPW2A22$QvZKDN(mUWChd)M|rEYB3QSwdS1)-s9{NASut*_;98Cgsk&&g3bvY5 z?X|LSwFPHZyJ}S@nPZi&DdV_<ML#;l^EJh|s46G_C)A$@5m_erywn*%GVt3vmndj{7EP<8tX%_d$(*ZI)$Cq6OW!z*^dCLR(A`6Kazd@ZW;(|W39D4)9++VDCa^qo zWx;#7%8HO8`%WivOoVP;l-q6%oP7mfTd!|R(*aeJ%4Kz7vAV3b`=y%xxbQdBRasY_ z{N4d>6rlNL=SIxcvXe*8(PPiP{gH250&M5DHnxU+XmIQLg&Z0yfz|NgZAhp+R`6!F zvOeNAdkU{wl-uh^9!$~0?<^Ie9d)I8R>Dg>y~yh=nBNFZ*SuY0RPl>4zGiFh9O|L7 zrXm(u&NWtsk!^|QsVvYumF1bIvN-b;S2k#Fefw8kbwFRZw9wsl+oXX6y6vQD;j27r zK(MX3twZB*+6pZcR$JKJKwn(S2Czrlp(7&wlaAhVF0dx)h>Im_2JfLTYt}5@tx_BSxwc7sdrb_0*#4O?$#@>p$*~by8!)LqU^F}0&D((LS233&9;?GwxnuD+G8%x zF2;imPOk6{_!9q4Qhz6_zZvRprusX@P@Ul|Qg=nP9<{LzH&5j35_+g$8LFnNyxduM z%H@Y+qjH=VLY^0HA-Gs*s)%sg9y?sQc2GM5`|@n9`Rew+-UQ*=NKVpZ4}8{h$p8L$ zP}MMe#ckEc^8BjmX1xrCT?l8s9Bk^XOC9NK)j+DswySn5wwMCpFO$>hF@gF(b2T^Y z5#5ee8y#bo6@lg7zy4^YY<@dl<8gtgBe*BDsB+ncaMnWb%M!dKZCq)m&IP_mI! z*|1_oH7>uC>KpvkNx1Wq*zCvsRO_+r|C=L_gwKWX5|sMP#9!;D$rxb06M^q48hFzq z^uc0e@V#<|Gd~|g;}sb7Vl8FsnKFL}E%e@nqyvo6IPChK!wU&4i~5+?(wB^L>b3MO zhO!pO)+bI*(m~tvZG-9N>L=tXg%vluN4kgb#sFU?us&A0SqQM(_d4v$#B+YyhxemG z_VEQjD-TYM1*7mD`#H+xt3Y;rt{Zf{tai2PyF~P*Q5imOprI1+vYPc_Sv;;4TItSQ zitlV&i9qUOx;CL@(#-LAImv2F#Kqy@rv-=Iz8Kh71gD^Vc+VnK-z_+&UhC6{LO0n0 zSS~-CaM<-NY~jzsXnlAqBczYtDY0cY&Y;8pV|($yirdj6-S<=R-o6!Si+c#?_Hu`< z4YxDizX+AP+m;8XhI4wjEht;6pToIbUp(|#eoD7ted(VEa9DY8YK(%uBA&>{ihCb2 z&r>A48R>4bUf7p7#vhk+NoGX-6yF}U1Y6t}wsS^bf^_zeRW4jNG=><@bn4r^lGsW| zTE4=l9ryymJ@6Nrcp(nfm-T0x*xbm-tHh5T*)m%CkSyY34|f?~blW4H5iLml_7W)D z1_ClVL$j9F;#4CutkD_Kb4=d{|LIQ)U_u{$YCwHBCQNwx1d%a)K<-&SL&G1Z8X0z( zo*n);4Yqpt<22}j;g3^&E5RZ1+9N-Iyoj$OQZLi< zJ8ag6`rn7#0;j$a=Zxof*{l!a`NawAL%ClM+4g08>y4_Uj4Ajk={fE@stfC+%#_T@ z;iohDT2fy@>htD`rPaQr`1Y&)vQ#ckeYlfZ-@sS6@LkA;db}af#H-8|)hj9+uMa8J zCwPSm&q_mq&05{Lo{0CjSpub%%bKXWo?7)ip|dv7>Pz2z;jR)7p83{ZD4^a7X|8X? z>v;a9TE$sO`P5`3UYZJDee1^Rf=ib^~Oh2vg z8OKHVAutk~fiFoc2A9Ck7~Ue}KUuaa}<71jKuM@@I~RDh5XeUN4#PDD6$iCf@3t+DUkUR zgcBq@Rpb&9c3s8r1pJbO$PFUjEOIC1(fEN&k)NYH7GD(-`7_FxgukJT4U_uOXza;` zV-H0+38em+A}=ISZWY6!=N57_-fbtx<277~e^27oZ`>d~e@u+!#DmN~fim(JkjP&l z;rCJ=gYQQQ_mPSE$7RT)l(Ba^Lt@XxpUh_ZVI<-w2x}#L6`6qk1zGNP$|>j%%BbIK z!ov(lx=%#@M&!Ym;~ZFACy?+fzsUTFL&rq?G!00-FHnZwJ(S@SuM7XfaHJcJxlq+x z*a}kbog!}&Zf7|3@Ww@ApatftAxviO~UJiEy8x;7U8di_X+{?9F);din_m2}cMM zgvmmFQ;z9p2SMxLx?PaF=ku@PP2J@I&D-;b+3{ zgx$j47>laj!a>3jLbZ;dp2;HfyL+nM!a2f1VY!e$Hq3NteF3??P+loqBita|EWA^= zO}Jh7xbSJ=F5!OR0pVfchr(mR&xGFzyM?_mA*uQc2MPJ(y9`edCJQr!GlX-5g~D>7 zPgo;t5Uv!i5pED}7Tzh`CfqK3T==wbmvF!Efbg*JL*X&uXTtA<-NN3OTUGsqgM=f5 z3BqJyhEV;Y8ro-$$c4gkA%9qodTWFY!hrBb;acGaVW)7b@aMv9!Uu(q2!AJhTF9T( zWx0EVuL=(c-x0nm{2$>l;lG4m3BMP13!|{sQGXv{f8ikE#llg-al&NbB;izHmT-x9k18-#0x8-<&NcM7)&w+kN^J}ulO+%G&JJS_ZBcue@2@H=6*us8N^tbae@AmIpM zf-qT_A)FypU%Nwo{wO~6lnZ^r8exNQrEraKgK)F(PT@A;cH!f~r-i$O`-KODhlL*s zj|o2$ekbe}_U1m4^%o8jju0jY`R~IpU50RmaE`E0ST6JlYlIELmBKZ`4Z_XBJB8bX z+l7w{pBC;C?iU^q9u|HmJSO~1_?@s@*gHn*FB~KsAxsb^3p0c>gmZ+2!g8TcSR-r@ zt`x2jZV+x3-YMKB+%9}v__T1BaKG??@UZYh;W6Q7!taFL!rr*XQvEL+Bpe|eE9B43 zGhK;riSRMuo5H`5*t@^v6k*_qBxcr}3HY42dH)R&%&8NjOb7 zPk03hJqtBTqC?rxLV?aB=mF&yCnW@ ziGNu5q=fGgz9Qjoi~OL_Q;OZ#)#EJtIhjjUi$0rNShM&ye`p!ll9{ z5_8Z^A_s*(6W%ZU8}BnfFF(BB0@qi>sUoILMYyXXvMKV{iI^U@gcRe1@xrmf3BnX% zx)8T|RK97#nZg|5Tw$KDNLVUdAY3S1EUXeP6V?eEg?`~G;Z4F8VViKHaFcM0@OI%{ z!e0vS5k4S%NVr4zgz!n>Gs5SDyM=p&uLxfk9uyuD9udAL{786IcwBf&__^?F;c4L+ zAs%_C{@{;+v0v4FCoo3jSm8h+{~1!%|H3$7yl|{=f-psxF3c42w+g9ercm9_f;?B` zJYkWrRJcI6P`FrFC0r(~6E+I@+lMS~mGCBEi?B_&QMgICMR>dLF5xeQ_Xr;lJ|x^B zd_wr7@EPHA!rj8X!dHZ^3l9np36BWh6MiH-Dm*ScCH!3YweYm?jL^Uwz;QK5gNQ-iFV>|Vv_tJKr%)c zD;y{sEF30`6UJNdoL8{797dvybdfVfE){u!$bOMmiF~`rcZvL@$j^v;NaQ0TpB7oo mXDDwV{Tk&DCRx77nIe~pyg+2X$g4!gZ7jpYAB(Y4&i?^f@=9j_ literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/color.o b/obj-i486-linux-gnu-patched/color.o new file mode 100644 index 0000000000000000000000000000000000000000..3c9d7b3fe92feac4d0c63053e957512b56090826 GIT binary patch literal 40464 zcmb7t34B!5_5Xb{6EcqsNr2%I1T^f3>;kd`B+GeXx+L|ZR^r%TccQU*V5JvTG6_ITBT?emzMwcd+&M45c~iCe*gJo@_pyrd(S=h z+;h)e-kX^%p@Lk?vXuL>lvnjoO5NXTQf6ovuZF5LH><|7j(6KX8s8a8?O6F)=aN82 z>_q2Ef5)b8I?ICFyER~}wgo!GGtec16Ly0GI_TJi$2 z#b&U-zcb`--`B_P6R$=E^GL5DPk2Y@*p9XY=IF~5Na>hitlp8>@x<0k6I66dXXx10 z*($bf`+@as^9CWCx-9AQg#JK(w4`R|w60UScqdiqLZVwuM`C-I6?;8ii&`Z2HpYkN zNPlQA*w(c(dXMSn_<|^RYQgB}KxdgTWR@|c$2Ea5CE+O_k09(orEzuUheUD_+dy3r0Vc(Uw5%h z{*EZzd`X(N1O`f3YG>jR2OW=&xxiH{W!q{9&6t<6t%^7*W!r_UB;=eGJ2s@dLE(~;F@OY0q}l&1X#?Cl5cB)xgG;ULnS#$iCGNvF7=jCrF&*|Cn-=e!Y} zwf$hUvoqU2=ZWZmo!h%Q9#7e}fmX-_C-zAvdOp(+Pj*e){^YO=FD_rX4<+toQ{s|7 z{CmgeJ?(A(C=JqL-*i0HvGPPTr!x)pEPzVEl!wFPYudj$8SR_$aQ1|n_7f*#Q(b@F zkv-b2Xh(Lsd+83F&Xp%RArP_dW{#$m$DVL=eE9os+q>h{r5#Vf<`YvM4h8myK7z8U zrX%!rM`>K=%7CPanBLj#c^FqI+g|WsNWg+_JiYsrEa>#@+mWMlk@54CZ6VAVbf@`5 zxYJCajAk=VQnr6XE!sD|t#-1%Q?`$U02!4#)`C8S^pwX!Z%;ee5jw>2Zk+J4p5W2h z2M+i$ve5=IAwUkQx&urFqlb<~$Lv`75#)7*KI&XJwX^IHcpa}DiC_RA;$RHC_bBqK z{cMC}kmw!D=b|Mcz8M9=D6k+=OIoNUGTX$Ram@4KP>32XmC zx}TbJe%_XkO?%s)oH(sZ`wK$AaZGU^|JN3Y0i!Q}_?juFE%fLwAuN{gC`U+qFFZo} z)LG3$sWLy^6;|o&4pdM;$11Hu%}#A0@da(D*pQLbeOo8$qvNy_ zN2P4{0qGw{TY0h8^^lz@+Yck&)a*R^Aoxb^ov2iOc-Q~aV#UaE^cfa8J>HPtA^VqL z??ikGcdiT~^daJRE=k=V;@C!9@?W^}=zUQ2+w*1b{PZW2f6IT(FY#}tj(?l{+dq%a z?Ku8nKhxhj=ta+Dv^xD@h^Loeem~-?6T$*wBSe9?j(<$423x=*+{5bYr z%43grJcrQ&2cxFCA5$KCDdjQDgiqZ;R!zsnzMB2HeJorp=*aamymaVh)pX=~rggQS z{7=g6E`($IaS)pV|KX}mI8Pw>VC~QoO}VmBp3S4WBlZy8G?&7+&Y>L|JCzL$1CBE=Pv(fA|hGmrqqt@hrdRLn|KhLaP*H5x060SgAVEj zjwlwbaNnuo_di3X?FVD8eJdYWWyd%#U4tC$oBT5GM@!H^_+#|El*i5+KW~X&>=-RX zA5LIB9RZniLdQ}bUIJs41!_9-#$%CO(@{Kub1kgnhH=zk@9)@%m~r`&Y=-G>#z{z{ zN9^s)nmFd<$v02h`#*dY?Wdi%dPHxrn{{v1>|ZzmV`Trr@h4BBBRfNwhf=oP!jQwOr{ma;-N#@Z4hF15&Du<6$2*V%MoZb22#Gs(FdGLn+VNEA6I~%onDHG78abUS zk5Ln<5Z_}kYWC=qZSR9^f+(VAc4ubZ_O8ttI(qKx{8rrjaOC!bzxJX;Y$L0suVB^T z8VC}fh+W#bTX*fsV~BIvQ{CB-z0#4L9-YK4iH<|b|JmU7es;eW*Rg(L2fX*_6^IAj zBA>R7u7!JPvmO0}0c1%KD+6d2=(MD%RMB-Pgttd@M|}MSN}=S*qthk6EbDk_DLl0O zql}KwYi3G5hGr^>#`{A@NMVA0r8CQ&PalLVhQ+-^%%^t)b)O+8r}56R*Pw*%3$nR( zXFt3LL{iTzz?qtHpfmK^{?H*@pw`3quR2q=ZtR0u_j&LbnyE1wle!~xgl*gr`l#cw z(Lr3w+K<(pEc5Hd!E!C|Q2VAs{Znq-*M6jL`w45UZ`;A>%+6f50oP)7X9Kno(SXZ< z-3`#I$?gWYg`xpWm3~eFpTG?e)?ZOIi2Kt~(p^emov`gZ(5N~|))m{XF?3&-{w3&b z2UE7cYxtJSU#hkK2p-#6b_8p$=s+&Tl4(uX$?Scdp+gCYTF;SpFsobq!>pQ}z4oDhLUOMe+wa;selt24J2t)AZ+|kQ<25t-_5Omr z$~sQzRp~>llh_~IGw7b7*E-WaoV9aD=pFjxjx4=F)7vju#!LTqgbsIx-oe%@WgF*O z$~}!8!`XzDacb4>}k zH$7l1I-HH}NNd-#gtd8^p3Ar{*b&@;6y?<`|4t89CW&|GydKO5bM%63%R$6PbYG7p zQLb0N`~xzMR-ygUt0~)ljO9i9rjP#P#_>S=rX&BM|LxT44xMj%*Upq}TS51dHUJGf zItbEgxNg-;!D-K6`~*ydKrG{+@^xZR`9`y+Qh&`x969$(47z+ zFF+XyPpx2kUwxXtkc((44X*`N--s1S@{E5qTdLWKX3{} zCXdAhcF0l$5@5KVLP<&ek^)IA+8<26QJ3U^fmTob1H08ppzvUiIz8nF`Ah+w!x;~S zhoR#Ji&W7(t%vL>Ib0M&vW|S(B}E1BNj!&{M-iQ5jlzP-s#di9(Zm+SpTMiqr#Npx~*Zg^<(Y zs)fMmNmdy$ogH6${=gn#GrAMB9eWaHiY6jnQ&&G1K^;tv8lW;$>_ReP2-BVmupso#uAtCl z#2oLA?OJF;C4z+KQM@y&nRWTj`|V?S@&wvXMcv!ncxWNx5r?hCJYubV82B&O~_RHGjv13 z5Fvy1G=#r|(}Ya3H&N73A&1%ZEIUldbo(*}xzmLlZ9hXb&Jc3E{Wn-WAzjFc_EH4! zgptLDTxeIYqN&yb zP3G92pbrwJSp}NRwRxnNFx`4aOI~Cz0Vd3{Ue{!vy@X9T*Sc0`F0j+7Ri1UXCQI#i z*`jV{`i5gbQ-% z6Po*p%N+;qzd$52Z;A(+d2+R8iTc)!Cl9^e=K^hn$1u7Rm)wec{-@w_LI21O_&`!R zO8dtemr_Y5;D`Qk;$TVhF;jbz>iW}L)J|LN%7fIaw+xbD9?vO(EtYzRC%DH}D}Lrm}ZbWQeY%;p(Io7{@4 z0e<`RZ-7a;_-CJClu}7E;J9`=6Fj4Q$f^tZ(LQ_Rt7NW#0s2l1LCt}e!+p~GMy!75 zAUldt*0)|?b7U=XKsH#+2RZgEjOo73Li+7%(el2nRzJ8hnr@e(&c5r!;ZyAo(Vu-c ziKw7`E1J@Gt9VOV@VBsN-z%+dLk$ZSLc6}Z497FvGiq3{1)BBUEqR8Ka~N@>?=8X^ zO3t6D@DGG@8aWq2*}k_6X9zi5uJyfBIBDR(Am<=g3Z1I&JyseTFd&e0*7>kN(g8SV z(nRU_{;lg((j@ZH{QgbNQI#~g$0rApKLSH0Y04S69FQ7_+({AawLp!CNJ6w%fm+vh zxP%SVjnM}6CvlY+s5cS=%JTpk6S$-j1qS&7^Q<>9J{&)?C}%tVSxyPkJL{l#3XgVXp_VaD6;j7K zyC7$r6UG1W&R0l1(|H*+PH@^$>MW-Pc9`hQN7+eEf8?3$B;fxPX9GHSs&feKn&xz( zMbn)#kpFDQfv?VRs-WRaCj&WWIq%^AIZg*OpY5a|&m5;2Hk|7`jZ*WRMrfYl+ysZ8 z?`%aa3!Hr@d#>{cN_8pc-)P?B%6SW#KB1fr6x^qr%_#Y#a>k<(e^Ac*u-jA0IRw%B zl`|1(Pb+66ggm31JE7&X$~gy(cuqM_qFv7`rv;t&f^zzy&KH$)0!DsGIR)s0mz7fk zVSiN4v&eElIlo7>e?moQ<)4*v6Kem9a{hysyrP^(QSMdcl%u}al=BRjuPf)z$nu7A zCPC|i%1J{n9#YQtQTtz&vluPq17+(*jUi5mW)oDx*~ zv2ymI+E0{o9Yh~f&et&aKb3PksN>3+htB#`Ik%v-pDE{0Xv)8oGYj>7uAISuFO+i; zM4wPj3^Kn|&L*_zE9HCz&AwL7Nr?VNIXA$p|5i>VZ2ceQtcRW_mGe*3u+?%tf)bZo z&Rr;Xh2`u8)owY%QPDQbseoCxTh3K5)|Hl12bot{jvqO%wwwWIN{8iKi5jl4oHEqj zX*na&9oJgU{YcwkIa^@5>n!IS2)o{L3Q%q*ibL2g%efD=e+Nvo?*_}kq7{2NCkbue zZ8_ti=XWjVQ!sC`oXgS7n;{e4bBl$xDs`*n%tVX6XE}Y4^ZS zEPE_xK5Dq#QUe#Ex&A=1CkZ`a>j;$MxffX&#yLd=QgxD<4j5Td{tkr${XM)M_y{WU z2ZEkFlpc(r7Z{{3y9+y>LZq0&%b;+gZ#d|b*-#}g*u(2Y-}NxZz%ejJaUjFjW2vco7CSRkZtaI{$k&K1f(xT;D8777&@TuCxh$W+^*s#!t??UQi2K(>%+ z_FbqekR#+U+Y9RjLeltjy9@0Lhm z&J%Kmor=Z<77IDsUP?6zbW=T}GVG)9-oO&iZ=j85)I$3_W-b&m$NnYjEfO*>I2Aq+ zINviB7Saoag5bN%P$C?x6bfKcPA7@J{xtO&?8C692G;`}^m!n#)YAv%w{N6vmWfiz zu4HqU3+Xdmze49Ui-zZ*UdmY3eu0PA1J8iOw7|ulXDRF;yf9Gi*)EQ=m%>&F>9hYq zb5scFx4*;gtrRj~kH?@2R0)|HydQD{)jcf?27gU&iS)EE7}Oq7BOJ{6!L(}3v4L9Q zV9pPwRkdQm6b7dJph{Um$@LyawSmjf*`)!*D_GBdjT$s|o5DlOGo_&R{?=~FI zU~=xF2YgrT?U0jAIX4Ms5IN&HXuc<$AUWyed|x;N$w@)T3*0800p$FSCfy^P{^VRk z{qGb`DmhO<_rQI^Ng-!FgU0>BNhasVG{P^0(~lf(Ap*Y=PJo>MP@e~clLQWiQ2@P^ z=wn|c`d*>$gfVZg66*%bXq!h&i6pdA1$Wb&zY`f~r3#KE=l8-vE0wXtW5Pizv1DTR zb_oZqRKauErpJYYRw`qyCxnAms^Ays(ZD|8pp`1Pmi_RgaL`JX*4$970)G$=TB(97 z>4r}U2dz{=9y12^3#TtRKV}a>l=oCJ(#UvMq!dc|=1!1BJ}F-)_8 zSEUpz?+d<0&Ktsk<$Xbik`D?8miGl8W4rz)99Z6G{NgR)!1BJ}rPTRt;lT1f`&Vq& z-#ugW81mbHq}ktmKrOcwx5=XH4`(z#m8@hKUxz zr>Jkh+dcQG;4O54e!{`rr-Jp=D_J<08B{RHsG1@igfkUvU_(=d16NYPd)Pnyg@fIo z3XWu{0fytj-cJQTAZMWDLCC|pgh~g!#zH=O7ljNG(r*H^BV@q-fIdE0$W(g{Y!OKF zUZt%Yv~w7Vh6tI4)^DO!-lkRkURo>BcPX-_OlE^m^D=edGBzVH#(Mw>gDcupV60bG zOoLlNjnfHq)rS~b#*6uR08k1>iY|Vp_ZE~+^u31vr}+Z&y}YqBlnc29UT$B9)?%&Y zeFv#S+oG6K7HTPK;DcyuT41{O31lDK+@biiw|0kx_isf?b z+c}Wygv_(AV?3!BvcT3;^d&+T4{nOAQ-Re&mfAn2Cp8GU+}5*qqmUQbdJ1b2a+R%T zy=Eb+?X9e+MaVikkz|{Mhz9#XPC!wyRf~NmD_SQ$6}8XcNZa6T)6HKS{D_vkRGbB; zW$Vp6c$shz2-XLi8FMxX2Z3OHFu>l~EF1)a^}!H3Xp3+V2-XLupoYL!;UEyKH*>+| z!ok{SeenD2sVjto(6Byug5A+B9E67TCIDV3t-H)Vlm32{_ZCR^j@oL$B_BW&5`9mj zU5P#hfkfX9{olg@ehw1bkyoEoT56a+g5)lBIR7E;ZAQuir2~ z7E#Vu5U8A|F|aIW9sJhg53`FQ7;K&Vx|EcK(2} zeVy;1nk45U&MC_CH%w{C9U;g}*^lNVXIp2WmVq-NzZ%3Jad2zjg$SM8Vug{30rIwZ z(qo@NvQ1Kb_Kx{JIi>(AC*pI`7lgq`R%60Q!ee~waQM*1KxYUV8C3ot#LY;#dN)+z`EN?cKxl$tppS-AuDKVbJ)_c-9!303 z>6BTZe@(4Q*HiKIK2jP-IO>9|kQ^xiwV=D=W9A8N!oP1>0NG4dqLE z13he=ZKyt46>A0sn3Dn4>G=e;STlKtO|0aGl;A%LJcg#P|PQ!ct zF+rs-gq^KA>ndbb{5PUSS@oJq^nDMqN4|+>TDN)hKu}L0$0)Yp2YSIfiY+jgqv_6a zt;XCyg)Wsskj&7>R|cM!7+V>uQPxI%7&8&Pv28B3ofM^S^ia+HBw2$YkAobiYccc; z$Q&DKZFNgu!aBy34n)o8SX$jKa5#)^2R_7_QPV7ocWn6B;Ml6>2GXpG2M$KIq0a?9 zemC8ImWcqn)S0@fSr*Oa+2xz?E}Y7mt?!|5xT`T187rmDkU0Qhy$dN*PG>XN=8JTj zKLU@M7>WxS-R6sQn+rjn$u=9(vnycKGGr4oYduWi>p-iste;cSzLu4a8ac^733fYc zr7dmUfMYC4xrQ8zoDW`qtWwSS1tq_FsUWe%elkVB2#?_&I%S>-+NS;y4DW^1*p zuLC{d4Vul+cY>adO4Ou!+-}zbCLrkG?u50Txf;cxApb4A=OgW1Xn&^Gezo|7Iupvf zgm1joeYMuzv&(N(Z;-432)+_sVnvMLV-VUO>efT>f^=7KRlH!A5W!Wa3a;)JJOfXt zK=3oV5$TY*6|reIrplgwU4`#z3{r$=0aR*pL|1;>>uru zhWwnl_4qb)3F=|x_B38)2DCiK0OS2)_ROiDmMvXAyLPuIp9px z{p9yhUGJ_V>&{_hWLDmYv-*0j1b^1GLeJiWM7RUyIqeSpw3uZ`#Y^A3-iz#WZUS}E zt44l|3CTL!40|hOB;up4Y`PxnqhJfUYUUMV&8RgPK60tYvdJ*F0%}_`bY*jOaG9wO z2Gp3dnecN{LprWkVakj_ohwJtejGnP)0N!;9*u9PE>c>)p$EY$#{G_>_IjqFh54jk zgecHqwB>Tp6Z8POPwT*sOia_=VQ2)2iS!P{(PYUq-g2quqM?>3Y7AdJHuk%Oq1zzf0kbQ^MHT8yCj0f_`J99d;f0M|N)VIaYaCaTQ8GskR(f&?$jssi_5Rq%7D zrWdBR%B#~gW>}onhe6SaxO%s z{TAVyM!AQ%QfWe)d=2B}=EP04fp`Z9rAe|%CO29v*LX%O}8lj6CPJq|H zL^aw516Am+%sujltXRs-pdCkX{&P7?P{tY^&-tA0Hztmw=Adqmy3hjO`Z~EE{_D@S zlb$?TO^LO&PHCvGoKjm=HKl&W>{*i<>YHNgC)GB^rp%ap_T;mt)HhW%#Hu4Erw~&r z>!WR_a84nnv~4&wbxKoJthFuDwoWOmkeXX3S1Hur7Ok$1)J(2}dMdi1CDMjVG#c#s zW?VvVDCSJ;OU*WCJcrP|@@zfQO`IA<7#tyovVC&S0b!%(A_RqYHSG0Ry+3a6l zf7bS^{g<`x-P`Vs-R3=E`QLfEptTSR-{l#3n*Sy54A0q?cjbBBQIoxq^ZfJu-|>&0 zKY!kQ@5bm8Ugx&gU#MQ|ubnr)?f%)*y^EJ$?w{|y1lm2PJo%RQ!7UlMTJEikdL{<_ zg`P>l*bOJVxtZ}w;Gig@jezj`-h z6nwVAJ2mQE`n11shIiv5KlksQ2zmYsXN ze^amg9zFcvX8$AJ+blF?x@VH*{ln(tp7B9%>lNN7EdNgL?>9&1|JIwd+ya&ymB^-{E9c|k9uYe_TS{09rVl_PRcX zMMO0<<6moJZ3KfHORtDVTk9)h(TJ*St*@<% zns9JR79AiA|G(87FRi)ql1Nol)kBZ<(1ywai~#2Qw%!wzT2kNEhT+`Pn8|8QtT`H~ zR^QG}PGd#WhMvp{5vwBB5KY&$w4q^9w5+A2xs?)d!&cH&TYYU)MKsnLp?dXI718Ea zS|%E6Q_LL}eD2!XZK{ZC&+A3-z3KpxVs-x9aTco13 zst%H?Bb61cYW z($LVn&TR}<0_$)aO)5i*ng+dWzR z5{j<$wI}3W=2hNo)X@%h_czaUVUsi>PDWym+ z!QN?Z-Q3KrI#vHubmPWs52iM^?kuKew46j?79+}1VZt`e zj`@k5hD~@@*hC(QA~)gxA=pR37vgQH^9dq2K-6nXbv{8Pa53Ed64m^~*?3#3m>^l{ z$lWi=8tAF4B(AbxPh}->m2oNF{SpbO#7%fxYAHd~O(U{muyNJ>l2Sq9R=h2>j3A|k z^^{r$u6}hv$m4jke~A0cwV%jiwD|sE-hbeYh7*P&83rfJ(U(gJD-D;h%5ZA|6otI; zwHiq!gesl7tS93s>Y0q^_f)xbDe}h&ze5*a`WnF0(`}Osurl#RD_V#w2<-{1jBFO( zYuE&7bBn7fFVU?2ES#^Zs0?@6!0+($6sIKH>ztVHCnz&5i|#?-@2h zB=oo;cv6F(DCs@E*OQ(am+lTwsE?BpyfMOp#AdwVLIlxZ7?EP*Jd5#hgl=opN5q{9 z+QU!e(PO*~nD<W{HOOR55o>JY;F$Kwsb z&&Xm_6ZRP{;efs@Ch*B@WFQT_}$Gmso4fP0TBl!qt!h@x7hn_h~I-fq0n9S;MJnacsF;&fe2nANP*s)ad&TwyNV z;>(bqI-#{KZcbjiS$XZ|{Sm6~M1JrZh_~swiU~g#Ht|WrChRqm8;B3!4f_!u6*jTU zunGHwO?=g`3DV*QSB)sWx8sf+FM5k*A66~X+jj48-F7jO6^VU@ltAzWg(RA-&x67Dfv!U4l2 zG-}0`x)sD3{dT0jpfjG|liKaKY|!Oe)2NTwZm#`Ao`|0R#$&8;L!|&u8)FI%Al{J(w^sa0&qH%;ie}Q@lHl zvG`Yb!?qgFXF)g=Q40Z|$Wv$Xi8~;M`H2)szAKu1_eI$rU2d0;D6#`_vVC!~1C)J( zk?kWsVq^!1#;QI2?=~Ct`PuFZP!=vmFlxtAiKeyPp2t!nObr1dZ3FFtM8EF0T>+x0 zE!MpjW4U`E4z;BcCB1t_y&dTv;|*CY#F5AYXCf5nVzCw?8xD3)`(rI``@v@OMR0di zx&(?f;EldNDmunF={aCgb+DQMQFG~sB2KcClAj!+) zlQ-(*5<)UhIMq_ZD1BK%SZ25v0QiMS$Z!|n#s2#8O8}+Dc`o(4Pzybuuv`~k#^OKJ z#h0Hx*3rwupLA`Z9qQpzqOB_szkbvDCylx#9#Etx`=I|7La?<7NF$4 z$Th~Vd-AS|%e(3_n5XR--VEU9#E_v2@CS4G8Gx1s*RASFRJ9*(^ejOPRvo8!^~0#F3vV>I zn)nvp$W9Q&t6gaiKwD}YSHUdkMjhi=e}oEDC5}Zw724^dK4O)*_7nBpl{jZ)-ph6R zE{%I|jj>I*SF>Y&B8$b%DsiQJEd70*yp$lN0zIX=J3g*dfTeEIrNRU$73?Y1ZPYF# zKaRJal7aiowV%j)IPpV^dEe6MyEO81P*9tYC|QXt7T21%Qa+acMwePjkWzu3Qr)eI zD-~d=FLbFeK}rRCN`>7{<&J#>-fRtVjJfs`dAlgSHT;wlHb{7VJqG6;xLKqR;(N}V z^u2w}YpK97W4WC7@t*l9Tzx>L?|5r=+<}q4yBU{PpBM7ZTO7}n=54a7`f{AtwMNZh zliCce^pV&3JSc{;KTHeRytJttXMuIb)ZLcCDQkJ8xq$-m z3$qK#azaIg1uJs%OTwkNN7Ps!Wg#9QGDl`XLD90z!f?K-XsfEPSLIpFD9XD)mCey; zb0hPV6=s#?=7vf_Ir)XfWu>aTI?_?b5B~Rq)nIoZyz@@I11P#mXz1svsIiw-wbaS-hw?e^FskNhn;F zrO@i?a;g6#4o zp>P-~g!NrD)LYJ@;IxU{4UW^RhCkM>xiG{1lyxS_eGrY#ax=*C)fT77j> zc~xCRo2I-RX^@AORWwG>H>w3k+|5n6A<($KysDwOEy7B&;4y`vWxQOHxm>luisk$i zd^s&lZf<56mMkt`WK{ zHqFmn!R%QjnfV0;q1=-EP+<-f0t?+yP*k`mKPTMX)fnnXSXPo*Oq8C^MKyW7LrQsm zQTe)79LJYOpm8!ptQh+yKDsPE}P`fhXyWvuPt$)#27bD-QQj zNlvIBR2nKPEX`aLAIscZAr;lt-Qz>MjJfrKf?*8L>^#&IDuL6`PgHGlb2aW=P%I2J zJ1f6*Nj|jb32be#%1g?5vsFdwv{$x7BCC129~U0O^&2Br zvn-K@=9Y*mMYWkZ`o6CSLgQmi@cGqfCPr&Z!-jHvNECXQtRD! z<_NO2GLLaN4t!Ee^FzzTFx4$Eesz6Y3*u0@2v@ulqUa_Z4aTYS@^eDQAcz3xg|bW4 zx{6lTq8i(35hvLt8!#l-RyD_P&!{_gonKZ|3gcB#5lGURRa307ysjR1;Z376m!eC= z6pRhp|Da|b*a%X%qA$Rumq`Q%hoc9Yh)T?plaFvx>JCnF^sv)|I8>;wapS2nR?G0; zot#-#S`^l3&31RHOs}PG-Lq%J(JX!(QZ;947H?^VOs`{3C-g&FTa|lfwgSbhD zlEwMOAqk<~Lzvx%ZsTJLCN9fl(}uB);D=ITH-;cBq^P(6v5l8z80Hr)%`C{z>FF{A zqR?{O!fTGTn1;hEb27tuh-GW*+v+P}y*3WC-24JPtLUjDEM8k$5MDY>4{3A1wY#se*hc%sQbD)(Qr((9L=}(o-;F2RzulXV|7nLW@Gni!ot0Mff?Ojdjg#RF93yQNYa`{A6_{7hILy|1 zqSlk2t_0IaezwGtu&#AcvEjif74A${;pQfL7&UOQz()`nE!BG6r&V>PYss1}#c39d z1Vp6z)}C&ozqLkcu&~j=c70C@XE^sxEv7)+&Q;~>5bVs9!NwGDT1Ue$%5y@6c||a{ z?te4u;Z7=U>>?R`p@&m`p=qR^oWYmLT+drvdljliP9D|GSXp3V#vNotifH}X2o^B( zXcWO9%PB&*EOaB9Sr!zQEy28(%^dVw9X*u90W6F0K(1?KabXVK{BTYvH?yojJ9TDw zG5ZY<&u|1(BQC;SFqZVtZ@{wxSd-OPSHUN{V-(#EGf@u%(Y&YxH5HbI3f=WeQ6W}n zC3^OC^FztfyrPn#vPF5}60LJ#CQ6zm7!tz>Y&w?VMtFS{g0h~s+FB~A@aO_oCp{Hn zgcW9%mLZInx5;Xb0gklmVVtX@trbme4VY1ApJkc(Sop3`k@YS0yu;24SA?~sf^b$r zQTAd4m)!bDLv(Q-aVi4JI8uWtvXV1!bfdb5JE%_ zYRt>TS}g>Npo`pLUjh%xFU-ussxW_%!a%5KHDL>8;u=ctOXwE}I*e3iDs5`!yiBUN6rWC>{V@cfV4C=K3JxXgQGuUPXiMN95Q#fz}FLg?ZgSzX^Mn=8G9)JFjN$~__A#Mp-E zk;@P+dfLkM;RV7>wQ2e(-cK*m%Wh~6_ts0D&~l9NMTKSQ+3EV>&A7m(SNc>74uVNb zFRZW{YK4oN=@AZ_h0Qv90jpQ7K}Cb^I=%4WvKtS6VPb3RUi0!vO+ATVMTVtIW?baP z7Ig`hXtZj0F{XiXuDr0Z8JfFIF&P_bSF+fVNdNx4I8kp+YW|wUabN zYIIkZ3}~@8I;gR283#f-Ecvn5q|N*jZuz zMZAq-`wMkAA%(EySpiv95zNOh$|-KFg=p(>9^?4OJcxqm=x|=qva-UmFvFK(fW_)k zpMgLKTgoNxlB}ZT;rt6i6kp#`uAji-lHW8G&#Uo4JxjL>mY%I5?luMMX|9sZrmyD!3mR}8QydB{W+8o@iOFy&W>6YoZb)>6)(w0Erp9H2~%#SZ1^S7 zjl?{!sc!1&&bWd2+yo;-B8{d)83tna|YPFxKw9gdN#spW?_CQO^lfD zZUE`(p_0;q%&d@hec6SUmPkYhhYR!^jP}zvV~P;g}cL-B`dJHS5>VIdS;htkSmtb6*%02Wb8;#OgGdVahZLL zK6GePdPL#0qC}x9yCaE??E2p+F-|5!nF~32(H5~r-7Q%4l%a*_90ZUE7XMgEnu^`+ zscy`YP-YklI=x2fUN^ap*3B?06qQw!v%vM924W(Q*_J&x4VzrCYo|@XqT78lj z#cqO1$Wh^RG*Lew4|mmb7sjaxp*UG9z__PBmt*IlBP`b-Fdd$6)yG=p2ryXna{b$_ z7os}OqWGMrp853Cu+)hgXA|(T*r1kj2&p}m=R9%4K_BhwBQj>Brz|O28Y;@o#r7l8 zB8LX-PKkNYU1GF}l_<0fhl3b7I6A`c>{d=YNVe>JdFEKneQ#B3y*@KATb1RdtQ6#t^I#s;T@$OvPE)i)z+%uj#rfq}91+X3tY@)u%G_99QH62An1NyL zHb>?KNO!kna5ox|8ls!=jhFeS>jBZd8Vv&)a14ejnD}gZ8ccuUbRLVChNnB z$-L5Gc5-D~o0_b5qvaKqm28qpKO^M{{ikx|u~Of7;|}r;;<`bJy_9+Z7H+ zj!$ceRWg#JZmo*04QJ$-L%P*Dl|pT5GENosGvJdkU?P*T#G8a&I8Mm_KVG;|h8uzS z;JlPs2>b=^!nrTp^3gAR7E9p)mF`#i7JPOr0iW3ihvj)!iud==6dF(TnHQdF(7(DM zWV#^ka-AaY*fxH5q>;z6uDmI@rd(HEDn10({UC(o1E?8zQxEsWeEfK_`*PEA!Empc z_Gbv=y+!xsre%Q<-`>}@;{n{kMnB$ObM@oRP`3`XF97X%Q6BSc6LeFa58=B#B74hZ~jK_G$25K z9>W6;$2D(*)2}S(R{*4aT$<1Rq(bdhAoDi>cY@|;El6(#&DW3cru?gbd|r#6hhX{* zp!wL)LX;tWH)w>wZuz+EetGrC>LwvAZXki})tbep(}R0nUM)GEM$n6Uc@+Xy+{>#R zJ&s%!+r8fHOe*)bX>;HEz+KwCCOdr^b9@UGU(u?M&5!@Hc7xto8^`h%~ z(a~Nsf2YiSQQi*F>A+&V`>W$8Z|aqPTQB-v(6pVg-|>?V^`al|mH*E|yY_zTl>7;b zU$Wx9sLwZ`S7Dg&b3?Q*zxJdnjvfx${mc;4CxUigEN@Od@O+2a%IUq0eoDg7dXHny z3T4j~&)4TWny=6C%6e`L>s?6iwfcWM-H}@Yr`(;7+rpSVmaanIst$8wtDja&VY3vMB`R^irH6>iK_SJg)FFbwX@f!S2mvO%>qwcyc-XiZPvCO0#(;Jn{G z8F24>>S`cG-*BqjpidsKfi?TSw%*&3_**)9J*{u-)<~Ug6*ZA^+5`KOT8+|3{lJb% z(HyNU^mhriMK{0abjjU#iG;Yvz)s;9(`lC8N6LQH+_5s-4y_eFoyx^|eUpBG2nTlE zRf{QgE*^~|*D2@PI-?wJ>+^0?)ZKpZ82~m{qZWe3;V}f03m?J6VIX^edCUhvbwl-o zV{+ELj(bbqi|p|LI9YWZX>MklkE6Ohqcgkb$(rbXhDxi!+dXVdoVoN?IgYNuoguat>x>64kN0_xL^Zku9@^NiL`aePsM;s(Q7RdAk zLN5}Uah~aQLT?uO8q(?bFbQ!ao?8?CQPQK#NAg*&AL0b*vxuXyhXh(Q#iO-E zFMkRY>EkdjkVZMiH_HDpaXj`II2r9BViR?N z@GAu`Bc7?$Z;8<7Ng&(%B5AbuebUhXpQNYq`@BHIF6RQ-?m8mM@hdHu4?mKrJXma9 zMS41ZWKZxf#IfjS;@L{QBlO%vQ+_FsA;YG5L`D7HQP;0cqIj zGa~HM2Qp}%0YKWPf;b+}CX$bGR}=BRUT_Z)`5zMcEX>KY=NiGwi09zRV4>dtdS+vf zDzpb>nSTb*GY9Jw(i8ABC=vP;5RuOBV`V+7@TOkBB0~Rz#JO0bCjrkyIpQqnNt}oF z0;%tQ((s$-NoU|QVx;GzodMtirA7g1*J{$|Dz%lk5c?$}_AbwKjJM;iTnE*`fgzmAVxqu-t(4LN@yosFM>5dMeckB9w*&!wxCgS8RR6T(Le zNJH*fq|uLAM6{!teE8WK(&O+s2jXb_um$UkVU{rL_3o;=jk-|%M>^YMKn#PjfJEF%4x2zxwB zM1Ai8S^vLDL%*Z}hMx-bEXEhTk%m4)iAWzI>1PRjj-)RmLZ6L9$lpoyp#Oo??+xJ} z6TUsr@FxN(pFccAzsw;Gy;cxWUlkGdY9u1xI>E~YI|X+O?h)Jz^b{%mqF(sZ`oT;Z zx%DMKT@Wg2da58)(ey&WJi%hY<$|jO>jYZ_*9&eHyjpOl;LU&+Eclw>VZkGU z#{^FZV(F*#>_Zwc4#PuPIOIZiYUECeG|vs#AKc3m;lj#F#JnWwXA5E|>-?F5d4e=0 zANlZwPX}W%(0=iLf1MM{tbb48d%{62S_=7QwB8 zR|(!Ac!%J9f?o^v^P2k71V;&SA5T5z3oaI1Ay_N8UT~-2_XHml+$VTg@MA$Q#vbJ- z3l0$+E6879V0w;VSg=xXjo?jm!+{FUGz1YZ?AD)_Y^f1!`{=#T#bmkYgGaD(7g zg8Hjfk?$^{e=W$L8KNA$J^(%|G|zs?e?{<+;M;;n1V0x1Ozje3`SmbXP zyjJiA!CM9I5d4wgeS!}O{!Z{o!RG`I2)-_OSnz$pj|KlF_>G{~Z}jRb*k3SB@C?DR zf|CSi2+kAC63iDY7F;ICACF=CBZ3WrZGsyGFBjD7Rpi&}Rp57p{{z9h1b-^Xug|3X z-w5&yiu8WL7X|+!cu4T?f*%O-W85rvLhz(uAFg}B?5DWzZKjk_^jX`1z!_9Ecg$> zZv+Qm{Z9Q(7vxt>lP(ji737x`k=-H6-|9-(g3%)1FpAKYt-&BLc1SbnF6x91CD#y`m?r3|C!Lg z7kpXpZNbk3`*1&m{Aq&Y1ZN3`1WN_01X~3!7u+ehM^Nv>AoqEp4+`?vs#u@?95T?) zeG+i6;8;QaGA;Qzf)@zZ2yPba6#RkUeS(h*{z>p%!7l{4FQfdSf)fPi2=Zs+n7&M~ zM({Gh>jZBV+$Z?Dpo5!8ET1h{CRi(Yli)pq{N-Wh|BK+;f+q!&vB6>baKVX!^90Wm zTp?H|xK8j&!QFy)2|gkCN5R8_p9u1oEm`j{!LtPC3g!zg7pxUrE4W?oMnV3(59R$@ z@L55A=|A}&3-VSN=>dYH1!oC{1aBAQuOBjhm*7)^&kG(9d`<9gg6|0OH-T9GnBeDv z-w1lrOu8)?6igSKB$y$%SdhP=O}X`g>jke8{I1~Lf)5Dp6FeaJmf$hLlY+_E@KXM8 z!HI(N1kV#(Ay_B4PVh>>-GX-s{z~u(!2^Qt3w|!>;KnuUA1OFRaDm_w!HWb}3vLv= zR&bZ#PX&J=_^{yb1osI(BlwcwUjz>dz9sm+;6DUE75q~0q+kNtz;+}F_7@y1I9za) z-~_>J!Se+-2wo-leZhMLeW=eXgV3puz!E1<+w~L5! zy9IBN^q&acM?}8g2>r6qhlnV5SnwT5KOxu$_d=*=5)tJcp(hAEQ|P%u=Lv>|UnN*4 z{5GN26XCm83VofV-%5l&w+a4G()UaH`+}cJ`WJ#<6QO5%y3uo?;9?@=6$yrk$QKc8 z6Wl7eL+}P7+PjB{@^=c}E9s94J|p-d5&2&i`iS5cg5OAb;s{g!V8LNTlp81XIf5BP z)VolyQ24b%uNGVPZ(IO+>lbg1LfA1urB* zUX9SJgBz-;6hwsT0xE3kdsQ*?^y9GT&=UdbZFRM9>!ry-MhlqBSI_I zi~9J*u9QDa=yaj=FBBntq0kpe`YNHf3cXEeKF>pWKN9+Bq4~o-l#gRIW#ONT*yd>d F{{d5$YWn~H literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/commands.o b/obj-i486-linux-gnu-patched/commands.o new file mode 100644 index 0000000000000000000000000000000000000000..b75869c4e5399680a4a8a8d13bb70f791e4dc9a6 GIT binary patch literal 56068 zcmeEvd3;pW+5fq7C*%$@!z5(5L`4mIKnMg;S;CTKfIv30u&EtGG9i&{CNl^sn@N;3 zMM0~zudPcreXUCutJbY3R@Cll)mGc$S|hZ@rD&@yzwh^)b0;?geShyCzdwKTVdmWD zIp;j*+0JvGbMC!iN2F|-VHm>s7{U}okPu({FI6*F7P(@aIK^oy%eww|dX8k@!Rv!1 zlf1I@PD)4FUoy!$K8A?r4(!=1_B=L~*Rp+X|3x47ALvhfnt!Z++vokSH0`p47wx^0 zPQQ23d!HXaete*K#tFE-{rykI=L}@#9~&qx=r2EtF)fnq4^LuS*{^SZVtmsszwqvf z9Cc{*A04>ptO9zUV4uroqP@Fpu*n6zd$cewJ`X>H3P=biUUXp3gQSaIL_JH?;Qi=)IJnpSQT*;YGGip$1_p|(gWgGDbabgF z)O!XDwP(-A|2lqLDiGtcx<8;59|=6u_Yr7|(1UBM2CBTr4unE|)o3*!`u2x-c0uT z;&4bb&gLK}sZo|0x|D;H7->*WX#FhIIS%RDDfJ~1Q+GX0(Lhp_FG9N2o343JOBmvmuY`TQ`o5Qg;4KZ7<`~S5PEQ3l{DFM4`72PTZAjh z2!l|=ke$pXO-2V8rlUPK(r{?!9gx;Yx<*}~slV^9s5^;gDUU)^s!&Sae{djTar`n9 zoS<*t@z9O?`=1FtxV~zL?a8Q={N7I&D-S4^zd@!>=3i_yjM=81$H|ch_3cmur~s+h zg7i@De-jr`Lq8dMuP-&TA0KjWOzAV^^jq4uKOR1~w1D=-!26dDbaw1>v+1Whwnh>A&*2hO%|W}UTy04xE*t|cz7Hg^3~7akTUKJ^V1(-EN6bY{kI&x zrQ#R8D-9G-dRMdbPQtI64g=2oqeCBmac~uTUFscth@N@0cmLi!m=}mL0Ea9)h~5Ko zHK9B=9)-P+6`r4y=x~p;D`lkqXQT~I2!ZZCWJ`0`e?U3yg|K6M5+~nrIgqx|;Db6| zI)Zf#byXdoIeZ@-ln~S-{&CSNpJx{ zJxIb>J_nDZ#Us)vzro^|bm;zHGDbVj-ghVJdY?lyWt)?Rf4A%lh6EUrox$A8900S} zI$`#Q9xOV4|9fdYM-5CL&hz0ddOkfKzY_ZD+b>tw(3hWj^3Al+gN5gFmh>F@lkeBN z3(p@kz@3t%0uDA%2RHT558;J_<n!nhcg ze+)#zNIV9%SxiI{pTazSk3ts%k?j0qk1~W~{w4tVBjHdVWAh#OivA0++QlaY5Z^5+ zdL-b?X5=LY5_1P486H8Vfap z<500z(mWZTezbG*c`OYPMIbs&a5!=ILKUU7GE;gDa=D@U2bLE!Js~_zk6PxC&O&`R z)9;rjBkElcem&>|^#sj;*5E>?46JNM`@uKxvscF-mG3;tiLvX**JOy!K1gn$K)LdK z#vm^3(rdv6@DG|OhD-A6OywV=gF8m;xiJ7XVDJEE0a|)@q6M-{IUf;N`!LCv2f=yw z{Af3P7A{PJvKf}m{sU6847=#}r=C9>ju_yJ^yCbi%catiG+j6~MkHG?feK1Tc2Amp zfP&1wBtb4gn#rF1(ASM%@nJ}EeAm-dj!Zjbe8mjF%9KB_Er2Dt_m_%(QXMZ4c7^Og zrm3o5BEZG)rzssqP@nD&kD>$Z4z80_Z%?Iq6B|7s^JS^6fh}eIeLJDdzT?}c4Xjw2 z|H43L?tn2c?&@R3NS#B6x9%PA?$cnRwdW~g{y(q$OaAfv*OU$95~AjVd)y!xR~BO^K#-DJ=-i} zpf3BA{huH?$n5v*e4NgN3 zhATIf_oR~JA-I7*l7aOl)OR)~kKE6YyfZOoa2S_ibv| zgnC~FYR}`l!2?4ixns<5joaIaaWQ3>uq*&&3_nnpA;SzpCFUk_8&G3(wH!a@bp0XP zh93I*=UOKm+Sy|C95$MIJ~KjBe*;LV_Wb=^Fa0#v=3)MKGg=Ij<-p*ZSREW~QZ#q< zGik>;(BQq4$F-23$^eCB9&9p8!1R;4U|QzPaV&$O-d-$6Wd42h-#b{3Uf}0g8blE} zdqaJrr2IdhA9;!MBy=q^oc_oWHwPFM+s!?ZBQ&3sZIFY@c*;00@?RS$$E3qQOhuHCnHO%#MbX+_X2;I~y4ISGG|3 zU|$YfcqeK4l6BhI2Q&pATHkAS9r+f7+Y|Ye;xgPuJ_VdyM-cZ4_k4W|6!}aaf9WFu z*#P3wX?L=*7Ha@hIJLc#7QtR5sLnKYJC3G~mf^i1F9lz7kASx_z~q?Ce`+spqao$zocsS|MO^1y97AD07!dUvAH z9r&u2D0|+Msj0*{J%$19;fGhiz@+4upL$n0l{X%6_uBO|8^Zot|B?zk>(5DULCK+_ zIejMb8RBd;^pxz)^Cg_0IqFgAXy~DHBo8t}MU{7*Fq?9r-@ z7)c_DN9A-s{D7RldOV*ve4`sS#o<0TY>B}x=|{T#2r;<94X24g>JQ^7{=H(b z$PK59!8vYtlo({bnr!b8gQEc>a16zZo+CVu%zq7Mdx=k<;E4_oB@g!39gR;6Jt!0E zoCdgJa=b^sMShw94#z`v3$RJ5_peE@LL|%2MV(@3S zR3kCQeg+4dfk^}9FTHmgV)KCO5LO5K{>bYCk=Os@)Iwd)(*-hBZQAShyGCO;SI*c6 zBd?EBZxgRpH!hT+YrhOc{%eN=&N|u42LHQtQk^~&EgcBlJWzx+b+`M_ z*%@SL#SJ|qv_9k4JDidwCUmN`;$er3r)po)dwQ}`F6^Oej{%W?3=)D*fwhJQ!wBwc>`d$TjEr7xLY0!?S2S-mCAA7U|m_?YdbOyZ&%|feQxiRKHyg3 zyC+lPa9zk_eYY;|$4ZARs_%u9=|VAZ_*yltOEXR;t3_qX_!lTu+kEg?AU>mC%#Y&=~NIDkOuLw9vVMuDz!+04WR^t{acq+`G?q@nGi zCJ*hg6x$W6=Z&2H->WHWz4rs$j7d`JKjy5D`TP6d`LRHAx}7uiGN?)gzGG$#3Ci=F7iEe`mVxMw1V+4Dat1L~KQ z1@6Ac1V^tYp$EtC-09d;8S&9QZ~kq!gmC(K(31nSN}b8LNM!DMn!KyKFDl+(1#~S@ zjC)5zy$^zCM5{g9j!4FUlY7+US{&N_0GN5EPf`WT@^lYmaOsuYA(w`Lva>!cx*2B-SZx^ z%3=4Zz>+#CLX+eGT8DtGn-q&)Ny1sH)kcJ>muzCrtNg-sbJgKN<^})P+#CC5B@GV& zz74`0n#m|xx-CU3Fv9T{T}B(04@^hn!8_Et0Fk9^x12V&^*d8q4mMM_DxSL4^+0O7 z)fn8};I-5S=a4%&-<e) z>_0I{%2IA$BG@^(h4e-DWKBBfPO9CNj3ZO;e+u{fkEe(F7K6T%{Pykw@Mswo-uEy@ z!-Y8Zv=N^&uzcRYQZE+R5u6Y6~d zc-cr%!ifMbsidNY1DDxhE!Gw?i?* z!V80%<1c!C(Zgy6Zj{7dh?kQ1K27`|(C1wq-7cPYBK@N$qp#cVse3km|3P^UEAR+G z&!^d4A1FO<`+0xlS)R8lM}^g`A{qjb$<6Gpr#V%Jo>%y_>v@G11`!n>LJvK4mk}?N z-hVMP=4iNYznb@<-t&Nk(2tfOWa^oPE2-JRuaS_94|ieq%tOnR2{?G46R)H{L0~cX zT|_6f55P%!sP}Eg%oC#DLe3i%b5*>h?gzFV!G7hG;hy92nB>%zUGn$4bbu3DOgxAKW^SY%p~E1TD3!?jVpsU#RBrn2U@6j+`n2NGv@itaf(1(bUTsIb3aW6t<uDlJw*rDmnq(R;}A?xs0$@*WwlUr_FGaq7v zk@}IjOba@J!r;G<{toF$?=Nw_{6nR`6Yay)*G(Pl9Dgx?|KP7caQMEV^+Zd`@so$8Ci^PZ)PFtmntc+YfGo6!M%+-F8ny3{&&X$#585_haxA`-d^! z;3B90iS^H(l%HOz4gPmx`?V?BP)^0LBQ=O6p3A0IiQ_NBoCr$31ma40)N?B5LFY=I z6UQqc|J(E;1PTBD$E^V))0jLe%WsZ4ZB(W)+Q=9ogvS=RHV{Mv*zKEgOLtpA^f@qy;u`4jM6Oj z2#yz}S+hWL)D&D`#n4?qL5Pf@PJVyTAMmqlCXkk5m*D6uV`%)WBs*y&9v)(6sQ(zR ztAm{jhR5MhYOKb}e%X2mEygKB;1HQp$0{N*hot`FzIz#g)+n$+) zAq%ix%02;rtfe9*=7}W%r!noe6n2|5)W0-KAu06aAu1lU znleO(;MBRvF$m`78AF8KRHnHrhKNshb%*lL0;rkv0G#0hL42kk-Zt7GQ+a-)4wzZe z+KAV)PdDPD>fuLF>uCi2l{&QNb5&K?qOX!N-*(JLX>o|l=>o8I&)WIm>0J&3_gPkIj0 zS|G1QU(*iuh7KnO>1e7L&UV`X+T=(TktryXXhEXo>vb_oUAgFmGn~v~$&S$G{5%8SJG45uEbT1VG$+(_- zg3yCEe;zPa3t0ZLcjl)U%*W@I(lQKE^-L7LF7!?tW8|QjXQJ14AzG%{8nk?4ae$OI zR)YcGqXe@xnBgl!c9M3A2E#riMI!A~4QBhE1ruqfX>goxIs1;&V2-Z>u`KNj4NmfH zARA|DFxU5G#MQJM4bJerX9JvIoQoyWGjX~qbT2(2KnI~X!GB^1V(AkS+w5Sc0^1H?6x)VAhNF3wNzT%}lB5Yo z98E2Y;?^a?8h zJU*_wAyLScUz z^k6O8E1_&ZcZk;FTO>5j|6`6&q(;c`(^^)E8X?zz3AA99D#On3Z)3kzBO#Gz;#~h* z5W%V(BcXZzmpIlIYxpF%#{zAr~#E3Cg^GKYN=CZ<8y zwHVGfMa?z)EV<*qVK*mbeO`i>tUgJ#9#EgtNtUgO2 z&Hw_Yqc%NWHk`>z>!(m&VC2|MAd$H#wpEPGrlo0(AVSv2QWi!u2It>;P zG1?k=#!V>wt3YYwnTjdl{}N{Q$Q)K6WT2_+6oGsrCtONo7#`xE5doW7H$Xu-{+Mwm zrmXJ?1Q&mcyk_Wm8{Xh=HQ0`!=X`jBze9tT?M+x|D!K+2Lkr)PJ>+RMfce4shq+r!bz=Jrl=;uL5WO8+Ds;#2m-~=BpZW z8Zq%&Ej|1+)I!HRcpzI?3lZH6|MvDC9h}3gtk}{_hw+fB>TdfwK-n1O5Qm z2+Yui&+OVF0yBw+_?hh;aS_PVb_b1niT?`(3C#L2E=OksV~Y?5q}75=j_({oRdA!@ zJEy@_gUyqrLM{JK(K*JA8DUL!`ltG4%icL9kf4(ACI!X0m31BEr!hiukcqpj5##g zeiMDO>@i?AY(I|cG4_R+y|z6AeaG7Kah+{H4|ASk`!V9F_C&CMn$4$;#@PnAI^Avn z<_x-wPh{>}x<_mi-f4&$c(TZpPuSnZk73^k^?Ph)xu(4zm0r7*iGuw+lsCeT z!uaX-U69POe*#{8b{Etz(mueDV!r^M0`?1_5VUsyGs<2G${~9`bdX`U;WyLfnd4~t zN${Fwr-547{vD`|v44T7XWJjcm}BjyK{MMfg33>^!8Tkb0hv#;=b-&K`!7J9Zb!k} z8TP#x@l4wSCda-3G{@WTf~yI34X!8JpM&xw`>)X2WIF?xDfT?jnQEVg-(1@diKf|q zgYKr=UqY|5>>`+YhP_U@%vCUKp1m2rvuwWLGutl2b-sNTB${Kt2MTA~=O84`wfn*0 zIrcA6d#=3~`19;Ra6Zp|71#6a0Cc^;?m@4G_Wj_qz%GW2i|oH)l*KkrDVEshqvd{K z{|e$gDeSL<)2D3i_C(n01z}%~VP6#X4nQvn zy9lHIR@k@04_+4b+c3^6!ajoWUKMsJkiQf57t!SR!hRpcYr;MZ=3f_fH%9-1u>SyU z{888|(eF>f9*ZW2gncX2@&<;5{BNQkjQp0c{{mj#7WOQd^BrOPz|y-QhT_k{u7ZW$ z6LuI>2H~He@;(?u_rt;tpx+T_0?z#xVb8>{e--w6DDrQ@&V^ST74|jI*$2X20O&(u zuZFQcf+$eI$HKlAYW=&gKY-B3gnb?a`$X8;ApNPZYe4fK!d?RJ`KPe&181KJ`$>@g zT-e`+TK^^No1yD}3;Vyp*>PbHfZd&jZNMtK40}8JU1iw4V5!Hj6CmAd*x!O$`wV+I zv~;y${}L^)G3?(1+HKfjh|+J^Gcm#!4f`C7K492SL&;w@(~R$alSAZ-jg|81@V3_hk$OSG&=$F9e@A8TS1U^DBnk2|jN&>>t3{ zziQZMDE`Z^7eb<240|zJe$B80u*%mB`yz~Rt6~2IO>P78K;CYMtX7C?1xI=4(>|sr z!H_2h{g^E<6AEU?DwTCGvV?AhnuD1hUT6Id16jearxd-jv9<=s$jfAB+f#`e)%gQ3 zm+n0SaOj^MxHA*xFXyN9|)fBnGFree6%cFPR6P=1_@~yRLZO+ z-8-79u7NFsH6AWbSrxEnAh_C-4o~pSr5V>~riAbNaNpos4SJR7*U6SDH~l%-3vJ-& z>pi^AdJ+1`4t~M&GZG6>(NWJIz!q&kjk>#7gI?b;s-s?mmhX9*cY_84J`_h&M?B>#s0&ZLrnD^AF#<ud9N!Nq*jC*)*LN;SU8%ttz8wg4!Ce}h?W4Yf zS9#LGFt$j_K-YMJ5}fCoLoe8^!Gi4OMo8c9sfAn8r_QAT20TBJV2SVFY`n))BdxW< zcMU0D=eb2PSr+c31KyxC=Y=Y(!f((dUsf0s8F*EACH?(Ih4G9f=5EBH;7wZJHZj{t z=PMdBhL{Xanp-p`Obp-q4Sr2yvWUq;$P3=8F{6pOjVirOV={^PE&2bZ#$*ul4nk`1 zevJtcGnql-dm1x}nD0^v-`AKRF}opg@P`@`Am((A{(#2#fx$Ei!b<60x_P?y75dHy z_|C;zyWwe=3&BTJ4?m<7VK3GBxTXOqMYxD_>j{m4ltO9ZCmI7OMfiF4+OIK?QiN}& zluv35q!db9PiYLK6ya}TeF+}W7)U9?G1}p2je(Tnl#bR$5&WsfKuQt5fidA3je(RR z{2(oSP-8|C^KV9_XEnx0%r$iU=QPG5W-lUo@Oh0%CniCg|4d^>5Ob7mey%ZT#Joky zzt9*jF$d@cztk9$nC*8466F2pp-0wQY-^q#GwlAqCS)HubN@IM3&N1d*ydHrN;)ETO`p7zv&NgcNY-n9Bj#wwW>p?1X(WzkIK@Vqdx_3WjY`XWSz-Lj$ zaazdm?Nmp=O!mgn5q&qPF<4qfxSe8;(iki}BAiVFgfs@xQiT6OSIE#9c&Z3j)59_~ z24@-~JcYeRD~tyx7$S^&FCv(w+aRI}-*sF&!lp8S*SCm7#%Rz|@!!^9z~^J&8mqw! zUj!-$W}APO#tZwt%XQ}z4Q4}n=JKJP3^|rbW2AduL(|Y&+Wb_LwOMaNj6iU*IR{}g zyS`flr|pH3)z;-PRvi!_b`MT7{{gZ%2L+8&y}?Ch0vD$-Ph4#B z5azUvNaf5DBD>>Qv6f0IBCB4y#vF43RFK`#DS~I4HF7G6Q+Q?*oU8RDV_+e5d5*@& z82Cqud#=VX28M5=f1al?jDgv0E$t#WPkXF4yR9Bf&DWsT?gBYJ4grigYi93X$btkrXiN0XS@LaEL>?U+xCu^v?3+YemO||q|zGoOG zF3@1W$9JQH7n&-2$ndRX?L`{Q_VHjV_ytWk$MqiQpy;*7`1{C$(yDtxqNgZ5q7L zCs)XJ4PNY%i)x1k8-0s8P^Si)egDm=+pQx|tM3}F(s8Y;PG1EFx=j02+;;(I+E(*L zDgNg0nOq*P(9VK0-z{pHy;5Tk2)2Z8r}DRH3^H`TI4H3Y-T|c?)gj4GBYxlXn_E0^)T3pzU1Qk4-|a z(5-iy#8^KBXMxc8BA_xG;#)*$0xvO{GMR3MCaP%T^<6s-p{sb7W{R;R_vyTHm!rq0oEZy#hT`l`mnA2w;1mTf(8Wiof z??f$5SdSnr$n1}RW{5WdGK-A|(K+jU%=bnB&6owgs}R^TI}IH{d{??bk1vy8x32a2 z{BCfBZz}1>b*<$a?*>Q88+)0Xb#1`c%G#}RP}~^s{ScgFUT#oq1Pb5Jp@z(DM$VZ8 zvwbVUV&--Yp5l86ddb|O!Bc%ppp?v=8a&On7?B`zmj=iAUW2kSuhQV@zMJ7_nLQdj z!?%lIuLjTbC7`LyJ`Lvhf>3eh)%w2IB;WO{-EGX2T;=+HMG*$HL^FIZL$R4((qNwN zVTy2_?mOFuIUq9kYH+S^GF7+FI9rmM=X-;szG^%S6L6b50Zy8EizcYYRJ{Xwe0Nh{U(vN*-vw~)#pMmYQh<`V9hd;4&;0>F`v3+P_HpRSuxG%P@r(;d zn)b^W)@yrVjx_rn2sXmbMkr0UAA#O1`ybG?&(1_G4rZ}D`|az|CSdz;9kgShIm-Sj zD1^E&j+#8MZ|;~EI8 zpUGx;mP+Eheg@$1Y&9b-|1l^poUfpf{>x#$@VOKLORt}~a`-&8KxPQf>##<69$6dX z9h375l=h8KpJA7QQIA~$8BF^Xc%Ik(H!x}TA26>**o&!3+}%epY64Tj(b;zH-0@(N zfy|!f4rKOp9mp~_G;S64St=>DD2_cti4(|dX+*b~q=1?3zZ*)i^OOM02o?aJ?j?7g zbD&#$)~mR*{tRW$9{bX$2{0ekk$s9%hwyWu&puVH^Xj%>_GxTJ1u(PA9;cuTKQn~v z)0H~HnOr}!&rsuL`xinH*=H)~R6iHuY@Hd8^FIeQWRG7jNHfR(2TYXg2@0Czp9ZhW zo~ZieO4DRdQqXk&(yB z08LYnSLA#Q5sfQ7hPVMu$8*6juJBON6SjF!bA{ZqOjzu?o`JOrc;*=s@iRQH842u-+&HTqh1UuX<>zHX`BtY zMjqBM<83vem`fj^`CrXJxfIYJh&YJ|7s2z7v`wg}@LNiac(^xu^rZzqXq#+{r2 zou;uD;J4v#x1hXflH$8VQauRFq2oG`)-R7ODe%n+)ag(QKe4FSjo>du}o!Tp=HlX@4nQrmf{~2G#kFize zTSp1Ef^Fk+2~UC+XI>2C5qx)n`qWlo^q7;;;$l>ZJbWRtFz%2N_Yp5KNHdfJ_`{UBlKtP0MB7N>SK2;(kU-34$q=L$SX7#%=wkQICRlQ#I>Jb7 zQOq=J=8kTkTFHCcXs*;(@$o|13}-L+Ec>~%Fv6r_#wFbv8im^1$bx`V^WSvOA;`uH+f zeG;|^#^;9g+ofpwAcFH0802m=pW+3=_)OMS12?CXjsGQKarPmEVx!V9_M^w;U~o5D z6y+*ksW2F79{@(q`wD~e{tp0^tEk7IJ|`?gsDdZM>6CL<$su?Sqn!JE2{!Ey?pwTP% z@=vQ>h=y}9O@A#LdiDwBH7^*-YhdhijEAYX4~#?TGCc>)(d|8SI~U!K(qP;WpC>2l zQLZ+gecpL;!hNXb+uPgcWl)HZG`MZP^rw$W!`%0F-F)frf0xHLiO%`br;o{;Bhk8m zQRx%LxSbe81<-$>pNgniVxch)euQO~O=g2RKJ0lbnjW4G1{)G^@r7jZd7$PU;`CUg zCjEZR#Udr={)8N9G0Eh?Tm_}bXAB9p5tPAm32P4koF|R2RAyO;&Up{fr3)3*TCk7i zD5AZx5eOD^#kz%2%%1H47j@#|N$@tmxd~<;@WUjYeQSk$GVOQ3&ud5IGk&ymJn>6K z9(6w-Qv9A247l*Ti#VIk{Tyx6FW!B8@Xs(7{~h9c zuUEhlWBys#M6=gYv3UNeSZK4B0b^ieFazb{&oC3lh81e@bzpF;%|!=fX!)@+I|gv! zNB|AA6M$c1__2)|xQxwW8u*+*rv^U7#2UL<1KkJ{V{axOh9P(RKgZ~WVll(c*ax4K zEEQdfSd=*?jk`6&D0&l)oOw!`)P+%0h;W#BnuY=-G-`&VPy?Z|mYD!RnGY*YQFs$# zWL2Cd@ryYFPMuRjwHkt2_Xs|1VHlr{3gQzY?-;SJuz!;-r0F)&uVFJXiYT6R7(xa+Rzg39)=kP%)gg7qz}8#*`|0bO?1Z;W**)W+714fU;>HX=pSR)tTv z#OdhLJi*+bMs1b_YSMT3_N13^GpaY*z8%FW$jy-uzu;8 z8oqn>&h^%KPhQaU-D4JbB8K^+9dDaqEB?x>fA-X7S&4-SJVj^vt-YR=S+ANttH8Q` z#^MF*XDqhv#bB={e&#tZ%bIYXRqn|Rn?Ky~vN`TUGt-J&VKd-4*Dw=Tz5A*e@_frM z%q^aU__@`*+=`otTRoG;c&fvmsaa;+Gubd_-fDJPIcBS8v0+}d-Fn1a-(*fHFxNj~ zX5C}9#myNjANNcd^8?ScF=pg#bH-jXP+-R6`^-(&JzLCdPrl)qmi3%j=9yzy-?H+} znFVIet>!tP6KFEyYfWF%4W`d?f$_bi8|#N)>!fV=H*SB5@sfC(`^+jn%^>i5h|Zs zIBVUF@8}=yTSikDG}P_gRa&S3zj=fgQKDnwMX-vAdwivnJb| z`eFIKW~DXS%(LFU-rQ_8nXMllJ9dn}wA+>s&F^l9b=vouqgR^k1?K3r1!nu&vpo|} zNtphEe_CPd9rH3P?=e^y{&bHS&x3wjtlrI5*54oV&1yyRKa_MByy zMbF-6eME_^=R9+RrvH)qJk#KU?^=r<^~}UsYS`+z*R1kPHOya%56zYjpYzNZ+c?{5 zW*5|YrjEJS+GLKk)?T&Pdfpt3hK(F`6!m&p+;jF=&y?_bpjN`&at%*zhV`y_foHaH zN5UNGX)w&oANk0WH`cr!hM9O)e%+FWmQ{(%?)}&^J?xnqer(?j=Go7hRn}g{&6(VtlRLS4nrLXQ#{v*%ia2X> zw^)dZMJS6q+T*eI_{>_w{slP%H^;i-Iq?p5Omud%=XA%~8(Z2pE*aJ|2jto}#u`<_ zJb`;sISr~W+G357WO%6-1%Y##ZjlqO--u44B-YT;7@OH$zd43cFqV$nPDMjU=hhP{ zy0&)4Pu@k=oY<%41oFiv(9MHXom;`D76c3OUhi9_z}%%GD6-?iN*Dc&{g?4VPGYmS|AP?qIu@;OxF! zwLm|#hh8+?or(YliPpv(DtSXJwX*xi>fI0}IaVfm1x=2@7 z2V{cVP(SsJjYv1U$BUx+#+=fUiUm1SCwEVE2xwWA7E_SY!cb;jUfvQYb%`UUl1DPt znCBq7Pm0aia6+>rW_7HqrDF#W; z->U5hj2X5}_b>uQ^o+choLuz6N)_q4=@OJ>D$JEqOb zjZbR^$Bnac6Vuwe(PLJ3OYY^V%1vFw~y-?jvn{C`caqC+_vCDoeDK~e_? zjJ4+=Wo&7W!D^6qNMTC1@mO1DM^}B9)NX7%<*k`jURoX*GEYu-qJa~oDbd=xH3tEw zrKyF~bh`#bAYd9evpOzohbkL8V#+bv>f;T~G9)3T6Km?bXo&?mRrOG2M^jF`xux5& zndDYY8E{P3kPM%|i<(;%m9?B(L%a<0r~kw-WE%l{C_d(a|p#9_&R;j=4vlmIQ2Y59fNZpr@l0$o@YeQqD`{?8ng6j zZ%>-jpJ#PxNYb79V%;B`Kl$M))}^lTm-h^f&2y-KyXru=>>9Ht&FRYnq*<=9-Fe^z-6aCb-HNY97ip4$hvgSb)Y-tE0<%dKsz}FDfEPfy_*95fYVa~PTzG9W}Y0chQi#eE{E7o&V$h)!&7?jx);R_>e3;@ zu=ss^=?g6Rv6U} zvz(+x3$Rop^R|upkVdv@Yq2bp*NF_4nug_~k>R3&oR#7^-7+Aaego9GADCxLaNR2*oU^lht3)vbntK6?FH@hBZUo zYiwR99hc%w% zXByA)>o_sR=mC}o$*PaV5Q(` z9llt|?m}_DysU|8?tmpjf5jJ<`r8Rs5 zWUTDI=2{e#2s4>Vn+e8oX@Cl;x#st&Lp;$bs3{Cde|Smx1iMoozz%g!dM(GfLDp8S z2H|azc$LE@v#x#k(ra1Xpsp>Jyr)R7bhmv-*6$N6Q|o^O+#%vc)u+1J6~CFo@u4z~ z#4<}=TP%5x(LGWexXbayH2#&YcFkyJdzrEaD512Bx)3R6$8)P#~I{TT>V$u2eQ&1!g& z)0;1p)JW9oq1xnf&7^o2zB1sU>`~ViOWw?M3(mIRz!!qE;G;$u=L;yVSC==T;GbGR z0~QY|Y{^*M`NJ1&`CRb>_~LRsh;slJr=jo^!9mK)+pKmmNgI!w7o1f?EuR* zHKv!P76p@DeMnF9WVv|CaPef3H_cOqi>IX3DI>?noMNG^!Qujibs2{Cxj|uRlqO{j z790^2E=KWvd0E4P#sT&uHsYu>GyLMhwjqfx+=yOE;>3m3New10bR@>#q{0(@q*_H1 znne~DO6(dIW}(NsxMOI%i|@dA{3{Kh=L}&FHSKgY?R*5yv;mTHk9)mK z@ul0d>{iznOWqB4yFJ?u$ohS$w6GM z&ztL+a$H11lv(Q9V#!;MZhpAed_&cHS-zvLEtb=BPHbyqgG=XUnOgrX;11#oH5TD! zX#;PV4uy`{pq4KwV#kT{Y;|q1HRPCMp)E)FE55iSeUf%*e)ISwtNRnJAfQ>@pD03ik^v9<6E42@CtQ5* zPe{HMtNRlUt7P*o#VUFGvf|I_=Ng{>36DqiDx86r?a@Wv;KdnQcS}dRD1{*()*5SwM|s#PpU;s`FHwD^3GTtm7a)|1?SG;W%jdiq&+I3Zt!iseyU0P9G zR#y_KtSDQzthBnO7SBJl!9UR#6x-RNu&k_dO<_e%=}F98-`&vCBBDhdAj&5lHgv?} z9c`jKx@JXXStMFsBgL$%D5_hwEK(gQDXplgt3`Ej^}4FsXie$z3K4CL;noBPDv#6_ zu8OSVLlB#AcWC%6jc9i>T$E2cp(Q9)7p_4O0j=`#l4T-Nu{u&#SruXJvdZdW4u&RG zh07z=ycvgwOk&ac_686^mzqdL3GiqeEnikwRa+@|*MTsOx4~3pb)=@Qh(>9QO4drt z3#)1()vF`b6_uqm5z)Q1J&yOs*ny_0sVXal4Wnhn(eg-54F;{zv&%i7`Orl)j^RlS zc5JQR*saGbUJ)r?Ra;#L{kO-q#6@&#M^h7TU&7QIVa1llb{G+11$t?WHSi7~hC>_B zgXh$@#b7PbiAcnFgGWK44XqvBF+A52?QXd|#!-skYZZ|-?2em};G(3kHWICl6h}%| zM@pRgrAb#okMhE`f^i|rzi1VuRYZBDqAprh2{uu`tgr?qs480rVxSzYsVrUvSH^pN zxJe=JT(DJLMR8?W8P&J4uDl9O3#+QA{t{l+tXc^F4wY8wJfkd9TpNWOh&81ZC6#M9=*jRaIVCTA^lJT}f#r$KHs(vI>)-wo>}wnrgTM zC}_W321ZwiXlZ5ivaXhREQKoo(pu(lS45qKsz*4lwZ ztrjd5mdK}~qD`=E$7PAmDE@eeTx1nt*gBy!8I2}d8sTIu?Fd|*ty|f!L&q0IC^1yt4?`170c#U114KUIagCpGknTOpt6bVxT|{(aF2unuNNk z$eX-f6irPkhFLC6S613{DMX5rkz^fj7pZ z%`JHDPx=ibMpDC!*mByiKhSDXprgX#YxIhXIz|pKra9zjC8Y@RwN7Z0(kjoum@>5U z!4JeIsYkSzVXLsNwz5V}0~NY~$J|&}U0KeU7gehY_~!at8(Ax(EM^%DR)#Q-$NH4A z7`3q~le|_|G}?xsj#{~7wZ@v_oRxUQkgF@1(*ZEa4c8m42B<=;E32$nURnaLQ88<+ z;Oc=OE)w0bD6J>(`VOX47ovJpIs^JCW;S`|_2D`-hAO1DJ-VGiMn zlXNeS4x4{8ZIdFPCeSW(@61 zD=T0JCKFqu>OmN}45(mOTCuvYtdv@i>%Z98)xqGyVKGHZ3Tswi`P$sl-Le630pil; zauI^Oa{Z90N{yb$QJt2tdu>_G>UF)=S)Apt`eCU)1mIpSOe%&-(01Hj`Vnv8?U&L2bJ1ko}!hW??7lth*lViaPKxzZu=aulOWBUVbepXcOkz~scFtifYec;Fg_gkEbI{M7!SvI5(j z>UFd$5)jhjM1(`}vUWvfb!FZ16*bkx1S<-wt1Hz$r$jx%wM<%obzH~f($!YKv4!F> zoVUi13SqH#wlmSfBAN4c);GiiACarU`!em=E{JHi&ULu7VX05fBBq--yJ+uj#q&rU zXiZ@$Hmd7HY)fZL7ewXQ>uR`nD=e!iDr3@L0^gulpb9zCT4ZF{V{rXo+p0n&@CX3$ zMmCYp3Krw7A5@iK>m^e*yF_u{+7550@5H-;3)PB$nHo1jz_C% zzk~70)W(`fIpLD_l$tEA!@R8)cy6%`8z?BLRql~zHFvbdX0#ShrT~GmzRzjnvc@!hcngR=rluIhF3I zjF&nZu1vYr%}Fr*LC%)LKboGBddYyzloG_Tsfs#V8Yqx@#b7HC2FoJQ4@}2&5YxM~ z3R@HDy>hA%wJwjYEh{XFl&K(sfLtb;>Nmj^)kZ`G-|kp_m$WssF5%+xj)sO7{{iLy~j= zng8;2Xf7EI9$?RA}kOQ4`};6vnP+ z!(>+Jzo%^fmK z4(VeE6L`87cxJQ7Ai{NwfXuJ;W+>hfhwFhh7taXN&2=Eq5Np}2qPTmFKqDBWW<}+i zx{A6Q#z~xxMtbDv4dla72 z#h5inySt8^)ZS2@z@kFtj<1d|x?>XZSW70T`KmZu6?0W_4xJF;OWm@NoGW%gi|5!}dbwjF zZ*?_1;$v866zN77>7ae&VVyeu6Hb1v4kYx6knAmw0xGM@OTk-(JU>Q`QK(Ph@)5kw2UjI6PO3LgD!ZBGOd!c z1wY)nVE>2=tE>JpTs!-^61nxm?5KB6RX`BY4&ev^QJ$Hpdq*nk#%T?9fauTTU6_oA z2FQ0d@)!qLEe&%LH8UUzJwbXe(p|mL0UObFF7O-bokKk3MfyaahskgYoSxL;kf~|~ zl3KDXPxYPI4$3PcWo(8sPw?N+)!L+-)VX!R7AjQ$p<<@}0;A!$8ZQ(uv|>5Ixf>Sb zhGrGg@jf%N*7)WqGDBt2?837iooq+3zHE*m^@n9~8V8Tqz|$?c5YS-yED5`i8t4p1 zJ8Cx&DXgihj$k$sfll1<$!xBnJuZ_cInkW6M(MRsg1m`QjzeO$m(7Yg8n@Q+eO6Ia zS+Y(==K6+BID$~g6at}4t>{C}&KByI7Q?!W0~#DpV$qAstpR5Fes!fclAB0Zl640_>bnv=|RhWZra9F03d9KGURgKRrTosbj#Q{9*%4 zBh`V(C)W$EqvhyRgKcRGUe8r##0+r^qE=Ysg~Zh2{21FaIoEiGEKl-TLC>HfE0-<9 z(u94TTI6V9om6p2#ThL8L9c&mJwo3#xF3Q!jx7odTg<&HZ#qf$I{8U6Z_QvO;|tBh z;tWoK8oFBKsh-;BO3zM2FHIni=kU&X7zV{XI+-I$S$Ghk7F29E)nNvj$a_mw^dC7? zH~h=FIelrO1;@QwZXSPPa^tpFa|ciKT|1@7mbl!HR5?LUM;j~@?2Wiuwa!U#qV)}! z=PD*P!nzSuC$s`en>zhS%v&_MqIiO7i1-3Hx8lr-CNth8p?Q= zDx00Fu2^fH^qD-leC2Jx;*y7bb7Et(e!~VzmB%IuBM*#Su*@~{x;ogEwDa@w(cA^j zRlOC;O{s}@I-P+KUfp$_i4EMJfRCY(ac2~(c#^f@5Jnbxd`f~-I}g)1mWTX)CiH|G zo&W0(o(;kyD)@_Iy2nzK?q?b@G#-y3;jgR>ed71yiAFr+il?4re=kZ4Upy)xVH2hN zOv5h+(4QP#o`sU_lkKMK3SE#MKeO?5b;kn__%8*Lorda)Qrg`(6Hk}oF&F3K&{zzF zTaMQs6XJF}*g-j{14oW(TswVmDPCTOhlv~|x#}u#?WT9-@047mNBJCjU(kK#pyX%8 z#dxMOMGlVFhA&H}-O~+tx61>B{*WH)ck0rqdOe1}#sZx4VLN`V#MjMVFZgQ)j{Nb- zMTfsH;o2>4MicmVi0gJJ#BO}u^p1cYJCYtAWlqxjszT#eeX=p=R~%;o${Fh}*EL(- zzXf)4DqVHo!u7Cme?O#WJcpbd7v@aT#-%vARfrs3=#NACVZd&BAA=s*qa1jWI7#nk zxOV#BQe<4t{|#j5E#AJ*=IqVQK-k{_q;FTgn0th|*9 zb$y&V%IiU?;w-pr<|A&)k)b&$Pjs{1Uy4rK}Z7J{@e|rl2ofMdVTg~~fJ^$dJ^CA2eVCOw(>gUsxdj1_o z=fn1A0CwJuX8Zh<`jQm5lI=&Ucct0BKBazR3f!Io$5Y_#DexCl;C(6Z%_;D=Q{X33 z;HLpE#X`yVx5@8sQ|f=80v}0%|D6J-xk5hmmz@HinF7yFf%*3ioe%pLrN9+{`OH6G z`jz@ksc%hz6Djc3fcZTCLC|LZn^Wp<2kg8r&iWsu)E`WNUrT{MNP&-~z+Tr9NcqO5 zz!Ov8^HShdfM@5Z_tnYY#VPe$Q{Zb;;9FAQ@1(#Fq`;4)zz0&`-=)BZQeggP3(kk~ z^1q~XK7=h-PC_`80`q^%U3z5^utI;W7%@rNSFhd!cwI3f8+J07OR!-efhSU!ErNBVKDnDU^1 z^1<7b#+N2yxZNlRIH8YxIY3sO_^72sZ^XeC4xX^LMO%5If@(p%r%%k|%_cY7=iQy2#cy#iGRNGaji1{ZNBC@t2Q!1ER>AjxM*znKXu&;yiH}o$MJ2umZDtBrN(i{ zaT^rLZIUsRa?PnD;>_uAa&TPE#bpS`rN~{X(M5()G>A$rrT5h^QmwD=Xut%E_ioHxW{TA}@z0lEy?1EV2b z@f(Ry5?zInm~)~Ta)Tr)~Ii7>BLsn zr5Cz|p+~3&MqPw$pqD2rJ6Gp>6FVp!Ca(UzG>6ciFKx?Bj|Pv`!e>r=lF$E%F3e)l z^TH)Fv2cq(joIr;^XN2|=6>nA)zG1CiPQheSrqt8zYd(la`^B|T>F{07&}bry)se2 zE*qUxPZWk$(I!d!jwKXDdrodtKTB-kf4@s-4;`s%#?!UW=~c{Qm!>e$I(pS}2K&lwHmu+C zV^>~v61vlS-yB~n5-ogmWo%Y-1|?L6({CDX)yt*}X2Jyrm(J938G5*|M!)9q zv2w+pke+qvQgzPSN2?UxelD#|n65yBoc{g9;GFdST2);%9}e57rT+fueqla=;j=9< z{~0c(&vE)qeyo_jANiZIO|lxi>1OpgEltKXu9r#nkZ4>3Epx2KWtLhEer~l%`j0*r zdb*yt%&OnjQcr`3ePnCvVHWz{kIj88i=FVz&$XV^G7msq1 zjMvrppL4xf>=9>;X%4p<6b*Mx*0^Q3*R!Vg{oXx&k=2-{ZXF-`Eu+uRUao3Z<%6W> zH_=(`&)G&A%PJ`w>)F7ziN^lOe%4|9R(;2`TL1mh)1R_ht}^<(Wh+{3SAV{AePbEd z;AFTrvC3yrzL4_eG-J2HJ?#rKOx%rD`&m_#WesH*I-ap>HG`l z78;i&k8#$1HP5-F){pXIE?2uE%737|y4Kz0ci2|?C8=$#TNT+hx~GWr@@>aGF4uaT zwpx$sWuxV2B;$9+VjXN--R#HSrJqsTb{e0S?&pZJrZ26*UFV9@xgog)xs$Wj@As6i zp?oKKAKA}_^n9yW%{N23-)!e!YW&i$RWw;k%yhgv+%& z7o0W!6b%~3JLp&9wzLW{R<~NN_Eyt(w_Wsf z2HREZYrE^|)3%465iPykXRX%1-}O<>ls^8q*`C@ywt@CP>c6q6I?l-@D@4;bwd${} z^mfRz>SwykAJqLytlspNxxANdz(aoB`5~>R?XCAEm-o@bxt$-@?@euA{WjX=+D>Pk z`^92@R8p~Y-P}fcJEu8k#9{-imScp=Z`1zktbO$<@=Nv+y>Gf)`_S7~)9uEyR_$Z@ z9jm7=D_wsBHo(?+ANIk)I2LE%^Y{lmVzoXuYiQN4b3N(fwh_6Lb7m~o-|F?vvHdm9 zPW@_U?H8NK+nhE15v%Q3LVtMT17doDyUfyeYx}6iM5O22%~{)Vh_klWXlJeOL_1Kg zlgqVSUpi|(C&(pkRMvd1maebwtmX4FUXjoqNjzsK1co8 zYU4J2Wso>cD>c~Rjt~!wfeUQ*$>8aKjX;L$S*kSUq3C? z(`}-BCwU+F1o<4fsn#XTN4noUTUSpZw|XC2>Uu5L3OihXr}WymeKYCy_gEbt6RoE6 z!=>E*Y4pRFV1~H)p=Ab zw$oYD9dsV8{l{uM#(pNpXdGAieW9vN({b$bUb_Dv*-tHwKcv4)&e|5;torNYaxKR= z@?2c(axK?7=T!Yxo$}o-SNkJY?_+!HQyzaucmw_c^~;KIhGVnS6RBBn&ffhna*0DdCq!mUv$=M zvxNMX^PO4`J5JlPrhH7Ff28{h57HX1aYpjJuAiXo=R8q=UuNsp7y*=}twVkI>K9}-!&g%b=^HhC~bgrlIeC^|YzbLeiYb;#4-^Etz zx6jdYSI_{m- z-*RUy#|Eq8YQOEL_eIxhc`w+j^?4&DYFAr&x+dfnR_*Vxvot?DTc7u(w|lPD^y6Kw z`OK$$3FT|8`rGRIIr`i~{SoTVko}(He#%MrlkBYJyUmu-BRnYYW3@eg?Q(68;m+C~ zh0bL(f2--1Sg%)1mW;);YsQM{Z=ODm1ogkcsx}^-ySCbGW5r5G_cwL>rnGB??eHG# zhI)$#{q@JesJGfsJ{BLxdH4dpg0JId`~dghU-1~8!hd4fV$u9=zTWx4`0An@D1F8AK^j#8hu{P{gx^bSqYP|3EqjFu{ZkR4Y>a+dvFm$a8v4A5%QG<>{j_OvZ3~ zSuJlPax)C$4l2Kk>?go^dvwP8u^0Bk{x}GS<47EblW-c&#s&BsF2@pSF66L!M~un%V7 zqZr0(G<_b~<2LSZ0#3yl7{+r{|19}MT#74jBZk}3s{Q-q9k?4m!$bH59>^ z+w0{ljn`sDtco?zkGymH26!uayvgOi!1mY)yWs=a2Q$#)Q=UEt^KcAKz^OO`=i#&X zA}+-h_!_Q5-yPTU+k#;{OnDdC<6^GgkDuc)EJBZ)x!n(V5sR0N%CExmSQ*1Oo2IKt z_Dy2l&(EHR>4)Pe9FJ3RCO(DF;qP!cdYsn%y@i``EAGILaX%i$Z}1{kEEn}x16$#P zI1meP3cicG@F03z*UNVSukyI8aurO$=GXyKF%xsK5a;3&+=9FC03OG4Snj%L{?#xA zn_~w|#Z1h_DfkTT#C>=S!?>~5v$)5BWd*E>O|UI?#lAQM$KsQ?5SOFJq22$dcoe_I zF#fFi8!JTZ>S1f_g5iO&YUhVEy1&WzG`@lx(c{le%&Cl0_-I32@yv-(*@{x95(U*LCGT5Ubw zs#q8Az>fF;dR*G=^KcT*!^QX-?!tpugctCt8>0TIUhVgavH;eofE=2#9$MgFGuE(vo2an)s^p7w+U3v8Qyz|eo4c>>nF^toz z-DvU?_zW(?H}QY)V?2zf@Fy(yvuOS|V?%6>_u@mCjpK0^uELGD4L`-B_$~UH2(S0` zSPSdo{n!ipVSgNi!*L{z!$~*|XX65V4j1FgxDwySEw~+b;U3(NpW`ts!qXT_Vtp|g zJ7F3Qz&tF(xwsTp;A^-J-^MMt9sh)NYDUY^4m)En%))$}gmZBvZo&_6FZ%p~U)M7j zOOA47Ou~lP3OivY4#Tnd1TMfOxEg&P!t>pRpWs0o*L4AS)ao*XH}nO<2o;c>C}(Fkyh;r$#ZZKE~9>xRX=MnoF~!pZl~R+coffD z^_yHQ#oI%dAn%^KCNBJbH&lKVOi~8N@tbX68-5+t6RlU!@*pqnH zs{K#o61POTyj8nOj?<12aA4K_7@+_<6n}<(RzXJE+=T`mx&8mG7o}|8X zN>uM#v%6g#Y-=_Dj^wUZ)8CH|Qa^(F$0#qvsnpM=ej#}g*|(SX{NAwYcRjvsHQ!x$ z5D#0mKS4fC{s*~O-KhQ=tLd*N-$cH}>h*0;c{i*1_QW)+>9TPQj<=fcbnT= z3i3wWj(hRXR{eZQE+T(VzDO=vFIujv@LH?os)2Q^`e{V{ZP=Xp&eZqA0n}$>j#Yo- zak5o^^KdbKLH&>9QuWnN+v{p9XVp(ltYg(r7xMk&hshb_!Q|oO@i-Hop?(>@YW2Fk zhdZq1bAWt;e9mfY!{_i_U(OcS`2cbfw!$vh8z04dEX3LPJTAv|xC;;9SNJ`aZx}64 z3O2)cim6=N)Bo5KSO&E!p!GtcB7zX6KrDDX_!u(C8i7I z%FSq(YL$DD^U0&h3&_7Eze(Oe{)D`be2RRQe4W=<{a0eW8n-rz#_OX>tKuv7|M%HvGKu}# z?(aM2-)pb6*Is+AwI64ajZG_-XqqPMq6tF`P(r*m&f+vms1av~3R_g->h6=@ymHm; z?`}1P*nB>lwA=g-6Lb606+NrX7Z+DMNOn7_yRWD=|M*3Je}B&Agt*2*d4nMd9zDPg*dOt^k&~Eky0Ld0)u{qK`|69 zcz!$V$8ew>a>)D=4f;$6&!juI z1yk+&In2!O#!DK196buo$&uPS5v;!7u>BHqOOBQv%I&~gY&sXS{lF07VfKb&B$0n+ zkS#R0v0yN}6@1fVB4Em?-7k1^ZzBZu90nXQUxmT)g*|Dd(wak$oCyt>4zJq&$?faT z^ zQ!y{?FXWjw>xFcFjZbx$G|(aatN;61uk`VtbT3LaI2hg$c9PJkBamBAW%jK0aA6eX z^z8?^Ca?Kc@VXcB>xS5|>3OD#@Mf>0E1Ntj$uS3+=&McJ;RtolC7yiR>_1c@vl(+d zbHHS8ZZQ=METq~d4=rI#u-J`(EJF959gIrDzTDA_a}S)*Uu2;*Z|LeyqpMm(%1V`1 z-dq>>hh&0?e4csIqix>r$oKYt_0?CO9GP_B_CIVwN%wtnVACcO2U%ee8F`$-mPM~{*j4GCq6;*6H>0uu??Of>1C7{*HTaMD( zw+exPpP3e;t+aR(Exqub^u`Lgf7oNeV{p@<#UqeCClQG@Jq_>B?>A!@r|{51o4yxs+ejU;E(UCY+3k!aTgW-^wG%THoA|xy0r6Qt0>f81`-WjH|5g zI#{Nn{zqt2)$_Ug$Ro{GQ7}ZNmc6$eYPyeW4fYmq`%)3%<~84U)EnOH0Z>x5r_#0+{wc?7 zuxrXg*i*<^Q?3R(=yK2Ly9@mxr;X62l=<97*|@S1+DNS&XOlig7-jR^=ee7GLKxM; z?Y;nfAsniT-PCDSg(&fYEkr4S;-*hC%G_@D)|Uh8V7MJK`PIXJGO|#9L{iStEJ9yMZM5IeuCEE zTV1loeHErP!6_Or>_o~6ai*NDQwaZnss$cSN&EzCoSP^PZ5rO%9PGaK1@#%kfJM*X zWgMHux1+Qc@`h%40xT^vdui++wRvdW99qq~W%-(mG`DH{Xr=#c{3sduZa zuB3)Mub_s*xdH9^L3X((fflEuRKJk?9psld^aNRtkkGGY`xBHZb&NwdOy?nR^|#RO zY^Xzv`6gc5optY_*>yh^lxtVBYn5=dpsi%IHk#vAIb8ou?ifXyuJ1!fNrfUkuAf1w zq*9UPt{w`HRpcnw6bhfA$V%70k~>b3<6WRc$#_NjUHd3JQIXZI1j#cMS>p;)*ssW$ zu2)G;)@DFRubSmrNt>&+21z!$E@t1UYDRNid6Lr=Ip4)>DVeDq1?W`^T@P>yv$P8& zx!6@nZiBW$l1p3{QuA!>9I1J!YaNBp)|N_gnQJkH7icG>@Cw&*3NO>Xl;jnzS4lQ2 za*gZPBrjIvwXQcwE?4CBuHz(EXj5e0uxkfxzEs)V;kt_4%e717xG^!T3>j7Ow0Sm~ zJtceT2KT>HEp;#xJWLQyXZQygnXSwT*?OJb zIt{I@Aj&9f^6F=n-n@-tu3?W`KEfNB<91N%2AP6Y4q={z;PvLr+hD5uF^HITIVDIx zne~>(P4^t~8XuKBkNX((n&&(xsdD$TCpi3R}iZ_eKQJSmrEzbNNw7Vu)a>DI_M%P5k64U)I z1YLg1%5wKYN=`aQY8>hIK$B}SRp?bdDjyQN zGR6$25Wa_~>IIE)^gV%rQO}|SY#bwoLl^@o%tm*lo9=7dR_PY~=hw02nGmgs&aPM_9SOAZBPW#(r2`#2JyYp$IMRkXtW4k36-l9r8KF6vKoxGo z@OCvF?TlEBN&zIp(PSh}WvD|G73gn|C0ar;>H<-akTGy#Pz0$)Gu(Ui+R^4Oeydkk zd~8&jht21VVZG+^$g}24=BZQ0#pWG3!)vDJwP)_r13trT?$xLH4F54>*fH~Z^T*~o z^SRgcs)`wZy7$l#BYN0OnpYcpHk!S9^{7+E9h$kuNF96qWxdvCuG6Pgm_8%4*IaPJ zjj@bFH@55gD$Su8@7_9JQfbuRyVdMHX|$VxS;n+udd+aN-N2|GJ3Vo zjOo`R)}5JjI%r2?o?q3X@pk`|6s|$_A|Q|jD1!uRYUhE^$6pgkCgTbJlyGeT@wxRLAcpYyhqkE9-^gV8zii96(EO46DxVvatf#_rr_Dr zg2xbTPB5 zKLhDVySxm!U*dTU4>xJM&_a7+PouwGg3Xr&aV`WS@vsOcV&Pz-tt}Nvi{QF+s3jJ$ z$)%UB_Am0w4O9e!sdO+JPhiUnrlL1T&`+Snk~b|+AQ2}38(0NTWL+dC zxcjHN;0CbUqhZk&jYXs-!C0bot%xPCk4dwGH)LQdEu>$A*1SLmTQf;)f3ZwwTm-uk zDIt|pO_8^xGlD6e?t}A+PFT{sq6x!?(jpTto;EDvP;?Dr6=$$y@GYyPX@wrNaS%bx zma9cjdY^+cRN)5L+!2bx+)O-^iiBqmghEEuc9RwU5W{bUZ?JwEcXlI$WQ?NmD13pm z3#B=bbT%A_Fvlb7$w2~2X=wt6q$P7KXtdxgK*n}66m)XrAcwIm$sj!8U_8_ru^cei z98A~BOfHi^px!=_a5o4B8D++bVUf{;HKaM!)_7VOhV*44G_{0U*Jirx91g=*mxQ7* zL_*~}?B_ZeaGVTqv@_JD)&f%)vxzces8B92dr2g@PB=lTkkMb&l}N;7&P3LCaf!+l z#C;`^Nf$+1CL**kHKqB;SfE(CXwf`>&0@JOtR0~4tXj1dh(PM5PHYswbkf2OyOxZ^ z0%?XP5Duk7BG8gbp~}S(47Ic*VP$|KR!cPAmMEsNt|Oom>`L7Yfri0kW3hBwl5tb2 zV1F^ME7QWLV(fv@Ldj6PolVx@gDH$A0tj#?E@>hVPv8cK-LDSGhb8+D7ygutLs($j zm1QB`JV))qdk72v1Sr4qB_+foRYJ_dLBLOJ_U9JPZc`MELsgbfi*&KU-s)$dPS)R( zn*|x_w+r>%U({e%FM@zwr|dS|qIing#pdw?t#}@DY1c=kMaO|kn>N7D!) zzA9?4tCxaTtnXm0H81Mp{A_*SLY;kP<6&8ZAHt?uRrw~5Pp3j#E(SUJ)GpLVxlIZI zvTTQ(_4iqerW^}Dbc^kK1@zWlc=otILEY{{4Ktz7&x$HGZx`rdeJ6_MfzTB6{Ty|>4^^yyzBR0< zV)K3pnsw$E%OjARWIGKsd3;`12$1DJ@R>TnCV;lS|0$}I{RjCu%bHbeIofLHJUNv6 z&=QevTaH-desKZ|^&vEjMf*rRG?j6rPm1+rCkx@Xm4H`N1vOBL+a2OV{(@2{ga7(Z z{lz1YE^-ul8T^Q{SoYEK`kf*4 zpNG&TMF~gyDu&R-KVuBO9m=!Mx~Iyjydku8C2Ye&+$cBV2dpj*3cVso4*yW-9fiifSPi7woqaL=*tJ5m7BywLEr4&K>~N*i@_ zb`=QLm}&^g;5`?=2$qnb?a+R}j%}4iS6Qw~2n_Cvg&fK*iQUJ)?m7WFe*# z!C$D_n^b$02z~2`u=_j2Dj}XERtxb45&Tm?>id*5^trJW>2O9h5&Sg@4=H?yh=X>v z)8e-gA%6pqdhSr|+epKI52*GRRQneSm*6fz`D=k3=LtnWspzTrR@J8ov788giU@z- zrRZ0H?EjjgPb)OhM*p2dM875=x?lDC_sqlG)hZX)x;oAyNDmY*Uy~m{rLC zAEKTgDg3FzeG30m;advdSI9qiu%E{D0+j0zI6=`|Z*0#f+^q0kg%2p)rEssp!wUJQ z9riz=@FRu18nC@g;dq7970y+-MBx<*TNHLF>{0kVg^wzHTHyhOM-+ahkU7us@fUE3 z@+UXYb&8%#gm306Tu8+A;~NUEBtrgrMRzJps`d?vzFXmU75+f+A64`-3iqn^mlX0B zJnH{ng&z}fz42qg66YvvBSJ2vaFfEk!hcfum_q*G%Xwkz6dJBq*wQ5pw$Sjhk!LUE F{vTB|Bl7?N literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/compose.o b/obj-i486-linux-gnu-patched/compose.o new file mode 100644 index 0000000000000000000000000000000000000000..cfd9823b8b2795575dbbb00a87836a0a9d8b28d8 GIT binary patch literal 68308 zcmc${33yaRx(0lfPI3-ux)ahI!lE`1Ajpn5fFwXj8i*tzWMOlOfh+_4aXJ10daJ$JMN;QLk3htMICkc-?yqx(k$LP|NZat{P8)ds;{cP z`u3{xoeHiGbR@Mk@=fdCTQB*t zs_EaF|H(I6*M8r+KkEHOYv|~@snL>Od>@_SZO!sVyG8ZZDdX^KdQLQSv~{kx?NZ(U z|#l;S(oD?c8`IBcN$t+|~B@QMC8A@Hc1e4IO0>HC(hLS3u$g!I%WefH+Ih zeGBPES1Jdg!~jtysnX@u(l~Vu1gq$6*%|Kde<&^)<9?qM4mBP4><-p9K25?N4x)O| zrDd1whDgLpoEnXHC%4AbI*>#jZG#da*3NM)J0o>_By(hhaz|$drR)&|xs14?rc`%! zA%8;H?s_Ll9+aFSd6GP8r=S=15|s*SIRKfqZhf2b1wN{h%Zk#IhL%$ORxz$bNalnX zE*K^+N>uIRVTf%H4CI_r|C29Ko6zOPBi}>zEibihP5R-)3IDZ;VDAaCcsRLgbJHGu z!s7zo_60zsfYuhxx&Qm97M+|+6GLc=-XNX zV5ozxt!%NMytM|TJv4ozM~09LFdEg|v5Mtux0G&Sq-%?B7UuZgDHhp9Io1Y|j7r-HmZTi6QH&YL>^faDA5Bs<>RdqXw zcSYjg5sy`Y?rA-o^?Ng%*}T(#Rs1Q~uKG{0os3$>CrYjhR|E+s^`F!L9j&`Ien3)M zUl?HMnwH65{^mRIn-HiflfV4UlL6WIfsXpdfAP1!c@NMxJslL$P5OaySgviKY3-(+ zdU&BL6posPQSFqg)cb!jzyIx+Bcx8r5=jx4a{Wbw*^}5(>TAh@opEi~=P%*f1proU zmX_7>mcMx@aBi3Y=K4$I9i#8zqA{k1?TGGS{XxQ&sNLP6X{YdI;Zm-MV0WGC%m>f0 z#B4hqy@ln7oyH>&#c3jm) zb=Brr%2r}{`+k7imY+oN62hN69lnn6uTF>G0QgA?+1>sfD3j-a7)hLATocBfydR6; zz46G~P-C>z+8a6qB@15L-`*~~Vi2upZvAx;jj*bA5?8$&>t=UOf zpfwu-IQ*@!V6pX6q(nmWng_#_14Q$!y)ARU;))pDaxrSe()3heYg-{2t=XRFB}Y`e z#Q{iB&^GyK<|7!lV$F%P7ETaytZG_&OoN{M&5t8OL_T}5F_^*v6z}e%1)m{2`mhJ)^gn6 zvWX@bI^r%R1RY)$%|8V3M7eiP$yj&(sJ9MVLJx#{Zf*DwZrvxsZJB*DbJG)g)p=#Y`6gSJbKAQZsEi4pFuBzCy(X5f4nqM_?V zXN_yxGCDQw48%Iw;iqMo7VhD1Zo&a6ntvoZ zFRexD#ot`j8z8t0f-9C#F<1mhzAwh|(eXy&Z{GSHR#LAv?elPs6&S`v3q3;Gho1i& zAQ}un*2A>MLyr)|bpY}{3_7$!zl#}_^e{rOcIXCxI`>fT2F!W%H=xfEJy9pBbd)P*ItYk=mod_9R?5KnbebeGW@-MO6bGV z0CgmrB;neLbz5xz-uJ1Spv~(k??q@)SJ@D}TAW6838?UTG-98iXs=WvV!Ox`!Nuz(; zfil{-feIht83uB0^~xj3o|ZnlsB?K!Nj0w_i_@kJUzD8sT$#Ilh z;W**rO}kPLz50m=I*9i!0v?rOgBlV17xvp&J^7n?m}f{WS@SnLC_0X+YDnvDfAdC2rRke^ zfAdOIVs+H|X43}=PkrEtTKrl(mYk|FNP@;#ewbb1cVeh3OuVPE3(>NIr^Vq4#7{;x^Jg12Y(R5hu8Z zx^cpL=%4=-al&;3*WQ(_cPNYY{vHBcr+!&Q&la((Z5m2O3bML@U?pR3xD8>L9-5_c(A#65KdS z=+6l4zyR~@U`OodjqDbDiD2d8qpTab_HykEavT6AV&&LY`U-+dpSIH1QKUvoT}gyq z5rPQ4E(*LClli7yLJkCB^vQBiya_oR!8xZx4)5{2b;&FK9r;IjQ1(ChqW(G#6>YPi zu%@-I=<5cZyt`35qfVg`YQ*LidIeIsHV^amwp7qx@iXf9;Xa$&vOA8px&J`a*`tq- zyyCxh3s=dkq*8F6TmSE-1Nu`366{@7t+NWDMZ8jp2>Sk~nD4%7H^WFtDn+zZGH|*xk`b(3xh=b6q}3-mzjgBNz{|4W)A-O zzVIvmLv18o`d`!gejZkn{0~jR0qCgx%vDng+olO4IN95qcK*oWb;I;o9t>@o9!QRH z=}vn5&Fk>t?_^|dFQD$xavlbWypIsNIQ3`5o}mARS6_ALDM_QdLB3)WtETxuT6`A~ zb0HA0CqPtV?A~@OzL3CYWgO^CO~IR(N@@QV2N~r@&68!CB{~DiSAX;0n50JPby-Hs z@kmnpuV5$9<>UAcd@ZWSr_QoAhd*_VL+%HM-;K$mU_bXaf5OcaLCekO4wsp4l}C~1 z0C~ox(MmaBD_IDt#QBXWGqE3fHbw(CGZ{IK1Ea>?$s(V4d`dtMca0hwE}Qk8NU&k+ z^xW(Uz}*-V67mV^ zJ)|p>(V#403Co9Qy=xCcjtH&rKDpu;y7xJZ0I3n_RK}=Qa)(e5R zwIu_;*N%=pND3vLI5V|*ceDkrj6TlJ!wHlRKL_hgPkCAm<2q z?E#4-b+Y#Yk%)xuQCOZilvB!Rcgp$3m5@*{>=_GUo8^L88MK3#lTY(0TTj#OK*#QL z#+L!w88!k9cG!6WjuC)3!2I*$m@ViXG)_M(-g3&q>io}l3Z8a<^22h3dlK9Mvf8&Hg8_Xg|M-OYTlm4{ zX)V~Ta*@guhZe>$Z+kp^NyM>mUlGG-H=S`z^h7>(-}?}XUOS}T|3y4o#8k-{PE`-h znuQPeAAGm-kkNEh7iTKN-gVWiS=3&(co}KG_M@1S2acB_UcW&`&vfcgiA}LTh~r4K zJEhcGn1tXVzV`8BlRFhk44)rsCf`s@G2fBd$2Cts>JY04S?bG^Sj@$Ha)T$1GmVON zXOE;39~lahM0Ibr_}bWX$k&=3Y~Oqk42us%I>wGV4#Bjq0gUpO!xe>~)bn=?aY<|gSG*BM7L7`!FV<1wqa7?hOoOVE8ZQ>=B#+tJ8@SmX7>L{8%GVtjMKL6&^(Z_9t%-J9Fn zXh6vG{79y_{RiZ5@ctl=N74Kw(t(iDNo0N!-c$DESSLiP&1E?zVatykXG+)ttFT&b zC1=Xa%1`1n_4b>17W|R4c>6`9P$*dVV5}6Dof>dszXHqL`2-wqvHxI;)7rT&nwdT%gVfEiXd4qPJiZF{Y?rb`6sA*>qx$*Yj5?t&Rf4Ud7PG;qr8tNtx4?!+^=HJ>cX=bV%r-&z_c@*=79-;cS=V4U=S&{VtEX8 z5kmexb_w}o?A~mCSJT>if})r=xHcq?q>m^kR&Q|agShZ%f#@cpxCw_L$<%F#JEtG7 zsrwM7%P~V>@Ur$EvI=cEJ^#nI$M!2AD>>ylZUvp%7BsdyI77(qfBqdf%WB$&u1Lpd zh9tLj>t(PA{|@nOvZ}Q$53OHwl zmz@9Z{g`ht?iX`mC8Qh+oOGiWK5}Zt4_6~FC??nV&Px!KV5Gg_1ggS2f*T(vFF(Uj ze>1O(xxqD75YZMX#I2N`e@7byCWKhks^lusz6=wSntB@_b56IHM}R*TuMlwithdiJ zcHNoAp2520%D2M^q^8aXCpCj?&Rjj1(`jOn8L&|<+(*XX{B#hTPz8ro{PqaGb#!9B|DSM5(+lnu= znQyww#ZF1>6s8cR&?Q&!opJbN3_tu|r<=rtQ&v9Zwc-p4#}aqF0pTy_{o1A@>CsRU z?oaSmPGHmRlrLVz&WA1#@A<-$I+7wUk+-+lO*P@=gS?2QGL(J0Hw)7}{B-Pneq6TR zcw{JO_dg`A{bVdcD$?IP1(0=fGiv?KH=&lXTU&PE}x zSQvNt)LwNwG}MYLiH1@)KFtNh%_)fow{)8sS~JQc_W@1YEzCv}*)tRt$lriYe90kR zY4oM((J4ILc=48pD?&Vtkw@1FxKwy6W^xn3+fX{H;wBr$Ax#nF%xEc3bZ3}+3WYeY zW8-2%_GHQd?VomQmfVa;DH}c$E+6U@Zy!}0P3NMDY9f5nezH&PW=ehAJ zh)R&#BDx_I9L0DFr6iiZ-o9kLo1TRC4a3n) z-vx;i5_5sbOw$q*C!$}|uv?2NTsclwH7(u`n5HGL;BYHNH+_kToUNm2ca^B(a#O}3 z9ofajtZ9j=2ea7Y)%DyI&gj}#%S{;pl)izeKznKmFo2QHNr{PF6TOL?nhc;N$z`)! zir%??N(VV{L>}lQr*nRHPs{`-9R&BmUeH59#k^Ftgkl3}Jh390ooIUXkZ8n&-kl>f ztxtD-kXLedR-9n!Y(=9Odrk_L%)k*b$Z;gI?{IyRSEwM46N5sO{o*=AscHR(L(JeA z{jxU=y%d5F(}2!iclN+BG5v$k5VI-M^v=OFfXVTsU~uPR1}x&-PV8(BQBx8Jc{`^J zRa2l)jv1yFWD{B$-nmL{O6Q~zon&#;NTGbBn?`l65IcOdqC>55UgsK`Hm0+|_0LCB z88I>c0}^7O@Z9GOr}~@ zH7CY2LDM8fB74!COqz%aR0&JSO4Lh*_@{JGE8y9kO-;)o@thvwXib|sMzyCU!k4@0 zRNr*MG%dH29};(ACr50~P)$W^UZ=n&d1;RM+`tO@;@8YhHe{C;Hws}wgb?Je3p}3ji&%{!;CZfC&Fbz1RIlVx#yM%IUL~qO z8H{Rch|tV|s9r6`7QzHPQ8D0P5~|mTY9<1sr|lh#H9c|9;qI}q7y|HITMtN_C&73E zr*F?z_Q!jSIuPu+lMUlN(C7IhMGtJH;8Rw{Gy6p$A@j=xbYJVO?v!6Z$ z5;FRav_HfK5TB-x63sF86tEIMP;oTQJ~tiBb5%3Lz6@H7AF973_?>L0Lt618^@*aH zV_y%A$B)wUM02XW24aXGt&bI$r`g+4#{Wd0CYsaj`^ds1{h%0}XV(YOoUZ>MnkDv~ zP-T3sYRRlc|An+Y z3J0(*Cm0r%xC;8P)(BJW@6oI-@TAM^p}+ND;N*TV$YCvNAmwR~keaa)UxRGyF~1dk z-b4f6x9qWxiB?i#Z5&$T_KH>@u|Jr%GdGJ?YGNY$CjL^i`XqMe3RC0?!9=Ra&XFsm zCzgX&J6CFRXksM@vS;vcWAq=BxRtBV>;efG{l_IX$D=iOGsYYJCnuf_o3ZD~*7U@i zx!!!)Dop&8D=hu9z%mztq+eOH;f{eW{ZcS8aVC&-87SRNOZ+>0w96pne2IHNY?pMU zx5Q%*ZkNHFWc2qYt?G-`xg&wtqn~5+Pf9wAh=xeO*#Ka%yTO8yz=6Y9wVs1hc@ukF z1Qf|jDp$d1sATHoFjh+JDJ|C{R!Z!}VMc%23-)rYo0WL>6(|#L=dW`lQCgw_r%nvA z1JMFQ#iYk^VLq{6Ie|WeHt*07$V@p7D-L=q^&2U?YY>6FHKNX_a||}&t<^b>QRibw z)LXBbmc0a=dmHo{#VTIAJJ$5BP{AO{?t|FiU8_(9>|6Vzxj}hSYM>Dk^;p{RH#8xlxx-o!R*IWK}%+o=I(U7UBZQlfK^3U+=83|*Z+0^)P# z0khxP2fCA-L|AvSbA;M=t^=(p&b^=`;9Lqhb$1416~|ctPI@?x181s}4pH`WVC7mb z=K=8C+iA!6KF+P+-0dqpK~4L(%<0~;56p~tUkcm z1&IuFs)1*aGYY@codb}|V5b63cCK?3cp2i{2jd#*6k+Z#=dvJ9$4&`;k8m!8=Z$nm zpgzjE033~WE`x=f=j_JZG0yFv@OU6L)J)U(9@3b6$f<{Z(_; zKwWz@XB|k~t2u*Vo6l&@c_3h)=3EIXpVgdsVB&9@GZ(Zyr#Yh_zvngQQpo=AnzIK& z{x8k>9dz)5=A)nC<|$&lJ>C@^oo=KK-sy{{x66ePVk-PoCR%uuQ?X5{D5U4>wg0$g6Ij&c?eW* z(48m2`$paQE#_^~9S5x@-RT9HHS5k|h_yv`Mng(h=uSMiy;67HN9!uxnG9B1b?0Ib zf3@yBg4LtCvmBDYMt4R*JZ-wu7b3q_cjf`vb-L3JD{R)C@es%s-I)Xaex^I$gR<*& zry28Z(4AdygRMXY`}(==@Ot2ly0Zp!-lRMCz}Ror9W=CG=*~muYT7S#=L(Gc6-WYO zx9HAltguaYdIET>?u4PL+jK3Z6zp0)pK&#;(B@|8^BXGe+T53YNuo>cfs8EvKS0dB zWP|mT0uX5V0>)l6QW5EW-9=Swe4OkU&!b09ejjWncz#6`K9J(;VX&Uy=?PJ#WW$aM zeHq4RAh$087rsp6Juy|Y?*se3iK^*I4cBYFNvdU~E?lVjCaab=bpe}Ms+nZJ0Svw= zsu{2!fYJG~RWsEt#+tqy)$C*E!=HR1#eC4dANur7Rn0VeBizL|O*PZ)7a?Kabk!Vc z_knNta#eGr{V&S#Le(5&2f5G;)f{IpfeZNZ1gl2>4Es%3uP@&i2hMTkvj4`x1*(~2 zkL9{ERdagaYuJEqmeH~4=LPQPfFcFK@hA@>g*-TOY8S3^G8y}&b!hdzi$~ zP{`R-;~YhlW`Bk7l^O3q zan$`yl-*^j>9GfKTDfXkHvf$T-vZV2+7|+WZ=q@?1%8jf;;ZQ7Fc5fz)>7HYVIUwZ zqDnz<&-tspq)1bQxPz$rliaLx&6{y1W;F>WOFUWA1bU#+noY}-|EYv0li zQQSjj>N-S0srl-~NQlDDq~@2YUay@_oBFA0CfUCuGYyKFfZcZhnk$UeKww>+qcPR0l_%7O9fqNL`8F)y_r^Um1<_B zE~)_ct;S2>m^L+~KYF7^CW4F6KgV82i)%BAg|?>K(}?*xqeT#z7pR~CUN0r*fhY?D zmtvmp1_?279xM!uqrGpH5TgenuOjsLey-&05VDzgZd8!&gj`S2{Zc^!ghUDXm4c)Y z@)#nDZ<~U2BV-`8bE|?R6EcJJ|5`zk2-%L<;`@_=_zBt1pmDE)_z3wOh45zu=}Jh8 z2ax*}#7oE>T>SwBNdyFL6otJccxdJco>KfynKuaUbxOK{1C-4paz-M!)B>3_{>K## zaH$0*(6^pY5OAqUNj#|_;8F|RL?!H05OApleB|;e1p$|ul-4c<0he0fL|=^Atsvl1 z3;dLNcv?ZgrPi~)wnFp$RYAa|7D!=e-lHJkQVWbC7kd??3n5QobMrl;AT}Wh)YU!( zu?QJS89%Ea34~lpo&QZi;t9EfW1drxI703w=I0f}L&!i%{qG855|YMP{9g)U5K=_P zdR0Q=;Ln~wD)vv`YZ4L<$$J93ad7bMSF<2_PhbNfZz>2R?+I+DSG}bmkh~}G7D9pV zT?K*UJ<=}TR}e_v6S$rR@N=oe4iULh2M{pA>^1*Dw-MgXbR^G6<{XYC9refSE`v~>r~}&qZsEI zqyKcfD{1~#F_>q+M5?}5+ft$3g%+-vlHU?}j_{a22;t1Nk26LlnDSV0G2CbihNtX+ z+*4IlN@R5N_mPxoiN6O|{<9=DPa+BPpDkxwiCYlU{OT>;n_L%Js`-OT&Pjb>Z2rC- zn_~b=z0Tp&sPu;ndT)YfqVVTz2qA?$_EAg*E}}TRX2)zTa4RjWtAb!_)dKI5ZJ&Z* zT-lXkMb4 zsW#IrzDpJ2puL+aFEhtuO{0IB-AaSF%$y{e>2@;XQ@OH$q0-kEm?6QJzr|hj(lFP9lW}H~0n$zu1Y&2_BGtU+$ zfW@j=m|9o4Lh~(A%@X@YT2ifQ&b7tiV5w?eY>OSTPBkyH#im-XnickYTxgkUF0ymk zY*Z1b)?NY?`NB$8%k0%$Xoa$=u>Bg(r>o3ag8k)zSv;R!u8aj4$dz)NU85if1S zK@b{N1}u7IlY$^Ltd#Nf3dP+TdoJz$N^=F)Gy5ZdmEh?I77{#sYfbPl2qbtYfdtPr zus82mSV}p@ip;pK^${uWp8{|ee__;pVjhS1D@gHGri82oq`N1n&&Md8EC@|=9>rlt zcWPn$hO-x8!*seswjSp$95LdYO_&|;e2uedf-|QJ6HL1iQf=oA*jpFpuLy97&RN*9 zkhr@AJ7%)@e&qinj%CT&I==y=TnNXlK;uu4w>=b5GkKY=LV-OnwrSWu$4ho{qw4k8 zn`4{tb{%4Wa#;0R_M+Hk7xAemdAaKK+W%(nDzPZ?&GrDWk-Su`X_FGsXxk)w8 zwqIqlSvAkG4`adP7S#;eyj_!gh5C|`W?PVB@>P0RP?c^MQJzu7(NNpR!PltfaJ!K# zT&L!av>_@jd9!McvHwWXZP8Z?RO9S&qPkf>0Tu9lwJWSG`IidSbUTjP+NOUYdh;~@ z1n4$7B!qQ#YVxJ}ht%A9M3m$*B~Z;?j%bv8ndm|k)Vzy;k_d!FdNe=(?Y-n`{ZW8Y z!XU<*yj8Gmr^Bq0f3DWn>?DfbZ5sADh=|EIs$P#>4NvN5#@i2Z(VJASWq$`(=xBDq zw?u=t56_to9D0JM4!kFLK8FIjd%D#pK(@|WgkR115`jf`UWJhx&OZS$ondf%k8=@+7${`4Ub9AHK`W)lWPlR61*fE{v`r#kvGyq~d4G>xv$AS_PodZyq*SQE7x;l5E*XQuxqxCz_ z0e_P71MSSYtse!o3*%FqDKN5t^Av(tcjqkB9fucZdpKTL6H?DGrk>7?Sh1J$XRy%Q zvEYk+oNF-hEN3Dj*x616qS-ml<-iwtPIhR^YJ!eCGY0fVEM(P=~4Rp3c zjDwsS;7oTyfDCpvfzETCD-a2XI5`m4P-hLs40DFS0ERn#F=m7_3D`zD$(S|DnGC8% zJ8Pim^PE?~#Te&7&~v_X3=pKAA;_`L3m8AnabSz%op&JM3!JB*?+K0vV=^2Y^2u~Y zW9~#}1SB)bSpk}NYL0)XNIm}@n9IK=cAAo zQqM=A4y2xMht!aI9)iV@dcGP3QqO;ZdXRd47>0w?^F|a%J-0!2NIhQwD?sXbKV*p1 zGyl~zq@Ev17pdoG07U9}6_!Qnc^C*p>bU_pk$U!lVWgh#0cS`(e+gtrJ->qKNIjni z%8+_q134h|%nKz*JvUiIXI6RGF@PzqAd8z5h#o}*A8QqP~Fh1B!I5EfF; ztq1Co$>{tC8-)bphPBK3R(6Oej-M;EE*cVTTvJs*c@AoaW% zdO+$q_gs;Bz6BGIdTu};QqO+_EgN*F3x*)|ydN?{>iHfJfzbWlpq@I5VHj#Sv!dH=cPJ%#?dVUb1L+bf!xHMAF*MKCXo-08oQqP~G52@$hfe56Y zAAop}dY%cnAoct$ObMyy`RGIH`9YW(QqM(DBT~;rparStK~O(Z&r84X-RTd-{a$y@LIC-L?leO0f7G2$dvxb&(6U!|ZiN1x(VZy}@;=@9In?;9?rg(^ zzd;WW>vOth#e=iC&fo$FCh<=2<(%tA{ZdHP86sOA@d4Et`U7Z2b|P^bC~}6)7cFlx z-*p`I5jH9D1QvHj$i6`0F|go_l&#c6rZ1gQvehTCH>h<+%T_Sa3%;E5WGgN4X&8?) zMz+!uzlM)E6MpOA>O&JNAb2N3QZ_R2SEMsjw#Fnr#q}oFV;$Z;I7nKuuM@3|CvL=ND~s>ny6Khn`p(mD~i{k%{i=aX0$`XK7YA!yH; z#bvsCdUWp%r*a;JC1{Qw$IUVsR&O}hLjR_7J32j1tZ$U&as0$(15;LXWD(>0!_bMXO0S}e~Hcn4@H?i zgL1zN^x|g)f8pmax(5rg%EUU5fp)IITPE<%Kzs0~K&qFC6X|+R8p6Mf(7(_(pl$-) z{U}F4>O)HiKSnEk56{r&$k8!oW9Z<+goM82Ky%B{weqBxg_bxep3sH|IlQM-0RLwC z4Ok1yZ5T6HpiULa$pCDyz@4hIZyDMn1oB?`odWxzIU_0?8Z=$qb&D*62uOywR`no; zjQk7)ok-C}osaENe@UP{faRjl@|{389Tq-Xh~Y&__XU843Msr;jEUc(c^=g8GC3WC zbwtIB`NJB+n*Iu{!`yPs`tvuzQuS9Q$JeYKwzRPtP2xuHYGJuRpy_XpeHZ!}`x0$S z(l`%e1dZ!;ZHP_PF4H%Iw(Bii(!@H~kUoK~p0CX-06MR}3I_O75hBKop(1|J^?NaH zycqXA$BnPTcSrquMip(`_mG4BXI*Dr`2yxi^?Uhk?>vmSk66wFEBA|`0|xg(Z>H3Y zJ`jOQnr4PDnSMer83LXLgUk@pl*Tzx7}3C0nm$QDp$7_Zf<6Ki>z_!Bw}GioMqqmc z?7CsFKS6N2PKx&fcCMiMpTf2HvNHI2Y>oP1;SJwG)ENsS(7_Qg-q_;Jyo*x*R3|EP z%aI0Y8lSoC#hLt=KPD)@6zz$Ezb}OOXF*I8e+{7i zrD)%r!10>?mEg_>BbmRV=w;iCys~%%NINci&B*JECt*9#zZOj&v^p_?F8PgU??l+l zyfhx|Z`JU(7f)IkhCu(Nw?h7R!hSPb$(n4NkpqhdC6blz#rQ$~z8&=uG{YZsX@^JF zP5vB~H4VX$-{SQjJo|>g+D5>x$M)y19{iQaUngjRS=cbO4>4pCH!ppu$w=}sR@bJ` z>_(!Z`;DPPG5$`p$KH%z*)+68?D6V3kE7132cgXXOnnBe0<@;Sh)Obd5iIcxew6^j zMDDrz9+Av1MBk)En!eYd;(x)B_WfIYYnE5LR?=Lb*qvm=6@1Hkn&TE<_uqd4FNPNR~Q1F>5+z1z<#( z{L-k~9%V4A2SO@c#67}^V=2%?&wOC(28t#jYpQ!a%%^6dsZE=O&Fm^Xqk%?>^Iaj% zGWJfP=Us+H^z+Qc7?2YO&svL~vEQO&>?imY;@>w-=Ue&I-uShP)3ng*0FL0PLobq_ zK_ZvQc;_}RR$=5eV3ncH)Q0S2sH@cZkB(0pi8mAA`W*ea*exo=F=vZ*p$EI8UV+_6 zGq!k!3dgA6Zso-eFq+>m^a}Di6isb-LRSplu8U2K|1LK#dFP?06f2x7;_)AZ&#nY) zu-Fp+Abj>Fv@^uEDBH#s>s(se9}utcHpSk?21KDh2+YQoq``C2vCHM2d6`?X!DYt4>A~0wUmaSGg*T8ux>7TZDRu|B(CCOHsQ3 zL`+?T%0gBeP}$DPI#k|f7T!_T^}Ji*<#9igjiCMp zMxDjA^0mBgVGpS(9|NKz%_59n5#s#WD@ucR+hRFIB!I}!Ryz@BdAsQ>D9}J@LS~2KGqYkX49#Yd6!Dv&( zrl#vN55lKYbzygCEdw>l-Q$=cL~90wncOpu7L3*&5SQFrwY&uGlgoY*4{v_(39+n~ zGI(FYUq)E!F^zw`019q{N%kDA$SHvAdY&g68Z!|FUe7q}J6~7)7Dq0&hY#0AL>e1L z)YL7kjZ{>QXk67O0kt&?MpQ3cIHG3ExStHGt*MKw99CTy88K$~dBe|hN1r@(K}}fA zRme{6uEU<#SlPHj8xAw8U%ITmv2r+EO4Ay{<>BFrKp<)r6_r(}gTwHuWtEMnVrK)m zrXJNeO#@YK)g6F&;hLqDvR~oCq=u@6<3^7L6e}z$Z(Jm64VBfEE9KCok#M-oZDSDI zauC9D`9d|JwtiuGEs+DI;s6b(Lrj+}$yrOwmo2NQtCkJiq((coUIxy{PlB4dw6ZRu zCQ9l-LUnEZg7R99qFCx16g}_)Fp1Fco}uq=%os5t^RdXhYOC)ebEOrGm|NCc-JaVU zv1S+pQ>;hLbF8YqbGB@(9=+h!<+ob#EFdbIt0xO<&x8pH&pG_F4O_ z#}|$=!*h+ClzHYI>+z2|kA2=uv8v3a8IO4k^N4Qr*FCy#Rqv{?dvV zIo+*WXG}2bwwXO&Ggm)iHdtY6o|$5tubWG&%#^w2hV|Qi{p@3Am(8#LY|EF%fbLfJ z7UTTDv(`uZtS77irfmhy{MU@h0n;{$_5J4AR+Y8HnCh6}yNyDhd67}58{-3JH|sTP znVD#X%`R5hNO#P?8^%c8?DmM+m=UQq6RXCqYBDAS8YV^>C(ej8OsX~y#~A}b=W6TV zbLIh$b#TA&la$A1m{;pYntq%4{;Frp+v1I%0C~#(kF4tbADLII4x9gu+jP(JeXn0| z`-Cm)O?%Uy%nGZU+2fe`{<>pkz!;<7Xck%-=E2J$n=Zx(9k4;Vb$D$^s+9rQif%M^k>ZA-R5uBL3WMC0NrfYUNi4nV{JCQ z)T_r|jEj-e5pD=I3jTbUky91@khmGr{3@J z(SUS8e4t{vk>B0=(&(3Rt2z0Z?Z$aM%2z>~z-Kt1VNWVw;$SeI9m`y0(w2OrDK&9t`Uj=0t8J7L7v z#*h^ARu2d=e-3W;qj_CqA58Mq%Z(*8(0e?_5dG)YJYxv1vZPGBV7ZlP{(IePnRATv z6m#$~E62LQ`k8Tl_a^h&_0~4CuhCC8@6@fi5O~B`(tYuQuOddiV{Of}F1gLxa=rCz z#Yk&)v(c}IH6JuvA6b2uTem?FuW44sJR>8;dNXs*cJnXmp4t9}1+6v#)qa@71$uRE z=7cR+o0Yc-kQ>35qg>oUym^^7?Y^MnWHvl8a>VjK*^7zn+YyL2nVdKR+y z*IHDbhk&gWP@0)(4L2WOYu)|)g#Fu%u>m-Saej)q#Q^w)wbmmT@+eJXn?ZxvZCH<( zt(O}Ub@TbSN6gPIw=yPHEVm-VGHdVoV!Qd3Nd;ZCo;KNV>|68Ds$=G-z_k5!^LNH0 z)~)7MAi}(A9h`CgCi6`LK4AWO%|Y{Ss*adXt=U{X$NIv2C+?WJ+Bi=)ds}nOmBuI?+A|+mX+2VHOzS@0 z+-n?rWM(G3xDWooKi$E1eJkT}V?c_Tv<>b%7jzk8yCUWWP246}Y6Y!*X4neCF^uya zddtJ>4^EzX1A^>a)81^>J@fiKfBuIV9&UOw%0pct%WVEZhO)P^T&!A6V?mNx>|fW`rhE{foan(!jx zk1SYRxiE~HHg(}b6j(VJ%&%FAY6j?CxTw6QE(mN`qGFoP^M9mKSL0~-5DiD+_Uu&SoEQq>`?U}I%17O$)j@W$adU6t0A zFQ}~yhUimDHYTQmsU15mRDCc5^Z=j?C6~Rgc8m<+WFRz5^7S=CY6|AqqO36D+TVAy%yF@XFyq5n_S^NjO|P zQW=~Sm#tS3AtRL--53YC(yb3AALe!J+%*D&BhG$tnIfwJk^c(>7r@~jB z0e0$`|Eu=zLHEP<=`{Rb;s5^=PdX?7-hZbPE)RQTjGz)l_WziIzp=r#!2R>DTV zNjjbGn_^(gV2?h$h^ONjfoBY!@pvAGX--1Pgeit=_$Oda=$gL9@_Ib{w|HQF9Y6f0 zljXBoj455?re5I*HN{~o|^9SyY@r5i@_p;7Td^Qu^MJ&ohbG` zctEl!(5-8;0T4eM@LTp4NdW8vBa#J@u!m);tXnMkEiD!~#}2{+kztk}%euvqAKPMS;@A^-Kog4; zbYt}%DDq_0C4>X{4}0la2k*RZ&>s)x9!9~xc}BGh=6S{3LKfX*l^D;JRTm>ocMBep z$?|$xw^;IN5jWBo+YJl zpNV?J%kqvi31@lR06CuJ1ERjg!}3i9XL&E&ns``#CF&6`%kJqC&hi(c9`Ul&k&5Pc zmfb}?;$?Yw!eV@*fh+;&(_t6U=f4 z9vCx=v#}8n%yKdwfLVNl{g7amNkM^|1wT&_%(6cojArqu0<(Naf>|gQ7r87x1{Q~d zbzo>njqs_6#TPRB4PPY!FeHzAzdYy zB^8DxSzN8aEX7Aut@!t-KBmCWqAZazYhXD~$gGg!dscy2z97KGhf#c|z$|Sk%5Es~ z@sKK(g#ui-7)6OR{|1&9;{gx!gkRy)0Y|gEho2F&;*U@qS6~m$m9I(NG_ZUV5BOmb z5NaxBF+fy{2BR2?hxo>#oT%z7r{TepER@4F(8;8uL>lNE%|qnWt58N&eH+UARQ)ZK zAF29LlpBW1@hn^LfUaMmcuav={#}5J-$e190(*ubO5-7sEZgy5<_Q$b@Zv%6tthXS zQLAA;$~RSAQ$M?4SGmgLcD<__vIf z;Jlc3iigPRonZBQ!ESL^uuGOPmQhJ@KDH}D8y+PD`XQ?SMls7Lsyuvugq;P@#n@ED zH+Zd>`wRcg3qb#Z;!RoQ3)mO38V@n{7Gf;s>)8-lEk_|GTAU9N_I3n@!6@=%bry<+ zvbr3_EwcJ}4-9~;Ndv^aR*1ZK6N+ph^5U5&nq`$rh{q`sWBKk!7e@7dxa@G@rp04X zOqJD5D4vnk=TS&ME*=Zr%@O)5Zb0#ZtiFxnQ(0Zw4|jv{0530k`>Q^ja zQkd3?;ucxuw)wQIzJlVQtj>Vh72v_x#VD4^>d#U9MpplX;$vAI3%jfowpqLy1;Y=f zxe*6dH{hU3!==@tN)sI>Y_m8WfnhivKrcd3E~}dQp~bc&vUm1XDDL%(D$R+`1Sl1} zSg3OLn<#iS98l_Sj?mO>Dy^`ufKn0sXWlS?(xvb5A2jcu{)iTRO zPhs~!cw{jvw0`unpfw9PE3|3ASttUIEOwWei+NWH=P6?3p-gZFbbFZ(`5X^lN?Cp( z>lRC1ib3!|bdf(Cn56fa%w^;ICSL|9GTPOOr zi1JMR_sD(^%Uz-#@v`LoDZcoztPu5xm!-tf`GOa-hL>yIiU+!hK^GvpZzY(8!WLlp zQ#=^WVhtV;A7Hsnf?3?9z%1XAU>03R%h4=T@Bj%5#o{^kJzu48(BQ zhcq3+1I`01)iQlpUWkWqmTDdBbDdgI{Xv#BQWNPcmBfOvV3JwF64k;A6r2^~u$=Rum{ZI-qeX9VsAFKU zi=1*WM8gK>LlM#C{UUi!s*IO~L@)Iq$9Y7XzbJP1=K^GzGVx^LxfGB4!+n|`CVFBa z@o_%gvTAv{@3wvnxSR zwdr_zV@yAk?vFb!1#>u$^S{RPpUxkTBg;2<+(WI4moE4Y9$MG37&~y`G)=;3tu$4R zn~ul*!8d31eNUTNSTZ9NDx6iC8!FMtmX$ZGB4}!Mc6MGUt4J%0)I}OAD@GGoSd?2( zk`v0FnG@2=_yxSKUQ^#I(Os6GJGZQ~IHWaHh9eDiKowp@a52ziPcNHUSU9sdwhlnYqwE*M})&6&8jH zadD*VkgdU-n z63D)!2)Y)7v!`bj6^qNDWntK5ZFzO0VkCQdD0@apQ7Me44j;KY6<3m*2ODO1<&;(U zgO$e0um*#!hRxPg)Riq{}I6$lXKr!A{&XsoX*uho{W zEL&KM8?Ly!TGm*zx{`EEfp8m6>gY0Jbrws=3%+wP~nU$GJyCYC@ToTFhj*Ni%KYi1+`0*7^F!G$9G*27w>D!mm#=F-k@y6 zio8&ENf~SqT3E?HyPT6-kTa9QgQ%o!Q2#Knd|^J*v*BzZaFjb$1Pw^2Fb7CPoGF=7 zl$D#87n)j>3rmEsgbe8$GR~CdrR6MKR8w1l z8yuunN~E-aqzjjBsHt8QmOSI~3y7IkG_#b<(xlKlN!Hj4h(yM5&;#?K>`xw)gXmV2 zi(ml5!e2=h!<{gMV(3suSqUJ*#u2m|$SRpS4O6FxN~Bd)*Vk9z@)rk6T#O(k(^WW= zhBXDP83=T4jDum0o03~1%p|+Mw!R?;*RVBQFIim1Tj5%Gk%)K8Dl3=pmW;&BjSXBC z&eK+w)s`=)tOb}mVTT)lgK5+9Lh#l(8vdoQ%G&y6m6}?V7nRCznX9&bMPyl7xL(|3 zk7Z8H<<7*7kb;s_zyTuCLQWN`>nVV{!ISZPYHl93k+Mil1-!PV4%-)Q9&t&G6Oms; z6B+Oc$eS{gai>I5S`^9-<<1V}ASS?u^RwVg*wsWF)>h*md5VN9Mf}V!#@@mJ?^@~% z_>#0z(pg$mgdLnZC2FpclUtOJ&EO>4Ai2s{%cg}2;HTNHlgs_T6aB2xnI#ZEg1J@^ zSyo%K5cj3Zl%6n(doBIiRkGL@Vzzg8$DfW}4i>5*gyY5^X)Dg1HnTv{nN^&fn=3br zn!2ib#J-A#@)c#`R-%aRjnD<|xQV^IL^=evN*WICN)acnJ&Jv@I2(JU#{HoI7tjQ< zNFDDe;uau=x!Z7_2sQbztUS^p!y~tDws=TT##ONlE&)*4l$nU(A+4gOaT$&sWol(j z+y`Tr;bs7}W9W1o5Tr_7msx?!oAea?*&+^9;t~}6aQVXe2>!1X9j6u{=p1b!sT7z_ z_GA$SA#lcU2tc~Kz^LJZCk!5ceO0!o27j_4rJFSy5|^hep%W3VNS;sx38ewR)aIz8 zBOt`x;l$jON^)|ig^Eku%?pr|tWKSYuru%o%JE|R5%CH~5pG4Cf@78l(V@9=GZGzH zr6n_qg$**sLz!~-1`Y%X!7MhwGI>maICuh8=QeDyvk_2);vk7^oG=Ap1=tKJv-~XV z3?LcCR)(8?uvT{G<>GKFBdLhBwUt$2gm3Fv(h-nwvURYgf=+4)2_;$s#Lsws-X$m1(?5%@qZ-XmAvo zG(===t@8`B)yNlgbqzL+R0v9QYUQ*kYMoBL*lDc=x-(^Zf?j5g?~neOOpk(hb6Ty> z_XxLls0MptGLJ?T)?zUm$w0JL;NplLkm@JmhH@nBq*)EMKI>?gZRy(3(5`7g4>7lC z&`Z6uKWX;UswY>^Y>ZmBo_fr@9zEw4QbVfCd%yU|ODZEM&zQEb~;weE_Z2Ku!%wlG_JX0vECgB9%7TRE*NO{5Ag&YQ*Y zHuH_7yvmBGorqo#!?4Ocg=tjH)GgXNJm={FzUc1Kgw#gayt+%gLr+D~cginemx zRkOv>Ywaj-!3_3D8N-(Imeh7Z+9AdM#P%RdYSIhFQhs*$Z4R$ zP)0qlYf6zF))_q>M?*ek6$+tLsmW+)>y)daI01SrRhWlt4QF$7C`OhrQd7gJ4BaMI zzltaN&TL;=1(2cV#}*2Uq=2b?P(LxuL>c4;cwYXD!P1B$`wh;1jXWS}Qt@P7Rb5|` z?7O7JH62nvQ7T$KX6N=o(t<)y(nW3Xs8|~6>upwabm>vcWIo0KlI%j6QXbRwjKG49 zG!tlOs?6&<`h2ZNZndm1lhec?=Y(@gA%vY}mr#AyjU}S8_ZX>ql*X)kW*k-tqHq=_ zsy(Y_2SbwKHfcsxCaq~;V2L!~&iOsh)vuSFsYH(d-^RyY?19PqjB^{$> zs#Qr}HGD((gd}P<)8sr=)^1X~TI!l>8!Kgo=~mn|Liq`2L4R*Yn-id1Csa8x zQu%X;^6POx&ysoq3llQcLK>)Cg0lFeZpK3(S^xZYS(*d#)oJi;)8MPCy0nrXfg!J? z*-o2cmADuny}n_ZG#8bXw5ditYS60(Uy`S#pd?E2*t3wb#7-A`(Sq69lJVYO-c36y-gceBy}+u9Yb;N9o-ba(7N-<}5<3Ajlt5W6hud~|(Z=(K09QBnlICIySc%K|rVA%?rI7o}`!S@fL=UQOa0^qWJY_ZM zp`v)Hz@*UO<81Z$+z&UQp}DzXYVta%Xkx;Oamtm8<*4hss$`Rh;pU^)6;u(*mHuBM zB_mcdq#n*}o}`6_bW)V3redon%+zyQk1BOrM2x1Ih8b#Nx>wz!wT^zN4$-Q8v&nH7 zx}2^*=r1cymU1!1BvEK;s#DXNW(_<$rl+l~Q#Sa3-EE%U!?~HN!uOG!_;oXyq)*A0 zU34Van3ASm$jyfKw36d?qEg7cD7osBo+c}q^s-htZEdEcsmkZjyK1DWOF7F84qMlH zYBcNbZSB@%(ylSZkyD9bA{4NwqeX^iurdr_>eA8eBd_ty<~YR!!okG|<|k40G^Lt| zZ1^@!h~3>9E>yP@Dx0dujwzlK7x7%(84wMzf2+f5W=e*T})4xRe$Lv_LbdIL5}1rD{miU_s^3>WD=Hp7Awn zoZH(Z$7rP-@NGSPvRIQdEV(5Ma*8d?i!3T4E;ec6o}BC%E%TPc)Ii~`Bl(J&C21KAnq8PE!zqSUv@K2_dZT2j@= z^gz=}s{O=6WC=N&R%@$e?H{7+wsmwaOnOSG7Nkh3Z%+U%^({@P!}*$c+=^x^Wm&yP z>)Gl2XslB;@iu9B$0>LA7UBVKJ9bm4^)K+6V+W=}J`yky$6ZAeELl@aE>PWGa%2{D zO?Sztu`Dfn%g`d}eklZ6!qWn|@3g6I`d;Ccmb1~1q`RbS`4tmVBzq_ttE;E@g!o&{ zSPn?FD7C&l681_Mld!jwi4iDHu?%+)4?F$|uC&!#Dzj9M7 zJU3}}oZZ?tqqAKzHv_&JgF_B#jHJ0kNH-Mj_J+o(wYn#H zDdP6iiX_^S&2X(ME2`{*N|s4ED_3;XTeQ49XsVPr$*Y?i!tXZIJf|gC71W2aHGt&(wcA@G8mgG>$TFPMwFLwQbMGJ#WF_GiK%g<+7@4*`l2u7 zp+jqzb(Irh*}}t8*v7e9ps2+3h2)sgYP=?;p70SzFLHwk%fq^g+Zb*x`jJ~KtF*;= zEb2C?mL+!=vl}Pp?OfBVeMsTrDBfDGe&!2ANyo}!R7!tW$xr0LT3yP{T%SpHa^0n+ zQA6=ut-VI`re4D~bL3c3*J$BYlh%B_#zo^)v|ybq2kQ)SCfiRmXc*btNTUrGEqI;5 zMeTkP9lof3cn~YhwYP;#1cxuOX9l8w!W@8Y4gY6HlJLr*L5bwJt&K@(IMt-Y{lZ{ z6`as2*T}bA(#0Eykr*9L2a^XSKVMq*v`Xy+$jzgg%DPEOvm97hkaeq6@)dY5rX@de ztZK(J8jU8utC&QzrZX*5w=YhipuTL!Zsx89-7(vG2ugS4>)TNqi}}^^ z7N>nTw(hy5;<#E{KdB)!!lL1v`^D1CU63DfVTXJ;>QuA6x)zzIhQZl3e<19x7&oc#RGG=2t}>_f7hPZBR4mS?`IuS^NH()B zBX4RXJ)xmW8+0^}&TefxO3M|Y5EQ3f_mJFqY>l`$VwadWG4muHRSU<`*apHHO1?X` zYK0RsX^Gl2la{Pi;}dJtz3Lm{EpLTqJk8W$bR z#pqT&UHZ>pQ*|FLgmUV7_mDm~3&=`q&=glIccNS-^Q3laGB0RG$t~7m@#XEY7*LZt z0AqKKZY44qMUwPt$w@VBno?`+R}18!jHEtoTSnQD8&6|F%)Ii6JKxR{{;=2!CFgUGL+$yB9cj8yjC5X8q*sM1 zDD}pjIXal#kSSK~`zo&C6z@DHw?SirCI9YDZSt`8J6n#UsB`Hqb%XjYCGX14OFkNY zDuKM|#6XiK=cu=$Z^7l7cA2FinSBwy-9gt&?9uTZ&=Ff22X_MLeD_>8u7*jIvi6RS zUKD5dD~!sNnbby-t0PyglfH;=BwlEv%fu)eV{!8g?bFgcqkR_YS;eA?4n2`&HSZ4# z+f443SP$U}T4u}NOH?ddA;YdO>Ge19Oph9bWannsLbdB<0ElABt&i&lFnQG>WHbUyU$~ z@d8S>;^tm>Rx|AD)F|rqnYC&w*20dG`thLbwY9WW%iB1^@zCd%q?6(XOKj)d2P4Nw zZV>B^JggSS@USM;Z5C#Qg<+EAqXtHa3a-m<5RxvwpgXOk&F|4FKxk>T(xGZ6Y8#l; zLpwsFHe$6t8m~75L~%sRbR;{yTt4od)3m`>T8lR}mfWG+b?mZ9<(@WE7V`SbCQqEW z|L~ov!gZT$=#hKxj4_>!>R-~Wdk_cu66fWA^>uWOily37{wq|nQM3E|vr$sf7tAfR z&YtZeNCzV%_S2Ne(NjnD_4rh$zsIOO6um?olg>^-r76wvCe8dpnqEtf^)8rg=Z^9b z*-Ckl`(N+p%FkF`@i-Yw0UkXr;I9j$-*};P zJAb~DUXL1P>!c|0fAf=i1aO$PnM?BdYv`XJyzvfr%lXd#<=*ZsIsXmk5AWnJP4AJH zvTVG%7-3!$bWgf z2?{99-}*1>9Rnj${?^j5Jb!+uF+ay?OzzaXYKl)F4IZ1OW2NbBrMI&Me!tiMasyXhD` z=CP>)`Q^v1lbrwUL;w3fdW?ZMMtWoHy1n=g;zT{makMpZcI$mJRnG z{PJUWNiI$Aex>I=;rnnl^Yk9m-}yQEGuuPyjm`_bi_wVth~;q;(n{&O1s z_ZrN@FSuLJR^~#h^w)vqAw3#HK|=c860za#^Z z-a6TOoUur(_+0wyWqQgd+U0jRzO(4Jh5LSosO9e=Zm3NA9Z;V?fBkHtj;~aFzXQt0 zTO|8sI79W%@;u4;JDe={N%pTs|Au_-{=S$Ur||sUPL8kUk*!ktE_dgr^fxqm(qPEY z%(XoD8=ASr5B`Qmi!GIX_k+KonVxql`3=oVo<~yn&}{SU+LGgL2X~gqkC(|S%H&te zB@M>c+onwRi<T-=<6+ zT_#tS$u(tibD2D^O!k*{^PjK({WAH|GWpIj`N1-IMVaiEdgVW-U*Um*pXH6pWPesI z|M~b{WpY)STvsOh<1hKo=l7J!$CSw@mC1g;S^o3+=a

l*xCL$xoEYFPF(5m&xmu zOc}o3#%1!3W%8IZ`M@%HQkm>;$>l$%-%%!amB~xW&oOi%jBoZy%j8STAJ!d^YHH=vg$`^kYwK&xZzHZ4Q& zNy(kiCL`kPORc&f6 z#DdgnINRz&R&&%@llSFbaOY=ydL@cX>)9Li8IsRO=$;jzP%}bdTo*Yao&kt zyrkX`9vj||UeM9EB%Cy91ukPnA|fhEn|7(j-@Mzr;Qrz*^{zm*FuO(4BT&6_dsSUp zTi1?(l3UQ8-^D3h4t?!BNC|rj`hUGmUD8WvDan5C0nwU`T3=Md;DrXm@{Go#Y~J!2 z0nw}N^vYJ>+!qJauBKvxNnzfST}W-V=*3J)Y2U0izQk6Z6p;EuZ0pifyIz;|-iP#O zuWC|WL+#~A8PS5cpFoHc^Odk9xTu`NynUpb)5zi8+S}US-#brkbnZv{669@)_>`dc z50?~S6mz<<{4%b+d0d(!vG>ytVny|NCyDDXbw)jqIA0sW;u++~Vcr7<>q*;F+qG#u zU$IDoi@yIepa)Ll6lYyuqFOCq?kUm5NP0 zibGWX0QX=(8t^|0VZ~>d;y~I>pB_w!0M}t&h~Z1k>NGD`$eD19sdo_FE)J2Y zdcP^hLikeTn0&^^hwJqc4j-XcT$l=f-{D`=+qPs2Rcx!5v6xEdXwm6hX?Z)n3dHjE z{?>2eQx4xjUz|2~lwED^r1Utxu55`4IRI=EIX&A#zTQEmUWhWy;d+I~49g?*dJ~TK zIQ(m}6)nq`bE&EOxZdG-aUIuQ$`w_1Yb-^Ik)K5BUqy37!8hiWOsZeanhJ!Ls5v zar`ij&qAJOc^~QcmQ@ZX5Pqt|RSst&pJ!R|-mt8ApAx=?bTh}>LiF`^HFbQPsr*!N zydF6|^r(1q9Ikwx=WxlFnex-#hy0k2E8qUGuaE!3RJtEKT2O2#)9X)69Umn+ z{(i_4Ebp)KxBPW|sEhF99Ikk$A%EYp;{D9B(!a}8zVCOq?rVi*rT-G)uRC1%USIaI z!?%OuU^AR0`Z`OIPep#*JU}+Q&aL={UZ`mvC|{yDL~UnZb9|OHm}(1ieY{d{hchSW zHEa%7`~S%DMCtnLidFK7i2m|lyQy@RIDC>`x@~!T-LE-WZcB`)jJ3+t3SMI`D^M|mUq#6x=h6zx?YO6wRupM%`(*w`r&D!%j-6{+~F#p z$IU6SVb|Aj4I0Bu#oJ!2m?}TJW##|tW}V(zY3leC(Z`Q7>-Aw+Q~l^#gO7-clwy-udt?Q|;tKQ~B_R!p&jB6kqLf zXVK*}+Ely)9Io=3fm|>Ze=c0)<2vu#9A9SY{PP{I^R6QN=cda00f+CZ_pF*tdLJ*x zKQ(pUFd0Nne=Ae*cN5)S_eHMZcq8F6O{H@x;WwHplRF(gQlBnlHYiEH?9HS@uxZ3CG=5G2Pyu%gmal)S_e0Rn1_}C*lzXO)H)BD5C=^7^;uJXIV z)P4NI;kxfTk?*st_WG=4-SDl{AVmH{tC;ApKT@{qVdi=RO7v=cn^z?_n2kH`^41! zRewoT{!SNNp66RuIsMr3VfyO4Wu5=Bxu@P)|7G!TjpODKT2nB;nPrR2g8H>NORvl| zTeIv*(bs*!veMmsb5ZAaibG~=d@yzVWQXhc%VtBCeL?Qvinc5pF1r3kn~FEi;fgoI z++Fjq*{)Zyn#$*Mrt@YMl7g;jUvj@14IbMIYbUvc|UqOtqJ4hpW9DggnjiKDvL)N_T-} zop+|ImkI9)o1 z@9#vjTjP+qxAY-%ewIBb4(ZW+ZYrJk9ln?52esvjUe&v)_zTUWv+Q28PxFt)jEa7> zTT}J17i@&TGY7KlN9r4ncY~>Tcfrx>Bi7H37Tw-1v8;N$+f+Ti;&A2XZObaBJ+>7O zmycL<`#HkY@lJ>9`2Uzk=mr1g0=*mDT&Q$J$A8aM{BNjCeLt6ruBTf~h2QD$v8rdn zAF{0add#x!`B}nWFg4$N;Nz;__0&gw{+C7PV<*c>ceG`tx3^`*pG0`Q!)w)#kPox0 z>&&vOcwK}KI9&0LA^dp4mzip3wE_#`rFV{{x#%NmX)vh$O}y6XQ`>{ zf7jG~o^2|vOOdY^osYW-{{!LA68^TSbU$#ouIumYR-CNyTXZ@bTK=x)56enlUrdYi zPBB$(=Qv#F{mio3!xPBQn9AP^rtIeE`%q;bK&Li7I-i8SA$%xFTgk9XK?+Bbo?uD7q}m+f#IJ}I&+X0z?0xP@G^Ka zTn-#vcnyCvKSdY_l` z`mEF62yO%IM{#&1 zoD8Qz@Bi`fLtp`Rz%DodPl0E`bKno*PvMR5=kQK=FMJUG0X_+zg)hLr!8hPL@I&|+ z9I64*_puHf1~-FWfg|9Ka36R8oCs@S18jkZ!B#jIcEf(S1Rf7hhNr``;rZ}lcscwj zyb=B!-U;u855hmdC*ia31^74k27Cv82tR{EHP=Kr!eMYT_!T$;?g&T1z2JWEKv)f@ zz=Poocm!;Nov;TkfXBjb!&Bgy@ErI<_!D>~{29C%{u15;AApa*C*gDOMfe(g3w{7U zgKMmt%5gooG28+UhyGTB%X<{u8;*k$;X&|VI1?7&9M}y9;IZ&T7=A-t?=0l=;g6yH zh|bS-@K$&Syca$M?N4<4r{N0t3VZ{;3qOY0dg;8ipucS7bT)%q!ENC#a1XdIJP=NT zQ(-ea49@;UHAcqzOF-UxpI?}qoo-@_;1vv4K+JA4zq590$z z%EwSCZZ4N~Vfa-gZ;reT+yRb+V_^7M6@LP9Eo_7{U;%c)W8vBGV)!fg6nqu_6IMu9 zcYepgDezF(3FFIDigya~58##XHh3R=0=@{}hW~*ZY>=)y93BX#z?pC^TnNvA7r-mw zZSX$$1bh*`4J(GF>uw4Ug41Ce?1SMK)_tFa{1bQsyc<3O{{ml!AH%g}2)LZT40nK4 zunEqFN5k*H^WfF+c4+^w(_I1IfV-ucK^ z!JotX;gj$s_zv{8Uf<6!_*FO(PJxHQPPiDJ0)GIngtx)_;Ir^m_#Ui~0qE;*2zP__ zcRT!W*a?q?XTqPro8f)%Pw?;XW4QL0Qo3J;JHWkR6+9GnL4VT0`MDJS621pVd^sK8 z3s%Dg@FaLOycPOW4^DRlTm}CH*Oh_o<6FR;;688?Y=P~tAD##=fj7c?V0?f|>HGVR zzRo8wzV9e`bNk)J9pPA54Vz&b?1Lx4AHZwi9qwP8VZ%eo{+!s!U(_sf3fZu`NhnGUHNBF*f z4IhOo;41hpxUSX}9DfVwPkvb52Tp=5upRcp6XDtL5_l7Q0LC}slTw z@HBW9JRklTUJ0**x57K%z3?IU7b6Z zKsX6bh0X9VI2(4tUbqMz2Tz7)z;ob*@KSgUyb=BadfnLdazFe%d;&fTSHi!;H{tv6 zQ#f?nl-{~hux2z&wl4ZZ>2fgi%p;LsgXy6eDUa5K0a+y#z?W8paHb$GYW z8aM+U0o&k_@LTXZ@HF^6cpm%_ycAvyuZOq7+u^C=TC#v zIUf57RPIM2$9@9I#~}a0lzgwL^B;h}b#rbJ@9$>Cj11B+9k!`-&DHafD=rmI~~q}N0~~0A@VZhYvCQx`xJcs zpWt(Z{|)(dWba>ayrH`$u5Bv)(a3uvk4LUXo`u|jya0Y1USjHgu7D4lD#yQ?y54KZ z6}zSI4NQe^g1i;-_HZQOV@>6+lJExD!trl%yp!U!_PY@}r6a~Ryr)OlOLk%aGK>io&b(~;Yek3x?95la6W%Sz`ucoXp+Fm?P% zxPtIi@Lj_HZR&jQ6*ptwgz~wiWpNu*>Fk1B0}m&BE^-(0v2YnYkK-32Uy1xM^3(8D zQ`dhTZo0c!(;ihnNxD^}@w}U&u-QZ|A2JQ>T!SS#P*1$U0 z2%F(dcsQH|+u=Oe1$*HDTnv}O6W~ekRCoqF3!V!vfEU3_;1%#1cpbb6-UfdK?}E$W z{qQ092z(qq1)qV>!;n?(kQ-q$oCyzyvtT=%2fJV|9Ds}AQg{M937!hifM>yT z;RWy_cnQ1$UIVX#H^JNBui#y9IlLb}1RsHq!>8ag@Oiirz5-u^tIT!M`(VuXkUxT- z!c23QkFNpOhMRkQ(3-_oj1%LK$0Hw(JPUa#@(IWnAzy-g7xHrC=aE+;$M~e{<>S+u M4%dGNnpY=DoR)ah!6+_L>48>BpJv?76?`yhGeoxHj@bi7eoOi zMk>^;wQ6yxwHB;ex2kP};%=3?pjB(FOAAGc8;)i7;u~^?W>HkZw>(I}(MJL(*?CCxK>%Q|ny=Q#Z z+x=xw4U^Hy{(pWo8_lrJPZ@_cLL3S7se|WOUqd%pgKW$n> z+SriMH<~wFUWi(KCQNXXf=5|b+w1u)Tl%AG`|{lYk7IJfrgNj}iF_@+!E*BTnNB+V zaiY^X9MoNRTYd{n+q5_Bd-3LdK5RIOP3?Y`GSZ6=J<+gT%dw+xi`l=ts`t@N@2A2$ zX~?2Yq^B}qHB>(i6P$K|y(>1(Q_;%aLJ#T&q13omLuxitr}Y-P?bOACQ->k7+m+ql zo3LqbYVSwiJM)Z3w`cbs+Q)tZygk-mJbeMrQ0={sWcS0Tp6vdO^Hs`K{ZBo*UF2#1 zh3}_gxb&%Q_kM{%$AOwEFC-lMxId+%s{kYHAw8y<|`{8fC`R0p#;~u&2?Tz?E z4}S5;#*IovXQ&r8{n0$(<88Ty6KuXG%8^GE&z{1FP)6a{g*^!y;3-4~)J2Bb2#tndtbv@tM1EBZw z0ezd^pTew&D{wMGOLv+MSE-I(w0|lTCToS~=~x-B6tx_`<@0Xepun_!%i-=1H!kgQ zqhJ4(=HuQV9(q+AFi`%A<*3m@#7BuB2#~#jeS_jiBFcA9V};`4$mc~psVSRZgjooo zeW8{Ei@##`NZIl#SzR6&HKH%DuW#m-&r>$<(qe-m4)SL_QKSP-_d*DsJTqnUZyg;KbK)vG{saUqEX= zm)heTqt)IBW~@x9-4j$F>WHsZEm%Wp#mUe;C_Ae_btrG37Aaev)T}|)>Y`Z#>6565 z?JPmGRBz(80X1>c*QUJ-(b>-o+1=gA$Z@mK=Gyc6?1K{#;kFN{#`j^$!5oARZMSZ` zm*T6Ljr1Yav>WfGgQq}U!}j<@TgTYmz+3SudcI4=TXFRn(s)DNp}WVysjxH7N4C(n zX6(A5<#EQ2E6UdOCakAZ#oymb|1Hvo%Oa=-beeviWoabYkx( z4>A58nEN?LQtu-vnNflaB7g8=>jD`!Id}fArxq2X$Pw zczmN_IC`>Q|5n$PAp+spU|@*YO*+oPL7gvEZq*h#kj}%slLHgV5jWeq8F)0h$~ky;b0Tn5BcM(YU?^azH{C~ zRe_E1QjAZ!HPJT?*K9mE0_vPmCG*R-mx9+Ts`QM$uwW?F$-l}AJaA~Sjx_0it zH`r4PI|ec1JbmzCq&IBG`eC4dV#)mFfz!|z`-26IM8*}N2VU(Lq8Ja_NE4ov%0&ncT3 znx*&l20q$wd@Klacca%j&$0<*<3PjyLc<0|CWh1FDVx898to29=n0jL2tlP6SrR1m zaQQcwTJlDn?9B0lqxU;V8`9?gQ}mY7dhP9;-T7s#Zh1Xr%kxkh*ECMA!NAdRLPs9E zyT{`7pyqd6x#eEAd8ngr4(q_GI+N)G-!@#w#6V|=Q(>pyfpond z9O%joy+zUN{)1Q29|!;g>!nTar^gm+SgB!Md=ffoUsp@-6Mg1^1s~}(a#3Fb7G}jr zd<}^y_tWvJp*KH@<=}y%v`qJil>75z+q_e<`v-rzsY>YHAef}iVcdT!u zG0I5Ae${0u(>Fh9K~m7KlsQo)C7ptFr4TFiEym3-`&Oxh6!4TvBv9PrH%wnr5_20M zy(4T@!-D>K*cT3WG%J-PDagf?WWxyhnPbE_74*-5O5Y^h;Iv^tE-7h5QgRZdQ^EAu z7Lpw4HwKCv6|-O%_4x-Z7|5R{cEBv9M!Vy3TT@{0m=Q`HC0wl}UCNVc96dk|=sd=c zoC}kcI`$}ApUw$Y+EQK8aifjN$#yl5AEs+JHp@6QSvz|eQ!=#EGKR&RrqsABIFwZ# zNFOih+Tjy&Vy;kXViLwq<}j6wYE6n)Z7ZIPjC7keW{MD6%LxOe*rHQ&w2~9EjBG#q z#o`1ya~f5<;PL4L^1-L^rm!%`pl#j!I6$1s?GHMxi zXj~H@P8hW*IFPy!&i^ZP^YcS&&G~UnNANKB&%~|iPF!jM49_tr({v?vpd>IyA+Kp9 zY$D|v_6vx(-NTyOqUgHA(s06MdJ^x4DXwaque#@jsnkoMlbd*3kAmD6pTpZAwodL# zSd?oKGPt+u+w-9UYZ`LT#Ick6QZ2g`E#&Ug0$wj}FVnZ%(U08Q{sdVQCLjX3G7%Zv z-){$Jm^;z64z+V%#qqZ#tzJ-J=sk!Rn012ko{!uKqm9wvx+b{2S3xqt64K*c2@4XA5;EEQCdqUmQ@vRz zA>n8t)4X>>eZnz9rhCUx)v-d3@t(`PV}#7`-h`$}I9|w!-d371R>&#d<51Ux3?Zj^ z?;Htoym2Dd<*o@cy)VMo2@{QMP3CyHz)qMXHJax=89q;#D&#`%$J9K{ctO{9vG)x$ zPQpy%6ipU*|Bl8?$TmteS?GP3s%9A{Y0X96SLmy`Mv*3qy^XBGsm8lnxWs!7ttvMD zqseOTKUkxnkhR_mnYu*C)4f|sE){Z>_i~aYMyAeN?|q({%f#j;@6j})!YI|{wy5D} zqR%GW_n#%j_7WSZ5e1?Webh9TUvxBfY zBmRLR$Yr0<+%p{RWN_<1_$Zs`)@qib$0nYpD_#k%r}PtK_GDnpc|7Orrac$Huby+s zMz2a*g*Nb0ijG1joW4Z_=|k@fyEQyX^Uzk_oLhBTa?&xV zqW2^=iEBb?Qa?NIJf3a1CZr|Zj-tJbwreUq=?bQu@?%YnNjjY+~;ge;kC0z?Mhfk4KO6sBH z3C!f0keo7{X;WuHrP~;b+NW%0@`*O%cref~^rq`^_;2`h-g@qZ`N>H~1)(B!O=P`F zN@tU@HFiQ<($RK5b?cInj-i-q0(-|O+>P`k9UlcI{Q)&g8Y{se=@6=tl)(hV28ilR zFQFGEjV~wjbaad4X#toyDhdZ>Bu9)bV0k~n&`)mG_lz-Z=ncs&2IUxIGSM57+lBOa zXP|1yoyHbjO0xG$l$pFvhJLDdDtdPE`JyV#`vIzwyivwYy8o|;K*<*yF-MK@o6Nq$ z=D3b?O&H^^gJsEAiOd*sMq#ui|42B;l9LBFCSNa{W5}t7vB^7yb2K?z_a@&goOE#D zkdwem^T21xw;J0~fsx50PJ9X;NV*wL8Zk{8KDDz)jhIe8s-N1{9#tc<21aKe`KO_4 zjF@o^Zbzp2BFCayy48FQPTwhjc3-2@ce*gzd`+3!p`N4wGW(isjmgS26P59u^%``I zcKgou*0glgl3FV|%|3Mc{wZ@~njI`#V^NzASNcCH9fS+bzA*@DQ z^(e)%u%=c=S$~4gbn8n<9&I5}9b;v}>SL{|QTiC`XyiK1^24^{tus;LSZft5$*>-S zE5})La6jHE#n_!-%|Paf*6$&oX*DBtlJzBgIN5p~|4*^LKs;KQY~2Mr=UWCeFR%{4wuRQ6@WUeOE|hYLbvyE&YK?>>nkW-)-J`5`Vd*2v zdIlLERn{+2-d<(>4wZOJS>r%GuB?T~{DiVj1NEe`#zVwhwO)xbuH@fzOrsY2_Goy0u=k9vW|fx{{cYSN6PvEeD<-jrh)oISyRzipDJq+ z>i3zll9Az`$~qb4eU1!(FO;teX|KgbT_ zzfo2({Bl@X_apm8!}=ULFEp$-knbYH+5>8nVJ(HvHXGKTQ0x}Nx*2u2*sy+t+FoK< zGa-!{Cex-$K{f@RT#+!?t;tNRSGrZrRJ$;2jPW0Z4Zs98u za*DSW755bjIn8?#+SwNra;EpE^y3mCbG#p+!F@}Goae2g86~=^t_cghm!cc_N?q$v zb1YxH%V<@ZkOkf?EVo?9V*fAD2Ykz1GvOh<+$ixsK!Hl(V7*ZSmvT}{bU#m5zfNCP zxhBGwqkf3?O!h5z?WL0+qi4VGO1F z&U9@>ZM<$O3%Tr7r1Bo3vQ`fG3^Qi3x_n7b|ozKHM{oH`W`fPwXenX zTR7i)kQTJYT(OXqX^XjnUh}nUNw~uMPj-_INlo^i&&E7k$W(71Rdq^b(!4LT=IdN- z=m4$>>E83Hsz=BSuM3v=)=S$7wN}FS1fmPwJVt>EN=D3a`=l2-hzN^LG7CCv;bB%CDlQWZp z=EuTGBWDUZ*9pf@&Txc0-wnbUMb01S(w_)tBsp2M|7PK&l5-%hbaTZt>hEylD)Fv=8-4Sj zog)dgRQ|`=`F|riP)p^XLe6i6gIX%v6TcGGJ48wSK`!8Zy`)y7FJn!~@!145oUH73 z^KSpEEbC3-!1HdqU;ITl@Vwjq1$*4v!hz@A-Wyr3cU+lz40*i&qTAn-A(iZPv&H}B zve)^k-sLRfpp39I?_<>VcOld5AaO{d!Wi%835;az%J;Erh939x>=5#aYmO!tdheujK9vBo*!w)g-amyb@V><% z^|^~J!65MqYW_+pSmHfEtGj8&|twzy^F=B=PQQDhq&V?xIh6myNTIWFuVmH$3+{33&p zr@YTGxTl%6huq%VsbsW}9$Ehgne2U!ef%gPQ@tm14oo)#+Pi69zE0vhTF7+xU;({y z0%L;5q_+~?JS$7{vBJlgOdYiq)kyYbn%j|(9`3?(5mQ!7>7Ae^>jZXH4+r-YalbxB zz=WE{?7kDs708|Fz8e1@>-H@&U&PHAF62%zxd|TAh_#k^6PaC6Oeu@C7B%WQaMFFV z%#Em3dV7cR%{J}XL>SQ6syYqGVIE1l%zd*>;bQqLt-Ub^v?KQ_&dwH6$Rn`xZOIDs!wRr+5!CfP|$7OtS~$YBN)(&h-A0alXzxQIk2| z{p{uSLeBG6>IIUJ3)9!mLQ6H6O%USbj|Xa48j0r$yki(KnuIL&UdedUEM$pSPtj)y zS&`lrS*Lt!gsk>{#tzvcWUW`vN3BAh?$uLRn~c&h!3){rwVi1?)E`;KU};JszAyH+P)0C9}Pa4)vD0f*K z;bhag4ji{t00V|uW05<-dJDcvv>rmy9_w*L7_T)Fd52q*;jtu3A^apmZED6>RLdi2 z!+Ht2UDiqnnAV>$n%ve(t(s4C1bKpxs%v5#uS_KBypS>C)mRbr)HC2qcN2##~M7ZcI`E^i_EQHWt7siM-Ar9 zNX78QJ^64OPrt{Vfegk^w7l8_{&-G<#tjso(6w3_J1I3W^IRllwlklaWL!dPCgUal zKY=m1F4_aTjb?a5jr$y)GAeaxIEIHhE}xBMryEytAZ0T)|sE=ES<_POoeT&p!!-@ps}Rc4hL+IKTCmjgC3TOutL}s2}nz=vu!4egTo}GUzmR>$SuVl^v$NyEBpK+Tos6*WMDNJTova8N2yp z4zUv?m88v5e3zz%rccF0Qky@a{JkG zbG{E%ePG>>%Xme%<6MV6iS23bxa@*Cr;F52DRtxE7M^E}!+z+FWd^OMD^Cn}NVN?JUU~d)hjhJYK7QFzx`Rq22;pPQg#%d$;W*Cb;a3RSp z22D>z_Umx%0qd&cojPu29r@&H0eket6tp0;kRyp7qwf^RW_|@S^F#c%C+z`uw zm!3uZ9wB(PTpi{tsS_*C&$=Gv0B|aJ8}CAu1&ZO zp%A;LuV8ohB`&S`R@^*=%UBtw`5|FWrM>u^x`NT*2gW||YcWWl2aX@>xMBxg@o%tZ zzKK9=Tw(YBkIsiNr!WRRsf}5Me7kY+1>bU=mqY0Z8dCulgeNkBG-}~H!MPW4`v<`6 z49D^Y3jY?Y#hgctrqht^C`jct;pW%Sx%d$IEgVFP!JiQBMnr2RnRhw+ej9VxZL}3P z#)dbMX`tSVZUa;5oKLqegp$*7851at(*E55Hv4`LnfO__oqTxSoU9?_)Vz*#%a8DKZ) zQImiOQOI(38Z4*^WRafLZq#wDkI6bp-lQYwJ)ny@L~hoDDag6xEfi?nW`v+Qb1LY} zvG{KhA8ws82X|i}i;T>59&~YB#{1653>eR&qDHfAs6u<+fK_4%WVViX3~kbe_JC(w za+bE_4$=&kYjhp|NRstv(e;>s>S{Y%Z9A92kaTn$<3~mg6lb1E6K8@kwHbFy7|x2B z{Bs@37B%5s!r0aemN1NMW$KU+rj}AIj;EDzkzuQR0K|aGeM}OS2XH@Fr9!y*mP&Mx zN8kbDZC$IKxV;zSs07tnJi+N&e_;pd0c(M7nRhrM-XO{PzsqLiBdP^-&U@?|#vI*L2T9Vpxw@$m5p$%I+sz{4$-8En zfg3&#dzQXo&Wk>q?Ws9+lWVp=IAhb>X4WTAJk|f}mFD#q?24Xx$L`Nc7I|(o&)oH? zIsFE+YN0uOq1m%=vst_3)9EvQ4d#CH9Q^Y{&EzM|=t46&%go&$UDR}kYrMb2Y<{=- z5w~bs26M}X{pRz=C+6|4 z#l}Ns2U_GODx%{4YJ>$(? z8=~e*uyXf?ESU17Ief|5J05y^mU;CC&q6R3mON#ST4=UCXpX4$tTa)F1&yv0M32nO z%&sm~8g6b`-QJV2F5Hz-*WTIL-4Tt{k5gG$GvWq#W`oL%s(cyo&25btnO#{3Iu0jN zKRw*h5oxPuQnX!C!>Xn&yt*Yq4u<2Jj8?m>aj|^)t@ZOWCTDg{9v)-Gln<~_N^7_+ zCRq@1EQ`si0bZQS&Ny~VbhuilqeQ47+!YPgwX}CdLXN&jeFlO?3!uGC%(7*>TH4qB z53>K&9f;-d%lwQ$XJ>mSTx~~B+U2+uU&CDIeA>yE;Z`LHizJ~B9s){Z94h&DwWrL+X|u;SOV3}u|> zNp`!rmPx09^1((*<@!8ZTzMmg6<~LP8B%{T@P9TgC(X&T3OsJP9exq=IBEUh?;4VZ z{jmOUdwEM-THz&T@M8C-VX^WM#xWnq^g24Z>$@+GPa7Sb+|FGVmzKB5eKAy>c}#kG;U{xp)N;C<7S{}NWKiv{BXJ733T!WHw`Pi z*bOg$=h(%ydOaA9OyQ8g}?};O}O_E**{#W8!K%4lK~iqi?YNC_PvM5elb*bE_jCGMp%DV;r}o$W+&F! z_a5S1`hK9ORiJm`8j{^+RU$!u`tkoBT+~Q>)V}u+c`6fcP(OGt==2@Q#6RMKcEa15 z-JM1}WU~n;+Zxh{`M4lW5XDaCRs9h4YtbEPM9DUWXv^+6l59qt?36g!45-r|j+(Qz z-l&_{W#4;aBheoCws**5Nl*4wJ7LB@zJhWk#A|{xF)l#-jr|;1C2JQ`2Mc}gyT0nFo8`y-Q z8W;#hYOPT>(Qn^-h&=C!uLNZ$;X+FiF4MPFmjft?0vylG1UXByDh5)QJE;XoS!$$5wCdHRV*~fJH4vqLC4@)D=6j37Iwg8)O zp|FX+ve|^8isyq@qLVAS0etQOH!;(-_N~(w_M!B*a3Pf-rS>qB6xG8VqQA$<#_3`Y zE>@EGsD1At@=Phdl9b)2(|2ebhIG`1FjSN?%}AXcg8}Hb?>$5wIK``_>~hW9q45md zLoK0Ev%5V+W&_(XJT8};xkW2xANv!R?qPbJ&c1>mT2lwK#v)N%u4Lv~rE@JONUpSj zT(NOjjbz*Eihzl9%6c7Tov2k*RRi3*tSV}{&%R~7p0RIf^8x#IE6lz@ z*S6{gDLY1|@6cF}Qyf&B(1?qoL}mlqF?$+vWZ}YS zTLOsMk{x_UTndQQFcay&(V|s<2Gl_Wrcx(!;g*@6v2Q;G_;pEDX9Mg)V_m)k*~_%1 ziqjy-w~x`MJ4bp@&MKO_u#Mv_!$M(fMx>pqh(cAG;D3Dwo=SnV=7xNsyU&WVPkd30B;X)Iz z*yFYSmyu;?!l!4AMjE8-b3WUVZ4thdr+tE&^Q+9 zP(?UFM2V#~n@}rkBDKX8d<@7jnpMHq&)3?wPRDu^#bj#M3aYHIZwJ)GBGnrZ9IsQC zQ*g0;J0KYAs@;0sMg27s@g_A6HgN(MZSRbPI>ON={jgAehs0Um3T()equ2 zBdzUgBcX=omWX~trgI!|H>{s&*$TsLIA#mi$Lr!#9-SD44Y35?aJQ}>82I7+%GoYABLlb__1fKXEaX+pfN7%{h+v?&K^7vmTa6|j8dMut0 zpZaY}>2B_ruw=vs^Rax`7n~1Qe$#RN5EqwjT;~VYj>G+bOXu>W3|9p%KDcr|FC(;b zD(OeaeiE1Sc@;c{eTV;+$T{i!@;c*N6RsXy&gZ}JXT{0S!F~0ReE&;2^OeNq%Ry9Z zz}1Ya1();rZ~T)WHy>Bs5c&U$zbsDvL);&Su*Zk(O}L!Tf8&3QJd|IJ>oeRRh5XKk z`Tm!5=Hp9H&gYMaFpM%Y(PwAlVrb&m=bX>b^!J9OmseCT4FoEd)dU083PfRkettvbf?!!ijW(_{P@TIpuu?I6Aku`on%X;~tGgSh2Xd9UD*ypi8Y(R65C8l3=w8g-Y^6rGcs{Xs*(aJ3>(y!Mt!+OSrL1ROc55 z@|RXu*1!*Kk)Eh(iL^B$x;NLig>+zNokHym4anXR?hLo$oUc=LL^`|LaR7*i9rj5j zp16d%n$L+)X&&0HEU<#NrMb1L3;qc4OPD&sl3SQt1)o%utVFI(90j(9qjgP8s42@Y zFDYT|meiD1zyWylf^tJ4KBN(!)>a29ORECa)xqi#)C{@uD_0_GRiI*NF3GY0TpFk< zudJp~t6SD+yYS{pOSl7_ha$!Kxu`ZA7%W^#IYY;LQM^w=}Tk>^G2z`Ca9mio>}+kcyqP(VSTBv2iwDXY#cVwcM+uT}M! zFykhqZ%;YMR)x`(UkvL4mFQ5hiFD{BjQY@W)!5!%-__hGg5Nd$LoZroUS6=eG>AHP zb+0}v#OG=%+N8U7MdzjUAYB{>x)nW zTCsgycSi`{QOYkbt$_2ZLcy}aa{cg66r+tX&C~y(Pc25K`yh<=AelG$>tKg|S(Qw&co3_oYZroi?@*LTY(1utMBd-+|YO>zlheTEgo?bUl=- zhR*g@-BkBqXy}!1F64h=apH3p2zXnpY4+_^NiI0y%oL z>*x_E)A#7$tGgTZ0@F#(t*I`r(w)u@T;QW87FL#*GNy#=fQfzqKKeYmSBYwj8}iNV zh<$h|C=_aKuSa`gxJJWuO(8txU=|55x^-A01E|D1gzA#=vZ7!?mEyx5#5UE9M?P!^ z=FBTcgbQGdqTeC#s}?>LiiR6ic}En5cEP&3=8onF9NmP+)@_PQ$btS@R$dq^LHMJp zieN=RB7H3Ou*uQXe9VmyhOnZ$h`5+RQfDl$C_(%k&#0Cb=Zr(DGEfw#t-yre7UBEu=QOqB1p|sypl?91P`taMGFTnR%g=`UTl^O55!r0fW4tMFgVL}V$OJLEH5^S}3=%uQmy|WGv{xD{#2yxjC z9I8h*6;~*-rYWjmJux6K*EV;e1L`=2>Y<-BV}S!;mxKcvKyezESV7B5WPMOkPA$dN zl`BzknvF4D5GX4yhvy@Jj1H2^~3*!*X=UQnAbLlV;tSSf;=GK(x z0gzj@lr3w|gRo3@9E>;}Mp`16b%s2TM!&7XY*SVpD09|Tr1w|Y0--KOV6ytoqS#3=3v*F{tt zR$Ew5%EE`i5%WQ;>v5$K?F_edwP4a=xhrymSU0bv&zn1C3Rzi&`38f#DzBtGeK>4Jw zFpdi?y5{*cl`tJ$Hr%3XiZ^;S&S+|Hjm&6kZfuISx3tfI`vBQ&ftV$|JT0y ztm%W_CYp}CSeM#9FRrMmEYblex29IF_~_y4Tts_&j;*W>>40HR$@c1lB7=RRm+W{F zEpsb>@@U93t3wc{c__!iG~_HR?ci8|!isaTaty#HXo0G@mgK)uAZBR z6>P9bVF-jf?MMX|a_Pp|Ot(Jb4+B+OJLhn=868|)fR3gY<#Tgv3pk6H1WOULuu$Te z#gR`**mtx+I&8%Swz6`z5~4dL(BJej7NreLwse_HxF`cjTnF3J1!5I83}96UYO4#e zbAmuac+J2v^`YURR?y^fkRc3Dja- z7M0axgev|JjU%$Yq-Ns zN0DXK!NMT+16ZEWUOn$r;jcl&da3R}XmNYAhU&x7Fa=`^24{uXg?Ek6Q|wioy^sxI zHMiCtJe7s{vu5U;RFPYWaENKd*;t?(qec;Iy6Vs{v9ZIrOG2-GL}#=;ip?;JW_S-^ zC9x7&>mto-?LZYD2kl0wDlT79Q&v;O5TG#NP>g*HVQ0{7#@$<0@U#F`HFwAqj0Lz| zfv#?D!Xunp?K25XoWkisyui-aKC-B)Dp@{T?*y&~f zk!%}g+mK_!9E$Q(rm!TpsK^chRW(%=*f1*@I`C0PdlwdnozZT1!`TuPL>j`~Ezwdv z-$9AqagO8vI)VIr z#H8G^U^Ttw?4)Ar0(2luXLy4XEl*ACjDgDPlH9yN3Hid7#aVTwj955O&wE(b+G{4I z`x*X2m*SEeTTH#Jl_e8L^T1++vyt6ZP$J!~n-;5+s{G1ep6+6yHpceVVZEiMU3vqI zZ6}T7VG3FR6LK}S_7%lgc^vt;8nVTK63XJB0v)@qv!%hF3!GCio@zLuTBZ=r^VKVH z9EGxRc!P5@%tO(&Ax!!#T-Vz^p|Tg|c<-wT16>aloHJA^v~_I6>u9R~8x*M!8yMYX z6&=EA0`p-@cdIlj20?x$8WM9}+rUg2;vy7Y#9Ee3vzi-L9g1L*vtiU;DGlUS)l>#b z?X?+1xlGpcb6s0hPmelMVo`+?HLSdGRzne;l2=}^(vBtJx;5D8*s~&rww@!|w9b+p zzR*F%j^5nuW4ECvF$8gYJ;E*!a?W|UI~&;6vQx)(_X6}-eWp>Rnh>fn@LH5JwN^LHfO9!t(H>hUAA2b-i930)V$USA>`4S;Q48`ctOR459Tp9X+-Tr7 zws5OHg&LS;R=3yVl#cGP1LNS?pM_TAz=KhO-I0eL`c#Su@PAEd`SL({VIdaMkq!yA z^r1|ZP$|JOwwG9elRES{oSPtsVNR~=Y}Wf=d$Cev zw+=Ch=xxy1-Octkjm99NFiH&Si82rnQks*V)&q&{{nK zI&CiwLX}&Z8=5icw6$Y*qJvei6vw*xLA}W4F%Qob^ddMm*>Q!&^4Q*$ION8J&tp@) zOGIdP9LcF(_b64ApFcliN`YQ?+pB`X6fBiD7<<#tCd9&o1>4d;%KgNklxO$)SaD`J($di&)vWSXGb|=Kzv$9_i8TF zQ1(D+IH1PqSl0 zoCkGyUaIhhLF_YcEx!JXOneuU`T1;*54SRfb{@#R>L>u8ALkk1iMXfy|0OpQGSu&U zsE@zM>U^BEJTRPlrj5f_nE9aB`8a8(fDvDh#pmJanq}96K5**6cN(2M)UoztJlQ)! zxn)R;*Z05=?0V5Jte>OrOx#o7EL{9NzKB09Ht=B@uU0`vt{(<3h%5 z$tTV)PTKE9j{S?DPw>KQ!%_A<|EC6H68PSBAf#+j{p+VG?smBg2$^k0NyeOZ6{BwnAV3vcAaF&upm8}y0iyVb{s;}gwT zt!%D2s05bB(g!}KihJA*wi$~iwv369z`mA&D;t*!`u)IFxZrk8PX_kmVmmWE{$ujx zq_~f%k`%hT{tEGBK+01OU!dG7G$8gdb?Gq@_Tlkx+{aXLk8{B{b&nblFtxSubnFFU z%`_DPNZiL%qZPk+#t+}w9tHavHD&+Db~}3r-7|#l9YX(j2>r7m^qruc_xf4hb3@YE zkDU+8f5#z!q(8uwfetqT$oyXcoe$H&QqKGTOy?Knoe$IbcV?Uq>6t_5c|+(^htNes z=&B*~YS25;zMMB${<%Za`CSUhBlcnW32}p$^k~q0tFjaKERTP8$N4b*B+z{8k#Dpxy>du;Xb9an zgg$2o&2QQ}AL{3qMV$}n%ZJeXyDZL!>30pGpB_T*Cyilw1CaI}0`9~h=XV}R4+A>i zaUeYowDY0<*!euZ11YCmM|x=WU8nd*c&6>_2L~N=b%h)7x)vYVU~P=U9;_U(dBT=J zpGEQfKyRoD_49!$`%!|y4m{J3%HGpH#yi5hVWChDSEqAxY<2ejtiBF4 z(o4(uCp`AOEqCN6}b$myNW$x)3&ziO^>MLzEf{EV`pkZ4{bv_ zrFBg-g69mVXI;m7JMWQ?Ss{UcwgjJY4VT79@}JzxI7lXv}u4v*C%wlvPFxFxsE8}bUBW*+hN zxq*~#J9W@O6MoPIL&k;04%dY)ECO8^$5ePp`1R4wQ zwj2@m7m^P@uN8U&>4kV`9^w?VH*vgD=Mv!${(>oy zKb%e6MVtsf0cp=)h^XHeLYr8yvfK<}KK6@1_Otm!*i|U${81h1JBtWA+KI5^9O4wr zUxHT(|5_mR+)hNf_mPis`16|7^E$BrKP@fvDVV#ozk&2`4H5o5n>bIYjZBAsdx`Mx z4~fuw3)A7JpA+HVJIIHB?;{QWK1CXGFOx?3?~-1OAF3vee20nfFMm3l^-3qAUKvEx z>qH{#Ehb`It_RY8ml1K@KtA;L6XCzd$Va_jA;N$BODRlu;hy@uMCeZeQf@2}GAEJ` zxl$s^=_aDwONsE)RYJc`#5hSDVaw^Co`GMMfTmwgBSPP5rlWpm3EfQ^e%(xjUw0DW z*E@*t+pmE1+e4(`x93Ph&ugS%*WXAl#&3C(hF%u}ApMp~gx^LJQLp2OsOL-~?4L(G z9zOyDq~G*!aY64Ddu`nWZqpGOiw9|NTPR3dyc zmwd=Ck@Qx!Hlc4NBCdP|G>Q>Nu?S*$4M6&-lL))E5mC;mF5m>bZAt`PO@5(L z2{6eRX7AmNG<)w$98EqDO{M1pgnW%K4L_TS^|_?O1T8mTFjo*JX@0rja>07RHG&<2 z=L%jdxI^$d!Ji4!A}L1VcU}=c)Z{Q!7Rb~fSy2CE3+NR>HwbnMZWg>k@Fqd7x2dOJ z@OeSDKl%J!SK>bf4b!Gm1oiI>A-!Gba|E{t?hyQm;2nYw3O*^w--={8?+Sh*sN6Q+ zCpboMs^C1qLcwam)q)*@{4OH(Unclt!Ji58H(HtgsNf$2|19{Cpa)}sa(+R+sZV-= zV69+-;JJbq3+@oSL2$R=!-CHUz9x83@Jqo&3`CZ9wBU(?iv-IB!-8FcmkI6^+$Z>s z;Kzc81xH})vYau3GX&=dE)dKWED|ggk z>jd>T96{eEG=El$>Gufo`+ubS1s@lDR`3PER|Ve`d{^-Af*%QfF8Cio{scAkCkc)c zJX(f`x*mg4KfjgFBR4E!Zr`AMhf7o!|z+ErOQ`ULkm`;EjT}3I0-$>s9L0U&#dS z6`Fr@hWr-<`Bz{_za{uL!4C!hDfqRZi8T%7hYOAr z73AOJVg6?XUlDv)@KZsqw{`h~8GBm?gCS zLMiADfk<~X9Zsu=E1`xLNR0 z!R>-q3tlI9li+QFcL?4i_@H3F;PZkn3%)M+7s0;?ejxa%;Mamj7;CX_V3+@zrRPar~e+d3dFy&agybQrg!7GT^dtM{>V zg@RiIzfXkzYlyJpCgI;Ic)O(kO45HL^y8BLwBYN4e-?b72z{Rl{e|Gai73y9vrD3% z2)T)ZGl;Nvw%|!b$So0EMuhz7lD0O5xui{5ypHt)#yw z_zn^F{7vv{;U{O<{8Yhlf|-J|iLi6N(5DFI5mBES!Db@lqLSVtc%GzRE_l7*O+?7= z68bKo9}@aW!RLklIuZ8&S@0c6|3WZfoNZ4M5qd45Ckf6c!e14FD}`TAgx)5>9wPE@ z7J94TWkl3>r{JA}zY}~;@NFW>`BcytZ_^_L#|oY-SSVO6xJs~7@KPe|xr*q*dS38) zBJ8rKJsM3i%u;CjKWf;))Nf3x5& z;on1qzCD7^2_6vqx1eXDEjLPSA~8<=r4u-TIf{T1$)xOKE8KCI!EXdp(})L5}LmR$olZl uFH@fHkC47i=v_iTDKy^?Vfq1~-xt~g9`oySVcg@`P8s;mK{TDt_x}K&^xWS7 literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/config.h b/obj-i486-linux-gnu-patched/config.h new file mode 100644 index 0000000..54d015c --- /dev/null +++ b/obj-i486-linux-gnu-patched/config.h @@ -0,0 +1,718 @@ +/* config.h. Generated from config.h.in by configure. */ +/* config.h.in. Generated from configure.ac by autoheader. */ + +/* Define if building universal (internal helper macro) */ +/* #undef AC_APPLE_UNIVERSAL_BUILD */ + +/* Define to one of `_getb67', `GETB67', `getb67' for Cray-2 and Cray-YMP + systems. This function is required for `alloca.c' support on those systems. + */ +/* #undef CRAY_STACKSEG_END */ + +/* Define if you want classic PGP support. */ +#define CRYPT_BACKEND_CLASSIC_PGP 1 + +/* Define if you want clasic S/MIME support. */ +#define CRYPT_BACKEND_CLASSIC_SMIME 1 + +/* Define if you use GPGME to support OpenPGP */ +#define CRYPT_BACKEND_GPGME 1 + +/* Define to 1 if using `alloca.c'. */ +/* #undef C_ALLOCA */ + +/* Define to enable debugging info. */ +#define DEBUG 1 + +/* Define if you want to use an external dotlocking program. */ +#define DL_STANDALONE 1 + +/* Define your domain name. */ +/* #undef DOMAIN */ + +/* Define to 1 if translation of program messages to the user's native + language is requested. */ +#define ENABLE_NLS 1 + +/* Enable exact regeneration of email addresses as parsed? NOTE: this requires + significant more memory when defined. */ +/* #undef EXACT_ADDRESS */ + +/* program to use for shell commands */ +#define EXECSHELL "/bin/sh" + +/* Define to 1 if you have `alloca', as a function or macro. */ +#define HAVE_ALLOCA 1 + +/* Define to 1 if you have and it should be used (not on Ultrix). + */ +#define HAVE_ALLOCA_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_ARGZ_H 1 + +/* Define to 1 if you have the `bind_textdomain_codeset' function. */ +#define HAVE_BIND_TEXTDOMAIN_CODESET 1 + +/* Define if you have bkgdset, as a function or macro. */ +#define HAVE_BKGDSET 1 + +/* Define if you have the C99 integer types */ +#define HAVE_C99_INTTYPES 1 + +/* Define if your curses library supports color. */ +#define HAVE_COLOR 1 + +/* Define if you have curs_set, as a function or macro. */ +#define HAVE_CURS_SET 1 + +/* Berkeley DB4 Support */ +/* #undef HAVE_DB4 */ + +/* Define to 1 if you have the `dcgettext' function. */ +#define HAVE_DCGETTEXT 1 + +/* Define to 1 if you have the declaration of `sys_siglist', and to 0 if you + don't. */ +#define HAVE_DECL_SYS_SIGLIST 1 + +/* Define to 1 if your system has the dirent::d_ino member */ +#define HAVE_DIRENT_D_INO 1 + +/* Define to 1 if you have the `fchdir' function. */ +#define HAVE_FCHDIR 1 + +/* Define to 1 if you have the `feof_unlocked' function. */ +#define HAVE_FEOF_UNLOCKED 1 + +/* Define to 1 if you have the `fgetpos' function. */ +#define HAVE_FGETPOS 1 + +/* Define to 1 if you have the `fgets_unlocked' function. */ +#define HAVE_FGETS_UNLOCKED 1 + +/* Define to 1 if fseeko (and presumably ftello) exists and is declared. */ +#define HAVE_FSEEKO 1 + +/* Define to 1 if you have the `ftruncate' function. */ +#define HAVE_FTRUNCATE 1 + +/* GDBM Support */ +#define HAVE_GDBM 1 + +/* Define to 1 if you have the `getaddrinfo' function. */ +#define HAVE_GETADDRINFO 1 + +/* Define to 1 if you have the `getcwd' function. */ +#define HAVE_GETCWD 1 + +/* Define to 1 if you have the `getegid' function. */ +#define HAVE_GETEGID 1 + +/* Define to 1 if you have the `geteuid' function. */ +#define HAVE_GETEUID 1 + +/* Define to 1 if you have the `getgid' function. */ +#define HAVE_GETGID 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_GETOPT_H 1 + +/* Define to 1 if you have the `getpagesize' function. */ +#define HAVE_GETPAGESIZE 1 + +/* Define to 1 if you have the `getsid' function. */ +#define HAVE_GETSID 1 + +/* Define if the GNU gettext() function is already present or preinstalled. */ +#define HAVE_GETTEXT 1 + +/* Define to 1 if you have the `getuid' function. */ +#define HAVE_GETUID 1 + +/* Define if GPGME supports PKA */ +#define HAVE_GPGME_PKA_TRUST 1 + +/* Define if your GSSAPI implementation is Heimdal */ +/* #undef HAVE_HEIMDAL */ + +/* Define if you have the iconv() function. */ +#define HAVE_ICONV 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_ICONV_H 1 + +/* Define if defines iconv_t. */ +#define HAVE_ICONV_T_DEF 1 + +/* Define to 1 if you have the `idna_to_ascii_8z' function. */ +#define HAVE_IDNA_TO_ASCII_8Z 1 + +/* Define to 1 if you have the `idna_to_ascii_from_locale' function. */ +/* #undef HAVE_IDNA_TO_ASCII_FROM_LOCALE */ + +/* Define to 1 if you have the `idna_to_ascii_from_utf8' function. */ +/* #undef HAVE_IDNA_TO_ASCII_FROM_UTF8 */ + +/* Define to 1 if you have the `idna_to_ascii_lz' function. */ +#define HAVE_IDNA_TO_ASCII_LZ 1 + +/* Define to 1 if you have the `idna_to_unicode_8z8z' function. */ +#define HAVE_IDNA_TO_UNICODE_8Z8Z 1 + +/* Define to 1 if you have the `idna_to_unicode_utf8_from_utf8' function. */ +/* #undef HAVE_IDNA_TO_UNICODE_UTF8_FROM_UTF8 */ + +/* Define to 1 if you have the header file. */ +#define HAVE_INTTYPES_H 1 + +/* Define to 1 if you have the header file. */ +/* #undef HAVE_IOCTL_H */ + +/* Define to 1 if you have the `iswalnum' function. */ +#define HAVE_ISWALNUM 1 + +/* Define to 1 if you have the `iswalpha' function. */ +#define HAVE_ISWALPHA 1 + +/* Define to 1 if you have the `iswcntrl' function. */ +#define HAVE_ISWCNTRL 1 + +/* Define to 1 if you have the `iswdigit' function. */ +#define HAVE_ISWDIGIT 1 + +/* Define to 1 if you have the `iswgraph' function. */ +#define HAVE_ISWGRAPH 1 + +/* Define to 1 if you have the `iswlower' function. */ +#define HAVE_ISWLOWER 1 + +/* Define to 1 if you have the `iswprint' function. */ +#define HAVE_ISWPRINT 1 + +/* Define to 1 if you have the `iswpunct' function. */ +#define HAVE_ISWPUNCT 1 + +/* Define to 1 if you have the `iswspace' function. */ +#define HAVE_ISWSPACE 1 + +/* Define to 1 if you have the `iswupper' function. */ +#define HAVE_ISWUPPER 1 + +/* Define to 1 if you have the `iswxdigit' function. */ +#define HAVE_ISWXDIGIT 1 + +/* Define if you have and nl_langinfo(CODESET). */ +#define HAVE_LANGINFO_CODESET 1 + +/* Define if you have and nl_langinfo(YESEXPR). */ +#define HAVE_LANGINFO_YESEXPR 1 + +/* Define if your file defines LC_MESSAGES. */ +#define HAVE_LC_MESSAGES 1 + +/* Define to 1 if you have the `idn' library */ +#define HAVE_LIBIDN 1 + +/* Define to 1 if you have the `intl' library (-lintl). */ +/* #undef HAVE_LIBINTL */ + +/* Define to 1 if you have the `nsl' library (-lnsl). */ +/* #undef HAVE_LIBNSL */ + +/* Define to 1 if you have the `sasl2' library (-lsasl2). */ +#define HAVE_LIBSASL2 1 + +/* Define to 1 if you have the `socket' library (-lsocket). */ +/* #undef HAVE_LIBSOCKET */ + +/* Define to 1 if you have the `ssl' library (-lssl). */ +/* #undef HAVE_LIBSSL */ + +/* Define to 1 if you have the `termlib' library (-ltermlib). */ +/* #undef HAVE_LIBTERMLIB */ + +/* Define to 1 if you have the `x' library (-lx). */ +/* #undef HAVE_LIBX */ + +/* Define to 1 if you have the header file. */ +#define HAVE_LIMITS_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_LOCALE_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_MALLOC_H 1 + +/* Define to 1 if you have the `memmove' function. */ +#define HAVE_MEMMOVE 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_MEMORY_H 1 + +/* Define to 1 if you have the `mempcpy' function. */ +#define HAVE_MEMPCPY 1 + +/* Define if you have meta, as a function or macro. */ +#define HAVE_META 1 + +/* Define to 1 if you have a working `mmap' system call. */ +#define HAVE_MMAP 1 + +/* Define to 1 if you have the `munmap' function. */ +#define HAVE_MUNMAP 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_NCURSESW_NCURSES_H 1 + +/* Define to 1 if you have the header file. */ +/* #undef HAVE_NCURSES_H */ + +/* Define to 1 if you have the header file. */ +/* #undef HAVE_NCURSES_NCURSES_H */ + +/* Define to 1 if you have the header file. */ +#define HAVE_NL_TYPES_H 1 + +/* Define to 1 if you have the `putenv' function. */ +#define HAVE_PUTENV 1 + +/* QDBM Support */ +/* #undef HAVE_QDBM */ + +/* Define to 1 if you have the `RAND_egd' function. */ +/* #undef HAVE_RAND_EGD */ + +/* Define to 1 if you have the `RAND_status' function. */ +/* #undef HAVE_RAND_STATUS */ + +/* Define to 1 if you have the `regcomp' function. */ +#define HAVE_REGCOMP 1 + +/* Define if you have resizeterm, as a function or macro. */ +#define HAVE_RESIZETERM 1 + +/* Define to 1 if you have the `setegid' function. */ +#define HAVE_SETEGID 1 + +/* Define to 1 if you have the `setenv' function. */ +#define HAVE_SETENV 1 + +/* Define to 1 if you have the `setlocale' function. */ +#define HAVE_SETLOCALE 1 + +/* Define to 1 if you have the `setrlimit' function. */ +#define HAVE_SETRLIMIT 1 + +/* Define to 1 if you have a C99 compliant snprintf function. */ +#define HAVE_SNPRINTF 1 + +/* Define to 1 if you have the `srand48' function. */ +#define HAVE_SRAND48 1 + +/* Define if you have start_color, as a function or macro. */ +#define HAVE_START_COLOR 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_STDARG_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_STDDEF_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_STDINT_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_STDLIB_H 1 + +/* Define to 1 if you have the `stpcpy' function. */ +#define HAVE_STPCPY 1 + +/* Define to 1 if you have the `strcasecmp' function. */ +#define HAVE_STRCASECMP 1 + +/* Define to 1 if you have the `strchr' function. */ +#define HAVE_STRCHR 1 + +/* Define to 1 if you have the `strdup' function. */ +#define HAVE_STRDUP 1 + +/* Define to 1 if you have the `strerror' function. */ +#define HAVE_STRERROR 1 + +/* Define to 1 if you have the `strftime' function. */ +#define HAVE_STRFTIME 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_STRINGS_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_STRING_H 1 + +/* Define to 1 if you have the `strsep' function. */ +#define HAVE_STRSEP 1 + +/* Define to 1 if you have the `strtok_r' function. */ +#define HAVE_STRTOK_R 1 + +/* Define to 1 if you have the `strtoul' function. */ +#define HAVE_STRTOUL 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_SYSEXITS_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_SYS_IOCTL_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_SYS_PARAM_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_SYS_RESOURCE_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_SYS_SELECT_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_SYS_STAT_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_SYS_TIME_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_SYS_TYPES_H 1 + +/* Tokyo Cabinet Support */ +/* #undef HAVE_TC */ + +/* Define to 1 if you have the `towlower' function. */ +#define HAVE_TOWLOWER 1 + +/* Define to 1 if you have the `towupper' function. */ +#define HAVE_TOWUPPER 1 + +/* Define to 1 if you have the `tsearch' function. */ +#define HAVE_TSEARCH 1 + +/* Define if you have typeahead, as a function or macro. */ +#define HAVE_TYPEAHEAD 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_UNISTD_H 1 + +/* Define to 1 if you have the header file. */ +/* #undef HAVE_UNIX_H */ + +/* Define if you have use_default_colors, as a function or macro. */ +#define HAVE_USE_DEFAULT_COLORS 1 + +/* Define to 1 if you have the header file. */ +/* #undef HAVE_VILLA_H */ + +/* Define to 1 if you have a C99 compliant vsnprintf function. */ +#define HAVE_VSNPRINTF 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_WCHAR_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_WCTYPE_H 1 + +/* Define if you are using the system's wchar_t functions. */ +#define HAVE_WC_FUNCS 1 + +/* Define to 1 if you have the `__argz_count' function. */ +#define HAVE___ARGZ_COUNT 1 + +/* Define to 1 if you have the `__argz_next' function. */ +#define HAVE___ARGZ_NEXT 1 + +/* Define to 1 if you have the `__argz_stringify' function. */ +#define HAVE___ARGZ_STRINGIFY 1 + +/* Is mail spooled to the user's home directory? If defined, MAILPATH should + be set to the filename of the spool mailbox relative the the home + directory. use: configure --with-homespool=FILE */ +/* #undef HOMESPOOL */ + +/* Define as const if the declaration of iconv() needs const. */ +#define ICONV_CONST + +/* Define as 1 if iconv() only converts exactly and we should treat all return + values other than (size_t)(-1) as equivalent. */ +#define ICONV_NONTRANS 0 + +/* Where to find ispell on your system. */ +/* #undef ISPELL */ + +/* Define if the result of isprint() is unreliable. */ +/* #undef LOCALES_HACK */ + +/* Where new mail is spooled. */ +#define MAILPATH "/var/mail" + +/* Define if you want complete documentation. */ +#define MAKEDOC_FULL 1 + +/* Where to find mixmaster on your system. */ +#define MIXMASTER "mixmaster" + +/* Define if you have problems with mutt not detecting new/old mailboxes over + NFS. Some NFS implementations incorrectly cache the attributes of small + files. */ +/* #undef NFS_ATTRIBUTE_HACK */ + +/* Name of package */ +#define PACKAGE "mutt" + +/* Define to the address where bug reports for this package should be sent. */ +#define PACKAGE_BUGREPORT "" + +/* Define to the full name of this package. */ +#define PACKAGE_NAME "" + +/* Define to the full name and version of this package. */ +#define PACKAGE_STRING "" + +/* Define to the one symbol short name of this package. */ +#define PACKAGE_TARNAME "" + +/* Define to the version of this package. */ +#define PACKAGE_VERSION "" + +/* Define to 1 if the C compiler supports function prototypes. */ +#define PROTOTYPES 1 + +/* Define as the return type of signal handlers (`int' or `void'). */ +#define RETSIGTYPE void + +/* Where to find sendmail on your system. */ +#define SENDMAIL "/usr/sbin/sendmail" + +/* Some systems declare sig_atomic_t as volatile, some others -- no. This + define will have value `sig_atomic_t' or `volatile sig_atomic_t' + accordingly. */ +#define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t + +/* The size of `int', as computed by sizeof. */ +#define SIZEOF_INT 4 + +/* The size of `long', as computed by sizeof. */ +#define SIZEOF_LONG 4 + +/* The size of `long long', as computed by sizeof. */ +#define SIZEOF_LONG_LONG 8 + +/* The size of `off_t', as computed by sizeof. */ +#define SIZEOF_OFF_T 8 + +/* The size of `short', as computed by sizeof. */ +#define SIZEOF_SHORT 2 + +/* If using the C implementation of alloca, define if you know the + direction of stack growth for your system; otherwise it will be + automatically deduced at runtime. + STACK_DIRECTION > 0 => grows toward higher addresses + STACK_DIRECTION < 0 => grows toward lower addresses + STACK_DIRECTION = 0 => direction of growth unknown */ +/* #undef STACK_DIRECTION */ + +/* Define to 1 if you have the ANSI C header files. */ +#define STDC_HEADERS 1 + +/* Define to enable Sun mailtool attachments support. */ +/* #undef SUN_ATTACHMENT */ + +/* Define to support compressed folders. */ +#define USE_COMPRESSED 1 + +/* Define to use dotlocking for mailboxes. */ +#define USE_DOTLOCK 1 + +/* Define to use fcntl() to lock folders. */ +#define USE_FCNTL 1 + +/* Define to use flock() to lock mailboxes. */ +/* #undef USE_FLOCK */ + +/* Define if you want to use the included regex.c. */ +/* #undef USE_GNU_REGEX */ + +/* Define if you have GSSAPI libraries available */ +#define USE_GSS 1 + +/* Enable header caching */ +#define USE_HCACHE 1 + +/* Define if you want support for the IMAP protocol. */ +#define USE_IMAP 1 + +/* Define if you want support for the POP3 protocol. */ +#define USE_POP 1 + +/* Define if want to use the Cyrus SASL library for POP/IMAP authentication. + */ +#define USE_SASL 1 + +/* Define if mutt should run setgid "mail". */ +#define USE_SETGID 1 + +/* Define if you compile with SLang instead of curses/ncurses. */ +/* #undef USE_SLANG_CURSES */ + +/* Include internal SMTP relay support */ +#define USE_SMTP 1 + +/* Include code for socket support. Set automatically if you enable POP3 or + IMAP */ +#define USE_SOCKET 1 + +/* Define if you want support for SSL. */ +#define USE_SSL 1 + +/* Define if you want support for SSL via GNUTLS. */ +#define USE_SSL_GNUTLS 1 + +/* Define if you want support for SSL via OpenSSL. */ +/* #undef USE_SSL_OPENSSL */ + +/* Enable extensions on AIX 3, Interix. */ +#ifndef _ALL_SOURCE +# define _ALL_SOURCE 1 +#endif +/* Enable GNU extensions on systems that have them. */ +#ifndef _GNU_SOURCE +# define _GNU_SOURCE 1 +#endif +/* Enable threading extensions on Solaris. */ +#ifndef _POSIX_PTHREAD_SEMANTICS +# define _POSIX_PTHREAD_SEMANTICS 1 +#endif +/* Enable extensions on HP NonStop. */ +#ifndef _TANDEM_SOURCE +# define _TANDEM_SOURCE 1 +#endif +/* Enable general extensions on Solaris. */ +#ifndef __EXTENSIONS__ +# define __EXTENSIONS__ 1 +#endif + + +/* Version number of package */ +#define VERSION "1.5.19" + +/* Define WORDS_BIGENDIAN to 1 if your processor stores words with the most + significant byte first (like Motorola and SPARC, unlike Intel). */ +#if defined AC_APPLE_UNIVERSAL_BUILD +# if defined __BIG_ENDIAN__ +# define WORDS_BIGENDIAN 1 +# endif +#else +# ifndef WORDS_BIGENDIAN +/* # undef WORDS_BIGENDIAN */ +# endif +#endif + +#ifndef HAVE_C99_INTTYPES +# if SIZEOF_SHORT == 4 +typedef unsigned short uint32_t; +# elif SIZEOF_INT == 4 +typedef unsigned int uint32_t; +# elif SIZEOF_LONG == 4 +typedef unsigned long uint32_t; +# endif +# if SIZEOF_INT == 8 +typedef unsigned int uint64_t; +# elif SIZEOF_LONG == 8 +typedef unsigned long uint64_t; +# elif SIZEOF_LONG_LONG == 8 +typedef unsigned long long uint64_t; +# endif +#endif + + +/* Number of bits in a file offset, on hosts where this is settable. */ +#define _FILE_OFFSET_BITS 64 + +/* Define to 1 to make fseeko visible on some hosts (e.g. glibc 2.2). */ +/* #undef _LARGEFILE_SOURCE */ + +/* Define for large files, on AIX-style hosts. */ +/* #undef _LARGE_FILES */ + +/* Define to 1 if on MINIX. */ +/* #undef _MINIX */ + +/* Define to 2 if the system does not provide POSIX.1 features except with + this defined. */ +/* #undef _POSIX_1_SOURCE */ + +/* Define to 1 if you need to in order for `stat' and other things to work. */ +/* #undef _POSIX_SOURCE */ + +/* Define like PROTOTYPES; this can be used by system headers. */ +#define __PROTOTYPES 1 + +/* Define to empty if `const' does not conform to ANSI C. */ +/* #undef const */ + +/* Define to `__inline__' or `__inline' if that's what the C compiler + calls it, or to nothing if 'inline' is not supported under any name. */ +#ifndef __cplusplus +/* #undef inline */ +#endif + +/* Define to 'int' if system headers don't define. */ +/* #undef mbstate_t */ + +/* Define to `long int' if does not define. */ +/* #undef off_t */ + +/* Define to `int' if does not define. */ +/* #undef pid_t */ + +/* Define to `int' if does not define. */ +/* #undef sig_atomic_t */ + +/* Define to `unsigned int' if does not define. */ +/* #undef size_t */ + +/* Define to 'int' if doesn't have it. */ +/* #undef socklen_t */ + +/* Define to `int' if does not define. */ +/* #undef ssize_t */ + +/* define if va_copy is not available */ +/* #undef va_copy */ + +/* Define to 'int' if system headers don't define. */ +/* #undef wchar_t */ + +/* Define to 'int' if system headers don't define. */ +/* #undef wint_t */ + +/* fseeko portability defines */ +#ifdef HAVE_FSEEKO +# define LOFF_T off_t +# if HAVE_C99_INTTYPES && HAVE_INTTYPES_H +# if SIZEOF_OFF_T == 8 +# define OFF_T_FMT "%" PRId64 +# else +# define OFF_T_FMT "%" PRId32 +# endif +# else +# if (SIZEOF_OFF_T == 8) && (SIZEOF_LONG == 4) +# define OFF_T_FMT "%lld" +# else +# define OFF_T_FMT "%ld" +# endif +# endif +#else +# define LOFF_T long +# define fseeko fseek +# define ftello ftell +# define OFF_T_FMT "%ld" +#endif + +#include "config-debian.h" diff --git a/obj-i486-linux-gnu-patched/config.log b/obj-i486-linux-gnu-patched/config.log new file mode 100644 index 0000000..c5d8849 --- /dev/null +++ b/obj-i486-linux-gnu-patched/config.log @@ -0,0 +1,3993 @@ +This file contains any messages produced by compilers while +running configure, to aid debugging if configure makes a mistake. + +It was created by configure, which was +generated by GNU Autoconf 2.63. Invocation command line was + + $ ../configure --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --with-sharedir=/usr/share/mutt --with-docdir=/usr/share/doc --with-mailpath=/var/mail --disable-dependency-tracking --enable-compressed --enable-debug --enable-fcntl --enable-hcache --enable-gpgme --enable-imap --enable-smtp --enable-inodesort --enable-pop --with-curses --with-gnutls --with-gss --with-idn --with-mixmaster --with-sasl --without-qdbm --without-bdb --without-tokyocabinet --build i486-linux-gnu + +## --------- ## +## Platform. ## +## --------- ## + +hostname = debian +uname -m = i686 +uname -r = 2.6.26-1-686 +uname -s = Linux +uname -v = #1 SMP Sat Jan 10 18:29:31 UTC 2009 + +/usr/bin/uname -p = unknown +/bin/uname -X = unknown + +/bin/arch = unknown +/usr/bin/arch -k = unknown +/usr/convex/getsysinfo = unknown +/usr/bin/hostinfo = unknown +/bin/machine = unknown +/usr/bin/oslevel = unknown +/bin/universe = unknown + +PATH: /usr/sbin +PATH: /usr/bin +PATH: /sbin +PATH: /bin +PATH: /usr/bin/X11 + + +## ----------- ## +## Core tests. ## +## ----------- ## + +configure:2040: checking for a BSD-compatible install +configure:2108: result: /usr/bin/install -c +configure:2119: checking whether build environment is sane +configure:2162: result: yes +configure:2187: checking for a thread-safe mkdir -p +configure:2226: result: /bin/mkdir -p +configure:2239: checking for gawk +configure:2255: found /usr/bin/gawk +configure:2266: result: gawk +configure:2277: checking whether make sets $(MAKE) +configure:2299: result: yes +configure:2483: checking whether to enable maintainer-specific portions of Makefiles +configure:2492: result: no +configure:2520: checking for style of include used by make +configure:2548: result: GNU +configure:2618: checking for gcc +configure:2634: found /usr/bin/gcc +configure:2645: result: gcc +configure:2877: checking for C compiler version +configure:2885: gcc --version >&5 +gcc (Debian 4.3.3-5) 4.3.3 +Copyright (C) 2008 Free Software Foundation, Inc. +This is free software; see the source for copying conditions. There is NO +warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. + +configure:2889: $? = 0 +configure:2896: gcc -v >&5 +Using built-in specs. +Target: i486-linux-gnu +Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.3-5' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu +Thread model: posix +gcc version 4.3.3 (Debian 4.3.3-5) +configure:2900: $? = 0 +configure:2907: gcc -V >&5 +gcc: '-V' option must have argument +configure:2911: $? = 1 +configure:2934: checking for C compiler default output file name +configure:2956: gcc -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:2960: $? = 0 +configure:2998: result: a.out +configure:3017: checking whether the C compiler works +configure:3027: ./a.out +configure:3031: $? = 0 +configure:3050: result: yes +configure:3057: checking whether we are cross compiling +configure:3059: result: no +configure:3062: checking for suffix of executables +configure:3069: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:3073: $? = 0 +configure:3099: result: +configure:3105: checking for suffix of object files +configure:3131: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:3135: $? = 0 +configure:3160: result: o +configure:3164: checking whether we are using the GNU C compiler +configure:3193: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:3200: $? = 0 +configure:3217: result: yes +configure:3226: checking whether gcc accepts -g +configure:3256: gcc -c -g -I/usr/include/qdbm conftest.c >&5 +configure:3263: $? = 0 +configure:3364: result: yes +configure:3381: checking for gcc option to accept ISO C89 +configure:3455: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:3462: $? = 0 +configure:3485: result: none needed +configure:3505: checking dependency style of gcc +configure:3596: result: none +configure:3617: checking how to run the C preprocessor +configure:3657: gcc -E -I/usr/include/qdbm conftest.c +configure:3664: $? = 0 +configure:3695: gcc -E -I/usr/include/qdbm conftest.c +conftest.c:10:28: error: ac_nonexistent.h: No such file or directory +configure:3702: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| /* end confdefs.h. */ +| #include +configure:3735: result: gcc -E +configure:3764: gcc -E -I/usr/include/qdbm conftest.c +configure:3771: $? = 0 +configure:3802: gcc -E -I/usr/include/qdbm conftest.c +conftest.c:10:28: error: ac_nonexistent.h: No such file or directory +configure:3809: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| /* end confdefs.h. */ +| #include +configure:3849: checking for grep that handles long lines and -e +configure:3909: result: /bin/grep +configure:3914: checking for egrep +configure:3978: result: /bin/grep -E +configure:3983: checking for ANSI C header files +configure:4013: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:4020: $? = 0 +configure:4119: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:4123: $? = 0 +configure:4129: ./conftest +configure:4133: $? = 0 +configure:4151: result: yes +configure:4175: checking for sys/types.h +configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:4203: $? = 0 +configure:4220: result: yes +configure:4175: checking for sys/stat.h +configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:4203: $? = 0 +configure:4220: result: yes +configure:4175: checking for stdlib.h +configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:4203: $? = 0 +configure:4220: result: yes +configure:4175: checking for string.h +configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:4203: $? = 0 +configure:4220: result: yes +configure:4175: checking for memory.h +configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:4203: $? = 0 +configure:4220: result: yes +configure:4175: checking for strings.h +configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:4203: $? = 0 +configure:4220: result: yes +configure:4175: checking for inttypes.h +configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:4203: $? = 0 +configure:4220: result: yes +configure:4175: checking for stdint.h +configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:4203: $? = 0 +configure:4220: result: yes +configure:4175: checking for unistd.h +configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:4203: $? = 0 +configure:4220: result: yes +configure:4245: checking minix/config.h usability +configure:4262: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c:53:26: error: minix/config.h: No such file or directory +configure:4269: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| /* end confdefs.h. */ +| #include +| #ifdef HAVE_SYS_TYPES_H +| # include +| #endif +| #ifdef HAVE_SYS_STAT_H +| # include +| #endif +| #ifdef STDC_HEADERS +| # include +| # include +| #else +| # ifdef HAVE_STDLIB_H +| # include +| # endif +| #endif +| #ifdef HAVE_STRING_H +| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H +| # include +| # endif +| # include +| #endif +| #ifdef HAVE_STRINGS_H +| # include +| #endif +| #ifdef HAVE_INTTYPES_H +| # include +| #endif +| #ifdef HAVE_STDINT_H +| # include +| #endif +| #ifdef HAVE_UNISTD_H +| # include +| #endif +| #include +configure:4283: result: no +configure:4287: checking minix/config.h presence +configure:4302: gcc -E -I/usr/include/qdbm conftest.c +conftest.c:20:26: error: minix/config.h: No such file or directory +configure:4309: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| /* end confdefs.h. */ +| #include +configure:4323: result: no +configure:4351: checking for minix/config.h +configure:4358: result: no +configure:4389: checking whether it is safe to define __EXTENSIONS__ +configure:4417: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:4424: $? = 0 +configure:4439: result: yes +configure:4472: checking build system type +configure:4490: result: i486-pc-linux-gnu +configure:4512: checking host system type +configure:4527: result: i486-pc-linux-gnu +configure:4550: checking for prefix +configure:4557: result: /usr +configure:4608: checking for gcc +configure:4635: result: gcc +configure:4867: checking for C compiler version +configure:4875: gcc --version >&5 +gcc (Debian 4.3.3-5) 4.3.3 +Copyright (C) 2008 Free Software Foundation, Inc. +This is free software; see the source for copying conditions. There is NO +warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. + +configure:4879: $? = 0 +configure:4886: gcc -v >&5 +Using built-in specs. +Target: i486-linux-gnu +Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.3-5' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu +Thread model: posix +gcc version 4.3.3 (Debian 4.3.3-5) +configure:4890: $? = 0 +configure:4897: gcc -V >&5 +gcc: '-V' option must have argument +configure:4901: $? = 1 +configure:4904: checking whether we are using the GNU C compiler +configure:4957: result: yes +configure:4966: checking whether gcc accepts -g +configure:5104: result: yes +configure:5121: checking for gcc option to accept ISO C89 +configure:5225: result: none needed +configure:5245: checking dependency style of gcc +configure:5336: result: none +configure:5351: checking for library containing strerror +configure:5392: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:5399: $? = 0 +configure:5430: result: none required +configure:5438: checking for function prototypes +configure:5441: result: yes +configure:5471: checking for string.h +configure:5478: result: yes +configure:5623: checking how to run the C preprocessor +configure:5741: result: gcc -E +configure:5770: gcc -E -I/usr/include/qdbm conftest.c +configure:5777: $? = 0 +configure:5808: gcc -E -I/usr/include/qdbm conftest.c +conftest.c:28:28: error: ac_nonexistent.h: No such file or directory +configure:5815: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| /* end confdefs.h. */ +| #include +configure:5854: checking whether make sets $(MAKE) +configure:5876: result: yes +configure:5899: checking for a BSD-compatible install +configure:5967: result: /usr/bin/install -c +configure:6021: checking for ranlib +configure:6037: found /usr/bin/ranlib +configure:6048: result: ranlib +configure:6113: checking for ar +configure:6129: found /usr/bin/ar +configure:6140: result: ar +configure:6163: checking for inline +configure:6189: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:6196: $? = 0 +configure:6214: result: inline +configure:6233: checking for an ANSI C-conforming const +configure:6308: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c: In function 'main': +conftest.c:57: warning: 't' is used uninitialized in this function +conftest.c:73: warning: 'b' may be used uninitialized in this function +conftest.c:79: warning: 'cs[0]' is used uninitialized in this function +configure:6315: $? = 0 +configure:6330: result: yes +configure:6341: checking whether byte ordering is bigendian +configure:6366: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c:29: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'a' +configure:6373: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| /* end confdefs.h. */ +| #ifndef __APPLE_CC__ +| not a universal capable compiler +| #endif +| typedef int dummy; +| +configure:6423: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:6430: $? = 0 +configure:6462: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c: In function 'main': +conftest.c:35: error: 'not' undeclared (first use in this function) +conftest.c:35: error: (Each undeclared identifier is reported only once +conftest.c:35: error: for each function it appears in.) +conftest.c:35: error: expected ';' before 'big' +configure:6469: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| /* end confdefs.h. */ +| #include +| #include +| +| int +| main () +| { +| #if BYTE_ORDER != BIG_ENDIAN +| not big endian +| #endif +| +| ; +| return 0; +| } +configure:6721: result: no +configure:6754: checking for special C compiler options needed for large files +configure:6849: result: no +configure:6855: checking for _FILE_OFFSET_BITS value needed for large files +configure:6890: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c:34: warning: left shift count >= width of type +conftest.c:34: warning: left shift count >= width of type +conftest.c:36: error: size of array 'off_t_is_large' is negative +configure:6897: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| /* end confdefs.h. */ +| #include +| /* Check that off_t can represent 2**63 - 1 correctly. +| We can't simply define LARGE_OFF_T to be 9223372036854775807, +| since some C++ compilers masquerading as C compilers +| incorrectly reject 9223372036854775807. */ +| #define LARGE_OFF_T (((off_t) 1 << 62) - 1 + ((off_t) 1 << 62)) +| int off_t_is_large[(LARGE_OFF_T % 2147483629 == 721 +| && LARGE_OFF_T % 2147483647 == 1) +| ? 1 : -1]; +| int +| main () +| { +| +| ; +| return 0; +| } +configure:6941: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:6948: $? = 0 +configure:6966: result: 64 +configure:7103: checking for _LARGEFILE_SOURCE value needed for large files +configure:7132: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:7139: $? = 0 +configure:7212: result: no +configure:7239: checking size of off_t +configure:7544: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:7548: $? = 0 +configure:7554: ./conftest +configure:7558: $? = 0 +configure:7584: result: 8 +configure:7597: checking for dbx +configure:7628: result: no +configure:7638: checking for gdb +configure:7656: found /usr/bin/gdb +configure:7669: result: /usr/bin/gdb +configure:7679: checking for sdb +configure:7710: result: no +configure:7759: checking for inttypes.h +configure:7766: result: yes +configure:7900: checking for uint32_t +configure:7928: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:7935: $? = 0 +configure:7962: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c: In function 'main': +conftest.c:68: error: expected expression before ')' token +configure:7969: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| /* end confdefs.h. */ +| #include +| #ifdef HAVE_SYS_TYPES_H +| # include +| #endif +| #ifdef HAVE_SYS_STAT_H +| # include +| #endif +| #ifdef STDC_HEADERS +| # include +| # include +| #else +| # ifdef HAVE_STDLIB_H +| # include +| # endif +| #endif +| #ifdef HAVE_STRING_H +| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H +| # include +| # endif +| # include +| #endif +| #ifdef HAVE_STRINGS_H +| # include +| #endif +| #ifdef HAVE_INTTYPES_H +| # include +| #endif +| #ifdef HAVE_STDINT_H +| # include +| #endif +| #ifdef HAVE_UNISTD_H +| # include +| #endif +| int +| main () +| { +| if (sizeof ((uint32_t))) +| return 0; +| ; +| return 0; +| } +configure:7992: result: yes +configure:8006: checking size of short +configure:8311: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:8315: $? = 0 +configure:8321: ./conftest +configure:8325: $? = 0 +configure:8351: result: 2 +configure:8365: checking size of int +configure:8670: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:8674: $? = 0 +configure:8680: ./conftest +configure:8684: $? = 0 +configure:8710: result: 4 +configure:8724: checking size of long +configure:9029: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:9033: $? = 0 +configure:9039: ./conftest +configure:9043: $? = 0 +configure:9069: result: 4 +configure:9083: checking size of long long +configure:9388: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:9392: $? = 0 +configure:9398: ./conftest +configure:9402: $? = 0 +configure:9428: result: 8 +configure:9442: checking for sendmail +configure:9461: found /usr/sbin/sendmail +configure:9474: result: /usr/sbin/sendmail +configure:9490: checking whether to build with GPGME support +configure:9502: result: yes +configure:9517: checking for gpgme-config +configure:9535: found /usr/bin/gpgme-config +configure:9548: result: /usr/bin/gpgme-config +configure:9576: checking for GPGME - version >= 1.0.0 +configure:9617: result: yes +configure:9648: checking for GPGME - version >= 1.1.1 +configure:9689: result: yes +configure:9716: checking for GPGME - version >= 1.0.0 +configure:9757: result: yes +configure:9850: checking for ispell +configure:9881: result: no +configure:10172: checking for initscr +configure:10228: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +/tmp/ccm6dj5h.o: In function `main': +/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/conftest.c:78: undefined reference to `initscr' +collect2: ld returned 1 exit status +configure:10235: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| /* end confdefs.h. */ +| /* Define initscr to an innocuous variant, in case declares initscr. +| For example, HP-UX 11i declares gettimeofday. */ +| #define initscr innocuous_initscr +| +| /* System header to define __stub macros and hopefully few prototypes, +| which can conflict with char initscr (); below. +| Prefer to if __STDC__ is defined, since +| exists even on freestanding compilers. */ +| +| #ifdef __STDC__ +| # include +| #else +| # include +| #endif +| +| #undef initscr +| +| /* Override any GCC internal prototype to avoid an error. +| Use char because int might match the return type of a GCC +| builtin and then its argument prototype would still apply. */ +| #ifdef __cplusplus +| extern "C" +| #endif +| char initscr (); +| /* The GNU C library defines this for functions which it implements +| to always fail with ENOSYS. Some functions are actually named +| something starting with __ and the normal name is an alias. */ +| #if defined __stub_initscr || defined __stub___initscr +| choke me +| #endif +| +| int +| main () +| { +| return initscr (); +| ; +| return 0; +| } +configure:10255: result: no +configure:10265: checking for waddnwstr in -lncurses +configure:10300: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c -lncurses >&5 +/tmp/ccEFgr2w.o: In function `main': +/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/conftest.c:55: undefined reference to `waddnwstr' +collect2: ld returned 1 exit status +configure:10307: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| /* end confdefs.h. */ +| +| /* Override any GCC internal prototype to avoid an error. +| Use char because int might match the return type of a GCC +| builtin and then its argument prototype would still apply. */ +| #ifdef __cplusplus +| extern "C" +| #endif +| char waddnwstr (); +| int +| main () +| { +| return waddnwstr (); +| ; +| return 0; +| } +configure:10330: result: no +configure:10265: checking for waddnwstr in -lncursesw +configure:10300: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c -lncursesw >&5 +configure:10307: $? = 0 +configure:10330: result: yes +configure:10340: checking for initscr in -lncursesw +configure:10375: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c -lncursesw >&5 +configure:10382: $? = 0 +configure:10405: result: yes +configure:10429: checking ncursesw/ncurses.h usability +configure:10446: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:10453: $? = 0 +configure:10467: result: yes +configure:10471: checking ncursesw/ncurses.h presence +configure:10486: gcc -E -I/usr/include/qdbm conftest.c +configure:10493: $? = 0 +configure:10507: result: yes +configure:10535: checking for ncursesw/ncurses.h +configure:10544: result: yes +configure:11615: checking for start_color declaration +configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:11650: $? = 0 +configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c: In function 'main': +conftest.c:50: warning: unused variable 'p' +configure:11686: $? = 0 +configure:11714: result: yes +configure:11615: checking for typeahead declaration +configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:11650: $? = 0 +configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c: In function 'main': +conftest.c:51: warning: unused variable 'p' +configure:11686: $? = 0 +configure:11714: result: yes +configure:11615: checking for bkgdset declaration +configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:11650: $? = 0 +configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:11686: $? = 0 +configure:11714: result: yes +configure:11615: checking for curs_set declaration +configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:11650: $? = 0 +configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c: In function 'main': +conftest.c:53: warning: unused variable 'p' +configure:11686: $? = 0 +configure:11714: result: yes +configure:11615: checking for meta declaration +configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c: In function 'main': +conftest.c:54: error: conflicting types for 'meta' +conftest.c:54: note: an argument type that has a default promotion can't match an empty parameter name list declaration +/usr/include/ncursesw/ncurses.h:604: error: previous declaration of 'meta' was here +configure:11650: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| /* end confdefs.h. */ +| #include +| int +| main () +| { +| #ifndef meta +| extern int meta(); +| #endif +| ; +| return 0; +| } +configure:11714: result: yes +configure:11615: checking for use_default_colors declaration +configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:11650: $? = 0 +configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c: In function 'main': +conftest.c:55: warning: unused variable 'p' +configure:11686: $? = 0 +configure:11714: result: yes +configure:11615: checking for resizeterm declaration +configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:11650: $? = 0 +configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c: In function 'main': +conftest.c:56: warning: unused variable 'p' +configure:11686: $? = 0 +configure:11714: result: yes +configure:11745: checking for ANSI C header files +configure:11913: result: yes +configure:11943: checking stdarg.h usability +configure:11960: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:11967: $? = 0 +configure:11981: result: yes +configure:11985: checking stdarg.h presence +configure:12000: gcc -E -I/usr/include/qdbm conftest.c +configure:12007: $? = 0 +configure:12021: result: yes +configure:12049: checking for stdarg.h +configure:12058: result: yes +configure:11943: checking sys/ioctl.h usability +configure:11960: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:11967: $? = 0 +configure:11981: result: yes +configure:11985: checking sys/ioctl.h presence +configure:12000: gcc -E -I/usr/include/qdbm conftest.c +configure:12007: $? = 0 +configure:12021: result: yes +configure:12049: checking for sys/ioctl.h +configure:12058: result: yes +configure:11943: checking ioctl.h usability +configure:11960: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c:89:19: error: ioctl.h: No such file or directory +configure:11967: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| /* end confdefs.h. */ +| #include +| #ifdef HAVE_SYS_TYPES_H +| # include +| #endif +| #ifdef HAVE_SYS_STAT_H +| # include +| #endif +| #ifdef STDC_HEADERS +| # include +| # include +| #else +| # ifdef HAVE_STDLIB_H +| # include +| # endif +| #endif +| #ifdef HAVE_STRING_H +| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H +| # include +| # endif +| # include +| #endif +| #ifdef HAVE_STRINGS_H +| # include +| #endif +| #ifdef HAVE_INTTYPES_H +| # include +| #endif +| #ifdef HAVE_STDINT_H +| # include +| #endif +| #ifdef HAVE_UNISTD_H +| # include +| #endif +| #include +configure:11981: result: no +configure:11985: checking ioctl.h presence +configure:12000: gcc -E -I/usr/include/qdbm conftest.c +conftest.c:56:19: error: ioctl.h: No such file or directory +configure:12007: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| /* end confdefs.h. */ +| #include +configure:12021: result: no +configure:12049: checking for ioctl.h +configure:12058: result: no +configure:11943: checking sysexits.h usability +configure:11960: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:11967: $? = 0 +configure:11981: result: yes +configure:11985: checking sysexits.h presence +configure:12000: gcc -E -I/usr/include/qdbm conftest.c +configure:12007: $? = 0 +configure:12021: result: yes +configure:12049: checking for sysexits.h +configure:12058: result: yes +configure:12090: checking sys/time.h usability +configure:12107: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:12114: $? = 0 +configure:12128: result: yes +configure:12132: checking sys/time.h presence +configure:12147: gcc -E -I/usr/include/qdbm conftest.c +configure:12154: $? = 0 +configure:12168: result: yes +configure:12196: checking for sys/time.h +configure:12205: result: yes +configure:12090: checking sys/resource.h usability +configure:12107: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:12114: $? = 0 +configure:12128: result: yes +configure:12132: checking sys/resource.h presence +configure:12147: gcc -E -I/usr/include/qdbm conftest.c +configure:12154: $? = 0 +configure:12168: result: yes +configure:12196: checking for sys/resource.h +configure:12205: result: yes +configure:12236: checking unix.h usability +configure:12253: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c:92:18: error: unix.h: No such file or directory +configure:12260: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| #define HAVE_SYSEXITS_H 1 +| #define HAVE_SYS_TIME_H 1 +| #define HAVE_SYS_RESOURCE_H 1 +| /* end confdefs.h. */ +| #include +| #ifdef HAVE_SYS_TYPES_H +| # include +| #endif +| #ifdef HAVE_SYS_STAT_H +| # include +| #endif +| #ifdef STDC_HEADERS +| # include +| # include +| #else +| # ifdef HAVE_STDLIB_H +| # include +| # endif +| #endif +| #ifdef HAVE_STRING_H +| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H +| # include +| # endif +| # include +| #endif +| #ifdef HAVE_STRINGS_H +| # include +| #endif +| #ifdef HAVE_INTTYPES_H +| # include +| #endif +| #ifdef HAVE_STDINT_H +| # include +| #endif +| #ifdef HAVE_UNISTD_H +| # include +| #endif +| #include +configure:12274: result: no +configure:12278: checking unix.h presence +configure:12293: gcc -E -I/usr/include/qdbm conftest.c +conftest.c:59:18: error: unix.h: No such file or directory +configure:12300: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| #define HAVE_SYSEXITS_H 1 +| #define HAVE_SYS_TIME_H 1 +| #define HAVE_SYS_RESOURCE_H 1 +| /* end confdefs.h. */ +| #include +configure:12314: result: no +configure:12342: checking for unix.h +configure:12351: result: no +configure:12372: checking for setrlimit +configure:12428: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:12435: $? = 0 +configure:12457: result: yes +configure:12372: checking for getsid +configure:12428: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:12435: $? = 0 +configure:12457: result: yes +configure:12470: checking return type of signal handlers +configure:12498: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c: In function 'main': +conftest.c:67: error: void value not ignored as it ought to be +configure:12505: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| #define HAVE_SYSEXITS_H 1 +| #define HAVE_SYS_TIME_H 1 +| #define HAVE_SYS_RESOURCE_H 1 +| #define HAVE_SETRLIMIT 1 +| #define HAVE_GETSID 1 +| /* end confdefs.h. */ +| #include +| #include +| +| int +| main () +| { +| return *(signal (0, 0)) (0) == 1; +| ; +| return 0; +| } +configure:12520: result: void +configure:12529: checking for sig_atomic_t in signal.h +configure:12563: result: yes, non volatile +configure:12696: checking whether sys_siglist is declared +configure:12731: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:12738: $? = 0 +configure:12753: result: yes +configure:12773: checking for pid_t +configure:12801: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:12808: $? = 0 +configure:12835: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c: In function 'main': +conftest.c:100: error: expected expression before ')' token +configure:12842: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| #define HAVE_SYSEXITS_H 1 +| #define HAVE_SYS_TIME_H 1 +| #define HAVE_SYS_RESOURCE_H 1 +| #define HAVE_SETRLIMIT 1 +| #define HAVE_GETSID 1 +| #define RETSIGTYPE void +| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t +| #define HAVE_DECL_SYS_SIGLIST 1 +| /* end confdefs.h. */ +| #include +| #ifdef HAVE_SYS_TYPES_H +| # include +| #endif +| #ifdef HAVE_SYS_STAT_H +| # include +| #endif +| #ifdef STDC_HEADERS +| # include +| # include +| #else +| # ifdef HAVE_STDLIB_H +| # include +| # endif +| #endif +| #ifdef HAVE_STRING_H +| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H +| # include +| # endif +| # include +| #endif +| #ifdef HAVE_STRINGS_H +| # include +| #endif +| #ifdef HAVE_INTTYPES_H +| # include +| #endif +| #ifdef HAVE_STDINT_H +| # include +| #endif +| #ifdef HAVE_UNISTD_H +| # include +| #endif +| int +| main () +| { +| if (sizeof ((pid_t))) +| return 0; +| ; +| return 0; +| } +configure:12865: result: yes +configure:12877: checking for ssize_t +configure:12905: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:12912: $? = 0 +configure:12939: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c: In function 'main': +conftest.c:100: error: expected expression before ')' token +configure:12946: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| #define HAVE_SYSEXITS_H 1 +| #define HAVE_SYS_TIME_H 1 +| #define HAVE_SYS_RESOURCE_H 1 +| #define HAVE_SETRLIMIT 1 +| #define HAVE_GETSID 1 +| #define RETSIGTYPE void +| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t +| #define HAVE_DECL_SYS_SIGLIST 1 +| /* end confdefs.h. */ +| #include +| #ifdef HAVE_SYS_TYPES_H +| # include +| #endif +| #ifdef HAVE_SYS_STAT_H +| # include +| #endif +| #ifdef STDC_HEADERS +| # include +| # include +| #else +| # ifdef HAVE_STDLIB_H +| # include +| # endif +| #endif +| #ifdef HAVE_STRING_H +| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H +| # include +| # endif +| # include +| #endif +| #ifdef HAVE_STRINGS_H +| # include +| #endif +| #ifdef HAVE_INTTYPES_H +| # include +| #endif +| #ifdef HAVE_STDINT_H +| # include +| #endif +| #ifdef HAVE_UNISTD_H +| # include +| #endif +| int +| main () +| { +| if (sizeof ((ssize_t))) +| return 0; +| ; +| return 0; +| } +configure:12969: result: yes +configure:12990: checking for fgetpos +configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:13053: $? = 0 +configure:13075: result: yes +configure:12990: checking for memmove +configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c:88: warning: conflicting types for built-in function 'memmove' +configure:13053: $? = 0 +configure:13075: result: yes +configure:12990: checking for setegid +configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:13053: $? = 0 +configure:13075: result: yes +configure:12990: checking for srand48 +configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:13053: $? = 0 +configure:13075: result: yes +configure:12990: checking for strerror +configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:13053: $? = 0 +configure:13075: result: yes +configure:13096: checking for setenv +configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:13159: $? = 0 +configure:13181: result: yes +configure:13096: checking for strcasecmp +configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c:93: warning: conflicting types for built-in function 'strcasecmp' +configure:13159: $? = 0 +configure:13181: result: yes +configure:13096: checking for strdup +configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c:94: warning: conflicting types for built-in function 'strdup' +configure:13159: $? = 0 +configure:13181: result: yes +configure:13096: checking for strsep +configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:13159: $? = 0 +configure:13181: result: yes +configure:13096: checking for strtok_r +configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:13159: $? = 0 +configure:13181: result: yes +configure:13202: checking for getopt +configure:13258: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:13265: $? = 0 +configure:13285: result: yes +configure:13305: checking getopt.h usability +configure:13322: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:13329: $? = 0 +configure:13343: result: yes +configure:13347: checking getopt.h presence +configure:13362: gcc -E -I/usr/include/qdbm conftest.c +configure:13369: $? = 0 +configure:13383: result: yes +configure:13411: checking for getopt.h +configure:13420: result: yes +configure:13438: checking for snprintf +configure:13494: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c:98: warning: conflicting types for built-in function 'snprintf' +configure:13501: $? = 0 +configure:13521: result: yes +configure:13529: checking for vsnprintf +configure:13585: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c:98: warning: conflicting types for built-in function 'vsnprintf' +configure:13592: $? = 0 +configure:13612: result: yes +configure:13621: checking whether your system's snprintf is C99 compliant +configure:13651: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:13655: $? = 0 +configure:13661: ./conftest +configure:13665: $? = 0 +configure:13682: result: yes +configure:13688: checking whether your system's vsnprintf is C99 compliant +configure:13728: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:13732: $? = 0 +configure:13738: ./conftest +configure:13742: $? = 0 +configure:13759: result: yes +configure:13787: checking for va_copy +configure:13810: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c: In function 'main': +conftest.c:81: warning: 'ap2' is used uninitialized in this function +configure:13817: $? = 0 +configure:13825: result: va_copy +configure:13903: checking for ftruncate +configure:13959: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:13966: $? = 0 +configure:13988: result: yes +configure:14081: checking for strftime +configure:14137: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c:101: warning: conflicting types for built-in function 'strftime' +configure:14144: $? = 0 +configure:14166: result: yes +configure:14259: checking for fchdir +configure:14315: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:14322: $? = 0 +configure:14344: result: yes +configure:14368: checking for regcomp +configure:14424: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:14431: $? = 0 +configure:14453: result: yes +configure:14471: checking whether your system's regexp library is completely broken +configure:14496: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +conftest.c:84: warning: return type defaults to 'int' +configure:14500: $? = 0 +configure:14506: ./conftest +configure:14510: $? = 0 +configure:14527: result: no +configure:14614: checking if /var/mail is world writable +configure:14647: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:14651: $? = 0 +configure:14657: ./conftest +configure:14661: $? = 1 +configure: program exited with status 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| #define HAVE_SYSEXITS_H 1 +| #define HAVE_SYS_TIME_H 1 +| #define HAVE_SYS_RESOURCE_H 1 +| #define HAVE_SETRLIMIT 1 +| #define HAVE_GETSID 1 +| #define RETSIGTYPE void +| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t +| #define HAVE_DECL_SYS_SIGLIST 1 +| #define HAVE_FGETPOS 1 +| #define HAVE_MEMMOVE 1 +| #define HAVE_SETEGID 1 +| #define HAVE_SRAND48 1 +| #define HAVE_STRERROR 1 +| #define HAVE_SETENV 1 +| #define HAVE_STRCASECMP 1 +| #define HAVE_STRDUP 1 +| #define HAVE_STRSEP 1 +| #define HAVE_STRTOK_R 1 +| #define HAVE_GETOPT_H 1 +| #define HAVE_SNPRINTF 1 +| #define HAVE_VSNPRINTF 1 +| #define HAVE_FTRUNCATE 1 +| #define HAVE_STRFTIME 1 +| #define HAVE_FCHDIR 1 +| #define HAVE_REGCOMP 1 +| #define MAILPATH "/var/mail" +| /* end confdefs.h. */ +| #include +| #include +| #include +| +| int main (int argc, char **argv) +| { +| struct stat s; +| +| stat ("/var/mail", &s); +| if (s.st_mode & S_IWOTH) exit (0); +| exit (1); +| } +configure:14678: result: no +configure:14690: checking if /var/mail is group writable +configure:14723: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:14727: $? = 0 +configure:14733: ./conftest +configure:14737: $? = 0 +configure:14754: result: yes +configure:14799: checking where to put the documentation +configure:14809: result: /usr/share/doc +configure:14923: checking sys/select.h usability +configure:14940: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:14947: $? = 0 +configure:14961: result: yes +configure:14965: checking sys/select.h presence +configure:14980: gcc -E -I/usr/include/qdbm conftest.c +configure:14987: $? = 0 +configure:15001: result: yes +configure:15029: checking for sys/select.h +configure:15038: result: yes +configure:15053: checking for socklen_t +configure:15066: result: yes +configure:15079: checking for gethostent +configure:15135: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:15142: $? = 0 +configure:15162: result: yes +configure:15244: checking for setsockopt +configure:15300: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:15307: $? = 0 +configure:15327: result: yes +configure:15413: checking for getaddrinfo +configure:15469: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5 +configure:15476: $? = 0 +configure:15498: result: yes +configure:15545: checking for krb5-config +configure:15563: found /usr/bin/krb5-config +configure:15576: result: /usr/bin/krb5-config +configure:15833: checking GSSAPI implementation +configure:15835: result: MIT +configure:16370: checking for pkg-config +configure:16388: found /usr/bin/pkg-config +configure:16400: result: /usr/bin/pkg-config +configure:16425: checking pkg-config is at least version 0.9.0 +configure:16428: result: yes +configure:16439: checking for GNUTLS +configure:16447: $PKG_CONFIG --exists --print-errors "gnutls" +configure:16450: $? = 0 +configure:16465: $PKG_CONFIG --exists --print-errors "gnutls" +configure:16468: $? = 0 +configure:16510: result: yes +configure:16562: checking for sasl_client_init in -lsasl2 +configure:16597: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm conftest.c -lsasl2 >&5 +configure:16604: $? = 0 +configure:16625: result: yes +configure:16704: checking whether struct dirent defines d_ino +configure:16728: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm conftest.c >&5 +configure:16735: $? = 0 +configure:16761: result: yes +configure:17433: checking for gdbm_open +configure:17461: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c -lgdbm >&5 +configure:17468: $? = 0 +configure:17489: result: yes +configure:17650: checking for off_t +configure:17678: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +configure:17685: $? = 0 +configure:17712: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +conftest.c: In function 'main': +conftest.c:139: error: expected expression before ')' token +configure:17719: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| #define HAVE_SYSEXITS_H 1 +| #define HAVE_SYS_TIME_H 1 +| #define HAVE_SYS_RESOURCE_H 1 +| #define HAVE_SETRLIMIT 1 +| #define HAVE_GETSID 1 +| #define RETSIGTYPE void +| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t +| #define HAVE_DECL_SYS_SIGLIST 1 +| #define HAVE_FGETPOS 1 +| #define HAVE_MEMMOVE 1 +| #define HAVE_SETEGID 1 +| #define HAVE_SRAND48 1 +| #define HAVE_STRERROR 1 +| #define HAVE_SETENV 1 +| #define HAVE_STRCASECMP 1 +| #define HAVE_STRDUP 1 +| #define HAVE_STRSEP 1 +| #define HAVE_STRTOK_R 1 +| #define HAVE_GETOPT_H 1 +| #define HAVE_SNPRINTF 1 +| #define HAVE_VSNPRINTF 1 +| #define HAVE_FTRUNCATE 1 +| #define HAVE_STRFTIME 1 +| #define HAVE_FCHDIR 1 +| #define HAVE_REGCOMP 1 +| #define MAILPATH "/var/mail" +| #define USE_DOTLOCK 1 +| #define USE_SETGID 1 +| #define DL_STANDALONE 1 +| #define USE_POP 1 +| #define USE_IMAP 1 +| #define USE_SMTP 1 +| #define HAVE_SYS_SELECT_H 1 +| #define HAVE_GETADDRINFO 1 +| #define USE_SOCKET 1 +| #define USE_GSS 1 +| #define USE_SSL 1 +| #define USE_SSL_GNUTLS 1 +| #define HAVE_LIBSASL2 1 +| #define USE_SASL 1 +| #define DEBUG 1 +| #define USE_FCNTL 1 +| #define HAVE_DIRENT_D_INO 1 +| #define USE_COMPRESSED 1 +| #define EXECSHELL "/bin/sh" +| #define USE_HCACHE 1 +| #define HAVE_GDBM 1 +| /* end confdefs.h. */ +| #include +| #ifdef HAVE_SYS_TYPES_H +| # include +| #endif +| #ifdef HAVE_SYS_STAT_H +| # include +| #endif +| #ifdef STDC_HEADERS +| # include +| # include +| #else +| # ifdef HAVE_STDLIB_H +| # include +| # endif +| #endif +| #ifdef HAVE_STRING_H +| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H +| # include +| # endif +| # include +| #endif +| #ifdef HAVE_STRINGS_H +| # include +| #endif +| #ifdef HAVE_INTTYPES_H +| # include +| #endif +| #ifdef HAVE_STDINT_H +| # include +| #endif +| #ifdef HAVE_UNISTD_H +| # include +| #endif +| int +| main () +| { +| if (sizeof ((off_t))) +| return 0; +| ; +| return 0; +| } +configure:17742: result: yes +configure:17754: checking for size_t +configure:17782: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +configure:17789: $? = 0 +configure:17816: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +conftest.c: In function 'main': +conftest.c:139: error: expected expression before ')' token +configure:17823: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| #define HAVE_SYSEXITS_H 1 +| #define HAVE_SYS_TIME_H 1 +| #define HAVE_SYS_RESOURCE_H 1 +| #define HAVE_SETRLIMIT 1 +| #define HAVE_GETSID 1 +| #define RETSIGTYPE void +| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t +| #define HAVE_DECL_SYS_SIGLIST 1 +| #define HAVE_FGETPOS 1 +| #define HAVE_MEMMOVE 1 +| #define HAVE_SETEGID 1 +| #define HAVE_SRAND48 1 +| #define HAVE_STRERROR 1 +| #define HAVE_SETENV 1 +| #define HAVE_STRCASECMP 1 +| #define HAVE_STRDUP 1 +| #define HAVE_STRSEP 1 +| #define HAVE_STRTOK_R 1 +| #define HAVE_GETOPT_H 1 +| #define HAVE_SNPRINTF 1 +| #define HAVE_VSNPRINTF 1 +| #define HAVE_FTRUNCATE 1 +| #define HAVE_STRFTIME 1 +| #define HAVE_FCHDIR 1 +| #define HAVE_REGCOMP 1 +| #define MAILPATH "/var/mail" +| #define USE_DOTLOCK 1 +| #define USE_SETGID 1 +| #define DL_STANDALONE 1 +| #define USE_POP 1 +| #define USE_IMAP 1 +| #define USE_SMTP 1 +| #define HAVE_SYS_SELECT_H 1 +| #define HAVE_GETADDRINFO 1 +| #define USE_SOCKET 1 +| #define USE_GSS 1 +| #define USE_SSL 1 +| #define USE_SSL_GNUTLS 1 +| #define HAVE_LIBSASL2 1 +| #define USE_SASL 1 +| #define DEBUG 1 +| #define USE_FCNTL 1 +| #define HAVE_DIRENT_D_INO 1 +| #define USE_COMPRESSED 1 +| #define EXECSHELL "/bin/sh" +| #define USE_HCACHE 1 +| #define HAVE_GDBM 1 +| /* end confdefs.h. */ +| #include +| #ifdef HAVE_SYS_TYPES_H +| # include +| #endif +| #ifdef HAVE_SYS_STAT_H +| # include +| #endif +| #ifdef STDC_HEADERS +| # include +| # include +| #else +| # ifdef HAVE_STDLIB_H +| # include +| # endif +| #endif +| #ifdef HAVE_STRING_H +| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H +| # include +| # endif +| # include +| #endif +| #ifdef HAVE_STRINGS_H +| # include +| #endif +| #ifdef HAVE_INTTYPES_H +| # include +| #endif +| #ifdef HAVE_STDINT_H +| # include +| #endif +| #ifdef HAVE_UNISTD_H +| # include +| #endif +| int +| main () +| { +| if (sizeof ((size_t))) +| return 0; +| ; +| return 0; +| } +configure:17846: result: yes +configure:17860: checking for working alloca.h +configure:17887: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:17894: $? = 0 +configure:17914: result: yes +configure:17924: checking for alloca +configure:17971: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:17978: $? = 0 +configure:17998: result: yes +configure:18241: checking for stdlib.h +configure:18248: result: yes +configure:18241: checking for unistd.h +configure:18248: result: yes +configure:18386: checking for getpagesize +configure:18442: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18449: $? = 0 +configure:18471: result: yes +configure:18483: checking for working mmap +configure:18630: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18634: $? = 0 +configure:18640: ./conftest +configure:18644: $? = 0 +configure:18661: result: yes +configure:18673: checking whether we are using the GNU C Library 2.1 or newer +configure:18704: result: yes +configure:18737: checking argz.h usability +configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +configure:18761: $? = 0 +configure:18775: result: yes +configure:18779: checking argz.h presence +configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c +configure:18801: $? = 0 +configure:18815: result: yes +configure:18843: checking for argz.h +configure:18852: result: yes +configure:18737: checking limits.h usability +configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +configure:18761: $? = 0 +configure:18775: result: yes +configure:18779: checking limits.h presence +configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c +configure:18801: $? = 0 +configure:18815: result: yes +configure:18843: checking for limits.h +configure:18852: result: yes +configure:18737: checking locale.h usability +configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +configure:18761: $? = 0 +configure:18775: result: yes +configure:18779: checking locale.h presence +configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c +configure:18801: $? = 0 +configure:18815: result: yes +configure:18843: checking for locale.h +configure:18852: result: yes +configure:18737: checking nl_types.h usability +configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +configure:18761: $? = 0 +configure:18775: result: yes +configure:18779: checking nl_types.h presence +configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c +configure:18801: $? = 0 +configure:18815: result: yes +configure:18843: checking for nl_types.h +configure:18852: result: yes +configure:18737: checking malloc.h usability +configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +configure:18761: $? = 0 +configure:18775: result: yes +configure:18779: checking malloc.h presence +configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c +configure:18801: $? = 0 +configure:18815: result: yes +configure:18843: checking for malloc.h +configure:18852: result: yes +configure:18737: checking stddef.h usability +configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +configure:18761: $? = 0 +configure:18775: result: yes +configure:18779: checking stddef.h presence +configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c +configure:18801: $? = 0 +configure:18815: result: yes +configure:18843: checking for stddef.h +configure:18852: result: yes +configure:18726: checking for stdlib.h +configure:18733: result: yes +configure:18726: checking for string.h +configure:18733: result: yes +configure:18726: checking for unistd.h +configure:18733: result: yes +configure:18737: checking sys/param.h usability +configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +configure:18761: $? = 0 +configure:18775: result: yes +configure:18779: checking sys/param.h presence +configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c +configure:18801: $? = 0 +configure:18815: result: yes +configure:18843: checking for sys/param.h +configure:18852: result: yes +configure:18893: checking for feof_unlocked +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for fgets_unlocked +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for getcwd +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for getegid +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for geteuid +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for getgid +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for getuid +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for mempcpy +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +conftest.c:149: warning: conflicting types for built-in function 'mempcpy' +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for munmap +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for putenv +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for setenv +configure:18978: result: yes +configure:18893: checking for setlocale +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for stpcpy +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +conftest.c:154: warning: conflicting types for built-in function 'stpcpy' +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for strchr +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +conftest.c:155: warning: conflicting types for built-in function 'strchr' +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for strcasecmp +configure:18978: result: yes +configure:18893: checking for strdup +configure:18978: result: yes +configure:18893: checking for strtoul +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for tsearch +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for __argz_count +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for __argz_stringify +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:18893: checking for __argz_next +configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:18956: $? = 0 +configure:18978: result: yes +configure:19005: checking for iconv +configure:19037: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:19044: $? = 0 +configure:19121: result: yes +configure:19129: checking for iconv declaration +configure:19168: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +configure:19175: $? = 0 +configure:19194: result: + extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft); +configure:19210: checking for nl_langinfo and CODESET +configure:19236: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +conftest.c: In function 'main': +conftest.c:146: warning: unused variable 'cs' +configure:19243: $? = 0 +configure:19264: result: yes +configure:19275: checking for LC_MESSAGES +configure:19301: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:19308: $? = 0 +configure:19328: result: yes +configure:19338: checking whether NLS is requested +configure:19347: result: yes +configure:19361: checking whether included gettext is requested +configure:19371: result: no +configure:19391: checking libintl.h usability +configure:19408: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +configure:19415: $? = 0 +configure:19429: result: yes +configure:19433: checking libintl.h presence +configure:19448: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c +configure:19455: $? = 0 +configure:19469: result: yes +configure:19497: checking for libintl.h +configure:19504: result: yes +configure:19509: checking for GNU gettext in libc +configure:19537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:19544: $? = 0 +configure:19564: result: yes +configure:19649: checking for dcgettext +configure:19705: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +conftest.c:169: warning: conflicting types for built-in function 'dcgettext' +configure:19712: $? = 0 +configure:19734: result: yes +configure:19750: checking for msgfmt +configure:19777: result: /usr/bin/msgfmt +configure:19786: checking for gmsgfmt +configure:19817: result: /usr/bin/msgfmt +configure:19828: checking for xgettext +configure:19855: result: /usr/bin/xgettext +configure:20032: checking for bison +configure:20048: found /usr/bin/bison +configure:20059: result: bison +configure:20073: checking version of bison +configure:20082: result: 2.4.1, ok +configure:20121: checking for catalogs to be installed +configure:20141: result: de eu ru it es uk fr pl nl cs id sk ko el zh_TW zh_CN pt_BR eo gl sv da lt tr ja hu et ca bg ga +configure:20185: checking iconv.h usability +configure:20202: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5 +configure:20209: $? = 0 +configure:20223: result: yes +configure:20227: checking iconv.h presence +configure:20242: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c +configure:20249: $? = 0 +configure:20263: result: yes +configure:20291: checking for iconv.h +configure:20300: result: yes +configure:20310: checking whether iconv.h defines iconv_t +configure:20323: result: yes +configure:20341: checking whether this iconv is good enough +configure:20379: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +configure:20383: $? = 0 +configure:20389: ./conftest +configure:20393: $? = 0 +configure:20411: result: yes +configure:20419: checking whether iconv is non-transcribing +configure:20458: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5 +conftest.c: In function 'main': +conftest.c:162: warning: passing argument 2 of 'iconv' from incompatible pointer type +configure:20462: $? = 0 +configure:20468: ./conftest +configure:20472: $? = 0 +configure:20490: result: no +configure:20519: checking for bind_textdomain_codeset +configure:20575: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c >&5 +configure:20582: $? = 0 +configure:20604: result: yes +configure:20647: checking for library containing stringprep_check_version +configure:20688: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c >&5 +/tmp/ccCU8kre.o: In function `main': +/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/conftest.c:162: undefined reference to `stringprep_check_version' +collect2: ld returned 1 exit status +configure:20695: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| #define HAVE_SYSEXITS_H 1 +| #define HAVE_SYS_TIME_H 1 +| #define HAVE_SYS_RESOURCE_H 1 +| #define HAVE_SETRLIMIT 1 +| #define HAVE_GETSID 1 +| #define RETSIGTYPE void +| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t +| #define HAVE_DECL_SYS_SIGLIST 1 +| #define HAVE_FGETPOS 1 +| #define HAVE_MEMMOVE 1 +| #define HAVE_SETEGID 1 +| #define HAVE_SRAND48 1 +| #define HAVE_STRERROR 1 +| #define HAVE_SETENV 1 +| #define HAVE_STRCASECMP 1 +| #define HAVE_STRDUP 1 +| #define HAVE_STRSEP 1 +| #define HAVE_STRTOK_R 1 +| #define HAVE_GETOPT_H 1 +| #define HAVE_SNPRINTF 1 +| #define HAVE_VSNPRINTF 1 +| #define HAVE_FTRUNCATE 1 +| #define HAVE_STRFTIME 1 +| #define HAVE_FCHDIR 1 +| #define HAVE_REGCOMP 1 +| #define MAILPATH "/var/mail" +| #define USE_DOTLOCK 1 +| #define USE_SETGID 1 +| #define DL_STANDALONE 1 +| #define USE_POP 1 +| #define USE_IMAP 1 +| #define USE_SMTP 1 +| #define HAVE_SYS_SELECT_H 1 +| #define HAVE_GETADDRINFO 1 +| #define USE_SOCKET 1 +| #define USE_GSS 1 +| #define USE_SSL 1 +| #define USE_SSL_GNUTLS 1 +| #define HAVE_LIBSASL2 1 +| #define USE_SASL 1 +| #define DEBUG 1 +| #define USE_FCNTL 1 +| #define HAVE_DIRENT_D_INO 1 +| #define USE_COMPRESSED 1 +| #define EXECSHELL "/bin/sh" +| #define USE_HCACHE 1 +| #define HAVE_GDBM 1 +| #define HAVE_ALLOCA_H 1 +| #define HAVE_ALLOCA 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_UNISTD_H 1 +| #define HAVE_GETPAGESIZE 1 +| #define HAVE_MMAP 1 +| #define HAVE_ARGZ_H 1 +| #define HAVE_LIMITS_H 1 +| #define HAVE_LOCALE_H 1 +| #define HAVE_NL_TYPES_H 1 +| #define HAVE_MALLOC_H 1 +| #define HAVE_STDDEF_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_UNISTD_H 1 +| #define HAVE_SYS_PARAM_H 1 +| #define HAVE_FEOF_UNLOCKED 1 +| #define HAVE_FGETS_UNLOCKED 1 +| #define HAVE_GETCWD 1 +| #define HAVE_GETEGID 1 +| #define HAVE_GETEUID 1 +| #define HAVE_GETGID 1 +| #define HAVE_GETUID 1 +| #define HAVE_MEMPCPY 1 +| #define HAVE_MUNMAP 1 +| #define HAVE_PUTENV 1 +| #define HAVE_SETENV 1 +| #define HAVE_SETLOCALE 1 +| #define HAVE_STPCPY 1 +| #define HAVE_STRCHR 1 +| #define HAVE_STRCASECMP 1 +| #define HAVE_STRDUP 1 +| #define HAVE_STRTOUL 1 +| #define HAVE_TSEARCH 1 +| #define HAVE___ARGZ_COUNT 1 +| #define HAVE___ARGZ_STRINGIFY 1 +| #define HAVE___ARGZ_NEXT 1 +| #define HAVE_ICONV 1 +| #define ICONV_CONST +| #define HAVE_LANGINFO_CODESET 1 +| #define HAVE_LC_MESSAGES 1 +| #define ENABLE_NLS 1 +| #define HAVE_GETTEXT 1 +| #define HAVE_DCGETTEXT 1 +| #define HAVE_ICONV_H 1 +| #define HAVE_ICONV_T_DEF 1 +| #define ICONV_NONTRANS 0 +| #define HAVE_BIND_TEXTDOMAIN_CODESET 1 +| /* end confdefs.h. */ +| +| /* Override any GCC internal prototype to avoid an error. +| Use char because int might match the return type of a GCC +| builtin and then its argument prototype would still apply. */ +| #ifdef __cplusplus +| extern "C" +| #endif +| char stringprep_check_version (); +| int +| main () +| { +| return stringprep_check_version (); +| ; +| return 0; +| } +configure:20688: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +configure:20695: $? = 0 +configure:20726: result: -lidn +configure:20746: checking for idna_to_unicode_utf8_from_utf8 +configure:20802: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +/tmp/ccstCW6K.o: In function `main': +/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/conftest.c:186: undefined reference to `idna_to_unicode_utf8_from_utf8' +collect2: ld returned 1 exit status +configure:20809: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| #define HAVE_SYSEXITS_H 1 +| #define HAVE_SYS_TIME_H 1 +| #define HAVE_SYS_RESOURCE_H 1 +| #define HAVE_SETRLIMIT 1 +| #define HAVE_GETSID 1 +| #define RETSIGTYPE void +| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t +| #define HAVE_DECL_SYS_SIGLIST 1 +| #define HAVE_FGETPOS 1 +| #define HAVE_MEMMOVE 1 +| #define HAVE_SETEGID 1 +| #define HAVE_SRAND48 1 +| #define HAVE_STRERROR 1 +| #define HAVE_SETENV 1 +| #define HAVE_STRCASECMP 1 +| #define HAVE_STRDUP 1 +| #define HAVE_STRSEP 1 +| #define HAVE_STRTOK_R 1 +| #define HAVE_GETOPT_H 1 +| #define HAVE_SNPRINTF 1 +| #define HAVE_VSNPRINTF 1 +| #define HAVE_FTRUNCATE 1 +| #define HAVE_STRFTIME 1 +| #define HAVE_FCHDIR 1 +| #define HAVE_REGCOMP 1 +| #define MAILPATH "/var/mail" +| #define USE_DOTLOCK 1 +| #define USE_SETGID 1 +| #define DL_STANDALONE 1 +| #define USE_POP 1 +| #define USE_IMAP 1 +| #define USE_SMTP 1 +| #define HAVE_SYS_SELECT_H 1 +| #define HAVE_GETADDRINFO 1 +| #define USE_SOCKET 1 +| #define USE_GSS 1 +| #define USE_SSL 1 +| #define USE_SSL_GNUTLS 1 +| #define HAVE_LIBSASL2 1 +| #define USE_SASL 1 +| #define DEBUG 1 +| #define USE_FCNTL 1 +| #define HAVE_DIRENT_D_INO 1 +| #define USE_COMPRESSED 1 +| #define EXECSHELL "/bin/sh" +| #define USE_HCACHE 1 +| #define HAVE_GDBM 1 +| #define HAVE_ALLOCA_H 1 +| #define HAVE_ALLOCA 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_UNISTD_H 1 +| #define HAVE_GETPAGESIZE 1 +| #define HAVE_MMAP 1 +| #define HAVE_ARGZ_H 1 +| #define HAVE_LIMITS_H 1 +| #define HAVE_LOCALE_H 1 +| #define HAVE_NL_TYPES_H 1 +| #define HAVE_MALLOC_H 1 +| #define HAVE_STDDEF_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_UNISTD_H 1 +| #define HAVE_SYS_PARAM_H 1 +| #define HAVE_FEOF_UNLOCKED 1 +| #define HAVE_FGETS_UNLOCKED 1 +| #define HAVE_GETCWD 1 +| #define HAVE_GETEGID 1 +| #define HAVE_GETEUID 1 +| #define HAVE_GETGID 1 +| #define HAVE_GETUID 1 +| #define HAVE_MEMPCPY 1 +| #define HAVE_MUNMAP 1 +| #define HAVE_PUTENV 1 +| #define HAVE_SETENV 1 +| #define HAVE_SETLOCALE 1 +| #define HAVE_STPCPY 1 +| #define HAVE_STRCHR 1 +| #define HAVE_STRCASECMP 1 +| #define HAVE_STRDUP 1 +| #define HAVE_STRTOUL 1 +| #define HAVE_TSEARCH 1 +| #define HAVE___ARGZ_COUNT 1 +| #define HAVE___ARGZ_STRINGIFY 1 +| #define HAVE___ARGZ_NEXT 1 +| #define HAVE_ICONV 1 +| #define ICONV_CONST +| #define HAVE_LANGINFO_CODESET 1 +| #define HAVE_LC_MESSAGES 1 +| #define ENABLE_NLS 1 +| #define HAVE_GETTEXT 1 +| #define HAVE_DCGETTEXT 1 +| #define HAVE_ICONV_H 1 +| #define HAVE_ICONV_T_DEF 1 +| #define ICONV_NONTRANS 0 +| #define HAVE_BIND_TEXTDOMAIN_CODESET 1 +| #define HAVE_LIBIDN 1 +| /* end confdefs.h. */ +| /* Define idna_to_unicode_utf8_from_utf8 to an innocuous variant, in case declares idna_to_unicode_utf8_from_utf8. +| For example, HP-UX 11i declares gettimeofday. */ +| #define idna_to_unicode_utf8_from_utf8 innocuous_idna_to_unicode_utf8_from_utf8 +| +| /* System header to define __stub macros and hopefully few prototypes, +| which can conflict with char idna_to_unicode_utf8_from_utf8 (); below. +| Prefer to if __STDC__ is defined, since +| exists even on freestanding compilers. */ +| +| #ifdef __STDC__ +| # include +| #else +| # include +| #endif +| +| #undef idna_to_unicode_utf8_from_utf8 +| +| /* Override any GCC internal prototype to avoid an error. +| Use char because int might match the return type of a GCC +| builtin and then its argument prototype would still apply. */ +| #ifdef __cplusplus +| extern "C" +| #endif +| char idna_to_unicode_utf8_from_utf8 (); +| /* The GNU C library defines this for functions which it implements +| to always fail with ENOSYS. Some functions are actually named +| something starting with __ and the normal name is an alias. */ +| #if defined __stub_idna_to_unicode_utf8_from_utf8 || defined __stub___idna_to_unicode_utf8_from_utf8 +| choke me +| #endif +| +| int +| main () +| { +| return idna_to_unicode_utf8_from_utf8 (); +| ; +| return 0; +| } +configure:20831: result: no +configure:20746: checking for idna_to_unicode_8z8z +configure:20802: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +configure:20809: $? = 0 +configure:20831: result: yes +configure:20848: checking for idna_to_ascii_from_utf8 +configure:20904: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +/tmp/ccWw2b3k.o: In function `main': +/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/conftest.c:187: undefined reference to `idna_to_ascii_from_utf8' +collect2: ld returned 1 exit status +configure:20911: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| #define HAVE_SYSEXITS_H 1 +| #define HAVE_SYS_TIME_H 1 +| #define HAVE_SYS_RESOURCE_H 1 +| #define HAVE_SETRLIMIT 1 +| #define HAVE_GETSID 1 +| #define RETSIGTYPE void +| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t +| #define HAVE_DECL_SYS_SIGLIST 1 +| #define HAVE_FGETPOS 1 +| #define HAVE_MEMMOVE 1 +| #define HAVE_SETEGID 1 +| #define HAVE_SRAND48 1 +| #define HAVE_STRERROR 1 +| #define HAVE_SETENV 1 +| #define HAVE_STRCASECMP 1 +| #define HAVE_STRDUP 1 +| #define HAVE_STRSEP 1 +| #define HAVE_STRTOK_R 1 +| #define HAVE_GETOPT_H 1 +| #define HAVE_SNPRINTF 1 +| #define HAVE_VSNPRINTF 1 +| #define HAVE_FTRUNCATE 1 +| #define HAVE_STRFTIME 1 +| #define HAVE_FCHDIR 1 +| #define HAVE_REGCOMP 1 +| #define MAILPATH "/var/mail" +| #define USE_DOTLOCK 1 +| #define USE_SETGID 1 +| #define DL_STANDALONE 1 +| #define USE_POP 1 +| #define USE_IMAP 1 +| #define USE_SMTP 1 +| #define HAVE_SYS_SELECT_H 1 +| #define HAVE_GETADDRINFO 1 +| #define USE_SOCKET 1 +| #define USE_GSS 1 +| #define USE_SSL 1 +| #define USE_SSL_GNUTLS 1 +| #define HAVE_LIBSASL2 1 +| #define USE_SASL 1 +| #define DEBUG 1 +| #define USE_FCNTL 1 +| #define HAVE_DIRENT_D_INO 1 +| #define USE_COMPRESSED 1 +| #define EXECSHELL "/bin/sh" +| #define USE_HCACHE 1 +| #define HAVE_GDBM 1 +| #define HAVE_ALLOCA_H 1 +| #define HAVE_ALLOCA 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_UNISTD_H 1 +| #define HAVE_GETPAGESIZE 1 +| #define HAVE_MMAP 1 +| #define HAVE_ARGZ_H 1 +| #define HAVE_LIMITS_H 1 +| #define HAVE_LOCALE_H 1 +| #define HAVE_NL_TYPES_H 1 +| #define HAVE_MALLOC_H 1 +| #define HAVE_STDDEF_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_UNISTD_H 1 +| #define HAVE_SYS_PARAM_H 1 +| #define HAVE_FEOF_UNLOCKED 1 +| #define HAVE_FGETS_UNLOCKED 1 +| #define HAVE_GETCWD 1 +| #define HAVE_GETEGID 1 +| #define HAVE_GETEUID 1 +| #define HAVE_GETGID 1 +| #define HAVE_GETUID 1 +| #define HAVE_MEMPCPY 1 +| #define HAVE_MUNMAP 1 +| #define HAVE_PUTENV 1 +| #define HAVE_SETENV 1 +| #define HAVE_SETLOCALE 1 +| #define HAVE_STPCPY 1 +| #define HAVE_STRCHR 1 +| #define HAVE_STRCASECMP 1 +| #define HAVE_STRDUP 1 +| #define HAVE_STRTOUL 1 +| #define HAVE_TSEARCH 1 +| #define HAVE___ARGZ_COUNT 1 +| #define HAVE___ARGZ_STRINGIFY 1 +| #define HAVE___ARGZ_NEXT 1 +| #define HAVE_ICONV 1 +| #define ICONV_CONST +| #define HAVE_LANGINFO_CODESET 1 +| #define HAVE_LC_MESSAGES 1 +| #define ENABLE_NLS 1 +| #define HAVE_GETTEXT 1 +| #define HAVE_DCGETTEXT 1 +| #define HAVE_ICONV_H 1 +| #define HAVE_ICONV_T_DEF 1 +| #define ICONV_NONTRANS 0 +| #define HAVE_BIND_TEXTDOMAIN_CODESET 1 +| #define HAVE_LIBIDN 1 +| #define HAVE_IDNA_TO_UNICODE_8Z8Z 1 +| /* end confdefs.h. */ +| /* Define idna_to_ascii_from_utf8 to an innocuous variant, in case declares idna_to_ascii_from_utf8. +| For example, HP-UX 11i declares gettimeofday. */ +| #define idna_to_ascii_from_utf8 innocuous_idna_to_ascii_from_utf8 +| +| /* System header to define __stub macros and hopefully few prototypes, +| which can conflict with char idna_to_ascii_from_utf8 (); below. +| Prefer to if __STDC__ is defined, since +| exists even on freestanding compilers. */ +| +| #ifdef __STDC__ +| # include +| #else +| # include +| #endif +| +| #undef idna_to_ascii_from_utf8 +| +| /* Override any GCC internal prototype to avoid an error. +| Use char because int might match the return type of a GCC +| builtin and then its argument prototype would still apply. */ +| #ifdef __cplusplus +| extern "C" +| #endif +| char idna_to_ascii_from_utf8 (); +| /* The GNU C library defines this for functions which it implements +| to always fail with ENOSYS. Some functions are actually named +| something starting with __ and the normal name is an alias. */ +| #if defined __stub_idna_to_ascii_from_utf8 || defined __stub___idna_to_ascii_from_utf8 +| choke me +| #endif +| +| int +| main () +| { +| return idna_to_ascii_from_utf8 (); +| ; +| return 0; +| } +configure:20933: result: no +configure:20848: checking for idna_to_ascii_8z +configure:20904: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +configure:20911: $? = 0 +configure:20933: result: yes +configure:20950: checking for idna_to_ascii_lz +configure:21006: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +configure:21013: $? = 0 +configure:21035: result: yes +configure:20950: checking for idna_to_ascii_from_locale +configure:21006: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +/tmp/ccwwbzQR.o: In function `main': +/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/conftest.c:189: undefined reference to `idna_to_ascii_from_locale' +collect2: ld returned 1 exit status +configure:21013: $? = 1 +configure: failed program was: +| /* confdefs.h. */ +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define PACKAGE "mutt" +| #define VERSION "1.5.19" +| #define STDC_HEADERS 1 +| #define HAVE_SYS_TYPES_H 1 +| #define HAVE_SYS_STAT_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_MEMORY_H 1 +| #define HAVE_STRINGS_H 1 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_STDINT_H 1 +| #define HAVE_UNISTD_H 1 +| #define __EXTENSIONS__ 1 +| #define _ALL_SOURCE 1 +| #define _GNU_SOURCE 1 +| #define _POSIX_PTHREAD_SEMANTICS 1 +| #define _TANDEM_SOURCE 1 +| #define PROTOTYPES 1 +| #define __PROTOTYPES 1 +| #define HAVE_STRING_H 1 +| #define _FILE_OFFSET_BITS 64 +| #define HAVE_FSEEKO 1 +| #define SIZEOF_OFF_T 8 +| #define HAVE_INTTYPES_H 1 +| #define HAVE_C99_INTTYPES 1 +| #define SIZEOF_SHORT 2 +| #define SIZEOF_INT 4 +| #define SIZEOF_LONG 4 +| #define SIZEOF_LONG_LONG 8 +| #define SENDMAIL "/usr/sbin/sendmail" +| #define CRYPT_BACKEND_GPGME 1 +| #define HAVE_GPGME_PKA_TRUST 1 +| #define CRYPT_BACKEND_GPGME 1 +| #define CRYPT_BACKEND_CLASSIC_PGP 1 +| #define CRYPT_BACKEND_CLASSIC_SMIME 1 +| #define MIXMASTER "mixmaster" +| #define HAVE_NCURSESW_NCURSES_H 1 +| #define HAVE_START_COLOR 1 +| #define HAVE_TYPEAHEAD 1 +| #define HAVE_BKGDSET 1 +| #define HAVE_CURS_SET 1 +| #define HAVE_META 1 +| #define HAVE_USE_DEFAULT_COLORS 1 +| #define HAVE_RESIZETERM 1 +| #define HAVE_COLOR 1 +| #define STDC_HEADERS 1 +| #define HAVE_STDARG_H 1 +| #define HAVE_SYS_IOCTL_H 1 +| #define HAVE_SYSEXITS_H 1 +| #define HAVE_SYS_TIME_H 1 +| #define HAVE_SYS_RESOURCE_H 1 +| #define HAVE_SETRLIMIT 1 +| #define HAVE_GETSID 1 +| #define RETSIGTYPE void +| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t +| #define HAVE_DECL_SYS_SIGLIST 1 +| #define HAVE_FGETPOS 1 +| #define HAVE_MEMMOVE 1 +| #define HAVE_SETEGID 1 +| #define HAVE_SRAND48 1 +| #define HAVE_STRERROR 1 +| #define HAVE_SETENV 1 +| #define HAVE_STRCASECMP 1 +| #define HAVE_STRDUP 1 +| #define HAVE_STRSEP 1 +| #define HAVE_STRTOK_R 1 +| #define HAVE_GETOPT_H 1 +| #define HAVE_SNPRINTF 1 +| #define HAVE_VSNPRINTF 1 +| #define HAVE_FTRUNCATE 1 +| #define HAVE_STRFTIME 1 +| #define HAVE_FCHDIR 1 +| #define HAVE_REGCOMP 1 +| #define MAILPATH "/var/mail" +| #define USE_DOTLOCK 1 +| #define USE_SETGID 1 +| #define DL_STANDALONE 1 +| #define USE_POP 1 +| #define USE_IMAP 1 +| #define USE_SMTP 1 +| #define HAVE_SYS_SELECT_H 1 +| #define HAVE_GETADDRINFO 1 +| #define USE_SOCKET 1 +| #define USE_GSS 1 +| #define USE_SSL 1 +| #define USE_SSL_GNUTLS 1 +| #define HAVE_LIBSASL2 1 +| #define USE_SASL 1 +| #define DEBUG 1 +| #define USE_FCNTL 1 +| #define HAVE_DIRENT_D_INO 1 +| #define USE_COMPRESSED 1 +| #define EXECSHELL "/bin/sh" +| #define USE_HCACHE 1 +| #define HAVE_GDBM 1 +| #define HAVE_ALLOCA_H 1 +| #define HAVE_ALLOCA 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_UNISTD_H 1 +| #define HAVE_GETPAGESIZE 1 +| #define HAVE_MMAP 1 +| #define HAVE_ARGZ_H 1 +| #define HAVE_LIMITS_H 1 +| #define HAVE_LOCALE_H 1 +| #define HAVE_NL_TYPES_H 1 +| #define HAVE_MALLOC_H 1 +| #define HAVE_STDDEF_H 1 +| #define HAVE_STDLIB_H 1 +| #define HAVE_STRING_H 1 +| #define HAVE_UNISTD_H 1 +| #define HAVE_SYS_PARAM_H 1 +| #define HAVE_FEOF_UNLOCKED 1 +| #define HAVE_FGETS_UNLOCKED 1 +| #define HAVE_GETCWD 1 +| #define HAVE_GETEGID 1 +| #define HAVE_GETEUID 1 +| #define HAVE_GETGID 1 +| #define HAVE_GETUID 1 +| #define HAVE_MEMPCPY 1 +| #define HAVE_MUNMAP 1 +| #define HAVE_PUTENV 1 +| #define HAVE_SETENV 1 +| #define HAVE_SETLOCALE 1 +| #define HAVE_STPCPY 1 +| #define HAVE_STRCHR 1 +| #define HAVE_STRCASECMP 1 +| #define HAVE_STRDUP 1 +| #define HAVE_STRTOUL 1 +| #define HAVE_TSEARCH 1 +| #define HAVE___ARGZ_COUNT 1 +| #define HAVE___ARGZ_STRINGIFY 1 +| #define HAVE___ARGZ_NEXT 1 +| #define HAVE_ICONV 1 +| #define ICONV_CONST +| #define HAVE_LANGINFO_CODESET 1 +| #define HAVE_LC_MESSAGES 1 +| #define ENABLE_NLS 1 +| #define HAVE_GETTEXT 1 +| #define HAVE_DCGETTEXT 1 +| #define HAVE_ICONV_H 1 +| #define HAVE_ICONV_T_DEF 1 +| #define ICONV_NONTRANS 0 +| #define HAVE_BIND_TEXTDOMAIN_CODESET 1 +| #define HAVE_LIBIDN 1 +| #define HAVE_IDNA_TO_UNICODE_8Z8Z 1 +| #define HAVE_IDNA_TO_ASCII_8Z 1 +| #define HAVE_IDNA_TO_ASCII_LZ 1 +| /* end confdefs.h. */ +| /* Define idna_to_ascii_from_locale to an innocuous variant, in case declares idna_to_ascii_from_locale. +| For example, HP-UX 11i declares gettimeofday. */ +| #define idna_to_ascii_from_locale innocuous_idna_to_ascii_from_locale +| +| /* System header to define __stub macros and hopefully few prototypes, +| which can conflict with char idna_to_ascii_from_locale (); below. +| Prefer to if __STDC__ is defined, since +| exists even on freestanding compilers. */ +| +| #ifdef __STDC__ +| # include +| #else +| # include +| #endif +| +| #undef idna_to_ascii_from_locale +| +| /* Override any GCC internal prototype to avoid an error. +| Use char because int might match the return type of a GCC +| builtin and then its argument prototype would still apply. */ +| #ifdef __cplusplus +| extern "C" +| #endif +| char idna_to_ascii_from_locale (); +| /* The GNU C library defines this for functions which it implements +| to always fail with ENOSYS. Some functions are actually named +| something starting with __ and the normal name is an alias. */ +| #if defined __stub_idna_to_ascii_from_locale || defined __stub___idna_to_ascii_from_locale +| choke me +| #endif +| +| int +| main () +| { +| return idna_to_ascii_from_locale (); +| ; +| return 0; +| } +configure:21035: result: no +configure:21067: checking wchar.h usability +configure:21084: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5 +configure:21091: $? = 0 +configure:21105: result: yes +configure:21109: checking wchar.h presence +configure:21124: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c +configure:21131: $? = 0 +configure:21145: result: yes +configure:21173: checking for wchar.h +configure:21182: result: yes +configure:21198: checking for wchar_t +configure:21230: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5 +conftest.c: In function 'main': +conftest.c:166: warning: unused variable 'wc' +configure:21237: $? = 0 +configure:21252: result: yes +configure:21263: checking for wint_t +configure:21295: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5 +conftest.c: In function 'main': +conftest.c:166: warning: unused variable 'wc' +configure:21302: $? = 0 +configure:21317: result: yes +configure:21344: checking wctype.h usability +configure:21361: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5 +configure:21368: $? = 0 +configure:21382: result: yes +configure:21386: checking wctype.h presence +configure:21401: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c +configure:21408: $? = 0 +configure:21422: result: yes +configure:21450: checking for wctype.h +configure:21459: result: yes +configure:21481: checking for iswalnum +configure:21537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c:180: warning: conflicting types for built-in function 'iswalnum' +configure:21544: $? = 0 +configure:21566: result: yes +configure:21481: checking for iswalpha +configure:21537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c:181: warning: conflicting types for built-in function 'iswalpha' +configure:21544: $? = 0 +configure:21566: result: yes +configure:21481: checking for iswcntrl +configure:21537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c:182: warning: conflicting types for built-in function 'iswcntrl' +configure:21544: $? = 0 +configure:21566: result: yes +configure:21481: checking for iswdigit +configure:21537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c:183: warning: conflicting types for built-in function 'iswdigit' +configure:21544: $? = 0 +configure:21566: result: yes +configure:21587: checking for iswgraph +configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c:184: warning: conflicting types for built-in function 'iswgraph' +configure:21650: $? = 0 +configure:21672: result: yes +configure:21587: checking for iswlower +configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c:185: warning: conflicting types for built-in function 'iswlower' +configure:21650: $? = 0 +configure:21672: result: yes +configure:21587: checking for iswprint +configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c:186: warning: conflicting types for built-in function 'iswprint' +configure:21650: $? = 0 +configure:21672: result: yes +configure:21587: checking for iswpunct +configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c:187: warning: conflicting types for built-in function 'iswpunct' +configure:21650: $? = 0 +configure:21672: result: yes +configure:21587: checking for iswspace +configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c:188: warning: conflicting types for built-in function 'iswspace' +configure:21650: $? = 0 +configure:21672: result: yes +configure:21587: checking for iswupper +configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c:189: warning: conflicting types for built-in function 'iswupper' +configure:21650: $? = 0 +configure:21672: result: yes +configure:21690: checking for iswxdigit +configure:21746: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c:190: warning: conflicting types for built-in function 'iswxdigit' +configure:21753: $? = 0 +configure:21775: result: yes +configure:21690: checking for towupper +configure:21746: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c:191: warning: conflicting types for built-in function 'towupper' +configure:21753: $? = 0 +configure:21775: result: yes +configure:21690: checking for towlower +configure:21746: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c:192: warning: conflicting types for built-in function 'towlower' +configure:21753: $? = 0 +configure:21775: result: yes +configure:21788: checking for mbstate_t +configure:21820: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5 +conftest.c: In function 'main': +conftest.c:180: warning: unused variable 's' +configure:21827: $? = 0 +configure:21842: result: yes +configure:21862: checking for wchar_t functions +configure:21899: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c: In function 'main': +conftest.c:184: warning: statement with no effect +conftest.c:184: warning: statement with no effect +conftest.c:184: warning: statement with no effect +conftest.c:184: warning: statement with no effect +conftest.c:185: warning: statement with no effect +configure:21906: $? = 0 +configure:21926: result: yes +configure:21941: checking for nl_langinfo and CODESET +configure:21967: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c: In function 'main': +conftest.c:175: warning: unused variable 'cs' +configure:21974: $? = 0 +configure:21994: result: yes +configure:22004: checking for nl_langinfo and YESEXPR +configure:22030: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5 +conftest.c: In function 'main': +conftest.c:176: warning: unused variable 'cs' +configure:22037: $? = 0 +configure:22057: result: yes +configure:22070: checking for ospcat +configure:22088: found /usr/bin/ospcat +configure:22101: result: /usr/bin/ospcat +configure:22111: checking for openjade docbook stylesheets +configure:22126: result: not found: PDF documentation will not be built. +configure:22309: creating ./config.status + +## ---------------------- ## +## Running config.status. ## +## ---------------------- ## + +This file was extended by config.status, which was +generated by GNU Autoconf 2.63. Invocation command line was + + CONFIG_FILES = + CONFIG_HEADERS = + CONFIG_LINKS = + CONFIG_COMMANDS = + $ ./config.status + +on debian + +config.status:1011: creating Makefile +config.status:1011: creating contrib/Makefile +config.status:1011: creating doc/Makefile +config.status:1011: creating imap/Makefile +config.status:1011: creating intl/Makefile +config.status:1011: creating m4/Makefile +config.status:1011: creating po/Makefile.in +config.status:1011: creating hcachever.sh +config.status:1011: creating muttbug.sh +config.status:1011: creating doc/instdoc.sh +config.status:1011: creating config.h +config.status:1278: executing depfiles commands +config.status:1278: executing default-1 commands +configure:23670: WARNING: unrecognized options: --with-sharedir, --enable-inodesort + +## ---------------- ## +## Cache variables. ## +## ---------------- ## + +ac_cv_build=i486-pc-linux-gnu +ac_cv_c_bigendian=no +ac_cv_c_compiler_gnu=yes +ac_cv_c_const=yes +ac_cv_c_inline=inline +ac_cv_dirent_d_ino=yes +ac_cv_env_CC_set= +ac_cv_env_CC_value= +ac_cv_env_CFLAGS_set=set +ac_cv_env_CFLAGS_value='-Wall -g -O2' +ac_cv_env_CPPFLAGS_set=set +ac_cv_env_CPPFLAGS_value=-I/usr/include/qdbm +ac_cv_env_CPP_set= +ac_cv_env_CPP_value= +ac_cv_env_GNUTLS_CFLAGS_set= +ac_cv_env_GNUTLS_CFLAGS_value= +ac_cv_env_GNUTLS_LIBS_set= +ac_cv_env_GNUTLS_LIBS_value= +ac_cv_env_LDFLAGS_set=set +ac_cv_env_LDFLAGS_value= +ac_cv_env_LIBS_set= +ac_cv_env_LIBS_value= +ac_cv_env_PKG_CONFIG_set= +ac_cv_env_PKG_CONFIG_value= +ac_cv_env_build_alias_set=set +ac_cv_env_build_alias_value=i486-linux-gnu +ac_cv_env_host_alias_set= +ac_cv_env_host_alias_value= +ac_cv_env_target_alias_set= +ac_cv_env_target_alias_value= +ac_cv_func___argz_count=yes +ac_cv_func___argz_next=yes +ac_cv_func___argz_stringify=yes +ac_cv_func_alloca_works=yes +ac_cv_func_bind_textdomain_codeset=yes +ac_cv_func_dcgettext=yes +ac_cv_func_decl_bkgdset=yes +ac_cv_func_decl_curs_set=yes +ac_cv_func_decl_meta=yes +ac_cv_func_decl_resizeterm=yes +ac_cv_func_decl_start_color=yes +ac_cv_func_decl_typeahead=yes +ac_cv_func_decl_use_default_colors=yes +ac_cv_func_fchdir=yes +ac_cv_func_feof_unlocked=yes +ac_cv_func_fgetpos=yes +ac_cv_func_fgets_unlocked=yes +ac_cv_func_ftruncate=yes +ac_cv_func_getaddrinfo=yes +ac_cv_func_getcwd=yes +ac_cv_func_getegid=yes +ac_cv_func_geteuid=yes +ac_cv_func_getgid=yes +ac_cv_func_gethostent=yes +ac_cv_func_getopt=yes +ac_cv_func_getpagesize=yes +ac_cv_func_getsid=yes +ac_cv_func_getuid=yes +ac_cv_func_idna_to_ascii_8z=yes +ac_cv_func_idna_to_ascii_from_locale=no +ac_cv_func_idna_to_ascii_from_utf8=no +ac_cv_func_idna_to_ascii_lz=yes +ac_cv_func_idna_to_unicode_8z8z=yes +ac_cv_func_idna_to_unicode_utf8_from_utf8=no +ac_cv_func_initscr=no +ac_cv_func_iswalnum=yes +ac_cv_func_iswalpha=yes +ac_cv_func_iswcntrl=yes +ac_cv_func_iswdigit=yes +ac_cv_func_iswgraph=yes +ac_cv_func_iswlower=yes +ac_cv_func_iswprint=yes +ac_cv_func_iswpunct=yes +ac_cv_func_iswspace=yes +ac_cv_func_iswupper=yes +ac_cv_func_iswxdigit=yes +ac_cv_func_memmove=yes +ac_cv_func_mempcpy=yes +ac_cv_func_mmap_fixed_mapped=yes +ac_cv_func_munmap=yes +ac_cv_func_putenv=yes +ac_cv_func_regcomp=yes +ac_cv_func_setegid=yes +ac_cv_func_setenv=yes +ac_cv_func_setlocale=yes +ac_cv_func_setrlimit=yes +ac_cv_func_setsockopt=yes +ac_cv_func_snprintf=yes +ac_cv_func_srand48=yes +ac_cv_func_stpcpy=yes +ac_cv_func_strcasecmp=yes +ac_cv_func_strchr=yes +ac_cv_func_strdup=yes +ac_cv_func_strerror=yes +ac_cv_func_strftime=yes +ac_cv_func_strsep=yes +ac_cv_func_strtok_r=yes +ac_cv_func_strtoul=yes +ac_cv_func_towlower=yes +ac_cv_func_towupper=yes +ac_cv_func_tsearch=yes +ac_cv_func_vsnprintf=yes +ac_cv_gdbmopen=yes +ac_cv_gnu_library_2_1=yes +ac_cv_have_decl_sys_siglist=yes +ac_cv_header_argz_h=yes +ac_cv_header_getopt_h=yes +ac_cv_header_iconv_h=yes +ac_cv_header_inttypes_h=yes +ac_cv_header_ioctl_h=no +ac_cv_header_libintl_h=yes +ac_cv_header_limits_h=yes +ac_cv_header_locale_h=yes +ac_cv_header_malloc_h=yes +ac_cv_header_memory_h=yes +ac_cv_header_minix_config_h=no +ac_cv_header_ncursesw_ncurses_h=yes +ac_cv_header_nl_types_h=yes +ac_cv_header_stdarg_h=yes +ac_cv_header_stdc=yes +ac_cv_header_stddef_h=yes +ac_cv_header_stdint_h=yes +ac_cv_header_stdlib_h=yes +ac_cv_header_string_h=yes +ac_cv_header_strings_h=yes +ac_cv_header_sys_ioctl_h=yes +ac_cv_header_sys_param_h=yes +ac_cv_header_sys_resource_h=yes +ac_cv_header_sys_select_h=yes +ac_cv_header_sys_stat_h=yes +ac_cv_header_sys_time_h=yes +ac_cv_header_sys_types_h=yes +ac_cv_header_sysexits_h=yes +ac_cv_header_unistd_h=yes +ac_cv_header_unix_h=no +ac_cv_header_wchar_h=yes +ac_cv_header_wctype_h=yes +ac_cv_host=i486-pc-linux-gnu +ac_cv_lib_ncurses___waddnwstr=no +ac_cv_lib_ncursesw___initscr=yes +ac_cv_lib_ncursesw___waddnwstr=yes +ac_cv_lib_sasl2_sasl_client_init=yes +ac_cv_objext=o +ac_cv_path_DBX=no +ac_cv_path_EGREP='/bin/grep -E' +ac_cv_path_GDB=/usr/bin/gdb +ac_cv_path_GMSGFMT=/usr/bin/msgfmt +ac_cv_path_GPGME_CONFIG=/usr/bin/gpgme-config +ac_cv_path_GREP=/bin/grep +ac_cv_path_ISPELL=no +ac_cv_path_KRB5CFGPATH=/usr/bin/krb5-config +ac_cv_path_MSGFMT=/usr/bin/msgfmt +ac_cv_path_OSPCAT=/usr/bin/ospcat +ac_cv_path_SDB=no +ac_cv_path_SENDMAIL=/usr/sbin/sendmail +ac_cv_path_XGETTEXT=/usr/bin/xgettext +ac_cv_path_ac_pt_PKG_CONFIG=/usr/bin/pkg-config +ac_cv_path_install='/usr/bin/install -c' +ac_cv_path_mkdir=/bin/mkdir +ac_cv_prog_AWK=gawk +ac_cv_prog_CPP='gcc -E' +ac_cv_prog_INTLBISON=bison +ac_cv_prog_ac_ct_AR=ar +ac_cv_prog_ac_ct_CC=gcc +ac_cv_prog_ac_ct_RANLIB=ranlib +ac_cv_prog_cc_c89= +ac_cv_prog_cc_g=yes +ac_cv_prog_make_make_set=yes +ac_cv_safe_to_define___extensions__=yes +ac_cv_search_strerror='none required' +ac_cv_search_stringprep_check_version=-lidn +ac_cv_sizeof_int=4 +ac_cv_sizeof_long=4 +ac_cv_sizeof_long_long=8 +ac_cv_sizeof_off_t=8 +ac_cv_sizeof_short=2 +ac_cv_sys_file_offset_bits=64 +ac_cv_sys_largefile_CC=no +ac_cv_sys_largefile_source=no +ac_cv_type_off_t=yes +ac_cv_type_pid_t=yes +ac_cv_type_sig_atomic_t=yes +ac_cv_type_signal=void +ac_cv_type_size_t=yes +ac_cv_type_ssize_t=yes +ac_cv_type_uint32_t=yes +ac_cv_working_alloca_h=yes +am_cv_CC_dependencies_compiler_type=none +am_cv_func_iconv=yes +am_cv_langinfo_codeset=yes +am_cv_lib_iconv=no +am_cv_proto_iconv='extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);' +am_cv_proto_iconv_arg1= +am_cv_val_LC_MESSAGES=yes +cf_cv_ncurses_header=ncursesw/ncurses.h +gt_cv_func_gnugettext1_libc=yes +mutt_cv_c99_snprintf=yes +mutt_cv_c99_vsnprintf=yes +mutt_cv_curses=/usr +mutt_cv_docdir=/usr/share/doc +mutt_cv_fcntl=yes +mutt_cv_func_snprintf=yes +mutt_cv_func_vsnprintf=yes +mutt_cv_groupwrite=yes +mutt_cv_iconv_good=yes +mutt_cv_iconv_nontrans=no +mutt_cv_langinfo_codeset=yes +mutt_cv_langinfo_yesexpr=yes +mutt_cv_mailpath=/var/mail +mutt_cv_mbstate_t=yes +mutt_cv_prefix=/usr +mutt_cv_regex=no +mutt_cv_regex_broken=no +mutt_cv_setgid=yes +mutt_cv_version=1.5.19 +mutt_cv_warnings=yes +mutt_cv_wc_funcs=yes +mutt_cv_wchar_t=yes +mutt_cv_wint_t=yes +mutt_cv_worldwrite=no +nls_cv_force_use_gnu_gettext=no +nls_cv_header_intl= +nls_cv_header_libgt= +nls_cv_use_gnu_gettext=no +pkg_cv_GNUTLS_CFLAGS=' ' +pkg_cv_GNUTLS_LIBS='-lgnutls ' + +## ----------------- ## +## Output variables. ## +## ----------------- ## + +ACLOCAL='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10' +ALLOCA='' +AMDEPBACKSLASH='' +AMDEP_FALSE='' +AMDEP_TRUE='#' +AMTAR='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar' +ANSI2KNR='' +AR='ar' +AUTOCONF='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf' +AUTOHEADER='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader' +AUTOMAKE='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10' +AWK='gawk' +BUILD_IMAP_FALSE='#' +BUILD_IMAP_TRUE='' +BUILD_INCLUDED_LIBINTL='no' +CATALOGS=' de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo' +CATOBJEXT='.gmo' +CC='gcc' +CCDEPMODE='depmode=none' +CFLAGS='-Wall -pedantic -Wno-long-long -Wall -g -O2' +CONFIG_STATUS_DEPENDENCIES='$(top_srcdir)/VERSION' +CPP='gcc -E' +CPPFLAGS='-I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl' +CYGPATH_W='echo' +DATADIRNAME='share' +DBX='no' +DEBUGGER='/usr/bin/gdb' +DEFS='-DHAVE_CONFIG_H' +DEPDIR='.deps' +DOTLOCK_GROUP='mail' +DOTLOCK_PERMISSION='2755' +DOTLOCK_TARGET='mutt_dotlock$(EXEEXT)' +DSLROOT='' +ECHO_C='' +ECHO_N='-n' +ECHO_T='' +EGREP='/bin/grep -E' +EXEEXT='' +GDB='/usr/bin/gdb' +GENCAT='gencat' +GLIBC21='yes' +GMOFILES=' de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo' +GMSGFMT='/usr/bin/msgfmt' +GNUTLS_CFLAGS=' ' +GNUTLS_LIBS='-lgnutls ' +GPGME_CFLAGS='' +GPGME_CONFIG='/usr/bin/gpgme-config' +GPGME_LIBS='-lgpgme -lgpg-error' +GREP='/bin/grep' +INSTALL_DATA='${INSTALL} -m 644' +INSTALL_PROGRAM='${INSTALL}' +INSTALL_SCRIPT='${INSTALL}' +INSTALL_STRIP_PROGRAM='$(install_sh) -c -s' +INSTOBJEXT='.mo' +INTLBISON='bison' +INTLLIBS='' +INTLOBJS='' +INTL_LIBTOOL_SUFFIX_PREFIX='' +ISPELL='no' +KRB5CFGPATH='/usr/bin/krb5-config' +LDFLAGS=' -L/lib' +LIBICONV='' +LIBIMAP='-Limap -limap' +LIBIMAPDEPS='$(top_srcdir)/imap/imap.h imap/libimap.a' +LIBOBJS='' +LIBS='-lidn ' +LTLIBOBJS='' +MAINT='#' +MAINTAINER_MODE_FALSE='' +MAINTAINER_MODE_TRUE='#' +MAKEINFO='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo' +MKDIR_P='/bin/mkdir -p' +MKINSTALLDIRS='../mkinstalldirs' +MSGFMT='/usr/bin/msgfmt' +MUTTLIBS=' -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm' +MUTT_LIB_OBJECTS=' crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o' +MUTT_MD5='mutt_md5' +OBJEXT='o' +OPS='$(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT ' +OSPCAT='/usr/bin/ospcat' +PACKAGE='mutt' +PACKAGE_BUGREPORT='' +PACKAGE_NAME='' +PACKAGE_STRING='' +PACKAGE_TARNAME='' +PACKAGE_VERSION='' +PATH_SEPARATOR=':' +PGPAUX_TARGET='pgpring$(EXEEXT) pgpewrap$(EXEEXT)' +PKG_CONFIG='/usr/bin/pkg-config' +POFILES=' de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po' +POSUB='po' +RANLIB='ranlib' +SDB='no' +SENDMAIL='/usr/sbin/sendmail' +SET_MAKE='' +SHELL='/bin/sh' +SMIMEAUX_TARGET='smime_keys' +STRIP='' +U='' +USE_GSS_FALSE='#' +USE_GSS_TRUE='' +USE_INCLUDED_LIBINTL='no' +USE_NLS='yes' +USE_SASL_FALSE='#' +USE_SASL_TRUE='' +USE_SSL_FALSE='#' +USE_SSL_TRUE='' +VERSION='1.5.19' +XGETTEXT='/usr/bin/xgettext' +ac_ct_CC='gcc' +am__fastdepCC_FALSE='' +am__fastdepCC_TRUE='#' +am__include='include' +am__isrc=' -I$(srcdir)' +am__leading_dot='.' +am__quote='' +am__tar='${AMTAR} chof - "$$tardir"' +am__untar='${AMTAR} xf -' +bindir='${exec_prefix}/bin' +build='i486-pc-linux-gnu' +build_alias='i486-linux-gnu' +build_cpu='i486' +build_os='linux-gnu' +build_vendor='pc' +datadir='${datarootdir}' +datarootdir='${prefix}/share' +docdir='/usr/share/doc' +dvidir='${docdir}' +exec_prefix='${prefix}' +host='i486-pc-linux-gnu' +host_alias='' +host_cpu='i486' +host_os='linux-gnu' +host_vendor='pc' +htmldir='${docdir}' +includedir='${prefix}/include' +infodir='${datarootdir}/info' +install_sh='$(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh' +libdir='${exec_prefix}/lib' +libexecdir='${exec_prefix}/libexec' +localedir='${datarootdir}/locale' +localstatedir='${prefix}/var' +mandir='/usr/share/man' +mkdir_p='/bin/mkdir -p' +oldincludedir='/usr/include' +pdfdir='${docdir}' +prefix='/usr' +program_transform_name='s,x,x,' +psdir='${docdir}' +sbindir='${exec_prefix}/sbin' +sharedstatedir='${prefix}/com' +sysconfdir='/etc' +target_alias='' + +## ----------- ## +## confdefs.h. ## +## ----------- ## + +#define PACKAGE_NAME "" +#define PACKAGE_TARNAME "" +#define PACKAGE_VERSION "" +#define PACKAGE_STRING "" +#define PACKAGE_BUGREPORT "" +#define PACKAGE "mutt" +#define VERSION "1.5.19" +#define STDC_HEADERS 1 +#define HAVE_SYS_TYPES_H 1 +#define HAVE_SYS_STAT_H 1 +#define HAVE_STDLIB_H 1 +#define HAVE_STRING_H 1 +#define HAVE_MEMORY_H 1 +#define HAVE_STRINGS_H 1 +#define HAVE_INTTYPES_H 1 +#define HAVE_STDINT_H 1 +#define HAVE_UNISTD_H 1 +#define __EXTENSIONS__ 1 +#define _ALL_SOURCE 1 +#define _GNU_SOURCE 1 +#define _POSIX_PTHREAD_SEMANTICS 1 +#define _TANDEM_SOURCE 1 +#define PROTOTYPES 1 +#define __PROTOTYPES 1 +#define HAVE_STRING_H 1 +#define _FILE_OFFSET_BITS 64 +#define HAVE_FSEEKO 1 +#define SIZEOF_OFF_T 8 +#define HAVE_INTTYPES_H 1 +#define HAVE_C99_INTTYPES 1 +#define SIZEOF_SHORT 2 +#define SIZEOF_INT 4 +#define SIZEOF_LONG 4 +#define SIZEOF_LONG_LONG 8 +#define SENDMAIL "/usr/sbin/sendmail" +#define CRYPT_BACKEND_GPGME 1 +#define HAVE_GPGME_PKA_TRUST 1 +#define CRYPT_BACKEND_GPGME 1 +#define CRYPT_BACKEND_CLASSIC_PGP 1 +#define CRYPT_BACKEND_CLASSIC_SMIME 1 +#define MIXMASTER "mixmaster" +#define HAVE_NCURSESW_NCURSES_H 1 +#define HAVE_START_COLOR 1 +#define HAVE_TYPEAHEAD 1 +#define HAVE_BKGDSET 1 +#define HAVE_CURS_SET 1 +#define HAVE_META 1 +#define HAVE_USE_DEFAULT_COLORS 1 +#define HAVE_RESIZETERM 1 +#define HAVE_COLOR 1 +#define STDC_HEADERS 1 +#define HAVE_STDARG_H 1 +#define HAVE_SYS_IOCTL_H 1 +#define HAVE_SYSEXITS_H 1 +#define HAVE_SYS_TIME_H 1 +#define HAVE_SYS_RESOURCE_H 1 +#define HAVE_SETRLIMIT 1 +#define HAVE_GETSID 1 +#define RETSIGTYPE void +#define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t +#define HAVE_DECL_SYS_SIGLIST 1 +#define HAVE_FGETPOS 1 +#define HAVE_MEMMOVE 1 +#define HAVE_SETEGID 1 +#define HAVE_SRAND48 1 +#define HAVE_STRERROR 1 +#define HAVE_SETENV 1 +#define HAVE_STRCASECMP 1 +#define HAVE_STRDUP 1 +#define HAVE_STRSEP 1 +#define HAVE_STRTOK_R 1 +#define HAVE_GETOPT_H 1 +#define HAVE_SNPRINTF 1 +#define HAVE_VSNPRINTF 1 +#define HAVE_FTRUNCATE 1 +#define HAVE_STRFTIME 1 +#define HAVE_FCHDIR 1 +#define HAVE_REGCOMP 1 +#define MAILPATH "/var/mail" +#define USE_DOTLOCK 1 +#define USE_SETGID 1 +#define DL_STANDALONE 1 +#define USE_POP 1 +#define USE_IMAP 1 +#define USE_SMTP 1 +#define HAVE_SYS_SELECT_H 1 +#define HAVE_GETADDRINFO 1 +#define USE_SOCKET 1 +#define USE_GSS 1 +#define USE_SSL 1 +#define USE_SSL_GNUTLS 1 +#define HAVE_LIBSASL2 1 +#define USE_SASL 1 +#define DEBUG 1 +#define USE_FCNTL 1 +#define HAVE_DIRENT_D_INO 1 +#define USE_COMPRESSED 1 +#define EXECSHELL "/bin/sh" +#define USE_HCACHE 1 +#define HAVE_GDBM 1 +#define HAVE_ALLOCA_H 1 +#define HAVE_ALLOCA 1 +#define HAVE_STDLIB_H 1 +#define HAVE_UNISTD_H 1 +#define HAVE_GETPAGESIZE 1 +#define HAVE_MMAP 1 +#define HAVE_ARGZ_H 1 +#define HAVE_LIMITS_H 1 +#define HAVE_LOCALE_H 1 +#define HAVE_NL_TYPES_H 1 +#define HAVE_MALLOC_H 1 +#define HAVE_STDDEF_H 1 +#define HAVE_STDLIB_H 1 +#define HAVE_STRING_H 1 +#define HAVE_UNISTD_H 1 +#define HAVE_SYS_PARAM_H 1 +#define HAVE_FEOF_UNLOCKED 1 +#define HAVE_FGETS_UNLOCKED 1 +#define HAVE_GETCWD 1 +#define HAVE_GETEGID 1 +#define HAVE_GETEUID 1 +#define HAVE_GETGID 1 +#define HAVE_GETUID 1 +#define HAVE_MEMPCPY 1 +#define HAVE_MUNMAP 1 +#define HAVE_PUTENV 1 +#define HAVE_SETENV 1 +#define HAVE_SETLOCALE 1 +#define HAVE_STPCPY 1 +#define HAVE_STRCHR 1 +#define HAVE_STRCASECMP 1 +#define HAVE_STRDUP 1 +#define HAVE_STRTOUL 1 +#define HAVE_TSEARCH 1 +#define HAVE___ARGZ_COUNT 1 +#define HAVE___ARGZ_STRINGIFY 1 +#define HAVE___ARGZ_NEXT 1 +#define HAVE_ICONV 1 +#define ICONV_CONST +#define HAVE_LANGINFO_CODESET 1 +#define HAVE_LC_MESSAGES 1 +#define ENABLE_NLS 1 +#define HAVE_GETTEXT 1 +#define HAVE_DCGETTEXT 1 +#define HAVE_ICONV_H 1 +#define HAVE_ICONV_T_DEF 1 +#define ICONV_NONTRANS 0 +#define HAVE_BIND_TEXTDOMAIN_CODESET 1 +#define HAVE_LIBIDN 1 +#define HAVE_IDNA_TO_UNICODE_8Z8Z 1 +#define HAVE_IDNA_TO_ASCII_8Z 1 +#define HAVE_IDNA_TO_ASCII_LZ 1 +#define HAVE_WCHAR_H 1 +#define HAVE_WCTYPE_H 1 +#define HAVE_ISWALNUM 1 +#define HAVE_ISWALPHA 1 +#define HAVE_ISWCNTRL 1 +#define HAVE_ISWDIGIT 1 +#define HAVE_ISWGRAPH 1 +#define HAVE_ISWLOWER 1 +#define HAVE_ISWPRINT 1 +#define HAVE_ISWPUNCT 1 +#define HAVE_ISWSPACE 1 +#define HAVE_ISWUPPER 1 +#define HAVE_ISWXDIGIT 1 +#define HAVE_TOWUPPER 1 +#define HAVE_TOWLOWER 1 +#define HAVE_WC_FUNCS 1 +#define HAVE_LANGINFO_CODESET 1 +#define HAVE_LANGINFO_YESEXPR 1 +#define MAKEDOC_FULL 1 + +configure: exit 0 diff --git a/obj-i486-linux-gnu-patched/config.status b/obj-i486-linux-gnu-patched/config.status new file mode 100755 index 0000000..31e511f --- /dev/null +++ b/obj-i486-linux-gnu-patched/config.status @@ -0,0 +1,1443 @@ +#! /bin/sh +# Generated by configure. +# Run this file to recreate the current configuration. +# Compiler output produced by configure, useful for debugging +# configure, is in config.log if it exists. + +debug=false +ac_cs_recheck=false +ac_cs_silent=false +SHELL=${CONFIG_SHELL-/bin/sh} +## --------------------- ## +## M4sh Initialization. ## +## --------------------- ## + +# Be more Bourne compatible +DUALCASE=1; export DUALCASE # for MKS sh +if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then + emulate sh + NULLCMD=: + # Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which + # is contrary to our usage. Disable this feature. + alias -g '${1+"$@"}'='"$@"' + setopt NO_GLOB_SUBST +else + case `(set -o) 2>/dev/null` in + *posix*) set -o posix ;; +esac + +fi + + + + +# PATH needs CR +# Avoid depending upon Character Ranges. +as_cr_letters='abcdefghijklmnopqrstuvwxyz' +as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ' +as_cr_Letters=$as_cr_letters$as_cr_LETTERS +as_cr_digits='0123456789' +as_cr_alnum=$as_cr_Letters$as_cr_digits + +as_nl=' +' +export as_nl +# Printing a long string crashes Solaris 7 /usr/bin/printf. +as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\' +as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo +as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo +if (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then + as_echo='printf %s\n' + as_echo_n='printf %s' +else + if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then + as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"' + as_echo_n='/usr/ucb/echo -n' + else + as_echo_body='eval expr "X$1" : "X\\(.*\\)"' + as_echo_n_body='eval + arg=$1; + case $arg in + *"$as_nl"*) + expr "X$arg" : "X\\(.*\\)$as_nl"; + arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;; + esac; + expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl" + ' + export as_echo_n_body + as_echo_n='sh -c $as_echo_n_body as_echo' + fi + export as_echo_body + as_echo='sh -c $as_echo_body as_echo' +fi + +# The user is always right. +if test "${PATH_SEPARATOR+set}" != set; then + PATH_SEPARATOR=: + (PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && { + (PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 || + PATH_SEPARATOR=';' + } +fi + +# Support unset when possible. +if ( (MAIL=60; unset MAIL) || exit) >/dev/null 2>&1; then + as_unset=unset +else + as_unset=false +fi + + +# IFS +# We need space, tab and new line, in precisely that order. Quoting is +# there to prevent editors from complaining about space-tab. +# (If _AS_PATH_WALK were called with IFS unset, it would disable word +# splitting by setting IFS to empty value.) +IFS=" "" $as_nl" + +# Find who we are. Look in the path if we contain no directory separator. +case $0 in + *[\\/]* ) as_myself=$0 ;; + *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break +done +IFS=$as_save_IFS + + ;; +esac +# We did not find ourselves, most probably we were run as `sh COMMAND' +# in which case we are not to be found in the path. +if test "x$as_myself" = x; then + as_myself=$0 +fi +if test ! -f "$as_myself"; then + $as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2 + { (exit 1); exit 1; } +fi + +# Work around bugs in pre-3.0 UWIN ksh. +for as_var in ENV MAIL MAILPATH +do ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var +done +PS1='$ ' +PS2='> ' +PS4='+ ' + +# NLS nuisances. +LC_ALL=C +export LC_ALL +LANGUAGE=C +export LANGUAGE + +# Required to use basename. +if expr a : '\(a\)' >/dev/null 2>&1 && + test "X`expr 00001 : '.*\(...\)'`" = X001; then + as_expr=expr +else + as_expr=false +fi + +if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then + as_basename=basename +else + as_basename=false +fi + + +# Name of the executable. +as_me=`$as_basename -- "$0" || +$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \ + X"$0" : 'X\(//\)$' \| \ + X"$0" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X/"$0" | + sed '/^.*\/\([^/][^/]*\)\/*$/{ + s//\1/ + q + } + /^X\/\(\/\/\)$/{ + s//\1/ + q + } + /^X\/\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + +# CDPATH. +$as_unset CDPATH + + + + as_lineno_1=$LINENO + as_lineno_2=$LINENO + test "x$as_lineno_1" != "x$as_lineno_2" && + test "x`expr $as_lineno_1 + 1`" = "x$as_lineno_2" || { + + # Create $as_me.lineno as a copy of $as_myself, but with $LINENO + # uniformly replaced by the line number. The first 'sed' inserts a + # line-number line after each line using $LINENO; the second 'sed' + # does the real work. The second script uses 'N' to pair each + # line-number line with the line containing $LINENO, and appends + # trailing '-' during substitution so that $LINENO is not a special + # case at line end. + # (Raja R Harinath suggested sed '=', and Paul Eggert wrote the + # scripts with optimization help from Paolo Bonzini. Blame Lee + # E. McMahon (1931-1989) for sed's syntax. :-) + sed -n ' + p + /[$]LINENO/= + ' <$as_myself | + sed ' + s/[$]LINENO.*/&-/ + t lineno + b + :lineno + N + :loop + s/[$]LINENO\([^'$as_cr_alnum'_].*\n\)\(.*\)/\2\1\2/ + t loop + s/-\n.*// + ' >$as_me.lineno && + chmod +x "$as_me.lineno" || + { $as_echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2 + { (exit 1); exit 1; }; } + + # Don't try to exec as it changes $[0], causing all sort of problems + # (the dirname of $[0] is not the place where we might find the + # original and so on. Autoconf is especially sensitive to this). + . "./$as_me.lineno" + # Exit status is that of the last command. + exit +} + + +if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then + as_dirname=dirname +else + as_dirname=false +fi + +ECHO_C= ECHO_N= ECHO_T= +case `echo -n x` in +-n*) + case `echo 'x\c'` in + *c*) ECHO_T=' ';; # ECHO_T is single tab character. + *) ECHO_C='\c';; + esac;; +*) + ECHO_N='-n';; +esac +if expr a : '\(a\)' >/dev/null 2>&1 && + test "X`expr 00001 : '.*\(...\)'`" = X001; then + as_expr=expr +else + as_expr=false +fi + +rm -f conf$$ conf$$.exe conf$$.file +if test -d conf$$.dir; then + rm -f conf$$.dir/conf$$.file +else + rm -f conf$$.dir + mkdir conf$$.dir 2>/dev/null +fi +if (echo >conf$$.file) 2>/dev/null; then + if ln -s conf$$.file conf$$ 2>/dev/null; then + as_ln_s='ln -s' + # ... but there are two gotchas: + # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail. + # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable. + # In both cases, we have to default to `cp -p'. + ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe || + as_ln_s='cp -p' + elif ln conf$$.file conf$$ 2>/dev/null; then + as_ln_s=ln + else + as_ln_s='cp -p' + fi +else + as_ln_s='cp -p' +fi +rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file +rmdir conf$$.dir 2>/dev/null + +if mkdir -p . 2>/dev/null; then + as_mkdir_p=: +else + test -d ./-p && rmdir ./-p + as_mkdir_p=false +fi + +if test -x / >/dev/null 2>&1; then + as_test_x='test -x' +else + if ls -dL / >/dev/null 2>&1; then + as_ls_L_option=L + else + as_ls_L_option= + fi + as_test_x=' + eval sh -c '\'' + if test -d "$1"; then + test -d "$1/."; + else + case $1 in + -*)set "./$1";; + esac; + case `ls -ld'$as_ls_L_option' "$1" 2>/dev/null` in + ???[sx]*):;;*)false;;esac;fi + '\'' sh + ' +fi +as_executable_p=$as_test_x + +# Sed expression to map a string onto a valid CPP name. +as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'" + +# Sed expression to map a string onto a valid variable name. +as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'" + + +exec 6>&1 + +# Save the log message, to keep $[0] and so on meaningful, and to +# report actual input values of CONFIG_FILES etc. instead of their +# values after options handling. +ac_log=" +This file was extended by $as_me, which was +generated by GNU Autoconf 2.63. Invocation command line was + + CONFIG_FILES = $CONFIG_FILES + CONFIG_HEADERS = $CONFIG_HEADERS + CONFIG_LINKS = $CONFIG_LINKS + CONFIG_COMMANDS = $CONFIG_COMMANDS + $ $0 $@ + +on `(hostname || uname -n) 2>/dev/null | sed 1q` +" + +# Files that config.status was made for. +config_files=" Makefile contrib/Makefile doc/Makefile imap/Makefile intl/Makefile m4/Makefile po/Makefile.in hcachever.sh muttbug.sh doc/instdoc.sh" +config_headers=" config.h" +config_commands=" depfiles default-1" + +ac_cs_usage="\ +\`$as_me' instantiates files from templates according to the +current configuration. + +Usage: $0 [OPTION]... [FILE]... + + -h, --help print this help, then exit + -V, --version print version number and configuration settings, then exit + -q, --quiet, --silent + do not print progress messages + -d, --debug don't remove temporary files + --recheck update $as_me by reconfiguring in the same conditions + --file=FILE[:TEMPLATE] + instantiate the configuration file FILE + --header=FILE[:TEMPLATE] + instantiate the configuration header FILE + +Configuration files: +$config_files + +Configuration headers: +$config_headers + +Configuration commands: +$config_commands + +Report bugs to ." + +ac_cs_version="\ +config.status +configured by ../configure, generated by GNU Autoconf 2.63, + with options \"'--prefix=/usr' '--sysconfdir=/etc' '--mandir=/usr/share/man' '--with-sharedir=/usr/share/mutt' '--with-docdir=/usr/share/doc' '--with-mailpath=/var/mail' '--disable-dependency-tracking' '--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' '--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-inodesort' '--enable-pop' '--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' '--with-sasl' '--without-qdbm' '--without-bdb' '--without-tokyocabinet' '--build' 'i486-linux-gnu' 'build_alias=i486-linux-gnu' 'CFLAGS=-Wall -g -O2' 'LDFLAGS=' 'CPPFLAGS=-I/usr/include/qdbm'\" + +Copyright (C) 2008 Free Software Foundation, Inc. +This config.status script is free software; the Free Software Foundation +gives unlimited permission to copy, distribute and modify it." + +ac_pwd='/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched' +srcdir='..' +INSTALL='/usr/bin/install -c' +MKDIR_P='/bin/mkdir -p' +AWK='gawk' +test -n "$AWK" || AWK=awk +# The default lists apply if the user does not specify any file. +ac_need_defaults=: +while test $# != 0 +do + case $1 in + --*=*) + ac_option=`expr "X$1" : 'X\([^=]*\)='` + ac_optarg=`expr "X$1" : 'X[^=]*=\(.*\)'` + ac_shift=: + ;; + *) + ac_option=$1 + ac_optarg=$2 + ac_shift=shift + ;; + esac + + case $ac_option in + # Handling of the options. + -recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r) + ac_cs_recheck=: ;; + --version | --versio | --versi | --vers | --ver | --ve | --v | -V ) + $as_echo "$ac_cs_version"; exit ;; + --debug | --debu | --deb | --de | --d | -d ) + debug=: ;; + --file | --fil | --fi | --f ) + $ac_shift + case $ac_optarg in + *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;; + esac + CONFIG_FILES="$CONFIG_FILES '$ac_optarg'" + ac_need_defaults=false;; + --header | --heade | --head | --hea ) + $ac_shift + case $ac_optarg in + *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;; + esac + CONFIG_HEADERS="$CONFIG_HEADERS '$ac_optarg'" + ac_need_defaults=false;; + --he | --h) + # Conflict between --help and --header + { $as_echo "$as_me: error: ambiguous option: $1 +Try \`$0 --help' for more information." >&2 + { (exit 1); exit 1; }; };; + --help | --hel | -h ) + $as_echo "$ac_cs_usage"; exit ;; + -q | -quiet | --quiet | --quie | --qui | --qu | --q \ + | -silent | --silent | --silen | --sile | --sil | --si | --s) + ac_cs_silent=: ;; + + # This is an error. + -*) { $as_echo "$as_me: error: unrecognized option: $1 +Try \`$0 --help' for more information." >&2 + { (exit 1); exit 1; }; } ;; + + *) ac_config_targets="$ac_config_targets $1" + ac_need_defaults=false ;; + + esac + shift +done + +ac_configure_extra_args= + +if $ac_cs_silent; then + exec 6>/dev/null + ac_configure_extra_args="$ac_configure_extra_args --silent" +fi + +if $ac_cs_recheck; then + set X '/bin/sh' '../configure' '--prefix=/usr' '--sysconfdir=/etc' '--mandir=/usr/share/man' '--with-sharedir=/usr/share/mutt' '--with-docdir=/usr/share/doc' '--with-mailpath=/var/mail' '--disable-dependency-tracking' '--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' '--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-inodesort' '--enable-pop' '--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' '--with-sasl' '--without-qdbm' '--without-bdb' '--without-tokyocabinet' '--build' 'i486-linux-gnu' 'build_alias=i486-linux-gnu' 'CFLAGS=-Wall -g -O2' 'LDFLAGS=' 'CPPFLAGS=-I/usr/include/qdbm' $ac_configure_extra_args --no-create --no-recursion + shift + $as_echo "running CONFIG_SHELL=/bin/sh $*" >&6 + CONFIG_SHELL='/bin/sh' + export CONFIG_SHELL + exec "$@" +fi + +exec 5>>config.log +{ + echo + sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX +## Running $as_me. ## +_ASBOX + $as_echo "$ac_log" +} >&5 + +# +# INIT-COMMANDS +# +AMDEP_TRUE="#" ac_aux_dir=".." + + + +# Handling of arguments. +for ac_config_target in $ac_config_targets +do + case $ac_config_target in + "config.h") CONFIG_HEADERS="$CONFIG_HEADERS config.h" ;; + "depfiles") CONFIG_COMMANDS="$CONFIG_COMMANDS depfiles" ;; + "default-1") CONFIG_COMMANDS="$CONFIG_COMMANDS default-1" ;; + "Makefile") CONFIG_FILES="$CONFIG_FILES Makefile" ;; + "contrib/Makefile") CONFIG_FILES="$CONFIG_FILES contrib/Makefile" ;; + "doc/Makefile") CONFIG_FILES="$CONFIG_FILES doc/Makefile" ;; + "imap/Makefile") CONFIG_FILES="$CONFIG_FILES imap/Makefile" ;; + "intl/Makefile") CONFIG_FILES="$CONFIG_FILES intl/Makefile" ;; + "m4/Makefile") CONFIG_FILES="$CONFIG_FILES m4/Makefile" ;; + "po/Makefile.in") CONFIG_FILES="$CONFIG_FILES po/Makefile.in" ;; + "hcachever.sh") CONFIG_FILES="$CONFIG_FILES hcachever.sh" ;; + "muttbug.sh") CONFIG_FILES="$CONFIG_FILES muttbug.sh" ;; + "doc/instdoc.sh") CONFIG_FILES="$CONFIG_FILES doc/instdoc.sh" ;; + + *) { { $as_echo "$as_me:$LINENO: error: invalid argument: $ac_config_target" >&5 +$as_echo "$as_me: error: invalid argument: $ac_config_target" >&2;} + { (exit 1); exit 1; }; };; + esac +done + + +# If the user did not use the arguments to specify the items to instantiate, +# then the envvar interface is used. Set only those that are not. +# We use the long form for the default assignment because of an extremely +# bizarre bug on SunOS 4.1.3. +if $ac_need_defaults; then + test "${CONFIG_FILES+set}" = set || CONFIG_FILES=$config_files + test "${CONFIG_HEADERS+set}" = set || CONFIG_HEADERS=$config_headers + test "${CONFIG_COMMANDS+set}" = set || CONFIG_COMMANDS=$config_commands +fi + +# Have a temporary directory for convenience. Make it in the build tree +# simply because there is no reason against having it here, and in addition, +# creating and moving files from /tmp can sometimes cause problems. +# Hook for its removal unless debugging. +# Note that there is a small window in which the directory will not be cleaned: +# after its creation but before its name has been assigned to `$tmp'. +$debug || +{ + tmp= + trap 'exit_status=$? + { test -z "$tmp" || test ! -d "$tmp" || rm -fr "$tmp"; } && exit $exit_status +' 0 + trap '{ (exit 1); exit 1; }' 1 2 13 15 +} +# Create a (secure) tmp directory for tmp files. + +{ + tmp=`(umask 077 && mktemp -d "./confXXXXXX") 2>/dev/null` && + test -n "$tmp" && test -d "$tmp" +} || +{ + tmp=./conf$$-$RANDOM + (umask 077 && mkdir "$tmp") +} || +{ + $as_echo "$as_me: cannot create a temporary directory in ." >&2 + { (exit 1); exit 1; } +} + +# Set up the scripts for CONFIG_FILES section. +# No need to generate them if there are no CONFIG_FILES. +# This happens for instance with `./config.status config.h'. +if test -n "$CONFIG_FILES"; then + + +ac_cr=' ' +ac_cs_awk_cr=`$AWK 'BEGIN { print "a\rb" }' /dev/null` +if test "$ac_cs_awk_cr" = "a${ac_cr}b"; then + ac_cs_awk_cr='\\r' +else + ac_cs_awk_cr=$ac_cr +fi + +echo 'BEGIN {' >"$tmp/subs1.awk" && +cat >>"$tmp/subs1.awk" <<\_ACAWK && +S["LTLIBOBJS"]="" +S["DSLROOT"]="" +S["OSPCAT"]="/usr/bin/ospcat" +S["INTL_LIBTOOL_SUFFIX_PREFIX"]="" +S["MKINSTALLDIRS"]="../mkinstalldirs" +S["GENCAT"]="gencat" +S["INSTOBJEXT"]=".mo" +S["DATADIRNAME"]="share" +S["POSUB"]="po" +S["POFILES"]=" de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po "\ +"ja.po hu.po et.po ca.po bg.po ga.po" +S["INTLOBJS"]="" +S["INTLLIBS"]="" +S["GMOFILES"]=" de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gm"\ +"o da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo" +S["CATOBJEXT"]=".gmo" +S["CATALOGS"]=" de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gm"\ +"o da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo" +S["USE_INCLUDED_LIBINTL"]="no" +S["BUILD_INCLUDED_LIBINTL"]="no" +S["INTLBISON"]="bison" +S["XGETTEXT"]="/usr/bin/xgettext" +S["GMSGFMT"]="/usr/bin/msgfmt" +S["MSGFMT"]="/usr/bin/msgfmt" +S["USE_NLS"]="yes" +S["LIBICONV"]="" +S["GLIBC21"]="yes" +S["ALLOCA"]="" +S["LIBIMAPDEPS"]="$(top_srcdir)/imap/imap.h imap/libimap.a" +S["LIBIMAP"]="-Limap -limap" +S["MUTT_LIB_OBJECTS"]=" crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-"\ +"classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mut"\ +"t_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o" +S["MUTTLIBS"]=" -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm" +S["MUTT_MD5"]="mutt_md5" +S["USE_SASL_FALSE"]="#" +S["USE_SASL_TRUE"]="" +S["USE_SSL_FALSE"]="#" +S["USE_SSL_TRUE"]="" +S["GNUTLS_LIBS"]="-lgnutls " +S["GNUTLS_CFLAGS"]=" " +S["PKG_CONFIG"]="/usr/bin/pkg-config" +S["USE_GSS_FALSE"]="#" +S["USE_GSS_TRUE"]="" +S["KRB5CFGPATH"]="/usr/bin/krb5-config" +S["BUILD_IMAP_FALSE"]="#" +S["BUILD_IMAP_TRUE"]="" +S["DOTLOCK_PERMISSION"]="2755" +S["DOTLOCK_GROUP"]="mail" +S["DOTLOCK_TARGET"]="mutt_dotlock$(EXEEXT)" +S["LIBOBJS"]="" +S["ISPELL"]="no" +S["SMIMEAUX_TARGET"]="smime_keys" +S["PGPAUX_TARGET"]="pgpring$(EXEEXT) pgpewrap$(EXEEXT)" +S["OPS"]="$(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT " +S["GPGME_LIBS"]="-lgpgme -lgpg-error" +S["GPGME_CFLAGS"]="" +S["GPGME_CONFIG"]="/usr/bin/gpgme-config" +S["SENDMAIL"]="/usr/sbin/sendmail" +S["DEBUGGER"]="/usr/bin/gdb" +S["SDB"]="no" +S["GDB"]="/usr/bin/gdb" +S["DBX"]="no" +S["AR"]="ar" +S["RANLIB"]="ranlib" +S["ANSI2KNR"]="" +S["U"]="" +S["host_os"]="linux-gnu" +S["host_vendor"]="pc" +S["host_cpu"]="i486" +S["host"]="i486-pc-linux-gnu" +S["build_os"]="linux-gnu" +S["build_vendor"]="pc" +S["build_cpu"]="i486" +S["build"]="i486-pc-linux-gnu" +S["EGREP"]="/bin/grep -E" +S["GREP"]="/bin/grep" +S["CPP"]="gcc -E" +S["am__fastdepCC_FALSE"]="" +S["am__fastdepCC_TRUE"]="#" +S["CCDEPMODE"]="depmode=none" +S["AMDEPBACKSLASH"]="" +S["AMDEP_FALSE"]="" +S["AMDEP_TRUE"]="#" +S["am__quote"]="" +S["am__include"]="include" +S["DEPDIR"]=".deps" +S["OBJEXT"]="o" +S["EXEEXT"]="" +S["ac_ct_CC"]="gcc" +S["CPPFLAGS"]="-I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl" +S["LDFLAGS"]=" -L/lib" +S["CFLAGS"]="-Wall -pedantic -Wno-long-long -Wall -g -O2" +S["CC"]="gcc" +S["CONFIG_STATUS_DEPENDENCIES"]="$(top_srcdir)/VERSION" +S["MAINT"]="#" +S["MAINTAINER_MODE_FALSE"]="" +S["MAINTAINER_MODE_TRUE"]="#" +S["am__untar"]="${AMTAR} xf -" +S["am__tar"]="${AMTAR} chof - \"$$tardir\"" +S["AMTAR"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar" +S["am__leading_dot"]="." +S["SET_MAKE"]="" +S["AWK"]="gawk" +S["mkdir_p"]="/bin/mkdir -p" +S["MKDIR_P"]="/bin/mkdir -p" +S["INSTALL_STRIP_PROGRAM"]="$(install_sh) -c -s" +S["STRIP"]="" +S["install_sh"]="$(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh" +S["MAKEINFO"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo" +S["AUTOHEADER"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader" +S["AUTOMAKE"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10" +S["AUTOCONF"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf" +S["ACLOCAL"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10" +S["VERSION"]="1.5.19" +S["PACKAGE"]="mutt" +S["CYGPATH_W"]="echo" +S["am__isrc"]=" -I$(srcdir)" +S["INSTALL_DATA"]="${INSTALL} -m 644" +S["INSTALL_SCRIPT"]="${INSTALL}" +S["INSTALL_PROGRAM"]="${INSTALL}" +S["target_alias"]="" +S["host_alias"]="" +S["build_alias"]="i486-linux-gnu" +S["LIBS"]="-lidn " +S["ECHO_T"]="" +S["ECHO_N"]="-n" +S["ECHO_C"]="" +S["DEFS"]="-DHAVE_CONFIG_H" +S["mandir"]="/usr/share/man" +S["localedir"]="${datarootdir}/locale" +S["libdir"]="${exec_prefix}/lib" +S["psdir"]="${docdir}" +S["pdfdir"]="${docdir}" +S["dvidir"]="${docdir}" +S["htmldir"]="${docdir}" +S["infodir"]="${datarootdir}/info" +S["docdir"]="/usr/share/doc" +S["oldincludedir"]="/usr/include" +S["includedir"]="${prefix}/include" +S["localstatedir"]="${prefix}/var" +S["sharedstatedir"]="${prefix}/com" +S["sysconfdir"]="/etc" +S["datadir"]="${datarootdir}" +S["datarootdir"]="${prefix}/share" +S["libexecdir"]="${exec_prefix}/libexec" +S["sbindir"]="${exec_prefix}/sbin" +S["bindir"]="${exec_prefix}/bin" +S["program_transform_name"]="s,x,x," +S["prefix"]="/usr" +S["exec_prefix"]="${prefix}" +S["PACKAGE_BUGREPORT"]="" +S["PACKAGE_STRING"]="" +S["PACKAGE_VERSION"]="" +S["PACKAGE_TARNAME"]="" +S["PACKAGE_NAME"]="" +S["PATH_SEPARATOR"]=":" +S["SHELL"]="/bin/sh" +_ACAWK +cat >>"$tmp/subs1.awk" <<_ACAWK && + for (key in S) S_is_set[key] = 1 + FS = "" + +} +{ + line = $ 0 + nfields = split(line, field, "@") + substed = 0 + len = length(field[1]) + for (i = 2; i < nfields; i++) { + key = field[i] + keylen = length(key) + if (S_is_set[key]) { + value = S[key] + line = substr(line, 1, len) "" value "" substr(line, len + keylen + 3) + len += length(value) + length(field[++i]) + substed = 1 + } else + len += 1 + keylen + } + + print line +} + +_ACAWK +if sed "s/$ac_cr//" < /dev/null > /dev/null 2>&1; then + sed "s/$ac_cr\$//; s/$ac_cr/$ac_cs_awk_cr/g" +else + cat +fi < "$tmp/subs1.awk" > "$tmp/subs.awk" \ + || { { $as_echo "$as_me:$LINENO: error: could not setup config files machinery" >&5 +$as_echo "$as_me: error: could not setup config files machinery" >&2;} + { (exit 1); exit 1; }; } +fi # test -n "$CONFIG_FILES" + +# Set up the scripts for CONFIG_HEADERS section. +# No need to generate them if there are no CONFIG_HEADERS. +# This happens for instance with `./config.status Makefile'. +if test -n "$CONFIG_HEADERS"; then +cat >"$tmp/defines.awk" <<\_ACAWK || +BEGIN { +D["PACKAGE_NAME"]=" \"\"" +D["PACKAGE_TARNAME"]=" \"\"" +D["PACKAGE_VERSION"]=" \"\"" +D["PACKAGE_STRING"]=" \"\"" +D["PACKAGE_BUGREPORT"]=" \"\"" +D["PACKAGE"]=" \"mutt\"" +D["VERSION"]=" \"1.5.19\"" +D["STDC_HEADERS"]=" 1" +D["HAVE_SYS_TYPES_H"]=" 1" +D["HAVE_SYS_STAT_H"]=" 1" +D["HAVE_STDLIB_H"]=" 1" +D["HAVE_STRING_H"]=" 1" +D["HAVE_MEMORY_H"]=" 1" +D["HAVE_STRINGS_H"]=" 1" +D["HAVE_INTTYPES_H"]=" 1" +D["HAVE_STDINT_H"]=" 1" +D["HAVE_UNISTD_H"]=" 1" +D["__EXTENSIONS__"]=" 1" +D["_ALL_SOURCE"]=" 1" +D["_GNU_SOURCE"]=" 1" +D["_POSIX_PTHREAD_SEMANTICS"]=" 1" +D["_TANDEM_SOURCE"]=" 1" +D["PROTOTYPES"]=" 1" +D["__PROTOTYPES"]=" 1" +D["HAVE_STRING_H"]=" 1" +D["_FILE_OFFSET_BITS"]=" 64" +D["HAVE_FSEEKO"]=" 1" +D["SIZEOF_OFF_T"]=" 8" +D["HAVE_INTTYPES_H"]=" 1" +D["HAVE_C99_INTTYPES"]=" 1" +D["SIZEOF_SHORT"]=" 2" +D["SIZEOF_INT"]=" 4" +D["SIZEOF_LONG"]=" 4" +D["SIZEOF_LONG_LONG"]=" 8" +D["SENDMAIL"]=" \"/usr/sbin/sendmail\"" +D["CRYPT_BACKEND_GPGME"]=" 1" +D["HAVE_GPGME_PKA_TRUST"]=" 1" +D["CRYPT_BACKEND_GPGME"]=" 1" +D["CRYPT_BACKEND_CLASSIC_PGP"]=" 1" +D["CRYPT_BACKEND_CLASSIC_SMIME"]=" 1" +D["MIXMASTER"]=" \"mixmaster\"" +D["HAVE_NCURSESW_NCURSES_H"]=" 1" +D["HAVE_START_COLOR"]=" 1" +D["HAVE_TYPEAHEAD"]=" 1" +D["HAVE_BKGDSET"]=" 1" +D["HAVE_CURS_SET"]=" 1" +D["HAVE_META"]=" 1" +D["HAVE_USE_DEFAULT_COLORS"]=" 1" +D["HAVE_RESIZETERM"]=" 1" +D["HAVE_COLOR"]=" 1" +D["STDC_HEADERS"]=" 1" +D["HAVE_STDARG_H"]=" 1" +D["HAVE_SYS_IOCTL_H"]=" 1" +D["HAVE_SYSEXITS_H"]=" 1" +D["HAVE_SYS_TIME_H"]=" 1" +D["HAVE_SYS_RESOURCE_H"]=" 1" +D["HAVE_SETRLIMIT"]=" 1" +D["HAVE_GETSID"]=" 1" +D["RETSIGTYPE"]=" void" +D["SIG_ATOMIC_VOLATILE_T"]=" volatile sig_atomic_t" +D["HAVE_DECL_SYS_SIGLIST"]=" 1" +D["HAVE_FGETPOS"]=" 1" +D["HAVE_MEMMOVE"]=" 1" +D["HAVE_SETEGID"]=" 1" +D["HAVE_SRAND48"]=" 1" +D["HAVE_STRERROR"]=" 1" +D["HAVE_SETENV"]=" 1" +D["HAVE_STRCASECMP"]=" 1" +D["HAVE_STRDUP"]=" 1" +D["HAVE_STRSEP"]=" 1" +D["HAVE_STRTOK_R"]=" 1" +D["HAVE_GETOPT_H"]=" 1" +D["HAVE_SNPRINTF"]=" 1" +D["HAVE_VSNPRINTF"]=" 1" +D["HAVE_FTRUNCATE"]=" 1" +D["HAVE_STRFTIME"]=" 1" +D["HAVE_FCHDIR"]=" 1" +D["HAVE_REGCOMP"]=" 1" +D["MAILPATH"]=" \"/var/mail\"" +D["USE_DOTLOCK"]=" 1" +D["USE_SETGID"]=" 1" +D["DL_STANDALONE"]=" 1" +D["USE_POP"]=" 1" +D["USE_IMAP"]=" 1" +D["USE_SMTP"]=" 1" +D["HAVE_SYS_SELECT_H"]=" 1" +D["HAVE_GETADDRINFO"]=" 1" +D["USE_SOCKET"]=" 1" +D["USE_GSS"]=" 1" +D["USE_SSL"]=" 1" +D["USE_SSL_GNUTLS"]=" 1" +D["HAVE_LIBSASL2"]=" 1" +D["USE_SASL"]=" 1" +D["DEBUG"]=" 1" +D["USE_FCNTL"]=" 1" +D["HAVE_DIRENT_D_INO"]=" 1" +D["USE_COMPRESSED"]=" 1" +D["EXECSHELL"]=" \"/bin/sh\"" +D["USE_HCACHE"]=" 1" +D["HAVE_GDBM"]=" 1" +D["HAVE_ALLOCA_H"]=" 1" +D["HAVE_ALLOCA"]=" 1" +D["HAVE_STDLIB_H"]=" 1" +D["HAVE_UNISTD_H"]=" 1" +D["HAVE_GETPAGESIZE"]=" 1" +D["HAVE_MMAP"]=" 1" +D["HAVE_ARGZ_H"]=" 1" +D["HAVE_LIMITS_H"]=" 1" +D["HAVE_LOCALE_H"]=" 1" +D["HAVE_NL_TYPES_H"]=" 1" +D["HAVE_MALLOC_H"]=" 1" +D["HAVE_STDDEF_H"]=" 1" +D["HAVE_STDLIB_H"]=" 1" +D["HAVE_STRING_H"]=" 1" +D["HAVE_UNISTD_H"]=" 1" +D["HAVE_SYS_PARAM_H"]=" 1" +D["HAVE_FEOF_UNLOCKED"]=" 1" +D["HAVE_FGETS_UNLOCKED"]=" 1" +D["HAVE_GETCWD"]=" 1" +D["HAVE_GETEGID"]=" 1" +D["HAVE_GETEUID"]=" 1" +D["HAVE_GETGID"]=" 1" +D["HAVE_GETUID"]=" 1" +D["HAVE_MEMPCPY"]=" 1" +D["HAVE_MUNMAP"]=" 1" +D["HAVE_PUTENV"]=" 1" +D["HAVE_SETENV"]=" 1" +D["HAVE_SETLOCALE"]=" 1" +D["HAVE_STPCPY"]=" 1" +D["HAVE_STRCHR"]=" 1" +D["HAVE_STRCASECMP"]=" 1" +D["HAVE_STRDUP"]=" 1" +D["HAVE_STRTOUL"]=" 1" +D["HAVE_TSEARCH"]=" 1" +D["HAVE___ARGZ_COUNT"]=" 1" +D["HAVE___ARGZ_STRINGIFY"]=" 1" +D["HAVE___ARGZ_NEXT"]=" 1" +D["HAVE_ICONV"]=" 1" +D["ICONV_CONST"]=" " +D["HAVE_LANGINFO_CODESET"]=" 1" +D["HAVE_LC_MESSAGES"]=" 1" +D["ENABLE_NLS"]=" 1" +D["HAVE_GETTEXT"]=" 1" +D["HAVE_DCGETTEXT"]=" 1" +D["HAVE_ICONV_H"]=" 1" +D["HAVE_ICONV_T_DEF"]=" 1" +D["ICONV_NONTRANS"]=" 0" +D["HAVE_BIND_TEXTDOMAIN_CODESET"]=" 1" +D["HAVE_LIBIDN"]=" 1" +D["HAVE_IDNA_TO_UNICODE_8Z8Z"]=" 1" +D["HAVE_IDNA_TO_ASCII_8Z"]=" 1" +D["HAVE_IDNA_TO_ASCII_LZ"]=" 1" +D["HAVE_WCHAR_H"]=" 1" +D["HAVE_WCTYPE_H"]=" 1" +D["HAVE_ISWALNUM"]=" 1" +D["HAVE_ISWALPHA"]=" 1" +D["HAVE_ISWCNTRL"]=" 1" +D["HAVE_ISWDIGIT"]=" 1" +D["HAVE_ISWGRAPH"]=" 1" +D["HAVE_ISWLOWER"]=" 1" +D["HAVE_ISWPRINT"]=" 1" +D["HAVE_ISWPUNCT"]=" 1" +D["HAVE_ISWSPACE"]=" 1" +D["HAVE_ISWUPPER"]=" 1" +D["HAVE_ISWXDIGIT"]=" 1" +D["HAVE_TOWUPPER"]=" 1" +D["HAVE_TOWLOWER"]=" 1" +D["HAVE_WC_FUNCS"]=" 1" +D["HAVE_LANGINFO_CODESET"]=" 1" +D["HAVE_LANGINFO_YESEXPR"]=" 1" +D["MAKEDOC_FULL"]=" 1" + for (key in D) D_is_set[key] = 1 + FS = "" +} +/^[\t ]*#[\t ]*(define|undef)[\t ]+[_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ][_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789]*([\t (]|$)/ { + line = $ 0 + split(line, arg, " ") + if (arg[1] == "#") { + defundef = arg[2] + mac1 = arg[3] + } else { + defundef = substr(arg[1], 2) + mac1 = arg[2] + } + split(mac1, mac2, "(") #) + macro = mac2[1] + prefix = substr(line, 1, index(line, defundef) - 1) + if (D_is_set[macro]) { + # Preserve the white space surrounding the "#". + print prefix "define", macro P[macro] D[macro] + next + } else { + # Replace #undef with comments. This is necessary, for example, + # in the case of _POSIX_SOURCE, which is predefined and required + # on some systems where configure will not decide to define it. + if (defundef == "undef") { + print "/*", prefix defundef, macro, "*/" + next + } + } +} +{ print } +_ACAWK + { { $as_echo "$as_me:$LINENO: error: could not setup config headers machinery" >&5 +$as_echo "$as_me: error: could not setup config headers machinery" >&2;} + { (exit 1); exit 1; }; } +fi # test -n "$CONFIG_HEADERS" + + +eval set X " :F $CONFIG_FILES :H $CONFIG_HEADERS :C $CONFIG_COMMANDS" +shift +for ac_tag +do + case $ac_tag in + :[FHLC]) ac_mode=$ac_tag; continue;; + esac + case $ac_mode$ac_tag in + :[FHL]*:*);; + :L* | :C*:*) { { $as_echo "$as_me:$LINENO: error: invalid tag $ac_tag" >&5 +$as_echo "$as_me: error: invalid tag $ac_tag" >&2;} + { (exit 1); exit 1; }; };; + :[FH]-) ac_tag=-:-;; + :[FH]*) ac_tag=$ac_tag:$ac_tag.in;; + esac + ac_save_IFS=$IFS + IFS=: + set x $ac_tag + IFS=$ac_save_IFS + shift + ac_file=$1 + shift + + case $ac_mode in + :L) ac_source=$1;; + :[FH]) + ac_file_inputs= + for ac_f + do + case $ac_f in + -) ac_f="$tmp/stdin";; + *) # Look for the file first in the build tree, then in the source tree + # (if the path is not absolute). The absolute path cannot be DOS-style, + # because $ac_f cannot contain `:'. + test -f "$ac_f" || + case $ac_f in + [\\/$]*) false;; + *) test -f "$srcdir/$ac_f" && ac_f="$srcdir/$ac_f";; + esac || + { { $as_echo "$as_me:$LINENO: error: cannot find input file: $ac_f" >&5 +$as_echo "$as_me: error: cannot find input file: $ac_f" >&2;} + { (exit 1); exit 1; }; };; + esac + case $ac_f in *\'*) ac_f=`$as_echo "$ac_f" | sed "s/'/'\\\\\\\\''/g"`;; esac + ac_file_inputs="$ac_file_inputs '$ac_f'" + done + + # Let's still pretend it is `configure' which instantiates (i.e., don't + # use $as_me), people would be surprised to read: + # /* config.h. Generated by config.status. */ + configure_input='Generated from '` + $as_echo "$*" | sed 's|^[^:]*/||;s|:[^:]*/|, |g' + `' by configure.' + if test x"$ac_file" != x-; then + configure_input="$ac_file. $configure_input" + { $as_echo "$as_me:$LINENO: creating $ac_file" >&5 +$as_echo "$as_me: creating $ac_file" >&6;} + fi + # Neutralize special characters interpreted by sed in replacement strings. + case $configure_input in #( + *\&* | *\|* | *\\* ) + ac_sed_conf_input=`$as_echo "$configure_input" | + sed 's/[\\\\&|]/\\\\&/g'`;; #( + *) ac_sed_conf_input=$configure_input;; + esac + + case $ac_tag in + *:-:* | *:-) cat >"$tmp/stdin" \ + || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5 +$as_echo "$as_me: error: could not create $ac_file" >&2;} + { (exit 1); exit 1; }; } ;; + esac + ;; + esac + + ac_dir=`$as_dirname -- "$ac_file" || +$as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$ac_file" : 'X\(//\)[^/]' \| \ + X"$ac_file" : 'X\(//\)$' \| \ + X"$ac_file" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$ac_file" | + sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ + s//\1/ + q + } + /^X\(\/\/\)[^/].*/{ + s//\1/ + q + } + /^X\(\/\/\)$/{ + s//\1/ + q + } + /^X\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + { as_dir="$ac_dir" + case $as_dir in #( + -*) as_dir=./$as_dir;; + esac + test -d "$as_dir" || { $as_mkdir_p && mkdir -p "$as_dir"; } || { + as_dirs= + while :; do + case $as_dir in #( + *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'( + *) as_qdir=$as_dir;; + esac + as_dirs="'$as_qdir' $as_dirs" + as_dir=`$as_dirname -- "$as_dir" || +$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$as_dir" : 'X\(//\)[^/]' \| \ + X"$as_dir" : 'X\(//\)$' \| \ + X"$as_dir" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$as_dir" | + sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ + s//\1/ + q + } + /^X\(\/\/\)[^/].*/{ + s//\1/ + q + } + /^X\(\/\/\)$/{ + s//\1/ + q + } + /^X\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + test -d "$as_dir" && break + done + test -z "$as_dirs" || eval "mkdir $as_dirs" + } || test -d "$as_dir" || { { $as_echo "$as_me:$LINENO: error: cannot create directory $as_dir" >&5 +$as_echo "$as_me: error: cannot create directory $as_dir" >&2;} + { (exit 1); exit 1; }; }; } + ac_builddir=. + +case "$ac_dir" in +.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;; +*) + ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'` + # A ".." for each directory in $ac_dir_suffix. + ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'` + case $ac_top_builddir_sub in + "") ac_top_builddir_sub=. ac_top_build_prefix= ;; + *) ac_top_build_prefix=$ac_top_builddir_sub/ ;; + esac ;; +esac +ac_abs_top_builddir=$ac_pwd +ac_abs_builddir=$ac_pwd$ac_dir_suffix +# for backward compatibility: +ac_top_builddir=$ac_top_build_prefix + +case $srcdir in + .) # We are building in place. + ac_srcdir=. + ac_top_srcdir=$ac_top_builddir_sub + ac_abs_top_srcdir=$ac_pwd ;; + [\\/]* | ?:[\\/]* ) # Absolute name. + ac_srcdir=$srcdir$ac_dir_suffix; + ac_top_srcdir=$srcdir + ac_abs_top_srcdir=$srcdir ;; + *) # Relative name. + ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix + ac_top_srcdir=$ac_top_build_prefix$srcdir + ac_abs_top_srcdir=$ac_pwd/$srcdir ;; +esac +ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix + + + case $ac_mode in + :F) + # + # CONFIG_FILE + # + + case $INSTALL in + [\\/$]* | ?:[\\/]* ) ac_INSTALL=$INSTALL ;; + *) ac_INSTALL=$ac_top_build_prefix$INSTALL ;; + esac + ac_MKDIR_P=$MKDIR_P + case $MKDIR_P in + [\\/$]* | ?:[\\/]* ) ;; + */*) ac_MKDIR_P=$ac_top_build_prefix$MKDIR_P ;; + esac +# If the template does not know about datarootdir, expand it. +# FIXME: This hack should be removed a few years after 2.60. +ac_datarootdir_hack=; ac_datarootdir_seen= + +ac_sed_dataroot=' +/datarootdir/ { + p + q +} +/@datadir@/p +/@docdir@/p +/@infodir@/p +/@localedir@/p +/@mandir@/p +' +case `eval "sed -n \"\$ac_sed_dataroot\" $ac_file_inputs"` in +*datarootdir*) ac_datarootdir_seen=yes;; +*@datadir@*|*@docdir@*|*@infodir@*|*@localedir@*|*@mandir@*) + { $as_echo "$as_me:$LINENO: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&5 +$as_echo "$as_me: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&2;} + ac_datarootdir_hack=' + s&@datadir@&${datarootdir}&g + s&@docdir@&/usr/share/doc&g + s&@infodir@&${datarootdir}/info&g + s&@localedir@&${datarootdir}/locale&g + s&@mandir@&/usr/share/man&g + s&\${datarootdir}&${prefix}/share&g' ;; +esac +ac_sed_extra=" + +:t +/@[a-zA-Z_][a-zA-Z_0-9]*@/!b +s|@configure_input@|$ac_sed_conf_input|;t t +s&@top_builddir@&$ac_top_builddir_sub&;t t +s&@top_build_prefix@&$ac_top_build_prefix&;t t +s&@srcdir@&$ac_srcdir&;t t +s&@abs_srcdir@&$ac_abs_srcdir&;t t +s&@top_srcdir@&$ac_top_srcdir&;t t +s&@abs_top_srcdir@&$ac_abs_top_srcdir&;t t +s&@builddir@&$ac_builddir&;t t +s&@abs_builddir@&$ac_abs_builddir&;t t +s&@abs_top_builddir@&$ac_abs_top_builddir&;t t +s&@INSTALL@&$ac_INSTALL&;t t +s&@MKDIR_P@&$ac_MKDIR_P&;t t +$ac_datarootdir_hack +" +eval sed \"\$ac_sed_extra\" "$ac_file_inputs" | $AWK -f "$tmp/subs.awk" >$tmp/out \ + || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5 +$as_echo "$as_me: error: could not create $ac_file" >&2;} + { (exit 1); exit 1; }; } + +test -z "$ac_datarootdir_hack$ac_datarootdir_seen" && + { ac_out=`sed -n '/\${datarootdir}/p' "$tmp/out"`; test -n "$ac_out"; } && + { ac_out=`sed -n '/^[ ]*datarootdir[ ]*:*=/p' "$tmp/out"`; test -z "$ac_out"; } && + { $as_echo "$as_me:$LINENO: WARNING: $ac_file contains a reference to the variable \`datarootdir' +which seems to be undefined. Please make sure it is defined." >&5 +$as_echo "$as_me: WARNING: $ac_file contains a reference to the variable \`datarootdir' +which seems to be undefined. Please make sure it is defined." >&2;} + + rm -f "$tmp/stdin" + case $ac_file in + -) cat "$tmp/out" && rm -f "$tmp/out";; + *) rm -f "$ac_file" && mv "$tmp/out" "$ac_file";; + esac \ + || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5 +$as_echo "$as_me: error: could not create $ac_file" >&2;} + { (exit 1); exit 1; }; } + ;; + :H) + # + # CONFIG_HEADER + # + if test x"$ac_file" != x-; then + { + $as_echo "/* $configure_input */" \ + && eval '$AWK -f "$tmp/defines.awk"' "$ac_file_inputs" + } >"$tmp/config.h" \ + || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5 +$as_echo "$as_me: error: could not create $ac_file" >&2;} + { (exit 1); exit 1; }; } + if diff "$ac_file" "$tmp/config.h" >/dev/null 2>&1; then + { $as_echo "$as_me:$LINENO: $ac_file is unchanged" >&5 +$as_echo "$as_me: $ac_file is unchanged" >&6;} + else + rm -f "$ac_file" + mv "$tmp/config.h" "$ac_file" \ + || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5 +$as_echo "$as_me: error: could not create $ac_file" >&2;} + { (exit 1); exit 1; }; } + fi + else + $as_echo "/* $configure_input */" \ + && eval '$AWK -f "$tmp/defines.awk"' "$ac_file_inputs" \ + || { { $as_echo "$as_me:$LINENO: error: could not create -" >&5 +$as_echo "$as_me: error: could not create -" >&2;} + { (exit 1); exit 1; }; } + fi +# Compute "$ac_file"'s index in $config_headers. +_am_arg="$ac_file" +_am_stamp_count=1 +for _am_header in $config_headers :; do + case $_am_header in + $_am_arg | $_am_arg:* ) + break ;; + * ) + _am_stamp_count=`expr $_am_stamp_count + 1` ;; + esac +done +echo "timestamp for $_am_arg" >`$as_dirname -- "$_am_arg" || +$as_expr X"$_am_arg" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$_am_arg" : 'X\(//\)[^/]' \| \ + X"$_am_arg" : 'X\(//\)$' \| \ + X"$_am_arg" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$_am_arg" | + sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ + s//\1/ + q + } + /^X\(\/\/\)[^/].*/{ + s//\1/ + q + } + /^X\(\/\/\)$/{ + s//\1/ + q + } + /^X\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'`/stamp-h$_am_stamp_count + ;; + + :C) { $as_echo "$as_me:$LINENO: executing $ac_file commands" >&5 +$as_echo "$as_me: executing $ac_file commands" >&6;} + ;; + esac + + + case $ac_file$ac_mode in + "depfiles":C) test x"$AMDEP_TRUE" != x"" || for mf in $CONFIG_FILES; do + # Strip MF so we end up with the name of the file. + mf=`echo "$mf" | sed -e 's/:.*$//'` + # Check whether this is an Automake generated Makefile or not. + # We used to match only the files named `Makefile.in', but + # some people rename them; so instead we look at the file content. + # Grep'ing the first line is not enough: some people post-process + # each Makefile.in and add a new line on top of each file to say so. + # Grep'ing the whole file is not good either: AIX grep has a line + # limit of 2048, but all sed's we know have understand at least 4000. + if sed -n 's,^#.*generated by automake.*,X,p' "$mf" | grep X >/dev/null 2>&1; then + dirpart=`$as_dirname -- "$mf" || +$as_expr X"$mf" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$mf" : 'X\(//\)[^/]' \| \ + X"$mf" : 'X\(//\)$' \| \ + X"$mf" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$mf" | + sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ + s//\1/ + q + } + /^X\(\/\/\)[^/].*/{ + s//\1/ + q + } + /^X\(\/\/\)$/{ + s//\1/ + q + } + /^X\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + else + continue + fi + # Extract the definition of DEPDIR, am__include, and am__quote + # from the Makefile without running `make'. + DEPDIR=`sed -n 's/^DEPDIR = //p' < "$mf"` + test -z "$DEPDIR" && continue + am__include=`sed -n 's/^am__include = //p' < "$mf"` + test -z "am__include" && continue + am__quote=`sed -n 's/^am__quote = //p' < "$mf"` + # When using ansi2knr, U may be empty or an underscore; expand it + U=`sed -n 's/^U = //p' < "$mf"` + # Find all dependency output files, they are included files with + # $(DEPDIR) in their names. We invoke sed twice because it is the + # simplest approach to changing $(DEPDIR) to its actual value in the + # expansion. + for file in `sed -n " + s/^$am__include $am__quote\(.*(DEPDIR).*\)$am__quote"'$/\1/p' <"$mf" | \ + sed -e 's/\$(DEPDIR)/'"$DEPDIR"'/g' -e 's/\$U/'"$U"'/g'`; do + # Make sure the directory exists. + test -f "$dirpart/$file" && continue + fdir=`$as_dirname -- "$file" || +$as_expr X"$file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$file" : 'X\(//\)[^/]' \| \ + X"$file" : 'X\(//\)$' \| \ + X"$file" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$file" | + sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ + s//\1/ + q + } + /^X\(\/\/\)[^/].*/{ + s//\1/ + q + } + /^X\(\/\/\)$/{ + s//\1/ + q + } + /^X\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + { as_dir=$dirpart/$fdir + case $as_dir in #( + -*) as_dir=./$as_dir;; + esac + test -d "$as_dir" || { $as_mkdir_p && mkdir -p "$as_dir"; } || { + as_dirs= + while :; do + case $as_dir in #( + *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'( + *) as_qdir=$as_dir;; + esac + as_dirs="'$as_qdir' $as_dirs" + as_dir=`$as_dirname -- "$as_dir" || +$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$as_dir" : 'X\(//\)[^/]' \| \ + X"$as_dir" : 'X\(//\)$' \| \ + X"$as_dir" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$as_dir" | + sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ + s//\1/ + q + } + /^X\(\/\/\)[^/].*/{ + s//\1/ + q + } + /^X\(\/\/\)$/{ + s//\1/ + q + } + /^X\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + test -d "$as_dir" && break + done + test -z "$as_dirs" || eval "mkdir $as_dirs" + } || test -d "$as_dir" || { { $as_echo "$as_me:$LINENO: error: cannot create directory $as_dir" >&5 +$as_echo "$as_me: error: cannot create directory $as_dir" >&2;} + { (exit 1); exit 1; }; }; } + # echo "creating $dirpart/$file" + echo '# dummy' > "$dirpart/$file" + done +done + ;; + "default-1":C) for ac_file in $CONFIG_FILES; do + # Support "outfile[:infile[:infile...]]" + case "$ac_file" in + *:*) ac_file=`echo "$ac_file"|sed 's%:.*%%'` ;; + esac + # PO directories have a Makefile.in generated from Makefile.in.in. + case "$ac_file" in */Makefile.in) + # Adjust a relative srcdir. + ac_dir=`echo "$ac_file"|sed 's%/[^/][^/]*$%%'` + ac_dir_suffix="/`echo "$ac_dir"|sed 's%^\./%%'`" + ac_dots=`echo "$ac_dir_suffix"|sed 's%/[^/]*%../%g'` + # In autoconf-2.13 it is called $ac_given_srcdir. + # In autoconf-2.50 it is called $srcdir. + test -n "$ac_given_srcdir" || ac_given_srcdir="$srcdir" + case "$ac_given_srcdir" in + .) top_srcdir=`echo $ac_dots|sed 's%/$%%'` ;; + /*) top_srcdir="$ac_given_srcdir" ;; + *) top_srcdir="$ac_dots$ac_given_srcdir" ;; + esac + if test -f "$ac_given_srcdir/$ac_dir/POTFILES.in"; then + rm -f "$ac_dir/POTFILES" + test -n "$as_me" && echo "$as_me: creating $ac_dir/POTFILES" || echo "creating $ac_dir/POTFILES" + sed -e "/^#/d" -e "/^[ ]*\$/d" -e "s,.*, $top_srcdir/& \\\\," -e "\$s/\(.*\) \\\\/\1/" < "$ac_given_srcdir/$ac_dir/POTFILES.in" > "$ac_dir/POTFILES" + test -n "$as_me" && echo "$as_me: creating $ac_dir/Makefile" || echo "creating $ac_dir/Makefile" + sed -e "/POTFILES =/r $ac_dir/POTFILES" "$ac_dir/Makefile.in" > "$ac_dir/Makefile" + fi + ;; + esac + done ;; + + esac +done # for ac_tag + + +{ (exit 0); exit 0; } diff --git a/obj-i486-linux-gnu-patched/contrib/Makefile b/obj-i486-linux-gnu-patched/contrib/Makefile new file mode 100644 index 0000000..64d8a31 --- /dev/null +++ b/obj-i486-linux-gnu-patched/contrib/Makefile @@ -0,0 +1,400 @@ +# Makefile.in generated by automake 1.10.1 from Makefile.am. +# contrib/Makefile. Generated from Makefile.in by configure. + +# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, +# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. +# This Makefile.in is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + + + +# $Id$ +VPATH = ../../contrib +pkgdatadir = $(datadir)/mutt +pkglibdir = $(libdir)/mutt +pkgincludedir = $(includedir)/mutt +am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd +install_sh_DATA = $(install_sh) -c -m 644 +install_sh_PROGRAM = $(install_sh) -c +install_sh_SCRIPT = $(install_sh) -c +INSTALL_HEADER = $(INSTALL_DATA) +transform = $(program_transform_name) +NORMAL_INSTALL = : +PRE_INSTALL = : +POST_INSTALL = : +NORMAL_UNINSTALL = : +PRE_UNINSTALL = : +POST_UNINSTALL = : +build_triplet = i486-pc-linux-gnu +host_triplet = i486-pc-linux-gnu +DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in +ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 +am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \ + $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \ + $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \ + $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \ + $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \ + $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \ + $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac +am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ + $(ACLOCAL_M4) +mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs +CONFIG_HEADER = $(top_builddir)/config.h +CONFIG_CLEAN_FILES = +SOURCES = +DIST_SOURCES = +DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) +ACLOCAL = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10 +ALLOCA = +AMTAR = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar +AR = ar +AUTOCONF = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf +AUTOHEADER = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader +AUTOMAKE = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10 +AWK = gawk +BUILD_INCLUDED_LIBINTL = no +CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo +CATOBJEXT = .gmo +CC = gcc +CCDEPMODE = depmode=none +CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2 +CONFIG_STATUS_DEPENDENCIES = $(top_srcdir)/VERSION +CPP = gcc -E +CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl +CYGPATH_W = echo +DATADIRNAME = share +DBX = no +DEBUGGER = /usr/bin/gdb +DEFS = -DHAVE_CONFIG_H +DEPDIR = .deps +DOTLOCK_GROUP = mail +DOTLOCK_PERMISSION = 2755 +DOTLOCK_TARGET = mutt_dotlock$(EXEEXT) +DSLROOT = +ECHO_C = +ECHO_N = -n +ECHO_T = +EGREP = /bin/grep -E +EXEEXT = +GDB = /usr/bin/gdb +GENCAT = gencat +GLIBC21 = yes +GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo +GMSGFMT = /usr/bin/msgfmt +GNUTLS_CFLAGS = +GNUTLS_LIBS = -lgnutls +GPGME_CFLAGS = +GPGME_CONFIG = /usr/bin/gpgme-config +GPGME_LIBS = -lgpgme -lgpg-error +GREP = /bin/grep +INSTALL = /usr/bin/install -c +INSTALL_DATA = ${INSTALL} -m 644 +INSTALL_PROGRAM = ${INSTALL} +INSTALL_SCRIPT = ${INSTALL} +INSTALL_STRIP_PROGRAM = $(install_sh) -c -s +INSTOBJEXT = .mo +INTLBISON = bison +INTLLIBS = +INTLOBJS = +INTL_LIBTOOL_SUFFIX_PREFIX = +ISPELL = no +KRB5CFGPATH = /usr/bin/krb5-config +LDFLAGS = -L/lib +LIBICONV = +LIBIMAP = -Limap -limap +LIBIMAPDEPS = $(top_srcdir)/imap/imap.h imap/libimap.a +LIBOBJS = +LIBS = -lidn +LTLIBOBJS = +MAINT = # +MAKEINFO = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo +MKDIR_P = /bin/mkdir -p +MKINSTALLDIRS = ../mkinstalldirs +MSGFMT = /usr/bin/msgfmt +MUTTLIBS = -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm +MUTT_LIB_OBJECTS = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o +MUTT_MD5 = mutt_md5 +OBJEXT = o +OPS = $(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT +OSPCAT = /usr/bin/ospcat +PACKAGE = mutt +PACKAGE_BUGREPORT = +PACKAGE_NAME = +PACKAGE_STRING = +PACKAGE_TARNAME = +PACKAGE_VERSION = +PATH_SEPARATOR = : +PGPAUX_TARGET = pgpring$(EXEEXT) pgpewrap$(EXEEXT) +PKG_CONFIG = /usr/bin/pkg-config +POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po +POSUB = po +RANLIB = ranlib +SDB = no +SENDMAIL = /usr/sbin/sendmail +SET_MAKE = +SHELL = /bin/sh +SMIMEAUX_TARGET = smime_keys +STRIP = +U = +USE_INCLUDED_LIBINTL = no +USE_NLS = yes +VERSION = 1.5.19 +XGETTEXT = /usr/bin/xgettext +abs_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/contrib +abs_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/../contrib +abs_top_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched +abs_top_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/.. +ac_ct_CC = gcc +am__include = include +am__leading_dot = . +am__quote = +am__tar = ${AMTAR} chof - "$$tardir" +am__untar = ${AMTAR} xf - +bindir = ${exec_prefix}/bin +build = i486-pc-linux-gnu +build_alias = i486-linux-gnu +build_cpu = i486 +build_os = linux-gnu +build_vendor = pc +builddir = . +datadir = ${datarootdir} +datarootdir = ${prefix}/share +docdir = /usr/share/doc +dvidir = ${docdir} +exec_prefix = ${prefix} +host = i486-pc-linux-gnu +host_alias = +host_cpu = i486 +host_os = linux-gnu +host_vendor = pc +htmldir = ${docdir} +includedir = ${prefix}/include +infodir = ${datarootdir}/info +install_sh = $(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh +libdir = ${exec_prefix}/lib +libexecdir = ${exec_prefix}/libexec +localedir = ${datarootdir}/locale +localstatedir = ${prefix}/var +mandir = /usr/share/man +mkdir_p = /bin/mkdir -p +oldincludedir = /usr/include +pdfdir = ${docdir} +prefix = /usr +program_transform_name = s,x,x, +psdir = ${docdir} +sbindir = ${exec_prefix}/sbin +sharedstatedir = ${prefix}/com +srcdir = ../../contrib +sysconfdir = /etc +target_alias = +top_build_prefix = ../ +top_builddir = .. +top_srcdir = ../.. +subdir = contrib +SAMPLES = Mush.rc Pine.rc gpg.rc pgp2.rc pgp5.rc pgp6.rc Tin.rc \ + sample.muttrc sample.mailcap sample.muttrc-tlr \ + colors.default colors.linux smime.rc \ + ca-bundle.crt smime_keys_test.pl mutt_xtitle + +EXTRA_DIST = language.txt language50.txt \ + patch.slang-1.2.2.keypad.1 \ + $(SAMPLES) \ + iconv/README \ + iconv/make.sh + +distdir = ../$(PACKAGE)-$(VERSION)/$(subdir) +all: all-am + +.SUFFIXES: +$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am $(am__configure_deps) + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \ + && exit 0; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu contrib/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu contrib/Makefile +.PRECIOUS: Makefile +Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status + @case '$?' in \ + *config.status*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \ + *) \ + echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \ + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \ + esac; + +$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh + +$(top_srcdir)/configure: # $(am__configure_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(ACLOCAL_M4): # $(am__aclocal_m4_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +tags: TAGS +TAGS: + +ctags: CTAGS +CTAGS: + + +distdir: $(DISTFILES) + @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + list='$(DISTFILES)'; \ + dist_files=`for file in $$list; do echo $$file; done | \ + sed -e "s|^$$srcdirstrip/||;t" \ + -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \ + case $$dist_files in \ + */*) $(MKDIR_P) `echo "$$dist_files" | \ + sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \ + sort -u` ;; \ + esac; \ + for file in $$dist_files; do \ + if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ + if test -d $$d/$$file; then \ + dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ + cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \ + fi; \ + cp -pR $$d/$$file $(distdir)$$dir || exit 1; \ + else \ + test -f $(distdir)/$$file \ + || cp -p $$d/$$file $(distdir)/$$file \ + || exit 1; \ + fi; \ + done + $(MAKE) $(AM_MAKEFLAGS) \ + top_distdir="$(top_distdir)" distdir="$(distdir)" \ + dist-hook +check-am: all-am +check: check-am +all-am: Makefile +installdirs: +install: install-am +install-exec: install-exec-am +install-data: install-data-am +uninstall: uninstall-am + +install-am: all-am + @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am + +installcheck: installcheck-am +install-strip: + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + `test -z '$(STRIP)' || \ + echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install +mostlyclean-generic: + +clean-generic: + +distclean-generic: + -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + +maintainer-clean-generic: + @echo "This command is intended for maintainers to use" + @echo "it deletes files that may require special tools to rebuild." +clean: clean-am + +clean-am: clean-generic mostlyclean-am + +distclean: distclean-am + -rm -f Makefile +distclean-am: clean-am distclean-generic + +dvi: dvi-am + +dvi-am: + +html: html-am + +info: info-am + +info-am: + +install-data-am: install-data-local + +install-dvi: install-dvi-am + +install-exec-am: + +install-html: install-html-am + +install-info: install-info-am + +install-man: + +install-pdf: install-pdf-am + +install-ps: install-ps-am + +installcheck-am: + +maintainer-clean: maintainer-clean-am + -rm -f Makefile +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-am + +mostlyclean-am: mostlyclean-generic + +pdf: pdf-am + +pdf-am: + +ps: ps-am + +ps-am: + +uninstall-am: uninstall-local + +.MAKE: install-am install-strip + +.PHONY: all all-am check check-am clean clean-generic dist-hook \ + distclean distclean-generic distdir dvi dvi-am html html-am \ + info info-am install install-am install-data install-data-am \ + install-data-local install-dvi install-dvi-am install-exec \ + install-exec-am install-html install-html-am install-info \ + install-info-am install-man install-pdf install-pdf-am \ + install-ps install-ps-am install-strip installcheck \ + installcheck-am installdirs maintainer-clean \ + maintainer-clean-generic mostlyclean mostlyclean-generic pdf \ + pdf-am ps ps-am uninstall uninstall-am uninstall-local + + +install-data-local: + $(top_srcdir)/mkinstalldirs $(DESTDIR)$(docdir)/samples $(DESTDIR)$(docdir)/samples/iconv + for f in $(SAMPLES) ; do \ + $(INSTALL) -m 644 $(srcdir)/$$f $(DESTDIR)$(docdir)/samples ; \ + done + for f in $(srcdir)/iconv/*.rc ; do \ + $(INSTALL) -m 644 $$f $(DESTDIR)$(docdir)/samples/iconv ; \ + done + +uninstall-local: + for f in $(SAMPLES) ; do \ + rm -f $(DESTDIR)$(docdir)/samples/$$f ; \ + done + -rm -rf $(DESTDIR)$(docdir)/samples/iconv + -rmdir $(DESTDIR)$(docdir)/samples + -rmdir $(DESTDIR)$(docdir) +dist-hook: Makefile $(DISTFILES) + mkdir -p $(distdir)/iconv + for file in $(srcdir)/iconv/*.rc ; do \ + ln $$file $(distdir)/iconv 2> /dev/null \ + || cp -p $$file $(distdir)/iconv ; \ + done +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: diff --git a/obj-i486-linux-gnu-patched/copy.o b/obj-i486-linux-gnu-patched/copy.o new file mode 100644 index 0000000000000000000000000000000000000000..b5ac310a13253f08fc6195e4050016b48a9f0157 GIT binary patch literal 44032 zcmb@vd0>>)^*4T>c?L2=5+{)O5H;ceVJB>&B7`L*14Ocs4Nx(JED#AvOlDZDAeuy( zj!_V;t*z9hb!%N}-Rg=P;8La9TI)(HT2N|nLt7VqpU=JLnGE^*e&6?x-@wf0Ip^Mc z?m6e4yFSlME)EsVvn)%wFH6~~mr|;2lS!GXVYJFpC%9QPRz*Kp9Q|u`MdzXMv9{c3 z=y0_7Q1_8Qmlr}}Az$ate$mi@gV!K$&x0%wn-`2#XGaUNQ=*mGX|d3O-38fRCV=IO zg$_l%*$2Kodh}?*W%tfN_pe#>yv%5>NgeY{^jwoYm$JON2=i@3K1fWVL{pVLFEhP5 z3k8`Eb^46>wbQzfgjXDywHHaoiPKs0g)K{5IH*s{05?%Y`!ecDb>U+5iIb>JlUF+IA_+qo%Q1+FNB zR-1|*9srRNH_P7ceA?>#lj`wqwss=tF650Z+xOJ>r$i%vjz#_)4edR%Bm3gN2Chh@ z?GaGHj^}$#@7xsh2QK>*?X;Et`uG-+TeXimx`x8agJ;ttM|vI`<@$f}(dvrmYnL1v z?;uRO-#7^I%8k=#_kPfwJMC!q0bJ0NF`dQD5WAKcy5EXkdl(q#dK4XFclRM&Q~bdb zLF)GF@FF17I<+{fad-C@&@`xG-TRQ!(%jfWU-$Eo5wZLfMB0#8nYa7Z@L(y>scYBe z(4ga0&$TR%h|o(FmkQyWhq|Oc%CIRflcO>ovy&gSN>?jZH&0^2W41 zJ>J2tP*ed~_5(DNZs_rz5l_07wc8KS7M4v&ik*{UKR_kmAzd`k^)vXTQ+vpYb)*=v zyYqFI-lfe@09Z#r!FYe?kf2AC3^bEFj66|rwk4Ck9fv&4jG^QPDEbjdJtiY8U z$-I{OiR%aWcXc0OC7n(PdvmBVWfdcZUwK>7&aIYu5%IOpmFUcWdW?6`fxXT6g-<>~1ED81%;{ z`hk3uAF$3R=p77Nmq##6Yuq|{XKdLQF^ES^hcNCit8I#SCjcQwa!3CB1QQ*FdzMGEA8Yw@F+j1yr6feTNQ@)t|DYTIFR`h?K>G+dhH8zWii*s zXsw>LYxb4sJDD1_X%b_c%iP3 z_4EfR`OfOi7wG;Ma+tg&R93eK^D|H-|I)<#|A^-w63@T+aR$bKt%2?b!E4-lFq27Z zb?63q<USmY9EDJbyLv zBbrBSX3p-tuq4p+9(r7iLxy6Q{R!0W?zfRbr*_UH-?J$gJDwMqV4au^Q@qeeB2b>zpv0%gCe0 zjM&Ct=e}U)Ke4XZiEtti&dp?DnDW8S9^ztvgsa5Fy2qm)uSJVCwK0$&U}D=4_xVmDO_l0-HYY$Kf8}c zqU^X?$8_AtD>{TGzh(T>hj!GFM-^XVSjhm40rf_7B@U?HKsAPSp!;D|%<(gb=0%+S z)Fc!d{|36h0xe^$)_Yn%*nv*nVpIW6&|(XQ@pWoNIb*Z;wFNb3Se{ z_2~}DV6_keXUA;UBho_fJ$SkUo1q+gnU_p&w>FK7ci5pldcr|drI>#I6{v`I)gJbd$NHxKdHLWLKce;d5Wir_t z59w7EW}x?U-haJvEVY7(LG%Wp@%{6D^z;=z0ijbZj#kp}EwEv^h%6(Lbl$N zg9kV?uNCts-iQ2DAL4i8Qp87Q_1y4<@t1E9b6{D59D93ngbU)znY8y4(ngyGVh+8` zg4a>{U~i5<_w7)maclG&-QA<_9em-xP)s*#pHhG5EfwB-Fpv6&4jowd1$ySrtyo*Y zU<`q7AVqf{+ywW@d>H8dn!a4C4sM}%j?0Il9@6(8<714yt`icb@IcoxG+eJzdO|j) zBu>a(JZCug@G%1QoNK&V*QtF31!F8p77uM`pb!WoWS+V)Kv9he#oJ{nJ3^3AS^Rr@$ zgSf)MR~knRHb}w*k7+J4_z^VhQS9xadwX|x(Ce#R3LPxaeJ)hPH7X9bL#No10*rsF zAkXzAkY{lU-Gtsm6=n{V{UvjHvx6qZ42@KVip0lIjI9`I|6;Q0MLd$V<5{yuMcSi> zJNM;v9>D7Ow{+Fv5eh5pnOxilx;&f*c0oZE$?E(t80anp;|FB1S_vh#iI-;gvUolg z=+gT%F0{95Tj#*mE{cK+8DI&vGRWe#N*1ul^Rn!mIc{Z4^kyGp*1_@YO?tg7MLAR@ zNDt6T*OQVZcx)CSX0+EV)GQ{^DG64ek!bbii?MCm z@&R%jnQx^9y1D=Qp}PLfx-dR6__Jekf|NIxf=s;Y(3fV9m1g6BD-c_p8=IS*JQtzz zEDF<}BC~8>!g7-Npc&_x$|glOa}&5y5d$~}B^WR+(SX2%^F6nxMXGQ2Mb`b0;)mde zhlioW!4~m|H#-mVSe1%q)Od&cYB$7VukkQ6=WBQOV{#R_04v~buFatAkvSf3IQhtKy|35}Ui1yF z_rJ!F_toB>Ygxn4r%^{5qBKR8ys;_{ZQfXMO8j7$yXar&K_I@DiR!AO*RtBLc0+v( zZJ*-vtKF)XZ*3M z3}bw(*cWRL!fdab{4q}5KC!spki{6ztfS9_&q1-pJW$6D0;=oA?)+vz! zIXdOz$Fv4PdfC|QO_WGu?}56~-zLA+`Okr!N3pp2CCt0zS+;BR4Sisu&mG{W?jsP> zQ?++@=nZ61yF+giqQ!fop+ATHqCn`4uXZ!K!`{x~x2@=Zx}M*_tKe6=gD%(i)$Td& zbs8Lrnsn|txJFTZ?a^%$%79X?Q=nY*nLu|f8Z)L_Ww;IoefGigH(IOtG2L3xyv*pH z&YihYG=TKLW2_RpQ72klHjCku8P*19bkx1t_IPoV1}SdP#SJY*et))T%UwkTeeCsOx+sVY3T zaqFY7^ysmM==s37ANBh-qXz0x#}*XJcZFV22k*h+2={&Tiocj02a%+A1twk)MDBd! zhEP0|vEz1E2;zYQu4o9v=$RN~aFkT5+vaKb7luuK%jNQ>jXNe@jxkZk*TXy~IQSk` zQJpUaxn4aJ+M-D}zcMhE7mO{+j)wO2bnitsj8^TZc{I}%({rs(kj}EJtKTcgH*8n; zUkGs{{+IrUZrsyD8N97@?ftAp?iTeF??Wx)&4PuaZJg}&_2YG9_{pW!``Xyk?BB*J-|E|+OB#V{@ATcur|h+EC$@3 zkM?qvWM%K`*@Z2t1(CIvtX|pC?mdtlz4j%1{=YaS?o|#@RTwuj4&3?=voKvt$-VVs zUH$sF8z}vx2Pl2qvVA8-_D2u<-w2Q5MvCXVQ2!+ua#SB+SN5g~clFan;vc{DLPpZj|mSjfH%R*yJev1OD_DA!A z(LK>c*&H(5==_pue}_^ffKx z;0-LG&0|KrdcaD8vE#oLd&X8dYdV}kCY#huD8dnmK!??DD=$7NTCSvQFow&d1cKUe8MV|`)237ag3;o`=KKO3D+@w>h!HOYqS?49 zF~g>NK80me{47jnb^kL7hhYb~AvNy0q&Uc9fRDF)oVqpfh5b_Jp=sJ%X>gt~U2mOY z^TsEhrFZXy6|->bJvIC@!yqnpZa zV$)*3SV)oDCv5jIU@~6VIT695fx7I+zrguLT#oT~c#FZ0?=+}|aQt3_CP8^?pf%#S z^kn(Xme)oFL+)-mFSx9dC_FF_xX&Pa8Bul-1RpB6VwL1t-9Fw2CEynl-dv zLQ@Qr^nOfdW6kML3x^{QodHcfXuWJHBIJmv@fKj}NRSDcNA-&A6*xK}54<}jK?2CJ zy`)m(lC3I89j_Y=18Yt);%N}#al!;^c1o``y}~DowrF?iGpW}=l9Lli)HOxwlFX;} zl1fblAu-@V*3)`PrB3f9DD{lqa?Co-C`sR)d9pP*y{i9``*ioqm&_M2hcx95G(gF9+Lu<>y&M|1|4t@IAwo{}a^L|9I;*O?v&y zkh8xdq|ZMAb@d-CWQzY8l9@uL`G1ZE?0OVxtZ2!Ad;}juB`-8Bme^AKr{%f#o>_5zU92IzmPx7yXQ~PII&uDV0e;SP+ zDHcuhe*j1JA1h?8e=W)J77vd+!{_){v7$-VEKL^ppF|tKTL}Xgyp6hQWxlqXE{tl8w z)(Bm;-hV$Omx#`*{6Vn$ms#)WdYjb%E{yu$@5@K?r}Te>Zb;tG+8#9?QORla*JH*Z z-sBr7e5Yw)pGxvxh5|`mMncM6_@Ftd*WrR(#)Rhn+vSb|_e&7RF>jJri`fSSlFrtK zUx@he6<@E@7&X2&v~z}kSSPkc$uA($Khgw~N`43t=pQAam3$5!)9{ZLt&(qK&M_?H z8J-gOJ2du>odj`S>lDxMv;fZ>{o@Q{2pCW#i+S&4#vESyrlVm~1`K`?*J-O8HmCua zGyyT4T#K3poM76;t7{r?BC~mh(;L^|YM^hxkR!n46nqRg#VDncpN1&|f=uuX_adt< z^gDQcz_34&`6=9xJU#?92Q5P21d|)AB(VIipw}cf>1+0>6L3nC+-xx)X%W%#d$Dao59PBPP1!=uTUS#d{YrTbWX zo8fp)_6*NTpTp{|l{{JGe1Y*M`Dem8iJYNuWAY8cIgy-7C<|8^$tRE#q@K43Cleev zD2AJpZ?y)&fPpC~;}+5>n;DwprQy@s*Q=Bq@?m~jOKVuAOptbmj8yXf3`0^T zo`B1NX{il2Py|~owNXSQzX9o~D-GpM_M+FOt{R~o>PvnSg;Sf1#1!QTz?jtY&xMTR zy{R*-zv0%4vm05Ia~VD?=PtC4$GH#!ZKo57UgvH&t)H_RI`?-Thr^Sc*Wev5l|5WEgl%49-L&MXY3z2%dGXVTE zoHOCQX-+P#&vc%Jp3|LmC^f?gL-SncLYOqu`3SYla-Kuk+0Fr!-Km^maKux}*#J$S zR?fR9_>6Lfd_eWn~92z(A3VBZ%g zhXP+J=VjD)L^<~WzEVypM1PF}koh0wTmg&ztDFm<**D4=50`(doH|JP4nBjgzgNx_ z_~oc_o<$9tE$2tD{SwQ0809XtoIFsSma`L1?y{W6P;Iy6{1!G`W;w4S?Q+Y>LC!6f z^LG@FTF$dj{>PS6irQl+0B2ocIZNQ49?Lle)RmTV2*R$ioO4iatL2;pVcRTcEs9@l zIcZo1ZMU2kknk%m6xeZx3j3Zs8rs*Uz z9dKmHxEhtD4)pMP(2r4(FEzt67o`Vd&`UjDU&aeNo&`uTg%?5LB=2C*8S|k^>R=DA zle|&5W6*2(C`--t+=UeX0@R;6({r{is{A$zrp^-5J2>2`QfCY08(deXQs)SjGI#~a zJR#Hke}HpR=L(tOza6%w<_nqWe;)Ev3xv$_{|lj&8WQ7!{;9Apb)Jyf{tFQnsq=*# z?LQ5Mr!Ek3yx&1Prxpr1$=`_9NIgr)ss1}*T z&h^>X%v>U5f&X0ATPoy&^fM3xsf#?5;32(GC`!MI8Onu&l|m6*%Aq*Pn@m@KM_*QW zmg9QRPPAuAYPClp9Q|jp85fIE%Ks9=H+6}SUeokTbxyNrcn<1i7I`rug5YB6UKhr85vy>w7KCNPh{{ zr8e|hn31j{qER@Q^D{E*F~_E^6b|P6jLf=rOqjyJl%Jt8?xt2vojd_8PY5sl`)h@yikfN~=yDIvI6zMG zM;QfMgv=ehsvg!yJ;e~gm|D#ShYYfN6(x@!`495GlhT|Db&RKNYPsHC2IiFI_b;3EGoK$w2p9?30oPOl| zLOAK>(od#M&j<%r zs`No@hi8QYD^+G|bG=G^PB^eqrB7rS?h+2HROuYQQ+Eqz06AW^@E+m#$=S)ke_l8~ za<*VzN_{~%N#q=$&Myk5KRKT>&r8DTN6x<)eSZ{=mz)i>>t*5COaCS0Xn% z$^Q`pi~Pfx`mIb$W&Ueuudyin_|c3K9yd`5J(jc=01cr^*T;Cm>Cd& zEENzAhBK8ujE1HO2ce|Wqimmn!ohA(rCU^akl}c+_fzTH$w`+y81j_=Y$}~$8xMK? zVG223NS_&?9U)Wvk1)mu3z_Dh17DIXAYQb*V?Az^TBhe{o3%Zh1mJE&1QfuYKEKA&WXnvQVm}5P+}fs6 zPqiy_>#9udc2lQ{pY$NbBkR=Dgrf(ki8S|g;c$>je~JNghHyAY4PMjKqEe?xNO=dZ zsfAK!3Mt;5uIuL+g7*CkA=3s!p*(v(wC22@+f46i{zp(_>M|iS{X7y#Jx>G& z{p;D}HFg#1^bF7TKfr)kZl9yc(f&pbAhi+!<4tE=Vb|)^N&X*koUgN2YI3T73$>~j za+<$XFOY=H9lUl5TB_0hFPzND|DQ}xqdx`wFtS~uV=khA?y7(O~<-P$W{KE*mXN(h-mh| z$rufbuiE@yv!ZnpQ(^x|_OuQ58g2gC^u6@tk0e-dTDIQIgBJ-01Ht)y!ok{SefnIs)TP3~(6B!JXKap6 z;b3T3ZwA22#JY?8eC#~+a(g@Uw})@G5R&)9ge33N2&W`32Z1E-<@)nmh)OvFi5rnu zpHW&WOCO8&fN?TEkoRR>j#)AeG9tIwF2i%Q?HO9R{k0~wq$WCpisha-VZHTH5dM3u^I53T>o#IUkjy(Z37ok}!=iij& z{24abP7QSQI+tjhuLY;S6XGz9A_I?aWszTDY*5Z4=!BLtT03hn6tbNm@V?gxfz!_^ z1gF3AJ=~P!+yNmz=Uf!>;}(hMx46*9(w9M)4up$Ua131Oxl@OOeGB+Qr=)>#2dz@W zE`n)3YwnWj`xTl9BX}{ z7Y;l`SHrwe+`8M+buC9de}$RvAmKXJg*LJ7vh>)BBvyTw#We@-1!r>$1ezI}NdFGb z20a3Wd1Ge82v&8E7JNVGk((oq`w;dh9)j z1i2p3$~sNCPf*J^n5agE*P!atwBjeh6lKDKdXB#i)X{XqxEl-|Cr8yVPU_YQTRSQU zhtxp70+c;5%Q&T0JEaYrksZpa(`IoHqqpm|S>xc+k#Ja}t~UZI2lo}#T)f8~g=&_W zL2#aG?SK;2Bohj#=N+{4jmW?CWE`_%4!3modU<)pQ*hvqf zhZ=G}Np?|7pPKWVP?I@mSrhdQj%`^}cmQBc=5q5TB%bkya@mYrQ=VYeXE0FiCwYM6G|D&*4RZQ=Wt~Z4CWteR zGHp6Vcp}YH-e%*?7y;^DBu=>wrLA1%os14L?FlwJ;<*&nkKI8cNxMm%$xb~Q*{q>f z0}`iS2U<icdlOiv>ioA+mKwJJAE&<0nm^SH)8aQFn+XA1&9E+|gBF`Exesl? zb;jAyV$l$^IoqLHcgf4ZV!x=iIPKg@N;iv1eH(PP_I$P0^jp%}_0<-AKLx#K3~%;W zORTlf89isyw4Xo_52L4}rV(S|2dmYhYs-;Yjcdclm=PRM>f9n5ad2*x(44=^5CUDF zLFvm-;&-Q@Na7VOJ91d!s$cv!I=wTVpMQO+H*_g8e0dOzgBeqiGOud6V4Ko5>Gpz49 z(C#+V!Cv^*3M#b>iK~Ix{H~()oaZZ8%wv7y-{-VGcYvPRL7PpwXPeKs`#BFI<~=0O z((c}6Hj>-YW@&HlGP}-g8OGU$JRTO9k#>*AjI0MXj$G5RQsE9W6*&#*BjK4Bbm8+s zVNB=5KEt|?D(*A-ry=VVcyB?5Z-BG3{_kr2J=@f9t*#;OM;4>+yGCEovu>uWcSXUJ zSvnft6Ee-{^LMQeQ>f2BbmACL(Bw@v%N<6Ot*D*PJLDp13(!RBZQ66Zvu;$mO>6cP zX&tGzX;uCX+C=7UTKr(R(>UvPO_zc;%G{}y;fj#T{6?qV3QEoX1;VP|Hs0s9tl1mT zHTqp`h&k3hQ0HWJ(mXZ$c~mth{V{MXY_V?!&VCj{X8I=1$|$)5{W|?(jwK-Wpz{oJ z7z-ep;Hp7mIKF|vCyu*>_@@Qp7Iti;yoq`S{Yr=(ByKf?Uc8<*3{!=gy%vre^x#+! zDDf;+`eTI_tQR(Cn@rPC`@oV?ohkng=#_CoKckp>04jSF*Oiv_&2g#t)IaJ&dcp)X zG1AdKvAJo*#Fce*6Pu<^J3XhlsU@;LXJt!d;?xPJPB;~_PhE4QzQN=aV&aOXaK|y6 zV~B|z8;(t#*isj1?`Y^)r&L{Q+lC3~7fP*(gu^w4KLKN@QXS#?`i4ead+-eUhPH+d zT*8rHH?`stvmF$5FWn5VF5I-H!KAl0)=ir-1=o`B=wLE6 zx7O7*Qw(ZcQ`^+MqLoFM#YIyKI4hf5SJXCBI}lLGT!@Jv&|nBD7=fYvvwqe+XExab zF7@O(zA2v3j(xr-+gkggC;NDN&<@|4b8q)daO~|HeZj5Q+Ubp-`*LRHl-R2uxhrSp z;=krB^}TFg`1;j%`I@_?`-*%kuUeWjafa>p472QYJM4(B(f-uq+i$0wWrrv1So6iz zzM*!&Gs;@mvHdY$Q6#ec^Ea+s>D#t#Wy3^YQNzj)8?b@hZ;#5gmp0m?CgAgh+4T|M zLf<|0v&J>~Zff}44(|7@^mY5vCtr|f<6O_OXLv?i6Ybj9eZRlecT?xxzDa+c^u~>M z+f}|L_Il4G%RU+Db_uRLV+Y%(cuu$M8#jP@#6Hd!wA*v-0gdZF_uX`4z?eNX=t@Vsan|;BrJ!fQi zCLC}7OZgsoVW)3>SN){teZRcNP7m8_a_xZ=W=)^v_1HhY*f+>)*+^&Vbf75lh{g+L?;A6gXzMJfu9d+g%h-tM)0QRKPR zPV-E(>`|UA7F_wdeJ)zimtmg(2d?&o?V)=-iyS-bS!CIhJ^9wkoV#wZYr>v!$J>RT zaa7lLseO3UrS_$kFZ?qEz+aWG(YG$*`_kT{JbBi+_Cps#QpzK~;hwR_`zC(3!8bW- z4}RS@y6bA+WV^yM!Mf2iJl*%Gz0$V_7xI5px@TDW2k`mp(DyMgZ@kg>YfpB%k0H6j z*9cBmk$oQY8?(c=)(-o^o)H=L->?(39%)8+&pF zT`_a}nN7ZBXXHKV8#Xg%Th2_l)z>(4ai<;m%>L=cp2?Q|xP|sZ;9l66o9BDpPW6SC z+L8U9yo@ha<~({v9wpvnUx*%qlmnHyb9_bBvpnO{@3!aoCTM!?c+i=5+v|N39{1!1 zeE;-tn8xst-`WyxXbI<3Vl2?uV}QS5eOps|ZMdnmW#)*E8Nud;mX+aEGe1mKt$Vun`#>>VsiQ2{+V* zgQ3!SLkFn#hH#|4C8w=6ylOg#w&o2v;nwM@vAuQ8bX8Y3UE${Ubk)(&LboU;aWcqh zY;A6CT^DK7ndc#MP|Y$>5v~nKI;N{7IqsF)XhquB(^U}^M~3nSIIp1vZ8cpLw&axS zx+_tEG(xbssUti+IHF?!Ob@GyhOk;33KayKIyA4Kp}A=-1k~rSOq~PJ#$n0yT^O$(K9WT$bjwyI2 zlrKmu&u#zgg!Flr+Y2u9cJ_3-Bu_Nt$QFlv~5hS^-H_@18sd6TtjMA1`dj6DixT8CCnk>t;ZfTZ zkrJo|(bTyuo|U`AEG@m7$s^6Bo4g!kE#5SaSZA(%L>{>%8ppir@rH2(Nv=;6wOJ>Z z6Mm&HD+v7FDFiJi@}~u0K0yR5PZVI}FG`SqZelXe-DotC2cJ}rXhiiIy%FO1d@H>B zIN&*bSxxxNa0z^1&{EX|p4TDo9RPivsumM=X>K)v6(EDF3$40CODbD|l(0@M<1f)}!~ys_bN>Og%PrA4opOMeh^eH`hKQj~Nra&%9sb4et|}Y^%r{-0tWX(;1s^ zF5x(&TPmLVAyRoh2OGWw{2Cnum;VN&>5Os9czcugy&?N>1uqustkndm^Ke`$B`(xb zt5*YVGnciK%;PQ3=MdR`f0L9^Qnux-s>o9y5L%ohSbZI939d9^qrXG$liuPFfZ1<-qh_QQja86vE3WV*zP6qH@y3kQN7*E>(3H1khmG^DOi(6 zd<<_lGp~y<(xJad7!$~Awnr3FWY|9RbVC~^QwfY`T= z7i=}1!VCIMr?~#oge!>cGZ@ArWKRT8CNAms-{Or+T9=A9E-5+;193?^dtehTe+Qrm zxa1igwZ-K_06HI+ZdGhue#;IWw;ir2(8Vig>0q6)f|~xyT)Jf#yVMJ|xABWXL!bh$ ziKDbuWrXd*Ci1Cc^e}>iPMd2vOZJrvZ@j(kWvC{8dVAe3p#oLcDT&z~?WcBwE+*9IIw}a4>dVCh(@GUoz_@uaVTi7`f?yhKv8zJDxJ>6uY|unwTQyatuM%38 zD?lDu>gf;ozPa`h^+OB^BNy}5rZew0jX#urRF~i8C0>BM(22n3TF`_kL>5a>H9@M6 z(nTtImw7Q=q^1yCkOu}3L~2H_)Of@uNKH$S8Xrx_YtoV`t_E!4tp!!_2Rs?@uA?sx z0F0&;t|rT&xPDfH3pHHV;jKq`Aa88IK)Bt!m^T--(O1L@eI4-;pAFaG8{}(&F z33jB=4&EbyJTFo7O-az#o1kwB^<8cB^%Aet*O3&W*x@CL9VtZ7*Gnuk`lb*?UoTPg zMU40Q{d3(e+k8Zkmqr|H{Nf{uU($%r37;tP;?c);6gyLhQ%t*L5JkU~1pP7+^h-(5 z58>6T-v*;!8nF;^&>0Bg!c5{8!zTO`Z$wBY@f28r+;rvvb4d^zGl?JKP7&paYZCey zEs>fth>Sjjd_oXrxj_gvV^I{!BK{R`un7`^S;Tj=78L~1B8#{koh09-vA-Htq zyAB77PG)rpslP+3uo*DIF?E5tdSWX(KnaR>B&8H!oG)1%P8iY?XbrY91 zyQ(C}Sd}1SRc&v(tztQ8p;d0VSyDIr_UuNt*J|Qt(p5F#wwxyVmW58s-J-mH2X$tk zE?yJq&;DxBb}tsAygnW8BvpoHtl#b>LB+73T)y2~zCCd$Snk$z0UD+oZ+D5h4cBZi zmv-~*g`hv-%_)%hnz{B7t)SK@KCCnE2Hfi9FiQNP^lX#vB~D--RZW3^GK}gj!;{HTStCIT_a$}-~HzpLG{;p|gZB~^_%R+f2OIftAB)_Pt zAXHjXv~*r!c||4eJFjU9Gdu4EF-KleQR(8ml8QoQj_(`W@Vrt&gChiL=C(pA@>Z41 zt(rG4R30iQEGetf3Kxee^A?7dD%=NO-B7P;I##u|hxynq zLf`hU2}2{6g+H5XS9XZ#`~{)>g_Y%1@KXzJMk#n2x4l$TeM=2)eHa64S{oZtysfsq zb`9Vzof`mr~v>E5dymCKcx`ksD8aIztCM zSHs^DsG&2NbzWWtyjNDV6c01Bh4YrGs+L02 zQb?Fvo>y2@6q;9F7%C}%DmuEV3JObE3hhx;S~9<|Kv%W693Jg0DNQ>M)h$ppg{3v? z+MB`+H5eGsB<;9c*A{7CiP~Fm+i?x0m4~WJ@`^(WxA@jHDBJ@?C^q4i+IppZQ@5(A zxgPhzn6)5O6sinWl~m@9eU83q6jDsuCfASYVR;U~ik#FuKs+Fy+^&L$sSr*Qi zHn*^nH?dSlWX1V4eC9)iSLq;YYiL;A+S0s1)vYn1vAza(4ja(CeD0)AlR+4IY+hw0 ze5de*pN8hvwgy#+%JT~J4K(k5$pC_hwK9V$>4;)@p% z-p52zaRquqxv3U$wx(uXQ$2!_DQJ*_!t!E7e@N9w+M1i{YT;KgKu3FC0UNnOA#UkJ z6sjnkUs_UGTE^?Viu}UD`~`XC721B>=48GWwgq$Mqkkbd*0iCGI+|JK#IjYn*Pjy%@ z+)eZ@C@csWm!N;270Rzv>uTFsx59I47~a@I8*qnnt-jf8n5reRre;+Wo&hp;=2gS_ zVm&*)jwmR(0Bj5|xMIU2HW$l~3J$viYLu#(r=SpHMWx%z$kF{s_r_3(zDB^Uh^*vz z98b=xsw}P0ab-pc6hpAhD=#f(AFVN?6HH|vsthgBBPaqD;ZlU457*YMs=+;Yij!`t zn}U^dWa5B=aj}L2V~65cgE0X&UK?uYT9%qyijg6NzJX}Mn5vpL+La0;G6pkM zs_%+-K$*IxwkA9xpjP40DDAhh!m^MIm+_v;wnS_35dl??5TgilkDHZ=3pu=yEGsQ5 z!g!T1ceryD5>1~hEUC^bDlAYk7OR!*t&uj<@(9m@yov=FvS=METHDmoggf@Cqv^s1 zHLtKp&lY-$sE{zOEUKuUOuw}^tw68AP3;EL6f!nemFRw0SKCsvqM@cG(yTpOoL9cE zw5Wh8>tEBgi9OdaP-0-9RCF0_Aw3%0u%* zOUkqX{KnLUt6K5&nsyBW02$|DY$mz5ys$DfH$PwTu?YkU9&{j^^HE^|?Br0{QMJjIU`-7^a-3PSVpP=K7giiK`e_Y3_@bS> zIIj?E#-&O>q9Y^r(hBsSlDwjdxkaV<3(@f#+xTF)`*4RgzAO*xf-*i9$)uVZ&ant` zJzeN=4j$`hz=M@dVI9|c_I3wPv@8Qg8kU{|g=HYRJDzi?ai4SHtOm=P^>TFLs@63P z6I+^At_rs{w@$=p*;I>1XjZSB$f?wPw5~Wm=h(+b`HT$~TY4rcUQkw5j#$w3EzxTh z`VtGostPlil`pB${npHVW+G>nW4)mlrNQ_l#@{^aGoR^^fb%JYV?nh_50;n(P|Jcm zEPFz50G#f2yK)3TVM*RxEU^mbD+Fq7yBQ1M6|PA1BAv~O9?qe_Ojj+focm}EJ-46$ zaZ|(ofBIB226FZ*DlEp}P{8$N7-86K#(G8rBgTvfoC9Roa1k;~O7p9*;DJnJMlk7h z7WlpM7QG^K7ivHf*K1~ER($RWm6`1$>7BG-%SNERMX4#qQwXLAoUs z#TZanfB~Sbb`1swJoLpTWc_Pu+gD=^{sVhau0d*a*Ft%-I5E?kR+*-{J0J=#t3F*X z`KjJ9YQ-083ott=&g$%tW<{gNc9fo9HXkDvh6nbA`lfc-Q(*FH(L=mxebbU0&C%N7 zRZSf=tt|~)7If6WU_3^QC-01L#{?>yU9U%B27*v81VT&D@#dFQ1@nXYVQU>y*b-o5 z<5B}Ff_4O+R<8mvH5dCycP$py{ZqFB7ueXoAkerVXzYlu0r}*#UK3zxg84d6M?Hp0 zjFft`D9bCuL>A`rbcm0R@S55-lYqKPDhuZoVntk7T0*V#bWnjm2^)_}9V;;2bif)c zD{7fBJ{7x*tByME6lGClJV<%-@~2FidIrXNjAoeS@-eY;p^Hd`3G$$vu1j|pz12XN z=;edR3b%%_Sz}9LVn8R;O#y}YEFU%DP#wZ_y%ZAb8u0L(9*Xp6&JI?pr*O1H#e&ks zRV7sw90j<(LhWXEZ3^gy;=ZJ!@azypHMP}XqHLLpQ_fi!_8diVcExL8>uTN=(12~Vf;D|6G1g*56<+H4V-FVs)5s(l}8Tq zit^^qH^V?hRYe*0cIZXAH+85Q)PeO^dpH75xr=F()64VHvf@J2QZk>CFx}+IK2s9i z0Sq3+zL|M&L{O?Xi%YmBF-xF%SfaswWtBRC{Co^Wc_oFF^p?9BsaxgFij2Ncd1X=F z+)$C0X;wFty5bBR( z1`Kp)4!!OKfe9U}*XGC?X$wSbemT64ISEH@viLGx1N{k#(@3tNWOqbOtI@GbjnT!S zyo##wP%($Q#f(V3EjG($EIJpcxupe5O=qvITaDGd?(gyWi%sFKQBjZX^=1U+Ru)gE zn$ek+x|;;^+$q*(=wo_B#b&+6Ju%>}rFR?05KIWp0>qczidV>ht!nUlEbf$f! zr|uAG26wmyPsYlAq6CL$x~rj=tktd7>wHc{G^JE$%Ey)i3n{GFaHL=+f+>0l&pw4? zqxi8O&tQtsRk^RK!KMm(3w`R*I~VXVZFAaEhGQ%lQ;V@`t7yY$f^U+TwJ%0}-6f8l z=c!U9jtMvxFjjd~pwCa3fYz%jF0IC+&GWFvXlRpRmW?CxBBm%AF3p&wHwdyQ;^V~_ z&~WU4flEKNjExZvU+UVM^!747xz(_MUOJndE{^^5{G>Hv$1u@{^{v@)To7q8J0a?a zafM^WF`+FRN(?OSyi#I<2V)rOuJsWj+@^BbTw52$n6Au{kZsqF z10FLeqX0LIJS=5lbI{1;rJltwROv|-O}JLotku(>8%yG=3ou?bH8x>$-qMP##9A$- zn2lGc7tA~-;q0tul=zItWf^laBFb@Mi@Dv52sJejSdXSq^Yink2S*p^6||Z1b50v0 zbHAF~d1y^Ozqqk<9rQ+}@uG+B_YE~0)8nuRf zWC9L>8YW=rlY_|{hot}SFWfc54HDjFG_N@T-YIckIP=#pp55cIwD{}BE0hZ2P881g zb$Q-f;EkyfLgPM!e(gz+MTUD1VjQlS|NoY667o<#_eFU>b_;>&rp-;bX5Mlr!aFza z%gr|nj6^$jUW11da07#O&B_nJxfHsHBj$wP3{eueAAdJmvp`j_<%#M`ywFhK_|*P z40()o%A=aDyccopmcgZ333)qtAul)WZ=iY2c;#!?Qz3S7WE}v+}tukEwYeWed?8FLm{)CREY4*(Cm#teqksc7|EP)~()JMCP z<9eOY6F~2S1Ni+ErYF8^m8=TD;B(~se#-w$XHV&U**ek_X?m{rW$TDcq!R)kY+GT# zNqE^RAy9OB{2sQ>Wut}8PRP&NR`j8p`q1rt=u7+1u|710!T5{vZ;Vr>U)?vmADVIRz9|2QO8`kHCo~CZ{y{kRMVfy^+OORBAG)~@y%sbdk>YpL=#N;R^zD6UesjisvA#d_pIAiGVYex9M}Euoy;HJDK@s@9(}k`Vei44NR7B(*4&D}IMTb( zH0K1k--BDsNZ_t`Wka~m9t6k$|%S+%2rFZ|9E3R7-JY|I^B{IPgJUp0UXW zIG$T8hIG-ZrLJv*E4GmbxpBQ{067VUW83RJXbui=3}qf=h(FVy4MDBAbKb|+M2*dvK%+U2 zpt^Nv*w#jq#nhW{;+QY@-Ar58wzRh3o_urf?YP8UyR-!x_6N?b-CMNsfRMYtHaXYu zG#;w+zAqgqp~I5`oN2YxH)GqYRnRS>4-oWMp=;V!wy{0=wdfjt#TRE%yzJohu?Y!& z)roTRzR^6|B94U?Jh#vhtX-q|ChqlRM>CHV>g%AR-hck!Q(^9*D;}J|V-qd7UAQj( z3>Y7#!JZG#D!F%&-N$Qs89(qqhAS#whcxvriA{M&*@k$TIxtoZfe<%39@cUza z@?cXsR4`ZY=fof$8YB+Icc`#d^9;k69)K1$9vg^QrfnjBIKJK^^lycJnV5}7z=IC2%V1k zjp-)=S-w!{5}~gq!fy`{;jg1YPeogJ#w%4!%)uWfAYu{AKVU$4H`005f^6~eViTD#}+Mg4N@aK<-kpD{}E9iK@$f5e^X{GnX-t6@N<&m=+~e_@~XHW5)Te_V@p zTraqb2)X=`Ew=LrO!C@)K*N`SF9`x!?g7%dSlM1;>gGw{GL5&iIbBF3dZ5TVBl#6p~75K+(f z!p}lpj{7eY&q9C0wP&GHb;Kh4!4e?#`7vqe^D?m*Z^$Np08o#=#1j1W0uk~XhK%849p8a=Knou*!(VW5y}%`%eO?t zO8{kP|7;@UGzonTka2N6u^e$peg(!u((vOP^l9pME)n{z6uKSA{Ff3@{z~#I@r5JO z(B~1-(8q_dfc0e&b1)whtMO$d;$r;a9%2F7pST2i6PF^6FgJS6K|B(xFdq`Ze^~ej zh$#0T;b&kDrM*Ld9M47(r{IBcBJ?X`dM@lB&N64C7UoK*sx0&obZ?CaXN_=`vM|TP z4H{8QS(wX4O8TjS(*^Sc5pudbT%{4FYOEJrE!ZabBf%|#J%T?MyjSo6!JUFH3BD!x zk>Gy>eU_XHkcyFbs72mX@4U3yTp*7{&hpp z+{cpNF37WZ($@;!Blx)Bn}Yl+49xePpwDaQbittDM8R2t#e(Mwt`_894x_xNAlHYa z?-G1c@K1v83w|kh9AcUIhY6Mo^7o<1?-0C1@G8L_g7*nNEXW^@U^)JzA@K!4p0SdC zUGQzee+Y6N%JfeJzYzSdAa6=Ay}w|JApfQY`I&-41hWOl3QiI{T`*UWzZlN){B0p( ziD0GR*@DXjx&CFoX2Etr{w@*u{9_YDy*>v1Sm>>SKN0+e;LU>keG8VmTkw9tM+A2Y z?h<@S@Kr(nCFE4W|qBf-OhM+CnW^k8gaIiKKhf*FGP=aZ2h6ndnf{s9i~rwDzf z;2gpEf?VHIewE<4f^~xD3tk||-?w1?iv=$e>=C?1@aKXz3*I4kuOR=tBjr3H_?+NN zg0Bg_DfoB61A_k+JRq0 z=|;gdg8W0CG@xUl)8wkbl~f zaKH65J*D7s364++Q-kC)waY!Jr`j6gJbjuOt==o-4RokU!bX^r+y^1s@UI zCHR`)KLkG&Ou|Bl<4b2-GbK%@=rui&ZC0d zx08NP@KZtlkxcTB7t9tsRdBB0BEjW?{7ca+w?*(8!N&z(6HG%M=9?*4Dp)JHP4Gs+ zX9Qmnd|U88f-|LNuZ8Z%^DXcP5TQ?|;4tBj5_+=GrxRiSbisT{uO!0Hjlw@)utU->mh>*6 zZxOtQ2zkF3e255rUJ!gk@POdIh|u$Ep}!N_$MZInOC=)xWFq7a6&x%4(}>77g9v?j zuE+cpf;B{xs}tloAM>|K`j3R(EObohp9|h7e0~0ha`y`TsHE={`bDAnYyj*3m*CgJ zPr~^h>rEj-pESW?!XHIMxhX>HpICuCMM9q=SW9HP5Rv}^;jb0?5}_{>`X@xxcfH^* zg?}dz`utw#CnfzELH`eUI71WmpG5&8@f%n_U>=}QC~1v@1DVj}eG z6uey0w@Uh*LO&w-r0`!BJRtldg5L?>Kh(%g6&y%}Jtq>O=Ln%s6ATHSCFxZ{pDlEQ z&=J8-!KkGFMDSk0X9V{Oz9aaN;8%j)VMd>UfBb?w2J&*40c^>DMo XFQ`iu)c6UX@EOHON`uWJ7 znKSdubDQUR=9!t3>!StivmzavV6>(0pCAn*8|nhBnSj-nc*_@m)1FnCYK;%+e!1B; zQmxW1_H1umptP|$_TD2hpmcAOdfl&3_xrWIxH7dpc4uV6Y=AkHEzQ!-9>$CB_RbDe z#XgjB_r~;w{J4Wu|46EF@7}!%MkIL-j~b5q@)T;C1x_S+5|6;Di|x*SgGT|Fe)Ld* z*I>P^5zCjCEd_c{l~58Jla7C=@iDBa)mHSw%%}9XqaUVPt%CU96YW*!oHwxl(nL?W zy&~8dsFne&bE^Y;E9A+kP!O!jYV~`kyhyZ{3wIQK;Is6RF;dwRue{1In{x5y{~4cbw+j2?Fn~`6lXQH*@Lo42AUHhp$ z-9FlaZ4DXw%u;)9>FPI)gA8N5{4;5DVvi9&-<}t!*=oVdx+(}Muun!zftu}hy)G^a zTH7XViBA-6*D=Yg=q_ngY@bt^+R4+>;u(L59TNFbYh*)fcVT1mrp&?iiVy90pMCA8 zR?mvI$ZhIPw;kOj`ooW1H#yaMo!{C-|Bzj;3!7*BMbW=%^A$sCTH#ywLt20Axy2#@ zdtR~2;zXYj{}qC<{h8B0V=grGSZzGl^DMgVHbX>eXg%RpdgfcAC)iskdf~I9LA#+i z9^RUL@^j{@Ov}t8JZ+`(TEV+b__@sLSZY0&=qa`RcAds%kUTij1E1JX#!9r8(!-sO zc0uM3OjS@Dlvyti15xudR}(Kk|M!Pq95vARiE8x6FVQmsNn4$^-x2$ZnQ40HqRbHk zh8ASYHDmgTso7Q}38#xZw7E>|-rnrkU8P_9^6!iAlj&ayt6ioy6vxi8r`U6`FDO(b z`8`CTl)~B+xj89?k(deRr7A0pxwdBej7_VCx%NNtU0OaYVuX{{wjAGcfMatUpx2#{ z2N;{D)vs>GCe?S*e%GH|(|=o)G|G8c80mhRKNFc*@BYuOqfz zpew_dMRv#ty#I(^piQfpDM-SAAR*NQ%45uwSX z=vMJnp4GGAbM|tqY2%4|XU2}Tk5wc&lS4>!-D0&KPrYu_I-rf^-WTmW^`6IcJ`TVw zCE6Eg=dHB1!*@6;knO`8DD@J8&{m^nuPaF_+SOfTi`Zk6>_PD0gQn?5?7ej5V}b$X z6|CrT+p1;+S})nrF1w+_xLGp9<+ z9NcJEdTGEe9+BD_e>)w`jhEURN&QSzCAwRr4RaeDJF`DI$G@p%yye3IGXChf#9RK% zAE+KE;*I}j5nruD{NIsf_9NVqNJbRjt7?`^{_JJEJ+Qh6%N;9c9avpFI#Sb`-GMqB z7-HjrA@&FJy*!xO>g<={h>o{L2rV*gtQCD${8Ou=A5CqzIu+#RViS9A(5eqgXj5NI zP-fMaT089cr#8I_nY2O4`-4Q!bmiaEvwY&5ylOVq#US>}bYnjcu{Qw)+>2 z&4lW#PHW<0FS6~OK z>-bUdI-_?LNmX<`{~Fl)$cBO>0m%xGsI7_*7r%l%h-@gTt%~)^n|j{Z3-6k-aD624 z3Pu=XonGa$7p_ki;~DSi6s(O-agVY>o#&%Zs*7jvj;{CF4eM)q@iE(DM>MA^pOi+4 z4xhE7AaBnKR`ev=@*LbfBffss^ByI1{El$SHJ?`k#+eUVrVDSi7UX4`{S!E+XFpME zMsC=PHBQgIt=4R8j@ZqcDp-p=xN0Q>~n)aON_~Gk_3}RQI1y1?WradPSuf-aH zD!=D7?Kweymo@D8O;VsAD^okI&DP>TBv~l}KGoMjOyel2}lSCpp0j^ljsL|VF6YY3U z%}y2XEWCYFR{=4WZ&Nxj$S!5AK4ZmtYp69VVC`7-hDUYnhTE-%p6pgJ?$@%iUQg&0 zc&SsA$>^+8Q^vZM6@L}n>5M*;qWTf}r>3_vx=m6*ozdrQ^|K?beqLRxe!70Bes=vt z{bcyp0Dn7rtM#(AhxwH`Dxi-Y-yPmT1`Q*X^GCD^o~Dk$L}YqObO1|I29Wl zU9jWui33=x8Y47U&HJWbYXcd$aRt=e0m510{PE(rVf>V^!s* zHv^9Gow4emL}rR_o6_&>DD*?#{r&Rp*K6mlx;l|L4taNXfrgOj*aycH-h&=?U}mwt zslD+b*{k4)o~ItW?yMhpRXaIWUVDO+W5uNO%#&hCVGYe%yRQWBXnvlj`= zPV-xT*80#L(!V66A{+FCTls;u6+OyUtbE(*o3tg8>;}$yUnKPwzkkVC(boR68@%m> zWLxe{ZH*+47ly8At=SscFy}OX?Tl52Tbp5llnN+~SKP51?p+fYtml6GMQd9@v^DFa zG1KS}K*A7Z5zQ5#80s8_SMd!<+2KNqk%OR3qX|C0mx)8r2*?XJ<9IP4?bdv^V4Q;mxl**@#62GQ$-U!DUJo4*d@)S*(&q#1lZb( zCa1Pv_YIlf4ZG9pE~lAGp^VioW5Dkwezm*Qw#kc!*wB7_l$el(zB{e$w33YE$Ro-5 zYRoB&c{yV~krlZA*MWEZyMbL|B^MGKj&8W5IVdfzWWl85+nJgJ<^KR6#&fVPbyKR@ zNw`#CpIz)F_+JCYwOgb!p>XjdRp=SfMXAs)>oS)I-tNO_(~n;e5qAvU-Z7 z9>GxCs!}bZGv_$<^Yis;BGfzeI|(WG(M7KSj%IYbZlV{Vd3l7a)ESVn&vbAnK_nF( zME4eH6xraHm}?8nu+vhJ*zB`fF5sc*DxVQa{+<`s(=~e&ZT_aK{6@SXyN()Xx)0RP z#NMKK>A*@A563P{&-Ynr1@~&75o>6=+Ha(n`eO^2Sk`lq$6KXaPOu6Asfj%9&s928 zIBq#391kLjMm0kG=Z($QI-$T;)We!UgUC_I#aXFnRXV$vwZddC@6O8ePIGPl%70cV z9cOtvUNW$wM+>Z1uqt#DKmF6I7C>JVJOyaSW ztJ}q@syI5)7W88C?Sa?~AcNIJK-@(;G2QxLBo&iiKXH8O5P1qjQnDU#*qb+k^CZ3g zWyw61SF=`A97?B^ktvpCVSoGL20mWI1{#-ii|Q?N%fm2x-V`;^!rfMJZlL|aPp1Z2 zICmX0(3l)(pu7z^{Xj;+N}r3Aoa}(zq6+6$mn!2RNQs%z20|re6<548f02Puf+%Gk zBCz#Uk<^{QT3^>3pSut5XQCO&9!VLT@6N28VB9q_+hvi|hqTE`L;QmmjT!sV3El@L zQ?Hr7uP=}Q)@$2ze9|9o&3^%|)h3L{`r)&Rr@VNN9ROe6iCzAG#oZa>hqAVExLXBz z`-toI0pm$q*YsqwtT*867xn+)7xY(Dt`itKZu%lPUlb20IP?EAI5+(}d_EyYcJR>_ z)1@}iH!+fWjfk?Jhq#*v*5e^gMrPVWq~(S3C5cUbE4@HoeA|!fi1EUDDbZQb^z8zQ z7kK~#nyv~^wM1H|t~EQmFPAvUzXnP(@d<{s#(~8&%Bfqnl1hpHy?Xv%nV;K;D+kQ` z|IYl(o(JT9@#=qXUS|JJ#I5GNwONIb*=bY=e{?=>bV= z-zPcDsT=KSL?bM>yTs@oOttlKWP`XC<6(oJL|-^&Ci;pWzMVoWlF0ZT-X>3l4_`p$ zK|ru771>H2!ka#0-*UWc_*kiJV8|X2xT`vT6Ma6j_oEjRe;d+~+Jyoe>2>nsRT0@s z@|xpx%Pv`~l#A~zT`FV6)VKkIfeBW1u#--!R+7bY&S`jI-ZucIfLgvEQ0bI{;w-3~ zk6N9O zb<;0626inESc}MWARy#@qWlv{#!(u(MP$Xfo75aiA4P+D!)-H>vzL#b48YIouv4P0 zvPzP+x@0d8csq?j?)xE%=%Sw_iMCu}N{(1lUaFa<^49i>9(!T2P8hq)OY|*|BtL;M zkz0Ptzlpx3jm_~FYkECNG*23+X~<9-m9B1=sU{n@9AIf|PM=?%4oIADq>05uGR2yE z+2?USkIRNt_B4q}(lX;Dx$qqI_GszhrSo|yd)MZH>b=iV0nfApcKlEF8ZnG3jT1#l z_>Clg%EO6I@{h6)k<>66zyq5dL(*S?W{wvCM{1YMf9^4mBO0*zsK)gp$<9ucgUc zwdTJ~9_uEeXTox&g`(tZq*`H)KqNHHy_L;Y_F#o2ROj-)oMy=nnA+)ZFp_*-+U&AK-q;r!z&jMSwb@W%8040;mnJ@RZvd#O9Be?*qF=L6alyUX! zHE5yoMy7*Od-)Y~Tq;nS&ie8yYO@W@58|6>Ms{Syd^!ddskcQ^g-W|~#{}Sy7HQ^> zJ;W>Tvts)?8nb^c3wv=wO5>&uP+bkhJ048RzUa~8;!g2P?s^{M2+mfEnkVck>IoBA zojK<%_}!7+C?O;M*~MPiA~`vT4r=V&H!{wpxpCG9;`iFK1NM@jePtD=(^_`G(@4u^ z5^0}DT1ZJ&ZH|>Q@5wvb(`KaA+Z*2jFMM@`ea=KCfSZimAQ@+lbC~YA8M2-B%o!=& zUi6bSb(wu;aO3UBl2f0ta3t|D)f@jJvUM0G67m`)w_b?3HP68Ow(u9|fb;==PHzbb zBFVd3V%WKscOZdA1Hs z@}gXyS6elxD}n5F80f^Ff{pjnAd>tXz#IR-WA;OyyZ}lE0?2!?)Jeq4-nNGhXltv8 zte?|bfD?n$%npfB95v6@4gi$RGg@Qak!|nmKh`t*Ho1c)HG4T#)#wC@-u+~CzNl6k zPHW+gMyug9H&k?NwP&WZ4+O3^u(7DoptYw{WGVq&=Dt@@)F&EVvl^ba{$e-mNW9^b z49MX-p-qnVpEX~0WL|%rso&5gQ2e&aNB@aNjfrbtGhzfT&!_53WAC_-r|1I; z%$o_;j!f)%x-Kmyl__bWKnCbKV<95a%l@XBD944U8_lCMw`%hiRm{8WH;M*;kV3GB z2ihp)ouz zu^WQc$700bKi-nG>Z_7eYlFL)VRXpz92!`i8_l?LCDM80l8yt$CwnEbxAK{Fkmq<}gnaHmk!dwf4fGv%L|hCg1r@%oEA?Gxa%5PIX-gN{TbsxvZQ!!T-XOoKyX1fX(y1tCHE!*6r?x zsdG`ej(fkL;{~dt*9}RikwThR_{(aCjm!2p8z+OXS9_LdCY#?Lv(r zLZ^fG`plg!epBQrP(--5x=q$D-oa|NKje^^b6+EH7g(eVF>iVUDKl-Gp87)pA)uOM zOcelW(;+!)$vCSZ&lBY%h0M4AjNN>2_(OhqzpW7zLt7d-H{KW8+-MEgdf91I0g+a0 zs*a|SyryMg(=$HRDm%)RYyRb+rf2;6r8qQJ9;wCrW>Z?uz|w;WYO-_DIK=OBhJ8pn zFg9(*Zqjv6rKBR3?7q$6YhtgD*JkUK*2cmDzhLcjRt+P`GeIbOndq>#3k>t%aCOML zPcjD6<@F-|p;l944bRpyEM*t3_%V$`d^wyx(>P_nDlk_Hy8axx$OG)Ml24;cuKqKp zek%3*uD?{$x8BCtkycreeU(Y;GA05Z1yzv}Z&W?f5O-CW~${ zxj0%UT_PZIs^30Uu90Z|J}i^C`*(6aj`LZ1H`$I(wi_lUx`OtSfU__Bc(mMV5kA>x zm*(JP&Pnu*T)Bc_*t)kL5V4Tixu`cfIT$-m5Ry^tsBEDrGpMj_ko`WEm@0&kjFWgB z5Ov&$9UbA>d}(ZEidF%oIk&NvT*7>6lzf>6-;f7?hA>0cirECKt2 zM;~0c@!#1EmFX2-zzq&}W}_f2vk`o?~rTxX*zk{m|6)o&GCAff10Id#lFCy#kL@uN`J^v*%9ol7p1 z3DTVX&46~PpHg8*55yBUxUo~B6`5~5t)`0N%DzI)W|>hAzRnh7Bz3$4|60ZK!@N9K z0aAaS%T*V-hQJ>4BGDNYadn@R*NfEO86%Ic9JWH10au1Od>bZm|H6^qzWR}!DVX99 z{&Q{M21HJKzW}f@0Ia{>3Os%sxWyZ7N1Fon$yJ<1A7#%DLf*`p?cIZs7pgI1^A$CA zh(kpm2w9p;nr=n>z(qLXQ~iq$hy#EOr|ULp(WmHKq8MA37_n1cX58s_LoGAmmMj$Y)M&GE1}C$EQvvCg%ZZ;8@*?d|k$T*654$-SMv zjgmNyAJWUo_6y}{#Ok*UR6FsB&umR}J(g(wiZh>GQD#?)!(ra%SWztRvNiz8uf#`ipt!@At|%O7egdtsZKKfvoge87?LNc1CvyJ{&;R zKV9;Je2=tsqs3hCi4Cr4%|xFPGI!`+b}6-CJGvutWWQ>4G-SYj!amsyy_VqWOGB_` ztHAiSg25s19XS?X`@9&XUywU=lLymvG{?9uY9xonI{Jj{9jKhwINBP(NdQQ*d~Uf_ zNKLi!uOc&bZ|+IbhPv*4=Lz2^e#{+sLT+G5Arv!^gow%{2N01fNn0I;7{qJ0<77QE zIF)mV)t5=N!SXXDpAz^V>4x0IAiLJwo>#iwAG5gy>d0J_&Y5ghhZTJ_k~{`UcBXF6 z;d@W+>8{+f4+Z||=&L!kS|{9-Y{qF4LZzi6%e1wv@yT|JFbGsZMHE4xBwJ(Uc1lqyP0@vaN?7}oRdl(0#Tg`U%@h4 zMiD>5-h3tDLnWEFG;!jlu@@^q=T#NRJ;0R zsn_Y~uFOFoo`zU=Oywn%o6!z~{31!`G&j3*%d6e1+r{0fT#20$SC?H%8#^WLFMF~y zk9NuCyevnBXPn>5ijv4C&FhHJ)~-lR&g>XT>g#3o!dG21vS$Ly8)N3j_aLkBsNteF z`>lFTF(|WZUsIW_6iwIWp#Lti1;e}wBFxm@OV~MZyGol1=(86G9&#+Kv$iE|I!t0z3{{FyTlVj&;;oA!qQH?Q@$emBRP|z>VQMDD> zRsG)UPbule>0?`mH#)T-<1=7I7lPY`ZXz}WH z8AmQF?;DTFeXysUyJ;i<8n|n++iQSj#So|#g_c@9DXypztN*_UvZl5B7>RG`$y>Rj z=VlNZq}v~)n>%6iUzfPNcP=N)`6@@OLq>Dd*6K{WABc^q*(v*nK?10OIfJ<qi_fx zok;Zgr5rnr`|0pK)~LVV5`iGW+Dkx;Rjg)Nu{G-N+mz)r~{17gtYz`aCv37re5f58OfcaMIxG0|UCg^u=8T8Mo_& z1G-ibi62Nqv{#Syp7xtL-fsgFIGc!%C5#2qIX{TOw8L9=b?1Bm;{*ki+@3wf1v(HZkD^OLT+iOm8PSX7H4M@H zGwG_&j|ZxAoXNg{OdLm=qt) zh+@f&Xb171vbsP1Opv_(ooT84?n?B}O6`7MX|v?WRCwn6%C>E8<7TW}(vBn(R5cT# z=^jDJ1F8^6!N~J2wm7{`+E}moI0y{QN0o*GDRKzsP3Kj=jM41x)aF*U-C z&ZswM=28Ocrw~$a6lLZcU@g~xisDLIJ-I6wK1UVZo!Z{XcNh3C7Iq^*YFRK)rRXHg zCvMLj7DEs3!XQL847Wb$j5bNn^tDMVC6Kv|&T%AaYFarqRnZJb*OV8@*K6b}I+4_^ zyy}=!nB=oHO-o_K&m! z2C3I{-~pZ;nJemYk#CO}sD({d`5N^J9+v7f1Vt;}6iJ;8x}e9KtR%yA+@|n9N8a>( zMaLh6mkDQUYno6lny-TIZ2t;kG$G1V2WI*jcBJWv8}FCrDce2pFt2 z!nG_pm#}<)>Y!*xrsUNWdtLEr;W(NH14PW}O2vn41;$<5my2mGpWt}O`M_56UisLA zRvR@wk{n*s+Ruc$c}?ZEevbW3?Y*vyHq#{j!IRlk&FH-TeR;l~=R0I*v~8G+T4$lu z$ba&wtcH8Jy-fg>xUN{{v0@qL@2u$k;!?1B@=X!7|B=g!vGCo1t+&&bqysSMaFX#~1TIBFl0LSSG#ELbdDFWCPxQ>%|`=A?NEOmIx2HVh5-cvnQy zb?%7F%6~}Ic@GWyEmIWW-CU7pm7o?Y#P&nKbe3xM~C@ZE)!=O{MgDT?HTGGJu{Xp_Mh;Yp4;p%ewpH9O(_2}+c) z+;$$H1khjmBN5k0M3dUN5k3*aKTIL}NB(Jcw5vHQxj2`D!n|wp>b*aP5QEk1+~14+ zu*dl@KvpKOvXt558QNYUkw;DdllCKkm$8IOS~u@jeBUn%HX})!FMjMvwc62p`CejX z8&Xooyzdmv&c^l~?4&OmZ0r{d*1%xd@53rteK)Mnt^xMHp(3YpTXALzQP9jx7ES8U zfq5vtR|Vxe5<4QvPX+yYb-wx^@>n-fRKGove2Y>|YvSslLGILwK1vebozr|nN*Jd< zTa=!Y$ls9Ve4H%wJ^Lt}=5>-CK8{^K%4|ygLW}`JY#{lHo-%7?;D&bUq^k1ueBv}Z!^kN0* zDgpH7r*cz_+rG0{A-+H%5q;IiSNb+IytJl_gLllCHTCj67gYUjARiCp?t3+nN(a?_ zH2H*OKddFD_h8+nv6fXcwTV_vT|T3)p@|(xuz=%KuK62v;~^3lxt`|px7C0 z5FcrlxHcxki(~GRGB^HElpPm)Q?$H%DuMqtN_=NC?ukMYb8f$ zmqTd7GwQ)_H*Dddqdrizrk?MA6eg~14a8S#ZmM&NAe~<1%l-mL`^JarJj}Twqtr&x zSPql4+|PrRmb@G;AVgKCkOc9;%&##eY|ijXYDkdsMBLt@`mU3X_Ni5NfxToz=6&p% zWISUlGqHcM6|kX2y2&@m#2Bw_C1rmZK|oN&AuR$3ZB&A?IyiTFy{mA#eX0%|wJAx- zFuirSht!>dI2H~L?zPt`7&()(x?Pdw{XUa?21np9tU4{LXpk^S(c#Vu89u(ce;pxU zWi@EGv_>}Qi_3b<7U2?`48x$1*D1+dfKZKda9i<(#Kz)8*Y&C1HM1A9(aHF1IM7YD zAI_n@9cP!v;WKowS)m9N|Cjn2?>VWwv!=JZgmVvlsD13HORG-RJ;3V9{dK7a+9RbED9FBAiP{{*4UyPn~E-DKo}R_onW z-+qp%kEM_BMdSv}rA6-Cjt0{$J)qol!IIA~2ZGV&kZvp2pcGTmX=x$dQ!v)uRDiRc zoR036bTu%&gG01v7us7)|E0ZzSN!}`J4EM1Zl~=B?nO?~|WL&PvoH|{uy~&~M z-q}lhu}ZR&kqxt!B)0fKBC=u05+t2?)1SjBeuXD%lU^sBaA&D&Fb~Z3DhBnieFO_{ zt!4_t)$JlTwKjCu3k|!~m3?AuSl^H=AyT5=jYBARAZT;f`t+O(- zopHVGo*B@tdp-VU1x%U^d*;I)U*e6=Lz{>}<}Zn)UIvJ~O1$w|qRSuJM5X$ivR)^M zP_+(-o#mVb|9Z!oI$$iX9P|CMe_{}2&)APz-7_7gIV_iNT$7Vm-@D$A)*sxT{k1vv zv*)$EmZUPDudQE{=!(?(W7WO$#Qr}8@W%yNtA9>T(__mA%wsQzt|Ol{%myV+0-#Oy z(&^+_ABGniVEp%LZ53PZH2$Hd@mf9S>~p3&Q?BVho^ncYBFR3`GpEM($MpE5{U@h(bHlV{=#`T=1o>F*Tio$V)t zUvgfI{m?dUydYT4L`;m@2^EH>amVdlCn4*vGEYQNCR&vTgR>=0E5nRvUkA&26J>PB-vbkKJ3W8lERfh)K z3Zn4-DJen9?Bex!gI@tT^CLQ0og6#9`3)XA2w`%$6x_-b^=&FfRpn>!eNod9+-=-5mLS*$T$s@T>_xeQNi?Tc?o46 zzeIW!m*n;!cSEXd8Ux9fG!#vmV;mUei~mrtR1Qu2iI5*oiMA`m_&l;~x8~uH=+LP# ziHsb~qFBm)F>XICzD4rv&U!-PycSWELt12BsFkR*AWl4{CPpNA7Mwfq5>tdF1dGxk zy6Uj&&y~nAOqd3}!~}0Ut@y|S_zJQAN=$#ru%v6W)O5_AE2#0kG_C0udNq9`VU5;w zHI$mRjHz!(xbwAc-{@I26wy5?F{Ya1B0afG1l~E-yKA5Za9P_Es%7uMKyfci<_MqS z$lS-7PmGKlto^n)kwCRdzbVhJ1f|bBrXQ=MgR01>h@da3kxq%x6UlOR)>R9Xq06THnV4~ zZi;3;A$`nL%w8^zm}6~Tz0J{_osQI19G;uNPMl8qZbh-A>mn&Rf96>4oIS&Zv*FU0 z8Q+%^#yg1B<)!D?Y4(jzB<{)Vd<~9^?b`k-4{|vyEfQ68y~FLtX7=&gZt=Yh`oYB9 zyoRw#ZRFQpr}{ckvvZE2QxI^(l(|F=mwlN7zluH}ey^;ItSp@3h~Z-zREM7laBx}XXYXU%p8j4I9b%o^R1rj*AcaM^d|?7-rsO% z|IX;PqLq1}z6#y4c`RE;tymnfcwSfov%nxhgpqRsIVYOE0ev0lbfE_GB(79AmAwW$ zm3<4y)JUhsh?Y6L&mNAbI1|_OM2RR+~PIpWc&=6}PDonQrD zF*`D@cnp36C(z5ys&=GCF@cTjO}&oU%AbW%*V7zBo6rAppIc?TUjqoyg-av0u`M=N z(H`|&>WZD{UcA{)fOxpD5PXDzXw(ANl_c7$oxh*x#-nz$uV!ny;ls?&*gYktJxa&{ z0oA>0025r4G#E7x?fl=JlAd%_J>^%vGL`$IRClNvE@o;govZgWagft#aTO1%KiEc2 zyn;P-CmUB3yy|WhwW7+g$yB%qCdROL-0RcId3ko@9fy81duawVv zq~w!rvv7xhG;v6xEvFVPY7n7vEuU&x`PqC>#$)3!o@5Z!AW$93y->62 zA$X2Bh75Z_sGZvEHSYAwkTOIkL-2T-1&kJ_*T-j+mrvDKH4hpq^S=tc|CIg!SG zCw0~R>f$$c|5)OpO3%I;XJ29^p+2=m*{8k;)yy>t>lJ2UM#3wGPq`n+%g@))X2p$(V}>lOP$MK{z8^(5IXDCdAZK|N`>swYIfY*W)1}ovR3?6moiZL z$A5qlzC$O_)ZH)#EAeVNU1jZH7KuvRgVPPKW-gRlRh#T+d1|W_ zQ7s`~5m$5kA^^urrTBYt@x#GMPSJB31C63Z7e6kOm9i-P$ZnQL%qxIZ!K7 z&oHvip1DZdEmG&|2S%`=ONTA0-d&V>wPdc=lDS$-=2r1#P9Rvzs$EX?XRvzPUws_H z(Q(0j;(vg9PJNnXsD0IEcR%$R|C)+_+t8eA_0HzroaWS%#h<&Vb8cR9L@aBNlG=~9 zm2fPfN{$LxFkLeO)|cz7WqIFq zuviP1^%7n2#~~!q-s#(=J?E?| z6f9Oy?m3o6biJ!S!Us3ZyOQwG5n;bvk(_T4MHrYXQlwXEmCob*2m(VMf}Sf*?;!gu z3HIgUu|j&P_qx${s0Z#PyTQ$w;=)~Px>E)2eCY2nVHXEdKHA2H_3Cy}j9fe*=V-nz z2=$W#QzIrjSKODSYwThwaFoH~bK39}{a5rI> zs=zoL$!8zHiEF<6t6aQmr4)P=Vy1B2%?R4{oIQ)p)DsR_NakImb49S}B)-M%3ccx? zL3;;tY)Hu$DC#8dHEv`1dSdE)DD%=kODvGKAsVEb+ujvpcD=BV`5@d7t#(JtRxS=-wBVwa7k(+to89x4$77UTm1UPb(&a`?4ewocN#k*885< zyjK^G^XnJ6zacxeayBHL>Jc{Uy%F_?3LwO@HzIF^Hf3~OP3N;2{OKclEAcpF3FBcF zD_kAut1S@co$QqTLSCHsCt?iY3t2F&QjQ_l$T^sMBZrP3*WmbL1;zx{q&m`#LWel6Y>P@!INEQTO@!&aQzbQy3;+;L+20t(c2`-`f-UOw=Da zkt-ldOsI)=+H!snQpDQ3L&K5I*er+FjvPd-T&Fpeo(`u6S`@0qMCp0g*KZAIdEz_y zd$5qYMQ~An3>LH+GMVpm5`ylOnZHqhT!B_NCx2s0R9;d3dM)dYRF>DyMPRJ&?u-c^ zrC#pz2oJB(Ti8mSREmOcY-L1Z8nL$SL&YEc2Mtww=3c!kj+*TROM7I`ihQ;6w|n`+ zw~ADV;BVi`c{P=Na@m__<&0r8$k%JnBbTWnzvM1qmXl+5C(Z?8sd2BJ z3PYJG?mWc2ihI=z?BL|%qV#z|7Lkc9e%1l>PeX!!%ijuiGBZEcWc?!d%BlZfUBAJt zm(@knX^Z`du3HjY>VOw{aPFeU@z;M|+|+0(=mJSWr&++dZer)$TCg!X=T4U&Ywl$E ztGfCx2-NiEpH&zg-Cfh`(vg3a*GFW!5A*DJY32u8H2?kw{>q=8+^zozy5{3>y?4X8 z+^cyFANgt}#^YdF+8&63htP6A3>>5xxG6_st|l5UJBHE zF2+{9M{-)L2g(nAyVBFF|Cv4*$l^tPd3FEdWy0mxlT3}(J-3RY5WT6*aH}Q86jW5( zszOboOdX)DHo2?MCxozMnfKeN;G5*C^_!dVosY>Qr-7nP+=r%#tsvRarpyO@N?%fM zvZQjXQzSK9nnat#-l}ODbCR#lymDrmD_HUAXV4v$bjpsb=@^GILQ5& zMp|ZiE?%eSqN7SBWCzsSrUR=|tyU#FE%aGN=?d3 zNmQ(3ANWA&c`i7VJI&Xi!B`CWrGj;!I%mNogVr=ZXQ}G3RP{MaMRF}rEj_ek>L=@) znzZMyr%$xFM=Lt07i!{vnlcw?l}WxLX2Xd+TwQ?WZuW%OtF3vXQJ#*pZZ10h3(_l{2(pUY=wwL9p8{|wMsK3 zW5-q@<7Q+$=?mqXs)DTSVF<5L-4hWYXKB{||C4ieY>ruxtS#-Oe!24C=kJL-qH#Q94 zP~Z5HvT#AksFI<+VZKr@^A9%)N{$bo5I%*IkOkF7ID8WC`MAIH$YxZbel(0h5ndZc zk^D&WV41I=BpjCBK8m3s8dTvaWz$($4R#?LM%Z~nFL_h!^PN&AJ%)@mPANMIkR=m% zV1KH@cWAMGRa&TOhE9NO!x$%+AEzu2EgT*aE)EOK@*FOO0=XiOOTNu;2O|(PjDyO2 zd5|Llo`N|MIx0C+IMS(A5Jv$q2&oQrymyQF0Y*EO4xMA1Ayof^g*HL0stoY81ioXB zgna^0Xs%K$JftuO)iB0Q^%SZpsK$c(c$(!36C5z%JQz-~D&&-uCOVB(VUh!ef*-CO zcBBL7(Bdk@aCq1!7)~xUYWO)KjHNtss(L=k!9@X?a-?r&@j%pTywr$x)eRC@N9QS$ zUA1HKWJqzU0~V%A@z^7cJYWsOFs9|{%Y!{GPn2|=9`-fxGb4|sPPGu&${GeO56dy7S;9Q&Jv(13OsV%^z}q>4 z9fXF$@Tia?jpl}#uJXq>=ee&9n}89Pwi=H z`hn-^9x+hANU#-fLWQ8RSh@>xOB|+%ylA*|H1#gAXJ~w-eS;T(VJvfog_SdlMf1;; zEsW)3`RA-WM*5Yp_3IcV-e7`!w;zwq+5*61j#M?qX*cO#|B(mt{>3Sj3Iavb&fv!v zT+ViOfxqb4qg3T*Go*4*pOpNCM>WtsQ24b=W6X@gn@*!LSX6cjLp`<(3pf2sK=LnL z%HxcS<#8H0hr%1aEssqcWi7l>hVtJ(kH{X-C`|vAwgrL0$8i+?-WqCdzKoi}K#{-j2!31S{h)wJ(*&aQ=A+so=x!(-!#He|F|ikuXB#9 zsM=Snic>?qLiz-UqUoUw5-d8*Db|LrUPy7WZ@Z$mE;Jp%7ESTN5J1fdwIKYW8s7p{ zoEvHZWYN*S*$VQ!&>sm7il+JG8@m2+Cx`A75@z~jN$VfCAau+uiYNO%Q^hkvsc{rf zaf-`B$IIJOo#MHnSyG(u6fX#!EX4)B@v85Ip*N19c$$Or#i6UIE?VSUuExE@7#tZ+ z`TpSCX*kHDhlLH{x9D2*h~|h9{>R~z9@Pv9ge!zyty;oCv_k$$M^QjDp;#0|$QklJ zLrAUYgsQ#Rtv!_5ODU8{+oFI1^L=Jz@N7l+!Z|!%TERR2y{J-X;Xi>BteVI_p>MYd zYMW1{`f900!NR{hozgW*X~zYCx0NOlMd@oimFE88)h;TA27j{5FfJH8d3yj*(->^< z5h(|hFnsV)T6Dp1BU51T)VtNY;_#>AC>{5xDwT$3Vo3&1?^LDo@DYbmIIb0N?G+(xl{NtvEpGA)bpFUXF zFm8JI`w>dZe+vHoadqLpVsr+drAsG=y9AfBb!k!fUoyfs{-B^NH-^Q&VN4F)cqNPs zUkI$w8fRXHXEFmqmM#UtAAwTnyN*P|27CzFx>Ou4!D@tV(xuXHBRUdF>r#36J&Z}{ zW?dQ)9*U_9-J(mC;TXytYSyKy@XK&B^aCxX>hNCV9a<|Y;U6~<$%uIf8Yd7-g%5dK zki7%egePdLVT4yIu@HYEHpEDcZ8fP>+|(sGh?@{cPn>p(Tbhl%M6_zw1uD=m`) zCE>$$#TY6W>^f* zh>9&^DBj@95l~t26wYMG_jHYaw0~S>#a&=Fq{V4dDK)DR!;qgiHKU|vmms{(sTnCX z@vea)SMBZ=1!+(1U2yHI7k|PIg$5}yM6LCtfD{>^dD4Oa?#oRhQ~m1Nuw*4 z)(T2r&530mrHjWao&>|!BeIgOX(1IG{wKkw-8hDFpb1I{ZH%AUPj0xuL==7oH8T>oZoHx}l zCYcxFehxFwXPCpyW5yC*o43*T2s2wpcx~Rpzekzxp$1dTsXW)1E1>9T^Sn8PJ!Ual zJ=MGmz8!0J&mtH$+rjfVGfYr4-8_*tGt9G5=Hty0IDCS+1k7vA#Y_0Bqh|R8!dCNe z=J!nVHSlRQ%Er(q6(mshItXdx(xFrRQL_UT(HxGg0d}Nr%gIS+p zRs-{6!wg_z_88`HCc!6$S%x$}HOx*d%V&o9LclOSH_T@EvX{}(^(LQr`#3&h>ND@B z-*0$Klx;pZOa|v3%zBApc!TD6Q=? zZ-w(W`OL4CkPq{j(}o$w%|7!;1aJ!@9L4c!pZR4N@;&SW^nKrF+R*m{pLrks*80q? zCmTkK&)kE4{m^Ir4%z<5XMPVnf9x~cQ1+kr%o(W7PkrV@DEgVtyp5K(`pj2RqIEv= zENJ+-&y>99Z9a24^YM0{Q68sDu%yI4shF9s3|+)u~n<y6qhXXzadP%91Bu%rh}9bnuP9^EO&|lEw{5& zOaC|tRqv+H@Xt`6lC%BtT;9k87*TSb|Cgv@=uiw$$@%`jf|f|EL3nq8Qw)S2ok#IY zPB9qzCF)c1Wv5siI)zDE@)f68T2U{>3-c6~S8RdWl8f>bmRBf^Xmo0D?d6phUKYcn zIyJcV^2)D#3#aN-;MvQK;XPnn@-_blg8he!4C9QFOZ+<#O=#C4y!b|r6@M3EF3qt* zxK?tRY6&YsgO^gg+<99Z`t~%6-*k$lp}m6rw;W>1Lp36T)`W1GnWVKVA5)yuwe8>L=2ovUN0o~|-M-``sE)p$R;}mO0 zU3?+bTmB=g0U{S)2S(ynk|I+CBJuSB2shIaBA*#YD%Q$ zw{xlagHtm^YUYHf`J+=)EHw`_P;Nl8mKfX-ma%jn^OaoMn$8@q1~y0N~7|!OD;4@o^)!U(x}*mn=0vWYM|1nI9nv# z>C_CCnyba4ZE26o|~9c4`Jm&8yPp8KbMZMtsrc(pw1EEp) z&XTwMSWV_oFm&HYif=npsyOt!aTMS2pRL}OhOQUal67WSd1xbEzvS;uafCJ!-HuhL z3|)phE$MOkR)>Cw`jx!v6eos06TN=VDNYWJoK5k4r#K}vPGlT&q!WtB_sd)ZloGiVLPv z6LD&=mPW<>qp2x%YS2{Lh=vVyYFJYOM|us@HGWo*M#UDQ*^)A+4Hnf19d-&eiBwn9>rvpbRw&{l-s&n+iG=6eF}sj6~Wg214^isc&|q8Vo%shWi#r z1&WQ~r-_kiF8C9jM+8bMR|3#{k3hgM?;$$ynGK6kEVJYYSy7H)B@i&bQz$FStCq@& zat6k)$UK%w7Bq`MHe`nBJJ=j`s;nrJye$Uo&}pv=*x$-5G);KwGk-+`zgZR*uv140 z*onBtLbGPDfIW%%QDi;@JA&qD>O3Xw_&>zFNlb+~0)rPZZ(!(B^C&1CYCbwgR>W(VI%VefP~39!UHVp- zV|gBK$`!bS%*{|g!W@FZFwG>Q8);qz38Ty!W=y5|Q=H;x^HBIa#=Hxsbg+2}F0jgc zY=NwZw*mhUa}+8*&TO15E8_3rOvanT!EJ(B02>cAkAbdWGBK|8aPcSzzdaZdL{5jD~PLmaJ3!I;6rog$?Fn_*Gt%(1D zh*%N-2t8y)ynd`&5r-Poin!ufwIaSGs#e4%{9r}A6>+d4-i}tWBCZ2jR>bq*04rj- z_Q;C(OH6Q9#NRJgE8=6IjTP~5w15@y7W9@C@s+F!SrOm3NUew;qLLMH6T`A19tVP~ zh>rp$E8=2A#ftcUp^O#rH2`BpyoBzoh<^=ctcc~aRji1kjKGR`G%dTx+AwEW5m&%R zR>VIzMy-h7LlamLkL8CI@nJ}e74g`GYDIiA#()*^yNH(+@i=sV74b`mlNIrW;K_>k z9u$%l@p$;liuiQ&ofYv=q{)hSEzDv?`~Y%hMf?zo&5C$F++{^P0hCw~FQXqT;wQn3 z74fmigcb2u0%}Ekvd|A0(Z#DAoc74b|M!isn!tYbx7h-R=N zJ|7xb5g$24t%&~z^8K+s;_pmQE8_1Q zrdGr!ht-O>6}4eS+ynBgh})R}tcdqA9xLJ#7@ZaI=clO^@i#%96>%R%{C1Y!!}<1< z&%6OBzwnvAML+KZYY4jwJeiKa^qH%eJ9qocPDK2_K2!Fj*89vgOt)Xrk9qQIpE(MC z{>EpnE;EdKAZ4s!{MKil1`WUSnK$$Ed!Jdyth<*HX!!@9`2c*m4+PP{KVqL?$o)Pu zi2NS#nSMyw01}vu2Yu#Kpu5p$ejhnJgg7AOVV^mK8SseDtSL5(M}6kA=o!?!aX$_{gK2w@YhmL0B30hLKD zoBWv}VM#E&7L3Y{I9rv9M}Ol>R~ltU>QZU=BDh+1lrEKrcR@ng6kQq-mW5eajV@J& zS4+#Ib*U=63cAXU(WUC}lc;CeR9%`Fo{x1bJ3+Pu{NpBv_rUnFT8-J1u))+UJ5iUW zhTCL>x?e($>_Z$RBh){sO0}b7U;3(17JXZl>cWr1z_L?6QKdPfW0zfSlr7ZbogDrL zEGs)rmllM_36#@yX;D~~Q)P>E=?vpw-)%rBmElXr!;ex`l(+bG@m@s%;jP}`5kz!@ zGSsrvY4w}jdqFJ^z=9Q>w0`>dBw#P z&0|pz!)(PJlMGu#S9AWM;zQq1;<|Kefmnj>hOA2`y<|B;aGh=9!pH~%MUp|S- zKVeJ_(|4r2`Ww!{Z>||C&@M&10rOIYQsG=d>DuE3r9%`-Lr)a9{tLXwVDo2)K5U-L zR4q1NLr6o+@i?^-Q*NF{%ps6dYCeWq4K){o;V^Tph}A5kZ@KyUNO9}m1n1%AU}pJ2 z=0BljgehByruj##&Pa3K(c;!$86s|dBoZ5Kc7yF0^O`fntw(rUWgZK?W6kTZD2JG@ zLe@C*XfUZZZ=?Nq^M>K#*5k~%L(NNhJJFmoQQZ0ku;nmwD)=96?wBQReI1k@VYV^_ zk2Dk19A)0WMBMrmSXX0~GUCzZeVC|Y%o9%)w{Fi6x84G;rkO9$@;GxPCSurd>M|-G=B)3Rvt?xZv8x@idzrWD!2Y! z#En}ILL6@WUU0yzKZ+XT*2jYciSBwd6SqDHso>VHL7{Q$GZ_!Jz5|1fTTh`?xb+=} zDYt$W_J``xNAYTQ?9JZoQca zgj-LbJS4ggMFzO_d3DOIPpDUJeJ$wX*1yIGxb?BT!>tcP_PF(b!ED@m3Eal5+vUow zkA!I4`b!LiTQ3C(-1xUps z-1-qz;?}=I_<>tr3@32wm%vZl`j@MfTYnMpljwc{mBOtTAP(I6QA|eM`hCcVME4^| z1-Je&6yeslpdq;R;UGw&djU;Ibbq@a4`v;X0H z?=#4yC?YUA#>Amn=@3O^kRmE5ilCw<#vlwuX@MC88wyxbb|c2kCfUT2vYP^$UeF|_ ztD9n)nz|{PzPkoZVv5QCd(Lz3FuK`&e=i^IoO7OXp7WgNob!}>=gwW|G^X{#;E8Gd z1yGpQAB2`Lt^bIUnATI^HJH|)hY*<7XJ9ljt$>F|8{wDa@Ml;UbtdpM~l$Ykq}s z$E;a|QNgTvFNX1DC=#u|qS`)%DZYwMC&Rq4&Ox(BR9iU|`8rlF^I+bp?Pd)Bn^>Co zz`RwPEe__5TN4=R4Vo=96eFhDK0wDhG~0F1Zl`9e!OXu=vkiquZ_;d2(TB~N?Jw|v zEt>6LaLTJS+cpS)jb@_<z_2+Y6Q0%HQRJp)}J-o^)Q&5G@DNWhDx&q`NP0;+Zi;p zLASkzzPIbP$w=(bZTSG5x@{4_M%`8gut~SA1lX+GHUVtWZCwZgSL?Quc@S5(JqYSr z-S#ZNb-L{hfIsNAPXPX?+xh^mM_cBR0!|+fX#ih=o;L&TnF@ITFTprp4fu})NCX%d43Pkbq26_X zXVLB-0IL%r72t~z5DPE?-mn!g9(wEo900@I2KXd&egoh*4Ec6IU*!J@a4ULzBVZwH z_0NEB!ijGJY()sV8L$`u<`zI7#LT|{-i!8c1>80oUI0kv$2$P$!ZmjSUWVb{1=tCG zy8(Yj{o4VrK)>$*9D`B26L3F_`!2v7$oE&kbL04yLl2g0WT zgXX}g0XN3Ls{ubpxmN(!L!Yk#{tP|72Dk=#Jpya2o(Mi;9IbRj{zqlsC)w02*3Cg@Br-S1Rx#uoCJ)+xP1nwAW(b`_#pDX08GYs zeF^wH>U{;+igEiIaPv@1YJhWKC;tRog>m>7U^?vj-+*tz&QAf3o`RVTa0Kk55Aaru z_i4a5@H+$eI{Nt?;Pa64d%*S3%MXA{pue+#UqN3#0^R}oC%{*rr=I~IMgM*QT#o#6 zfd5AQUjf~)i{AkM1^-!(fZ2h5Z2;hALVg{KtBL7^2<_ zWoX?tZwN7d1|3&zqcf=XOW-7IFGB@Bwu8a6inhK=r7M3L7rrOpdp)Ey&jEeQ!I^+(w zSVyYQQn6eJtJvPbSYuy`DMYhX!k>g~8Zs@m8{iv0iuLAPR2;2tmo;P5Z>i>Yuv^8} zil~dNEPO??oq}iK?OfJ>!_%!v>Z>SaeF1`6(|KU5V^PYQ&v@vYu-*~Y0`;Ns=pvoh zT4ys(hr3PCzqLrE-5T9Zpu4Zu`39-`9fbW_7aC6;2KqTNL0)E%gZZS@dWGr-wz#hu z2IVN$Qf`t@y@!SML9^C!BL(Ny!@~XngR@pL2g@a>MQ6ZasBc|L8PzOSXnrJgYkggf z#b8Kz-(Z~Ny~mDnZ?jfN-r)#P*5e*|by$$~J%bGNYXu|ghpK!^ZLr^TD*UmLOK0-5 zrMBk4EUce$1EKq|CQ7k>pt51B$%+ z-i`Xa`yQ-VKZh+^!!=TH=tEXKYhfLweII9Pdo<%7ZI3hhg69AYZO0lZFeXE{2}TNQ zy9{it$wmrmn+aF^4KP6f&?PcgbYSoSg7=v0*KW3EAt@f)6q=4NO+ zSeeiO`eU8VZQ&v0i`>=aa4my#iuAPk2AS%YN1~d~Ii&looeJ_YBRA7;DLLL12CJ!l zzp!g*Pq3%W@cSN`wU!$sJ!e4&Z`Nb*VQU3zFmyR4t|;pY?Ri8d=|VM(dsJI*D2Y|e zM%rkkuxeRtZka-UYVkWtzSN>oAcNt^&aL*Sjl;+~gB&b7XFf6zDm&L{37RLMoPb1n)mzr-O{+b zFWr*E+G838dveRG=b(@KJlg#d%Pi~D9_{`>p7xwUhWc%#(D0HmGQ<4V1%W)Qk<*cO zk6t5PPIt8Uj@aZBSvnN-y1Mp>zhXI7{3Rx{;(d^&aoIVaMUEw$F<9#cVEj< zum~;Ahf`atEVt57@LW>OIEF&ThvobzFj-7DiMhfey@MXzDJ6F~9fpruu7jCzt>q~s z+K!G=6glB{Ij5zwRWih3UgdQz^wZl>7 zQOm`sP6NjCP_MxOHyu~e%(vgN9ofE?vG@$76+x8sO-no`A=$UL7^l9`lP=a{7FtUX zZ|=;yMrU-tu~-;bKd{iMhGKLUbY=b6f@K0oBSM|9$S7>Y=+6y7hRKlhPwomC1BaDw z4U+V73q-Tdq&eXef+aE2LA`4qwd;@>vC;!w^$-Yk^NRrffM-vwi-FTBI8`&LX2W#w~a*>do^> zL{VSMk0_*{K^O>Bm((F8;BiC<^$MvuCEyQeLtQE<3qPu_UP;AZ^r$=$m|lR%Nmt8n z1Ag%eXRD$*&C0ZzRE>wtEsFjy0)41jbBbD_(4p263JC-53jtL};T?l_adml%qSlk@ z(8|R$jj9cD4HpB91(pD@t+S(s?H9P2YI}xu4sdi>o_a;#WMqezO$UBa0Iy+{ zhmjIds;I*Q=xZtw%SWc%ZSY(3-LoZ$$NaGP%r>F-9 zl75x&2jZ|POw&}lk0EX%`J9c7O4uZgc6-XGupn^SEIaoQaz}&7CPL8tCjbT!8t#u3 zr8>aqPSrYLCebm<=CU@NnG^Ti1JBnWTk=RdND{#Dl5f6m$D-u9xKW52-s>_Agv~< zK&Lc1VY%gjWJeF;QZ7~RAb+q0tEWJHhwD9D6DGsC)Sp!aa$Snc7uU0BZsN&lNdJla zA{j~45oHn-@hiKf+l5;+>R_a*4+X24D6k6GTwLFv?qqt1T758>BS9B#;HcEEdsw6E zQHFkPY%Q)x7`FpF?yQq|%@8RYLAQ)wm_`|?L-5VS;1$fM*_(-Levt|NIN13b=AWk5u zTaX-A4l1hwA2%Z@ZViyQE%>0n#3@6;X@U$^nP_wYrtHU1>>6qqaqCi!Tc08&39(C3 z8p=`pn&^pNsf?w#kT{9sS2&8KPz;mg6e1hp69J3SC_Rd#B+jN`Tq0Y(60Kg3s|z{L z8!cbXEz`pm)Uu>bbInijsh;uY0osaMr*YA5C)?Ad%%}Y+*3L%?)s)maP$ctr{$|Ym zo-vZ@2Y-_4Zz!Q8PKRPt#R%T8pLkp^AZM|``#0wOt-)JTqftgl?2155UDixM%1yYI z;Cj@k>C64O8Yv`|q#guCQu%o_=`S@2sRCG6@1cZ}ScgwFRPx>h{54!Z;yPvU4q@KW zm@Gf*8zczQe}EA9V&ZOOhC#76(2Dxp5cm0;tyDM zt2Yf&X`)e()`@G3j>AsKkW+%wMfJ~vC~qFplA2u5)1L>C>o$T;UW5{-NGkblj0tcuvp(b`^BnmL&ynM3eM-}wdTt;sHJ1@x=E7p; z*MSY7hX;V>=<(Y?iXK-G&5Ip;nE?$yPc%>8>L7|JXF*SWz6k9(2fYWOvuWO6NO~88 zMxs+Osi0H0klLpLi<^y)ti|}qM$fa#fjmV>9gs^%-%9R5l%>a>Q!vL5V@1=+e+uSt z+n{I^_#3F?QHXx(@Imx!$$Oxu#X*dnxRQCoO&dfy8###hO`~5kIzU?BtX9sVuLL1Z z6^#IwuX(<_A5sW#+J>B`(Yk|m@D(ZdDI~>1x!(|>Ojt4pmA0vasW7hhkvk+46)G@T zT`wU*(<|K_%iI+p$t*?@S>uHKT_pZgkYoQu;@?0S9_mNt|YB7be1Rq{A`;RN}0j#YgmGNx*&#pcPP5EyBI}GdCOc+jQW+NKQ|aD%{(;02EmYc(x-&o}hUzR7iDs@ln5%4U2e(GyXqSN{dQkLx zH#bVlyxRj*c#ksU3R-fu;;kM}fL{cus)bb*L27D|^8P&&WmW}HiAYw@T9z{ELyEH! zC)p(yD;0H(m!c$&%?Bx&?hf%ep|6rBhJryV7A+XAMvTwJgJHxu#*j@6q#?^gQqC2* zC^wO-SA(YRO=60gO$#Kq%BJP$7b?n44IG~hx48$jlB#3UOQEjJU?skV+S#PJRHUl~ zftyh>-w9d?MwP{su@E^k8-QtDQ?u3prXVY83y=kbYzNW;1Of8KOx)iiJ~IOI?*@J? zl2gAxLe|5ea)tmo0Aw{GF9UgukmEp31DW*+kZdxOF;I#+EHD85jr?mvL@nV4X7-7iNJDiJ+!w!97+YWPBkrk z1Fr(}kj8$oft6ehQpTtbR^~RMq2x|h@;;_uh?0ECicDG-Yz(9?@x0F@_F$U=sg+e2 z(t=Y!)Xjk*2=$`ti*?BtA~vx8AS2(X{05gD|-gfqV-pzAod=fKrgX@;z@5WN9hdEIRg;Y)xCq7pqN`g zCl5d{Qy<{DsF&!Li$Fg(h~~QEM4!Mctv)n}+8sWe>_Sl==F;ziiW+1=uA~cAj|Tq8 zAX1~~dfz>VL$-&mO@Xo=WtrpAL<++BV}qW96m_7I$48*<e?8uA^t z;AS;iNxo$^TD+76Y)6>_-iS^JGL+&>J&S^J>z*D&$3k-McLb3+(-Sc%%M~>vC;>df z;VuX(bSyB8940Y{H=C)n5WQf-nME5;`c^jnd@U-F#GwcZ>bW4cpHr}%yf{T!hm21# zj$|)C2hnVKFH&*}U|yiH=~O-hEiL93mf;-bv&H-pL>4n*B)Y^)wqJv2$%ffBnT_$c zATq{u%1)gHcFJI)HFs6=iwi)igUO!g2@bLXjWbt+irR}Mjw<+R&S^Kn$=<=0;;My! z5nSj_6hd#>a!@R5F!!bqJ)t$+zmWCE8IYGAXjRks;nU%E$ScSc989MX&Hc+5O#LeZ zE&DfRFzL91^0|MRgQry6j z+b(Wf>$0Hom_k%;kd-r0aW1Z#QMuDox&Hjh^`6RkbOfhGoeJ^LC74;jW!`IXD^0I4d!--MnR;qddM-vkV8+x zBhPAxKOHgMf!w5~#xg|>^`{8)Ea)8irjZ)PbOl78yw(@Am1(VO*klEMs}42D5jpe? zbaj|NK9wSvVGgg6ZT`DZiJnuLQ&EeV@*;ndQ|nq7#r+!L|0Bpbyz;!*pGI4_UtX7t zF~R7wK6apL!ThP9M>5T`A~b8~cE^pzK=Wx}I5*q|I`>K+JdFjmDP`zh0++iD=>=Oc zL#m1X(uR(&BMVDpRrMh^`4d0nCUG01#-K7@M58AA(?s4tB(J(tSaThqr~M3r9F4h% z=l>=CH2=SXbTq#e&F`n?d292KKZUmuV?opO;ZLqt2udk@4;+?F!p<6(y37A4s>FPQ zG$oUc`yK}u^&bBiKeS;?nxrb8BZCm>$R5(vr!|xc4OZ`m5e%OUdj;oFaE)R*6r>HZ z8WxNrTq}?@G9aq%0;~qGRbCauXMP+ZR&fN3;Q4YjN55!}468ZvMPi4ymP^xeSz=Kf z3DiQsZ-Kevfz&A+zw_M=u5~sb5+9C0WXra+5@p71{x>4dB5jRPkL+cg} zt+dpTSk%-!l)jo%qd3@JBXN$j*9K9f9bbVCM$zqC^&w^z8?zY7h@k_Tm~4E+##P{R z{4^B%zno;!5g141SGg%fl*FFF%A*u{Z{TuVm zL}ewDT;WROsRswgECwDkn?ADXgRCcYEAq1F$*L<*JgWi7HH54J@*N?YfP}{Z*#?9r z->e-#+6cK9$R0u-1@ZwQ&jJaAuV=jqWHKS|0$C0u?lT}+r|@wjCI14%g*cF<7bwau zAi26Pw1mOPvLWR)q+}+bX9-A!4PRissWXtwCY(*{qXsH8MV)}!a*ecwvguGhiw@=g z31)mS&+DXsL{iuMUgTbz0cmil>8kVsWTaB8j;n+W{O4;SGoGS;PVV~KV3q8>0k(cM zt`uOOr-BYyrQ=a9!CwiUO8hSOO8k)Ue#E?oUzbN#w?=Q^1rjt!Pb?WkJDHS zwM93+p~#1crpFT0vlf~Q=pkqFsvr6O`bnZnS0Eru`YdQA@7!nksPj5tia=P{~Uo!R8GM-6VYwbPD(3 zP3{9N9a3B^(AQhs$A5uV5(@{SLX<_GMWfvZ^I_BI@tR`dP4^eW`A$4Nh%04@U|DV= znl%!^8lkV2O4%YFc+Ad>8026vFYuPQq@g_+(?G}N4FNkFx4sBY?UFpY%ksmr*}DXv5l z{SEmAtgbTVrWQ(G<;*Jso@(fO)MV{rg_iicZoMcQEqmUCYeGUu@# z_fuuwIWJJ@nDivkJdPz?*G54s(GMFS^>tO3&$Vr|D&C!Pah)NrFCz5jL zOLU+=K)n{C>8Un@z819HroX|BC-bW8O=i0Tc{tdIfvI?%8#QzQja&+Mr{{wk(2x{! z9gF!P(h9hC8<*8^yDBk&4C-Tf!!8pQ=g-DjHVS@<%5nkt5f>hVH4RJs5lcM-q?GCt zmP*bDpQ=<%bbYgw))k+s6kn1r8iW>3sGS&Zdg@x94xB+bd0Y^rBvyh@Gc@(S`S3in ze?5Z7EhtKK4o{fr8hP!DNXxm$j=~Op(C8=7vV&9jMGbW4iDsKjE}aERij}2308XOo z7e0N-=CVtXTM$A)Cr6`pX!ExKhNw>EC!e-ZWj6m@erSuP+!`{EX&PAv_JRmE6e;-m zz-PdK*KuXaj5~p=w^>wm+ye8E=2k8l{RNHFt?Vy!8nc5fmQMM0vX4aZNs+`O`M6;h zKLtaolvorm-*{pYgbkXm+S*exBqJ(3zyvQ*du}xlhb{z++y+N2;zP zT7M4gH|qIK{9%Grw)(oXOI(#~t3a_DUhpvhVPO*HRog9j`I)1WD!r=V?h$N<{+#)B@{ z4K`}%0J^;`x~^+W_QQry4P)+ekS{xG<@zn4=kQn!9YA9x-22xiKLE2fj(Bzx6MSZJ(( zNvV(fv9%{)e*1k89@={Uv62b-y2t?l#aVw1a+<$-jb}mUubNw{azZ0|x3b=5r7kw5;le zC8||YMmyx2S_&DEw*t&a#!7DG;v6YsCChj-C@Ew01u`yY-mf8F%D94S{|Y+l9g?wz zX(?|l3rNR&EN>l?*MppP$5KoRxTL&)VxEs90}c^MJ(%LlDlLSlZ#glmBI|EZZ_Wq9 zkeT62MmP*h77qOxzLeDgGUr2@+%kMgOLu@SxON8UY+qB$1#gT2onz9glhYBP)TzE? zJ-XW*XGG%E^{v1Q17I5BmD9aj~&Ez8>r~YjOviJCw zJIQs(_3raMvJ7}FW=Hid-_>R4v#*8hClTLN$1N;PrFrfnl#i*z{t=o;g@MS)(@!G} z&O%y_4>jwjkqXy?ma}I7Pe#%J0yU|=Z`P*J@?fAwZR|qPD4s$G@hg&2*XyP)jnItQ zb_wncj3iMe>Z-aIZAbGgKS8IqBj64bbaIDidJh_Kl2%SIsXCR8no9w0l8#l5615x= z&cGupVESqL0V;Bn1<8|TRT3^;C*kDmM+M|u9s5fC z#gf-z_|zuGKczf15VT9Dcg98W3QOWL61lnWqHFuSf~6OsTr>BGra7L7T6D5aU#tR? zzo&TK%F3KX^e6BUbv3JN1<|8OT9fE5VDi+j1PwG)!hR*Hll++_&nS7NEssG?H`4g(- zo<-sY6qhmlU#z2NkRfBZr2he0#_)f0{w1>@7f&Fkm{z8(uSMX)C1;3Fbz_ErNQukw z-9TI~QX6C&F@7}kgC7r%magsH zZCNg0FQQJ?dLW5#v8?NWbP@7rAWsr<2aqp;;4e*erh%=Wt|q{uCN(Nb7#55-!K!lD zM0K4)Ko-&pID+}JhBbGK9Mu3G)ly`qRO7~JAdh()$T{^`466eT8*n8*b}3pJ#HRER zvX#WfI3zqFgJmX~J=X-eku&~EBRD?pOCHgOBznZn2p$Zpw6;xjc^~e$a?z`URAf=`_ofgvgvi&jWtPplfo5t8C^XbX7XIP@_U4b! z$i!BB8x>h?m^E_l(~$WBFOS|pnp`fuFo5EmKcWt``~ok2786zG#!~Zz0aWvD&{7*O z4Uo?A*4jCU1_uYwK3?mZms~g!tPe5kvnVX*y2HHqm|O(Q5WuT+xMSy;J zKs1Do`WQx~zQSdvjan&XPFV(F0$B|^sDAVWlo`nMOQ0#P)38lZ2aQL@PTAp1bT)St z)}knJ(K55cJ6Ng_v@_%t#SZRpI%w+f4({;fL~)0AaEG^nmL1+@boe-Tc(>8vg;8&k zK(}*c+1Wd|15cr%lK2Q2Qiojd7eb(i*Wn%)a*km}%4waC%nd#yzW+Ql3q5Y&1^&gL za(EHc&I^18(Y%Ch=e7J*pp$zjs&+E{H=;QrY-IWc&~mQY#I%f5n|W*TIhCy$in?2T zXs-E%=wBhLK_@_{-1TtyK!_;A(jI0q6&W%tNxB8J3`=`CzZ2Nn$|@}Zi|w@=~rn6AA!q{ zxNZlh6&_CK*bEF#=hzB7oX)Wk5U0e4LcwUOJU39h-);`UxpH zZ<9Y<&;CCN+X!jIU8=d^1Na@A0pg{ywqK=2bwSLnWd~kJ!ldPf$J|18m}B0NUsz-#!EN zC0z(wNqmbU-~$>TvTTJULpyNzf}B2&H1{*NTahMPdyre(%eCuLQ2U^!l00_QEbqk4 zI^=Avfb6{YdyyBB|3X?0pIE%eCl>U0Mh^YlsQME3Er#gt93Gl>9kR7U+}a&Pvu+Nv zG@pQ$d(FQye+2tp%=XnNf7G?)I6a=9yK1RcKkV(ybGqVEL7ktEP)dOQWZhh@|EquEWH z5$BP0qtWz3%xp7KWYZ6EQ%@63Pdcd&@jDd%0b2I!5zbFtB1L(WYcBvLMR|-xX(O7o z{y2+rFK8wFNf@B&BiP>5;3}+VS&$PYe1PeD7!3Q@MZYX-*aMZGhXmE()o$&xc z-%5)5Asgwwf?RsM24*qpB;1pV^T#LPd6bg)F$IoEQVCn3fRO9(h5`tcQ7!eK%H8-4 zDbg5HS&l7N$WEql?%kl0^Duv@lUcHJprwzdb7|>t4k3@pwzSD3i45+YaIbHZF?|Xv zWD?d|GNekn19T>h$m8&9b-jpr8F>Bye7u63n1_MH+>MXaBgoG>4(xlRXPp2t@=B~8 zPo+W&SHtOXsTYai)rLM&&r*5PNimAyV3G<3U5ou5E_JA2HKh)Qb_~U#%oH{CB4pkp zwPlB<5^=3T{pDa=1Z%yU^?}fcva`{EdZ#R#iE{MwN_V3yebIu--r*_BhkSoUGRGfH z8M_!kQC$EBQhdZW1jJ)?y^fZfs5xOg zh&B=h#52=TI8+v1&@%|cSZWbDMF_D&a}C1R3gS9RaBN)*whNU7_rhR@KHA7_E!ZCc z;tQij2>LMeD}%71v7x_6V$myO6}()FXHzuuWh8D}Po(9Fsw$r#Flc!99T7hd8i-FM zg1~=VoD%PDYK*V0E30vrJL8*Ln`A;w^|JWNva)bNG zR!V^;(9c-xW$PP}0ik8LC0bLzth9#eqZm3P5kpTPe9_zbMnfnVEINnH$;ZRgsMO2F z&=aDj@0jio0qsjgI;07R;ZbCpI}!#Hxdb#kuhAt)ejfcuyT(JS4)>#fpW;b~}4M79l%&gkP_y z=oYnFg4*08Y)7@Ip<2{nvAszfqkbh;<=5yfCms77)rTBz$4t?>1Jz#?&Fy+fd{6wg z&-E&8lC`p_GU1ZXF6k88+v1+qcTSl!WrKctvO^CuGm;+|Tam0EtA1M>(_eUKT)U&m zA+CzkXU10P)rW_H9(u8-u}6MOrIPdn|MeM+aums zr{{~g-6B3t%&j=AC#5zom@+9db;eZDk}d-B^}X@UGaa#xhj0A5s9(5iK_=v0m7gtE zrIYw0Tp~FArR6=szx}F}!awdzWm&6uUTI(ccRgM|Df~|8+jlL2Zj6*BuoTyY-&t9)0>{7aS?s%`ot}&eo(tKv`758O}A6xDBUi4ohPc>DiV)X_Ec6@ zi(A|D_PvwZ6FW9II$E`;kdqyFv9Z2m_xSWF?~7G>_qH=Lwb8@G^J-sr<^l0y)mE{8 zXu5d5Do&iWw(FmDc1&*W6oY!j^=;|mTP6LZ_+y((oKcR7pnMUYE|%smZp=9JW~;cU zyIDMi-yu-NlS6grN*k|=*VdiTBQ_q^Gn&)(trWor$F=BD4z0v0R%#ilo&e2ei=c{a zFrp+?43Fz^#Kb$qpl;E)@Uv!z7Bx&n?5I3h;z;-;!#yb@e$t#C5!5Y4RfxrLT_Vcm z5D%@ZSb3F}Vr$5pw>&k$twme)2)*-PB6zEKOzqaII^KM5uXtkJ!9C5QDPIgs7ftPA zV4P@j@n^ai(k=d~>MlKgrm&t6``5MWjp88{1}yGqgQ=|4E>-n-5nLh0rO$k4a~_(q>T%-Sx^#V|9VuF(FTHzGL&5mhz0twTMtHDa?aeAIQ{~l?uPOFN^hN zH2C!9C8*LDyD{UmcvaEcwUiLCN{dn@j8V1J5HSZ@JB`!?{!I0JW^1V`4t)k{PE|DZ zYIQ8x%#)|PMD2x)zz~e;Nd2copBUUL8sbDig>a|CNE%k?hyR#x>#Q5Mh{g&rC{8q{ zi{SjbgufQ8UZL;OGxW%2rSAu4wq*G7kk7ZiPmencBL?6CN-4Bm9-h+c6O3_*OnCcRnQCS2mP zHCx3k5b(1#6~`#*jSkf_dbWI5SyFjYO9<5$=^cAw-OJ$tQ`C;0V~e!uA>yQ_MW~{E ztv*B#kBzU{b8MTwNIWLAbXC7!+`UHc78~)K9%=#nv*gJF@z)V2_7M!$UD`aW-YLrT zh2pI;xYfB~__zw!^McGL8-{cE9T;k!imxk+LM>7icWZk3!=k0a-Q220hi1f7b$sgR z*dxZc#6p;5x^Sh_XMjsf3f(zbERWmug*GWn4AC~K>R~-pcW)NuJH!}mp^EU3{_4iX z8Mjut6Cs!$A%;_%^}5~Z*3!dfEfN8+FX7gEPj*!9)NP5P7+M|JEe@#%`&Jx&7ZF~Y zW)<;p6MsD}Y1!ps?m}(46-w6Ko%&58_F5yysv#}e{=qn_R}MYL9A zP8mNXrs^+KwDF-YitcsoPvbib6UD#^(UQMnirB06Rqv|QCWeYbh@$T)?c%u7r%kkq z+uHOYyR?W9@n{G>eBUuS&nTEN9IKFzH;^}>2tNd_^vad*>0|UiC3eKd$4?e+mk4U#sn6OIvrYf0wDlcrdZ-A)_)Od?ZeH6f z>MKN`Yb9jgxo;0b!kImLwFzOOv0H?}_eHA~ukO+=4MQ0{K6Vk@B9Uy!B{r0Gi)G!H z=>-KMvO5DYD+6Ij{BuOQj^FZe>08-W0c^c{-qp|OD@FbZF(Ix}D0y*<6l4KwUza8G&f-#5VqtDn-wh3bxd;w7QCcf$ZrLe~Mh9fG-Z zS5?)lo}S5$Z)a%}hW8v|WPHdmlz6gj$I~4%DJG8!6Crx{%zdJn#64{ojSm$J)}9}Aw;ukZaCaXU6|kLuw4%lB%Qj)n({puE zmT;fY<7Z*Lu}?JhVYLCES7##yV}`o)F&5fFxm<+!YIV%fsaI>lRxHeD6|eG{AA%^hN_>t#JMEhDBmey=F# z{!G7ro7?G_+$kCAHe5 zP?{RAst`eOm`z2ukDe~AySr-jBD9zvFCJ*q(@&Q?xp7;^?O7A=Si3@B6dPadbfCX@ zAJx@A{(yNaTHQ1c(N7y6(u1*iYn?Vqg)GgEnHa^LDq;i@l6p3Z0&*+AgDB^S#T2_l zKPtxTK*iXd`kn;|X&It=hqy>4XfZa-zK6tPSUl{B$*4LO>!{j~qD_vDL$tz?v$^Xj zccoZWp(Tb^VzTVR)c>dow5u}D;iwevYmls0_*aPLbm(E`HhsGeZ%w%Ds>CO;fbh@X zh}F#^;n&w8ru2!eZF<~h{j-7}u_C=%L@vBsFPt)d@u679isSBWr|-N@KQ5-i2>f-| zvE8B$lggsW@r#7LU9`4qd0_}}6}$D*hxcKij~_dBIyQcVMHA08AGN6BDL=j9vl$tC z^(awt5cV*{K|T&Ie0G4ArS|4vmT@>|!mPg0yPjB7rDtHC8=e*)zb_VJq5n{I=ySmP zogE!mfM8;Sfr(O@ZAa2FzyIo_{0i@xr=_PHlA9%VirXpVYq; zL-d3C6n(j#u)b=!{-9e7-iqbSyIOvjm~cY)9i4Ujm^R+_?)@D!Nkr)3C-qr-MZm#5 zVABnT6~s;)#*NQCuVR!d#jER1U?q=X+l7T3G<^J+_-!qsJ(+h7wor@oVTb{5=uZ8e zrTUb``jVZW>DA(O1%~$^LQs$R1#zO|P7!uckJ=gQsO=EBy_B))K89 za9c!;k+jWtpbei|>d?u00Swe7I*8WS>^v!MQ1xDsMbut|L~W8Pa>zORklcbEAu=x& zcegFX1i6kFJ*Q~nRB?dj;njL41~^DdhVAX>r1>9iDO$UGzK!qE-S>+d+YbID;=AKT zarbWhkTzx*{`KSf9{m;l&$Nr|xLV(bag9)WL}0scVPeE?W1-B^B8C@?UpQsgtYw`& z`T?;rpH}(UBMi(JZv48FRS!QdUR;YA-Va9bjncaat?BmFg{6}nm1&h3Z{tv7a`UGS zJsc+Sr;Uge9X)SXbslrLK|kGzMFQfU?wHxMuhQw*hd`1B8=U3>h!YJbM5$hJ+04mZ zU5>Y^CpT5azwJ1UYOi!w-sV_ztmo~F@{EqZJC8TPjlfIa=f$eaiKx^gK3j*NJ9m~C z3b|Gsecw^8&vc;hW@`A5dzNTMaD8a5z44_oTi&yA*UH|r(oJjjo!-BBQHf*G zneD>=#BC02#l(;k9a^OAT!()ASfN9d_inrmhZR_LT(m>XBg^>$i;2qEt&YtiVr!yU zpbxpm{X{$hZBmD@Vyr3oq+$+PB!0!O#*Y%K7H*le za?yrNOlvi|17W#mqkC3b*GZ_rJu`3HvHf`&?uMM(;zi|AVLM0**f>;*+cN2@>_r>L zWmZwWL$X>S7W7^FXE+X5b?D6Sq`0;k%l9HaM#Fr6Ta4zHd>-HC>Y{7rpQHVu+=uHd>uLvtv)stPdvQ~(X^gD`OY zqhgls0;ik6X`6@Br|^H>%_SGDUcqjMRK^rg<68 z^jy_-mG&lQUAePyiM_V8x@K8@OPW2p$zPdb{3+9r>MXar>g~v%-Hk{e|dVhw9dKGUcroryW)0L#HK3t@pdI=wlZhFGDj(%SCpGO zPniV-->i+XD|S4IZja-?G`ljpwAR^AU6xmeZ(3ECFHxe)lm&#@r#05s+NI<&VO~AT z8(mQr#$B2)NhzFOsLXV>+UMbH)X0pnN7uORIEm#xQ|A1p(n{o_O$84v(79`MeVr2B z1gY`NdL8tolsOw+)fLrcrJOYlNzTTG#_Bp3Dv|1np{LTC*x8UE&7ROgNqJ38ZYVLk zl{pu?m*F&&`y&hBDFA14{R$^~bXjgoLv&XwmqGVSl-w3bXb0mOXBi% zcH&`IW;kmasB8Apx^jDQd_i78F6A^~I9+8`Brj#2pYprK&My+(WKWN7%7{ac>=DsT z5phafT>Sax&?}Xk(z?+uds(Bi)aA6hoV5-0jirsP_6k^xl2czp(vpFdm%2(Zl1eTe z>LRzUoKmYvCygYT9HyD*PTo{QAy9YTR1~q-)w}FG*l{pPBdxx!rWM_5tgNmptpRG} zqe4|_lidw#MjKE!r&qgL_Hp0_k__Ov<5{3a)L2XZ)AXZ8woH@azx zVz<}S*RP;Xm%7Xj+pmm{OT4scw7-&D=aPCrMOg#FgezoBBoc&zFCfVu_W?-L<-q4v zIqf+`vrG+@Hp98dSp1bN6E*W)_4RiA0wi+mxLbiyvh(4(y}k_h7hq|4{S+9MG}hNu zF2xuuWe-p;qv521T%t^`uP?Wg@t3;D&nw_+Y09|ltf}MvBek%x9zxXqN4ov|KPTHb z>3rpQrJ=GR)^IflQ(xwCx?=GH8fR&(VKCflQXbR|<1VX*zFJ)VP)|JFLy-4HVi)qC zQKgzpk!=s-fs%`2qibWM%asQAGBW7sOXDuZXL)>dDggcaD^0(fh0$T7t*LG@*`aK8 zQ+;e|>ZOxn6O~x{%g&viH``8rrWE8B7sDht8KEF=`t01P_VW`9=V#B#%dyYQU1ZOm zH794LQI;D@L-!h5*<*}=>91TC8*A@x!Qf?&ja}j|^KxfT<+i=*+Ii-6+(zBf(#hv&7Q+I%k?4Z|`z9Qp|*|$@N&3W>`fk1qSK-4J*o; zCdSe|Af<`#1T{>AgCXi83O74z>KmNpu~b^-#?sv@Gd@FFe0j0Ph{y5gn^Qw$y{n$S zYmDz*$KhU?A%hXhy#z4&eIX~0*`MDAOWU7EZNg1!Awx~2(o}`_t;!Dd7cqMUbsAb` zZ=xGie1mIgeZx`=5ZT#M+=gp(dC!->Q>G3Bdwvn+G8vA`tD72XN?Yx&DuhpW6G98( z${2Uuin{uhb#`dKp2F`~Of~)&PGJWd880>0?B-tleB|iYKjBJ@qFto7lOmodV6cV8@9}I&C1d`7d3&Z&@jjQ zDUg4b5#K3(qly06S5BUo{EWM}ODml&6j+8x+?dv{BAR0DrInDsiDw9eq!_M>7-`Jb zW1M5~HPxhEz%-hpV_$~wQCHbSgGK|^;B0I{tfJUbj(OkSR7Gx4 zx~#q#CeqKFCRnnS@_J_z8kmO&JZsME>Hjw_UVQRcC&Yl3jclJ)SOgfR^Z!e@l2VSP zY4$mF7@-Q2M-#7lmN}huuu)z`Qa{YHWt?y^Fd-Nu zf;o%tS@p7NXt8DZ4qEi8M{WKW<}!>JJBe~Pe5l@DYOlpwkW7pe4%6*lVAGIb-O^Bx z@ZO5IU|$E2Eo6o6Q-E1jHnBbpub5%K}X3 z=sc}Gj96RlG`B-u^Nz6$k!utu7UW(7@5PCWk-nK9)(rjTabYQAJxp5UIdiFJZ3sKB zE3a`j(s+BxRaWn=Dd&BHY1`**M8eN&n@qC;JCk}SPOd*FWEl~b$G_a{61VX`%lAtr z7h|Se=pWqke5O1=RIFbI{bl+Yc@?em!4`%YiML)=a>-W zKCu={I>c?MB2w%B=(DGip(WaG_RDQ5fZF?goq6j2M-)+Q8Ilot@pK*Ud zQ-}XWJ%;^ze7k=SEB6{z^|c&=jB@7IRc1n1XaF{kBJ3kL{*Zoj-bTf4GRdVijyYCd z3(chv&fB*C!{6d%gpvmiUe0IOQvcrI!kvXQebQBbne(?Krm^!L=a2dZPi6*gQR=IB`K$bDLz^(goQDKRHjBWoQ=bmke_r@5js_e*}+EZpFj*XYo+y zS>UO_t8lG1uEBWvGXM{BUwAbbXuIziUoV!)3KXqKTDrXB>p+W`yG z@LP1a{(!3kS1T@h81*;&sq~GsK#OIIil;*i=MSvL3QXQC0SSN^QcVw0uA$0P5Rcq$T4!FuYOeCc(|WnSr7n?z0r(#(ERCx5RV zy@w7@Vte>a+br^_L9^bj|5A_M$V6}3GW(Hh=*N_Y9;NK`;tP4EkvwMpR^*Qa53_#O zW-*;qVdm4DXX$BLGk@+TLDdyIF8ZSv&9(!Y`H*`?hfnS%?=rhk<{GauXd`EnB?sE< zmxJC?nhjY@KFB?9Jm`g+>5#?D&!*hG4v(E22*-2qh@)mcvd*hdZ|z%z$4Jfm3;Rj0 z;-LqHz4G&kg&i`|AH7gXz$U!%(Fe4GJadffc($H!E;D_gXY4YO9&Dyh9q41)C%s;! z-b{xLlI@y$KZ3m1@o=r#p4lI>F1?;>`G2WPZ;;BvL*Qmz^mQur#gwxl2Tx3U)iu+% zUXX6eazD~Hc$J3@<$2o>z39fhPwyphgO}OHtPAq#)gxhEZ9r!{{$_o8El9kV z{g^VE`CALY+k3p=2jstIKE3cE+pCY}c$)bMm*Fi1Ui>f2r?2xzdD&kftlyhIeSf~w zi~ogV@R1W|8~>w!36=P|kYB%k%=S%tqi?(VdDZu}Rr)%rx9?o28~$pjm+mk0J^Dsx ziI?nX8{^v_gXjy8K3;8Km`~qDEcdE!_T98=`nuci**krC%{$#33;r&eS9_-anE9vH zEBJlleqGHr<_0sLzJj&ctG`7wP+oHjeaUL7SN)kCJ~O=gOW$&uXyzl1TsSw;SCNjI z`G_YM=F_)y$UjY6H^wzy&ntt)^1eb*%%$snX;7P{a^i>nj zAHHCM@`VH_TUF+IvVg#VkW_RFz#|gHC;yR+4abGL1i~3DngmcJQwdxyQ;7?)04L%i z+o62^3&Q6`xKyP$5n!=Is{v%eVqpA7%Z+bwQP&8bmbgyvJI1}bhQ6z~SPg(e;yS@g z89%>lAkxqk0!fT|TFnHRg^M^5%#pZGkbbB`Q~Eir2fab&TL^YYTqj6B)Nx_i>yd_5 zAv^zF4e|j_Dt-unYCtJwF0FoE$3=n=d{g2&LHcD4Z{}3?E6(p?n1CpyDhmkg#YII4 zQZ*!-E#Q|+6#7k6h;$I(8;ORZPzo3H2s#2e4$du}1JEkbTL6eFWDY`ks^=v>wY`dS z7p(OZ^fXONw=7(&WxyPX>jW3TExbENWtZZDm;{XM8nYLaeK}_r5iqi8oyLF7NISyW zbB_bi9Oh;8TRgc%{ka}f-HzP9aNWYE0G^X5aeGsu(cl)t96h?CMQ154>KVZ@iR%Qf zXT0BjsH~gQx)`noj$RVjC{Y6cqn3qg%UVVKwTirI1)6%GMK8TzmE0; zC?u{EjAy)GHYyv&X=DA}*4PV6wz@ zf;TbVFBg?{;DP`Iniwrv2|y)PrNrzk70l;i>0&NgM8Mz>NU&Ze6WE9g zG6WKQP$m;F7<;<$3z+>X#i5edbIG~e0q&A0RXQwDb4Y9;Q#q-yzhEI1+$U4bg7kyj zBo+eET!3PkOKng+q*5DFxVcAxekD`As~hc9AZG*T7WUUEq&n}(RI?84G3f^{*u?;a z#C3x7^EBSWLS={Gg3bxFGwLzR{#;L-3`Gh0k!@5Uuo@Tmxd^V8$pnmMu#l902~2FDGA;nah)Lj(2cj0RJI2f8YM6Q%N$HU1lBUTfIu6T%kaJZ0Bwn91k@0*htpS6CbUiVJ)R>_)R*-b=0C!>tw(Foc@n-2s_B*DHIfnY{-hku2y( z0|`PB5KhfgyM*g#aIx%b12t|m(O~lUxSz)?FCMdkP~YG&%ZtY>v)&*2>(zMGtMO{P zhUyvZ)tL2eLA|GNK_B$OC#S<>HF5Ra0{feg>Ffzt?PT1fn7OO%2SImhoC@ReR_zmjf}80K^(b)WhT zU0>;Cz*m|Ipe`C(B^LjwRWg&8xnIToW>V~>Rg=?LRF_6t{QI2Df^-`B0E^_Z5PV4D zIzjq-As8ZYogn>imNzFVOF#bwP6YnQs3#Us zZUQG25xADo^V*TQa|sl2u4f-cC!@P@@j?sm4vFgo>1VdQrJ%A8Ka&NT~mBlkHjSo{XSC@$y`oepdhagpc* zlO?Vbq@SDe7M;rG#1klGH=Ezwf|bP9`9vnl$$vjw;yUW0lX@S88t z)L3K#9S=aYfSQ%O94pu0iT*v_X67?tO7NHd5)XTqc-W(kP?Xq;3*%>2S_qXKWwn$L z;GaHF<`US+YAGQNjTp>Q5g5%HnoEF0hk&FZqX(ptG*(LqfdWS761YpI66les1Rj^E z1fG?t1pX;g3HV?@5rqlR*m|jBEhIG5T|*)o>aH<019jJsIEKa4nEhR4)Pv^kZZj(~ zVb)~AtjdI0x2eDGo!)it^w##BZC-Wn^r(Ih>VAw17DIqU$0(2hA2V9q4Q-O$p#W)g z3>$)HnAUr$FX%TOu6{4qS@0SF4KJ8_RX0WP8gSx7!k`@jG}6#jCPBkJ2pFo(BmocM zq9O#XFahXfe;Xm;Y!<}?HZoec58zFS5_pHvVge&r%t8W&lM$c}6KgMrBfm2SGt(Rr zDnebki!Gy=fV84Q0*}a40zctm@d&vD7DF`&O6w^$N0NH`DK5l~EQnBy3up(xMu~=_ z{wQ2XEe0r)=n8;3i3WgaFq>pyK0uK~P5z{0QXyp7c+JKAV zAHfcZ>jdeS;m{?|R77QO#sx76P&S&RV`=$E`FC=D5rG$R3JO#B5`c<&S;dFQbq%GY zlJ^1nBzhkTJ;nt+lhQ{>cIMNBs#f9{@))8_qrxz1=fYBlX z!&tIn0(UW5LVyJ2iiDKn6dXqT7QiuFoKDC&nLhLqgrSjKguv~%xCkMSa(WSg5WA61 z$S7QxzzE!GrV~Q_hU{kd!RPoo(t}i*M;98-m#GZ$pZBPI7Zh~H%EQz^Fp%|AM4$>6 zMz4Y3Mwv{2G)Tz=KbOe_=Hk4Wk_ndK!Wa{H%t$8qvP>pmhZd+b!ARCfApyf+8WiI% z5{$=i8-=$5?3URbW=3qWByUss8OU@%*Ig`OI-PP26@kMe~YQVYjAlD%L(L8 zjbiQ%1oLsBmjs@WjW!VEcP=VL1Ps-B>@yriQ@BWP;DiWCByi%4C9<V%uM{ZS>3 zYZp!eAZ8eP;`gpZy?9bTBe*MUU{#F%Kg!+&POhp<|Gx0IWY?o^zXc(#W>GEpd*4%S&MFvFUQeavA}Cp5_yAGa_U($ zU4d7y;NOF*;Adv-6MVu_?H8zI$df>MfPiMJ0=e;KHeHPI)DhrDeZNzO8hN2O;_gIXsC=!oMtlOUXuZ#X?;&wiU zMyz0ev|QA(T%;Z2-S}Q>0V{U{Uk}#r1HTE@$AM>B^vYqtvB7#haAUB>By|I7wUz7a z0%0xKn}q*zRAYH7?3oyHCy=)~bE<1({#E(^{75VLUjPc4tAs4z>Kvn=G%&i5Xewsm zRc4=S5(c5NNip)$q!^h|z6)apcOlO17=(TU@UCF}A@E?Z#(?J|@c8BW*Pw~hCaSQnz>vD&PiF1YHBN=h4V4ObwE0#A@@**F%zw4~ z|7=0~#ptmmR~ojNZM)%%%s$s7T;uM-5qB59`j`-2 zc!AmHnuNbQF1QQtK0c%)eDN!TyYQ7}pKB7n(q!3g*y?f#gN)l_b`r_xvMk8SvQV-d z5oB2)bXgV(9}TiB5V|Z2bFwVR$+9pf%L2*dvMkKWvLFg0SsuqwUJHf0AOlS;@9o98 zNa)46k8uAW>LQ_wx=&8jMLALT$%(osC+a>D_0Lv>+ZPF+5sGaep%>?(To(4pWg%@; z%EF6|wJhu@Tx#~YeT8SayYOOn7vAaa!XLT2@a|B|dkRC5&+RMJH!mroJ%t|$O<`Z* zvxDq=3PZD)+gCW|?!u3leQsajx7=MA@;$e2mhbI*X8E4mSNZm)vuD0Obdwxe_7i&Z zM_UR%m4*8sB;4P^&K<6%z%*@!MYn2yAOr{R_D-mmyMQv+uOSSJD7^;d`P>KJyf^~Vyzb~Qe_QDWg zA3(*8HDlTrna&XP>71f(F3IP43uY2gWnV?bVpaVrFIZ!f#Tsi1YiyWUBhy!`f&2e2nbEeS-i3~^?7Dw zO0{6!``+K&m_oq=gS|2LY!C z>-oTS!5T9t0Rq#iKxv}7T(bG;{;PBT7d7}Fi6ol+gc3(WN3rBC@g$qvql|Kwtj|Uq zxeM2teY>GVmAmkh?k+4A%5zR+_Qg;rku{w|*}u?AqVEJEh3xl<*T*rr-t$ZHEK$kx zWt%0ZO3Mhv^U}C1&F$~A;M?-Sw{6Y^-+)fro-2vuS&0G1k^fA~vo)tLEVqh?zB%zu%_VtiF3D44*bmbgUVV~P ztzd&$D}qocePW;{OWms@cyoOL1>%iEt@ia+J{5slFJV<`YL~etlM`!APOLRKvDQSf zVp!Vv&H3hVbG|v;oHmDC@SF0%Z^{S1X=lN&&j-IgAN=~A1-~vI{JMPb>vk4=M?UzD zeDEDR3w}*L_%-?9*X%6#)%oC8=YwDUwBR(!o?M~#et{aEMU~|M zYgzpQAO3E$Jo{83(9mn);~1RV5QuGrlBncLA{~z8p7<|@h1Zq&LcTIz$XBL?tnTs# z%UDgELw89Bn``mC2ZJs)j&I0bIt^ck&u7iI@+IJ_!FpC2FqKKqR-IvU?d$^KOt3cz z-)#15zSi?r+k^iC;X8u8N%&E-XJPdW)~AF20^yCp-XvVo7N$2ZmPBEHjA7Il$eSYi z<2g_Fugd>O{Br}qa>!=m$U_QXYp^#7KUr!_NnuxGNJ-${sgfk`e)Fyh+E#Mx2C?SlOhz-xDcne zV93=Cz&C>R09YMn?9$5CgKeM2m~sZ*80<|#ePf-*nkr`s`(+GFV_q_+s(h9cgG{#q zij4K?0aq(vv-$RA0n^Ofh40-Vk=+P%xCKnplh5z}sqbO}pBN$t#62hLHpuN5WmWi& zU~dxMaB^c-74`;<$`9Ckg{*yx0e$Wi>)U|iSDIB{mi%$qtWN?jf)xRd2Ihiw3!nsY zEi~g_6@O1YZC080YI)yglGFqbn|1ZGNd6*|q$aq|tgH1E`1^wEa)i3rgsOcRkTleW z;5BAlEtn0ilJDGL6qqcc%N73C>~l@R(?~_`LY0OZj!P4Mcdva3(YSLEMPSYm`*}^4)%78 z`k?TRU~dv0*`lT?n>`yB6}BCdD-byinNyl|Ih|-u>1uit zg3ExKVpiI(yD(nmf=>$JCYu}H7W!-Y^`z-K_V9oR2W&x{$_nWn*I8Ov? z45$ypzSH7XcO%_}m|P($aJMmc!L(Vay6iNk+=$YVX(%4*TBZb7Dx=r z_x$tzf#n2Z8X-%IaqAPjKDx`I9C}8@-oneGqRP)JklQgf$ARw%_9o$d%(3}W-GA7 zP3JA8Zzzlr7hrLzvYVv}eycI7JxJh9^e;y18vuRM7i$R+3#>bUUj*y(dy-^12G^Ls zT*5b>_hNXxA49@7pZ6`exfC~_CkDU6m`{v*GZNflQdA_na!8hb5B&3tD*Tr$V4ptn z`(Gw`pQKhMbCq~9a&%zeC`rC;0c#4VypaPH%o~GM(mfum%HG90&mz^{rjmM-v8oC_ zVAj%mnJ3Ix%@FV+-7o~mrPz^C?j!g4=>Xm??-FBgi1+>1P@##_#dOpN#r z+4g33OWJ00Nsh(Pup664lFoW8vX;LZAT_g>d*_ z6!uRTYF;33HM?}#BmZZh@vy=Zxc^N%@n4p6vuatxw=ANZYFX-MHG=3lXZeRl(Uv)@7kzZ+;-Yt|LOj$n;(S_xRPIF&B| zo{pklYSC+o{@Y;Po2U~Oy|yPQpAb^N9r#MHejAWnNGj2uOG)PHMB;tblIj=#R~gfO z@eeZfD|*Nh-r=_&wgC(ka@#rEuqdVxBg9i&BYuKK(ix##ij@)K=QVa)S|iG-OCl-s zaa~5%O8{}iDuHe#W^TMy94}lI?5G9oQ^6`d%2`G7MT^s?A_*Cx>4e|qg#VbusoVgB zbSg^c8y3CtAfPYVQ?=ssl3{l;C;aw1L`F!`&*fDfC3&E>`lV9fyS~_*m3jUZnzCQTm|nn z=eZ`~sc3;X{}||87dQwnz~C(SnmhjrZ1O~&4Ib=vp%N!};yoENMg1a1sgFCG$Lkz+|!1(JkHdSL6*{a5Gw?@#^jB+|=?q}sX&R1&hs z_?z+HX8bEJM9Te5(u%S&7_4UiTY~jt!1cj;2XIfYDuaIx)>jR(putcsHv*pt)~^8f z2CMQaDF`4zt_{{G%eN#);H0AZ4TgZxSEVeukbX>(sElQQHLO35kzJ^iU4RGOS@>{p z7Kph*OOm%?WG|+op0G70V}#OCOe11cBZ_h9iHiA64AvMAYm9|8#!Ii+JmEGJr-TI1J^c}=ZRHHE9Vhy_-)#vx0mrq-zH z!BwqM<%0EJ0o4>%HB2=>tWo#}As@o1&j^1W>`lVMH(0@D${B8d#85SYJ4R&fzY|zU zNUXa9ij*rH@!!J&Rt55&`nBo0k>TC$h4F%EgC@@&Ay;zq}znR4zVLE@le9QGnehxv`0%(|r&4QLskeTSrl*F!bn8le?c- zMr%KtpzT_~n&KR0GSxDf(oPixq3LXEsAQ-pOz?{d#u$h=mJ@v}hL(Fi?7n0K;ntnb z!2t&AHNek;^>dWy?pC6;ZHRmuh5*+hvc$%^6HYhoGZ*z zDRn@0Wxnqb`9|5VEroa&0vjL%i^q#POl@b5~6OW?gf8aRl<@4rVk#sF4Xy11MNn}CtEIdbo_`@N7lW-h^RD#XsJhwYLSbLcy+ZPHK2dVZH1_`#ODTu4Hn%W}^n~oxSYwBu?&x#kU1$&e5rgIx}tFUtz z2BcV6a+)%ysz5QQzbnqk`wy7^YQc48t(|c;%SjA*>LJEBCYL?&d^1LcDtyQy^$QeQ zJz1!$080!L`lEr>~Xw075{7;TL?`%QtYRK zRpM_o@%zN)^(IJPWb{}jXIjc_L_EzRS4IHwq7Ws=GmKB=Y~b=>jeM4;0c#4V{E;CA z{DK9nJqakQxok?-z`Rd!TwcZbrp4(~oKQ5WykhK9T!HVE7O=8=T83#|E1+0WLYJI# zEtWG0V}vX!iJT<4z?YqK4S~JDFC%F9iGzzTiT20j;@<|l+c6r?g?9vdlkf*-&yDBM z4+Z}P!k-6wlkhKQ&%)}hzVk3PYl6E3dz0|7^F!;35-RLo7^+Hem04>qCDaNG!k!8Y z2J3$Uil57ZqA#{MRlyt0+OO!t7O?+AX`KGVf9(WXX#p!6@ZEu-?foYZn5VV&76NSx z0R`eJeQ+%(wz4PwdmsKm_KLh+V6j)ooWPP$jObMg=u&0@Qz<3O?=dPw;U9v%NqFG} zjfJSNyS_n8D+2dkm-tWK$C-CEIxU3U&z$-fdyHH^e?CqxG~Ze`u-dGZ_XA%Iu7Z1m ztKd-NA&*A_N1L@G=n1YdNilt~#px>n1Hme$&$EDiiZ0P}6N=&-grTUXUJoj??2mv7 zF1wQQ9H(Q!-uQdGv6C|Yw7Rz8w%y`$#|nH$ur~?!zOb=y74~*aZbZHV^3Fyly=i)X zi^+yIcwn$M35PCfpJd)ufqSP*&CGkXygzIqYaao=9<2WWo==k0 zNCoH()>sXS-iOi1FH~rXu_?xqyJ8oG-b%O&FbJ(Al^zKw$zKPnA~lD!lIIVyoC%(te@gt)bsA-%)<42(L8a7(Z^3IFYljU}(J z*O~uz!}Hx=c$wL^8}2OLyF$DLLib-7Ww;Z!bBT}8Vs&Y-M&F0=J;$8-E&$#ftnUJ@ z3Dy|!5(0)~=B9-2!%*G=Pcd!b*Wh+-@K%bK7^9l<@Zn&MJg&7b}p2S`tVO1_8kVX6=(G?+;di#38_Mfb%W=K7r)IH8Smk>A{2`r6mL*wF~rQD$tjZa)9_Q#r{OVDsG`rYT_j}xQf%aL(*0lmi1JM@4!jf zBWt<*WSsgkPJQC^Y2(xINIuI{4a_kXO)yIZ!ziR)X9g#eX00R`6cT^_b6M6z?sV9*p>uFehUU z#pt67kHh1oVEpZgeQ!)Y-f7Uqc={+qKHe{%feyVZZ-T@;fVl#*19J&x8z%l@xPRuq zoUmtO#6xdI7mu4U;-NV47sKi024k*@2(l3mJdA?!k3eOfg*Ee`U_U?tD%GPsOap)G+Os zGDhjNVD5Cj>%h-p`Z2G=bYrTR_>;Up#YB03^IWzTFp~4vpkB`SQta_J_D{lpgs=*K z73M=2#lIXZ#{V?&Z^C@U%SY+#}}Uy zFpJ?KK6)?e;h2Zut9M=g2>dBV>3j=QOh<7fukxXnV8(nzIX?PAPM|P)W8G0Njjqg8 z2T^|*y*Ej3#EQScm$5p)eD%=q%CdE@pbucKID~ORcKq}Xsk6XKG4U7UJ?Zfj|3Qr2 zVWs#@7{&i2aUaEe409c31xEaS`f_fhfgb=rhuMgE6Q&8X7V|J^J%zai^Ht1En9pD& z&-*b&d6ZTgCceJuN7%1Np7{H}{3UaYqrAkQ+^=$8a{rWv`xvOVkbMC25lsB)%ZK{9 zVSMiY38wHSX6*gIC<7(JM}0*pV= zyF*Vcr%o{OC-?7RqWd!mqi{dN?QfX)dpGu5bK(9k_cy~s`BHv=icx;=!^Gczw3DwD z^aISznD~21nf`~-!#aBWC;n!t^gYbQJ@83YaP$jz|7LG+-xJiW@Bbm(LU0H89n6O@ zAHl@mll}OwL7T?t)@uB%!G13$-j3CURb83YJ<)x@_^Xc~H|C3&+c5EW&?tH^CLZ+0 zWBz#ZuT%9yCaE*dtk+?WKhY0j{#p1K?gNC;-GU;&=)d0>i&gw}mafC49tzquHs}T`j@-<>aEodp0ep#RVr0h z_m)dNBHCM9TRTe4)wqxu-B2H&92&0ArZJmqwR(TG+*49I-PNQ%H=$3S-&rcDI#GFJ_&xp3k9gO5@c^Ybtd~*HI#NrPP`X z4ot)kTc@E)YuZYENquB=YZPup>e_^_>DGrQ$CBA`R&9f+ z2r7rJ?w)$H=TWg*yE|b)$&gmPvs9}!uP7xwYb&MZuC@60l)G9xdfQ6fT^(!N%hj4n zq+Y3(`aGq4<@A(0OI`_-QJs|obpVUzj*jmB=B`>f6@*+?>q}G8YPPdh?`}Ccbu0CE z_ja_kbac0_%G^4RUTJkwZ!6a-9nEX&&24Q}WKM=A>I2i$10HJx>8&P1 zz0zAn)R%w-(V;n+7cF@r%YPf!?l`-uCuVl|t^S^!BKJ>}$s}Y06Z~%5v9=dV6ZN0m~sinDUEh8y)^_4ohNueI9VQ_Ms&OTfp7#f;p0V>w*-PKkV2mC8ExN0(_1#e}; z6yF=4-rCM5-v_epTk0rv(yp!PhVltJ3>yb#Hr5BmHcV2*wVq~r!Nl<9F+OcxAD9>< zACj`Ox!e`nYnRGlB|Wsat6Jh=|JVi?bJ{z~tv$)6k+FddGs(!rz<9oTceYXBI~-ay zlOx6{Bv8vx*7(ADc|}(@#o60JQM6LAXLBWtEnVGZ+EyqWN^?~4toJupDkZ9a z;7m3YX0}eu4s4N6OSQXS9R`NA)@r$>l&E`!Er`K^DN9si6kVch)g1e@HvzSq#+nF; z*6SUuu}jpHkj8-SYQ3jQXSG40b!Bt4mXODhnPgU5N4ZL&#kO>;vhFs(&@^0EyQqgU z48_p8vede&r`pS)5ewUf%I>zd`pVLpdRK2}O9}oH!&_z<5GUqf&rrC55pI+YZ5bRM zN*Joc-bTu$)LkL5NoXWE&_7@MbO zlNq+r%QZ8|#CT~6-ptmMYp;zm|yy}7n(ZOK}1j6X9tJuo}CQRy&^cEY^cdh}BI z=Z4`eDuaOy8-|DKlM`b!SCc3VcVVOqT}Cpj=_yq^Yo(r^a!&^dFd)G*w+ZLloRd=; z?c+G0h^^JN+a9y&fcz7UC{OBjuqYLS}Qvl)74-G#)h+L zPP3FZ>(Fg9l8sJ`Or`=@TU(-ZTdMTJj#7KI%$P_6v%IK08pAGYB#&t%k8LE6Yb1|v zBwv}ty=!XJ2DQ|`tGnLT+|wLJ-hnA9&UB>SwsLpFwr{S1G*krDyn%7Pp_rSiZOO>w z^dPN~0Uuw>VHkv|+9`%C6x3<)p@xSBW(Vq%>rWpZWVT_-8y=sME~)CIS!vpc%x#eE z?doi1D5GyxnyV%2RsGfGN-{V%J&j%zck_wOFybvzNu*rV5>_@-^417^!fq$2m1z)H zpO`~>R(4zZbT}0g$|35q^qH1&S2GG}z1&^jJUu!)j7~PBLS!@<8=z38CbPzYM$kiE z`np#!zGhQwm|bR-QEA9!^fLMoaVMDTGc7!}KU$7P5lW5X8$jKN#nP(sj)X+F^qAsk zQ9~o##Uufr0oAZuo6(BfP>7L zX^QmfE*2~^tT=}1>orAbGNLHPZI(RhN_7(o ztgD$GjOMo46wjHt@$rFa)6qOTsC#9!@bW31p(v^Aj6o;0aU~(O;VofS7~III0&OMB zK^uA#Q@(eS>EXfAsZrXJq-bM&=_&OxVXa8Rvx4a@<+Qe#Y^k}utJ}wZp2=Z4qU2Xp zyL;7=HI+=bF4Z_rvCd0bQ<$A(u9rb(bVmBPbuC(7t-PYv+gaC;7h4k2h1C)cOflJ5 z$C^$F=D_XmrEqY<*JntP~ft%UNj^vFK1hx_Zj(Wrk;IJdLXb zwP_TpG;pb>yStNR94bOBbyT#b2CcMrx?23jnul5y2WLqVW-p3LNtvQWx& zaFv}p>g41Qoh>&5J^gSDj-h0v!}hFf)W6m1SwWXs4k&4x@mdJ73U$39WT~~etCe<^ z^i`=qa>Wke2HiLdC%2CBk{*p~UIIA|=W&nu|4*zUq=pHir-O|+hyot~qW zZmEwAtY_AxLD3ddO@RVju|kaj#cp`w%;B-gsbSQG(Xsjn)AQu!IcAH=WOggAQN+@k z_TG*TPcXFIuoP3DPv*kFrcDZ4YQ|WSmGL*MOsT!FZiuS`t#8_C$Y~;)vUZ}(k=t@t zdpEkz+~^SVSmYkZ&!|SBWK0iFjj?{7OsmDz%dmbj9l533)YG75^^~=cqi{mCRZFd< zavzm7GBrCsm2}crt4vA6TSc|8T(Mn}fw|d@3?ZX~46UgsYJF8xB$BhnMV^g@ z_MJ7-Q9^OFUWJ+vMr!gBWYJigq*G+-Y?@%b+TOb4m?cNq(k0BvjRQw)jIm^F9mA;7 z*sV7Y4{Y*TinLf)MsRb4$NS-kj2TU;JtGxp+aw}~n)RlAzAj%mG+<%0AA zhNgN)H=WKFp>Z20mbfOS=GN9yHaJJ05~FgDf>&8%1Ra5qQ)_-{ku+z@BW@0@WV+Id zNh?1#a42PFhwd&f@#b1_eORE<78xmjA=!1Va!Gzvh2s>N(pTEn&>ZQRs5`Ib7$ zEtI>8DlAvDL6c0*&AO)9qunGQ_=cutBYWRriLI$klk(JB*KPrqVT=R+j|LFKl|C zzEN!Jw`%*TAv!8ZO7}9fv2&{lEf%jeS25LIg>@@eeBh?ut+I{XREk!;z1rQG#-{Gu z=|k0K(?$uZm7jDHQ$faOHn0gCw!qOW>tQj(PRDee5ouy>yuNXCXvnsOduq*nltb9( zwBBNUvaq)nW+>_{H2PEwwgMPw)gsdMOg7kQ#*MixRdPxhd^G4VV)y&Tx0)9jNT+Yx zhX{=+F4a{Yu5j9jYG8 z^YxzXqXw}WmpL}y5R>|)(RN6!Z|vcWnmF4fE6oej+KM?#d!AWtx@#5nJZ-F_-qEtq z-Lm?L1*lfZpy^W$!8^+I=fW0@b`P{D>`4Y@X9os1*0ou{EFAVW!>}1|A*CCbi0^w8 zHjZ$O$X1tHM7FMyazg<24>W3*+cJexJ*2m4d;4J^tgUQbdd#tLxxU8s?=&D#>0Fj# zKOoCZDHHHm9f18jX|w)Vt9CHN{hFRESK2MwGKBEc(!+UFs!SjY;QXZM=YIt zY6&|zewGra*UoaAR#gtI4ib^7)hr}wsEiu6HB zkQ-c#+nL(c)s1pU!?GQW*{A81`E^^V<7gf9Fh+&K?5UJ1sGYvKZ2Gw?fcA3>+}n~C^Fb=OO&gAs}8W?*b` zL%PS!#tHo|6N9b1mYN-A`GBUCOXgi=66EY4N@BYLQcu>>CRgxW>@@56Ey>9Aq^;#c z8}DperU;S9Hl5m7#M-(yD|wnXDnL#T(!8yy&Brs%t=iGaYZYuvF11Ys&ihyg2Ia+$ z{A?g$_k^N|hc2p&RQ!@EOI?bl-PX*35Bg6i_&B@7jFvd^Sy4vG%QwC-k>!^WlGZd& za&YG8%%~2(B8#94G9X0<#y;h2Z89{yb$Tw_I>_(!#wBn*3#_!+@U7d1B00-XBc<++ z#MU*rreRXrn1>>%%-a5ZO`6?CHsfdH)YDPxTf#03%V*nVq9CV7*Rz&LW~YaTS*bDi zq;e}G?32;n)J3w~FzuGRm=44+&U1c#qzYhWwp9%3{>0qaSXSp{6zgo~KGh^N+y#Xo zO@h@cBdqv$Hdj|Mv{_PWp_-VqU#kJ08T>4rzDQ*Y2TGBFB)0)a!~2vr45l*q+fYcT z{JJ$_c8uYmh3WdqEw=A6J!!i{)}!rAw{SG3s_#Nw)CPT+j%?bu^W5WGm_wrwjM<&7 zE3=&+DQ7y^pp0yc&K+tnkf?#im=eFegH0oXnjE%;L|yb~@sI|~x1Vf-d1h*0a5&M4 zpZ3ts+Bi8kZBCbU5Ln6d3#pz{NvMKCL zPfbtGPO{Ukim_V+Ev6v{ajhSxT2U&mvgN1Qj1i5xLbII)Z5*18dw{Vlm?~WL(b}rU zysK%0wL-WHVOi55Vp%hqhFt9>*4Gcr3?~EYN5`04StmDWxmJPf)}R%4u#29nuo|}q zQfa03>r5#M(phGC$0AKbp-RQOqef5mP=hXvbJX{DvZ+H>bflvqpwzVHYxQjbYe6*Y z;6{EqkTD%4Y=x(%bV{~M?G7C%oDELa8Nnn@P!{6JWgOl#|3bLE-98}ksdYf~bvP^VU^tY6!E#$W}?)spT^)!bfO{Xyq zaglUdt+|n=O0ljcU>$#1epR#2PJTj@k`#9P#`jN?h33(oPr9>tTDI z5l4l^DdQ^bVY5jx%EHI@O2VEsT5#C6rXkGD#N2SM=4UCMmzcQr#jC4Z>Go{NaWV}% zt7o0_>!c&Q#S&v=YdbsZz?nW7XCbxIY<KbHWs_9px4Yo=dtNaMO&ID;zd_*EPB zl+H@-+b|%?fki9Zvn#{NXc!(i>uP1=D=Mtsk$lsoVXLOpx{@8Bw1_o;u!pJZ6%^@Q zHsvb&H7>#A)F@w9bNRtGo#J^(%)SPJToJT(S}GJlZm-;Xe42cJ6)nHc?VFamrktR7 zbAr$uyRS{YWvQsySWZ7;m6l9SbM&GU_oQwo`%-+h<{1)qlI28}CBo6iFH1IW9GInS znUl5*4Nuv{CPrtwf@Eioy4KZ|m<}E@6K=$qOdN*IOtMct?B_gTO*u0>rV}!a1~iMf z#cw;gDGz2RrcC*}j;SpY-^;XpSjyP;wg}P62v27#hA1s%hb%3wQa8(%c5XR&7JV3J zo29>*b!)f-F*!Emhi?tD54DiZbM!227O3#jBRAveUq6fZm$LH zl_peAZ!*{|6NZ+Uz0h1My)By7ZEs6bh1)D_Xsxno%g*wAO!4(Zj8CcBcz^(&gLHTx zh_-SP-&dI))md-_eb(n(m2{ z>sH+t3bUm)Be)n+3O5i_8Pf}il(SS2E+*;hNJCY_WiK^VRGY*$s0Sw}W_3gtxlll~ zFIsErLf%_*SMxMlWSVf;mkN`hCPZzClALL3xx;`2-I#TTo#=9^kn*;M-`0XREkry1 z(_5!>mdXiH8m55Tf7TRW~7|m=wiLcfI4GaI!ChgFf{fqTn4vTd_Cs(I$?&+;E2nRJUYcq{o z5Bajz9?a12`Z<>6oH8ZhKQb*fuh2nutQ=G4GrbgNpLF6tmRD?c^86SPtbRiu_vXx; z9HsL~nWFLqMcw9Onj1aLcHwi~ug0z)8taTM+Jq*6ma216ZXjvp8`o^Pc9j?1b{^T; zPE}srAz=TEqal@ie{-1&!CZ0UnxUqHWO&QeD0}QyD{C2jDC&-y-6W-rjo7w`gw?7( zExoSp=B{oQg@cnrx)!Ahtu%A}$F9p*bGO@8zAT}1qB0il701gtp*e;b?wBP@X}3e# zg&};KD3Zp#rHCgzS{3}L_t$0<)co3>fVv=s`tbEVxA zR$)d3-PW(R|Bzout2UZ@*Vt_?0()DxZSN9VfSL~r{oYzQZHlc-YDH(ItZmAXWO!_b z!+pDiXPw%PSYpUh$I>q8jy}H8hV42QhyI+QX6H3jN4kBPM%7Y1t;mwp(Rf=V4Z;y> zjoTnus5aK??8L?Z`Q^4IaUEK)CbfJucBgpR#3s1?(z7QvVO;cZ|8D6row_bvwk({w z4iClCsc>6PizNz-tA3$jv*=}HF};8t;Gsb~XbOkMQAA2ecfsrN_8i(khg~+4kZqKE zxVyv>hCbxAnXMRM4Z|u^6W5yP9@I;M!lm0bQHjwF zajuPKEU0vwYGOKSE7{u3+EEX?LMyoG!?IO(kLizE2u)0KrIgDDaj=+CCL$N#{?t*Y z9sp3~#F7d6ez=V1%6`x}kff^Xk5jCgMz_FU=W}A}%zSEK$8gT>YUk4<+bp=*IO(kG zx@AmDQ&~Dfgq?Uq3|BXa&dw1x0o#~}>D-&ux$SQ5vCF6}e09p#QSRjV1zVDslxpg& zT!gCmq>I);;QVa0a}`b+ZnzGUO{E@E$1IvVbh{&Lmmq#v|Abx@9v>ORpT$H_H|_K$ zZqOhqN)m$?IrlCb3qZX?o5k9=i*9lIgj)*CDXPtoKHc7~zo{*v#dmk2XrZ&mXu8*B z8=$r!Y%PI=vtuz$WWKPVykKG*X&MsiIzT0?F8KL8({L$yMrxEE8(~vzO^?nSP?iYu)l*ZO_*pCj=;_CEWVeXyix_w7~&F<>NrwqbK zA6GE(;&79pwpG#J<>&rGw+!EKBWVwxNjZ^Fl`Rp$VeVrSs%{v||Aniw} z9#m?%CZ?f5MVap2=t3p6?axT04Zu`CS0a=ID!uOM={N{=MleQu+0RG$FuK^{ZY8Ul zw1RYKO}7lUvqHhgz0};=O)J{ouJYHEzPykvCC2cEo;(;)rz?7 zxQP?hm~K$KeOQuGL5uT<9j3srOq`ventcap0uHKvw~w})tQ`KAhK)VTAfqH zxxvU5aXce2Ix#h;#|t>jFPvjav#4-_)|y?1kgOV=v@pxXyAn*wY)DNE$j!WT2wdVYKd^XV)xEZ6eRP?bGza zZ}u9JbTrb#ec_NGvhCOHK`>DEkQH6M z`?c=3Z1K^Hk0ytv(`ihla(P0^F6}uH=5kd(;}o0ac6EgQzf?CLra9-4;>K~TJt3Fa zT{KB2V3M3Lkkf^?3iA8RV{Dyuvd$Ifrso zX9wm?s@NKcHAX8-)>cO?JI?m)GDam`p|qt>HqAHO6;P?feUX^Dlv%Vp_GqcvVXprV zGHhhs$n_|0Fviy^#fXf9+Tu$UZIy(*7HV{6W{!JpHsLZrvtA;$p9rW&NlR%sN6?-b zLt`hK>ZVjPnuHydC21LPlGfeJo~i4gO4PJLzwR{4^R>1m(xq$GcIUFb5$!)WGIC9} zjcwtQl#AZp&~r_zcKs{t>$a|CZD8G(?Y(f_kgG()qdddWu!*meQav6;UFUZ?AnB}9 zmg9zs6g{0&6VkVYY@aR7nB`rqjbh=Uo=m;gQglVU>aGn0@-j9$&LcIp(PiUSCubP8 zu5TO^S<4Jln~dMSq@J16vyH>PcN`}kU%pv6TJzHGfr-Nvh>Dg;|tXa~B zO6qK5&nt4*5|*diI5|(-NN+gOiF8YEc7~!p9JZ$GsKm6t7|5H0ZnIIIwOU8t(cw(Y zF37}C`LRp-6&i|m zvO}v>wo*$kH;WkJOzDd}tgcuE+7no5WHQL@Hk7!quOW>;zukp5Zy)f2FjSp73?qn8od3$YCb^!j)R~mC~XSQ(6#DVyFc4#s=N&EX9PzRN)i zW|Edn4CowtW#eUBx5w2{xP{DPS%obM<&5j+y=+-&tmj$fG}DaT;T03G=PprqccSaw zN^A|a)4`Ob=hfNI-RLWjSOuk)cJ{1NKDE}iW(L4)Q->>=)n4tV*y6z(cN)3f4n$`- z76^&4a%YiGcvDmJ+875T94fPg7>0;}nN2*UG98zZaVXH!y*y^ZxEoGmQ@ND&?lL-) z-Qriilr2u1YR&2{Y$?Xd3Y!B_Ge}Rm?BFGpyQ|wKd=^d9OlxANDW0*kqq&7^>F`4H zu*1732thrh66Ur753BP;Vm$Ahw5ysn_G_fD4RbDn#WO_ar0}Xj<{{=LEotHcP+8Za zKu)n3te1psuT*3^b;^aYHG|&>it$)w=~_p44kSJwWjmw{+{uRNNj^#j3+u0Ow=6z_ z5%x#yN{H{3w6VEkLwJ-yN~>MXi4N&bxpv8$xx`*I)e|L?W02{A&ADvGZ3V8rPYrC~ ztlah-yldE5hL=^kpJ|0;k738;)CiQmEiDJ~H$J62bkM@GwGtzMJ?~)`so8nY(3@AJTaaZNvTa^W_j{u{ z5uWF$my*re_fqTUZV|;ndDSPhDVonJ`AImwgR7kBOdeaBl`rn|;~vs#*&UwlgR`BB z#o7)B=dm#pUvC6p2j`WVQx&d>9_GI(xhVYgXJ;ZD)ma!3P zaF$1&{Ed=grG4I5aAL(R?Xb}et8l($!xSaS`w{H@38O>yf{S?T&ToOzHm$t46B;bO zJr%nMo*YP^ZrK(XMVx46t?96rP`pH(s zPhT2`**ozkhU=UM*4ciV8=v5Q7kiZPVHy&#yN#g~v#j#QkX|-BdUzbLZf_*eNv3b^ zX+x-Zir2bQk2NE)UwsLyv^4AW?5^Rsc7_>7IsRZ=wwEH!XhuAP*?V+kG`Id@->6z& zVvqG}L{A?oN!zp@U{7ZoYb>3m<{Ag&YKm!IG;_24njLQiO}U$8j$Y#7OWfQ8MzlL5 z)0HzjC>orYwX=uV45V{v%%ucJ;fx%5YjM}hpEvbdJsfp_OG&T?HN!N4{r@>tt40=?ZC%V}1)%K5C zjc?G?OoCdb)@S8KRa?s8#*ga{L1E0+<3aV3E@Myb@V1^&Zt}(~vXn%@NJ-nI(Xpd0 zOfakJGmMQM^TlRz5Oi z>oeCky{izAtZ}2-uUW*=SQ{guFs!MHX&+k(9Q^o`{tb6P)#8v?Z7sjCEazCUzVEE| zWg3F6A%^$TsEnoGM&&lmPjg$J{CM~v2%C+=CHAsVQ*{9xJ=@p7b*`etv#pdz;VEjA z+iJs2Z5>aAXNtmBKEo}Czf1;!)Ls{=u(l@jP8N#Znuaxra8VvQ?4H$DmGxQ_)@U{# z+kmaD2zq+BPZnlBZSQBJj?@sn6-B#2z9p!Amh{>Bz$M%O)2I+%2E@wV-$4;`O7Yur zUpJin%@x_et0N6<-18!_EWI!grp+h6)Qq>B;b=GFgTP@-#JQZJ^s6Hj6I z&Do%PrOZp@kS&KOEZ03-SLxjdxkth19+g!q!d@=xC3gB-4Q|0SI4Md9)V5sNfUPrbHb zNR92Aj??gD8+YAw8#6McdcsKttzS<@WP4B9{cDEA{Ouh@N!w54!w4?1tqbX1icfjD zuE7qXT>_=Rr839B@#+n&wecZ@aEM3S;#j1+tIXn&)m(1Z+nS)wbVsMTY21~xdnOto zXu)V6VZ+e|{j?u799rOtRB@y+4I(`6V%;iiQ!+3Th}RTx$=EeXhIGYKjb-Oi(o&Qqzk+c%_4MFAc&J2Cw0>qll;uQBKV8 z?6GLIp(El{G^r8|?{Xryojg#>DuVlT+_ei=;(aj_&h^PgIG?E3N3wan#4`{KG@<84 z{;}hS`w-Dp7umILqQTpv2+>{p?mf&t*?FN=tF|4ru8mK(YoKmt?qy1_11u`dCe=6& zp_JK)u^*&nB`Q@Wrlo4i9cuVuMyE4FyhLYfJSV6R45D<0UDS9$r85BS!BWuis;*x) zN6(WwJg!%%@XS7Y#c6srg5>VvS9t1GJ=I&aRAcRZ+f8L;Bu{L7ujBxoM~C%dMmur0 z_wpo6w&}fkWYD!gJ4uX{#C&WU!+tpeCBTLYh7a1o`XSvXwC0p5-Ap29CiOGzx?ofe zNOUt-A2{5ZwizY%qNw1{aAQ(0Ux=?tun~}%mzO8`h)n%0mOp`KN$wRWi?%uVTfBZmp;o|?8jXpB=E z#)rdYuo{&Oa~m$jS$AkMR;Zsm7o|CX!qK6$_I#;37RXtpX!Nzy;?Uf~oy&UcXK^Q# zoh7z0Q_U#7wB;Q-Y(Ud5lNGJ4C+v4fn_XQDr;A4%^9ny^Ocu{<9j5}oS>4+NH%8m^ z@YrHgz85od4#Y`yAkv4R8_tB)M5!(aR-6;-^KEMC$`E(@_kh&-ne zy+Sc2#9Wv6;}H}c>L5p!GOt{uwWOjoQly+Lj$3bwIUE>X%qi;;6gY3w{eSEKmNq;n#csl=*LUTQ@g@0+aA8uBD;PuoL=^w&&QJ|%}>7C5%Qrji22}! z+i4uE$-F0%7i;OV0RPe#E@w{&kVc{C41!54Y##e6lEJ zD(80%_I$brZO_V?4=beU-ja)hH939TyktLF{1?-@89LAJaQLaMD<6F5BIS1v_813i zaw+@{*-f_ai+(?VlwIvrzZ>2=FZpxs4es)jdDs!K-;UqUOI{oaF!K9N&Mxme377vx zN_mfcNd5}Aea(pYVG5zT)fU{PK(byi`9~PC@KN82O(Ly$;VKLDA=e+n@)XeitaQ zqyNVtkAmLl{YK+U6N-f^KjaR|4WG@e}<3bdOC2; z!@m@I(ZBEpd#ClqpsS&I0lkGk9{MQiu>~HAUx7aV`AKpjJVe)_Z`+^oo3<@_3VPkq zd??T3pAG#OgZ5e)k^JeVNo6r#mIXy$4Qd>T<#!$QB09q^l%f3dzg-x4Zo%nZ_}|B% zEB~)UBMNOH)X(>!_oI@^FqQv9(AT#n$s6z&{V4SEHolev8h_-vzQh*;+@I+w+1AdN z+z?3qFNeO3%AWM_Cqk>eM|oF4AJviZuPZ$Cobx*adU+?GqV)I|L$B+izCrQ765Lkd zdt#m+eQD`I`hSb3{{`sE0QKwi{qi5?(}2!TUus%Dot5XaDF}Vmc*w)=rGnvW1CM$5 zL!lo#pAYdleGIg|?Rl}wdor{>j@jn^b@}6Yq4OhH`rE}u?v$hsR5ICbmqepX_S?lq z$UIF$%Kdgp_R3MJ(|ro`-pLs9JccXHIoX5qI|n-cl={Wc%aQ#A?DD^&;Q!$Q{iy=| z*#iAV=zHO(_9A`{6#O48(0?z`yHalPC;2qz#h>U`6zEqL=u(01DA1=A=#c_FRiIUm z@u&3PTcEEm(6<)o`wR5X3iMM2`q`=||0%t_3-n70^veqL2?ct2fnHIdy9#tqfqrd) zUSFWc3iMooKCeJuQlPgL=zlBFpD56`6zDq&^nC^ThXwlA1^O=qdN(Pj{tS;{u8}dfj+cAA61}FEYNMxQ>{tz0(dDuYoWL0=&?fh za|`sl3iSI5^mPULYX$m&0{veF`iTPlj{?0Yr~IotUS6P&DbOtix?G?K3iND&zO+EU zw?N-epzkQqcNggU3iK}v^luCFUkdcI(DROZEnn9|?@;}{0y_Rw9FK$0)0F5@~!BHQC}j!!2-KbWIe7s78W(B~BB3k&o+3-pcx{T~JTz5@Nr0{ujR zZep#b@4Fx8`F}Zd{3(COKwtkx%HRFF3;rVo`pg1-QGtF>f&L`4zNH-J!>>T=d&vr> z`U|JY>3fRVDd*;mzT>Np==jNhe5TId)Dl0Fke)+xG@x^o@Qxig6z^Dt`x7B}Dh%%dvl2KvKPkc^kwmqCChk? zclL#ZAdtPWBUr-)HkFiKTwa2zU&yh;a$*$B+^%&D|l$!+(L*Ssm|VY;HS)bGTOe4 zRLF`h5r*SJ?x61ElV&@8npP3g`+!foIyf^hGF%^_d&LtGB|-Iagk~2B!<{M%MLF@Z z@+7`?6;jt!^Bi6LhWJ~i)Izy<#{2MQJQ1}`&L((zOHb8LPYm+To}ocnp`D~yx_Y;) zf>8pxo54#XczM5WHWGf2c#2YKc!SyW?Bu2pM19PzcbeEd4XFc?&~iD{&Sf+{_UcZ& zM};KA6QA~ZhY%;{Y%k98K0vF{vHjEIQhM$f^Y}DAv=uUzs~IdNw1x57wR$Iz!*23I%Kz4DESXs||P6g#mlAXlBAW z1(|hmI9ze?*nCo~V{&pTquTVw4PJU_+1DdoB5o*U-Fp#74DdcD4J^QtW&#yt&7$c5}hPAlXE0aM6Lc z)J%tlO9cgaG=_7va*T(oyp`H#8uTK}^;s5lxtjiOx9Ze->6*N(uvYl8X1+^hmus?- zCUb*FN%uV4!0qygSD1w7PxV?BJ$`Ebe&a%~_YO5J(PK{tkAr1N+4W)q@Bxhw zdw9#JSGRq8aC&6$_@zthG*lisnNFMx=g?b2jOpR=N#2KZBo@IWxR{+j>vhH+}H($C78P;RR2P zwcdY%gN^QL?t1&My@S9mc{h4`=~~#C;oyk7h2N1ass-K}U_yjixAMzZ;?ACjweU7C z#)llug$oz<)Pi`#2N=!6+K%1rGSa`_lC_GbKQx&>t{r=P{0zeQrXd?|LeBMxIQ5$R zt35LxHJ7}PB|be)WyMLB5*;1aB?+!ea0g&h?lRp!&9~CCyvKXLe5Y!76StC+5xjUo z=Ik)TW-L`&gw3j!wwi|~2*POssfXdxsmwWypEd^jSQ=yGpEPZJU_0cxu|KF;qEC6x zG`SKJmLbz#yJbSzht$IJ4o1_I^d@9`cW&sP_9T#v?P;zk18SMe4f+UER*_HBsBHdo zEy1|cM)D;~)CR>Rs&w{F%bi8ArWqQn3!0NL6J)1+vc{Pi4 zM=EKFS<*R2%Ru<7TfPGpovmkB73Wh8T12SVplk9Vxu$Rr6x|q;Gne#UjUGL8XBv6b zM-}I3t}!-sYEJ?;RLD+VeP`mUuuSeO<1vw_A6U2z!`!LUP`{qXvxoE|sHi%jP#(9Q zIV|K5AsdAg#c*h^=?y{B=RCvQn6C&69MjDtYH&`H{aND9FC|GQIFG%he&LEFIZenO z#-RIe60T&e?(T0C68>KuKPW6GcHTMv5&f0O@Fp!|;);{Ou-=C4i?okIyXg7diK@=2#3 zbZp|>LGC(VQMgMTcewkH9q(d)UH*?a?#_O*%HhSJ(mz;qjq_!vS32D%B)=PkJxQ`z zSW1$oguO}fPWEZ%b8h;SkgwP8&HmkdzEppbaBY&jO-Q)^1XUkD7kx^S{6RFwj!Ikk ze!h_X&HaR@Cdpw!(m72?{7Z$%`+4E(lH_OZ|5wMCu|KBtriFz6H&E$)N;K)+Dw_1Z zA)53a5|Z9ug@oU2VF&i>K-dXl_GxGqUnf%68EWIza?)8)QCNwx|HIp-F_?<>NSljJwT zp(J?@8$1fX4>*6Ab|QrD--LvJ)^h^B$Z;vCe4Qk^oBkq%|5@(-CU<|AyFVa=-=BoY zdEj#c{T|2f36;(sL5|%W_jY`VC_9TaBmb%xa*w0+37C}iFdz{@J)Mzn>dFC74IO?W88aldbw!$RD|P< zPwxH((ZqYR(^rWm-Y1;?oM_^GO-Q_-3n!A~@9w{lqkN@zu;UU?;g>tzBbssrC!AjJqQGxYA?chfBwk%eIZlC!_Xg3F<94U75{(=; z3W@hsA>r?J|6hqF{9m2kb>9$vUm@XNE~MN~0L8z{{a@$wu;ZNE3I9f?w~Hp-tK9uA zA@cs*@z=tWxog9PDe>J0RQQ9OK1wwFmOI_y{zFbrIeoU%mxw0(6;5B{{$F$ z`a#D>_=`95*_B-~psprX2~Z+#3_l=MIzO z>5gYOUIxyeOp9~W-L?PVbGj}Q{?)k5NxLB)HM zXu`i&^jS%=!|Cfqzn=CX8b0^C`-5^P-h!8deVp$IPoupHhtLCrrzgpKglm%IT45*m z#e}Dzhk#1&KSjgm_d?pklS0Bh^APaVBzeB@>?C=ikn%YORJ>Nv#2XM&eisVQAsyjb z^d#YHDF-2P=7YQvQTn>-4bGZxxcxhur;>?tZ7! z_c{HPXzJ;J!-JfQLGhauo=^SC{SELDUXUcW3z6e4`41<_AKm{c_uu=7z~|+l%B5Af z8hu;t#2XZSVUnC7y3Bn+cfZWtKOnq_{4Nghj(6NFq@3OZ&Rf7eV0Ztm@QvshM}luk zl40S+%om{eZx?+@l6+KHM{kik@jvHyyWCeM$vut>j=~=~I~~`8Dvwdo)Z?4n{q64l zA$Pyt>05+vW0>2l7;?w2ydeLeJqAx|C6ph@!TMGRa$`uqnb~NiAstDU~d>F+rH%H99&^d85-=k1I?LinEuiqB@px48Rv7C7SRjJAImH_}<|3 zT~6O8n)dQz$A=w%BP5+u9j8F?Kg;Qh94~jg!tp;GZw2SSGfBQJ zdIjq@;a=oR?zE$S2rHabzY2U8=?LFV`xO2ws-3!bN$*Ly6K=m(gNz4DK#d0{2pJE0g@hZB|9Fyo%>8e4|9jm3JMRB; z_kYy==buD;lCxqnt zHO+x5#eUW9e01L;}wn{bo_V6uY>bH!1ydA{$oPq*rO%jX2*+#r6hT~ z(^ok@0xExxi>4eGwStuQN+IEELinBLcsr=@KM+m({H2h7@VLA0(gsa`cs8hTdy6LA zfx-`=w>yry|FqNZcD&l%KkD??gyicXcmI{U|J~``kWq5KKnVXMg@iAIO26vvBTi3? zCj1-R{XOpfA*XK>ei(hUo%pnyLqLT;UI_mlcVFl3vreDy^!-jh==7sP;^_eg$@2_Q z^g7YBlPiU!vqSErbCdhuBSenBy8o`s0rKBNNcRCbzQWztIu6NyH|9g9-!7W)SGoH&jvsaZ zdqgi_A5C;0?R6E{&;BE*aqShNPeD%-4WAXFN%vIYHSEs_8Q-SmPx!M$6aG@sgug;G z;XffH{O5#(e?T}&e-(a&{B;C+Um^4XpyXO7`davkhW`bk;s18g@V{C#{J$goH^xV~ z6YdwH3HK+_gxjSvgxg1m90v)JV@kM#b}0NP>v7@fj90>svEK=*JRcH$9(=mMkE8zx zuS2f~mEM7(N$+UUq{rL;Os>m>eau@z#`BbhlS+lF}aiGqH3V`1w|hw zq`fb9cRu`R^!psI6_W1v-Gxc>se%72j%_XC8;bCmEi>~{)3i@qwn8T~-`xg(I(lkO))lkXcv ze~I<2(+@hG(8lEd3{d6rJf~kInsT{VH2mHn8hJk;MBbZ)Uts@R_(k+a;jQR%!n2cP zw{;-pvIvxX`wEfoHA48cfs*f3r^iLZf2$Dw+l7?Z4)?#w{cm&s@4EX#?*3<|=MMxv zuL70M8KV1`KSkfcdQ(V#KPh+G?Pr8vX1yc4ljj-MgLlzCK*{|w;RUS!gz!5Vl-&Ko zudoghewBS!`4j#e;RQ+ZK_Tf}3o87rLfXQw-2HLUl=okq*4kg?{X*f_*jEtJCr<{& zwjlW7@_7j;xn3a}|D{6w`-J$v7L@;#X#B4beO{7$ zNHpQ@5+d(Ca>qQ2HXwR;Q029+(+7#Byn2Mpf0IJyzqbg9_kJOKuN6{0Hwh`%uL+s| zz9VG*`)?uR&_9IePJ3$b_Pr7O2673% zN&f*Q|7D`T#eSI69}|5q8O}W672nB1?8+WE%`kC__VblcucMvW$*pY-LH7 zs1ZddYqkt?B9uMLv6ZoeY=??Qgpkg4z0dEQ&!_YKT=)Opp66ZWooVLoq1&~uM+XG$ zMXcJpTa6zjU7t*S4)twr*FN^sev0uQ;}1LQI!@Sh{hZ03(C4^8@?=<8UKxH$uPf)% z`aaM4adW%Izvryi_e%SdUQe`t?|er8e%c<;`+!~x?w?=!^;C{r$@!43gWQ7L#p?O2 zU&9SOF9uRi!jW!2tIy@+8TcXXtF6Xww0d40A)h2)mfp`b{KM^7x5!!dX9f8yXFXm!?KXX$wU_j{!*0;m8GBHl z`-V!rA5@l}r+eyG_4{;Q zyG~!Hr9bCC?fjyCu0)>a+)>YCXU+4qv*t;+dQM!lnlD_}?Dz4!(*2%vR=+A%^=I9# z*IxrWR$nKquB)BvdT*O)^?tXT_DUmzdFn{d^NQ7ay{zV&;kw3eB<~;}AYaDYwz;l% zRM0=a^!Q5TI?kHE1?`FUsy=7gwR)aQf8RISS@&U@v##$GXN@bPd+mKxkbZok$kEQa zH|^|i`hLLb>&YN{P45p@kJl`FUC&edyWVfeSFG+u&Sa_g`65=2b7`ygMpln+YuYDU zjbALi-<8hV?`CK1_j_mU_mb7z+4WfX=jIjcWPP6@{rT(_+gZ;)w`-o)oi)!8XU#Lt zS@W#09rX1L_uEeT_g7Zq&)STzup9P+5!{pW>|NYpT`#|Hkcq=<|@X`X6@I{69Nu-0#jBmwBAjYp<8|&$~WxzNyb? z_LjbGS-l=kSgrq?)$<_Nc=@Lu2kH4sJ8S-$&RV~*v*vGS)xWFN_+8|~wyEBS?47W% zJJRDGILGR7o)F}GSV;PP_bGA(tU`NRaz|&4pJSWqbILnX>*uq|C9Kwql3uUAv-)?l zf9dl+?SpWb+qLcpt8pLFKG#{}Hqd^8_A|7Xem9uEymY@;>^*%RvD(Kg zBzcO}I;&{^%314Nw0fT1r#+`$quzH3t9{2x&(jLy-L8Ffvs&j(t9j>H?PCe;UrIl3 zQ=Rp^-RZ1(jymgk`>R#|+g9^re=jg=nEGYW^WQeo`#V04MQkR$-(yLeO5diz!KN6G{{2t)AB1CYI?l&c=yP)1e?OkWU+^!?u6yf#h45*77Gv;b?2bO4#^aK4 z8h(mj;%3~3C-Ex&g<+2b^X0;#SPtLD2{;|+;u1{7%lHR|We(0W6A<_%v3;>KKLo{ci6g2Ag9X zw!QN_j)rh1?S@z_$97K|NgwkeTRGT z5FW=fcnN)ehsWJS|K7cGc+SA=m!KsF2gmr5x3w@+>b}`B>s$7@OQk84>6}cpm|?K(SKLq+!+0L1tjpog#LR2_aA|CaS5)+?RW&Q;4KV)jPu0+61(C6`~uhERy>G5;cw`_bMU?&%@bGz%VBM7hHWts-@>uD09WG{Jb-8M20juI ztot~Y#X8smyI_ADgCF4MxDof_b-a(c^#MQhxMDSIf^D$}4#z3D8o$M(cnR-d=vti;4Iaj>Q?c05{-q zyo`UM|DMI`6~J;>8EfKm7>&)aCAPu#*cB78Hx9tjI02{N4EzW`!9}Ak`0^w>0pGyBI0%z) z6pqKqI2}L4dAJal;woH^U*k61h5PXcrsEmBh`(S4-o^)*sc>+gvg2b|0E=QIK8+Qz zI!0jwjKSs@hwZR4cE_IBABW;d9FJ3QCeFbHxCB>WDsIN@_&xgXr~Eug$Fq1Dui-7c zkD2s?8;{F@5m*R|V;QW7HSjrXgt6EP+hG?>#6CC(hhs9ni|^xXoQI2WIj+St+={#K z03O3rcpk4}2HwGkn5AfNpK@V-EQ%$u99F?v=)XVneU8Bv*akab0`|auI0Q%FIGl_# zFa_u17x*Qv$4waeJ2&lXFZmE2$1`{df5V%255u1bt}i?0!GicCmd0nWI@ZBxd>&uI zw%8e8!`?U$lW;V?gHv%9&c%he4AcQ+#kdZ);Xyo&zu;ZWsvqcj9|f=!Ho%V96Nh4^;=#B) zSP`pZ6gI#ZY>si*4m)Fa9EihkB#y&LI1OjxVqA`Ea4YV_eRvp;<4<@2uj23cC*H^K z62X1QhPg367Qqr&2A{!dSR3nO6MO+%VO#8kuVN2;6W_w&I2tG56r6z{;U~BVm*Hwm z#ZCAv?#2Un6i?t;yoA5v4ZMSY<0Fy5ea(S+@Ns+sOJZ59gf*}ZHpFK5BF1AU?2f%~ z01m@ZI04_o5Ab9B442|++<@QU4%~-F@C2U2|KfH06CdCsC4>9*DCWh&SOTBMN>~%? zVq<&(-5gzK^qU9xlS= zxE9lJEAGMrcnnYBdAy1lcn2S1meRp}%7yu{D3-)>SOsfgeT=~t*akab0`|auI0Q%F zIGl_#Fa_u17x*Qv$4&Sh?!`lxj_2?SW}yGx+MgrB$^>S|2rP_|SPrXV6h>n##$kI* zz@9h&lQ0=4;&e>G1-KN~U>a`2J$MMy@f=>k47`i}7vjDT*)akOVjY( z9uu%94!|T##)&u`Q*Z$;#Wk3Q+i(va!gM@`S1<$bVpv(OA0x0ZMq)XvicuJiu^5N# zF#&tx08GMUoQTsg1sC8_T!U%24fo(7OviJ01vBt2hLz*`F#-!?B$mUf7=_Uoi*eW< z6R;-^z$8q@i8vioZ~-pGHJFCma1S2BbUcSwFaz&mSb44=Bd{<=VmYjeQ5cP}7>6D3 zbsUIeaU#ya`M3_#a0~9hqj&<(;wAhQZ{S_bSs}R2(76VBy%!=siBF-=JMjBK6?_)! zVk3MWU&6N78540Bjzpi6;Q1%xr??oG;~Lz6n{hj);~Bh&zu+JE5FdReShpZPh1IbU z#$h+?ha+(seuiJ;EY#_JeXIantjmc|;`7+Yfk_Qz2;4_DyVxEIs$zxX%isKVon zWw18BfSqtSPQ;J!3rt0yE8*wualD8(F-z5;UI@!$T@0N=q4C|w192SA#wGY~+=IvQ zGX9B~s|D-k$5L1gqcIMBUWKotKTgF(n1)+%Kc2#0@Gs0>J(#aJR>0cW4BKOG9FCK4 zE-uB5xC?*4i+B_B)(F;*#9G)GTVYr1hm&v`&c?a;87{$9n2MWmJARKx@C^Qn_pory zV83Nir;mmnkEZBzKm7Q-fk`+S=iv(c8uwy4UdMZw?b%@7g7`E>VGOpx1RR3X@Kaol zX?Py*V5VBZdeyKgw!qfd9(_KEuX_`o#E9BKds(c5t?+G}gIn=5Ucl)vyV+!nwE&kKh@+fsfY-<}Yb8>Dvn|Z|m##obg3$V|CqK$Zz6c+DBN;lZ@l3 zPoh4Z_F0%h{WIz-$ZKr0&U2!Dzty~l@R-&9Lg%AsKcRC`Zkpbv>I2*YFssZmiqJ9 z7CTw>?_t%y5B8@%2B+a#+-Nm!yVbbexQ}}1oEYC%@(rv0f78!<^|&ln{}jS9SlQ}v ziosWCPryF3kHqP;&%w{E*89?Gowb-seGB!y$!%1SpD-ixoBf$tz8l8TJ?`1$CJB~`;(J!48BJ_h3xZ+Jnt9e z)tH9g;(x6AUBc_MKfo+ag8k&O>i0Oggw-{awV8Ad2v(uq1lwSD9Dt+oef$I$TFtu- zzoGp*@&WP@@~`Ck7#0)kGmF(c5mxu}N%BjWi0|M`oQq5FM?7zJotM$)DtX?U)I;Yh zDd%b$v=_w+=yR65pXbO8$<4{F$Q{Yu$i2x)IFj~BxQ=$8!{q(!r2P>22l6@cC9B8r zE;&;(WnEWR44vbodL?IB%WB@%*b!gDzBmL&S zk$ML0x9~3YT(KIb`%h&h?}j} z_jy)s-%mbHzJ$Nfeh;&}5cJPwHNLRbI>j)OdKC2+ur2it*u`qyA=D?}RO&NuwpG70 z>f6ajF`f2{cniat2m8v5*{$ZuYkl9zCCL@Z&9NhPqu!g`pF9euVhZ(7$V~cN_i3MPHSaR=M*P;Q|4uw* z)i1oI{?WQQtm?Tjuhl+^TlFhz)vpP5!hhkr_yNwx6}S<%x$BV&wMR6#O zwc6)9IN55SpWsT|jQi2&c6tAybGy{v=XN>Y!z?ca^E_(R{y4cjISQN5-Wt2%n>fg7 z{7CXtoJspatNXc;{2le(R@dco!0b=7Unc*8ckn)DZxzf})atrQlcVtk+S_0!OvE>F zD2~R7I0HY%MYtBf#_hPr>iT{lpCSK=kHiJ_0$9pw-&L`$)%7<-pKIp%-mto_gJ>U$ zZ(EIDLwz&t+i(Z_|4(88-IjqJ%f#tD@)p{+g_R|VqrrraG;k!5+KeihGIe9rb zmAoB~;tA?MTdj8quTuXTbGK35`^8ABb)F&D#TM9_dKasCU&Ys{564M32bbYS+>QIK z);neOxLl|Gmeu@sG5qDAUoNZt7Q+fy)oOfmax1HOeg2#K55ZwzW>`Fo+q1C&PRTVT$x;x9Bnmk48~ILjIUbFGZ05w z^&f*1tk!#<`W*67JWBf+@}K1Jw!u6;$IkQRu$m{I)p}2oOOY#)>thS-h5f9?jl_wx z&m(__r||(6Zx@Vv25VdGr!F?M+SkkY8Vt1gy@vQAwz2Bp9p9vV5P2kdEO{z<9)4!E&gZz?YQ9wJ z-;noGKY)j+U%(r9+iHB)j)8ft_Fa%%lKeEeI@YJXCAPNOS6l38HSg=x`;wEWkHBQ= zlc>)kFT$m?e??9s@4a4(rTvjk!S&?Fr?8yW{%Vk;$W6%cyV$vE;t0oU<&TR zV^;f5$J18(xsDGoyi2fNE~|Q8axrpAaz%1Aa(#@Y{Y7#I9D>uR&mzw!FD9=huP1LM z?;szux(`2*ui`CRU+2(t4a{M6y}7ZV)qN~$HNGObw$-?Lw8xPX@O7(k1IRVhl8`K|rHCVTZ)xL|9%abdU>yR6en`1kx{dB}$R`c|u zKAik6`2(x|AK_f;i>a?BuP1LMAHbjRJoSGtXLrrpNbloT>lY)Jvzhcf$EsHKI#&H- z$ZgQ)l)Ak;xd(X=c^G*t`Cal%@+$m__ATV?kVEISYM$`dgZax^;0tRH&*-FLq0%GCtt>2X}?XrPtMvSm@l{0JVmV5dlE}huYplk{hE+t z$uE=JlV2kb#G$m0A-_YOLH>xGiU;rnUc!7mgY}DB?XwgY=BQP1q<3xN9r{gS4!Fjj<3tL@OF>>g7m7~a^>rwvy z^@R4P{Qv!h)>Z!hx{H}_DdTsL_mD4=uaF;*L+7^X@hs-YSMx>kIM*ack>knj$$iNK z$nTM-lUI`0koS`hk$)p+kR!AQuV29GpPJ+-ay+>`c`!MNJd2z{UQbRVA0wxe?~)&o zBOYOWtG3X&Y}!vnat!rYaw54WIhj13ynwuzoJQVEK14o7&LH0+M`UI{R{N<+u1Ss~ z$CC$>lgP8kDdhF!H1aWWI{6m)F1bLKVEw{Y>(?Ylk>knj$%DyByXOTVFr9COM8APaZ%Ho!6%R)5)`_FD0)eZzJy@pCex+hh+=a&ulecB)K#> injAw;ASaTO$>Yfj$cxEo$5(okJjR^V%4g>SEVhj;-g}%R@7EouWwtak5;R-RBJ8TTkrSnvrcjnnA`q;^ZT9i z?X~vWYp=ET+K+RRoZq>0kzp9h{TRxpij-1&Tb!Di8YZiH6?8>4uDa}<)8G5Y7himF z<&KGD{J){yC`hpOg5HDcIb6GNZO63@*EP5{<4WV=XDzNSTphUDaW&zp!F8aIG2ECi ztTx~qHg?!>V}wyNL@9Hm@(nvGFek92Rw>_j6$l)IdZjEW`jx71ib@SR2-Qke5-9Gk zHGIPY0k$?k+Cv>x6-#PoRVh{FYE~*BHE6|}YQtDk%N9cqQA=vupmNwm6qGtBs3ujz z{GxauFf>pdV58x+MzO0Ag`O*@r&hW`&q~#ywI4Q#8Ns4eMP(z4GDYU7TG&4q{ntxZ zTK8z$M7?8z1`F(OY=t(rfgI8Yw;~V>!=!4)wPOgG<0>3G;Is+*8$n8-Nj4RmEU7Iv zI;2&k*pd+$7Wi`(%Xgju=Hjno**nvu5UYR-zEaOECqj40(K9KC%C+T5cVnOOf zCXUale3)SPZ^4N8%t~vhW==#~pE2YkwDy@5--ZIqs)#3Z@UEi15=?((zYj|8V|i8> zD$GAp_R5R2(hA&_`2uxal|r$?sx-H;{(9CAu_~>*f#_f~v++BSv!*`+j=vICTxYeM z4q(v<w8KhyNT%RaZQ~Fa+ME z;SV|yQGq=e;EIQwfLMWRAyBc)8DYPwv@Ql+X)zP3@5YVp4E+WQE@poc)>imaZgmPd8#??R3NheqdNBol{ zxdLO5T>i;oSKukA@K0eQv$?va2|E0Taq?J3quE?j^9F^dI*f5(z?5;6-HHDFEi4YN zv12c>&mCady>6eo(9rI4`#ckq#_o6G><|1NakAr%1=Y&jUJ3Hd8=zyvPFiXYGlwCr zwpMtMDH?5BYS-v0v)O_nZ=yx*JBW!r++?}Zx|}*LhPp0$u9;<@PtlB{%_ivMJZq+o zV}!Koaw%mWE0n)35>a-CP}OxkB1Kx!K%de@?5G3AxZdpDrvHa&hoBhW#Y7FxX3j2UB2$a4_0S5mF9qrB#Rc z)#fl;?3Lz3lt=s+9ar0{%_kV-N7(LUF-qCvICyJ>w48A}MN68^oCuerP3`;a{Zy0X z5vyQ!y?uuHHTwEGqZ2YOg6$l!moNwHwL)6<^ArgS>9=$2xkt!q`)T?g5wa%u1cjqT z59@-5Q9f4mur8=GqE|Qvo6U72qp2J+S2zviL^4QTVT=Vs)vl)Xar0$be|Zi!8>Q`J`Lip?xX)z0zE%M{BXYj1j-u3}_>l25;g-zt)MI zg-~_{yD4y;!|{zKCxEk=eZ9jmN0D1NH9!bs|M&=vB36isw9&Hs)9XZn(uA78Y ztM#z=ZwqGxIh7opn}su+oD1pBt-`4xCqX^;3g;klb}(Gqg)@vCF3k4#g)@|#b2*eh z6izicH_+1^!U=$b%zp;`S6WQ-N{jU)&Oo!Z65ZhY?D+wwMF3u^;9DH?heZdxRKY6t z^Aq8~OXWo35#hi~75p+2ahGu5r3yYz4;~c`yi`uKekvSzse-kP@ngb)mn!(5jLpx4 z125IcR3fVE$AtqgRd5q+enL3#QUwp@$oyP5Rph)$d!7`IP0k9A%x>ZM$w60Gtc6oa z&Wr5*Y2geZ=VC_m8R1lr(@)L65ROI8bdJm~h2tZqgE4$oI3_u>DD#5Dsla@;g3r+A z7ah(JMBWPCLC#Ck3X!*hA@=pEa1ePbcr7h_O*n|W6k5`CHW^IC)*=v$%jHtv)9p#KMUDz?`GWg3OTbbmRzswznIhYyr1PP zAs?Av(&St_#)B8U4BhZ1_yx4AMNBhLVrS>S2|B!8|%bv>7 zQ9j4tZs!nS`EJ+2Sz}jIRi*C^O`e8n^lJ>usKY_x7&IEz)SgYRer$4j;asIB+ywAP z(1-@HB6ug$w%S+N`&95B>~^Sdu=lCpy&Uji!okj30_BkwRA6FEIs130Y%* zlPOT|J5EOz`vg^u7P1~OIGRyeNB8_bMyt}A1JO!r2in!w*q8fmCu(_xH~#8pn$eVD`q|_ z^J2uWYU-6*^ja;-%DX9AkQ&S6RA!o9w%o5pe^Lt*>Z-H?#ox`zS!W ziZ^8*jf$#v>mZt6h5HzTy^TRhcdN|R81$;?6STn8f0eMVYZHIc7$yIoFy?Ej zmfklU&p3PN^fI=?tPLDV!x7j=^@C!N`I!aS>1F=d_ zYneAV>jmy*yB?0d*}O3D3F~?}a#+Lz5737`juM^|0w1!!ehvu^I)Q1V;*7u9+^x)q z>EM~`LHb9+=F_UqdY`epl-^{VbzTLIp-`4VMl99A?;#9E9DQJ6;SHab5qJgFn^s0Y zbIjbL#^u6&ptOc9*0@}XbsTVWi(ef)AC4JO1HCG~Pnd?Q8yXsCp(7*09EJ*Y@HyZc zA)^T}1=ku}=TK}b^cZL8=SGM%9gQxHReIXBLu59t3vunDO<`qpJKd_ryTCNM#iYh< zaM9>yhS8*^u{5bmuXY{aEy1-Nm&JE$bZoinSP#mMMyv5dHd^jzgpL?uYn-4B=|bC6 zaJ`PJ4LTY_4BGKdcd+@(Bo}GXwGfHp@*|=-b_bg~U7NL)olY~W@hW!ES?KRK2$V5T z+nk1ijksn)$=y^kkVX7E^v1JAH9p4fIyj%rEtYCpL~^cfxEYNu!?hL-Kcb;8BL$5) z(*L+D%3N5`%yD6kGdl2g4_X;t(k@(s;*GejfReFwjtfVM3e~imk)EMnRc(V1hv9w* zuB9NJ@{Q>-lH($g0%48gGrn7e-p*&JPt_)KTz2Am8%nOHk^yC$;xYIXF<3R-LO)w{ zqg`mQ8&?ft@RT%~=4mvo&}c8yX^L+292&fWYc3j%!W&Kw&16p^Oy+io(2RqrlO1LL zaZ!}HIhtFl)ge=DC>yVp?SZ2AaP>pkp?nW*G#YzB@56N+c+J1T=vrI&ipnsW3D(yg zV*GfH$-qxB0gVd80iTud-Bcf;WEh_h8;ZOB76e?QwNN-gi4ko!pR{$fFix0${`b=+R){Ge_ zL)$<;mvc&mE*%nY?$80=;=ZelV;X&%9&m5@LaE3*P-zn7R^av{w_3IwqRdhu=0 z7lty<^;cWgr7#4^Qutsr)x2T;i_G~$D_lO?9EjgE2)}(0e#apEu0i-~2jQm&;cp&< zf6XBLZG-T)55nIy2>-c3_S+lKS00brJBSt1rR zElV7&%SG8H(1&PV<EDWj}F>E*E9nK~Hz;E#l!$*-xCU%SG7^(DO7eXAu`TWj}F= zE*E9HK%eB)Tf~)4*-t!0my5D%L5DRjXAvV#*-wn?a#1!7`Yfm3B4(YkpSV$%i?W+R ze?{|h7V)c2*-yMomy5F3fZpQNTf}RfvY&XPE*E9Dfxboaau)Gcr|c)*rOQRx?V!K! z)LX~o-h<{ z7dNh!@}WNWlSn1|n)r2CHs5n*ERqXF`oqb-SX70w{i#f@C*P}jGpPX;TCzNpNJZ9# zaw?q5g(LmxTt>R>%_k$FY`iZS8i-}H;l3DTD2}$FSTd^8;S6>G$3!g~PsVeQDK$Et zT%TGO3-!fv>tfgzM3u_KBC+^-*wdQ`_hq%-vorBrOl!_3*=;PU9Z1GDJi8!3iv;^}w{aR@mbNjOwI8;VDhUhCI~6LG{D+f=$g z6VB4xa5S2M>jj^jhzwvCLJ;DKXeg`8P#@2sI~5uTXV%3sS#%ptgxHk?H55tZVM88T zqw#E7=`qmW#gf{SSTuz3i6&wh<>*`=%fx#(hO!7Wc)jsNEEyh%sdOf`UiD*hOsZ%Y z(L#Mrwe_b4Vr|KIUw{J@Ig|CB3e%ja#F0OZA-DQo6slq{F#LKSm%E>rJLq zIFiG7s7?K;JRAt8(}{Q_oQtQD1;aceE!L%yjMC!Hc?&yNctd%B){IU%l~vJD!55D{ zW_M|#Kpw||RNhIsYRDl-t$1ES}dzLg|xX&?I!vd8yqEGNSZ zpV4#7nGHSR$U3BY4>D2hA08D-_4cAAoI)NdJVRk_hf>MJM(;Q1sNR0gJE-QiF=@!&x*sVJyIdU%>Hwd0~LvJ?aSz3@kko- z%;J(+hR)WfN|u1K94KbJ%EboKy;uQr{R%0!DW*Mi*U7SGGWvzu4Ls47$sAzDU|vQu z;j_K5*)NY^a#^Nrz`$X(=UN-$0`D2FP$HgX!h|zes8Tr6mo{~G7baV|$=O_ZAg#bn zA@F@(lX@|?bY}=&JR8UO>alVbLdC@{5ymp+Y(nm8cvc>3ZEsvMU5_ib9js_!HE-d< z6`dg7#k)8R-=AN#eZiC)IJC%RE*q-V~$20M9%TygdiJ$bn9bK}EvE^@s%U%5F( zW7$Y1p60|?X)N4&{xjF~f}@)|=^oO%gIchBS$F5MZq<)e#Io#}m$ER-U%v1Z6~R6g zPG`|4-nYjRDU3F=lu=-|hulELGsSIr{;EZbu!x32h)opECgKCw4Wr&rv$y?LD~NW@ zTQTp%&Th1Jrh&WFhOn7Mr$Z%Rh69H?Fw=n}oM@CRT)lc#;}l^~u)XW$(H%c`v{g11 z&dBD04OXJlxomak(&b&9+&#E&?PvWUBL*L`SXJR1*0M~@v%crCToi19*m28NH7#h; z52iTSaKvK8ZjjR@@;v(Jsm8-YG@g+YKwl=6#}4eac26+wA*=itpkxn8hvOv&qXSG6 z7+6@R;6Kk8Oh_!uIG!OQ^%bY(O7~%Y$Hhq}gYTTPFqEew%yld}a(2|y3XbdLsF&M{gcuFn%>lD6 z6Yt6A$``3Z0`jb>^vM;u7|G-4xDf??SPJ0_PFD~6T(o3qXZbuT+3es#=~7s}4fLe2 zg;fa2Y+}KOJf1d=6GUs&O`%YoI>&$uH&9v zcC&1Ed z7-ZGbJ1I{U>#>ewLsOhlg~O@mkWrp%&S6dIwA_@6MD!Gq=aU(Z-$-rbG@cp~`GKU` zG=O(PG}; zA#FKgima%rHM?;DXEb0g<6ysA%ES__IX;QCvZU9u)}Ab~1y39KzEHTQhfgL>rRKzw zy(urvldYHT=Az?fDeWmrGNG_5u0nK;>yp zQQw=SJOSv{caujS+q(MNP^Mm2-%aey^Kqa4XM*RgqTHW647a$bOztu$=GzAMu(S0y!zgTJ~pI2yfH86%Q|e_ozL4C$X(8h6U}f{UjWK2v*NaK&bLik$WwP7 z$|e0SEc$_OKMMWc;Aw-RdJg)USdfp~*VjRN^?d++%sKi&bmMY6%52k)i=VyFH;Ns~ zhjqNR3kq9Rw&3eAm+;i>^psgW9&+A~Yu|7%-P~h6<#u}nT{)sBtZMsoFwk%mfOCv~ z&>#Bh)wdmqyUxRK^+BxU=w`yqXF8QoPzC(7sx%II&E(f5?m50%kRm(j16 z(eIVfUzE}Ome~E!{%K|OyfS)~(A+DABO=a*exNg0$wvP#kLP6vgOanzf$QAI$I=tU zpogFmbM|{YE$iX{$Ko=H@;48qRums$O8K5MVQB>qg@qR{rB#JTiBh&0;CUfiT7RH7 zHKh_Ihp*DA{hrCns>@zK{d-RZlqwxp562x%vIZMN*6lxX~A@Iy_d;JTJOT<|Etd4gI$^eh*8wO~|`2X*$7 z7SzAu0ez{^R|;+w+%CwtvfVDhX9Qmp(_@3b31uGFd%8wMBAUIQSf#3?kuwYtnv*0Cy{BIKV-6D9e zpn>g!{A$5Q!Ks3?1&-6^>+(CD7ahjWx=-u_X>U?7_^-BlLTi9 zE)e{(;1z;f1-~b_Q}9W_mjr(=_=%u}9HyPMf`?Bje>Uy-Y57A z!B+%-FZhX|g^8s57d%vOy5IuARf3lbenap!!5<3#RPa}Vdj$V1_)o#1n2YSUL2#@Iyg`=Uehe2#yy#QgE^0 zse=5I3FXfdyhiXlg8c6f>z@#OS?~{ne-o_011sg~1e*nC2+kAi5)26@1+Ng?D)>FY zoq|saz9h(h?yA-tx+x|_!Yrx1#cI;PjI*3Yl8g$E!*!C z^y4vtH2*t5oG3U~@N~h1;5mX{6a1FocLn)xRqA2|?6f@=i7DtM3Jvx1)q zj>Yd{*?y5=MDQxX9|^uD_;Q-&3mzx9N-!dLmf-n%v z`dfs5yWm|?|FqP08!xUAkg085>br-(1;gKD=NovPW zCzG-6KDO4(pJ*DzcmLzp4?mX|5R26U^u06PJ#I+OGHe6|38*z2w zT8xXIW(V}W-c$A#jbX;bA=Lrjkh&qmjNwMrAf?O^$~RdV54ExMzO2mg`Uf(r&_u~&q~#xwI4Q#8Ns4e zMP(z3GDYUdYS_O3{ntuYTK6d0M7^Vf1`F)3u1uRdh8)s|G)WLAS2C`P5!XYDtoCY` zIkpJ_W4K&7Hm)x#jDQJ0#}#GVhLjo)DSCwvQmUb)&}dO5ZJyv|P(nRhgVEKaZyCEW zjK(Nr)^jq|UXipgyDUikn#tp{%5NbU{;e1hpILq%)Png%IhliQC1sYK4F#4}7Ek72 zPuU0X)aNfh#s?)AQ*K@uD$MICyW>2qvj8Z~qW3m5mg# z(teS`wL(_eZ@{^-Q9{<(S5fn5A#3dfIxVXca*TaEYsUy#Zx4ryWrqqm!M+i0myH#2 zioF|_memV6-CmDKm5n!k2CmuAY#Z>bY=ZHKCR=PDjhrMN&9fJ=_AntA*#Aj0rW;$e zgNyBztZgW%vh7TxLzBzwQ8aRvv0rOmZa>JjbB$Ltxx#*gMlLe8YvB(2Rl2ak z;7FSdYwb5kwhOu5euw1ILY`!QK=K$NH`@X(kwoyC4z^)XVd+k0N*=hVv_nS}^ zQ)t#b{?(AGEW4j!2s}c=A8;a~0(&_UKXn3P1vW#VY@aj2epPOL3v{`~OsL$A8{HYq z!6KJAp}8Np+{xg63}Ogn%PpfVIp(<;-NG=hw%6H-%Gu%LXNTXtZfs^>uv6U_A((S*kO{(g`8qPPZL)NIonfh zEonAzB3y(v)ep1x6HS(fSHtXD`(*Rm^z|V|CuE)n+c{$QV-DCGg|zG+QY0*--#(T- zcL`Z(pGE&8LRJN@qj0q7VNK9S`B>4znxM{zZs8naHq?xWrgF$!;fx_Cl0otcqYeyJ z-AL=>=F7Bx60&)%oiO(?JePoD_Z33%8hOb=C>S+6r6myx`wQBamfA{t3FCIEkX7~$ z+L{q(YV3dGlsL^)5HcHT?MJCNa{?o{ga*JtRZe5A{@HuF4QUzaNUrz|9f}Fjy=Skt%=%xo9CW4ZUkIn1oIBY2Q^FZU&IbDav~bGESwzjx2*)C)hF&}?93MGj8N=sK0R$p!WaT=xDZ3(R8sn{4~BkgfJOy6}m~n3@eM>_4!h z&&0tF`zezDBim9ZHh+-H=lHwUIRsd~TXb;N+i!9d%6;G07p)9K%Ehhx@~(@hhrMFvYAmU%{~#^*%HvY+C(1%>oG z3-kyfEA9K40waa2vQKA^wLTu5us7NLR5eP-TEyT;9TmFg_c2=K))5dbx9&l^+A8}Z zpI(7)=ak&;J63DKQbuxzkd{4>1A4K9-EVJamzT&GRjO)}F7EWLVPihKRgA5L2WBf; zRn$MAd;2-=qnxAl6VP2T{zc7x8TZke{V7Uy?7mKym|1mSfP|&wmRma4*1?a8i9_%_ zk3$LWPTQ#{)#(;2p^7eo-@$3kV^fZ?c^+NCRd zad&i{Lji4%R?K`<<_5&CV%iQZdYKkwLGDyE zy`lwvrv=FWi~_W)cvI$)sHkYRhSK~B+(#SiZ8S={TV*z4&?{z6)B@8A0&T807lK)YR`TB~Edxzl}XD^*z$#$5vfx~Fns#}KQo+}s&{Sn$ zJmb2Wuc7b^6}X7@u9=~!nm{9SYAq83=ej_YI@d7^%!V<6i{VGbaU3ACp+4|u_HaDI zY&J{?bg^#zCT+`Yp8#sU@X?nn;~*I zu5aQx2cqM<)5=)H)P>~uE|i%!<}R!L1?pa;jojr|<4%P!#>sm2Ek@gRTzhamK^X0?k5>BI#GK9uHWE#pZ4+*)95PLyN~vspzYlVkvJ|s zo=@hxv%YMPGS=%Qf0wGiih)_rnS|cdxcM}4t!|h`qkdd1XqZ65`a3ZA#u_nmd=_O+ zX&SkPt=2fb!_z0x%2=g6-G<_YxHdw`73>|Jt`rq&+`rT6qxDOooe;Vj*LDcLNgZ;Rw5V&1z1izX+NzlxV2%#AdQ=1)S{_#46>UuSq#JwEJ$G^!Z#S?7F_}Om5W1zuFrHw=FOUgGPL#Ob2+C}=+GfCtI+}8l1?-h zKGm>prf=jq3&;Al-jCZMxIGBWlhB;vEnUh>fi%kyHT}H;z9IS2P{tYlO3S(conu4` zA6TfC4Dp|59yPek{V2jOo#2tR!g{$X?69`rcP z%UQ$*r|c(A)#akzX3#U8dW$&QDf@|s>vB>Mi0L zr|c)5pvy(sjiAGtm$Qfwr|c)jb-5^;27RhiZxORj*-z}(<)Z91&}VC2&LW=cl>NjD zb-5_J6Z9^p-XdP+l>Nl3b-5^eBj}qnFJ}>NcFKO@ZMs~P-2?hgr`{so?Uen*y}DeK z-3R*TnwPVPk2qyNalbAXWuFKAf>Uo1f9aI{#8-5=C_72hxTzO0RUg8o7mpBDs}NSJ zkY24=t;XQe%Lvyc`B0ntNu-iJ_55Ndo9{X$7RiMoz2Rg}EUH4;-c%;nmG4&FnN*(& zwXX^#QjtxeoC@c1;Ye>fmyu4p^T|jk8}CVm`eNB^xF-e~ilc2PmW--&ID^&JF;L6K zlkps6L|SEHkyv~)y6jGbd$KATi=}n@(=zc~Ol!y|sXi9fh9+ZM&^8=Tgt}9SMC!DB zI)pv6)PJuvDxM5wV(COb#n4wg9go4^kkgyEt>W2GJepMDXfy*SU|mzwjKYFkvIBS= z$@XDMhoA98G~|?_Ii5pLD%2OwY>H*F=rNoKu@{M3D3Z#f`+PPQipH~PrNgWpizT({ zSTuwoh$dng<>=fT%f!3;Ls`TUyzY1+mJIjBR5}yeta`E2BvmwwK%qXTX7r}|Vl$HQ zp59z4k(v>Wb;ZNU#`LD18Qf=_TdM1n#?q~_F&)lDdNBf-Sa&j|!jT-tLv8I%<>5d$ zole9f;aohGEEwjAfmoMHa@be2Eop6A?H%i{XwB%PQyAz_!55D{rf)pCIkhPk>WSqx z#rioI*jrP1C#$mI%}!DzQgq#E>E=CSge*+vRaZEQBv8@3V?2!O#YjYv4AIyY{Y6oxRW96v=^IKV6a5F+9nWEQi9N_%wK<%~ z$1oF^QYp!{QtuFqY%f!-JHAEt-518dU{pfRDu7s{W1f^kdTK*s97|9*n@#tkDRUwl z-|9e5QiV3>!d;1&Yq1!f%fw<{B~IFVMn96uz)UPD96~1!JZ&Wv=bsAc6`?fD#Yl=< z2ToFsTqMTzE~BGYbmA+f9sJmwD)DSUaEsGGo1yHA_G=?O^VBt%f%a@2dcts-=YEFALF9OGj&je7#*|-*>*qS0S2$v^VmHX% z5_z6z^lai;AsWxfhToG(<+1C!t=)r(yMqi|z?AG8>2SQ{yz>>)1O^t?D4u(8q+mi~ zG1i&gCwnZ8LtHeq%a}Uuq=?26JSkyk&mpxkv1lfI8X}2#k%{HQhK)yXCv`Alw+U8`6h#}MYAxJXClmYEHH8?)DsK(*jjaSLy;h( zfx9(e-euxl`P{(8u#kd0L@IqGMK(tAI4ky}ppQr)d^n8E|hK` z1K0Yl6c!yGBI5|qS5Cx%`oChIL@&uyB!w@DbXpeX9d{sS+5K0cR^4fAdfjP#7RvH$ zjukAINx3_{-h#b5yriUak}jUuWvXP;u}D^}S-WIy8#5w?yo_K`hKV_5=$23-+=Z+x z9G(X*V4fXiK)~2T6NBf$!P=X@@ zbvVa=9Vy}P>7>38L$2niMRa0Y(s9flmCW~rdgFLggG0T3V8QV}ha(+zaKGP-Vv3K%a<;lUq7W)pXQzQuW`;)SqN2Aw!aU@ zDqt?-V6R)s#1c(8J})(~q?e(lu54B{;lUu^6AE{A@gc&g)SP&-JLRQ$2=&t4T%g?M zcpmiDrSo0fJ)m88=Jb%^8dK;HcB!UFs!tyqo06$qtO;v+BhD9*P3{xv{{_cF$iRg+ zwfeIdckfeemBUtbKwHX$6?2r@2poZn?fFd17cx_Y_5t~+N99RQ(V?Y05$M(T1L#YG zM}2JT>YITw^}71bU}v6>`z+o9p0|o}fAKKf;<5p9aVX}Kzx#3JjsnALU+r9_dhr5} z_Tj6Ef_=xK?6yHs9f6llD?ALhxEgg{ecKj0eo-I!uD{(VyKPWZ-yEe>)WdN7?LwVb z-vx`6dL2CK!?zg)eOZ(}&DA@2A=c}>#z0N6?i^2<{LVv^I*bMRxH`@R?d`XBNzo6y z+b{HcCCY9as@MvB^(@H8t-BPoS6>?Xm~-@l=*Hz1l-Z^k7eCiPAHNH8Kdj@mN6_Uj znugyOyM(81ucyrFlOX5)P!~VLaJjihnsWPDkdG@z^n_KtgT%cNjFI58fBHdx=&M)X z1+(xQbx%WAAH+&NUcRM1`qEqJD~UAqdwU?wH>SmpuQ1yko=<1Ax8BxvljFQ=H58_& zwx92?P4u@GSdWYTkWK?RHZHvr<;5QQc9c6k^b;s=^w7UUnL6C|e@A(nhpt8dsMD=K z4D^j2`e@L5Jahu|J`a69=;u8&iiM9)&zJ&g}VmO&kms989;wFfFA708S3MAzV3(g;REQ70kn4wpge!G;C@J7H-P?; z&|J%h!6RqGJ>W~7(rtLaS!Tc{eZZ-@v~kI?VL;OZp56x34}9z{)$BP(4XkiqdX@4$ zhpEyEo~8(Sz7^;PZO8uBPNvX$(la=}vaf-9v8<;aZ zyAbgWzedh2(mZky`5hIJ-!2gA1<{43p-Llvd%*f;!FhtMf`f=<(hv4{?pp>hD2QW( zZqL1ldf*y<#HJKX*K)H3=L;?oTp_qh@HoM!;3mPeAb%gmelHN*A$YCe9zn*9a{C0I z7JN7i5nL*`S}-h_7ThLyzTjnoHwoS$XkdwDKb3-G1*ZufF1TE9onS;TC%9ek z2EpBe4+!oTd|B{KLH?qM{eLMKv>bY}V2j{VLH=Nz^4kTk739B($lojYq~J?}Zwr1b zXd#CwUoD6~ZfSa^;9|j5f?>gJg4+eJ7W{#r{y7BnJ|pxif^Q3cENEdO>HY=B3(gc= zD!5LNe;c9vRf69Wyj$>L!50Ky7vx{R*zTW#gE1FLj}e?EIA5?`aJ^uU;CX_V3*Ibv zm*As3j>M6IlLQwC zZV*feo-X)p!D|F>6}(gMNkI!oZ|ZLrJVJ22;JJdg3qB|KxnLcBGsyPK1S5hM3;tN} zHNn3Nj>1OGc8dhVf(gOX1kV-RC3u72Zovlx_Y1xx_?F<`1PyH1>~E;xA%fEc4;Nf6 zxK1!4c&gx8f;$AS6}(OGKEX!>pA-D8;GYHmM#Nt9so+0|e3-?f4($vOQ9o3$nuz*Z zsUIu+2EoZv-z@cu1do>bm4d5@(36w;a|JJ!`b!0`Btq^#q<*j9lY-9?Vc#zWUm`;O zb*cYA@N=pEr=VHw$c-Yx&nbeliO}~o!6S&!*DCcV3-$?aAwvEP!EHpyUn%uB3I7(s z+ob+AsefDe?+Lyy^;I}H(ylrp^p6$9|HQQZHmUCv{#wEHQh%w`UoHIW1aFf1Tc!SP z!F__y5T`2j1M-2LStK2{8y=qn5J6K{{jsx BS5N=| literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/crypt-mod-smime-classic.o b/obj-i486-linux-gnu-patched/crypt-mod-smime-classic.o new file mode 100644 index 0000000000000000000000000000000000000000..4fd900abc0508e7e9b25eb659c07e9491d01ff2b GIT binary patch literal 16248 zcmdU0dw5jUwcqE=88RmmAdn0M!ebzSLCFIM77&$JfYeAL1jPpqlbJ~}GMO3Yfk5pQ z?X}ek78I@4UbVFr+pk!9#rmq1Y87d%ezmRd+Naglwp#0>+6VXd+h?7b$pByP{qvsh zJLk98+H0@9*4k@7&dKDm_RbZCVJP=9lt&dQrQSW!scF;DsOnU}71g-z>en{>{vSt< z9NBqb1{wcvXx9tVDeMQ_j(ZpG?YMcRac{)kje9Zfe|NP)Ac(tK1dUO~^bs|F&xraF zqm0o;^)RK(G0HPyq5l+rM~zaRY0B?E4fRS{QuHb1b&5(28;NSADhL$!)fk=;em`3q zAnoCfDsM;4{7R)NUCm1Qr3S57Q)L((HEc0_it4CofyxmxP*7@QK%GzpbBp4B|8Rem zpN&S<7{#te7kc(mPmOeio|URaYaeV9GXh1cips_mWs1zPHL!mX`md9&wC-`ViF(He z3>Mg5y;qw%fgI8kn-K_x;e;y2b@4DVCwU8zHDUkcqD)6kQ7Q;2T8q$7YD%*-Vpooo zQd5gem(|c#P=0z9ZJt)jpeA)uEk;)lyk*>sVKf$C8u=x=9*~SM(-x$jW1@JhikAt7 zZyrX(V^&-XwO~G1LFTY9DbxEflvtKGp3K2+@8ifIkFR2p2TG!pn;(V>^IXdAyizOm z;;GE_!@;>Wg`(H0Fl$+V1M7!b71ll=I=BOp<_ySLvmXJ+cNk9Wv6?P}#da-v^;R3_ zfp0b_yB^(o1IAuWTJ{VZD zm?qooN*XysJeqH}!Ef)0LN2l&rWv!0ZQ8-b_A=JC8mDP;xqS)S&NezVxxyYt7v>m; zwdR%fUba2icu|w9?0aeC>BbH%+-dK}D0x>IcWSc7zK>*wkn8R5lKi-k7ub)JJVVHh z_6+vhX-wB`qxM}GFz;%ydBEGUm{I^2Dd(atSpQ^Av4Z6Z&CRFXigYFFfJPPD8Cp7mhmwN)Z?|~RW*$PXmxe5^< zcAj=Tj)AK<^9!gOX;fHa5E9=83{S0Z>Xj(_e}QV>jJ>EvcKJ8K5#I?8W%+-OspD%D zyZmoJ#y69V%!aD!v!TOxA}5b!Og0;;s}CR(eJ44LNnpT~Nt9j54w_gTRc*(fXP=E= z*?n%Gw<1b*zuRXYse$R*9-n_3;$+7i3#yd4p#tPZH$ungMYPl&VU9ptZLM&mDH?5B zYFFzjv%!KPzebCi9>l~RWwKmhT|*snp|0CrWMa3oJa=AD~x(DRE>w$$ITaL{a;{1kDV|NGCT~uJy;0E zA@Y)iP%vtCN=qUX_D^VET57B8IS93Vv5?jFPWqM+XKL+FGpd)E3PNT>oqdq1wg?%t z|HPiMQ{Mv~LWzV-`e1UX*X^DW^FCub%T;vV5tkyFXRJs=!E zILQ2`;C+R~G_SC3#B;PC%{EGO1N+$XgH8)Syi|chwD)1r0WVeHK5G50aNwnKBJqfD z;H3(j!lXMW9C)b$OX?6Rk&u120vefj&JZ9C)b$f2N-A3kP1RF{wmU*^dhc zUaCMBZGJ*H@KOc#vadtJsU+u4>UmN)HaYLJ)nVcI$iXlu`v=0QAm=)c%nyY#jGT{{ zJ5LG6OU?{x{*iDja=MxLPYcIGP7`DJjBreH&Y{fD9F7m}hJ@>XCeEqqxxh`beepQH1ta1eRR$%|hJ2a&e|gVg+M;UMys{Y^&f zH|BIbhkSM=)BiP@QdPEMFRz=?Dv=MZ3d z?$p6qZ$Cp-6`sACya3baSun=V1&L$OIB2Sw#`u2Q^`eJU`>u0{w4I|C*SIU|LGv1Av*$>m0fRH|CfgU4dmHj>wWUP?bC)i`1XQhsAt$h|% zjT5pC-k-{-Y-Ut_9!9IeIt8K?)&aDutG2K4+zir=)5;y5Gqo1%StNG~Y1wl*pw~*+ zefF*F@^dmqRjTG;O7HTlW#bP}uAE#456m@aRT+Fp_x3$J$2mvqD=0DbSv=3xW*);)IkQ(+4&dqNyn+JS9<7-9sLbVvU*$fk zxA7?HZk6f9pjXbGt_4mi2(-Hby2pCQg=ew$R?h9#qG#hd!RVzJUp$m~A>-6Gs4KI0 zI-%G}0qvg-v?Dr#dQQGci{6Uo1mgh3bi~+`SoRnap>n|^TI_K=9gQzhlo?z9k?!|8 zX3C=1wA7n;PB1>81Xmkne#pvG&1!n@!_!ewhmuyI%zjLW%F`RPz)USbV^5=iw%UpJ ztKd~G?a)$Pcup`jQi7E-BA-C9a=A|3wKRJLqvYFUTK}b3 zMJl`QWUe(>{^vOc-TO7=^S?v|XC2a1mH&+jP;2-Z3hz+7M*walp=CI-%R z{sgmP9kak}nBecA&1Z9f%!Z)<4fb#j!)!K8^G{^m`c2xFM*rPxcRo|XY?$R=$dFyY zyu_Qj|2($az>LRn&%c9KU&!>vLhk=E?F=o{)FS_A+PRT=gR`E08B@5Iqi;4W_kWpn zeH=L~;{F%uLqA6e?+N~A+1~(%1P2}eXi{;;-)!hn<|pXjMVmqTz7CBSR9^fhW4VE` z%sA`3^8bU{vkWp~sV0txJH|TnfrW(+T*1-!1ho?^qh~KjbGMqr7h9LI)a3bW)UD?R zI#c|NFbnrNXc!DDql?MFW+$;(m!kyD>Z$V#y$A&%J`?wP+}qh~Kp7v`E9-826gvl8 zV};QQSb+OKaqp!N_eP^#Z;cR}+=KudOSHbl5b40ZANMaQI+*QO#$wSpX&Zbq7IO-i zyJ5&6>@ybWhTUjzF78)wPv^I{Je8gz9t5)}b1tIUr1R+r;!NJu~!XTV1D%9j#*!dj&btes>t+?ADcs&L2VrH53bSNtXlHfOiLo( z+tMG2w8Y!ypWKv)C-YmH`jh#Vw&uCbb6eucNFpDNIg&!O^u}}9A)FyZOLl8ksYqsP zI@dIqiZ*2j=n5b~ za?s?|XZj-Z=gdJF+6MEvoKq@v>X7(yg%0o)^QX!DEo+vi>dNhP@St9fSlE`L`*v^OB|=mMcE+eDVmqF zhz(BJN1Un4McG!+vz>a2IM*rrhzoSND7zT+63xq5#AQy|N9@q$qHH(lvz&U1xYjBA zi0A5ZQFbHfu;%3~V#F!?h;dym%BDeI?9^MttW)+8x9W0Hc01_HH7{ooKjoBt#H)3= zD7y>vZl~TNUhkBB#G7@wD0@5TFKJ%RBHrPYeZ;Tna#40a=x;go7V#dZ>?1y)%SG7} zHI0W#Vv3xPTTj*yR)~;ZAwsf3P()3@t*0*60=cNsy%MQpe~^Fd$mV-5ibZmv$Ur#R zAB(C`b|96>_2&CjUnVuELLFV9L@Kf=lvCkcE*u$1=Q7f9Up^TLW#j$H&|oZ^4fn?& zQ*Kg!EVn6!)r@MOGZafkOIyd2@f=!7dzFbrV)4x|qAwBd&#GuFmOe^jIGs+!BjH>; zl?=h;Xd;%;+Aqn(b1|(ypQKT-sCF+I+XDUJcp}u7N+eR339sG2sz!B`>;8diT7;{Wnnw|YHn^RERsj9%<*g}9!;unG@3z33h{6v#Z??Zh$r0f zLZ9&*Y=Aj^@kC682E&<6u}l^wg%cqTjKn+?N#$W*J{t=~Y)WtHZ{fb+ zJW{l^B_g%$y^D+-P zLh)@(fY9b#xHl1V9T9(WnOJOyJ9?^=3~wZraR!jXON+!O-QU#hVW`O8%oiZ;iyal~6Ezq7h1t{{mp)-z|} zcbAxp^BAR9>2Q--Z%Y1fm2D>Qd0ygy;lDNaQ0WYJhQl8L9OM5VEe zQde=->*h|nhV%?n%eq$gw6E?_1IQ^X>?QL}vVUpU@^e)L+eSE@MW1-RizQMRJf<7N z$FvQ(5sqhyd+5@2D^_5c3xyEWD4b8k2eCN~nX&8*%O^M163=t0d&!z5XSVmCwUf_< z4U{u+wlg8;I55|NHnlAkiNvFvgGVn)$5>w#lb=z-I;|~mGr`Rpm5qfnvbJMylyJ4L zKD)iMtGiu6CAY$(+$nXWWC-DZ7HbK-#iEsoC5zdV$3jrB1!CNi)XLTCg3E&X-3eL6 zaf}uFLJAIP#Jtn+Qx&UsmaCvX=XSQO>Bw*7~ zBZ>UZU_<8$pAGRCShCKC67ek0Z2hT}-aNzENIcFHOO)r64E{`*RXQ2Dm^eo>9{lw5 zD_=a_11lQ2I|62CCf=JzBJgae^w|^n7|G*!w-p6_1`FX2P;LVb(Ta}F_Rc<776UyKG`z#Vh+R=^g=*woN2nTn+FT}NkGVY}yM;w;MlE>fy5jcuwg&ErWZ z%VRZ`saz(twY2xrEnBkAInEXj+miX&bS#opYkQXTw8NRc7*a2SB^xH@n1owGiEuBH zyl}WJU!_W1E?b4!Z%7vF;_*dY63*~AjU^1Dj#C*Ivt(>AjB`Lf!v&^QzfV)RX*+|ZA6&w9Kk|(xtgOP0vFqoj$^{8WPUI-5XUzU9Io|i2u|)fEbmm$ zU41i_UuHf)WjAlNG2@##6-#&U%TlB`8%IZx{sg=u?Eetj;*Jo{KwQHI;QC4seRkgK^;C( z(qDWiFW7fB%5EDJ)qP`?YA<29#Wkoa)prwqc}Ksfk9^nPK9t=yD5`(dIUj{t=H>d^ zi*l*H+oA6uc+`ha`~`hkluPxsj>nH-ozD}fDb`(4QYL>fK4UbqAeXD-KR}oEyYcj* zANU+z==VmH-8NK_guWmPa=CTafiBfI0Da6k`ayK#awp1c(~6tdwa|ANJ}|o%>v-=M zbos;a@n)h+l+-cDT^m?^B0ut!TyEVc@Z8*EHRTQ;Lyqz#VO0kZyzO8h9rWCxAM}U5 zmg;Mpjc;Bh4c&erHsmVhTk0=IN-I4>JfZ&59!TT+bIIi?%yx(A(HUJ7@W4vWcV4vD zg#HCU*M8ER(?Q&B{Wg?2HZIL^U0gzc1Lf`#`Vh(+OX%OCoGzjNiSqUmdI|!ttAsuc z^z9{d2=x9E8pXop(KDhzA|54)1GYyobBmWpds<544@V`JXUG?Hwy#l_p?~+PM&bH0 z`Wt2R!7}>kGWyjr`mHkBEXf)6H>!-DT}Cf2qt7p+FBY2PItm^+8~HK+2vWXv|DRve z%M}dy4j?Cp;vw994=Zm~JYSdBlpJ!(t9UjlyvLVU7LNPn6~}s&E0-xfNgn0HQ7;GO zt;>#t$NVI8+|Mjd#n31YeTQ|ZV#J2Dzz0Ihp+`u-_7KkXc6zDitG6Q7TWIs??Rl z2BmHwPE+bm;&i3%CC+g6FaD|vfBaQM&L<*|1w?eIF(?QXnr;;A6zmr45#-;n*?t(& zEBdjYb5AjV0l{%1$9;I)a{R>_ak3zP zBujdM;7Y-Df)T--;10pt1osI(BzRcx1;O74zAbn}Fkm_To*>vJxJ>Yqf;$9n5&XK~ z1Aw?!S@6$0B1%dP=!B)Ygf<1zLf?EVXEBHmhy9IwD_)Ece z1T7re*v}ZjM!|)Goq`t%@<;TP-y`@{!TSY&Aoz;lp9NK=({8ljG{KVvR|%dcm=OFA z!Civ<4H)}BAozsf3xcl;@<+~;^WuewSS#2dI7e`aV7FjMkUzm>yB&hJ2=X^nQ>jm!=yif43;LC!45d2Wk#~S+}`MR2{~rv&d7d`9pi!Fv35jqO(m zMg*@FyjSpL!M_QP!v@WErwfJ!6M~lreoAn+;BA8Y1RoMSEcm?OYl43jG_YZ_zmb9y z1y2%OAh=R+onS=pV!_J zoFX`j2>DjQHX`IZq<+0%MC$tmHxVIsxzt}J{2hY3r2a0czeo7@2|gtC&r1ET1pg@Y zZwtOlL_hzOdi>X{_G5>-0a6iC9*SIbn9Q6cBa@kN9=xnA z>a|t{h5D}ER%?}NYpboTTCKHet=3m-zxwQL?L(`z54BgV)?V-Lx6e8=Cjq|pzk9y# zoZnt+uf6tKYp?w{CzH=~u3ljnhVm{$RjCT4ROD#4rd`7{)uh6nsK$*Ky?Xk?dy7-m z-usUtW8*z+t(o7|G>UJ0^zp|Z@4aj4|0~VT4|SPJ-5~sW;6B{Dh0X!D;O@rVf&1UN z+8`7WL1UybrLG}VRX46~q%q2_EhYEY_bvI>P3qh2XXib16UZc(XW zBT%hWHG$&62BWGj6k=-wq&?hK73gYMP@`0hr&+0x)Swk>Y7L{Sfh~qlR9y|NP+2z> z1*JxW)ls!d)mOwrq2Zz05F3qbFe+V*D)$_qo(Aa(JuB6S)KwQUHSX~Vsb3zLO#&A)Q z%VhINz_l3RG2!V%kTN7BC$*Q!6KZK*)X$)Vn$(Da)MIQJJ27I$O_oy6%dELo2H#u+ zruiK6p~|X$m|z5L1i#9x?txk`@2e(r*gR5Z;36ontUxMLgn5D6;8azxI#>lIU6fl8 zhYE8RW%pj7l?L!s=FH*XT$)8OU{#y1vx6&HKg_DOZU>@+^B`${h?dsuAAl45FF0|9 zHS06*!TyL1>y6C-Gpg(lAsPr92Q+Ef!)%bFg$&wP!ll3%A#3fuurbgiWWAk3-+{40 zHrn5z<|Bk`vR9$gz&IhB?NeCWEM&xfimJv7IoUn~ZU-g^In90mmIfk1&a}56Qh`av z_rW!zZT8pTSzxm9uqNB>=h$|tc(lL{B0hnmg ziR34QJk7q1IA2WU7?>sCODmq%xG=>bm#~k&B;0%{B9t@Z=p0ZQf z!7LU>*4xhW?6VpyyVvXU97M_P^ZM*0)jvhs6AZ0Eoa~fqL9H^ER)akAD(D!6HBkla zIzD%%}xJev1|j(-0GTq{(u%bqRGeL0z}K$SknWUf6FRZ$_Yx z^DIgoi-oiri&OcB$o(TZ(ocgw3iCmXn%_?EEBTH{sr|e7qZ#5 zXjG?I9fFowtO60*&1VN^dMWV?ME`#n*}1@-~9 zU9DX;ql@gTS$mSX6P}yV4*NA)wMNM0b~{~IE99#1e1`p#W_hqzho7akb;7}DuSQ5Y zwAEH4;@2>SmaR9ZqCBb_qP6zP=A#U9nu<>mqm=zqG_f}cX}RNes+KgPoCueoO~X0t zeY45(s4v6pCi@KYV*2`HMki)o0NXiYPhbw%TZFXijTDIs8MLRf=N=(z?K;LiA!L1c zE`^g74;#b3riV_&!^W`Ah+g3wX+|4IC$mLlu5g;kN#v2d!WajJYIvQRQ|1e_{ztH3 zgPk@XWOz1#V-J)=ae%x`ITVbVoz;>Eg?$gTkFFC=BRQ|pu zK+Zqu$QOk(ik#OO!!HSEBsmRib(3)F$(hJj-xSUWaz3ILcL=ABoS)I2JB2fxoI0lS zw}n$n&KvafF5!g0LFPXRUbV$EuePqjbJSaSY?0`O&t=cwb6bSqr3ybnd%rI_;H3&* z&y;yUIPg-rk@$gd;H3&jm~;;c2VSc1Xh!RY!hx5{jn+fLftM=GoyUGyIPg-1pQfHi zgaa?t=xjQv>>mjSUaD{_ZGKcZ@KS}(W?w%RP7OI1P|st+vB~)fTRkqEAUPNYW&cDt z)#T(kGEWF+7&$L8qE8AZKu(C7pAwEmPBXoDS~ykYe8AP{8R3}ZL@DzNmlMEzw!%^7 z;Bzi#7$R?l@8ozsFRc)HD{Qi_mxP1JTj5Ex@MYm3@>cj|j?S-ygUDNMUi?Nlh`beE zN6o(#4kB;a=QCozGpFb|6tv%AC|;E*RcpV(e*a*)yJfxo6eq_UGQ%3}b13{rA)DMq z;!Rlvyjv5uh81R2szWfiDvv&$Ts^j=H6REwl_MNZOVSzoDCr} zy1-pR-Z78S`U3v2jbvryF~IM*_OKP z(KJ$3x&Cf&4*^!y%{n-n>~B(4b=3h)o`z}kEEr?vg2XXsEHpLPjPG|%PA{CRU{|#@ z1^iJoqFJm6Z)5`2R+aZY6@G!;4i^sgJ{4ZauIhw?ok4})r0NmE!E&a;kJ9gY;UJY% zcn=3;q;QTP=RPhUqg;;JM9xI&X%HDKdCESTsnl5IM#!=+;<$x{47v;SXd!FuhnNCm zgsitq?6Ike>nQdndp1>#6|xE5AJ3>PrF+3DMyuL74x-i8U1---Z(mY%Ewlf4TDhm{ zB&`J}9g=&6wCs;*(4`Xgp#52Pd6|q+t!mg$>3vn}+4u>RYbG?IfjJ&&P!qXN_x3|P z$GS)BlPNLjSX9r3G~u~&;;u0>gSJ4MS<;|^%i7m#8#v+mKN50piprl>1$2hD4FQ49Q93y}W- z1!!00q0Hk^QPXCPp!qd;9$~PzBT&-aD)Uv^HG7H{m{At!^aON|<6IYRprY#5>M525$}9Vb+G?SYv9|-ppK!TA{lcknTG)6%5@%1)uz}rfNe^RfAf`FHU%e z3SCZn*SBh_G4uiJHZU=8t_z*Wtk}pbFr&?(BWd%=93V3q2|dOhPGOkM=;YAboJO0r zYFnm-_Oji7FeS|B%+N4~>@?;j-qb@2+3s{^JdS&zvuO1hOm8gYp$zSeE!5Pa(EF_0 z!o0y*FEoZd^lM0QcJstNZ+-pYRn^RmFYnTJ(el_u9>RfXGRpx$6O{ju)V}n-L z2Hvr_{}cCiHtSc$dcC0ThyGdw#rT94?0`TQ?mKu>aG=nqj4lzKxEX;qx|q_shb8Q= zQ#b5JgHv(;68F1kIB_$TE*H}x1(Z3r&}`yDy0e^<%-kPT6TVHaJG6IO&^U!V2+POw ziyFK;K~$&-XS4I;^w*jkgm&U?hhTz&c+oW$>X+dCDuNeVkFX+q&Gjhs27i??Uz@xe z#fxxnfs$*eWI!47dZ z<|+$Dk|=YjH}}`7BadZZCK@+D$*s8gU3=04NH1$YKdczWq%Q!h&$~o)8ETA84U7&I`|J17~(KkA0#sXw!WYqYee)>0wgnojk!_9YUnsrCi)XQfk_(vDeunNn+e z%iNZ^t*J~RT}nExq!6t=sbXOeXAsd^*jYfJ^E-3JSp(VRtinKQz?s#T>l<)d;HOfB zVlwIUw)FG!WpQWDDWC{z!A@mSgby&uD|!M*gCg{}_4(e!f;n?ghPHuHvFMh{UAiRZ z3Oc~I$0^3*C!!l?S4})`@q`B!PpB$=5071kdt^~z1`sGTt;dbO8hmUh<5R&}%laIc z`0QG~I2o7J1urm{4i9*Iw!vI>`70~@2zbcJgXG%|!|yl@zxy!!Er;Rf4#VGl82-M) z@NXEx2g&eb5Q`R(`GzvT73)RHR3)r*?o|&!QfgUZlUoiFxp4VqBcLa0UeO{(-ExpP zU6(6*+d$8D>n-A3w;UvL1@r6e0KG)>iWYI1TMiPtbh)Cp8}ujLdW*Q;EeDBQxBPmy zfR1Zk(IO_?a*&wP<%-@M=(F5-okBEEn~8S2~;Ni}3FXg;LL%PNEn~^v5%OPEy4R{n>o6r_`%@^VtCv>slL2XA@gv zMHMd=S0aK2=0_DmD<$Z*}qobQ@2{s7&G)OJqy1p;T~U$y6bybhxz(PDZPC zl4XD0K^<&YZz}C%;scJ#<(+M+A4_vaCF2MQ>@KR-{_KF$no0Hb7qjVXYtrdS#WS;V zTl-qMFuRXz&zZ9Z?=G`)@nWJMvM`*ot=y?HlA$B3v(s4laAYvA=imeh;MWA zAf06ldg4i>gG!d%w1I{F2z?SMkaTt^FS|<_Y^hsSZ#F*=(^1s(KtBehlh4S4QCUT?`4i~q)4mOWLG2h%BG`9}n(;+k#oq=4h!i?!x$hch& z!ckcQ)efGJ{GJ{(t2wNC5rs`yCbBrrF+D`iTT3ww;sZGaZWgZg`8D<;rDd*cOBGTG zw$3+q!BJdP(s3+f?z--+I%k!Tsl6%5O&w$!ft4eE&_I?mP%T-$d|l`I^?HF(g%jk7GJ<)v~o~HgvApp!$(kSk-+KQKrSxwaZUc3G5m1 zTmgOJQ=*g3VhEX53?ef(=EXUcuWXb{H?CNL^)D7fXp?Y0of^Q-G-xWbH>|7NJ$;@R zRriv0OHS(CfY!2YyNjPYMQ6J($A!5rw5wg&L?V^sf@OnByIQr5mKxAbIY>dO~q$Pp0y+bNA)5CG4DD>w=f$Nhhsj+0VsOgU%_3 zm|`%7#}z#ncwWIy&uqm0t7pZ4?1{NJ{1Nvs?Q{wqG^kh)^4OG%NU^+=%*VGQfS6u+ zr&!8ou<&BBa1AR*v@(OrBZ6~=n=TN-Cf|ofm~#W(u?go8F7tz@Rb{SXMK5rn)2BG> zi1GYR%$784I%p7)+Iej9T=fev9`k%_e=MCU@T}IC&FT#`UPz=;JjEn=X366(ZUv?D zkgJJ%B;$e4ow(deWB?%O?E#pO`BYD-=wLI(VxiBINWVl0N4cFS=<`+#f4}h>a9CD! zt?u-%dI!y1*w~ZBLc;@I3O-^4@E+`LN_vH7i$iQ~XqU+*viOsM&aCpb&ppCjiT_n} zRBsNuPj8OLlvsgBWvoiYe0Hb5cmLKcndTl{D+g%F_Cn4{6x8|+OEz@EnO+C!mcTj< z6N^l|9kF!02Z>!i$PQhUd@c`JblGo=@98L1jxlO`JkO&uRxFG(PG?-ZGR{C8=Ydk5 z3vcC|r&f2Z-vA}p#;LKfj&PEM+hWl5_N%Mo)H!-fgo5y{9R)a@n$lk!j2IncH3A zX3d)}OPy*d>>R+!2w2R!*zc9{PP(PY_m>uy^y1UfQz)nw9N$ZQv3O4pkNR$<=A<&c zSwGF;^V7Xti@fG|d-K=jNfIbSgWU@u41*`TfoJbN| zz4ym|2PZ(tz>SY)`s%>b{|;L3veh`CEoDM(j#8_Dqj9r6-(dOiV!F^(Kz*U|G_MSd zNO=m-ukRk{<40HOV_Q#OE6UXC={t>``7ZCxxg9)z73E&=F}&i6A#&|d%r|xK^5m9+ z;kU1Tu2QdqLHqEfxoqFbD0^*CRGY^rb)1jk71yE8ukY`RT)(J~e9zxrl)W}6s%!AU zr`gBw{Ov)VU!TICcRP#~%Cp_&Rq2fO z*V_tdqA#{Iq5oJQ?dNw|()_ba1ULO5eGU+=lQj0K$(R9zC;1LN@uFSzP>`}`cXq@-vXiQ8Wr(A|m;@ml_`w%&v4hn{AK z3LN6~d#K2uH+VTDRL<6w4>q9FJ^%6Ez#(yY0s9SwFmKQ?) zdFBuw7QOdHT|L-yf5VE`ey;C?=4bOzSNZDTewWeu%bxnB59Ou5evpU$3hmv{c(|X8 zrXa6O{NZ695o>QJ5g)KO60yKK#PLe;$0Q~W6&DaAmmN7rbBa3Bi{H-w^z}U^QaLe)%ga;uOJl!DWK$1ml7^ z!QFxv3SKUFqu@6M4J={QUn|JpQ;?n^c&y+`!Ht3m!J^#Lg|1~K0Ex|_wpA&pt@I%2` zEJTzaFW4ryRB(e}uiy^Biv_P2{D$Dq1z!<-N6^ASiT#WgoF>Sh){wti@C?D6Apd`Y z^|uJ#Blr`+UkdWqRFvZZjW|khvfz9{{yPurHw*Ho_oP29xKHrQf_Di%D#%}@QT`8t z?+FI*(m{TsU{r99;1a=Z!I)r1aF5`1g8V-P>bqC)F~R2rUlV*+kpD43`6C3U3N98r zQSfxZtl+tVmkZu3c(>r=f-ejHQSbvn{+kl}dzPcg@Ttz{gZT{hx*Zw&1%`|Dn`Z!xq}nC^(TA#czvv z9)jKc9SnW&&WUY8w@dvhp;rsNMd+l^JB0p}(EEhGLg=pw{dJ)q6#5aNUl972Lcb;S a{|K$mYp}1D=O);TZB7|@c!;#u{Qm=7e4j}G literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/crypt-mod.o b/obj-i486-linux-gnu-patched/crypt-mod.o new file mode 100644 index 0000000000000000000000000000000000000000..4ff5f460772ae9672c9fb337f728d090878a0e22 GIT binary patch literal 13184 zcma)C3wT^rwch8oTbDSak=Kxj)JP_Qt}<0LtBGBeDh zZ3$lR}?`%t8zs^idsNo1(&5lYM26dn%~o9V1}BYngUUS`(uQy`(D_8c4Y6- z@|ahqAGnX4{hOS1NSZkcs zFiI(Vyb9GXj-DP}*Qiuzs)|OJqF*UTnh~XH{H9W)#-LlNFoEKcMk`bwjdHXFQjhjk z)vRk=RI5~NpjoM?^k5Ww>MUzrBS(y$qSiHbLS_AQG?W?>QzyfnhGFq&bab>X%0Xir zt>LN0Rc5ZCo<^ApGb`1E(Gl1rX2gcA8df%bSZ0_xp%L~k!TilKmC-$sHc{`Sn8gO? zYpF5jwvt2ogbr(2ogYSuFt*D_vE#&=N_1@mdvez>376WchYb&!GAy;Mj`pbEj6sa_Jtzh$B=M)Sq<8Y64V#gXdc*Wl-AT?p#4>HuFHW_}Ry~TETZL@XE3tNKP84#g z-UT;mCJQ-3U(bo!gq*E6(#Vsn@6i4Bx%#6VJJovBkX`ycYMw40Ez+ZD^C?0u(KnKu zZS64*F4te?*tynHLw4)4ICh@ZYsl65V>DyF^`z0fM%xr#XgzDlwfZwOW0`fW5$@H? z>EK%HPD5_dYe=pWa+_XH@=PJO>#Zcu67pibon)^y&5TX!he)m$n+Nnl+Pu;FrI|OQ zYVSinYwnGl2D+~1L53mvC0csOkBEw#d%gvA%6@_5 zC7*_lalfTnU2oS@-Y6Vni$+aLb%W`$+Z`D48;oeIC3mdNcG%fZ9k(M68}$;q2tV}< z*sss9+n|r@?0g95r9wJQrJT~sgo-q!Qc5ous;((Xa)po$dPW!{R|?srKTiW!3E8X< zBU8Ft$X5LxJ?at5+w?eCq*n_$Rhtc9jgT|+3Dmq+$l1C?RqKSDtDmQTXA0S+Z>I2B zLN3zx(4Su8s@=XsFXOyt+e7f&ZeOmCVBzTXLU!xj?A;*b+E|XN&ao@W?v35SoNW>g zvfYc2GPPl+3GO!5(&x?gbilZ`!LHNi+K(~FZ&2}hVianCMr{+)@$+`Rk+j>n5cXqC z<3uXEz-D{guMwYSeUW_)vaelcEN<`hYgaE|I4%~_(TY_r>A^}UYZF9)AclinWn0*8q?e<0b z2wnKNkV~2d((rzt-B{<>)H77I-=1v9Zv83Re8Appvb9zZQS&G4s4=oP_A+h0(T|*i zP;QLvVL)#3IiZQ<#1KQMF=c2^Ag6||eOlr@o*W$fO5ZG;7&*6aqFaU2L{5eg_?&PW z$?4?mw+Uw)Ie8j?yKu&m^E;0Ef^ZthxsXZux^Tvj^K;64Lpb&1Y^B%t2xl}o3+dN4 zg;Ph)A(qI!!ij=|%0B{M!w$Sm+m*6m3 z-xUtLRDLABCmeXGVlF*6EF5^LVm~M6Vd20_dm~9C)c>SJCFjg;PsTH>350a5Om%sz*O5oCrBf8RH)cCrr*t zM&n1q8AZ;?lsO`t8gh1UulTWW9CA7tpPvXPM9yQ>^Hbs2Mi1-jKYUIN*0U2kk({S| z&L~9Qi9N^Kd0Ivx@=oj;X81YbAo5P^BHHu3a1ePX7GZt;r*IH?$FGZD3kQ*RVt-+L zej^-2-q9y8hQGC^nKcyAy%cysmQ?o|3u_B^xh7x`Pr zpY0DAa*6(DTJ?r(Fw6CFPV}ab-TDTm>96*wc>l87*Xmic`5kevS9=WgyK*dT)Q8!t zLcYIS{D%N1bf*csD8e&gAynWoXd{3O-gXLEVsxeDbFcBX+p zjz+YK6|uG8=({GE{FmWP|P| z*&JG9qT8fjr~ea$Y=-w|Fe-0RVJFCKwV|_(76g!5 z4hZS!tLeja684C0B>4%+QJrdB4psX4&}I%!!<^d5%?N`XLxI({9Wt{$jQd3Y(fTDw z*Pe9Lu%E$wl3~AvRtu+ZF)dbB%X=VUDY;?C)Y|pbKCK?F=6EQ<-5)y>trjzaEp*W( zI|3VOr&HG6i0szR=s`2=oP~R$qh@OjktCge} zUp$n(of+#IG@V7<{ZJgBfbq`++82Epi=lSmEk^V<+*_@CDP|(ZnZ&XoCgHU28L=PW z?rVIGqO91KznOWzMrBK0FjBAJ-fF!?3GOz^ev+MM*bVePg1fJx87-qi+4nI#%i4{= zOd~*Jmr}r3?Z^8(rg`N$BeendR_kI)uv0RUrJin6x_s%YUCk&(E(%k4mM(1K7bUzyMZdyqZSFKw zQ}hw&uie7Jz;j)6kbPTO1$KLDbUVkL%LLi&ZP9yJ{O2*ucKg)mTQqUo4r9xV=xeN| z53(fe_Swa0oKXh$(ZStn8})4~@;Yx29ks%Q(`wI)-{fBPW+1nYW~rM1A~5MC>MP#=NVi8Rcb zPs3*8Z}OcK?cy+NlWMcRMSat)jp+Ia{?5YRgB)dSm_~)WIBGpdooq&(qb46g2&|Jx z)qttv}WLf`RKN@%Qxs|habg0g9vCx_ElAZmj zRHxUqXyKfUmo4v})1NJOc6BW1SkUQZQ<-ww^(BSqOnRl_2+jzivp7^#DpeTDm*x!S z(j6&&(k+(KX}7OqfS=q-LwUD|CTs`W%b^MTVMfpl1dybXH|YBPg}&6H`Sa0+w!w0# zWF&&5qCcyWy`BtO5WZ9w9UphKJl!c)nAuapnpw$WUsw)bWOl#n!50}LilJZtT#ASa)_upwj)H2w^bQ+HGFYS zTiu|D?6)c(92HfcW4cQY(Yyme6_J%ut%|Zc4ethnLugxSBjH%ll|~FV^&-mZO#GRM z<>JUpIpfANx!jI&-c;(yj)L3o6-#b`LscvOOk9~Lxj0jB?PkVQI$tWNqPNG5msB~6 zO4^}P1Bq4JKVT8n9mhTklwsy#g-nGD3ubafq2@@sLp}h zpxc@C`Ugt6Os+HSCcQ*+~PjI7x?`9vu-fa&7vHpGjGoo?LCrWKe2 zs^In&<6}$XI;rJjYuI>AqYc<3W>B=@^aZk1~D*}7QOzgil@qjcq*4E4`z=kgi5}>Y`oy+GedEF&Pp(& z>2f~fr5Li(K*3EQpva&ojSsrTVxr%rMT7BdV$fBYT(-ZB-@pC%n4Ft{#Pf+_F+Wg1 zAmKtLmxQg1?_i>^19es`=UupyM*0Se{n?yKCepBZgc`Tt^$o>ySt_W=7m-}JSu7_n zLG|@#-EqA%v%R1oyl>w0_CV8YA9`*N8~ZdW-^$IIDjO;w&C-mILo zTc8OQLKRcF!if5i0J-TnmOwgVNJW{So1=m&ae6DB?1eAqe6Clm<8nIoN99QZN zVa}z!Y(LjopSK$+NfgW$fZEvuowDdE6@6S<6xN`Naj+jo#CLi{FPRyU$-h(Xh?pt! zN|~_U=`r`ZxN&{HVzzTdvkHg(Hp@GaDtS9$Tsd2Y_w!XeerXvoDPg_&OAQM*C>yo2 zQuIi|FS|5_s=diImldh3Usvw!WZn{C(Q* zlG!UIUsZ4>F1xYQpmfbH#$v59A)dhj0-f3NV0^&C@t;M}6jKE+&y9&Cn3CP1vSno5 z-B@17q@q8UGaCVd!-Y5EF!8b;r>L@uH5yb0dj>pwWm?hQy{TvOW|IbgJLkbrJ<8Ns zvJBz4?>J)Um9Pn_e7V4^iZj*QzFOO}q8p`cHbw4a$#S26PK>Av*&^dO68tc#Y%Z0< z2M|A7TnTaPjp=zlupB@w@S)3xQ&qeO?OgQOH9Z`fXjPr8l3Q-J3~o`a+|Yf#+8xg% zk~mHMid3=|xXtolP<{Da8HIwe*uUi{QXL(gCNA>mwkMZLc}QJ}qY(|W$csF+k#e(d zCUd(H$xNR@Eyr2&YG=;F0lzi zb@ggw8=GT49w?B!f|rC_eq~^#Ba~clFw3u?rf0tfJb%vhzoeB6J+Fg2G*;Q`JsyLfQ`nPHvCNj+kDt2mdJZ{)%*n90TCALjqp zDz08C|6s#`zF-M(Z3UZDu%8xPJb7S21*dW;S3(6Ed(FdwZ!mYyouvde;9%?G$(;5I zQo+YQN8q?f4CY4^joG}+8h}M5e@DjGMmLkg6RIg(vn8P1R3e=&;PC}=C_p@Lpk9gt z%CEhuqsnX*xonAxARVuqj!1-yU7Y(p56qn67NUCBZQg>4$hw0G94bsl+lb8oFFagy z)ny*{kH+9h$|Tq`TX^N+)0~!kq4KxpV-^@3aChgu0&Ky7%#l?K=kFXTkmp8Z9u|Up z-~h^aeI8aIA6S*C6#tyZgP#=ih_e7r4&u2utyXPVzolpW7Q_%|7ihCvP}PX16IM<2 zdX#h6?A9f<6FV9VP<=eeq;}PsRjU@a&FD6d{{ExMoKt7YGm7dc4h^DEfTeig|9&7T8?}5`xoCQd9~n= z@1DWce2P+SAow#Wj_2DOUr473ZN46${eApZUzFoD3xAZamJ9mWAGGJ9P5r?|eGgPI zf+pWagEnO^$4ljlcqa|6ppU=gsPmvMB>st$bZQxNKzRgth<sH$%d+ST(8RQZ8#gOzzdSv3YtbvN|2u_0G5*L9$)_2r?DwM0Mg zEv};P^JsGn^UUiB=-YztTEWFW{(V(2;I~f2*Rg=8>ibqzo86~DuKJ=bUiiXQsXfw^ z`vDtr1#(1`Qsug325bcr;Wqv-Z}f}42DOZ)dSa$hXR{$!pf8{UtmZrFPwxkO;xWHi z1YJD?`#JmY6;k-DRdt0btJ-IVP?5|fFOIa18_x$z-)WqdI(r zRO2v#R!EIA`6qJ){>H%qEI;#sir>CSlOJ4+tAF6gBV%xYnnUQ=m(Y>S%14J{qR+)^ z3|_!fRL5LeaGvYT#{Q5N+N=}sxd&JXBR#heEP6y_-4glVXA4SLd&DV3e4v{y{U~!I zw^)$=aNJtK4T9$in)%VsJ)3fQ!OH|cE_gujR>5xwntI2$!$Kbsd|vQn!FL4tpI^?y zy^J_r@KnKW!Oen6!Ak|N6#RtXZGr~{9}@hL;B$h15PVxOjM#Dh@q*I?y98GWZW2rg z<^``5{Fva4f}a=sx}b$6!+GiiCkxIJJWX(o;8wwuAb%Ul@z)C8E_hJzkl>So&j|ij z@Q;G;3&v1m)OWIAm*6VFe-gY_@K!SNw+QwL@;7djyGHPHf?pH-H^E;C{#g*eEHmTA3-Wh^)U#NySMVaiyx>iO{2?gi z9}xVZ;LinL6Xe4N<@l38;#9$ff@=l&I|ue>1V1Erz2F^!_X_e?E|h;p@b`j$73438 z*xw}BE;wIsh2TcPxL{WBTESZdzasc;!6yWt7JO0gO+o(Rhx1PooG!Rj@GQX#1#^N| z3En7pr{Mj9PYOOS__E+Tf)UKgc_#=?7hEEEp+PQ)S3amxe~f*HYGf>#UPAb7jr zLBT_UPYOOQ_=4aYf));J&NoKz1i@K?rwOhR+$xw7yj1WC!2^P~3VvDe0l`NFe=7J3 z!B+*}6RgLx2JM<8I74uuV6WhLM4Vk86pRzGHU^}>AoMPwKPq^Dh;cUveu{{3w@Lrq wLLU_Rkl^D)oEb-iepc`eJ}*FDGZA|N|4&DHuF!m5BaLlWS-1s=G#LK>0>W&pl>h($ literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/crypt.o b/obj-i486-linux-gnu-patched/crypt.o new file mode 100644 index 0000000000000000000000000000000000000000..6b31c09a00889a557f5aedb6da0206ea53668e7f GIT binary patch literal 39912 zcmbWg3w%`7wFkVuw!W&Uy^3#BP|+%C#q$0C`>c~pg1z_qzR7Rqf7aS- zuf6u#Yd_DK$t8iJ0>dzr^D>mFdMTx*G}|e&HB3??)Nzie#){4lLv07syUzA>ycJ9F zKb#kA+wadF5cAJ?x$T+s&KJ)-d)KzDu?eax&)u;z_K!XJG=^ppVk)ubCcI=G5 z)|Kbk;~qDVT%-y+_9R8q5=0-PmC$k5fnQPK*2gDO(f^O~rzR-{H*4dg))2pWd4O)A=vOpWo`r!-Z}T9wO6HycO!hxwjz5~L)Llkw;NfSC z_=3aFxZ=JUJG+n}ex&o@*}J+z^SW|VVS=YC*GEgbay^biJ9c&sh`;w_gS#JLqr!Bd}}P z?2f&$QQ3=hyrb|x!%3+q)3YshuTASb(~(DH^C^2n?KY8%T@Jnd)QyHncN8DA zL+4-Ao8QgE6->0-jZt?!YnkVE)F9TqbWiuE|2}%u4xg6nRDb($>4RjxpfAK4X8MMyByUC7iq+v(4pfkXcGd%!}HkNUdu(mS7i>R+Qe%Mk(< zb_lo}o4WEc%)HFb-6u!WV+&>+t=$HRuAbDkZ;zrMj%oYMX!~|hti0{pfw5^bj&@ZX zg1Jy9W5wb4b6tT$j>Z`~+nyOIAq+p&b{viW8Oa!72GLH~t1EcmzwLH-l7roWyJ5dg z>qH%qHhtg$acDyQXB=G-n(@|_gHzCfyDB_;0*6@7J%NJ+gm?eZtaEo)z|(QKYf*M* z$NnFV9*vzrw@ria)|(H4cAN*Uhl6it4E=TFxVCSN&OL4K9MvZ6?l^$9pi^~5XXL>E zW9~){8HhS}b?Fi~?$}pd!Fe4ob70Qpz&w9nYz0e6qPgJCVfZg#W}{Ob6!E8y$8 zjuz_?B;9V}&RtucVa+@DX)indVH10HPfobCC(Y>Sm7mYdzLT-4a3 z$A*Bfr)&g*u1lgpox2WPYPSome->JtaSa9Dg4j8n>ofcvjL83BJJ^R8L8g5!qPi<^ zuw$pceF`oUtvk@qI!0}RSGtd&C0PD%`;;HsOx_!Pc>eY}Tethse*7T#-Q7@RS8{9d zLA2D?z@bmR{|>z3gB^SQ?bNmPx`PnvOlSA>l$v(4{RIiSy|#8R)$UcEW8H2Nri>HbV!iO{{zjy8DO3rg6T`v(Q56<9hl}+iqii z{Gk7;7Ono!){%ceKGo&>J%&-e1aQTQyWAuE4+n!?8{CJV_Q!szhvlx39TYrpWn!5O zlKy2TI(&M9!@F`4g3RAOz%IYbhoYq5_~lMR^pTB?=P-aKVpDXvGrATfD2icdI@G;P z$AnLOj`7Nl$wQEK!jkdA0a3h&8T?Baw*ywdwRXm~_YHVT`jZDeuWW0&_DyNN-itiqermJmxf-R{058q7mU%Rt&_klJ<_Wxmc$6^LuF6_m` z**l(bevf0i_H>^8Rp&)VIu6@jJzNk(|2;xy6=3b=Z~uZ;!harA*0BfOF3?rL5igTm zr0RMzto-d97MbDXJ{kNSY=B1%u6}-rtKR-R400%|S9k1J%pUH~j-QK3Ko{C@Y@t-y zGaNp>bhD;2V3(1T3<((|!8kaI(b-_Is>DA0O ziZ19Q8vpyFV^Eg^uj_RL(+iN^Rp8T8OK)ZT9ZTqblQDMAl#aLTdiy&{HDgl8TROkL zV=mN>M3cY02twTfThhG|DShK)I25=qve~Fy z@8+V>u0R*n_STER`4);}u4|dplfmEdJDS1uyq%NvOvo8aXP)2o$rD?L)w8>HhhZ@7 zA)PfLh~opcJWqX0WS#n09`|o~o^|eC$6kr`N>5z0uL5Vw^P7=Ke)m$l+irP&5jeHm zu=v%x25P+loZfKux1R<-&3LQ(RKSl{e~-Uo5!Bg+SyKG%zlQf@`R#At+e^g!+3r{h24H7@(REHXb}^ql z2^)`MPTJ&xJ>K2$=%?O`4s{-C+yA{6xju5oo^Jct9e<*&_)uzsnr+V73D~(y zSHZgvOVHRtgnb!yC2nMJ-{p=?17a**5$rx2C8E5<1#4``;es+FmO@$S_q`Py;P2pC z!O4(N&@S)Uhp_EoR$Yu%p8{Dnm@~f4*r|8OZY-7$?=j+|Hh=7j4{UqJjg7Hh$MdS2 zTVcCBbrlZ0*>AnQ<={xP5>#yM_zG=;2P>)HP zYwyvX-0}60adC|uO#$oL;ovgh`9{D9n0)0IA*`O~-gA93kMOG5Sg@pT?F zq`#eu5wu7968b2ATu*x#*wSO6>**{)@p4|^VAn8hXYQgd-}J6rn0f`)t61=}F(yHe z!h2Oo>Xgkz8~$7Wy^D|94}10~zf<3&TzKI(+oAo9*xLyB5*Tb`PYS>T7>?Uu@^= z>x*t5<-|%`?l0eK{m%R`rRySR{_sDN+_`(pM?5zAW;c41>OAD{Xu!qz&2ao_{P4Gb z0KN<}_PVJ3F>tyTXCF=)j0<;XU_XZW_-ZJ#JA*4$!{F}7g`&=t?P~0=jwN-5vw0RV#XgHjjHm8XIOsey0U3Jg=x^t45^H$9`A0wLW2C*0 z?p&M=eKU3@?z^=mw<4<^qR!!1xOg76HVM0%?tKU`&ZI8Hl7~egq`Kh0-uVIRp?2E` zy6*FFgu_Kdf>7Jed5(Pd7$hZz;J3({Sic^@slD|))++8pYPp{784|ASrw2OwoC>#n zf^|O_qiYu_n5|Y`|23$*tsqCwi8L+ahA|0 zM4pQ6b{wxjzfDkX?jzA6*iRfE3;!`=D!#_u`4&bYtg(;d@j!3 zvuGY0K4DYWQ}Vq~=MZcI?$>_24eYAj0{H`jwk5vgJXBXpe;n(p<9^In`hatnUhl04 zZ8B?OHX~6&)wS`F~`w-RZb8h8W`qr=^&Kj~_h57;2@ug5Y6-}sBvq-!@yEZ4G`S;j)2_Iwh>*c^)nunwb>dX%`(K4Vgh3c%ReeYoSY;Cc82 zd3$q?M^4QwOk>Uoi6!((O-#@PcTNJCkZE!PiPV#Ng_Sxv1@SW!(Lbd}b4p*^r-}t= zXIhXYxrLl2H4}2W6eZ-01QI3BOvnpzR+bWXp-8(jO3hBRqql~qB$R`!b9xmo^s&w6 zvSsM%c^T-4^GD-jfykicY#DX;DD(}apeGm?pg$O!uy{Wep~}}M%!rrkHcbDn*QVpr zbSF=?0EXuY>`_ct@}D3JW-0QT#(;gKTuDEHh})f1-xNc0Cf$?{rYCs-OmSu5j-)xS zib`LFi_NV(VKm)IwnlDxszS{P$}~|rVnr@yYHc#G2nktj%zB+anIlZ ziRX2UdDpt9UV=J!e+7j}sm2-LyT*bDBPa0!9fdX7(r+cg6)TD97E=|t%&VcPn6QoA-ywAdsNhb-J?JXub#kfFM zaFO?97Bt;BU6c9Vy=a4^8Ag#N3%qYr)l6fr*1Xtz0&6tKctev*yqB{I3ymwaaFO?M zTD8RB0fB35x%WcWs8Gn2-d#*xD&$$-=SVISa<%s*l10XNowvq&gqlml<~r|inh`YK z(d9O%fxaZr4|yJk`+Z4|(G4ksykPCHJ)%;|=ZhqzO|r}CY43wufFXC*Vt4)kL^4s z+l&*zfFUC(>!ILOUV6SmOZvRWJ&)_ub&-wAo53m|rc?e7A@6XzUEI1P?+A*y#?l+t z;%bP;d*WeW${2ijN7+WHl;aVy-b^OA#=0S@GYvugyklM>(}#c`I3)lxhn|VR$s8Cl zlHnQeOgMaCy}o9jI)acJ*kDi&dc1D*=7G&Zdc5bNY6Dx1WCSs)?j4OX2c9pXp6YEz zOAfq9RHb{T4F$Pb;v^$24v!AJ%;<5{$h1YUZs2yC<2u1Lc4XR8ST^uFkr_$OVno-# z8-#N_Iqfv~X5ow=rx?Z#{H1V)lfymmz}tnB0S+887gFh!aPz=BjG?H&5MRp4%iw{O z{RqvJDbnz%ts7LzRPs^%)TZW`O39LThmJwy??XjWrVYpCkW^pfW~yMT`D#T)%E!>| zTWeG9l-+QHuWr0{s3&C?GW+UnjXvdSMP+>Fo&_Dl+`b?70TEk_P zz-SY5yKjI|iB_~ugP)ak5TzJa4m{?vMxY9&bpTelt%WEd$(jof46vr6rzKnCk?OHd zgD$Ui24n_WcR^!{^&)z`&+a=7p*hu>ilT;Cry%c8D*&6)tZSex z-MSN{52H1w8du=bdLHE|>n3~{Rw}CFveqNNX*~#Ow}mwpta%Aq23W%|cO+X=P&1De zf>*p2AG#Q5HKU{y>tS5`tQ=?rlsn!!4yhBYsn9dgO2y|Ss}!myTfc?xPO=no zoot}Jq)kzR@OF{yGL1{gL+n3W1wWOvUoq>Ic0r@49_d; z7TES@1R5Ie1!cX9?0-?#_i*xGl{E>TeG&PP{Uv2>g~-dwIuFIZqO5;`dR1B6DE>`Z zccLb*DeI5O_qwvupn9LO&IR)gWvztBo633=@D@yh@qbs=TsZH4l=U&Z@wT$wLj$~n z{(!pfR~E;dcOioMzo)EhG~N5kx*oQCpsYfOe5fp*n0$mdKzSd-6KJ7Nl=TUqTUi@X z&_9&bf$RrRBV<3Qtfx`Jr^*_DVn0(>DIEE^vcgC^q^$pjyT3riKz*q!FUG-tDytUt z`$}0?qAFi2s~eR*tgKf7-zaN5RDX*~L+5wO`T#Zhm$GhyW#5Ad)kl=o2)F*Ati|y4 zzu^hkc~n`ipoGnabt#P4Vpv0v{ZhkP0;J*QR~y!Y$hXa~u7pFj8`frI z|EXb(K>e;UtT!NetzrEQ5ptbj4ThaRGpsvMzn>dc9PEvl9v3$m z)+eBTVOYOIhMNuR2uircu>Kp&TMcUvO8BLrhR#QIJ-)%NhfuIr514+}oe<%y!x`0= zs*~*5iz7?=FW_e15Erk9UWf!FvWMA zi`U8SPPk*}YxoHIvR!AvQ{Ehu?>o)qg%mY$LiC+3q&p+ltb7ZF@?=z3E8ilad>Ly< z<_MYUeFM(%qCfcpQu$2p3dD%7K*(|4SD1IPkdwS~ zP;uW9A*XmZA{2auLQeO-i)QyN6>_%sDOAq4OvriOTM+xcB3)J2*lh0uh+bc@YYl4d z8oS8*J%vkz%=i9*<(3M$B<){lXWw$yba+UwYl_l7p+K2%u&^nDOF8=`yC0*gdC2Vx zx%{Z>(7*HAx59NFom|dltQ4b^_aMU8w^B%~+9|q9OWJFk81keaV(DkNcs+DC{FC83 z#}!3wy!X@5VONI)P9A-?T1dC|HfF05(&N30&AUcOpZ6UaQY~a^+G1GktLd#_dfIpt z=Zo~#Fg;C2M6GbJL`ffBgC&7)t#GhJNgrO_iuqj_SfQk=^jBzAz3VAjKLEo*xv#Ko>E3Y|u6*aa zuueeRW_X{XS2qZm>7C1pZIrx|ycbZ_CLyPIA7I`sLQeP6-@Z#-_rYM-*x7aiUGDmW zCg*wIV-#E=WOhbf4Qk)%Is(TtraodkcDX#z=o*{v-OPyF>I&)BTH@VG%~!ipw2?(= zA29&0u|4O8D}!nGu}QAAIVM(e!L;ib@7LKJ*Ky?3(rG^ve_P~yMLj>rj{@aC-@_BQw&T7ZFKwRkt}Gy3K+J4Xs? zsnRCVoll4k)KaD0!5aKgIH;wvJ@KS)P)n8e1as{a4r-~=l3Ayxgo9ct+gncy2enjb zU2NE0!a*%n+B~+yGr~bF)$rzq8s+XNBV> zXDi!kuW&r%Y{R_ddrmmX3uS+g?-ks(m=S|_j^X{~R>{V|G2cCDQ zZD76L77je`w&UVm;lT6mwE498J>kIfZf`B)>wVXF-G@BhJLvWgrAzs|+t}hCyX*}` zs`ntP(=9zL-J48p{}3|69wZLPs4&tyi(UDk4hcCsBhs{9`Mz-BI1&ARo;`$o>B`h(w)cNH{QOe}m_^=m=;5!0%=bRPau2&s zgz2uaOT7E3`8%m#k#{~*kI1wX^j^pMD$}lSxxJ2Xo4?l1S?L|m8YP=|YVs^}qa9E- zq6U7)p4A0w(ywN#JnUlkN_N-j4mTLAp)_KoSdn&!_WI1}P^0HQl@?$K3=$6JK5%H) zVBuh9P-$l|1pLCmaHi5SS-UySaLsM7{-+1#vBxF=Ym2ZM6E2fNAP!n|mL$#Qldy=@H=M_JI zk*>2(Hgl0X*}Vmy$Gd%}nSaE^NG{|~H@Vv$xfW|Jb1RwA7^aj(T8kRmgt}(sZ=Qsd zJEO4*M$H#eyt_b`&m#}*`%{HX&458U<~6XI^M10Ml}e|{zFb|wp}&Xg+I^Mgzp=iy zyTM9vkIJY;=2bd{zMDmdpJCc_qsMy~ntW#p>GMuv6P#t*(|fA7i>YS|nc?LLhVL9v zoax=lCJ&o#9PYZtj`KdrfLLt~)Z`@ZbsRvdBm$<`opFtss#B+XzhyVCHZ4ug_TEXW zYJ{BUy^{;sh>+PC>t~{+YR!Ma$(;NbvD>T_&*gj1;owsz}CTY`4Fm*>^=`Mne65uknEnLKaWt=TqI6` ztUgjT)Cu|&Hyex-`2pFBbUuotzrwJ-!X#%@s;|qu5lrvBbkLO&#L9acy}7j~rr%_k zUM0TvcqgF~_^y_Q@u~DNG(FQ5jWX>hHtKfPN`i8j&4=bhi zyU>}G#e;IgO3~WqL$7J=M;^CzJUB_#I&cP9!_flCRv3JbRe?-iDj9bvmHb(o_!veL z!+H$$bXh~RiN8lvyRGfuBw3%L_yH=@I1gEknTGZ*E>)Z#cM%{vB#xrvmeP9LF_@` z)sPw87+tFjtoUFspW_(63~mB#A=-vPPE9cQxUVtZW$@(TW3ZP2A7xfpFiu;5Z4Aq~ z1>Q5hu`7KDg72Yu??KYS<89%?y3)KOFgmJ?!v^_&$c>)@LC`!>=Yiow47A3#28Uo* zyk%^)GQQKc^EhDAVGIYxzl;z{e1-J6wD)^`X#E9fRGM*~XM{Y-N1J7 z>OQjwZFdsFBSq_;q+85qvMFLnnfyzL8-wib6mJ+?uZ+Q(cmau%xKAYP+5)YngB03zu`cAVprGhgG=cG`t%!5tFhmf(#G`8QKqBpXL@Nq{GZBjZ zTPs3HoIDRhcnohUd`HXN44JWUW$f27J4mf}s5eNR?@&C>K;Jcn(2>nrJQKxo=Qt29 z`Y#kcl>?vAbOz++fR)u6LFp|dIm)0*T!ylZWiDeiGMxZD*MdF#MA%%XjHS9S(c5g{ zBE8~16(h}LKIdZ;yX?R^c+sT6^lPzRRr5y7*jOWKQ=$)@?gc%GW3y4}VmJ62moWK7 z%-6=Hw#g`U3sTbH{@Pe%x7>+rSAv{=H=Jv`8nf4lRS=} zv5RCoQ{mj{dr>K)gVX^ePS?J;jFq1TB{NZ{%SjkPHOpvWAS^ew!H~b;y#oTXjY|P6Snp3;4vvA1#9ZKk5%cfdTu(39#Wh|E`WZh`IohtJdb7W@Tmm^wU3*Ve#R3c+DZbwK;zf}d+Cbsu`Q zOP$WfHNGD_2%iS773r)jH7y=(oz_slX4=~7>S^_}=gpbgP~Q~aFm-KHeA?`+Sy{8D z)i+f)#A_n9q!82A)W@QIIDLp|(T#mmr!`f_TceTa`ASu{ZfuEVVen8Y8mp;^)MnN3 zae~;!mPizra5C8S&A5c!FwD7h1TeKh|=dTVX1!LB*Hkso5D;QC2o5VM31(uCMJx(fyt_&yA0mzQ@d^ zUw#1I`ntzgpLvS8@fLG~YqH@QGtAt3u_rsWsLmYt>=nZMHdbsafY4dd;cZ z&9qBNTVH;?o#=gRyP0}7uZDSsUPttKvOOPvXb$|6M2TnRHWR0VzjBRFtGm~;@bt4T zFq=Ox)0aMP#-3f}xxs9WnQbnVYYtm#uFEoqW$`n$);vEuzR9y}(Mi|NYOiU3uYHH- zw9{{gZLX7tnXf8Ot$D{Ko@`V;3sqa^nl{Yb;CanV0c*~)o;pw5eDD(2bi=dAOmm%L zcuv39v)45--8{|{GwWTa8jmknZw`CS9O`+@Tm>A`r*LLc(${F{V*Ind^O*A)V)#jaf*1NwkUp2pkLD`f#|7eG6%y9TN z=6Ryc^N)7V$NN0fid^H;JP(-V@c%&12cD1GK||zj*Q5+H1Np|MwNc_skLB59-gOBo zGz6kIZt^VMcKZ6?zhMsh(ld5Z%ekg6>v7K14tVWxj@TEB@tH>O-%^dZ?jx){c zF4<-_d19}7R<)bosciG|OR|Ak<}WXK?3$mNr+QYJ>2UK`_n22+@})V74S6n#J|*4! zT)Ac$=4NoGdtURTnp06PweY^&3zZU#u@9+Jd^beUwU_*IdI#Q=Un+| zADZhw*zx{pt6YoIJUOnR7@#6edX$LNsFv2|SaWrAgQ{w2X{fKRiq$taO>0@(GPPGE zTEDgll8y0(Sba-XYiwF${RYteGf=E57H^I8N!c*9WnFc2?$jSo?VnZ?X{cWxY27$A z8iT5+I$zP0-n{+gZA-GUra6P&vBeEMbL!O0KvPX-b8V(wlgyf`SXJiKsb>#VjyT6B zWh>X0QGQP4h^TN*7HMd1iPTJGHf5`@uS3&{3yT9#F3!v>jzptXYa^<;Iu?nc4y}=@ zM%7eB-E$l9jxs_AsCS$|YFM5*x`6j^nhjG^Q$STHm~`zG-b{aB(mTlT&e3eM2TrWiq3YrdXB= zRz;&Nb*)v=$fW4xOjxkCITnjFWhs?83G+)UgfcldEXW*RJz3=`x^{dtvpF7XiN_${ z(9nE-6b$WKJd8@ux3)I7F32ows%~zI)<>Z&mf0Ig(jf3uyqcjiT4&{2Cn0Y|)4HbS z^P7&%=EN>+=*h@@l~t`xsN{mo%1CB)Rnx>+CSt0-b|d7b!MdJsie~i`r^_p^i%2Et zA{{05ws@q*k?f;CPb;sjM|4#+ZTwNi5+l;u(aiJfV|DO&W*r{HgXfwu;TP?cs@6zm zyeS%QX=!eaMQY%4Ro=RhhQyjPBO79^Xje8{CL11Y2PYkyE~QmRT4VLK?9G_+wWyNN z6o0IV=oZhcZ^B|El9icR7J-Y>f4nD5A&bc3*+18w;nN zR~%P4gFPLt+(AkCZDvo}X7HcsmzD{dFYa!y06O_{E;sWobLX{T^`Wqd(69ZFxfxfE zOhKEw;4-WxoU*weT?-i}onaZznIx&u@c>lb_3XJ{IPr z7hL8pyxeR{a?-i$;Zr{UDV>{{Qxfx2Im&lz=Z<5pV_&}QH%B)&6?~M_(OoEco%Bqs z@vBfjC%vGbZm!1p$f1*-=oc=^GZO4t(&na1^$TpQ6l46FEEjFO_7K^=E*00?CS2+l zR^i}nSH#hH8!AK?tJ!f6k=ek;r+(q!LuKM^sNhP#x%MSK^=mUex8Tk4iEZ|^hsd*& z#PT9@8C=n0f4Fd>YXm;E~WVQsm*tvPu!xD)9w68rxo;f9!K-m$R zw_RfiuAz#sM?{It)~|#joxI&myhdNgeZ-rDPZSkCM+NEuuKh|V*+UB!<87!F1j&}_ zWCPpDMZ+4jWQY*emqEhMZ7z$w%jOauv$+InONcmXx6Ak=uGgt6dQ*F> z;DOl}cxw*>|7l-)h&)K^<6-c4g3mT2GTl`1{TDh#QQ23vfSbtUEhz92Z_wA<-NbK& zPt3vj5S>Ys0&x~$za~J(zo|#9pbFlx!R366PxU-iP%8$&0zR^w;MRY^hJ2kT#8WhF z20Avfx8RMIZw2sC6#w9zJA37~&@w@1 zuVi*sB%uigLVhIJ@I?y|4-6x@jKGSJP26O&3A~p|Ht{Z-O%MmQI1ZvmSRU$61vD3z zF~Ak}%F+DBL$ETSGE%)|?PA*L_AB8pH6hR06pz9l=1L-|@jt->v5_%FR(x>od zBoTMn*B&BIBT*fcYQHG^rcU3k@e?d^U^wA(yeUd#wuGk50BZ!^2>lI!2lQp=4Zw%? zCG)J-d3u^_9$2|LwUT)b*q3}}wB^2cU^Hq3i=X zeY?iTaSf9RyEQxRAu?M+P5uDZlX$~@UPOBf-nhIL@Q8i+CSZ`x6C&`bAPC$DxYfRN zJV{MYYfY6r@6%`ID#*uGY)!$>sZi$$CIRrxBWMazA+w4 zjLZh)+n4-a3Uh($6fhR#e9a0{kP>h`p~Aj&1i22Z!kd;5tLizh)^MHBFj#w56d{QuL7j<(Q7`0 zj>{Ct|41G_Ba2497(g3v>6FhvL3TbTjmyb6x8004E*;M})xwZ;=%P3>-=!4<9R-?y zvRI%A#|BL}YJLsN@6?V8(mA$`J>kw}_Gs;91OgDx3$Q6XM4r4Sx}UN|I(@rFK3a@X zgfJ0riW1Ma*@TV4CQ@6%yg+3QI(fUBD55^%3&JOUtFPle;^`Jk+3qIZp|9gUA|Deb zpD0G7=i9FvP|jO;qlvx*jD;Fp)&gSsGI$q&%E6`Hv+zcwQtcn~Wr$D2XK3R?%cTIw zI{I&g(kHe4B}IC8l{ykCrGITdI<9$OWma}mlO8r%TPk8AE4Bav;jdEN=?@W zEVlr*Ex`%6oUFM)0!>RWix0&}qpYS&#f_^+L#6G;_-dy#G~DXf!57!9cB(cHI@sQb zNrJxHi{leqj??C@U;*>(OF}?j1}gyTZLU)?G_YXXp(_Y~!W(WTysR%*5NHLsjxhk<;kA)iSf7pY<~9yjc&-tSHHYWoj*7l(ZHt}XS|5vqC3gTfrL=0B4%byR)igv} z^{rH=$b{q0us$Bt_fUT|8viL!A>eK8f3bcA6a8g?VVFz0M;9?5FU;dR1O* z7UzX^kb*PRB)sDe6IdE7Uls@imsb=9%1IRD<>eIxa>`UV-V~2UYG#rdEGsN2&ky94 z<_A=`wjQ^To0Zf+;SOrNwFy?n>J$zf!;$6&RlX`1$SGOHtc4|cMHTsh(vqT81%+jy z@*ipG-biSuZ>(p9aW>i7#N0VWMWvNFC80u96|JtXSG6rT6%FS$qYR{0l;llw z`GqCH3T=LIpgd<;V3oo>s&zO|4M*#6=(Z+aOL54R-5J7nhWl1ws|Mqzj94 zf}ud!ia=ROX<;a!q8poHc%H3)*^b7aFR|@+sulR@|?w} zQ=@&F4}J(eD{l!D1p7ws@6nwe?Z^ODKCf9dhTtgauk-6ukR5{PSi5a!{K$X9rt%z8a84O zWpTD>Ss*V^xFV3RF2J*xaU3%5>c+?kJE1X-3kcGwdQ8dcNuoR~_ zDC>}5#M^PZq%c2V`ve_&X&|p$osZiOY#Tg~fsu~Qun~`stgmj4!$QrJfu%Nr?xE)( zecvpqn&OS&x_aERx80Dl0*xZhVTadY1?!f8jS&Y|Y;=Tcr3|{@uz$c1v4}GHg%~5s zo&Kk5r$-WA=`N;y8Yt1%JX^lLbq2lp;VdG3y&k82KA0j<6Tw;gy)$pqs?Gtry17f`K)RnO@cxi-W8)f*o^K zeJh%~7Ap+)ZRtOp067|nK}DQmQOaD_6g+g*{6NW)QoB_-PasN5OG?;jb*tL*6;^0* zeG@zEOnfj|cap-AqQVl?QO~GQC^N90fVdng(GR+?sIcytmHE1Vz&VQpSZhc~q95g# z7UvX}IHQ<7otIP;V-CyHIf^Ta$_s-znChU5fw{b*6!V#MeB2zzlVU8zp7juhq;z*J z4CMz3a*&-I%(84MEL|DpHC$BiUZX;sh44{Q9w>3v5~U?r5|!x*lyQcMhYHG&C!CYZi96a-RUNVK zh=-%H-r|Ub5xXaFIM3p4XH&ERw=Y?0WlkX$pQ}`4LrZ@y?tLSB6`wloqhh_w4RfAsbPOEEfj7)2)Ut1SzZfKrX z6IoMV)r6-a)=uMs-u`G_bMDl>&xTD!UM$pfEEg{cR+J%vba^ZF3W)W>g0muIPn2aV z!+I33=T&$K`3FTsGZe2rLp!htw9k= z;{wkf%kAxjvzOA%gmlhh1=vY2oT}FKu2LGC@pN7k4`t{E>0J>zLtMCbx#{$KtY~x( z42MER@MRf?e04!{b#*-^cO9qpCZMP?ge4-@<2_3ZPE42%!p@9RWACKs#44g%&PAGt%AfmyIRjunV&GDg9$S^VpMP z!e)v(gDd9fZ3C_9V@=OWa0%u;v0!mb{n~cn;H)aUEP{DGd6@eF} zogu_jF7~T*Al8N2q^bt(b*|B|_ra4*TtU=Edl!{>PEs!-u&}|@pQA$-V=9JJJzNBH zf|wm+Rh;;1u@-5pYOxbgR!MnbK_S-Jg{37dUQZt({I8gvaMi(sqYk?>hV{cm5bT-R zC301?x|xqu+3P5K4M}|kc{8Wao{K30gPZuJ&yfZy62UH`8co3V*Ih`Dtc@*U98iSq zAYqbTt%&|ua}2vb6kSna`%(8Bj_Lud23Em6)e$_Pr8}CQ3)lxs^->g#7FtqTSy56E z(z5}&BrHJtW3O&!&}~|rTe>n-ct(J#>RZD4G=z&{yJmR&1zXSv=PG;8jww<&SRLco zV2!<{N3U8jORvtcaMVvv!6#gU1OtI(^tZmw!6dN)GYc0GGi;b;13Cqnr%;sV8U;l; zix=C2M5rPZ#8y#Bmx23Qnxk0XwZ`Ibjk6v{KE3cS4Hg%oloCAwV=Bs#y{jZTqZry5 zJ8zbTlZR5h_gsk;KoPqm0;|RY1+)aVHs#o`2bW+G zqSkEWZt_1JZ6VW=K#|@VV)+J#Eh#Ts#f?UFYeTJVj&tHfQG05E{ygqe6pX?0oRO`U z$dJ&ku#a&HOY#FNRV(M|sL~w^8=EqPhVK~=^bo5*`ixx|Iyk7yYB-Fw0~X&6@kVKI z^oYDNG^uWCXOn1`?QGm=-3p8vrM5Q^3ZaU!K(QWF`G9qVPtmDdjO*omj9cZF=C86x zlB();Sa0aTq^F;=6`dtD%F#m#MsOJ|jLz_;+ zN)?BKx_6^vu6G(S7b_2}SbH0VlV7iR9`;aJ%b~UPP6ta$9E;d<(@c9>LdV8ziIK8? z1M~54sR&lGD}?z#q-xYhIK9)Bo>=KB3^YZ~=&oIdDMz<&-_-}TmZSS|3}TS;5JaE< zFafPwL9dh+6ku-_X^}CWjVH4)CMg-0?O_s`Dsc#gp%dpQ7$O~?9eXsL$Av!je%SL> zx7O?3vBDQA?1O6=`}O+Y-nipnQ%{)MO7C6io9oMg?&>9yJK|K^WydP z?vGXBb|2lPPsfn1h_R0q4(F8yS2+`9xT+fcgo6&o3a7p@XF%53#UR?aA?Na+&$X_{ zI*doPdY#jXGc9{{fehR*^YoYn$uL980>s5HYp0Azo6aSuvu^kUgqGvVX zVQ73ao?438#)W!`&m$t9PUw2{Own9mQj&pFh9hjOR_r6#a2N_}(0pofUfzPtN%?xs zZ!cn|o-$chGb$^(u@Tk)W34vUIajTbhAiEJS$cHNS`&?`ENmU(Yr|D**03V@PEvz# z^dVOQ&6O9@o0*lmXJpOjOU_QrUCYy7M>!T~iD@nIHQWQE?B3FFT8#Op$DFf=l z%4}r!$-;~s$-)ATk8|UM`2Xz-H-m6TiC@IDUyA^VHz{zdR=;?o0#A$dyp~)HIXuR~ z`x(s7TO540WW3OL5=_4);Z9QG%efVDGMJSAzvQMvhWecs^_}cw0@F#$O}M6P2zOt2 zr^|Uca(q@Zu^!Ve!wqfRN@P9g1E(H*M9|5DOJ!!`Yn+bp327y`PSm&WM!R0r$ND+? z&XGJbfqXr@NU0k8?vSQg7T=A6j@-yR+@wq}g!)Ks76j(g+o{frX?*V!boeJW;n@X;NJx7(;hM>(LN4(|U3}5jgz(jJU+5J3!;vEdo;p7hZ5W&P=sM13PS;tQpab6$=1q}ut(cV3kLy+Z&={|WES2nard&-{Pum;MjXd`){GI~qJ0YQSGXKne^g__i_ZBE$*)P2wwDY|MrpH0^ z3Aee>Mf%Eq^1tavKLeW2q4B#5l>e|_`ltQqq=YU^d-;86=S4cRA3d=jeQH0tq95JV zkG`NEy`>+0186>bRRyH|cl1ktq94s)+;LvCm%nP}ymWow2j@lF{(q4+hxDv|=}Y_3 zXZE9O`_Y&5qi+H2eD{O)Kin_<#eVcb(9ZWkD1WqHy8g!!QUTgKC}Bt?eOx~pzaQW8 zV!FM<#8;7JH{btur?Y?Q-ShQ6~-*kfp6c}&2rFK=Y_I zYHJ(fIFrx`xVeRg&TvFtk9c>^zwGF&=a)7k;rd2?GtidCw+;E^4WDb{Jv}^vA?}j0 zS|cbC_xtn{aSZ1l(c#?v=oMn<^%&R7#>q*IK4istxpYuUCTPdKTOOG3Y^OJyi1sMd z)ohJ4Hsj`SPmi~&Q_CA3`f$b0Zr3|Ot8QAoscyCpGi;yfUehPbu{E%Dt%>8-gdBfh zYs!0jcD`eup6ji_`sTh*>Lr%+<7s`Kw~IDOr_!fLs15Ia;8uYKn-^=X)fboxFkBkg zoSh1EVGb%3x{UNNrSx76>9vynprr2*dauwglZO0$p+6xFecuUfV68x!|4f7BjSzZ* z&{;y?O~l^gEAp|xpO3lQg(oW45Rb=CHvq{Wf;rDM66<>)=`z99!v6(nlyfI(l*^y& zabdG!Vy+=S1?a+__*7yhew>ClTB(bPWAJ0h#IZ^}B=k$farWH9{F#_@Sl=bY3E009 zC*rYFq4_J}u1QM$5oqA)#^*>+#t&K(Pr|QA6S4768vvYwFA@MLmrELQ{0}Iusrb4g z5ptWDj&j>cqdvbC{;R^@Pa667LpjucMEGu;OHe))$ov^X^Jn5nPZyfMxlj56(pmU^ z6!Annv`aqh`XAEJ{}mB-&4R2k4G$O-k-i+r^wmU^-$*{*8%U%48-)Iq&<_gzl+gTf z9R8N&2rqC3^a8bB($q_YUj7b_Yo=1aCL(zM31m6nlSVmS*g|?JknO`C7$-f2G}4QN zt`xdj=q8~r7W#71$bSRz6g(#_{3l35&t9Ql68bBlj|iQPZ5zuS2c-O2r03xIdLm>t zkUtp@N|T1%>!cy~q0pa^M)|2Ym|*%aplcq!KO*!3q0bOHEHr-ynevyAhQ2PLuNV3b zq4|5u)X!fYru<$>-!F8xq<<~+50XA)kS)*uAw>OILeCevUFa)?{JN~H z{$gT*Qeh&>Ighv)-|PTVe>-WE`%|GGCk_425TXB7@}X}(Y3Tce2z`f%OE6wA9eVid z(9FmG97USHjz{`DBJ^w_A9}WuhMwz)&~rNxdOjw?e#QpJOFt3*KAQ-CM}hS7J%T&P zUy5-Eu|YjKM98fsF2ncBh(-852eBCbB9>sBBbMUq2Qk4oNCncK3?lTLLJXq6GadG> zl=M2{a`=t>GW+kAfAQx75*Y!SRr@Cw1Lf;S1?FZc(+oq~TBd`s{jg5L@9Oow*y?1re< z6+r$L0%@Mf5P9}OTqCG|V-WOaq4|rEOut3&9zp*2Jo(QHzA4x(_^n_vd`CG;aJ=Ab z!92k-!79NP!Oen~3tl65o8WzdhH01M6Ffn1vfx}n{`fHM2?_Fyfpn|jPXwof>FVZf|m&Lrx$5om*956p9|hB zc)Q?l1n(34gCKvjk$RpI+#~pc;46Y}2)-luq2K|*F9g34{6Wyf7^M9u=ocI&c)Z|f z!HI(Wzi`YqOK`p*|K}0;0l{U0%LOY1&lao}tQTw+)azyFxlrgWf|muHvI ztKhE%e<%2W;3Ix3mz8yL6AQz!1NSB{&NV@ z!v!-1Ckkc>o+6knm?yYYkn4Zy;eSRTh6VY5EJ*A905B%>g@XKNHcamn+$Q*Q!CM4> zEqJ$}-ajCp{#jk%Q^J2%@UMce3I31Z2Z9F#_3uF<|93+3W(@5~791=%OmL*&SizG7 zX9&&{Tqsx|SS(mBc&6YQ!Fs_K!Se+#7VHqbQt%qV8wL6AgJ}0%g7*pPUt0j5KZMQn zX9S-Yd|B`f!To|C3w|c}wcrs!6Kg8!8z{)1G$zd-MIeq6oFF(=aJC?Sn3Qt*#}I&p zLI(x8KV$kif)T+6!KmN`f?EVT1%D>^Yr!3Ydj#JT{I_5#_gyIO1i>kSwSsZMc0vC5 z0_FcpkUzRWdZ*xD1>Y9@RFMDih;k`dh!IB!P8OUexKyxSFfMqh;C8`Z3O+3OwBTO_ z-xmB-kpF{Gm(P6|%NLv?c)DOraI+wPmz?sy5d59sV}g4H_X+aHS1Es3kpKOgbh_YJ z!I^?Nfm~E^XA+2`1ZN253G(+6n7&qUqagn~3;8z--Y58!;ERIq2!1B`gCO^(%zwP#NrHO6 z3jPwID+S|%+@CVvHG=;o_<-O}!M_T=E%>RRiG3yW`voTo&K4{XTq$_2;3mPV1b->` zd%{Egra!50MI5&TTBko#QZKS!`p zaFbw{;7x*m5Zod7l;9r07X)7sd_z$0r%}#_LLU(PLhu{G9|Q+rLruHV1cwWb5*#mh zvfvECxq_z&<_Q)Gt`s~+utxA)!4|>wf|~@}1-B8ghrCwsdLrh8-wNJG#8~!((0?ML z9xoA*?{9){NcsW6?*xw$A)h?LmQNA%6H!hE5$R)vo*}qUuuRg=A)>rBg0+%25uyJ) z^4%}^kfiSxd{yubBFgC&{7U%l6Tyf5ULw-dg+5;B2}I~WNia*&a|8>B$QKm4Lg=v2 zH9|KD9Tj?uV3+W>34No`cMJU>5#>K3xI@yPlJsYV|7XD$CH+H5|6J%Jf+ynao%WtA z7!X`37!kZk@F#+|3-Vbh+Jj*f|IWhxO;*ygg`P(Q9Td7;=$OzOguYhj>xI5w=!b-U zQRr8NJ|y&4LZ{LWl%Fp4@EI@CvxVmKdZf#RZV7{Rz=Y& zM%1|1YTfOktyrzKRa;zIcWdifck5EOT357n`+wiP=gqtc0qy@c`uN^C_uO;OJ@?%8 zy_uX8uBxysOSvCQWvMi!RBqg)EYvVd6{v}>sK&;PZ$vk|=N~*gaKC@L@+tM!m*0Hz z&1qW_#a?=_WDZ!ncv%|{4-8h$*>Io#(8IrZwf$Uub8q{((6`~ef{llNK6rR&WAe+v zb8bg>0n9Ww&fsN3ME?pKiZG2!1i|=Z&lXdOh9doYt^IhY=4kc_G|8?H@zn%Rq<&boHjp)DO{i|w3{Z(H5Q2oF6 zuYw)-uY&(`yiG#9NzXFf%7m-8F$OF1(665HvNGc?Pg`;Bro;^C&x7H>#>3I2^K_Ta z)m=KYG5mp7#c5lT6SnQuUWvhyTzK{Q3|8X@8xPOZT{>5H=@3VQMg(WBu|ba~!$yz9 z>Lc&lfH|STYMN zJ$|~Z%t-n_%@?jpMAi=H3s-KiZaR9Go-bV1NPZYTUwFm?HybLY=UbN^tSm>5(c_KF z((PBi-SJ?@?Ux*J{B%_hmdu9%di-=*Bh_QRZqFT#pKf+|aD@56P4&zVE=$+$f1MxP z%qZX(`y+$o#7ZuW1h-$M9P&$Dg@UB89@D^5yNn%gO|WuDp}Lb)*4X`n-w#F{rLv~0VDLbsD}@sDZ9u7P zbF0*-ao{PHL!fxTv9iVngUoG#w8t1#*%4>aXr)HGnw1Jl3UV$(zI$twSgJ_mD>Qz#{ z?02BV@6V3+B;c;>FA+9bft){MknmlK_{dt+Or`fwcGGEEsp;}3?gY-+z2Ic~bA11r z1nNSjkMigEe@QuO)F|lkIgs-&;E_e39;RO4pL-Gtv{{ktTx&J>z9MD60@3V=)=xF* zw|(P5P7*R;U&tPnFJ#ERpTY$~=Gy2qDtjj(^X#9a%Go;$Szw=rh{@hX$jSC6C?R{Y zkcD}&m9la=;n8hMa)mKLtESE4nuE3NA^*6#S~#F`{69p796uu=!~kJ+#$1dWav2kv`)`*!6WmWhjHPUjU#s~XQ8;R~u6PXx z)#^);HqOfNPs&1gt%h`7V7Jq7A8bR}ff**8RB#9t3Cxt>3hs}IFEC5&3f>3T2likl zUr{J`cjySrX6Nx+Q+-9bx%VOx1A7|A6fj`Q6v~c9`GL8-9iMB*o?)4v!7p~ZTc$;- z!!5Jg2Gwc&90xz6q2k9Rh+WTzHJInE5|&vWRGiO$ie<0OZ>-+X60_yx|M7)C?rvf^sI=i9)3Y{^qVVY9}AMWP-7Bwnz9!8g%?!1gJ+}$|_ z{29(1+|P7^C}o!ODpL1w4nVzTJBPyBJ)NII!yM-Z?p#dpS+eu(wkHOBOoikl)8S5SsUOz6R%e&Vfi>%~^b+2*`gfH$>&Hx(WPs(`^l7CiC zG0eSRIa^SJ2b41bZTO&a7D4Yr%K07)d{{YOLGvTZ$wwnSs+`^7p~sYS0u1|$a{dLK zk1OX4wEAC_a}-4WrkpQe?i0#+0a~7fG8plca{dUvKdqc=P{K3Hxg1)aRnCbh_V3Dh z7%lUha`u8-o>$J9F#ZMQybc3jRL|zOEb}(%w+cqwv$4%2|i(|5VP?2i1tLgArdS=RCOeOXZA*|CAXEAnIH;>a@bE|g)9 z_whc*KM1q)<{_}^?8UxoVT*kg%(D;h9fD-)sDv*2Kq38;61~bkNT|T1)>dVg2o;*t zLb6oITzfYJg}p?`Jo`d;#x4`Gz4%&Go5WD`aK<>CAhGZ$4b2XNRi%GiXV@a41Ne5XmP=c5z6L9f}pS`x0XS29PRq=xLvS+}Ew%(d@f-TI|6d3H04JjSQs9$!&`{Ss9j zD`cVFPOq(#ytC{JG4$C#5OR)vIeM;rvXJv_`rAIm_Zf=!6)iLkbh_^=O)j#hW5lx0 z5OVRP&NkG3qput_VN9LHatD2Nnk={PWfeC0qPn#z?ZeoD=lFu!$g2FKsp@>=IX_%k zm)}Bx3k)Y~Cvtv-E^l9GIKF&xUS~jW66opo|}a;h8%1hm3@nF zLgd`Wn%*j$AUKHpuMizMeujCDpUeKdU%-7wig)whW`qCU#2!a*%neiMWD zKH;F2s-U;4P1%1E4r;0L_o2;y77l8u@)tAK?ibEzaz3R!4+zI5=S2>t4+ILzwF|-|o5(1?;UHwcn5~6|!GoEBw=Eme;xV^)&u%>0x>H zatgmAWPuqZ-jz{dvb_xRzWtu$oo=7NCjOU@v+R7v()&Wru`eX~Zz1Q~=P>p@5OU$9 zSkGEzf9Pw`{eF=dLO$|!YI3o?ABVkKMJDK-WA=cKFLzRB2z!VfjB& z!76)SR{u+xmg?-+SV5I#>f2xz0sgG(v~yP4bEqmO%d80wLpRETJ9qjQA_M!TgONCK z54PoPK6bAh|7P9cmV=*1BPNR#`7>xjC~H2n>bXzlchNUvgoC+H zmESqn9?W`(Iqu_Nc~;hmT8pxO#}?cqq~9(hdA7JcVE>8aInqWUHE~Z?@!YIak$D&Y z=*e?2ggS?_OFR2xEXTSPj`KNhgPrBHXhlkNIYo`Y8iZu9xLFHyXaVw1rU30q|D${lAt5;bEG>GT z7G<$lQh-1}KA`V#(~YP~}-9)KucHvP2l zQ=Rw){xz&S;2h^k(A?~fq$o3iz%jCP`klc_9eykTdKvX@vqU?LQ!^v zDgV{wZe`Fc?$%NR_;;#x5+z!6dDR?*|9;?XU1GM@GhPSV1QSfqVX}U+JEe^hp9v(cBaf2mf@KlCy z3tQh;R37|@-K3o@hq)nG&pLFlm9YH?KFlWSWRqb16nvao;`G0-s6qMeWd)D=8f2gV zPCP7l^Z3)PZv=t{z-3f?w1<(4nm3Ee6V^;7z*<{sqmjdjT}E9}L^Agvq`Ioc$05 zQ*h0O@2A}iXITTfmmdsX(Euq9GG~FBHl4}_v@MT;hS_0sAgkN5N9RH>s{=NVey>LMqGn~a>Xi4Gxqz8lwX$Ng12SKQ zf2~7J=0b=haP=YSFOqq+&U~2>{uJ$M)mu9MdI)}q>m?*jMh_{%R@*wn;s`Vv1{Gm* zEo2o*ZnlL!8#GF8V9AxneF{pVxE@DRgvvUVwN(55O9~fShalRlQp-9LLchXwAi7zC zf?T!0Y3%Svfd|o}!M66dEPYCd+&6-K14ZGA{d8@f1&0l?pKg$yp&I7w3Z}Kdm{W*s zgSZYu(wofMt*rSv>lxrM>wKN{A(QnwmN?5~Jr~)=K~)H0cmTZ3QfFEm+!ldT)Iy5$ z)Jjrt$xN;GQc`WCICH%KN=>(t0BfpIn+uf7yIteO}#KmpXKWJ@xpTbM3G&dI^T9jx;ComS& zYr0pbb8x%>w3=ZZkDS)$x(ltRB3w@+Wy;PtB-LH$GrerVATvw%pwHNW%0VLU81!%J z-#YIH$QMU_e~6S0}a zGCazi*@}43)UBj+kJ02-qv#LNY2BmCEQFE-u0^QeaZqGjayRX50}G{=Apor3Y2oz{ z{1DgmNV!)GyqyOA4UAb_=~=h4YI$f5Q}NrWXgNqIx*aWJZPtyX;QV87UBYpBGE8K& z+{9qH51g5Z?VG4}6s}opQ0peDtptfSvKewex7H*7W4O))cOi7ldWwVa&*+2OC^*A< zk~y!`1wIbJ@1uP_M@kn9L>pbfBBrBE#>5qj39hM;Z!~ISU99t!AkPiBeuk85nGgN< zBIbKi@?FGylW-y5J8+G4w$8U1dFG)RS0ZJrl(&iXI~5GpZxg%jwIt9~o2c` z*l}l}snu-j0*sxQf>?RRNdnhVNZHf62{P7+)_O1=#B~vvdsssl&M=^J?&FC$4~44n z;B*#`R;)Et@;=q>X`P9o#ae8YFgQ@x>2T~M_n|Fx+hsa+&R+1jHSb`yiZ$m_lx*!S#Lwuc z?+G!NVYA2(Di>Ao;S`&Bz8E_O|LXY{bCFeCtmY*L`sa1UTjq7Nw$6($T(s}pu6R%K z*ts1&$$1Nl_b%RhUc9HZE7=w^l0wXDi6;g!I2pvefpr5)wf3*;OLTN4W5s9>r3Mmh zZL#*^P8g#S>-u5?xP@t8$9r)L_rMJI))hcUNyNKjCcVGCb*{T7 z?xF;g=_2QL_qLg&j;`L8<}Mb59N6)oWbA=9WLb#=d__)R+KOda$x~kE{Xh3R2>%_L zH4sPy4nAOOpf51bunyWU>zH%3$Q$230ROGZN(2(GAF%aru0U4u^@Jt^MU7d>r^0lo8e1C`)%BW!fh!sq0NKnJJHDG;rP{HjdCj%3VNv=E3&-6k9 zUf7yZ>*4gaUPz4Kg*EWP>eavV&2&~&X4M2<@60NA;Et@(zlSpdRleEIn^O+VI^v^0 z{N*m+1oVJN&)VKK@t%&tx}|l+=mjY{I96dUnMR{S~J}B&DMS zWwm6;7#(gITuHW$knY-7h)CxW&MkxX6@unxJ<^T_x@i>~(&fAP*_Wao8RmD>jzrq_ z>ds}|j_fW(FJI%)JKQ&1pq=DNk9cguh^jwaZIyduTt3%Z5f9(Bmn*K}_7-YQ_y^Nj z(v!#Q3)k0NIqj%DIhk&+JzX2P_}QKfTCpFpVVwMAq4-l4ynWXJ^eDQp7S`mWmQ8G&>m}Rv9*7xCV|O zhu~sqMD|3MM!Z$ur%R)3zvc~Tyd3wIT28o5vy%bhX2T}zK!cx}F4m$^f@la4Z!m0v zXn_CBXA9tNT(p;XuelEpx$pLRXA5|5>GUCuTXAox6@>q4b}~R*fNWqBcA&veO&{Yz zjR~S5MBGzrSWXZP8TN_|0phz_LzEyIa*4ZZ4N-z<$OTt_O28|{#TpaK%zc2!0|IZ2 zDchoXLmD^X9`+J0)a+z{_!Gk>>_CH`noifEQG#d)5r1sh1ksSHG3Se$anWAlE#^Kz zH zqP@f-a~~k`5X5UQWqHo+Q$rd{a1XVFC7PWK5RW!&!f*}i!8;ijOCxSD_W>eLQM{#5 z_Gg+mr12KqBTxyy)$C+|__kpacA&veO`Emoa)M|G5nnTGf@ny2$74f)8g9^{QG#g5 zCBA6b1ksR+Uk+dvF4mZsW$y8W!W{K@YfRalbvni~U>PosXMhUL#&`xi#IOlGEb?mL zilJHa5`JQ%gyYA*cyFG^Z$WEH1DKJJ8^#2END!dkLZ;L=0*TQG#elwIf$xxDsLc8TT~wP6!PL#i*F3!Z2Q5%1QbQG#g5BYtk!1kvCw78F;c<8{pwexhUU z14Nz+dOgBbYO_iA6I;!FfXLHAuPj%tH=A@nk*~xtGKf4w94`Bi<_#(0$G8xOgsqyL z#MdkEhMQp%hHKzj*uuqjC1#oX0FlR#-qI*LOY?>_uEISUh|sLr$pDcrzJX2Hfd)S{ zMYZU1f@la4dkmW(8d5Fqu^~VW)mk)45DmG+HHJ+P4XKvr%Kl_rtTAzexepL|R_d)W zWv|w}A&rmX9&tu^O0$yz;wy$t*ntK=HQld8qXf|qB0g`}1ksSHF?Sjt;-bC8kIj96 z$n#mRy_7A`ydjM@kZVFw!g)bIf=L=-_Zgot=& zk8FZyNcq=eLx39I)f%D%(U42rRcnY6L_^BI+*g+3VvUJq<~~5=vAMU#lwGZPLmH37 zJ^V{((d=Y^IAqv_;To<4?J!zPG^lz%-o1gPN#EgB_=hFs!{ zhD{I+DgW}J2frJ^8WXe3eSpY^AzuGdc9!O0&H}E&g&Gr@H5+plaKNw$JJ8^#hNu=@ zP7n4BTMu14KT$@z$8K zmulXS#(QxOwS+%wb}~SG#IOm&HSpZ#ueewm@d5<~~5=GbgXTlx@*G?8|}O zxL_E8-&LU~@fyP>>_CH`8e&>BN)Qbp;^l@-5Dh7Nd9HOcF4{}H#oPyoeAeZ)m$HxP z^dXIs-si5Rnf{VV_Y>d4h4?0XpxMa~aXQq3O%M$k)`*4x@oil22thRD5~pYl%L$?( z6`h-rEE+<@S8*ZY2%;g6SfDjT38EpjmgXtm0$lV6ac^@UAo5wA*CRaHJK3cBi5tv) zfXGL9URj>@{ne!ViBFjO0Fh7jhReRJ(}xss0@5v2N0=g_L}mlq^*_%HOLa104_IdI z14KR&^p@}@wuji3{Ee*JPxW>QaEQ+KQJu{CWZ%oe9^?4AQnkY_~wW=wIi0$x%i@pmmllVRIIJ3v$?0O z3qIicAzq2*zP_$_YjYyr+aqSXl6)P+E7=w^6uqin`0ysKZSIPHA<&zd-knPC>*(_~65r!68JQ3}HqqbQnrLF}n%et&yPKL5iRRW$v|6I6D?X6W zFLR{j=^xXid@m!-_cSP9x=1HvHYeYuNT-SSQjNuzC(@}I?a0?5(n+aSHEtL@re1RaHv`r|CL$CBC4-16psZ=rB?HYVFz+{W}#1p!Iqa5k! zI5?1x`|WCywRH`623gwJP+J}@Q(e719fkbz^gy!Zs2GB%6?N%|wW54V=wzp$U^p-&X8qL+E zk*e}YeRTt#+bXvq;I3GFE&K+Z(P&jgZGBm|p(;ue_bcG)`c-vqrAw#fI$B$= zQ_5(x1+IqC$MnY&F>Q9Thjom#>Bj0omsj1*@vf%!-mb3RW0HMMcy}n? z)6^g9>srTqlnW0;8|ouvsBW2Q&Nv1H)zseA+%e#`Hw8j8XQLmd#3~f6@Kxw?EJ>C^lP2J7?YhwKas1gPM zhAlNVgjY6HRMoBsm#gGJtf?(N(5G~$YJWjM`@cS1SG6jNxPVL89*{;-X%#Y-)tI~kb48t?+J-rH30wPi!*V&td zw~(&_@m0H`v96)kTfOwCkIGdd@WL6j_YQS3%t6kKIi}*7vx7Hf+h!E2YirQwM2Q}_ z+L}@hGYWLC=FplsPNQg4q^`EEsx+$m4Et|Yq&mW;#EU(>NiAS{e$|So?nDF4YfT?Q z*2WsQmmS<#T}Ne7WxTk9cJW&8t+}bGJIos?TIZQxGUlR|<~DR!)s{31hgegh6XDv1 z7;cLltK2a**@IV~*3gLR()wj##6o*-e|M9P8!#i)rFD_=D&5rVh7?>;8fjP-US-B@ zJ$Ppf46XfL?cT;sFYJuxmej%l=!jL305;H>y3&2X&YmbOY7ZM`{{md>)7&hj>+-Zp3c9-X`nb zj=l~vrnScr#(dpQ64IlHlDRX{AB)jwGphq!FR%$y-d6*yz5Q?;<~nu|69vc>MZaEB zTCZQ$>rr|+-QLIE-K6I}nZxwvWrR@%-KaIjrA+^@S$u?{+O)s8mSKriP9oOb*RDOz zSput;x@D!RuQ}04UTJ-O?TWI-dQ962z5KYCc2#Nt42hLoBA6hluB>aUU#c6c8o?AT ztH&U$j^*2i)D>+gg?cj_vNv@%AB)kut-tvgkL&3$<9Oq7JvMF==%yaBqR=x$x>sbx zbz5JepF>bT4Jb$1m8CTpWw2bpz=9DIt*vdVsbwWo(=&rW_r5M{VB)Ph*u;ob-3JoQ z-F=)Pd)x4?n^ZxY>#p{Vl~KO)7KxUJD@q%y8r0hOKpd+s9R+4~SDe7Rn%C+19m`T> zb~H^#C$WcWk7LwHua5M@Mrz8#E8W^AdK1lEjINfpb!zP}wQP&+O+RL(R*Lm03fC(gJsO)u z4|(uac`c%}MzJSxy^pu^v1UM$UXuXfn%b)68J*UCfK6jyG3grgLU1Nc>EF7+@s488$)GRr%_$=ijUT*~#7}(1M zMs;mX7{lc%!(6D2>uqg~w{cNB(#nOC$+iuL0@<k534_dCcrc4+QWKNi z4PC7cNXTjr$tG91qmlTLDm)X|K&-hR^4k9uWo4y$SHuR;vt$&$(7l%9d3EjbaBW3} z!j3XrRa+NU@FdUC+J?8#c6zEA4m0;AY5+TI#0L6Te@t%`7zEL9J(e0ZwUMaXB{3i; zu~kj^!{~}4M#EU9tWryB8Vkz`^(*z*?XgS7(uNJs%<7rl5q_ASn?pTAaf{g&@0TrO zM}Kb;yDC?e?oSvE>(R!Mn$jf*g2+<0Z??sBXRfa(+iU*9@99|7JKoe_#9f&346u5O zi30(wg7v7i1W~4a&H}J&lkqkkvm-5Z`kLdI+VrwS&pK?_VM7hPlv-@?I6!v?EH-Ky zA{7y|b)>dN_qA}9E?!oy9GdIUf$OpBPUzU^YewT>^kG}!xJpll+b&EYg-u|>jAHt% z!7SApmmC}}!;YCV6Fe_R3Jvub_%Qz`lKnk6Siy3`I0)gyZy%(lS!~VCBG|-eLuGA! zZR66)Xg$tzVm%#ZnW8<7u7d*?%mZz)SRYGbc)0VPOhtNR(v1_TMr@Zw^wNEKB)ozd zpn>Bc2TPKk0aK1Xa8SSmwpR_ZjI_F~(Mu-11WYgdut^i&|woG@*w*3I=i915rZNQEzB87lb-B#_4IBJi{*~qUcDnjCOW$e9jde@ z(vV)8vxL;J&^*u@kF!=7KufvZ(wjFka$+xDSBZg*=M4S$u@v16=q(v1ykn_n95rVs zk(%W={4r-cJdo1UBEmj)Zi=wJ>5sQ0&HAOfbR{;J zI0n=wZrG@`CUJbUPU#_+t0o<5+$wO^@{E0%du(LXPXbWv3Y^Me1BTOjS=56kd+P|! zme?B9 zc>Wbfub9`_+Z~(N6YuCu^mg^mYm2qSn|tQ=t?8J@j%5DnZ8>Ug=J${0qR+XV8{ak> zR`v)3j%2~Dd znKLAwsu@2u4e(4BYp_Ir?>d@bj{e-8p{a@qt5lSym(Y4gpodMF7Y6!btpkd?6WyxO zRX85aIBP=hjbQ+6#Y!B7Y4fbcqemKo?h&oT85ee1oRBcO^UGWi_2|i14jC;KI8D;gtd42! z=RqrVmE)vLHrDK(TtOyu8Jq{AJizKp_H*g%Svr_8r(qRV0>+xE+M1;iY|TC84<8{@ z*6BfR_%kA?DUFszB4w4OI3KD)w?n1S8;#*OH&|lMZn-Kuq%jh1(7VxCTcNwd!HmjYz)RNkA?FO7SV)sV~-J_1{#upe9rYF#6dP>5Y9h?2g60=CwEKZNQ?e<-W)@w@kB(WmfOP}Mn z^d76XyuAbZ$(B+}%gXjIoK>#JEwhH3yU!l7m{Y|A>$>rr0+{GG*y-N&$GVCWd^%99 z=fL8YfdSmcT9O@2%`GiFi!P>!;owBQ*GuyR0(394Qul)51>WR#u4Pr1w9 zb&kT)>aq60qoh>%P^gMqd%O8qQWf{~CSt`{qRz#cLF*d#LDje7R7l`Weub9}^``{? zdY^8&F9zV5qQdJtsZRnA$1cG$a6I_d`T1-NuTQDng+`M8bmFrsz;HxF*r z3&r>bw`;5?tp@jAeHWZ%>P3C5pR4Z($+H)bpAQz`T{3g4|7BUc_&qLfxp~MCa-D`W z_qH4N-f}NPx%^QJmW%f@QsthAd#}F2eevUtsdqKfX`6=0^&O0#@*JVQ8zJW{_r|l+ z^+nU9%DrlszSVG4A$ab`wdry&y!vj1KE@pDL3I7M8TZUH9~VEzLEm+FYVUrS#_JA2 zmp`==uTQ#!C+$AZJ(Cwh&iirg8xN+(4O;F=kDx0@^n|5)yi2Jokue{9w;n{+)vK?s z4|Q}K6=|+M+-7{de82jTUj|QovWDf#$|!;5c?v+TEQOcHJ)f*p?>EdW9l2?NEWY&S z`DEz`OEa<*UXby8viNgVo==wcK$?-ICZq}6rN6aj*jdU+X+$$a+EUX!Iq1jzaMj^z z!^QMk;1*o#gl-3xz-cW)uLru{xuyISpbODp4U&F4a6M@DKc+tlq#OB-J<|UK9tqmD z=L^v8cV(Hr6Ur)tn>q55J_t0wm%#5ll3ocq7j7>XItiNJB!~z-1bQ=QSO4{(*)05S zEA#VPSnEN%_2qBZy5C!6`WK-2{;V>3GO3!l;ClKTw77@6~O?; zYSOz1t`kiP-X^oIoB666?9{$3bciFJalf>#P|5qv^$0>&=N?=wf`1cyL$DC@9`(!@ zEEBv`@E3x23Fcznqx>SlWrC*&@`vJ?ex2Yef?W2H&)-5P)(iFtZV=oe_=@1if_q`U zWWGAVR>3O;w+KEVScv(O^794D1kV$^TJSf5?+E5%9%a5F!PSE617G$AP<3vGj8!Yqr?+E@!kmCo-&lj8_xQ}4DU{sL5I6(QM1=kCnBlr`+UkctS z_^_b<{Q%^DTjQg7tzc1&(5}Y7dAjo-z za?=H83(gnZS8%c562VHr8bN-un|f9Yaz948U9d}VK=3%hlLgNZJV)>%LH->A>bX|% z2Ekto{!Va<;QfM+2|gwGg5Ya{?+AV<__^RWf}=3-vD`6&d4jtL?k2d0Am>xce^2m0 z!LVSJAivU0xz&RFQa0&M!Ct|&f+q-`DmW;3p5TuJuN3^L;I9OKBY3Cay@LEbP?q~w z!Dj_u7JO6iUxJ?qej(_?7|;B+AlC_`^982}?k+e-aBso=1xp1h1#1QQcRQ%>aKSdg zHG=(u>jc*eo-TN{;Dv&h30@=k3&EQOZx{Td;GYE_6?{_gdBJ}OzAeZvD$`zm#hCcD zU^eD>(jmb-!D)i?1uFzs3dRHzg8cPF>bXns5y9sL-x2(eU;yhP%I6Et5Zp(wT#&!T zOt}`pqXl_hLH>DyHw)e+_>kb=1>X|y)F8Hya59>0@j~6TybXMjF2P3xpBH>b@IQh99EdR=|B@JShTuMe z{Bu|2uMq4N{DI)vf>#RuTJS!>rv={<{I6gL3v24#MR2y@eu9;P{GD^k@vrv~&lbE~ z@J7Kq1RoZBS&)AvjQQRb{7~>S!LJ0fupy_MEjUhaqTnuq(*$P<77OktSSNUv;O&C< z3cey3bWC~s3a$`5MerKI#{}OMoRnws@ekY4-d4f&f>#ONFZj0LCxYJy2C<=G{+$G8 z3hpCVCU}TolVG>t@q!x#FBZH`@D{()kx&DgTC~^Y3R;E(c$_CFToG zAtK*wBIJt&_mXt}l^)73BSJ1J=_>>emGoZ0wM59BDCwsN{!r2{5xidTmqf__j)?N_ z61-c|pAdXi@GT{G)lyzl@0dwSrMeUnS|y!jB2Y zCB0YDj}iXyf+tBj|8OexpD*;KLSIcpdDjd6LelRNd{pp7!Pkk<^KT;ZeJuEyq>si| zg;~#WM9A$VbfM6D5|MA7;NFtHSkfzmjtZ_6ev8m?q5Fu?lMp;s(odH3L7~qR`f?)V zuM)gY(r**Ig9v;7B=kcy8aU%3QDfq0U zza#jW;Fm<`8-=eVvp!>pp!0~xUm!SH(s!5ic|z|ibSV+?VZn%`uNLeO>>)z`IwIsx z5IkAZ&l9{t@OmQTZze+iH-f*D^oInW5qw?nL&499$e)FSIp)t13=&b_@kFE-2!FC* zp`_1{^tr-cAh?gDA1LXSLe~ntoQU#P3mzfqt&-j+c&6ab1b-uVkKkVfUl0uOoD6y~ z3@HnH3{+3k3x!@Jbc4_3DXg_3Fet?K;y3n(Pt`xdT=r*A{ zg+4>*vxL4@=${GwfY5vfP5rM6{g%-Dkzbat&kw0L#g~oA&{+&J-v7FX={vTx?)2jdg literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/curs_lib.o b/obj-i486-linux-gnu-patched/curs_lib.o new file mode 100644 index 0000000000000000000000000000000000000000..84a8efaada9cf5428f9d01deb16425e59a917ca6 GIT binary patch literal 71852 zcmcG1d3;nw_V2xYJITG!&`l>KDF_fCKtdoP>^p>{1CeZIVN+~EHliVkNjHll5am|7p5q?UKKUtIY?IeDRE{~4$Fd{EnH9%I5{fh(cAVpTOR-w z#h^Xui(k&3J$uOW1vNY5IVr$V0&V+(hx|FmH=@{)@?&V}sbGR=-L}s^;B-VE(CvPG zT$^PJ%M0p zk|TIwk{u#K=rg8>p)yC?+rj-lSEw5;Xlu`c)Hb#c+>Q6ZU5e4AZ<4^-x)-eftG;Re z&ej{b5J&N?WSl)QO3ZH$P3|fBYLA&Vt<14{f#x|n&Er~Kkn(ZRbJUlsF4coaz_~sD zi(p=oqdosr&<6!Ol1Rr~gW$g3H;Buru6iicrFOw_)q`9gKZWvR+7A2lQ2x=7Cnl&v z&A~UhqPf1L{xjY_afIVt^Yb`N9d&mi?mf-N_mJqTly2Sw+@EARkW)C2)Z6d-5lvxD z;xv!Gp&^9vXo8sCZD6gKgQqOjQ-1UnseVV;)g1rL)kX?eb8e}I>yx{kANuhN0nUMdN;7RgjyGH6Daje=1>{ESz;j*Ge zr#{@LWwf7ouEVrnp7Tjh0-QUPuS=1)diI1oNr5lbVA;OlD^m8hebNCAd5-aM^7lI1 z?m_AJX?&5MJjreQd_4o}PW9q*UO%;)#s7!-f&yX9{AvCe=T$coU(ZnrL%3{v*_*+b zE|;F>fkUkRLwo+4DSlUqKZaVt`|TmmUeh1crF&DB?n_yh zC3q%U8IrU5QrqWJ26ApmhrR-bRNwN@I+5^@giODPMjg$!Y;S1kzG+Kc>$T8QSKEi{ z7X;SDtG;C!`vA{6TW=xpVQ%M>`FplHY_P|a_x#@;wA+-xfjmq8;%*n1T;CWV9&q{ z>hs`#_P7sU@B`o(XOGtq!q=nrMJkCE7E!L4)3A6RbOy?)Cw)=;m4ueYKmZ^bzhLR{uYWyz_C&7^>)-FRM|0W!`QL3HI2nIBA{veC{#DK=`EniVOPvBoXT#00 zWF3tN+1nC`%^Vj`76=KFoHzPHC1r5siaM!Ij!-L1<1Apeyc6mhkItffk?ZjO;Av~V zgFLip&<{q?2#U{kc)vLu?*cESF@HOpX^+E5c*1Q+AAys0zP_)S8XQ3U!if^eFDh`r zPHR0S;5-DB~oby<3+%AGg2Ee-c6_!#OYm$x?8JmNN|5Qw4F}`%%RHgSYpoB0m)s+ zisW}HL3|iLo{gBgX+qZtAFh2HDquM?U#XgmS0erR~r53*ZElqOK@RL9myEL6ML)#f7OK74m zmC_Qj6<51GDUVvB$JrwxYdR9*S!YBeb@P_}C!Vmx%f^#0qk#-T%p|nbfi#N^4l=EO zkn>NG;oU#q4_9NC&!%1EaJHWzvAPYtN;#clQ=M&JQB8sF{L`E5_C6VBGY(JL?`$U` zZMv(Wg6FxBp_Ku$;EOSxX&IWCp3J$ml6cNP^$vazeD8&y29c6lKzZRGJ%0RmaKH1R z_dz~0h}78LRtNhKqhQ-2DoL}ooef^3`?TPCS18AUQ_hvYqJJpgCDLBoVds^@;4~qR z3rt+?IkatXgaijTMkt43_;PgN+J5`^S)^5N8|3-pKLeq4pU*b<<_kxAs4ru-+cb*5 z92b-|{b}+@tOnFCEF!Hr`WjT2^XV?~@pc=<3#e~;&=qW7O&4iTMyY9sKWJt=U&{_(#bcT@-4mVxm8 zZu3!Gdkjq!# zsP60C%@aG2E1w<)-r++WKfr!>KXFTo>TC{5SpOtB{k zy^=nTd#LWe*x9*t9r#rTcmhy-Lrtq=a=&AE^~K;q978Ef@|F5rzd8N^w>vf#G`()V zM`iS~)ZZ=2x zU1Ccw+6iEX(6yeUzqwx-B*pO=B3;>hy*R~Wd3Zn8YwT~hr|4p{$OSU9+riLe-*_aU zemMF2`kEVqZajiByLpn7!xWZl_W!vb5v^ytXxe;y{&iw=HSO;+W&jTg&+KOousVXZB?ONH(dLjJ@AdQC-#bd zm@jQ#T*zQy(a!vAI**64pj|e<22jqa8t)`h`(29yAcv@b3~g z9w2!yxCr}1$Pe);0ko1r=SaOTso7@sH0{MFapW1~<@qsUFKw~7C`voxr ztt(U^mQ|n9=Y4%!hEYg7zwrP`Vct`TrR%mas4+L`CNpf-rGxUhlR?EQOAW|2fZ%kF z4or{gzEkHM&J{o==;w*Y|4u)0!F~I8mVHXRrVRfd)abwPbOaQv*qm(}0i^m8Xi#~^ z`S0rUkL3cH(*2%>c-ER7Hc@qlIfdU<_=$%)xMFGl&;)~YzyIO)v6quL=9cs*#I(AG zweDC~9rp5^?Lp7iqIraZjXftJc8r$E7dcyxAto};f|;sBh}Z~M-AGlZ!-9ja@;^&- z@UXCM@;d_S9BQa+JMI=Ef^UV&geI`Mxab-(xbzEZoxqQipJN0>fjCQsmVRNTV>$_4 zh~Tg%(akHm>cU(pFQP13(_Nn2+zD?K`t;mjQbS8`z%elJb1!G>ahk}_J)EsaQP}wN zLKVBo*1w?K_95;ywq6aq?d;a2U-9+I*?Ki<+C5*9VC|llp=utjfDTkpQ1gg2$H8uL z`@YtF{>$mQ;|*)qd;f=Boo!E`o9Ugct6;TID4Hxl!9$zYiOe4X^@tD_=U=lCUJ9%2k76mx^5 zPdt}?;%1r$7^C8B$MIBAFU)bTxHrWF=#*xTK+i2a*f<`aNxR3#`Sp=BAHN);37^~k zC!F+;e}}K%-lt&yz@_9tA{P*I59Ti`;zaI8Frz1`fEeK)z^KgdIbD zDJ(GII{=h+`->r0Xtq5V8_cnzW$=_}TiwwzBZ?ZVy}#wt4K!^+%($1_4@LF|@x;qq zZa#04ri~J%Ro=FJP}ujvZ8x#k*s81x&j2G zMZ0;?0wO;A-}KPBgpfaxOiVX_R)55$xn+I)AC3Qi(=nHg zPv;r3!PE4GH7&~dyzYFy$VRtSzN7?fq2u`xCp#$-hc>$EhqZ9eN@q2knrLH<8{Y5{ z2p6HaTWBoL>M{5)amJAClt0{=IEWn^^H5gjUcOOq>An3*k7{Y_^3eGi9lEt3^z8?Dsc zxCxiRb)sCRLrZZ``I~h2@n9eLd6u*FBXl#PA+S#~8wYXGh{wT@$R3ZTCOPmcZl?$D zr;BtmXN1a<=m85%8y_l5q`T{11N)MI#)Qfepf(4J(!6w|4h)JsX)=VLU|n<^#FF|X zzk%3=aXzrLMz;)iUB_&)I-kIS$&A!@hzAO8y3NX9z`K4`Q-Hm*bc`kTJNbnr}fN*M`=k)&z>_;k4FQth|wZMQBfkD zs8*CH0@PfOR<+(eds1%|sL@NXipY(gjHfU?;?%CXp0bYjbEs-=H1+5;Sjmk}2g}~k zmbT8Ww#3Ip!)d)~z&@t1isBxQu8I;ZDHu~xV!Ar^?AfcQqbGIm3!*M2NN8+W<_MA? zPIf{6t}gL*i!>}5vr52?S3gPR{rXF;a;~W7gLGpvKq`QD7}(W9Q3mx@M>vEE5+nFL z21^C-wnL&ZwsOurS(+H&@{b^k)n+0LTJp4 zG`I~7GQ!c-Z>&X3j6BXVGSKm9ikyGAlcG!r6MLGR6lG%9gcM~`Pk6i=!cGng8*WOv z!2=tiRH2)xvM-#JW~nBA-{CW&#_gJ+W-Nk-2AH6yw#a#7F4h?ATMB?Gj%mLbu0o@E+9bGtara*!LHNA5_UHz>#k>gZIYkdJW7+)h03_s>BB+R|c?INqgu2+bb# z>r4Pu-{u6cMZGeF6R#af#K?aWW{W7E4Sx2B+Ik}(F8)q7^WCSRgNuXTW07`^C%2u8T>{_a~O~LAEzn+Sb_9**PfEeq~5ZBg>%j<}Y zS3uFf9IYtZBSv3==@^e=&l%}bmr&=Sit#WWxJ33c&kvWRZFiAGc2FVUH^QBW%}m>~O3UnMMPB`Wc8;}>UBK|n$la3 zD*PCzb3S}Csz_Se89xr#V)6kPTCrV`40H)~v)P^Sk<{-|blES!`GolOak?PGQLmj0k)3gSQ0{w4)mp_FPdY>3I={zAPWG^v z3?IqakDA$rlKNXw>a9Bm{u9utBAq!03856{I>e_SC#rBW^6o|26`W$O|9lR}D&a{AOGv^(#_mQ=w6PYDHEitM)71E$sJjm% zDr}odEh=Gb8=C_8H1;a4iS2A5Oc=q&K?RXaAB@0Y*F)nv8#f-l!S2Rv7pDW36QKWt3sT`vJ|A}IF?T0 zvyBc2#mFZ8*m6Wrf3_`AQ4-i|6BT6uvq83j>|-RYLF`vZlE|J0&%x{+l!q|Z54%XV z2%M8x6h;}w`k{6>8vs5d*gNpBWHxy?_JQoG+1UQESK)}M%pZr%9_xj^quCy)J&j$9 z?{wB5&OCi4D-89j!s;-u*A#X?jQ6_2?u73D ztgr#V-cVQ+Z1ASSuI{5KZz(JrEC1UH+l67@QCI=2_ZNkYAE+pQRoE){!Mh5(9L71K zFgs*;U@`~jH3C?6^;1v&I@3i~Hi_>sacgEl^fxbW$}E9@S~c~oKaj?X_7 zmW%m+qOip<@}~;>91eI)Vf&$u&lFYyk^ZT$dL*UK74{Y^^o7DU!1azRYyrmmQeh)! z;0%fm@U@c)%fkr&Qdkm({YqhlP~_JNbHXc5DeOD=&NrAJux}Oi2N>%+g&l_qzK35y zOFt-V8pb=VuvmZ}6_yCe&M0g!c>Y^q5%BV#6!tV6?PrA@1M6QD_6yR_e-uWm$FI;Q z^l}!Ohb%2B>&tL+rLqe2+oZA|AyPnPLt=23sIq3LwGBilYqQGUfs1WX*{?A8R+XJb z_aHFn>+asRYzSrWgyyt83NExN(2D1F@hY*pP-clv zftuZYY*db2KAU>S*fs*`j~wdm%ZuU8v9>L!5uG#P98vZK#KMcoy5nqAj=XXG=7}xCZg$_Q=U68gIgT-8m9XGVVh^t(}dW-_4SW>X@$b(90b&9f|2mM7?!3W$Www)-) z=E3F;_X6823}HNjz;`c{LMcWk+}FKGqIO~W#k{51gV@n0`WYI1iH*v!KOlzU-51&D zhQ*jeiuT&tAQsvFS<>AyiQ0{mNNw(NiRwl#c%XZ^L>WX^~S;}46HN%*= z)o@&QRo4t-;4ja5u@x z#27s%0$pvp4o0vIjW>={K&_EzqH#Y>Y_05@Y_yYKTrSa3#sQ={_eP11F-YI;O}1GO z*fw;$Fwhp8hoh5?kH}57N_2Yv6_uEM(6$XTA)mT{{4r$vk)zp0uhBr;Z6(}V^NdT0 z^HsLnxR7~q50JNBBQ$4+DvRQNMN)Ea7ZeRUt)jTK5M_MjrS}l%3o>%I?H> zY!Wsf%cOSW0*UDHjOfu5vsB_Hkn=w)d0>`G+-WQ#?&l;0vs8p8o|hENQi=O38DXEK zV3tZ;3r^tf7bFF~ohai;>wlIMjVNW5i{FqG8&N)|Eb&)Ci9kHt-0uoXBs6c2 zOQrxiB6~se_PFGKqWLPCm~W}rN7%K8`SceV>uBAL(!{pnLWI$LOd|I0(`f+_S;wmvIwR;EvY@apT1piIG5=MB_30zHou)^PzLMu8}dK?9rs; zyU6DKG^&mL1z!&LFzsSg^e=D5QwmLP$oe+{8^J3m65fMB+{x0qbY0O-`wr^vPSG;Z zJIdaO?*VrA3~e_G18JW)Q=`N7z#44jw9ARu?8AyRn{!cOk7KU!?y=eu1bu%x43E=F zxGyOQbT)U7mwMtk@P5+e1WDmJFrTJ7QBo)e#%<^a$|Oml9N2$lZN1{2EIroVe`Ps@ znj%rD-Kl(hT=odvPm`#tKLpCuHbH9IRz%rpQqd%`dk&vqYzf3}buZNZg_TQ0*&?YP zrGGU#FXlC*J2&~$5=|_)_jk*~Veo#MDU5Wg8z*Zd)PIc?RuI+_e(TGx!eRVu=>@ zudiCIxG#}tsSzMgs*~sM?YGuR z3KGGZIQwK!)=LT!!J4?o$T2ra3KGGZxO-=U(jqBH1Z%`nvr$s8wOSK*KUr#%q#!k{ ziOVH(1SAEiVU5VIo8{~-H*SqUgDqMHW5iL>nW$?o&J0*cA`!N1}5*ttl zk|8c$|4x?@XcFvai73#qNRteb|<e62 zH8GmaL8^>l>k&eI*)imTSk?!2ier@!JD%-D8^*qb`TMaauvhKR)}S_l?Le;qtQV#~ zklhYd3}O!>fD_r(aKXXsX7C@vw!%h3*=J+uwyY7m#9{0;$TpmP0M(9Qd%-iArGS#c z-oq?Lvf)r;Dr-xp+p;UsW;CNW_0!l-aL0633vOfBBJ|2&e}PnE*>R|G9J>(Z@$5Os zGl6Zy=o8s~q@hVH8sRsY-GBg?!tR5~rm~L)(rsBXdQE2u(9aCE7hXG)O@?M>v5O${ zK7~D%$#2VwVQJi!?L#)iZP~6kep@zeHoq-<20U?FHUbmIZP_yD1Gie2ezC;JymVFN$;<{n(+?MTxEVwOO203wCwg3)^+p;?77q?}-(H*yCv2beKmdzZ&Z_6%+opD<> z7BPa`vbW)vxGkFik#Jkqfqu9x+YiZbTlP3Q;I?cZf)KZ5*CFb0TXrK{1Gi;kUTp}O0kYt>>_v3IZCMS>h}*IQV2#@{dj5vnvR`0s+?JK4^4qdw z=z!a@=MWvZEt>}-Zp)@aA-FBegA3ud>_O}}aa)#;8R53<8VHZuvR_b#+p?82`EA)> zp&s0pl|V1JEn{$A+?G8G0dZSa3=QJ8tOI7mZP`cYj@z}2vM=B^xGh@<;c;7* z429sfY%@F&w`B)lINX+90_VeRSrmlFZP_bGV!Kqf)`izqRQ4*k+^(`8(Bux4y^o3A zsj>^${s_IJcc_(M8M;?&V&7)P+2af@}$ZRW4rYy zXcyu>rLq|Cd>Z$Sn94IMOG5}xdHj}b7?0mup4zNE5MaK(cvyA-kf)eYT>_TW#*V^_&qhw(bquH}Q`8J$rLUx~d;r8NM1IiokcGIpK% zGen~6nqT14?u`#L$cV!TSKH&L6h1W6$FdRc2XrowB(Xr%E+8uSKPs~b-tJBLxc z=cC$2LPtZI5W{Me-G;eG+1p_8czayK&A`}pcrg+;L{r%}NLn^F6l&Ahl1a4s-vFnG zU@0&{B&&y2qu5)JRcARU8!QtZ)Pqe#O76)n1|J984ZrBce#DTy*+vNJWQS39vG)<8 zeOL=7=4P|OIhq|uIY#NdJ?{EQ#9!aq`U)lP24psh0q0wp*a+MxFk9c1%{5BgP2zE} zy>DYfvl4f68*iyQ>6j3Ai@+StcMybew?bdw;&K*Xo^d;fJ)KqfQ}S3K+#DMe+dyb8 zZYL?h_7mbUdI%ktd&kEoZzX{$d~1~Wl&2vj1nNt7it!`Gk<#9GdF5IqK2;pp^}aaO z#E+um4o*vbYb()hG;tsat^nWov=S~4ZSbxHJ<2|qYM;T18J|wM#}yw&p0nb+GmMR@BtL(i)6yV0<$~gkeJvIf$7dR1_CYyl%YnMI>`JLST~>2X)CuL$0<#aGZXrX;>}T z+c0lSi_Sg(+z9vy;3mNBh@1f6Er6|n3L3WoJ^*|(;7+*07Qz9y0`3P40XaZ=`w$7DT{Az?%WzhKgoLG>kn3^48v&mHyc_UI zz{ddp1h^0IDZtkOp9cH@@EO2qe9`G-KLBPKPZU=l9a0U1s0rUaB z2Z%GH@;=~Ftm7X5?nKCc25S8M0`~n1@Okk28c;>9YiV(?sgQRg;6U)%1lWS`4FE2IzFGmdAn@A&r@=2a z1G;BZ{5jZAz^#C{MN#}Y*d>V1D*zW^{1D(1$cEbh$725NfYFfSO27r!o?QjF19%7E z2k6%ccoCMEs{yZ_N%7}kv1o^d1zxVQ>oHdwD;rJ=%iSpB-=slwM6f4Nj${Y$9mO8T zyx`3!8!Q&F+=E5gX<>0=9u9T}QuJbl=+&FWV5Ht`0RqCwIzY#(7?^t>b~6?hH!Flb zqFEkh8^fZZ^SoGiSiKkHbx)Het_1J*oT!5L-3a)QPX6m+*CB2K1jm#Ay4WkwN*mx`FrUqUCkK=Nx>)TX@?RJG9v&71#H+^e zUl*&#j6;Br!z$YVdm-N10iOf?O28AC*;RnggMSC$AdK4ycnj2UHQ-C5$bVhzJ}kZ4 z0qyXTYXRTE;(8rm9%gYp;BnaI2Ef?gqRIMtBgg7v|m4VrQ{vM{qoLP#XbHA=(H& z0{J!pj(~>;04E?CS^?vsw>H3)$S<1#w}Wp>OAPCc`i+1S;Q5;X-vm7XI0~j@hGyJLpa6&A_!5Ae;eFYNQ_VII*mWM1j%uUzU7{qVDE5p$}2ZdK3E;*vJZ~ zPJK}O869n%%P?k55(wMHn5WR97CKS!nTR>jnAh+zM}w034T*ORzoBmco0D74=fC8#*r~*O}OH!YaaOGBlE00X;VH zfu<1(sRdREOiZxZRNbfszfVy&YqP-y2M-c%wE7(aMa|RHA`siqXA?eG(v-kyK9}J^ zP)M!w`SiX8#>LI&;=1jGDry05T1ptySjYvUSMrnVs=%m-;~xPRBAsuF1id=QMEBab z2ho!hCtCfC&uJ2Z>~)Wgd}ajPFlD*F8ZKo!3f$H?Pw=|WCOl(Ba(xCIj6a8-OO5Nt zny6ZYiT;R)QD3yF^lw01jVP`{oAHRU)W@)CP@m;bdpki(Ek?=$J`C!i?3WtAlA%7w zpCrFU_h{?v3f?6Q+Stc=4@X8#eH>|5 zeS!DQ0iN8bsQbAjR}enDJwu6T6dX zXfa4rcVV2XAnG(U`y#B&e%hmGUjv#@W`Az}&4k~I-Hw{TJ?SpsW1*Y@9J6&QOL_12R_@t^y)CviQSn_ z>dthsmFbi))A8y__?3ECRZoH8YS@qNZ6>JKQfS_xwt(<5KF2^Dt)`IXSK8D!K}m#G zT=34HFn;ROq}e)dwCSLYbYf*t>p30)=fmH4^%bl}YPn6Nj&udE4h=`EA7QOfOKs|G zP_D=4kD!*oW5(i5Y_)`QfOW>=>2nyfPxP$>T4tj+wh_cVXz=e;9>lwdIavG^pFLnh z0q`x7AzENDPeBU$Ufl-|)H)yDkV3EIs6R;j`}N6)@6(*iB(zN?0R&nG6rxU{*!xmd zXM^_{d{%(`4T*{|j`J}fDLKjs{!;#S(aQ&2shhDx0KEnq#Fqg#V`G_0uCKPKRQ?{c z5ppZr8%o}dtTlsa{L#R*jty0vW`X@}) z)>)Zc-++j{LPZ`^>=;#~-~B4h4C$9HpGK=yNV}?6Rd=Dm1ujqkBd~`NqFu;ETMXI= zy7p2p^KNoG8DH@z>9{KTk>N1RZ zBR=!cW`bHm&NW%x1;U&7_&^-321$E=QB|VUBe(4Wbp=EeBE7>!dJVMXDnGpBlWz^RteNP`Z7yQ*e zHtK2XbR^Si8_g>>q4A_QCG(VumGCBJ`wq>t&Xem%&D)`7p1w3J$vl0XRVJ%*vAtC9 zQ$RuLiUsZ9oQg-9>IXcczFCzauUnP}145ESQMZ-87(Q`H_ ztC+@^1B*gCl)RrSx$lA=nrW zS3gZfAyrsoAK3pBR|$7xh}SVhD!0Z+o|oPRZ3G`=B-iqwIMjzI#76Rc*eu}V6320z zzY^5xNPTlCM`^48HRtLZ$xU{MaIU|RHd0_us4|r+aHNg87Xs(j9>uMlwgxvDE*`M$SI>)v-WcE#ZxFuY=hAUz5lv>>&Do z{19)JcM6i_|2P~j)i;8k)~Ra#&&XJ@EJBEp|0ove*!~i85Ru+M!)T|mhQvMbF=tco z9_Fl$BSoolJ2V7(u_+&@#Pa9fz3@$kNQH1@lXQP`Q#uyaI)7!AKN46+~@D5yl3&wn4N&FSEG1VnumVxLFM7EfadSG?x6>dq-N+VZr3jRRx{GH)zi_p zZTIu({??;f&bQkiIx=#sX6&$yjNTI%ojzuX?$;Wq$==mkFTMIZy*W>7ct(3;y?(4t zyKMR#d@?aW!Qy-Lhc%b}K!?`jyqS}=H9pNTed>ylYf|6WdgyLF31YU68Z*Y05<7Lq z3_X2@Rz2O87PEKpEC^h!4Vb<=Ph-_uLz))%?yY%w+MIW_neS>#^+auGwYF@>jA`?a zOq((7^INq6i?mBRrY_0f19VI7gST!za;s)6(y}&buPOSs*FhY7(&ntVTJPL^p)Dsy z^XZAF&dktfVDd4~%%9e|bF{WvpDqeluG6R2Tw@y&ZA*#P_Z-pQUiZL?X8)McwzO#N zpti#|D}Tjnm+oA(K)Y;**0^cbz@6HqdScySeV1)Sw07-=2cF3cOxu&29?<={d*|7v z^qsHII2_RX9{%jG-WjkBi(W!QX*IUl>Sy{G+pHK{QnWr=yMBW$S%s9oFEb$S-?Ryf zuGaFu{Xuga%U@y}9=&Vl#+~|^(KFI#KBzfuGgYnNTmAgiTAydMI@=gkuhDmDgKWc9 zzqZzvp=t)0Yr8g}rgqA+snavYXoH^7D&N)CZu%&F)|8nuQ}d?HOy6l69>2s7BkHU5 z+jio4vDTm;(;Voey}k|%YV`T~e7|;a$BONG(qXMrOVbB0Y086pTpf5dU2D?GR(lp} z6FRObdlnAi*5B2dkNImxE!Oww=j;8o&^p^>^&x-NV*Ri_)0P_j+!Erbh13UjWa>ZI z^7_IV{o0y$kJx5LA3kz{UprqvkJpTdM&;FqkLcfV^4bUVPqfwzy6>Xz zJx%McpO;s#3!Z!d==W_P@|0s*pLfa4`uNg!&j~(I}ssz?PBf0_4@QpnflOOdi=p9qcZlss`c#99OvoLqtmrT$FyX9ht~Y^ zc0EI@)2A=FM$gn-KCLlLb5(!pA6=uZ>{zUI*!8q)OEPUUqV=JRkJwV#o-IMW6w?_F ze_OI&TeV3$^@ndeF4i{#*LN@0J8hFE*}t~9M?k!>>8g!Ia)Rp~z8 zTBWF|s<}C_ynbyW5?G?IA+e&N-iKA7Dh;beuO5oO{t_Jc>Jzd5YiLr2HBU_()|{9O ztiB;}M&hu_lpeoFRLUAF%fY55v9YP4hK4}Dx=OUg!59pNHK!AsVU@#%r3kzmLZswj z%_&Mvm5&m5Lv>~O+QjPe+PbPrFan?D{@Ob5S3D$EVw1nVo(3B-ta->_bnckz7-ibfvV)+CxDr~^)}m_UJ*Hgh|Tsbn!-0Ppr68Lt))IYpoRO=CF_Tl zI04QZ^3qrA6lfYOkQ-;Q)FpRIx_pvMGp2<;W?Oe zy2@E-p__B2yP0b&I?I*zFze}Fl>-hs;d+x!w+>@0bWgNUQIj7F#OGoNU!N{Da>7V9&=m2@EWn8l#ogWul zczUEfW<8wXNd><%E}d;PIHl>sM;JNjjdf95(Eh=fZG1b>pM9#P!Hh<^ps5r&J|<=zsDh$H|?|&l=XBe$p5HM4L+7B zQ`p^Y;eI((la@$F{$lgUf;># z7rgA(3C`keJ2|YA{Rj#ko#t=~@t}YF08wlwD8~pZcO7W-f)Yg_!AJ0cI}&(Ok_o;j z$OI&ZuqlW`KveGo5G{*H?$*+Dg@V2KFgPyeVD zlsFiG9(|&CIRHswQLPURSBW9J*n}gWwg{d0km3nmBg#5KdJbt-Jhgq9*LQMwZv8>j zy^aqAJ_7KeD4IH_%|;*2(Pt+ZEy_AUdKzgRiQ3XXcS1>);P2H>6!mt3vVOL8tPe%K zPVg6A_PYpPfb&22>IARmWxtEyqmoW=gOJBXQ1I>y$0*761n1Z3ASijq5X=`m90W^v z*&jnt@(8;Z@mL|+x(G@+;t3vl{Z5IbsOX7@FeWLmNK+M}sUC4dMw( zffBhuVh}!{n7BW&YvP@j0sV=R9sUWiuu&2$MoF^P*NE{F37+L;e=CQYBiO z8s*&08IYDX;zLnS@J4(Pas+lrGQoEQnSgY>aMTkAdJzWkN8n0cEFqCeyPy(yQBcXi zJ-IX`B>Nvk(G<)Q!Nhbt@3WBpS6m&Uct5}aQ6x^ic=v_GX|^aX2aprDPS7u;e;_QW zMZA)((Zd=33NXKlkFy{a953h0!-<=Y2)E%w`GepcqO237$KuwgrndCfGx7rgS$&}? z998e*)x`v4^&)HaQC@xi34keJ4%=h_Ea%1ZF9D!VmLz!y4QFxELTXqhic0}R!*Ck> zCmK=uFHKME&q{s4BCDFO* z1yOG&xL=fYg7mcA+Lq2y--voU!S6&_CrA&`t!?RSwUN_&c7g#>)(O(Hb!%HXZ@nez z?F8QuWt||Mx6W<*F|Y4b2>yT%EI{B#PWI~re-`9u^d=4#8xcB~GxgaC4i#mcAU&bC z4mKNjrl_|Q%o1gtAU(IYw%rB%Hc@XUc!wzK1nJ@YxoxZQn2FXKfFGYbVL*OHP!naHAU*ZB@~5_gd3`5`IVdCN5Xk3bzfO?4SyGXu zmz{dkOaBmnfb8WU_>dqIcmW@b>mVqYh1EgK@DC`Xx>F}OnV0=8f@dY2pcFm4^3m%9 zGz!utM7pa`_O=$psdIE;?L4wCqA#>19cNP z!rA&=1n)pskO`dP-25(r;~)*l1SI3I3N4Hs#Q05oU}gf6aSTD~X0bl?lH$57;+oeq z3f*gz<3s*OutJn|g7k_-H`M^YP1M^7-XY35LAvj-wk7;6QEw;sjwtH{>3xiI+kVgM zI~9WT{sELgV6bdTkh+0vD*9Wr9KcBnyK2KGr~8#l@u7JUY!+pmAidII9iQ4>$?H4q z1Yg4kjzoZ7(m+!OLF#5nB`<(<7$1m4FVCg%+LA>8qG4E2y2>fXhpQN{LX>ra^d5&* z6l(hrukYmW|59(KcCtR~eRM4}nDazt1{^BNIzf81!#WnVy@S_xa(He%T_a`kK1h9l zS)!~Hr1v|lyr}IOUf;>#x%G7IME`6e>44xhqO237H$1Gos4e{xnKC=UyWp%;Pf)b& zG<`s!wo64@J3-mjVQGs^llXf>w#ELjV*@n~;)8s{0c7BGvoSpkrZymMw=^!cG~OQG zwqJmT+c>il0#b+-Ca>e*W#iRFb^v zJ4OJaTHMeHZj9G1poVsFZwJnIp)S;!-@~~;|~Kkc%R}v0Lh{_51>R87XmC7 z#gzblQM?SGO%zS0WS`ghe2TY%=}m$^y$5gMPjX>Y8s@kBiDA2Fa5cboQ8f9}bz~pz zA2@*mMvJmekY2U0`VC!CJ|gPv1RoP+oglsXVr}~qXuseCbrwE|<9dLRpz4I6_zbDj{DC!Ai)003aYm0r59Y zAN;BeGqngo(%Q-Ti&GJyvrnILhqWCa>HZy*iOX(uQL z3)_t9ZM=J@PB4*|{VsxHv`(GiG)X5Ycy!&WSa`TBJmM`pToxYj79L^Wu<(en@JO)m zh_UcUuA;$1FS&EIg7dJQ6HCk}N#nA>!{w=$Ys+YMn{z zz%3sB!=Et&7DTB`!DpX1Nu1#C#*&ruMdwtE0kViB(1T$ zvXcIxE&8bgZv-4~&hTFya2(G%SC;#{XoKga{N46$Wbmu1;%}38BlB0mIi-0;!)mX1 z7JTnGIYvcYRe6&n(hp~NL;lte-ooK;aSLX3{^k|6^^J;aylmsI$MaoCM{i~GCU^|( z#bao%ufc0RhUV{D^U6jsEWMs3aQS4}>!)YURm!#r=T_9#*ZTNt$Gm-gRaK=IO02|t zJ(W%6tCfBeWrwD!YCNJ|p`@FHs`|>+c(_cj1M{wx4PO4fjzVwSa!OTYt!7){;H<6-YPttR>qq&p&oi0 zlQ&uE$1`tl#fpa7iYoqArI(Y@3Zhiu$@=c8vSpa$_1ELwzUnGWnZH~pdQ{cpog;5` zefi2N<@9vip^zc68vOX*T+kmmtnkV3)`-V8uf!MKZeENJ{XcnD<758ai&cFOK8=W) zt>MVQFZlioJrQlvW!oDp?f)B{{`oL7-ex0?%s+2Io;Ry>agoPcSXP>yJ2$s3ol;==`!=PpM+QkwDa(tgNg&PiC$(rXaEGjB2$u0E|DKE36)axlIEnduL zQ_5$YvZJ=wVhMP<-sWmR4IT0T7YqJVi)?!EG^B1do0NHEcBLo7L|6j7LG%0 zO6Ga;^1Pmstjr>hBE1DEyU9l{_+os>S)92LfLwSnG*$}N&(19M$T0C1fU%bkOx&RU zIhn=WArw!+0#9Bc*pl9)jUa6qIVXapnAqnO7H5$zFh&t<0p4ia-3&Z3@y`O{P17oG zc|DR@6A2E(76`{Hpy|!?6hH^Xp3H0|EiK*h25D1OIVq#GXl_yN+=4>HUm2{5WzQ>= zE(XibEbBB3bK{vwe>#y(~uy}DK1=yc3yBS z$tupBLoG$n!!L6wiD0_7kWYn~@-era(Tg0a48jjzkHrMY>OZPqqaSJPUG^}hzWqI6y% zGD(qATUn3Qpo%+4m!?gRnm``Ko!paIQdaEAM<`(i*`5+4L9dtcjn&h=7y|+}mN#Kl zK)Ca+rJg)b(L4kRJPy$a29!=Y({m%|9DZ1>n;Y=Ht+H~Bx1z40xr(Mb2T2(A#prX3 z3(Jaf3+7rhHm5L8@io*ntj5@Ao1eLeDoZoxl3(P&Vp)Z-7f-U5T?m?RpCy0$9e3kl zg_YJv`wGQN(L~I1kXMU6MR_6;$yLId5nCf{lCUvB%d!GQWFC3Yd1d)UVgw=}WEOgI z=gupou=Qq^%tthlyl}G;S}-!_h#W8A1f{v6iL(^=B&gurRAULNyv%~Rh(dTa#g810 zV2S5^GV1b6YMSaRv3}rvW!Q{{rK}(_1WCQ9)Ki=fJD28`=0UEeDtaG|m=%=edx~?j zyjaH&7kS>ILNY3NqElA!V$2s_F+Y=7Vzneck#E|0SC!)>?q(XSw7`Q9_mmVC^Pu3N z%NHs$1y?lG)s;75IaL-S`xe69mT8n`&dKxe0WmWXP82eT$$XEn?l~JN3^*?fna=~& z=H@J>^?PNbPw?c6zM0{=LECz8S7*Zk@RwhL;1m1?5D!d4vX`BT6we)WXcXQmk;;nqa>`%T9L- z&`=ADGmA*?@Oa+k+#E|@Dss9vGruUGy2yN+gMsGpKHQV}S3Yu%)!=5}m(ZV#>l^0T*?Yr%5$a3AbRvE%ucn-}iK*Ge1%HLE2by=-UHle)})?7?U z=0vzcK~^U6=fc8bp%%d!YYw(*l(ffkCg<9v2>Dm+0C;tH(atI^$XZNGSbbGp)k;zb zb}n2^c=r@r+pdwZ9_C_SlDot@wv4Ni#rbo*^D;~3VZB@8fxyVm*!+6x=DytAmeBElQty$sg=J?{I0O5I(gcnhs0@^KHuyeJHgBfI%6+?xK;9azE&&6t5 zSW>{7blZr~hJ=I{dj{wW`HHWJ-MC|sz!HeHlW%>wt;KAGpyBfn3J7*A;rQ2+*e>PVlkM>zdr$ZhpfQ86kXsce9bLEzQ{6$}?sZ$m2hSc~%K+jj}w5R)jr%wN+tRrNif`dDulG$Q5iADX&rN=guuG zkQ2x($;!Qj`2kU>#@>K0YP8YgJEPKhXfK@7OgyX0o9Zd?;CGfdJyZCv#ol^V1;76YAHld; zvXRiSTNisQGfsKrAqnx86?qcviF7U3X#V_21$}<mo_@!;9P{{os(IH-A#UONeOoJ z-aI5mbcarm@Wg5T9Ft*lT1dH$oR=jGx$rEA~cePc6;E(pZ0`{)!eGJ$oEz_%%ULu2lM zx%*?T{QSlbHpq*nB<9&Tw`2|y`6{o!xvJv-G0*aB1%D-3}=*7 zbbuKcftitEIH>VBGt9^+%pk+rB(>L5d8!QG%t(6+4=L(fl9^I!nQ4(}ky)B{P&2da zP1L@^_y51wZ$BsezU!Oog5Ptmwf5R;t-TKSy4TukXPye#@+zU=%I%VxtVy&R@l5rY znmlW_QrI(<-ZHJ;v$vL*J{DHAouT(%x@-(qn7l)p)i8Ccdi|zlE4q7o`lRxAbT8|c zQc|>cRaRmKo7P6vl^NM$y=a;2JH@AvTSUsW2|t50XKiS%E6$3`M~T!|soyUumTui@ zzG>X^L>+rdJRXWS*A^?M1?p!#F^j>hPx@)h3yb3%8JMYdk?DX7TfIw9JZ9gnoO7BA zb0$asLyPhpC(GwD1$8WXD!o06`ly8StOz76G=7eaNaN?Y($DdwpA$+yHL26%kFdv- zeoo9h5geU0&nj3|wJ^p{Jt<%fjiIZA^H@L5+~(p@w`2!U0oBcqK>28QOh`v(XDshs zxhx*7yY;D3W79meva_;2u&TSSyIltBg63D63Tr%(6(Jw|^>*yKP?+=kOaIfuDOhE9 zvdVjxI(7c>P+a@Ur*P4-tad4TVgG6IAmc)b2O0mlm$3hwnJsfiySXjzZr5O+6}lHK z={+k`ckE;odp3+f&F&|hju!Q!Sw~w>p}n)vvvSFj%2`<#Rl+iAFn3a7kl)Qo zDpR`C?6tVCQOYfvkY+JDBG`5!+oF^VThBJ*$o#k<@S(Zm7O3lBoZB=KXy)7(1 zdHr!CterhIX*)_rKGK(^qTo8wS5<2;;;R8QOhLtrTBL`X+%&#rGQD?nT4B+P=T4t& z*t(OAM*5vP+1yg6Qq!_nd)%eEzpkB}+W)TZ>I^g(uF#1=QG(@aa9$xMgq2w}zGOMG zfhAe6V#1fLiLTI^r=Ml1Ka=G)>6%^nLYaK?_SM=PR$67VNtWhmnxm!;)kCAZ6PIYC ztl(+Z?V;7xWLmRpzVrwUwB4!wq&0?IVTor`Obd z&Na)HM>G)_J*p}uGvbt{yrx9`S1`tIJ;azVx`L{=(JUr+Xwybf@o)HtqV*SmZZdCVT zIBD@sv!#LSF*MFe534L^>hn}1ogt6Lj!!?ObI9;NZFWWB2HV`cb=OB!nxcUq@X z_DdRjj4rBsX%RyaHaBU_P}g)6Iy&AivogxmO>=h`gIn1eyRNk^VVy(+_!-^l>gWpm z-zhRqq(@5c7|MUrPfI1|{w@{$%APPI6*NFZuO4AyGFzOtrRXYbsiRy&`j)k6IbYcf zLrbdN)<(u=u|6-4vI?A*C5w;1Mw8k(THFc!MZH3w=a9ZSR&q-zEv3R4*K|^s6bEVB zepf7)eS3-bQCJhSHm!j3Y8$k0zQEl?w|5W}3iY#VwRn*1*p6v|=6p)R%$CVBo2Jab z;4?2RaunBilg^tul2{f=-5tTutMi4DvS8@e#U+zn>SMI9&Yq6mMV?bRJ|NSzE4(hRoVA4Esb!AZOG`3;Io%Z*E}!d0 zzZ&+z+4EBmpKNl;gj`mdl_NwHX+@-=|5e!Pl*g)8(;=-|>P!}E^+Q(LJY^eNw`U^d zi7Xkn!!%QAYD<1R)+%+IsmiDnL+R+MDXKH>go~{}tKbnk^|?@`rR1G{bW(~- zG0fKXg@#5i;3@r?#_cxEB+FuSd23ikN7Xg1j$R&F+O8pUMdujV#-ty4+mW*sy{%_2 z?(`ZoZ`Jg|6CL$oU2C5AQ;;gBtL18_d*)U5JCzhT)y|9X>_3aK1zXc^& zb1wa_Ikjdz9tP5^$ErkxC{36en`EtNQ3kBhm1iR_>uC0lMnw=ya%ZmWThXn;P$^7q znlq$~Q&VXx)?OV@)~Ahy(JQz}(mG{KC>OUaNtXJ`wx@@y#W*c3?OH#^xqhtc z?da&1K~_)A(?91`Wg!#x%y}(IK`7f(S&D;2Jk7bZ)uL#MwoOaMib8Hy(TZv`;YDdX znCrO8Hs92g&tTfLGQMcha>4CGIvU~t& zZIlL6+?Erwh!_LC-L4QFifXFQx%EJ;>6g?}HoEN6Rg6hpg~kEzr%G1L$U@mRnOUXZ zRq0Q$E^#-JZ;Mkk^3!UbD}ALvPp7t0Q7mqhjTM7{=Wnh|6_rRij)5%7tYULRRN!5r z^w?6al4*(AN68hRX>4vR)X!8GTwK@lQnv%-U1fCItS0CBcv#UjyNV?aroeQ+y42a7 z);vu+Zlt@|`n9NAyGdg|lMIaRL#UC-CXrgawD?*LM_S5`4kO?HTAh%5wMy=3{Ue$D zob#&2?p2@IYO_nJC~xH}V`cR(Zv{4~^~tc-=QaBkZS8&ODMyK?)zYT=`q(F>i_=PN z+H@iNPhUZeSO@>DP}SE~k!bXJj_d2R77(>FHJx2X^2$+bl&hkXA0r_qh^E=O3F73| zI`s%_RCBO&b;-D0J300&R8-N%u;W-cTNF##dR!U|V}&ACe5N(F4w*6}j(1dbt=5>r zY^wn`ROlq6amSB6M)tHQB(wQ)jn=Md(q&?sVCIfZ%Yan<%3doPofXFDKO@0akJDAI z)tk6tp~uZQ&9XI$>bS{W_bsc)HRYdHC*zt{x0|QWuGOF}BT`>+$Q%#rl z_~|If6tpszF0M2P*UhXCeZd2LjA=y!PWiyy-RCDHRj{BAr_EQ#I38L)D|*sA*m=>{ zA&W}Bf`u7dm8L=&t=@Fz1(_wCUDlT8%&wm@X4JT&n`>ul5+#SSfg)BTDhK-Vo#n+j zjn;*y`XOk)c~6I0SWzSL6fOw)E?Tv6t4LX&n@=DUz4Gq@9vkt+G=O!w6}>Ce z*C$_ZZkB~5AN(qM&&r0Dj|~dX=$q^~Qx>SdbV=AUP$vuf0_CNnvs>mAyM|4|3Y@GS z64k1#u(UR66-64c@1C@#n8=r!wbe9dF;{Y}-D;4Ft<@>wXq;M8pYIJwzGe3^E#xoh zUgRa}^dS3IdP8L=_Mp7$MyE{^BR%S3Nyb*_c!t^^Abp@X*G;>XWnm*apOUviOL8j2 zvJGm*t|nKnC)!Zqf@zsKcWf;9Yd=$GEYE8_(<_e7zHNfVJ1Mm7u+83Yv`Y_N+@O<( zQWMtdrc-o+qra-r2hJ&8!*MxK@dI>i>Z^iM= z^ClSf+cecIa}Aw}rM5hzwsm=lCsqp_LsZgGjIFezcze>+fTms1al78A?cuH8K)Xa2K5tEPG?VdoX&9=n;z=zlW4UkBtHCZLwvr7#15^ zOVPsMzCwCqX>W6}q?2}4R#&_kJ+c;W<6x{TGgUI;c)TxWtrUKIR08kY_f~%y60}{9 z-7XQIcX;aoR%~?7YXaSNo|b%na%B;z*NS~QHgRjbpRPp@PwYCDYwDYH6<#z`CB}$h z+hmlf3h8ZE^V9R5RjalAV!6avOzqQy(H0bKvc|qx2&=dDtmUSo>9sTK(-c)3TD+e{ zH;?9%Uiy$3L)#Q$N2@x($baQ7gZ#KyHj*6h$bRaY(zh0vCvw80@BD8puMvbE8e0*QE-yGB`P81&Bl z@<-(`sjEu&QXX0BN=m23eZN(r`KHDU{QU`hqX|Hmr1QH`XsYyHo0kP+6PJ@$ERtcnYU?;lHs_?(7JGTG_vVwT+)n1sMf$7fjQO&?b5;>~`Seyro5o4kyU>Kw zOjK()n(V9y3z5sSDGU#>Br6R|x@a&-Z}9kK`%$>g}Ldn zBQ`e0QSpU*uer@;X^QH$#Q0rmNO@!T425pW)8*2W%WZzK?`&6RC8IbJR?ekR#?k;{ z9jg%2PM3*C`jWyhXR3zl*mf+_s^)_>trVX}vEul-rK+Q^7UjD;9Ik52R3})f59JlH z*gHm7pLV&HLQc<@HsdWB6=D=tT11ZBJd)Eyvt>qu-#XE5*f2}R7!al*KkTMPb>N{- zYCp%S=-(40O*5tBdYo40shg@-@*=GwrCoY!m2^&7 z)!F+zD*rJ$|1l<8YOTx{#p+hP8x_fjaYvI-Y4oUV6(v-VA=h6u@J)65WT2|DC`4WG zhPeo-l*fC~x>YDE-YQ7X7;_8FJKS~W-uYsf9%tIWR4jC5T`y)9ttO>Ps3nJ_$kPSe z4wAL^>eJ(D#dXuPsW+bq=q9O_xQges#1Vz*Bwn*@)QBDF%9~zjVQD*BrTIIGD_4}Q z!s<;ZwixloU5xrp48>epKlMHH0fVgxksn5h^ir5=Kq~99SL5T=k+Nsq+FW`UM(aPt zSB^Y5&1#xkr_NG~`<=^}(Yvq2;;4EUv1@V?Z~K?ZGi+Ddr^WO*O(KKd(~jMfVh`Fp3u{yo(T=0s_;vfnyO#@^(a*Y~k$ZdlxiioHlCIv5G?Ch1@ zG`qa+l_s5}kh-)oNjN0cql_OjWyT9{o11sWn!IO$+hW zu4%t(wd*l&8}G!7SK&4Fi~v=GOKs~^y{)Gy8OF0hTZj6o;)G_UcVTM9M)QEY4PZu5 zznX8JVQZ3?#v^OA$kJ}BlEc`ntz(7kI%Ul;25QGq>kEY~pgVnW({=;Skww-n7EJ-ymkv`Xcoe$}tt>9skn;d=c&T5)VL zkDl0D*uyMVv`E^h;S1BNp$(e-msN$lZA5P&oljG^vch+d9WS}0rj^zbb}ioY?odG) z_gL%=ri)}|RW_<>Q{JrXWvxE_H!ICD${cjC&$KC1K04$>Q)8DxvWkxw|6$DISxw*C zr7C%G#qz|(`LE@jOKMhlgK$mE#B197^a-TcGf-%2Z}&s1aggK^Z^o3#VJ5Cw-s?*p z_vo6@3ZBG{z7^xjukG^t*m=}icPRH;wzA!8U%GSYUV499jis2FN=f(1YV^L&QfnVI zQWQFCv>q@*mUg`t{r~^xvp00?cb1?1aiV_v@SprIKfOnXQDr($v-r2#?LVi{f0OjDJRd)QQQwmok@Dd($n)V-q4I0=Q<|PmY03+!%&$?u z%j3IDA3kutTrOrF-$MO%d}H*_f1f%-CmNRBz(4(ODb#s?@pseWUCYmLuGhb^%d=Y* z?t6J*%Fki^w@&}c(|5H$%%BrtoIaO#p1x1(cX@o;pp@NMc92W%cWqU;11{7#Zs~*> z`IO?=px+huJ)~4FI{UJC-_2#$=x280#aTAQKlsbVL&bNMfAE+4Ju2D1UBCP{?-Cv8D}JZqC2Uq&&X;p3Jh-bf8cEm&cdO zIm_L5%U*pecQ*%Al%VDEJ6O(ZSGsCIR(8X*egc_E-G*Nm`DnpJLQ$ zSrKcJcguAAQL+8>+vR>bx3}zXK&FnU>~BCtPvZ3MQ|4>gHL&zIAZk##d_YOiuhQ3S zlJkIg0;M1WvV*cIh`$pDDo4d5;ri|CkCdE$lgP5aCgSt6)qKN$y5#)N*Uzq!=U2%KtK`L1 zvOh_3p4!uN#pU~5Alc_?HzQwF75)p7hp4f+W;pzf_`AODulnh4Z{&YYpT943qQcM9 zZ-;-l%KsOVub02Sb!7ins{CK8lJ)Vb;-BMxXIbZ9dA};zUkb_p?0;yLJhV#waFsl= zN}f<9pD5YqW#6s1o&K3s{;gH==~eQXRr2yG+27A_GxoQf9KXNvk^ebA|5YX5Q6+!7 zN`9zH-X_`SCHpx!{^um0u84I&Tgb0hh2L2v@1ZX7dW9cF_yfwiNT=`pk{{ELjrf14 z%6~+aJWjIDCVq+V{^m&j=lG^q$#bgYLY2ItNJomKMPlJoCw z`Tmbo`TtC^4_~!E^Y3!``caa7P^Q1fWqESh5by9ORmtVw zh7F5WzLqIlW!YOSHKRw38#}S$Rm|cp)3{92nzSUCOI}gv?pwV~r(DWr%PY~VI|$Ui zd`0i-jxd7h)eFys;;lhUc5LvCsLJ+(hMZg6*m}8I2Dl#2sr;j3af*P&*VP@m%hLAb zmgg&3sdYt9$1>YEwJxJ=&as=!dnn|gP4ktPaFC!aw|OinK-nQ!rK3>N#^TjWdu7{L z-LXW``EbBGe9g!%w_6-hfa7AH5~F|9Q%5R#tE>E-QT5* zjm}=PuZ%EG2n?rPb`-FcES`hb0wYjvYhRuJ2v=>J@%H3s-wkq&>HDfebm;XaM~>$qEIw7YdPhrifV{GQMI|ApltS@yK$ z!!=LS*zI_aFm=BM(f+4dK0-Q$`GG9^GkgvIcWMms^=nPt=aZuE^A*cVhsQKu=dr5) zFnwWNV~p?fQB(K%f;l|PexrG0{}1UiFs9NyM)L%J;Qky_?r(^Wx4-mxb5B$0d#`zv z(rwD-Gg0iXiRUEz>n)Ger~HslHAm@Wal0$s-IjHI5B`^!ivLPe;chS$?``8C&lLL~qwyO5PvZU=!7hZr1+0Jp3=Te4>u-w_L0GfqWhQ zTTI2f)ts!8&+V`HpE8w>-`jnP@@tOPKg}ELKhTu_V6p$yEIZQF{hLia=hMu3mA}|; znrvg{blJ2_UH2LIC9!{lzK3A>BM2Kn2PVSrv6>4e~#xl zbEZCWBler6Pd@IQ{3nV||9a%BEjP;6V>W5-ZTDvBQkqvdz9Hr;&B0Ciorn9UaKGPF zdM50f?$;#xy3?d>vP$Y4e3|7rDi6y_*G=#aQ}yy5y+v zpQh(+eoXDkoR?*Pw7}C5aU;nbKa_x6OlJ^%~t|ytDS=MCtF4bRiRF-Y9 zyZW!|EUVnV2JbNy-*?TUWXm*Fe$R+5w-@n$!&E%kfpS+rwY%u+_O`6@JixN9KLqz7 zc2~I$v#k4_X<6x7W?A)Tt*QERsj2*a#{Q}|8!Ri`Pnx>l({@+7e{WgwybRwob^o2F z?z_i9qSAe+=yVUaEdP;~mA>(o74DET5%*2>Iit?suWx8#RwL zmuRk!`%R{<`-a_@s$VpFWMea1v+U<)uiB@^uKvr^4&kRn=XZl;<;%uxr*BWu`Q6*p z^-bp4S+)?KZ7$dIg5NXyWIuxkE6)DovTUe1R`p-(w^HrUR6ZK)u5w#ob}OIe=q&3s z$LNzVV!u`TKAoxbe8%pp_2DjaL6+TYuF10dM5q4;=6HSX*wl5u75lGM|6p0yziN4% z>V?L9yYD4B+)3tc>ZeRyzuZ*VOT_+1YkW0V=o7EzIr{dSxj^;(eWLFFUeV8Ww5j_{ zw7Z_`Y~)ics~ii+XIj>CKHF5et~K>swwUMY+fbtK|8vWF9xs@BHgDQp_t{%IiSKie z==;1E`3TF3cetr|d(BTMe*5dX%S~PPdAsYnYmvWVS=Vhr-fCIteb7`q595B|p_0$b zvJZ%k?-*0@ooIK(SBE^yvf`U>p0E4ZUHQ4w^7<_M7VZL6#q$>OI|fTu zIt~_HUxr#%eHmw2;g7?A7ILd)-S-qz>FzXprC*vVzt5U#PdA8;?`F&Yk!AOqdd~ke z*Q;I}CV!>(y`tOCNaR_j?%Qg2rK`=j}c zhmqz4)yGWXch52egAmcc>r1Ur|N)kHT80t~A`6;9R%} zswl!=T|w|1cnQ25ei3eh-+|wQkHTNV=izJ6A5Zs~bO1a8j)o_~CTJVF!!Ly&hn`2+ z{aSc4yc_-yZijz_|9}HjhQ59vJRFXKC%{JdF}MVt18p02JR4zr#98uV$iIaz!5#1| zXd7;%0}g>Ta2<>6VJqx_XT$jRufkn{d@uYd{000qd=9<}JspVJ}<>JzsUW^Wnwta_H~R+W!mi%kXRP>+nwa zEqEV%5dH}M6#fGK8v47nzRwHrFVNqqwfmd!Ex7xh$$c-lKRg&73WvfE!;x@2JQmi% zX>b;7feT;(cEYpZ*>DZ~1iT1d4zGq^gkOO-!#m)&;8yqp_+#kr?7Cc@g3m$E=k5Mi zxC8zh?xu0Z{(HfJ@I7z{91d&Xcz7K2=X4#CU`rvUBuz;gWrdb!pGsS;Ir@r_zH~A z6f2&8ArIIq#rrO}KYR}y2FJr0a2{L^uYlLX+u*%$2i#o>k@ImN916$4TG$K=um_$C zFN0r%x4>`1hv8H3O}P8s>HY)Z;cyhJhqGY;_P}%DW$=se7I-h*26x*h-ETj5C_D-t z3r~Uz;9|HMUIaf6zY4zrAAmoD&%&K>?|oA`-VZ+lkB4C|(sOA;?t>RX+l~C(Zie51 zKY_o6ufhTQrSJ#A;czBg0MCNw!Ykno@Eh<4@Ru;`LrTxyQmmb>!{BH*1-8O7;9B@; z_$7Ed^w)VE-xDzGKayWZey8m+lHUhMz!Tuf@O0P<*Tc)|nd@Lc#gcs<+b8N3!V$Fgg3x%zz5*Z z;Ir_rFzh|L-+`Ji`M$&870M+Vl0dzDtsOO8xF7?O63?IEEe}gJ_x=K9u9}Y5pXQD zoy_r^0PElkcru&^KL$HsH|&Kg;W_Ypcrm;jehz*Cei?3px5011@4yG(kKkkQm+%?* zNBA=QANWt$&-OIsdr!D890U)AAAlc$@l|JCHxcz#qdWpg#a@|L5R~@UL(O{5Raqc0h&S3l4kzy+`XJK@au33ydVAq{u=%Xz7BW)K#KnWcsLvh=fZ`s3--WO za6P;TUI912jc^m(47b3o@FBPjZimmn=iw`G2iytw_+ZM5lZiNrQZE!n$20jm8fji(%xW_Q^4F|!&a2TwC6W}CR z4;$fJxDa;19=HmwhZn&s;0Cx6Zi1WP7Pu8Y1h>KM@EQ0#dI%x5H=P^Y9h81MY--e2DzR zL2xh}25aC1I0@FnMmQHPgk7))u7V$j7r;y474T|!ExaCXg15r|hIhlQ@cZx)_!!&{ ze*=F9Uxcr~f53mj?8B*?_JHq(1K}ZXF#G^K5{`ls;Bjy=oDLh|9C!*m9d^Mba5-E9 z*TesSpMqDx4e&bn6?hZe48IBQf!~7{{;senacHDaDR9R zJPZzlBj7lAESwA*U^AQt7s5`s1opvo@O*d)yb^AJ8{sCn8E%1F;X`m6+zy|C&%;;X z4!9HU@e$f390Ui$VXy{HfRkW7Y=m>+Lf8d+;3~KtUIedz8{kH`32ug4;8yq$+y=M9 zXW;Yj6}SWLgnJxC{^1}v7!HFqZ~~kJ>tQ3D3m3vJ*aKI=_3$Ei1>68P!cA~9+yb}4 zhu}829XDo1=qui;1zHK+z2

o;CA>7d>+06cfg%+j~en12f@K`7#sx~;VEW+?JtAvrq&2nz)!-B@K$)I zsd>`_aGR-k9*5ga#q%Qki>dH$An!FY$wN(r8x4=aeX6PWro)-|pAI`s#kUN3CGvU5 z7b0JU{AG9>{0@8s{tCVTUp5tg|4}I&`Bcp5wtu7jU272j3x zI#c<*9)8tSyx)S4nhO61d4+{U|kZX}=BA<+W z8gd)*66AI85_mcO|B1W_-UT0oKZDQ0KblJCKj45dNgilwZRKF(p|HkO{_2otnJTxF zVJrR%@$W|NL0*fz9{Ez_FCyOp@522-_%QBIAU}!xd*qjp|86QhJK#U@A23$#%I83M zI6MJPGj-hz*kmf7^YK3eu7X#?>rB@h_*GNa-Gcv}xZef8jsJJ?{~_*=!k^;*B>ulg zei8XKbAZ;Tk#`%H?!PB|x2gLNG!M{zKHLYxBk*stE$nTht(z}nT`wfJHOvV3x{DOXPPRXRi^H@4z9=lV*EG28*tx*d>7n?`xB<(`6b-_=oJ6EO}Xy}4>XmZL-8Mu zd=&BotF-^r@~dH;`t=J(o}q(gV&gf?|S@ihxg$A2=XtG zpGSVxR6MW2H}Us7PQKr}O~v~@I0W}2kw+p=M4p5^9eEb=Jmk}myO3AH3*eRTc2oDi z$5i^Z!Uynw0sq(F{>P^9hnfn1IQ*cg^w;1&5xD_2;=TZRA@WkV2KRH3FG0Q>`9G1r zgnSe7-KOge@;3aRGI!JdedIqQ??4`KocxvVL*XcRJUj``gNxwD;iYf`{4aPHd=UN& zz64)~yB)9lt1o<^pQv&?Bop^hzh_ET^$uCVL!N^?A9)4x8sw{y{}cI}$af?E9QjG) ze;~hs>@!Y$f4_g}`yYio3VABB&oZ(9X~?G|uR)G|*7ElmB#!TD{BJ_O71?Ks*#F1K zFCxE;{BFfzf4}D$=|PTt*7`jac{={5A)k)?apd!muS32b`CjDjAwP-y8{~f=zkz(9 tbOfj85L0ePA&)|yiQJ651bG?qWyn64#@Bxp`6lE&{2cUO&i!~U{|nGA^SS^4 literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/curs_main.o b/obj-i486-linux-gnu-patched/curs_main.o new file mode 100644 index 0000000000000000000000000000000000000000..f7aa9c2b1eb149db79c7291321f32c2bcf3ade8b GIT binary patch literal 103944 zcmb@v2Ygh;_Xm2*Cb^g0a1*i&0RjdRAoPSLfgqv908v2%5o}0Tnvh^JK$`^S)?c)$3XP-#)1 zrfgtnPS(pc_?Pp3Xl(v*cSUhq#kXC}Jy6yvR6`QCe=l$Tm@mF4T#SRoD25KrUttt7Q z=pX-PN_UP@{*7Av?Uc&n`zxMrO9&OOwxc)B>L}ldv`~pBw8RKh7w3jrP(|RAk_N|f zD?{V61D_P<1dB60!Nr-zuECiuQb1@>X3&*+>@Nrts46}b8q_IRkmTE$##x|#*QcVD zqpVVPi~i7?Hyc^BMyNhTB2WNV?5p4eU><}8N*hgn#K6t}m|DP@yL{ z&iD#IAe~SvlyBRnM^ zhDM(Vjq?OPS@2?>b#K#@kb{CARS#uNqK503t{>|E65>iO*ZWe*aqc+9@zn$4)#A@-Aj7f>S_UtH!}gG)|H8uD z-eHbMjOSX^!MMb?jWw$wuyCGXh<;c5&gwDb(t zMM&xkv(f1HLZV%+%nZD7*Aemd#uJ~Kh~k^#Qbct;$qnNLW>nYI@OHr+h%3AD(?CX9 zk3VJCpx)wbFunPX>A^wi$5#A~Ff+(g5jY0C&=n_$1KtX{B$~v5f(R5*)*x4i_d(-z zCBj{GTq87d?Fw8D0)!bVIk78nwGHr@U{_!gVEVT!FiqB2{${Wh^p#VEsNFC$s1Otb zFQU)TprV|bz$Xa(#d>H_VKo;qsra10Czk(LNW+^JC)wWXe-lBR^lr1Y8U%yeE&qPB z^@B@#52i_9;QWM!7X|iM{<)BgLgENd;C*ZPBtW_ESt~B5(m|M0Dno;^LaxeCepV&< zZ*a)5iXq292rA(o9vRGms^AW5`4O=0`%Sf0Z}a_z_!SrhLH&Dz?^yl@B-H3*!H>~d zFfWsQQ$+G(``}IGTd1XC1;)dm!5_hK;6^<8{&ZP>H(?Grky9<&@5=Y4lZG!Y3XVuB zPo(f&4%fh&aE)B9=V0Jb5X3|{Vpcj)a1Hs16$oP}kXu-RAMq6a9xqcWLlxxOu-oeG z{`alG&T~P6w-0g>;WP+Gb_#J%tjP=zi{ux4(!|u0g1Hi|hDpKGcVLlq>!>(*Z-F<- z^7|ndmuSi^lqpEp$h$-2S6hz3L^PGyQwtvqdBU4=s;cAMXrCnU6s5%AbbQA&@(%tS zaTghGc%iL2!QA>J5D5-U^6gH?lppb{S}g_OoQJtwB1;me6kfd2&tZZo-XE&t8j?7c ze*@k)1rlsvd-Qe&k$5Ap%rhfQ`yOK7&W?C?;}nCa9mx{Z;BIIuf(4u$Xgm!4D?xA- z@gjJQ?RL8gDCjBhKHK-Ixm{dVU=}>5I!;9`?A8>3t=>>UnqJ`PSWp;IyshIX8^rGG zK;KhW(LVh6pFo9w@=>v?Ky;76h)yZgeF}sM1PrO~5RaS{lYh47aSTUdn0Mgo zhbKi3a@Q~G$a%)h(>hc^W1dvB2*H-jb2-|9WUwgHBQQl&u>4P_`$HgR`o#0bRA!0)KcsS(W|q~?LI@G4tb{*L`IPV+}#N*pWXw(*-)yl@cA*=qBh zaQU`;iUPIdGof2zo6JsZ-%Rh0NCy#WK7bX%o1jEaky@h><~6mR2l%Sg;ueusd>#VL zWoT_{msf689VJfn_9Hb2F3&z}}H~9|r9E&Gj1figGKE!*h#cFJl6ts9$@kcql^EsTZ2j>**!D2b3$hNJ1M% z_;Yfm=i8#S;G0ImakN4=m?P4KaWUZ>K$#HiZKA>Rwyk{Z`Kq+z&lAk)hO#lO_#3vt z1SF;*E=71YkZgm}7%A{Rs#<}I;USO4TY*#bZdm@CDWvwubn-){oI|RdADyZ(j<^*dCm{vCcj1G;CzrA6XE=!!Vxs1KZ+iB`Tq~zV7tZ{9U;AgqHvc9*Fd{sdYx39 zSRIGio1)X_V8&@HuUf}eI|RDb|T?XmH*O3G8{R)Sl`7ZP(g>$F|?Z68ZE!>>o@VH-4fjG;Z$!QR@ zI?dp@6)}kL>bFNEtKU8{bS?oN*QxaD@E{@tf9{dV#}Th1KVMD)osOSbr=w38?}1Xp z5}#nk3GoEwu~rUuF?eD^nwF-0Bk(PjEW1?G6M^8bQPU}VjZyWIB zROW`d4R?fFfTGCWHOrrjG*zgeaXzN)Iz5TdPOc=}(hl!iVLP$YL&N){(Lfx4RpAL5 z_mj>6G>Yf$m*FvYpS5Bn6%F9IJNAQk?j9aUWn3-A&q@(XBY)JGO z09WL*;q{jPB!awk+iUrD(HzS^;Q}--@C2%)eXZr^6`-1DxBIaMLehfat5k;FwRj$X z3D5@6;>LeIrL26t(RU;|{9k{}ssl=q)Tr&~=?094y+aXE5znw)WBD%!P)AR&@9%XL zEp;V0DFP=L4#`t0!@kIjL4r3Q0b;`oNsUc<;SqwDdHOB_AEl6TR{>x6V(CSUwwPec zJ!@CsB^a6*+7&3q6aB;D<^enkWzE|aD2n7cj#EP(p~5Z3W= z9jQ=WU;bqI$8Zw7JIkK}mC@$KF6-8gcoaA}H934=z)o=1!FTG9Gmt^d`-`?9_;x2* z@6@H}S2)y{@KOv03d|_9iUmMSl}2C_=~a!2*vJ_~w6hf6gFs-D$Oe2>2qJ%W)_4M_eiwgEcXhpC?Vg zrAHNoF7yP~JPqSvEniV^9*P45ArZ>mW>u860^1AJ+$~gAb`g9k7%0ahU+}*a63?{q z&#xY+sTD=bjgoW1ZwyuxtUqa+E3}5Ub}bVEZbS{4mXllhnLUaea{lvUOme=9=C+&> zi>FfL5f*omoY4@nzn>jKnj^ec515Z&G88h?{3U`dEC3@rGU>SpzD`GT)~%zqG8FF+ zftYsD5n%R1x#4aRSxEcIW5Eh(KN#2u4O)TUuuP<8Zfe$;`lS@%b~s9CAdi3hB=gt- z#`?Qr0C;ou-oH*@11Ge@5piMAhPP5t_|YHGg=1}mUe{1jL}hUoqSui)IkEh$YOCxX zI574W;Mo%pJM1J+IMo#2qT)Eqe?Jl|bcW3}>g-XZa=k&^cld`51cQfk;vthd@Io4TGy?pOdN?h3yb?b6eLZHr5eI~bGZ6_-E8-eNSF+VrAQ_pWSHpm@Ptj?_mAyCPzXwy9*#3hx zsSB~=w~C}ZbrLNjjP33pRyro96(I=W+YR1c)=U_m-PAv*}@NcJnwFs?7Ht0c#mUk7dd z%eWp#EJgh42g*8xU-g$PjS%z8K^$3%grx;oLWW<16Te8dl~#$94xT?P!6vEmu!B+x zKP?*IaNi$yivKr7%G;s$%bmK^mXpiJHy!Dn7pspkbEOF2ambnHc=)JvosDF>OJOS~@mZxPzo?=Ws5qV0Q)fNOBvXNR*6XItozm)`RBw4(Oj?R09 z=Fv$hmnAelKUA0%(s5v(TbNbi4SUG;`~bagVV33p8(txf&A)^G?3mI$?1+^=B96(C zcxLAVhrCV1`F=bW-L0y-p=i%5Z=p@p-F8Gr<9}#ciq8GrC_wP#LpI`eBqN@KRYg=$ zc6xcHMML;X>g@%-vyQ3jT+C_WBxe#_C43%0EntX~4^^ zN*eE~Z1&H$PM^PW5RgUG9Y=GPGwMFp4f7;td86sN(DAvh#DQXgOFzV7r|w4OM>Fi7k$JGzZdU0)yI3GYbTSES$>>WXRLu+aAmEi0H)wyFkhXo zrWb#O95c1#*)vcxA#xpR$DfYQt{WkawP|4KqhNXmRE>SNz%ux(Z@000U}=2^`59a~ z(?Z*2`PNGAH%^xvS_o#v1hEM_iVl~&nNqFDgy6-5ApGND@M^880=pjYq(V6^vKaP+ zs*c5pV1hbvUVyz?Y+0p|50HrYR$w+9-C?$kN5M?(IrTqO6p7HMhDP{%tu}v;bOu>I zWEQ5<6Ro(f!dRDfEJEHyyrEmtg&S|&`yFMLT_zYJ({c?psl~xoa`Odz`E;Z<2S>2q zB{(mgB%=u^)=GZzE)X0abI4`5VF6DUqx&lA=v^7m+98Hs(( zs1-4i>=Otc-$AR+6aqJO6(^JrFV%!n(jh@O-qCmX_pcrMS33uQ{MdAwKnKIJP;O+G zzd>CmygbuWao;g4f4K=zD@L{O6uRL9Gtstc4LloE5tde7T?vpji78^5}{JFRp&U?d>gEsFCjv z1ja?Ei8%o)CnY?b3gImLWQh*C9GeVefJCZ~jKxG^LBtB$t#o+V2Q)Auv4XbhdOLIy ze&b80Br_@L5|VV3lF0ptOeF6j>+Eg$XJJg0x1qJcpSErN9WW79$3dHlR(vjG4t$Sb zE_6hBP{iuqO6x_fdZ()-6$+`N4%xg;<|K!OI2Yn!>kINDJK@6m4~KdQWb1;Wu(y^x zQ%Egh9?VD=IMOm-BUX#4rV2i7FUJjAZ&p-KeUz#Q`SdIDL2 zP6%;zh2mpbWUCEO%>|aJ79_B9k^I9LdXz&b@%ZEZSj&5n7m&6eO}7GH!{+2Uhu3bP zqHr8g3C7~7q#(40XBapwyaPeqIpn`kd8`G7jJ2*zim}8G?+)uQY)4V546gVQ=qRH8 z$QMrcxQb7oe2?K?u?~#R-F+hpy_ys{Xg&_0wju6B_2zFkP|V*0v2e%y?G@`bF*i@C zv{tl3IoIpcG&{plFo!*wUi^90F_)aYq7yzC=SSw`aFOk7;XlWphz`vbQI7jy8v?@F z$^W7@PP2QXmhMT;I|)VohkOnV*Pdp( zQ4x0>imeOsi50H&{!;1EhkvBKD6vkn0@q`e{U1 z_E|j`YV{Q@pN_< zQ$}Q@qDww)`04Z+8l*Pinopb^R+IONwet)l_KvOVAsD41SKJLW92Shjl2a7?M-+@l zLHQOcM#kM0x!JA&owy-P+HE@^ENLq4&){`62iGwrEgw5fj415^|-<_C!4(wGM^4LW981Kufe&SMSfiL&0E*kTCC^L_uX zm_vzE(xo%+wbS?8L^;J}=eACDoQ4vtFV3NKmya5v!1LjRTD*M`<;_)_x1OzR-V#8b z^A>n9>)-O>&jd4gl@o>|e_R)>3!Y~GdhW-LG&F=cfZwgR{5Lemqc}zxfqm)2WO1I} zkb6gRtU(?=$G-zUg|H-jxFu-T36pLVMFvkACc~(a77hR;2EarLAtLP4Vc^{$TYpE* z4(ZXEIsC-IXj0GD#o>EU66x;<7FN+1olpIV7`+)wD%l^McHTqkmT3_W%YSsEru^ts zOmaLM!a)t@BbyETav4|$w^fuu?nL#!gk^Gwx--l10}g&~LxhX+n?s>X@ViLz8`+g@ z4UVbDF2KORTrm{yIo0?)LcRIA6VW75_H-0*db1JMyglsCx;AmbfEaL~)-OqEOKUhIJ|u&zR{*6p^-3 z-gyY`_y`-ZxUViwaVstV3R+swxy*fZINRVp zIzPr`QFIeIq5U)h;Dq+w2r#es9MNQ9F_UeJar#S_;}%$fZM>a4JboTPXbl0uF`n?l zfMk9x?w>S*^9sEQ`1$>4$Pb>wL8SOjK@b+?-NNtzgu~Nc?4d@3GvVu8ueGLsUzHbC ze6Ne+%Ps0E(YRgoQq3G+iO2q4QxQkEp*h2wfkFt86sF1s+a zC_gkR3!mEwB?Q;Jg`!|Z5qF?vIq%c1e(P|TR{Y$)f+|CXA)07N9?0$@Fg&ohNP zVnN|M{Of6VV5?xpdf4FwbY_H5Jzohww-3l77}7qt)D-%6NO{JigcS5r z3x65yc{mBKK-i!S0W0wByQd?4#?#c7(454o7^w2I^BFi@wS~L)w4~0+`_!JI9#dwHi08P8$S4UMCp0RXzDnf zypa;g#O=$08-O*%J`X=LUcFPeYaMurXU417UpL^%?L{agoN-o6pL|Q+tCmg{L;ueL zRm!{m%xHEB7RjR)0WEUA5R1G6&#phWv%j8aX0)DN-hUJN?MEplzYo9s*X{^rH7a!7 zw90ol!B>?W!~oqGZDlPVjohbxlYuA|>TP`H?(1d6qd>Thm-B;w;1(SG(io;#N(0zV zq-u@b>NuKVvE{Q7TeajKHv>yB5sMDqK~5s_q1XkWe8%>VGp`2f`Nw$bQl3A>a+4wh zc;!851H#~OZy8R6V`uuaJ<$5-W3-0GRRkDCECLOviSj7`+6-dwcov@*hTf}brFL%|{h>yR}yx9#9{7_Cue6ZOf%2}~_WCNPmwb!D1!Edd^i55uq z98m_MwPX>8hTOuSA$X4DwBd`;To^2d0n`jgw%%j8-2T-YXNUJ#6fc(XIuB@0z4fT0 zH|P*sEYUSQE%*H8*bIwa;Un{R0vR6pY?t}Jq&4B{*KG&s+2f4E$ToMxdQ}mu#4}^n zo2PF9R>U4>#zU;(rjGP>@mbDJ$sgT3!`|k z=w%SlY`w&S=XT)5q|f&;q1bkhMK5bmstASaF%%2I`CrAXEz64EPVd)T2#JR`r97Gi^Z=)K(qZi z7Q9goyqNsD+1c^=^_H{a^YOF9n+H5+o>=RduR7@tfc^1F`(wO;cW~5W@0Lxn{96Iq znGatK=4J9MB2e`JC6)M;AKiSt;>58Y&tpq+kk~~*SCmxO$u{le`OvF;5fXl%-s`P# z#sM*`Amr4qT3siDi)1p(iISZZ6PLW_@B~cA{LFb8>g9$Y_5+{Bibx!Wbi=260odp4 zfjaL+e5zbS&|F?<-s%a{Uy31)%NEG5O^( zAfC;9GR%P&%Q$c3z>8(wc4)JM&luKi8=`oztS_$vT120X&)i?VysTTaznIpgf4m%( zFP8qcJMd!B=PeGr#52oRZ{2XQ122~Tnw=%yS2$U<{WBImAB*C}V)uDKv+W)WUS9`Z zOm^3ze1>9?Z|{pyy~N@#s~mW-*l(NzFBU#qNAY6O=kZNZJH(`yXMt$@ODys&bl}Az z-@qtdEb_UX^2K7m_g^?W`R;b$#UkG|XNlLrfftK>r;riY_KO8?a}+NYJNSSmru7nW zUYHe`=jU6293-=p$538^cfRKtj<@$ZL$UDJ?Ckja`Z>oq=y~QiU2j+DF(96e9_OAV zULOZuEdHfA@M4i~@3Uto->S338wWhv1h0L<7jAPXdQ7~?=_)wHw?EF~Jl;k2$#Xq^ zP3|vTD3vFG#Y2S`F2a{k(A7GAWf2*&lO%Z|(Hg}+naIDp!zPCunp1oanK8ITdPygh z;fJ09cb|wWq8o(|NA6?bz6luILARYx$DrV#?pCK`U~fvKj80MSAH<7bc@(Klya+P2B71ECI06z$lMy z;?hMd4>$mc@Lb^HJwPcsozPnTp7=<cMYrmaaUV`rN*G`!L$zzJUK>5;R7up&v3F zT}lWH#6c0RbkIr6x%61y)vlKJKI(YjR|ikq`WLjO%R0m8eh9x!qK5ByiZ?}m6Asa1 zK~bn5*vDrtJnQNGwaf4l8j+4~CE}kiwGR*8t9yd!GNIk-+q$jrJ+ri| zg0>rAH@oHl*a)Wx7O=ol`2`mpFzzeauHZa5q~=GS-_^ulZY$_O#7sq4`S`>?^~){>NP@@?lCj6By*LwT6x36F&GxGwujt z+}%dK$lC-YCJiBRL)degapWKqarIN&?4O7QK%_jT|#_V;z{L>;~$ zw{HazTSs)%P&R%C$nv}70$x(cCgHYuPd?q9oyWZx7$d6(A+44EH72aU4h=O9dkOaoFBtdk^13!O*Y|$?ZVq|B|kO zM6636y(+?&ljGZpcL�!5qQBt#~cFfVx_QE40f)-aCV929vFMeZ}RKMkqiqefLU9 zv+zD#9l>}H>G%#}d;>C-TK-p1NJJ}$*wU|~-^dcRFdv*#9tYjX-J~@5Q14KFCyJI; z7=Qe3bKq8tlh6PZ7B`^lE>>U>71SGRlj?+EJ~YGEZmM<91GmkE1K1&@Rh^LH^s{x; zR^EC!%{}(V9*dl%)uq~^PMC;+>Lq8U`dO48KEuaA^`HNqk=I+!p4UguOf~83sa|YT zjpbCe1(2MMWcxjzb)YDInr`PZp;6g%(P4y#*OnLJBeV6~DW#5M*pXh0*BLl{r5OgF z=Y8N&XZ~E*6ULmq9)^K1nOKq(OM~NIpkw;Vz85g?=^Kvy8%3lEZ}>3EM=a};uOFe% zL)i+C*J1yD(XEUmTyf!IbSrd3pE=urofb@~xRdXkO~rQ#-h?{N;8&QuIfEbLfkGkw z*x)L3gBXyGH+$dp8ZaPYBV8AX1gc+a1u9I>ql$vtD5ks@3_Oph5?tfQ>yo0=1uCkq z6R4Vob;Klme^jkF^#d_UGZE2R?1)n^u0hk#>kmV4x_7 zO*IL>O{%Y@r&mzI<2g}s#&cUw_dR4gh%+jk@nX;{Y95)U`Mss_C=zba1ULF|!ToV^q}{vS+%T=pwSw{qHkl)?451ebBM~J2PIr{n=Fxyq;&qtJmK+2VUbd zJ|rHES9+VEb*E-@M7WftNSAI#bSrYfo9twrtvZth}NckAzgkreVSq5Lom%$aU zBDtX~XLm5LoHC{nr^}eAQJsvbML3LQzx@1Mt-R?yl=Hla=sEMI=sGw&=A=DdW3gJN zd%;E|uZaco)IAY<$7Hw7z;h;dzt%}x!!skt7O@Pki6DDce$>GsM=Twlx;rX=EPC7Q zz>8%(FN@;EGQNfb&DKjScqzaWsWq(}E5ob5=VpuSWXW}%K^s-hbSC^U{7|kTDEX$Z z;gp{g>V=xfCxvJo8eW03CfQc()JFy+zH?zjb~s;b!pbIccX?}JUBT6vjsiCZ^6v%hW2v4Q@d zZy~hUKwm+R(e1t4UbBaAERHe#E?B0(i_K8V+s6a4?H!86FIy8L?JbJWnca)y@Ccn) z*g143m&x9Ld{cno9rRu=JZII(Pa@%YH8pphQb0N-JX+{0JRh~OXRP@VtXSk}K%C&i zfX}z(Ec|%~9|wFJ1rrMvwBk-wcsJduirR7)Sj8p^vlW-z^0P#35dZS4*K2y( z=KW6BJbW>d zTL{`Zqf46h#*xz&jFQ&00v17;jdPqcX%A#o}_OC zzk|+p3#L3!EB_ii{F)_n#Y3lWXD9LF zQ=2&9^9KX%mFn|#S4qZ=U(#>f1~2%rI6E{tDKs!$A6OW=I4O5uS!w9<+y6SAF-80y z(dMZ@#cx5ano`NXKjV0?lD97mrTIb^6$URj5gO_W>?vt>JUe%6Cu=Q!>J8r>m!BP| zT5t}pDNYRy@S@*SA^ZgD`z42{)xFz~ADmLTc?w8}JHr?0c)t_xoAFME(^YuC9Pjo&HCb)bFvYDmY~Chkl zl-`(A8rYN-#Vu=qMKvB(9hyQIiLI2ODfGo#4cp=YX^lhy1^nDm6v^#QbbH){nv6n2 zuuEX06gAp^N`##_BJPc{6UA@rav-oQFq{TQZX!!LUaIUuiqSL*M#(fw0cIYy(VI6B z^f)F+appMtEgGxsJVMNtaa_7{B(uD2I#m;!t+)=5&9&~L_V)-|wDY8Mjb_9-jFTCu zk0ZjOMH|_IciFZJ>_N(j*0<{s(U+oR$$AHVd*G8kIerHxJ~>E!JaO1DN<)LrJ2^l& zP-iDwQKT+W!Wvq2jq*ugHfRv1=$62o2o279lu9>=2FIax-MgqcDbd;u7d-h^mcFnFxQQ-(MTn6`?%H7=&NrOT~YF=_0W_a9_p=Mgj=r2XpiSb zQK(&iB19DPTS&IYx-a9#A3%&N%0SVnq73Rmf}qpE)N*vZ-EK&fNku7$)+x&Q5gwqi zC!dGmFw_Bp`Y=gOYIC>)MB}0;*xy6GeE}u&7q-I7MLoF#kBG7(T8wm}P>0Ip z-4IfExN)hU<7SrnSO-K<9Dmclhi?$?nua-1-=7UgcO{JPj5pQD0J^RvY(b|eECa5t z#_uCYi#vrTE?3<2S;g?yxO+iTHxl;ad#<#vyP&2w#Xjv}1UpwnfD?_o3SWPueTS=6 zt`)OU66Z?LQo)654b{iH5?oJEJ2ie8zA01dg^LhzIa^U;TmW%b$8}x`8O%#TFg{78 z4@+nniuq?2z{ct$9CVqD&@!G$&@j_*IW4}41U+UB?pwvDN-)W!Bdz$R67-tiVz|dQ zlVGYjI2~Yf38tAvL@G^!>EP%CD_TlIs;&9bqn~{ zGP2F*urQ9#RCjQ&hj|rvk8dj_>TPa?BI7$qFwfKp?4&N_0_K~4Lcj6Z>UkU-Yz}~? z<8#y^4i=bCr~tdEdpPCu&BjO^;(MtdbFk3tMk4fAZ{>}P%oD8v7OD?%@Deizr@Zk) zB{Me4JE;K6A%(yf5E3VmCR8dV zpWvlG*rn}I`U`-D)YkeP-li9D&JtXlLfx4P4tyTVmq`R^9_O$+q z@aaxrVy7WsGi6O@MM+PbtYR`!%-tAQiPQNrjk+}*0nSjV9q5=3!wVBq|faTJYQoWln>Jx8LBZ^A%j)Y|rSBes?g_e=# z^@Fp-HL^__mD~X8{K6!4b(y%j?L;U1fvx}96U8LPX1JkOaEr4q@?AjNP zjgqX%^wXN$YSt9ncSd7SSW|7^Y19tTv^HF!hPx|}t?7cIN6{{UFxItYM9Z*dp2U0d z#A%8(OIkH~_8i5UEdZCIt%Jp_IeXEnvCF!F?9ZxjF+pV&nc$0UL-OciLy=7y%!Klj z*iOXYbhaIuuTt2gMBJND740N=vC4lFR5ren04mSmMP)aGpvLAQ;OXpX;J8>N{4|ce zgG+t!%mYVBV3(l8U@f3BlYN0`*MQM)Xu8>lc=oXNcur)qq1}coAADHs8E}xq5JZ$@ zc0J-yBi0zWDU2>uc-e8pjmAvDdYQ5Az-_`lgML!ke)vICwklmwnz1Ud+nh~-`=+rk zK(htYAX`iJ5xn{w_Aadc-6KV8@Y@Ya>>#B(-_$7>E70Xp5-h6YHC z*iP`!gAGKFJ=y+diqeZc4O5=WIzYzW>_b>0myN<$>cfg5X8sv@CTuuNq_8jWqOv=oevQ2We4QOdYZp6&I26ZzgYx3p zOE7){8wbe@RtANcY%h$~fb9esH(L}(+8u}UwqhURxivco&1NtaX3S(qptUwEfReWCFwE7CJ%-mTb|duCo;5-T z9awu{b!6W_51rU2FnDM7K8)Xmy@A)RY$Gg@%@*T1hs}gU-Pi%})1CQ%+k-s?4tug( z(Coz~q5NFd658v{Uc+-PqYbS->^)%hWeMOskF|u1{n&qDx$_uZQ|!-7w5(EC7ACW8 z3OgTiY**MrK-{6QOMtmkVb?>5*A=!HBmNDAeF}DWDXb?3&u)bc0t0&#_BXiPt1$ZV z);ARv58mEV*tzM7^0vZGzyj|m>@_I)U4`YwE6P5F<-kPmDQqK}yst32HT!|WZiMwd zRM@NN{Ue3Bptb!9qo3@9Hi8~Y{#s%!-mvQlN$kZ+aBUWI(OtL%K>tybBZc8an_WnIDN9V)vFV&18;APjz&$}WNT z{6}TrNV!{O{UFgjDtl2?lzUZnrLHLVsqB07a6jr$xK?FHQMgW3QaV9g!)mDQ0v(g` z8q3li0ToI!D21|;c$G+3D6&|8L(NvQM$ajKp(DfcYAz@{6_c{nm_J64nbrU`0(l-( zlHmH7NZbiltR@;gC%7I*FDVI7#t17#TPoqr;qErI$t@9-4N-dtPSp6kr zq)wcuSosq2q+Ubd00}0Uzkz}^P=a1_C7jM0B*9d(3Hr1KOEAs+ssq3wQuuVU3w*>X zkYJ`+is53NFTpHxT4#WT66|D7M;x(+N-*18NO~M5!5-!jj0bDD1bdr*UjJF=l4}|H=FP;_g%TWW=2E{GNwCnn7d~K()Uu%=p2!w?AEyQv%MxU=MNlcF zI|;70N!2ajE!HTlH8hd(BsA@@#%S9~$@9sKmrAA-^IEvCHCBQyVfxE>OOe#x3>>S9 zdLO6Ja|%NMNVTriZUPcPyT0lBZ3hC}@3A)Uaa87H21PzmR;;m~W=rPMN&aH_O zO!EE>y4IwqgkEnS3_fdeR6?(pd&Cr3f}GUbbP{qvYpN_kPU>wsaV`=%S%8$(t5`FL z@^tM(;(jf{!X?%W?Ny9u^AujJnGsd&AYo=jR6$y^X7iR%h51}3fOBN6$9x-esCB&r zlgv3pYOWNc5|?|SxH{7T!MM2(XgM-aLI=~8T6t`BP zc|Td}HmwO~vdEi74tTrJoC~TP;e81~$yzN+bfoShyaDp}HKIgoLM5+|v)v)}&8XxO zqI0J#X-p*s4VrsoiI++gD!Esdq)^G?E-1NQmNcT0n@FW=Wl1uXj3oXakR?e}GM+}* zQ?kUOlDjErJS|HaQb{3s;WM%%kxH6km{`xr5)YM(px&RCC2o{p8106?U=a*APjIcm zYsz0R%+*r6-ad%_)@Fg>hLno;H5y4k~YVW%vCluFatGbSn4>#_t=D&9(p z32(>}NU3;lA`9=5B@L)VBMa}AB_@?DA;;e%OAIRc8A*e+SC%AD$#Amyo3bRHN+y#X z-jXG8RC1Ey-P^LnMJ0R53*M0>I+eUkvG`qCqEX3miV`1*k~oZKm-ln(YriOohvr@0 z>u3NSkXX>X%bP_dhhzyf@ACGfQT2%|f#zM_D@d--WeGIz5`OWeEP>`--XhY*SF!|} zcbQEw{aRmZ7+4r#hS`l`#!)$>JmxsE__x|PUYlh8L*j(x2=kgNNCV$VFjWMJ<1#9w znQbv6TPGxLrg<&7!AS{bnJLuo_Y&-6wx=oW2MK1IOKD{MD8U}7lV{;)^ZuuG=HtG% z2qCAm?i|cB-#}Jk{UienCLWp)ev#l{^K}|h)mjcbL(3>M#}LoIO96|_NyOD(a#|W; z-bC^$x{&u0kw>`nhq(A-&G(7P1pN^XUXEe(4u*8IZqU1$;A#wRtS_?gvPq-imEc;$ z2V5(Zrw|iqk_)d+#`Nfsxli%VCI?KEC7AmZ?;PT*p)A47pmb|x1{mL=G&P`vjNRwGfOVQ)h57LgDsvJFC>VxDY=60a^aa!)`kkJU!MA7!Z%<|$TNU1m_Ja{;yE738|~%aT@>GzV>1;ZRAj2;FMW zDJHlcM3d$&tDpWQ9?~eWJ5Q(8Y1&leUOKHc)8-Xpipl3xl$1Qko@#Z|S0Eau(soF9 zUCb^@Q`()edPu$TptYBD+f$bCpf!NR?YYP%2bAKQJx7JVg{lnRCh=$pVbQ>85io4-@2m?ptOa~sV7(%^!!%JBOI^(|cT-0D!Kc*w7Ma5*OAvfYMTosgO1IeDMw#W!`itOS&nQ>nyEk0V7DV^o9rfxv<7Sm;=Y?@ zq=O~6ECyL}a0qBxIG0qC2dVwgOUef*o&?|rj7sx4^q)LOmBGb)!U<|7BXFLqb(u*{ zFy4F+V=}o|)*9yhPOt$#*h-!+YdvNmf^PBx-YHH8%zGe4@LVC` zl-IvSoR>+ksW}W%B`=j=GqV&*NiLUQbF&WQZl$`Jlj?1rBvSuT`*SeQq)(J4-y=yCns>palJ8f$^V%Y$dx#~; zL%6ceNlm^|%|M0O6E2*5l~gE}pNK}uSMw@FLB;b2a#A9|J<_FE-(d76PgVbf{3$;p zzIc+?aIwvY&@lN9*|%ceN~*U(&D=@)x>MG=%sWXVHW+WdNuAy$Yq69==#794aPq08 zLr2Xr!3GkOC-IixqBG0Ju12#dt}_dR7u!@|O=a|Zml_LpAcub!26wTWp~5(}7bc2l zSHP+XtQdMS*kC-HEC3H`z<$plhqr*`VUyq&iL5!=H)P*{QH#w+_ety)#QbEo0D?7Q zuYqz3dkoKB#h@P`>CtHUb6|x|KpF-4Ne9lOXdY;E%OhY;%Sd;RN3z-|Bxix-DN~h3 z6=J+(C0_$zg#bFZDM@W~+c=KZiJxLMswCPtBZc53u+|TDZ?uvgja}f`NNI8s&u+>f zQc^{Kikr3$Qkn`nE-1^}YYb#!b5M+}J?IbHS`b5H&tg>T?68NFbq$)tu@xwZXY12R zSzBRPgI$Vplg-9!1J;HsD+6sjEE7T{GB;>8WRHP@g^n73v>9_To7jpvS`AiJR)b&! zt3XjYdlPQsVl&~%acmuG5F zvGX88bJiCFKaKUlIB3CMhOe|_MG zPd|158at0&2hI0qC&6Kr!uBHFz*cux$b_x#r_m9%x|5(~Y;}LqnQwJ}44T;L4nat4 zb!R{y*y_Fx=D=3>5;x!K{vU+HR`)pYfUWMX7(m$S9tQ1Vt2+g6*y=VQ8@9SfzzeX| zeKGjKR`;7g$5!`v=oMStgHVXA?si}aTiuU?L2Pvo1WjypzXmGU>Rt}Xu+@Dnh+(UH z2hg$A{Sr9CR`-9P2W)lEK@ZsK9*mZUv9%7fVypXx1isaM5^ja9?!(X_wz|vkhOKTt zEQYP__n=H{bzcV+V5@sVTfWupf)8M;`v&lWt?qcZJhr-ThqT!0{tyuYTipiGvDHnp zHMY8kL&ezY4#I}m>dr z!d7<;?0~KA0-$57`#~UJt9t}S2e!H!Vyt4T`%WkXTirXLI&5|KfoEW=yE$0GRyX}1 zI<~rNP=~GVE^r2Hbyq??*y{e?#kacqzL=KcO-oWO!0#PvGq-(1hDOjV5UMjLIzd{IfVn0I}y(77v9yk3D?Y?*)~4Aj&3{ zEkxLOQDwh?-IrAM80_$}%4S29%_^h2B(I)^Ac%9*H1RhvtF(Y`A zX{pBK`FxVw4^phFsPnqdf!$cPfKuJGUCMF@J{8_c}Na>mi^l zH-iFMU;1V0_x%Z1S(_s6mhkT-tI}%!=OA4?ADss;uDi;Z8gqzkkY=nR=QPOc*gh)@_ zw?s3^T4o6F-BvMWv6~P6((@g&QQ~)LT8Gb)}T$Bi6yAG z?b5V4HN!&NP1_nx(*%^{rp0U17Gf#uO{S$?)0U$kDsp6Z$9UA8BcNt(S|c`17g|bl z_s6(v+Dbs_?x!$No3<8Eru%02Wz!6Sm*u8qThmMdb#RX-&e{m56I4kOHg+{jUkC2k z)tCcR_BsZY#@>UBI{Oq(?P4R~CUI;Ox{PN(LmLT-F%jzaG;eaimc4l-w;?{8+qn&w zsChHNnIY~y9Rp6QJ0T-NWMfxa&S21G6H*XSHTF9!TaKfD=&0Oa^y_)$N$g>a`SNtu z0<4!;DeM3SRe8C}wjlnM1E(2g8I_emSsH7LvF~DeiAYzJ*6K>AMZG~)u0#(RG#1tQ zkDy=FbcY?)#i~+DHI$pFi+D|@`Y0SgYoYSAUcU>~ZGOg!mZs88CZ+AQ;7r}iYZb~g zGiY~F-9rMlo35yD(u2}A6FN{o6s_o@ooMxe-RdLWDr-1Ythz*3ijMf*eqwQ{qU!3N zW+2ib3&TnMQV;>Wfhgl&A2jSpJJjk|L`EIi3H|cNPE_4lt%jb|eTMoppj6m$G~NS1 z>cXkNYY_DtQPy=ADdAm%CeIy!vuXUQ?-|rK4tVg6m(e0eod5)ND`$kV{mb!}fxp+$ zuG?6udyN>m2t}QyDQXqbqqJPtBWsl>w|z>uL7 z9^Uh1VzZ^HR-r5%o-zUNec@e#S{kQTfij_^G;RU9@6a`ohC~{tf0*ED5J45Or3Uc1 zZxUevYb$Ys6rod1SNR4~$(&x-Drzf^dk#iWE`4X)So|sIxYu=xI+a&#Kvf?UDt)26 z>p16V`!w49g})Be78RGOwC%JXZHcIW8o*VRy!#NlTW6!&IDIgxm451Zz)_zQenrCe zoR91mZKrod26|1&6h(brrGcxjJY3SdEeRNbXZAwWR$t(ZT>_MBQlh$v!}9@?wqN8B ztzd~20Zl|Vy=XR2U*fe7BmkE#|Ee!@_-c&NY_7Y_9KP6%_H!pH>MI<)1}(F>VPEB@ z2m$Uj5u9w{m+)pH3T1Omzs8$4Lk0thL0x#|G=d)?x3A*$j{xqy2uSKS4(lZ+X7oqS ztjxd=$>t_K$}9Gup^{IISOx|k!Jj%xy9td3{02KK`Q*UwqV!Ly8Lh3OnnP5ROG`33 z!PtzVzQr@a>f_o;vTgsdc=-^eqMrq>aexoOc1r(py!=Bo|DaoSYaG@5f?Oy200^m7 z9BzU!sN_>*c?>Rm2!HDAxQ-YL18BuO&@LQw2oU8oXiPzB0-WF#{HcTD#!}<|Qe(St z(DQ)kY8!YshL@+&f_&<`cp4^CQIUNS28o0#38qs7^>{q_9IbhJ(PS>+eN=xw4Z;)g zB*E{1mBAF{DA=gi#J@odR0CFWf5-$IZ4~7QiiGD~sgoDN^Oh+6d!u~^#M5j>h#syf zT5S#Cj*`gX>>G%)hWt4fbwaBahi3v-29x+>iNMf=i$IKv-e(R9xY+k&E|iUyQ=^gb z#gRsj+KrZ_Q={DHuELT8f2)Y6A81^h;QN5%TcNi9ZnWM=HQawz=p_3rs^J_^m{K2$ zdoMyVsu!reX^1@=?}1(f^J8t)0U3nK>6cQY%=ny0 zqr2=z&7fo1=p|}2Ghs}m(LuY>KfF-^O?SUhqsIDx5Lrmf$P0kLcadt8^VJg;>Tgu@ z=ZlN>U%`BhFxU#`DQY>*k%--eGw_UZJiEH_VOvh&7@xjThR!OPiAqvV0l;C8lLs&B z9*>WM5x4?TL-kSZZ3O1PcLcZtAk7|r(#zKb@Ie(I4^$DW1fvw^IHMk=Au%=l84Aa} zdgC!pr|-RJNVD|t+mTGD=ZexEC>{PCJVos-3g~C|hF2s0sJWsbp9)gZhuTLJP*&{O z36zy~cZSkC&P0O;)EjwM;72KX39c2latEnXE&3g7$E}jU38Y+cw+kR$Jph!J#McE% z(LGRlYRVCmsMs&ti}#`m1f~{cbm{>zErHo$Dd`8m#du5gipE8^BXFcLn!8bR71Wq| zE?EP>4NzigNCMw91h7&92heHiDhYf6)YR1y__8&CH3HyU+c)IkGa5=!heVWbngIZW z8^iBDY?0XJcLjq_;>`pHG1J^!N*E4+vp`qOVITa$mAU>Xct|GnXY9w$;SgQ zLCfv}82JqxzIk)XYB4W@u2NJ8J*(G~*Q%DP3fI&osx={O5omtdi2sQ)iWQ?a`%sm+rM&O0=%mOfQ~S zi%{2j3+fcinpiS--sE{VCsMiRl`9Cha8StT~&^cmO8CQi`v)ETp{nJ|MI0zeKkWr1uY>*r0MH2Indb4B4q z(gGf#JfTJ4%$q$|vW~Hd3QR(WRkiWx@f|Z(89#qqq%SDe-OCmkH|OZ3#TV_+4_e0V z%IOyv{fvXxzUV5%x?aB2D1KI7m^ZDo=#{&k(%O56&)0BGdu88#Q;Yfz*XL>-RK4*j z-8^Dkpts)LZ)nN%b^SYP9g_40%RbfzY&51DDUmOZ3EL zD_?zAU!&gN@1_nnz4oSl%zf$*#MJ*PHu6AdiX=E?y57KOq<7n>zor_S^)Jg#>6Wp1 z{iQ3lw%*%TYS}3Vj_xt=QnFWnc(K+-)j!p>_NxBh#afoCf2M1l)P7^;KfQO4-&i?* z?`4;*Em^xje|agI_zvj#M!NoS;wgQ>l#+#kC-sfErZ|3uL`tDtNY?=9J*_dlZF zzVy^_Jx*mr;O z{rdCU#%0yt7=GjOz9ssWMW^)QQ$Bs=(o=dbqgcysthGzoqn`^My{j0-`W9X5sv6Ub zpMC;?`FPd?Wm<-+H`fNK2XtS&)>AcnNA(orh>`W6{>$RsfYz?tqcg3Y`i_2|y3z1` zTcXWqtb2^g+e?kl{CkaV#>e_tt%qtnwYQ&N->GW7K;j!MgT15gUb2~}ot(eSxa@2F zZgV3HJykE{EsUvpu(wje&Z_BJd61W+2YczgW20=%EK1$a?+pGGm$kNhze#H#OL=Z<=p_^P^gi6#c}K zBl=G+YGJ9oxWMshN$`j3FI!FNFzoo zy|U~Gq}1KJjd5C+6s;pWug|x})Xx2kB46K9W11goH&*HM^7OOB7_M*AK<6kl{81TM;}*l%d>IsGOwkj$>_&=Fbkx|@&p79xe!>NH8Yyen zJz1qM#E^Z}Xnn2T5-zJhQnJ4)I8}eU0dVx=I%!?YZ@fxxa7w?sWV3!k=mm&~BmMM- z_uoN+>8aX8^#qC2&)8G4O@Fjx_nv39J}LSa@y0R;_l|Lu*2Sx}P1&c1)gyWeG3-0) zGtSeG%|E68+~A15WeNNQ27Y0ovET58-<-b>x-d$#wy7)Oi(BJB<>=ZyxM!AP3^y** zXB=63*&ZW9e{11xV}^b#LF=vRA1nj~lIa`c8?g4bhKK;HJz9Iq-g^2645>ANAD<_v@9V8(+~6 zyN(!FYUg|Pavh_$ombzfVQA?`7VO4&X>dRF;v2mXgB|0@EH+vl+VGBkB4M-EIYqyF z=@EMS9*)^hzf0BHsx)j4Lxw{N+-bLJjMaaDV;L7AI>5PJlNT-9iN$Ab^*tCnuopL2nren%N%>l%$bbtaw;E;Jgg)ms1@ zI(3Hr72J9?)fpu)>oWc1LT#9;XKHz>{*PPhuIiQZjb&P{SL@D7jJ;F!r_lb@#pDDJ z>hyXg#=gES;fOv_>#OSTE~2snyynvz=y_`#y&lxi>}UNtW9(l2jWWozY!Sr_Xk?H6 zP8`DQSn6<>LT%^J%RLKegnzD`LO7!y{-JpReCDe9mkWU315y3cvi3J8Y`xWowy?82lma`P*QxlTwTv`X20i( zdWHMSZr(hJnr!BeHM}8L(F>4TQ(FP3hk*s`&~5o(;5@|*q!`0=UtS3Rizia7I@ zahaBh52O86oTvNUQ{+44YEyjLz+{vWrNR1BODd7)t<@JG=}cJ0@25i=gJ|7}F=qNb~>1oznlG?%q4TuHszV zUY2aI0fXr!6j4kG*fi5^uq?@zu$r|c7fQBe6Kv^9O!TKkeCh9CIszWWb9 zWcbz-E*&gB8|ByEz3ex|S1lM{{KANK^D;mmFLCQS#dGg~O+wdrt8& z!!)vf>!ac?mV8uv>A&8W@HnG**q)x2(#UXS(FN7-i@^C4i3ic~QJ>EnPlnH&?+(#b` zGpyp<7b}PD(tHvs+ik(?rJ)wR5qgMNqka@(JURIJa)C-|d7_j&75v{9-1GaMCqm7< zBZRQJf`2!38t;dIpAD7w?FA&|X0>*6JZyiosA6s0LN&Sh zd&g446zOH5OFDgtvi#c6;U5+MzlFva+sF2b^WzX(?2v9QR!;jrD*o|M=HA24 zom>3nkv}i~XEOY?;^lqgi?0~jZjOhmFPDn?$$%!&Qf0HhfC)U5k~wb9ow`fsG+<*^yG- zFqGO;-2)}#OM=wZKR3upZQH^UwhTH;I=V{+=5_Q3 zK`Umqa(Yss1oxiaw(hZVV~2ijTWd*ITYrD^Ts9IC9LAvF>h8HE13e|JJ!6vt2fKP@ zx37ImlE!(>1F5L+ctE*iK}Ubb9CiTM@mtW`*^vvhgblzsZGB^t*0#>JfwuIr?fZ8~ z%2#qxatB%zF)>tkbaf2uTQa&o;a?E)Qm~TGX@eaDB{l3r9FR0N&rO40$;)8(zsB8E z;I`5QP2H5kzYVI6l1oc6uTb0iOXf8%Xe;5oHfTw8S}x70_pwREA}6(EVaLF{p22~V z{^kYbmz2-zYin**nY%RGx|=D?*0I)<%<1cy-`36UMfZGetvvTz)n6jVw$^YvgC=#D z)iYSq+}BppquS6`(%IafyJ_L(r^S-HRowrAYuY>d@-ND?HTSj5D_Pjb77o>hI>9-> z*yLZG=kyE=^mL6)ay7A2_mfK&ba0|g#R~=HS|@q1TY1VAIpsH+)U7l_mDG}#D9_Os4c8`Nn0y-!F4(5YVMn#3RKCG=Kc~TBuUFA)g`KCs<26@I7x=P zoz&3Ql7_b4&c(@;zMjF}q_VBEm)p`t(p2!>xi&*y$fTP{8YYekfd;C(u4u>fbayVM zwWiJsNlx3Mfwn$&=sFjdboI1$w0BS|N=hbEGODtROXjq3KYG|tV+ZR$U8h~Hu&LHT z?O&AD*4n|NTMym0WC{(qr?+Hu>uO19-`qhI6wx5Jp3tel@kZrZa#GgZttLOZf8P=s zL|^kj2X#y?2;67g=sAl^O3SK=k9>!lU((x*qOV(drGIK`Z*ObS(MzMsg=Rwz(}?8~-G9KF%A@vb_nrGL-g?&_KwXEil5Z$-5oo|WXdClE)r;4+klX=py zu!HP{TczUZ)|J+@(J3f@|HU;b)fLyNykZ+~>7kG6=vCT(@>j!|q)a2S zObI8xlJ&4@>UIS7)Sozp z$N%OSmG|LL{_cR6atgK_lU}z6_2hMo?#*|oPx(fE&LST_vH1f`ue)F?o>;_m(VoUb zxo@*IPgr2?v8mlAx*rOEgLwv{%>!-O(6gdWI8aLXB;z+jc&=#p8bgQbv^kv5OUd7lFq79D zenQctk;5vE8+PK*lZtctThYzKlv+R8dTv$tD^xQD+=7x zv@FN{={)~wT&aF3d7Dih)3i)dO7WEH^+3t`y({!p1$oiAaXWFO*Qentv0TcT%)n5Q zVwQclsInmb<^S-fg1Zf)K*igmeYmKn5%L3--(Lp( zIg#jxBr}S@P82I?VP|u{djZ-VTL4`H2B$w&Eb-Pp<+w44;S@> zR(|kTAYU2vL&dA2eYmLSwetNgM}9f#hl;O8`*2ZDZWa3d4EG^Py9}ByGl<~rOi)<{OVh8Btx*eK0m162X%v> zZ?tfq4+S?33syayrHgRQza|DbEicIGLUmDcPKdcMMS2ujAHO3*g5nyIOcO4Ot~Z0F z!P@XU@L6;fP9`yAZnpUSkiKcc&A~cDP;%u%ygfSW*|L~}Tmh~^Sl^1lP5}o;>kvFD zWD<5MaHwgvJ|fxwdQF~3MW?v(Zq&VqZv>|XJu&r@;vmv@Qkur~B%Y${sW_u^e3=AILpU68A7{dK@D$lfG@cV8f zPrmZ7DISiT$vY4jTq|ZV55nO3?rbi@;5v?eeNPMxum;petMF>DPWu3S6|4ox~1J^X~xiwg{7&x zESiMiE*!ms{mY^W9`3@}UF|N5CU&?BFH?>oURie9L+%a2eUw9Rmt|=vl>T8UK^^R!qwH{OspQ!%&> z*@!&pxhy&s?#XYq4pvR^GNXf4Gc(myJUk0tj8@grXEC^5M3L?oE9U}mTC}RVs;=Te z)pguH!P){Ii&lN?^QQfR>#N}J`v>c&19+2YVz4%p@`lT#VEr?=c1p0m2rjD%)<1!t z9T=?df27&&GumJ2dj4mYZKUjI)jJ3z+pYXdM9`!TDR&=l7_>B>p|eF zXx*fbq+_^j(|-Cm4AvvT$yl-!D7@Aw%U`I*K_iRmbht(qb;Lmbz7?Gv`}NGtG24D;;I@@9%{h!v^;plDtQ=*F-7=$Xg&3UiVoM*qu!0w z>mmdr9LbQ+tfEsq34>4J-F2h0xXXIMS=eQx=q&2X)*8V;%f``J)JLjt7W9Cl!WJtr zI186;8lA=4FgOeMvDTDt@c|6Z!cHa8S!}~7Z1BKV(OG;5gR_vO7!-(jE(T}eWjl*s zMQ7mz`dj%HPsZR|_}jM8S$q$JvvBfG(OJ9@gR{^yHad%^VsI8dw6i#J=in^-Zd~*& zzJbBFaNIu8Sv(nov+&uz(OLWogR{_1&#iQeT^O7N_3LsLe;SNEKIJ8&SDJ)XJK2avZ55nU~m==wX@h3orP7VMc?8`48Da0b{3aJXF)@e!WJLH z;9JnpBxiA0CO8XwV&p7Nh|a=`b{1cc&ce}+(YJU4hOh;Vbs;-&3`W@j-?6jU7M+Dv zXxs8Fj>ITC;0!y9XGLd0W2k(K(_)VxXiSx}_)>Hh)aA%oJQ+jS!fy_a&f@DBoQ1;< zjm}~h24~^7b{3zG&cYwQ6Mc)%VDK&Ir2|DN{tSb&FlKgi7Wcs5EZk{l@xJIRsDo1= ziT?`5gZJXlkk|A7Z7n9mqZDjLJ^8U1ta=?rdyiOGtRgZRmb5y+b&FEohr?ji1WB_a ztR4ThH`k;`GafwT_2zk9c$!#^W8aT`@I3Ld*ar)*tRC_;PmIG?y`XW3?9S6bH1kr z;-A2a(JJJPz%FqO#D|6vIMW4gBJC817J-_2V9mQF8jSVz0bDg0YZS(+IrfN<+InHj zV9jVo67!JJL_>EIzZ#Xw(W(jlwisN)1V4~=BRh!FaMXUCg=X@);>I+!2Hw{+pWZw|2+A!aLv*4_I}D5&txYbER_#8&8LirYt_&-d zj8-h)3ZrF4TgiF>h7j_ak{08mwhOL0n^+#LI!f4ihv2GJ<;&5k1BI(GgrIYThcQ@n zgrIMIW7UaB<<7yXO?JJ+gR9PQUX4~A*;Hb1)sFmU(W(XNNf=yp1~CbPRmVYt(Ygqn z6Rp}N&>jIER!r|QT7un)!BtDJC-)52cR;dNuxbhRPPDGGce)zO+=ulg43}w)KM#X- z85p{6uxiTK6s;QVN9-3|$AZ#m)nLCkS~bAmAFUeHKaW-ox=`KHes+HL+^G@?BRX}9*x%bgxJ|_3-*rILqS|8W=56KHZg=S8O(~- zpMhUT>*#VW!{Ffu;QDC&J$N}oV|MwC*{DJCDJ`iIsf&0fY5^@MN^MS5cA}T-Rg;TY|x=HSMpXRqNVhYH%G5_KsHV z^bD;It{a0bqE++u%c51&nkO*?_9+-q8?0l&#Av+?+!n2x>%1MUn%~UAaGB;bdtN~-DB=|+NYHqMjHn?g&@IbVVnN2xhxNMzf4izw1wK^ZfVEr9) z zFLrVZFatC>>H9`o&hQT^b6NhCO zHb(zDo5{;ZF|c6B#fLz139Kuo6w|bl{~Uv>uzKh(r@cQhokC61qFz(Mf4?L9asF)T zV{TpiQ{j2O^;y1;&sOsB-zn4o%Yyv>R(g5mbkhdBJ-T5ihP?gvymHbOhjs-E%E>#g zc?S!c9RBMGLD)XsNSDvhPT!o+wa^#EzXvzxs2&up=j!bg~2*)MJY|w=Kltmf(rOQslb+w zjZgcmTpptsYITHy>o!z~Z-+`TE%D#~v`Ue8qu-^GYw|$Gw4Gkux6;kiG~r_m!_)uN zylNj=Pb95;KgTiC*)z;`>MKBZv})^j42FJ5I3QU6H{9hPkiU2!Gfjt_Fa58{*wQ)a znbI_M)PMY6(=H#L#n6MH+J3>rw3|T->$m7zxBQ>ozvlHl8?d6$B8Q9}#Mm7V`KGPT zsIqn(S<*g7PkxnR^Z<@n7VX1D{bVOQcEj`iJ`wci3>W_t?1Q7k&+RVyIwqv?PjMU; z^=pXMub1k3aJvY@4C58>ezZ;?_DPt$d51h+7POhCavn2^GJ4EZ<6oiYb*j4NM;J2F zdp~sKy=mn0aJvG-oJ8K@)iYA@aauzz#$0E12^SZI0A}wNzx)** z=jLM$+4#V7wxy@Dr!P5e2d3WP8Sg0T(_HeTXUV&=9Xvdo?QZUB3m@QG;XcqY(Ak!q z)7%$6g;nsNc-T+!bK}kP+p;_&-nTfJNHS_BRaa#iL#j5-rEh4E^`Ekx{%tXg++iv( zjhOVWX;pT-s0`_*(#*Aa2o-b1nsHxKJGYhCm%|S*%b5v(fJy%@qC#whe;v2$tUXLrtw_;9=(I$%Wuzat$OP1>YG>&=O9`Tf1 zv)pvzo9c%!$ZdhTRWwSNTvk?AT~XSQWCyzk``cP~lVg2DRc&K= zMOj^WMf%N@@IF_PZSUx8>+VU?w_WP$vo%#SvrU&)uoxnY(;Hj!>okVW!ri>6<1YlS#?u+MO|(6tjSdkG<$s3H&jfw&+w{; zLe;At@?TnAT{ok&Hd7^!e5-+((>|#icBV4+te_nB3px0I;A3M?r-VnP$|SW z+>-319-`G3XW|=0l*)|Cx@s=SgtBR>ozygWaz#T$c~xzFQzPoKhFSHE*-X`x+JrC3 zbT%(mB5EocOQ+JdYZ|j=@kvNbyZZNnu^+{EC~-~ zrJ7Y*Ur)rzObs(tj5108VqQ~Oq;yPbsGGsHSwhT|HB?Pf9g8)WI#CruNK3(YLU$~i ztu9LoB-9t~bR##gv4J`jima@%v>_9|ZIo4`Q4*>5dOgY+DXXj~o7&jWL@K*^nQBEP zXsoJMgW)A8uFNj(X>VsJOlUB3X%ii--Px9TZJ}~xv*_^C+uX;XN!}9PbL#KmrL3fD zQMRSCr(butaS{!cGA0q_-2QAsMOj7F^onw+YD#AUwP@Xn$&?gTMVeSGbSJ|HiL&~U zq454xw!EUcMwd2DrZqNH)K^o9xn@Q-Q&%>XE`gtr;jO{&;-q{v)l$E!b(0Qk zs;N&ZTl*$=k>jRDnm}!n!VEWvL}ATLomCOal>3>fs;lMAxVde-OiG85oil%KUw13@ zfloh?^X7q`4y86Uj(B?%-OR>{hMG)8V`EigbqK04G(Y;6`l+Qvktv;Ck*y>684d1K z=*V=d8*3}5!WEgihFEn}M?-&;b_BGY&gNb^xLC)i3RLOpin7KmRWq4URa;&+LkUW& zjH(5FTTQ4{m1Q*K3Zku=OmR)Bn@PJ1b(E{?>M7ES(8D!OYACI$uCAEeP(`Ix$*MZ5 zy(opmQ(ad(rK&umvf@_6JOn?n5-NW3pbC%w84XlCT-B@MVP8{QaW)};0o zdf}>CnnPpKJJ`o7xJlVy-z0s-N?O-(vRGSIO0O`ZuAyAttM;ovn;9>Q`Er#dVTFa$U`Z3OANdQ>`-6 zwt%51v@4ZBrlNvgRlPx9$J}`XigQXsU6V>d6%%o#+re0+@Z!)yYN=(qJu7=Er*mzn zVqBsAp;IT~8&uxcym0bhXJ@rL&_>jup)k1g{YyA>D+f|N6k#@0vbjAyt^FNybKs>QN23(#TR$tbCYiYZOi48Z+^ za}LYuBWX!|&y+r)ZNAHJg_y!z-&T{QqSutt_84HpJcJ^0Dw8Al z!KuLk_8hs60lT6h3`nlsQ)zm!W>;yU5?-BE4x1V%^F~T1R7Taya)#8#*tFB2Ll@}g zo}E%rOH(gPJBT=CAt*;Qt*MUQSi?lpI@sIU(W2M1e9!Qusen3!v>JpFCvSq1&RHrM zGO57{qk`HKSz?k=SL<|^X3DCn;!sqR3zDMnP>b)_NEl;Pad`Dr;qa2Ex`W0{8AC1e zg|6N{USaL%Zl?#X%FO9(<~|N~Q;WNKqZa?6+N(%(QS3rB5s;*w*>$V6H?)t&?4&xz zgNmfJqraDlP}UJA?R`C6p-a*@L*wS^O6DW+&Zg~XVRN4%*4+#r(dVn7px z#f+Aor{yMAp|C@LNRZ_fwUwG2v?%EzqTKxpRdRAeT@A4_mNlq&Vh0fiAU+z9o!7y4 z4r56(j-dn6UQtl=SJj&H#m_z{eKbgB+96A|49Y6!nosLB>E;nmUpj}@U-REP;uy!2$u4iQa^>c z5k+6us~4L4nUS<~^mb^0L?q3f`ns&H_59iWVpA0LM_ErVyG=9L?3xXjP$i4&$O%DdDpTVYJRm8{Hbi zb?k8anFlb9M4R@-PI)zViU!-<*)vxe?C))EQOB=ozp8eKACYN{rc30lUh5}K=bTBD zj0UlK(4n``PRm>zj4fqu^>zitsn#L*aTz%sp z)#G9MKlnsA_2|?OEleh$#V$G^+`a z5}MyiE9$C~FlOPtQpDjFF>ENSVP%wY*PQi|Rf@*y%=BGV@B2FDFft|Cj@Hhe`3c=w zDCM+k$o1M`2CEyfsI_A*AAq1(Xk{(U-Pt*9*={B$D+)fA8*$W>HcX|)E4o}qph@e$ z?45;4sS1QLW#6uQAgoRpNojT2$xReM+UIFLz-J=(gbMTho-o4*wKXifbBT>>ZB1ZQ zXrZme8y)bFIX;A-^ z<#F65JGo&x*QKj(VvX?=`UZBOkEnS0>RuT{wu;p=CK^tUVpf(q4yLKz|dGt7`X7ZvCwE$EP zkt|B5a=C`j4ugE8mAR=ttR6{i9h(|c=&ZsOHK7%-9ww08g8#}=nkHK+bp5P|HT~9_ zMZ*pq1#8ug(7$+NCmmfiBhkb@H(;x8?`vzo^9g zm+(S{g)pCoNwNzW$NIypLN`5hXrTboZHV+vmM5{BjGun-;;Twsk5_B4Qe|e+Bcu%3B`#Jc z&rs#3A#xMTxzlVnupy;Ei###QdV zKn?4A)j`kO)tZI&omQR75JKK<$<&uJiO*$5TbregO{^EP{c$fcuSiyO zjzpsgu)L)`uJ#@V`kK4@JDCzF9WzR+*j=8Lv@PoG=<_6DRwhJHotadv9j5Xm!=7j9 z;G)pxL*mr|v~{=eEh1)til)AlJ)kfF4)-Q(a(S2`CuzSHMvGiGN@4K*E9EqHPztD= zEyyrnu*k}4Q$ypT_W#1L95r>75S6-^d`HzJFW6M<$Hh=Wpdmn$$pI6nhGZ#7#d~+{o`lXZDX`~;blWgYvG4E>K4EjC~ zo1qvQ>onGdLlCtqMt@CqxF%H8Fne0jVpxW-{BG}9#Bqn#%JSz~xjH8L(UqsWB#G)A zc2&KP8Y@_=u57^)K%){>S*~pZ%{%rS$Boc;Vv>cqC2?4LS69_Amtx^W`j~O?Kij~x zTP?HWOo`DsluJ5&A?(^ZRW=f((Tf=HPlph;7~@=%K|NaHAu#!wRM*&8$Am@u&4jRG zZKGT3^$p3uXFW?JdC|6}n`oAML*n><@ycJj2{k;%#OM1oOP*O>I;o;so0>}W;Ciuuy*73@;%7n7$;p<-g;lpz@1Z6U=y~6yF1g6`CvW887 z8QNG5l_s0XR8#XBH0@80=xJ%;HvyEqFbN2!J<4G`=%}8Ni34zMn?wsc)&<#gG1D4P z)7(L)+d}F5h|iQYx3>0qY*Sv{g;%oPW_p$`W;Cokc3NgicqQ1Q2ug(gcYp2zD~XiSE4(j4Fru(ny#sD#G0G5hIYmP z+tn3EFN$pg7SB!xba1D1ZC-EJNj)TGW8QYWghW6y1aRu0T|y^??X7)L|ZluBk@ z49u)O`m@wUevL!ReifmXYq3p-J3F~T%S$DmsV3E9rT&|Ur!`ejTYZq%5q^V2YfsKG z!=yf~)>?*=*qu6;|$H z^EWqaub3c&&OL6SvHPSb!^GU{(nRf#jWfz9wD6FTX!Q#jsW4e> zlu_%n_zSa{dd`v?_|PgJCFH2jha2J6Xw%AT=1kJg))+sH60c! z9Y-!4iA~P+`=LXmc;gtHrPVYm6}deKckk2*+I6e|{VjY&GhGSC%|!NlNwb!Moo($d z$#7E?R>S17-F6wbSAA&%Q$7MxcT!qj6AsM6(M{}+!iG}Uiid=9WkYYEu19T(KANt8 z8_~|^6}wxg-!)ljbEBSSt2&!a==&I#7j*Ot_Vds~{E}-}I)pwdtlZj}46sI^s|vFr zFYO0<25{wO*0Pr(x<`)dm$F$b;*=>(;w#wmm_=e*+Bz1*=~n(^4o_4X4N6V5O&QHV z6q;AoA+uU?&_itS0e^h}i3LBV#|Ai>5z3%rPfE%)$6LefMxaz@D!5 zSK~=nl@4U8-QKmR&BeiblG$8L9p#;w%a>sF{0MVA^%xaXb9NdIo5A530}uaU>ta{x zGnH%ih;b2ns5nCl2!ofZXZ~{vp#Wm8GaYkh@PkSrN<9~&$+)&ZbsL*9;n{;s{NbM& z9j%<=d+6$?M)#3Lfu$#e>G;CU_koy>DOe^~vau1i z&HFmr$*8JkbzR+5idSCa;z+CfkWuo%2|;a7ZrV-6s=nzhPB)=_L=XbO0|y35cWB6A zT=31uE$&@~>zQXVIdCoDdZ@bbDXX}zA0BuJGlNhg)4Yd~ zki+AKg!yT1b`a)O|2nzy3eNk_T1V+=-NCLfkx(ZW^Q2PAKd{q&%8J~0CoxVsbROy5 zC5CHu)!8DWL9mwh%Bw~LDB-Ct#u=q&)kJawy@b5I_t*_9 z(P8Go?4C0~9&=%)IS^KUOtI5V5r#l=rpFI>BB)FqP;DLmX>O#WYCWBi4Ufxc<1wxB zTG_fR$e4S57q9|w3vgxEEYQtKMMTB)VT@+7JhGwlMb+qBvSS@oW6g%CwsN8|V8yV( zI+bUlSnKEu)k&7LrHlGp`K9%X2}OKbDYa<&#P*VI;#Be)G7!ost`v~t3_3HlN>h2B zdUFczTCZ=pfQfM9M0jhUIb}M!prxr#U^XVT&o2 zsqSKanYxCA4j~TDEAOYMtm89=p{1pduqazAcAdh*SSmKRu%`MIk9={xx&_siy2+E- zpKI&&WL<5>Q@dE`F@~2a$RN zFif-AWC|xi4xBT{mcEW~8n0xB0_73FbYGOl7amCoyX`tx&P__l4NtU&1L05}8WPgk zJbQ29JSj~{W!~9Ac)(QC8$}lvb%zgjgoCK{YK~&+GAWgdYaQ~=xrEHCcErE1HihZN7$cteq(Yc}wD_<>&lI()8 zkW4!e-}1xRD$#WpYJ)E;FP&rgF8>=egp~1X!q4*R=+EzD$Dw`!Wt>iM9QdYKa$@b-8>pSiWjM-xcZx1A6 z`xkeS6*$lrIWM*KwRMgSXX9gK3-h?KbNc&}v0=kH+dOBEN+K$CV#FQc0jfMXEV9S; z_2^QCzbl{TTuB@keMcYpSGMbc-!vjNRq}PcgL8CRLpnmTLd-lMtPlUESF9}Q2yZM8 zdFj^`lCkVLw2ftlWDKWl9Q*yh{^P9@UMS+TSH5B*%zwoueKqP^xbqo-+~0-!4@s`u zk?+yqqU(oZ^!gQV1_ikohQCF;f|A-{iS46des~iP8d61b5doVZgQSoes4IE5C8DiQTnI6=x-7xKYd4&zWQxq`gpr2m%i!P z(`&FMtKE_$C#Hp#r)$8TAKnvZ4hi{6%Qelf-a=7$X_C%w1 z;pjhIB7eu5scQJIc-15=Omu0`M`O=V-?OCeWGaQy#~V_){GN?HKfi}OnuHIF;~f6d z@J>g{4{!GQLlRx9@Yce}pYH3WnEddL{0-mS+73tmrMerDQ@d2ReaP!vviL96U5A_> z?+3)IcogqCm^9v{*wbsUCeuD5AF}u_)%^lFKfKQfPq$a$@%C3PyvMPp*I-Q!C%jR4 z<(%qXu)kg8iN9k$;Z-8uHc$WLPv$K%b?@3{NU~Wfe#@k%i$zPxw*@KT)XwNn3TnJfN^Nu}zp{(gih`j_xmPk6H~Sx%y!ww^96SxN!S zCUf$?H*z_4g)<}<8UlaC$r`yYO;jQe!6pB%82@?;ZX(VqH(h@!)KA2x^5w|-LHJa@ z0a?E(pUO*-^~>|AjF|f?4lOAs61(p5iofDeliS0LX~AnR8Y(m!4Q zK!N=00{NK&`S}9*?E?AZ0{QC#SwDP`{we6K)$a)exyKtqCkGRK>mAy{8@oKOdXH^RDK&5$YToR@dfgf0=d3G zo>?Gw6vzt-PZY?1DUjbQkc;w$pirL*SqTMFbS3glM`vW4R?3bp`cmDeiiG(*FSDXh2PwD1Z+oHCXyjLUR17PuCpB1lB zt@zf6pMPx+Zw9sJJ;$=*vm-GL+Ek01Duw$R!*O=>2d#)}5Xj#2B@$$h$e=dG8pC>X=?W2qExVm2#I0 z#E&bj^g^r>#$)z+jwwDw;%CVgcJ;6gxv-_PZ=gq?Y*?smT!pM#65`cG{qe=H5I4v1 zt=gK(drN1<`}@HM4{1=(=kZ~0pS}mz_Rhh69{1~wS;B+fWMOZ(jWdz(DgcL3A(iof zHQTP&Wpvca6DsW7@v1-wh7Hk$*?7(rWL;A3_gv<8Wn1~(+r{}$g0FZ=HSeLB)JceiT0d0x0dgcH3}Z%8?{M$eU( zt@IdWxR6kYo7XydJxt$m@G}?{uqEM5_Y zQkpjUc0NQAvmUmSbwKWmI(li9@x{gHK^xSuZia}0nCD+F2(ElV7cYF$l%gLcJVX(8 zZ$rA`g9`Bgy`^t)FO9f|m*R6zh6LNue^xdhb!RSSosQ07LD;$+Ro_cg@Lod|Ki<&E4q)sVUs``~%zu-xE z&;&!g3;8MS@YRR@Zg-5%syYoa!H*RaLUU)fcW!SIpITqJ{iJXA`sueAYU-G~AEB}l zR$2~eovI-l@sd!fIgsw^qDDriw8F>7#10>9>suT)^Lygy4}+oJW6T8^?s6O+2}~z> zDx-PLo$a*Zh19K_$WJAQT!v0Fn{Ck>PT4v7?nUmSB(Y=H&E*`UGd>E&i}XAK>9BJ- z^4lWW@S0S-mwLZ!rL4!-AnBSrnkjds!!0)JH#S#ti}i42e|o?*1|A+oUQtjAECv#* z0;MvCqh?+xTPX#xg9#5&hG6I~^UE$~H{OHx@Dd13Sr6^5+zR78P-2r_>R!8gyx=3D zs|=lJs7oP+LA?_|hZuuyR;Qbek1->i>gIx#PYrMsot@XCE_+cp*3QKnMx=i?hVd9D zH8lJhaSVlqnmY9B!z8@vpwM)_7G5CD1z8zCOA-?n22_0OZIbj$V%lOE!sg{1kqy7| zMGiieiCgkTW>~Zpdo6ezvNdNIBL3@OQ3*d^BAI#IiQ=|=l1lE|@d+-w|H|&axBK5D zbNzx8E?tu zngc#$B!dQp3E=3NXFk2lJWPB zh`*2Jj=v4rmshykm=z-N*Ffc~L7c*8#^hefFXKtBqP)celjLZ-pDl9T6>^`-uLnpb zpTCe?&F|BQHQaZxmi)7rDXL>%TCC?As&L3O>XX>O_v%G9%ny^EbRH*ie}5=<(tD*y z_>Y(`iy7)KENbKjfVg%@6MLp2`P~v0anQEAWbWS-k@VKdoqW!++#%xsaJkRmGkkVG zPBQoPERpnHFU}->=}E^rYesG+67Luh-9Aw9R!QbQH%sPoehVa%k7FhCCI0VAKA3!o zgm;_u4@=Jhz=z_YtOKdDMc?5p0m|QoBH`>{xl|;7O(OX_6e@pnEiV+w-%)ZWf5+SX zbjjrJLXrGEBzMAnP9z_%%bk3z%>uS4%MYl)A+xz(lAFnwIEQ*6worazE8)W-ZTtp; z3b;@?;#y*t684$fpn+WSFrKaBbzlD-9UCw-?% zru;7wx$auK-zIri`di7A_jBTW`USZY&Ob%`ud+@IXCtU|mP;mo2aBD2%1|W#-;V&UmPXkzeFUy zouJ~YlgxG7t{?r~EF!-mQVySr_%GTZ`X33U-^gr``?vW}x#f36;`vhKy5St>D4wmL zu6s&E|C)&Y1M64YDC(=A@>wSte_0WK^W{!B-<8b$I>qu8k_q<_^K%jZ!#FmQ|MkT# z`a`ihNhUz~KU{JTpP;mSx=1-+V%}``Z(va`?UOGz7adOdL0#V{xsQ5exnJb^qvTHd zPms)gI!z=WSIM39ESJpn>u`9hbZ!piK2{{1^c2U z?`e68XStJ~Ns@_YiR5Fs zf0pl(d>r#{%U?@Ao;_0L3i4kn5`Lvf`kE}aTYoxKc;{QbQSu4=hLz>#%{8}=;cRa< zLtQslveG5_M1ICn@=27debVhUoeM#JBG84Sq_z+10{3aBFU$b9`SV2VfSB)#Q(Ip>W=ZckxZ*%X9&ZU19zt4IJ>bg@!;=e=g=kbAc zyPq@$`F#3GD1T2&{sH5qWc+_2`2v3AmpW5)A^oKIL+S^V{}UxI;Wy9CpU9o-erx@R zozYj(PN3@579#20QSPL7KglDRpIOdICfx5!zKH%>yqNJx?u7f4^&9Sj`z6eq#Y^e0 zq4eb<*LPaJOnUCm)pq}bsCDFD#cYynKMr2byi?>JFM#s*1Iyd*f%_Gd7nFO0NV;cR?lmtqe+gAy&shG( z@>YA|er1yE0CoL%b3pF+KhyG0%zMqpMB;rH7X65M)m~9PN2H&)L2OErpNo{!ub}e( zq-3sp%lgkm%4g`_QGYg6IbR`i-Hmqto87;#`>Ojy|9e9DpDg0P!S2V4RkRnmbN|j3 z@pql|zn4r|zas8Wxy$_k)|;09A$elLfRCQ^t|sDta}odBLiyj(^6rxHUoKunyy6kW z3w8Z(M9TMbxs$GMB$KXT`$5vR8C3b~Dx%*@?&v32-(-D<^*z=PT7QQ1S4bwFn=OXd^LGHx!w)O8@|B3Y@$4C8^BG+#Vb^T5v*OyyA%lfSKZPqWb{v7LnVErZ5 z-(mfu)<16j)7HOheKLXg$j7#3B~*H9C6k^;k@R%Ro%~!Y(oTLN_s#gNRmt>S_edt3 z$0T$8A0>1Bb0XJ&D0i+O!9A6JEhzo^BKk3MM_+3FWb3P~Z?%50_20Apcz}v&W9vsyXG6YW$hW9`%U$`lev0)q*0)*z1MwQhWx12TpGzh^OC^(@Ux|eG zqTC5@R4L>>Z2*`Wc?Y|Ut|3} z*57aa!`44<{fE|nYW*reEW&H`(|Iqr&t-r?l`>cP` z`e&?v!TL|EA5jtGUkfV!^+nr)tiR9t zr>%e6`uDB>#QKqwWBgl+l+Sih=^G=Gz6$GSS^pjDTdhCR`g5%Rf%TVIe~0ytTK~B9 zPh0=4^+Tq__*aFBf22tKqvcNd>|_1@)|Xp8FEK|rHJ{l+|l18qF*L= z^v{Wym*kHAbrJnna!0@RflKRdbN$9OQNIP0ezeH-6XcG5 zn)NfRKh*j`>rb)%EbGs={wC`mwEhw6AG7{->p!>t8|#PF#`rgbihoy;^zSKm(l_4v zM(aDQ@3DT+`ZKJ*()u4;f0Omgtbfk>m#lx?`md~CyDrARAyoXEiImSCawmONBI)D% z20`CseV6seSbviBXIOuY_4io+fc49)f5G|>t^bGhUs=C?eT;txk@&|#rEi=_`uJ>f zNMEz{?bdf%f4ucSwElAIud)6<>z}m#8S7uL{uAp*OpEca1r`7LBJq!rJLOYq{S@nK ztZ%b^vGqq;e}eUwT7R4MKePT9)<0$a+t$Bt{U_FsY>4r1DN;V$L8WhuNcwoKGNf;o z^;zrNtY2dNIoAKc`b(_8!}>?9f86?~t$){goh2#$RiWY^DH8u^xl=y-Sbu=^eC;gg z54HYq>la$T#QO8Czux*=tiRLx$E<(Z`ZukA*ZN_NG5(E3(ziKO`nC~C-+1efvHm3M z&#?X)>+iAte(N8${(0*^wEiE~e`Wpptc{ib9Yo^a87lrgMB=ZpzS;V@)^}Ndg7rVN z{&MTDvHm{mpS1oN>tC?`6YEEi2F1S?RQ&6U#6L#vm{Jk_6uG0X5z)8F9dn=fUCwdk zzANh(k$!!R8Mt4={=JC470UfQ%RiEg|932ZVR<-Xf!xQ6BUpYz#dDz8#krc?3Fjfn zgn!^HWYWV2HiP>Nk?Xq6BcQH7&+-+PZ?U{w^7ZUj9~8scK;-(Zpsw3PGG$dEj$}Nr z`wzt<82{x?dX`&$Lo(_AyIFj2)L$$T?vJ6uy-OrNpNdB??n+NMyB!kcy`jSSt>q^z zzbxYK%0nUfzD*=u_d$jGq*%pxXZ@QZ@&4WV;_pQNYeV_pPQ?Ehxf9+55&u=z&yq~| zb1g3s@qe7$@&A1h|Cd{Ti)5w8@*hR~KPPwmzb)eb6YGa%qyKfG(zAnz|DENI{{uw) zPqqGF$%Nlw`6vaixq<5O-gGJIiUnIQ?r6;{VmP~keh+MZv3ncyu5r5O5{9PcD&P(M^I-vpF!ruZa{Lv!ePq2QP^)swL)cQf|PqF?i>(96TChH%x z{t@dRv;KAKKezrH>xWVI75`>1+%Hl0OYXW~);C$-VSSI?j}k|4o^1Wal4*z6TYf+! zyk&AHyx)q%_p0@uTmOyq!#bjVGZ@k%a{XR%S9(OQZ<0IZ$#2*NeYf=k)}L+iJwG3#Hp{!Q!OwSHJvynZXF z`ZCt?-XiJWU+%mRZHG3#Hqeyzh}cw30vhaI89-Cr{4J6JOD zH%lh|xgzl&C3pOtWBmozUuylG*1s+;;r{l)8wnRG++T`>^GA_*Uy`2iJ{L9j=#T!k zGV7t{sq-zLDsufr;z-UHr04p3?Ea`oxKG>tb;-p0tpWT|{&i5YzK&9K6YmULo-cU} z?b7mvBJo@&65bus6VF%HuR9pS+0&dX;(xkGy5>On@3a0w$vd&mS`e>W2P(d)mYc-Q zlcZO?ne#;HZ()9B`E8MO=uaGOjxskgOU&)fUCh1BRm5S;r^HQ?WNmYOb7QfH{>|J{ zT$ORt`rXZa%~G?{tTU&ZOb0?dbSr^Wzd&wj;K}A0=Edf%=AGtJ^LOT7%)gqSo5P31 za5pr!HT6!s@>_0Z%sJ-a=F#R^rrvGWbvK#6Fn??Q*?iml%v_Z+)O8z}qs?(?gc_VXcbF6uQIn|tH&NTH3Lj}6UTOub7i_W|=H^L+Cv z^EPv-`JOq12BYg&HAkB3nj4#2n4`^|%yH%vv&PJrv&^j7X3jVD?yursXf832Gfy$k zGS4^lPOz@K()_V`lX<&&kNJSP%>1qSr1^~bg88cXw)wvKiTQ=8z9W>MInrF$+}Pa0 z9BuAs?rQF3PB6>NDznbi&zdW~gH63#EP1ZkW%iqk&7;f{%+t(sOub{Qa4t2kGOssp zG4C`VHh*J2VgAW{!+gj5$o$Ow+8jzpuXtB8N0}R#o0?mh+nZy}apu0}M02uPZR#Cm z#WU0Vj@fDsm`9jLn0Gx%~#B~%=gTX%`eQN)na*$Fh`ji znwy)W&7I8M&3#S1|DpR*Y1Wz3%|p#rbH3SUE;f%gPcqLm&o?hI_5O(ByTQE8yxV-h z{FV8b`IPw=^A+=L^8@oA=GW%1)nj~XnCqIGm|L3Ln>(9(niI@&bE>KLR+Nuf=4^AW z*=-J*N1Df(r<&)O7n+xw*P1t(cbNB@51EgePnge`FPg8L@0fo#|7i|kBC320H`g*Z zFgG)|F?Td~Gxsqknp4bLv&lTfY%%rTjp9ArTx1?)o@kz7o@ZWSUT@xQ{@(nv`H8tU zYXQZxwYiIVfVtQ_*}TBK*1Xev*!-jUius|LtQq53%iP=y@97Z#c*|4GL(L=2lg;zZ ztIgZZN6n|rS4_RPqx|VJTjE;g=H?jl0CSpolKFk}3iB58e)BQ&dGl}PKg|&=fE4dW z=62?uW`)^kwwTA5XPcLsH=9e%KbWtXpPIv2I4RyuOufG&d4IFsoMR4{Cz=FcaKQ+HJi@p`Z8*Z*?u4isy zmYCa_yP5l&Q_X|S4s(%tlKBJk8uJeGm*yYLm(35%Z_G6}jp^OY+{xU}JkXqF&NCO9 zCz|J*SDUw+51CJz%gqnWVQg@z{MR$Xdt}HHE!UWbnDfmeOubj8>n}8KFmEv*H6J&h zHveM2Y`$r}YyRE*-2BEI#@?XfTismS+|b<2+}hm1+}Yg2+|MjEE6rxJ$GpJ2#{9Xt z%zV;($^6v((k$8{rgylxrn#QEiCJQ9Ywl$3X6|k7ZPs}gOAtkXKS2ahP>zW&z zTbQHG9nD?Mz03(_nOSAlnN8-wX0tih>@xe!#pY4w3Fc|$IpziCrRG)U_2w<+o#wsf zgXSaVW9A>t=ggPPH_Ug2jxa}=8=9M&qs^Vn-OYW?QnS+3`;=;*)6GN8 zR&&1DXD&96Hcv9oG|x9LF|RUjFmE&OHXks5Wja&xNLV9qjUn{&->bI?4}JkC7TJjcAyyxhFjyve-7yw`ll zeAIlxe8zmyeBFG<{JZ&2Q{S#oISx11GB+?cGq*AI{;T}&W`_4*ktbT7V%C~X<{@T_ zd6;>)xyU@qJkdPEJkPw?)cdwd$Mxo|=3VCf<}&kl<{!;Jn=hMhneUsQnqQeiw~6ts zZmwf)Y?heYnPbg8%<*QKd7wGXoN0#lf5}(7=R7n+xu z*O<4N515ace=*-Shiww+}WI9PBmwl3(OgZY5@g!#HTbcdL}wZtMm zi(zgkvWDBk94}Ij%dM|8tF51Hwu$)bwLEC~Xv=3n-1HK4JH#MdEqR{F~iB5VeNeG3tkz8;YcJw7H{5zV{T_i<)4$ zN+jGGbDGF?hgpBT#j5nMgcOSbo~_a?9_VAKU#K%WLiw<6T$e`pqqG zZF#Ka-7W8Lxy*7#q#O>hJlFceMe;Xjo@Sn9UTI!q-YXK$!y@T;T%Oe^(^jV@1+^qIs&w^*^!xPRkFQkJ|l@mY=o!isd&ge`xt@bL1{D-0el; z9Vf2EKCR^gE!SB-*z#=4;X4QTKiu*X>(8}(xmfJ)9}xa+cE8_z*8H3KnK^9Nn4Wda zEzF(Feay*b#++>~GEXqiH7_@BH19WmYd&YbY3fIGR4yaUP0a1gab~GmE8fcYaV#g? zL)}OHi9^ld<{IWGlWo`FkL|fYwqpWIOr}pkX4nj*8wjM>0>_zqo8!%iX1Q5uR-5%^ zqdC(&#GGxmn)A#~v)3Fj7nw(zN1Ml+C!436XPf7l7n+xtSD06u*O@n(x0-jDcbmU3 zmzocozcznoK4Cs(K5IU2E;nB@-!k7ZKQKQwKQq5HlOgf`3^l`ZSk#9#ERQnRGdD6f zHA_r>awpz@b0>2bbDX)iIo_OThUdG8x6*R8soy+N{cJR6nunOP%~o@s*=hEg1Lh+0 zNb_j(c=KfQbn|TUJo7^H67vf4YV$htM)Owl4)bpF7v@s)Ve{AK@60F6r_5)~=gsBj zYvx<#JLU)G$L43|muA`z45f@!&cn?$%u(ig=0@hGW{J6txxKlQxr-T|pToYlV$L>O&3R_0*=r7%i_9a&zR? zTg^MnyUkyiOU;MPUz@)(pD>>?pEaL1mz%GdZ<+6yADADTpP65p31eXB|IOj%8s;c- zJu^I~$hDhVE-|+;w>Nh(cM(T0ew%xn)BZK|m&j>h{>R)!IF}ZK>Onz`BZSx1j7Ey4|&IkKIEJ-9_tK4r|T+e)rv% znb>;v=Dhd&fB*mY>%IFX`x>`2NhyWXq%cID6XMV;TeCvJA~8qIc1#tvWqzGLZ)GZL zGRYbMew?L$znd8g#a=-792FJHkp$am+qY|6Sl zTRc3nXThQLNJBbi%Hfer@zC$m7q8vxv-72!Oqo8{kST_2-$&Ud6V?lJyM(g0Xy0TG zeWV-?<&sy3bd#m*n@l=j@U+UO<(=ng2 zFQvU_!rljaZ>FgfGTM8GM@qh$=E&?V9jiH%+c*wg=EAw}d^SD~krJH|$e3d6ZM$xttRIJ%rkM-bcJH|eB52>7=~{DQ@4Uq)(&JMz?cRN- za~mboygqhDkLQ=#gF8;J1U*k}$G-FY^GhOn|3>cJnA`m0$nk#6TjtHtOI4#E%$Gn{ z?m+3)PoiUOUU@cWt{;8RFq*7Pdu889gVAL6ooz7Y55Jw7nf`l!=Ioc+cbqts9+P7) zW4RR_m&5R(6wlRg2m8c0+c3r99ntvf-+x%FLTdjO=)_D1A=u zotZnl|HaS77r&E__vgp=-zvr8cgD`^j^|#zl0&A}@9OMUYxrczf#)E|HChwdN;7Sz zvaM#O?F6BMl+9)In0C2nE~`bz z=~sXdq67i0e8AEG;xqb{-sUpD$}yuz7?xA+%oPPp8JLNV_zFGQ)%C^9H!JV$Lf>b5 zWE-G7ABNJ3fL!Nw^5%W#0hq;AT&1HGJdB~ybV6@81WPMp%@pjK$s{YH0L_G?b zPhgm;6(nHiR|F)N7gPgwLEc}8YUKv&ntU4{6uG)ZuQJQx3wykk&?mYszwXLwE~87Pl#3(GpmiW>F-T#7GzMEnrwvA^?@j zSRG=#C+LzJRzZvAQuz`MzY>R}$eiN(GwL6szSx{%zCb%!JO&f%dfbi_Ela|{eHY|r zsk|HDsuu3Ip)zMlZa7!9>CRC*TeFt?9e9}Kn)SMm(YQjhrS1^5b2RI7$H~ssY=!%W zWanwN()~;NR%+JoF2zup^EF%Jeul;m~WFmhGbxewB~Mlyk` zdWCx-LtUYJwA%d|wM#VH;C9n@sk|THs$TD|W*K$zdc|&VOZwK!EsAY&KSk};@+T_t zMz@dbO8HNU-Q>QOq1MSql<^k#MQS(6Zz=W;_c+;R&2D!Wvy9D}y~jO`?9H0J*X<*_ zMJ`mnUGATfZP7LNx=%7xt2_g#t2!#Cu4k1mTVI3NYaZh;c;?aL$M%Q_&oUakY7dC% zsipgfJ;RomVm<)dDdx+_<>jhicc!T~8l+qkO8UMdy%N$7z)YvD>j~V7xAI<+>=#Rm zA3BOup82>HKWt|Zo~5uZ&e)vkd5<1{VRM$}+o+{DYja-DCF&lrxl&Jvx}44VJhxK! z6`QN@T%hi&HdpCsVunLD=l9%8%dc^vyQ*tEJQo!oVfn7=MWXa_5b`ql-vIGG%AC<7 zWF@&7sbnWe%4SBBLe5tdh$?E!N{~?cnF9U41c`4KNEuU;LTQ9Iv_&Q!a2N~O&j3py zQ3tW|JwooJ`(_%63i%(1A&2Aum^Tr-7Z`I~chmIJeJtzh1AUIQGal`L@;*vr)ftm4?Z4sTk(qBb$oI#p0L3)&3b?0X?p6}5w_VnsVi zu%-hb(7fy>OH#|&Bc?O8TE!eYNB9Kj8V*>|VeSkmYt|q{(W5padQq}V97QB4|9AQ{ z+|}tDQW*${+Eik&HX7-u?dj~SjjUL`a#=JIOARgSiKS{+1eOPu*G6KU(NtI1w$w~* zMNfnGkO6(WHQnpwuPu!b=&x@ zkS8Pc){?`nbrp~Ax^83L(&gW4-nQc?sI|+VZtmLgs6(|+P&=$yQDe8Y-Eaqt-3@gu zDP!7GVPhz1?XJD{x>{?F@zB1H78yg^lN+qZRt;VEtWjbeGX@*#dyJt5!_#oxy6fs% zjL1`l@5{yy_BFippKI@4TUUS7xW2pIxZx?Iq1$M&{P(^1J=YCoMzC9}pD|{28Sv4Pj>IU{twkk;Zkmd9a;o?K;6YuI(;w4%)ijWkAgLeD*UH|!n#jR(z#j1B1`$DcdxSC0S2 zX+@1`^B^Wl_;9gt)xQOF{3(MA<~3;&X$#sSvJRI>S%8UF4oZsF1%Rt;(ox~eBIYX5 z?ezdUOL05ysFU2;(Yuc1ZH;7@V8hd_Psgox0 ztW8@)^|C4G32nU?370smunjaq5$;stltuiOEhapt#Y9H?T;dj`K5P%3MNG`9_S@`bm3hfcW?r5kd!B9Q@Nmz=FEp7gr{OXM$B8e^G(7;{c&|p)zLj?OngMHz_ zgvvJxa;ctAPyu46$5uQpsF;M zW5*c?b=8Yt5C9*-avN6IaE%DY!b3^X8SfuRAqmzoM=TQ43t>_(pot{966_8}bCN1w zrc;kyG^aSIb`bl5+7Nlt`~=xk-Or9tXJ2Z-?kL~tD1%tx$WRFS};3UhyK3*wc?pz~rEfy$&@Pjs}t(>j0KjNCY|(SYue|sh(h{ zqhm0#I8T`W7kOsEi%{U#0@c>zUib(swZ&o{(5-30lMt*1 z+GhcLuz}_wVIeNYbDnZE&V!Z*2iiO8FS4tH4dXeDcE2bPIOL5maA?{-hX+1i z5KeP+{Bkbr#~JkF5Mr_)90R8xd@(sbAjMAn{1hz^IAjZSh4H#DpzIgp5uJGLpy}hh zE#AWsVB)n2xgQss`ccLv)xB;S=A(dj#;+T)!n{%BT@M-aqST4JyFoj(f)uYJ-V06< z1-gR;H0>go_$?%Kb7FiMd|}@27W5at2TtUD0<`195U(JfpM-9X?s4#i@m@wen5upd zo$>o?(2fsC@y}55jO{c>_X7w>*J;Jp8A9CbEHbU5{RqATIPS=alm8<_zAyuMXLZ?LhA7xT%HMfPIC@L1adHt{F7#6Um;jn5Tq&liqmv&r z=YxDOVdTLA-p`pFGA8{*|e{A=zCtzWKjt;QQPZqj&*#%&tAH1=uayfDuL8Xwk} z)A&t|FKOhrHtk0>p3?YBjsKoi`kaf`;gHS)8Ce!Dat(DXwD4^He@t^fc4 literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/doc/Makefile b/obj-i486-linux-gnu-patched/doc/Makefile new file mode 100644 index 0000000..6fa379f --- /dev/null +++ b/obj-i486-linux-gnu-patched/doc/Makefile @@ -0,0 +1,624 @@ +# Makefile.in generated by automake 1.10.1 from Makefile.am. +# doc/Makefile. Generated from Makefile.in by configure. + +# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, +# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. +# This Makefile.in is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + + + +VPATH = ../../doc +pkgdatadir = $(datadir)/mutt +pkglibdir = $(libdir)/mutt +pkgincludedir = $(includedir)/mutt +am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd +install_sh_DATA = $(install_sh) -c -m 644 +install_sh_PROGRAM = $(install_sh) -c +install_sh_SCRIPT = $(install_sh) -c +INSTALL_HEADER = $(INSTALL_DATA) +transform = $(program_transform_name) +NORMAL_INSTALL = : +PRE_INSTALL = : +POST_INSTALL = : +NORMAL_UNINSTALL = : +PRE_UNINSTALL = : +POST_UNINSTALL = : +build_triplet = i486-pc-linux-gnu +host_triplet = i486-pc-linux-gnu +noinst_PROGRAMS = makedoc$(EXEEXT) +DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in \ + $(srcdir)/instdoc.sh.in TODO +ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 +am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \ + $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \ + $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \ + $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \ + $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \ + $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \ + $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac +am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ + $(ACLOCAL_M4) +mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs +CONFIG_HEADER = $(top_builddir)/config.h +CONFIG_CLEAN_FILES = instdoc.sh +PROGRAMS = $(noinst_PROGRAMS) +makedoc_SOURCES = makedoc.c +makedoc_OBJECTS = makedoc.$(OBJEXT) +makedoc_LDADD = $(LDADD) +DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir) +depcomp = $(SHELL) $(top_srcdir)/depcomp +am__depfiles_maybe = depfiles +COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \ + $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) +CCLD = $(CC) +LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ +SOURCES = makedoc.c +DIST_SOURCES = makedoc.c +ETAGS = etags +CTAGS = ctags +DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) +ACLOCAL = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10 +ALLOCA = +AMTAR = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar +AR = ar +AUTOCONF = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf +AUTOHEADER = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader +AUTOMAKE = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10 +AWK = gawk +BUILD_INCLUDED_LIBINTL = no +CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo +CATOBJEXT = .gmo +CC = gcc +CCDEPMODE = depmode=none +CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2 +CONFIG_STATUS_DEPENDENCIES = $(top_srcdir)/VERSION +CPP = gcc -E +CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl +CYGPATH_W = echo +DATADIRNAME = share +DBX = no +DEBUGGER = /usr/bin/gdb +DEFS = -DSYSCONFDIR=\"$(sysconfdir)\" -DBINDIR=\"$(bindir)\" -DHAVE_CONFIG_H=1 +DEPDIR = .deps +DOTLOCK_GROUP = mail +DOTLOCK_PERMISSION = 2755 +DOTLOCK_TARGET = mutt_dotlock$(EXEEXT) +DSLROOT = +ECHO_C = +ECHO_N = -n +ECHO_T = +EGREP = /bin/grep -E +EXEEXT = +GDB = /usr/bin/gdb +GENCAT = gencat +GLIBC21 = yes +GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo +GMSGFMT = /usr/bin/msgfmt +GNUTLS_CFLAGS = +GNUTLS_LIBS = -lgnutls +GPGME_CFLAGS = +GPGME_CONFIG = /usr/bin/gpgme-config +GPGME_LIBS = -lgpgme -lgpg-error +GREP = /bin/grep +INSTALL = /usr/bin/install -c +INSTALL_DATA = ${INSTALL} -m 644 +INSTALL_PROGRAM = ${INSTALL} +INSTALL_SCRIPT = ${INSTALL} +INSTALL_STRIP_PROGRAM = $(install_sh) -c -s +INSTOBJEXT = .mo +INTLBISON = bison +INTLLIBS = +INTLOBJS = +INTL_LIBTOOL_SUFFIX_PREFIX = +ISPELL = no +KRB5CFGPATH = /usr/bin/krb5-config +LDFLAGS = -L/lib +LIBICONV = +LIBIMAP = -Limap -limap +LIBIMAPDEPS = $(top_srcdir)/imap/imap.h imap/libimap.a +LIBOBJS = +LIBS = -lidn +LTLIBOBJS = +MAINT = # +MAKEINFO = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo +MKDIR_P = /bin/mkdir -p +MKINSTALLDIRS = ../mkinstalldirs +MSGFMT = /usr/bin/msgfmt +MUTTLIBS = -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm +MUTT_LIB_OBJECTS = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o +MUTT_MD5 = mutt_md5 +OBJEXT = o +OPS = $(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT +OSPCAT = /usr/bin/ospcat +PACKAGE = mutt +PACKAGE_BUGREPORT = +PACKAGE_NAME = +PACKAGE_STRING = +PACKAGE_TARNAME = +PACKAGE_VERSION = +PATH_SEPARATOR = : +PGPAUX_TARGET = pgpring$(EXEEXT) pgpewrap$(EXEEXT) +PKG_CONFIG = /usr/bin/pkg-config +POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po +POSUB = po +RANLIB = ranlib +SDB = no +SENDMAIL = /usr/sbin/sendmail +SET_MAKE = +SHELL = /bin/sh +SMIMEAUX_TARGET = smime_keys +STRIP = +U = +USE_INCLUDED_LIBINTL = no +USE_NLS = yes +VERSION = 1.5.19 +XGETTEXT = /usr/bin/xgettext +abs_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/doc +abs_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/../doc +abs_top_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched +abs_top_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/.. +ac_ct_CC = gcc +am__include = include +am__leading_dot = . +am__quote = +am__tar = ${AMTAR} chof - "$$tardir" +am__untar = ${AMTAR} xf - +bindir = ${exec_prefix}/bin +build = i486-pc-linux-gnu +build_alias = i486-linux-gnu +build_cpu = i486 +build_os = linux-gnu +build_vendor = pc +builddir = . +datadir = ${datarootdir} +datarootdir = ${prefix}/share +docdir = /usr/share/doc +dvidir = ${docdir} +exec_prefix = ${prefix} +host = i486-pc-linux-gnu +host_alias = +host_cpu = i486 +host_os = linux-gnu +host_vendor = pc +htmldir = ${docdir} +includedir = ${prefix}/include +infodir = ${datarootdir}/info +install_sh = $(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh +libdir = ${exec_prefix}/lib +libexecdir = ${exec_prefix}/libexec +localedir = ${datarootdir}/locale +localstatedir = ${prefix}/var +mandir = /usr/share/man +mkdir_p = /bin/mkdir -p +oldincludedir = /usr/include +pdfdir = ${docdir} +prefix = /usr +program_transform_name = s,x,x, +psdir = ${docdir} +sbindir = ${exec_prefix}/sbin +sharedstatedir = ${prefix}/com +srcdir = ../../doc +sysconfdir = /etc +target_alias = +top_build_prefix = ../ +top_builddir = .. +top_srcdir = ../.. +subdir = doc +AM_CPPFLAGS = -I. -I.. -I$(includedir) -I$(top_srcdir) +MAKEDOC_CPP = $(CPP) $(AM_CPPFLAGS) $(DEFS) $(CPPFLAGS) -D_MAKEDOC -C +EXTRA_DIST = dotlock.man \ + smime_keys.man \ + muttbug.man \ + mutt.man \ + PGP-Notes.txt \ + applying-patches.txt \ + devel-notes.txt \ + gen-map-doc \ + muttrc.man.head \ + muttrc.man.tail \ + mbox.man \ + mmdf.man \ + manual.xml.head \ + manual.xml.tail \ + instdoc.sh.in \ + patch-notes.txt \ + smime-notes.txt \ + Muttrc Muttrc.head stamp-doc-rc \ + makedoc.c makedoc-defs.h \ + mutt.css mutt.xsl html.xsl chunk.xsl $(BUILT_DISTFILES) + +HTML_DOCFILES = manual.html index.html intro.html gettingstarted.html \ + configuration.html mimesupport.html advancedusage.html \ + optionalfeatures.html tuning.html reference.html miscellany.html + +BUILT_DISTFILES = stamp-doc-xml stamp-doc-chunked manual.txt $(HTML_DOCFILES) +srcdir_DOCFILES = PGP-Notes.txt applying-patches.txt \ + devel-notes.txt patch-notes.txt smime-notes.txt + +topsrcdir_DOCFILES = COPYRIGHT GPL INSTALL ChangeLog \ + README NEWS TODO README.SECURITY README.SSL + +DISTCLEANFILES = manual.txt manual.html manual.xml manual.pdf html \ + instdoc Muttrc + +EDIT = sed -e 's,@sysconfdir\@,$(sysconfdir),g' \ + -e 's,@bindir\@,$(bindir),g' \ + -e 's,@docdir\@,$(docdir),g' + +all: all-am + +.SUFFIXES: +.SUFFIXES: .c .o .obj +$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am $(am__configure_deps) + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \ + && exit 0; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu doc/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu doc/Makefile +.PRECIOUS: Makefile +Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status + @case '$?' in \ + *config.status*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \ + *) \ + echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \ + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \ + esac; + +$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh + +$(top_srcdir)/configure: # $(am__configure_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(ACLOCAL_M4): # $(am__aclocal_m4_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +instdoc.sh: $(top_builddir)/config.status $(srcdir)/instdoc.sh.in + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ + +clean-noinstPROGRAMS: + -test -z "$(noinst_PROGRAMS)" || rm -f $(noinst_PROGRAMS) +makedoc$(EXEEXT): $(makedoc_OBJECTS) $(makedoc_DEPENDENCIES) + @rm -f makedoc$(EXEEXT) + $(LINK) $(makedoc_OBJECTS) $(makedoc_LDADD) $(LIBS) + +mostlyclean-compile: + -rm -f *.$(OBJEXT) + +distclean-compile: + -rm -f *.tab.c + +#include ./$(DEPDIR)/makedoc.Po + +.c.o: +# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $< +# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po +# source='$<' object='$@' libtool=no +# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) + $(COMPILE) -c $< + +.c.obj: +# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ `$(CYGPATH_W) '$<'` +# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po +# source='$<' object='$@' libtool=no +# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) + $(COMPILE) -c `$(CYGPATH_W) '$<'` + +ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES) + list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | \ + $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \ + END { if (nonempty) { for (i in files) print i; }; }'`; \ + mkid -fID $$unique +tags: TAGS + +TAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \ + $(TAGS_FILES) $(LISP) + tags=; \ + here=`pwd`; \ + list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | \ + $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ + END { if (nonempty) { for (i in files) print i; }; }'`; \ + if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \ + test -n "$$unique" || unique=$$empty_fix; \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + $$tags $$unique; \ + fi +ctags: CTAGS +CTAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \ + $(TAGS_FILES) $(LISP) + tags=; \ + list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | \ + $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ + END { if (nonempty) { for (i in files) print i; }; }'`; \ + test -z "$(CTAGS_ARGS)$$tags$$unique" \ + || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \ + $$tags $$unique + +GTAGS: + here=`$(am__cd) $(top_builddir) && pwd` \ + && cd $(top_srcdir) \ + && gtags -i $(GTAGS_ARGS) $$here + +distclean-tags: + -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags + +distdir: $(DISTFILES) + @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + list='$(DISTFILES)'; \ + dist_files=`for file in $$list; do echo $$file; done | \ + sed -e "s|^$$srcdirstrip/||;t" \ + -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \ + case $$dist_files in \ + */*) $(MKDIR_P) `echo "$$dist_files" | \ + sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \ + sort -u` ;; \ + esac; \ + for file in $$dist_files; do \ + if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ + if test -d $$d/$$file; then \ + dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ + cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \ + fi; \ + cp -pR $$d/$$file $(distdir)$$dir || exit 1; \ + else \ + test -f $(distdir)/$$file \ + || cp -p $$d/$$file $(distdir)/$$file \ + || exit 1; \ + fi; \ + done +check-am: all-am +check: check-am +all-am: Makefile $(PROGRAMS) +installdirs: +install: install-am +install-exec: install-exec-am +install-data: install-data-am +uninstall: uninstall-am + +install-am: all-am + @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am + +installcheck: installcheck-am +install-strip: + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + `test -z '$(STRIP)' || \ + echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install +mostlyclean-generic: + +clean-generic: + +distclean-generic: + -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test -z "$(DISTCLEANFILES)" || rm -f $(DISTCLEANFILES) + +maintainer-clean-generic: + @echo "This command is intended for maintainers to use" + @echo "it deletes files that may require special tools to rebuild." +clean: clean-am + +clean-am: clean-generic clean-local clean-noinstPROGRAMS \ + mostlyclean-am + +distclean: distclean-am + -rm -rf ./$(DEPDIR) + -rm -f Makefile +distclean-am: clean-am distclean-compile distclean-generic \ + distclean-tags + +dvi: dvi-am + +dvi-am: + +html: html-am + +info: info-am + +info-am: + +install-data-am: install-data-local + +install-dvi: install-dvi-am + +install-exec-am: + +install-html: install-html-am + +install-info: install-info-am + +install-man: + +install-pdf: install-pdf-am + +install-ps: install-ps-am + +installcheck-am: + +maintainer-clean: maintainer-clean-am + -rm -rf ./$(DEPDIR) + -rm -f Makefile +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-am + +mostlyclean-am: mostlyclean-compile mostlyclean-generic + +pdf: pdf-am + +pdf-am: + +ps: ps-am + +ps-am: + +uninstall-am: uninstall-local + +.MAKE: install-am install-strip + +.PHONY: CTAGS GTAGS all all-am check check-am clean clean-generic \ + clean-local clean-noinstPROGRAMS ctags distclean \ + distclean-compile distclean-generic distclean-tags distdir dvi \ + dvi-am html html-am info info-am install install-am \ + install-data install-data-am install-data-local install-dvi \ + install-dvi-am install-exec install-exec-am install-html \ + install-html-am install-info install-info-am install-man \ + install-pdf install-pdf-am install-ps install-ps-am \ + install-strip installcheck installcheck-am installdirs \ + maintainer-clean maintainer-clean-generic mostlyclean \ + mostlyclean-compile mostlyclean-generic pdf pdf-am ps ps-am \ + tags uninstall uninstall-am uninstall-local + + +all: makedoc-all + +makedoc-all: mutt.1 smime_keys.1 muttrc.man manual.html stamp-doc-rc stamp-doc-chunked manual.txt + +install-data-local: makedoc-all instdoc + $(top_srcdir)/mkinstalldirs $(DESTDIR)$(mandir)/man1 + $(top_srcdir)/mkinstalldirs $(DESTDIR)$(mandir)/man5 + $(top_srcdir)/mkinstalldirs $(DESTDIR)$(sysconfdir) + ./instdoc mutt.1 $(DESTDIR)$(mandir)/man1/mutt.1 + ./instdoc smime_keys.1 $(DESTDIR)$(mandir)/man1/smime_keys.1 + ./instdoc $(srcdir)/muttbug.man $(DESTDIR)$(mandir)/man1/flea.1 + ./instdoc $(srcdir)/muttbug.man $(DESTDIR)$(mandir)/man1/muttbug.1 + test xmutt_dotlock$(EXEEXT) = x || ./instdoc $(srcdir)/dotlock.man \ + $(DESTDIR)$(mandir)/man1/mutt_dotlock.1 + ./instdoc muttrc.man $(DESTDIR)$(mandir)/man5/muttrc.5 + ./instdoc $(srcdir)/mbox.man $(DESTDIR)$(mandir)/man5/mbox.5 + ./instdoc $(srcdir)/mmdf.man $(DESTDIR)$(mandir)/man5/mmdf.5 + $(top_srcdir)/mkinstalldirs $(DESTDIR)$(docdir) + for f in $(topsrcdir_DOCFILES) ; do \ + $(INSTALL) -m 644 $(top_srcdir)/$$f $(DESTDIR)$(docdir) ; \ + done + for f in $(srcdir_DOCFILES) ; do \ + $(INSTALL) -m 644 $(srcdir)/$$f $(DESTDIR)$(docdir) ; \ + done + -$(INSTALL) -m 644 manual.txt $(DESTDIR)$(docdir) + -for f in $(HTML_DOCFILES) ; do \ + $(INSTALL) -m 644 $$f $(DESTDIR)$(docdir) ; \ + done + $(INSTALL) -m 644 Muttrc $(DESTDIR)$(sysconfdir)/Muttrc.dist + -if [ -f $(DESTDIR)$(pkgdatadir)/Muttrc ] ; then \ + mv $(DESTDIR)$(pkgdatadir)/Muttrc* $(DESTDIR)$(sysconfdir) ; \ + elif [ -f $(DESTDIR)$(pkgdatadir)/../Muttrc ] ; then \ + mv $(DESTDIR)$(pkgdatadir)/../Muttrc* $(DESTDIR)$(sysconfdir) ; \ + elif [ ! -f $(DESTDIR)$(sysconfdir)/Muttrc ] ; then \ + $(INSTALL) -m 644 Muttrc $(DESTDIR)$(sysconfdir) ; \ + fi + +uninstall-local: + for f in mutt.1 mutt_dotlock.1 flea.1 muttbug.1 smime_keys.1; do \ + rm -f $(DESTDIR)$(mandir)/man1/$$f ; \ + done + for f in muttrc.5 mbox.5 mmdf.5 ; do \ + rm -f $(DESTDIR)$(mandir)/man5/$$f ; \ + done + for f in $(srcdir_DOCFILES) $(topsrcdir_DOCFILES) $(HTML_DOCFILES) ; \ + do \ + rm -f $(DESTDIR)$(docdir)/$$f ; \ + done + -rm -f $(DESTDIR)$(docdir)/manual.txt + for i in Muttrc ; do \ + if cmp -s $(DESTDIR)$(sysconfdir)/$$i.dist $(DESTDIR)$(sysconfdir)/$$i ; then \ + rm $(DESTDIR)$(sysconfdir)/$$i ; \ + fi ; \ + rm $(DESTDIR)$(sysconfdir)/$${i}.dist ; \ + done + +check: +manual.txt: manual.html + links.main -dump $< > $@ || links -dump $< > $@ || \ + LC_ALL=C lynx -dump -nolist -with_backspaces manual.html > $@ || \ + LC_ALL=C w3m -dump manual.html > $@ || \ + LC_ALL=C elinks -dump -no-numbering -no-references manual.html | sed -e 's,\\001, ,g' > $@ + +Muttrc: stamp-doc-rc + +stamp-doc-rc: $(top_srcdir)/init.h makedoc$(EXEEXT) $(srcdir)/Muttrc.head + -rm -f Muttrc stamp-doc-rc + sed -e 's,[@]docdir[@],$(docdir),' $(srcdir)/Muttrc.head > Muttrc + $(CPP) $(AM_CPPFLAGS) $(DEFS) $(CPPFLAGS) -D_MAKEDOC -C \ + $(top_srcdir)/init.h | ./makedoc$(EXEEXT) -c >> Muttrc + touch stamp-doc-rc + +manual.html: $(srcdir)/html.xsl $(srcdir)/mutt.xsl stamp-doc-xml $(srcdir)/mutt.css + xsltproc --nonet -o $@ $(srcdir)/html.xsl manual.xml + +stamp-doc-chunked: $(srcdir)/chunk.xsl $(srcdir)/mutt.xsl stamp-doc-xml $(srcdir)/mutt.css + xsltproc --nonet $(srcdir)/chunk.xsl manual.xml + touch stamp-doc-chunked + +$(HTML_DOCFILES): stamp-doc-chunked + +manual.pdf: manual.tex + -if test -f manual.tex; then pdfjadetex manual.tex; fi + +manual.tex: stamp-doc-xml + -if test -n "$(DSLROOT)"; then \ + openjade -t tex -D $(DSLROOT) -d print/docbook.dsl dtds/decls/xml.dcl manual.xml; \ + fi + +validate: stamp-doc-xml + xmllint --noout --noblanks --postvalid manual.xml + +spellcheck: + -aspell -l en --mode sgml -c manual.xml.head && \ + -aspell -l en --mode nroff -c muttrc.man.head + +clean-local: + rm -f *~ *.html *.orig *.rej stamp-doc-* *.ps mutt.1 smime_keys.1 muttrc.man + rm -f *.aux *.log *.tex *.out + +instdoc: instdoc.sh + cat instdoc.sh > instdoc + chmod a+x instdoc + +update-doc: stamp-doc-xml stamp-doc-chunked stamp-doc-rc manual.txt manual.html + +muttrc.man: makedoc$(EXEEXT) $(top_srcdir)/init.h muttrc.man.head muttrc.man.tail + $(MAKEDOC_CPP) $(top_srcdir)/init.h | ./makedoc$(EXEEXT) -m | \ + cat $(srcdir)/muttrc.man.head - $(srcdir)/muttrc.man.tail\ + > muttrc.man + +mutt.1: $(srcdir)/mutt.man + $(EDIT) $(srcdir)/mutt.man > $@ + +smime_keys.1: $(srcdir)/smime_keys.man + $(EDIT) $(srcdir)/smime_keys.man > $@ + +stamp-doc-xml: makedoc$(EXEEXT) $(top_srcdir)/init.h \ + manual.xml.head $(top_srcdir)/functions.h $(top_srcdir)/OPS* manual.xml.tail \ + $(srcdir)/gen-map-doc $(top_srcdir)/VERSION $(top_srcdir)/ChangeLog + ( date=`head -n 1 $(top_srcdir)/ChangeLog | LC_ALL=C cut -d ' ' -f 1` && \ + sed -e "s/@VERSION\@/`cat $(top_srcdir)/VERSION` ($$date)/" $(srcdir)/manual.xml.head && \ + $(MAKEDOC_CPP) $(top_srcdir)/init.h | ./makedoc$(EXEEXT) -s && \ + $(MAKEDOC_CPP) $(top_srcdir)/functions.h | \ + perl $(srcdir)/gen-map-doc $(srcdir)/manual.xml.tail $(top_srcdir)/OPS* \ + ) > manual.xml + touch stamp-doc-xml +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: diff --git a/obj-i486-linux-gnu-patched/doc/Muttrc b/obj-i486-linux-gnu-patched/doc/Muttrc new file mode 100644 index 0000000..a1be004 --- /dev/null +++ b/obj-i486-linux-gnu-patched/doc/Muttrc @@ -0,0 +1,4811 @@ +# +# System configuration file for Mutt +# + +# Default list of header fields to weed when displaying. +# Ignore all lines by default... +ignore * + +# ... then allow these through. +unignore from: subject to cc date x-mailer x-url user-agent + +# Display the fields in this order +hdr_order date from to cc subject + +# emacs-like bindings +bind editor "\e" kill-word +bind editor "\e" kill-word + +# map delete-char to a sane value +bind editor delete-char + +# some people actually like these settings +#set pager_stop +#bind pager previous-line +#bind pager next-line + +# Specifies how to sort messages in the index menu. +set sort=threads + +# Uncomment if your MTA does not strip Bcc: headers. +# (exim4 and postfix strip them, exim(3) does not.) +#unset write_bcc +# Postfix and qmail use Delivered-To for detecting loops +unset bounce_delivered + +set mixmaster="mixmaster-filter" + +# System-wide CA file managed by the ca-certificates package +set ssl_ca_certificates_file="/etc/ssl/certs/ca-certificates.crt" + +# imitate the old search-body function +macro index \eb "~b " "search in message bodies" + +# simulate the old url menu +macro index,pager,attach,compose \cb "\ + set my_pipe_decode=\$pipe_decode pipe_decode\ + urlview\ + set pipe_decode=\$my_pipe_decode; unset my_pipe_decode" \ +"call urlview to extract URLs out of a message" + +# Show documentation when pressing F1 +macro generic,pager " zcat /usr/share/doc/mutt/manual.txt.gz | sensible-pager" "show Mutt documentation" + +# show the incoming mailboxes list (just like "mutt -y") and back when pressing "y" +macro index,pager y "?" "show incoming mailboxes list" +bind browser y exit + +# Use folders which match on \\.gz$ as gzipped folders: +# open-hook \\.gz$ "gzip -cd %f > %t" +# close-hook \\.gz$ "gzip -c %t > %f" +# append-hook \\.gz$ "gzip -c %t >> %f" + +# If Mutt is unable to determine your site's domain name correctly, you can +# set the default here. (better: fix /etc/mailname) +# +# set hostname=cs.hmc.edu + +# If your sendmail supports the -B8BITMIME flag, enable the following +# +# set use_8bitmime + +# Use mime.types to look up handlers for application/octet-stream. Can +# be undone with unmime_lookup. +mime_lookup application/octet-stream + +## +## *** DEFAULT SETTINGS FOR THE ATTACHMENTS PATCH *** +## + +## +## Please see the manual (section "attachments") for detailed +## documentation of the "attachments" command. +## +## Removing a pattern from a list removes that pattern literally. It +## does not remove any type matching the pattern. +## +## attachments +A */.* +## attachments +A image/jpeg +## unattachments +A */.* +## +## This leaves "attached" image/jpeg files on the allowed attachments +## list. It does not remove all items, as you might expect, because the +## second */.* is not a matching expression at this time. +## +## Remember: "unattachments" only undoes what "attachments" has done! +## It does not trigger any matching on actual messages. + +## Qualify any MIME part with an "attachment" disposition, EXCEPT for +## text/x-vcard and application/pgp parts. (PGP parts are already known +## to mutt, and can be searched for with ~g, ~G, and ~k.) +## +## I've added x-pkcs7 to this, since it functions (for S/MIME) +## analogously to PGP signature attachments. S/MIME isn't supported +## in a stock mutt build, but we can still treat it specially here. +## +attachments +A */.* +attachments -A text/x-vcard application/pgp.* +attachments -A application/x-pkcs7-.* + +## Discount all MIME parts with an "inline" disposition, unless they're +## text/plain. (Why inline a text/plain part unless it's external to the +## message flow?) +## +attachments +I text/plain + +## These two lines make Mutt qualify MIME containers. (So, for example, +## a message/rfc822 forward will count as an attachment.) The first +## line is unnecessary if you already have "attach-allow */.*", of +## course. These are off by default! The MIME elements contained +## within a message/* or multipart/* are still examined, even if the +## containers themseves don't qualify. +## +#attachments +A message/.* multipart/.* +#attachments +I message/.* multipart/.* + +## You probably don't really care to know about deleted attachments. +attachments -A message/external-body +attachments -I message/external-body + +# enable mime lookup by extension +mime_lookup application/octet-stream + +## +## More settings +## + + +# set abort_nosubject=ask-yes +# +# Name: abort_nosubject +# Type: quadoption +# Default: ask-yes +# +# +# If set to yes, when composing messages and no subject is given +# at the subject prompt, composition will be aborted. If set to +# no, composing messages with no subject given at the subject +# prompt will never be aborted. +# +# +# set abort_unmodified=yes +# +# Name: abort_unmodified +# Type: quadoption +# Default: yes +# +# +# If set to yes, composition will automatically abort after +# editing the message body if no changes are made to the file (this +# check only happens after the first edit of the file). When set +# to no, composition will never be aborted. +# +# +# set alias_file="~/.muttrc" +# +# Name: alias_file +# Type: path +# Default: "~/.muttrc" +# +# +# The default file in which to save aliases created by the +# function. Entries added to this file are +# encoded in the character set specified by $config_charset if it +# is set or the current character set otherwise. +# +# Note: Mutt will not automatically source this file; you must +# explicitly use the ``source'' command for it to be executed in case +# this option points to a dedicated alias file. +# +# The default for this option is the currently used muttrc file, or +# ``~/.muttrc'' if no user muttrc was found. +# +# +# set alias_format="%4n %2f %t %-10a %r" +# +# Name: alias_format +# Type: string +# Default: "%4n %2f %t %-10a %r" +# +# +# Specifies the format of the data displayed for the ``alias'' menu. The +# following printf(3)-style sequences are available: +# %a alias name +# %f flags - currently, a ``d'' for an alias marked for deletion +# %n index number +# %r address which alias expands to +# %t character which indicates if the alias is tagged for inclusion +# +# +# set allow_8bit=yes +# +# Name: allow_8bit +# Type: boolean +# Default: yes +# +# +# Controls whether 8-bit data is converted to 7-bit using either Quoted- +# Printable or Base64 encoding when sending mail. +# +# +# set allow_ansi=no +# +# Name: allow_ansi +# Type: boolean +# Default: no +# +# +# Controls whether ANSI color codes in messages (and color tags in +# rich text messages) are to be interpreted. +# Messages containing these codes are rare, but if this option is set, +# their text will be colored accordingly. Note that this may override +# your color choices, and even present a security problem, since a +# message could include a line like +# [-- PGP output follows ... +# +# and give it the same color as your attachment color (see also +# $crypt_timestamp). +# +# +# set arrow_cursor=no +# +# Name: arrow_cursor +# Type: boolean +# Default: no +# +# +# When set, an arrow (``->'') will be used to indicate the current entry +# in menus instead of highlighting the whole line. On slow network or modem +# links this will make response faster because there is less that has to +# be redrawn on the screen when moving to the next or previous entries +# in the menu. +# +# +# set ascii_chars=no +# +# Name: ascii_chars +# Type: boolean +# Default: no +# +# +# If set, Mutt will use plain ASCII characters when displaying thread +# and attachment trees, instead of the default ACS characters. +# +# +# set askbcc=no +# +# Name: askbcc +# Type: boolean +# Default: no +# +# +# If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients +# before editing an outgoing message. +# +# +# set askcc=no +# +# Name: askcc +# Type: boolean +# Default: no +# +# +# If set, Mutt will prompt you for carbon-copy (Cc) recipients before +# editing the body of an outgoing message. +# +# +# set assumed_charset="" +# +# Name: assumed_charset +# Type: string +# Default: "" +# +# +# This variable is a colon-separated list of character encoding +# schemes for messages without character encoding indication. +# Header field values and message body content without character encoding +# indication would be assumed that they are written in one of this list. +# By default, all the header fields and message body without any charset +# indication are assumed to be in ``us-ascii''. +# +# For example, Japanese users might prefer this: +# set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8" +# +# However, only the first content is valid for the message body. +# +# +# set attach_charset="" +# +# Name: attach_charset +# Type: string +# Default: "" +# +# +# This variable is a colon-separated list of character encoding +# schemes for text file attachments. Mutt uses this setting to guess +# which encoding files being attached are encoded in to convert them to +# a proper character set given in $send_charset. +# +# If unset, the value of $charset will be used instead. +# For example, the following configuration would work for Japanese +# text handling: +# set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8" +# +# Note: for Japanese users, ``iso-2022-*'' must be put at the head +# of the value as shown above if included. +# +# +# set attach_format="%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] " +# +# Name: attach_format +# Type: string +# Default: "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] " +# +# +# This variable describes the format of the ``attachment'' menu. The +# following printf(3)-style sequences are understood: +# %C charset +# %c requires charset conversion (``n'' or ``c'') +# %D deleted flag +# %d description +# %e MIME content-transfer-encoding +# %f filename +# %I disposition (``I'' for inline, ``A'' for attachment) +# %m major MIME type +# %M MIME subtype +# %n attachment number +# %Q ``Q'', if MIME part qualifies for attachment counting +# %s size +# %t tagged flag +# %T graphic tree characters +# %u unlink (=to delete) flag +# %X number of qualifying MIME parts in this part and its children +# (please see the ``attachments'' section for possible speed effects) +# %>X right justify the rest of the string and pad with character ``X'' +# %|X pad to the end of the line with character ``X'' +# %*X soft-fill with character ``X'' as pad +# +# +# For an explanation of ``soft-fill'', see the $index_format documentation. +# +# +# set attach_sep="\n" +# +# Name: attach_sep +# Type: string +# Default: "\n" +# +# +# The separator to add between attachments when operating (saving, +# printing, piping, etc) on a list of tagged attachments. +# +# +# set attach_split=yes +# +# Name: attach_split +# Type: boolean +# Default: yes +# +# +# If this variable is unset, when operating (saving, printing, piping, +# etc) on a list of tagged attachments, Mutt will concatenate the +# attachments and will operate on them as a single attachment. The +# $attach_sep separator is added after each attachment. When set, +# Mutt will operate on the attachments one by one. +# +# +# set attribution="On %d, %n wrote:" +# +# Name: attribution +# Type: 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 printf(3)-like sequences see +# the section on $index_format. +# +# +# set autoedit=no +# +# Name: autoedit +# Type: boolean +# Default: no +# +# +# When set along with $edit_headers, Mutt will skip the initial +# send-menu (prompting for subject and recipients) and allow you to +# immediately begin editing the body of your +# message. The send-menu may still be accessed once you have finished +# editing the body of your message. +# +# Also see $fast_reply. +# +# +# set auto_tag=no +# +# Name: auto_tag +# Type: boolean +# Default: no +# +# +# When set, functions in the index menu which affect a message +# will be applied to all tagged messages (if there are any). When +# unset, you must first use the function (bound to ``;'' +# by default) to make the next function apply to all tagged messages. +# +# +# set beep=yes +# +# Name: beep +# Type: boolean +# Default: yes +# +# +# When this variable is set, mutt will beep when an error occurs. +# +# +# set beep_new=no +# +# Name: beep_new +# Type: boolean +# Default: no +# +# +# When this variable is set, mutt will beep whenever it prints a message +# notifying you of new mail. This is independent of the setting of the +# $beep variable. +# +# +# set bounce=ask-yes +# +# Name: bounce +# Type: quadoption +# Default: ask-yes +# +# +# Controls whether you will be asked to confirm bouncing messages. +# If set to yes you don't get asked if you want to bounce a +# message. Setting this variable to no is not generally useful, +# and thus not recommended, because you are unable to bounce messages. +# +# +# set bounce_delivered=yes +# +# Name: bounce_delivered +# Type: boolean +# Default: yes +# +# +# When this variable is set, mutt will include Delivered-To headers when +# bouncing messages. Postfix users may wish to unset this variable. +# +# Note: On Debian systems, this option is unset by default in +# /etc/Muttrc. +# +# +# set braille_friendly=no +# +# Name: braille_friendly +# Type: boolean +# Default: no +# +# +# When this variable is set, mutt will place the cursor at the beginning +# of the current line in menus, even when the $arrow_cursor variable +# is unset, making it easier for blind persons using Braille displays to +# follow these menus. The option is unset by default because many +# visual terminals don't permit making the cursor invisible. +# +# +# set check_mbox_size=no +# +# Name: check_mbox_size +# Type: boolean +# Default: no +# +# +# When this variable is set, mutt will use file size attribute instead of +# access time when checking for new mail in mbox and mmdf folders. +# +# This variable is unset by default and should only be enabled when +# new mail detection for these folder types is unreliable or doesn't work. +# +# Note that enabling this variable should happen before any ``mailboxes'' +# directives occur in configuration files regarding mbox or mmdf folders +# because mutt needs to determine the initial new mail status of such a +# mailbox by performing a fast mailbox scan when it is defined. +# Afterwards the new mail status is tracked by file size changes. +# +# +# set charset="" +# +# Name: charset +# Type: string +# Default: "" +# +# +# Character set your terminal uses to display and enter textual data. +# It is also the fallback for $send_charset. +# +# Upon startup Mutt tries to derive this value from environment variables +# such as $LC_CTYPE or $LANG. +# +# Note: It should only be set in case Mutt isn't abled to determine the +# character set used correctly. +# +# +# set check_new=yes +# +# Name: check_new +# Type: boolean +# Default: yes +# +# +# Note: this option only affects maildir and MH style +# mailboxes. +# +# When set, Mutt will check for new mail delivered while the +# mailbox is open. Especially with MH mailboxes, this operation can +# take quite some time since it involves scanning the directory and +# checking each file to see if it has already been looked at. If +# this variable is unset, no check for new mail is performed +# while the mailbox is open. +# +# +# set collapse_unread=yes +# +# Name: collapse_unread +# Type: boolean +# Default: yes +# +# +# When unset, Mutt will not collapse a thread if it contains any +# unread messages. +# +# +# set uncollapse_jump=no +# +# Name: uncollapse_jump +# Type: boolean +# Default: no +# +# +# When set, Mutt will jump to the next unread message, if any, +# when the current thread is uncollapsed. +# +# +# set compose_format="-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-" +# +# Name: compose_format +# Type: string +# Default: "-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-" +# +# +# Controls the format of the status line displayed in the ``compose'' +# menu. This string is similar to $status_format, but has its own +# set of printf(3)-like sequences: +# %a total number of attachments +# %h local hostname +# %l approximate size (in bytes) of the current message +# %v Mutt version string +# +# +# See the text describing the $status_format option for more +# information on how to set $compose_format. +# +# +# set config_charset="" +# +# Name: config_charset +# Type: string +# Default: "" +# +# +# When defined, Mutt will recode commands in rc files from this +# encoding to the current character set as specified by $charset +# and aliases written to $alias_file from the current character set. +# +# Please note that if setting $charset it must be done before +# setting $config_charset. +# +# Recoding should be avoided as it may render unconvertable +# characters as question marks which can lead to undesired +# side effects (for example in regular expressions). +# +# +# set confirmappend=yes +# +# Name: confirmappend +# Type: boolean +# Default: yes +# +# +# When set, Mutt will prompt for confirmation when appending messages to +# an existing mailbox. +# +# +# set confirmcreate=yes +# +# Name: confirmcreate +# Type: boolean +# Default: yes +# +# +# When set, Mutt will prompt for confirmation when saving messages to a +# mailbox which does not yet exist before creating it. +# +# +# set connect_timeout=30 +# +# Name: connect_timeout +# Type: number +# Default: 30 +# +# +# Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this +# many seconds if the connection is not able to be established. A negative +# value causes Mutt to wait indefinitely for the connection attempt to succeed. +# +# +# set content_type="text/plain" +# +# Name: content_type +# Type: string +# Default: "text/plain" +# +# +# Sets the default Content-Type for the body of newly composed messages. +# +# +# set copy=yes +# +# Name: copy +# Type: quadoption +# Default: yes +# +# +# This variable controls whether or not copies of your outgoing messages +# will be saved for later references. Also see $record, +# $save_name, $force_name and ``fcc-hook''. +# +# +# set crypt_use_gpgme=no +# +# Name: crypt_use_gpgme +# Type: boolean +# Default: no +# +# +# This variable controls the use of the GPGME-enabled crypto backends. +# If it is set and Mutt was built with gpgme support, the gpgme code for +# S/MIME and PGP will be used instead of the classic code. Note that +# you need to set this option in .muttrc; it won't have any effect when +# used interactively. +# +# +# set crypt_use_pka=no +# +# Name: crypt_use_pka +# Type: boolean +# Default: no +# +# +# Controls whether mutt uses PKA +# (see http://www.g10code.de/docs/pka-intro.de.pdf) during signature +# verification (only supported by the GPGME backend). +# +# +# set crypt_autopgp=yes +# +# Name: crypt_autopgp +# Type: boolean +# Default: yes +# +# +# This variable controls whether or not mutt may automatically enable +# PGP encryption/signing for messages. See also $crypt_autoencrypt, +# $crypt_replyencrypt, +# $crypt_autosign, $crypt_replysign and $smime_is_default. +# +# +# set crypt_autosmime=yes +# +# Name: crypt_autosmime +# Type: boolean +# Default: yes +# +# +# This variable controls whether or not mutt may automatically enable +# S/MIME encryption/signing for messages. See also $crypt_autoencrypt, +# $crypt_replyencrypt, +# $crypt_autosign, $crypt_replysign and $smime_is_default. +# +# +# set date_format="!%a, %b %d, %Y at %I:%M:%S%p %Z" +# +# Name: date_format +# 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 $index_format. This is passed to the strftime(3) +# function to process the date, see the man page for the proper syntax. +# +# Unless the first character in the string is a bang (``!''), the month +# and week day names are expanded according to the locale specified in +# the variable $locale. If the first character in the string is a +# bang, the bang is discarded, and the month and week day names in the +# rest of the string are expanded in the C locale (that is in US +# English). +# +# +# set default_hook="~f %s !~P | (~P ~C %s)" +# +# Name: default_hook +# Type: string +# Default: "~f %s !~P | (~P ~C %s)" +# +# +# This variable controls how ``message-hook'', ``reply-hook'', ``send-hook'', +# ``send2-hook'', ``save-hook'', and ``fcc-hook'' will +# be interpreted if they are specified with only a simple regexp, +# instead of a matching pattern. The hooks are expanded when they are +# declared, so a hook will be interpreted according to the value of this +# variable at the time the hook is declared. +# +# The default value matches +# if the message is either from a user matching the regular expression +# given, or if it is from you (if the from address matches +# ``alternates'') and is to or cc'ed to a user matching the given +# regular expression. +# +# +# set delete=ask-yes +# +# Name: delete +# Type: quadoption +# Default: ask-yes +# +# +# Controls whether or not messages are really deleted when closing or +# synchronizing a mailbox. If set to yes, messages marked for +# deleting will automatically be purged without prompting. If set to +# no, messages marked for deletion will be kept in the mailbox. +# +# +# set delete_untag=yes +# +# Name: delete_untag +# Type: boolean +# Default: yes +# +# +# If this option is set, mutt will untag messages when marking them +# for deletion. This applies when you either explicitly delete a message, +# or when you save it to another folder. +# +# +# set digest_collapse=yes +# +# Name: digest_collapse +# Type: boolean +# Default: yes +# +# +# If this option is set, mutt's received-attachments menu will not show the subparts of +# individual messages in a multipart/digest. To see these subparts, press ``v'' on that menu. +# +# +# set display_filter="" +# +# Name: display_filter +# Type: path +# Default: "" +# +# +# When set, specifies a command used to filter messages. When a message +# is viewed it is passed as standard input to $display_filter, and the +# filtered message is read from the standard output. +# +# +# set dotlock_program="/usr/bin/mutt_dotlock" +# +# Name: dotlock_program +# Type: path +# Default: "/usr/bin/mutt_dotlock" +# +# +# Contains the path of the mutt_dotlock(8) binary to be used by +# mutt. +# +# +# set dsn_notify="" +# +# Name: dsn_notify +# Type: string +# Default: "" +# +# +# This variable sets the request for when notification is returned. The +# string consists of a comma separated list (no spaces!) of one or more +# of the following: never, to never request notification, +# failure, to request notification on transmission failure, +# delay, to be notified of message delays, success, to be +# notified of successful transmission. +# +# Example: +# set dsn_notify="failure,delay" +# +# Note: when using $sendmail for delivery, you should not enable +# this unless you are either using Sendmail 8.8.x or greater or a MTA +# providing a sendmail(1)-compatible interface supporting the -N option +# for DSN. For SMTP delivery, DSN support is autodetected so that it +# depends on the server whether DSN will be used or not. +# +# +# set dsn_return="" +# +# Name: dsn_return +# Type: string +# Default: "" +# +# +# This variable controls how much of your message is returned in DSN +# messages. It may be set to either hdrs to return just the +# message header, or full to return the full message. +# +# Example: +# set dsn_return=hdrs +# +# Note: when using $sendmail for delivery, you should not enable +# this unless you are either using Sendmail 8.8.x or greater or a MTA +# providing a sendmail(1)-compatible interface supporting the -R option +# for DSN. For SMTP delivery, DSN support is autodetected so that it +# depends on the server whether DSN will be used or not. +# +# +# set duplicate_threads=yes +# +# Name: duplicate_threads +# Type: boolean +# Default: yes +# +# +# This variable controls whether mutt, when $sort is set to threads, threads +# messages with the same Message-Id together. If it is set, it will indicate +# that it thinks they are duplicates of each other with an equals sign +# in the thread tree. +# +# +# set edit_headers=no +# +# Name: edit_headers +# Type: boolean +# Default: no +# +# +# This option allows you to edit the header of your outgoing messages +# along with the body of your message. +# +# Note that changes made to the References: and Date: headers are +# ignored for interoperability reasons. +# +# +# set editor="" +# +# Name: editor +# Type: path +# Default: "" +# +# +# This variable specifies which editor is used by mutt. +# It defaults to the value of the $VISUAL, or $EDITOR, environment +# variable, or to the string ``/usr/bin/editor'' if neither of those are set. +# +# +# set encode_from=no +# +# Name: encode_from +# Type: boolean +# Default: no +# +# +# When set, mutt will quoted-printable encode messages when +# they contain the string ``From '' (note the trailing space) in the beginning of a line. +# This is useful to avoid the tampering certain mail delivery and transport +# agents tend to do with messages (in order to prevent tools from +# misinterpreting the line as a mbox message separator). +# +# +# set envelope_from_address="" +# +# Name: envelope_from_address +# Type: e-mail address +# Default: "" +# +# +# Manually sets the envelope sender for outgoing messages. +# This value is ignored if $use_envelope_from is unset. +# +# +# set escape="~" +# +# Name: escape +# Type: string +# Default: "~" +# +# +# Escape character to use for functions in the builtin editor. +# +# +# set fast_reply=no +# +# Name: fast_reply +# Type: boolean +# Default: no +# +# +# When set, the initial prompt for recipients and subject are skipped +# when replying to messages, and the initial prompt for subject is +# skipped when forwarding messages. +# +# Note: this variable has no effect when the $autoedit +# variable is set. +# +# +# set fcc_attach=yes +# +# Name: fcc_attach +# Type: boolean +# Default: yes +# +# +# This variable controls whether or not attachments on outgoing messages +# are saved along with the main body of your message. +# +# +# set fcc_clear=no +# +# Name: fcc_clear +# Type: boolean +# Default: no +# +# +# When this variable is set, FCCs will be stored unencrypted and +# unsigned, even when the actual message is encrypted and/or +# signed. +# (PGP only) +# +# +# set folder="~/Mail" +# +# Name: folder +# Type: path +# Default: "~/Mail" +# +# +# Specifies the default location of your mailboxes. A ``+'' or ``='' at the +# beginning of a pathname will be expanded to the value of this +# variable. Note that if you change this variable (from the default) +# value you need to make sure that the assignment occurs before +# you use ``+'' or ``='' for any other variables since expansion takes place +# when handling the ``mailboxes'' command. +# +# +# set folder_format="%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f" +# +# Name: folder_format +# Type: string +# Default: "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f" +# +# +# This variable allows you to customize the file browser display to your +# personal taste. This string is similar to $index_format, but has +# its own set of printf(3)-like sequences: +# %C current file number +# %d date/time folder was last modified +# %f filename +# %F file permissions +# %g group name (or numeric gid, if missing) +# %l number of hard links +# %N N if folder has new mail, blank otherwise +# %s size in bytes +# %t ``*'' if the file is tagged, blank otherwise +# %u owner name (or numeric uid, if missing) +# %>X right justify the rest of the string and pad with character ``X'' +# %|X pad to the end of the line with character ``X'' +# %*X soft-fill with character ``X'' as pad +# +# +# For an explanation of ``soft-fill'', see the $index_format documentation. +# +# +# set followup_to=yes +# +# Name: followup_to +# Type: boolean +# Default: yes +# +# +# Controls whether or not the ``Mail-Followup-To:'' header field is +# generated when sending mail. When set, Mutt will generate this +# field when you are replying to a known mailing list, specified with +# the ``subscribe'' or ``lists'' commands. +# +# This field has two purposes. First, preventing you from +# receiving duplicate copies of replies to messages which you send +# to mailing lists, and second, ensuring that you do get a reply +# separately for any messages sent to known lists to which you are +# not subscribed. +# +# The header will contain only the list's address +# for subscribed lists, and both the list address and your own +# email address for unsubscribed lists. Without this header, a +# group reply to your message sent to a subscribed list will be +# sent to both the list and your address, resulting in two copies +# of the same email for you. +# +# +# set force_name=no +# +# Name: force_name +# Type: boolean +# Default: no +# +# +# This variable is similar to $save_name, except that Mutt will +# store a copy of your outgoing message by the username of the address +# you are sending to even if that mailbox does not exist. +# +# Also see the $record variable. +# +# +# set forward_decode=yes +# +# Name: forward_decode +# Type: boolean +# Default: yes +# +# +# Controls the decoding of complex MIME messages into text/plain when +# forwarding a message. The message header is also RFC2047 decoded. +# This variable is only used, if $mime_forward is unset, +# otherwise $mime_forward_decode is used instead. +# +# +# set forward_edit=yes +# +# Name: forward_edit +# Type: quadoption +# Default: yes +# +# +# This quadoption controls whether or not the user is automatically +# placed in the editor when forwarding messages. For those who always want +# to forward with no modification, use a setting of ``no''. +# +# +# set forward_format="[%a: %s]" +# +# Name: forward_format +# Type: string +# Default: "[%a: %s]" +# +# +# This variable controls the default subject when forwarding a message. +# It uses the same format sequences as the $index_format variable. +# +# +# set forward_quote=no +# +# Name: forward_quote +# Type: boolean +# Default: no +# +# +# When set, forwarded messages included in the main body of the +# message (when $mime_forward is unset) will be quoted using +# $indent_string. +# +# +# set from="" +# +# Name: from +# Type: e-mail address +# Default: "" +# +# +# When set, this variable contains a default from address. It +# can be overridden using ``my_hdr'' (including from a ``send-hook'') and +# $reverse_name. This variable is ignored if $use_from is unset. +# +# This setting defaults to the contents of the environment variable $EMAIL. +# +# +# set gecos_mask="^[^,]*" +# +# Name: gecos_mask +# Type: regular expression +# Default: "^[^,]*" +# +# +# A regular expression used by mutt to parse the GECOS field of a password +# entry when expanding the alias. The default value +# will return the string up to the first ``,'' encountered. +# If the GECOS field contains a string like ``lastname, firstname'' then you +# should set it to ``.*''. +# +# This can be useful if you see the following behavior: you address an e-mail +# to user ID ``stevef'' whose full name is ``Steve Franklin''. If mutt expands +# ``stevef'' to ``"Franklin" stevef@foo.bar'' then you should set the $gecos_mask to +# a regular expression that will match the whole name so mutt will expand +# ``Franklin'' to ``Franklin, Steve''. +# +# +# set hdrs=yes +# +# Name: hdrs +# Type: boolean +# Default: yes +# +# +# When unset, the header fields normally added by the ``my_hdr'' +# command are not created. This variable must 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. +# +# +# set header=no +# +# Name: header +# Type: boolean +# Default: no +# +# +# When set, this variable causes Mutt to include the header +# of the message you are replying to into the edit buffer. +# The $weed setting applies. +# +# +# set help=yes +# +# Name: help +# Type: boolean +# Default: yes +# +# +# When set, help lines describing the bindings for the major functions +# provided by each menu are displayed on the first line of the screen. +# +# Note: The binding will not be displayed correctly if the +# function is bound to a sequence rather than a single keystroke. Also, +# the help line may not be updated if a binding is changed while Mutt is +# running. Since this variable is primarily aimed at new users, neither +# of these should present a major problem. +# +# +# set hidden_host=no +# +# Name: hidden_host +# Type: boolean +# Default: no +# +# +# When set, mutt will skip the host name part of $hostname variable +# when adding the domain part to addresses. This variable does not +# affect the generation of Message-IDs, and it will not lead to the +# cut-off of first-level domains. +# +# +# set hide_limited=no +# +# Name: hide_limited +# Type: boolean +# Default: no +# +# +# When set, mutt will not show the presence of messages that are hidden +# by limiting, in the thread tree. +# +# +# set hide_missing=yes +# +# Name: hide_missing +# Type: boolean +# Default: yes +# +# +# When set, mutt will not show the presence of missing messages in the +# thread tree. +# +# +# set hide_thread_subject=yes +# +# Name: hide_thread_subject +# Type: boolean +# Default: yes +# +# +# When set, mutt will not show the subject of messages in the thread +# tree that have the same subject as their parent or closest previously +# displayed sibling. +# +# +# set hide_top_limited=no +# +# Name: hide_top_limited +# Type: boolean +# Default: no +# +# +# When set, mutt will not show the presence of messages that are hidden +# by limiting, at the top of threads in the thread tree. Note that when +# $hide_limited is set, this option will have no effect. +# +# +# set hide_top_missing=yes +# +# Name: hide_top_missing +# Type: boolean +# Default: yes +# +# +# When set, mutt will not show the presence of missing messages at the +# top of threads in the thread tree. Note that when $hide_missing is +# set, this option will have no effect. +# +# +# set history=10 +# +# Name: history +# Type: number +# Default: 10 +# +# +# This variable controls the size (in number of strings remembered) of +# the string history buffer per category. The buffer is cleared each time the +# variable is set. +# +# +# set history_file="~/.mutthistory" +# +# Name: history_file +# Type: path +# Default: "~/.mutthistory" +# +# +# The file in which Mutt will save its history. +# +# +# set honor_followup_to=yes +# +# Name: honor_followup_to +# Type: quadoption +# Default: yes +# +# +# This variable controls whether or not a Mail-Followup-To header is +# honored when group-replying to a message. +# +# +# set hostname="" +# +# Name: hostname +# Type: string +# Default: "" +# +# +# Specifies the fully-qualified hostname of the system mutt is running on +# containing the host's name and the DNS domain it belongs to. It is used +# as the domain part (after ``@'') for local email addresses as well as +# Message-Id headers. +# +# Its value is determined at startup as follows: If the node's name +# as returned by the uname(3) function contains the hostname and the +# domain, these are used to construct $hostname. If there is no +# domain part returned, Mutt will look for a ``domain'' or ``search'' +# line in /etc/resolv.conf to determine the domain. Optionally, Mutt +# can be compiled with a fixed domain name in which case a detected +# one is not used. +# +# Also see $use_domain and $hidden_host. +# +# Note: On Debian systems, the default for this variable is obtained +# from /etc/mailname when Mutt starts. +# +# +# set ignore_linear_white_space=no +# +# Name: ignore_linear_white_space +# Type: boolean +# Default: no +# +# +# This option replaces linear-white-space between encoded-word +# and text to a single space to prevent the display of MIME-encoded +# ``Subject:'' field from being divided into multiple lines. +# +# +# set ignore_list_reply_to=no +# +# Name: ignore_list_reply_to +# Type: boolean +# Default: no +# +# +# Affects the behaviour of the function when replying to +# messages from mailing lists (as defined by the ``subscribe'' or +# ``lists'' commands). When set, if the ``Reply-To:'' field is +# set to the same value as the ``To:'' field, Mutt assumes that the +# ``Reply-To:'' field was set by the mailing list to automate responses +# to the list, and will ignore this field. To direct a response to the +# mailing list when this option is set, use the +# function; will reply to both the sender and the +# list. +# +# +# set imap_authenticators="" +# +# Name: imap_authenticators +# Type: string +# Default: "" +# +# +# This is a colon-delimited list of authentication methods mutt may +# attempt to use to log in to an IMAP server, in the order mutt should +# try them. Authentication methods are either ``login'' or the right +# side of an IMAP ``AUTH=xxx'' capability string, eg ``digest-md5'', ``gssapi'' +# or ``cram-md5''. This option is case-insensitive. If it's +# unset (the default) mutt will try all available methods, +# in order from most-secure to least-secure. +# +# Example: +# set imap_authenticators="gssapi:cram-md5:login" +# +# Note: Mutt will only fall back to other authentication methods if +# the previous methods are unavailable. If a method is available but +# authentication fails, mutt will not connect to the IMAP server. +# +# +# set imap_check_subscribed=no +# +# Name: imap_check_subscribed +# Type: boolean +# Default: no +# +# +# When set, mutt will fetch the set of subscribed folders from +# your server on connection, and add them to the set of mailboxes +# it polls for new mail just as if you had issued individual ``mailboxes'' +# commands. +# +# +# set imap_delim_chars="/." +# +# Name: imap_delim_chars +# Type: string +# Default: "/." +# +# +# This contains the list of characters which you would like to treat +# as folder separators for displaying IMAP paths. In particular it +# helps in using the ``='' shortcut for your folder variable. +# +# +# set imap_headers="" +# +# Name: imap_headers +# Type: string +# Default: "" +# +# +# Mutt requests these header fields in addition to the default headers +# (``Date:'', ``From:'', ``Subject:'', ``To:'', ``Cc:'', ``Message-Id:'', +# ``References:'', ``Content-Type:'', ``Content-Description:'', ``In-Reply-To:'', +# ``Reply-To:'', ``Lines:'', ``List-Post:'', ``X-Label:'') from IMAP +# servers before displaying the index menu. You may want to add more +# headers for spam detection. +# +# Note: This is a space separated list, items should be uppercase +# and not contain the colon, e.g. ``X-BOGOSITY X-SPAM-STATUS'' for the +# ``X-Bogosity:'' and ``X-Spam-Status:'' header fields. +# +# +# set imap_idle=no +# +# Name: imap_idle +# Type: boolean +# Default: no +# +# +# When set, mutt will attempt to use the IMAP IDLE extension +# to check for new mail in the current mailbox. Some servers +# (dovecot was the inspiration for this option) react badly +# to mutt's implementation. If your connection seems to freeze +# up periodically, try unsetting this. +# +# +# set imap_keepalive=900 +# +# Name: imap_keepalive +# Type: number +# Default: 900 +# +# +# This variable specifies the maximum amount of time in seconds that mutt +# will wait before polling open IMAP connections, to prevent the server +# from closing them before mutt has finished with them. The default is +# well within the RFC-specified minimum amount of time (30 minutes) before +# a server is allowed to do this, but in practice the RFC does get +# violated every now and then. Reduce this number if you find yourself +# getting disconnected from your IMAP server due to inactivity. +# +# +# set imap_list_subscribed=no +# +# Name: imap_list_subscribed +# Type: boolean +# Default: no +# +# +# This variable configures whether IMAP folder browsing will look for +# only subscribed folders or all folders. This can be toggled in the +# IMAP browser with the function. +# +# +# set imap_login="" +# +# Name: imap_login +# Type: string +# Default: "" +# +# +# Your login name on the IMAP server. +# +# This variable defaults to the value of $imap_user. +# +# +# set imap_pass="" +# +# Name: imap_pass +# Type: string +# Default: "" +# +# +# Specifies the password for your IMAP account. If unset, Mutt will +# prompt you for your password when you invoke the function +# or try to open an IMAP folder. +# +# Warning: you should only use this option when you are on a +# fairly secure machine, because the superuser can read your muttrc even +# if you are the only one who can read the file. +# +# +# set imap_passive=yes +# +# Name: imap_passive +# Type: boolean +# Default: yes +# +# +# When set, mutt will not open new IMAP connections to check for new +# mail. Mutt will only check for new mail over existing IMAP +# connections. This is useful if you don't want to be prompted to +# user/password pairs on mutt invocation, or if opening the connection +# is slow. +# +# +# set imap_peek=yes +# +# Name: imap_peek +# Type: boolean +# Default: yes +# +# +# When set, mutt will avoid implicitly marking your mail as read whenever +# you fetch a message from the server. This is generally a good thing, +# but can make closing an IMAP folder somewhat slower. This option +# exists to appease speed freaks. +# +# +# set imap_pipeline_depth=15 +# +# Name: imap_pipeline_depth +# Type: number +# Default: 15 +# +# +# Controls the number of IMAP commands that may be queued up before they +# are sent to the server. A deeper pipeline reduces the amount of time +# mutt must wait for the server, and can make IMAP servers feel much +# more responsive. But not all servers correctly handle pipelined commands, +# so if you have problems you might want to try setting this variable to 0. +# +# Note: Changes to this variable have no effect on open connections. +# +# +# set imap_servernoise=yes +# +# Name: imap_servernoise +# Type: boolean +# Default: yes +# +# +# When set, mutt will display warning messages from the IMAP +# server as error messages. Since these messages are often +# harmless, or generated due to configuration problems on the +# server which are out of the users' hands, you may wish to suppress +# them at some point. +# +# +# set imap_user="" +# +# Name: imap_user +# Type: string +# Default: "" +# +# +# The name of the user whose mail you intend to access on the IMAP +# server. +# +# This variable defaults to your user name on the local machine. +# +# +# set implicit_autoview=no +# +# Name: implicit_autoview +# Type: boolean +# Default: no +# +# +# If set to ``yes'', mutt will look for a mailcap entry with the +# ``copiousoutput'' flag set for every MIME attachment it doesn't have +# an internal viewer defined for. If such an entry is found, mutt will +# use the viewer defined in that entry to convert the body part to text +# form. +# +# +# set include=ask-yes +# +# Name: include +# Type: quadoption +# Default: ask-yes +# +# +# Controls whether or not a copy of the message(s) you are replying to +# is included in your reply. +# +# +# set include_onlyfirst=no +# +# Name: include_onlyfirst +# Type: boolean +# Default: no +# +# +# Controls whether or not Mutt includes only the first attachment +# of the message you are replying. +# +# +# set indent_string="> " +# +# Name: indent_string +# Type: string +# Default: "> " +# +# +# Specifies the string to prepend to each line of text quoted in a +# message to which you are replying. You are strongly encouraged not to +# change this value, as it tends to agitate the more fanatical netizens. +# +# This option is a format string, please see the description of +# $index_format for supported printf(3)-style sequences. +# +# Because for format=lowed style messages the quoting mechanism +# is strictly defined, this setting is ignored if $text_flowed is +# set. +# +# +# set index_format="%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s" +# +# Name: index_format +# Type: string +# Default: "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s" +# +# +# This variable allows you to customize the message index display to +# your personal taste. +# +# ``Format strings'' are similar to the strings used in the C +# function printf(3) to format output (see the man page for more details). +# The following sequences are defined in Mutt: +# %a address of the author +# %A reply-to address (if present; otherwise: address of 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 converted to sender's time zone +# %D date and time of the message in the format specified by +# $date_format converted to the local time zone +# %e current message number in thread +# %E number of messages in current thread +# %f sender (address + real name), either From: or Return-Path: +# %F author name, or recipient name if the message is from you +# %H spam attribute(s) of this message +# %i message-id of the current message +# %l number of lines in the message (does not work with maildir, +# mh, and possibly IMAP folders) +# %L If an address in the ``To:'' or ``Cc:'' header field matches an address +# defined by the users ``subscribe'' command, this displays +# "To ", otherwise the same as %F. +# %m total number of message in the mailbox +# %M number of hidden messages if the thread is collapsed. +# %N message score +# %n author's real name (or address if missing) +# %O original save folder where mutt would formerly have +# stashed the message: list name or recipient name +# if not sent to a list +# %P progress indicator for the builtin pager (how much of the file has been displayed) +# %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 +# %v first name of the author, or the recipient if the message is from you +# %X number of attachments +# (please see the ``attachments'' section for possible speed effects) +# %y ``X-Label:'' field, if present +# %Y ``X-Label:'' field, if present, and (1) not at part of a thread tree, +# (2) at the top of a thread, or (3) ``X-Label:'' is different from +# preceding message's ``X-Label:''. +# %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 library function +# strftime(3); 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 library function +# strftime(3); a leading bang disables locales +# %(fmt) the local date and time when the message was received. +# ``fmt'' is expanded by the library function strftime(3); +# a leading bang disables locales +# % the current local time. ``fmt'' is expanded by the library +# function strftime(3); 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'' +# %*X soft-fill with character ``X'' as pad +# +# +# ``Soft-fill'' deserves some explanation: Normal right-justification +# will print everything to the left of the ``%>'', displaying padding and +# whatever lies to the right only if there's room. By contrast, +# soft-fill gives priority to the right-hand side, guaranteeing space +# to display it and showing padding only if there's still room. If +# necessary, soft-fill will eat text leftwards to make room for +# rightward text. +# +# Note that these expandos are supported in +# ``save-hook'', ``fcc-hook'' and ``fcc-save-hook'', too. +# +# +# set ispell="ispell" +# +# Name: ispell +# Type: path +# Default: "ispell" +# +# +# How to invoke ispell (GNU's spell-checking software). +# +# +# set keep_flagged=no +# +# Name: keep_flagged +# Type: boolean +# Default: no +# +# +# If set, read messages marked as flagged will not be moved +# from your spool mailbox to your $mbox mailbox, or as a result of +# a ``mbox-hook'' command. +# +# +# set locale="C" +# +# Name: locale +# Type: string +# Default: "C" +# +# +# The locale used by strftime(3) to format dates. Legal values are +# the strings your system accepts for the locale environment variable $LC_TIME. +# +# +# set mail_check=5 +# +# Name: mail_check +# Type: number +# Default: 5 +# +# +# This variable configures how often (in seconds) mutt should look for +# new mail. Also see the $timeout variable. +# +# +# set mailcap_path="" +# +# Name: mailcap_path +# Type: string +# Default: "" +# +# +# This variable specifies which files to consult when attempting to +# display MIME bodies not directly supported by Mutt. +# +# +# set mailcap_sanitize=yes +# +# Name: mailcap_sanitize +# Type: boolean +# Default: yes +# +# +# If set, mutt will restrict possible characters in mailcap % expandos +# to a well-defined set of safe characters. This is the safe setting, +# but we are not sure it doesn't break some more advanced MIME stuff. +# +# DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE +# DOING! +# +# +# set maildir_mtime=no +# +# Name: maildir_mtime +# Type: boolean +# Default: no +# +# +# If set, the sort-by-date option in the browser will sort maildirs +# smartly, not using the mtime of the maildir itself but that of the +# newest message in the new subdirectory, making the sorting by +# reverse date much more useful. People with maildirs over NFS may +# wish to leave this option unset. +# +# +# set header_cache="" +# +# Name: header_cache +# Type: path +# Default: "" +# +# +# This variable points to the header cache database. +# If pointing to a directory Mutt will contain a header cache +# database file per folder, if pointing to a file that file will +# be a single global header cache. By default it is unset so no header +# caching will be used. +# +# Header caching can greatly improve speed when opening POP, IMAP +# MH or Maildir folders, see ``caching'' for details. +# +# +# set maildir_header_cache_verify=yes +# +# Name: maildir_header_cache_verify +# Type: boolean +# Default: yes +# +# +# Check for Maildir unaware programs other than mutt having modified maildir +# files when the header cache is in use. This incurs one stat(2) per +# message every time the folder is opened (which can be very slow for NFS +# folders). +# +# +# set header_cache_pagesize="16384" +# +# Name: header_cache_pagesize +# Type: string +# Default: "16384" +# +# +# When mutt is compiled with either gdbm or bdb4 as the header cache backend, +# this option changes the database page size. Too large or too small +# values can waste space, memory, or CPU time. The default should be more +# or less optimal for most use cases. +# +# +# set maildir_trash=no +# +# Name: maildir_trash +# Type: boolean +# Default: no +# +# +# If set, messages marked as deleted will be saved with the maildir +# trashed flag instead of unlinked. Note: this only applies +# to maildir-style mailboxes. Setting it will have no effect on other +# mailbox types. +# +# +# set mark_old=yes +# +# Name: mark_old +# Type: boolean +# Default: yes +# +# +# Controls whether or not mutt marks new unread +# messages as old if you exit a mailbox without reading them. +# With this option set, the next time you start mutt, the messages +# will show up with an ``O'' next to them in the index menu, +# indicating that they are old. +# +# +# set markers=yes +# +# Name: markers +# Type: boolean +# Default: yes +# +# +# Controls the display of wrapped lines in the internal pager. If set, a +# ``+'' marker is displayed at the beginning of wrapped lines. +# +# Also see the $smart_wrap variable. +# +# +# set mask="!^\\.[^.]" +# +# Name: mask +# Type: regular expression +# Default: "!^\\.[^.]" +# +# +# A regular expression used in the file browser, optionally preceded by +# the not operator ``!''. Only files whose names match this mask +# will be shown. The match is always case-sensitive. +# +# +# set mbox="~/mbox" +# +# Name: mbox +# Type: path +# Default: "~/mbox" +# +# +# This specifies the folder into which read mail in your $spoolfile +# folder will be appended. +# +# Also see the $move variable. +# +# +# set mbox_type=mbox +# +# Name: mbox_type +# Type: folder magic +# Default: mbox +# +# +# The default mailbox type used when creating new folders. May be any of +# ``mbox'', ``MMDF'', ``MH'' and ``Maildir''. +# +# +# set metoo=no +# +# Name: metoo +# Type: boolean +# Default: no +# +# +# If unset, Mutt will remove your address (see the ``alternates'' +# command) from the list of recipients when replying to a message. +# +# +# set menu_context=0 +# +# Name: menu_context +# Type: number +# Default: 0 +# +# +# This variable controls the number of lines of context that are given +# when scrolling through menus. (Similar to $pager_context.) +# +# +# set menu_move_off=yes +# +# Name: menu_move_off +# Type: boolean +# Default: yes +# +# +# When unset, the bottom entry of menus will never scroll up past +# the bottom of the screen, unless there are less entries than lines. +# When set, the bottom entry may move off the bottom. +# +# +# set menu_scroll=no +# +# Name: menu_scroll +# Type: boolean +# Default: no +# +# +# When set, menus will be scrolled up or down one line when you +# attempt to move across a screen boundary. If unset, the screen +# is cleared and the next or previous page of the menu is displayed +# (useful for slow links to avoid many redraws). +# +# +# set meta_key=no +# +# Name: meta_key +# Type: boolean +# Default: no +# +# +# If set, forces Mutt to interpret keystrokes with the high bit (bit 8) +# set as if the user had pressed the Esc key and whatever key remains +# after having the high bit removed. For example, if the key pressed +# has an ASCII value of 0xf8, then this is treated as if the user had +# pressed Esc then ``x''. This is because the result of removing the +# high bit from 0xf8 is 0x78, which is the ASCII character +# ``x''. +# +# +# set mh_purge=no +# +# Name: mh_purge +# Type: boolean +# Default: no +# +# +# When unset, mutt will mimic mh's behaviour and rename deleted messages +# to , in mh folders instead of really deleting +# them. This leaves the message on disk but makes programs reading the folder +# ignore it. If the variable is set, the message files will simply be +# deleted. +# +# This option is similar to $maildir_trash for Maildir folders. +# +# +# set mh_seq_flagged="flagged" +# +# Name: mh_seq_flagged +# Type: string +# Default: "flagged" +# +# +# The name of the MH sequence used for flagged messages. +# +# +# set mh_seq_replied="replied" +# +# Name: mh_seq_replied +# Type: string +# Default: "replied" +# +# +# The name of the MH sequence used to tag replied messages. +# +# +# set mh_seq_unseen="unseen" +# +# Name: mh_seq_unseen +# Type: string +# Default: "unseen" +# +# +# The name of the MH sequence used for unseen messages. +# +# +# set mime_forward=no +# +# Name: mime_forward +# Type: quadoption +# Default: no +# +# +# When set, the message you are forwarding will be attached as a +# separate message/rfc822 MIME part instead of included in the main body of the +# message. This is useful for forwarding MIME messages so the receiver +# can properly view the message as it was delivered to you. If you like +# to switch between MIME and not MIME from mail to mail, set this +# variable to ``ask-no'' or ``ask-yes''. +# +# Also see $forward_decode and $mime_forward_decode. +# +# +# set mime_forward_decode=no +# +# Name: mime_forward_decode +# Type: boolean +# Default: no +# +# +# Controls the decoding of complex MIME messages into text/plain when +# forwarding a message while $mime_forward is set. Otherwise +# $forward_decode is used instead. +# +# +# set mime_forward_rest=yes +# +# Name: mime_forward_rest +# Type: quadoption +# Default: yes +# +# +# When forwarding multiple attachments of a MIME message from the attachment +# menu, attachments which cannot be decoded in a reasonable manner will +# be attached to the newly composed message if this option is set. +# +# +# set mix_entry_format="%4n %c %-16s %a" +# +# Name: mix_entry_format +# Type: string +# Default: "%4n %c %-16s %a" +# +# +# This variable describes the format of a remailer line on the mixmaster +# chain selection screen. The following printf(3)-like sequences are +# supported: +# %n The running number on the menu. +# %c Remailer capabilities. +# %s The remailer's short name. +# %a The remailer's e-mail address. +# +# +# set mixmaster="mixmaster" +# +# Name: mixmaster +# Type: path +# Default: "mixmaster" +# +# +# This variable contains the path to the Mixmaster binary on your +# system. It is used with various sets of parameters to gather the +# list of known remailers, and to finally send a message through the +# mixmaster chain. +# +# Note: On Debian systems, this option is set by default to +# ``mixmaster-filter'' in /etc/Muttrc. +# +# +# set move=no +# +# Name: move +# Type: quadoption +# Default: no +# +# +# Controls whether or not Mutt will move read messages +# from your spool mailbox to your $mbox mailbox, or as a result of +# a ``mbox-hook'' command. +# +# +# set message_cachedir="" +# +# Name: message_cachedir +# Type: path +# Default: "" +# +# +# Set this to a directory and mutt will cache copies of messages from +# your IMAP and POP servers here. You are free to remove entries at any +# time. +# +# When setting this variable to a directory, mutt needs to fetch every +# remote message only once and can perform regular expression searches +# as fast as for local folders. +# +# Also see the $message_cache_clean variable. +# +# +# set message_cache_clean=no +# +# Name: message_cache_clean +# Type: boolean +# Default: no +# +# +# If set, mutt will clean out obsolete entries from the message cache when +# the mailbox is synchronized. You probably only want to set it +# every once in a while, since it can be a little slow +# (especially for large folders). +# +# +# set message_format="%s" +# +# Name: message_format +# Type: string +# Default: "%s" +# +# +# This is the string displayed in the ``attachment'' menu for +# attachments of type message/rfc822. For a full listing of defined +# printf(3)-like sequences see the section on $index_format. +# +# +# set narrow_tree=no +# +# Name: narrow_tree +# Type: boolean +# Default: no +# +# +# This variable, when set, makes the thread tree narrower, allowing +# deeper threads to fit on the screen. +# +# +# set net_inc=10 +# +# Name: net_inc +# Type: number +# Default: 10 +# +# +# Operations that expect to transfer a large amount of data over the +# network will update their progress every $net_inc kilobytes. +# If set to 0, no progress messages will be displayed. +# +# See also $read_inc, $write_inc and $net_inc. +# +# +# set pager="builtin" +# +# Name: pager +# Type: path +# Default: "builtin" +# +# +# This variable specifies which pager you would like to use to view +# messages. The value ``builtin'' means to use the builtin pager, otherwise this +# variable should specify the pathname of the external pager you would +# like to use. +# +# Using an external pager may have some disadvantages: Additional +# keystrokes are necessary because you can't call mutt functions +# directly from the pager, and screen resizes cause lines longer than +# the screen width to be badly formatted in the help menu. +# +# +# set pager_context=0 +# +# Name: pager_context +# Type: number +# Default: 0 +# +# +# This variable controls the number of lines of context that are given +# when displaying the next or previous page in the internal pager. By +# default, Mutt will display the line after the last one on the screen +# at the top of the next page (0 lines of context). +# +# +# set pager_format="-%Z- %C/%m: %-20.20n %s%* -- (%P)" +# +# Name: pager_format +# Type: string +# Default: "-%Z- %C/%m: %-20.20n %s%* -- (%P)" +# +# +# 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 $index_format +# section. +# +# +# set pager_index_lines=0 +# +# Name: pager_index_lines +# Type: number +# Default: 0 +# +# +# Determines the number of lines of a mini-index which is shown when in +# the pager. The current message, unless near the top or bottom of the +# folder, will be roughly one third of the way down this mini-index, +# giving the reader the context of a few messages before and after the +# message. This is useful, for example, to determine how many messages +# remain to be read in the current thread. One of the lines is reserved +# for the status bar from the index, so a setting of 6 +# will only show 5 lines of the actual index. A value of 0 results in +# no index being shown. If the number of messages in the current folder +# is less than $pager_index_lines, then the index will only use as +# many lines as it needs. +# +# +# set pager_stop=no +# +# Name: pager_stop +# Type: boolean +# Default: no +# +# +# When set, the internal-pager will not move to the next message +# when you are at the end of a message and invoke the +# function. +# +# +# set crypt_autosign=no +# +# Name: crypt_autosign +# Type: boolean +# Default: no +# +# +# Setting this variable will cause Mutt to always attempt to +# cryptographically sign outgoing messages. This can be overridden +# by use of the pgp menu, when signing is not required or +# encryption is requested as well. If $smime_is_default is set, +# then OpenSSL is used instead to create S/MIME messages and settings can +# be overridden by use of the smime menu instead of the pgp menu. +# (Crypto only) +# +# +# set crypt_autoencrypt=no +# +# Name: crypt_autoencrypt +# Type: boolean +# Default: no +# +# +# Setting this variable will cause Mutt to always attempt to PGP +# encrypt outgoing messages. This is probably only useful in +# connection to the ``send-hook'' command. It can be overridden +# by use of the pgp menu, when encryption is not required or +# signing is requested as well. If $smime_is_default is set, +# then OpenSSL is used instead to create S/MIME messages and +# settings can be overridden by use of the smime menu instead. +# (Crypto only) +# +# +# set pgp_ignore_subkeys=yes +# +# Name: pgp_ignore_subkeys +# Type: boolean +# Default: yes +# +# +# Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, +# the principal key will inherit the subkeys' capabilities. Unset this +# if you want to play interesting key selection games. +# (PGP only) +# +# +# set crypt_replyencrypt=yes +# +# Name: crypt_replyencrypt +# Type: boolean +# Default: yes +# +# +# If set, automatically PGP or OpenSSL encrypt replies to messages which are +# encrypted. +# (Crypto only) +# +# +# set crypt_replysign=no +# +# Name: crypt_replysign +# Type: boolean +# Default: no +# +# +# If set, automatically PGP or OpenSSL sign replies to messages which are +# signed. +# +# Note: this does not work on messages that are encrypted +# and signed! +# (Crypto only) +# +# +# set crypt_replysignencrypted=no +# +# Name: crypt_replysignencrypted +# Type: boolean +# Default: no +# +# +# If set, automatically PGP or OpenSSL sign replies to messages +# which are encrypted. This makes sense in combination with +# $crypt_replyencrypt, because it allows you to sign all +# messages which are automatically encrypted. This works around +# the problem noted in $crypt_replysign, that mutt is not able +# to find out whether an encrypted message is also signed. +# (Crypto only) +# +# +# set crypt_timestamp=yes +# +# Name: crypt_timestamp +# Type: boolean +# Default: yes +# +# +# If set, mutt will include a time stamp in the lines surrounding +# PGP or S/MIME output, so spoofing such lines is more difficult. +# If you are using colors to mark these lines, and rely on these, +# you may unset this setting. +# (Crypto only) +# +# +# set sidebar_delim="|" +# +# Name: sidebar_delim +# Type: string +# Default: "|" +# +# +# This specifies the delimiter between the sidebar (if visible) and +# other screens. +# +# +# set sidebar_visible=no +# +# Name: sidebar_visible +# Type: boolean +# Default: no +# +# +# This specifies whether or not to show sidebar (left-side list of folders). +# +# +# set sidebar_width=0 +# +# Name: sidebar_width +# Type: number +# Default: 0 +# +# +# The width of the sidebar. +# +# +# set pgp_use_gpg_agent=no +# +# Name: pgp_use_gpg_agent +# Type: boolean +# Default: no +# +# +# If set, mutt will use a possibly-running gpg-agent(1) process. +# (PGP only) +# +# +# set crypt_verify_sig=yes +# +# Name: crypt_verify_sig +# Type: quadoption +# Default: yes +# +# +# If ``yes'', always attempt to verify PGP or S/MIME signatures. +# If ``ask-*'', ask whether or not to verify the signature. +# If \Fi``no'', never attempt to verify cryptographic signatures. +# (Crypto only) +# +# +# set smime_is_default=no +# +# Name: smime_is_default +# Type: boolean +# Default: no +# +# +# The default behaviour of mutt is to use PGP on all auto-sign/encryption +# operations. To override and to use OpenSSL instead this must be set. +# However, this has no effect while replying, since mutt will automatically +# select the same application that was used to sign/encrypt the original +# message. (Note that this variable can be overridden by unsetting $crypt_autosmime.) +# (S/MIME only) +# +# +# set smime_ask_cert_label=yes +# +# Name: smime_ask_cert_label +# Type: boolean +# Default: yes +# +# +# This flag controls whether you want to be asked to enter a label +# for a certificate about to be added to the database or not. It is +# set by default. +# (S/MIME only) +# +# +# set smime_decrypt_use_default_key=yes +# +# Name: smime_decrypt_use_default_key +# Type: boolean +# Default: yes +# +# +# If set (default) this tells mutt to use the default key for decryption. Otherwise, +# if managing multiple certificate-key-pairs, mutt will try to use the mailbox-address +# to determine the key to use. It will ask you to supply a key, if it can't find one. +# (S/MIME only) +# +# +# set pgp_entry_format="%4n %t%f %4l/0x%k %-4a %2c %u" +# +# Name: pgp_entry_format +# Type: string +# Default: "%4n %t%f %4l/0x%k %-4a %2c %u" +# +# +# This variable allows you to customize the PGP key selection menu to +# your personal taste. This string is similar to $index_format, but +# has its own set of printf(3)-like sequences: +# %n number +# %k key id +# %u user id +# %a algorithm +# %l key length +# %f flags +# %c capabilities +# %t trust/validity of the key-uid association +# %[] date of the key where is an strftime(3) expression +# +# +# (PGP only) +# +# +# set pgp_good_sign="" +# +# Name: pgp_good_sign +# Type: regular expression +# Default: "" +# +# +# If you assign a text to this variable, then a PGP signature is only +# considered verified if the output from $pgp_verify_command contains +# the text. Use this variable if the exit code from the command is 0 +# even for bad signatures. +# (PGP only) +# +# +# set pgp_check_exit=yes +# +# Name: pgp_check_exit +# Type: boolean +# Default: yes +# +# +# If set, mutt will check the exit code of the PGP subprocess when +# signing or encrypting. A non-zero exit code means that the +# subprocess failed. +# (PGP only) +# +# +# set pgp_long_ids=no +# +# Name: pgp_long_ids +# Type: boolean +# Default: no +# +# +# If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs. +# (PGP only) +# +# +# set pgp_retainable_sigs=no +# +# Name: pgp_retainable_sigs +# Type: boolean +# Default: no +# +# +# If set, signed and encrypted messages will consist of nested +# multipart/signed and multipart/encrypted body parts. +# +# This is useful for applications like encrypted and signed mailing +# lists, where the outer layer (multipart/encrypted) can be easily +# removed, while the inner multipart/signed part is retained. +# (PGP only) +# +# +# set pgp_autoinline=no +# +# Name: pgp_autoinline +# Type: boolean +# Default: no +# +# +# This option controls whether Mutt generates old-style inline +# (traditional) PGP encrypted or signed messages under certain +# circumstances. This can be overridden by use of the pgp menu, +# when inline is not required. +# +# Note that Mutt might automatically use PGP/MIME for messages +# which consist of more than a single MIME part. Mutt can be +# configured to ask before sending PGP/MIME messages when inline +# (traditional) would not work. +# +# Also see the $pgp_mime_auto variable. +# +# Also note that using the old-style PGP message format is strongly +# deprecated. +# (PGP only) +# +# +# set pgp_replyinline=no +# +# Name: pgp_replyinline +# Type: boolean +# Default: no +# +# +# Setting this variable will cause Mutt to always attempt to +# create an inline (traditional) message when replying to a +# message which is PGP encrypted/signed inline. This can be +# overridden by use of the pgp menu, when inline is not +# required. This option does not automatically detect if the +# (replied-to) message is inline; instead it relies on Mutt +# internals for previously checked/flagged messages. +# +# Note that Mutt might automatically use PGP/MIME for messages +# which consist of more than a single MIME part. Mutt can be +# configured to ask before sending PGP/MIME messages when inline +# (traditional) would not work. +# +# Also see the $pgp_mime_auto variable. +# +# Also note that using the old-style PGP message format is strongly +# deprecated. +# (PGP only) +# +# +# set pgp_show_unusable=yes +# +# Name: pgp_show_unusable +# Type: boolean +# Default: yes +# +# +# If set, mutt will display non-usable keys on the PGP key selection +# menu. This includes keys which have been revoked, have expired, or +# have been marked as ``disabled'' by the user. +# (PGP only) +# +# +# set pgp_sign_as="" +# +# Name: pgp_sign_as +# Type: string +# Default: "" +# +# +# If you have more than one key pair, this option allows you to specify +# which of your private keys to use. It is recommended that you use the +# keyid form to specify your key (e.g. 0x00112233). +# (PGP only) +# +# +# set pgp_strict_enc=yes +# +# Name: pgp_strict_enc +# Type: boolean +# Default: yes +# +# +# If set, Mutt will automatically encode PGP/MIME signed messages as +# quoted-printable. Please note that unsetting this variable may +# lead to problems with non-verifyable PGP signatures, so only change +# this if you know what you are doing. +# (PGP only) +# +# +# set pgp_timeout=300 +# +# Name: pgp_timeout +# Type: number +# Default: 300 +# +# +# The number of seconds after which a cached passphrase will expire if +# not used. +# (PGP only) +# +# +# set pgp_sort_keys=address +# +# Name: pgp_sort_keys +# Type: sort order +# Default: address +# +# +# Specifies how the entries in the pgp menu are sorted. The +# following are legal values: +# address sort alphabetically by user id +# keyid sort alphabetically by key id +# date sort by key creation date +# trust sort by the trust of the key +# +# +# If you prefer reverse order of the above values, prefix it with +# ``reverse-''. +# (PGP only) +# +# +# set pgp_mime_auto=ask-yes +# +# Name: pgp_mime_auto +# Type: quadoption +# Default: ask-yes +# +# +# This option controls whether Mutt will prompt you for +# automatically sending a (signed/encrypted) message using +# PGP/MIME when inline (traditional) fails (for any reason). +# +# Also note that using the old-style PGP message format is strongly +# deprecated. +# (PGP only) +# +# +# set pgp_auto_decode=no +# +# Name: pgp_auto_decode +# Type: boolean +# Default: no +# +# +# If set, mutt will automatically attempt to decrypt traditional PGP +# messages whenever the user performs an operation which ordinarily would +# result in the contents of the message being operated on. For example, +# if the user displays a pgp-traditional message which has not been manually +# checked with the function, mutt will automatically +# check the message for traditional pgp. +# +# +# set pgp_mime_signature_filename="signature.asc" +# +# Name: pgp_mime_signature_filename +# Type: string +# Default: "signature.asc" +# +# +# This option sets the filename used for signature parts in PGP/MIME +# signed messages. +# +# +# set pgp_mime_signature_description="Digital signature" +# +# Name: pgp_mime_signature_description +# Type: string +# Default: "Digital signature" +# +# +# This option sets the Content-Description used for signature parts in +# PGP/MIME signed messages. +# +# +# set pgp_decode_command="" +# +# Name: pgp_decode_command +# Type: string +# Default: "" +# +# +# This format strings specifies a command which is used to decode +# application/pgp attachments. +# +# The PGP command formats have their own set of printf(3)-like sequences: +# %p Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty +# string otherwise. Note: This may be used with a %? construct. +# %f Expands to the name of a file containing a message. +# %s Expands to the name of a file containing the signature part +# of a multipart/signed attachment when verifying it. +# %a The value of $pgp_sign_as. +# %r One or more key IDs. +# +# +# For examples on how to configure these formats for the various versions +# of PGP which are floating around, see the pgp and gpg sample configuration files in +# the samples/ subdirectory which has been installed on your system +# alongside the documentation. +# (PGP only) +# +# +# set pgp_getkeys_command="" +# +# Name: pgp_getkeys_command +# Type: string +# Default: "" +# +# +# This command is invoked whenever mutt will need public key information. +# Of the sequences supported by $pgp_decode_command, %r is the only +# printf(3)-like sequence used with this format. +# (PGP only) +# +# +# set pgp_verify_command="" +# +# Name: pgp_verify_command +# Type: string +# Default: "" +# +# +# This command is used to verify PGP signatures. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) +# +# +# set pgp_decrypt_command="" +# +# Name: pgp_decrypt_command +# Type: string +# Default: "" +# +# +# This command is used to decrypt a PGP encrypted message. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) +# +# +# set pgp_clearsign_command="" +# +# Name: pgp_clearsign_command +# Type: string +# Default: "" +# +# +# This format is used to create an old-style ``clearsigned'' PGP +# message. Note that the use of this format is strongly +# deprecated. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) +# +# +# set pgp_sign_command="" +# +# Name: pgp_sign_command +# Type: string +# Default: "" +# +# +# This command is used to create the detached PGP signature for a +# multipart/signed PGP/MIME body part. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) +# +# +# set pgp_encrypt_sign_command="" +# +# Name: pgp_encrypt_sign_command +# Type: string +# Default: "" +# +# +# This command is used to both sign and encrypt a body part. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) +# +# +# set pgp_encrypt_only_command="" +# +# Name: pgp_encrypt_only_command +# Type: string +# Default: "" +# +# +# This command is used to encrypt a body part without signing it. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) +# +# +# set pgp_import_command="" +# +# Name: pgp_import_command +# Type: string +# Default: "" +# +# +# This command is used to import a key from a message into +# the user's public key ring. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) +# +# +# set pgp_export_command="" +# +# Name: pgp_export_command +# Type: string +# Default: "" +# +# +# This command is used to export a public key from the user's +# key ring. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) +# +# +# set pgp_verify_key_command="" +# +# Name: pgp_verify_key_command +# Type: string +# Default: "" +# +# +# This command is used to verify key information from the key selection +# menu. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) +# +# +# set pgp_list_secring_command="" +# +# Name: pgp_list_secring_command +# Type: string +# Default: "" +# +# +# This command is used to list the secret key ring's contents. The +# output format must be analogous to the one used by: +# gpg --list-keys --with-colons. +# +# This format is also generated by the pgpring utility which comes +# with mutt. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) +# +# +# set pgp_list_pubring_command="" +# +# Name: pgp_list_pubring_command +# Type: string +# Default: "" +# +# +# This command is used to list the public key ring's contents. The +# output format must be analogous to the one used by +# gpg --list-keys --with-colons. +# +# This format is also generated by the pgpring utility which comes +# with mutt. +# +# This is a format string, see the $pgp_decode_command command for +# possible printf(3)-like sequences. +# (PGP only) +# +# +# set forward_decrypt=yes +# +# Name: forward_decrypt +# Type: boolean +# Default: yes +# +# +# Controls the handling of encrypted messages when forwarding a message. +# When set, the outer layer of encryption is stripped off. This +# variable is only used if $mime_forward is set and +# $mime_forward_decode is unset. +# (PGP only) +# +# +# set smime_timeout=300 +# +# Name: smime_timeout +# Type: number +# Default: 300 +# +# +# The number of seconds after which a cached passphrase will expire if +# not used. +# (S/MIME only) +# +# +# set smime_encrypt_with="" +# +# Name: smime_encrypt_with +# Type: string +# Default: "" +# +# +# This sets the algorithm that should be used for encryption. +# Valid choices are ``des'', ``des3'', ``rc2-40'', ``rc2-64'', ``rc2-128''. +# If unset, ``3des'' (TripleDES) is used. +# (S/MIME only) +# +# +# set smime_keys="" +# +# Name: smime_keys +# Type: path +# Default: "" +# +# +# Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle +# storage and retrieval of keys/certs by itself. This is very basic right now, +# and stores keys and certificates in two different directories, both +# named as the hash-value retrieved from OpenSSL. There is an index file +# which contains mailbox-address keyid pair, and which can be manually +# edited. This option points to the location of the private keys. +# (S/MIME only) +# +# +# set smime_ca_location="" +# +# Name: smime_ca_location +# Type: path +# Default: "" +# +# +# This variable contains the name of either a directory, or a file which +# contains trusted certificates for use with OpenSSL. +# (S/MIME only) +# +# Note: On Debian systems, this defaults to the first existing file in +# the following list: ~/.smime/ca-certificates.crt ~/.smime/ca-bundle.crt +# /etc/ssl/certs/ca-certificates.crt. +# +# +# set smime_certificates="" +# +# Name: smime_certificates +# Type: path +# Default: "" +# +# +# Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle +# storage and retrieval of keys by itself. This is very basic right +# now, and keys and certificates are stored in two different +# directories, both named as the hash-value retrieved from +# OpenSSL. There is an index file which contains mailbox-address +# keyid pairs, and which can be manually edited. This option points to +# the location of the certificates. +# (S/MIME only) +# +# +# set smime_decrypt_command="" +# +# Name: smime_decrypt_command +# Type: string +# Default: "" +# +# +# This format string specifies a command which is used to decrypt +# application/x-pkcs7-mime attachments. +# +# The OpenSSL command formats have their own set of printf(3)-like sequences +# similar to PGP's: +# %f Expands to the name of a file containing a message. +# %s Expands to the name of a file containing the signature part +# of a multipart/signed attachment when verifying it. +# %k The key-pair specified with $smime_default_key +# %c One or more certificate IDs. +# %a The algorithm used for encryption. +# %C CA location: Depending on whether $smime_ca_location +# points to a directory or file, this expands to +# ``-CApath $smime_ca_location'' or ``-CAfile $smime_ca_location''. +# +# +# For examples on how to configure these formats, see the smime.rc in +# the samples/ subdirectory which has been installed on your system +# alongside the documentation. +# (S/MIME only) +# +# +# set smime_verify_command="" +# +# Name: smime_verify_command +# Type: string +# Default: "" +# +# +# This command is used to verify S/MIME signatures of type multipart/signed. +# +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) +# +# +# set smime_verify_opaque_command="" +# +# Name: smime_verify_opaque_command +# Type: string +# Default: "" +# +# +# This command is used to verify S/MIME signatures of type +# application/x-pkcs7-mime. +# +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) +# +# +# set smime_sign_command="" +# +# Name: smime_sign_command +# Type: string +# Default: "" +# +# +# This command is used to created S/MIME signatures of type +# multipart/signed, which can be read by all mail clients. +# +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) +# +# +# set smime_sign_opaque_command="" +# +# Name: smime_sign_opaque_command +# Type: string +# Default: "" +# +# +# This command is used to created S/MIME signatures of type +# application/x-pkcs7-signature, which can only be handled by mail +# clients supporting the S/MIME extension. +# +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) +# +# +# set smime_encrypt_command="" +# +# Name: smime_encrypt_command +# Type: string +# Default: "" +# +# +# This command is used to create encrypted S/MIME messages. +# +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) +# +# +# set smime_pk7out_command="" +# +# Name: smime_pk7out_command +# Type: string +# Default: "" +# +# +# This command is used to extract PKCS7 structures of S/MIME signatures, +# in order to extract the public X509 certificate(s). +# +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) +# +# +# set smime_get_cert_command="" +# +# Name: smime_get_cert_command +# Type: string +# Default: "" +# +# +# This command is used to extract X509 certificates from a PKCS7 structure. +# +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) +# +# +# set smime_get_signer_cert_command="" +# +# Name: smime_get_signer_cert_command +# Type: string +# Default: "" +# +# +# This command is used to extract only the signers X509 certificate from a S/MIME +# signature, so that the certificate's owner may get compared to the +# email's ``From:'' field. +# +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) +# +# +# set smime_import_cert_command="" +# +# Name: smime_import_cert_command +# Type: string +# Default: "" +# +# +# This command is used to import a certificate via smime_keys. +# +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) +# +# +# set smime_get_cert_email_command="" +# +# Name: smime_get_cert_email_command +# Type: string +# Default: "" +# +# +# This command is used to extract the mail address(es) used for storing +# X509 certificates, and for verification purposes (to check whether the +# certificate was issued for the sender's mailbox). +# +# This is a format string, see the $smime_decrypt_command command for +# possible printf(3)-like sequences. +# (S/MIME only) +# +# +# set smime_default_key="" +# +# Name: smime_default_key +# Type: string +# Default: "" +# +# +# This is the default key-pair to use for signing. This must be set to the +# keyid (the hash-value that OpenSSL generates) to work properly +# (S/MIME only) +# +# +# set ssl_client_cert="" +# +# Name: ssl_client_cert +# Type: path +# Default: "" +# +# +# The file containing a client certificate and its associated private +# key. +# +# +# set ssl_force_tls=no +# +# Name: ssl_force_tls +# Type: boolean +# Default: no +# +# +# If this variable is set, Mutt will require that all connections +# to remote servers be encrypted. Furthermore it will attempt to +# negotiate TLS even if the server does not advertise the capability, +# since it would otherwise have to abort the connection anyway. This +# option supersedes $ssl_starttls. +# +# +# set ssl_starttls=yes +# +# Name: ssl_starttls +# Type: quadoption +# Default: yes +# +# +# If set (the default), mutt will attempt to use STARTTLS on servers +# advertising the capability. When unset, mutt will not attempt to +# use STARTTLS regardless of the server's capabilities. +# +# +# set certificate_file="~/.mutt_certificates" +# +# Name: certificate_file +# Type: path +# Default: "~/.mutt_certificates" +# +# +# This variable specifies the file where the certificates you trust +# are saved. When an unknown certificate is encountered, you are asked +# if you accept it or not. If you accept it, the certificate can also +# be saved in this file and further connections are automatically +# accepted. +# +# You can also manually add CA certificates in this file. Any server +# certificate that is signed with one of these CA certificates is +# also automatically accepted. +# +# Example: +# set certificate_file=~/.mutt/certificates +# +# +# set ssl_use_sslv3=yes +# +# Name: ssl_use_sslv3 +# Type: boolean +# Default: yes +# +# +# This variable specifies whether to attempt to use SSLv3 in the +# SSL authentication process. +# +# +# set ssl_use_tlsv1=yes +# +# Name: ssl_use_tlsv1 +# Type: boolean +# Default: yes +# +# +# This variable specifies whether to attempt to use TLSv1 in the +# SSL authentication process. +# +# +# set ssl_min_dh_prime_bits=0 +# +# Name: ssl_min_dh_prime_bits +# Type: number +# Default: 0 +# +# +# This variable specifies the minimum acceptable prime size (in bits) +# for use in any Diffie-Hellman key exchange. A value of 0 will use +# the default from the GNUTLS library. +# +# +# set ssl_ca_certificates_file="" +# +# Name: ssl_ca_certificates_file +# Type: path +# Default: "" +# +# +# This variable specifies a file containing trusted CA certificates. +# Any server certificate that is signed with one of these CA +# certificates is also automatically accepted. +# +# Example: +# set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt +# +# Note: On Debian systems, this variable defaults to the example +# mentioned. This file is managed by the ``ca-certificates'' package. +# +# +# set pipe_split=no +# +# Name: pipe_split +# Type: boolean +# Default: no +# +# +# Used in connection with the function following +# . If this variable is unset, when piping a list of +# tagged messages Mutt will concatenate the messages and will pipe them +# all concatenated. When set, Mutt will pipe the messages one by one. +# In both cases the messages are piped in the current sorted order, +# and the $pipe_sep separator is added after each message. +# +# +# set pipe_decode=no +# +# Name: pipe_decode +# Type: boolean +# Default: no +# +# +# Used in connection with the command. When unset, +# Mutt will pipe the messages without any preprocessing. When set, Mutt +# will weed headers and will attempt to decode the messages +# first. +# +# +# set pipe_sep="\n" +# +# Name: pipe_sep +# Type: string +# Default: "\n" +# +# +# The separator to add between messages when piping a list of tagged +# messages to an external Unix command. +# +# +# set pop_authenticators="" +# +# Name: pop_authenticators +# Type: string +# Default: "" +# +# +# This is a colon-delimited list of authentication methods mutt may +# attempt to use to log in to an POP server, in the order mutt should +# try them. Authentication methods are either ``user'', ``apop'' or any +# SASL mechanism, eg ``digest-md5'', ``gssapi'' or ``cram-md5''. +# This option is case-insensitive. If this option is unset +# (the default) mutt will try all available methods, in order from +# most-secure to least-secure. +# +# Example: +# set pop_authenticators="digest-md5:apop:user" +# +# +# set pop_auth_try_all=yes +# +# Name: pop_auth_try_all +# Type: boolean +# Default: yes +# +# +# If set, Mutt will try all available authentication methods. +# When unset, Mutt will only fall back to other authentication +# methods if the previous methods are unavailable. If a method is +# available but authentication fails, Mutt will not connect to the POP server. +# +# +# set pop_checkinterval=60 +# +# Name: pop_checkinterval +# Type: number +# Default: 60 +# +# +# This variable configures how often (in seconds) mutt should look for +# new mail in the currently selected mailbox if it is a POP mailbox. +# +# +# set pop_delete=ask-no +# +# Name: pop_delete +# Type: quadoption +# Default: ask-no +# +# +# If set, Mutt will delete successfully downloaded messages from the POP +# server when using the function. When unset, Mutt will +# download messages but also leave them on the POP server. +# +# +# set pop_host="" +# +# Name: pop_host +# Type: string +# Default: "" +# +# +# The name of your POP server for the function. You +# can also specify an alternative port, username and password, ie: +# [pop[s]://][username[:password]@]popserver[:port] +# +# where ``[...]'' denotes an optional part. +# +# +# set pop_last=no +# +# Name: pop_last +# Type: boolean +# Default: no +# +# +# If this variable is set, mutt will try to use the ``LAST'' POP command +# for retrieving only unread messages from the POP server when using +# the function. +# +# +# set pop_reconnect=ask-yes +# +# Name: pop_reconnect +# Type: quadoption +# Default: ask-yes +# +# +# Controls whether or not Mutt will try to reconnect to the POP server if +# the connection is lost. +# +# +# set pop_user="" +# +# Name: pop_user +# Type: string +# Default: "" +# +# +# Your login name on the POP server. +# +# This variable defaults to your user name on the local machine. +# +# +# set pop_pass="" +# +# Name: pop_pass +# Type: string +# Default: "" +# +# +# Specifies the password for your POP account. If unset, Mutt will +# prompt you for your password when you open a POP mailbox. +# +# Warning: you should only use this option when you are on a +# fairly secure machine, because the superuser can read your muttrc +# even if you are the only one who can read the file. +# +# +# set post_indent_string="" +# +# Name: post_indent_string +# Type: string +# Default: "" +# +# +# Similar to the $attribution variable, Mutt will append this +# string after the inclusion of a message which is being replied to. +# +# +# set postpone=ask-yes +# +# Name: postpone +# Type: quadoption +# Default: ask-yes +# +# +# Controls whether or not messages are saved in the $postponed +# mailbox when you elect not to send immediately. +# +# Also see the $recall variable. +# +# +# set postponed="~/postponed" +# +# Name: postponed +# Type: path +# Default: "~/postponed" +# +# +# Mutt allows you to indefinitely ``postpone sending a message'' which +# you are editing. When you choose to postpone a message, Mutt saves it +# in the mailbox specified by this variable. +# +# Also see the $postpone variable. +# +# +# set preconnect="" +# +# Name: preconnect +# Type: string +# Default: "" +# +# +# If set, a shell command to be executed if mutt fails to establish +# a connection to the server. This is useful for setting up secure +# connections, e.g. with ssh(1). If the command returns a nonzero +# status, mutt gives up opening the server. Example: +# set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \ +# sleep 20 < /dev/null > /dev/null" +# +# Mailbox ``foo'' on ``mailhost.net'' can now be reached +# as ``{localhost:1234}foo''. +# +# Note: For this example to work, you must be able to log in to the +# remote machine without having to enter a password. +# +# When set, Mutt uses the tunnel for all remote connections. +# Please see ``account-hook'' in the manual for how to use different +# tunnel commands per connection. +# +# +# set print=ask-no +# +# Name: print +# Type: quadoption +# Default: ask-no +# +# +# Controls whether or not Mutt really prints messages. +# This is set to ``ask-no'' by default, because some people +# accidentally hit ``p'' often. +# +# +# set print_command="lpr" +# +# Name: print_command +# Type: path +# Default: "lpr" +# +# +# This specifies the command pipe that should be used to print messages. +# +# +# set print_decode=yes +# +# Name: print_decode +# Type: boolean +# Default: yes +# +# +# Used in connection with the command. If this +# option is set, the message is decoded before it is passed to the +# external command specified by $print_command. If this option +# is unset, no processing will be applied to the message when +# printing it. The latter setting may be useful if you are using +# some advanced printer filter which is able to properly format +# e-mail messages for printing. +# +# +# set print_split=no +# +# Name: print_split +# Type: boolean +# Default: no +# +# +# Used in connection with the command. If this option +# is set, the command specified by $print_command is executed once for +# each message which is to be printed. If this option is unset, +# the command specified by $print_command is executed only once, and +# all the messages are concatenated, with a form feed as the message +# separator. +# +# Those who use the enscript(1) program's mail-printing mode will +# most likely want to set this option. +# +# +# set prompt_after=yes +# +# Name: prompt_after +# Type: boolean +# Default: yes +# +# +# If you use an external $pager, setting this variable will +# cause Mutt to prompt you for a command when the pager exits rather +# than returning to the index menu. If unset, Mutt will return to the +# index menu when the external pager exits. +# +# +# set query_command="" +# +# Name: query_command +# Type: path +# Default: "" +# +# +# 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. +# +# +# set query_format="%4c %t %-25.25a %-25.25n %?e?(%e)?" +# +# Name: query_format +# Type: string +# Default: "%4c %t %-25.25a %-25.25n %?e?(%e)?" +# +# +# This variable describes the format of the ``query'' menu. The +# following printf(3)-style sequences are understood: +# %a destination address +# %c current entry number +# %e extra information * +# %n destination name +# %t ``*'' if current entry is tagged, a space otherwise +# %>X right justify the rest of the string and pad with ``X'' +# %|X pad to the end of the line with ``X'' +# %*X soft-fill with character ``X'' as pad +# +# +# For an explanation of ``soft-fill'', see the $index_format documentation. +# +# * = can be optionally printed if nonzero, see the $status_format documentation. +# +# +# set quit=yes +# +# Name: quit +# Type: quadoption +# Default: yes +# +# +# This variable controls whether ``quit'' and ``exit'' actually quit +# from mutt. If this option is set, they do quit, if it is unset, 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. +# +# +# set quote_regexp="^([ \t]*[|>:}#])+" +# +# Name: quote_regexp +# Type: regular expression +# Default: "^([ \t]*[|>:}#])+" +# +# +# A regular expression used in the internal pager to determine quoted +# sections of text in the body of a message. Quoted text may be filtered +# out using the command, or colored according to the +# ``color quoted'' family of directives. +# +# Higher levels of quoting may be colored differently (``color quoted1'', +# ``color quoted2'', etc.). The quoting level is determined by removing +# the last character from the matched text and recursively reapplying +# the regular expression until it fails to produce a match. +# +# Match detection may be overridden by the $smileys regular expression. +# +# +# set read_inc=10 +# +# Name: read_inc +# Type: number +# Default: 10 +# +# +# If set to a value greater than 0, Mutt will display which message it +# is currently on when reading a mailbox or when performing search actions +# such as search and limit. The message is printed after +# this many messages have been read or searched (e.g., if set to 25, Mutt will +# print a message when it is at message 25, and then again when it gets +# to message 50). This variable is meant to indicate progress when +# reading or searching large mailboxes which may take some time. +# When set to 0, only a single message will appear before the reading +# the mailbox. +# +# Also see the $write_inc, $net_inc and $time_inc variables and the +# ``tuning'' section of the manual for performance considerations. +# +# +# set read_only=no +# +# Name: read_only +# Type: boolean +# Default: no +# +# +# If set, all folders are opened in read-only mode. +# +# +# set realname="" +# +# Name: realname +# Type: string +# Default: "" +# +# +# This variable specifies what ``real'' or ``personal'' name should be used +# when sending messages. +# +# By default, this is the GECOS field from /etc/passwd. Note that this +# variable will not be used when the user has set a real name +# in the $from variable. +# +# +# set recall=ask-yes +# +# Name: recall +# Type: quadoption +# Default: ask-yes +# +# +# Controls whether or not Mutt recalls postponed messages +# when composing a new message. +# +# Setting this variable to is not generally useful, and thus not +# recommended. +# +# Also see $postponed variable. +# +# +# set record="~/sent" +# +# Name: record +# Type: path +# Default: "~/sent" +# +# +# This specifies the file into which your outgoing messages should be +# appended. (This is meant as the primary method for saving a copy of +# your messages, but another way to do this is using the ``my_hdr'' +# command to create a ``Bcc:'' field with your email address in it.) +# +# The value of $record is overridden by the $force_name and +# $save_name variables, and the ``fcc-hook'' command. +# +# +# set reply_regexp="^(re([\\[0-9\\]+])*|aw):[ \t]*" +# +# Name: reply_regexp +# Type: regular expression +# Default: "^(re([\\[0-9\\]+])*|aw):[ \t]*" +# +# +# A regular expression used to recognize reply messages when threading +# and replying. The default value corresponds to the English "Re:" and +# the German "Aw:". +# +# +# set reply_self=no +# +# Name: reply_self +# Type: boolean +# Default: no +# +# +# If unset and you are replying to a message sent by you, Mutt will +# assume that you want to reply to the recipients of that message rather +# than to yourself. +# +# Also see the ``alternates'' command. +# +# +# set reply_to=ask-yes +# +# Name: reply_to +# Type: quadoption +# Default: ask-yes +# +# +# If set, when replying to a message, Mutt will use the address listed +# in the Reply-to: header as the recipient of the reply. If unset, +# it will use the address in the From: header field instead. This +# option is useful for reading a mailing list that sets the Reply-To: +# header field to the list address and you want to send a private +# message to the author of a message. +# +# +# set resolve=yes +# +# Name: resolve +# Type: boolean +# Default: yes +# +# +# When set, the cursor will be automatically advanced to the next +# (possibly undeleted) message whenever a command that modifies the +# current message is executed. +# +# +# set reverse_alias=no +# +# Name: reverse_alias +# Type: boolean +# Default: no +# +# +# This variable controls whether or not Mutt will display the ``personal'' +# name from your aliases in the index menu if it finds an alias that +# matches the message's sender. For example, if you have the following +# alias: +# 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. +# +# +# set reverse_name=no +# +# Name: reverse_name +# Type: boolean +# Default: no +# +# +# It may sometimes arrive that you receive mail to a certain machine, +# move the messages to another machine, and reply to some the messages +# from there. If this variable is set, the default From: line of +# the reply messages is built using the address where you received the +# messages you are replying to if that address matches your +# ``alternates''. If the variable is unset, or the address that would be +# used doesn't match your ``alternates'', the From: line will use +# your address on the current machine. +# +# Also see the ``alternates'' command. +# +# +# set reverse_realname=yes +# +# Name: reverse_realname +# Type: boolean +# Default: yes +# +# +# This variable fine-tunes the behaviour of the $reverse_name feature. +# When it is set, mutt will use the address from incoming messages as-is, +# possibly including eventual real names. When it is unset, mutt will +# override any such real names with the setting of the $realname variable. +# +# +# set rfc2047_parameters=no +# +# Name: rfc2047_parameters +# Type: boolean +# Default: no +# +# +# When this variable is set, Mutt will decode RFC2047-encoded MIME +# parameters. You want to set this variable when mutt suggests you +# to save attachments to files named like: +# =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?= +# +# When this variable is set interactively, the change won't be +# active until you change folders. +# +# Note that this use of RFC2047's encoding is explicitly +# prohibited by the standard, but nevertheless encountered in the +# wild. +# +# Also note that setting this parameter will not have the effect +# that mutt generates this kind of encoding. Instead, mutt will +# unconditionally use the encoding specified in RFC2231. +# +# +# set save_address=no +# +# Name: save_address +# Type: boolean +# Default: no +# +# +# If set, mutt will take the sender's full address when choosing a +# 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. +# +# +# set save_empty=yes +# +# Name: save_empty +# Type: boolean +# Default: yes +# +# +# When unset, mailboxes which contain no saved messages will be removed +# when closed (the exception is $spoolfile which is never removed). +# If set, mailboxes are never removed. +# +# Note: This only applies to mbox and MMDF folders, Mutt does not +# delete MH and Maildir directories. +# +# +# set save_history=0 +# +# Name: save_history +# Type: number +# Default: 0 +# +# +# This variable controls the size of the history (per category) saved in the +# $history_file file. +# +# +# set save_name=no +# +# Name: save_name +# Type: boolean +# Default: no +# +# +# This variable controls how copies of outgoing messages are saved. +# When set, a check is made to see if a mailbox specified by the +# recipient address exists (this is done by searching for a mailbox in +# the $folder directory with the username part of the +# recipient address). If the mailbox exists, the outgoing message will +# be saved to that mailbox, otherwise the message is saved to the +# $record mailbox. +# +# Also see the $force_name variable. +# +# +# set score=yes +# +# Name: score +# Type: boolean +# Default: yes +# +# +# When this variable is unset, scoring is turned off. This can +# be useful to selectively disable scoring for certain folders when the +# $score_threshold_delete variable and related are used. +# +# +# set score_threshold_delete=-1 +# +# Name: score_threshold_delete +# Type: number +# Default: -1 +# +# +# Messages which have been assigned a score equal to or lower than the value +# of this variable are automatically marked for deletion by mutt. Since +# mutt scores are always greater than or equal to zero, the default setting +# of this variable will never mark a message for deletion. +# +# +# set score_threshold_flag=9999 +# +# Name: score_threshold_flag +# Type: number +# Default: 9999 +# +# +# Messages which have been assigned a score greater than or equal to this +# variable's value are automatically marked "flagged". +# +# +# set score_threshold_read=-1 +# +# Name: score_threshold_read +# Type: number +# Default: -1 +# +# +# Messages which have been assigned a score equal to or lower than the value +# of this variable are automatically marked as read by mutt. Since +# mutt scores are always greater than or equal to zero, the default setting +# of this variable will never mark a message read. +# +# +# set send_charset="us-ascii:iso-8859-1:utf-8" +# +# Name: send_charset +# Type: string +# Default: "us-ascii:iso-8859-1:utf-8" +# +# +# A colon-delimited list of character sets for outgoing messages. Mutt will use the +# first character set into which the text can be converted exactly. +# If your $charset is not ``iso-8859-1'' and recipients may not +# understand ``UTF-8'', it is advisable to include in the list an +# appropriate widely used standard character set (such as +# ``iso-8859-2'', ``koi8-r'' or ``iso-2022-jp'') either instead of or after +# ``iso-8859-1''. +# +# In case the text cannot be converted into one of these exactly, +# mutt uses $charset as a fallback. +# +# +# set sendmail="/usr/sbin/sendmail -oem -oi" +# +# Name: sendmail +# Type: path +# Default: "/usr/sbin/sendmail -oem -oi" +# +# +# Specifies the program and arguments used to deliver mail sent by Mutt. +# Mutt expects that the specified program interprets additional +# arguments as recipient addresses. +# +# +# set sendmail_wait=0 +# +# Name: sendmail_wait +# Type: number +# Default: 0 +# +# +# Specifies the number of seconds to wait for the $sendmail process +# to finish before giving up and putting delivery in the background. +# +# Mutt interprets the value of this variable as follows: +# >0 number of seconds to wait for sendmail to finish before continuing +# 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. +# +# +# set shell="" +# +# Name: shell +# Type: path +# Default: "" +# +# +# Command to use when spawning a subshell. By default, the user's login +# shell from /etc/passwd is used. +# +# +# set sig_dashes=yes +# +# Name: sig_dashes +# Type: boolean +# Default: yes +# +# +# If set, a line containing ``-- '' (note the trailing space) will be inserted before your +# $signature. It is strongly recommended that you not unset +# this variable unless your signature contains just your name. The +# reason for this is because many software packages use ``-- \n'' to +# detect your signature. For example, Mutt has the ability to highlight +# the signature in a different color in the builtin pager. +# +# +# set sig_on_top=no +# +# Name: sig_on_top +# Type: boolean +# Default: no +# +# +# If set, the signature will be included before any quoted or forwarded +# text. It is strongly recommended that you do not set this variable +# unless you really know what you are doing, and are prepared to take +# some heat from netiquette guardians. +# +# +# set signature="~/.signature" +# +# Name: signature +# Type: path +# Default: "~/.signature" +# +# +# Specifies the filename of your signature, which is appended to all +# 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 standard output. +# +# +# set simple_search="~f %s | ~s %s" +# +# Name: simple_search +# Type: string +# Default: "~f %s | ~s %s" +# +# +# 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 ``~'' pattern +# operators. See ``patterns'' 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 by +# replacing ``%s'' with the supplied string. +# For the default value, ``joe'' would be expanded to: ``~f joe | ~s joe''. +# +# +# set smart_wrap=yes +# +# Name: smart_wrap +# Type: boolean +# Default: yes +# +# +# Controls the display of lines longer than the screen width in the +# internal pager. If set, long lines are wrapped at a word boundary. If +# unset, lines are simply wrapped at the screen edge. Also see the +# $markers variable. +# +# +# set smileys="(>From )|(:[-^]?[][)(><}{|/DP])" +# +# Name: smileys +# Type: regular expression +# Default: "(>From )|(:[-^]?[][)(><}{|/DP])" +# +# +# The pager uses this variable to catch some common false +# positives of $quote_regexp, most notably smileys and not consider +# a line quoted text if it also matches $smileys. This mostly +# happens at the beginning of a line. +# +# +# set sleep_time=1 +# +# Name: sleep_time +# Type: number +# Default: 1 +# +# +# Specifies time, in seconds, to pause while displaying certain informational +# messages, while moving from folder to folder and after expunging +# messages from the current folder. The default is to pause one second, so +# a value of zero for this option suppresses the pause. +# +# +# set smtp_authenticators="" +# +# Name: smtp_authenticators +# Type: string +# Default: "" +# +# +# This is a colon-delimited list of authentication methods mutt may +# attempt to use to log in to an SMTP server, in the order mutt should +# try them. Authentication methods are any SASL mechanism, eg +# ``digest-md5'', ``gssapi'' or ``cram-md5''. +# This option is case-insensitive. If it is ``unset'' +# (the default) mutt will try all available methods, in order from +# most-secure to least-secure. +# +# Example: +# set smtp_authenticators="digest-md5:cram-md5" +# +# +# set smtp_pass="" +# +# Name: smtp_pass +# Type: string +# Default: "" +# +# +# Specifies the password for your SMTP account. If unset, Mutt will +# prompt you for your password when you first send mail via SMTP. +# See $smtp_url to configure mutt to send mail via SMTP. +# +# Warning: you should only use this option when you are on a +# fairly secure machine, because the superuser can read your muttrc even +# if you are the only one who can read the file. +# +# +# set smtp_url="" +# +# Name: smtp_url +# Type: string +# Default: "" +# +# +# Defines the SMTP smarthost where sent messages should relayed for +# delivery. This should take the form of an SMTP URL, eg: +# smtp[s]://[user[:pass]@]host[:port]/ +# +# \.\.\. where ``[...]'' denotes an optional part. +# Setting this variable overrides the value of the $sendmail +# variable. +# +# +# set sort=date +# +# Name: sort +# Type: sort order +# Default: date +# +# +# Specifies how to sort messages in the ``index'' menu. Valid values +# are: +# - date or date-sent +# - date-received +# - from +# - mailbox-order (unsorted) +# - score +# - size +# - spam +# - subject +# - threads +# - to +# +# +# You may optionally use the ``reverse-'' prefix to specify reverse sorting +# order (example: ``set sort=reverse-date-sent''). +# +# Note: On Debian systems, this option is set by default to +# ``threads'' in /etc/Muttrc. +# +# +# set sort_alias=alias +# +# Name: sort_alias +# Type: sort order +# Default: alias +# +# +# Specifies how the entries in the ``alias'' menu are sorted. The +# following are legal values: +# - address (sort alphabetically by email address) +# - alias (sort alphabetically by alias name) +# - unsorted (leave in order specified in .muttrc) +# +# +# set sort_aux=date +# +# Name: sort_aux +# Type: sort order +# Default: date +# +# +# When sorting by threads, this variable controls how threads are sorted +# in relation to other threads, and how the branches of the thread trees +# are sorted. This can be set to any value that $sort can, except +# ``threads'' (in that case, mutt will just use ``date-sent''). You can also +# specify the ``last-'' prefix in addition to the ``reverse-'' prefix, but ``last-'' +# must come after ``reverse-''. The ``last-'' prefix causes messages to be +# sorted against its siblings by which has the last descendant, using +# the rest of $sort_aux as an ordering. For instance, +# set sort_aux=last-date-received +# +# would mean that if a new message is received in a +# thread, that thread becomes the last one displayed (or the first, if +# you have ``set sort=reverse-threads''.) +# +# Note: For reversed $sort +# order $sort_aux is reversed again (which is not the right thing to do, +# but kept to not break any existing configuration setting). +# +# +# set sort_browser=alpha +# +# Name: sort_browser +# Type: sort order +# Default: alpha +# +# +# Specifies how to sort entries in the file browser. By default, the +# entries are sorted alphabetically. Valid values: +# - alpha (alphabetically) +# - date +# - size +# - unsorted +# +# +# You may optionally use the ``reverse-'' prefix to specify reverse sorting +# order (example: ``set sort_browser=reverse-date''). +# +# +# set sort_re=yes +# +# Name: sort_re +# Type: boolean +# Default: yes +# +# +# This variable is only useful when sorting by threads with +# $strict_threads unset. In that case, it changes the heuristic +# mutt uses to thread messages by subject. With $sort_re set, mutt will +# only attach a message as the child of another message by subject if +# the subject of the child message starts with a substring matching the +# setting of $reply_regexp. With $sort_re unset, mutt will attach +# the message whether or not this is the case, as long as the +# non-$reply_regexp parts of both messages are identical. +# +# +# set spam_separator="," +# +# Name: spam_separator +# Type: string +# Default: "," +# +# +# This variable controls what happens when multiple spam headers +# are matched: if unset, each successive header will overwrite any +# previous matches value for the spam label. If set, each successive +# match will append to the previous, using this variable's value as a +# separator. +# +# +# set spoolfile="" +# +# Name: spoolfile +# Type: path +# Default: "" +# +# +# If your spool mailbox is in a non-default place where Mutt cannot find +# it, you can specify its location with this variable. Mutt will +# automatically set this variable to the value of the environment +# variable $MAIL if it is not set. +# +# +# set status_chars="-*%A" +# +# Name: status_chars +# Type: string +# Default: "-*%A" +# +# +# Controls the characters used by the ``%r'' indicator in +# $status_format. The first character is used when the mailbox is +# unchanged. The second is used when the mailbox has been changed, and +# it needs to be resynchronized. The third is used if the mailbox is in +# 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 operation, bound by default to ``%''). The fourth +# is used to indicate that the current folder has been opened in attach- +# message mode (Certain operations like composing a new mail, replying, +# forwarding, etc. are not permitted in this mode). +# +# +# set status_format="-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---" +# +# Name: status_format +# Type: string +# Default: "-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---" +# +# +# Controls the format of the status line displayed in the ``index'' +# menu. This string is similar to $index_format, but has its own +# set of printf(3)-like sequences: +# %b number of mailboxes with new mail * +# %d number of deleted messages * +# %f the full pathname of the current mailbox +# %F number of flagged messages * +# %h local hostname +# %l size (in bytes) of the current mailbox * +# %L size (in bytes) of the messages shown +# (i.e., which match the current limit) * +# %m the number of messages in the mailbox * +# %M the number of messages shown (i.e., which match the current limit) * +# %n number of new messages in the mailbox * +# %o number of old unread messages * +# %p number of postponed messages * +# %P percentage of the way through the index +# %r modified/read-only/won't-write/attach-message indicator, +# according to $status_chars +# %s current sorting mode ($sort) +# %S current aux sorting method ($sort_aux) +# %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'' +# %*X soft-fill with character ``X'' as pad +# +# +# For an explanation of ``soft-fill'', see the $index_format documentation. +# +# * = 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 sequence_char is a character from the table above, and +# optional_string is the string you would like printed if +# sequence_char is nonzero. optional_string may contain +# other sequences as well as normal text, but you may not nest +# optional strings. +# +# Here is an example illustrating how to optionally print the number of +# new messages in a mailbox: +# +# %?n?%n new messages.? +# +# You can also switch between two strings using the following construct: +# +# %??&? +# +# If the value of sequence_char is non-zero, if_string will +# be expanded, otherwise else_string will be expanded. +# +# You can force the result of any printf(3)-like sequence to be lowercase +# by prefixing the sequence character with an underscore (``_'') sign. +# For example, if you want to display the local hostname in lowercase, +# you would use: ``%_h''. +# +# If you prefix the sequence character with a colon (``:'') character, mutt +# will replace any dots in the expansion by underscores. This might be helpful +# with IMAP folders that don't like dots in folder names. +# +# +# set status_on_top=no +# +# Name: status_on_top +# Type: boolean +# Default: no +# +# +# Setting this variable causes the ``status bar'' to be displayed on +# the first line of the screen rather than near the bottom. If $help +# is set, too it'll be placed at the bottom. +# +# +# set strict_threads=no +# +# Name: strict_threads +# Type: boolean +# Default: no +# +# +# If set, threading will only make use of the ``In-Reply-To'' and +# ``References:'' fields when you $sort by message threads. By +# default, messages with the same subject are grouped together in +# ``pseudo threads.''. This may not always be desirable, such as in a +# personal mailbox where you might have several unrelated messages with +# the subjects like ``hi'' which will get grouped together. See also +# $sort_re for a less drastic way of controlling this +# behaviour. +# +# +# set suspend=yes +# +# Name: suspend +# Type: boolean +# Default: yes +# +# +# When unset, mutt won't stop when the user presses the terminal's +# susp key, usually ``^Z''. This is useful if you run mutt +# inside an xterm using a command like ``xterm -e mutt''. +# +# +# set text_flowed=no +# +# Name: text_flowed +# Type: boolean +# Default: no +# +# +# When set, mutt will generate ``format=flowed'' bodies with a content type +# of ``text/plain; format=flowed''. +# This format is easier to handle for some mailing software, and generally +# just looks like ordinary text. To actually make use of this format's +# features, you'll need support in your editor. +# +# Note that $indent_string is ignored when this option is set. +# +# +# set thread_received=no +# +# Name: thread_received +# Type: boolean +# Default: no +# +# +# When set, mutt uses the date received rather than the date sent +# to thread messages by subject. +# +# +# set thorough_search=no +# +# Name: thorough_search +# Type: boolean +# Default: no +# +# +# Affects the ~b and ~h search operations described in +# section ``patterns''. If set, the headers and body/attachments of +# messages to be searched are decoded before searching. If unset, +# messages are searched as they appear in the folder. +# +# Users searching attachments or for non-ASCII characters should set +# this value because decoding also includes MIME parsing/decoding and possible +# character set conversions. Otherwise mutt will attempt to match against the +# raw message received (for example quoted-printable encoded or with encoded +# headers) which may lead to incorrect search results. +# +# +# set tilde=no +# +# Name: tilde +# Type: boolean +# Default: no +# +# +# When set, the internal-pager will pad blank lines to the bottom of the +# screen with a tilde (``~''). +# +# +# set time_inc=0 +# +# Name: time_inc +# Type: number +# Default: 0 +# +# +# Along with $read_inc, $write_inc, and $net_inc, this +# variable controls the frequency with which progress updates are +# displayed. It suppresses updates less than $time_inc milliseconds +# apart. This can improve throughput on systems with slow terminals, +# or when running mutt on a remote system. +# +# Also see the ``tuning'' section of the manual for performance considerations. +# +# +# set timeout=600 +# +# Name: timeout +# Type: number +# Default: 600 +# +# +# When Mutt is waiting for user input either idleing in menus or +# in an interactive prompt, Mutt would block until input is +# present. Depending on the context, this would prevent certain +# operations from working, like checking for new mail or keeping +# an IMAP connection alive. +# +# This variable controls how many seconds Mutt will at most wait +# until it aborts waiting for input, performs these operations and +# continues to wait for input. +# +# A value of zero or less will cause Mutt to never time out. +# +# +# set tmpdir="" +# +# Name: tmpdir +# Type: path +# Default: "" +# +# +# This variable allows you to specify where Mutt will place its +# temporary files needed for displaying and composing messages. If +# this variable is not set, the environment variable $TMPDIR is +# used. If $TMPDIR is not set then ``/tmp'' is used. +# +# +# set to_chars=" +TCFL" +# +# Name: to_chars +# Type: string +# Default: " +TCFL" +# +# +# Controls the character used to indicate mail addressed to you. The +# first character is the one used when the mail is not addressed to your +# address. The second is used when you are the only +# recipient of the message. The third is when your address +# appears in the ``To:'' header field, but you are not the only recipient of +# the message. The fourth character is used when your +# address is specified in the ``Cc:'' header field, but you are not the only +# recipient. The fifth character is used to indicate mail that was sent +# by you. The sixth character is used to indicate when a mail +# was sent to a mailing-list you subscribe to. +# +# +# set trash="" +# +# Name: trash +# Type: path +# Default: "" +# +# +# If set, this variable specifies the path of the trash folder where the +# mails marked for deletion will be moved, instead of being irremediably +# purged. +# +# NOTE: When you delete a message in the trash folder, it is really +# deleted, so that you have a way to clean the trash. +# +# +# set tunnel="" +# +# Name: tunnel +# Type: string +# Default: "" +# +# +# Setting this variable will cause mutt to open a pipe to a command +# instead of a raw socket. You may be able to use this to set up +# preauthenticated connections to your IMAP/POP3/SMTP server. Example: +# set tunnel="ssh -q mailhost.net /usr/local/libexec/imapd" +# +# Note: For this example to work you must be able to log in to the remote +# machine without having to enter a password. +# +# +# set use_8bitmime=no +# +# Name: use_8bitmime +# Type: boolean +# Default: no +# +# +# Warning: do not set this variable unless you are using a version +# of sendmail which supports the -B8BITMIME flag (such as sendmail +# 8.8.x) or you may not be able to send mail. +# +# When set, Mutt will invoke $sendmail with the -B8BITMIME +# flag when sending 8-bit messages to enable ESMTP negotiation. +# +# +# set use_domain=yes +# +# Name: use_domain +# Type: boolean +# Default: yes +# +# +# When set, Mutt will qualify all local addresses (ones without the +# ``@host'' portion) with the value of $hostname. If unset, no +# addresses will be qualified. +# +# +# set use_envelope_from=no +# +# Name: use_envelope_from +# Type: boolean +# Default: no +# +# +# When set, mutt will set the envelope sender of the message. +# If $envelope_from_address is set, it will be used as the sender +# address. If unset, mutt will attempt to derive the sender from the +# ``From:'' header. +# +# Note that this information is passed to sendmail command using the +# -f command line switch. Therefore setting this option is not useful +# if the $sendmail variable already contains -f or if the +# executable pointed to by $sendmail doesn't support the -f switch. +# +# +# set use_from=yes +# +# Name: use_from +# Type: boolean +# Default: yes +# +# +# When set, Mutt will generate the ``From:'' header field when +# sending messages. If unset, no ``From:'' header field will be +# generated unless the user explicitly sets one using the ``my_hdr'' +# command. +# +# +# set use_idn=yes +# +# Name: use_idn +# Type: boolean +# Default: yes +# +# +# When set, Mutt will show you international domain names decoded. +# Note: You can use IDNs for addresses even if this is unset. +# This variable only affects decoding. +# +# +# set use_ipv6=yes +# +# Name: use_ipv6 +# Type: boolean +# Default: yes +# +# +# When set, Mutt will look for IPv6 addresses of hosts it tries to +# contact. If this option is unset, Mutt will restrict itself to IPv4 addresses. +# Normally, the default should work. +# +# +# set user_agent=yes +# +# Name: user_agent +# Type: boolean +# Default: yes +# +# +# When set, mutt will add a ``User-Agent:'' header to outgoing +# messages, indicating which version of mutt was used for composing +# them. +# +# +# set visual="" +# +# Name: visual +# Type: path +# Default: "" +# +# +# Specifies the visual editor to invoke when the ``~v'' command is +# given in the builtin editor. +# +# +# set wait_key=yes +# +# Name: wait_key +# Type: boolean +# Default: yes +# +# +# Controls whether Mutt will ask you to press a key after an external command +# has been invoked by these functions: , +# , , , +# and commands. +# +# It is also used when viewing attachments with ``auto_view'', provided +# that the corresponding mailcap entry has a needsterminal flag, +# and the external program is interactive. +# +# 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. +# +# +# set weed=yes +# +# Name: weed +# Type: boolean +# Default: yes +# +# +# When set, mutt will weed headers when displaying, forwarding, +# printing, or replying to messages. +# +# +# set wrap=0 +# +# Name: wrap +# Type: number +# Default: 0 +# +# +# When set to a positive value, mutt will wrap text at $wrap characters. +# When set to a negative value, mutt will wrap text so that there are $wrap +# characters of empty space on the right side of the terminal. +# +# +# set wrap_search=yes +# +# Name: wrap_search +# Type: boolean +# Default: yes +# +# +# Controls whether searches wrap around the end. +# +# When set, searches will wrap around the first (or last) item. When +# unset, incremental searches will not wrap. +# +# +# set wrapmargin=0 +# +# Name: wrapmargin +# Type: number +# Default: 0 +# +# +# (DEPRECATED) Equivalent to setting $wrap with a negative value. +# +# +# set write_inc=10 +# +# Name: write_inc +# Type: number +# Default: 10 +# +# +# When writing a mailbox, a message will be printed every +# $write_inc messages to indicate progress. If set to 0, only a +# single message will be displayed before writing a mailbox. +# +# Also see the $read_inc, $net_inc and $time_inc variables and the +# ``tuning'' section of the manual for performance considerations. +# +# +# set write_bcc=yes +# +# Name: write_bcc +# Type: boolean +# Default: yes +# +# +# Controls whether mutt writes out the ``Bcc:'' header when preparing +# messages to be sent. Exim users may wish to unset this. If mutt +# is set to deliver directly via SMTP (see $smtp_url), this +# option does nothing: mutt will never write out the ``Bcc:'' header +# in this case. +# +# Note: On Debian systems, exim4 and postfix strip BCC headers by +# default. The above warning applies to exim3 users, see /etc/Muttrc. +# +# +# set xterm_icon="M%?n?AIL&ail?" +# +# Name: xterm_icon +# Type: string +# Default: "M%?n?AIL&ail?" +# +# +# Controls the format of the icon title, as long as xterm_set_titles +# is enabled. This string is identical in formatting to the one used by +# ``$status_format''. +# +# +# set xterm_set_titles=no +# +# Name: xterm_set_titles +# Type: boolean +# Default: no +# +# +# Controls whether mutt sets the xterm title bar and icon name +# (as long as you are in an appropriate terminal). +# +# +# set xterm_title="Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?" +# +# Name: xterm_title +# Type: string +# Default: "Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?" +# +# +# Controls the format of the title bar of the xterm provided that +# xterm_set_titles has been set. This string is identical in formatting +# to the one used by ``$status_format''. +# +# diff --git a/obj-i486-linux-gnu-patched/doc/advancedusage.html b/obj-i486-linux-gnu-patched/doc/advancedusage.html new file mode 100644 index 0000000..789f716 --- /dev/null +++ b/obj-i486-linux-gnu-patched/doc/advancedusage.html @@ -0,0 +1,609 @@ + + +Chapter 4. Advanced Usage

Chapter 4. Advanced Usage
Prev   Next

Chapter 4. Advanced Usage

Table of Contents

1. Regular Expressions
2. Patterns: Searching, Limiting and Tagging
2.1. Pattern Modifier
2.2. Simple Patterns
2.3. Complex Patterns
2.4. Searching by Date
3. Using Tags
4. Using Hooks
4.1. Message Matching in Hooks
5. External Address Queries
6. Mailbox Formats
7. Mailbox Shortcuts
8. Handling Mailing Lists
9. Handling multiple folders
10. Editing threads
10.1. Linking threads
10.2. Breaking threads
11. Delivery Status Notification (DSN) Support
12. Start a WWW Browser on URLs

1. Regular Expressions

+All string patterns in Mutt including those in more complex +patterns must be specified +using regular expressions (regexp) in the “POSIX extended” syntax (which +is more or less the syntax used by egrep and GNU awk). For your +convenience, we have included below a brief description of this syntax. +

+The search is case sensitive if the pattern contains at least one upper +case letter, and case insensitive otherwise. +

Note

+Note that “\” +must be quoted if used for a regular expression in an initialization +command: “\\”. +

+A regular expression is a pattern that describes a set of strings. +Regular expressions are constructed analogously to arithmetic +expressions, by using various operators to combine smaller expressions. +

Note

+Note that the regular expression can be enclosed/delimited by either " +or ' which is useful if the regular expression includes a white-space +character. See Syntax of Initialization Files +for more information on " and ' delimiter processing. To match a +literal " or ' you must preface it with \ (backslash). +

+The fundamental building blocks are the regular expressions that match +a single character. Most characters, including all letters and digits, +are regular expressions that match themselves. Any metacharacter with +special meaning may be quoted by preceding it with a backslash. +

+The period “.” matches any single character. The caret “^” and +the dollar sign “$” are metacharacters that respectively match +the empty string at the beginning and end of a line. +

+A list of characters enclosed by “[” and “]” matches any +single character in that list; if the first character of the list +is a caret “^” then it matches any character not in the +list. For example, the regular expression [0123456789] +matches any single digit. A range of ASCII characters may be specified +by giving the first and last characters, separated by a hyphen +“-”. Most metacharacters lose their special meaning inside +lists. To include a literal “]” place it first in the list. +Similarly, to include a literal “^” place it anywhere but first. +Finally, to include a literal hyphen “-” place it last. +

+Certain named classes of characters are predefined. Character classes +consist of “[:”, a keyword denoting the class, and “:]”. +The following classes are defined by the POSIX standard in +Table 4.1, “POSIX regular expression character classes” +

Table 4.1. POSIX regular expression character classes

Character classDescription
[:alnum:]Alphanumeric characters
[:alpha:]Alphabetic characters
[:blank:]Space or tab characters
[:cntrl:]Control characters
[:digit:]Numeric characters
[:graph:]Characters that are both printable and visible. (A space is printable, but not visible, while an “a” is both)
[:lower:]Lower-case alphabetic characters
[:print:]Printable characters (characters that are not control characters)
[:punct:]Punctuation characters (characters that are not letter, digits, control characters, or space characters)
[:space:]Space characters (such as space, tab and formfeed, to name a few)
[:upper:]Upper-case alphabetic characters
[:xdigit:]Characters that are hexadecimal digits

+A character class is only valid in a regular expression inside the +brackets of a character list. +

Note

+Note that the brackets in these +class names are part of the symbolic names, and must be included +in addition to the brackets delimiting the bracket list. For +example, [[:digit:]] is equivalent to +[0-9]. +

+Two additional special sequences can appear in character lists. These +apply to non-ASCII character sets, which can have single symbols (called +collating elements) that are represented with more than one character, +as well as several characters that are equivalent for collating or +sorting purposes: +

Collating Symbols

+A collating symbol is a multi-character collating element enclosed in +“[.” and “.]”. For example, if “ch” is a collating +element, then [[.ch.]] is a regexp that matches +this collating element, while [ch] is a regexp that +matches either “c” or “h”. +

Equivalence Classes

+An equivalence class is a locale-specific name for a list of +characters that are equivalent. The name is enclosed in “[=” +and “=]”. For example, the name “e” might be used to +represent all of “è” “é” and “e”. In this case, +[[=e=]] is a regexp that matches any of +“è”, “é” and “e”. +

+A regular expression matching a single character may be followed by one +of several repetition operators described in Table 4.2, “Regular expression repetition operators”. +

Table 4.2. Regular expression repetition operators

OperatorDescription
?The preceding item is optional and matched at most once
*The preceding item will be matched zero or more times
+The preceding item will be matched one or more times
{n}The preceding item is matched exactly n times
{n,}The preceding item is matched n or more times
{,m}The preceding item is matched at most m times
{n,m}The preceding item is matched at least n times, but no more than m times

+Two regular expressions may be concatenated; the resulting regular +expression matches any string formed by concatenating two substrings +that respectively match the concatenated subexpressions. +

+Two regular expressions may be joined by the infix operator “|”; +the resulting regular expression matches any string matching either +subexpression. +

+Repetition takes precedence over concatenation, which in turn takes +precedence over alternation. A whole subexpression may be enclosed in +parentheses to override these precedence rules. +

Note

+If you compile Mutt with the GNU rx package, the +following operators may also be used in regular expressions as described in Table 4.3, “GNU regular expression extensions”. +

Table 4.3. GNU regular expression extensions

ExpressionDescription
\\yMatches the empty string at either the beginning or the end of a word
\\BMatches the empty string within a word
\\<Matches the empty string at the beginning of a word
\\>Matches the empty string at the end of a word
\\wMatches any word-constituent character (letter, digit, or underscore)
\\WMatches any character that is not word-constituent
\\`Matches the empty string at the beginning of a buffer (string)
\\'Matches the empty string at the end of a buffer

+Please note however that these operators are not defined by POSIX, so +they may or may not be available in stock libraries on various systems. +

2. Patterns: Searching, Limiting and Tagging

+Many of Mutt's commands allow you to specify a pattern to match +(limit, tag-pattern, +delete-pattern, etc.). Table 4.4, “Pattern modifiers” +shows several ways to select messages. +

Table 4.4. Pattern modifiers

Pattern modifierDescription
~Aall messages
~b EXPRmessages which contain EXPR in the message body
=b STRINGmessages which contain STRING in the message body. If IMAP is enabled, searches for STRING on the server, rather than downloading each message and searching it locally.
~B EXPRmessages which contain EXPR in the whole message
~c EXPRmessages carbon-copied to EXPR
%c GROUPmessages carbon-copied to any member of GROUP
~C EXPRmessages either to: or cc: EXPR
%C GROUPmessages either to: or cc: to any member of GROUP
~d [MIN]-[MAX]messages with “date-sent” in a Date range
~Ddeleted messages
~e EXPRmessages which contains EXPR in the “Sender” field
%e GROUPmessages which contain a member of GROUP in the “Sender” field
~Eexpired messages
~Fflagged messages
~f EXPRmessages originating from EXPR
%f GROUPmessages originating from any member of GROUP
~gcryptographically signed messages
~Gcryptographically encrypted messages
~h EXPRmessages which contain EXPR in the message header
~H EXPRmessages with a spam attribute matching EXPR
~i EXPRmessages which match EXPR in the “Message-ID” field
~kmessages which contain PGP key material
~L EXPRmessages either originated or received by EXPR
%L GROUPmessage either originated or received by any member of GROUP
~lmessages addressed to a known mailing list
~m [MIN]-[MAX]messages in the range MIN to MAX *)
~n [MIN]-[MAX]messages with a score in the range MIN to MAX *)
~Nnew messages
~Oold messages
~pmessages addressed to you (consults alternates)
~Pmessages from you (consults alternates)
~Qmessages which have been replied to
~r [MIN]-[MAX]messages with “date-received” in a Date range
~Rread messages
~s EXPRmessages having EXPR in the “Subject” field.
~Ssuperseded messages
~t EXPRmessages addressed to EXPR
~Ttagged messages
~umessages addressed to a subscribed mailing list
~Uunread messages
~vmessages part of a collapsed thread.
~Vcryptographically verified messages
~x EXPRmessages which contain EXPR in the “References” field
~X [MIN]-[MAX]messages with MIN to MAX attachments *)
~y EXPRmessages which contain EXPR in the “X-Label” field
~z [MIN]-[MAX]messages with a size in the range MIN to MAX *)
~=duplicated messages (see $duplicate_threads)
~$unreferenced messages (requires threaded view)
~(PATTERN)messages in threads +containing messages matching PATTERN, e.g. all +threads containing messages from you: ~(~P)

+Where EXPR is a +regular expression. Special attention has to be +made when using regular expressions inside of patterns. Specifically, +Mutt's parser for these patterns will strip one level of backslash (“\”), +which is normally used for quoting. If it is your intention to use a +backslash in the regular expression, you will need to use two backslashes +instead (“\\”). You can force mutt to treat EXPR as a simple string +instead of a regular expression by using = instead of ˜ in the +pattern name. For example, =b *.* will find all messages that contain +the literal string “*.*”. Simple string matches are less powerful than +regular expressions but can be considerably faster. This is especially +true for IMAP folders, because string matches can be performed on the +server instead of by fetching every message. IMAP treats =h specially: +it must be of the form "header: substring" and will not partially +match header names. The substring part may be omitted if you simply +wish to find messages containing a particular header without regard to +its value. +

+*) The forms “<[MAX]”, “>[MIN]”, +“[MIN]-” and “-[MAX]” +are allowed, too. +

2.1. Pattern Modifier

Note

+Note that patterns matching 'lists' of addresses (notably c, C, p, P and t) +match if there is at least one match in the whole list. If you want to +make sure that all elements of that list match, you need to prefix your +pattern with “^”. +This example matches all mails which only has recipients from Germany. +

+^~C \.de$
+

2.2. Simple Patterns

+Mutt supports two versions of so called “simple searches” which are +issued if the query entered for searching, limiting and similar +operations does not seem to be a valid pattern (i.e. it does not contain +one of these characters: “˜”, “=” or “%”). If the query is +supposed to contain one of these special characters, they must be escaped +by prepending a backslash (“\”). +

+The first type is by checking whether the query string equals +a keyword case-insensitively from Table 4.5, “Simple search keywords”: +If that is the case, Mutt will use the shown pattern modifier instead. +If a keyword would conflict with your search keyword, you need to turn +it into a regular expression to avoid matching the keyword table. For +example, if you want to find all messages matching “flag” +(using $simple_search) +but don't want to match flagged messages, simply search for +“[f]lag”. +

Table 4.5. Simple search keywords

KeywordPattern modifier
all~A
.~A
^~A
del~D
flag~F
new~N
old~O
repl~Q
read~R
tag~T
unread~U

+The second type of simple search is to build a complex search +pattern using $simple_search +as a template. Mutt will insert your query properly quoted and search +for the composed complex query. +

2.3. Complex Patterns

+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 and that have the word “elkins” in the “From” header +field. +

+Mutt also recognizes the following operators to create more complex search +patterns: +

  • +! -- logical NOT operator +

  • +| -- logical OR operator +

  • +() -- 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”. +

Example 4.1. Using boolean operators in patterns

+!(~t mutt|~c mutt) ~f elkins
+

+Here is an example using white space in the regular expression (note +the ' and " delimiters). For this to match, the mail's subject must +match the “^Junk +From +Me$” and it must be from either “Jim +Somebody” +or “Ed +SomeoneElse”: +

+ '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
+

Note

+If a regular expression contains parenthesis, or a vertical bar +("|"), you must enclose the expression in double or single quotes since +those characters are also used to separate different parts of Mutt's +pattern language. For example: ~f "me@(mutt\.org|cs\.hmc\.edu)" +

+Without the quotes, the parenthesis wouldn't end. +This would be separated to two OR'd patterns: ˜f me@(mutt\.org +and cs\.hmc\.edu). They are never what you want. +

2.4. Searching by Date

+Mutt supports two types of dates, absolute and relative. +

+Absolute. Dates must be in DD/MM/YY format (month and year are +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 before the given date will be selected. If you omit the maximum +(second) date, and specify “DD/MM/YY-”, all messages after the given +date will be selected. If you specify a single date with no dash (“-”), +only messages sent on the given date will be selected. +

+Error Margins. You can add error margins to absolute dates. +An error margin is a sign (+ or -), followed by a digit, followed by +one of the units in Table 4.6, “Date units”. As a special case, you can replace the +sign by a “*” character, which is equivalent to giving identical plus and minus error margins. +

Table 4.6. Date units

UnitDescription
yYears
mMonths
wWeeks
dDays

+Example: To select any messages two weeks around January 15, 2001, +you'd use the following pattern: +

+Limit to messages matching: ~d 15/1/2001*2w
+

+Relative. This type of date is relative to the current date, and may +be specified as: +

  • +>offset (messages older than offset units) +

  • +<offset (messages newer than offset units) +

  • +=offset (messages exactly offset units old) +

+offset is specified as a positive number with one of the units from Table 4.6, “Date units”. +

+Example: to select messages less than 1 month old, you would use +

+Limit to messages matching: ~d <1m
+

Note

+All dates used when searching are relative to the +local time zone, so unless you change the setting of your $index_format to include a +%[...] format, these are not the dates shown +in the main index. +

3. Using Tags

+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 all messages with a given subject. To tag all messages +matching a pattern, use the <tag-pattern> function, which is bound to +“shift-T” by default. Or you can select individual messages by +hand using the <tag-message> function, which is bound to “t” by +default. See patterns for Mutt's pattern +matching syntax. +

+Once you have tagged the desired messages, you can use the +“tag-prefix” operator, which is the “;” (semicolon) key by default. +When the “tag-prefix” operator is used, the next operation will +be applied to all tagged messages if that operation can be used in that +manner. If the $auto_tag +variable is set, the next operation applies to the tagged messages +automatically, without requiring the “tag-prefix”. +

+In macros or push commands, +you can use the “tag-prefix-cond” operator. If there are no tagged +messages, mutt will "eat" the rest of the macro to abort it's execution. +Mutt will stop "eating" the macro when it encounters the “end-cond” +operator; after this operator the rest of the macro will be executed as +normal. +

4. Using Hooks

+A hook is a concept found in many other programs which allows you to +execute arbitrary commands before performing some operation. For example, +you may wish to tailor your configuration based upon which mailbox you are +reading, or to whom you are sending mail. In the Mutt world, a hook +consists of a regular expression or +pattern along with a +configuration option/command. See + +

+ +for specific details on each type of hook available. +

Note

+If a hook changes configuration settings, these changes remain +effective until the end of the current mutt session. As this is generally +not desired, a default hook needs to be added before all other hooks to +restore configuration defaults. Here is an example with send-hook and the +my_hdr directive: +

Example 4.2. Combining send-hook and my_hdr

+send-hook . 'unmy_hdr From:'
+send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
+

4.1. Message Matching in Hooks

+Hooks that act upon messages (message-hook, reply-hook, +send-hook, send2-hook, save-hook, fcc-hook) are evaluated in a +slightly different manner. For the other +types of hooks, a regular expression is +sufficient. But in dealing with messages a finer grain of control is +needed for matching since for different purposes you want to match +different criteria. +

+Mutt allows the use of the search pattern +language for matching messages in hook commands. This works in +exactly the same way as it would when limiting or +searching the mailbox, except that you are restricted to those +operators which match information mutt extracts from the header of +the message (i.e., from, to, cc, date, subject, etc.). +

+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 <user@host>'
+

+which would execute the given command when sending mail to +me@cs.hmc.edu. +

+However, it is not required that you write the pattern to match using the +full searching language. You can still specify a simple regular +expression like the other hooks, in which case Mutt will translate your +pattern into the full language, using the translation specified by the +$default_hook variable. The +pattern is translated at the time the hook is declared, so the value of +$default_hook that is in effect +at that time will be used. +

5. External Address Queries

+Mutt supports connecting to external directory databases such as LDAP, +ph/qi, bbdb, or NIS through a wrapper script which connects to mutt +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, then each matching response on a +single line, each line containing a tab separated address then name then +some other optional information. On error, or if there are no matching +addresses, return a non-zero exit code and a one line error message. +

+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@does-not-exist.org        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 menu which will +list the matching responses. From the query menu, you can select +addresses to create aliases, or to mail. You can tag multiple addresses +to mail, start a new query, or have a new query appended to the current +responses. +

+The other mechanism for accessing the query function is for address +completion, similar to the alias completion. In any prompt for address +entry, you can use the <complete-query> function (default: ^T) to run a +query based on the current address you have typed. Like aliases, mutt +will look for what you have typed back to the last space or comma. If +there is a single response for that query, mutt will expand the address +in place. If there are multiple responses, mutt will activate the query +menu. At the query menu, you can select one or more addresses to be +added to the prompt. +

6. Mailbox Formats

+Mutt supports reading and writing of four different mailbox formats: +mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there +is no need to use a flag for different mailbox types. When creating new +mailboxes, Mutt uses the default specified with the $mbox_type variable. +

+mbox. This is the most widely used mailbox format for UNIX. All +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). +

+MMDF. This is a variant of the mbox format. Each message is +surrounded by lines containing “^A^A^A^A” (four control-A's). +

+MH. A radical departure from mbox and MMDF, a mailbox +consists of a directory and each message is stored in a separate file. +The filename indicates the message number (however, this is may not +correspond to the message number Mutt displays). Deleted messages are +renamed with a comma (,) prepended to the filename. Mutt +detects this type of mailbox by looking for either .mh_sequences +or .xmhcache (needed to distinguish normal directories from MH +mailboxes). +

+Maildir. The newest of the mailbox formats, used by the Qmail MTA (a +replacement for sendmail). Similar to MH, except that it adds three +subdirectories of the mailbox: tmp, new and cur. Filenames +for the messages are chosen in such a way they are unique, even when two +programs are writing the mailbox over NFS, which means that no file locking +is needed. +

7. Mailbox Shortcuts

+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. +

  • +! -- refers to your $spoolfile (incoming) mailbox +

  • +> -- refers to your $mbox file +

  • +< -- refers to your $record file +

  • +^ -- refers to the current mailbox +

  • +- or !! -- refers to the file you've last visited +

  • +˜ -- refers to your home directory +

  • += or + -- refers to your $folder directory +

  • +@alias -- refers to the default save folder as determined by the address of the alias +

8. Handling Mailing Lists

+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 does not have to be a mailing list, but that is what it is most +often used for), and what lists you are subscribed to. This is +accomplished through the use of the lists and subscribe commands in your muttrc. +

+Now that Mutt knows what your mailing lists are, it can do several +things, the first of which is the ability to show the name of a list +through which you received a message (i.e., of a subscribed list) in +the index menu display. This is useful to distinguish between +personal and list mail in the same mailbox. In the $index_format variable, the escape “%L” +will return the string “To <list>” when “list” appears in the +“To” field, and “Cc <list>” 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 the message they reply to from the list, resulting in +two or more copies being sent to that person. The <list-reply> +function, which by default is bound to “L” in the index menu +and pager, helps reduce the clutter by only replying to the +known mailing list addresses instead of all recipients (except as +specified by Mail-Followup-To, see below). +

+Mutt also supports the Mail-Followup-To header. When you send +a message to a list of recipients which includes one or several +subscribed mailing lists, and if the $followup_to option is set, mutt will generate +a Mail-Followup-To header which contains all the recipients to whom +you send this message, but not your address. This indicates that +group-replies or list-replies (also known as “followups”) to this +message should only be sent to the original recipients of the +message, and not separately to you - you'll receive your copy through +one of the mailing lists you are subscribed to. +

+Conversely, when group-replying or list-replying to a message which +has a Mail-Followup-To header, mutt will respect this header if +the $honor_followup_to configuration +variable is set. Using list-reply will in this case also make sure +that the reply goes to the mailing list, even if it's not specified +in the list of recipients in the Mail-Followup-To. +

Note

+When header editing is enabled, you can create a +Mail-Followup-To header manually. Mutt will only auto-generate +this header if it doesn't exist when you send the message. +

+The other method some mailing list admins use is to generate a +“Reply-To” field which points back to the mailing list address rather +than the author of the message. This can create problems when trying +to reply directly to the author in private, since most mail clients +will automatically reply to the address given in the “Reply-To” +field. Mutt uses the $reply_to +variable to help decide which address to use. If set to ask-yes or +ask-no, you will be +prompted as to whether or not you would like to use the address given in +the “Reply-To” field, or reply directly to the address given in the +“From” field. When set to yes, the “Reply-To” field will be used when +present. +

+The “X-Label:” header field can be used to further identify mailing +lists or list subject matter (or just to annotate messages +individually). The $index_format variable's “%y” and +“%Y” escapes can be used to expand “X-Label:” fields in the +index, and Mutt's pattern-matcher can match regular expressions to +“X-Label:” fields with the “˜y” selector. “X-Label:” is not a +standard message header field, but it can easily be inserted by procmail +and other mail filtering agents. +

+Lastly, Mutt has the ability to sort the mailbox into +threads. A thread is a group of messages which all relate to the same +subject. This is usually organized into a tree-like structure where a +message and all of its replies are represented graphically. If you've ever +used a threaded news client, this is the same concept. It makes dealing +with large volume mailing lists easier because you can easily delete +uninteresting threads and quickly find topics of value. +

9. Handling multiple folders

+Mutt supports setups with multiple folders, allowing all of them to +be monitored for new mail (see Section 14, “Monitoring incoming mail” for details). +

+When in the index menu and being idle (also see +$timeout), Mutt periodically checks +for new mail in all folders which have been configured via the +mailboxes command. The interval depends on the folder +type: for local/IMAP folders it consults +$mail_check and +$pop_checkinterval +for POP folders. +

+Outside the index menu the directory browser supports checking +for new mail using the <check-new> function which is +unbound by default. Pressing TAB will bring up a +menu showing the files specified by the mailboxes command, +and indicate which contain new messages. Mutt will automatically enter this +mode when invoked from the command line with the -y option. +

+For the pager, index and directory browser menus, Mutt contains the +<buffy-list> function (bound to “.” by default) +which will print a list of folders with new mail in the command line at +the bottom of the screen. +

+For the index, by default Mutt displays the number of mailboxes with new +mail in the status bar, please refer to the +$index_format +variable for details. +

+When changing folders, Mutt fills the prompt with the first folder from +the mailboxes list containing new mail (if any), pressing +space will cycle through folders with new mail. +

10. Editing threads

+Mutt has the ability to dynamically restructure threads that are broken +either by misconfigured software or bad behavior from some +correspondents. This allows to clean your mailboxes formats) from these +annoyances which make it hard to follow a discussion. +

10.1. Linking threads

+Some mailers tend to "forget" to correctly set the "In-Reply-To:" and +"References:" headers when replying to a message. This results in broken +discussions because Mutt has not enough information to guess the correct +threading. +You can fix this by tagging the reply, then moving to the parent message +and using the <link-threads> function (bound to & by default). The +reply will then be connected to this "parent" message. +

+You can also connect multiple children at once, tagging them and using the +tag-prefix command (';') or the auto_tag option. +

10.2. Breaking threads

+On mailing lists, some people are in the bad habit of starting a new +discussion by hitting "reply" to any message from the list and changing +the subject to a totally unrelated one. +You can fix such threads by using the <break-thread> function (bound +by default to #), which will turn the subthread starting from the +current message into a whole different thread. +

11. Delivery Status Notification (DSN) Support

+RFC1894 defines a set of MIME content types for relaying information +about the status of electronic mail messages. These can be thought of as +“return receipts.” +

+To support DSN, there are two variables. $dsn_notify is used to request receipts for +different results (such as failed message, message delivered, etc.). +$dsn_return requests how much +of your message should be returned with the receipt (headers or full +message). +

+When using $sendmail for mail +delivery, you need to use either Berkeley sendmail 8.8.x (or greater) a MTA +supporting DSN command line options compatible to Sendmail: The -N and -R +options can be used by the mail client to make requests as to what type of +status messages should be returned. Please consider your MTA documentation +whether DSN is supported. +

+For SMTP delivery using $smtp_url, it depends on the +capabilities announced by the server whether mutt will attempt to +request DSN or not. +

12. Start a WWW Browser on URLs

+If a message contains URLs, it is efficient to get +a menu with all the URLs and start a WWW browser on one of them. This +functionality is provided by the external urlview program which can be +retrieved at +ftp://ftp.mutt.org/mutt/contrib/ +and the configuration commands: +

+macro index \cb |urlview\n
+macro pager \cb |urlview\n
+
Prev   Next
Chapter 3. Configuration Home Chapter 5. Mutt's MIME Support
diff --git a/obj-i486-linux-gnu-patched/doc/configuration.html b/obj-i486-linux-gnu-patched/doc/configuration.html new file mode 100644 index 0000000..00a6f46 --- /dev/null +++ b/obj-i486-linux-gnu-patched/doc/configuration.html @@ -0,0 +1,1282 @@ + + +Chapter 3. Configuration
Chapter 3. Configuration
Prev   Next

Chapter 3. Configuration

Table of Contents

1. Location of initialization files
2. Syntax of Initialization Files
3. Address groups
4. Defining/Using aliases
5. Changing the default key bindings
6. Defining aliases for character sets
7. Setting variables based upon mailbox
8. Keyboard macros
9. Using color and mono video attributes
10. Message header display
11. Alternative addresses
12. Mailing lists
13. Using Multiple spool mailboxes
14. Monitoring incoming mail
15. User defined headers
16. Specify default save mailbox
17. Specify default Fcc: mailbox when composing
18. Specify default save filename and default Fcc: mailbox at once
19. Change settings based upon message recipients
20. Change settings before formatting a message
21. Choosing the cryptographic key of the recipient
22. Adding key sequences to the keyboard buffer
23. Executing functions
24. Message Scoring
25. Spam detection
26. Setting and Querying Variables
26.1. Commands
26.2. User-defined variables
27. Reading initialization commands from another file
28. Configuring features conditionnaly
29. Removing hooks
30. Format Strings
30.1. Basic usage
30.2. Filters

1. Location of initialization files

+While the default configuration (or “preferences”) make Mutt +usable right out of the box, it is often desirable to tailor Mutt to +suit your own tastes. When Mutt is first invoked, it will attempt to +read the “system” configuration file (defaults set by your local +system administrator), unless the “-n” command line option is specified. This file is typically +/usr/local/share/mutt/Muttrc or /etc/Muttrc. Mutt +will next look for a file named .muttrc in your home +directory. If this file does not exist and your home directory has +a subdirectory named .mutt, mutt try to load a file named +.mutt/muttrc. +

+.muttrc is the file where you will usually place your commands to configure Mutt. +

+In addition, mutt supports version specific configuration files that are +parsed instead of the default files as explained above. For instance, if +your system has a Muttrc-0.88 file in the system configuration +directory, and you are running version 0.88 of mutt, this file will be +sourced instead of the Muttrc file. The same is true of the user +configuration file, if you have a file .muttrc-0.88.6 in your home +directory, when you run mutt version 0.88.6, it will source this file +instead of the default .muttrc file. The version 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. +

2. Syntax of Initialization Files

+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 +(;). +

Example 3.1. Multiple configuration commands per line

+set realname='Mutt user' ; ignore x-
+

+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, +

Example 3.2. Commenting configuration files

+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 shell programs, +namely that a single quote is used to specify a literal string (one that is +not interpreted for shell variables or quoting with a backslash [see +next paragraph]), while double quotes indicate a string for which +should be evaluated. For example, backticks are evaluated inside of double +quotes, but not for single quotes. +

+\ quotes the next character, just as in shells such as bash and zsh. +For example, if want to put quotes “"” inside of a string, you can use +“\” to force the next character to be a literal instead of interpreted +character. +

Example 3.3. Escaping quotes in congfiguration files

+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. +

+A \ at the end of a line can be used to split commands over +multiple lines, provided that the split points don't appear in the +middle of command names. +

+It is also possible to substitute the output of a Unix command in an +initialization file. This is accomplished by enclosing the command in +backticks (``). For example, +

Example 3.4. Using external command's output in configuration files

+my_hdr X-Operating-System: `uname -a`
+

+The output of the Unix command “uname -a” will be substituted before the +line is parsed. +

Note

+Since initialization files are line oriented, only +the first line of output from the Unix command will be substituted. +

+Both environment variables and mutt variables can be accessed by +prepending “$” to the name of the variable. For example, +

Example 3.5. Using environment variables in configuration files

+set record=+sent_on_$HOSTNAME
+

+will cause mutt to save outgoing messages to a folder named +“sent_on_kremvax” if the environment variable HOSTNAME is set to +“kremvax.” (See $record for +details.) +

+Mutt expands the variable when it is assigned, not when it is used. If +the value of a variable on the right-hand side of an assignment +changes after the assignment, the variable on the left-hand side will +not be affected. +

+The commands understood by mutt are explained in the next paragraphs. +For a complete list, see the command reference. +

+All configuration files are expected to be in the current locale as +specified by the $charset variable +which doesn't have a default value since it's determined by Mutt at startup. +If a configuration file is not encoded in the same character set the +$config_charset +variable should be used: all lines starting with the next are recoded +from $config_charset to $charset. +

+This mechanism should be avoided if possible as it has the +following implications: +

  • These variables should be set early in a configuration +file with $charset preceding $config_charset so Mutt +know what character set to convert to.

  • If $config_charset is set, it should be set +in each configuration file because the value is global and not +per configuration file.

  • Because Mutt first recodes a line before it attempts to parse it, +a conversion introducing question marks or other characters as +part of errors (unconvertable characters, transliteration) may introduce syntax +errors or silently change the meaning of certain tokens (e.g. inserting +question marks into regular expressions).

3. Address groups

Usage:

group [ +-group +name +...] { +-rx +expr +... | +-addr +expr +... }

ungroup [ +-group +name +...] { +* + | +-rx +expr +... | +-addr +expr +... }

+group is used to directly add either addresses or +regular expressions to the specified group or groups. The different +categories of arguments to the group command can be +in any order. The flags -rx and +-addr specify what the following strings (that cannot +begin with a hyphen) should be interpreted as: either a regular +expression or an email address, respectively. +

+These address groups can also be created implicitly by the +alias, lists, +subscribe and +alternates commands by specifying the +optional -group option. +

+Once defined, these address groups can be used in +patterns to search for and limit the +display to messages matching a group. +

+ungroup is used to remove addresses or regular +expressions from the specified group or groups. The syntax is similar to +the group command, however the special character +* can be used to empty a group of all of its +contents. +

4. Defining/Using aliases

Usage:

alias [ +-group +name +...] +key + +address + [ +address +...]

+It's usually very cumbersome to remember or type out the address of someone +you are communicating with. Mutt allows you to create “aliases” which map +a short string to a full address. +

Note

+If you want to create an alias for more than +one address, you must separate the addresses with a comma (“,”). +

+The optional -group argument to +alias causes the aliased address(es) to be added to +the named group. +

+To remove an alias or aliases (“*” means all aliases): +

unalias [ +-group +name +...] { +* + | +key +... }

+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. Consequently, you can have multiple alias files, or +you can have all aliases defined in your muttrc. +

+On the other hand, the <create-alias> +function can use only one file, the one pointed to by the $alias_file variable (which is +˜/.muttrc by default). This file is not special either, +in the sense that Mutt will happily append aliases to any file, but in +order for the new aliases to take effect you need to explicitly source this file too. +

+For example: +

Example 3.6. Configuring external alias files

+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 To: or Cc: prompt. You can +also enter aliases in your editor at the appropriate headers if you have the +$edit_headers variable set. +

+In addition, at the various address prompts, you can use the tab character +to expand a partial alias to the full alias. If there are multiple matches, +mutt will bring up a menu with the matching aliases. In order to be +presented with the full list of aliases, you must hit tab with out a partial +alias, such as at the beginning of the prompt or after a comma denoting +multiple addresses. +

+In the alias menu, you can select as many aliases as you want with the +select-entry key (default: <Return>), and use the +exit key (default: q) to return to the address prompt. +

5. Changing the default key bindings

Usage:

bind +map + +key + +function +

+This command allows you to change the default key bindings (operation +invoked when pressing a key). +

+map specifies in which menu the binding belongs. Multiple maps may +be specified by separating them with commas (no additional whitespace is +allowed). The currently defined maps are: +

generic

+This is not a real menu, but is used as a fallback for all of the other +menus except for the pager and editor modes. If a key is not defined in +another menu, Mutt will look for a binding to use in this menu. This allows +you to bind a key to a certain function in multiple menus instead of having +multiple bind statements to accomplish the same task. +

alias

+The alias menu is the list of your personal aliases as defined in your +muttrc. It is the mapping from a short alias name to the full email +address(es) of the recipient(s). +

attach

+The attachment menu is used to access the attachments on received messages. +

browser

+The browser is used for both browsing the local directory structure, and for +listing all of your incoming mailboxes. +

editor

+The editor is the line-based editor the user enters text data. +

index

+The index is the list of messages contained in a mailbox. +

compose

+The compose menu is the screen used when sending a new message. +

pager

+The pager is the mode used to display message/attachment data, and help +listings. +

pgp

+The pgp menu is used to select the OpenPGP keys used to encrypt outgoing +messages. +

smime

+The smime menu is used to select the OpenSSL certificates used to encrypt outgoing +messages. +

postpone

+The postpone menu is similar to the index menu, except is used when +recalling a message the user was composing, but saved until later. +

query

+The query menu is the browser for results returned by +$query_command. +

mix

+The mixmaster screen is used to select remailer options for outgoing +messages (if Mutt is compiled with Mixmaster support). +

+key is the key (or key sequence) you wish to bind. To specify a +control character, use the sequence \Cx, where x is the +letter of the control character (for example, to specify control-A use +“\Ca”). Note that the case of x as well as \C is +ignored, so that \CA, \Ca, \cA and \ca are all +equivalent. An alternative form is to specify the key as a three digit +octal number prefixed with a “\” (for example \177 is +equivalent to \c?). In addition, key may +be a symbolic name as shown in Table 3.1, “Symbolic key names”. +

Table 3.1. Symbolic key names

Symbolic nameMeaning
\ttab
<tab>tab
<backtab>backtab / shift-tab
\rcarriage return
\nnewline
\eescape
<esc>escape
<up>up arrow
<down>down arrow
<left>left arrow
<right>right arrow
<pageup>Page Up
<pagedown>Page Down
<backspace>Backspace
<delete>Delete
<insert>Insert
<enter>Enter
<return>Return
<home>Home
<end>End
<space>Space bar
<f1>function key 1
<f10>function key 10

+key does not need to be enclosed in quotes unless it contains a +space (“ ”) or semi-colon (“;”). +

+function specifies which action to take when key is pressed. +For a complete list of functions, see the reference. The special function <noop> unbinds the specified key +sequence. +

6. Defining aliases for character sets

Usage:

charset-hook +alias + +charset +

iconv-hook +charset + +local-charset +

+The charset-hook command defines an alias for a character set. +This is useful to properly display messages which are tagged with a +character set name not known to mutt. +

+The iconv-hook command defines a system-specific name for a +character set. This is helpful when your systems character +conversion library insists on using strange, system-specific names +for character sets. +

7. Setting variables based upon mailbox

Usage:

folder-hook +[!]regexp + +command +

+It is often desirable to change settings based on which mailbox you are +reading. The folder-hook command provides a method by which you can execute +any configuration command. regexp is a regular expression specifying +in which mailboxes to execute command before loading. If a mailbox +matches multiple folder-hook's, they are executed in the order given in the +muttrc. +

Note

+If you use the “!” shortcut for $spoolfile at the beginning of the pattern, you must place it +inside of double or single quotes in order to distinguish it from the +logical not operator for the expression. +

Note

+Settings are not restored when you leave the mailbox. +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 default command, use the +pattern “.” before other folder-hooks adjusting a value on a per-folder basis +because folder-hooks are evaluated in the order given in the configuration file. +The following example will set the sort variable +to date-sent for all folders but to threads +for all folders containing “mutt” in their name. +

Example 3.7. Setting sort method based on mailbox name

+folder-hook . set sort=date-sent
+folder-hook mutt set sort=threads
+

8. Keyboard macros

Usage:

macro +menu + +key + +sequence + [ +description +]

+Macros are useful when you would like a single key to perform a series of +actions. When you press key in menu menu, Mutt will behave as if +you had typed sequence. So if you have a common sequence of commands +you type, you can create a macro to execute those commands with a single +key or fewer keys. +

+menu is the map which the macro will be bound in. +Multiple maps may be specified by separating multiple menu arguments by +commas. Whitespace may not be used in between the menu arguments and the +commas separating them. +

+key and sequence are expanded by the same rules as the +key bindings with some additions. The +first is that control characters in sequence can also be specified +as ^x. In order to get a caret (“^”) you need to use +^^. Secondly, to specify a certain key such as up +or to invoke a function directly, you can use the format +<key name> and <function name>. For a listing of key +names see the section on key bindings. Functions +are listed in the reference. +

+The advantage with using function names directly is that the macros will +work regardless of the current key bindings, so they are not dependent on +the user having particular key definitions. This makes them more robust +and portable, and also facilitates defining of macros in files used by more +than one user (e.g., the system Muttrc). +

+Optionally you can specify a descriptive text after sequence, +which is shown in the help screens. +

Note

+Macro definitions (if any) listed in the help screen(s), are +silently truncated at the screen width, and are not wrapped. +

9. Using color and mono video attributes

Usage:

color +object + +foreground + +background +

color { +header + | +body + } +foreground + +background + +regexp +

color +index + +foreground + +background + +pattern +

uncolor +index + { +* + | +pattern +... }

+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 information), you +must specify both a foreground color and a background color (it is not +possible to only specify one or the other). +

+header and body match regexp +in the header/body of a message, index matches pattern +(see Section 2, “Patterns: Searching, Limiting and Tagging”) in the message index. +

+object can be one of: +

  • attachment

  • bold (hiliting bold patterns in the body of messages)

  • error (error messages printed by Mutt)

  • hdrdefault (default color of the message header in the pager)

  • indicator (arrow or bar used to indicate the current item in a menu)

  • markers (the “+” markers at the beginning of wrapped lines in the pager)

  • message (informational messages)

  • normal

  • quoted (text matching $quote_regexp in the body of a message)

  • quoted1, quoted2, ..., quotedN (higher levels of quoting)

  • search (hiliting of words in the pager)

  • signature

  • status (mode lines used to display info about the mailbox or message)

  • tilde (the “˜” used to pad blank lines in the pager)

  • tree (thread tree drawn in the message index and attachment menu)

  • underline (hiliting underlined patterns in the body of messages)

+foreground and background can be one of the following: +

  • white

  • black

  • green

  • magenta

  • blue

  • cyan

  • yellow

  • red

  • default

  • colorx

+foreground can optionally be prefixed with the keyword bright to make +the foreground color boldfaced (e.g., brightred). +

+If your terminal supports it, the special keyword default can be +used as a transparent color. The value brightdefault is also valid. +If Mutt is linked against the S-Lang library, you also need to set +the COLORFGBG 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
+

Note

+The S-Lang library requires you to use the lightgray +and brown keywords instead of white and yellow when +setting this variable. +

Note

+The uncolor command can be applied to the index object only. It +removes entries from the list. You must 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 color0, color1, …, +colorN-1 (N being the number of colors supported +by your terminal). This is useful when you remap the colors for your +display (for example by changing the color associated with color2 +for your xterm), since color names may then lose their normal meaning. +

+If your terminal does not support color, it is still possible change the video +attributes through the use of the “mono” command: +

Usage:

mono +object + +attribute +

mono { +header + | +body + } +attribute + +regexp +

mono +index + +attribute + +pattern +

unmono +index + { +* + | +pattern +... }

+For object, see the color command. attribute +can be one of the following: +

  • none

  • bold

  • underline

  • reverse

  • standout

10. Message header display

Usage:

ignore +pattern + [ +pattern +...]

unignore { +* + | +pattern +... }

+Messages often have many header fields added by automatic processing systems, +or which may not seem useful to display on the screen. This command allows +you to specify header fields which you don't normally want to see in the pager. +

+You do not need to specify the full header field name. For example, +“ignore content-” will ignore all header fields that begin with the pattern +“content-”. “ignore *” will ignore all headers. +

+To remove a previously added token from the list, use the “unignore” command. +The “unignore” command will make Mutt display headers with the given pattern. +For example, if you do “ignore x-” it is possible to “unignore x-mailer”. +

+“unignore *” will remove all tokens from the ignore list. +

+For example: +

Example 3.8. Header weeding

+# 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:
+

Usage:

hdr_order +header + [ +header +...]

unhdr_order { +* + | +header +... }

+With the hdr_order command you can specify an order in +which mutt will attempt to present these headers to you when viewing messages. +

+“unhdr_order *” will clear all previous headers from the order list, +thus removing the header order effects set by the system-wide startup file. +

Example 3.9. Configuring header display order

+hdr_order From Date: From: To: Cc: Subject:
+

11. Alternative addresses

Usage:

alternates [ +-group +name +...] +regexp + [ +regexp +...]

unalternates [ +-group +name +...] { +* + | +regexp +... }

+With various functions, mutt will treat messages differently, +depending on whether you sent them or whether you received them from +someone else. For instance, when replying to a message that you +sent to a different party, mutt will automatically suggest to send +the response to the original message's recipients -- responding to +yourself won't make much sense in many cases. (See $reply_to.) +

+Many users receive e-mail under a number of different addresses. To +fully use mutt's features here, the program must be able to +recognize what e-mail addresses you receive mail under. That's the +purpose of the alternates command: It takes a list of regular +expressions, each of which can identify an address under which you +receive e-mail. +

+As addresses are matched using regular expressions and not exact strict +comparisons, you should make sure you specify your addresses as precise +as possible to avoid mismatches. For example, if you specify: +

+alternates user@example
+

+mutt will consider “some-user@example” as +being your address, too which may not be desired. As a solution, in such +cases addresses should be specified as: +

+alternates '^user@example$'
+

+The -group flag causes all of the subsequent regular expressions +to be added to the named group. +

+The unalternates command can be used to write exceptions to +alternates patterns. If an address matches something in an +alternates command, but you nonetheless do not think it is +from you, you can list a more precise pattern under an unalternates +command. +

+To remove a regular expression from the alternates list, use the +unalternates command with exactly the same regexp. +Likewise, if the regexp for an alternates command matches +an entry on the unalternates list, that unalternates +entry will be removed. If the regexp for unalternates +is “*”, all entries on alternates will be removed. +

12. Mailing lists

Usage:

lists [ +-group +name +...] +regexp + [ +regexp +...]

unlists [ +-group +name +...] { +* + | +regexp +... }

subscribe [ +-group +name +...] +regexp + [ +regexp +...]

unsubscribe [ +-group +name +...] { +* + | +regexp +... }

+Mutt has a few nice features for handling mailing lists. In order to take advantage of them, you must +specify which addresses belong to mailing lists, and which mailing +lists you are subscribed to. Once you have done this, the <list-reply> function will work for all known lists. +Additionally, when you send a message to a subscribed list, mutt will +add a Mail-Followup-To header to tell other users' mail user agents +not to send copies of replies to your personal address. +

Note

+The Mail-Followup-To header is a non-standard extension which is not +supported by all mail user agents. Adding it is not bullet-proof against +receiving personal CCs of list messages. Also note that the generation +of the Mail-Followup-To header is controlled by the +$followup_to +configuration variable. +

+More precisely, Mutt maintains lists of patterns for the addresses +of known and subscribed mailing lists. Every subscribed mailing +list is known. To mark a mailing list as known, use the “lists” +command. To mark it as subscribed, use “subscribe”. +

+You can use regular expressions with both commands. To mark all +messages sent to a specific bug report's address on mutt's bug +tracking system as list mail, for instance, you could say +“subscribe [0-9]*@bugs.guug.de”. Often, it's sufficient to just +give a portion of the list's e-mail address. +

+Specify as much of the address as you need to to remove ambiguity. For +example, if you've subscribed to the Mutt mailing list, you will receive mail +addressed to mutt-users@mutt.org. So, to tell Mutt +that this is a mailing list, you could add “lists mutt-users@” to your +initialization file. To tell mutt that you are subscribed to it, +add “subscribe mutt-users” to your initialization file instead. +If you also happen to get mail from someone whose address is +mutt-users@example.com, you could use +“lists ^mutt-users@mutt\\.org$” +or “subscribe ^mutt-users@mutt\\.org$” to +match only mail from the actual list. +

+The -group flag adds all of the subsequent regular expressions +to the named group. +

+The “unlists” command is used to remove a token from the list of +known and subscribed mailing-lists. Use “unlists *” to remove all +tokens. +

+To remove a mailing list from the list of subscribed mailing lists, +but keep it on the list of known mailing lists, use “unsubscribe”. +

13. Using Multiple spool mailboxes

Usage:

mbox-hook +[!]pattern + +mailbox +

+This command is used to move read messages from a specified mailbox to a +different mailbox automatically when you quit or change folders. +pattern is a regular expression specifying the mailbox to treat as a +“spool” mailbox and mailbox specifies where mail should be saved when +read. +

+Unlike some of the other hook commands, only the first matching +pattern is used (it is not possible to save read mail in more than a single +mailbox). +

14. Monitoring incoming mail

Usage:

mailboxes +mailbox + [ +mailbox +...]

unmailboxes { +* + | +mailbox +... }

+This command specifies folders which can receive mail and +which will be checked for new messages periodically. +

+folder can either be a local file or directory +(Mbox/Mmdf or Maildir/Mh). If Mutt was built with POP and/or IMAP +support, folder can also be a POP/IMAP folder +URL. The URL syntax is described in Section 1.2, “URL syntax”, +POP and IMAP are described in Section 3, “POP3 Support” and Section 4, “IMAP Support” +respectively. +

+Mutt provides a number of advanced features for handling (possibly many) +folders and new mail within them, please refer to +Section 9, “Handling multiple folders” for details (including in what +situations and how often Mutt checks for new mail). +

+The “unmailboxes” command is used to remove a token from the list +of folders which receive mail. Use “unmailboxes *” to remove all +tokens. +

Note

+The folders 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 affects these characters (like $folder and $spoolfile) +should be set before the mailboxes command. If +none of these shorcuts are used, a local path should be absolute as +otherwise mutt tries to find it relative to the directory +from where mutt was started which may not always be desired. +

+For Mbox and Mmdf folders, new mail is detected by comparing access and/or +modification times of files: Mutt assumes a folder has new mail if it wasn't +accessed after it was last modified. Utilities like biff or +frm or any other program which accesses the mailbox might cause +Mutt to never detect new mail for that mailbox if they do not properly reset the +access time. Other possible causes of Mutt not detecting new mail in these folders +are backup tools (updating access times) or filesystems mounted without +access time update support. +

+In cases where new mail detection for Mbox or Mmdf folders appears to be +unreliable, the +$check_mbox_size +option can be used to make Mutt track and consult file sizes for new +mail detection instead. +

15. User defined headers

Usage:

my_hdr +string +

unmy_hdr { +* + | +field +... }

+The my_hdr command allows you to create your own header +fields which will be added to every message you send. +

+For example, if you would like to add an “Organization:” header field to +all of your outgoing messages, you can put the command +

Example 3.10. Defining custom headers

+my_hdr Organization: A Really Big Company, Anytown, USA
+

+in your .muttrc. +

Note

+Space characters are not allowed between the keyword and +the colon (“:”). The standard for electronic mail (RFC2822) says that +space is illegal there, so Mutt enforces the rule. +

+If you would like to add a header field to a single message, you should +either set the $edit_headers variable, +or use the <edit-headers> function (default: “E”) in the compose 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
+

16. Specify default save mailbox

Usage:

save-hook +[!]pattern + +mailbox +

+This command is used to override the default mailbox used when saving +messages. mailbox will be used as the default if the message +matches pattern, see Message Matching in Hooks for information +on the exact format. +

+To provide more flexibility and good defaults, Mutt applies the +expandos of $index_format to +mailbox after it was expanded. +

+Examples: +

Example 3.11. Using %-expandos in save-hook

+# default: save all to ~/Mail/<author name>
+save-hook . ~/Mail/%F
+
+# save from me@turing.cs.hmc.edu and me@cs.hmc.edu to $folder/elkins
+save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
+
+# save from aol.com to $folder/spam
+save-hook aol\\.com$ +spam
+

+Also see the fcc-save-hook command. +

17. Specify default Fcc: mailbox when composing

Usage:

fcc-hook +[!]pattern + +mailbox +

+This command is used to save outgoing mail in a mailbox other than +$record. Mutt searches the initial list of +message recipients for the first matching regexp and uses mailbox +as the default Fcc: mailbox. If no match is found the message will be saved +to $record mailbox. +

+To provide more flexibility and good defaults, Mutt applies the +expandos of $index_format to +mailbox after it was expanded. +

+See Message Matching in Hooks for information on the exact format of pattern. +

+Example: fcc-hook [@.]aol\\.com$ +spammers +

+The above will save a copy of all messages going to the aol.com domain to +the `+spammers' mailbox by default. Also see the fcc-save-hook command. +

18. Specify default save filename and default Fcc: mailbox at once

Usage:

fcc-save-hook +[!]pattern + +mailbox +

+This command is a shortcut, equivalent to doing both a fcc-hook +and a save-hook with its arguments, +including %-expansion on mailbox according +to $index_format. +

19. Change settings based upon message recipients

Usage:

reply-hook +[!]pattern + +command +

send-hook +[!]pattern + +command +

send2-hook +[!]pattern + +command +

+These commands can be used to execute arbitrary configuration commands based +upon recipients of the message. pattern is used to match +the message, see Message Matching in Hooks for details. command +is executed when pattern matches. +

+reply-hook is matched against the message you are replying to, +instead of the message you are sending. send-hook is +matched against all messages, both new +and replies. +

Note

+reply-hooks are matched before the send-hook, regardless +of the order specified in the user's configuration file. +

+send2-hook is matched every time a message is changed, either +by editing it, or by using the compose menu to change its recipients +or subject. send2-hook is executed after send-hook, and +can, e.g., be used to set parameters such as the $sendmail variable depending on the message's sender +address. +

+For each type of send-hook or reply-hook, when multiple matches +occur, commands are executed in the order they are specified in the muttrc +(for that type of hook). +

+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 change the language of the attributions and +signatures based upon the recipients. +

Note

+send-hook's are only executed once after getting the initial +list of recipients. Adding a recipient after replying or editing the +message will not cause any send-hook to be executed. Also note that +my_hdr commands which modify recipient headers, or the message's +subject, don't have any effect on the current message when executed +from a send-hook. +

20. Change settings before formatting a message

Usage:

message-hook +[!]pattern + +command +

+This command can be used to execute arbitrary configuration commands +before viewing or formatting a message based upon information about the message. +command is executed if the pattern matches the message to be +displayed. When multiple matches occur, commands are executed in the order +they are specified in the muttrc. +

+See Message Matching in Hooks for +information on the exact format of pattern. +

+Example: +

+message-hook ~A 'set pager=builtin'
+message-hook '~f freshmeat-news' 'set pager="less \"+/^  subject: .*\""'
+

21. Choosing the cryptographic key of the recipient

Usage:

crypt-hook +pattern + +keyid +

+When encrypting messages with PGP/GnuPG or OpenSSL, you may want to associate a certain +key with a given e-mail address automatically, either because the +recipient's public key can't be deduced from the destination address, +or because, for some reasons, you need to override the key Mutt would +normally use. The crypt-hook command provides a +method by which you can specify the ID of the public key to be used +when encrypting messages to a certain recipient. +

+The meaning of keyid is to be taken broadly in this context: You +can either put a numerical key ID here, an e-mail address, or even +just a real name. +

22. Adding key sequences to the keyboard buffer

Usage:

push +string +

+This command adds the named string to the keyboard buffer. The string may +contain control characters, key names and function names like the sequence +string in the macro command. You may use it to +automatically run a sequence of commands at startup, or when entering +certain folders. For example, the following command will automatically +collapse all threads when entering a folder: +

Example 3.12. Embedding push in folder-hook

+folder-hook . 'push <collapse-all>'
+

23. Executing functions

Usage:

exec +function + [ +function +...]

+This command can be used to execute any function. Functions are +listed in the function reference. +“exec function” is equivalent to “push <function>”. +

24. Message Scoring

Usage:

score +pattern + +value +

unscore { +* + | +pattern +... }

+The score commands adds value to a message's score if pattern +matches it. pattern is a string in the format described in the patterns section (note: For efficiency reasons, patterns +which scan information not available in the index, such as ˜b, +˜B or ˜h, may not be used). value is a +positive or negative integer. A message's final score is the sum total of all +matching score entries. However, you may optionally prefix value with +an equal sign (=) to cause evaluation to stop at a particular entry if there is +a match. Negative final scores are rounded up to 0. +

+The unscore command removes score entries from the list. You must +specify the same pattern specified in the score command for it to be +removed. The pattern “*” is a special token which means to clear the list +of all score entries. +

25. Spam detection

Usage:

spam +pattern + +format +

nospam { +* + | +pattern + }

+Mutt has generalized support for external spam-scoring filters. +By defining your spam patterns with the spam and nospam +commands, you can limit, search, and sort your +mail based on its spam attributes, as determined by the external +filter. You also can display the spam attributes in your index +display using the %H selector in the $index_format variable. (Tip: try %?H?[%H] ? +to display spam tags only when they are defined for a given message.) +

+Your first step is to define your external filter's spam patterns using +the spam command. pattern should be a regular expression +that matches a header in a mail message. If any message in the mailbox +matches this regular expression, it will receive a “spam tag” or +“spam attribute” (unless it also matches a nospam pattern -- see +below.) The appearance of this attribute is entirely up to you, and is +governed by the format parameter. format can be any static +text, but it also can include back-references from the pattern +expression. (A regular expression “back-reference” refers to a +sub-expression contained within parentheses.) %1 is replaced with +the first back-reference in the regex, %2 with the second, etc. +

+If you're using multiple spam filters, a message can have more than +one spam-related header. You can define spam patterns for each +filter you use. If a message matches two or more of these patterns, and +the $spam_separator variable is set to a string, then the +message's spam tag will consist of all the format strings joined +together, with the value of $spam_separator separating +them. +

+For example, suppose I use DCC, SpamAssassin, and PureMessage. I might +define these spam settings: +

Example 3.13. Configuring spam detection

+spam "X-DCC-.*-Metrics:.*(....)=many"         "90+/DCC-%1"
+spam "X-Spam-Status: Yes"                     "90+/SA"
+spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
+set spam_separator=", "
+

+If I then received a message that DCC registered with “many” hits +under the “Fuz2” checksum, and that PureMessage registered with a +97% probability of being spam, that message's spam tag would read +90+/DCC-Fuz2, 97/PM. (The four characters before “=many” in a +DCC report indicate the checksum used -- in this case, “Fuz2”.) +

+If the $spam_separator variable is unset, then each +spam pattern match supersedes the previous one. Instead of getting +joined format strings, you'll get only the last one to match. +

+The spam tag is what will be displayed in the index when you use +%H in the $index_format variable. It's also the +string that the ˜H pattern-matching expression matches against for +<search> and <limit> functions. And it's what sorting by spam +attribute will use as a sort key. +

+That's a pretty complicated example, and most people's actual +environments will have only one spam filter. The simpler your +configuration, the more effective mutt can be, especially when it comes +to sorting. +

+Generally, when you sort by spam tag, mutt will sort lexically -- +that is, by ordering strings alphanumerically. However, if a spam tag +begins with a number, mutt will sort numerically first, and lexically +only when two numbers are equal in value. (This is like UNIX's +sort -n.) A message with no spam attributes at all -- that is, one +that didn't match any of your spam patterns -- is sorted at +lowest priority. Numbers are sorted next, beginning with 0 and ranging +upward. Finally, non-numeric strings are sorted, with “a” taking lower +priority than “z”. Clearly, in general, sorting by spam tags is most +effective when you can coerce your filter to give you a raw number. But +in case you can't, mutt can still do something useful. +

+The nospam command can be used to write exceptions to spam +patterns. If a header pattern matches something in a spam command, +but you nonetheless do not want it to receive a spam tag, you can list a +more precise pattern under a nospam command. +

+If the pattern given to nospam is exactly the same as the +pattern on an existing spam list entry, the effect will be to +remove the entry from the spam list, instead of adding an exception. +Likewise, if the pattern for a spam command matches an entry +on the nospam list, that nospam entry will be removed. If the +pattern for nospam is “*”, all entries on both lists +will be removed. This might be the default action if you use spam +and nospam in conjunction with a folder-hook. +

+You can have as many spam or nospam commands as you like. +You can even do your own primitive spam detection within mutt -- for +example, if you consider all mail from MAILER-DAEMON to be spam, +you can use a spam command like this: +

+spam "^From: .*MAILER-DAEMON"       "999"
+

26. Setting and Querying Variables

26.1. Commands

+The following commands are available to manipulate and query variables: +

Usage:

set { +[ no | inv ] +variable + | +variable=value + } [...]

toggle +variable + [ +variable +...]

unset +variable + [ +variable +...]

reset +variable + [ +variable +...]

+This command is used to set (and unset) configuration variables. There are four basic types of variables: +boolean, number, string and quadoption. boolean variables can be +set (true) or unset (false). number variables can be +assigned a positive integer value. +string variables consist of any number of printable characters and +must be enclosed in quotes if they contain spaces or tabs. You +may also use the escape sequences “\n” and “\t” for newline and tab, respectively. +quadoption variables are used to control whether or not to be prompted +for certain actions, or to specify a default action. A value of yes +will cause the action to be carried out automatically as if you had answered +yes to the question. Similarly, a value of no will cause the +action to be carried out as if you had answered “no.” A value of +ask-yes will cause a prompt with a default answer of “yes” and +ask-no will provide a default answer of “no.” +

+Prefixing a variable with “no” will unset it. Example: set noaskbcc. +

+For boolean variables, you may optionally prefix the variable name with +inv to toggle the value (on or off). This is useful when writing +macros. Example: set invsmart_wrap. +

+The toggle command automatically prepends the inv prefix to all +specified variables. +

+The unset command automatically prepends the no prefix to all +specified variables. +

+Using the <enter-command> function in the index menu, you can query the +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 and quadoption +variables. +

+The reset command resets all given variables to the compile time +defaults (hopefully mentioned in this manual). If you use the command +set and prefix the variable with “&” this has the same +behavior as the reset command. +

+With the reset command there exists the special variable “all”, +which allows you to reset all variables to their system defaults. +

26.2. User-defined variables

26.2.1. Introduction

+Along with the variables listed in the +Configuration variables section, mutt +supports user-defined variables with names starting +with my_ as in, for +example, my_cfgdir. +

+The set command either creates a +custom my_ variable or changes its +value if it does exist already. The unset and reset +commands remove the variable entirely. +

+Since user-defined variables are expanded in the same way that +environment variables are (except for +the shell-escape command and +backtick expansion), this feature can be used to make configuration +files more readable. +

26.2.2. Examples

+The following example defines and uses the variable my_cfgdir +to abbreviate the calls of the source command: +

Example 3.14. Using user-defined variables for config file readability

+set my_cfgdir = $HOME/mutt/config
+
+source $my_cfgdir/hooks
+source $my_cfgdir/macros
+# more source commands...
+

+A custom variable can also be used in macros to backup the current value +of another variable. In the following example, the value of the +$delete is changed temporarily +while its original value is saved as my_delete. +After the macro has executed all commands, the original value of $delete is restored. +

Example 3.15. Using user-defined variables for backing up other config option values

+macro pager ,x '\
+<enter-command>set my_delete=$delete<enter>\
+<enter-command>set delete=yes<enter>\
+...\
+<enter-command>set delete=$my_delete<enter>'
+

+Since mutt expands such values already when parsing the configuration +file(s), the value of $my_delete in the +last example would be the value of $delete exactly +as it was at that point during parsing the configuration file. If +another statement would change the value for $delete +later in the same or another file, it would have no effect on +$my_delete. However, the expansion can +be deferred to runtime, as shown in the next example, when escaping the +dollar sign. +

Example 3.16. Deferring user-defined variable expansion to runtime

+macro pager <PageDown> "\
+<enter-command> set my_old_pager_stop=\$pager_stop pager_stop<Enter>\
+<next-page>\
+<enter-command> set pager_stop=\$my_old_pager_stop<Enter>\
+<enter-command> unset my_old_pager_stop<Enter>"
+

+Note that there is a space +between <enter-command> and +the set configuration command, preventing mutt from +recording the macro's commands into its history. +

27. Reading initialization commands from another file

Usage:

source +filename +

+This command allows the inclusion of initialization commands +from other files. For example, I place all of my aliases in +˜/.mail_aliases so that I can make my +˜/.muttrc readable and keep my aliases private. +

+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 filename is +considered to be an executable program from which to read input (eg. +source ˜/bin/myscript|). +

28. Configuring features conditionnaly

+Usage: ifdef item command +

+This command allows to test if a feature has been compiled in, before +actually executing the command. Item can be either the name of a +function, variable, or command. Example: +

+

+ifdef imap_keepalive 'source ~/.mutt/imap_setup'
+

+

29. Removing hooks

Usage:

unhook { +* + | +hook-type + }

+This command permits you to flush hooks you have previously defined. +You can either remove all hooks by giving the “*” character as an +argument, or you can remove all hooks of a specific type by saying +something like unhook send-hook. +

30. Format Strings

30.1. Basic usage

+Format strings are a general concept you'll find in several locations +through the mutt configuration, especially in the +$index_format, +$pager_format, +$status_format, +and other “*_format” variables. These can be very straightforward, +and it's quite possible you already know how to use them. +

+The most basic format string element is a percent symbol followed +by another character. For example, %s +represents a message's Subject: header in the $index_format variable. The +“expandos” available are documented with each format variable, but +there are general modifiers available with all formatting expandos, +too. Those are our concern here. +

+Some of the modifiers are borrowed right out of C (though you might +know them from Perl, Python, shell, or another language). These are +the [-]m.n modifiers, as in %-12.12s. As with +such programming languages, these modifiers allow you to specify the +minimum and maximum size of the resulting string, as well as its +justification. If the “-” sign follows the percent, the string will +be left-justified instead of right-justified. If there's a number +immediately following that, it's the minimum amount of space the +formatted string will occupy -- if it's naturally smaller than that, it +will be padded out with spaces. If a decimal point and another number +follow, that's the maximum space allowable -- the string will not be +permitted to exceed that width, no matter its natural size. Each of +these three elements is optional, so that all these are legal format +strings: +%-12s +%4c +%.15F +%-12.15L +

+Mutt adds some other modifiers to format strings. If you use an equals +symbol (=) as a numeric prefix (like the minus +above), it will force the string to be centered within its minimum +space range. For example, %=14y will reserve 14 +characters for the %y expansion -- that's the X-Label: header, in +$index_format. If the expansion +results in a string less than 14 characters, it will be centered in a +14-character space. If the X-Label for a message were "test", that +expansion would look like “ test ”. +

+There are two very little-known modifiers that affect the way that an +expando is replaced. If there is an underline (“_”) character +between any format modifiers (as above) and the expando letter, it will +expands in all lower case. And if you use a colon (“:”), it will +replace all decimal points with underlines. +

30.2. Filters

+Any format string ending in a vertical bar (“|”) will be +expanded and piped through the first word in the string, using spaces +as separator. The string returned will be used for display. +If the returned string ends in %, it will be passed through +the formatter a second time. This allows the filter to generate a +replacement format string including % expandos. +

+All % expandos in a format string are expanded before the script +is called so that: +

Example 3.17. Using external filters in format strings

+set status_format="script.sh '%r %f (%L)'|"
+

+will make mutt expand %r, +%f and %L +before calling the script. The example also shows that arguments can be +quoted: the script will receive the expanded string between the single quotes +as the only argument. +

+A practical example is the mutt_xtitle +script installed in the samples +subdirectory of the mutt documentation: it can be used as filter for +$status_format to set the current +terminal's title, if supported. +

Prev   Next
Chapter 2. Getting Started Home Chapter 4. Advanced Usage
diff --git a/obj-i486-linux-gnu-patched/doc/gettingstarted.html b/obj-i486-linux-gnu-patched/doc/gettingstarted.html new file mode 100644 index 0000000..10bf855 --- /dev/null +++ b/obj-i486-linux-gnu-patched/doc/gettingstarted.html @@ -0,0 +1,553 @@ + + +Chapter 2. Getting Started
Chapter 2. Getting Started
Prev   Next

Chapter 2. Getting Started

Table of Contents

1. Core concepts
2. Moving Around in Menus
3. Editing Input Fields
3.1. Introduction
3.2. History
4. Reading Mail - The Index and Pager
4.1. The Message Index
4.2. The Pager
4.3. Threaded Mode
4.4. Miscellaneous Functions
5. Sending Mail
5.1. Introduction
5.2. Editing the message header
5.3. Sending cryptographically signed/encrypted messages
5.4. Sending anonymous messages via mixmaster
5.5. Sending format=flowed messages
6. Forwarding and Bouncing Mail
7. Postponing Mail

+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 various web +pages. See the Mutt homepage for more details. +

+The keybindings described in this section are the defaults as distributed. +Your local system administrator may have altered the defaults for your site. +You can always type “?” in any menu to display the current bindings. +

+The first thing you need to do is invoke mutt, simply by typing mutt +at the command line. There are various command-line options, see +either the mutt man page or the reference. +

1. Core concepts

+Mutt is a text-based application which interacts with users through +different menus which are mostly line-/entry-based or page-based. A +line-based menu is the so-called “index” menu (listing all messages of +the currently opened folder) or the “alias” menu (allowing you to +select recipients from a list). Examples for page-based menus are the +“pager” (showing one message at a time) or the “help” menu listing +all available key bindings. +

+The user interface consists of a context sensitive help line at the top, +the menu's contents followed by a context sensitive status line and +finally the command line. The command line is used to display +informational and error messages as well as for prompts and for entering +interactive commands. +

+Because Mutt allows for customizing almost all key bindings, there are +so-called “functions” which can be executed manually (using the +command line) or in macros. Macros allow the user to bind a sequence of +commands to a single key or a short key sequence instead of repeating a +sequence of actions over and over. +

+Many commands (such as saving or copying a message to another folder) +can be applied to a single message or a set of messages (so-called +“tagged” messages). To help selecting messages, Mutt provides a rich +set of message patterns (such as recipients, sender, body contents, date +sent/received, etc.) which can be combined into complex expressions +using the boolean and and or +operations as well as negating. These patterns can also be used to (for +example) search for messages or to limit the index to show only matching +messages. +

+Mutt supports a “hook” concept which allows the user to execute +arbitrary configuration commands and functions in certain situations +such as entering a folder, starting a new message or replying to an +existing one. These hooks can be used to highly customize Mutt's +behaviour including managing multiple identities, customizing the +display for a folder or even implementing auto-archiving based on a +per-folder basis and much more. +

2. Moving Around in Menus

+The most important navigation keys common to all menus are shown in +Table 2.1, “Most common navigation keys”. +

Table 2.1. Most common navigation keys

KeyFunctionDescription
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
Z or <PageUp><page-up>go to the previous page
= or <Home><first-entry>jump to the first entry
* or <End><last-entry>jump to the last entry
q<quit>exit the current menu
?<help>list all keybindings for the current menu

3. Editing Input Fields

3.1. Introduction

+Mutt has a built-in line editor for inputting text, e.g. email +addresses or filenames. The keys used to manipulate text input are +very similar to those of Emacs. See Table 2.2, “Most common line editor keys” for a full +reference of available functions, their default key bindings, and +short descriptions. +

Table 2.2. Most common line editor keys

KeyFunctionDescription
^A or <Home><bol>move to the start of the line
^B or <Left><backward-char>move back one char
Esc B<backward-word>move back one word
^D or <Delete><delete-char>delete the char under the cursor
^E or <End><eol>move to the end of the line
^F or <Right><forward-char>move forward one char
Esc F<forward-word>move forward one word
<Tab><complete>complete filename or alias
^T<complete-query>complete address with query
^K<kill-eol>delete to the end of the line
Esc d<kill-eow>delete to the end of the word
^W<kill-word>kill the word in front of the cursor
^U<kill-line>delete entire line
^V<quote-char>quote the next typed key
<Up><history-up>recall previous string from history
<Down><history-down>recall next string from history
<BackSpace><backspace>kill the char in front of the cursor
Esc u<upcase-word>convert word to upper case
Esc l<downcase-word>convert word to lower case
Esc c<capitalize-word>capitalize the word
^Gn/aabort
<Return>n/afinish editing

+You can remap the editor functions using the +bind command. For example, to make +the <Delete> key delete the character in front of +the cursor rather than under, you could use: +

+bind editor <delete> backspace
+

3.2. History

+Mutt maintains a history for the built-in editor. The number of items +is controlled by the $history +variable and can be made persistent using an external file specified +using $history_file. +You may cycle through them at an editor prompt by using the +<history-up> and/or +<history-down> commands. +

+Mutt maintains several distinct history lists, one for each of the +following categories: +

  • muttrc commands

  • addresses and aliases

  • shell commands

  • filenames

  • patterns

  • everything else

+Mutt automatically filters out repeated items from the history. It +also mimics the behavior of some shells by ignoring items starting +with a space. The latter feature can be useful in macros to not clobber +the history's valuable entries with unwanted entries. +

4. Reading Mail - The Index and Pager

+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 of the +message contents. This is called the “pager.” +

+The next few sections describe the functions provided in each of these +modes. +

4.1. The Message Index

+Common keys used to navigate through and manage messages in the index +are shown in Table 2.3, “Most common message index keys”. How messages are presented +in the index menu can be customized using the +$index_format variable. +

Table 2.3. Most common message index keys

KeyDescription
cchange to a different mailbox
Esc cchange to a folder in read-only mode
Ccopy the current message to another mailbox
Esc Cdecode a message and copy it to a folder
Esc sdecode a message and save it to a folder
Ddelete messages matching a pattern
ddelete the current message
Fmark as important
lshow messages matching a pattern
Nmark message as new
ochange the current sort method
Oreverse sort the mailbox
qsave changes and exit
ssave-message
Ttag messages matching a pattern
ttoggle the tag on a message
Esc ttoggle tag on entire message thread
Uundelete messages matching a pattern
uundelete-message
vview-attachments
xabort changes and exit
<Return>display-message
<Tab>jump to the next new or unread message
@show the author's full e-mail address
$save changes to mailbox
/search
Esc /search-reverse
^Lclear and redraw the screen
^Tuntag messages matching a pattern

+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 “flags” in Table 2.4, “Message status flags” +may appear, some of which can be turned on or off using these functions: +<set-flag> and +<clear-flag> +bound by default to “w” and “W” respectively. +

+Furthermore, the flags in Table 2.5, “Message recipient flags” reflect +who the message is addressed to. They can be customized with the +$to_chars variable. +

Table 2.4. Message status flags

FlagDescription
Dmessage is deleted (is marked for deletion)
dmessage has attachments marked for deletion
Kcontains a PGP public key
Nmessage is new
Omessage is old
Pmessage is PGP encrypted
rmessage has been replied to
Smessage is signed, and the signature is successfully verified
smessage is signed
!message is flagged
*message is tagged

Table 2.5. Message recipient flags

FlagDescription
+message is to you and you only
Tmessage is to you, but also to or cc'ed to others
Cmessage is cc'ed to you
Fmessage is from you
Lmessage is sent to a subscribed mailing list

4.2. The Pager

+By default, Mutt uses its builtin pager to display the contents of messages. +The pager is very similar to the Unix program less though not nearly as +featureful. +

Table 2.6. Most common pager keys

KeyDescription
<Return>go down one line
<Space>display the next page (or next message if at the end of a message)
-go back to the previous page
nsearch for next match
Sskip beyond quoted text
Ttoggle display of quoted text
?show keybindings
/regular expression search
Esc /backward regular expression search
\toggle highlighting of search matches
^jump to the top of the message

+In addition to key bindings in Table 2.6, “Most common pager keys”, +many of the functions from the index menu are also available in +the pager, such as <delete-message> or <copy-message> +(this is one advantage over using an external pager to view messages). +

+Also, the internal pager supports a couple other advanced features. For +one, it will accept and translate the “standard” nroff sequences for +bold and underline. These sequences are a series of either the letter, +backspace (^H), the letter again for bold or the letter, backspace, +“_” for denoting underline. Mutt will attempt to display these +in bold and underline respectively if your terminal supports them. If +not, you can use the bold and underline color +objects to specify a color or mono attribute for them. +

+Additionally, the internal pager supports the ANSI escape sequences for +character attributes. Mutt translates them into the correct color and +character settings. The sequences Mutt supports are: +

+\e[Ps;Ps;..Ps;m
+

+where Ps can be one of the codes shown in +Table 2.7, “ANSI escape sequences”. +

Table 2.7. ANSI escape sequences

Escape codeDescription
0All attributes off
1Bold on
4Underline on
5Blink on
7Reverse video on
3<color>Foreground color is <color> (see Table 2.8, “Color sequences”)
4<color>Background color is <color> (see Table 2.8, “Color sequences”)

Table 2.8. Color sequences

Color codeColor
0Black
1Red
2Green
3Yellow
4Blue
5Magenta
6Cyan
7White

+Mutt uses these attributes for handling text/enriched +messages, and they can also be used by an external +autoview script for highlighting +purposes. +

Note

+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. +

Note

+Note that the search commands in the pager take regular expressions, +which are not quite the same as the more +complex patterns used by the search +command in the index. This is because the pager only performs simple +text search, whereas the index provides boolean filtering on several +aspects of messages. +

4.3. Threaded Mode

+When the mailbox is sorted by threads, there are +a few additional functions available in the index and pager modes +as shown in Table 2.9, “Most common thread mode keys”. +

Table 2.9. Most common thread mode keys

KeyFunctionDescription
^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
^P<previous-thread>jump to the start of the previous thread
^R<read-thread>mark the current thread as read
Esc d<delete-subthread>delete all messages in the current subthread
Esc u<undelete-subthread>undelete all messages in the current subthread
Esc n<next-subthread>jump to the start of the next subthread
Esc p<previous-subthread>jump to the start of the previous subthread
Esc r<read-subthread>mark the current subthread as read
Esc t<tag-thread>toggle the tag on the current thread
Esc v<collapse-thread>toggle collapse for the current thread
Esc V<collapse-all>toggle collapse for all threads
P<parent-message>jump to parent message in thread

Note

+Collapsing a thread displays only the first message +in the thread and hides the others. This is useful when threads +contain so many messages that you can only see a handful of threads on +the screen. See %M in $index_format. +For example, you could use "%?M?(#%03M)&(%4l)?" in $index_format to optionally +display the number of hidden messages if the thread is collapsed. +

+See also: $strict_threads. +

4.4. Miscellaneous Functions

+In addition, the index and pager +menus have these interesting functions: +

+<create-alias> (default: a) +

+Creates a new alias based upon the current message (or prompts for a +new one). Once editing is complete, an alias +command is added to the file specified by +the $alias_file variable +for future use +

Note

+Mutt does not read the $alias_file +upon startup so you must explicitly source the file. +

+<check-traditional-pgp> (default: Esc P) +

+This function will search the current message for content signed or +encrypted with PGP the “traditional” way, that is, without proper +MIME tagging. Technically, this function will temporarily change +the MIME content types of the body parts containing PGP data; this +is similar to the <edit-type> function's +effect. +

+<edit> (default: e) +

+This command (available in the index and pager) allows you to +edit the raw current message as it's present in the mail folder. +After you have finished editing, the changed message will be +appended to the current folder, and the original message will be +marked for deletion; if the message is unchanged it won't be replaced. +

+<edit-type> (default: +^E on the attachment menu, and in the pager and index menus; +^T on the compose menu) +

+This command is used to temporarily edit an attachment's content +type to fix, for instance, bogus character set parameters. When +invoked from the index or from the pager, you'll have the +opportunity to edit the top-level attachment's content type. On the +attachment menu, you can change any +attachment's content type. These changes are not persistent, and get +lost upon changing folders. +

+Note that this command is also available on the compose +menu. There, it's used to fine-tune the properties of attachments you are going +to send. +

+<enter-command> (default: “:”) +

+This command is used to execute any command you would normally put in a +configuration file. A common use is to check the settings of variables, or +in conjunction with macros to change settings on the +fly. +

+<extract-keys> (default: ^K) +

+This command extracts PGP public keys from the current or tagged +message(s) and adds them to your PGP public key ring. +

+<forget-passphrase> (default: +^F) +

+This command wipes the passphrase(s) from memory. It is useful, if +you misspelled the passphrase. +

+<list-reply> (default: L) +

+Reply to the current or tagged message(s) by extracting any addresses which +match the regular expressions given by the lists or subscribe +commands, but also honor any Mail-Followup-To header(s) if the +$honor_followup_to +configuration variable is set. Using this when replying to messages posted +to mailing lists helps avoid duplicate copies being sent to the author of +the message you are replying to. +

+<pipe-message> (default: |) +

+Asks for an external Unix command and pipes the current or +tagged message(s) to it. The variables $pipe_decode, $pipe_split, +$pipe_sep and $wait_key control the exact behavior of this function. +

+<resend-message> (default: Esc e) +

+Mutt takes the current message as a template for a +new message. This function is best described as "recall from arbitrary +folders". It can conveniently be used to forward MIME messages while +preserving the original mail structure. Note that the amount of headers +included here depends on the value of the $weed +variable. +

+This function is also available from the attachment menu. You can use this +to easily resend a message which was included with a bounce message +as a message/rfc822 body part. +

+<shell-escape> (default: !) +

+Asks for an external Unix command and executes it. The $wait_key can be used to control +whether Mutt will wait for a key to be pressed when the command returns +(presumably to let the user read the output of the command), based on +the return status of the named command. If no command is given, an +interactive shell is executed. +

+<toggle-quoted> (default: T) +

+The pager uses the $quote_regexp variable to detect quoted text when +displaying the body of the message. This function toggles the display +of the quoted material in the message. It is particularly useful when +being interested in just the response and there is a large amount of +quoted text in the way. +

+<skip-quoted> (default: S) +

+This function will go to the next line of non-quoted text which comes +after a line of quoted text in the internal pager. +

5. Sending Mail

5.1. Introduction

+The bindings shown in Table 2.10, “Most common mail sending keys” are available in the +index and pager to start a new message. +

Table 2.10. Most common mail sending keys

KeyFunctionDescription
m<compose>compose a new message
r<reply>reply to sender
g<group-reply>reply to all recipients
L<list-reply>reply to mailing list address
f<forward>forward message
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. These items are discussed +in greater detail in the next chapter “Forwarding +and Bouncing Mail.” +

+Mutt will then enter the compose menu and prompt you for the +recipients to place on the “To:” header field. Next, it will ask +you for the “Subject:” field for the message, providing a default if +you are replying to or forwarding a message. See also +$askcc, +$askbcc, +$autoedit, +$bounce, +$fast_reply, +and $include +for changing how Mutt asks these questions. +

+Mutt will then automatically start your $editor +on the message body. If the $edit_headers +variable is set, the headers will be at the top of the message in your editor. +Any messages you are replying to will be added in sort order to the message, +with appropriate $attribution, +$indent_string and +$post_indent_string. +When forwarding a message, if the $mime_forward +variable is unset, a copy of the forwarded message will be included. If +you have specified a $signature, it +will be appended to the message. +

+Once you have finished editing the body of your mail message, you are +returned to the compose menu providing the functions +shown in Table 2.11, “Most common compose menu keys” to modify, send or postpone the +message. +

Table 2.11. Most common compose menu keys

KeyFunctionDescription
a<attach-file>attach a file
A<attach-message>attach message(s) to the message
Esc k<attach-key>attach a PGP public key
d<edit-description>edit description on attachment
D<detach-file>detach a file
t<edit-to>edit the To field
Esc f<edit-from>edit the From field
r<edit-reply-to>edit the Reply-To field
c<edit-cc>edit the Cc field
b<edit-bcc>edit the Bcc field
y<send-message>send the message
s<edit-subject>edit the Subject
S<smime-menu>select S/MIME options
f<edit-fcc>specify an “Fcc” mailbox
p<pgp-menu>select PGP options
P<postpone-message>postpone this message until later
q<quit>quit (abort) sending the message
w<write-fcc>write the message to a folder
i<ispell>check spelling (if available on your system)
^F<forget-passphrase>wipe passphrase(s) from memory

+The compose menu is also used to edit the attachments for a message which can be either files +or other messages. The <attach-message> function to will prompt you for a folder to +attach messages from. You can now tag messages in that folder and they +will be attached to the message you are sending. +

Note

+Note that certain +operations like composing a new mail, replying, forwarding, etc. are +not permitted when you are in that folder. The %r in +$status_format will change to +a “A” to indicate that you are in attach-message mode. +

5.2. Editing the message header

+When editing the header because of $edit_headers +being set, there are a several pseudo headers available which +will not be included in sent messages. +

5.2.1. Fcc: pseudo header

+If you specify + +Fcc: filename + +as a header, Mutt will pick up filename +just as if you had used the <edit-fcc> function in the compose menu. +

5.2.2. Attach: pseudo header

+You can also attach files to your message by specifying + +Attach: filename [ description ] + +where filename is the file to attach and description is an +optional string to use as the description of the attached file. +

5.2.3. Pgp: pseudo header

+If you want to use PGP, you can specify +

+Pgp: [ E | S | S<id> ] + +

+“E” selects encryption, “S” selects signing and +“S<id>” selects signing with the given key, setting +$pgp_sign_as +permanently. +

5.2.4. In-Reply-To: header

+When replying to messages, the In-Reply-To: header contains the +Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a +References: field, which allows you to create a new message thread, for example +to create a new message to a mailing list without having to enter the mailing list's address. +

5.3. Sending cryptographically signed/encrypted messages

+If you have told mutt to PGP or S/MIME encrypt a message, it will guide you +through a key selection process when you try to send the message. +Mutt will not ask you any questions about keys which have a +certified user ID matching one of the message recipients' mail +addresses. However, there may be situations in which there are +several keys, weakly certified user ID fields, or where no matching +keys can be found. +

+In these cases, you are dropped into a menu with a list of keys from +which you can select one. When you quit this menu, or mutt can't +find any matching keys, you are prompted for a user ID. You can, as +usually, abort this prompt using ^G. When you do so, mutt will +return to the compose screen. +

+Once you have successfully finished the key selection, the message +will be encrypted using the selected public keys when sent out. +

+Most fields of the entries in the key selection menu (see also $pgp_entry_format) +have obvious meanings. But some explanations on the capabilities, flags, +and validity fields are in order. +

+The flags sequence (%f) will expand to one of the flags in +Table 2.12, “PGP key menu flags”. +

Table 2.12. PGP key menu flags

FlagDescription
RThe key has been revoked and can't be used.
XThe key is expired and can't be used.
dYou have marked the key as disabled.
cThere are unknown critical self-signature packets.

+The capabilities field (%c) expands to a two-character sequence +representing a key's capabilities. The first character gives +the key's encryption capabilities: A minus sign (“-”) means +that the key cannot be used for encryption. A dot (“.”) means that +it's marked as a signature key in one of the user IDs, but may +also be used for encryption. The letter “e” indicates that +this key can be used for encryption. +

+The second character indicates the key's signing capabilities. Once +again, a “-” implies “not for signing”, “.” implies +that the key is marked as an encryption key in one of the user-ids, and +“s” denotes a key which can be used for signing. +

+Finally, the validity field (%t) indicates how well-certified a user-id +is. A question mark (“?”) indicates undefined validity, a minus +character (“-”) marks an untrusted association, a space character +means a partially trusted association, and a plus character (“+”) +indicates complete validity. +

5.4. Sending anonymous messages via mixmaster

+You may also have compiled mutt to co-operate with Mixmaster, an +anonymous remailer. Mixmaster permits you to send your messages +anonymously using a chain of remailers. Mixmaster support in mutt is for +mixmaster version 2.04 (beta 45 appears to be the latest) and 2.03. +It does not support earlier versions or the later so-called version 3 betas, +of which the latest appears to be called 2.9b23. +

+To use it, you'll have to obey certain restrictions. Most +important, you cannot use the Cc and Bcc headers. To tell +Mutt to use mixmaster, you have to select a remailer chain, using +the mix function on the compose menu. +

+The chain selection screen is divided into two parts. In the +(larger) upper part, you get a list of remailers you may use. In +the lower part, you see the currently selected chain of remailers. +

+You can navigate in the chain using the <chain-prev> and +<chain-next> functions, which are by default bound to the left +and right arrows and to the h and l keys (think vi +keyboard bindings). To insert a remailer at the current chain +position, use the <insert> function. To append a remailer behind +the current chain position, use <select-entry> or <append>. +You can also delete entries from the chain, using the corresponding +function. Finally, to abandon your changes, leave the menu, or +<accept> them pressing (by default) the Return key. +

+Note that different remailers do have different capabilities, +indicated in the %c entry of the remailer menu lines (see +$mix_entry_format). Most important is +the “middleman” capability, indicated by a capital “M”: This +means that the remailer in question cannot be used as the final +element of a chain, but will only forward messages to other +mixmaster remailers. For details on the other capabilities, please +have a look at the mixmaster documentation. +

5.5. Sending format=flowed messages

5.5.1. Concept

+format=flowed-style messages (or f=f +for short) are text/plain messages that consist of paragraphs which a receiver's +mail client may reformat to its own needs which mostly means to +customize line lengths regardless of what the sender sent. Technically this is +achieved by letting lines of a “flowable” paragraph end in spaces +except for the last line. +

+While for text-mode clients like mutt it's the best way to assume only a +standard 80x25 character cell terminal, it may be desired to let the +receiver decide completely how to view a message. +

5.5.2. Mutt support

+Mutt only supports setting the required format=flowed +MIME parameter on outgoing messages if the $text_flowed +variable is set, specifically it does not add the +trailing spaces. +

+After editing the initial message text and before entering +the compose menu, mutt properly space-stuffes the message. +Space-stuffing is required by RfC3676 defining +format=flowed and means to prepend a space to: +

  • all lines starting with a space

  • lines starting with the word “From” +followed by space

  • all lines starting with “>” which +is not intended to be a quote character

Note

+Mutt only supports space-stuffing +for the first two types of lines but not for the third: It is impossible to +safely detect whether a leading > character starts a +quote or not. Furthermore, Mutt only applies space-stuffing +once after the initial edit is finished. +

+All leading spaces are to be removed by receiving clients to restore +the original message prior to further processing. +

5.5.3. Editor considerations

+As mutt provides no additional features to compose f=f +messages, it's completely up to the user and his editor to produce +proper messages. Please consider your editor's documentation if you +intend to send f=f messages. +

+Please note that when editing messages from the compose menu several +times before really sending a mail, it's up to the user to ensure that +the message is properly space-stuffed. +

+For example, vim provides the w +flag for its formatoptions setting to assist in +creating f=f messages, see :help +fo-table for details. +

6. Forwarding and Bouncing Mail

+Bouncing and forwarding let you send an existing message to recipients +that you specify. Bouncing a message sends a verbatim copy of a message +to alternative addresses as if they were the message's original +recipients specified in the Bcc header. +Forwarding a message, on the other hand, allows you to modify the message +before it is resent (for example, by adding your own comments). Bouncing +is done using the <bounce> function and forwarding +using the <forward> function bound to “b” and “f” +respectively. +

+Forwarding can be done by including the original message in the new +message's body (surrounded by indicating lines) or including it as a MIME +attachment, depending on the value of the $mime_forward variable. Decoding of attachments, +like in the pager, can be controlled by the $forward_decode and $mime_forward_decode variables, +respectively. The desired forwarding format may depend on the content, +therefore $mime_forward is a quadoption which, for +example, can be set to “ask-no”. +

+The inclusion of headers is controlled by the current setting of the +$weed variable, unless $mime_forward is set. +

+Editing the message to forward follows the same procedure as sending or +replying to a message does. +

7. Postponing Mail

+At times it is desirable to delay sending a message that you have +already begun to compose. When the <postpone-message> function is +used in the compose menu, the body of your message and attachments +are stored in the mailbox specified by the $postponed variable. This means that you can recall the +message even if you exit Mutt and then restart it at a later time. +

+Once a message is postponed, there are several ways to resume it. From the +command line you can use the “-p” option, or if you compose a new +message from the index or pager you will be prompted if postponed +messages exist. If multiple messages are currently postponed, the +postponed menu will pop up and you can select which message you would +like to resume. +

Note

+If you postpone a reply to a message, the reply setting of +the message is only updated when you actually finish the message and +send it. Also, you must be in the same folder with the message you +replied to for the status of the message to be updated. +

+See also the $postpone quad-option. +

Prev   Next
Chapter 1. Introduction Home Chapter 3. Configuration
diff --git a/obj-i486-linux-gnu-patched/doc/index.html b/obj-i486-linux-gnu-patched/doc/index.html new file mode 100644 index 0000000..acf7a2a --- /dev/null +++ b/obj-i486-linux-gnu-patched/doc/index.html @@ -0,0 +1,178 @@ + + +The Mutt E-Mail Client
The Mutt E-Mail Client
   Next

The Mutt E-Mail Client

Michael Elkins

version 1.5.19 (2009-01-05)

Abstract

+“All mail clients suck. This one just sucks less.” -me, circa 1995 +

Table of Contents

1. Introduction
1. Mutt Home Page
2. Mailing Lists
3. Software Distribution Sites
4. Mutt online resources
5. Contributing to Mutt
6. Typograhical conventions
7. Copyright
2. Getting Started
1. Core concepts
2. Moving Around in Menus
3. Editing Input Fields
3.1. Introduction
3.2. History
4. Reading Mail - The Index and Pager
4.1. The Message Index
4.2. The Pager
4.3. Threaded Mode
4.4. Miscellaneous Functions
5. Sending Mail
5.1. Introduction
5.2. Editing the message header
5.3. Sending cryptographically signed/encrypted messages
5.4. Sending anonymous messages via mixmaster
5.5. Sending format=flowed messages
6. Forwarding and Bouncing Mail
7. Postponing Mail
3. Configuration
1. Location of initialization files
2. Syntax of Initialization Files
3. Address groups
4. Defining/Using aliases
5. Changing the default key bindings
6. Defining aliases for character sets
7. Setting variables based upon mailbox
8. Keyboard macros
9. Using color and mono video attributes
10. Message header display
11. Alternative addresses
12. Mailing lists
13. Using Multiple spool mailboxes
14. Monitoring incoming mail
15. User defined headers
16. Specify default save mailbox
17. Specify default Fcc: mailbox when composing
18. Specify default save filename and default Fcc: mailbox at once
19. Change settings based upon message recipients
20. Change settings before formatting a message
21. Choosing the cryptographic key of the recipient
22. Adding key sequences to the keyboard buffer
23. Executing functions
24. Message Scoring
25. Spam detection
26. Setting and Querying Variables
26.1. Commands
26.2. User-defined variables
27. Reading initialization commands from another file
28. Configuring features conditionnaly
29. Removing hooks
30. Format Strings
30.1. Basic usage
30.2. Filters
4. Advanced Usage
1. Regular Expressions
2. Patterns: Searching, Limiting and Tagging
2.1. Pattern Modifier
2.2. Simple Patterns
2.3. Complex Patterns
2.4. Searching by Date
3. Using Tags
4. Using Hooks
4.1. Message Matching in Hooks
5. External Address Queries
6. Mailbox Formats
7. Mailbox Shortcuts
8. Handling Mailing Lists
9. Handling multiple folders
10. Editing threads
10.1. Linking threads
10.2. Breaking threads
11. Delivery Status Notification (DSN) Support
12. Start a WWW Browser on URLs
5. Mutt's MIME Support
1. Using MIME in Mutt
1.1. Viewing MIME messages in the pager
1.2. The Attachment Menu
1.3. The Compose Menu
2. MIME Type configuration with mime.types
3. MIME Viewer configuration with mailcap
3.1. The Basics of the mailcap file
3.2. Secure use of mailcap
3.3. Advanced mailcap Usage
3.4. Example mailcap files
4. MIME Autoview
5. MIME Multipart/Alternative
6. Attachment Searching and Counting
7. MIME Lookup
6. Optional features
1. General notes
1.1. Enabling/disabling features
1.2. URL syntax
2. SSL/TLS Support
3. POP3 Support
4. IMAP Support
4.1. The Folder Browser
4.2. Authentication
5. SMTP Support
6. Managing multiple accounts
7. Local caching
7.1. Header caching
7.2. Body caching
7.3. Maintenance
8. Exact address generation
7. Performance tuning
1. Reading and writing mailboxes
2. Reading messages from remote folders
3. Searching and limiting
8. Reference
1. Command line options
2. Configuration Commands
3. Configuration variables
3.1. abort_nosubject
3.2. abort_unmodified
3.3. alias_file
3.4. alias_format
3.5. allow_8bit
3.6. allow_ansi
3.7. arrow_cursor
3.8. ascii_chars
3.9. askbcc
3.10. askcc
3.11. assumed_charset
3.12. attach_charset
3.13. attach_format
3.14. attach_sep
3.15. attach_split
3.16. attribution
3.17. autoedit
3.18. auto_tag
3.19. beep
3.20. beep_new
3.21. bounce
3.22. bounce_delivered
3.23. braille_friendly
3.24. check_mbox_size
3.25. charset
3.26. check_new
3.27. collapse_unread
3.28. uncollapse_jump
3.29. compose_format
3.30. config_charset
3.31. confirmappend
3.32. confirmcreate
3.33. connect_timeout
3.34. content_type
3.35. copy
3.36. crypt_use_gpgme
3.37. crypt_use_pka
3.38. crypt_autopgp
3.39. crypt_autosmime
3.40. date_format
3.41. default_hook
3.42. delete
3.43. delete_untag
3.44. digest_collapse
3.45. display_filter
3.46. dotlock_program
3.47. dsn_notify
3.48. dsn_return
3.49. duplicate_threads
3.50. edit_headers
3.51. editor
3.52. encode_from
3.53. envelope_from_address
3.54. escape
3.55. fast_reply
3.56. fcc_attach
3.57. fcc_clear
3.58. folder
3.59. folder_format
3.60. followup_to
3.61. force_name
3.62. forward_decode
3.63. forward_edit
3.64. forward_format
3.65. forward_quote
3.66. from
3.67. gecos_mask
3.68. hdrs
3.69. header
3.70. help
3.71. hidden_host
3.72. hide_limited
3.73. hide_missing
3.74. hide_thread_subject
3.75. hide_top_limited
3.76. hide_top_missing
3.77. history
3.78. history_file
3.79. honor_followup_to
3.80. hostname
3.81. ignore_linear_white_space
3.82. ignore_list_reply_to
3.83. imap_authenticators
3.84. imap_check_subscribed
3.85. imap_delim_chars
3.86. imap_headers
3.87. imap_idle
3.88. imap_keepalive
3.89. imap_list_subscribed
3.90. imap_login
3.91. imap_pass
3.92. imap_passive
3.93. imap_peek
3.94. imap_pipeline_depth
3.95. imap_servernoise
3.96. imap_user
3.97. implicit_autoview
3.98. include
3.99. include_onlyfirst
3.100. indent_string
3.101. index_format
3.102. ispell
3.103. keep_flagged
3.104. locale
3.105. mail_check
3.106. mailcap_path
3.107. mailcap_sanitize
3.108. maildir_mtime
3.109. header_cache
3.110. maildir_header_cache_verify
3.111. header_cache_pagesize
3.112. maildir_trash
3.113. mark_old
3.114. markers
3.115. mask
3.116. mbox
3.117. mbox_type
3.118. metoo
3.119. menu_context
3.120. menu_move_off
3.121. menu_scroll
3.122. meta_key
3.123. mh_purge
3.124. mh_seq_flagged
3.125. mh_seq_replied
3.126. mh_seq_unseen
3.127. mime_forward
3.128. mime_forward_decode
3.129. mime_forward_rest
3.130. mix_entry_format
3.131. mixmaster
3.132. move
3.133. message_cachedir
3.134. message_cache_clean
3.135. message_format
3.136. narrow_tree
3.137. net_inc
3.138. pager
3.139. pager_context
3.140. pager_format
3.141. pager_index_lines
3.142. pager_stop
3.143. crypt_autosign
3.144. crypt_autoencrypt
3.145. pgp_ignore_subkeys
3.146. crypt_replyencrypt
3.147. crypt_replysign
3.148. crypt_replysignencrypted
3.149. crypt_timestamp
3.150. sidebar_delim
3.151. sidebar_visible
3.152. sidebar_width
3.153. pgp_use_gpg_agent
3.154. crypt_verify_sig
3.155. smime_is_default
3.156. smime_ask_cert_label
3.157. smime_decrypt_use_default_key
3.158. pgp_entry_format
3.159. pgp_good_sign
3.160. pgp_check_exit
3.161. pgp_long_ids
3.162. pgp_retainable_sigs
3.163. pgp_autoinline
3.164. pgp_replyinline
3.165. pgp_show_unusable
3.166. pgp_sign_as
3.167. pgp_strict_enc
3.168. pgp_timeout
3.169. pgp_sort_keys
3.170. pgp_mime_auto
3.171. pgp_auto_decode
3.172. pgp_mime_signature_filename
3.173. pgp_mime_signature_description
3.174. pgp_decode_command
3.175. pgp_getkeys_command
3.176. pgp_verify_command
3.177. pgp_decrypt_command
3.178. pgp_clearsign_command
3.179. pgp_sign_command
3.180. pgp_encrypt_sign_command
3.181. pgp_encrypt_only_command
3.182. pgp_import_command
3.183. pgp_export_command
3.184. pgp_verify_key_command
3.185. pgp_list_secring_command
3.186. pgp_list_pubring_command
3.187. forward_decrypt
3.188. smime_timeout
3.189. smime_encrypt_with
3.190. smime_keys
3.191. smime_ca_location
3.192. smime_certificates
3.193. smime_decrypt_command
3.194. smime_verify_command
3.195. smime_verify_opaque_command
3.196. smime_sign_command
3.197. smime_sign_opaque_command
3.198. smime_encrypt_command
3.199. smime_pk7out_command
3.200. smime_get_cert_command
3.201. smime_get_signer_cert_command
3.202. smime_import_cert_command
3.203. smime_get_cert_email_command
3.204. smime_default_key
3.205. ssl_client_cert
3.206. ssl_force_tls
3.207. ssl_starttls
3.208. certificate_file
3.209. ssl_use_sslv3
3.210. ssl_use_tlsv1
3.211. ssl_min_dh_prime_bits
3.212. ssl_ca_certificates_file
3.213. pipe_split
3.214. pipe_decode
3.215. pipe_sep
3.216. pop_authenticators
3.217. pop_auth_try_all
3.218. pop_checkinterval
3.219. pop_delete
3.220. pop_host
3.221. pop_last
3.222. pop_reconnect
3.223. pop_user
3.224. pop_pass
3.225. post_indent_string
3.226. postpone
3.227. postponed
3.228. preconnect
3.229. print
3.230. print_command
3.231. print_decode
3.232. print_split
3.233. prompt_after
3.234. query_command
3.235. query_format
3.236. quit
3.237. quote_regexp
3.238. read_inc
3.239. read_only
3.240. realname
3.241. recall
3.242. record
3.243. reply_regexp
3.244. reply_self
3.245. reply_to
3.246. resolve
3.247. reverse_alias
3.248. reverse_name
3.249. reverse_realname
3.250. rfc2047_parameters
3.251. save_address
3.252. save_empty
3.253. save_history
3.254. save_name
3.255. score
3.256. score_threshold_delete
3.257. score_threshold_flag
3.258. score_threshold_read
3.259. send_charset
3.260. sendmail
3.261. sendmail_wait
3.262. shell
3.263. sig_dashes
3.264. sig_on_top
3.265. signature
3.266. simple_search
3.267. smart_wrap
3.268. smileys
3.269. sleep_time
3.270. smtp_authenticators
3.271. smtp_pass
3.272. smtp_url
3.273. sort
3.274. sort_alias
3.275. sort_aux
3.276. sort_browser
3.277. sort_re
3.278. spam_separator
3.279. spoolfile
3.280. status_chars
3.281. status_format
3.282. status_on_top
3.283. strict_threads
3.284. suspend
3.285. text_flowed
3.286. thread_received
3.287. thorough_search
3.288. tilde
3.289. time_inc
3.290. timeout
3.291. tmpdir
3.292. to_chars
3.293. trash
3.294. tunnel
3.295. use_8bitmime
3.296. use_domain
3.297. use_envelope_from
3.298. use_from
3.299. use_idn
3.300. use_ipv6
3.301. user_agent
3.302. visual
3.303. wait_key
3.304. weed
3.305. wrap
3.306. wrap_search
3.307. wrapmargin
3.308. write_inc
3.309. write_bcc
3.310. xterm_icon
3.311. xterm_set_titles
3.312. xterm_title
4. Functions
4.1. generic menu
4.2. index menu
4.3. pager menu
4.4. alias menu
4.5. query menu
4.6. attach menu
4.7. compose menu
4.8. postpone menu
4.9. browser menu
4.10. pgp menu
4.11. smime menu
4.12. mix menu
4.13. editor menu
9. Miscellany
1. Acknowledgements
2. About this document

List of Tables

1.1. Typographical conventions for special terms
2.1. Most common navigation keys
2.2. Most common line editor keys
2.3. Most common message index keys
2.4. Message status flags
2.5. Message recipient flags
2.6. Most common pager keys
2.7. ANSI escape sequences
2.8. Color sequences
2.9. Most common thread mode keys
2.10. Most common mail sending keys
2.11. Most common compose menu keys
2.12. PGP key menu flags
3.1. Symbolic key names
4.1. POSIX regular expression character classes
4.2. Regular expression repetition operators
4.3. GNU regular expression extensions
4.4. Pattern modifiers
4.5. Simple search keywords
4.6. Date units
8.1. Command line options
8.2. Default generic function bindings
8.3. Default index function bindings
8.4. Default pager function bindings
8.5. Default alias function bindings
8.6. Default query function bindings
8.7. Default attach function bindings
8.8. Default compose function bindings
8.9. Default postpone function bindings
8.10. Default browser function bindings
8.11. Default pgp function bindings
8.12. Default smime function bindings
8.13. Default mix function bindings
8.14. Default editor function bindings

List of Examples

3.1. Multiple configuration commands per line
3.2. Commenting configuration files
3.3. Escaping quotes in congfiguration files
3.4. Using external command's output in configuration files
3.5. Using environment variables in configuration files
3.6. Configuring external alias files
3.7. Setting sort method based on mailbox name
3.8. Header weeding
3.9. Configuring header display order
3.10. Defining custom headers
3.11. Using %-expandos in save-hook
3.12. Embedding push in folder-hook
3.13. Configuring spam detection
3.14. Using user-defined variables for config file readability
3.15. Using user-defined variables for backing up other config option values
3.16. Deferring user-defined variable expansion to runtime
3.17. Using external filters in format strings
4.1. Using boolean operators in patterns
4.2. Combining send-hook and my_hdr
5.1. Attachment counting

1. Compressed folders Support (OPTIONAL)

+If Mutt was compiled with compressed folders support (by running the +configure script with the +--enable-compressed flag), Mutt can open folders +stored in an arbitrary format, provided that the user has a script to +convert from/to this format to one of the accepted. + +The most common use is to open compressed archived folders e.g. with +gzip. + +In addition, the user can provide a script that gets a folder in an +accepted format and appends its context to the folder in the +user-defined format, which may be faster than converting the entire +folder to the accepted format, appending to it and converting back to +the user-defined format. + +There are three hooks defined (open-hook, close-hook and append-hook) which define commands to +uncompress and compress a folder and to append messages to an existing +compressed folder respectively. + +For example: + +

+open-hook \\.gz$ "gzip -cd %f > %t" 
+close-hook \\.gz$ "gzip -c %t > %f"
+append-hook \\.gz$ "gzip -c %t >> %f" 
+

+ +You do not have to specify all of the commands. If you omit append-hook, the folder will be open and +closed again each time you will add to it. If you omit close-hook (or give empty command) , the +folder will be open in the mode. If you specify append-hook though you'll be able to +append to the folder. + +Note that Mutt will only try to use hooks if the file is not in one of +the accepted formats. In particular, if the file is empty, mutt +supposes it is not compressed. This is important because it allows the +use of programs that do not have well defined extensions. Just use +"." as a regexp. But this may be surprising if your +compressing script produces empty files. In this situation, unset +$save_empty, so that +the compressed file will be removed if you delete all of the messages. +

1.1. Open a compressed mailbox for reading

+Usage: open-hook regexp "command" + +The command is the command that can be used for +opening the folders whose names match regexp. + +The command string is the printf-like format +string, and it should accept two parameters: %f, which is +replaced with the (compressed) folder name, and %t which is +replaced with the name of the temporary folder to which to write. + +%f and %t can be repeated any number of times in the +command string, and all of the entries are replaced with the +appropriate folder name. In addition, %% is replaced by +%, as in printf, and any other %anything is left as is. + +The command should not remove the original compressed file. The +command should return non-zero exit status if it +fails, so mutt knows something's wrong. + +Example: + +

+open-hook \\.gz$ "gzip -cd %f > %t" 
+

+ +If the command is empty, this operation is +disabled for this file type. +

1.2. Write a compressed mailbox

+Usage: close-hook regexp "command" + +This is used to close the folder that was open with the open-hook command after some changes were +made to it. + +The command string is the command that can be +used for closing the folders whose names match +regexp. It has the same format as in the open-hook command. Temporary folder in this +case is the folder previously produced by the open-hook command. + +The command should not remove the decompressed file. The +command should return non-zero exit status if it +fails, so mutt knows something's wrong. + +Example: + +

+close-hook \\.gz$ "gzip -c %t > %f"
+

+ +If the command is empty, this operation is +disabled for this file type, and the file can only be open in the +read-only mode. + +close-hook is not called when you +exit from the folder if the folder was not changed. +

1.3. Append a message to a compressed mailbox

+Usage: append-hook regexp "command" + +This command is used for saving to an existing compressed folder. The +command is the command that can be used for +appending to the folders whose names match +regexp. It has the same format as in the open-hook command. The temporary folder in +this case contains the messages that are being appended. + +The command should not remove the decompressed file. The +command should return non-zero exit status if it +fails, so mutt knows something's wrong. + +Example: + +

+append-hook \\.gz$ "gzip -c %t >> %f" 
+

+ +When append-hook is used, the folder +is not opened, which saves time, but this means that we can not find +out what the folder type is. Thus the default ($mbox_type) type is always +supposed (i.e. this is the format used for the temporary folder). + +If the file does not exist when you save to it, close-hook is called, and not append-hook. append-hook is only for appending to +existing folders. + +If the command is empty, this operation is +disabled for this file type. In this case, the folder will be open and +closed again (using open-hook and +close-hookrespectively) each time you +will add to it. +

1.4. Encrypted folders

+The compressed folders support can also be used to handle encrypted +folders. If you want to encrypt a folder with PGP, you may want to use +the following hooks: + +

+open-hook  \\.pgp$ "pgp -f < %f > %t"
+close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
+

+ +Please note, that PGP does not support appending to an encrypted +folder, so there is no append-hook defined. + +If you are using GnuPG instead of PGP, you may use the following hooks +instead: + +

+open-hook  \\.gpg$ "gpg --decrypt < %f > %t"
+close-hook \\.gpg$ "gpg --encrypt --recipient YourGpgUserIdOrKeyId < %t > %f"
+

+ +Note: the folder is temporary stored +decrypted in the /tmp directory, where it can be read by your system +administrator. So think about the security aspects of this. +

   Next
   Chapter 1. Introduction
diff --git a/obj-i486-linux-gnu-patched/doc/instdoc.sh b/obj-i486-linux-gnu-patched/doc/instdoc.sh new file mode 100644 index 0000000..1e283d0 --- /dev/null +++ b/obj-i486-linux-gnu-patched/doc/instdoc.sh @@ -0,0 +1,25 @@ +#!/bin/sh -- + +prefix=/usr +exec_prefix=${prefix} +bindir=${exec_prefix}/bin +libdir=${exec_prefix}/lib +mandir=/usr/share/man +srcdir=../../doc +datarootdir=${prefix}/share +docdir=/usr/share/doc +includedir=${prefix}/include +top_srcdir=../.. +top_builddir=.. + +SOURCE="$1" +TARGET="$2" + + +rm -f "$TARGET" + +sed -e "s;/usr/local/bin/;$bindir/;g" \ + -e "s;/usr/local/doc/mutt/;$docdir/;g" \ + "$SOURCE" > $TARGET + +chmod 644 "$TARGET" diff --git a/obj-i486-linux-gnu-patched/doc/intro.html b/obj-i486-linux-gnu-patched/doc/intro.html new file mode 100644 index 0000000..b9c322b --- /dev/null +++ b/obj-i486-linux-gnu-patched/doc/intro.html @@ -0,0 +1,108 @@ + + +Chapter 1. Introduction
Chapter 1. Introduction
Prev   Next

Chapter 1. Introduction

Table of Contents

1. Mutt Home Page
2. Mailing Lists
3. Software Distribution Sites
4. Mutt online resources
5. Contributing to Mutt
6. Typograhical conventions
7. Copyright

+Mutt is a small but very powerful text-based MIME mail client. Mutt is +highly configurable, and is well suited to the mail power user with advanced +features like key bindings, keyboard macros, mail threading, regular +expression searches and a powerful pattern matching language for selecting +groups of messages. +

1. Mutt Home Page

+The official homepage can be found at +http://www.mutt.org/. +

2. Mailing Lists

+To subscribe to one of the following mailing lists, send a message with the +word subscribe in the body to +list-name-request@mutt.org. +

Note

+All messages posted to +mutt-announce are automatically forwarded to +mutt-users, so you do not need to be subscribed to +both lists. +

3. Software Distribution Sites

+Mutt releases can be downloaded from +ftp://ftp.mutt.org/mutt/. +For a list of mirror sites, please refer to +http://www.mutt.org/download.html. +

4. Mutt online resources

Bug Tracking System

+The official mutt bug tracking system can be found at +http://dev.mutt.org/ +

Wiki

+An (unofficial) wiki can be found +at http://wiki.mutt.org/. +

IRC

+For the IRC user community, visit channel #mutt on +irc.freenode.net. +

USENET

+For USENET, see the newsgroup comp.mail.mutt. +

5. Contributing to Mutt

+There are various ways to contribute to the Mutt project. +

+Especially for new users it may be helpful to meet other new and +experienced users to chat about Mutt, talk about problems and share +tricks. +

+Since translations of Mutt into other languages are highly appreciated, +the mutt developers always look for skilled translators that help +improve and continue to maintain stale translations. +

+For contributing code patches for new features and bug fixes, please +refer to the developer pages at +http://dev.mutt.org/ for more details. +

6. Typograhical conventions

+This section lists typographical conventions followed throughout this +manual. See table Table 1.1, “Typographical conventions for special terms” for typographical +conventions for special terms. +

Table 1.1. Typographical conventions for special terms

ItemRefers to...
printf(3)UNIX manual pages, execute man 3 printf
<PageUp>named keys
<create-alias>named Mutt function
^GControl+G key combination
$mail_checkMutt configuration option

+Examples are presented as: +

+mutt -v
+

+Within command synopsis, curly brackets (“{}”) denote a set +of options of which one is mandatory, square brackets +(“[]”) denote optional arguments, three dots +denote that the argument may be repeated arbitrary times. +

7. Copyright

+Mutt is Copyright (C) 1996-2009 Michael R. Elkins + and others. +

+This program is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 2 of the License, or +(at your option) any later version. +

+This program is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. +

+You should have received a copy of the GNU General Public License +along with this program; if not, write to the Free Software +Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. +

Prev   Next
The Mutt E-Mail Client Home Chapter 2. Getting Started
diff --git a/obj-i486-linux-gnu-patched/doc/makedoc b/obj-i486-linux-gnu-patched/doc/makedoc new file mode 100755 index 0000000000000000000000000000000000000000..7893511a7c4b0ad52672d28e6ada867879e814b1 GIT binary patch literal 38798 zcmdUYd3;nw_V2xYJK+Wb-Rvj<8%Qu9NeG((LJUhlkTqddun9?b63J$|n?*qaohWUL z6A+YH1l*Y!oN*jQ1koUjpg4-S;kYq^+7TS%2Dp*;{Z`%E-D#Ma-+Q0;{&*Lv&pB16 zPMtb+YPogm-mJ-)I#E?s#k?$vrjUAKy;UCuxT;pB3{xCR8zoukuk=%55yiA&)!;!m z0h}QQ!HS?Ebb*jAYpps%XV45xqihCoA+Lh4DjVe>Fu!7#=_2kZ(h%Y;in17i`=se}L|*E_Je?3aB3yyc9)VXc1RDb5yCU>JXot`ip&J72aXCVFgv$`RAc*<{ z{_kGYfx74j@d&*UOdGQ;s5f=wMH_TL=t%-s8wr#Iz&Hf*Q!nPHKI^V(+m|%?DR)4x zyApO@cd{|#o4SOeIr;XX2hW+Jkt(lUCIZOB4N>%rC_2GZ*5Idp=H&oFTbh>x$QLF7 zNcj~}bWIf9K1zO46kQa>zdDM3EsB0FiheMPzB7tG5JjJiqQ8!!pNOJ=h@$63(OskJ zGbJkh_n;e(S#`F3M|k3Bz=UT^+NOK}`r(N5<)C*&(2GHDkDwLwkCMW2_Kfs&#px_6 zt0;GRy!lmLr&DoGS?0`j6_t3ruB!2+`5uqUL;eDCk5HVGXMnS?q}=KAxC#~5iW0Bl zsjMm~_qs(|rO#WSR8)FP$_o{bx2me3xQej6pmHT3@{#gZlq&8bm)Aq0)Kv}@Tvb)& z70%L%f_!gDMY)1R2w{#2pI31Usr>aQ?t;<^kBb=#@;$DCvPxtw@UER^@8=2ID#kT2sav zv|Z2^XM^d!Q11rS6`e zTUuIbk9lK)HzGDT0M!aUm8K~3Z+Q7Y%kWC%Y)SIsmw8%}Xn|s)O(&48C5e_OW?Iux zLDM3|G`plR9S`J@L6nieizOxhu6TDq7OYO)KO7B8+Otq7WyFJ3{q z`2r%6*aF4Xq)!N%Em6Fl^ie^xMT#3pHwv09Q@n-r6M|+76>lfKUC?Z);vJ+L1kDyJ zeu8whpxJW8yGd7qPXF@8z(4(`nrF_=End6}DV6w{HMh9oDXSj*3Jl*hw7QJ;t{!s` z4y^dH>$)BWvU@$24JkGF*?-Khwp3 ze&Mq2f!T@HKtf{hP3Z1F*agBH>b?Dymc-ic_F{Qc`?A!_`z{$Fbuk9+;Idy@T28+~ zzS@_)`;3$oOj*d3XWYo=eZ+_#$@mG3-zMVgjra=24`TcsjJMU?jOI1ca+zjFT2nD1 zQC+6b3a1ZddNcY>)3xFB^lmz6DG#W;&hCNdJ8}{W_*!%XB)Mksb)A7co7V>2x-vqdn)%#R!p5mlI#N zTCelj13AqPC}?{Bd3AZ8x;f3Y$85E+7y$#T;{!h3e=y;O8=Z@qPW^=JXb=B+i?^K- zNjC|sN{kPDduT$Uj=@X;v~s{jJFa2L&!c49uGq{>-{__$#Jd|ZoqJM%G$mVZUy>0ymRNF4CrqOqp<**d410zcL?QWDZAMABG z&2US{>B9P_`h!KWJ>U2&H3|F}EI~6%X)i%qETny6O5^Ggzs~^BLG`dV;xb+VQ$MAJnZ5`kU0ioHK!G&9)jp>Rz`^F2PY!%zd;Y~pahee4 za|Uk$68PG->y0|)?1Y)ndupJ0{rDDCD6r^^ZP(R-Z)%QtGtkohvS!tr7Wk%qd`tC@ z3j;Z4Y&Fn8ar;+)rg*mnzOMdZp{?c=Vgk*XeSLc%0QRYyb|!HCB^6xKn6?@YwIa{% zzoI#9HB(R@Xb;`ug^k$Wdy#@3W^ZMqK2Wrk72hORq!n9!plf6X&a+F%am*~&n=G={ z%{f8&M_bu{Ho6GfU_WxB4eF+SP(Mjsf7we|sz8_!>} zEaklw^<2{}Gv8Kw2+sG?_?9;AhNkCaf6lBj#?OhFUiMF0?L(3$PR2KFl6nNjxdvYKEXUdz$dle^X0g@$0y@+tJEN7_aGu;v$HC-o2(jH4-6%JK z?ew|^LtimpWdv6L95_^$qX!m!7npM*;5#39F>pYRa-VecpL`7-jN#5Zu&M{gv(czW z;CP+yeBGk&>X7pc+ScDZ)2!sCMDD0N!%C8WN=g5e6mE5PDElHJq-6Jr1+E0(U2I=)0!D)8M|u%0~UKcY6h z0q(O0EVf!Jn9m-tiu&7XUqkiI9@33=@b*K!FClQ1S?Px$aP7$-pn;g0&K|OcvS7rC z)Zt6EIPFx4EQex_a?HflG#Pq?$?7B3O;;nP_L#3(1*}pabsjzC@v=f|r1M!K$=I>fsYTma6PQZ8Td?y0K5`%yL9$C+~2^?C}N477_ zhOUY+)PcfaDQmDTrMI-X?bGU$YiOgo;{F_{$#891LslET58i) z;II@usi{9)IBbvV&wpyFHu48?UlsRe)6Ha_)-0Xl5{3W3c4Xm;S@?J<8um0<{U?6_ zYMLv?^xz@n?n-VSY9&m@TCF|#3w$sl!!M?rsLa514?G#oV~SsU@~74rRMVx8ev1r$ zWd=CK$#cxWZ7?`Ng!n5>eI6utttmc^+&#b@!P>zTyqv7plXcDs+pbPE$JWpJ+*UIg z5!I_d?`x~M3Oi)LFg^ZSVkr%_nwhXBy!M5gAmv$hsc#>()&7WESfgVCi!3a#$LM8k zQJ6pHgv!vWy!S9ap1#}Y-@=(Vp2L|qKKeRytg$9?{6OPagD1Z+EG_&es<1fLj9u}5 za5Ys!FmuBKQG650$ENm?Z$A0vpe?e=8Z}ad{Cx^pQ^1NL#a8oYw6QT9L=C^!nL1p? z3_oKAG<1ks)lK9WOdY=d8hme&k2(l{pbi)L!&VAr7iwgNhooS`KV^50^v@%-JH>A# zw~yTL9_gRB&%f9|@1S@N$@$DM!4NNJm?+hsG|e}Hte1gRG}{(*0*(Pc&o59g_fjKR zJF;QfPCdYiQOj0y4jtQYf~bi&(R6|{UqS5a;H!RJMV`={6=kk-v;ya>=fH1RG)kmm z&h5XZ$W<&_PFvh6k5Kayieim!Cf{uE$pwJ#KP>>rKbA#v=n`W~RCn2HD%g`!FJR6( zdqB62!DIzcX#_Qm1 zI!M0gg19Yt>5la=`#&>pGz)r}%aTiW!e&lQ;0;fo!G$a`ht9)MgA>gq=V}&^PSzV` z{~_O{YD~Y0Bi{v%E7BkNSSP|CD_L9e{qqd?xY{wg%%%7^usut@x44{;mX5Msp=s$2 zBe3Xv z-~jIjd_M=?sp~ZIAIrMDWKjbDfcV|?;Nagd=>>Y%EjnKZ4y^wJXG8m6`>~@McoW-M zI~=~^x~^|wxrj})+G7t9v(>(Z>}UUG@hv;MA5?(U{%m)Ht@bxS&+U)Jz#!(wEUYNg zj|JY_jZI!9IEUrEmws%wXas8_;*?-EXWkTwRk2gH+krUl#fj|$GdGtk!S2kx|McU$ zZ!x4|-dBPxn8^bBsYuOotg_5BPC8;fW*UY$cSIVWMFkIud{S9kO&*d@|0;CDHIw5n z+$FS^@WU4vr>%+bXeBu2G^`x8zu`aA!~bJj@0?}*{6EHfv;04{hn_x%`;fA*>ZNRp z@-pplz?g6RKgNlE?9IYZ%q5(49)}P#`^Ki0mX{AOms{jA?zcggODUpQQx5sOk}q1H zd2<8rb=|C zw(upsum~>tEXR$&N8di`n;>;%e`s={cEX=U_o;iDss|P(at&-f*s3GJPV}>#P~-HU z+zl@jM#}VFTlX~UUwhV8(+MKsiT?9xzU#49I?z_j=N8qsS_X>sTkSV!;p$s8MYfZ7 zwuDXZBO2{dC#+dlOUnh*FeZi#8xWCAPlD0i;6D$+FQ5*xi2H?5i-K`%Bhb2iw1M1! zyehcmGsM_W_h9*cVI8$j0Nbt}t#&9ssoTtarsV>gk5Wo)BkxR}X37gStTo3p+?>=@ zhvU~r#_tZt-xV4EQaHXLGQKm~-H^X2GQLkZeoJKhO0>Jd|GUWe``{}^{C383;zE1J zNo%~+#v!W*-$Ek>YM(-du$gY#b$QMEz9CJMAr*d_)BKV$5K9n$Ei12qL1Jp1voma=h>mi()tX_EGQtx~E0lj&Pic-rQrzN@2jh43katV>=U{Rf4~?wAN?LX!8N>32<#UesN=_Qpe!Thwu@2{ zMM~g+t!4?*9&m6|1tQj>BI##OcW%J?tj_wq8GRF?(RU#dqrMn#Pn}|!zT<)SBFlRX zBL;dPq{c&P^*-iU<;$zy_fH^-Z;I(zw%Vs4v31^!BCoCH7@WR!Emnl2?&2ar&abV? zog3oV1P)p5Am96DxyM?|OP1U(VrB)mZI`gssF*!yG+(OBGu4+=z3&sDbVA^b$SR%| z<4^#ZxngOZ_PR_%_1hyYT-h(sV_H}Ckr3xeEI(VRfaNmS(fseWv^?`=xp3jaxubnvT>D8iE^pJh7ptok#TUE(3%h^6 zMLD*c!>0c|?W%eT9dMXKuyhwL;($SvdYEIK@(C)~%Fh47NFv&|_U0C}#O4!_klrY? z47}^V&^EC7390Dqm$MF=DGN1090pXq1w*j#AI!xM{}WTiZ_rP+_UBO ziCDQDhc2?y;TBL2>1*vz9z5RK&2;PciRdGBPm9S80*1-^0G+#x_kn>~DR>&=5$9(n zllziue9S1pY2a!)!8Ly5xPLVl-!gB+-S=4Vu06AzT843wZ@y$Eez4=OVbcG7fV+ z9OhaJE~8i5Y9AKklIYpC+WSC+d+G3thNPC0rn{Gcvnd0DLd)!6tJMK&u@R$%xQhv~ z?29&Y1zEmD)mjpt&cMb;eeEacAV#-~>?9E9|A^zl{p>rOaNdIg!5PSpzK$q7E$NO2 zi*?p@>(T4+sPQt)VP~5D3aw2&r}rTf>5SrakVCf0jB=QRCK6GM(QuR#a8nh5KTV(G=x+P?L)#{6smd? z1X0xo(fm**q8V6R8$+q@K7gdzkQDMtK0gop+pteVUfEIfUUtiRJf09;vQ92GFf1fs zXHUlA<`Q?aC{zia!(?i>^jp}(#xpKk?GYey$YSkzjFReb(Tc9}AhqHiL3=1)cRyDH zFaTUW(>K2U{(k~FJzCnucz*BgBp%-zPw)GSr}uUH#Aty6KT=7w?~m`Jz@8MZB_YItF}sS3{J;@AeVy{qrE;xV~0BY`_Uc#HkQ33(rdV>81|YA zoMGj%{(aoj%jqg)cI!>70_GL=ilGoCtx12N+e9=-U+&3ZG!6dp4{#Y%m1tfvEtAb9 ztZ@bm!nU(eb79+S1rnY|GXx#BFHbIqCo&HB5e09eXij7`kc*=LqW=UBVS|=8vG7!S zPVf$DWvUZB7jBi6#QrC^n%-jnkc((O*a`opGs=3F(@+7wRE*>+*AO@B+ zviyoWfYQQz))unxGGUNbT>*Y4N3Ng?x7Lvs1~2x%Fju#>@EezK;>)R@;l$-oKvveM zeS2&c8@0D4_JvT?)*74#Hf9O=j9iMLrBf(C`Zvua7Gar*T+0MIG3npgf1zpr4=^#b z(x8sMBkdod!P{VK8beEoBxwbfC~9NuTWpV(bq!@nKR0A?WDSr_OaK%h7M0MqDFw@b z*0VH|H7bgV*1Q7+PQhU>o{~g^V?@X&%YIH1PaBI;ohRcdg&hE$Zx4mBcYX#|j?-{` zjMFn@vGu+a*orE{R#~7q_#HL|ZM$+#Ai00w+y5|xA3<%z5H3%=;B?lWP&4UKPi)?n zO&=e0Q`M(_Hq9wEg}L2-8-$(SWq2c>6C2*>n^3ozo+w?;m_55BqU#6W$Bk>GCvr0) zxQp|OxM4TPJw(R9d)S{v9jsNNWf!cVPZB zwETBg+#HpU>x*C|=UrplLrzL6w5IW{;bobzc^J6QiF7hm21;&D*#({Gt__i-Bq z`&X1!B!$zbPe1x^EpZ^U;D0FF7n=XyHI4wl5xmL$2@b|CbsNZP3(% z;}Exg5{*i>L4?@$#Itc6?`^sHXFQphn>ULmF&9|t(%H*!BwMM|I5~F{)p&?U`fN4n z&=gVx1vb40r-_9q7t6mCF#6B8*lIQ*um60Zx5BtzT{FUez5weRZ+U1nG1yoVg*NgB zBQp#~Lj=9R<^EBbx2ONS$9MQp3{Qn}U}pU3TDks{vCJZlYd5(4F+9YmHZ9@svrLic zNS4R78y?t>)RE2JHLPGhG_SMzS;H>J#I4Xv-g5sKQO>enAw_2!iZ4*J)LET=aHuX+P5 zqfmvhz~DP}p(5470yv~YFB%!f4jD^BIi|5D0XI%PqZRRp1_iX*&koLj%4-jNjq%fe zCO%kn6iV#1vo?PI4mh;G#ZueiO-w&qmm}_9aT=Fy%tut##FkBeB^P{nY^${8Z|a1+wyB=VwyAEfV|;Gg)N(fy+$C*OT?HZ%EJ#*T zbHO)rf@3hy*~rYFg~`P$9Z1O$De20>GgU~;Sy73iOUjEJg)Vo#uhi>UmS5^~8Gewr zw4}0&_5(FN zzsxlXG*f2djVTj1xMacvsf3vpA|ZqRkva|n+A3!Dwn~U$VR9)v1@00Nr@-rAY++kR z3HwLithSkGu2NT)(l(UUFglvj^d>Z(L^IQj1_^T~!_~Yi2Snsg^02i%gZOvqJSDHsY$ z9r=ZY%*L@!ztgI(4dC5az-tkT4VrQPH$$}{cgz1H`Tt4RCs5{5gzczPBf|0j%XRxt zWt(ZuMw!jfW5-75g0KbQ{tdACJyyLPLUIG%Pe$C=h?|Pg2jOFc9SBUj9cf1Z?*;FK zO?a0Y;ZxwxAnZVxzghCVhWLjNdlf|zpBVrhT$gPjeh9xVAygl_aqM(hlzH0!SXv2MV)JQ#lnR6+*!Z zM`=ZQQL4i+*0a=+?^s@POMVsO9jG+7@KllM@h#y?uUU@Ff{L=T{4BwPNl^@~ZOxI?7!A$QnqvpcT9RMr z5ZSOi5#@5mMB|CoiNQ0y!hwMluiUbs%ksSr52mRScZsV|6h%=A)^Oq$#)ORH%GnG& zy2u-)=G(10Z?t~iCEr=T7Vq?bf1#zqz7FrCB7Rs6-dzQp0Gd892LgB-$h|+ld(VsO zxzab}dc6@i4-s+`itpbKhJ4~WAn&M?5qL0}k7Test~gwa7x@6GS2N(9pn?8xU;I{q znQ6owR(&GETm(15GKAX^?nQVMVHd(n2=5?#hHw@k7T;v(hR`2j1j0mwxd?8AWeB$; z+>7uif?3XggS5+kx<+7~pM{WvFb!c2!a{@sgqsjd@4oDZ>Xyh;Iyb^&}lymr%>GW}?)5qz1<|XC$;d+v<5_3w^ATw1_q?{SZBGVJ# zC&aouBcaLJ2Z%+v3BUCSK7^=O@e!lUL$D|;>{axKDdrUWKF? zqH9kSJzJ?k#LTLSqH>G@%Do`ah`u6)2l+V0h$V;O7NS{**eny@7dZw$O-)Vntn?JR zDm`f>Lo-ICxk}w>;!^^tc}iMwMVTut-&f@-9XceVPPT{aco#`hjv7c?-oc+&~6ZrwuHYHbV%kZHgr*5NWZ?MOsV_ zfM$)s*9jDh9&;xn^)`G*++vOS6@b;+#-hgF1}ug*wCZJd@Ha-|#}#53qpU};C{FxZ z)pd-(_1~+t#D}}Z6nsg*C5(a(k)YP7Yg$2-x8(oWFo)3~7UgDWU>N2-IA{T!g+8?a zem4RQZ@ChY+B>dYeqh}Ed>~+ zanwNw6_&Gn#hAM*5EEl<6Kic_eNalJF)iOhshISqfa+fX-4v7Jg;sGtAtKhUUQd>O zO5B%-i|wlZPLS5PY2b|QW{`T^c&2tY$oRNkP$ssALE7UIP<-rV2H7R`nAbZ5c z!}DW%8e~G;n@mkGNJm^IMfEnw#JG=Owb&~RGCA%pk`99$6z3q>SA7!NSo#f)+re@Z z)!l*|7T1c~acl%sWDTO_0~deNOTk^)A6YHSRg)y;l8=AZN#Mw1L{LiE>MowvSP*r*!HOAG?QUXt$6#_DYK= z?Kp$SJ|_)gZMTf(YLqRkD{ZW|g13#8o)G^aeki8>eLxsXpAfO9%-Aat`vr&&4}w7? zwU|k56q~h8`VG+C{%4d}ZLzCJs_ZV}wGT#&u5`>Kp^mMl{8~gQ_E%98)qWdri~UF78Wd3Tej>xaKq~eD zg5el`E%s4lu&1JMtNjlA#@IXIH`dN2M;rSsz;*jbh>ElS8Zm9{k0Pd>{XYE0+doBo zd;1Ug?Oj^u zz11RILwN{^T|J6=i-oP#m7iq+&e(1xg^Ie$@*s*p^Zg#bUG9Z4>di*ZkBpp^5jiVG z&hC60L#?#XU6dZLvbZlq@yZX#a~Vo&;^3fMuC7FyrI#vH(JlkgeGrPUB&bwI>A8m$ z>1|P!DM;#Cps2kp8~~-3y+m0FFHrmy7IH|}x*nMDMVrzk4&|wLt5O^b>wXh#rPj;3 z_uP*>>UEI67fD^0De9Dnx=e|XKUK)@)%y*|>&-^$y%#^Qh>PO!;rBONJx37~cGEVaj)OmrhBbOFjxszt=%mLj; z*jc7?#iI08Q5RU(s@fsMe;1Z~pg*P{ku_*#*1sXHPY39#2CZzO0Zdn$JU=0~WEwFvUkoG`%H;^|%MLtcN9r_5KTJbZ%z6Vk=8%FKv|#=>_*&^$(DK zkR^z^#|w>kD<@^f3)?ILtqgqu&Y*U-sFld|Ey4!G{>+>wD7KS@MeJivcyuSxi{BUd z?qYHh+;*!~Ux)AmVi!FAW|J@>75R|_m%ibJdBv( zV}MyUETmF>*P6t1IDB7}Ew(S2;P zMbu2F-4*W8K{SFKpgIVXcNeDXAj~ZXD|-yNyTQRb3hr)bE{Tm8hJ*ysH482E}&zhR{J>iu`Lf3J*p#qTNnW;El6 zR~u_N@^-iyXwOHf^M|m~IYf2E@bZDQ66*PZ7^G>r55zbwr;HDT{1N-Wp71ZW{5e_R zh}T0g7mS#%5M$IZ*1}eh7K)YgA(}2;DAaQ)TVbO`RUgA$P* z-e^PNs3WqGsdp(Qjkqq1E+HBkt9xZ|oCe2oMn_FvBi4no_3FI=f_mS9pI#aF^Ea9q zLPkD`AN3h^J37)`Phpo7*?IGsj8CYkyXaR}BPLmlHiDcFa@5Dnw3`mEZ8%;r3SSFR z)MpLSIRNgqhaOh*SKxXs0y0-IY}P`EjrRZNgv*}X7udsR(&zT4cLRq z6!Ys_NywZjrdNR~qjwIb=yl>QOOd?3A#0qK1hKZz@lI{XV@u+fZ+ zvp|OPgOnCuWk1eo^XVv^Vumo2nAj345i{Hd7OU^oZEG@m0!z9QKd*uX*XZU4F_I!w zgHAIEso;mKl2q_RS)D-~KN?uZiQX=t={Ml#3*<};vKT!05qb?@4aB2PF3A zHA$O+y=DW~12Sscnttq2&1|~&)O(TAdjQ%ty%&C5aF*U3NyXsD4{9)18AJaFe?n0I zZb>G8$a@o$kt$Xi$H8k%pHG7Gb8^3KnM&>`ryj;dUN-Wn$1P!}PMnXJ;dE@vhWTQ_ zvg$9`218JDEnyL220kmw!V1WPdQ=KY>JKbw8|dDf`BR6V^tJfO$DR9V?yBb?d;+Gd ztTdC%cpD5E|HKd0NL=^M2hTDD^-I+l0Y>-2X8j<9UMLe;O)_IBvtA>zrfxyjks>|u z37{FBnRbOp8(sCVRlgHqk<4$B8Q-EYGFtEh^(G*F8p2x1W0DzflILT=(~ryF!>sBf z>VsetLuld&md0TeF7)a{R{d=RC~2Y@f2DvIgaEKyqk6%rt`=h;Kl;Xvi~X=qPlW7Q z^sZH+>tZ7}`)9hxDlSkKfgFG(!EH>thXj_PYdDxZ2SORumYm;yh3qj}^)ahHWCA-< zTVrX&S5C*yW#R_jsH*DNS|rD8G>AQr5Oa?~%^`Qk8zCqEAg8+ z79ob`SH?M6(o!xn5yP`0@w`#v?wPo|Xs3+dz%p-EcOVKZ4zMV5!ERB0fH14dMWzCy zh#j(mf?;!S@ea>V_52U^nJ%?`rgl{9u^rV;s;2kUll0DP7`3CC)S+`btwYZaOtE7X zYDrYuwaY>jI<0|14ZNt!Sg12h(K?K3H@e;A&ez0S(0H-^mC2ojD2SgE`(K223*`=r zM@fcw4JE~xCB@oMBqm(~mY{c5wGQptv1}D&Tze@hW^(5YsL|GxjQeLJ1-Y0Kud0(f zGe`SA&@>GqJ4lsr+a4BYPlmVz496XKPj_-NTZ!^O$M5{#A*h4pF&XX_oK zq(l4_Va~~&*{s>IRNfI*&ceHqutp^NMwS`Q)UTJC-g!>!{B{e30TSD(bHJQ53*( zg!&JT)P^Zo*h@W!7-cXkTw-Y0LSZe3g~~!rhKm}4bwoRrlCBoMgMh6P;{pNUy;Tx106Hr|Lp zRb>Z7Cy(x#^H8Ei8Nyzx{?ws8epQ%H;dph4ZF>bL9PkNXY)_L(iLvk#;##Ak4(&5+ zOj2L1hhxF@efloE0rz04+7BES@nPqSL@OobCEnBm%21vVY%B455!?UyF1iw-e37f% zRaJt*jGc9;&f?wpfeILRSrI;)(K@Jo()x_KzE4q6TAC#W`dBSU;^P|ajAEq0-&FMr zIGsg#=2AMNVEo6kUnR}wsY)v;FDUgDx+H-;{ReQDxJSZhur zTiTKmoEgG1nWZjBgtpKfUoVE7)M9E5ywK$aj!8m1hXIO-1<@rHk^`(JDn5ZMV_9SF z4{7gN)uPd3w2t$i)5>;g?bqp_Yb$W5@K(K2KcRnyP^J6yRr)7-P^*s7Pc`g)@K2iE ztyOxpTN<=(^EK~I?ao`LXlJddfcnn&AJo&e<$5RWd+S#HQ|;$lzR^c(>tnX+UuYFu zwK#o>cE_!jzN&U^mA>vTtCwn(ZmpeHTc$fkYu%9Rrgd7k%rr|<*GIH?{jk>Vl-9%2 zPt|K6v|zs0D^n}T)cX#~8kJR|bsl{DyvmHbZx4LoCT^v)1z)E$^F$vNKj_g?hucS{KWesR#;^MR)&c%xL{{OTW(A>~+_hsAnA_#%NEjS-0U`OIl}b-)%b= zkY&ZGZCcs7>xibVdtdK!yY3r3=IiUnXiL^@)5fi<_G_=Ihd&*y-J-7>Gg>=xnw`o~az||mi|N3hC)sfIYxH&6HdWuMcS@oD;vH{A2* zeR>yt>N2=_CwQt?AG|^Q*F5j&FKaEU^>syh*1g(_!w>6OSKU*w`NSqI?$pcLEncm| zp6%MQOs#FEwrmfwPZ_7(lIeRvi}%*+U%af{V%woaI^@yjQcs@uwcvh9CB5 zzt{CW+Pllw0dbe;%Ub;#v(eJ8+XhbtBFE~>_G*7zepnx@J+Hd87jJU|?gT^)5%IZx zk5-`Xv?O-c`snlZKk0ps>l-Y6FVi2#((iHoTm8@apWXv9OrNeVx7^T0f9ms*wc1r~ z?G9BxwNbyrl6{$FU>7ZJtG3+zt^T8)r9HjMa+Rug))#1h)%8xe)3PLYxAgC#?O1N< zuUZCm(Hh~zTiSRT_t;9r=^NkGmgwJT-O-!1-uy}MVt9CV^(pO;oQ3!AVRyj*u{e^<6@ z4~wY1+J_1n`FqV~!8Co$3ZH?+_Ue5++QyYTwfBXz4YxA)ry{B?{zMb8qY|5;!59FXlMq4y0_+7Iiejw@phr$)N{jzyBly?dr$3{`9ro91v-DIg;T!Fib(S$*Eb*A_W@4VhDd|hicDx_K#2UUK zG1dh?Xg%g(R<^^w25PFt@%Tld9>YJ^M!dS$n7gFRh&XF4!jAu z_!A9FonCX%!^I5$T7##ktkfxws^H-YcQUC1@;Gs-UXh38%ww@k5r5o4q&eNC`9+?H zV=m^Y*}R#~oaqysc{$@}E6%d~s--TRzeZ%nFR!YxfSRT*DVj#J(~ z`S&f1W8?)D@t6(-ipyOMR69P%k7jXBxQ0F=prFJn;uD z6sNlce@~;rtk=x3xh6V!s>0KTus!lm&zU!M^7I^t&RbDfQiQ+Z!9uEB`Gv9w991k3 z3r+lKj&j!ukta82Vot7M=#btaU1pCRX9#AQ^4Jg(CrrTK(eR`@`A0rTvMnmGV#axV zaoUK2oOB=<(dqIOp7j}%m}T92(2iNt{^K8gWy$=s?yM(Frj10KR?p?LXsTr-gdfoELyCQ6IKnQt@HPPuPde;W9^Jq4Dt+YzUIjjjL!M4~$kQWKG(3S_ z5BiF3Y3xOnmlPHAZ>OXcier8$l}n4#%6wk0{Ha)SQ%dW*pA;ODFDP~uid!a}diQ!) zI&n|Kw;V)w#;JOgP*jy)DUQ;MGx)d{!hI<8=1?KHc$(gc1M(pQpvfjqo+{iozZ5T{ zi2CEazSF~D#;B2e&j<3&;eyQ$L*XPo%FHjt;eNAk(0P#}PV$RZD=8F>ZjLMLA1qup z;F8k(@};mS9%tlxD@xD@^CnH33NU`g^ofe_=vG5n=)kZ-zeFw+@2kX1N8l|hEAeui z!{8_evLT9bavHq8DrZ4OsjsYDDRg;67vxYSdK7dSF-&%45jRzF`pWqSdEh~)F9b?= z<^+Pd0~5Sg92vu0L0r61&Pmv!__+5Ny6`{&{4)vq2sE!B06A494_N5pUvyHHT&7Nu z=v070iMjz+NtCC-Hc9ke0B#2$+tUC?CHgi%vqZlK;ImUO@DDyYB$@=kH|!BR20%Rf zQF0dn<--uft_Ij5Q3wcKQo~tc4QGWloE6q^R#?MXVGU=6HJlaJa8_8uSz!%lg*BWN z)^Ju>!&zYsXPN44hr$mauwe)vlDJOT8LbrAFy!Tj%PjaiT!il+sLDKo4@9(2Cp;~q z3BEL<318*jvoeoBoFzkx6S5FQN9yym$hE;rXy{NGnQrKy6TXe0Dsu@89qfc($Y=sX z2RmVg&|xmY7=h*yh`oMgF2PzEOK?P>a|sN6?S!AoXafGVBDf=g*!5TD637aLoU|(# zc|HZ+JR4wzM43l2&NOT0KvW+Dwge$hoUn@!t`Ivx;VwenYY-rm;1mKHY9Zli?92c! zB^-hML&g(smUt;4PhT*e@Jl0}u#+riAz>ehml7JqFN{=G7N1M-xh#G@p;3HgMDg<@ zim!|)ettypl`P&UX8y&+%wjPs5#T8VK3U0P!UhD`;WGf9O$5rau?5U378CNg1)?L= zC^prAJZkZw!A&jt$%+>fjzB=pSpah-N?_<&Z0h+oG-?t>&r5}XVF-|G7H1Se(Lm#n zpC$!rW`7;o4YRqK-)Jc}6*F4F9Z{^?%vTLDYZ2%$gno(Zg!On9h3bdKRPx@9fXWaY z5a_%^09|qZ2g+msvV3acd^|Ih8XOPk3ax=Bfz~9eFfk63Md&jO5D5$?F5yD$$1kUYF=w0DMUW z3~ZQGiSmK$0*SJX@+HcLySy(2FTqfWW&qqE(Zv7-60HMxMxxIFd@RvZ0G~^=D;{2D zAwbx8fC`Cv0e&OVZ2+H2lprY4&hU|R;U~Ex07go*5TIV78v!;;v4lAw(h}wX_ZcWH% z%$x@Z4+%Wnt;xF;0o|IQQJ|rzhpCT!Ay~wN02MfTmotm(aZVTmWn{72{no9gnogCl_u|W1SmbzNCs+_ z9!|{-r{TvkRpR2B3%^dwGs}MxK5aGRcl4a>qdYg1WdLnzUQ{BG0huh$c%( z+sK0(DLKLyju&kH)h}n7z3i*i5>tm)7 z+axKZ5j)-2O#2$xFOovq$bQ&aLx4T z=t)-tj1=h1Jb*b8T>}tdl;29Dd=BvN6+(w&06$3dN(VZgFi{>o@nwn9)ry3*^6CNT zbx?ge9EolPlzwyYN`Xe!v02n{u7-B%EZS;rS13DNG|=2d00k0dvu%?on@wssml{f4 z=2Dkq=m&6zur70{%OIi4+!6q()?Cxu!ArGX5o*mf)%pqK6w$8pDgfy0SW23y5e;)` zSE51KJyBBvd80x?L#_P}{kbrNs{*0Hv89 z7p*^w2CYIstOKQHBLFq4;((VYB5)of94Neg7Qt0UG+~Owbwa*e8aek<#5|FHvw#l) zM?(@kXG9YYMm9tftP>J$7I3SKCXj+}HdRw11Y23aD#4mZU`VhMG8>F%W^;nmgMgmB z4B$SAQiHC7G1T8p1))?bQlx$}O+^rEN|exi2c2gh^NLRA<^j{m$K49^;w^D00^c`Vj$mFHC@Cin&tkAxeHfvCTinke@b=_;J6X)KC5q2UBfli#Ye}aA*U=aG)p^p=F zV!f_In1OHtI*kTA40sgb354AUTM)J*R3ofMC`PD6n29hSAp?Oc6!T*Jx`0kV;5x>< zt~TlyU2ik}*C=}%0&PoMn`0<#OIw?RE^SL&n?o}PBiedD@^Z-f1K?f+^EwRtD8m0# zZW6{JwqYN@eh4hb256Qu0>c)|83H&Afe&LH2;X3eJBPrj?r#XUBCJN>3|N9N3xP8t zC&z0Lh9hvYZiNgY@w`_eMQ-e&$<*kTI;?fxBtdHuWiSfk!%` z_+r({a%7ee4^c!4zJn${VH8O?k%o8u$uE&gJm*Q}c|3j^3y%@;IjHgyBvlmVd-Ii4 zSFzL0505CR1>Oqzc`N~LDu5se$uGmnzSN=$WW-OZkS233!H1Ai`S=7M1p_O;SK!1q zOv;P!WXvEdeM|U=F+`V?yDQAJ{3T1OT+2*KJb^WG8Tv?xe9_N{$HOQSHHt9}|383e ze$02AmNAy#+b4Xp7x%@Xi)p+tG$?Hl$d?ShWF$C%o0ru3E-Omq!}_}K?4Xr?3gIy5i|ty@tZBf zAYcv|jLSr?1I_QPkdNP5xf2Cu0XNHKJi~khexHRnztM6S4B5aV%LSP$~FI z$zWXMVK{_f$~ytR6X4rn@DMl*{O^D)pZaabTN&%e;Rv^pM&K~;V}O)rUgSGs5`bpf z`w=*k=Z{Cdi5M5l;`IfBnTK=`eAPsZ%S`(bw23pRc!Hw*K4Rc7)A-lyO`Lok(Xram z5XNPuaojO+CM7I{- z<+v(oX-M;1RhpO?p(zoILqTJK6me+^XW{S_K2<2=H1RS+WO~G64bhr{ zg3yQ;zODSms(jrd6gRj?M|5TQ;@2%Kk>fL2RD9iR5TI#K6<+}v1=_Ty ziWS5p&?k)cvncJAMW7GDKJ-^r=^@6(!=UMDq;CPt#`#MC^o#bb)*vkZcEndll+XFa zY;P6q{Q&65@*f9%)bJO|i>}`Rq?;GzbG$Xrf0CbbfqABr^e3RJp)cjA__EvgfaaM_ zre6TfuN;{5v9qGanNFrBfHu!?lI{^U;`Vr8kzpIum%AY`+{_H^g#An^10x$NKSCDRAq(6(I ze~6;nV~AM{`*Y;z1pRt}Hv2Q_L^%Wrkq-P0jiM)kX8)#rI--A1k4R_vi$R;?K_{hy z;*LsR8Aab2Mc)saFGMoBBmD27sPx7t`c2UM^p>g5CsFC&foA`g={=NK45_9)?XV}0 zcJP%LEiFCOAt9SCAU6h}%AAp|7lL zrCAOS*0Gq0xnrm0h*QF(Sd5txE=AnFic-SoR71x<3nC8*i*K5?I-e@f3gQ-de8d6a z)L|orUES(@VE7ba#7X6-ld~6}J-q1Lr=g$XoHTXDxUo~6GbT>V%bD%O3CO8AtRGE} zJL#(YmGXFXWQ2G`7;o&AJ9#{l95_E4nTKDEE-#FXaXKR`8~QGz(psX@7 zzgrx#ZWVKJLpz<=xruO^h?)p3Tia814Sw3jtUV7OFLzZ%+d%lLJb)jm0MEkWaC56d z`{woWd-eO<*($pm@+|j+=C)X_|)fF%8RzP=-)$6|)f@g@ zk~1fq^IRUv`5%?^i^Az!RQd)d6V87i zk{^uZj}PaU>wNUj>{%HV$2wMzi?3c|R|mYoamOD7mr-%XT;8R6=JBfio~l@Md2mg9 zFkn}_+Hvl6ne#*JKK4h&8JEAAB<_LTf~ynagD3ZnO|U(X0d&(_(2tn_)sLR-v1w_6 zVWAKb@@mpDclJZ1#@{+^gy*IAY68v5Z!itNZ|4Z4LYO<)Mtr5#^f#^8V|un*m9>F= ztcSI@z!p_YF-TQQ^|<3zwSHfH&W2}tAkFZ+RQo(N3I1G{{~J6{NqZgAVj=BoM_Lnb zL`f?JDUPaIy(h1RDxozAPEP0ujVsF74U31JrvBay*P*H_&Cn>CO*#067kh%+p#6jI zvIo-gDuy$~2#)(KIP-v~>Ke4ov;ES_PyIb~lf1BRy;m2n*b9NoYwFp)=hWEIrY~?z z1en1!bvJfbeJF~#eH068=|s1-s45@)!c)1D6}_}4IPM^L*t&ACt17E%JypG7w(?)P z=ItH#4cIC#0dw`_1JyG>t6o!A5i)}_j|C?m_f%G(O!a(~xW}xY5Io^|>6P=v1u~V~ z;P;;G?^heA#!iFYlY+l)Yz0kBW?0t)6+1@(UW2 zoPi+{>4WOYpKTa#uD|H@QKkW5N>pA=`C8NPRB_S>^}<(;>hC6LMX;3r2DEc+yRtoI}$*T#ysK;|!smz~OrujKOJyj2Do;aNzx=ZuvhD}m~$PMkzZ&;`t@C zn}-&#j2=gzn^JCQl9sdMZj^;SAx=U-r~QHJHq18BwBXD-&-UeJ@MHRqX#~+d$1CAg z&qH`E{zkv?-$yFCpDy24b08Du`VYXElVyjy{OV{tgeubm#9~+JW=gFtj6hpgM4-dj1d9D0vKhTXD|2 zy#8FmF29N9qWz%Ny0!cxZC7ONKohzbw>AxcV)LxhLOONU`$IFlY2CuN=pgO$+ z`J5r20CK?U!9MOdSvZA6v7}(|(Qy?^`Md7WO!x+5`+H!b{$HfRpiL_rZN?kIPf#2J@*sZqR6=erPSt^$p1q^*D4ej_rs1sOEz2fy$ z{ekknHfvy{ng7v9PBG|F@s^juFJwx`gF>~~9AMW_xf081+&@n38Hw@asr(aCD^zcp zq0NZHQuL%y54do|9_2@W36)FvI_!qx{t;SA=E=vkb6lYE&uQs!u z&M4!yBkaMUw&V_=Rmx;+)lG+fgAYa(_=*J_Hwhj71qIfifXfko)1hA)7C6EJ&NvP| z%>rx|P~r0&QYRntRQ(KZmw`#YkE(1s^>SKK zG47zr(4f9gem-}u{x%uk%9%Ky!fs#ipLaB9Vu0N69_^p)l=w#eS;7Kg2O2Bl z^$OES^*=O_eGynyx7~|Dz&Swe7b+Cx9u zp!JWQQBy-zcW2yjs#HGW7as|&0}BNn+RgbK0=uHsKxY8&qpyU`IfLARDDISo+;@>X z+^apb?DC^$DY#Wb*5>S3M=)kBPvvP0Y;nX!3$d?(6TAz)@^?*?39ng=%yp7ha7L3@ zw2??|6C(Y%npNv%t4%{SzaU?@MKi#sHvobEZ3E!&tEo%PEsciDbI}Th&YptQJ+`On zUesMZ4wH;gS-XB5CYi&?Id2x}gu>FOM!kPE?c})01!s{vA+Y|58a0N(&VU71FKGc* zhmC_c2_C+5`h2Ey@^fJ`SveI{@FV5F^=OYX%O6 zE@3jJ!&%ThJRNfIU3fYi6Kx+hBy^0kj~*LnWVDA~O$UUwP6e?t5YdT`xq zC*e_@tLLAo1_$>4!BgSq^_O{~^$#3pZS@5fSGQ&NZ5VAYFyfAEtXEsn z7R=kL^0cy^$_!-J-~J#nl#?F=qB|O%C18M}+w?wED;TyHp1(R&{M^((b6K~FpX2=_ zDt>MbJp;bHy~e!K*GIaHH)xMNvffnu9H+*ye*~stZsFYXI3VP4`Hej+m8VL{^ET)r zEkzxxIC9A6*L;ojnLR7`5zZuW=B1`Jf5wJ2hwFPw{b^nOlhWqp)%dUUyky}J0-o)5 zYF9^3{)Dtk*M5SdDrTOk>qy&?CoMsZJ$*d&nR6mm!#o&go@1Q)tx{3MK4E?OYJJM6 z&(N?wp2`{&PMfEjfqgWoe*RgQ&Z3obj>h~0q2C*gtM$CpI(P;wbp@DA&e!+tidXyU zGYsTi=v<9cnrdJDJ>q}DcY#Sm&p`z+4E^!K@;Jyf-&pd&0ix}ZanrGa{^<3p7vF`p zn|9!PZ&fY6(R5>P)vMvyKE!-T%d4qYyc;$h#MDQxF)(a!bVx^4_249{@(cz=g(_`s zsB#$9=0n_zOpjyyZ@B;9cjwOSq>R@=Z6I&(K;5)s*u2yRtG1z5|835(MId4KLb&Mj zoHv4BoO~=WR_n^~5XwdCls`WR%BX&pst4yKa1ZQW0FKB&f}I>ctA8@DW_NzHO#fBY z&$9hhr#zLdAQE0yaV9x%EzU}Nd#Vhil;7a$t@dwKC(y&?H&}-5C;tqMp-+*F{-{>g ztgfQv>XI=hMhqKNiJ`xNF|VfL3^KueYPH>N>av}1R_fy18 zXh_Pb`qnkrpH;hmM5_!YUyo#rU5Lc2AD(ZkY6Ay?pG4R9_c}EKAvGRS%XhKF>Oe;M zuCEX=0uvq2@>D$oi4Du%p~`wH_rvKMwqiwC>UM4t)H>3z?5r@yUEt95_6>aM)Vsf- zyhP3Y3RYHdd$ucE4UO52P75UIGLr(`%XfXPlc93Ow^^eg4%;EsLyTW`h7E@S@=PMZ~;o z; z8m7}R`YX=5!}Ms*25O*aJ*%s@PVoVfllvrg$?62#X{R1^ObP4j9zY&>y@kO5eK5VK z#SQ{SG82t*P8nI0g0Eq^oIHlPFSy6YilUd;gWTgs&-<5i^Q~)Y^z?nxt6X^1RzQz~ z>RntZurbBlYE*AfO@w(Lg^SC2!RK{3k9Qhh0{4lmY_hn9E`lf4gyq3WqU6nt$QwXy zom#n7jntYP;fe>B>elK_TvKV8j##ZwYt%~|^o3*p=nZPhsnDYsKjBKa1&CDgCWekQ z?eWu5T-+H)xE_gc-2^Tf)t;(H)V!odwx{YI5Rp+j=)5WE+#$!^3&9ymg&@@?wx&|I zrr|a_#5p0%^2!Cxd=f0@5}qB4%nemvV}Qu8iykE5w@>$T>~O*P1PUl`!B|HU-j=k- zi^Xd9y7d_Kc-43j*05utr@^(M>Ij5}y;zSrC>+@VhlN)DS3<8-LOGP#?jP8wsQuV& za6CO(G50KUWq5Pp7{T3|ng*B~8#SPq`x{2Po^Y7kp1BdpRiDF9dgvloHG^E2M#%{6 zA&XiMFy}+T{+_B^kc8d_VR$Nk4kgZoumaH6*L`W&_hg$L}FRrQzWcPqUm<>P{aH7yjS}JX4;* z%bK?k(Nh*%9}hOF1E=GwsHbTJ=Zv8Ge(nZf0JwZwV9bX5ze1#bn6`_&zxTINukYpU zeGm2azIvCMEwBl9j&1Z?cjq1ctC8wC0;8(0jjo=H5-O~$_4n4A)Q7JD_&exn&3UmFiwH z-J-k8cC4Xn%l8M$wtUpX(j8tmQxzStZzAZ(LdFR{s^Ui}+F8hO6+n%jy1mEIEd5|j z&(T^r>NH*pdE$>o%3AmV$A{iTe}$sqj#9S*)T+~XP@#+W;%q5;P(fp(?xC+5_tj+> zQWz!}EZAx9rQ4`20qw~{o~UO1q%9`)beyy?S2KE;WA)I*)I2P(c|(C4&lf1Rx{pp4 zu7Rs~lpb4HEL_9$d_+`xE~?Dk6j?3u$Sx)HHyrPs&!Q$Vhvjyj0BQ?|P+Qo-%alPH z3;swFt&OVJyE-yte$NWF!bv_ z#e-|KC!z|YZadc%^}z1T%i}QxiQK=zS;Jnw9_**pgEOy5`cwbo!Nr0SG#ZIN;L4tCtp z)=*k*{Vc5If3o7HM&-D_s4GD^=h#D^HJQ+|{Fem37v~r2JLuz!&@qfz=S)Pkz_Y#c z-m16JT@Zq+XbJuydN8WY>Qr8UbC0(Jm*A{vB=51oLE)S`(QL(sdw{*v>!8l{A2@P% z@fZc?SCqC$3#U)lKlUFju_wIYhdQsv;vkJ8s&`Q@JuPEuu`#QJk1y7DuK2eZR7!?A za312(Pl7bE2@=$?C*F-$96o+->92S*F)L#_Z(?5Ku1?`7ONK_(R%FZiFx&5`Oo675 zq9~5rVO%EWplya67`?2%8ZeM))(rc7&G@-avR4;cJ9?gfj^I zoC7vdU7+c?^KV$wci3vfY-x6H(Yl${;*u6E%~qxtPe!hGhSg$dvti99;8u#2U^Hts z0{Mo4w@)gHC-fK{HH=sf(jb{YcDuD{wP@CirA?4=&9$hQ39VDHBWvnNHjHMHgHp_i zH_ZvHS)zFtV?yg>h-}dV5xBM6jEM6lLR?48H7(r@s%a%mF_h4{wJxEEHc4QFHZeWp zC$#n{o!Z72mdzxJZ#OWCXpbDl%$yEVvRS0$MN(3=^x`D*iulH|FNsvAE9(gPVUeA9 zr>Ap_kpl6TMmQ(5rsYS*Qh8rQITyO3OGG1*U8C!a6zbN=Oldtcc22WvRGSl;nKQxM zeIP1gsUFNGHyI40XLQ3NLJ}j5W1(JR7_^mSZ)t~+eImJr(KlQ@x~-q&z`87#L|xdh zF0$umFZDQcg2sAcoBqVe>1eh{zl%-6Yl-6%lkrd>WRx(a{NP z+ZaheQ?H0;g0T-z0-QrJ%*Z@`LS1k-^eT0)Z!*VytCYUxyw&iM4 zgLWfv4=FSDMpCYr{-E6MnEWC?+&qSliI&}@Cxp1>p$>Oy7DTuT!He@(B{XIYO1QeA zH{7@J&U}o!Nvykx`yo|T>^KN;odkPK$}>o@zXJ1JG5!2Vjw?Yztk=92;Ob_?RU<97 zt;uVIu5RwQi@_P&PDnfMGpG>TUdZ^kH_6;VNN-#Z)DU}-kZs~-Qu4(@c8D7Z^eFdSj65@)}5Udxs*$Hd@A!Fh`YB{xe82ymKJQ^ge;O%X=H*7T1}KU&ycyq~YC+ zFVlM+;x6w~h+E#hh`YT$s2t;c4Dnd+VWcb(Lf&Ak2b9q+ve z7H{tDhwm2NREYO@w}Z#)4WevI?=OhAGO&7GXO4%C-WS1PcppX7^q#~w?0|2}%cBan zcM9r=@xFkRSnoi@n|NOZyX~EV?>O&G_-<;nw#`Db7%Xv*qkgkUT-}KK9~3Z)g>)Nj zW|6+ZrCdX8BHET2<|-F^t8H<>&p5Xh?ecRBbG7Rs2uJt*5#Md5Lm6|al>7obELjp& zvP6|^&mu^tyBHk|Sit;NRd4)+G8dsth?9eHvAGqhxH_3i6$@*u(f$)?;p%8o8RL>U z_%=JcOk*Ol+GZPOCl@C`tz{=wSI57?kmjW>a%k7O7BS_E9;3~BRQNVii(5(gyxnSU z&~3k@7s{AdL;eetzsxWvMzv*Pl>A9bey7gwqjcxj_{F|}MgB<%6}kb&SxQ0c)~WhB zs;VkgRh>ExW>aoaqqF0`BXR5o+ET}B#i$T>KN`f(MA*%THeaLc$YsE%dgmIY7iY#U zWRv{UjCVDcGbQ9UAApe75d1sfmlULm*16fSuOY2VYv^j$x!Fa%ppLIJH;**!J^`T{ z9f=?FNB2u8-?^HN<}NhBht%%(AjTseY%%_b=z2sSLok1GpJ$_<$H8TuQV!sQN-H3) z8}M2jCMCkfexxr z4;FF7FegAtb-gQw?YI-PZig#|?fxrh3~m;@^c~jFT-)kBNI!{v(Pzkil{Kig$19Ea zHbcvdSGJkYJI|W^Y$#>>`cMJ@J*W6)A&;Bj(yT zk4k+9M=}SwOdkYy$4%*VD7syQ4^+aR3=1Eqgn#S^-$&uYqJ`Hr6yAouYI6MOwNNH+uT0lMnOjd*-WYPXgM+tJ-0jd^IyQJ9GCHcEnWGA{Q^PV>v32|t zRmzKb2w-#)4_AxnWR$v`t1r%HFBw7KxdXq?U5uu1Hrl90o>pn2NiXO)jh%I;Qd+BY zmx{OZ7nZy zB?p_Y{26_vls$?q4*-y4;`*U6t8$$vj8|9#2t)R}(VDU}<#PN|3Soq8N!{4{YF zp=^uG5xwMQn8ExURyvKOwwPW%(^f(|KU0%5E%%w4$Mur&nUX(v7uY-gkqthrD;)f8 zIOVLQe1{ZiVXTY2pe+=u*F$t&yi({AH+$g@muWs8kA+F~$wuXry2g!)zpb*pPM1DZ zjyiZG3Uw}^q`_B5q6--f&()n$IZuOQIg=YLUW3<#i*@R}5rR73g0D`g_w&0kGlUGe z7+>adW`7K%j(xDtLGjlxktOCA8RmBS)#XS@RI`mD=YSkKo`rVM;jN7aiidtm(>*U_ zW-qwgPRXQ6n2S?^G_}5d z&>e--)bgsL#<0}(hA|dlZJ6hy2#<;y!)76W8Ny$|lk5<^m4|=I?(2sGkTm7wpR#g1 zIPL)VTL@pWghQl7N;Kde&Kbw%sQfG)l2X0^nT1H_{fKnlhpz*n<3{87R>4tCB(G-WQnzD3D|eXM3FDC#w64I=K12X?O=6x6Y&)^^{7 z*x&IiG3Y^^v}J8KjwrS7`oz2&Ih}id{uzz&t1lzF7T(WsQn#R zBKgDKt6n*(oyGz1%JMlHoXg4mu4@vx8#(nrZt{GPY94S!oH`*DDTCZ2^QGeH#zlB5oBF8v z5ZKfdno!HyIE})E=0QL%0+e*3sZUeDZY2OLSC|ij)m)?IKwls1g!&rB%dpQS2qV9x z`>(zhd~WP4Mn1<`U^O==^Fj8)mf%L_-AMx5(6yXQUIbwbeGVRIp8O8qF;+Pe20V{1 zv#D&2Aix;)9c0IB&j&T$%~wws&5SX;24F5Vw<1YcjBl~qaT(9CkoilC=J@8hgTdw} zB_-qkoZ@UFIZ#%boL`h(5Xi~ZL_z+-UeZ=~8)d_o;wLWIE z{jF8J*^09#TDRQb>S|i2SKI6Ux@L)0l4mvZTgz+pPBl?aw;2P4#)wTWQmsuk>Kj2Di zTVV~IXwBYy+TQfOJ=dCQ`>X-3MDw_H$q6gt#KR*~S6DfA%}J|`tEXw*;YOCdsDJ+% zBZiE!p0*BK`&XZ^{$-r7ZZ&Pc^_yYmJvn@sebm*hwKZeiwNA8b9TJ9He_Ok59q0 z>#ZAI-OalfQPePN3E~w4U$CArcUr-#Y0Cb=I3V`iJL2+3x1>VU1aEv<#DrUk$L#*W*t)?R0AG40KEtK`MQj|{MGT5Tsi zG1?#NF14eUI29`rKK(>EK;f z+~GH@Rer0*&IhbzX;#xTYuQc|pE%lDl@{1-#rrqd-@aj8@3$`9S$SZxRdV=&Nmkwo z4vy>7uCdzgv|9OZbtOW#Hr9`;UH#3SuD%z82w*tu`_l+J{}ES03s?URr(IWh;Jua? zjz4LiHE3U%^+(&@X??tW9U^)8_Ob^54Zp+Ht=-15R3whFm%U*9dHFuOzx9%tXT5S` z9&j5FEkwdm`%Wv{-sVbZZFRBd*iYJB57--BT`#hqu)8Ciw4bt{`~;DK_7r=$Yi=9+ znWIChtUh_xEv9|=4*M3@$ctRP+gNd%t>t+q?Vs%t*0ZZ!eN4NxeU0_BZMVX5?n-R$ z>e0s9y4=;nboFgx)xwGIZQ^Iz<13M7-|?}v&^}?c$7r@X^Q)sD)5G&?4qJO&`_L8Z zK-Ge(1yuy<4gLqt@uu5l-Fu^b7;l5#HSK*B)-$mz{?5$ve0!t)pk^(D z8>%Gh)f??RSGShd_a@7ox{=kk8#>AAvKh9#7JhrHx!L+vN&Y^@o@kFywLfJqdl8Wb z9K!Azp{z^iSc^^stiLZq>6ha6v6q*vTV^%2YdEhAcXe%@4A-_cEQ7eDdG^OQ+b`M+ ztc&bcZ(8$DJY>)Q;X5n-#2w&YcaQy?6}PXV%9?H`SshPUtJb-Ow{gW|ZR=6sA7=De z#ILNv5`5|sV4R>CDde&rVB4DV`m9bu#;lN@1mFB|I1D-IOp_$V;fm%TWvG%MSmTbhIo ziAu`xDW>toeqZ-8e=$T1^)2XL))NdYoSs{lm0y&TTN+Mn+RbP5^BF$*;5TK{5Jn?R zKp0~rO_yPLR z6z12w#KkLp$Qh?{QjB?trAv)@^Ne}@j0Foo6)ZJ+_Czyt3riMfmF1V|CZl0l1&BJS zzS81?+~Hjp78m5uC{8k>1^EtdatTZ_qN$N4*fh;aX_{7+U7DL)giIt#9MNT2rTJM4 z3vvtc%ls?|n$g@Mf9c8*X^>k;Z4@GxS*WaVgsuQNsv`D~WFV=52v)}u`KxlVQ_*!K zm*r;r2SBdsG|HFAyzc!kD>jmQ_vzC+8PKmEfE~9ut0<=+Hxs)actWn~QdqX6#7M%1 zD9N8|B;^z!0P}(QKp)JSRYpsLA;*u9WAw{R8)3|xq$G}8Q34(Eix&B?Wy%T^_BAC6U) zOD}{AH|+*$N>*X+P|(bofvuMl7cQMKR_o&Ag-OVuA0>^305qJw=g4Skgt?R>(YK<~ z47ezIKpEVZuLo4qH1uIX?g*o4xTy3*v?n=E74Dn}cOrbxzp@wlO_&O@R^kYNt`(Np zz3lwl?834fqg2^{Ojc1(zpuC?w+K!0C3Y|C1w)UW0qaf~XTX3(x&26vo;r1sv9K79 zpH-x?XHGVX0)-26OG#zSNXPEB6dgrs+Nc><86{c%#U!TB95ohmLRL<3i9f$smCcx% zKEo(0E=9Gam;=a_KF27{T@=9d<;z`BQkq*|BbAXsB-~A zf7Cw>Ve$Xxw*5CcluMoE&?6ORCjAi-5&Ge=@C@)igdKPu`wQrs5I)1%{9h4@5l=;6 zUOVv2MOqIm8y_G%j1WK=kHE_*b$HMw-*rGfmB%0~!0AOQLNx;OE(Tu-5uc6mnbR7-b9MeuSMkAjm=B&qA{i(hv_J{|ba&xdamPRjkS*42tg_wl0@-Th-$}p#8E-y>$HPq)Y z!IqR$RO~A(F3t5RS!KTBBA{*<51JUknLt?KkP?&9+ z#C4*34iqf*6%-dOO7i(el`ZjQ`IhIe$|_~LFSiKeeo<~yvKOxOEez!4(M(vV&=w}D zwWfOxist2)micvKhx)p9FY6k%OJp5MD+?^-GxZ2xT6S?^Vb%!6gQZi=wN0I=Ri;X3 z`i6N`T??~ve5x3BH>zH)tLQwvxzRjRiup>UB;aR97iRf=Wmv=V^YU|ZR8(qj%n zxa=*~c(OS8e96`v{_Esld5bmWW_Lx5lh0RIm!qa|euew0n<3B9jW3?MIrWd#y5Y@` z{vc8jRW>XW>Fc7>M^oc5kvjSIC&rP9_BPJvf%Y-TaCDj=ZBCSGd7AYG%8!jVjX1Y? zCCurtj;V~Pa8rMNz=ER}zq$#{B*fJZ4`^$b5x|TS`CzI5|1?4u70u`dAg5{Y$SM5k zgqUfhGk2nnP6FiUXdYm-j@}5kOGobp{6$Bf1-z%D9|Df+=#Kz(AZ?^KM~yyJYkGG8 ze~5wFh6B_+2_t5h62K;Z`w*fGS1b=)TM1$lJGke9!2cNrTMeuTJb%qH;G z5?P7$I+^eC?4)hM z$QuLj<{5w$I?6JdahlUIP90qk*b_wF0pJiJuE4Yr-4o=!0s%q^hY^rHk64dmOvDR_ zgK^}{bmAr*FCgxgbmG4xo!ClOGmpq$`cn>3s-G9Fs;)kra8y@6hbYyTL{&d0s``?s z>gPmNU&898nmOlJGo96}M1ZFd0=kili9Gd(9lik^)lt@sJDXI0F_AC8!4aj#Vn+?g zqZXeFH?`mmKb9m8MnK8wfLS_95Iq+=dVUCvLaOT7Nf5vbNRaDPCsj~1qH!oslOpOA ze;38YY2XInHxl_kk33<8k-mIhChrg?%+?E@v3)0y!Njl2S z_%%ApKFZQjzHa081HuTG=_ohrb9Iz^_iP>I_Wd~><&OJH9pwi8sE%?EKLP>5xTP=F zQSRh_ucO@9AJI`losM$LpQ8LEoxAxVI?4_H1|8*of0K@K`%h;=6@<%mln(}(I?CsT z+jW%itd7#@;+3bR)9L!?=or8(9i{(Wr=#?}5z7D4>3@D5T?yEtqi+Mg)6pLQ?UlEr z&jT#hQTpn79d*3zS@@8Qv2W1jdI(L6&fTT_Z`Kkhp>8`Fvz%OR0XHIWSQGiykLv)D zx0<4dHF-B9U|17sRW!WxF!xcFlup>Aq7CYKK_yM!1)yltm>#XgACbiILfo#hrx6+} z!9D5w2vnH(p^n=`UXqGdn7nleP?*pK*{F0XAX7(|0G8`$1>jB{-2!+@M_&LO)lo-R z3jIFr}jv0dL%d9 z$>qJRjR>kYfp_Y-P2_#9=z7Te00M*)eo@hka{zKiDNn{nRBk%qR~4N_ATtI_q)fQG zxy$dOD#Z2z*iFZ6BJX}hD?;A>2vCIZXBEwO3P8>%MaVc%<)#z1spu>MnW0FeOjr>< zPNb*`{chrAI&KqrZzft1^5!8x5dyQ_M&QLQYaR1O7}BE{c0?GM+7(YvD7J0OTE<3d z>b)&%8Eb)CAUe;7*kny1Zzf_{VQLj(tHTsy-(Xv>%Q5EZtSFRYY<3qXkFmQng*?XU zyE=K_Bler7kT;|o9-t5)6BJ{2B{-bFN9-|8A@2xc$HNq3r@A|wzanP$aHNb!EImvy zR+;E<{tsezYYH;oN9?mO^)+Ju4pU2eq3sA-vvr8w7N*+whIJ8i-U!69!xUq;BVcz< z_)9p0F#|n`41#njv~W6=efDL0GGx%y#>FbS9(LZ2fYf;~@?8i~p12matweyQ^nvmE zAt3qztnqJz==VF-xUqHV7sAexA#^g}>&0U%dL{|@+vj>baSW(Z(#)awSFE<-@= zA2C-oCBw<3@-HAD_f0T;t{A5s2AtN>vjE+sX|vF>yLIab53A@j!mm1&&>I(6Fp@3@ z3{lZ(8GxBOx)u;+l>4+%jshOR2^e(Xf!I$v+S7-Dr%aSVPkcj1>1vCVwK6sU=yfPI z1&&0wLX>{S#6>0Ak{&$<^!^Il-;&PN7-#!!&%f&>oSYF z?8i8OJ4AGuMP2$TU1sG2v|6(qZwD{cdQ+)2%TenWkP}tE&MpSf*|C*$a-%xt!mdPv zaCoB4tcNB*lud7^BxUeIlolH9?SG<7b5&+q2S8UHjjr;1J4IQ9hKcGv?bEZmp=PQ5 zENbtdYM(`5v!GL?b>X(Nb?a4^Os~ShkF6{|{WsaFLhKiq6E8H!D_{tK@bUUB8$OzPO(gImLXtdF9Y18 zqtu|SVhoRWM?ol+gdDBkG)EDnIuhw>E=6$9$loWF;Dw7nlb4iv6O?aMjZ$PyRY#Lo zs*_2h5((2vix(B)4AZz9#Ms=0fko;f70*b^lt7;4Y0+*)^Na0qK0lZkuL#b$LMt%O z(FGJs<9wb-FrR!p0&zZk&MrXkBk;#o&WG;d;Iza!sTSjg)0Fd}yhLmh{(*^}@+yE_zqsg?Ab1hD2;Pd-;xUBl5x8I; zL;VKuO&}N7yAbY07ztgtEXN|?XS~K2(1{EBBM93N20$ln1%82k7O)Qbc%e@w+QfEU zjW8AAAaoiA+y{IQ;V%d~5bi~I0HGXVJ;Gvy5`<|8a}ZJyxb1O1Y+oDD9TB)Waz2+! z`x>{~$^RYd-hx2e($>zzOxx1d&P-0*($>y=&l!%kei>ys5B>@G0)q3|hxmI4|E=8a znB3ThU4Y#XSdRzj)H4_ZhxH5q4&)$0@FASQx_KIb>*s3-Hz2G*;If*JFdc!*ELYqs z5C$P|1?Ga>4R{9lGs52yzCm~s;cbL%2s;qABK!&AHUuv1TTeA=1n8+IQ_Ky$H1X4+zfZKc&Y?yPf`V_?g}t!AVaOJ|{mfP*7lG zmMz9BX}o+gGAB&UEGW)ilIeG@c=GBd-gg;giwX-e^|XuE-TZL?c~K@4cVrCx;>vkH z&79?>c!j3&0!3x{i;D1SkUt5|%qz%RR2DUVJMXeHre%(sGBz_~+?W|gW?@$8l3d)H zKw`#>QR#RGf2C2DwJetjxhqte z^l?{?OP9_FHzI6=8KXvvU{o#f=mO=4y%bxZJjxJE?_v$7Y{!0K%yd{4gwb}GOft1=~B zJDoOfW)bB?I!<|CX4wFxcevLz?}QB86)P<;cu@o1tb9EWFFCV~hPQrbTy5L1k$4*=%1W}bb0gc4%*>LkoD^^X257iU!$1v#jLcco1il1d6i#hJLG? zso(0BDW#=5IKI&WHTDfPQ>c-gytue9H@PT((PDpbL2+_U?!x@6qJAYy79|%3{C@pa zyzu&d4X>8>!{wOl#ko1^KDz20_6x4P`28z0bM)0CHI3j}4Jut!npL9i(x^)~c)MQa z&q7l;MJX;`r%_TG49iU1nF-qsUUlV!NorhV72s~0G8?Y&sHq`bOuKLy=RmQ9zEWtY zaZPv8zD1vc-P7k#yQ~7-19AoNA!oAVfTU8|9~Ks56)k}qtBFxn zt~*WJH>?(oqjtAh{^ER04;kYpPXdgYI^{}34Y39@a`+B{!I8m%J|QDef}4=wEiBCU zbGptmv^CT`Jiw3}87L4a&CD(?2ox3>Ik{zOcHm5_20OGKJW$UvDs7UH87K;r<$I$I|p9+fpPx?~=&I5-u- zucGrx0t-2rK@X*t)}=J7Xc3dNY7HsWY$VavxVnfda=0Lxgu&SlP78niuRqud;Nb~- zSt&6R82wCwCm!{|_P~gfIN|t>*yF|HmoJF3yc@wrz;;>D7LcEj{jdkpQT6SUIJO}T z$FU-}T-t~XL{u61e7cX|g_1=$oRB@xtOgu}qLZW<}yltSJ zIJ16Qgx6idLvZrwL(%O`MFsR9)=RNYdutJQ${=dYSZo+RM&#qizZS?>UA+HA zItMgmIsCq^p9TE@)a3oUR?v61r*t z{Qqb~e_peaksJ8|x(M)}buqJF$0=6pzd8qw_<(U&x$*^kbL<$Hnl z0T&>!J;{yo2REYmmkgW_%cnP@dGX8nFh2)0k4kx0kM_%Nl)tnQ&1-GWhvnBcqWO>X zIUnZpuLU_D(swnY?`uSFYeYMb^7yr8_~|4&`bk*bsBQ2trMH#XvW|&*3Qih0c;Mv? zwvv$zXVl|(qer*%x2fkngvc|Xp&z-TH_bfZZSZ)Nr?%m0+o_(qUl~P&Q^+wDO4Xc zK!mzo%>L#`c42~tYvHHIxF<@)#KirQ%cs{`(hG#rOwT(?<%uh1Od zq>l=HOlU3yl*fyu%x@1Q-BDDX^8Jo9@*kD_CnbNo|GaGHH~bBJ^yb`NvL}&%eLI z{67i(w9xy7{#0nIx#o`tl0QZ0p+YYddWp~*guYwo144f#w8^_?sJ|(Y^7!{ns5k#Q z3H@@er1Ou5kPZs{XVNJ5jL;toeNbrpC0Ld31yXKrp)V6UUFf+&uM@gj=&eHkRpk&`b}a_yx1nf{+|*P4dW1y z^Tc<=zWAFJ*pjloiQM1zL;H!4ulBnbZ}Hd*lg<^a5c~rX`FnvZ|2App`<>7~2;Clg zXXbYVGQX0TWEg)W_QpF<=3`zvLIhtNw!qZ;5+d|YASPlD4y4{gNQ3V%=^j|e@IH>^ zlZi+lFPJH~T<~_m#|3u_ek?c|3pC5m5^REZD`qnOjEP_>kbiM(DQVQ#3=gQ}zm5p{ zHleo*cEkgnD+TMf;LSkJyJv_f=f=Y(+tU$9Izi|@q*3n>NgpTa(}li9=w(8$B@Mg& znTUQ0F&*~%QS#3c6R{5Ay%X!34`lulBJ8_@i2O>)uOY%O+>pg~r4YeCgb4o8MDR}p zQr-;7pGQPHawWe|@>i0^ocKG^u*Va`0XV}Enm$B21<3M4NMDBcw?fYrx=`qV(A7fU zDfC~3ex5Yyadkl$h`l_JauZ1-eY?=RNyBb&=o8v)5RiN$NF#j}Y4pQ-BHDcy)6w34 zk_O+`LZ1+N9Lms6lZnWmMNEW$09o#SN&lnJuM7PyX@rkRqrStEew^tjcSVAhcNLI) zxkTu@PSUF-{XU`Fq0dfoH%Y@@M}+>D(7y@25Mz(^ z6alH{CL;8DT+*MC^zEe4u9qbJO-Vm0^l{SAvpsCb^8JC7n?@RPvn740q}K@E%XH}X zw9qdI{khQJkcQm(=mW~j1Cp*5`jB7+>R|qC%tf3}Rsl(`C5>>J2w%Cf4{$L07s!5| zE0|3Le=+kf$JJFyzmM1qcNU1KYa5X5*+InkdYkF+ov#H?5@}=PF})=*6=zaJ$WH{i zhG1VN`DsMxF_zd2e+ZK}6#F0IFvD01bfuxaq`~)lNq>;(!!chFM_?UhI_jwJ$wIa7t6C8+d4`Vyg)KA>+9dcEKV!AAxEB>1f0%YyF-eku5G!QTY&b3&yT&rR5_ z-hx8}uM(Usm?szztQ5Rc@F79<*FYh!R_J#HzYydP#aQ33g3Vw%(iaQ%66CMQm_A-` zmSC=6KybAn{|GGk?-qPSkUxTCx<{~`U?;%@!9IeQ2@Vq+BRD~Ds^CmP{ylTbUo5Ep zlox2;@nX7q-UJ4PR?nNDHwk^8;DdsX3qB$Ev>^XM7s}f$_?jU9$s4A>FZi+G=Yod> zLxSH4{wNsZ*5#WCwiIkH$bVIg^1BK45=<5xBsffPl;Cv11%f4le-hj;_@$tF?nOP# zG3Hp`#eyRQ=L!}It`giV_@dwe!6Sm-3!W2fhJnrT>Je;B?0~!Xf`bIrb29W8C-fvD z=ov(mpCdR=@=F8*MDX$KnR06c)sL&N$9sx2aEGMtAwnL1D@8m=M0xdm4f;DtKS_i< zH|7{(OTo^9>iHY#{Yj(zP)VOmM1AU)R!Cn&8giEi77O1BBJwMQzEkjF!L5@2w9tD5 z_YoogeIn$3D0oQn|1I1)9 z8Nt|iEx(oER>7x;unW&Ci0Vglu+JN$fd>RXCqlntg6bRt`8LlZklsNsQ81MVd1->< zBz>CTJV{?5m@n!4MIPmqOM0cCItPKgjY9K0gnSPWp~s^_|4s6@3+@)&Be;)KsF z*9m<}@Ej5HERV*Eh>+8jh;scTJwXFcKN9>W5$!!B`Tr97gwVeV9fyr6`PvC~Btl*y5o>%up?TiKdG-pS zCkb97m?u~!SWfJUe+^w|bsp6d?Gl>z)cM@;ywH1z$+*wT{Uz+f4-r)=#Pp~T!%-pB zSJ*}nO;9vcSLhQ=5KI*8E7)I9Jtv@^RH4%ZM+%M=yh?DA;50$?oPhFkgq|n3Krlye zv0#B2ejs>2@H4@Kf`niuh4A- zI|%Z<68U_B34)1&eFggq4irokOcNX_I955PU%J5y7p3+XVk2_>ABV!50N<1z#21C-}DD zdx9Sb9uWLY@Sxyf!8*ZXg2x4a5IiIJtDphf&^~TKTQFYGE7(S`gJ4HNpJ0MuqF`Ua z{(=Jq)$=0aX+n<_94mO0;3UCmf-?m9dmZXKPjG=?j^JX!0>KXSbDSl26n`HmbgIxZ zgq|a`U+5J=-zD_DLO&z)4x!cfg!~VLR^tz}GyZJa8FakZJ5lJqLSH5HB%$&6V3_!F I&?|EPACcmbUH||9 literal 0 HcmV?d00001 diff --git a/obj-i486-linux-gnu-patched/doc/manual.html b/obj-i486-linux-gnu-patched/doc/manual.html new file mode 100644 index 0000000..a3e4c97 --- /dev/null +++ b/obj-i486-linux-gnu-patched/doc/manual.html @@ -0,0 +1,6459 @@ + +The Mutt E-Mail Client

The Mutt E-Mail Client

Michael Elkins

version 1.5.19 (2009-01-05)

Abstract

+“All mail clients suck. This one just sucks less.” -me, circa 1995 +

Table of Contents

1. Introduction
1. Mutt Home Page
2. Mailing Lists
3. Software Distribution Sites
4. Mutt online resources
5. Contributing to Mutt
6. Typograhical conventions
7. Copyright
2. Getting Started
1. Core concepts
2. Moving Around in Menus
3. Editing Input Fields
3.1. Introduction
3.2. History
4. Reading Mail - The Index and Pager
4.1. The Message Index
4.2. The Pager
4.3. Threaded Mode
4.4. Miscellaneous Functions
5. Sending Mail
5.1. Introduction
5.2. Editing the message header
5.3. Sending cryptographically signed/encrypted messages
5.4. Sending anonymous messages via mixmaster
5.5. Sending format=flowed messages
6. Forwarding and Bouncing Mail
7. Postponing Mail
3. Configuration
1. Location of initialization files
2. Syntax of Initialization Files
3. Address groups
4. Defining/Using aliases
5. Changing the default key bindings
6. Defining aliases for character sets
7. Setting variables based upon mailbox
8. Keyboard macros
9. Using color and mono video attributes
10. Message header display
11. Alternative addresses
12. Mailing lists
13. Using Multiple spool mailboxes
14. Monitoring incoming mail
15. User defined headers
16. Specify default save mailbox
17. Specify default Fcc: mailbox when composing
18. Specify default save filename and default Fcc: mailbox at once
19. Change settings based upon message recipients
20. Change settings before formatting a message
21. Choosing the cryptographic key of the recipient
22. Adding key sequences to the keyboard buffer
23. Executing functions
24. Message Scoring
25. Spam detection
26. Setting and Querying Variables
26.1. Commands
26.2. User-defined variables
27. Reading initialization commands from another file
28. Configuring features conditionnaly
29. Removing hooks
30. Format Strings
30.1. Basic usage
30.2. Filters
4. Advanced Usage
1. Regular Expressions
2. Patterns: Searching, Limiting and Tagging
2.1. Pattern Modifier
2.2. Simple Patterns
2.3. Complex Patterns
2.4. Searching by Date
3. Using Tags
4. Using Hooks
4.1. Message Matching in Hooks
5. External Address Queries
6. Mailbox Formats
7. Mailbox Shortcuts
8. Handling Mailing Lists
9. Handling multiple folders
10. Editing threads
10.1. Linking threads
10.2. Breaking threads
11. Delivery Status Notification (DSN) Support
12. Start a WWW Browser on URLs
5. Mutt's MIME Support
1. Using MIME in Mutt
1.1. Viewing MIME messages in the pager
1.2. The Attachment Menu
1.3. The Compose Menu
2. MIME Type configuration with mime.types
3. MIME Viewer configuration with mailcap
3.1. The Basics of the mailcap file
3.2. Secure use of mailcap
3.3. Advanced mailcap Usage
3.4. Example mailcap files
4. MIME Autoview
5. MIME Multipart/Alternative
6. Attachment Searching and Counting
7. MIME Lookup
6. Optional features
1. General notes
1.1. Enabling/disabling features
1.2. URL syntax
2. SSL/TLS Support
3. POP3 Support
4. IMAP Support
4.1. The Folder Browser
4.2. Authentication
5. SMTP Support
6. Managing multiple accounts
7. Local caching
7.1. Header caching
7.2. Body caching
7.3. Maintenance
8. Exact address generation
7. Performance tuning
1. Reading and writing mailboxes
2. Reading messages from remote folders
3. Searching and limiting
8. Reference
1. Command line options
2. Configuration Commands
3. Configuration variables
3.1. abort_nosubject
3.2. abort_unmodified
3.3. alias_file
3.4. alias_format
3.5. allow_8bit
3.6. allow_ansi
3.7. arrow_cursor
3.8. ascii_chars
3.9. askbcc
3.10. askcc
3.11. assumed_charset
3.12. attach_charset
3.13. attach_format
3.14. attach_sep
3.15. attach_split
3.16. attribution
3.17. autoedit
3.18. auto_tag
3.19. beep
3.20. beep_new
3.21. bounce
3.22. bounce_delivered
3.23. braille_friendly
3.24. check_mbox_size
3.25. charset
3.26. check_new
3.27. collapse_unread
3.28. uncollapse_jump
3.29. compose_format
3.30. config_charset
3.31. confirmappend
3.32. confirmcreate
3.33. connect_timeout
3.34. content_type
3.35. copy
3.36. crypt_use_gpgme
3.37. crypt_use_pka
3.38. crypt_autopgp
3.39. crypt_autosmime
3.40. date_format
3.41. default_hook
3.42. delete
3.43. delete_untag
3.44. digest_collapse
3.45. display_filter
3.46. dotlock_program
3.47. dsn_notify
3.48. dsn_return
3.49. duplicate_threads
3.50. edit_headers
3.51. editor
3.52. encode_from
3.53. envelope_from_address
3.54. escape
3.55. fast_reply
3.56. fcc_attach
3.57. fcc_clear
3.58. folder
3.59. folder_format
3.60. followup_to
3.61. force_name
3.62. forward_decode
3.63. forward_edit
3.64. forward_format
3.65. forward_quote
3.66. from
3.67. gecos_mask
3.68. hdrs
3.69. header
3.70. help
3.71. hidden_host
3.72. hide_limited
3.73. hide_missing
3.74. hide_thread_subject
3.75. hide_top_limited
3.76. hide_top_missing
3.77. history
3.78. history_file
3.79. honor_followup_to
3.80. hostname
3.81. ignore_linear_white_space
3.82. ignore_list_reply_to
3.83. imap_authenticators
3.84. imap_check_subscribed
3.85. imap_delim_chars
3.86. imap_headers
3.87. imap_idle
3.88. imap_keepalive
3.89. imap_list_subscribed
3.90. imap_login
3.91. imap_pass
3.92. imap_passive
3.93. imap_peek
3.94. imap_pipeline_depth
3.95. imap_servernoise
3.96. imap_user
3.97. implicit_autoview
3.98. include
3.99. include_onlyfirst
3.100. indent_string
3.101. index_format
3.102. ispell
3.103. keep_flagged
3.104. locale
3.105. mail_check
3.106. mailcap_path
3.107. mailcap_sanitize
3.108. maildir_mtime
3.109. header_cache
3.110. maildir_header_cache_verify
3.111. header_cache_pagesize
3.112. maildir_trash
3.113. mark_old
3.114. markers
3.115. mask
3.116. mbox
3.117. mbox_type
3.118. metoo
3.119. menu_context
3.120. menu_move_off
3.121. menu_scroll
3.122. meta_key
3.123. mh_purge
3.124. mh_seq_flagged
3.125. mh_seq_replied
3.126. mh_seq_unseen
3.127. mime_forward
3.128. mime_forward_decode
3.129. mime_forward_rest
3.130. mix_entry_format
3.131. mixmaster
3.132. move
3.133. message_cachedir
3.134. message_cache_clean
3.135. message_format
3.136. narrow_tree
3.137. net_inc
3.138. pager
3.139. pager_context
3.140. pager_format
3.141. pager_index_lines
3.142. pager_stop
3.143. crypt_autosign
3.144. crypt_autoencrypt
3.145. pgp_ignore_subkeys
3.146. crypt_replyencrypt
3.147. crypt_replysign
3.148. crypt_replysignencrypted
3.149. crypt_timestamp
3.150. sidebar_delim
3.151. sidebar_visible
3.152. sidebar_width
3.153. pgp_use_gpg_agent
3.154. crypt_verify_sig
3.155. smime_is_default
3.156. smime_ask_cert_label
3.157. smime_decrypt_use_default_key
3.158. pgp_entry_format
3.159. pgp_good_sign
3.160. pgp_check_exit
3.161. pgp_long_ids
3.162. pgp_retainable_sigs
3.163. pgp_autoinline
3.164. pgp_replyinline
3.165. pgp_show_unusable
3.166. pgp_sign_as
3.167. pgp_strict_enc
3.168. pgp_timeout
3.169. pgp_sort_keys
3.170. pgp_mime_auto
3.171. pgp_auto_decode
3.172. pgp_mime_signature_filename
3.173. pgp_mime_signature_description
3.174. pgp_decode_command
3.175. pgp_getkeys_command
3.176. pgp_verify_command
3.177. pgp_decrypt_command
3.178. pgp_clearsign_command
3.179. pgp_sign_command
3.180. pgp_encrypt_sign_command
3.181. pgp_encrypt_only_command
3.182. pgp_import_command
3.183. pgp_export_command
3.184. pgp_verify_key_command
3.185. pgp_list_secring_command
3.186. pgp_list_pubring_command
3.187. forward_decrypt
3.188. smime_timeout
3.189. smime_encrypt_with
3.190. smime_keys
3.191. smime_ca_location
3.192. smime_certificates
3.193. smime_decrypt_command
3.194. smime_verify_command
3.195. smime_verify_opaque_command
3.196. smime_sign_command
3.197. smime_sign_opaque_command
3.198. smime_encrypt_command
3.199. smime_pk7out_command
3.200. smime_get_cert_command
3.201. smime_get_signer_cert_command
3.202. smime_import_cert_command
3.203. smime_get_cert_email_command
3.204. smime_default_key
3.205. ssl_client_cert
3.206. ssl_force_tls
3.207. ssl_starttls
3.208. certificate_file
3.209. ssl_use_sslv3
3.210. ssl_use_tlsv1
3.211. ssl_min_dh_prime_bits
3.212. ssl_ca_certificates_file
3.213. pipe_split
3.214. pipe_decode
3.215. pipe_sep
3.216. pop_authenticators
3.217. pop_auth_try_all
3.218. pop_checkinterval
3.219. pop_delete
3.220. pop_host
3.221. pop_last
3.222. pop_reconnect
3.223. pop_user
3.224. pop_pass
3.225. post_indent_string
3.226. postpone
3.227. postponed
3.228. preconnect
3.229. print
3.230. print_command
3.231. print_decode
3.232. print_split
3.233. prompt_after
3.234. query_command
3.235. query_format
3.236. quit
3.237. quote_regexp
3.238. read_inc
3.239. read_only
3.240. realname
3.241. recall
3.242. record
3.243. reply_regexp
3.244. reply_self
3.245. reply_to
3.246. resolve
3.247. reverse_alias
3.248. reverse_name
3.249. reverse_realname
3.250. rfc2047_parameters
3.251. save_address
3.252. save_empty
3.253. save_history
3.254. save_name
3.255. score
3.256. score_threshold_delete
3.257. score_threshold_flag
3.258. score_threshold_read
3.259. send_charset
3.260. sendmail
3.261. sendmail_wait
3.262. shell
3.263. sig_dashes
3.264. sig_on_top
3.265. signature
3.266. simple_search
3.267. smart_wrap
3.268. smileys
3.269. sleep_time
3.270. smtp_authenticators
3.271. smtp_pass
3.272. smtp_url
3.273. sort
3.274. sort_alias
3.275. sort_aux
3.276. sort_browser
3.277. sort_re
3.278. spam_separator
3.279. spoolfile
3.280. status_chars
3.281. status_format
3.282. status_on_top
3.283. strict_threads
3.284. suspend
3.285. text_flowed
3.286. thread_received
3.287. thorough_search
3.288. tilde
3.289. time_inc
3.290. timeout
3.291. tmpdir
3.292. to_chars
3.293. trash
3.294. tunnel
3.295. use_8bitmime
3.296. use_domain
3.297. use_envelope_from
3.298. use_from
3.299. use_idn
3.300. use_ipv6
3.301. user_agent
3.302. visual
3.303. wait_key
3.304. weed
3.305. wrap
3.306. wrap_search
3.307. wrapmargin
3.308. write_inc
3.309. write_bcc
3.310. xterm_icon
3.311. xterm_set_titles
3.312. xterm_title
4. Functions
4.1. generic menu
4.2. index menu
4.3. pager menu
4.4. alias menu
4.5. query menu
4.6. attach menu
4.7. compose menu
4.8. postpone menu
4.9. browser menu
4.10. pgp menu
4.11. smime menu
4.12. mix menu
4.13. editor menu
9. Miscellany
1. Acknowledgements
2. About this document

List of Tables

1.1. Typographical conventions for special terms
2.1. Most common navigation keys
2.2. Most common line editor keys
2.3. Most common message index keys
2.4. Message status flags
2.5. Message recipient flags
2.6. Most common pager keys
2.7. ANSI escape sequences
2.8. Color sequences
2.9. Most common thread mode keys
2.10. Most common mail sending keys
2.11. Most common compose menu keys
2.12. PGP key menu flags
3.1. Symbolic key names
4.1. POSIX regular expression character classes
4.2. Regular expression repetition operators
4.3. GNU regular expression extensions
4.4. Pattern modifiers
4.5. Simple search keywords
4.6. Date units
8.1. Command line options
8.2. Default generic function bindings
8.3. Default index function bindings
8.4. Default pager function bindings
8.5. Default alias function bindings
8.6. Default query function bindings
8.7. Default attach function bindings
8.8. Default compose function bindings
8.9. Default postpone function bindings
8.10. Default browser function bindings
8.11. Default pgp function bindings
8.12. Default smime function bindings
8.13. Default mix function bindings
8.14. Default editor function bindings

List of Examples

3.1. Multiple configuration commands per line
3.2. Commenting configuration files
3.3. Escaping quotes in congfiguration files
3.4. Using external command's output in configuration files
3.5. Using environment variables in configuration files
3.6. Configuring external alias files
3.7. Setting sort method based on mailbox name
3.8. Header weeding
3.9. Configuring header display order
3.10. Defining custom headers
3.11. Using %-expandos in save-hook
3.12. Embedding push in folder-hook
3.13. Configuring spam detection
3.14. Using user-defined variables for config file readability
3.15. Using user-defined variables for backing up other config option values
3.16. Deferring user-defined variable expansion to runtime
3.17. Using external filters in format strings
4.1. Using boolean operators in patterns
4.2. Combining send-hook and my_hdr
5.1. Attachment counting

Chapter 1. Introduction

Table of Contents

1. Mutt Home Page
2. Mailing Lists
3. Software Distribution Sites
4. Mutt online resources
5. Contributing to Mutt
6. Typograhical conventions
7. Copyright

+Mutt is a small but very powerful text-based MIME mail client. Mutt is +highly configurable, and is well suited to the mail power user with advanced +features like key bindings, keyboard macros, mail threading, regular +expression searches and a powerful pattern matching language for selecting +groups of messages. +

1. Mutt Home Page

+The official homepage can be found at +http://www.mutt.org/. +

2. Mailing Lists

+To subscribe to one of the following mailing lists, send a message with the +word subscribe in the body to +list-name-request@mutt.org. +

Note

+All messages posted to +mutt-announce are automatically forwarded to +mutt-users, so you do not need to be subscribed to +both lists. +

3. Software Distribution Sites

+Mutt releases can be downloaded from +ftp://ftp.mutt.org/mutt/. +For a list of mirror sites, please refer to +http://www.mutt.org/download.html. +

4. Mutt online resources

Bug Tracking System

+The official mutt bug tracking system can be found at +http://dev.mutt.org/ +

Wiki

+An (unofficial) wiki can be found +at http://wiki.mutt.org/. +

IRC

+For the IRC user community, visit channel #mutt on +irc.freenode.net. +

USENET

+For USENET, see the newsgroup comp.mail.mutt. +

5. Contributing to Mutt

+There are various ways to contribute to the Mutt project. +

+Especially for new users it may be helpful to meet other new and +experienced users to chat about Mutt, talk about problems and share +tricks. +

+Since translations of Mutt into other languages are highly appreciated, +the mutt developers always look for skilled translators that help +improve and continue to maintain stale translations. +

+For contributing code patches for new features and bug fixes, please +refer to the developer pages at +http://dev.mutt.org/ for more details. +

6. Typograhical conventions

+This section lists typographical conventions followed throughout this +manual. See table Table 1.1, “Typographical conventions for special terms” for typographical +conventions for special terms. +

Table 1.1. Typographical conventions for special terms

ItemRefers to...
printf(3)UNIX manual pages, execute man 3 printf
<PageUp>named keys
<create-alias>named Mutt function
^GControl+G key combination
$mail_checkMutt configuration option

+Examples are presented as: +

+mutt -v
+

+Within command synopsis, curly brackets (“{}”) denote a set +of options of which one is mandatory, square brackets +(“[]”) denote optional arguments, three dots +denote that the argument may be repeated arbitrary times. +

7. Copyright

+Mutt is Copyright (C) 1996-2009 Michael R. Elkins + and others. +

+This program is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 2 of the License, or +(at your option) any later version. +

+This program is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. +

+You should have received a copy of the GNU General Public License +along with this program; if not, write to the Free Software +Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. +

Chapter 2. Getting Started

Table of Contents

1. Core concepts
2. Moving Around in Menus
3. Editing Input Fields
3.1. Introduction
3.2. History
4. Reading Mail - The Index and Pager
4.1. The Message Index
4.2. The Pager
4.3. Threaded Mode
4.4. Miscellaneous Functions
5. Sending Mail
5.1. Introduction
5.2. Editing the message header
5.3. Sending cryptographically signed/encrypted messages
5.4. Sending anonymous messages via mixmaster
5.5. Sending format=flowed messages
6. Forwarding and Bouncing Mail
7. Postponing Mail

+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 various web +pages. See the Mutt homepage for more details. +

+The keybindings described in this section are the defaults as distributed. +Your local system administrator may have altered the defaults for your site. +You can always type “?” in any menu to display the current bindings. +

+The first thing you need to do is invoke mutt, simply by typing mutt +at the command line. There are various command-line options, see +either the mutt man page or the reference. +

1. Core concepts

+Mutt is a text-based application which interacts with users through +different menus which are mostly line-/entry-based or page-based. A +line-based menu is the so-called “index” menu (listing all messages of +the currently opened folder) or the “alias” menu (allowing you to +select recipients from a list). Examples for page-based menus are the +“pager” (showing one message at a time) or the “help” menu listing +all available key bindings. +

+The user interface consists of a context sensitive help line at the top, +the menu's contents followed by a context sensitive status line and +finally the command line. The command line is used to display +informational and error messages as well as for prompts and for entering +interactive commands. +

+Because Mutt allows for customizing almost all key bindings, there are +so-called “functions” which can be executed manually (using the +command line) or in macros. Macros allow the user to bind a sequence of +commands to a single key or a short key sequence instead of repeating a +sequence of actions over and over. +

+Many commands (such as saving or copying a message to another folder) +can be applied to a single message or a set of messages (so-called +“tagged” messages). To help selecting messages, Mutt provides a rich +set of message patterns (such as recipients, sender, body contents, date +sent/received, etc.) which can be combined into complex expressions +using the boolean and and or +operations as well as negating. These patterns can also be used to (for +example) search for messages or to limit the index to show only matching +messages. +

+Mutt supports a “hook” concept which allows the user to execute +arbitrary configuration commands and functions in certain situations +such as entering a folder, starting a new message or replying to an +existing one. These hooks can be used to highly customize Mutt's +behaviour including managing multiple identities, customizing the +display for a folder or even implementing auto-archiving based on a +per-folder basis and much more. +

2. Moving Around in Menus

+The most important navigation keys common to all menus are shown in +Table 2.1, “Most common navigation keys”. +

Table 2.1. Most common navigation keys

KeyFunctionDescription
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
Z or <PageUp><page-up>go to the previous page
= or <Home><first-entry>jump to the first entry
* or <End><last-entry>jump to the last entry
q<quit>exit the current menu
?<help>list all keybindings for the current menu

3. Editing Input Fields

3.1. Introduction

+Mutt has a built-in line editor for inputting text, e.g. email +addresses or filenames. The keys used to manipulate text input are +very similar to those of Emacs. See Table 2.2, “Most common line editor keys” for a full +reference of available functions, their default key bindings, and +short descriptions. +

Table 2.2. Most common line editor keys

KeyFunctionDescription
^A or <Home><bol>move to the start of the line
^B or <Left><backward-char>move back one char
Esc B<backward-word>move back one word
^D or <Delete><delete-char>delete the char under the cursor
^E or <End><eol>move to the end of the line
^F or <Right><forward-char>move forward one char
Esc F<forward-word>move forward one word
<Tab><complete>complete filename or alias
^T<complete-query>complete address with query
^K<kill-eol>delete to the end of the line
Esc d<kill-eow>delete to the end of the word
^W<kill-word>kill the word in front of the cursor
^U<kill-line>delete entire line
^V<quote-char>quote the next typed key
<Up><history-up>recall previous string from history
<Down><history-down>recall next string from history
<BackSpace><backspace>kill the char in front of the cursor
Esc u<upcase-word>convert word to upper case
Esc l<downcase-word>convert word to lower case
Esc c<capitalize-word>capitalize the word
^Gn/aabort
<Return>n/afinish editing

+You can remap the editor functions using the +bind command. For example, to make +the <Delete> key delete the character in front of +the cursor rather than under, you could use: +

+bind editor <delete> backspace
+

3.2. History

+Mutt maintains a history for the built-in editor. The number of items +is controlled by the $history +variable and can be made persistent using an external file specified +using $history_file. +You may cycle through them at an editor prompt by using the +<history-up> and/or +<history-down> commands. +

+Mutt maintains several distinct history lists, one for each of the +following categories: +

  • muttrc commands

  • addresses and aliases

  • shell commands

  • filenames

  • patterns

  • everything else

+Mutt automatically filters out repeated items from the history. It +also mimics the behavior of some shells by ignoring items starting +with a space. The latter feature can be useful in macros to not clobber +the history's valuable entries with unwanted entries. +

4. Reading Mail - The Index and Pager

+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 of the +message contents. This is called the “pager.” +

+The next few sections describe the functions provided in each of these +modes. +

4.1. The Message Index

+Common keys used to navigate through and manage messages in the index +are shown in Table 2.3, “Most common message index keys”. How messages are presented +in the index menu can be customized using the +$index_format variable. +

Table 2.3. Most common message index keys

KeyDescription
cchange to a different mailbox
Esc cchange to a folder in read-only mode
Ccopy the current message to another mailbox
Esc Cdecode a message and copy it to a folder
Esc sdecode a message and save it to a folder
Ddelete messages matching a pattern
ddelete the current message
Fmark as important
lshow messages matching a pattern
Nmark message as new
ochange the current sort method
Oreverse sort the mailbox
qsave changes and exit
ssave-message
Ttag messages matching a pattern
ttoggle the tag on a message
Esc ttoggle tag on entire message thread
Uundelete messages matching a pattern
uundelete-message
vview-attachments
xabort changes and exit
<Return>display-message
<Tab>jump to the next new or unread message
@show the author's full e-mail address
$save changes to mailbox
/search
Esc /search-reverse
^Lclear and redraw the screen
^Tuntag messages matching a pattern

+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 “flags” in Table 2.4, “Message status flags” +may appear, some of which can be turned on or off using these functions: +<set-flag> and +<clear-flag> +bound by default to “w” and “W” respectively. +

+Furthermore, the flags in Table 2.5, “Message recipient flags” reflect +who the message is addressed to. They can be customized with the +$to_chars variable. +

Table 2.4. Message status flags

FlagDescription
Dmessage is deleted (is marked for deletion)
dmessage has attachments marked for deletion
Kcontains a PGP public key
Nmessage is new
Omessage is old
Pmessage is PGP encrypted
rmessage has been replied to
Smessage is signed, and the signature is successfully verified
smessage is signed
!message is flagged
*message is tagged

Table 2.5. Message recipient flags

FlagDescription
+message is to you and you only
Tmessage is to you, but also to or cc'ed to others
Cmessage is cc'ed to you
Fmessage is from you
Lmessage is sent to a subscribed mailing list

4.2. The Pager

+By default, Mutt uses its builtin pager to display the contents of messages. +The pager is very similar to the Unix program less though not nearly as +featureful. +

Table 2.6. Most common pager keys

KeyDescription
<Return>go down one line
<Space>display the next page (or next message if at the end of a message)
-go back to the previous page
nsearch for next match
Sskip beyond quoted text
Ttoggle display of quoted text
?show keybindings
/regular expression search
Esc /backward regular expression search
\toggle highlighting of search matches
^jump to the top of the message

+In addition to key bindings in Table 2.6, “Most common pager keys”, +many of the functions from the index menu are also available in +the pager, such as <delete-message> or <copy-message> +(this is one advantage over using an external pager to view messages). +

+Also, the internal pager supports a couple other advanced features. For +one, it will accept and translate the “standard” nroff sequences for +bold and underline. These sequences are a series of either the letter, +backspace (^H), the letter again for bold or the letter, backspace, +“_” for denoting underline. Mutt will attempt to display these +in bold and underline respectively if your terminal supports them. If +not, you can use the bold and underline color +objects to specify a color or mono attribute for them. +

+Additionally, the internal pager supports the ANSI escape sequences for +character attributes. Mutt translates them into the correct color and +character settings. The sequences Mutt supports are: +

+\e[Ps;Ps;..Ps;m
+

+where Ps can be one of the codes shown in +Table 2.7, “ANSI escape sequences”. +

Table 2.7. ANSI escape sequences

Escape codeDescription
0All attributes off
1Bold on
4Underline on
5Blink on
7Reverse video on
3<color>Foreground color is <color> (see Table 2.8, “Color sequences”)
4<color>Background color is <color> (see Table 2.8, “Color sequences”)

Table 2.8. Color sequences

Color codeColor
0Black
1Red
2Green
3Yellow
4Blue
5Magenta
6Cyan
7White

+Mutt uses these attributes for handling text/enriched +messages, and they can also be used by an external +autoview script for highlighting +purposes. +

Note

+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. +

Note

+Note that the search commands in the pager take regular expressions, +which are not quite the same as the more +complex patterns used by the search +command in the index. This is because the pager only performs simple +text search, whereas the index provides boolean filtering on several +aspects of messages. +

4.3. Threaded Mode

+When the mailbox is sorted by threads, there are +a few additional functions available in the index and pager modes +as shown in Table 2.9, “Most common thread mode keys”. +

Table 2.9. Most common thread mode keys

KeyFunctionDescription
^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
^P<previous-thread>jump to the start of the previous thread
^R<read-thread>mark the current thread as read
Esc d<delete-subthread>delete all messages in the current subthread
Esc u<undelete-subthread>undelete all messages in the current subthread
Esc n<next-subthread>jump to the start of the next subthread
Esc p<previous-subthread>jump to the start of the previous subthread
Esc r<read-subthread>mark the current subthread as read
Esc t<tag-thread>toggle the tag on the current thread
Esc v<collapse-thread>toggle collapse for the current thread
Esc V<collapse-all>toggle collapse for all threads
P<parent-message>jump to parent message in thread

Note

+Collapsing a thread displays only the first message +in the thread and hides the others. This is useful when threads +contain so many messages that you can only see a handful of threads on +the screen. See %M in $index_format. +For example, you could use "%?M?(#%03M)&(%4l)?" in $index_format to optionally +display the number of hidden messages if the thread is collapsed. +

+See also: $strict_threads. +

4.4. Miscellaneous Functions

+In addition, the index and pager +menus have these interesting functions: +

+<create-alias> (default: a) +

+Creates a new alias based upon the current message (or prompts for a +new one). Once editing is complete, an alias +command is added to the file specified by +the $alias_file variable +for future use +

Note

+Mutt does not read the $alias_file +upon startup so you must explicitly source the file. +

+<check-traditional-pgp> (default: Esc P) +

+This function will search the current message for content signed or +encrypted with PGP the “traditional” way, that is, without proper +MIME tagging. Technically, this function will temporarily change +the MIME content types of the body parts containing PGP data; this +is similar to the <edit-type> function's +effect. +

+<edit> (default: e) +

+This command (available in the index and pager) allows you to +edit the raw current message as it's present in the mail folder. +After you have finished editing, the changed message will be +appended to the current folder, and the original message will be +marked for deletion; if the message is unchanged it won't be replaced. +

+<edit-type> (default: +^E on the attachment menu, and in the pager and index menus; +^T on the compose menu) +

+This command is used to temporarily edit an attachment's content +type to fix, for instance, bogus character set parameters. When +invoked from the index or from the pager, you'll have the +opportunity to edit the top-level attachment's content type. On the +attachment menu, you can change any +attachment's content type. These changes are not persistent, and get +lost upon changing folders. +

+Note that this command is also available on the compose +menu. There, it's used to fine-tune the properties of attachments you are going +to send. +

+<enter-command> (default: “:”) +

+This command is used to execute any command you would normally put in a +configuration file. A common use is to check the settings of variables, or +in conjunction with macros to change settings on the +fly. +

+<extract-keys> (default: ^K) +

+This command extracts PGP public keys from the current or tagged +message(s) and adds them to your PGP public key ring. +

+<forget-passphrase> (default: +^F) +

+This command wipes the passphrase(s) from memory. It is useful, if +you misspelled the passphrase. +

+<list-reply> (default: L) +

+Reply to the current or tagged message(s) by extracting any addresses which +match the regular expressions given by the lists or subscribe +commands, but also honor any Mail-Followup-To header(s) if the +$honor_followup_to +configuration variable is set. Using this when replying to messages posted +to mailing lists helps avoid duplicate copies being sent to the author of +the message you are replying to. +

+<pipe-message> (default: |) +

+Asks for an external Unix command and pipes the current or +tagged message(s) to it. The variables $pipe_decode, $pipe_split, +$pipe_sep and $wait_key control the exact behavior of this function. +

+<resend-message> (default: Esc e) +

+Mutt takes the current message as a template for a +new message. This function is best described as "recall from arbitrary +folders". It can conveniently be used to forward MIME messages while +preserving the original mail structure. Note that the amount of headers +included here depends on the value of the $weed +variable. +

+This function is also available from the attachment menu. You can use this +to easily resend a message which was included with a bounce message +as a message/rfc822 body part. +

+<shell-escape> (default: !) +

+Asks for an external Unix command and executes it. The $wait_key can be used to control +whether Mutt will wait for a key to be pressed when the command returns +(presumably to let the user read the output of the command), based on +the return status of the named command. If no command is given, an +interactive shell is executed. +

+<toggle-quoted> (default: T) +

+The pager uses the $quote_regexp variable to detect quoted text when +displaying the body of the message. This function toggles the display +of the quoted material in the message. It is particularly useful when +being interested in just the response and there is a large amount of +quoted text in the way. +

+<skip-quoted> (default: S) +

+This function will go to the next line of non-quoted text which comes +after a line of quoted text in the internal pager. +

5. Sending Mail

5.1. Introduction

+The bindings shown in Table 2.10, “Most common mail sending keys” are available in the +index and pager to start a new message. +

Table 2.10. Most common mail sending keys

KeyFunctionDescription
m<compose>compose a new message
r<reply>reply to sender
g<group-reply>reply to all recipients
L<list-reply>reply to mailing list address
f<forward>forward message
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. These items are discussed +in greater detail in the next chapter “Forwarding +and Bouncing Mail.” +

+Mutt will then enter the compose menu and prompt you for the +recipients to place on the “To:” header field. Next, it will ask +you for the “Subject:” field for the message, providing a default if +you are replying to or forwarding a message. See also +$askcc, +$askbcc, +$autoedit, +$bounce, +$fast_reply, +and $include +for changing how Mutt asks these questions. +

+Mutt will then automatically start your $editor +on the message body. If the $edit_headers +variable is set, the headers will be at the top of the message in your editor. +Any messages you are replying to will be added in sort order to the message, +with appropriate $attribution, +$indent_string and +$post_indent_string. +When forwarding a message, if the $mime_forward +variable is unset, a copy of the forwarded message will be included. If +you have specified a $signature, it +will be appended to the message. +

+Once you have finished editing the body of your mail message, you are +returned to the compose menu providing the functions +shown in Table 2.11, “Most common compose menu keys” to modify, send or postpone the +message. +

Table 2.11. Most common compose menu keys

KeyFunctionDescription
a<attach-file>attach a file
A<attach-message>attach message(s) to the message
Esc k<attach-key>attach a PGP public key
d<edit-description>edit description on attachment
D<detach-file>detach a file
t<edit-to>edit the To field
Esc f<edit-from>edit the From field
r<edit-reply-to>edit the Reply-To field
c<edit-cc>edit the Cc field
b<edit-bcc>edit the Bcc field
y<send-message>send the message
s<edit-subject>edit the Subject
S<smime-menu>select S/MIME options
f<edit-fcc>specify an “Fcc” mailbox
p<pgp-menu>select PGP options
P<postpone-message>postpone this message until later
q<quit>quit (abort) sending the message
w<write-fcc>write the message to a folder
i<ispell>check spelling (if available on your system)
^F<forget-passphrase>wipe passphrase(s) from memory

+The compose menu is also used to edit the attachments for a message which can be either files +or other messages. The <attach-message> function to will prompt you for a folder to +attach messages from. You can now tag messages in that folder and they +will be attached to the message you are sending. +

Note

+Note that certain +operations like composing a new mail, replying, forwarding, etc. are +not permitted when you are in that folder. The %r in +$status_format will change to +a “A” to indicate that you are in attach-message mode. +

5.2. Editing the message header

+When editing the header because of $edit_headers +being set, there are a several pseudo headers available which +will not be included in sent messages. +

5.2.1. Fcc: pseudo header

+If you specify + +Fcc: filename + +as a header, Mutt will pick up filename +just as if you had used the <edit-fcc> function in the compose menu. +

5.2.2. Attach: pseudo header

+You can also attach files to your message by specifying + +Attach: filename [ description ] + +where filename is the file to attach and description is an +optional string to use as the description of the attached file. +

5.2.3. Pgp: pseudo header

+If you want to use PGP, you can specify +

+Pgp: [ E | S | S<id> ] + +

+“E” selects encryption, “S” selects signing and +“S<id>” selects signing with the given key, setting +$pgp_sign_as +permanently. +

5.2.4. In-Reply-To: header

+When replying to messages, the In-Reply-To: header contains the +Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a +References: field, which allows you to create a new message thread, for example +to create a new message to a mailing list without having to enter the mailing list's address. +

5.3. Sending cryptographically signed/encrypted messages

+If you have told mutt to PGP or S/MIME encrypt a message, it will guide you +through a key selection process when you try to send the message. +Mutt will not ask you any questions about keys which have a +certified user ID matching one of the message recipients' mail +addresses. However, there may be situations in which there are +several keys, weakly certified user ID fields, or where no matching +keys can be found. +

+In these cases, you are dropped into a menu with a list of keys from +which you can select one. When you quit this menu, or mutt can't +find any matching keys, you are prompted for a user ID. You can, as +usually, abort this prompt using ^G. When you do so, mutt will +return to the compose screen. +

+Once you have successfully finished the key selection, the message +will be encrypted using the selected public keys when sent out. +

+Most fields of the entries in the key selection menu (see also $pgp_entry_format) +have obvious meanings. But some explanations on the capabilities, flags, +and validity fields are in order. +

+The flags sequence (%f) will expand to one of the flags in +Table 2.12, “PGP key menu flags”. +

Table 2.12. PGP key menu flags

FlagDescription
RThe key has been revoked and can't be used.
XThe key is expired and can't be used.
dYou have marked the key as disabled.
cThere are unknown critical self-signature packets.

+The capabilities field (%c) expands to a two-character sequence +representing a key's capabilities. The first character gives +the key's encryption capabilities: A minus sign (“-”) means +that the key cannot be used for encryption. A dot (“.”) means that +it's marked as a signature key in one of the user IDs, but may +also be used for encryption. The letter “e” indicates that +this key can be used for encryption. +

+The second character indicates the key's signing capabilities. Once +again, a “-” implies “not for signing”, “.” implies +that the key is marked as an encryption key in one of the user-ids, and +“s” denotes a key which can be used for signing. +

+Finally, the validity field (%t) indicates how well-certified a user-id +is. A question mark (“?”) indicates undefined validity, a minus +character (“-”) marks an untrusted association, a space character +means a partially trusted association, and a plus character (“+”) +indicates complete validity. +

5.4. Sending anonymous messages via mixmaster

+You may also have compiled mutt to co-operate with Mixmaster, an +anonymous remailer. Mixmaster permits you to send your messages +anonymously using a chain of remailers. Mixmaster support in mutt is for +mixmaster version 2.04 (beta 45 appears to be the latest) and 2.03. +It does not support earlier versions or the later so-called version 3 betas, +of which the latest appears to be called 2.9b23. +

+To use it, you'll have to obey certain restrictions. Most +important, you cannot use the Cc and Bcc headers. To tell +Mutt to use mixmaster, you have to select a remailer chain, using +the mix function on the compose menu. +

+The chain selection screen is divided into two parts. In the +(larger) upper part, you get a list of remailers you may use. In +the lower part, you see the currently selected chain of remailers. +

+You can navigate in the chain using the <chain-prev> and +<chain-next> functions, which are by default bound to the left +and right arrows and to the h and l keys (think vi +keyboard bindings). To insert a remailer at the current chain +position, use the <insert> function. To append a remailer behind +the current chain position, use <select-entry> or <append>. +You can also delete entries from the chain, using the corresponding +function. Finally, to abandon your changes, leave the menu, or +<accept> them pressing (by default) the Return key. +

+Note that different remailers do have different capabilities, +indicated in the %c entry of the remailer menu lines (see +$mix_entry_format). Most important is +the “middleman” capability, indicated by a capital “M”: This +means that the remailer in question cannot be used as the final +element of a chain, but will only forward messages to other +mixmaster remailers. For details on the other capabilities, please +have a look at the mixmaster documentation. +

5.5. Sending format=flowed messages

5.5.1. Concept

+format=flowed-style messages (or f=f +for short) are text/plain messages that consist of paragraphs which a receiver's +mail client may reformat to its own needs which mostly means to +customize line lengths regardless of what the sender sent. Technically this is +achieved by letting lines of a “flowable” paragraph end in spaces +except for the last line. +

+While for text-mode clients like mutt it's the best way to assume only a +standard 80x25 character cell terminal, it may be desired to let the +receiver decide completely how to view a message. +

5.5.2. Mutt support

+Mutt only supports setting the required format=flowed +MIME parameter on outgoing messages if the $text_flowed +variable is set, specifically it does not add the +trailing spaces. +

+After editing the initial message text and before entering +the compose menu, mutt properly space-stuffes the message. +Space-stuffing is required by RfC3676 defining +format=flowed and means to prepend a space to: +

  • all lines starting with a space

  • lines starting with the word “From” +followed by space

  • all lines starting with “>” which +is not intended to be a quote character

Note

+Mutt only supports space-stuffing +for the first two types of lines but not for the third: It is impossible to +safely detect whether a leading > character starts a +quote or not. Furthermore, Mutt only applies space-stuffing +once after the initial edit is finished. +

+All leading spaces are to be removed by receiving clients to restore +the original message prior to further processing. +

5.5.3. Editor considerations

+As mutt provides no additional features to compose f=f +messages, it's completely up to the user and his editor to produce +proper messages. Please consider your editor's documentation if you +intend to send f=f messages. +

+Please note that when editing messages from the compose menu several +times before really sending a mail, it's up to the user to ensure that +the message is properly space-stuffed. +

+For example, vim provides the w +flag for its formatoptions setting to assist in +creating f=f messages, see :help +fo-table for details. +

6. Forwarding and Bouncing Mail

+Bouncing and forwarding let you send an existing message to recipients +that you specify. Bouncing a message sends a verbatim copy of a message +to alternative addresses as if they were the message's original +recipients specified in the Bcc header. +Forwarding a message, on the other hand, allows you to modify the message +before it is resent (for example, by adding your own comments). Bouncing +is done using the <bounce> function and forwarding +using the <forward> function bound to “b” and “f” +respectively. +

+Forwarding can be done by including the original message in the new +message's body (surrounded by indicating lines) or including it as a MIME +attachment, depending on the value of the $mime_forward variable. Decoding of attachments, +like in the pager, can be controlled by the $forward_decode and $mime_forward_decode variables, +respectively. The desired forwarding format may depend on the content, +therefore $mime_forward is a quadoption which, for +example, can be set to “ask-no”. +

+The inclusion of headers is controlled by the current setting of the +$weed variable, unless $mime_forward is set. +

+Editing the message to forward follows the same procedure as sending or +replying to a message does. +

7. Postponing Mail

+At times it is desirable to delay sending a message that you have +already begun to compose. When the <postpone-message> function is +used in the compose menu, the body of your message and attachments +are stored in the mailbox specified by the $postponed variable. This means that you can recall the +message even if you exit Mutt and then restart it at a later time. +

+Once a message is postponed, there are several ways to resume it. From the +command line you can use the “-p” option, or if you compose a new +message from the index or pager you will be prompted if postponed +messages exist. If multiple messages are currently postponed, the +postponed menu will pop up and you can select which message you would +like to resume. +

Note

+If you postpone a reply to a message, the reply setting of +the message is only updated when you actually finish the message and +send it. Also, you must be in the same folder with the message you +replied to for the status of the message to be updated. +

+See also the $postpone quad-option. +

Chapter 3. Configuration

Table of Contents

1. Location of initialization files
2. Syntax of Initialization Files
3. Address groups
4. Defining/Using aliases
5. Changing the default key bindings
6. Defining aliases for character sets
7. Setting variables based upon mailbox
8. Keyboard macros
9. Using color and mono video attributes
10. Message header display
11. Alternative addresses
12. Mailing lists
13. Using Multiple spool mailboxes
14. Monitoring incoming mail
15. User defined headers
16. Specify default save mailbox
17. Specify default Fcc: mailbox when composing
18. Specify default save filename and default Fcc: mailbox at once
19. Change settings based upon message recipients
20. Change settings before formatting a message
21. Choosing the cryptographic key of the recipient
22. Adding key sequences to the keyboard buffer
23. Executing functions
24. Message Scoring
25. Spam detection
26. Setting and Querying Variables
26.1. Commands
26.2. User-defined variables
27. Reading initialization commands from another file
28. Configuring features conditionnaly
29. Removing hooks
30. Format Strings
30.1. Basic usage
30.2. Filters

1. Location of initialization files

+While the default configuration (or “preferences”) make Mutt +usable right out of the box, it is often desirable to tailor Mutt to +suit your own tastes. When Mutt is first invoked, it will attempt to +read the “system” configuration file (defaults set by your local +system administrator), unless the “-n” command line option is specified. This file is typically +/usr/local/share/mutt/Muttrc or /etc/Muttrc. Mutt +will next look for a file named .muttrc in your home +directory. If this file does not exist and your home directory has +a subdirectory named .mutt, mutt try to load a file named +.mutt/muttrc. +

+.muttrc is the file where you will usually place your commands to configure Mutt. +

+In addition, mutt supports version specific configuration files that are +parsed instead of the default files as explained above. For instance, if +your system has a Muttrc-0.88 file in the system configuration +directory, and you are running version 0.88 of mutt, this file will be +sourced instead of the Muttrc file. The same is true of the user +configuration file, if you have a file .muttrc-0.88.6 in your home +directory, when you run mutt version 0.88.6, it will source this file +instead of the default .muttrc file. The version 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. +

2. Syntax of Initialization Files

+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 +(;). +

Example 3.1. Multiple configuration commands per line

+set realname='Mutt user' ; ignore x-
+

+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, +

Example 3.2. Commenting configuration files

+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 shell programs, +namely that a single quote is used to specify a literal string (one that is +not interpreted for shell variables or quoting with a backslash [see +next paragraph]), while double quotes indicate a string for which +should be evaluated. For example, backticks are evaluated inside of double +quotes, but not for single quotes. +

+\ quotes the next character, just as in shells such as bash and zsh. +For example, if want to put quotes “"” inside of a string, you can use +“\” to force the next character to be a literal instead of interpreted +character. +

Example 3.3. Escaping quotes in congfiguration files

+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. +

+A \ at the end of a line can be used to split commands over +multiple lines, provided that the split points don't appear in the +middle of command names. +

+It is also possible to substitute the output of a Unix command in an +initialization file. This is accomplished by enclosing the command in +backticks (``). For example, +

Example 3.4. Using external command's output in configuration files

+my_hdr X-Operating-System: `uname -a`
+

+The output of the Unix command “uname -a” will be substituted before the +line is parsed. +

Note

+Since initialization files are line oriented, only +the first line of output from the Unix command will be substituted. +

+Both environment variables and mutt variables can be accessed by +prepending “$” to the name of the variable. For example, +

Example 3.5. Using environment variables in configuration files

+set record=+sent_on_$HOSTNAME
+

+will cause mutt to save outgoing messages to a folder named +“sent_on_kremvax” if the environment variable HOSTNAME is set to +“kremvax.” (See $record for +details.) +

+Mutt expands the variable when it is assigned, not when it is used. If +the value of a variable on the right-hand side of an assignment +changes after the assignment, the variable on the left-hand side will +not be affected. +

+The commands understood by mutt are explained in the next paragraphs. +For a complete list, see the command reference. +

+All configuration files are expected to be in the current locale as +specified by the $charset variable +which doesn't have a default value since it's determined by Mutt at startup. +If a configuration file is not encoded in the same character set the +$config_charset +variable should be used: all lines starting with the next are recoded +from $config_charset to $charset. +

+This mechanism should be avoided if possible as it has the +following implications: +

  • These variables should be set early in a configuration +file with $charset preceding $config_charset so Mutt +know what character set to convert to.

  • If $config_charset is set, it should be set +in each configuration file because the value is global and not +per configuration file.

  • Because Mutt first recodes a line before it attempts to parse it, +a conversion introducing question marks or other characters as +part of errors (unconvertable characters, transliteration) may introduce syntax +errors or silently change the meaning of certain tokens (e.g. inserting +question marks into regular expressions).

3. Address groups

Usage:

group [ +-group +name +...] { +-rx +expr +... | +-addr +expr +... }

ungroup [ +-group +name +...] { +* + | +-rx +expr +... | +-addr +expr +... }

+group is used to directly add either addresses or +regular expressions to the specified group or groups. The different +categories of arguments to the group command can be +in any order. The flags -rx and +-addr specify what the following strings (that cannot +begin with a hyphen) should be interpreted as: either a regular +expression or an email address, respectively. +

+These address groups can also be created implicitly by the +alias, lists, +subscribe and +alternates commands by specifying the +optional -group option. +

+Once defined, these address groups can be used in +patterns to search for and limit the +display to messages matching a group. +

+ungroup is used to remove addresses or regular +expressions from the specified group or groups. The syntax is similar to +the group command, however the special character +* can be used to empty a group of all of its +contents. +

4. Defining/Using aliases

Usage:

alias [ +-group +name +...] +key + +address + [ +address +...]

+It's usually very cumbersome to remember or type out the address of someone +you are communicating with. Mutt allows you to create “aliases” which map +a short string to a full address. +

Note

+If you want to create an alias for more than +one address, you must separate the addresses with a comma (“,”). +

+The optional -group argument to +alias causes the aliased address(es) to be added to +the named group. +

+To remove an alias or aliases (“*” means all aliases): +

unalias [ +-group +name +...] { +* + | +key +... }

+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. Consequently, you can have multiple alias files, or +you can have all aliases defined in your muttrc. +

+On the other hand, the <create-alias> +function can use only one file, the one pointed to by the $alias_file variable (which is +˜/.muttrc by default). This file is not special either, +in the sense that Mutt will happily append aliases to any file, but in +order for the new aliases to take effect you need to explicitly source this file too. +

+For example: +

Example 3.6. Configuring external alias files

+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 To: or Cc: prompt. You can +also enter aliases in your editor at the appropriate headers if you have the +$edit_headers variable set. +

+In addition, at the various address prompts, you can use the tab character +to expand a partial alias to the full alias. If there are multiple matches, +mutt will bring up a menu with the matching aliases. In order to be +presented with the full list of aliases, you must hit tab with out a partial +alias, such as at the beginning of the prompt or after a comma denoting +multiple addresses. +

+In the alias menu, you can select as many aliases as you want with the +select-entry key (default: <Return>), and use the +exit key (default: q) to return to the address prompt. +

5. Changing the default key bindings

Usage:

bind +map + +key + +function +

+This command allows you to change the default key bindings (operation +invoked when pressing a key). +

+map specifies in which menu the binding belongs. Multiple maps may +be specified by separating them with commas (no additional whitespace is +allowed). The currently defined maps are: +

generic

+This is not a real menu, but is used as a fallback for all of the other +menus except for the pager and editor modes. If a key is not defined in +another menu, Mutt will look for a binding to use in this menu. This allows +you to bind a key to a certain function in multiple menus instead of having +multiple bind statements to accomplish the same task. +

alias

+The alias menu is the list of your personal aliases as defined in your +muttrc. It is the mapping from a short alias name to the full email +address(es) of the recipient(s). +

attach

+The attachment menu is used to access the attachments on received messages. +

browser

+The browser is used for both browsing the local directory structure, and for +listing all of your incoming mailboxes. +

editor

+The editor is the line-based editor the user enters text data. +

index

+The index is the list of messages contained in a mailbox. +

compose

+The compose menu is the screen used when sending a new message. +

pager

+The pager is the mode used to display message/attachment data, and help +listings. +

pgp

+The pgp menu is used to select the OpenPGP keys used to encrypt outgoing +messages. +

smime

+The smime menu is used to select the OpenSSL certificates used to encrypt outgoing +messages. +

postpone

+The postpone menu is similar to the index menu, except is used when +recalling a message the user was composing, but saved until later. +

query

+The query menu is the browser for results returned by +$query_command. +

mix

+The mixmaster screen is used to select remailer options for outgoing +messages (if Mutt is compiled with Mixmaster support). +

+key is the key (or key sequence) you wish to bind. To specify a +control character, use the sequence \Cx, where x is the +letter of the control character (for example, to specify control-A use +“\Ca”). Note that the case of x as well as \C is +ignored, so that \CA, \Ca, \cA and \ca are all +equivalent. An alternative form is to specify the key as a three digit +octal number prefixed with a “\” (for example \177 is +equivalent to \c?). In addition, key may +be a symbolic name as shown in Table 3.1, “Symbolic key names”. +

Table 3.1. Symbolic key names

Symbolic nameMeaning
\ttab
<tab>tab
<backtab>backtab / shift-tab
\rcarriage return
\nnewline
\eescape
<esc>escape
<up>up arrow
<down>down arrow
<left>left arrow
<right>right arrow
<pageup>Page Up
<pagedown>Page Down
<backspace>Backspace
<delete>Delete
<insert>Insert
<enter>Enter
<return>Return
<home>Home
<end>End
<space>Space bar
<f1>function key 1
<f10>function key 10

+key does not need to be enclosed in quotes unless it contains a +space (“ ”) or semi-colon (“;”). +

+function specifies which action to take when key is pressed. +For a complete list of functions, see the reference. The special function <noop> unbinds the specified key +sequence. +

6. Defining aliases for character sets

Usage:

charset-hook +alias + +charset +

iconv-hook +charset + +local-charset +

+The charset-hook command defines an alias for a character set. +This is useful to properly display messages which are tagged with a +character set name not known to mutt. +

+The iconv-hook command defines a system-specific name for a +character set. This is helpful when your systems character +conversion library insists on using strange, system-specific names +for character sets. +

7. Setting variables based upon mailbox

Usage:

folder-hook +[!]regexp + +command +

+It is often desirable to change settings based on which mailbox you are +reading. The folder-hook command provides a method by which you can execute +any configuration command. regexp is a regular expression specifying +in which mailboxes to execute command before loading. If a mailbox +matches multiple folder-hook's, they are executed in the order given in the +muttrc. +

Note

+If you use the “!” shortcut for $spoolfile at the beginning of the pattern, you must place it +inside of double or single quotes in order to distinguish it from the +logical not operator for the expression. +

Note

+Settings are not restored when you leave the mailbox. +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 default command, use the +pattern “.” before other folder-hooks adjusting a value on a per-folder basis +because folder-hooks are evaluated in the order given in the configuration file. +The following example will set the sort variable +to date-sent for all folders but to threads +for all folders containing “mutt” in their name. +

Example 3.7. Setting sort method based on mailbox name

+folder-hook . set sort=date-sent
+folder-hook mutt set sort=threads
+

8. Keyboard macros

Usage:

macro +menu + +key + +sequence + [ +description +]

+Macros are useful when you would like a single key to perform a series of +actions. When you press key in menu menu, Mutt will behave as if +you had typed sequence. So if you have a common sequence of commands +you type, you can create a macro to execute those commands with a single +key or fewer keys. +

+menu is the map which the macro will be bound in. +Multiple maps may be specified by separating multiple menu arguments by +commas. Whitespace may not be used in between the menu arguments and the +commas separating them. +

+key and sequence are expanded by the same rules as the +key bindings with some additions. The +first is that control characters in sequence can also be specified +as ^x. In order to get a caret (“^”) you need to use +^^. Secondly, to specify a certain key such as up +or to invoke a function directly, you can use the format +<key name> and <function name>. For a listing of key +names see the section on key bindings. Functions +are listed in the reference. +

+The advantage with using function names directly is that the macros will +work regardless of the current key bindings, so they are not dependent on +the user having particular key definitions. This makes them more robust +and portable, and also facilitates defining of macros in files used by more +than one user (e.g., the system Muttrc). +

+Optionally you can specify a descriptive text after sequence, +which is shown in the help screens. +

Note

+Macro definitions (if any) listed in the help screen(s), are +silently truncated at the screen width, and are not wrapped. +

9. Using color and mono video attributes

Usage:

color +object + +foreground + +background +

color { +header + | +body + } +foreground + +background + +regexp +

color +index + +foreground + +background + +pattern +

uncolor +index + { +* + | +pattern +... }

+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 information), you +must specify both a foreground color and a background color (it is not +possible to only specify one or the other). +

+header and body match regexp +in the header/body of a message, index matches pattern +(see Section 2, “Patterns: Searching, Limiting and Tagging”) in the message index. +

+object can be one of: +

  • attachment

  • bold (hiliting bold patterns in the body of messages)

  • error (error messages printed by Mutt)

  • hdrdefault (default color of the message header in the pager)

  • indicator (arrow or bar used to indicate the current item in a menu)

  • markers (the “+” markers at the beginning of wrapped lines in the pager)

  • message (informational messages)

  • normal

  • quoted (text matching $quote_regexp in the body of a message)

  • quoted1, quoted2, ..., quotedN (higher levels of quoting)

  • search (hiliting of words in the pager)

  • signature

  • status (mode lines used to display info about the mailbox or message)

  • tilde (the “˜” used to pad blank lines in the pager)

  • tree (thread tree drawn in the message index and attachment menu)

  • underline (hiliting underlined patterns in the body of messages)

+foreground and background can be one of the following: +

  • white

  • black

  • green

  • magenta

  • blue

  • cyan

  • yellow

  • red

  • default

  • colorx

+foreground can optionally be prefixed with the keyword bright to make +the foreground color boldfaced (e.g., brightred). +

+If your terminal supports it, the special keyword default can be +used as a transparent color. The value brightdefault is also valid. +If Mutt is linked against the S-Lang library, you also need to set +the COLORFGBG 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
+

Note

+The S-Lang library requires you to use the lightgray +and brown keywords instead of white and yellow when +setting this variable. +

Note

+The uncolor command can be applied to the index object only. It +removes entries from the list. You must 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 color0, color1, …, +colorN-1 (N being the number of colors supported +by your terminal). This is useful when you remap the colors for your +display (for example by changing the color associated with color2 +for your xterm), since color names may then lose their normal meaning. +

+If your terminal does not support color, it is still possible change the video +attributes through the use of the “mono” command: +

Usage:

mono +object + +attribute +

mono { +header + | +body + } +attribute + +regexp +

mono +index + +attribute + +pattern +

unmono +index + { +* + | +pattern +... }

+For object, see the color command. attribute +can be one of the following: +

  • none

  • bold

  • underline

  • reverse

  • standout

10. Message header display

Usage:

ignore +pattern + [ +pattern +...]

unignore { +* + | +pattern +... }

+Messages often have many header fields added by automatic processing systems, +or which may not seem useful to display on the screen. This command allows +you to specify header fields which you don't normally want to see in the pager. +

+You do not need to specify the full header field name. For example, +“ignore content-” will ignore all header fields that begin with the pattern +“content-”. “ignore *” will ignore all headers. +

+To remove a previously added token from the list, use the “unignore” command. +The “unignore” command will make Mutt display headers with the given pattern. +For example, if you do “ignore x-” it is possible to “unignore x-mailer”. +

+“unignore *” will remove all tokens from the ignore list. +

+For example: +

Example 3.8. Header weeding

+# 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:
+

Usage:

hdr_order +header + [ +header +...]

unhdr_order { +* + | +header +... }

+With the hdr_order command you can specify an order in +which mutt will attempt to present these headers to you when viewing messages. +

+“unhdr_order *” will clear all previous headers from the order list, +thus removing the header order effects set by the system-wide startup file. +

Example 3.9. Configuring header display order

+hdr_order From Date: From: To: Cc: Subject:
+

11. Alternative addresses

Usage:

alternates [ +-group +name +...] +regexp + [ +regexp +...]

unalternates [ +-group +name +...] { +* + | +regexp +... }

+With various functions, mutt will treat messages differently, +depending on whether you sent them or whether you received them from +someone else. For instance, when replying to a message that you +sent to a different party, mutt will automatically suggest to send +the response to the original message's recipients -- responding to +yourself won't make much sense in many cases. (See $reply_to.) +

+Many users receive e-mail under a number of different addresses. To +fully use mutt's features here, the program must be able to +recognize what e-mail addresses you receive mail under. That's the +purpose of the alternates command: It takes a list of regular +expressions, each of which can identify an address under which you +receive e-mail. +

+As addresses are matched using regular expressions and not exact strict +comparisons, you should make sure you specify your addresses as precise +as possible to avoid mismatches. For example, if you specify: +

+alternates user@example
+

+mutt will consider “some-user@example” as +being your address, too which may not be desired. As a solution, in such +cases addresses should be specified as: +

+alternates '^user@example$'
+

+The -group flag causes all of the subsequent regular expressions +to be added to the named group. +

+The unalternates command can be used to write exceptions to +alternates patterns. If an address matches something in an +alternates command, but you nonetheless do not think it is +from you, you can list a more precise pattern under an unalternates +command. +

+To remove a regular expression from the alternates list, use the +unalternates command with exactly the same regexp. +Likewise, if the regexp for an alternates command matches +an entry on the unalternates list, that unalternates +entry will be removed. If the regexp for unalternates +is “*”, all entries on alternates will be removed. +

12. Mailing lists

Usage:

lists [ +-group +name +...] +regexp + [ +regexp +...]

unlists [ +-group +name +...] { +* + | +regexp +... }

subscribe [ +-group +name +...] +regexp + [ +regexp +...]

unsubscribe [ +-group +name +...] { +* + | +regexp +... }

+Mutt has a few nice features for handling mailing lists. In order to take advantage of them, you must +specify which addresses belong to mailing lists, and which mailing +lists you are subscribed to. Once you have done this, the <list-reply> function will work for all known lists. +Additionally, when you send a message to a subscribed list, mutt will +add a Mail-Followup-To header to tell other users' mail user agents +not to send copies of replies to your personal address. +

Note

+The Mail-Followup-To header is a non-standard extension which is not +supported by all mail user agents. Adding it is not bullet-proof against +receiving personal CCs of list messages. Also note that the generation +of the Mail-Followup-To header is controlled by the +$followup_to +configuration variable. +

+More precisely, Mutt maintains lists of patterns for the addresses +of known and subscribed mailing lists. Every subscribed mailing +list is known. To mark a mailing list as known, use the “lists” +command. To mark it as subscribed, use “subscribe”. +

+You can use regular expressions with both commands. To mark all +messages sent to a specific bug report's address on mutt's bug +tracking system as list mail, for instance, you could say +“subscribe [0-9]*@bugs.guug.de”. Often, it's sufficient to just +give a portion of the list's e-mail address. +

+Specify as much of the address as you need to to remove ambiguity. For +example, if you've subscribed to the Mutt mailing list, you will receive mail +addressed to mutt-users@mutt.org. So, to tell Mutt +that this is a mailing list, you could add “lists mutt-users@” to your +initialization file. To tell mutt that you are subscribed to it, +add “subscribe mutt-users” to your initialization file instead. +If you also happen to get mail from someone whose address is +mutt-users@example.com, you could use +“lists ^mutt-users@mutt\\.org$” +or “subscribe ^mutt-users@mutt\\.org$” to +match only mail from the actual list. +

+The -group flag adds all of the subsequent regular expressions +to the named group. +

+The “unlists” command is used to remove a token from the list of +known and subscribed mailing-lists. Use “unlists *” to remove all +tokens. +

+To remove a mailing list from the list of subscribed mailing lists, +but keep it on the list of known mailing lists, use “unsubscribe”. +

13. Using Multiple spool mailboxes

Usage:

mbox-hook +[!]pattern + +mailbox +

+This command is used to move read messages from a specified mailbox to a +different mailbox automatically when you quit or change folders. +pattern is a regular expression specifying the mailbox to treat as a +“spool” mailbox and mailbox specifies where mail should be saved when +read. +

+Unlike some of the other hook commands, only the first matching +pattern is used (it is not possible to save read mail in more than a single +mailbox). +

14. Monitoring incoming mail

Usage:

mailboxes +mailbox + [ +mailbox +...]

unmailboxes { +* + | +mailbox +... }

+This command specifies folders which can receive mail and +which will be checked for new messages periodically. +

+folder can either be a local file or directory +(Mbox/Mmdf or Maildir/Mh). If Mutt was built with POP and/or IMAP +support, folder can also be a POP/IMAP folder +URL. The URL syntax is described in Section 1.2, “URL syntax”, +POP and IMAP are described in Section 3, “POP3 Support” and Section 4, “IMAP Support” +respectively. +

+Mutt provides a number of advanced features for handling (possibly many) +folders and new mail within them, please refer to +Section 9, “Handling multiple folders” for details (including in what +situations and how often Mutt checks for new mail). +

+The “unmailboxes” command is used to remove a token from the list +of folders which receive mail. Use “unmailboxes *” to remove all +tokens. +

Note

+The folders 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 affects these characters (like $folder and $spoolfile) +should be set before the mailboxes command. If +none of these shorcuts are used, a local path should be absolute as +otherwise mutt tries to find it relative to the directory +from where mutt was started which may not always be desired. +

+For Mbox and Mmdf folders, new mail is detected by comparing access and/or +modification times of files: Mutt assumes a folder has new mail if it wasn't +accessed after it was last modified. Utilities like biff or +frm or any other program which accesses the mailbox might cause +Mutt to never detect new mail for that mailbox if they do not properly reset the +access time. Other possible causes of Mutt not detecting new mail in these folders +are backup tools (updating access times) or filesystems mounted without +access time update support. +

+In cases where new mail detection for Mbox or Mmdf folders appears to be +unreliable, the +$check_mbox_size +option can be used to make Mutt track and consult file sizes for new +mail detection instead. +

15. User defined headers

Usage:

my_hdr +string +

unmy_hdr { +* + | +field +... }

+The my_hdr command allows you to create your own header +fields which will be added to every message you send. +

+For example, if you would like to add an “Organization:” header field to +all of your outgoing messages, you can put the command +

Example 3.10. Defining custom headers

+my_hdr Organization: A Really Big Company, Anytown, USA
+

+in your .muttrc. +

Note

+Space characters are not allowed between the keyword and +the colon (“:”). The standard for electronic mail (RFC2822) says that +space is illegal there, so Mutt enforces the rule. +

+If you would like to add a header field to a single message, you should +either set the $edit_headers variable, +or use the <edit-headers> function (default: “E”) in the compose 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
+

16. Specify default save mailbox

Usage:

save-hook +[!]pattern + +mailbox +

+This command is used to override the default mailbox used when saving +messages. mailbox will be used as the default if the message +matches pattern, see Message Matching in Hooks for information +on the exact format. +

+To provide more flexibility and good defaults, Mutt applies the +expandos of $index_format to +mailbox after it was expanded. +

+Examples: +

Example 3.11. Using %-expandos in save-hook

+# default: save all to ~/Mail/<author name>
+save-hook . ~/Mail/%F
+
+# save from me@turing.cs.hmc.edu and me@cs.hmc.edu to $folder/elkins
+save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
+
+# save from aol.com to $folder/spam
+save-hook aol\\.com$ +spam
+

+Also see the fcc-save-hook command. +

17. Specify default Fcc: mailbox when composing

Usage:

fcc-hook +[!]pattern + +mailbox +

+This command is used to save outgoing mail in a mailbox other than +$record. Mutt searches the initial list of +message recipients for the first matching regexp and uses mailbox +as the default Fcc: mailbox. If no match is found the message will be saved +to $record mailbox. +

+To provide more flexibility and good defaults, Mutt applies the +expandos of $index_format to +mailbox after it was expanded. +

+See Message Matching in Hooks for information on the exact format of pattern. +

+Example: fcc-hook [@.]aol\\.com$ +spammers +

+The above will save a copy of all messages going to the aol.com domain to +the `+spammers' mailbox by default. Also see the fcc-save-hook command. +

18. Specify default save filename and default Fcc: mailbox at once

Usage:

fcc-save-hook +[!]pattern + +mailbox +

+This command is a shortcut, equivalent to doing both a fcc-hook +and a save-hook with its arguments, +including %-expansion on mailbox according +to $index_format. +

19. Change settings based upon message recipients

Usage:

reply-hook +[!]pattern + +command +

send-hook +[!]pattern + +command +

send2-hook +[!]pattern + +command +

+These commands can be used to execute arbitrary configuration commands based +upon recipients of the message. pattern is used to match +the message, see Message Matching in Hooks for details. command +is executed when pattern matches. +

+reply-hook is matched against the message you are replying to, +instead of the message you are sending. send-hook is +matched against all messages, both new +and replies. +

Note

+reply-hooks are matched before the send-hook, regardless +of the order specified in the user's configuration file. +

+send2-hook is matched every time a message is changed, either +by editing it, or by using the compose menu to change its recipients +or subject. send2-hook is executed after send-hook, and +can, e.g., be used to set parameters such as the $sendmail variable depending on the message's sender +address. +

+For each type of send-hook or reply-hook, when multiple matches +occur, commands are executed in the order they are specified in the muttrc +(for that type of hook). +

+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 change the language of the attributions and +signatures based upon the recipients. +

Note

+send-hook's are only executed once after getting the initial +list of recipients. Adding a recipient after replying or editing the +message will not cause any send-hook to be executed. Also note that +my_hdr commands which modify recipient headers, or the message's +subject, don't have any effect on the current message when executed +from a send-hook. +

20. Change settings before formatting a message

Usage:

message-hook +[!]pattern + +command +

+This command can be used to execute arbitrary configuration commands +before viewing or formatting a message based upon information about the message. +command is executed if the pattern matches the message to be +displayed. When multiple matches occur, commands are executed in the order +they are specified in the muttrc. +

+See Message Matching in Hooks for +information on the exact format of pattern. +

+Example: +

+message-hook ~A 'set pager=builtin'
+message-hook '~f freshmeat-news' 'set pager="less \"+/^  subject: .*\""'
+

21. Choosing the cryptographic key of the recipient

Usage:

crypt-hook +pattern + +keyid +

+When encrypting messages with PGP/GnuPG or OpenSSL, you may want to associate a certain +key with a given e-mail address automatically, either because the +recipient's public key can't be deduced from the destination address, +or because, for some reasons, you need to override the key Mutt would +normally use. The crypt-hook command provides a +method by which you can specify the ID of the public key to be used +when encrypting messages to a certain recipient. +

+The meaning of keyid is to be taken broadly in this context: You +can either put a numerical key ID here, an e-mail address, or even +just a real name. +

22. Adding key sequences to the keyboard buffer

Usage:

push +string +

+This command adds the named string to the keyboard buffer. The string may +contain control characters, key names and function names like the sequence +string in the macro command. You may use it to +automatically run a sequence of commands at startup, or when entering +certain folders. For example, the following command will automatically +collapse all threads when entering a folder: +

Example 3.12. Embedding push in folder-hook

+folder-hook . 'push <collapse-all>'
+

23. Executing functions

Usage:

exec +function + [ +function +...]

+This command can be used to execute any function. Functions are +listed in the function reference. +“exec function” is equivalent to “push <function>”. +

24. Message Scoring

Usage:

score +pattern + +value +

unscore { +* + | +pattern +... }

+The score commands adds value to a message's score if pattern +matches it. pattern is a string in the format described in the patterns section (note: For efficiency reasons, patterns +which scan information not available in the index, such as ˜b, +˜B or ˜h, may not be used). value is a +positive or negative integer. A message's final score is the sum total of all +matching score entries. However, you may optionally prefix value with +an equal sign (=) to cause evaluation to stop at a particular entry if there is +a match. Negative final scores are rounded up to 0. +

+The unscore command removes score entries from the list. You must +specify the same pattern specified in the score command for it to be +removed. The pattern “*” is a special token which means to clear the list +of all score entries. +

25. Spam detection

Usage:

spam +pattern + +format +

nospam { +* + | +pattern + }

+Mutt has generalized support for external spam-scoring filters. +By defining your spam patterns with the spam and nospam +commands, you can limit, search, and sort your +mail based on its spam attributes, as determined by the external +filter. You also can display the spam attributes in your index +display using the %H selector in the $index_format variable. (Tip: try %?H?[%H] ? +to display spam tags only when they are defined for a given message.) +

+Your first step is to define your external filter's spam patterns using +the spam command. pattern should be a regular expression +that matches a header in a mail message. If any message in the mailbox +matches this regular expression, it will receive a “spam tag” or +“spam attribute” (unless it also matches a nospam pattern -- see +below.) The appearance of this attribute is entirely up to you, and is +governed by the format parameter. format can be any static +text, but it also can include back-references from the pattern +expression. (A regular expression “back-reference” refers to a +sub-expression contained within parentheses.) %1 is replaced with +the first back-reference in the regex, %2 with the second, etc. +

+If you're using multiple spam filters, a message can have more than +one spam-related header. You can define spam patterns for each +filter you use. If a message matches two or more of these patterns, and +the $spam_separator variable is set to a string, then the +message's spam tag will consist of all the format strings joined +together, with the value of $spam_separator separating +them. +

+For example, suppose I use DCC, SpamAssassin, and PureMessage. I might +define these spam settings: +

Example 3.13. Configuring spam detection

+spam "X-DCC-.*-Metrics:.*(....)=many"         "90+/DCC-%1"
+spam "X-Spam-Status: Yes"                     "90+/SA"
+spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
+set spam_separator=", "
+

+If I then received a message that DCC registered with “many” hits +under the “Fuz2” checksum, and that PureMessage registered with a +97% probability of being spam, that message's spam tag would read +90+/DCC-Fuz2, 97/PM. (The four characters before “=many” in a +DCC report indicate the checksum used -- in this case, “Fuz2”.) +

+If the $spam_separator variable is unset, then each +spam pattern match supersedes the previous one. Instead of getting +joined format strings, you'll get only the last one to match. +

+The spam tag is what will be displayed in the index when you use +%H in the $index_format variable. It's also the +string that the ˜H pattern-matching expression matches against for +<search> and <limit> functions. And it's what sorting by spam +attribute will use as a sort key. +

+That's a pretty complicated example, and most people's actual +environments will have only one spam filter. The simpler your +configuration, the more effective mutt can be, especially when it comes +to sorting. +

+Generally, when you sort by spam tag, mutt will sort lexically -- +that is, by ordering strings alphanumerically. However, if a spam tag +begins with a number, mutt will sort numerically first, and lexically +only when two numbers are equal in value. (This is like UNIX's +sort -n.) A message with no spam attributes at all -- that is, one +that didn't match any of your spam patterns -- is sorted at +lowest priority. Numbers are sorted next, beginning with 0 and ranging +upward. Finally, non-numeric strings are sorted, with “a” taking lower +priority than “z”. Clearly, in general, sorting by spam tags is most +effective when you can coerce your filter to give you a raw number. But +in case you can't, mutt can still do something useful. +

+The nospam command can be used to write exceptions to spam +patterns. If a header pattern matches something in a spam command, +but you nonetheless do not want it to receive a spam tag, you can list a +more precise pattern under a nospam command. +

+If the pattern given to nospam is exactly the same as the +pattern on an existing spam list entry, the effect will be to +remove the entry from the spam list, instead of adding an exception. +Likewise, if the pattern for a spam command matches an entry +on the nospam list, that nospam entry will be removed. If the +pattern for nospam is “*”, all entries on both lists +will be removed. This might be the default action if you use spam +and nospam in conjunction with a folder-hook. +

+You can have as many spam or nospam commands as you like. +You can even do your own primitive spam detection within mutt -- for +example, if you consider all mail from MAILER-DAEMON to be spam, +you can use a spam command like this: +

+spam "^From: .*MAILER-DAEMON"       "999"
+

26. Setting and Querying Variables

26.1. Commands

+The following commands are available to manipulate and query variables: +

Usage:

set { +[ no | inv ] +variable + | +variable=value + } [...]

toggle +variable + [ +variable +...]

unset +variable + [ +variable +...]

reset +variable + [ +variable +...]

+This command is used to set (and unset) configuration variables. There are four basic types of variables: +boolean, number, string and quadoption. boolean variables can be +set (true) or unset (false). number variables can be +assigned a positive integer value. +string variables consist of any number of printable characters and +must be enclosed in quotes if they contain spaces or tabs. You +may also use the escape sequences “\n” and “\t” for newline and tab, respectively. +quadoption variables are used to control whether or not to be prompted +for certain actions, or to specify a default action. A value of yes +will cause the action to be carried out automatically as if you had answered +yes to the question. Similarly, a value of no will cause the +action to be carried out as if you had answered “no.” A value of +ask-yes will cause a prompt with a default answer of “yes” and +ask-no will provide a default answer of “no.” +

+Prefixing a variable with “no” will unset it. Example: set noaskbcc. +

+For boolean variables, you may optionally prefix the variable name with +inv to toggle the value (on or off). This is useful when writing +macros. Example: set invsmart_wrap. +

+The toggle command automatically prepends the inv prefix to all +specified variables. +

+The unset command automatically prepends the no prefix to all +specified variables. +

+Using the <enter-command> function in the index menu, you can query the +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 and quadoption +variables. +

+The reset command resets all given variables to the compile time +defaults (hopefully mentioned in this manual). If you use the command +set and prefix the variable with “&” this has the same +behavior as the reset command. +

+With the reset command there exists the special variable “all”, +which allows you to reset all variables to their system defaults. +

26.2. User-defined variables

26.2.1. Introduction

+Along with the variables listed in the +Configuration variables section, mutt +supports user-defined variables with names starting +with my_ as in, for +example, my_cfgdir. +

+The set command either creates a +custom my_ variable or changes its +value if it does exist already. The unset and reset +commands remove the variable entirely. +

+Since user-defined variables are expanded in the same way that +environment variables are (except for +the shell-escape command and +backtick expansion), this feature can be used to make configuration +files more readable. +

26.2.2. Examples

+The following example defines and uses the variable my_cfgdir +to abbreviate the calls of the source command: +

Example 3.14. Using user-defined variables for config file readability

+set my_cfgdir = $HOME/mutt/config
+
+source $my_cfgdir/hooks
+source $my_cfgdir/macros
+# more source commands...
+

+A custom variable can also be used in macros to backup the current value +of another variable. In the following example, the value of the +$delete is changed temporarily +while its original value is saved as my_delete. +After the macro has executed all commands, the original value of $delete is restored. +

Example 3.15. Using user-defined variables for backing up other config option values

+macro pager ,x '\
+<enter-command>set my_delete=$delete<enter>\
+<enter-command>set delete=yes<enter>\
+...\
+<enter-command>set delete=$my_delete<enter>'
+

+Since mutt expands such values already when parsing the configuration +file(s), the value of $my_delete in the +last example would be the value of $delete exactly +as it was at that point during parsing the configuration file. If +another statement would change the value for $delete +later in the same or another file, it would have no effect on +$my_delete. However, the expansion can +be deferred to runtime, as shown in the next example, when escaping the +dollar sign. +

Example 3.16. Deferring user-defined variable expansion to runtime

+macro pager <PageDown> "\
+<enter-command> set my_old_pager_stop=\$pager_stop pager_stop<Enter>\
+<next-page>\
+<enter-command> set pager_stop=\$my_old_pager_stop<Enter>\
+<enter-command> unset my_old_pager_stop<Enter>"
+

+Note that there is a space +between <enter-command> and +the set configuration command, preventing mutt from +recording the macro's commands into its history. +

27. Reading initialization commands from another file

Usage:

source +filename +

+This command allows the inclusion of initialization commands +from other files. For example, I place all of my aliases in +˜/.mail_aliases so that I can make my +˜/.muttrc readable and keep my aliases private. +

+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 filename is +considered to be an executable program from which to read input (eg. +source ˜/bin/myscript|). +

28. Configuring features conditionnaly

+Usage: ifdef item command +

+This command allows to test if a feature has been compiled in, before +actually executing the command. Item can be either the name of a +function, variable, or command. Example: +

+

+ifdef imap_keepalive 'source ~/.mutt/imap_setup'
+

+

29. Removing hooks

Usage:

unhook { +* + | +hook-type + }

+This command permits you to flush hooks you have previously defined. +You can either remove all hooks by giving the “*” character as an +argument, or you can remove all hooks of a specific type by saying +something like unhook send-hook. +

30. Format Strings

30.1. Basic usage

+Format strings are a general concept you'll find in several locations +through the mutt configuration, especially in the +$index_format, +$pager_format, +$status_format, +and other “*_format” variables. These can be very straightforward, +and it's quite possible you already know how to use them. +

+The most basic format string element is a percent symbol followed +by another character. For example, %s +represents a message's Subject: header in the $index_format variable. The +“expandos” available are documented with each format variable, but +there are general modifiers available with all formatting expandos, +too. Those are our concern here. +

+Some of the modifiers are borrowed right out of C (though you might +know them from Perl, Python, shell, or another language). These are +the [-]m.n modifiers, as in %-12.12s. As with +such programming languages, these modifiers allow you to specify the +minimum and maximum size of the resulting string, as well as its +justification. If the “-” sign follows the percent, the string will +be left-justified instead of right-justified. If there's a number +immediately following that, it's the minimum amount of space the +formatted string will occupy -- if it's naturally smaller than that, it +will be padded out with spaces. If a decimal point and another number +follow, that's the maximum space allowable -- the string will not be +permitted to exceed that width, no matter its natural size. Each of +these three elements is optional, so that all these are legal format +strings: +%-12s +%4c +%.15F +%-12.15L +

+Mutt adds some other modifiers to format strings. If you use an equals +symbol (=) as a numeric prefix (like the minus +above), it will force the string to be centered within its minimum +space range. For example, %=14y will reserve 14 +characters for the %y expansion -- that's the X-Label: header, in +$index_format. If the expansion +results in a string less than 14 characters, it will be centered in a +14-character space. If the X-Label for a message were "test", that +expansion would look like “ test ”. +

+There are two very little-known modifiers that affect the way that an +expando is replaced. If there is an underline (“_”) character +between any format modifiers (as above) and the expando letter, it will +expands in all lower case. And if you use a colon (“:”), it will +replace all decimal points with underlines. +

30.2. Filters

+Any format string ending in a vertical bar (“|”) will be +expanded and piped through the first word in the string, using spaces +as separator. The string returned will be used for display. +If the returned string ends in %, it will be passed through +the formatter a second time. This allows the filter to generate a +replacement format string including % expandos. +

+All % expandos in a format string are expanded before the script +is called so that: +

Example 3.17. Using external filters in format strings

+set status_format="script.sh '%r %f (%L)'|"
+

+will make mutt expand %r, +%f and %L +before calling the script. The example also shows that arguments can be +quoted: the script will receive the expanded string between the single quotes +as the only argument. +

+A practical example is the mutt_xtitle +script installed in the samples +subdirectory of the mutt documentation: it can be used as filter for +$status_format to set the current +terminal's title, if supported. +

Chapter 4. Advanced Usage

Table of Contents

1. Regular Expressions
2. Patterns: Searching, Limiting and Tagging
2.1. Pattern Modifier
2.2. Simple Patterns
2.3. Complex Patterns
2.4. Searching by Date
3. Using Tags
4. Using Hooks
4.1. Message Matching in Hooks
5. External Address Queries
6. Mailbox Formats
7. Mailbox Shortcuts
8. Handling Mailing Lists
9. Handling multiple folders
10. Editing threads
10.1. Linking threads
10.2. Breaking threads
11. Delivery Status Notification (DSN) Support
12. Start a WWW Browser on URLs

1. Regular Expressions

+All string patterns in Mutt including those in more complex +patterns must be specified +using regular expressions (regexp) in the “POSIX extended” syntax (which +is more or less the syntax used by egrep and GNU awk). For your +convenience, we have included below a brief description of this syntax. +

+The search is case sensitive if the pattern contains at least one upper +case letter, and case insensitive otherwise. +

Note

+Note that “\” +must be quoted if used for a regular expression in an initialization +command: “\\”. +

+A regular expression is a pattern that describes a set of strings. +Regular expressions are constructed analogously to arithmetic +expressions, by using various operators to combine smaller expressions. +

Note

+Note that the regular expression can be enclosed/delimited by either " +or ' which is useful if the regular expression includes a white-space +character. See Syntax of Initialization Files +for more information on " and ' delimiter processing. To match a +literal " or ' you must preface it with \ (backslash). +

+The fundamental building blocks are the regular expressions that match +a single character. Most characters, including all letters and digits, +are regular expressions that match themselves. Any metacharacter with +special meaning may be quoted by preceding it with a backslash. +

+The period “.” matches any single character. The caret “^” and +the dollar sign “$” are metacharacters that respectively match +the empty string at the beginning and end of a line. +

+A list of characters enclosed by “[” and “]” matches any +single character in that list; if the first character of the list +is a caret “^” then it matches any character not in the +list. For example, the regular expression [0123456789] +matches any single digit. A range of ASCII characters may be specified +by giving the first and last characters, separated by a hyphen +“-”. Most metacharacters lose their special meaning inside +lists. To include a literal “]” place it first in the list. +Similarly, to include a literal “^” place it anywhere but first. +Finally, to include a literal hyphen “-” place it last. +

+Certain named classes of characters are predefined. Character classes +consist of “[:”, a keyword denoting the class, and “:]”. +The following classes are defined by the POSIX standard in +Table 4.1, “POSIX regular expression character classes” +

Table 4.1. POSIX regular expression character classes

Character classDescription
[:alnum:]Alphanumeric characters
[:alpha:]Alphabetic characters
[:blank:]Space or tab characters
[:cntrl:]Control characters
[:digit:]Numeric characters
[:graph:]Characters that are both printable and visible. (A space is printable, but not visible, while an “a” is both)
[:lower:]Lower-case alphabetic characters
[:print:]Printable characters (characters that are not control characters)
[:punct:]Punctuation characters (characters that are not letter, digits, control characters, or space characters)
[:space:]Space characters (such as space, tab and formfeed, to name a few)
[:upper:]Upper-case alphabetic characters
[:xdigit:]Characters that are hexadecimal digits

+A character class is only valid in a regular expression inside the +brackets of a character list. +

Note

+Note that the brackets in these +class names are part of the symbolic names, and must be included +in addition to the brackets delimiting the bracket list. For +example, [[:digit:]] is equivalent to +[0-9]. +

+Two additional special sequences can appear in character lists. These +apply to non-ASCII character sets, which can have single symbols (called +collating elements) that are represented with more than one character, +as well as several characters that are equivalent for collating or +sorting purposes: +

Collating Symbols

+A collating symbol is a multi-character collating element enclosed in +“[.” and “.]”. For example, if “ch” is a collating +element, then [[.ch.]] is a regexp that matches +this collating element, while [ch] is a regexp that +matches either “c” or “h”. +

Equivalence Classes

+An equivalence class is a locale-specific name for a list of +characters that are equivalent. The name is enclosed in “[=” +and “=]”. For example, the name “e” might be used to +represent all of “è” “é” and “e”. In this case, +[[=e=]] is a regexp that matches any of +“è”, “é” and “e”. +

+A regular expression matching a single character may be followed by one +of several repetition operators described in Table 4.2, “Regular expression repetition operators”. +

Table 4.2. Regular expression repetition operators

OperatorDescription
?The preceding item is optional and matched at most once
*The preceding item will be matched zero or more times
+The preceding item will be matched one or more times
{n}The preceding item is matched exactly n times
{n,}The preceding item is matched n or more times
{,m}The preceding item is matched at most m times
{n,m}The preceding item is matched at least n times, but no more than m times

+Two regular expressions may be concatenated; the resulting regular +expression matches any string formed by concatenating two substrings +that respectively match the concatenated subexpressions. +

+Two regular expressions may be joined by the infix operator “|”; +the resulting regular expression matches any string matching either +subexpression. +

+Repetition takes precedence over concatenation, which in turn takes +precedence over alternation. A whole subexpression may be enclosed in +parentheses to override these precedence rules. +

Note

+If you compile Mutt with the GNU rx package, the +following operators may also be used in regular expressions as described in Table 4.3, “GNU regular expression extensions”. +

Table 4.3. GNU regular expression extensions

ExpressionDescription
\\yMatches the empty string at either the beginning or the end of a word
\\BMatches the empty string within a word
\\<Matches the empty string at the beginning of a word
\\>Matches the empty string at the end of a word
\\wMatches any word-constituent character (letter, digit, or underscore)
\\WMatches any character that is not word-constituent
\\`Matches the empty string at the beginning of a buffer (string)
\\'Matches the empty string at the end of a buffer

+Please note however that these operators are not defined by POSIX, so +they may or may not be available in stock libraries on various systems. +

2. Patterns: Searching, Limiting and Tagging

+Many of Mutt's commands allow you to specify a pattern to match +(limit, tag-pattern, +delete-pattern, etc.). Table 4.4, “Pattern modifiers” +shows several ways to select messages. +

Table 4.4. Pattern modifiers

Pattern modifierDescription
~Aall messages
~b EXPRmessages which contain EXPR in the message body
=b STRINGmessages which contain STRING in the message body. If IMAP is enabled, searches for STRING on the server, rather than downloading each message and searching it locally.
~B EXPRmessages which contain EXPR in the whole message
~c EXPRmessages carbon-copied to EXPR
%c GROUPmessages carbon-copied to any member of GROUP
~C EXPRmessages either to: or cc: EXPR
%C GROUPmessages either to: or cc: to any member of GROUP
~d [MIN]-[MAX]messages with “date-sent” in a Date range
~Ddeleted messages
~e EXPRmessages which contains EXPR in the “Sender” field
%e GROUPmessages which contain a member of GROUP in the “Sender” field
~Eexpired messages
~Fflagged messages
~f EXPRmessages originating from EXPR
%f GROUPmessages originating from any member of GROUP
~gcryptographically signed messages
~Gcryptographically encrypted messages
~h EXPRmessages which contain EXPR in the message header
~H EXPRmessages with a spam attribute matching EXPR
~i EXPRmessages which match EXPR in the “Message-ID” field
~kmessages which contain PGP key material
~L EXPRmessages either originated or received by EXPR
%L GROUPmessage either originated or received by any member of GROUP
~lmessages addressed to a known mailing list
~m [MIN]-[MAX]messages in the range MIN to MAX *)
~n [MIN]-[MAX]messages with a score in the range MIN to MAX *)
~Nnew messages
~Oold messages
~pmessages addressed to you (consults alternates)
~Pmessages from you (consults alternates)
~Qmessages which have been replied to
~r [MIN]-[MAX]messages with “date-received” in a Date range
~Rread messages
~s EXPRmessages having EXPR in the “Subject” field.
~Ssuperseded messages
~t EXPRmessages addressed to EXPR
~Ttagged messages
~umessages addressed to a subscribed mailing list
~Uunread messages
~vmessages part of a collapsed thread.
~Vcryptographically verified messages
~x EXPRmessages which contain EXPR in the “References” field
~X [MIN]-[MAX]messages with MIN to MAX attachments *)
~y EXPRmessages which contain EXPR in the “X-Label” field
~z [MIN]-[MAX]messages with a size in the range MIN to MAX *)
~=duplicated messages (see $duplicate_threads)
~$unreferenced messages (requires threaded view)
~(PATTERN)messages in threads +containing messages matching PATTERN, e.g. all +threads containing messages from you: ~(~P)

+Where EXPR is a +regular expression. Special attention has to be +made when using regular expressions inside of patterns. Specifically, +Mutt's parser for these patterns will strip one level of backslash (“\”), +which is normally used for quoting. If it is your intention to use a +backslash in the regular expression, you will need to use two backslashes +instead (“\\”). You can force mutt to treat EXPR as a simple string +instead of a regular expression by using = instead of ˜ in the +pattern name. For example, =b *.* will find all messages that contain +the literal string “*.*”. Simple string matches are less powerful than +regular expressions but can be considerably faster. This is especially +true for IMAP folders, because string matches can be performed on the +server instead of by fetching every message. IMAP treats =h specially: +it must be of the form "header: substring" and will not partially +match header names. The substring part may be omitted if you simply +wish to find messages containing a particular header without regard to +its value. +

+*) The forms “<[MAX]”, “>[MIN]”, +“[MIN]-” and “-[MAX]” +are allowed, too. +

2.1. Pattern Modifier

Note

+Note that patterns matching 'lists' of addresses (notably c, C, p, P and t) +match if there is at least one match in the whole list. If you want to +make sure that all elements of that list match, you need to prefix your +pattern with “^”. +This example matches all mails which only has recipients from Germany. +

+^~C \.de$
+

2.2. Simple Patterns

+Mutt supports two versions of so called “simple searches” which are +issued if the query entered for searching, limiting and similar +operations does not seem to be a valid pattern (i.e. it does not contain +one of these characters: “˜”, “=” or “%”). If the query is +supposed to contain one of these special characters, they must be escaped +by prepending a backslash (“\”). +

+The first type is by checking whether the query string equals +a keyword case-insensitively from Table 4.5, “Simple search keywords”: +If that is the case, Mutt will use the shown pattern modifier instead. +If a keyword would conflict with your search keyword, you need to turn +it into a regular expression to avoid matching the keyword table. For +example, if you want to find all messages matching “flag” +(using $simple_search) +but don't want to match flagged messages, simply search for +“[f]lag”. +

Table 4.5. Simple search keywords

KeywordPattern modifier
all~A
.~A
^~A
del~D
flag~F
new~N
old~O
repl~Q
read~R
tag~T
unread~U

+The second type of simple search is to build a complex search +pattern using $simple_search +as a template. Mutt will insert your query properly quoted and search +for the composed complex query. +

2.3. Complex Patterns

+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 and that have the word “elkins” in the “From” header +field. +

+Mutt also recognizes the following operators to create more complex search +patterns: +

  • +! -- logical NOT operator +

  • +| -- logical OR operator +

  • +() -- 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”. +

Example 4.1. Using boolean operators in patterns

+!(~t mutt|~c mutt) ~f elkins
+

+Here is an example using white space in the regular expression (note +the ' and " delimiters). For this to match, the mail's subject must +match the “^Junk +From +Me$” and it must be from either “Jim +Somebody” +or “Ed +SomeoneElse”: +

+ '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
+

Note

+If a regular expression contains parenthesis, or a vertical bar +("|"), you must enclose the expression in double or single quotes since +those characters are also used to separate different parts of Mutt's +pattern language. For example: ~f "me@(mutt\.org|cs\.hmc\.edu)" +

+Without the quotes, the parenthesis wouldn't end. +This would be separated to two OR'd patterns: ˜f me@(mutt\.org +and cs\.hmc\.edu). They are never what you want. +

2.4. Searching by Date

+Mutt supports two types of dates, absolute and relative. +

+Absolute. Dates must be in DD/MM/YY format (month and year are +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 before the given date will be selected. If you omit the maximum +(second) date, and specify “DD/MM/YY-”, all messages after the given +date will be selected. If you specify a single date with no dash (“-”), +only messages sent on the given date will be selected. +

+Error Margins. You can add error margins to absolute dates. +An error margin is a sign (+ or -), followed by a digit, followed by +one of the units in Table 4.6, “Date units”. As a special case, you can replace the +sign by a “*” character, which is equivalent to giving identical plus and minus error margins. +

Table 4.6. Date units

UnitDescription
yYears
mMonths
wWeeks
dDays

+Example: To select any messages two weeks around January 15, 2001, +you'd use the following pattern: +

+Limit to messages matching: ~d 15/1/2001*2w
+

+Relative. This type of date is relative to the current date, and may +be specified as: +

  • +>offset (messages older than offset units) +

  • +<offset (messages newer than offset units) +

  • +=offset (messages exactly offset units old) +

+offset is specified as a positive number with one of the units from Table 4.6, “Date units”. +

+Example: to select messages less than 1 month old, you would use +

+Limit to messages matching: ~d <1m
+

Note

+All dates used when searching are relative to the +local time zone, so unless you change the setting of your $index_format to include a +%[...] format, these are not the dates shown +in the main index. +

3. Using Tags

+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 all messages with a given subject. To tag all messages +matching a pattern, use the <tag-pattern> function, which is bound to +“shift-T” by default. Or you can select individual messages by +hand using the <tag-message> function, which is bound to “t” by +default. See patterns for Mutt's pattern +matching syntax. +

+Once you have tagged the desired messages, you can use the +“tag-prefix” operator, which is the “;” (semicolon) key by default. +When the “tag-prefix” operator is used, the next operation will +be applied to all tagged messages if that operation can be used in that +manner. If the $auto_tag +variable is set, the next operation applies to the tagged messages +automatically, without requiring the “tag-prefix”. +

+In macros or push commands, +you can use the “tag-prefix-cond” operator. If there are no tagged +messages, mutt will "eat" the rest of the macro to abort it's execution. +Mutt will stop "eating" the macro when it encounters the “end-cond” +operator; after this operator the rest of the macro will be executed as +normal. +

4. Using Hooks

+A hook is a concept found in many other programs which allows you to +execute arbitrary commands before performing some operation. For example, +you may wish to tailor your configuration based upon which mailbox you are +reading, or to whom you are sending mail. In the Mutt world, a hook +consists of a regular expression or +pattern along with a +configuration option/command. See + +

+ +for specific details on each type of hook available. +

Note

+If a hook changes configuration settings, these changes remain +effective until the end of the current mutt session. As this is generally +not desired, a default hook needs to be added before all other hooks to +restore configuration defaults. Here is an example with send-hook and the +my_hdr directive: +

Example 4.2. Combining send-hook and my_hdr

+send-hook . 'unmy_hdr From:'
+send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
+

4.1. Message Matching in Hooks

+Hooks that act upon messages (message-hook, reply-hook, +send-hook, send2-hook, save-hook, fcc-hook) are evaluated in a +slightly different manner. For the other +types of hooks, a regular expression is +sufficient. But in dealing with messages a finer grain of control is +needed for matching since for different purposes you want to match +different criteria. +

+Mutt allows the use of the search pattern +language for matching messages in hook commands. This works in +exactly the same way as it would when limiting or +searching the mailbox, except that you are restricted to those +operators which match information mutt extracts from the header of +the message (i.e., from, to, cc, date, subject, etc.). +

+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 <user@host>'
+

+which would execute the given command when sending mail to +me@cs.hmc.edu. +

+However, it is not required that you write the pattern to match using the +full searching language. You can still specify a simple regular +expression like the other hooks, in which case Mutt will translate your +pattern into the full language, using the translation specified by the +$default_hook variable. The +pattern is translated at the time the hook is declared, so the value of +$default_hook that is in effect +at that time will be used. +

5. External Address Queries

+Mutt supports connecting to external directory databases such as LDAP, +ph/qi, bbdb, or NIS through a wrapper script which connects to mutt +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, then each matching response on a +single line, each line containing a tab separated address then name then +some other optional information. On error, or if there are no matching +addresses, return a non-zero exit code and a one line error message. +

+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@does-not-exist.org        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 menu which will +list the matching responses. From the query menu, you can select +addresses to create aliases, or to mail. You can tag multiple addresses +to mail, start a new query, or have a new query appended to the current +responses. +

+The other mechanism for accessing the query function is for address +completion, similar to the alias completion. In any prompt for address +entry, you can use the <complete-query> function (default: ^T) to run a +query based on the current address you have typed. Like aliases, mutt +will look for what you have typed back to the last space or comma. If +there is a single response for that query, mutt will expand the address +in place. If there are multiple responses, mutt will activate the query +menu. At the query menu, you can select one or more addresses to be +added to the prompt. +

6. Mailbox Formats

+Mutt supports reading and writing of four different mailbox formats: +mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there +is no need to use a flag for different mailbox types. When creating new +mailboxes, Mutt uses the default specified with the $mbox_type variable. +

+mbox. This is the most widely used mailbox format for UNIX. All +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). +

+MMDF. This is a variant of the mbox format. Each message is +surrounded by lines containing “^A^A^A^A” (four control-A's). +

+MH. A radical departure from mbox and MMDF, a mailbox +consists of a directory and each message is stored in a separate file. +The filename indicates the message number (however, this is may not +correspond to the message number Mutt displays). Deleted messages are +renamed with a comma (,) prepended to the filename. Mutt +detects this type of mailbox by looking for either .mh_sequences +or .xmhcache (needed to distinguish normal directories from MH +mailboxes). +

+Maildir. The newest of the mailbox formats, used by the Qmail MTA (a +replacement for sendmail). Similar to MH, except that it adds three +subdirectories of the mailbox: tmp, new and cur. Filenames +for the messages are chosen in such a way they are unique, even when two +programs are writing the mailbox over NFS, which means that no file locking +is needed. +

7. Mailbox Shortcuts

+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. +

  • +! -- refers to your $spoolfile (incoming) mailbox +

  • +> -- refers to your $mbox file +

  • +< -- refers to your $record file +

  • +^ -- refers to the current mailbox +

  • +- or !! -- refers to the file you've last visited +

  • +˜ -- refers to your home directory +

  • += or + -- refers to your $folder directory +

  • +@alias -- refers to the default save folder as determined by the address of the alias +

8. Handling Mailing Lists

+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 does not have to be a mailing list, but that is what it is most +often used for), and what lists you are subscribed to. This is +accomplished through the use of the lists and subscribe commands in your muttrc. +

+Now that Mutt knows what your mailing lists are, it can do several +things, the first of which is the ability to show the name of a list +through which you received a message (i.e., of a subscribed list) in +the index menu display. This is useful to distinguish between +personal and list mail in the same mailbox. In the $index_format variable, the escape “%L” +will return the string “To <list>” when “list” appears in the +“To” field, and “Cc <list>” 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 the message they reply to from the list, resulting in +two or more copies being sent to that person. The <list-reply> +function, which by default is bound to “L” in the index menu +and pager, helps reduce the clutter by only replying to the +known mailing list addresses instead of all recipients (except as +specified by Mail-Followup-To, see below). +

+Mutt also supports the Mail-Followup-To header. When you send +a message to a list of recipients which includes one or several +subscribed mailing lists, and if the $followup_to option is set, mutt will generate +a Mail-Followup-To header which contains all the recipients to whom +you send this message, but not your address. This indicates that +group-replies or list-replies (also known as “followups”) to this +message should only be sent to the original recipients of the +message, and not separately to you - you'll receive your copy through +one of the mailing lists you are subscribed to. +

+Conversely, when group-replying or list-replying to a message which +has a Mail-Followup-To header, mutt will respect this header if +the $honor_followup_to configuration +variable is set. Using list-reply will in this case also make sure +that the reply goes to the mailing list, even if it's not specified +in the list of recipients in the Mail-Followup-To. +

Note

+When header editing is enabled, you can create a +Mail-Followup-To header manually. Mutt will only auto-generate +this header if it doesn't exist when you send the message. +

+The other method some mailing list admins use is to generate a +“Reply-To” field which points back to the mailing list address rather +than the author of the message. This can create problems when trying +to reply directly to the author in private, since most mail clients +will automatically reply to the address given in the “Reply-To” +field. Mutt uses the $reply_to +variable to help decide which address to use. If set to ask-yes or +ask-no, you will be +prompted as to whether or not you would like to use the address given in +the “Reply-To” field, or reply directly to the address given in the +“From” field. When set to yes, the “Reply-To” field will be used when +present. +

+The “X-Label:” header field can be used to further identify mailing +lists or list subject matter (or just to annotate messages +individually). The $index_format variable's “%y” and +“%Y” escapes can be used to expand “X-Label:” fields in the +index, and Mutt's pattern-matcher can match regular expressions to +“X-Label:” fields with the “˜y” selector. “X-Label:” is not a +standard message header field, but it can easily be inserted by procmail +and other mail filtering agents. +

+Lastly, Mutt has the ability to sort the mailbox into +threads. A thread is a group of messages which all relate to the same +subject. This is usually organized into a tree-like structure where a +message and all of its replies are represented graphically. If you've ever +used a threaded news client, this is the same concept. It makes dealing +with large volume mailing lists easier because you can easily delete +uninteresting threads and quickly find topics of value. +

9. Handling multiple folders

+Mutt supports setups with multiple folders, allowing all of them to +be monitored for new mail (see Section 14, “Monitoring incoming mail” for details). +

+When in the index menu and being idle (also see +$timeout), Mutt periodically checks +for new mail in all folders which have been configured via the +mailboxes command. The interval depends on the folder +type: for local/IMAP folders it consults +$mail_check and +$pop_checkinterval +for POP folders. +

+Outside the index menu the directory browser supports checking +for new mail using the <check-new> function which is +unbound by default. Pressing TAB will bring up a +menu showing the files specified by the mailboxes command, +and indicate which contain new messages. Mutt will automatically enter this +mode when invoked from the command line with the -y option. +

+For the pager, index and directory browser menus, Mutt contains the +<buffy-list> function (bound to “.” by default) +which will print a list of folders with new mail in the command line at +the bottom of the screen. +

+For the index, by default Mutt displays the number of mailboxes with new +mail in the status bar, please refer to the +$index_format +variable for details. +

+When changing folders, Mutt fills the prompt with the first folder from +the mailboxes list containing new mail (if any), pressing +space will cycle through folders with new mail. +

10. Editing threads

+Mutt has the ability to dynamically restructure threads that are broken +either by misconfigured software or bad behavior from some +correspondents. This allows to clean your mailboxes formats) from these +annoyances which make it hard to follow a discussion. +

10.1. Linking threads

+Some mailers tend to "forget" to correctly set the "In-Reply-To:" and +"References:" headers when replying to a message. This results in broken +discussions because Mutt has not enough information to guess the correct +threading. +You can fix this by tagging the reply, then moving to the parent message +and using the <link-threads> function (bound to & by default). The +reply will then be connected to this "parent" message. +

+You can also connect multiple children at once, tagging them and using the +tag-prefix command (';') or the auto_tag option. +

10.2. Breaking threads

+On mailing lists, some people are in the bad habit of starting a new +discussion by hitting "reply" to any message from the list and changing +the subject to a totally unrelated one. +You can fix such threads by using the <break-thread> function (bound +by default to #), which will turn the subthread starting from the +current message into a whole different thread. +

11. Delivery Status Notification (DSN) Support

+RFC1894 defines a set of MIME content types for relaying information +about the status of electronic mail messages. These can be thought of as +“return receipts.” +

+To support DSN, there are two variables. $dsn_notify is used to request receipts for +different results (such as failed message, message delivered, etc.). +$dsn_return requests how much +of your message should be returned with the receipt (headers or full +message). +

+When using $sendmail for mail +delivery, you need to use either Berkeley sendmail 8.8.x (or greater) a MTA +supporting DSN command line options compatible to Sendmail: The -N and -R +options can be used by the mail client to make requests as to what type of +status messages should be returned. Please consider your MTA documentation +whether DSN is supported. +

+For SMTP delivery using $smtp_url, it depends on the +capabilities announced by the server whether mutt will attempt to +request DSN or not. +

12. Start a WWW Browser on URLs

+If a message contains URLs, it is efficient to get +a menu with all the URLs and start a WWW browser on one of them. This +functionality is provided by the external urlview program which can be +retrieved at +ftp://ftp.mutt.org/mutt/contrib/ +and the configuration commands: +

+macro index \cb |urlview\n
+macro pager \cb |urlview\n
+

1. Compressed folders Support (OPTIONAL)

+If Mutt was compiled with compressed folders support (by running the +configure script with the +--enable-compressed flag), Mutt can open folders +stored in an arbitrary format, provided that the user has a script to +convert from/to this format to one of the accepted. + +The most common use is to open compressed archived folders e.g. with +gzip. + +In addition, the user can provide a script that gets a folder in an +accepted format and appends its context to the folder in the +user-defined format, which may be faster than converting the entire +folder to the accepted format, appending to it and converting back to +the user-defined format. + +There are three hooks defined (open-hook, close-hook and append-hook) which define commands to +uncompress and compress a folder and to append messages to an existing +compressed folder respectively. + +For example: + +

+open-hook \\.gz$ "gzip -cd %f > %t" 
+close-hook \\.gz$ "gzip -c %t > %f"
+append-hook \\.gz$ "gzip -c %t >> %f" 
+

+ +You do not have to specify all of the commands. If you omit append-hook, the folder will be open and +closed again each time you will add to it. If you omit close-hook (or give empty command) , the +folder will be open in the mode. If you specify append-hook though you'll be able to +append to the folder. + +Note that Mutt will only try to use hooks if the file is not in one of +the accepted formats. In particular, if the file is empty, mutt +supposes it is not compressed. This is important because it allows the +use of programs that do not have well defined extensions. Just use +"." as a regexp. But this may be surprising if your +compressing script produces empty files. In this situation, unset +$save_empty, so that +the compressed file will be removed if you delete all of the messages. +

1.1. Open a compressed mailbox for reading

+Usage: open-hook regexp "command" + +The command is the command that can be used for +opening the folders whose names match regexp. + +The command string is the printf-like format +string, and it should accept two parameters: %f, which is +replaced with the (compressed) folder name, and %t which is +replaced with the name of the temporary folder to which to write. + +%f and %t can be repeated any number of times in the +command string, and all of the entries are replaced with the +appropriate folder name. In addition, %% is replaced by +%, as in printf, and any other %anything is left as is. + +The command should not remove the original compressed file. The +command should return non-zero exit status if it +fails, so mutt knows something's wrong. + +Example: + +

+open-hook \\.gz$ "gzip -cd %f > %t" 
+

+ +If the command is empty, this operation is +disabled for this file type. +

1.2. Write a compressed mailbox

+Usage: close-hook regexp "command" + +This is used to close the folder that was open with the open-hook command after some changes were +made to it. + +The command string is the command that can be +used for closing the folders whose names match +regexp. It has the same format as in the open-hook command. Temporary folder in this +case is the folder previously produced by the open-hook command. + +The command should not remove the decompressed file. The +command should return non-zero exit status if it +fails, so mutt knows something's wrong. + +Example: + +

+close-hook \\.gz$ "gzip -c %t > %f"
+

+ +If the command is empty, this operation is +disabled for this file type, and the file can only be open in the +read-only mode. + +close-hook is not called when you +exit from the folder if the folder was not changed. +

1.3. Append a message to a compressed mailbox

+Usage: append-hook regexp "command" + +This command is used for saving to an existing compressed folder. The +command is the command that can be used for +appending to the folders whose names match +regexp. It has the same format as in the open-hook command. The temporary folder in +this case contains the messages that are being appended. + +The command should not remove the decompressed file. The +command should return non-zero exit status if it +fails, so mutt knows something's wrong. + +Example: + +

+append-hook \\.gz$ "gzip -c %t >> %f" 
+

+ +When append-hook is used, the folder +is not opened, which saves time, but this means that we can not find +out what the folder type is. Thus the default ($mbox_type) type is always +supposed (i.e. this is the format used for the temporary folder). + +If the file does not exist when you save to it, close-hook is called, and not append-hook. append-hook is only for appending to +existing folders. + +If the command is empty, this operation is +disabled for this file type. In this case, the folder will be open and +closed again (using open-hook and +close-hookrespectively) each time you +will add to it. +

1.4. Encrypted folders

+The compressed folders support can also be used to handle encrypted +folders. If you want to encrypt a folder with PGP, you may want to use +the following hooks: + +

+open-hook  \\.pgp$ "pgp -f < %f > %t"
+close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
+

+ +Please note, that PGP does not support appending to an encrypted +folder, so there is no append-hook defined. + +If you are using GnuPG instead of PGP, you may use the following hooks +instead: + +

+open-hook  \\.gpg$ "gpg --decrypt < %f > %t"
+close-hook \\.gpg$ "gpg --encrypt --recipient YourGpgUserIdOrKeyId < %t > %f"
+

+ +Note: the folder is temporary stored +decrypted in the /tmp directory, where it can be read by your system +administrator. So think about the security aspects of this. +

Chapter 5. Mutt's MIME Support

Table of Contents

1. Using MIME in Mutt
1.1. Viewing MIME messages in the pager
1.2. The Attachment Menu
1.3. The Compose Menu
2. MIME Type configuration with mime.types
3. MIME Viewer configuration with mailcap
3.1. The Basics of the mailcap file
3.2. Secure use of mailcap
3.3. Advanced mailcap Usage
3.4. Example mailcap files
4. MIME Autoview
5. MIME Multipart/Alternative
6. Attachment Searching and Counting
7. MIME Lookup

+Quite a bit of effort has been made to make Mutt the premier text-mode +MIME MUA. Every effort has been made to provide the functionality that +the discerning MIME user requires, and the conformance to the standards +wherever possible. When configuring Mutt for MIME, there are two extra +types of configuration files which Mutt uses. One is the +mime.types file, which contains the mapping of file extensions to +IANA MIME types. The other is the mailcap file, which specifies +the external commands to use for handling specific MIME types. +

1. Using MIME in Mutt

+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. +

1.1. Viewing MIME messages in the pager

+When you select a message from the index and view it in the pager, Mutt +decodes the message to a text representation. Mutt internally supports +a number of MIME types, including text/plain, text/enriched, +message/rfc822, and message/news. In addition, the export +controlled version of Mutt recognizes a variety of PGP MIME types, +including PGP/MIME and application/pgp. +

+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-printable/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) --]
+

1.2. The Attachment Menu

+The default binding for view-attachments is `v', which displays the +attachment menu for a message. The attachment menu displays a list of +the attachments in a message. From the attachment menu, you can save, +print, pipe, delete, and view attachments. You can apply these +operations to a group of attachments at once, by tagging the attachments +and by using the “tag-prefix” operator. You can also reply to the +current message from this menu, and only the current attachment (or the +attachments tagged) will be quoted in your reply. You can view +attachments as text, or view them using the mailcap viewer definition. +

+Finally, you can apply the usual message-related functions (like +<resend-message>, and the +<reply> and <forward> +functions) to attachments of type message/rfc822. +

+See the help on the attachment menu for more information. +

1.3. The Compose Menu

+The compose menu is the menu you see before you send a message. It +allows you to edit the recipient list, the subject, and other aspects +of your message. It also contains a list of the attachments of your +message, including the main body. From this menu, you can print, copy, +filter, pipe, edit, compose, review, and rename an attachment or a +list of tagged attachments. You can also modifying the attachment +information, notably the type, encoding and description. +

+Attachments appear as follows: +

+- 1 [text/plain, 7bit, 1K]           /tmp/mutt-euler-8082-0 <no description>
+  2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
+

+The '-' denotes that Mutt will delete the file after sending (or +postponing, or canceling) 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 the edit-type command +(default: ^T). The next field is the encoding for the attachment, +which allows a binary message to be encoded for transmission on 7bit +links. It can be changed with the edit-encoding command +(default: ^E). The next field is the size of the attachment, +rounded to kilobytes or megabytes. The next field is the filename, +which can be changed with the rename-file command (default: R). +The final field is the description of the attachment, and can be +changed with the edit-description command (default: d). +

2. MIME Type configuration with mime.types

+When you add an attachment to your mail message, Mutt searches your +personal mime.types file at ${HOME}/.mime.types, and then +the system mime.types file at /usr/local/share/mutt/mime.types or +/etc/mime.types +

+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 +as text/plain. If the file contains binary information, then Mutt will +mark it as application/octet-stream. You can change the MIME +type that Mutt assigns to an attachment by using the edit-type +command from the compose menu (default: ^T). The MIME type is actually a +major mime type followed by the sub-type, separated by a '/'. 6 major +types: application, text, image, video, audio, and model have been approved +after various internet discussions. Mutt recognizes all of these if the +appropriate entry is found in the mime.types file. It also recognizes other +major mime types, such as the chemical type that is widely used in the +molecular modeling community to pass molecular data in various forms to +various molecular viewers. Non-recognized mime types should only be used +if the recipient of the message is likely to be expecting such attachments. +

3. MIME Viewer configuration with mailcap

+Mutt supports RFC 1524 MIME Configuration, in particular the Unix +specific format specified in Appendix A of RFC 1524. This file format +is commonly referred to as the mailcap format. Many MIME compliant +programs utilize the mailcap format, allowing you to specify handling +for all MIME types in one place for all programs. Programs known to +use this format include Netscape, XMosaic, lynx and metamail. +

+In order to handle various MIME types that Mutt can not handle +internally, Mutt parses a series of external configuration files to +find an external handler. The default search string for these files +is a colon delimited list containing the following files: +

  1. $HOME/.mailcap

  2. $PKGDATADIR/mailcap

  3. $SYSCONFDIR/mailcap

  4. /etc/mailcap

  5. /usr/etc/mailcap

  6. /usr/local/etc/mailcap

+where $HOME is your home directory. The +$PKGDATADIR and the +$SYSCONFDIR directories depend on where mutt +is installed: the former is the default for shared data, the +latter for system configuration files. +

+The default search path can be obtained by running the following +command: +

+mutt -nF /dev/null -Q mailcap_path
+

+In particular, the metamail distribution will install a mailcap file, +usually as /usr/local/etc/mailcap, which contains some baseline +entries. +

3.1. The Basics of the mailcap file

+A mailcap file consists of a series of lines which are comments, blank, +or definitions. +

+A comment line consists of a # character followed by anything you want. +

+A blank line is blank. +

+A definition line consists of a content type, a view command, and any +number of optional fields. Each field of a definition line is divided +by a semicolon ';' character. +

+The content type is specified in the MIME standard type/subtype method. +For example, +text/plain, text/html, image/gif, +etc. In addition, the mailcap format includes two formats for +wildcards, one using the special '*' subtype, the other is the implicit +wild, where you only include the major type. For example, image/*, or +video, will match all image types and video types, +respectively. +

+The view command is a Unix command for viewing the type specified. There +are two different types of commands supported. The default is to send +the body of the MIME message to the command on stdin. You can change +this behavior by using %s as a parameter to your view command. +This will cause Mutt to save the body of the MIME message to a temporary +file, and then call the view command with the %s replaced by +the name of the temporary file. In both cases, Mutt will turn over the +terminal to the view program until the program quits, at which time Mutt +will remove the temporary file if it exists. +

+So, in the simplest form, you can send a text/plain message to the +external pager more on stdin: +

+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. +

Note

+Some older versions of lynx contain a bug where they +will check the mailcap file for a viewer for text/html. They will find +the line which calls lynx, and run it. This causes lynx to continuously +spawn itself to view the object. +

+On the other hand, maybe you don't want to use lynx interactively, you +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. +

3.2. Secure use of mailcap

+The interpretation of shell meta-characters embedded in MIME parameters +can lead to security problems in general. Mutt tries to quote parameters +in expansion of %s syntaxes properly, and avoids risky characters by +substituting them, see the $mailcap_sanitize variable. +

+Although mutt's procedures to invoke programs with mailcap seem to be +safe, there are other applications parsing mailcap, maybe taking less care +of it. Therefore you should pay attention to the following rules: +

+Keep the %-expandos away from shell quoting. +Don't quote them with single or double quotes. Mutt does this for +you, the right way, as should any other program which interprets +mailcap. Don't put them into backtick expansions. Be highly careful +with eval statements, and avoid them if possible at all. Trying to fix +broken behavior with quotes introduces new leaks - there is no +alternative to correct quoting in the first place. +

+If you have to use the %-expandos' values in context where you need +quoting or backtick expansions, put that value into a shell variable +and reference the shell variable where necessary, as in the following +example (using $charset inside the backtick expansion is safe, +since it is not itself subject to any further expansion): +

+text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
+        && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
+

3.3. Advanced mailcap Usage

3.3.1. Optional Fields

+In addition to the required content-type and view command fields, you +can add semi-colon ';' separated fields to set flags and other options. +Mutt recognizes the following optional fields: +

copiousoutput

+This flag tells Mutt that the command passes possibly large amounts of +text on stdout. This causes Mutt to invoke a pager (either the internal +pager or the external pager defined by the pager variable) on the output +of the view command. Without this flag, Mutt assumes that the command +is interactive. One could 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. +

needsterminal

+Mutt uses this flag when viewing attachments with auto_view, in order to decide whether it should honor the setting +of the $wait_key variable or +not. When an attachment is viewed using an interactive program, and the +corresponding mailcap entry has a needsterminal flag, Mutt will use +$wait_key and the exit status +of the program to decide if it will ask you to press a key after the +external program has exited. In all other situations it will not prompt +you for a key. +

compose=<command>

+This flag specifies the command to use to create a new attachment of a +specific MIME type. Mutt supports this from the compose menu. +

composetyped=<command>

+This flag specifies the command to use to create a new attachment of a +specific MIME type. This command differs from the compose command in +that mutt will expect standard MIME headers on the data. This can be +used to specify parameters, filename, description, etc. for a new +attachment. Mutt supports this from the compose menu. +

print=<command>

+This flag specifies the command to use to print a specific MIME type. +Mutt supports this from the attachment and compose menus. +

edit=<command>

+This flag specifies the command to use to edit a specific MIME type. +Mutt supports this from the compose menu, and also uses it to compose +new attachments. Mutt will default to the defined editor for text +attachments. +

nametemplate=<template>

+This field specifies the format for the file denoted by %s in the +command fields. Certain programs will require a certain file extension, +for instance, to correctly view a file. For instance, lynx will only +interpret a file as text/html if the 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
+
test=<command>

+This field specifies a command to run to test whether this mailcap +entry should be used. The command is defined with the command expansion +rules defined in the next section. If the command returns 0, then the +test passed, and Mutt uses this entry. If the command returns non-zero, +then the test failed, and Mutt continues searching for the right entry. +Note that the content-type must match before Mutt performs the test. +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 display the +text/html object. If RunningX doesn't return 0, then Mutt will go on +to the next entry and use lynx to display the text/html object. +

3.3.2. Search Order

+When searching for an entry in the mailcap file, Mutt will search for +the most useful entry for its purpose. For instance, if you are +attempting to print an image/gif, and you have the following +entries 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. +

+In addition, you can use this with auto_view +to denote two commands for viewing an attachment, one to be viewed +automatically, the other to be viewed interactively from the attachment +menu. In addition, you 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 auto_view, 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 program returns non-zero, Mutt will use the second entry +for interactive viewing. +

3.3.3. Command Expansion

+The various commands defined in the mailcap files are passed to the +/bin/sh shell using the system() function. Before the +command is passed to /bin/sh -c, it is parsed to expand +various special parameters with information from Mutt. The keywords +Mutt expands are: +

%s

+As seen in the basic mailcap section, this variable is expanded +to a filename specified by the calling program. This file contains +the body of the message to view/print/edit or where the composing +program should place the results of composition. In addition, the +use of this keyword causes Mutt to not pass the body of the message +to the view/print/edit program on stdin. +

%t

+Mutt will expand %t to the text representation of the content +type of the message in the same form as the first parameter of the +mailcap definition line, ie text/html or +image/gif. +

%{<parameter>}

+Mutt will expand this to the value of the specified parameter +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 metamail +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 % +

+Mutt does not currently support the %F and %n keywords +specified in RFC 1524. The main purpose of these parameters is for +multipart messages, which is handled internally by Mutt. +

3.4. Example mailcap files

+This mailcap file is fairly simple and standard: +

+# I'm always running X :)
+video/*;        xanim %s > /dev/null
+image/*;        xv %s > /dev/null
+
+# I'm always running netscape (if my computer had more memory, maybe)
+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
+video/*;        xanim %s > /dev/null
+
+# Send html to a running netscape by remote
+text/html;      netscape -remote 'openURL(%s)'; test=RunningNetscape
+
+# If I'm not running netscape but I am running X, start netscape on the
+# object
+text/html;      netscape %s; test=RunningX
+
+# Else use lynx to view it as text
+text/html;      lynx %s
+
+# This version would convert the text/html to text/plain
+text/html;      lynx -dump %s; copiousoutput
+
+# I use enscript to print text in two columns to a page
+text/*;         more %s; print=enscript -2Gr %s
+
+# Netscape adds a flag to tell itself to view jpegs internally
+image/jpeg;xv %s; x-mozilla-flags=internal
+
+# Use xv to view images if I'm running X
+# In addition, this uses the \ to extend the line and set my editor
+# for images
+image/*;xv %s; test=RunningX; \
+        edit=xpaint %s
+
+# Convert images to text using the netpbm tools
+image/*;  (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
+pbmtoascii -1x2 ) 2>&1 ; copiousoutput
+
+# Send excel spreadsheets to my NT box
+application/ms-excel; open.pl %s
+

4. MIME Autoview

+In addition to explicitly telling Mutt to view an attachment with the +MIME viewer defined in the mailcap file, Mutt has support for +automatically viewing MIME attachments while in the pager. +

+To work, you must define a viewer in the mailcap file which uses the +copiousoutput option to denote that it is non-interactive. +Usually, you also use the entry to convert the attachment to a text +representation which you can view in the pager. +

+You then use the auto_view muttrc command to list the +content-types that you wish to view automatically. +

+For instance, if you set auto_view to: +

+auto_view text/html 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
+image/*;        anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | \
+                pgmtopbm | pbmtoascii ; copiousoutput
+application/x-gunzip;   gzcat; copiousoutput
+application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
+application/postscript; ps2ascii %s; copiousoutput
+

+“unauto_view” can be used to remove previous entries from the autoview list. +This can be used with message-hook to autoview messages based on size, etc. +“unauto_view *” will remove all previous entries. +

5. MIME Multipart/Alternative

+Mutt has some heuristics for determining which attachment of a +multipart/alternative type to display. First, mutt will check the +alternative_order list to determine if one of the available types +is preferred. The alternative_order list consists of a number of +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. +

+To remove a MIME type from the alternative_order list, use the +unalternative_order command. +

6. Attachment Searching and Counting

+If you ever lose track of attachments in your mailboxes, Mutt's +attachment-counting and -searching support might be for you. You can +make your message index display the number of qualifying attachments in +each message, or search for messages by attachment count. You also can +configure what kinds of attachments qualify for this feature with the +attachments and unattachments commands. +

+In order to provide this information, mutt needs to fully MIME-parse +all messages affected first. This can slow down operation especially for +remote mail folders such as IMAP because all messages have to be +downloaded first regardless whether the user really wants to view them +or not. +

+The syntax is: +

+attachments   {+|-}disposition mime-type
+unattachments {+|-}disposition mime-type
+attachments   ?
+

+Disposition is the attachment's Content-disposition type -- either +inline or attachment. +You can abbreviate this to I or A. +

+Disposition is prefixed by either a + symbol or a - symbol. If it's +a +, you're saying that you want to allow this disposition and MIME +type to qualify. If it's a -, you're saying that this disposition +and MIME type is an exception to previous + rules. There are examples +below of how this is useful. +

+Mime-type is, unsurprisingly, the MIME type of the attachment you want +to affect. A MIME type is always of the format major/minor, where +major describes the broad category of document you're looking at, and +minor describes the specific type within that category. The major +part of mime-type must be literal text (or the special token “*”), but +the minor part may be a regular expression. (Therefore, “*/.*” matches +any MIME type.) +

+The MIME types you give to the attachments directive are a kind of +pattern. When you use the attachments directive, the patterns you +specify are added to a list. When you use unattachments, the pattern +is removed from the list. The patterns are not expanded and matched +to specific MIME types at this time -- they're just text in a list. +They're only matched when actually evaluating a message. +

+Some examples might help to illustrate. The examples that are not +commented out define the default configuration of the lists. +

Example 5.1. Attachment counting

+## Removing a pattern from a list removes that pattern literally. It
+## does not remove any type matching the pattern.
+##
+##  attachments   +A */.*
+##  attachments   +A image/jpeg
+##  unattachments +A */.*
+##
+## This leaves "attached" image/jpeg files on the allowed attachments
+## list. It does not remove all items, as you might expect, because the
+## second */.* is not a matching expression at this time.
+##
+## Remember: "unattachments" only undoes what "attachments" has done!
+## It does not trigger any matching on actual messages.
+
+
+## Qualify any MIME part with an "attachment" disposition, EXCEPT for
+## text/x-vcard and application/pgp parts. (PGP parts are already known
+## to mutt, and can be searched for with ~g, ~G, and ~k.)
+##
+## I've added x-pkcs7 to this, since it functions (for S/MIME)
+## analogously to PGP signature attachments. S/MIME isn't supported
+## in a stock mutt build, but we can still treat it specially here.
+##
+attachments   +A */.*
+attachments   -A text/x-vcard application/pgp.*
+attachments   -A application/x-pkcs7-.*
+
+## Discount all MIME parts with an "inline" disposition, unless they're
+## text/plain. (Why inline a text/plain part unless it's external to the
+## message flow?)
+##
+attachments   +I text/plain
+
+## These two lines make Mutt qualify MIME containers.  (So, for example,
+## a message/rfc822 forward will count as an attachment.)  The first
+## line is unnecessary if you already have "attach-allow */.*", of
+## course.  These are off by default!  The MIME elements contained
+## within a message/* or multipart/* are still examined, even if the
+## containers themseves don't qualify.
+##
+#attachments  +A message/.* multipart/.*
+#attachments  +I message/.* multipart/.*
+
+## You probably don't really care to know about deleted attachments.
+attachments   -A message/external-body
+attachments   -I message/external-body
+

+Entering the command “attachments ?” +as a command will list your current settings in Muttrc format, so that +it can be pasted elsewhere. +

7. MIME Lookup

+Mutt's mime_lookup list specifies a list of mime-types that should not +be treated according to their mailcap entry. This option is designed to +deal with binary types such as application/octet-stream. When an attachment's +mime-type is listed in mime_lookup, then the extension of the filename will +be compared to the list of extensions in the mime.types file. The mime-type +associated with this extension will then be used to process the attachment +according to the rules in the mailcap file and according to any other configuration +options (such as auto_view) specified. Common usage would be: +

+mime_lookup application/octet-stream application/X-Lotus-Manuscript
+

+In addition, the unmime_lookup command may be used to disable this feature +for any particular mime-type if it had been set, for example, in a global +muttrc. +

Chapter 6. Optional features

Table of Contents

1. General notes
1.1. Enabling/disabling features
1.2. URL syntax
2. SSL/TLS Support
3. POP3 Support
4. IMAP Support
4.1. The Folder Browser
4.2. Authentication
5. SMTP Support
6. Managing multiple accounts
7. Local caching
7.1. Header caching
7.2. Body caching
7.3. Maintenance
8. Exact address generation

1. General notes

1.1. Enabling/disabling features

+Mutt supports several of optional features which can be enabled or +disabled at compile-time by giving the configure script +certain arguments. These are listed in the “Optional features” section of +the configure --help output. +

+Which features are enabled or disabled can later be determined from the +output of mutt -v. If a compile option starts with +“+” it is enabled and disabled if prefixed with “-”. For example, if +mutt was compiled using GnuTLS for encrypted communication instead of +OpenSSL, mutt -v would contain: +

+-USE_SSL_OPENSSL +USE_SSL_GNUTLS

1.2. URL syntax

+Mutt optionally supports the IMAP, POP3 and SMTP protocols which require +to access servers using URLs. The canonical syntax for specifying URLs +in mutt is (an item enclosed in [] means it is optional and +may be omitted): +

+proto[s]://[username[:password]@]server[:port]/[path]
+

+proto is the communication protocol: +imap for IMAP, pop for POP3 and +smtp for SMTP. If “s” for “secure communication” +is appended, mutt will attempt to establish an encrypted communication +using SSL or TLS. If no explicit port is given, mutt will use the +system's default for the given protocol. +

+Since all protocols by mutt support authentication, the username may be +given directly in the URL instead of using the pop_user or +imap_user variables. It may contain the “@” symbol +being used by many mail systems as part of the login name. A password can be +given, too but is not recommended if the URL is specified in a configuration +file on disk. +

+The optional path is only relevant for IMAP. +

+For IMAP for example, you can select an alternative port by specifying it with the +server: imap://imapserver:port/INBOX. You can also specify different +username for each folder: imap://username@imapserver[:port]/INBOX +or imap://username2@imapserver[:port]/path/to/folder. +Replacing imap:// by imaps:// +would make mutt attempt to connect using SSL or TLS on a different port +to encrypt the communication. +

2. SSL/TLS Support

+If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be +compiled with support for SSL or TLS using either OpenSSL or GnuTLS ( +by running the configure script with the +--enable-ssl=... option for OpenSSL or +--enable-gnutls=... for GnuTLS). Mutt can then +attempt to encrypt communication with remote servers if these protocols +are suffixed with “s” for “secure communication”. +

3. POP3 Support

+If Mutt was compiled with POP3 support (by running the configure +script with the --enable-pop flag), it has the ability to work +with mailboxes located on a remote POP3 server and fetch mail for local +browsing. +

+Remote POP3 servers can be accessed using URLs with the pop protocol +for unencrypted and pops for encrypted +communication, see Section 1.2, “URL syntax” for details. +

+Polling for new mail is more expensive over POP3 than locally. For this +reason the frequency at which Mutt will check for mail remotely can be +controlled by the +$pop_checkinterval +variable, which defaults to every 60 seconds. +

+Another way to access your POP3 mail is the <fetch-mail$ function +(default: G). It allows to connect to $pop_host, 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. +

Note

+If you only need to fetch all messages to a +local mailbox you should consider using a specialized program, such as +fetchmail, getmail or similar. +

4. IMAP Support

+If Mutt was compiled with IMAP support (by running the configure +script with the --enable-imap flag), it has the ability to work +with folders located on a remote IMAP server. +

+You can access the remote inbox by selecting the folder by its URL +(see Section 1.2, “URL syntax” for details) using the +imap or imaps protocol. +Alternatively, a pine-compatible notation is also supported, ie +{[username@]imapserver[:port][/ssl]}path/to/folder +

+Note that not all servers use “/” as the hierarchy separator. Mutt should +correctly notice which separator is being used by the server and convert +paths accordingly. +

+When browsing folders on an IMAP server, you can toggle whether to look +at only the folders you are subscribed to, or all folders with the +toggle-subscribed command. See also the +$imap_list_subscribed variable. +

+Polling for new mail on an IMAP server can cause noticeable delays. So, you'll +want to carefully tune the +$mail_check +and +$timeout +variables. Personally I use +

+set mail_check=90
+set timeout=15
+

+with relatively good results over my slow modem line. +

Note

+Note that if you are using mbox as the mail store on UW servers prior to +v12.250, the server has been reported to disconnect a client if another client +selects the same folder. +

4.1. The Folder Browser

+As of version 1.2, mutt supports browsing mailboxes on an IMAP +server. This is mostly the same as the local file browser, with the +following differences: +

  • +In lieu of file permissions, mutt displays the string "IMAP", +possibly followed by the symbol "+", indicating +that the entry contains both messages and subfolders. On +Cyrus-like servers folders will often contain both messages and +subfolders. +

  • +For the case where an entry can contain both messages and +subfolders, the selection key (bound to enter by default) +will choose to descend into the subfolder view. If you wish to view +the messages in that folder, you must use view-file instead +(bound to space by default). +

  • +You can create, delete and rename mailboxes with the +create-mailbox, delete-mailbox, and +rename-mailbox commands (default bindings: C, +d and r, respectively). You may also +subscribe and unsubscribe to mailboxes (normally +these are bound to s and u, respectively). +

4.2. Authentication

+Mutt supports four authentication methods with IMAP servers: SASL, +GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add +NTLM authentication for you poor exchange users out there, but it has +yet to be integrated into the main tree). There is also support for +the pseudo-protocol ANONYMOUS, which allows you to log in to a public +IMAP server without having an account. To use ANONYMOUS, simply make +your username blank or "anonymous". +

+SASL is a special super-authenticator, which selects among several protocols +(including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure +method available on your host and the server. Using some of these methods +(including DIGEST-MD5 and possibly GSSAPI), your entire session will be +encrypted and invisible to those teeming network snoops. It is the best +option if you have it. To use it, you must have the Cyrus SASL library +installed on your system and compile mutt with the --with-sasl flag. +

+Mutt will try whichever methods are compiled in and available on the server, +in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN. +

+There are a few variables which control authentication: +

  • +$imap_user - controls +the username under which you request authentication on the IMAP server, +for all authenticators. This is overridden by an explicit username in +the mailbox path (ie by using a mailbox name of the form +{user@host}). +

  • +$imap_pass - a +password which you may preset, used by all authentication methods where +a password is needed. +

  • +$imap_authenticators - a colon-delimited list of IMAP +authentication methods to try, in the order you wish to try them. If +specified, this overrides mutt's default (attempt everything, in the order +listed above). +

5. SMTP Support

+Besides supporting traditional mail delivery through a +sendmail-compatible program, mutt supports delivery through SMTP if it +was configured and built with --enable-smtp. +

+If the configuration variable +$smtp_url is set, mutt +will contact the given SMTP server to deliver messages; if it is unset, +mutt will use the program specified by $sendmail. +

+For details on the URL syntax, please see Section 1.2, “URL syntax”. +

+The built-in SMTP support supports encryption (the smtps protocol +using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms +for SASL are specified in $smtp_authenticators +defaulting to an empty list which makes mutt try all available methods +from most-secure to least-secure. +

6. Managing multiple accounts

+If you happen to have accounts on multiple IMAP, POP and/or SMTP servers, +you may find managing all the authentication settings inconvenient and +error-prone. The account-hook command may help. This hook works like +folder-hook but is invoked whenever you access a remote mailbox +(including inside the folder browser), not just when you open the +mailbox which includes (for example) polling for new mail, storing Fcc +messages and saving messages to a folder. As a consequence, +account-hook should only be used to set connection-related settings such +as passwords or tunnel commands but not settings such as sender +address or name (because in general it should be considered unpredictable +which account-hook was last used). +

+Some examples: +

+account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
+account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
+account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
+account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
+

7. Local caching

+Mutt contains two types of local caching: (1) +the so-called “header caching” and (2) the +so-called “body caching” which are both described in this section. +

+Header caching is optional as it depends on external libraries, body +caching is always enabled if mutt is compiled with POP and/or IMAP +support as these use it (body caching requires no external library). +

7.1. Header caching

+Mutt provides optional support for caching message headers for the +following types of folders: IMAP, POP, Maildir and MH. Header caching +greatly improves speed because for remote folders, headers +usually only need to be downloaded once. For Maildir and MH, reading the +headers from a single file is much faster than looking at possibly +thousands of single files (since Maildir and MH use one file per message.) +

+Header caching can be enabled via the configure script and the +--enable-hcache option. It's not turned on +by default because external database libraries are required: one +of tokyocabinet, qdbm, gdbm or bdb must be present. +

+If enabled, $header_cache can be +used to either point to a file or a directory. If set to point to +a file, one database file for all folders will be used (which may +result in lower performance), but one file per folder if it points +to a directory. +

+For the one-file-per-folder case, database files for remote folders +will be named according to their URL while database files for local +folders will be named by the MD5 checksums of their path. These database +files may be safely removed if a system is short on space. You +can compute the name of the header cache file for a particular local folder +through a command like the following: +

+$ printf '%s' '/path/to/folder' | md5sum
+

+The md5sum command may also be +named md5, depending on your operating system. +

7.2. Body caching

+Both cache methods can be combined using the same directory for storage +(and for IMAP/POP even provide meaningful file names) which simplifies +manual maintenance tasks. +

+In addition to caching message headers only, mutt can also cache +whole message bodies. This results in faster display of messages +for POP and IMAP folders because messages usually have to be +downloaded only once. +

+For configuration, the variable $message_cachedir must point to a +directory. There, mutt will create a hierarchy of subdirectories +named like: proto:user@hostname where +proto is either “pop” or “imap.” Within +there for each folder, mutt stores messages in single files (just +like Maildir) so that with manual symlink creation these cache +directories can be examined with mutt as read-only Maildir folders. +

+All files can be removed as needed if the consumed disk space +becomes an issue as mutt will silently fetch missing items again. +

7.3. Maintenance

+Mutt does not (yet) support maintenance features for header cache +database files so that files have to be removed in case they grow too +big. It depends on the database library used for header caching whether +disk space freed by removing messages is re-used. +

+For body caches, mutt can keep the local cache in sync with the +remote mailbox if the +$message_cache_clean +variable is set. Cleaning means to remove messages from the cache which +are no longer present in the mailbox which only happens when other mail +clients or instances of mutt using a different body cache location +delete messages (Mutt itself removes deleted messages from the cache +when syncing a mailbox). As cleaning can take a noticeable amount of time, +it should not be set in general but only occasionally. +

8. Exact address generation

+Mutt supports the “Name <user@host>” address syntax for reading and +writing messages, the older “user@host (Name)” syntax is only supported when +reading messages. The --enable-exact-address +switch can be given to configure to build it with write-support +for the latter syntax. EXACT_ADDRESS in the output of +mutt -v indicates whether it's supported. +

Chapter 7. Performance tuning

Table of Contents

1. Reading and writing mailboxes
2. Reading messages from remote folders
3. Searching and limiting

1. Reading and writing mailboxes

+Mutt's performance when reading mailboxes can be improved in two ways: +

  1. +For remote folders (IMAP and POP) as well as folders using +one-file-per message storage (Maildir and MH), mutt's +performance can be greatly improved using +header caching. +Using a single database per folder may further increase +performance. +

  2. +Mutt provides the $read_inc +and $write_inc +variables to specify at which rate to update progress +counters. If these values are too low, mutt may spend more +time on updating the progress counter than it spends on +actually reading/writing folders. +

    +For example, when opening a maildir folder with a few +thousand messages, the default value for +$read_inc +may be too low. It can be tuned on on a folder-basis using +folder-hooks: +

    +# use very high $read_inc to speed up reading hcache'd maildirs
+folder-hook . 'set read_inc=1000'
+# use lower value for reading slower remote IMAP folders
+folder-hook ^imap 'set read_inc=100'
+# use even lower value for reading even slower remote POP folders
+folder-hook ^pop 'set read_inc=1'

These settings work on a per-message basis. However, as messages may +greatly differ in size and certain operations are much faster than others, +even per-folder settings of the increment variables may not be +desirable as they produce either too few or too much progress updates. +Thus, Mutt allows to limit the number of progress updates per second it'll +actually send to the terminal using the +$time_inc variable.

2. Reading messages from remote folders

+Reading messages from remote folders such as IMAP an POP can be +slow especially for large mailboxes since mutt only caches a very +limited number of recently viewed messages (usually 10) per +session (so that it will be gone for the next session.) +

+To improve performance and permanently cache whole messages, +please refer to mutt's so-called +body caching for details. +

3. Searching and limiting

+When searching mailboxes either via a search or a limit action, for +some patterns mutt distinguishes between regular expression and string +searches. For regular expressions, patterns are prefixed with +“˜” and with “=” for string searches. +

+Even though a regular expression search is fast, it's several times +slower than a pure string search which is noticeable especially on large +folders. As a consequence, a string search should be used instead of a +regular expression search if the user already knows enough about the +search pattern. +

+For example, when limiting a large folder to all messages sent to or by +an author, it's much faster to search for the initial part of an e-mail +address via =Luser@ instead of +˜Luser@. This is especially true for searching +message bodies since a larger amount of input has to be searched. +

+Please note that string search is an exact case-sensitive search +while a regular expression search with only lower-case letters performs +a case-insensitive search. +

Chapter 8. Reference

Table of Contents

1. Command line options
2. Configuration Commands
3. Configuration variables
3.1. abort_nosubject
3.2. abort_unmodified
3.3. alias_file
3.4. alias_format
3.5. allow_8bit
3.6. allow_ansi
3.7. arrow_cursor
3.8. ascii_chars
3.9. askbcc
3.10. askcc
3.11. assumed_charset
3.12. attach_charset
3.13. attach_format
3.14. attach_sep
3.15. attach_split
3.16. attribution
3.17. autoedit
3.18. auto_tag
3.19. beep
3.20. beep_new
3.21. bounce
3.22. bounce_delivered
3.23. braille_friendly
3.24. check_mbox_size
3.25. charset
3.26. check_new
3.27. collapse_unread
3.28. uncollapse_jump
3.29. compose_format
3.30. config_charset
3.31. confirmappend
3.32. confirmcreate
3.33. connect_timeout
3.34. content_type
3.35. copy
3.36. crypt_use_gpgme
3.37. crypt_use_pka
3.38. crypt_autopgp
3.39. crypt_autosmime
3.40. date_format
3.41. default_hook
3.42. delete
3.43. delete_untag
3.44. digest_collapse
3.45. display_filter
3.46. dotlock_program
3.47. dsn_notify
3.48. dsn_return
3.49. duplicate_threads
3.50. edit_headers
3.51. editor
3.52. encode_from
3.53. envelope_from_address
3.54. escape
3.55. fast_reply
3.56. fcc_attach
3.57. fcc_clear
3.58. folder
3.59. folder_format
3.60. followup_to
3.61. force_name
3.62. forward_decode
3.63. forward_edit
3.64. forward_format
3.65. forward_quote
3.66. from
3.67. gecos_mask
3.68. hdrs
3.69. header
3.70. help
3.71. hidden_host
3.72. hide_limited
3.73. hide_missing
3.74. hide_thread_subject
3.75. hide_top_limited
3.76. hide_top_missing
3.77. history
3.78. history_file
3.79. honor_followup_to
3.80. hostname
3.81. ignore_linear_white_space
3.82. ignore_list_reply_to
3.83. imap_authenticators
3.84. imap_check_subscribed
3.85. imap_delim_chars
3.86. imap_headers
3.87. imap_idle
3.88. imap_keepalive
3.89. imap_list_subscribed
3.90. imap_login
3.91. imap_pass
3.92. imap_passive
3.93. imap_peek
3.94. imap_pipeline_depth
3.95. imap_servernoise
3.96. imap_user
3.97. implicit_autoview
3.98. include
3.99. include_onlyfirst
3.100. indent_string
3.101. index_format
3.102. ispell
3.103. keep_flagged
3.104. locale
3.105. mail_check
3.106. mailcap_path
3.107. mailcap_sanitize
3.108. maildir_mtime
3.109. header_cache
3.110. maildir_header_cache_verify
3.111. header_cache_pagesize
3.112. maildir_trash
3.113. mark_old
3.114. markers
3.115. mask
3.116. mbox
3.117. mbox_type
3.118. metoo
3.119. menu_context
3.120. menu_move_off
3.121. menu_scroll
3.122. meta_key
3.123. mh_purge
3.124. mh_seq_flagged
3.125. mh_seq_replied
3.126. mh_seq_unseen
3.127. mime_forward
3.128. mime_forward_decode
3.129. mime_forward_rest
3.130. mix_entry_format
3.131. mixmaster
3.132. move
3.133. message_cachedir
3.134. message_cache_clean
3.135. message_format
3.136. narrow_tree
3.137. net_inc
3.138. pager
3.139. pager_context
3.140. pager_format
3.141. pager_index_lines
3.142. pager_stop
3.143. crypt_autosign
3.144. crypt_autoencrypt
3.145. pgp_ignore_subkeys
3.146. crypt_replyencrypt
3.147. crypt_replysign
3.148. crypt_replysignencrypted
3.149. crypt_timestamp
3.150. sidebar_delim
3.151. sidebar_visible
3.152. sidebar_width
3.153. pgp_use_gpg_agent
3.154. crypt_verify_sig
3.155. smime_is_default
3.156. smime_ask_cert_label
3.157. smime_decrypt_use_default_key
3.158. pgp_entry_format
3.159. pgp_good_sign
3.160. pgp_check_exit
3.161. pgp_long_ids
3.162. pgp_retainable_sigs
3.163. pgp_autoinline
3.164. pgp_replyinline
3.165. pgp_show_unusable
3.166. pgp_sign_as
3.167. pgp_strict_enc
3.168. pgp_timeout
3.169. pgp_sort_keys
3.170. pgp_mime_auto
3.171. pgp_auto_decode
3.172. pgp_mime_signature_filename
3.173. pgp_mime_signature_description
3.174. pgp_decode_command
3.175. pgp_getkeys_command
3.176. pgp_verify_command
3.177. pgp_decrypt_command
3.178. pgp_clearsign_command
3.179. pgp_sign_command
3.180. pgp_encrypt_sign_command
3.181. pgp_encrypt_only_command
3.182. pgp_import_command
3.183. pgp_export_command
3.184. pgp_verify_key_command
3.185. pgp_list_secring_command
3.186. pgp_list_pubring_command
3.187. forward_decrypt
3.188. smime_timeout
3.189. smime_encrypt_with
3.190. smime_keys
3.191. smime_ca_location
3.192. smime_certificates
3.193. smime_decrypt_command
3.194. smime_verify_command
3.195. smime_verify_opaque_command
3.196. smime_sign_command
3.197. smime_sign_opaque_command
3.198. smime_encrypt_command
3.199. smime_pk7out_command
3.200. smime_get_cert_command
3.201. smime_get_signer_cert_command
3.202. smime_import_cert_command
3.203. smime_get_cert_email_command
3.204. smime_default_key
3.205. ssl_client_cert
3.206. ssl_force_tls
3.207. ssl_starttls
3.208. certificate_file
3.209. ssl_use_sslv3
3.210. ssl_use_tlsv1
3.211. ssl_min_dh_prime_bits
3.212. ssl_ca_certificates_file
3.213. pipe_split
3.214. pipe_decode
3.215. pipe_sep
3.216. pop_authenticators
3.217. pop_auth_try_all
3.218. pop_checkinterval
3.219. pop_delete
3.220. pop_host
3.221. pop_last
3.222. pop_reconnect
3.223. pop_user
3.224. pop_pass
3.225. post_indent_string
3.226. postpone
3.227. postponed
3.228. preconnect
3.229. print
3.230. print_command
3.231. print_decode
3.232. print_split
3.233. prompt_after
3.234. query_command
3.235. query_format
3.236. quit
3.237. quote_regexp
3.238. read_inc
3.239. read_only
3.240. realname
3.241. recall
3.242. record
3.243. reply_regexp
3.244. reply_self
3.245. reply_to
3.246. resolve
3.247. reverse_alias
3.248. reverse_name
3.249. reverse_realname
3.250. rfc2047_parameters
3.251. save_address
3.252. save_empty
3.253. save_history
3.254. save_name
3.255. score
3.256. score_threshold_delete
3.257. score_threshold_flag
3.258. score_threshold_read
3.259. send_charset
3.260. sendmail
3.261. sendmail_wait
3.262. shell
3.263. sig_dashes
3.264. sig_on_top
3.265. signature
3.266. simple_search
3.267. smart_wrap
3.268. smileys
3.269. sleep_time
3.270. smtp_authenticators
3.271. smtp_pass
3.272. smtp_url
3.273. sort
3.274. sort_alias
3.275. sort_aux
3.276. sort_browser
3.277. sort_re
3.278. spam_separator
3.279. spoolfile
3.280. status_chars
3.281. status_format
3.282. status_on_top
3.283. strict_threads
3.284. suspend
3.285. text_flowed
3.286. thread_received
3.287. thorough_search
3.288. tilde
3.289. time_inc
3.290. timeout
3.291. tmpdir
3.292. to_chars
3.293. trash
3.294. tunnel
3.295. use_8bitmime
3.296. use_domain
3.297. use_envelope_from
3.298. use_from
3.299. use_idn
3.300. use_ipv6
3.301. user_agent
3.302. visual
3.303. wait_key
3.304. weed
3.305. wrap
3.306. wrap_search
3.307. wrapmargin
3.308. write_inc
3.309. write_bcc
3.310. xterm_icon
3.311. xterm_set_titles
3.312. xterm_title
4. Functions
4.1. generic menu
4.2. index menu
4.3. pager menu
4.4. alias menu
4.5. query menu
4.6. attach menu
4.7. compose menu
4.8. postpone menu
4.9. browser menu
4.10. pgp menu
4.11. smime menu
4.12. mix menu
4.13. editor menu

1. Command line options

+Running mutt with no arguments will make Mutt attempt to read your spool +mailbox. However, it is possible to read other mailboxes and +to send messages from the command line as well. +

Table 8.1. Command line options

OptionDescription
-Aexpand an alias
-aattach a file to a message
-bspecify a blind carbon-copy (BCC) address
-cspecify a carbon-copy (Cc) address
-Dprint the value of all mutt variables to stdout
-especify a config command to be run after initialization files are read
-fspecify a mailbox to load
-Fspecify an alternate file to read initialization commands
-hprint help on command line options
-Hspecify a draft file from which to read a header and body
-ispecify a file to include in a message composition
-mspecify a default mailbox type
-ndo not read the system Muttrc
-precall a postponed message
-Qquery a configuration variable
-Ropen mailbox in read-only mode
-sspecify a subject (enclose in quotes if it contains spaces)
-vshow version number and compile-time definitions
-xsimulate the mailx(1) compose mode
-yshow a menu containing the files specified by the mailboxes command
-zexit immediately if there are no messages in the mailbox
-Zopen the first folder with new message,exit immediately if none

+To read messages in a mailbox +

mutt [-nz] [-F +muttrc +] [-m +type +] [-f +mailbox +]

+To compose a new message +

mutt [-n] [-F +muttrc +] [-c +address +] [-i +filename +] [-s +subject +] [ +-a +file + [...] +-- +] +address +...

+Mutt also supports a “batch” mode to send prepared messages. Simply redirect +input from the file you wish to send. For example, +

+mutt -s "data set for run #2" professor@bigschool.edu +< ˜/run2.dat +

+This command will send a message to “professor@bigschool.edu” with a subject +of “data set for run #2”. In the body of the message will be the contents +of the file “˜/run2.dat”. +

+All files passed with -a file will be attached as a MIME +part to the message. To attach several files, use “--” to separate files and +recipient addresses: mutt -a *.png -- some@one.org +

2. Configuration Commands

+The following are the commands understood by mutt. +

  • account-hook +pattern +command +

  • alias [ +-group +name +...] +key + +address + [ +address +...]

  • unalias [ +-group +name +...] { +* + | +key +... }

  • alternates [ +-group +name +...] +regexp + [ +regexp +...]

  • unalternates [ +-group +name +...] { +* + | +regexp +... }

  • alternative-order +mimetype + [ +mimetype +...]

  • unalternative-order { +* + | +mimetype +... }

  • auto-view +mimetype + [ +mimetype +...]

  • unauto-view { +* + | +mimetype +... }

  • bind +map + +key + +function +

  • charset-hook +alias + +charset +

  • iconv-hook +charset + +local-charset +

  • color +object + +foreground + +background +

    color { +header + | +body + } +foreground + +background + +regexp +

    color +index + +foreground + +background + +pattern +

  • uncolor +index + +pattern +...

  • exec +function + [ +function +...]

  • fcc-hook +[!]pattern + +mailbox +

  • fcc-save-hook +[!]pattern + +mailbox +

  • folder-hook +[!]regexp + +command +

  • group [ +-group +name +...] { +-rx +expr +... | +-addr +expr +... }

  • ungroup [ +-group +name +...] { +* + | +-rx +expr +... | +-addr +expr +... }

  • hdr_order +header + [ +header +...]

  • unhdr_order { +* + | +header +... }

  • ignore +pattern + [ +pattern +...]

  • unignore { +* + | +pattern +... }

  • lists [ +-group +name +] +regexp + [ +regexp +...]

  • unlists [ +-group +name +...] { +* + | +regexp +... }

  • macro +menu + +key + +sequence + [ +description +]

  • mailboxes +mailbox + [ +mailbox +...]

  • unmailboxes { +* + | +mailbox +... }

  • mbox-hook +[!]pattern + +mailbox +

  • message-hook +[!]pattern + +command +

  • mime-lookup +mimetype + [ +mimetype +...]

  • unmime-lookup { +* + | +mimetype +... }

  • mono +object + +attribute +

    mono { +header + | +body + } +attribute + +regexp +

    mono +index + +attribute + +pattern +

  • unmono +index + { +* + | +pattern +... }

  • my_hdr +string +

  • unmy_hdr { +* + | +field +... }

  • crypt-hook +pattern + +keyid +

  • push +string +

  • reset +variable + [ +variable +...]

  • save-hook +[!]pattern + +mailbox +

  • score +pattern + +value +

  • unscore { +* + | +pattern +... }

  • reply-hook +[!]pattern + +command +

  • send-hook +[!]pattern + +command +

  • send2-hook +[!]pattern + +command +

  • set { +[ no | inv ] +variable + | +variable=value + } [...]

  • unset +variable + [ +variable +...]

  • source +filename +

  • spam +pattern + +format +

  • nospam { +* + | +pattern + }

  • subscribe [ +-group +name +...] +regexp + [ +regexp +...]

  • unsubscribe [ +-group +name +...] { +* + | +regexp +... }

  • toggle +variable + [ +variable +...]

  • unhook { +* + | +hook-type + }

3. Configuration variables

3.1. abort_nosubject

Type: quadoption
+Default: ask-yes

+If set to yes, when composing messages and no subject is given +at the subject prompt, composition will be aborted. If set to +no, composing messages with no subject given at the subject +prompt will never be aborted. +

3.2. abort_unmodified

Type: quadoption
+Default: yes

+If set to yes, composition will automatically abort after +editing the message body if no changes are made to the file (this +check only happens after the first edit of the file). When set +to no, composition will never be aborted. +

3.3. alias_file

Type: path
+Default: “˜/.muttrc”

+The default file in which to save aliases created by the +<create-alias> function. Entries added to this file are +encoded in the character set specified by $config_charset if it +is set or the current character set otherwise. +

+Note: Mutt will not automatically source this file; you must +explicitly use the “source” command for it to be executed in case +this option points to a dedicated alias file. +

+The default for this option is the currently used muttrc file, or +“˜/.muttrc” if no user muttrc was found. +

3.4. alias_format

Type: string
+Default: “%4n %2f %t %-10a   %r”

+Specifies the format of the data displayed for the “alias” menu. The +following printf(3)-style sequences are available: + +

%a

alias name +

%f

flags - currently, a “d” for an alias marked for deletion +

%n

index number +

%r

address which alias expands to +

%t

character which indicates if the alias is tagged for inclusion +

3.5. allow_8bit

Type: boolean
+Default: yes

+Controls whether 8-bit data is converted to 7-bit using either Quoted- +Printable or Base64 encoding when sending mail. +

3.6. allow_ansi

Type: boolean
+Default: no

+Controls whether ANSI color codes in messages (and color tags in +rich text messages) are to be interpreted. +Messages containing these codes are rare, but if this option is set, +their text will be colored accordingly. Note that this may override +your color choices, and even present a security problem, since a +message could include a line like + +

+[-- PGP output follows ...
+
+

+and give it the same color as your attachment color (see also +$crypt_timestamp). +

3.7. arrow_cursor

Type: boolean
+Default: no

+When set, an arrow (“->”) will be used to indicate the current entry +in menus instead of highlighting the whole line. On slow network or modem +links this will make response faster because there is less that has to +be redrawn on the screen when moving to the next or previous entries +in the menu. +

3.8. ascii_chars

Type: boolean
+Default: no

+If set, Mutt will use plain ASCII characters when displaying thread +and attachment trees, instead of the default ACS characters. +

3.9. askbcc

Type: boolean
+Default: no

+If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients +before editing an outgoing message. +

3.10. askcc

Type: boolean
+Default: no

+If set, Mutt will prompt you for carbon-copy (Cc) recipients before +editing the body of an outgoing message. +

3.11. assumed_charset

Type: string
+Default: (empty)

+This variable is a colon-separated list of character encoding +schemes for messages without character encoding indication. +Header field values and message body content without character encoding +indication would be assumed that they are written in one of this list. +By default, all the header fields and message body without any charset +indication are assumed to be in “us-ascii”. +

+For example, Japanese users might prefer this: + +

+set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
+
+

+However, only the first content is valid for the message body. +

3.12. attach_charset

Type: string
+Default: (empty)

+This variable is a colon-separated list of character encoding +schemes for text file attachments. Mutt uses this setting to guess +which encoding files being attached are encoded in to convert them to +a proper character set given in $send_charset. +

+If unset, the value of $charset will be used instead. +For example, the following configuration would work for Japanese +text handling: + +

+set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
+
+

+Note: for Japanese users, “iso-2022-*” must be put at the head +of the value as shown above if included. +

3.13. attach_format

Type: string
+Default: “%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] ”

+This variable describes the format of the “attachment” menu. The +following printf(3)-style sequences are understood: + +

%C

charset +

%c

requires charset conversion (“n” or “c”) +

%D

deleted flag +

%d

description +

%e

MIME content-transfer-encoding +

%f

filename +

%I

disposition (“I” for inline, “A” for attachment) +

%m

major MIME type +

%M

MIME subtype +

%n

attachment number +

%Q

“Q”, if MIME part qualifies for attachment counting +

%s

size +

%t

tagged flag +

%T

graphic tree characters +

%u

unlink (=to delete) flag +

%X

number of qualifying MIME parts in this part and its children +(please see the “attachments” section for possible speed effects) +

%>X

right justify the rest of the string and pad with character “X” +

%|X

pad to the end of the line with character “X” +

%*X

soft-fill with character “X” as pad +

+For an explanation of “soft-fill”, see the $index_format documentation. +

3.14. attach_sep

Type: string
+Default: “\n”

+The separator to add between attachments when operating (saving, +printing, piping, etc) on a list of tagged attachments. +

3.15. attach_split

Type: boolean
+Default: yes

+If this variable is unset, when operating (saving, printing, piping, +etc) on a list of tagged attachments, Mutt will concatenate the +attachments and will operate on them as a single attachment. The +$attach_sep separator is added after each attachment. When set, +Mutt will operate on the attachments one by one. +

3.16. attribution

Type: 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 printf(3)-like sequences see +the section on $index_format. +

3.17. autoedit

Type: boolean
+Default: no

+When set along with $edit_headers, Mutt will skip the initial +send-menu (prompting for subject and recipients) and allow you to +immediately begin editing the body of your +message. The send-menu may still be accessed once you have finished +editing the body of your message. +

+Also see $fast_reply. +

3.18. auto_tag

Type: boolean
+Default: no

+When set, functions in the index menu which affect a message +will be applied to all tagged messages (if there are any). When +unset, you must first use the <tag-prefix> function (bound to “;” +by default) to make the next function apply to all tagged messages. +

3.19. beep

Type: boolean
+Default: yes

+When this variable is set, mutt will beep when an error occurs. +

3.20. beep_new

Type: boolean
+Default: no

+When this variable is set, mutt will beep whenever it prints a message +notifying you of new mail. This is independent of the setting of the +$beep variable. +

3.21. bounce

Type: quadoption
+Default: ask-yes

+Controls whether you will be asked to confirm bouncing messages. +If set to yes you don't get asked if you want to bounce a +message. Setting this variable to no is not generally useful, +and thus not recommended, because you are unable to bounce messages. +

3.22. bounce_delivered

Type: boolean
+Default: yes

+When this variable is set, mutt will include Delivered-To headers when +bouncing messages. Postfix users may wish to unset this variable. +

+Note: On Debian systems, this option is unset by default in +/etc/Muttrc. +

3.23. braille_friendly

Type: boolean
+Default: no

+When this variable is set, mutt will place the cursor at the beginning +of the current line in menus, even when the $arrow_cursor variable +is unset, making it easier for blind persons using Braille displays to +follow these menus. The option is unset by default because many +visual terminals don't permit making the cursor invisible. +

3.24. check_mbox_size

Type: boolean
+Default: no

+When this variable is set, mutt will use file size attribute instead of +access time when checking for new mail in mbox and mmdf folders. +

+This variable is unset by default and should only be enabled when +new mail detection for these folder types is unreliable or doesn't work. +

+Note that enabling this variable should happen before any “mailboxes” +directives occur in configuration files regarding mbox or mmdf folders +because mutt needs to determine the initial new mail status of such a +mailbox by performing a fast mailbox scan when it is defined. +Afterwards the new mail status is tracked by file size changes. +

3.25. charset

Type: string
+Default: (empty)

+Character set your terminal uses to display and enter textual data. +It is also the fallback for $send_charset. +

+Upon startup Mutt tries to derive this value from environment variables +such as $LC_CTYPE or $LANG. +

+Note: It should only be set in case Mutt isn't abled to determine the +character set used correctly. +

3.26. check_new

Type: boolean
+Default: yes

+Note: this option only affects maildir and MH style +mailboxes. +

+When set, Mutt will check for new mail delivered while the +mailbox is open. Especially with MH mailboxes, this operation can +take quite some time since it involves scanning the directory and +checking each file to see if it has already been looked at. If +this variable is unset, no check for new mail is performed +while the mailbox is open. +

3.27. collapse_unread

Type: boolean
+Default: yes

+When unset, Mutt will not collapse a thread if it contains any +unread messages. +

3.28. uncollapse_jump

Type: boolean
+Default: no

+When set, Mutt will jump to the next unread message, if any, +when the current thread is uncollapsed. +

3.29. compose_format

Type: string
+Default: “-- Mutt: Compose  [Approx. msg size: %l   Atts: %a]%>-”

+Controls the format of the status line displayed in the “compose” +menu. This string is similar to $status_format, but has its own +set of printf(3)-like sequences: + +

%a

total number of attachments +

%h

local hostname +

%l

approximate size (in bytes) of the current message +

%v

Mutt version string +

+See the text describing the $status_format option for more +information on how to set $compose_format. +

3.30. config_charset

Type: string
+Default: (empty)

+When defined, Mutt will recode commands in rc files from this +encoding to the current character set as specified by $charset +and aliases written to $alias_file from the current character set. +

+Please note that if setting $charset it must be done before +setting $config_charset. +

+Recoding should be avoided as it may render unconvertable +characters as question marks which can lead to undesired +side effects (for example in regular expressions). +

3.31. confirmappend

Type: boolean
+Default: yes

+When set, Mutt will prompt for confirmation when appending messages to +an existing mailbox. +

3.32. confirmcreate

Type: boolean
+Default: yes

+When set, Mutt will prompt for confirmation when saving messages to a +mailbox which does not yet exist before creating it. +

3.33. connect_timeout

Type: number
+Default: 30

+Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this +many seconds if the connection is not able to be established. A negative +value causes Mutt to wait indefinitely for the connection attempt to succeed. +

3.34. content_type

Type: string
+Default: “text/plain”

+Sets the default Content-Type for the body of newly composed messages. +

3.35. copy

Type: quadoption
+Default: yes

+This variable controls whether or not copies of your outgoing messages +will be saved for later references. Also see $record, +$save_name, $force_name and “fcc-hook”. +

3.36. crypt_use_gpgme

Type: boolean
+Default: no

+This variable controls the use of the GPGME-enabled crypto backends. +If it is set and Mutt was built with gpgme support, the gpgme code for +S/MIME and PGP will be used instead of the classic code. Note that +you need to set this option in .muttrc; it won't have any effect when +used interactively. +

3.37. crypt_use_pka

Type: boolean
+Default: no

+Controls whether mutt uses PKA +(see http://www.g10code.de/docs/pka-intro.de.pdf) during signature +verification (only supported by the GPGME backend). +

3.38. crypt_autopgp

Type: boolean
+Default: yes

+This variable controls whether or not mutt may automatically enable +PGP encryption/signing for messages. See also $crypt_autoencrypt, +$crypt_replyencrypt, +$crypt_autosign, $crypt_replysign and $smime_is_default. +

3.39. crypt_autosmime

Type: boolean
+Default: yes

+This variable controls whether or not mutt may automatically enable +S/MIME encryption/signing for messages. See also $crypt_autoencrypt, +$crypt_replyencrypt, +$crypt_autosign, $crypt_replysign and $smime_is_default. +

3.40. date_format

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 $index_format. This is passed to the strftime(3) +function to process the date, see the man page for the proper syntax. +

+Unless the first character in the string is a bang (“!”), the month +and week day names are expanded according to the locale specified in +the variable $locale. If the first character in the string is a +bang, the bang is discarded, and the month and week day names in the +rest of the string are expanded in the C locale (that is in US +English). +

3.41. default_hook

Type: string
+Default: “˜f %s !˜P | (˜P ˜C %s)”

+This variable controls how “message-hook”, “reply-hook”, “send-hook”, +“send2-hook”, “save-hook”, and “fcc-hook” will +be interpreted if they are specified with only a simple regexp, +instead of a matching pattern. The hooks are expanded when they are +declared, so a hook will be interpreted according to the value of this +variable at the time the hook is declared. +

+The default value matches +if the message is either from a user matching the regular expression +given, or if it is from you (if the from address matches +“alternates”) and is to or cc'ed to a user matching the given +regular expression. +

3.42. delete

Type: quadoption
+Default: ask-yes

+Controls whether or not messages are really deleted when closing or +synchronizing a mailbox. If set to yes, messages marked for +deleting will automatically be purged without prompting. If set to +no, messages marked for deletion will be kept in the mailbox. +

3.43. delete_untag

Type: boolean
+Default: yes

+If this option is set, mutt will untag messages when marking them +for deletion. This applies when you either explicitly delete a message, +or when you save it to another folder. +

3.44. digest_collapse

Type: boolean
+Default: yes

+If this option is set, mutt's received-attachments menu will not show the subparts of +individual messages in a multipart/digest. To see these subparts, press “v” on that menu. +

3.45. display_filter

Type: path
+Default: (empty)

+When set, specifies a command used to filter messages. When a message +is viewed it is passed as standard input to $display_filter, and the +filtered message is read from the standard output. +

3.46. dotlock_program

Type: path
+Default: “/usr/bin/mutt_dotlock”

+Contains the path of the mutt_dotlock(8) binary to be used by +mutt. +

3.47. dsn_notify

Type: string
+Default: (empty)

+This variable sets the request for when notification is returned. The +string consists of a comma separated list (no spaces!) of one or more +of the following: never, to never request notification, +failure, to request notification on transmission failure, +delay, to be notified of message delays, success, to be +notified of successful transmission. +

+Example: + +

+set dsn_notify="failure,delay"
+
+

+Note: when using $sendmail for delivery, you should not enable +this unless you are either using Sendmail 8.8.x or greater or a MTA +providing a sendmail(1)-compatible interface supporting the -N option +for DSN. For SMTP delivery, DSN support is autodetected so that it +depends on the server whether DSN will be used or not. +

3.48. dsn_return

Type: string
+Default: (empty)

+This variable controls how much of your message is returned in DSN +messages. It may be set to either hdrs to return just the +message header, or full to return the full message. +

+Example: + +

+set dsn_return=hdrs
+
+

+Note: when using $sendmail for delivery, you should not enable +this unless you are either using Sendmail 8.8.x or greater or a MTA +providing a sendmail(1)-compatible interface supporting the -R option +for DSN. For SMTP delivery, DSN support is autodetected so that it +depends on the server whether DSN will be used or not. +

3.49. duplicate_threads

Type: boolean
+Default: yes

+This variable controls whether mutt, when $sort is set to threads, threads +messages with the same Message-Id together. If it is set, it will indicate +that it thinks they are duplicates of each other with an equals sign +in the thread tree. +

3.50. edit_headers

Type: boolean
+Default: no

+This option allows you to edit the header of your outgoing messages +along with the body of your message. +

+Note that changes made to the References: and Date: headers are +ignored for interoperability reasons. +

3.51. editor

Type: path
+Default: (empty)

+This variable specifies which editor is used by mutt. +It defaults to the value of the $VISUAL, or $EDITOR, environment +variable, or to the string “/usr/bin/editor” if neither of those are set. +

3.52. encode_from

Type: boolean
+Default: no

+When set, mutt will quoted-printable encode messages when +they contain the string “From ” (note the trailing space) in the beginning of a line. +This is useful to avoid the tampering certain mail delivery and transport +agents tend to do with messages (in order to prevent tools from +misinterpreting the line as a mbox message separator). +

3.53. envelope_from_address

Type: e-mail address
+Default: (empty)

+Manually sets the envelope sender for outgoing messages. +This value is ignored if $use_envelope_from is unset. +

3.54. escape

Type: string
+Default: “˜”

+Escape character to use for functions in the builtin editor. +

3.55. fast_reply

Type: boolean
+Default: no

+When set, the initial prompt for recipients and subject are skipped +when replying to messages, and the initial prompt for subject is +skipped when forwarding messages. +

+Note: this variable has no effect when the $autoedit +variable is set. +

3.56. fcc_attach

Type: boolean
+Default: yes

+This variable controls whether or not attachments on outgoing messages +are saved along with the main body of your message. +

3.57. fcc_clear

Type: boolean
+Default: no

+When this variable is set, FCCs will be stored unencrypted and +unsigned, even when the actual message is encrypted and/or +signed. +(PGP only) +

3.58. folder

Type: path
+Default: “˜/Mail”

+Specifies the default location of your mailboxes. A “+” or “=” at the +beginning of a pathname will be expanded to the value of this +variable. Note that if you change this variable (from the default) +value you need to make sure that the assignment occurs before +you use “+” or “=” for any other variables since expansion takes place +when handling the “mailboxes” command. +

3.59. folder_format

Type: string
+Default: “%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f”

+This variable allows you to customize the file browser display to your +personal taste. This string is similar to $index_format, but has +its own set of printf(3)-like sequences: + +

%C

current file number +

%d

date/time folder was last modified +

%f

filename +

%F

file permissions +

%g

group name (or numeric gid, if missing) +

%l

number of hard links +

%N

N if folder has new mail, blank otherwise +

%s

size in bytes +

%t

“*” if the file is tagged, blank otherwise +

%u

owner name (or numeric uid, if missing) +

%>X

right justify the rest of the string and pad with character “X” +

%|X

pad to the end of the line with character “X” +

%*X

soft-fill with character “X” as pad +

+For an explanation of “soft-fill”, see the $index_format documentation. +

3.60. followup_to

Type: boolean
+Default: yes

+Controls whether or not the “Mail-Followup-To:” header field is +generated when sending mail. When set, Mutt will generate this +field when you are replying to a known mailing list, specified with +the “subscribe” or “lists” commands. +

+This field has two purposes. First, preventing you from +receiving duplicate copies of replies to messages which you send +to mailing lists, and second, ensuring that you do get a reply +separately for any messages sent to known lists to which you are +not subscribed. +

+The header will contain only the list's address +for subscribed lists, and both the list address and your own +email address for unsubscribed lists. Without this header, a +group reply to your message sent to a subscribed list will be +sent to both the list and your address, resulting in two copies +of the same email for you. +

3.61. force_name

Type: boolean
+Default: no

+This variable is similar to $save_name, except that Mutt will +store a copy of your outgoing message by the username of the address +you are sending to even if that mailbox does not exist. +

+Also see the $record variable. +

3.62. forward_decode

Type: boolean
+Default: yes

+Controls the decoding of complex MIME messages into text/plain when +forwarding a message. The message header is also RFC2047 decoded. +This variable is only used, if $mime_forward is unset, +otherwise $mime_forward_decode is used instead. +

3.63. forward_edit

Type: quadoption
+Default: yes

+This quadoption controls whether or not the user is automatically +placed in the editor when forwarding messages. For those who always want +to forward with no modification, use a setting of “no”. +

3.64. forward_format

Type: string
+Default: “[%a: %s]”

+This variable controls the default subject when forwarding a message. +It uses the same format sequences as the $index_format variable. +

3.65. forward_quote

Type: boolean
+Default: no

+When set, forwarded messages included in the main body of the +message (when $mime_forward is unset) will be quoted using +$indent_string. +

3.66. from

Type: e-mail address
+Default: (empty)

+When set, this variable contains a default from address. It +can be overridden using “my_hdr” (including from a “send-hook”) and +$reverse_name. This variable is ignored if $use_from is unset. +

+This setting defaults to the contents of the environment variable $EMAIL. +

3.67. gecos_mask

Type: regular expression
+Default: “^[^,]*”

+A regular expression used by mutt to parse the GECOS field of a password +entry when expanding the alias. The default value +will return the string up to the first “,” encountered. +If the GECOS field contains a string like “lastname, firstname” then you +should set it to “.*”. +

+This can be useful if you see the following behavior: you address an e-mail +to user ID “stevef” whose full name is “Steve Franklin”. If mutt expands +“stevef” to “"Franklin" stevef@foo.bar” then you should set the $gecos_mask to +a regular expression that will match the whole name so mutt will expand +“Franklin” to “Franklin, Steve”. +

3.68. hdrs

Type: boolean
+Default: yes

+When unset, the header fields normally added by the “my_hdr” +command are not created. This variable must 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. +

3.69. header

Type: boolean
+Default: no

+When set, this variable causes Mutt to include the header +of the message you are replying to into the edit buffer. +The $weed setting applies. +

3.70. help

Type: boolean
+Default: yes

+When set, help lines describing the bindings for the major functions +provided by each menu are displayed on the first line of the screen. +

+Note: The binding will not be displayed correctly if the +function is bound to a sequence rather than a single keystroke. Also, +the help line may not be updated if a binding is changed while Mutt is +running. Since this variable is primarily aimed at new users, neither +of these should present a major problem. +

3.71. hidden_host

Type: boolean
+Default: no

+When set, mutt will skip the host name part of $hostname variable +when adding the domain part to addresses. This variable does not +affect the generation of Message-IDs, and it will not lead to the +cut-off of first-level domains. +

3.72. hide_limited

Type: boolean
+Default: no

+When set, mutt will not show the presence of messages that are hidden +by limiting, in the thread tree. +

3.73. hide_missing

Type: boolean
+Default: yes

+When set, mutt will not show the presence of missing messages in the +thread tree. +

3.74. hide_thread_subject

Type: boolean
+Default: yes

+When set, mutt will not show the subject of messages in the thread +tree that have the same subject as their parent or closest previously +displayed sibling. +

3.75. hide_top_limited

Type: boolean
+Default: no

+When set, mutt will not show the presence of messages that are hidden +by limiting, at the top of threads in the thread tree. Note that when +$hide_limited is set, this option will have no effect. +

3.76. hide_top_missing

Type: boolean
+Default: yes

+When set, mutt will not show the presence of missing messages at the +top of threads in the thread tree. Note that when $hide_missing is +set, this option will have no effect. +

3.77. history

Type: number
+Default: 10

+This variable controls the size (in number of strings remembered) of +the string history buffer per category. The buffer is cleared each time the +variable is set. +

3.78. history_file

Type: path
+Default: “˜/.mutthistory”

+The file in which Mutt will save its history. +

3.79. honor_followup_to

Type: quadoption
+Default: yes

+This variable controls whether or not a Mail-Followup-To header is +honored when group-replying to a message. +

3.80. hostname

Type: string
+Default: (empty)

+Specifies the fully-qualified hostname of the system mutt is running on +containing the host's name and the DNS domain it belongs to. It is used +as the domain part (after “@”) for local email addresses as well as +Message-Id headers. +

+Its value is determined at startup as follows: If the node's name +as returned by the uname(3) function contains the hostname and the +domain, these are used to construct $hostname. If there is no +domain part returned, Mutt will look for a “domain” or “search” +line in /etc/resolv.conf to determine the domain. Optionally, Mutt +can be compiled with a fixed domain name in which case a detected +one is not used. +

+Also see $use_domain and $hidden_host. +

+Note: On Debian systems, the default for this variable is obtained +from /etc/mailname when Mutt starts. +

3.81. ignore_linear_white_space

Type: boolean
+Default: no

+This option replaces linear-white-space between encoded-word +and text to a single space to prevent the display of MIME-encoded +“Subject:” field from being divided into multiple lines. +

3.82. ignore_list_reply_to

Type: boolean
+Default: no

+Affects the behaviour of the <reply> function when replying to +messages from mailing lists (as defined by the “subscribe” or +“lists” commands). When set, if the “Reply-To:” field is +set to the same value as the “To:” field, Mutt assumes that the +“Reply-To:” field was set by the mailing list to automate responses +to the list, and will ignore this field. To direct a response to the +mailing list when this option is set, use the <list-reply> +function; <group-reply> will reply to both the sender and the +list. +

3.83. imap_authenticators

Type: string
+Default: (empty)

+This is a colon-delimited list of authentication methods mutt may +attempt to use to log in to an IMAP server, in the order mutt should +try them. Authentication methods are either “login” or the right +side of an IMAP “AUTH=xxx” capability string, eg “digest-md5”, “gssapi” +or “cram-md5”. This option is case-insensitive. If it's +unset (the default) mutt will try all available methods, +in order from most-secure to least-secure. +

+Example: + +

+set imap_authenticators="gssapi:cram-md5:login"
+
+

+Note: Mutt will only fall back to other authentication methods if +the previous methods are unavailable. If a method is available but +authentication fails, mutt will not connect to the IMAP server. +

3.84. imap_check_subscribed

Type: boolean
+Default: no

+When set, mutt will fetch the set of subscribed folders from +your server on connection, and add them to the set of mailboxes +it polls for new mail just as if you had issued individual “mailboxes” +commands. +

3.85. imap_delim_chars

Type: string
+Default: “/.”

+This contains the list of characters which you would like to treat +as folder separators for displaying IMAP paths. In particular it +helps in using the “=” shortcut for your folder variable. +

3.86. imap_headers

Type: string
+Default: (empty)

+Mutt requests these header fields in addition to the default headers +(“Date:”, “From:”, “Subject:”, “To:”, “Cc:”, “Message-Id:”, +“References:”, “Content-Type:”, “Content-Description:”, “In-Reply-To:”, +“Reply-To:”, “Lines:”, “List-Post:”, “X-Label:”) from IMAP +servers before displaying the index menu. You may want to add more +headers for spam detection. +

+Note: This is a space separated list, items should be uppercase +and not contain the colon, e.g. “X-BOGOSITY X-SPAM-STATUS” for the +“X-Bogosity:” and “X-Spam-Status:” header fields. +

3.87. imap_idle

Type: boolean
+Default: no

+When set, mutt will attempt to use the IMAP IDLE extension +to check for new mail in the current mailbox. Some servers +(dovecot was the inspiration for this option) react badly +to mutt's implementation. If your connection seems to freeze +up periodically, try unsetting this. +

3.88. imap_keepalive

Type: number
+Default: 900

+This variable specifies the maximum amount of time in seconds that mutt +will wait before polling open IMAP connections, to prevent the server +from closing them before mutt has finished with them. The default is +well within the RFC-specified minimum amount of time (30 minutes) before +a server is allowed to do this, but in practice the RFC does get +violated every now and then. Reduce this number if you find yourself +getting disconnected from your IMAP server due to inactivity. +

3.89. imap_list_subscribed

Type: boolean
+Default: no

+This variable configures whether IMAP folder browsing will look for +only subscribed folders or all folders. This can be toggled in the +IMAP browser with the <toggle-subscribed> function. +

3.90. imap_login

Type: string
+Default: (empty)

+Your login name on the IMAP server. +

+This variable defaults to the value of $imap_user. +

3.91. imap_pass

Type: string
+Default: (empty)

+Specifies the password for your IMAP account. If unset, Mutt will +prompt you for your password when you invoke the <fetch-mail> function +or try to open an IMAP folder. +

+Warning: you should only use this option when you are on a +fairly secure machine, because the superuser can read your muttrc even +if you are the only one who can read the file. +

3.92. imap_passive

Type: boolean
+Default: yes

+When set, mutt will not open new IMAP connections to check for new +mail. Mutt will only check for new mail over existing IMAP +connections. This is useful if you don't want to be prompted to +user/password pairs on mutt invocation, or if opening the connection +is slow. +

3.93. imap_peek

Type: boolean
+Default: yes

+When set, mutt will avoid implicitly marking your mail as read whenever +you fetch a message from the server. This is generally a good thing, +but can make closing an IMAP folder somewhat slower. This option +exists to appease speed freaks. +

3.94. imap_pipeline_depth

Type: number
+Default: 15

+Controls the number of IMAP commands that may be queued up before they +are sent to the server. A deeper pipeline reduces the amount of time +mutt must wait for the server, and can make IMAP servers feel much +more responsive. But not all servers correctly handle pipelined commands, +so if you have problems you might want to try setting this variable to 0. +

+Note: Changes to this variable have no effect on open connections. +

3.95. imap_servernoise

Type: boolean
+Default: yes

+When set, mutt will display warning messages from the IMAP +server as error messages. Since these messages are often +harmless, or generated due to configuration problems on the +server which are out of the users' hands, you may wish to suppress +them at some point. +

3.96. imap_user

Type: string
+Default: (empty)

+The name of the user whose mail you intend to access on the IMAP +server. +

+This variable defaults to your user name on the local machine. +

3.97. implicit_autoview

Type: boolean
+Default: no

+If set to “yes”, mutt will look for a mailcap entry with the +“copiousoutput” flag set for every MIME attachment it doesn't have +an internal viewer defined for. If such an entry is found, mutt will +use the viewer defined in that entry to convert the body part to text +form. +

3.98. include

Type: quadoption
+Default: ask-yes

+Controls whether or not a copy of the message(s) you are replying to +is included in your reply. +

3.99. include_onlyfirst

Type: boolean
+Default: no

+Controls whether or not Mutt includes only the first attachment +of the message you are replying. +

3.100. indent_string

Type: string
+Default: “> ”

+Specifies the string to prepend to each line of text quoted in a +message to which you are replying. You are strongly encouraged not to +change this value, as it tends to agitate the more fanatical netizens. +

+This option is a format string, please see the description of +$index_format for supported printf(3)-style sequences. +

+Because for format=lowed style messages the quoting mechanism +is strictly defined, this setting is ignored if $text_flowed is +set. +

3.101. index_format

Type: string
+Default: “%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s”

+This variable allows you to customize the message index display to +your personal taste. +

+“Format strings” are similar to the strings used in the C +function printf(3) to format output (see the man page for more details). +The following sequences are defined in Mutt: + +

%a

address of the author +

%A

reply-to address (if present; otherwise: address of 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 converted to sender's time zone +

%D

date and time of the message in the format specified by +$date_format converted to the local time zone +

%e

current message number in thread +

%E

number of messages in current thread +

%f

sender (address + real name), either From: or Return-Path: +

%F

author name, or recipient name if the message is from you +

%H

spam attribute(s) of this message +

%i

message-id of the current message +

%l

number of lines in the message (does not work with maildir, +mh, and possibly IMAP folders) +

%L

If an address in the “To:” or “Cc:” header field matches an address +defined by the users “subscribe” command, this displays +"To <list-name>", otherwise the same as %F. +

%m

total number of message in the mailbox +

%M

number of hidden messages if the thread is collapsed. +

%N

message score +

%n

author's real name (or address if missing) +

%O

original save folder where mutt would formerly have +stashed the message: list name or recipient name +if not sent to a list +

%P

progress indicator for the builtin pager (how much of the file has been displayed) +

%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 +

%v

first name of the author, or the recipient if the message is from you +

%X

number of attachments +(please see the “attachments” section for possible speed effects) +

%y

“X-Label:” field, if present +

%Y

“X-Label:” field, if present, and (1) not at part of a thread tree, +(2) at the top of a thread, or (3) “X-Label:” is different from +preceding message's “X-Label:”. +

%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 library function +strftime(3); 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 library function +strftime(3); a leading bang disables locales +

%(fmt)

the local date and time when the message was received. +“fmt” is expanded by the library function strftime(3); +a leading bang disables locales +

%<fmt>

the current local time. “fmt” is expanded by the library +function strftime(3); 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” +

%*X

soft-fill with character “X” as pad +

+“Soft-fill” deserves some explanation: Normal right-justification +will print everything to the left of the “%>”, displaying padding and +whatever lies to the right only if there's room. By contrast, +soft-fill gives priority to the right-hand side, guaranteeing space +to display it and showing padding only if there's still room. If +necessary, soft-fill will eat text leftwards to make room for +rightward text. +

+Note that these expandos are supported in +“save-hook”, “fcc-hook” and “fcc-save-hook”, too. +

3.102. ispell

Type: path
+Default: “ispell”

+How to invoke ispell (GNU's spell-checking software). +

3.103. keep_flagged

Type: boolean
+Default: no

+If set, read messages marked as flagged will not be moved +from your spool mailbox to your $mbox mailbox, or as a result of +a “mbox-hook” command. +

3.104. locale

Type: string
+Default: “C”

+The locale used by strftime(3) to format dates. Legal values are +the strings your system accepts for the locale environment variable $LC_TIME. +

3.105. mail_check

Type: number
+Default: 5

+This variable configures how often (in seconds) mutt should look for +new mail. Also see the $timeout variable. +

3.106. mailcap_path

Type: string
+Default: (empty)

+This variable specifies which files to consult when attempting to +display MIME bodies not directly supported by Mutt. +

3.107. mailcap_sanitize

Type: boolean
+Default: yes

+If set, mutt will restrict possible characters in mailcap % expandos +to a well-defined set of safe characters. This is the safe setting, +but we are not sure it doesn't break some more advanced MIME stuff. +

+DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE +DOING! +

3.108. maildir_mtime

Type: boolean
+Default: no

+If set, the sort-by-date option in the browser will sort maildirs +smartly, not using the mtime of the maildir itself but that of the +newest message in the new subdirectory, making the sorting by +reverse date much more useful. People with maildirs over NFS may +wish to leave this option unset. +

3.109. header_cache

Type: path
+Default: (empty)

+This variable points to the header cache database. +If pointing to a directory Mutt will contain a header cache +database file per folder, if pointing to a file that file will +be a single global header cache. By default it is unset so no header +caching will be used. +

+Header caching can greatly improve speed when opening POP, IMAP +MH or Maildir folders, see “caching” for details. +

3.110. maildir_header_cache_verify

Type: boolean
+Default: yes

+Check for Maildir unaware programs other than mutt having modified maildir +files when the header cache is in use. This incurs one stat(2) per +message every time the folder is opened (which can be very slow for NFS +folders). +

3.111. header_cache_pagesize

Type: string
+Default: “16384”

+When mutt is compiled with either gdbm or bdb4 as the header cache backend, +this option changes the database page size. Too large or too small +values can waste space, memory, or CPU time. The default should be more +or less optimal for most use cases. +

3.112. maildir_trash

Type: boolean
+Default: no

+If set, messages marked as deleted will be saved with the maildir +trashed flag instead of unlinked. Note: this only applies +to maildir-style mailboxes. Setting it will have no effect on other +mailbox types. +

3.113. mark_old

Type: boolean
+Default: yes

+Controls whether or not mutt marks new unread +messages as old if you exit a mailbox without reading them. +With this option set, the next time you start mutt, the messages +will show up with an “O” next to them in the index menu, +indicating that they are old. +

3.114. markers

Type: boolean
+Default: yes

+Controls the display of wrapped lines in the internal pager. If set, a +“+” marker is displayed at the beginning of wrapped lines. +

+Also see the $smart_wrap variable. +

3.115. mask

Type: regular expression
+Default: “!^\.[^.]”

+A regular expression used in the file browser, optionally preceded by +the not operator “!”. Only files whose names match this mask +will be shown. The match is always case-sensitive. +

3.116. mbox

Type: path
+Default: “˜/mbox”

+This specifies the folder into which read mail in your $spoolfile +folder will be appended. +

+Also see the $move variable. +

3.117. mbox_type

Type: folder magic
+Default: mbox

+The default mailbox type used when creating new folders. May be any of +“mbox”, “MMDF”, “MH” and “Maildir”. +

3.118. metoo

Type: boolean
+Default: no

+If unset, Mutt will remove your address (see the “alternates” +command) from the list of recipients when replying to a message. +

3.119. menu_context

Type: number
+Default: 0

+This variable controls the number of lines of context that are given +when scrolling through menus. (Similar to $pager_context.) +

3.120. menu_move_off

Type: boolean
+Default: yes

+When unset, the bottom entry of menus will never scroll up past +the bottom of the screen, unless there are less entries than lines. +When set, the bottom entry may move off the bottom. +

3.121. menu_scroll

Type: boolean
+Default: no

+When set, menus will be scrolled up or down one line when you +attempt to move across a screen boundary. If unset, the screen +is cleared and the next or previous page of the menu is displayed +(useful for slow links to avoid many redraws). +

3.122. meta_key

Type: boolean
+Default: no

+If set, forces Mutt to interpret keystrokes with the high bit (bit 8) +set as if the user had pressed the Esc key and whatever key remains +after having the high bit removed. For example, if the key pressed +has an ASCII value of 0xf8, then this is treated as if the user had +pressed Esc then “x”. This is because the result of removing the +high bit from 0xf8 is 0x78, which is the ASCII character +“x”. +

3.123. mh_purge

Type: boolean
+Default: no

+When unset, mutt will mimic mh's behaviour and rename deleted messages +to ,<old file name> in mh folders instead of really deleting +them. This leaves the message on disk but makes programs reading the folder +ignore it. If the variable is set, the message files will simply be +deleted. +

+This option is similar to $maildir_trash for Maildir folders. +

3.124. mh_seq_flagged

Type: string
+Default: “flagged”

+The name of the MH sequence used for flagged messages. +

3.125. mh_seq_replied

Type: string
+Default: “replied”

+The name of the MH sequence used to tag replied messages. +

3.126. mh_seq_unseen

Type: string
+Default: “unseen”

+The name of the MH sequence used for unseen messages. +

3.127. mime_forward

Type: quadoption
+Default: no

+When set, the message you are forwarding will be attached as a +separate message/rfc822 MIME part instead of included in the main body of the +message. This is useful for forwarding MIME messages so the receiver +can properly view the message as it was delivered to you. If you like +to switch between MIME and not MIME from mail to mail, set this +variable to “ask-no” or “ask-yes”. +

+Also see $forward_decode and $mime_forward_decode. +

3.128. mime_forward_decode

Type: boolean
+Default: no

+Controls the decoding of complex MIME messages into text/plain when +forwarding a message while $mime_forward is set. Otherwise +$forward_decode is used instead. +

3.129. mime_forward_rest

Type: quadoption
+Default: yes

+When forwarding multiple attachments of a MIME message from the attachment +menu, attachments which cannot be decoded in a reasonable manner will +be attached to the newly composed message if this option is set. +

3.130. mix_entry_format

Type: string
+Default: “%4n %c %-16s %a”

+This variable describes the format of a remailer line on the mixmaster +chain selection screen. The following printf(3)-like sequences are +supported: + +

%n

The running number on the menu. +

%c

Remailer capabilities. +

%s

The remailer's short name. +

%a

The remailer's e-mail address. +

3.131. mixmaster

Type: path
+Default: “mixmaster”

+This variable contains the path to the Mixmaster binary on your +system. It is used with various sets of parameters to gather the +list of known remailers, and to finally send a message through the +mixmaster chain. +

+Note: On Debian systems, this option is set by default to +“mixmaster-filter” in /etc/Muttrc. +

3.132. move

Type: quadoption
+Default: no

+Controls whether or not Mutt will move read messages +from your spool mailbox to your $mbox mailbox, or as a result of +a “mbox-hook” command. +

3.133. message_cachedir

Type: path
+Default: (empty)

+Set this to a directory and mutt will cache copies of messages from +your IMAP and POP servers here. You are free to remove entries at any +time. +

+When setting this variable to a directory, mutt needs to fetch every +remote message only once and can perform regular expression searches +as fast as for local folders. +

+Also see the $message_cache_clean variable. +

3.134. message_cache_clean

Type: boolean
+Default: no

+If set, mutt will clean out obsolete entries from the message cache when +the mailbox is synchronized. You probably only want to set it +every once in a while, since it can be a little slow +(especially for large folders). +

3.135. message_format

Type: string
+Default: “%s”

+This is the string displayed in the “attachment” menu for +attachments of type message/rfc822. For a full listing of defined +printf(3)-like sequences see the section on $index_format. +

3.136. narrow_tree

Type: boolean
+Default: no

+This variable, when set, makes the thread tree narrower, allowing +deeper threads to fit on the screen. +

3.137. net_inc

Type: number
+Default: 10

+Operations that expect to transfer a large amount of data over the +network will update their progress every $net_inc kilobytes. +If set to 0, no progress messages will be displayed. +

+See also $read_inc, $write_inc and $net_inc. +

3.138. pager

Type: path
+Default: “builtin”

+This variable specifies which pager you would like to use to view +messages. The value “builtin” means to use the builtin pager, otherwise this +variable should specify the pathname of the external pager you would +like to use. +

+Using an external pager may have some disadvantages: Additional +keystrokes are necessary because you can't call mutt functions +directly from the pager, and screen resizes cause lines longer than +the screen width to be badly formatted in the help menu. +

3.139. pager_context

Type: number
+Default: 0

+This variable controls the number of lines of context that are given +when displaying the next or previous page in the internal pager. By +default, Mutt will display the line after the last one on the screen +at the top of the next page (0 lines of context). +

3.140. pager_format

Type: string
+Default: “-%Z- %C/%m: %-20.20n   %s%*  -- (%P)”

+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 $index_format +section. +

3.141. pager_index_lines

Type: number
+Default: 0

+Determines the number of lines of a mini-index which is shown when in +the pager. The current message, unless near the top or bottom of the +folder, will be roughly one third of the way down this mini-index, +giving the reader the context of a few messages before and after the +message. This is useful, for example, to determine how many messages +remain to be read in the current thread. One of the lines is reserved +for the status bar from the index, so a setting of 6 +will only show 5 lines of the actual index. A value of 0 results in +no index being shown. If the number of messages in the current folder +is less than $pager_index_lines, then the index will only use as +many lines as it needs. +

3.142. pager_stop

Type: boolean
+Default: no

+When set, the internal-pager will not move to the next message +when you are at the end of a message and invoke the <next-page> +function. +

3.143. crypt_autosign

Type: boolean
+Default: no

+Setting this variable will cause Mutt to always attempt to +cryptographically sign outgoing messages. This can be overridden +by use of the pgp menu, when signing is not required or +encryption is requested as well. If $smime_is_default is set, +then OpenSSL is used instead to create S/MIME messages and settings can +be overridden by use of the smime menu instead of the pgp menu. +(Crypto only) +

3.144. crypt_autoencrypt

Type: boolean
+Default: no

+Setting this variable will cause Mutt to always attempt to PGP +encrypt outgoing messages. This is probably only useful in +connection to the “send-hook” command. It can be overridden +by use of the pgp menu, when encryption is not required or +signing is requested as well. If $smime_is_default is set, +then OpenSSL is used instead to create S/MIME messages and +settings can be overridden by use of the smime menu instead. +(Crypto only) +

3.145. pgp_ignore_subkeys

Type: boolean
+Default: yes

+Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, +the principal key will inherit the subkeys' capabilities. Unset this +if you want to play interesting key selection games. +(PGP only) +

3.146. crypt_replyencrypt

Type: boolean
+Default: yes

+If set, automatically PGP or OpenSSL encrypt replies to messages which are +encrypted. +(Crypto only) +

3.147. crypt_replysign

Type: boolean
+Default: no

+If set, automatically PGP or OpenSSL sign replies to messages which are +signed. +

+Note: this does not work on messages that are encrypted +and signed! +(Crypto only) +

3.148. crypt_replysignencrypted

Type: boolean
+Default: no

+If set, automatically PGP or OpenSSL sign replies to messages +which are encrypted. This makes sense in combination with +$crypt_replyencrypt, because it allows you to sign all +messages which are automatically encrypted. This works around +the problem noted in $crypt_replysign, that mutt is not able +to find out whether an encrypted message is also signed. +(Crypto only) +

3.149. crypt_timestamp

Type: boolean
+Default: yes

+If set, mutt will include a time stamp in the lines surrounding +PGP or S/MIME output, so spoofing such lines is more difficult. +If you are using colors to mark these lines, and rely on these, +you may unset this setting. +(Crypto only) +

3.150. sidebar_delim

Type: string
+Default: “|”

+This specifies the delimiter between the sidebar (if visible) and +other screens. +

3.151. sidebar_visible

Type: boolean
+Default: no

+This specifies whether or not to show sidebar (left-side list of folders). +

3.152. sidebar_width

Type: number
+Default: 0

+The width of the sidebar. +

3.153. pgp_use_gpg_agent

Type: boolean
+Default: no

+If set, mutt will use a possibly-running gpg-agent(1) process. +(PGP only) +

3.154. crypt_verify_sig

Type: quadoption
+Default: yes

+If “yes”, always attempt to verify PGP or S/MIME signatures. +If “ask-*”, ask whether or not to verify the signature. +If \Fi“no”, never attempt to verify cryptographic signatures. +(Crypto only) +

3.155. smime_is_default

Type: boolean
+Default: no

+The default behaviour of mutt is to use PGP on all auto-sign/encryption +operations. To override and to use OpenSSL instead this must be set. +However, this has no effect while replying, since mutt will automatically +select the same application that was used to sign/encrypt the original +message. (Note that this variable can be overridden by unsetting $crypt_autosmime.) +(S/MIME only) +

3.156. smime_ask_cert_label

Type: boolean
+Default: yes

+This flag controls whether you want to be asked to enter a label +for a certificate about to be added to the database or not. It is +set by default. +(S/MIME only) +

3.157. smime_decrypt_use_default_key

Type: boolean
+Default: yes

+If set (default) this tells mutt to use the default key for decryption. Otherwise, +if managing multiple certificate-key-pairs, mutt will try to use the mailbox-address +to determine the key to use. It will ask you to supply a key, if it can't find one. +(S/MIME only) +

3.158. pgp_entry_format

Type: string
+Default: “%4n %t%f %4l/0x%k %-4a %2c %u”

+This variable allows you to customize the PGP key selection menu to +your personal taste. This string is similar to $index_format, but +has its own set of printf(3)-like sequences: + +

%n

number +

%k

key id +

%u

user id +

%a

algorithm +

%l

key length +

%f

flags +

%c

capabilities +

%t

trust/validity of the key-uid association +

%[<s>]

date of the key where <s> is an strftime(3) expression +

+(PGP only) +

3.159. pgp_good_sign

Type: regular expression
+Default: (empty)

+If you assign a text to this variable, then a PGP signature is only +considered verified if the output from $pgp_verify_command contains +the text. Use this variable if the exit code from the command is 0 +even for bad signatures. +(PGP only) +

3.160. pgp_check_exit

Type: boolean
+Default: yes

+If set, mutt will check the exit code of the PGP subprocess when +signing or encrypting. A non-zero exit code means that the +subprocess failed. +(PGP only) +

3.161. pgp_long_ids

Type: boolean
+Default: no

+If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs. +(PGP only) +

3.162. pgp_retainable_sigs

Type: boolean
+Default: no

+If set, signed and encrypted messages will consist of nested +multipart/signed and multipart/encrypted body parts. +

+This is useful for applications like encrypted and signed mailing +lists, where the outer layer (multipart/encrypted) can be easily +removed, while the inner multipart/signed part is retained. +(PGP only) +

3.163. pgp_autoinline

Type: boolean
+Default: no

+This option controls whether Mutt generates old-style inline +(traditional) PGP encrypted or signed messages under certain +circumstances. This can be overridden by use of the pgp menu, +when inline is not required. +

+Note that Mutt might automatically use PGP/MIME for messages +which consist of more than a single MIME part. Mutt can be +configured to ask before sending PGP/MIME messages when inline +(traditional) would not work. +

+Also see the $pgp_mime_auto variable. +

+Also note that using the old-style PGP message format is strongly +deprecated. +(PGP only) +

3.164. pgp_replyinline

Type: boolean
+Default: no

+Setting this variable will cause Mutt to always attempt to +create an inline (traditional) message when replying to a +message which is PGP encrypted/signed inline. This can be +overridden by use of the pgp menu, when inline is not +required. This option does not automatically detect if the +(replied-to) message is inline; instead it relies on Mutt +internals for previously checked/flagged messages. +

+Note that Mutt might automatically use PGP/MIME for messages +which consist of more than a single MIME part. Mutt can be +configured to ask before sending PGP/MIME messages when inline +(traditional) would not work. +

+Also see the $pgp_mime_auto variable. +

+Also note that using the old-style PGP message format is strongly +deprecated. +(PGP only) +

3.165. pgp_show_unusable

Type: boolean
+Default: yes

+If set, mutt will display non-usable keys on the PGP key selection +menu. This includes keys which have been revoked, have expired, or +have been marked as “disabled” by the user. +(PGP only) +

3.166. pgp_sign_as

Type: string
+Default: (empty)

+If you have more than one key pair, this option allows you to specify +which of your private keys to use. It is recommended that you use the +keyid form to specify your key (e.g. 0x00112233). +(PGP only) +

3.167. pgp_strict_enc

Type: boolean
+Default: yes

+If set, Mutt will automatically encode PGP/MIME signed messages as +quoted-printable. Please note that unsetting this variable may +lead to problems with non-verifyable PGP signatures, so only change +this if you know what you are doing. +(PGP only) +

3.168. pgp_timeout

Type: number
+Default: 300

+The number of seconds after which a cached passphrase will expire if +not used. +(PGP only) +

3.169. pgp_sort_keys

Type: sort order
+Default: address

+Specifies how the entries in the pgp menu are sorted. The +following are legal values: + +

address

sort alphabetically by user id +

keyid

sort alphabetically by key id +

date

sort by key creation date +

trust

sort by the trust of the key +

+If you prefer reverse order of the above values, prefix it with +“reverse-”. +(PGP only) +

3.170. pgp_mime_auto

Type: quadoption
+Default: ask-yes

+This option controls whether Mutt will prompt you for +automatically sending a (signed/encrypted) message using +PGP/MIME when inline (traditional) fails (for any reason). +

+Also note that using the old-style PGP message format is strongly +deprecated. +(PGP only) +

3.171. pgp_auto_decode

Type: boolean
+Default: no

+If set, mutt will automatically attempt to decrypt traditional PGP +messages whenever the user performs an operation which ordinarily would +result in the contents of the message being operated on. For example, +if the user displays a pgp-traditional message which has not been manually +checked with the <check-traditional-pgp> function, mutt will automatically +check the message for traditional pgp. +

3.172. pgp_mime_signature_filename

Type: string
+Default: “signature.asc”

+This option sets the filename used for signature parts in PGP/MIME +signed messages. +

3.173. pgp_mime_signature_description

Type: string
+Default: “Digital signature”

+This option sets the Content-Description used for signature parts in +PGP/MIME signed messages. +

3.174. pgp_decode_command

Type: string
+Default: (empty)

+This format strings specifies a command which is used to decode +application/pgp attachments. +

+The PGP command formats have their own set of printf(3)-like sequences: + +

%p

Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty +string otherwise. Note: This may be used with a %? construct. +

%f

Expands to the name of a file containing a message. +

%s

Expands to the name of a file containing the signature part + of a multipart/signed attachment when verifying it. +

%a

The value of $pgp_sign_as. +

%r

One or more key IDs. +

+For examples on how to configure these formats for the various versions +of PGP which are floating around, see the pgp and gpg sample configuration files in +the samples/ subdirectory which has been installed on your system +alongside the documentation. +(PGP only) +

3.175. pgp_getkeys_command

Type: string
+Default: (empty)

+This command is invoked whenever mutt will need public key information. +Of the sequences supported by $pgp_decode_command, %r is the only +printf(3)-like sequence used with this format. +(PGP only) +

3.176. pgp_verify_command

Type: string
+Default: (empty)

+This command is used to verify PGP signatures. +

+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. +(PGP only) +

3.177. pgp_decrypt_command

Type: string
+Default: (empty)

+This command is used to decrypt a PGP encrypted message. +

+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. +(PGP only) +

3.178. pgp_clearsign_command

Type: string
+Default: (empty)

+This format is used to create an old-style “clearsigned” PGP +message. Note that the use of this format is strongly +deprecated. +

+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. +(PGP only) +

3.179. pgp_sign_command

Type: string
+Default: (empty)

+This command is used to create the detached PGP signature for a +multipart/signed PGP/MIME body part. +

+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. +(PGP only) +

3.180. pgp_encrypt_sign_command

Type: string
+Default: (empty)

+This command is used to both sign and encrypt a body part. +

+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. +(PGP only) +

3.181. pgp_encrypt_only_command

Type: string
+Default: (empty)

+This command is used to encrypt a body part without signing it. +

+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. +(PGP only) +

3.182. pgp_import_command

Type: string
+Default: (empty)

+This command is used to import a key from a message into +the user's public key ring. +

+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. +(PGP only) +

3.183. pgp_export_command

Type: string
+Default: (empty)

+This command is used to export a public key from the user's +key ring. +

+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. +(PGP only) +

3.184. pgp_verify_key_command

Type: string
+Default: (empty)

+This command is used to verify key information from the key selection +menu. +

+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. +(PGP only) +

3.185. pgp_list_secring_command

Type: string
+Default: (empty)

+This command is used to list the secret key ring's contents. The +output format must be analogous to the one used by: + +

+gpg --list-keys --with-colons.
+
+

+This format is also generated by the pgpring utility which comes +with mutt. +

+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. +(PGP only) +

3.186. pgp_list_pubring_command

Type: string
+Default: (empty)

+This command is used to list the public key ring's contents. The +output format must be analogous to the one used by + +

+gpg --list-keys --with-colons.
+
+

+This format is also generated by the pgpring utility which comes +with mutt. +

+This is a format string, see the $pgp_decode_command command for +possible printf(3)-like sequences. +(PGP only) +

3.187. forward_decrypt

Type: boolean
+Default: yes

+Controls the handling of encrypted messages when forwarding a message. +When set, the outer layer of encryption is stripped off. This +variable is only used if $mime_forward is set and +$mime_forward_decode is unset. +(PGP only) +

3.188. smime_timeout

Type: number
+Default: 300

+The number of seconds after which a cached passphrase will expire if +not used. +(S/MIME only) +

3.189. smime_encrypt_with

Type: string
+Default: (empty)

+This sets the algorithm that should be used for encryption. +Valid choices are “des”, “des3”, “rc2-40”, “rc2-64”, “rc2-128”. +If unset, “3des” (TripleDES) is used. +(S/MIME only) +

3.190. smime_keys

Type: path
+Default: (empty)

+Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle +storage and retrieval of keys/certs by itself. This is very basic right now, +and stores keys and certificates in two different directories, both +named as the hash-value retrieved from OpenSSL. There is an index file +which contains mailbox-address keyid pair, and which can be manually +edited. This option points to the location of the private keys. +(S/MIME only) +

3.191. smime_ca_location

Type: path
+Default: (empty)

+This variable contains the name of either a directory, or a file which +contains trusted certificates for use with OpenSSL. +(S/MIME only) +

+Note: On Debian systems, this defaults to the first existing file in +the following list: ˜/.smime/ca-certificates.crt ˜/.smime/ca-bundle.crt +/etc/ssl/certs/ca-certificates.crt. +

3.192. smime_certificates

Type: path
+Default: (empty)

+Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle +storage and retrieval of keys by itself. This is very basic right +now, and keys and certificates are stored in two different +directories, both named as the hash-value retrieved from +OpenSSL. There is an index file which contains mailbox-address +keyid pairs, and which can be manually edited. This option points to +the location of the certificates. +(S/MIME only) +

3.193. smime_decrypt_command

Type: string
+Default: (empty)

+This format string specifies a command which is used to decrypt +application/x-pkcs7-mime attachments. +

+The OpenSSL command formats have their own set of printf(3)-like sequences +similar to PGP's: + +

%f

Expands to the name of a file containing a message. +

%s

Expands to the name of a file containing the signature part + of a multipart/signed attachment when verifying it. +

%k

The key-pair specified with $smime_default_key +

%c

One or more certificate IDs. +

%a

The algorithm used for encryption. +

%C

CA location: Depending on whether $smime_ca_location + points to a directory or file, this expands to + “-CApath $smime_ca_location” or “-CAfile $smime_ca_location”. +

+For examples on how to configure these formats, see the smime.rc in +the samples/ subdirectory which has been installed on your system +alongside the documentation. +(S/MIME only) +

3.194. smime_verify_command

Type: string
+Default: (empty)

+This command is used to verify S/MIME signatures of type multipart/signed. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.195. smime_verify_opaque_command

Type: string
+Default: (empty)

+This command is used to verify S/MIME signatures of type +application/x-pkcs7-mime. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.196. smime_sign_command

Type: string
+Default: (empty)

+This command is used to created S/MIME signatures of type +multipart/signed, which can be read by all mail clients. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.197. smime_sign_opaque_command

Type: string
+Default: (empty)

+This command is used to created S/MIME signatures of type +application/x-pkcs7-signature, which can only be handled by mail +clients supporting the S/MIME extension. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.198. smime_encrypt_command

Type: string
+Default: (empty)

+This command is used to create encrypted S/MIME messages. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.199. smime_pk7out_command

Type: string
+Default: (empty)

+This command is used to extract PKCS7 structures of S/MIME signatures, +in order to extract the public X509 certificate(s). +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.200. smime_get_cert_command

Type: string
+Default: (empty)

+This command is used to extract X509 certificates from a PKCS7 structure. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.201. smime_get_signer_cert_command

Type: string
+Default: (empty)

+This command is used to extract only the signers X509 certificate from a S/MIME +signature, so that the certificate's owner may get compared to the +email's “From:” field. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.202. smime_import_cert_command

Type: string
+Default: (empty)

+This command is used to import a certificate via smime_keys. +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.203. smime_get_cert_email_command

Type: string
+Default: (empty)

+This command is used to extract the mail address(es) used for storing +X509 certificates, and for verification purposes (to check whether the +certificate was issued for the sender's mailbox). +

+This is a format string, see the $smime_decrypt_command command for +possible printf(3)-like sequences. +(S/MIME only) +

3.204. smime_default_key

Type: string
+Default: (empty)

+This is the default key-pair to use for signing. This must be set to the +keyid (the hash-value that OpenSSL generates) to work properly +(S/MIME only) +

3.205. ssl_client_cert

Type: path
+Default: (empty)

+The file containing a client certificate and its associated private +key. +

3.206. ssl_force_tls

Type: boolean
+Default: no

+If this variable is set, Mutt will require that all connections +to remote servers be encrypted. Furthermore it will attempt to +negotiate TLS even if the server does not advertise the capability, +since it would otherwise have to abort the connection anyway. This +option supersedes $ssl_starttls. +

3.207. ssl_starttls

Type: quadoption
+Default: yes

+If set (the default), mutt will attempt to use STARTTLS on servers +advertising the capability. When unset, mutt will not attempt to +use STARTTLS regardless of the server's capabilities. +

3.208. certificate_file

Type: path
+Default: “˜/.mutt_certificates”

+This variable specifies the file where the certificates you trust +are saved. When an unknown certificate is encountered, you are asked +if you accept it or not. If you accept it, the certificate can also +be saved in this file and further connections are automatically +accepted. +

+You can also manually add CA certificates in this file. Any server +certificate that is signed with one of these CA certificates is +also automatically accepted. +

+Example: + +

+set certificate_file=~/.mutt/certificates
+
+

3.209. ssl_use_sslv3

Type: boolean
+Default: yes

+This variable specifies whether to attempt to use SSLv3 in the +SSL authentication process. +

3.210. ssl_use_tlsv1

Type: boolean
+Default: yes

+This variable specifies whether to attempt to use TLSv1 in the +SSL authentication process. +

3.211. ssl_min_dh_prime_bits

Type: number
+Default: 0

+This variable specifies the minimum acceptable prime size (in bits) +for use in any Diffie-Hellman key exchange. A value of 0 will use +the default from the GNUTLS library. +

3.212. ssl_ca_certificates_file

Type: path
+Default: (empty)

+This variable specifies a file containing trusted CA certificates. +Any server certificate that is signed with one of these CA +certificates is also automatically accepted. +

+Example: + +

+set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
+
+

+Note: On Debian systems, this variable defaults to the example +mentioned. This file is managed by the “ca-certificates” package. +

3.213. pipe_split

Type: boolean
+Default: no

+Used in connection with the <pipe-message> function following +<tag-prefix>. If this variable is unset, when piping a list of +tagged messages Mutt will concatenate the messages and will pipe them +all concatenated. When set, Mutt will pipe the messages one by one. +In both cases the messages are piped in the current sorted order, +and the $pipe_sep separator is added after each message. +

3.214. pipe_decode

Type: boolean
+Default: no

+Used in connection with the <pipe-message> command. When unset, +Mutt will pipe the messages without any preprocessing. When set, Mutt +will weed headers and will attempt to decode the messages +first. +

3.215. pipe_sep

Type: string
+Default: “\n”

+The separator to add between messages when piping a list of tagged +messages to an external Unix command. +

3.216. pop_authenticators

Type: string
+Default: (empty)

+This is a colon-delimited list of authentication methods mutt may +attempt to use to log in to an POP server, in the order mutt should +try them. Authentication methods are either “user”, “apop” or any +SASL mechanism, eg “digest-md5”, “gssapi” or “cram-md5”. +This option is case-insensitive. If this option is unset +(the default) mutt will try all available methods, in order from +most-secure to least-secure. +

+Example: + +

+set pop_authenticators="digest-md5:apop:user"
+
+

3.217. pop_auth_try_all

Type: boolean
+Default: yes

+If set, Mutt will try all available authentication methods. +When unset, Mutt will only fall back to other authentication +methods if the previous methods are unavailable. If a method is +available but authentication fails, Mutt will not connect to the POP server. +

3.218. pop_checkinterval

Type: number
+Default: 60

+This variable configures how often (in seconds) mutt should look for +new mail in the currently selected mailbox if it is a POP mailbox. +

3.219. pop_delete

Type: quadoption
+Default: ask-no

+If set, Mutt will delete successfully downloaded messages from the POP +server when using the <fetch-mail> function. When unset, Mutt will +download messages but also leave them on the POP server. +

3.220. pop_host

Type: string
+Default: (empty)

+The name of your POP server for the <fetch-mail> function. You +can also specify an alternative port, username and password, ie: + +

+[pop[s]://][username[:password]@]popserver[:port]
+
+

+where “[...]” denotes an optional part. +

3.221. pop_last

Type: boolean
+Default: no

+If this variable is set, mutt will try to use the “LAST” POP command +for retrieving only unread messages from the POP server when using +the <fetch-mail> function. +

3.222. pop_reconnect

Type: quadoption
+Default: ask-yes

+Controls whether or not Mutt will try to reconnect to the POP server if +the connection is lost. +

3.223. pop_user

Type: string
+Default: (empty)

+Your login name on the POP server. +

+This variable defaults to your user name on the local machine. +

3.224. pop_pass

Type: string
+Default: (empty)

+Specifies the password for your POP account. If unset, Mutt will +prompt you for your password when you open a POP mailbox. +

+Warning: you should only use this option when you are on a +fairly secure machine, because the superuser can read your muttrc +even if you are the only one who can read the file. +

3.225. post_indent_string

Type: string
+Default: (empty)

+Similar to the $attribution variable, Mutt will append this +string after the inclusion of a message which is being replied to. +

3.226. postpone

Type: quadoption
+Default: ask-yes

+Controls whether or not messages are saved in the $postponed +mailbox when you elect not to send immediately. +

+Also see the $recall variable. +

3.227. postponed

Type: path
+Default: “˜/postponed”

+Mutt allows you to indefinitely “postpone sending a message” which +you are editing. When you choose to postpone a message, Mutt saves it +in the mailbox specified by this variable. +

+Also see the $postpone variable. +

3.228. preconnect

Type: string
+Default: (empty)

+If set, a shell command to be executed if mutt fails to establish +a connection to the server. This is useful for setting up secure +connections, e.g. with ssh(1). If the command returns a nonzero +status, mutt gives up opening the server. Example: + +

+set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \
+sleep 20 < /dev/null > /dev/null"
+
+

+Mailbox “foo” on “mailhost.net” can now be reached +as “{localhost:1234}foo”. +

+Note: For this example to work, you must be able to log in to the +remote machine without having to enter a password. +

+When set, Mutt uses the tunnel for all remote connections. +Please see “account-hook” in the manual for how to use different +tunnel commands per connection. +

3.229. print

Type: quadoption
+Default: ask-no

+Controls whether or not Mutt really prints messages. +This is set to “ask-no” by default, because some people +accidentally hit “p” often. +

3.230. print_command

Type: path
+Default: “lpr”

+This specifies the command pipe that should be used to print messages. +

3.231. print_decode

Type: boolean
+Default: yes

+Used in connection with the <print-message> command. If this +option is set, the message is decoded before it is passed to the +external command specified by $print_command. If this option +is unset, no processing will be applied to the message when +printing it. The latter setting may be useful if you are using +some advanced printer filter which is able to properly format +e-mail messages for printing. +

3.232. print_split

Type: boolean
+Default: no

+Used in connection with the <print-message> command. If this option +is set, the command specified by $print_command is executed once for +each message which is to be printed. If this option is unset, +the command specified by $print_command is executed only once, and +all the messages are concatenated, with a form feed as the message +separator. +

+Those who use the enscript(1) program's mail-printing mode will +most likely want to set this option. +

3.233. prompt_after

Type: boolean
+Default: yes

+If you use an external $pager, setting this variable will +cause Mutt to prompt you for a command when the pager exits rather +than returning to the index menu. If unset, Mutt will return to the +index menu when the external pager exits. +

3.234. query_command

Type: path
+Default: (empty)

+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. +

3.235. query_format

Type: string
+Default: “%4c %t %-25.25a %-25.25n %?e?(%e)?”

+This variable describes the format of the “query” menu. The +following printf(3)-style sequences are understood: + +

%a

destination address +

%c

current entry number +

%e

extra information * +

%n

destination name +

%t

“*” if current entry is tagged, a space otherwise +

%>X

right justify the rest of the string and pad with “X” +

%|X

pad to the end of the line with “X” +

%*X

soft-fill with character “X” as pad +

+For an explanation of “soft-fill”, see the $index_format documentation. +

+* = can be optionally printed if nonzero, see the $status_format documentation. +

3.236. quit

Type: quadoption
+Default: yes

+This variable controls whether “quit” and “exit” actually quit +from mutt. If this option is set, they do quit, if it is unset, 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. +

3.237. quote_regexp

Type: regular expression
+Default: “^([ \t]*[|>:}#])+”

+A regular expression used in the internal pager to determine quoted +sections of text in the body of a message. Quoted text may be filtered +out using the <toggle-quoted> command, or colored according to the +“color quoted” family of directives. +

+Higher levels of quoting may be colored differently (“color quoted1”, +“color quoted2”, etc.). The quoting level is determined by removing +the last character from the matched text and recursively reapplying +the regular expression until it fails to produce a match. +

+Match detection may be overridden by the $smileys regular expression. +

3.238. read_inc

Type: number
+Default: 10

+If set to a value greater than 0, Mutt will display which message it +is currently on when reading a mailbox or when performing search actions +such as search and limit. The message is printed after +this many messages have been read or searched (e.g., if set to 25, Mutt will +print a message when it is at message 25, and then again when it gets +to message 50). This variable is meant to indicate progress when +reading or searching large mailboxes which may take some time. +When set to 0, only a single message will appear before the reading +the mailbox. +

+Also see the $write_inc, $net_inc and $time_inc variables and the +“tuning” section of the manual for performance considerations. +

3.239. read_only

Type: boolean
+Default: no

+If set, all folders are opened in read-only mode. +

3.240. realname

Type: string
+Default: (empty)

+This variable specifies what “real” or “personal” name should be used +when sending messages. +

+By default, this is the GECOS field from /etc/passwd. Note that this +variable will not be used when the user has set a real name +in the $from variable. +

3.241. recall

Type: quadoption
+Default: ask-yes

+Controls whether or not Mutt recalls postponed messages +when composing a new message. +

+Setting this variable to is not generally useful, and thus not +recommended. +

+Also see $postponed variable. +

3.242. record

Type: path
+Default: “˜/sent”

+This specifies the file into which your outgoing messages should be +appended. (This is meant as the primary method for saving a copy of +your messages, but another way to do this is using the “my_hdr” +command to create a “Bcc:” field with your email address in it.) +

+The value of $record is overridden by the $force_name and +$save_name variables, and the “fcc-hook” command. +

3.243. reply_regexp

Type: regular expression
+Default: “^(re([\[0-9\]+])*|aw):[ \t]*”

+A regular expression used to recognize reply messages when threading +and replying. The default value corresponds to the English "Re:" and +the German "Aw:". +

3.244. reply_self

Type: boolean
+Default: no

+If unset and you are replying to a message sent by you, Mutt will +assume that you want to reply to the recipients of that message rather +than to yourself. +

+Also see the “alternates” command. +

3.245. reply_to

Type: quadoption
+Default: ask-yes

+If set, when replying to a message, Mutt will use the address listed +in the Reply-to: header as the recipient of the reply. If unset, +it will use the address in the From: header field instead. This +option is useful for reading a mailing list that sets the Reply-To: +header field to the list address and you want to send a private +message to the author of a message. +

3.246. resolve

Type: boolean
+Default: yes

+When set, the cursor will be automatically advanced to the next +(possibly undeleted) message whenever a command that modifies the +current message is executed. +

3.247. reverse_alias

Type: boolean
+Default: no

+This variable controls whether or not Mutt will display the “personal” +name from your aliases in the index menu if it finds an alias that +matches the message's sender. For example, if you have the following +alias: + +

+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. +

3.248. reverse_name

Type: boolean
+Default: no

+It may sometimes arrive that you receive mail to a certain machine, +move the messages to another machine, and reply to some the messages +from there. If this variable is set, the default From: line of +the reply messages is built using the address where you received the +messages you are replying to if that address matches your +“alternates”. If the variable is unset, or the address that would be +used doesn't match your “alternates”, the From: line will use +your address on the current machine. +

+Also see the “alternates” command. +

3.249. reverse_realname

Type: boolean
+Default: yes

+This variable fine-tunes the behaviour of the $reverse_name feature. +When it is set, mutt will use the address from incoming messages as-is, +possibly including eventual real names. When it is unset, mutt will +override any such real names with the setting of the $realname variable. +

3.250. rfc2047_parameters

Type: boolean
+Default: no

+When this variable is set, Mutt will decode RFC2047-encoded MIME +parameters. You want to set this variable when mutt suggests you +to save attachments to files named like: + +

+=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
+
+

+When this variable is set interactively, the change won't be +active until you change folders. +

+Note that this use of RFC2047's encoding is explicitly +prohibited by the standard, but nevertheless encountered in the +wild. +

+Also note that setting this parameter will not have the effect +that mutt generates this kind of encoding. Instead, mutt will +unconditionally use the encoding specified in RFC2231. +

3.251. save_address

Type: boolean
+Default: no

+If set, mutt will take the sender's full address when choosing a +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. +

3.252. save_empty

Type: boolean
+Default: yes

+When unset, mailboxes which contain no saved messages will be removed +when closed (the exception is $spoolfile which is never removed). +If set, mailboxes are never removed. +

+Note: This only applies to mbox and MMDF folders, Mutt does not +delete MH and Maildir directories. +

3.253. save_history

Type: number
+Default: 0

+This variable controls the size of the history (per category) saved in the +$history_file file. +

3.254. save_name

Type: boolean
+Default: no

+This variable controls how copies of outgoing messages are saved. +When set, a check is made to see if a mailbox specified by the +recipient address exists (this is done by searching for a mailbox in +the $folder directory with the username part of the +recipient address). If the mailbox exists, the outgoing message will +be saved to that mailbox, otherwise the message is saved to the +$record mailbox. +

+Also see the $force_name variable. +

3.255. score

Type: boolean
+Default: yes

+When this variable is unset, scoring is turned off. This can +be useful to selectively disable scoring for certain folders when the +$score_threshold_delete variable and related are used. +

3.256. score_threshold_delete

Type: number
+Default: -1

+Messages which have been assigned a score equal to or lower than the value +of this variable are automatically marked for deletion by mutt. Since +mutt scores are always greater than or equal to zero, the default setting +of this variable will never mark a message for deletion. +

3.257. score_threshold_flag

Type: number
+Default: 9999

+Messages which have been assigned a score greater than or equal to this +variable's value are automatically marked "flagged". +

3.258. score_threshold_read

Type: number
+Default: -1

+Messages which have been assigned a score equal to or lower than the value +of this variable are automatically marked as read by mutt. Since +mutt scores are always greater than or equal to zero, the default setting +of this variable will never mark a message read. +

3.259. send_charset

Type: string
+Default: “us-ascii:iso-8859-1:utf-8”

+A colon-delimited list of character sets for outgoing messages. Mutt will use the +first character set into which the text can be converted exactly. +If your $charset is not “iso-8859-1” and recipients may not +understand “UTF-8”, it is advisable to include in the list an +appropriate widely used standard character set (such as +“iso-8859-2”, “koi8-r” or “iso-2022-jp”) either instead of or after +“iso-8859-1”. +

+In case the text cannot be converted into one of these exactly, +mutt uses $charset as a fallback. +

3.260. sendmail

Type: path
+Default: “/usr/sbin/sendmail -oem -oi”

+Specifies the program and arguments used to deliver mail sent by Mutt. +Mutt expects that the specified program interprets additional +arguments as recipient addresses. +

3.261. sendmail_wait

Type: number
+Default: 0

+Specifies the number of seconds to wait for the $sendmail process +to finish before giving up and putting delivery in the background. +

+Mutt interprets the value of this variable as follows: + +

>0

number of seconds to wait for sendmail to finish before continuing +

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. +

3.262. shell

Type: path
+Default: (empty)

+Command to use when spawning a subshell. By default, the user's login +shell from /etc/passwd is used. +

3.263. sig_dashes

Type: boolean
+Default: yes

+If set, a line containing “-- ” (note the trailing space) will be inserted before your +$signature. It is strongly recommended that you not unset +this variable unless your signature contains just your name. The +reason for this is because many software packages use “-- \n” to +detect your signature. For example, Mutt has the ability to highlight +the signature in a different color in the builtin pager. +

3.264. sig_on_top

Type: boolean
+Default: no

+If set, the signature will be included before any quoted or forwarded +text. It is strongly recommended that you do not set this variable +unless you really know what you are doing, and are prepared to take +some heat from netiquette guardians. +

3.265. signature

Type: path
+Default: “˜/.signature”

+Specifies the filename of your signature, which is appended to all +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 standard output. +

3.266. simple_search

Type: string
+Default: “˜f %s | ˜s %s”

+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 “˜” pattern +operators. See “patterns” 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 by +replacing “%s” with the supplied string. +For the default value, “joe” would be expanded to: “˜f joe | ˜s joe”. +

3.267. smart_wrap

Type: boolean
+Default: yes

+Controls the display of lines longer than the screen width in the +internal pager. If set, long lines are wrapped at a word boundary. If +unset, lines are simply wrapped at the screen edge. Also see the +$markers variable. +

3.268. smileys

Type: regular expression
+Default: “(>From )|(:[-^]?[][)(><}{|/DP])”

+The pager uses this variable to catch some common false +positives of $quote_regexp, most notably smileys and not consider +a line quoted text if it also matches $smileys. This mostly +happens at the beginning of a line. +

3.269. sleep_time

Type: number
+Default: 1

+Specifies time, in seconds, to pause while displaying certain informational +messages, while moving from folder to folder and after expunging +messages from the current folder. The default is to pause one second, so +a value of zero for this option suppresses the pause. +

3.270. smtp_authenticators

Type: string
+Default: (empty)

+This is a colon-delimited list of authentication methods mutt may +attempt to use to log in to an SMTP server, in the order mutt should +try them. Authentication methods are any SASL mechanism, eg +“digest-md5”, “gssapi” or “cram-md5”. +This option is case-insensitive. If it is “unset” +(the default) mutt will try all available methods, in order from +most-secure to least-secure. +

+Example: + +

+set smtp_authenticators="digest-md5:cram-md5"
+
+

3.271. smtp_pass

Type: string
+Default: (empty)

+Specifies the password for your SMTP account. If unset, Mutt will +prompt you for your password when you first send mail via SMTP. +See $smtp_url to configure mutt to send mail via SMTP. +

+Warning: you should only use this option when you are on a +fairly secure machine, because the superuser can read your muttrc even +if you are the only one who can read the file. +

3.272. smtp_url

Type: string
+Default: (empty)

+Defines the SMTP smarthost where sent messages should relayed for +delivery. This should take the form of an SMTP URL, eg: + +

+smtp[s]://[user[:pass]@]host[:port]/
+
+

+\.\.\. where “[...]” denotes an optional part. +Setting this variable overrides the value of the $sendmail +variable. +

3.273. sort

Type: sort order
+Default: date

+Specifies how to sort messages in the “index” menu. Valid values +are: + +

  • date or date-sent +

  • date-received +

  • from +

  • mailbox-order (unsorted) +

  • score +

  • size +

  • spam +

  • subject +

  • threads +

  • to +

+You may optionally use the “reverse-” prefix to specify reverse sorting +order (example: “set sort=reverse-date-sent”). +

+Note: On Debian systems, this option is set by default to +“threads” in /etc/Muttrc. +

3.274. sort_alias

Type: sort order
+Default: alias

+Specifies how the entries in the “alias” menu are sorted. The +following are legal values: + +

  • address (sort alphabetically by email address) +

  • alias (sort alphabetically by alias name) +

  • unsorted (leave in order specified in .muttrc) +

3.275. sort_aux

Type: sort order
+Default: date

+When sorting by threads, this variable controls how threads are sorted +in relation to other threads, and how the branches of the thread trees +are sorted. This can be set to any value that $sort can, except +“threads” (in that case, mutt will just use “date-sent”). You can also +specify the “last-” prefix in addition to the “reverse-” prefix, but “last-” +must come after “reverse-”. The “last-” prefix causes messages to be +sorted against its siblings by which has the last descendant, using +the rest of $sort_aux as an ordering. For instance, + +

+set sort_aux=last-date-received
+
+

+would mean that if a new message is received in a +thread, that thread becomes the last one displayed (or the first, if +you have “set sort=reverse-threads”.) +

+Note: For reversed $sort +order $sort_aux is reversed again (which is not the right thing to do, +but kept to not break any existing configuration setting). +

3.276. sort_browser

Type: sort order
+Default: alpha

+Specifies how to sort entries in the file browser. By default, the +entries are sorted alphabetically. Valid values: + +

  • alpha (alphabetically) +

  • date +

  • size +

  • unsorted +

+You may optionally use the “reverse-” prefix to specify reverse sorting +order (example: “set sort_browser=reverse-date”). +

3.277. sort_re

Type: boolean
+Default: yes

+This variable is only useful when sorting by threads with +$strict_threads unset. In that case, it changes the heuristic +mutt uses to thread messages by subject. With $sort_re set, mutt will +only attach a message as the child of another message by subject if +the subject of the child message starts with a substring matching the +setting of $reply_regexp. With $sort_re unset, mutt will attach +the message whether or not this is the case, as long as the +non-$reply_regexp parts of both messages are identical. +

3.278. spam_separator

Type: string
+Default: “,”

+This variable controls what happens when multiple spam headers +are matched: if unset, each successive header will overwrite any +previous matches value for the spam label. If set, each successive +match will append to the previous, using this variable's value as a +separator. +

3.279. spoolfile

Type: path
+Default: (empty)

+If your spool mailbox is in a non-default place where Mutt cannot find +it, you can specify its location with this variable. Mutt will +automatically set this variable to the value of the environment +variable $MAIL if it is not set. +

3.280. status_chars

Type: string
+Default: “-*%A”

+Controls the characters used by the “%r” indicator in +$status_format. The first character is used when the mailbox is +unchanged. The second is used when the mailbox has been changed, and +it needs to be resynchronized. The third is used if the mailbox is in +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 “%”). The fourth +is used to indicate that the current folder has been opened in attach- +message mode (Certain operations like composing a new mail, replying, +forwarding, etc. are not permitted in this mode). +

3.281. status_format

Type: string
+Default: “-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---”

+Controls the format of the status line displayed in the “index” +menu. This string is similar to $index_format, but has its own +set of printf(3)-like sequences: + +

%b

number of mailboxes with new mail * +

%d

number of deleted messages * +

%f

the full pathname of the current mailbox +

%F

number of flagged messages * +

%h

local hostname +

%l

size (in bytes) of the current mailbox * +

%L

size (in bytes) of the messages shown +(i.e., which match the current limit) * +

%m

the number of messages in the mailbox * +

%M

the number of messages shown (i.e., which match the current limit) * +

%n

number of new messages in the mailbox * +

%o

number of old unread messages * +

%p

number of postponed messages * +

%P

percentage of the way through the index +

%r

modified/read-only/won't-write/attach-message indicator, +according to $status_chars +

%s

current sorting mode ($sort) +

%S

current aux sorting method ($sort_aux) +

%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” +

%*X

soft-fill with character “X” as pad +

+For an explanation of “soft-fill”, see the $index_format documentation. +

+* = 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: +

+%?<sequence_char>?<optional_string>? +

+where sequence_char is a character from the table above, and +optional_string is the string you would like printed if +sequence_char is nonzero. optional_string may contain +other sequences as well as normal text, but you may not nest +optional strings. +

+Here is an example illustrating how to optionally print the number of +new messages in a mailbox: +

+%?n?%n new messages.? +

+You can also switch between two strings using the following construct: +

+%?<sequence_char>?<if_string>&<else_string>? +

+If the value of sequence_char is non-zero, if_string will +be expanded, otherwise else_string will be expanded. +

+You can force the result of any printf(3)-like sequence to be lowercase +by prefixing the sequence character with an underscore (“_”) sign. +For example, if you want to display the local hostname in lowercase, +you would use: “%_h”. +

+If you prefix the sequence character with a colon (“:”) character, mutt +will replace any dots in the expansion by underscores. This might be helpful +with IMAP folders that don't like dots in folder names. +

3.282. status_on_top

Type: boolean
+Default: no

+Setting this variable causes the “status bar” to be displayed on +the first line of the screen rather than near the bottom. If $help +is set, too it'll be placed at the bottom. +

3.283. strict_threads

Type: boolean
+Default: no

+If set, threading will only make use of the “In-Reply-To” and +“References:” fields when you $sort by message threads. By +default, messages with the same subject are grouped together in +“pseudo threads.”. This may not always be desirable, such as in a +personal mailbox where you might have several unrelated messages with +the subjects like “hi” which will get grouped together. See also +$sort_re for a less drastic way of controlling this +behaviour. +

3.284. suspend

Type: boolean
+Default: yes

+When unset, mutt won't stop when the user presses the terminal's +susp key, usually “^Z”. This is useful if you run mutt +inside an xterm using a command like “xterm -e mutt”. +

3.285. text_flowed

Type: boolean
+Default: no

+When set, mutt will generate “format=flowed” bodies with a content type +of “text/plain; format=flowed”. +This format is easier to handle for some mailing software, and generally +just looks like ordinary text. To actually make use of this format's +features, you'll need support in your editor. +

+Note that $indent_string is ignored when this option is set. +

3.286. thread_received

Type: boolean
+Default: no

+When set, mutt uses the date received rather than the date sent +to thread messages by subject. +

3.287. thorough_search

Type: boolean
+Default: no

+Affects the ˜b and ˜h search operations described in +section “patterns”. If set, the headers and body/attachments of +messages to be searched are decoded before searching. If unset, +messages are searched as they appear in the folder. +

+Users searching attachments or for non-ASCII characters should set +this value because decoding also includes MIME parsing/decoding and possible +character set conversions. Otherwise mutt will attempt to match against the +raw message received (for example quoted-printable encoded or with encoded +headers) which may lead to incorrect search results. +

3.288. tilde

Type: boolean
+Default: no

+When set, the internal-pager will pad blank lines to the bottom of the +screen with a tilde (“˜”). +

3.289. time_inc

Type: number
+Default: 0

+Along with $read_inc, $write_inc, and $net_inc, this +variable controls the frequency with which progress updates are +displayed. It suppresses updates less than $time_inc milliseconds +apart. This can improve throughput on systems with slow terminals, +or when running mutt on a remote system. +

+Also see the “tuning” section of the manual for performance considerations. +

3.290. timeout

Type: number
+Default: 600

+When Mutt is waiting for user input either idleing in menus or +in an interactive prompt, Mutt would block until input is +present. Depending on the context, this would prevent certain +operations from working, like checking for new mail or keeping +an IMAP connection alive. +

+This variable controls how many seconds Mutt will at most wait +until it aborts waiting for input, performs these operations and +continues to wait for input. +

+A value of zero or less will cause Mutt to never time out. +

3.291. tmpdir

Type: path
+Default: (empty)

+This variable allows you to specify where Mutt will place its +temporary files needed for displaying and composing messages. If +this variable is not set, the environment variable $TMPDIR is +used. If $TMPDIR is not set then “/tmp” is used. +

3.292. to_chars

Type: string
+Default: “ +TCFL”

+Controls the character used to indicate mail addressed to you. The +first character is the one used when the mail is not addressed to your +address. The second is used when you are the only +recipient of the message. The third is when your address +appears in the “To:” header field, but you are not the only recipient of +the message. The fourth character is used when your +address is specified in the “Cc:” header field, but you are not the only +recipient. The fifth character is used to indicate mail that was sent +by you. The sixth character is used to indicate when a mail +was sent to a mailing-list you subscribe to. +

3.293. trash

Type: path
+Default: (empty)

+If set, this variable specifies the path of the trash folder where the +mails marked for deletion will be moved, instead of being irremediably +purged. +

+NOTE: When you delete a message in the trash folder, it is really +deleted, so that you have a way to clean the trash. +

3.294. tunnel

Type: string
+Default: (empty)

+Setting this variable will cause mutt to open a pipe to a command +instead of a raw socket. You may be able to use this to set up +preauthenticated connections to your IMAP/POP3/SMTP server. Example: + +

+set tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
+
+

+Note: For this example to work you must be able to log in to the remote +machine without having to enter a password. +

3.295. use_8bitmime

Type: boolean
+Default: no

+Warning: do not set this variable unless you are using a version +of sendmail which supports the -B8BITMIME flag (such as sendmail +8.8.x) or you may not be able to send mail. +

+When set, Mutt will invoke $sendmail with the -B8BITMIME +flag when sending 8-bit messages to enable ESMTP negotiation. +

3.296. use_domain

Type: boolean
+Default: yes

+When set, Mutt will qualify all local addresses (ones without the +“@host” portion) with the value of $hostname. If unset, no +addresses will be qualified. +

3.297. use_envelope_from

Type: boolean
+Default: no

+When set, mutt will set the envelope sender of the message. +If $envelope_from_address is set, it will be used as the sender +address. If unset, mutt will attempt to derive the sender from the +“From:” header. +

+Note that this information is passed to sendmail command using the +-f command line switch. Therefore setting this option is not useful +if the $sendmail variable already contains -f or if the +executable pointed to by $sendmail doesn't support the -f switch. +

3.298. use_from

Type: boolean
+Default: yes

+When set, Mutt will generate the “From:” header field when +sending messages. If unset, no “From:” header field will be +generated unless the user explicitly sets one using the “my_hdr” +command. +

3.299. use_idn

Type: boolean
+Default: yes

+When set, Mutt will show you international domain names decoded. +Note: You can use IDNs for addresses even if this is unset. +This variable only affects decoding. +

3.300. use_ipv6

Type: boolean
+Default: yes

+When set, Mutt will look for IPv6 addresses of hosts it tries to +contact. If this option is unset, Mutt will restrict itself to IPv4 addresses. +Normally, the default should work. +

3.301. user_agent

Type: boolean
+Default: yes

+When set, mutt will add a “User-Agent:” header to outgoing +messages, indicating which version of mutt was used for composing +them. +

3.302. visual

Type: path
+Default: (empty)

+Specifies the visual editor to invoke when the “˜v” command is +given in the builtin editor. +

3.303. wait_key

Type: boolean
+Default: yes

+Controls whether Mutt will ask you to press a key after an external command +has been invoked by these functions: <shell-escape>, +<pipe-message>, <pipe-entry>, <print-message>, +and <print-entry> commands. +

+It is also used when viewing attachments with “auto_view”, provided +that the corresponding mailcap entry has a needsterminal flag, +and the external program is interactive. +

+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. +

3.304. weed

Type: boolean
+Default: yes

+When set, mutt will weed headers when displaying, forwarding, +printing, or replying to messages. +

3.305. wrap

Type: number
+Default: 0

+When set to a positive value, mutt will wrap text at $wrap characters. +When set to a negative value, mutt will wrap text so that there are $wrap +characters of empty space on the right side of the terminal. +

3.306. wrap_search

Type: boolean
+Default: yes

+Controls whether searches wrap around the end. +

+When set, searches will wrap around the first (or last) item. When +unset, incremental searches will not wrap. +

3.307. wrapmargin

Type: number
+Default: 0

+(DEPRECATED) Equivalent to setting $wrap with a negative value. +

3.308. write_inc

Type: number
+Default: 10

+When writing a mailbox, a message will be printed every +$write_inc messages to indicate progress. If set to 0, only a +single message will be displayed before writing a mailbox. +

+Also see the $read_inc, $net_inc and $time_inc variables and the +“tuning” section of the manual for performance considerations. +

3.309. write_bcc

Type: boolean
+Default: yes

+Controls whether mutt writes out the “Bcc:” header when preparing +messages to be sent. Exim users may wish to unset this. If mutt +is set to deliver directly via SMTP (see $smtp_url), this +option does nothing: mutt will never write out the “Bcc:” header +in this case. +

+Note: On Debian systems, exim4 and postfix strip BCC headers by +default. The above warning applies to exim3 users, see /etc/Muttrc. +

3.310. xterm_icon

Type: string
+Default: “M%?n?AIL&ail?”

+Controls the format of the icon title, as long as xterm_set_titles +is enabled. This string is identical in formatting to the one used by +“$status_format”. +

3.311. xterm_set_titles

Type: boolean
+Default: no

+Controls whether mutt sets the xterm title bar and icon name +(as long as you are in an appropriate terminal). +

3.312. xterm_title

Type: string
+Default: “Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?”

+Controls the format of the title bar of the xterm provided that +xterm_set_titles has been set. This string is identical in formatting +to the one used by “$status_format”. +

4. Functions

+The following is the list of available functions listed by the mapping +in which they are available. The default key setting is given, and an +explanation of what the function does. The key bindings of these +functions can be changed with the bind +command. +

4.1. generic menu

+The generic menu is not a real menu, but specifies common functions +(such as movement) available in all menus except for pager and +editor. Changing settings for this menu will affect the default +bindings for all menus (except as noted). +

Table 8.2. Default generic function bindings

FunctionDefault keyDescription
<top-page>Hmove to the top of the page
<next-entry>jmove to the next entry
<previous-entry>kmove to the previous entry
<bottom-page>Lmove to the bottom of the page
<refresh>^Lclear and redraw the screen
<middle-page>Mmove to the middle of the page
<search-next>nsearch for next match
<exit>qexit this menu
<tag-entry>ttag the current entry
<next-page>zmove to the next page
<previous-page>Zmove to the previous page
<last-entry>*move to the last entry
<first-entry>=move to the first entry
<enter-command>:enter a muttrc command
<next-line>>scroll down one line
<previous-line><scroll up one line
<half-up>[scroll up 1/2 page
<half-down>]scroll down 1/2 page
<help>?this screen
<tag-prefix>;apply next function to tagged messages
<tag-prefix-cond> apply next function ONLY to tagged messages
<end-cond> end of conditional execution (noop)
<shell-escape>!invoke a command in a subshell
<select-entry><Return>select the current entry
<search>/search for a regular expression
<search-reverse>Esc /search backwards for a regular expression
<search-opposite> search for next match in opposite direction
<jump> jump to an index number
<current-top> move entry to top of screen
<current-middle> move entry to middle of screen
<current-bottom> move entry to bottom of screen
<what-key> display the keycode for a key press

4.2. index menu

Table 8.3. Default index function bindings

FunctionDefault keyDescription
<create-alias>acreate an alias from a message sender
<bounce-message>bremail a message to another user
<break-thread>#break the thread in two
<change-folder>copen a different folder
<change-folder-readonly>Esc copen a different folder in read only mode
<next-unread-mailbox> open next mailbox with new mail
<collapse-thread>Esc vcollapse/uncollapse current thread
<collapse-all>Esc Vcollapse/uncollapse all threads
<copy-message>Ccopy a message to a file/mailbox
<decode-copy>Esc Cmake decoded (text/plain) copy
<decode-save>Esc smake decoded copy (text/plain) and delete
<delete-message>ddelete the current entry
<delete-pattern>Ddelete messages matching a pattern
<delete-thread>^Ddelete all messages in thread
<delete-subthread>Esc ddelete all messages in subthread
<edit>eedit the raw message
<edit-type>^Eedit attachment content type
<forward-message>fforward a message with comments
<flag-message>Ftoggle a message's 'important' flag
<group-reply>greply to all recipients
<fetch-mail>Gretrieve mail from POP server
<imap-fetch-mail> force retrieval of mail from IMAP server
<display-toggle-weed>hdisplay message and toggle header weeding
<next-undeleted>jmove to the next undeleted message
<previous-undeleted>kmove to the previous undeleted message
<limit>lshow only messages matching a pattern
<link-threads>&link tagged message to the current one
<list-reply>Lreply to specified mailing list
<mail>mcompose a new mail message
<toggle-new>Ntoggle a message's 'new' flag
<toggle-write>%toggle whether the mailbox will be rewritten
<next-thread>^Njump to the next thread
<next-subthread>Esc njump to the next subthread
<purge-message> really delete the current entry, bypassing the trash folder
<query>Qquery external program for addresses
<quit>qsave changes to mailbox and quit
<reply>rreply to a message
<show-limit>Esc lshow currently active limit pattern
<sort-mailbox>osort messages
<sort-reverse>Osort messages in reverse order
<print-message>pprint the current entry
<previous-thread>^Pjump to previous thread
<previous-subthread>Esc pjump to previous subthread
<recall-message>Rrecall a postponed message
<read-thread>^Rmark the current thread as read
<read-subthread>Esc rmark the current subthread as read
<resend-message>Esc euse the current message as a template for a new one
<save-message>ssave message/attachment to a file
<tag-pattern>Ttag messages matching a pattern
<tag-subthread> tag the current subthread
<tag-thread>Esc ttag the current thread
<untag-pattern>^Tuntag messages matching a pattern
<undelete-message>uundelete the current entry
<undelete-pattern>Uundelete messages matching a pattern
<undelete-subthread>Esc uundelete all messages in subthread
<undelete-thread>^Uundelete all messages in thread
<view-attachments>vshow MIME attachments
<show-version>Vshow the Mutt version number and date
<set-flag>wset a status flag on a message
<clear-flag>Wclear a status flag from a message
<display-message><Return>display a message
<buffy-list>.list mailboxes with new mail
<sync-mailbox>$save changes to mailbox
<display-address>@display full address of sender
<pipe-message>|pipe message/attachment to a shell command
<next-new> jump to the next new message
<next-new-then-unread><Tab>jump to the next new or unread message
<previous-new> jump to the previous new message
<previous-new-then-unread>Esc <Tab>jump to the previous new or unread message
<next-unread> jump to the next unread message
<previous-unread> jump to the previous unread message
<parent-message>Pjump to parent message in thread
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory
<check-traditional-pgp>Esc Pcheck for classic PGP
<mail-key>Esc kmail a PGP public key
<decrypt-copy> make decrypted copy
<decrypt-save> make decrypted copy and delete
<sidebar-scroll-up> scroll the mailbox pane up 1 page
<sidebar-scroll-down> scroll the mailbox pane down 1 page
<sidebar-next> go down to next mailbox
<sidebar-prev> go to previous mailbox
<sidebar-open> open hilighted mailbox

4.3. pager menu

Table 8.4. Default pager function bindings

FunctionDefault keyDescription
<break-thread>#break the thread in two
<create-alias>acreate an alias from a message sender
<bounce-message>bremail a message to another user
<change-folder>copen a different folder
<change-folder-readonly>Esc copen a different folder in read only mode
<next-unread-mailbox> open next mailbox with new mail
<copy-message>Ccopy a message to a file/mailbox
<decode-copy>Esc Cmake decoded (text/plain) copy
<delete-message>ddelete the current entry
<delete-thread>^Ddelete all messages in thread
<delete-subthread>Esc ddelete all messages in subthread
<edit>eedit the raw message
<edit-type>^Eedit attachment content type
<forward-message>fforward a message with comments
<flag-message>Ftoggle a message's 'important' flag
<group-reply>greply to all recipients
<imap-fetch-mail> force retrieval of mail from IMAP server
<display-toggle-weed>hdisplay message and toggle header weeding
<next-undeleted>jmove to the next undeleted message
<next-entry>Jmove to the next entry
<previous-undeleted>kmove to the previous undeleted message
<previous-entry>Kmove to the previous entry
<link-threads>&link tagged message to the current one
<list-reply>Lreply to specified mailing list
<redraw-screen>^Lclear and redraw the screen
<mail>mcompose a new mail message
<mark-as-new>Ntoggle a message's 'new' flag
<search-next>nsearch for next match
<next-thread>^Njump to the next thread
<next-subthread>Esc njump to the next subthread
<print-message>pprint the current entry
<previous-thread>^Pjump to previous thread
<previous-subthread>Esc pjump to previous subthread
<purge-message> really delete the current entry, bypassing the trash folder
<quit>Qsave changes to mailbox and quit
<exit>qexit this menu
<reply>rreply to a message
<recall-message>Rrecall a postponed message
<read-thread>^Rmark the current thread as read
<read-subthread>Esc rmark the current subthread as read
<resend-message>Esc euse the current message as a template for a new one
<save-message>ssave message/attachment to a file
<skip-quoted>Sskip beyond quoted text
<decode-save>Esc smake decoded copy (text/plain) and delete
<tag-message>ttag the current entry
<toggle-quoted>Ttoggle display of quoted text
<undelete-message>uundelete the current entry
<undelete-subthread>Esc uundelete all messages in subthread
<undelete-thread>^Uundelete all messages in thread
<view-attachments>vshow MIME attachments
<show-version>Vshow the Mutt version number and date
<search-toggle>\\toggle search pattern coloring
<display-address>@display full address of sender
<next-new> jump to the next new message
<pipe-message>|pipe message/attachment to a shell command
<help>?this screen
<next-page><Space>move to the next page
<previous-page>-move to the previous page
<top>^jump to the top of the message
<sync-mailbox>$save changes to mailbox
<shell-escape>!invoke a command in a subshell
<enter-command>:enter a muttrc command
<buffy-list>.list mailboxes with new mail
<search>/search for a regular expression
<search-reverse>Esc /search backwards for a regular expression
<search-opposite> search for next match in opposite direction
<next-line><Return>scroll down one line
<jump> jump to an index number
<next-unread> jump to the next unread message
<previous-new> jump to the previous new message
<previous-unread> jump to the previous unread message
<half-up> scroll up 1/2 page
<half-down> scroll down 1/2 page
<previous-line> scroll up one line
<bottom> jump to the bottom of the message
<parent-message>Pjump to parent message in thread
<check-traditional-pgp>Esc Pcheck for classic PGP
<mail-key>Esc kmail a PGP public key
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory
<decrypt-copy> make decrypted copy
<decrypt-save> make decrypted copy and delete
<what-key> display the keycode for a key press
<sidebar-scroll-up> scroll the mailbox pane up 1 page
<sidebar-scroll-down> scroll the mailbox pane down 1 page
<sidebar-next> go down to next mailbox
<sidebar-prev> go to previous mailbox
<sidebar-open> open hilighted mailbox

4.4. alias menu

Table 8.5. Default alias function bindings

FunctionDefault keyDescription
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry

4.5. query menu

Table 8.6. Default query function bindings

FunctionDefault keyDescription
<create-alias>acreate an alias from a message sender
<mail>mcompose a new mail message
<query>Qquery external program for addresses
<query-append>Aappend new query results to current results

4.6. attach menu

Table 8.7. Default attach function bindings

FunctionDefault keyDescription
<bounce-message>bremail a message to another user
<display-toggle-weed>hdisplay message and toggle header weeding
<edit-type>^Eedit attachment content type
<print-entry>pprint the current entry
<save-entry>ssave message/attachment to a file
<pipe-entry>|pipe message/attachment to a shell command
<view-mailcap>mforce viewing of attachment using mailcap
<reply>rreply to a message
<resend-message>Esc euse the current message as a template for a new one
<group-reply>greply to all recipients
<list-reply>Lreply to specified mailing list
<forward-message>fforward a message with comments
<view-text>Tview attachment as text
<view-attach><Return>view attachment using mailcap entry if necessary
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry
<collapse-parts>vToggle display of subparts
<check-traditional-pgp>Esc Pcheck for classic PGP
<extract-keys>^Kextract supported public keys
<forget-passphrase>^Fwipe passphrase(s) from memory

4.7. compose menu

Table 8.8. Default compose function bindings

FunctionDefault keyDescription
<attach-file>aattach file(s) to this message
<attach-message>Aattach message(s) to this message
<edit-bcc>bedit the BCC list
<edit-cc>cedit the CC list
<copy-file>Csave message/attachment to a file
<detach-file>Ddelete the current entry
<toggle-disposition>^Dtoggle disposition between inline/attachment
<edit-description>dedit attachment description
<edit-message>eedit the message
<edit-headers>Eedit the message with headers
<edit-file>^X eedit the file to be attached
<edit-encoding>^Eedit attachment transfer-encoding
<edit-from>Esc fedit the from field
<edit-fcc>fenter a file to save a copy of this message in
<filter-entry>Ffilter attachment through a shell command
<get-attachment>Gget a temporary copy of an attachment
<display-toggle-weed>hdisplay message and toggle header weeding
<ispell>irun ispell on the message
<print-entry>lprint the current entry
<edit-mime>medit attachment using mailcap entry
<new-mime>ncompose new attachment using mailcap entry
<postpone-message>Psave this message to send later
<edit-reply-to>redit the Reply-To field
<rename-file>Rrename/move an attached file
<edit-subject>sedit the subject of this message
<edit-to>tedit the TO list
<edit-type>^Tedit attachment content type
<write-fcc>wwrite the message to a folder
<toggle-unlink>utoggle whether to delete file after sending it
<toggle-recode> toggle recoding of this attachment
<update-encoding>Uupdate an attachment's encoding info
<view-attach><Return>view attachment using mailcap entry if necessary
<send-message>ysend the message
<pipe-entry>|pipe message/attachment to a shell command
<attach-key>Esc kattach a PGP public key
<pgp-menu>pshow PGP options
<forget-passphrase>^Fwipe passphrase(s) from memory
<smime-menu>Sshow S/MIME options
<mix>Msend the message through a mixmaster remailer chain

4.8. postpone menu

Table 8.9. Default postpone function bindings

FunctionDefault keyDescription
<delete-entry>ddelete the current entry
<undelete-entry>uundelete the current entry

4.9. browser menu

Table 8.10. Default browser function bindings

FunctionDefault keyDescription
<change-dir>cchange directories
<display-filename>@display the currently selected file's name
<enter-mask>menter a file mask
<sort>osort messages
<sort-reverse>Osort messages in reverse order
<select-new>Nselect a new file in this directory
<check-new> check mailboxes for new mail
<toggle-mailboxes><Tab>toggle whether to browse mailboxes or all files
<view-file><Space>view file
<buffy-list>.list mailboxes with new mail
<create-mailbox>Ccreate a new mailbox (IMAP only)
<delete-mailbox>ddelete the current mailbox (IMAP only)
<rename-mailbox>rrename the current mailbox (IMAP only)
<subscribe>ssubscribe to current mailbox (IMAP only)
<unsubscribe>uunsubscribe from current mailbox (IMAP only)
<toggle-subscribed>Ttoggle view all/subscribed mailboxes (IMAP only)

4.10. pgp menu

Table 8.11. Default pgp function bindings

FunctionDefault keyDescription
<verify-key>cverify a PGP public key
<view-name>%view the key's user id

4.11. smime menu

Table 8.12. Default smime function bindings

FunctionDefault keyDescription
<verify-key>cverify a PGP public key
<view-name>%view the key's user id

4.12. mix menu

Table 8.13. Default mix function bindings

FunctionDefault keyDescription
<accept><Return>Accept the chain constructed
<append>aAppend a remailer to the chain
<insert>iInsert a remailer into the chain
<delete>dDelete a remailer from the chain
<chain-prev><Left>Select the previous element of the chain
<chain-next><Right>Select the next element of the chain

4.13. editor menu

Table 8.14. Default editor function bindings

FunctionDefault keyDescription
<bol>^Ajump to the beginning of the line
<backward-char>^Bmove the cursor one character to the left
<backward-word>Esc bmove the cursor to the beginning of the word
<capitalize-word>Esc ccapitalize the word
<downcase-word>Esc lconvert the word to lower case
<upcase-word>Esc uconvert the word to upper case
<delete-char>^Ddelete the char under the cursor
<eol>^Ejump to the end of the line
<forward-char>^Fmove the cursor one character to the right
<forward-word>Esc fmove the cursor to the end of the word
<backspace><Backspace>delete the char in front of the cursor
<kill-eol>^Kdelete chars from cursor to end of line
<kill-eow>Esc ddelete chars from the cursor to the end of the word
<kill-line>^Udelete all chars on the line
<quote-char>^Vquote the next typed key
<kill-word>^Wdelete the word in front of the cursor
<complete><Tab>complete filename or alias
<complete-query>^Tcomplete address with query
<buffy-cycle><Space>cycle among incoming mailboxes
<history-up> scroll up through the history list
<history-down> scroll down through the history list
<transpose-chars> transpose character under cursor with previous

Chapter 9. Miscellany

Table of Contents

1. Acknowledgements
2. About this document

1. Acknowledgements

+Kari Hurtta +co-developed the original MIME parsing code back in the ELM-ME days. +

+The following people have been very helpful to the development of Mutt: +

2. About this document

+This document was written in DocBook, +and then rendered using the Gnome XSLT toolkit. +

diff --git a/obj-i486-linux-gnu-patched/doc/manual.txt b/obj-i486-linux-gnu-patched/doc/manual.txt new file mode 100644 index 0000000..63f0322 --- /dev/null +++ b/obj-i486-linux-gnu-patched/doc/manual.txt @@ -0,0 +1,11584 @@ + The Mutt E-Mail Client + + Michael Elkins + + + + version 1.5.19 (2009-01-05) + + Abstract + + "All mail clients suck. This one just sucks less." -me, circa 1995 + + ---------------------------------------------------------------------- + + Table of Contents + + 1. Introduction + + 1. Mutt Home Page + + 2. Mailing Lists + + 3. Software Distribution Sites + + 4. Mutt online resources + + 5. Contributing to Mutt + + 6. Typograhical conventions + + 7. Copyright + + 2. Getting Started + + 1. Core concepts + + 2. Moving Around in Menus + + 3. Editing Input Fields + + 3.1. Introduction + + 3.2. History + + 4. Reading Mail - The Index and Pager + + 4.1. The Message Index + + 4.2. The Pager + + 4.3. Threaded Mode + + 4.4. Miscellaneous Functions + + 5. Sending Mail + + 5.1. Introduction + + 5.2. Editing the message header + + 5.3. Sending cryptographically signed/encrypted + messages + + 5.4. Sending anonymous messages via mixmaster + + 5.5. Sending format=flowed messages + + 6. Forwarding and Bouncing Mail + + 7. Postponing Mail + + 3. Configuration + + 1. Location of initialization files + + 2. Syntax of Initialization Files + + 3. Address groups + + 4. Defining/Using aliases + + 5. Changing the default key bindings + + 6. Defining aliases for character sets + + 7. Setting variables based upon mailbox + + 8. Keyboard macros + + 9. Using color and mono video attributes + + 10. Message header display + + 11. Alternative addresses + + 12. Mailing lists + + 13. Using Multiple spool mailboxes + + 14. Monitoring incoming mail + + 15. User defined headers + + 16. Specify default save mailbox + + 17. Specify default Fcc: mailbox when composing + + 18. Specify default save filename and default Fcc: mailbox at + once + + 19. Change settings based upon message recipients + + 20. Change settings before formatting a message + + 21. Choosing the cryptographic key of the recipient + + 22. Adding key sequences to the keyboard buffer + + 23. Executing functions + + 24. Message Scoring + + 25. Spam detection + + 26. Setting and Querying Variables + + 26.1. Commands + + 26.2. User-defined variables + + 27. Reading initialization commands from another file + + 28. Configuring features conditionnaly + + 29. Removing hooks + + 30. Format Strings + + 30.1. Basic usage + + 30.2. Filters + + 4. Advanced Usage + + 1. Regular Expressions + + 2. Patterns: Searching, Limiting and Tagging + + 2.1. Pattern Modifier + + 2.2. Simple Patterns + + 2.3. Complex Patterns + + 2.4. Searching by Date + + 3. Using Tags + + 4. Using Hooks + + 4.1. Message Matching in Hooks + + 5. External Address Queries + + 6. Mailbox Formats + + 7. Mailbox Shortcuts + + 8. Handling Mailing Lists + + 9. Handling multiple folders + + 10. Editing threads + + 10.1. Linking threads + + 10.2. Breaking threads + + 11. Delivery Status Notification (DSN) Support + + 12. Start a WWW Browser on URLs + + 5. Mutt's MIME Support + + 1. Using MIME in Mutt + + 1.1. Viewing MIME messages in the pager + + 1.2. The Attachment Menu + + 1.3. The Compose Menu + + 2. MIME Type configuration with mime.types + + 3. MIME Viewer configuration with mailcap + + 3.1. The Basics of the mailcap file + + 3.2. Secure use of mailcap + + 3.3. Advanced mailcap Usage + + 3.4. Example mailcap files + + 4. MIME Autoview + + 5. MIME Multipart/Alternative + + 6. Attachment Searching and Counting + + 7. MIME Lookup + + 6. Optional features + + 1. General notes + + 1.1. Enabling/disabling features + + 1.2. URL syntax + + 2. SSL/TLS Support + + 3. POP3 Support + + 4. IMAP Support + + 4.1. The Folder Browser + + 4.2. Authentication + + 5. SMTP Support + + 6. Managing multiple accounts + + 7. Local caching + + 7.1. Header caching + + 7.2. Body caching + + 7.3. Maintenance + + 8. Exact address generation + + 7. Performance tuning + + 1. Reading and writing mailboxes + + 2. Reading messages from remote folders + + 3. Searching and limiting + + 8. Reference + + 1. Command line options + + 2. Configuration Commands + + 3. Configuration variables + + 3.1. abort_nosubject + + 3.2. abort_unmodified + + 3.3. alias_file + + 3.4. alias_format + + 3.5. allow_8bit + + 3.6. allow_ansi + + 3.7. arrow_cursor + + 3.8. ascii_chars + + 3.9. askbcc + + 3.10. askcc + + 3.11. assumed_charset + + 3.12. attach_charset + + 3.13. attach_format + + 3.14. attach_sep + + 3.15. attach_split + + 3.16. attribution + + 3.17. autoedit + + 3.18. auto_tag + + 3.19. beep + + 3.20. beep_new + + 3.21. bounce + + 3.22. bounce_delivered + + 3.23. braille_friendly + + 3.24. check_mbox_size + + 3.25. charset + + 3.26. check_new + + 3.27. collapse_unread + + 3.28. uncollapse_jump + + 3.29. compose_format + + 3.30. config_charset + + 3.31. confirmappend + + 3.32. confirmcreate + + 3.33. connect_timeout + + 3.34. content_type + + 3.35. copy + + 3.36. crypt_use_gpgme + + 3.37. crypt_use_pka + + 3.38. crypt_autopgp + + 3.39. crypt_autosmime + + 3.40. date_format + + 3.41. default_hook + + 3.42. delete + + 3.43. delete_untag + + 3.44. digest_collapse + + 3.45. display_filter + + 3.46. dotlock_program + + 3.47. dsn_notify + + 3.48. dsn_return + + 3.49. duplicate_threads + + 3.50. edit_headers + + 3.51. editor + + 3.52. encode_from + + 3.53. envelope_from_address + + 3.54. escape + + 3.55. fast_reply + + 3.56. fcc_attach + + 3.57. fcc_clear + + 3.58. folder + + 3.59. folder_format + + 3.60. followup_to + + 3.61. force_name + + 3.62. forward_decode + + 3.63. forward_edit + + 3.64. forward_format + + 3.65. forward_quote + + 3.66. from + + 3.67. gecos_mask + + 3.68. hdrs + + 3.69. header + + 3.70. help + + 3.71. hidden_host + + 3.72. hide_limited + + 3.73. hide_missing + + 3.74. hide_thread_subject + + 3.75. hide_top_limited + + 3.76. hide_top_missing + + 3.77. history + + 3.78. history_file + + 3.79. honor_followup_to + + 3.80. hostname + + 3.81. ignore_linear_white_space + + 3.82. ignore_list_reply_to + + 3.83. imap_authenticators + + 3.84. imap_check_subscribed + + 3.85. imap_delim_chars + + 3.86. imap_headers + + 3.87. imap_idle + + 3.88. imap_keepalive + + 3.89. imap_list_subscribed + + 3.90. imap_login + + 3.91. imap_pass + + 3.92. imap_passive + + 3.93. imap_peek + + 3.94. imap_pipeline_depth + + 3.95. imap_servernoise + + 3.96. imap_user + + 3.97. implicit_autoview + + 3.98. include + + 3.99. include_onlyfirst + + 3.100. indent_string + + 3.101. index_format + + 3.102. ispell + + 3.103. keep_flagged + + 3.104. locale + + 3.105. mail_check + + 3.106. mailcap_path + + 3.107. mailcap_sanitize + + 3.108. maildir_mtime + + 3.109. header_cache + + 3.110. maildir_header_cache_verify + + 3.111. header_cache_pagesize + + 3.112. maildir_trash + + 3.113. mark_old + + 3.114. markers + + 3.115. mask + + 3.116. mbox + + 3.117. mbox_type + + 3.118. metoo + + 3.119. menu_context + + 3.120. menu_move_off + + 3.121. menu_scroll + + 3.122. meta_key + + 3.123. mh_purge + + 3.124. mh_seq_flagged + + 3.125. mh_seq_replied + + 3.126. mh_seq_unseen + + 3.127. mime_forward + + 3.128. mime_forward_decode + + 3.129. mime_forward_rest + + 3.130. mix_entry_format + + 3.131. mixmaster + + 3.132. move + + 3.133. message_cachedir + + 3.134. message_cache_clean + + 3.135. message_format + + 3.136. narrow_tree + + 3.137. net_inc + + 3.138. pager + + 3.139. pager_context + + 3.140. pager_format + + 3.141. pager_index_lines + + 3.142. pager_stop + + 3.143. crypt_autosign + + 3.144. crypt_autoencrypt + + 3.145. pgp_ignore_subkeys + + 3.146. crypt_replyencrypt + + 3.147. crypt_replysign + + 3.148. crypt_replysignencrypted + + 3.149. crypt_timestamp + + 3.150. sidebar_delim + + 3.151. sidebar_visible + + 3.152. sidebar_width + + 3.153. pgp_use_gpg_agent + + 3.154. crypt_verify_sig + + 3.155. smime_is_default + + 3.156. smime_ask_cert_label + + 3.157. smime_decrypt_use_default_key + + 3.158. pgp_entry_format + + 3.159. pgp_good_sign + + 3.160. pgp_check_exit + + 3.161. pgp_long_ids + + 3.162. pgp_retainable_sigs + + 3.163. pgp_autoinline + + 3.164. pgp_replyinline + + 3.165. pgp_show_unusable + + 3.166. pgp_sign_as + + 3.167. pgp_strict_enc + + 3.168. pgp_timeout + + 3.169. pgp_sort_keys + + 3.170. pgp_mime_auto + + 3.171. pgp_auto_decode + + 3.172. pgp_mime_signature_filename + + 3.173. pgp_mime_signature_description + + 3.174. pgp_decode_command + + 3.175. pgp_getkeys_command + + 3.176. pgp_verify_command + + 3.177. pgp_decrypt_command + + 3.178. pgp_clearsign_command + + 3.179. pgp_sign_command + + 3.180. pgp_encrypt_sign_command + + 3.181. pgp_encrypt_only_command + + 3.182. pgp_import_command + + 3.183. pgp_export_command + + 3.184. pgp_verify_key_command + + 3.185. pgp_list_secring_command + + 3.186. pgp_list_pubring_command + + 3.187. forward_decrypt + + 3.188. smime_timeout + + 3.189. smime_encrypt_with + + 3.190. smime_keys + + 3.191. smime_ca_location + + 3.192. smime_certificates + + 3.193. smime_decrypt_command + + 3.194. smime_verify_command + + 3.195. smime_verify_opaque_command + + 3.196. smime_sign_command + + 3.197. smime_sign_opaque_command + + 3.198. smime_encrypt_command + + 3.199. smime_pk7out_command + + 3.200. smime_get_cert_command + + 3.201. smime_get_signer_cert_command + + 3.202. smime_import_cert_command + + 3.203. smime_get_cert_email_command + + 3.204. smime_default_key + + 3.205. ssl_client_cert + + 3.206. ssl_force_tls + + 3.207. ssl_starttls + + 3.208. certificate_file + + 3.209. ssl_use_sslv3 + + 3.210. ssl_use_tlsv1 + + 3.211. ssl_min_dh_prime_bits + + 3.212. ssl_ca_certificates_file + + 3.213. pipe_split + + 3.214. pipe_decode + + 3.215. pipe_sep + + 3.216. pop_authenticators + + 3.217. pop_auth_try_all + + 3.218. pop_checkinterval + + 3.219. pop_delete + + 3.220. pop_host + + 3.221. pop_last + + 3.222. pop_reconnect + + 3.223. pop_user + + 3.224. pop_pass + + 3.225. post_indent_string + + 3.226. postpone + + 3.227. postponed + + 3.228. preconnect + + 3.229. print + + 3.230. print_command + + 3.231. print_decode + + 3.232. print_split + + 3.233. prompt_after + + 3.234. query_command + + 3.235. query_format + + 3.236. quit + + 3.237. quote_regexp + + 3.238. read_inc + + 3.239. read_only + + 3.240. realname + + 3.241. recall + + 3.242. record + + 3.243. reply_regexp + + 3.244. reply_self + + 3.245. reply_to + + 3.246. resolve + + 3.247. reverse_alias + + 3.248. reverse_name + + 3.249. reverse_realname + + 3.250. rfc2047_parameters + + 3.251. save_address + + 3.252. save_empty + + 3.253. save_history + + 3.254. save_name + + 3.255. score + + 3.256. score_threshold_delete + + 3.257. score_threshold_flag + + 3.258. score_threshold_read + + 3.259. send_charset + + 3.260. sendmail + + 3.261. sendmail_wait + + 3.262. shell + + 3.263. sig_dashes + + 3.264. sig_on_top + + 3.265. signature + + 3.266. simple_search + + 3.267. smart_wrap + + 3.268. smileys + + 3.269. sleep_time + + 3.270. smtp_authenticators + + 3.271. smtp_pass + + 3.272. smtp_url + + 3.273. sort + + 3.274. sort_alias + + 3.275. sort_aux + + 3.276. sort_browser + + 3.277. sort_re + + 3.278. spam_separator + + 3.279. spoolfile + + 3.280. status_chars + + 3.281. status_format + + 3.282. status_on_top + + 3.283. strict_threads + + 3.284. suspend + + 3.285. text_flowed + + 3.286. thread_received + + 3.287. thorough_search + + 3.288. tilde + + 3.289. time_inc + + 3.290. timeout + + 3.291. tmpdir + + 3.292. to_chars + + 3.293. trash + + 3.294. tunnel + + 3.295. use_8bitmime + + 3.296. use_domain + + 3.297. use_envelope_from + + 3.298. use_from + + 3.299. use_idn + + 3.300. use_ipv6 + + 3.301. user_agent + + 3.302. visual + + 3.303. wait_key + + 3.304. weed + + 3.305. wrap + + 3.306. wrap_search + + 3.307. wrapmargin + + 3.308. write_inc + + 3.309. write_bcc + + 3.310. xterm_icon + + 3.311. xterm_set_titles + + 3.312. xterm_title + + 4. Functions + + 4.1. generic menu + + 4.2. index menu + + 4.3. pager menu + + 4.4. alias menu + + 4.5. query menu + + 4.6. attach menu + + 4.7. compose menu + + 4.8. postpone menu + + 4.9. browser menu + + 4.10. pgp menu + + 4.11. smime menu + + 4.12. mix menu + + 4.13. editor menu + + 9. Miscellany + + 1. Acknowledgements + + 2. About this document + + List of Tables + + 1.1. Typographical conventions for special terms + + 2.1. Most common navigation keys + + 2.2. Most common line editor keys + + 2.3. Most common message index keys + + 2.4. Message status flags + + 2.5. Message recipient flags + + 2.6. Most common pager keys + + 2.7. ANSI escape sequences + + 2.8. Color sequences + + 2.9. Most common thread mode keys + + 2.10. Most common mail sending keys + + 2.11. Most common compose menu keys + + 2.12. PGP key menu flags + + 3.1. Symbolic key names + + 4.1. POSIX regular expression character classes + + 4.2. Regular expression repetition operators + + 4.3. GNU regular expression extensions + + 4.4. Pattern modifiers + + 4.5. Simple search keywords + + 4.6. Date units + + 8.1. Command line options + + 8.2. Default generic function bindings + + 8.3. Default index function bindings + + 8.4. Default pager function bindings + + 8.5. Default alias function bindings + + 8.6. Default query function bindings + + 8.7. Default attach function bindings + + 8.8. Default compose function bindings + + 8.9. Default postpone function bindings + + 8.10. Default browser function bindings + + 8.11. Default pgp function bindings + + 8.12. Default smime function bindings + + 8.13. Default mix function bindings + + 8.14. Default editor function bindings + + List of Examples + + 3.1. Multiple configuration commands per line + + 3.2. Commenting configuration files + + 3.3. Escaping quotes in congfiguration files + + 3.4. Using external command's output in configuration files + + 3.5. Using environment variables in configuration files + + 3.6. Configuring external alias files + + 3.7. Setting sort method based on mailbox name + + 3.8. Header weeding + + 3.9. Configuring header display order + + 3.10. Defining custom headers + + 3.11. Using %-expandos in save-hook + + 3.12. Embedding push in folder-hook + + 3.13. Configuring spam detection + + 3.14. Using user-defined variables for config file readability + + 3.15. Using user-defined variables for backing up other config option + values + + 3.16. Deferring user-defined variable expansion to runtime + + 3.17. Using external filters in format strings + + 4.1. Using boolean operators in patterns + + 4.2. Combining send-hook and my_hdr + + 5.1. Attachment counting + +Chapter 1. Introduction + + Table of Contents + + 1. Mutt Home Page + + 2. Mailing Lists + + 3. Software Distribution Sites + + 4. Mutt online resources + + 5. Contributing to Mutt + + 6. Typograhical conventions + + 7. Copyright + + Mutt is a small but very powerful text-based MIME mail client. Mutt is + highly configurable, and is well suited to the mail power user with + advanced features like key bindings, keyboard macros, mail threading, + regular expression searches and a powerful pattern matching language for + selecting groups of messages. + +1. Mutt Home Page + + The official homepage can be found at http://www.mutt.org/. + +2. Mailing Lists + + To subscribe to one of the following mailing lists, send a message with + the word subscribe in the body to list-name-request@mutt.org. + + o -- low traffic list for announcements + + o -- help, bug reports and feature + requests + + o -- development mailing list + + Note + + All messages posted to mutt-announce are automatically forwarded to + mutt-users, so you do not need to be subscribed to both lists. + +3. Software Distribution Sites + + Mutt releases can be downloaded from ftp://ftp.mutt.org/mutt/. For a list + of mirror sites, please refer to http://www.mutt.org/download.html. + +4. Mutt online resources + + Bug Tracking System + + The official mutt bug tracking system can be found at + http://dev.mutt.org/ + + Wiki + + An (unofficial) wiki can be found at http://wiki.mutt.org/. + + IRC + + For the IRC user community, visit channel #mutt on + irc.freenode.net. + + USENET + + For USENET, see the newsgroup comp.mail.mutt. + +5. Contributing to Mutt + + There are various ways to contribute to the Mutt project. + + Especially for new users it may be helpful to meet other new and + experienced users to chat about Mutt, talk about problems and share + tricks. + + Since translations of Mutt into other languages are highly appreciated, + the mutt developers always look for skilled translators that help improve + and continue to maintain stale translations. + + For contributing code patches for new features and bug fixes, please refer + to the developer pages at http://dev.mutt.org/ for more details. + +6. Typograhical conventions + + This section lists typographical conventions followed throughout this + manual. See table Table 1.1, "Typographical conventions for special terms" + for typographical conventions for special terms. + + Table 1.1. Typographical conventions for special terms + + +----------------------------------------------------------+ + | Item | Refers to... | + |----------------+-----------------------------------------| + | printf(3) | UNIX manual pages, execute man 3 printf | + |----------------+-----------------------------------------| + | | named keys | + |----------------+-----------------------------------------| + | | named Mutt function | + |----------------+-----------------------------------------| + | ^G | Control+G key combination | + |----------------+-----------------------------------------| + | $mail_check | Mutt configuration option | + +----------------------------------------------------------+ + + Examples are presented as: + + mutt -v + + Within command synopsis, curly brackets ("{}") denote a set of options of + which one is mandatory, square brackets ("[]") denote optional arguments, + three dots denote that the argument may be repeated arbitrary times. + +7. Copyright + + Mutt is Copyright (C) 1996-2009 Michael R. Elkins and + others. + + This program is free software; you can redistribute it and/or modify it + under the terms of the GNU General Public License as published by the Free + Software Foundation; either version 2 of the License, or (at your option) + any later version. + + This program is distributed in the hope that it will be useful, but + WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY + or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License + for more details. + + You should have received a copy of the GNU General Public License along + with this program; if not, write to the Free Software Foundation, Inc., 51 + Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. + +Chapter 2. Getting Started + + Table of Contents + + 1. Core concepts + + 2. Moving Around in Menus + + 3. Editing Input Fields + + 3.1. Introduction + + 3.2. History + + 4. Reading Mail - The Index and Pager + + 4.1. The Message Index + + 4.2. The Pager + + 4.3. Threaded Mode + + 4.4. Miscellaneous Functions + + 5. Sending Mail + + 5.1. Introduction + + 5.2. Editing the message header + + 5.3. Sending cryptographically signed/encrypted messages + + 5.4. Sending anonymous messages via mixmaster + + 5.5. Sending format=flowed messages + + 6. Forwarding and Bouncing Mail + + 7. Postponing Mail + + 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 various web pages. See + the Mutt homepage for more details. + + The keybindings described in this section are the defaults as distributed. + Your local system administrator may have altered the defaults for your + site. You can always type "?" in any menu to display the current bindings. + + The first thing you need to do is invoke mutt, simply by typing mutt at + the command line. There are various command-line options, see either the + mutt man page or the reference. + +1. Core concepts + + Mutt is a text-based application which interacts with users through + different menus which are mostly line-/entry-based or page-based. A + line-based menu is the so-called "index" menu (listing all messages of the + currently opened folder) or the "alias" menu (allowing you to select + recipients from a list). Examples for page-based menus are the "pager" + (showing one message at a time) or the "help" menu listing all available + key bindings. + + The user interface consists of a context sensitive help line at the top, + the menu's contents followed by a context sensitive status line and + finally the command line. The command line is used to display + informational and error messages as well as for prompts and for entering + interactive commands. + + Because Mutt allows for customizing almost all key bindings, there are + so-called "functions" which can be executed manually (using the command + line) or in macros. Macros allow the user to bind a sequence of commands + to a single key or a short key sequence instead of repeating a sequence of + actions over and over. + + Many commands (such as saving or copying a message to another folder) can + be applied to a single message or a set of messages (so-called "tagged" + messages). To help selecting messages, Mutt provides a rich set of message + patterns (such as recipients, sender, body contents, date sent/received, + etc.) which can be combined into complex expressions using the boolean and + and or operations as well as negating. These patterns can also be used to + (for example) search for messages or to limit the index to show only + matching messages. + + Mutt supports a "hook" concept which allows the user to execute arbitrary + configuration commands and functions in certain situations such as + entering a folder, starting a new message or replying to an existing one. + These hooks can be used to highly customize Mutt's behaviour including + managing multiple identities, customizing the display for a folder or even + implementing auto-archiving based on a per-folder basis and much more. + +2. Moving Around in Menus + + The most important navigation keys common to all menus are shown in + Table 2.1, "Most common navigation keys". + + Table 2.1. Most common navigation keys + + +------------------------------------------------------------------------+ + | Key | Function | Description | + |---------------+------------------+-------------------------------------| + | j or | | move to the next entry | + |---------------+------------------+-------------------------------------| + | k or | | move to the previous entry | + |---------------+------------------+-------------------------------------| + | z or | | go to the next page | + |---------------+------------------+-------------------------------------| + | Z or | | go to the previous page | + |---------------+------------------+-------------------------------------| + | = or | | jump to the first entry | + |---------------+------------------+-------------------------------------| + | * or | | jump to the last entry | + |---------------+------------------+-------------------------------------| + | q | | exit the current menu | + |---------------+------------------+-------------------------------------| + | ? | | list all keybindings for the | + | | | current menu | + +------------------------------------------------------------------------+ + +3. Editing Input Fields + + 3.1. Introduction + + Mutt has a built-in line editor for inputting text, e.g. email addresses + or filenames. The keys used to manipulate text input are very similar to + those of Emacs. See Table 2.2, "Most common line editor keys" for a full + reference of available functions, their default key bindings, and short + descriptions. + + Table 2.2. Most common line editor keys + + +------------------------------------------------------------------------+ + | Key | Function | Description | + |----------------+-------------------+-----------------------------------| + | ^A or | | move to the start of the line | + |----------------+-------------------+-----------------------------------| + | ^B or | | move back one char | + |----------------+-------------------+-----------------------------------| + | Esc B | | move back one word | + |----------------+-------------------+-----------------------------------| + | ^D or | | delete the char under the cursor | + |----------------+-------------------+-----------------------------------| + | ^E or | | move to the end of the line | + |----------------+-------------------+-----------------------------------| + | ^F or | | move forward one char | + |----------------+-------------------+-----------------------------------| + | Esc F | | move forward one word | + |----------------+-------------------+-----------------------------------| + | | | complete filename or alias | + |----------------+-------------------+-----------------------------------| + | ^T | | complete address with query | + |----------------+-------------------+-----------------------------------| + | ^K | | delete to the end of the line | + |----------------+-------------------+-----------------------------------| + | Esc d | | delete to the end of the word | + |----------------+-------------------+-----------------------------------| + | ^W | | kill the word in front of the | + | | | cursor | + |----------------+-------------------+-----------------------------------| + | ^U | | delete entire line | + |----------------+-------------------+-----------------------------------| + | ^V | | quote the next typed key | + |----------------+-------------------+-----------------------------------| + | | | recall previous string from | + | | | history | + |----------------+-------------------+-----------------------------------| + | | | recall next string from history | + |----------------+-------------------+-----------------------------------| + | | | kill the char in front of the | + | | | cursor | + |----------------+-------------------+-----------------------------------| + | Esc u | | convert word to upper case | + |----------------+-------------------+-----------------------------------| + | Esc l | | convert word to lower case | + |----------------+-------------------+-----------------------------------| + | Esc c | | capitalize the word | + |----------------+-------------------+-----------------------------------| + | ^G | n/a | abort | + |----------------+-------------------+-----------------------------------| + | | n/a | finish editing | + +------------------------------------------------------------------------+ + + You can remap the editor functions using the bind command. For example, to + make the key delete the character in front of the cursor rather + than under, you could use: + + bind editor backspace + + 3.2. History + + Mutt maintains a history for the built-in editor. The number of items is + controlled by the $history variable and can be made persistent using an + external file specified using $history_file. You may cycle through them at + an editor prompt by using the and/or commands. + + Mutt maintains several distinct history lists, one for each of the + following categories: + + o muttrc commands + + o addresses and aliases + + o shell commands + + o filenames + + o patterns + + o everything else + + Mutt automatically filters out repeated items from the history. It also + mimics the behavior of some shells by ignoring items starting with a + space. The latter feature can be useful in macros to not clobber the + history's valuable entries with unwanted entries. + +4. Reading Mail - The Index and Pager + + 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 of the message + contents. This is called the "pager." + + The next few sections describe the functions provided in each of these + modes. + + 4.1. The Message Index + + Common keys used to navigate through and manage messages in the index are + shown in Table 2.3, "Most common message index keys". How messages are + presented in the index menu can be customized using the $index_format + variable. + + Table 2.3. Most common message index keys + + +--------------------------------------------------------+ + | Key | Description | + |----------+---------------------------------------------| + | c | change to a different mailbox | + |----------+---------------------------------------------| + | Esc c | change to a folder in read-only mode | + |----------+---------------------------------------------| + | C | copy the current message to another mailbox | + |----------+---------------------------------------------| + | Esc C | decode a message and copy it to a folder | + |----------+---------------------------------------------| + | Esc s | decode a message and save it to a folder | + |----------+---------------------------------------------| + | D | delete messages matching a pattern | + |----------+---------------------------------------------| + | d | delete the current message | + |----------+---------------------------------------------| + | F | mark as important | + |----------+---------------------------------------------| + | l | show messages matching a pattern | + |----------+---------------------------------------------| + | N | mark message as new | + |----------+---------------------------------------------| + | o | change the current sort method | + |----------+---------------------------------------------| + | O | reverse sort the mailbox | + |----------+---------------------------------------------| + | q | save changes and exit | + |----------+---------------------------------------------| + | s | save-message | + |----------+---------------------------------------------| + | T | tag messages matching a pattern | + |----------+---------------------------------------------| + | t | toggle the tag on a message | + |----------+---------------------------------------------| + | Esc t | toggle tag on entire message thread | + |----------+---------------------------------------------| + | U | undelete messages matching a pattern | + |----------+---------------------------------------------| + | u | undelete-message | + |----------+---------------------------------------------| + | v | view-attachments | + |----------+---------------------------------------------| + | x | abort changes and exit | + |----------+---------------------------------------------| + | | display-message | + |----------+---------------------------------------------| + | | jump to the next new or unread message | + |----------+---------------------------------------------| + | @ | show the author's full e-mail address | + |----------+---------------------------------------------| + | $ | save changes to mailbox | + |----------+---------------------------------------------| + | / | search | + |----------+---------------------------------------------| + | Esc / | search-reverse | + |----------+---------------------------------------------| + | ^L | clear and redraw the screen | + |----------+---------------------------------------------| + | ^T | untag messages matching a pattern | + +--------------------------------------------------------+ + + 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 "flags" in Table 2.4, "Message status flags" may appear, + some of which can be turned on or off using these functions: + and bound by default to "w" and "W" respectively. + + Furthermore, the flags in Table 2.5, "Message recipient flags" reflect who + the message is addressed to. They can be customized with the $to_chars + variable. + + Table 2.4. Message status flags + + +----------------------------------------------------------------------+ + | Flag | Description | + |------+---------------------------------------------------------------| + | D | message is deleted (is marked for deletion) | + |------+---------------------------------------------------------------| + | d | message has attachments marked for deletion | + |------+---------------------------------------------------------------| + | K | contains a PGP public key | + |------+---------------------------------------------------------------| + | N | message is new | + |------+---------------------------------------------------------------| + | O | message is old | + |------+---------------------------------------------------------------| + | P | message is PGP encrypted | + |------+---------------------------------------------------------------| + | r | message has been replied to | + |------+---------------------------------------------------------------| + | S | message is signed, and the signature is successfully verified | + |------+---------------------------------------------------------------| + | s | message is signed | + |------+---------------------------------------------------------------| + | ! | message is flagged | + |------+---------------------------------------------------------------| + | * | message is tagged | + +----------------------------------------------------------------------+ + + Table 2.5. Message recipient flags + + +----------------------------------------------------------+ + | Flag | Description | + |------+---------------------------------------------------| + | + | 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 | + |------+---------------------------------------------------| + | L | message is sent to a subscribed mailing list | + +----------------------------------------------------------+ + + 4.2. The Pager + + By default, Mutt uses its builtin pager to display the contents of + messages. The pager is very similar to the Unix program less though not + nearly as featureful. + + Table 2.6. Most common pager keys + + +------------------------------------------------------------------------+ + | Key | Description | + |----------+-------------------------------------------------------------| + | | 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 | search for next match | + |----------+-------------------------------------------------------------| + | S | skip beyond quoted text | + |----------+-------------------------------------------------------------| + | T | toggle display of quoted text | + |----------+-------------------------------------------------------------| + | ? | show keybindings | + |----------+-------------------------------------------------------------| + | / | regular expression search | + |----------+-------------------------------------------------------------| + | Esc / | backward regular expression search | + |----------+-------------------------------------------------------------| + | \ | toggle highlighting of search matches | + |----------+-------------------------------------------------------------| + | ^ | jump to the top of the message | + +------------------------------------------------------------------------+ + + In addition to key bindings in Table 2.6, "Most common pager keys", many + of the functions from the index menu are also available in the pager, such + as or (this is one advantage over using an + external pager to view messages). + + Also, the internal pager supports a couple other advanced features. For + one, it will accept and translate the "standard" nroff sequences for bold + and underline. These sequences are a series of either the letter, + backspace (^H), the letter again for bold or the letter, backspace, "_" + for denoting underline. Mutt will attempt to display these in bold and + underline respectively if your terminal supports them. If not, you can use + the bold and underline color objects to specify a color or mono attribute + for them. + + Additionally, the internal pager supports the ANSI escape sequences for + character attributes. Mutt translates them into the correct color and + character settings. The sequences Mutt supports are: + + \e[Ps;Ps;..Ps;m + + where Ps can be one of the codes shown in Table 2.7, "ANSI escape + sequences". + + Table 2.7. ANSI escape sequences + + +------------------------------------------------------------------------+ + | Escape code | Description | + |-------------+----------------------------------------------------------| + | 0 | All attributes off | + |-------------+----------------------------------------------------------| + | 1 | Bold on | + |-------------+----------------------------------------------------------| + | 4 | Underline on | + |-------------+----------------------------------------------------------| + | 5 | Blink on | + |-------------+----------------------------------------------------------| + | 7 | Reverse video on | + |-------------+----------------------------------------------------------| + | 3 | Foreground color is (see Table 2.8, "Color | + | | sequences") | + |-------------+----------------------------------------------------------| + | 4 | Background color is (see Table 2.8, "Color | + | | sequences") | + +------------------------------------------------------------------------+ + + Table 2.8. Color sequences + + +----------------------+ + | Color code | Color | + |------------+---------| + | 0 | Black | + |------------+---------| + | 1 | Red | + |------------+---------| + | 2 | Green | + |------------+---------| + | 3 | Yellow | + |------------+---------| + | 4 | Blue | + |------------+---------| + | 5 | Magenta | + |------------+---------| + | 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. + + Note + + 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. + + Note + + Note that the search commands in the pager take regular expressions, which + are not quite the same as the more complex patterns used by the search + command in the index. This is because the pager only performs simple text + search, whereas the index provides boolean filtering on several aspects of + messages. + + 4.3. Threaded Mode + + When the mailbox is sorted by threads, there are a few additional + functions available in the index and pager modes as shown in Table 2.9, + "Most common thread mode keys". + + Table 2.9. Most common thread mode keys + + +------------------------------------------------------------------------+ + | Key | Function | Description | + |-------+----------------------+-----------------------------------------| + | ^D | | delete all messages in the current | + | | | thread | + |-------+----------------------+-----------------------------------------| + | ^U | | undelete all messages in the current | + | | | thread | + |-------+----------------------+-----------------------------------------| + | ^N | | jump to the start of the next thread | + |-------+----------------------+-----------------------------------------| + | ^P | | jump to the start of the previous | + | | | thread | + |-------+----------------------+-----------------------------------------| + | ^R | | mark the current thread as read | + |-------+----------------------+-----------------------------------------| + | Esc d | | delete all messages in the current | + | | | subthread | + |-------+----------------------+-----------------------------------------| + | Esc u | | undelete all messages in the current | + | | | subthread | + |-------+----------------------+-----------------------------------------| + | Esc n | | jump to the start of the next subthread | + |-------+----------------------+-----------------------------------------| + | Esc p | | jump to the start of the previous | + | | | subthread | + |-------+----------------------+-----------------------------------------| + | Esc r | | mark the current subthread as read | + |-------+----------------------+-----------------------------------------| + | Esc t | | toggle the tag on the current thread | + |-------+----------------------+-----------------------------------------| + | Esc v | | toggle collapse for the current thread | + |-------+----------------------+-----------------------------------------| + | Esc V | | toggle collapse for all threads | + |-------+----------------------+-----------------------------------------| + | P | | jump to parent message in thread | + +------------------------------------------------------------------------+ + + Note + + Collapsing a thread displays only the first message in the thread and + hides the others. This is useful when threads contain so many messages + that you can only see a handful of threads on the screen. See %M in + $index_format. For example, you could use "%?M?(#%03M)&(%4l)?" in + $index_format to optionally display the number of hidden messages if the + thread is collapsed. + + See also: $strict_threads. + + 4.4. Miscellaneous Functions + + In addition, the index and pager menus have these interesting functions: + + (default: a) + + Creates a new alias based upon the current message (or prompts for + a new one). Once editing is complete, an alias command is added to + the file specified by the $alias_file variable for future use + + Note + + Mutt does not read the $alias_file upon startup so you must + explicitly source the file. + + (default: Esc P) + + This function will search the current message for content signed + or encrypted with PGP the "traditional" way, that is, without + proper MIME tagging. Technically, this function will temporarily + change the MIME content types of the body parts containing PGP + data; this is similar to the function's effect. + + (default: e) + + This command (available in the index and pager) allows you to edit + the raw current message as it's present in the mail folder. After + you have finished editing, the changed message will be appended to + the current folder, and the original message will be marked for + deletion; if the message is unchanged it won't be replaced. + + (default: ^E on the attachment menu, and in the pager and + index menus; ^T on the compose menu) + + This command is used to temporarily edit an attachment's content + type to fix, for instance, bogus character set parameters. When + invoked from the index or from the pager, you'll have the + opportunity to edit the top-level attachment's content type. On + the attachment menu, you can change any attachment's content type. + These changes are not persistent, and get lost upon changing + folders. + + Note that this command is also available on the compose menu. + There, it's used to fine-tune the properties of attachments you + are going to send. + + (default: ":") + + This command is used to execute any command you would normally put + in a configuration file. A common use is to check the settings of + variables, or in conjunction with macros to change settings on the + fly. + + (default: ^K) + + This command extracts PGP public keys from the current or tagged + message(s) and adds them to your PGP public key ring. + + (default: ^F) + + This command wipes the passphrase(s) from memory. It is useful, if + you misspelled the passphrase. + + (default: L) + + Reply to the current or tagged message(s) by extracting any + addresses which match the regular expressions given by the lists + or subscribe commands, but also honor any Mail-Followup-To + header(s) if the $honor_followup_to configuration variable is set. + Using this when replying to messages posted to mailing lists helps + avoid duplicate copies being sent to the author of the message you + are replying to. + + (default: |) + + Asks for an external Unix command and pipes the current or tagged + message(s) to it. The variables $pipe_decode, $pipe_split, + $pipe_sep and $wait_key control the exact behavior of this + function. + + (default: Esc e) + + Mutt takes the current message as a template for a new message. + This function is best described as "recall from arbitrary + folders". It can conveniently be used to forward MIME messages + while preserving the original mail structure. Note that the amount + of headers included here depends on the value of the $weed + variable. + + This function is also available from the attachment menu. You can + use this to easily resend a message which was included with a + bounce message as a message/rfc822 body part. + + (default: !) + + Asks for an external Unix command and executes it. The $wait_key + can be used to control whether Mutt will wait for a key to be + pressed when the command returns (presumably to let the user read + the output of the command), based on the return status of the + named command. If no command is given, an interactive shell is + executed. + + (default: T) + + The pager uses the $quote_regexp variable to detect quoted text + when displaying the body of the message. This function toggles the + display of the quoted material in the message. It is particularly + useful when being interested in just the response and there is a + large amount of quoted text in the way. + + (default: S) + + This function will go to the next line of non-quoted text which + comes after a line of quoted text in the internal pager. + +5. Sending Mail + + 5.1. Introduction + + The bindings shown in Table 2.10, "Most common mail sending keys" are + available in the index and pager to start a new message. + + Table 2.10. Most common mail sending keys + + +----------------------------------------------------------+ + | Key | Function | Description | + |-------+---------------+----------------------------------| + | m | | compose a new message | + |-------+---------------+----------------------------------| + | r | | reply to sender | + |-------+---------------+----------------------------------| + | g | | reply to all recipients | + |-------+---------------+----------------------------------| + | L | | reply to mailing list address | + |-------+---------------+----------------------------------| + | f | | forward message | + |-------+---------------+----------------------------------| + | b | | bounce (remail) message | + |-------+---------------+----------------------------------| + | Esc k | | 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. These items are discussed in greater detail in the next + chapter "Forwarding and Bouncing Mail." + + Mutt will then enter the compose menu and prompt you for the recipients to + place on the "To:" header field. Next, it will ask you for the "Subject:" + field for the message, providing a default if you are replying to or + forwarding a message. See also $askcc, $askbcc, $autoedit, $bounce, + $fast_reply, and $include for changing how Mutt asks these questions. + + Mutt will then automatically start your $editor on the message body. If + the $edit_headers variable is set, the headers will be at the top of the + message in your editor. Any messages you are replying to will be added in + sort order to the message, with appropriate $attribution, $indent_string + and $post_indent_string. When forwarding a message, if the $mime_forward + variable is unset, a copy of the forwarded message will be included. If + you have specified a $signature, it will be appended to the message. + + Once you have finished editing the body of your mail message, you are + returned to the compose menu providing the functions shown in Table 2.11, + "Most common compose menu keys" to modify, send or postpone the message. + + Table 2.11. Most common compose menu keys + + +------------------------------------------------------------------------+ + | Key | Function | Description | + |-------+---------------------+------------------------------------------| + | a | | attach a file | + |-------+---------------------+------------------------------------------| + | A | | attach message(s) to the message | + |-------+---------------------+------------------------------------------| + | Esc k | | attach a PGP public key | + |-------+---------------------+------------------------------------------| + | d | | edit description on attachment | + |-------+---------------------+------------------------------------------| + | D | | detach a file | + |-------+---------------------+------------------------------------------| + | t | | edit the To field | + |-------+---------------------+------------------------------------------| + | Esc f | | edit the From field | + |-------+---------------------+------------------------------------------| + | r | | edit the Reply-To field | + |-------+---------------------+------------------------------------------| + | c | | edit the Cc field | + |-------+---------------------+------------------------------------------| + | b | | edit the Bcc field | + |-------+---------------------+------------------------------------------| + | y | | send the message | + |-------+---------------------+------------------------------------------| + | s | | edit the Subject | + |-------+---------------------+------------------------------------------| + | S | | select S/MIME options | + |-------+---------------------+------------------------------------------| + | f | | specify an "Fcc" mailbox | + |-------+---------------------+------------------------------------------| + | p | | select PGP options | + |-------+---------------------+------------------------------------------| + | P | | postpone this message until later | + |-------+---------------------+------------------------------------------| + | q | | quit (abort) sending the message | + |-------+---------------------+------------------------------------------| + | w | | write the message to a folder | + |-------+---------------------+------------------------------------------| + | i | | check spelling (if available on your | + | | | system) | + |-------+---------------------+------------------------------------------| + | ^F | | wipe passphrase(s) from memory | + +------------------------------------------------------------------------+ + + The compose menu is also used to edit the attachments for a message which + can be either files or other messages. The function to + will prompt you for a folder to attach messages from. You can now tag + messages in that folder and they will be attached to the message you are + sending. + + Note + + Note that certain operations like composing a new mail, replying, + forwarding, etc. are not permitted when you are in that folder. The %r in + $status_format will change to a "A" to indicate that you are in + attach-message mode. + + 5.2. Editing the message header + + When editing the header because of $edit_headers being set, there are a + several pseudo headers available which will not be included in sent + messages. + + 5.2.1. Fcc: pseudo header + + If you specify Fcc: filename as a header, Mutt will pick up filename just + as if you had used the function in the compose menu. + + 5.2.2. Attach: pseudo header + + You can also attach files to your message by specifying Attach: filename [ + description ] where filename is the file to attach and description is an + optional string to use as the description of the attached file. + + 5.2.3. Pgp: pseudo header + + If you want to use PGP, you can specify + + Pgp: [ E | S | S ] + + "E" selects encryption, "S" selects signing and "S" selects signing + with the given key, setting $pgp_sign_as permanently. + + 5.2.4. In-Reply-To: header + + When replying to messages, the In-Reply-To: header contains the Message-Id + of the message(s) you reply to. If you remove its value, Mutt will not + generate a References: field, which allows you to create a new message + thread, for example to create a new message to a mailing list without + having to enter the mailing list's address. + + 5.3. Sending cryptographically signed/encrypted messages + + If you have told mutt to PGP or S/MIME encrypt a message, it will guide + you through a key selection process when you try to send the message. Mutt + will not ask you any questions about keys which have a certified user ID + matching one of the message recipients' mail addresses. However, there may + be situations in which there are several keys, weakly certified user ID + fields, or where no matching keys can be found. + + In these cases, you are dropped into a menu with a list of keys from which + you can select one. When you quit this menu, or mutt can't find any + matching keys, you are prompted for a user ID. You can, as usually, abort + this prompt using ^G. When you do so, mutt will return to the compose + screen. + + Once you have successfully finished the key selection, the message will be + encrypted using the selected public keys when sent out. + + Most fields of the entries in the key selection menu (see also + $pgp_entry_format) have obvious meanings. But some explanations on the + capabilities, flags, and validity fields are in order. + + The flags sequence (%f) will expand to one of the flags in Table 2.12, + "PGP key menu flags". + + Table 2.12. PGP key menu flags + + +-----------------------------------------------------------+ + | Flag | Description | + |------+----------------------------------------------------| + | R | The key has been revoked and can't be used. | + |------+----------------------------------------------------| + | X | The key is expired and can't be used. | + |------+----------------------------------------------------| + | d | You have marked the key as disabled. | + |------+----------------------------------------------------| + | c | There are unknown critical self-signature packets. | + +-----------------------------------------------------------+ + + The capabilities field (%c) expands to a two-character sequence + representing a key's capabilities. The first character gives the key's + encryption capabilities: A minus sign ("-") means that the key cannot be + used for encryption. A dot (".") means that it's marked as a signature key + in one of the user IDs, but may also be used for encryption. The letter + "e" indicates that this key can be used for encryption. + + The second character indicates the key's signing capabilities. Once again, + a "-" implies "not for signing", "." implies that the key is marked as an + encryption key in one of the user-ids, and "s" denotes a key which can be + used for signing. + + Finally, the validity field (%t) indicates how well-certified a user-id + is. A question mark ("?") indicates undefined validity, a minus character + ("-") marks an untrusted association, a space character means a partially + trusted association, and a plus character ("+") indicates complete + validity. + + 5.4. Sending anonymous messages via mixmaster + + You may also have compiled mutt to co-operate with Mixmaster, an anonymous + remailer. Mixmaster permits you to send your messages anonymously using a + chain of remailers. Mixmaster support in mutt is for mixmaster version + 2.04 (beta 45 appears to be the latest) and 2.03. It does not support + earlier versions or the later so-called version 3 betas, of which the + latest appears to be called 2.9b23. + + To use it, you'll have to obey certain restrictions. Most important, you + cannot use the Cc and Bcc headers. To tell Mutt to use mixmaster, you have + to select a remailer chain, using the mix function on the compose menu. + + The chain selection screen is divided into two parts. In the (larger) + upper part, you get a list of remailers you may use. In the lower part, + you see the currently selected chain of remailers. + + You can navigate in the chain using the and + functions, which are by default bound to the left and right arrows and to + the h and l keys (think vi keyboard bindings). To insert a remailer at the + current chain position, use the function. To append a remailer + behind the current chain position, use or . You can + also delete entries from the chain, using the corresponding function. + Finally, to abandon your changes, leave the menu, or them + pressing (by default) the Return key. + + Note that different remailers do have different capabilities, indicated in + the %c entry of the remailer menu lines (see $mix_entry_format). Most + important is the "middleman" capability, indicated by a capital "M": This + means that the remailer in question cannot be used as the final element of + a chain, but will only forward messages to other mixmaster remailers. For + details on the other capabilities, please have a look at the mixmaster + documentation. + + 5.5. Sending format=flowed messages + + 5.5.1. Concept + + format=flowed-style messages (or f=f for short) are text/plain messages + that consist of paragraphs which a receiver's mail client may reformat to + its own needs which mostly means to customize line lengths regardless of + what the sender sent. Technically this is achieved by letting lines of a + "flowable" paragraph end in spaces except for the last line. + + While for text-mode clients like mutt it's the best way to assume only a + standard 80x25 character cell terminal, it may be desired to let the + receiver decide completely how to view a message. + + 5.5.2. Mutt support + + Mutt only supports setting the required format=flowed MIME parameter on + outgoing messages if the $text_flowed variable is set, specifically it + does not add the trailing spaces. + + After editing the initial message text and before entering the compose + menu, mutt properly space-stuffes the message. Space-stuffing is required + by RfC3676 defining format=flowed and means to prepend a space to: + + o all lines starting with a space + + o lines starting with the word "From" followed by space + + o all lines starting with ">" which is not intended to be a quote + character + + Note + + Mutt only supports space-stuffing for the first two types of lines but not + for the third: It is impossible to safely detect whether a leading > + character starts a quote or not. Furthermore, Mutt only applies + space-stuffing once after the initial edit is finished. + + All leading spaces are to be removed by receiving clients to restore the + original message prior to further processing. + + 5.5.3. Editor considerations + + As mutt provides no additional features to compose f=f messages, it's + completely up to the user and his editor to produce proper messages. + Please consider your editor's documentation if you intend to send f=f + messages. + + Please note that when editing messages from the compose menu several times + before really sending a mail, it's up to the user to ensure that the + message is properly space-stuffed. + + For example, vim provides the w flag for its formatoptions setting to + assist in creating f=f messages, see :help fo-table for details. + +6. Forwarding and Bouncing Mail + + Bouncing and forwarding let you send an existing message to recipients + that you specify. Bouncing a message sends a verbatim copy of a message to + alternative addresses as if they were the message's original recipients + specified in the Bcc header. Forwarding a message, on the other hand, + allows you to modify the message before it is resent (for example, by + adding your own comments). Bouncing is done using the function + and forwarding using the function bound to "b" and "f" + respectively. + + Forwarding can be done by including the original message in the new + message's body (surrounded by indicating lines) or including it as a MIME + attachment, depending on the value of the $mime_forward variable. Decoding + of attachments, like in the pager, can be controlled by the + $forward_decode and $mime_forward_decode variables, respectively. The + desired forwarding format may depend on the content, therefore + $mime_forward is a quadoption which, for example, can be set to "ask-no". + + The inclusion of headers is controlled by the current setting of the $weed + variable, unless $mime_forward is set. + + Editing the message to forward follows the same procedure as sending or + replying to a message does. + +7. Postponing Mail + + At times it is desirable to delay sending a message that you have already + begun to compose. When the function is used in the + compose menu, the body of your message and attachments are stored in the + mailbox specified by the $postponed variable. This means that you can + recall the message even if you exit Mutt and then restart it at a later + time. + + Once a message is postponed, there are several ways to resume it. From the + command line you can use the "-p" option, or if you compose a new message + from the index or pager you will be prompted if postponed messages exist. + If multiple messages are currently postponed, the postponed menu will pop + up and you can select which message you would like to resume. + + Note + + If you postpone a reply to a message, the reply setting of the message is + only updated when you actually finish the message and send it. Also, you + must be in the same folder with the message you replied to for the status + of the message to be updated. + + See also the $postpone quad-option. + +Chapter 3. Configuration + + Table of Contents + + 1. Location of initialization files + + 2. Syntax of Initialization Files + + 3. Address groups + + 4. Defining/Using aliases + + 5. Changing the default key bindings + + 6. Defining aliases for character sets + + 7. Setting variables based upon mailbox + + 8. Keyboard macros + + 9. Using color and mono video attributes + + 10. Message header display + + 11. Alternative addresses + + 12. Mailing lists + + 13. Using Multiple spool mailboxes + + 14. Monitoring incoming mail + + 15. User defined headers + + 16. Specify default save mailbox + + 17. Specify default Fcc: mailbox when composing + + 18. Specify default save filename and default Fcc: mailbox at once + + 19. Change settings based upon message recipients + + 20. Change settings before formatting a message + + 21. Choosing the cryptographic key of the recipient + + 22. Adding key sequences to the keyboard buffer + + 23. Executing functions + + 24. Message Scoring + + 25. Spam detection + + 26. Setting and Querying Variables + + 26.1. Commands + + 26.2. User-defined variables + + 27. Reading initialization commands from another file + + 28. Configuring features conditionnaly + + 29. Removing hooks + + 30. Format Strings + + 30.1. Basic usage + + 30.2. Filters + +1. Location of initialization files + + While the default configuration (or "preferences") make Mutt usable right + out of the box, it is often desirable to tailor Mutt to suit your own + tastes. When Mutt is first invoked, it will attempt to read the "system" + configuration file (defaults set by your local system administrator), + unless the "-n" command line option is specified. This file is typically + /usr/local/share/mutt/Muttrc or /etc/Muttrc. Mutt will next look for a + file named .muttrc in your home directory. If this file does not exist and + your home directory has a subdirectory named .mutt, mutt try to load a + file named .mutt/muttrc. + + .muttrc is the file where you will usually place your commands to + configure Mutt. + + In addition, mutt supports version specific configuration files that are + parsed instead of the default files as explained above. For instance, if + your system has a Muttrc-0.88 file in the system configuration directory, + and you are running version 0.88 of mutt, this file will be sourced + instead of the Muttrc file. The same is true of the user configuration + file, if you have a file .muttrc-0.88.6 in your home directory, when you + run mutt version 0.88.6, it will source this file instead of the default + .muttrc file. The version 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. + +2. Syntax of Initialization Files + + 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 (;). + + Example 3.1. Multiple configuration commands per line + + set realname='Mutt user' ; ignore x- + + 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, + + Example 3.2. Commenting configuration files + + 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 shell programs, namely + that a single quote is used to specify a literal string (one that is not + interpreted for shell variables or quoting with a backslash [see next + paragraph]), while double quotes indicate a string for which should be + evaluated. For example, backticks are evaluated inside of double quotes, + but not for single quotes. + + \ quotes the next character, just as in shells such as bash and zsh. For + example, if want to put quotes """ inside of a string, you can use "\" to + force the next character to be a literal instead of interpreted character. + + Example 3.3. Escaping quotes in congfiguration files + + 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. + + A \ at the end of a line can be used to split commands over multiple + lines, provided that the split points don't appear in the middle of + command names. + + It is also possible to substitute the output of a Unix command in an + initialization file. This is accomplished by enclosing the command in + backticks (``). For example, + + Example 3.4. Using external command's output in configuration files + + my_hdr X-Operating-System: `uname -a` + + The output of the Unix command "uname -a" will be substituted before the + line is parsed. + + Note + + Since initialization files are line oriented, only the first line of + output from the Unix command will be substituted. + + Both environment variables and mutt variables can be accessed by + prepending "$" to the name of the variable. For example, + + Example 3.5. Using environment variables in configuration files + + set record=+sent_on_$HOSTNAME + + will cause mutt to save outgoing messages to a folder named + "sent_on_kremvax" if the environment variable HOSTNAME is set to + "kremvax." (See $record for details.) + + Mutt expands the variable when it is assigned, not when it is used. If the + value of a variable on the right-hand side of an assignment changes after + the assignment, the variable on the left-hand side will not be affected. + + The commands understood by mutt are explained in the next paragraphs. For + a complete list, see the command reference. + + All configuration files are expected to be in the current locale as + specified by the $charset variable which doesn't have a default value + since it's determined by Mutt at startup. If a configuration file is not + encoded in the same character set the $config_charset variable should be + used: all lines starting with the next are recoded from $config_charset to + $charset. + + This mechanism should be avoided if possible as it has the following + implications: + + o These variables should be set early in a configuration file with + $charset preceding $config_charset so Mutt know what character set to + convert to. + + o If $config_charset is set, it should be set in each configuration file + because the value is global and not per configuration file. + + o Because Mutt first recodes a line before it attempts to parse it, a + conversion introducing question marks or other characters as part of + errors (unconvertable characters, transliteration) may introduce + syntax errors or silently change the meaning of certain tokens (e.g. + inserting question marks into regular expressions). + +3. Address groups + + Usage: + + group [ -group name ...] { -rx expr ... | -addr expr ... } + + ungroup [ -group name ...] { * | -rx expr ... | -addr expr ... } + + group is used to directly add either addresses or regular expressions to + the specified group or groups. The different categories of arguments to + the group command can be in any order. The flags -rx and -addr specify + what the following strings (that cannot begin with a hyphen) should be + interpreted as: either a regular expression or an email address, + respectively. + + These address groups can also be created implicitly by the alias, lists, + subscribe and alternates commands by specifying the optional -group + option. + + Once defined, these address groups can be used in patterns to search for + and limit the display to messages matching a group. + + ungroup is used to remove addresses or regular expressions from the + specified group or groups. The syntax is similar to the group command, + however the special character * can be used to empty a group of all of its + contents. + +4. Defining/Using aliases + + Usage: + + alias [ -group name ...] key address [ address ...] + + It's usually very cumbersome to remember or type out the address of + someone you are communicating with. Mutt allows you to create "aliases" + which map a short string to a full address. + + Note + + If you want to create an alias for more than one address, you must + separate the addresses with a comma (","). + + The optional -group argument to alias causes the aliased address(es) to be + added to the named group. + + To remove an alias or aliases ("*" means all aliases): + + unalias [ -group name ...] { * | key ... } + + 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. Consequently, you can have multiple + alias files, or you can have all aliases defined in your muttrc. + + On the other hand, the function can use only one file, the + one pointed to by the $alias_file variable (which is ~/.muttrc by + default). This file is not special either, in the sense that Mutt will + happily append aliases to any file, but in order for the new aliases to + take effect you need to explicitly source this file too. + + For example: + + Example 3.6. Configuring external alias files + + 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 To: or Cc: prompt. You can also enter + aliases in your editor at the appropriate headers if you have the + $edit_headers variable set. + + In addition, at the various address prompts, you can use the tab character + to expand a partial alias to the full alias. If there are multiple + matches, mutt will bring up a menu with the matching aliases. In order to + be presented with the full list of aliases, you must hit tab with out a + partial alias, such as at the beginning of the prompt or after a comma + denoting multiple addresses. + + In the alias menu, you can select as many aliases as you want with the + select-entry key (default: ), and use the exit key (default: q) to + return to the address prompt. + +5. Changing the default key bindings + + Usage: + + bind map key function + + This command allows you to change the default key bindings (operation + invoked when pressing a key). + + map specifies in which menu the binding belongs. Multiple maps may be + specified by separating them with commas (no additional whitespace is + allowed). The currently defined maps are: + + generic + + This is not a real menu, but is used as a fallback for all of the + other menus except for the pager and editor modes. If a key is not + defined in another menu, Mutt will look for a binding to use in + this menu. This allows you to bind a key to a certain function in + multiple menus instead of having multiple bind statements to + accomplish the same task. + + alias + + The alias menu is the list of your personal aliases as defined in + your muttrc. It is the mapping from a short alias name to the full + email address(es) of the recipient(s). + + attach + + The attachment menu is used to access the attachments on received + messages. + + browser + + The browser is used for both browsing the local directory + structure, and for listing all of your incoming mailboxes. + + editor + + The editor is the line-based editor the user enters text data. + + index + + The index is the list of messages contained in a mailbox. + + compose + + The compose menu is the screen used when sending a new message. + + pager + + The pager is the mode used to display message/attachment data, and + help listings. + + pgp + + The pgp menu is used to select the OpenPGP keys used to encrypt + outgoing messages. + + smime + + The smime menu is used to select the OpenSSL certificates used to + encrypt outgoing messages. + + postpone + + The postpone menu is similar to the index menu, except is used + when recalling a message the user was composing, but saved until + later. + + query + + The query menu is the browser for results returned by + $query_command. + + mix + + The mixmaster screen is used to select remailer options for + outgoing messages (if Mutt is compiled with Mixmaster support). + + key is the key (or key sequence) you wish to bind. To specify a control + character, use the sequence \Cx, where x is the letter of the control + character (for example, to specify control-A use "\Ca"). Note that the + case of x as well as \C is ignored, so that \CA, \Ca, \cA and \ca are all + equivalent. An alternative form is to specify the key as a three digit + octal number prefixed with a "\" (for example \177 is equivalent to \c?). + In addition, key may be a symbolic name as shown in Table 3.1, "Symbolic + key names". + + Table 3.1. Symbolic key names + + +-------------------------------------+ + | Symbolic name | Meaning | + |---------------+---------------------| + | \t | tab | + |---------------+---------------------| + | | tab | + |---------------+---------------------| + | | backtab / shift-tab | + |---------------+---------------------| + | \r | carriage return | + |---------------+---------------------| + | \n | newline | + |---------------+---------------------| + | \e | escape | + |---------------+---------------------| + | | escape | + |---------------+---------------------| + | | up arrow | + |---------------+---------------------| + | | down arrow | + |---------------+---------------------| + | | left arrow | + |---------------+---------------------| + | | right arrow | + |---------------+---------------------| + | | Page Up | + |---------------+---------------------| + | | Page Down | + |---------------+---------------------| + | | Backspace | + |---------------+---------------------| + | | Delete | + |---------------+---------------------| + | | Insert | + |---------------+---------------------| + | | Enter | + |---------------+---------------------| + | | Return | + |---------------+---------------------| + | | Home | + |---------------+---------------------| + | | End | + |---------------+---------------------| + | | Space bar | + |---------------+---------------------| + | | function key 1 | + |---------------+---------------------| + | | function key 10 | + +-------------------------------------+ + + key does not need to be enclosed in quotes unless it contains a space (" + ") or semi-colon (";"). + + function specifies which action to take when key is pressed. For a + complete list of functions, see the reference. The special function + unbinds the specified key sequence. + +6. Defining aliases for character sets + + Usage: + + charset-hook alias charset + + iconv-hook charset local-charset + + The charset-hook command defines an alias for a character set. This is + useful to properly display messages which are tagged with a character set + name not known to mutt. + + The iconv-hook command defines a system-specific name for a character set. + This is helpful when your systems character conversion library insists on + using strange, system-specific names for character sets. + +7. Setting variables based upon mailbox + + Usage: + + folder-hook [!]regexp command + + It is often desirable to change settings based on which mailbox you are + reading. The folder-hook command provides a method by which you can + execute any configuration command. regexp is a regular expression + specifying in which mailboxes to execute command before loading. If a + mailbox matches multiple folder-hook's, they are executed in the order + given in the muttrc. + + Note + + If you use the "!" shortcut for $spoolfile at the beginning of the + pattern, you must place it inside of double or single quotes in order to + distinguish it from the logical not operator for the expression. + + Note + + Settings are not restored when you leave the mailbox. 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 default command, use the pattern + "." before other folder-hooks adjusting a value on a per-folder basis + because folder-hooks are evaluated in the order given in the configuration + file. The following example will set the sort variable to date-sent for + all folders but to threads for all folders containing "mutt" in their + name. + + Example 3.7. Setting sort method based on mailbox name + + folder-hook . set sort=date-sent + folder-hook mutt set sort=threads + +8. Keyboard macros + + Usage: + + macro menu key sequence [ description ] + + Macros are useful when you would like a single key to perform a series of + actions. When you press key in menu menu, Mutt will behave as if you had + typed sequence. So if you have a common sequence of commands you type, you + can create a macro to execute those commands with a single key or fewer + keys. + + menu is the map which the macro will be bound in. Multiple maps may be + specified by separating multiple menu arguments by commas. Whitespace may + not be used in between the menu arguments and the commas separating them. + + key and sequence are expanded by the same rules as the key bindings with + some additions. The first is that control characters in sequence can also + be specified as ^x. In order to get a caret ("^") you need to use ^^. + Secondly, to specify a certain key such as up or to invoke a function + directly, you can use the format and . For a + listing of key names see the section on key bindings. Functions are listed + in the reference. + + The advantage with using function names directly is that the macros will + work regardless of the current key bindings, so they are not dependent on + the user having particular key definitions. This makes them more robust + and portable, and also facilitates defining of macros in files used by + more than one user (e.g., the system Muttrc). + + Optionally you can specify a descriptive text after sequence, which is + shown in the help screens. + + Note + + Macro definitions (if any) listed in the help screen(s), are silently + truncated at the screen width, and are not wrapped. + +9. Using color and mono video attributes + + Usage: + + color object foreground background + + color { header | body } foreground background regexp + + color index foreground background pattern + + uncolor index { * | pattern ... } + + 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 information), + you must specify both a foreground color and a background color (it is not + possible to only specify one or the other). + + header and body match regexp in the header/body of a message, index + matches pattern (see Section 2, "Patterns: Searching, Limiting and + Tagging") in the message index. + + object can be one of: + + o attachment + + o bold (hiliting bold patterns in the body of messages) + + o error (error messages printed by Mutt) + + o hdrdefault (default color of the message header in the pager) + + o indicator (arrow or bar used to indicate the current item in a menu) + + o markers (the "+" markers at the beginning of wrapped lines in the + pager) + + o message (informational messages) + + o normal + + o quoted (text matching $quote_regexp in the body of a message) + + o quoted1, quoted2, ..., quotedN (higher levels of quoting) + + o search (hiliting of words in the pager) + + o signature + + o status (mode lines used to display info about the mailbox or message) + + o tilde (the "~" used to pad blank lines in the pager) + + o tree (thread tree drawn in the message index and attachment menu) + + o underline (hiliting underlined patterns in the body of messages) + + foreground and background can be one of the following: + + o white + + o black + + o green + + o magenta + + o blue + + o cyan + + o yellow + + o red + + o default + + o colorx + + foreground can optionally be prefixed with the keyword bright to make the + foreground color boldfaced (e.g., brightred). + + If your terminal supports it, the special keyword default can be used as a + transparent color. The value brightdefault is also valid. If Mutt is + linked against the S-Lang library, you also need to set the COLORFGBG + 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 + + Note + + The S-Lang library requires you to use the lightgray and brown keywords + instead of white and yellow when setting this variable. + + Note + + The uncolor command can be applied to the index object only. It removes + entries from the list. You must 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 color0, color1, ..., colorN-1 (N being + the number of colors supported by your terminal). This is useful when you + remap the colors for your display (for example by changing the color + associated with color2 for your xterm), since color names may then lose + their normal meaning. + + If your terminal does not support color, it is still possible change the + video attributes through the use of the "mono" command: + + Usage: + + mono object attribute + + mono { header | body } attribute regexp + + mono index attribute pattern + + unmono index { * | pattern ... } + + For object, see the color command. attribute can be one of the following: + + o none + + o bold + + o underline + + o reverse + + o standout + +10. Message header display + + Usage: + + ignore pattern [ pattern ...] + + unignore { * | pattern ... } + + Messages often have many header fields added by automatic processing + systems, or which may not seem useful to display on the screen. This + command allows you to specify header fields which you don't normally want + to see in the pager. + + You do not need to specify the full header field name. For example, + "ignore content-" will ignore all header fields that begin with the + pattern "content-". "ignore *" will ignore all headers. + + To remove a previously added token from the list, use the "unignore" + command. The "unignore" command will make Mutt display headers with the + given pattern. For example, if you do "ignore x-" it is possible to + "unignore x-mailer". + + "unignore *" will remove all tokens from the ignore list. + + For example: + + Example 3.8. Header weeding + + # 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: + + Usage: + + hdr_order header [ header ...] + + unhdr_order { * | header ... } + + With the hdr_order command you can specify an order in which mutt will + attempt to present these headers to you when viewing messages. + + "unhdr_order *" will clear all previous headers from the order list, thus + removing the header order effects set by the system-wide startup file. + + Example 3.9. Configuring header display order + + hdr_order From Date: From: To: Cc: Subject: + +11. Alternative addresses + + Usage: + + alternates [ -group name ...] regexp [ regexp ...] + + unalternates [ -group name ...] { * | regexp ... } + + With various functions, mutt will treat messages differently, depending on + whether you sent them or whether you received them from someone else. For + instance, when replying to a message that you sent to a different party, + mutt will automatically suggest to send the response to the original + message's recipients -- responding to yourself won't make much sense in + many cases. (See $reply_to.) + + Many users receive e-mail under a number of different addresses. To fully + use mutt's features here, the program must be able to recognize what + e-mail addresses you receive mail under. That's the purpose of the + alternates command: It takes a list of regular expressions, each of which + can identify an address under which you receive e-mail. + + As addresses are matched using regular expressions and not exact strict + comparisons, you should make sure you specify your addresses as precise as + possible to avoid mismatches. For example, if you specify: + + alternates user@example + + mutt will consider "some-user@example" as being your address, too which + may not be desired. As a solution, in such cases addresses should be + specified as: + + alternates '^user@example$' + + The -group flag causes all of the subsequent regular expressions to be + added to the named group. + + The unalternates command can be used to write exceptions to alternates + patterns. If an address matches something in an alternates command, but + you nonetheless do not think it is from you, you can list a more precise + pattern under an unalternates command. + + To remove a regular expression from the alternates list, use the + unalternates command with exactly the same regexp. Likewise, if the regexp + for an alternates command matches an entry on the unalternates list, that + unalternates entry will be removed. If the regexp for unalternates is "*", + all entries on alternates will be removed. + +12. Mailing lists + + Usage: + + lists [ -group name ...] regexp [ regexp ...] + + unlists [ -group name ...] { * | regexp ... } + + subscribe [ -group name ...] regexp [ regexp ...] + + unsubscribe [ -group name ...] { * | regexp ... } + + Mutt has a few nice features for handling mailing lists. In order to take + advantage of them, you must specify which addresses belong to mailing + lists, and which mailing lists you are subscribed to. Once you have done + this, the function will work for all known lists. + Additionally, when you send a message to a subscribed list, mutt will add + a Mail-Followup-To header to tell other users' mail user agents not to + send copies of replies to your personal address. + + Note + + The Mail-Followup-To header is a non-standard extension which is not + supported by all mail user agents. Adding it is not bullet-proof against + receiving personal CCs of list messages. Also note that the generation of + the Mail-Followup-To header is controlled by the $followup_to + configuration variable. + + More precisely, Mutt maintains lists of patterns for the addresses of + known and subscribed mailing lists. Every subscribed mailing list is + known. To mark a mailing list as known, use the "lists" command. To mark + it as subscribed, use "subscribe". + + You can use regular expressions with both commands. To mark all messages + sent to a specific bug report's address on mutt's bug tracking system as + list mail, for instance, you could say "subscribe [0-9]*@bugs.guug.de". + Often, it's sufficient to just give a portion of the list's e-mail + address. + + Specify as much of the address as you need to to remove ambiguity. For + example, if you've subscribed to the Mutt mailing list, you will receive + mail addressed to mutt-users@mutt.org. So, to tell Mutt that this is a + mailing list, you could add "lists mutt-users@" to your initialization + file. To tell mutt that you are subscribed to it, add "subscribe + mutt-users" to your initialization file instead. If you also happen to get + mail from someone whose address is mutt-users@example.com, you could use + "lists ^mutt-users@mutt\\.org$" or "subscribe ^mutt-users@mutt\\.org$" to + match only mail from the actual list. + + The -group flag adds all of the subsequent regular expressions to the + named group. + + The "unlists" command is used to remove a token from the list of known and + subscribed mailing-lists. Use "unlists *" to remove all tokens. + + To remove a mailing list from the list of subscribed mailing lists, but + keep it on the list of known mailing lists, use "unsubscribe". + +13. Using Multiple spool mailboxes + + Usage: + + mbox-hook [!]pattern mailbox + + This command is used to move read messages from a specified mailbox to a + different mailbox automatically when you quit or change folders. pattern + is a regular expression specifying the mailbox to treat as a "spool" + mailbox and mailbox specifies where mail should be saved when read. + + Unlike some of the other hook commands, only the first matching pattern is + used (it is not possible to save read mail in more than a single mailbox). + +14. Monitoring incoming mail + + Usage: + + mailboxes mailbox [ mailbox ...] + + unmailboxes { * | mailbox ... } + + This command specifies folders which can receive mail and which will be + checked for new messages periodically. + + folder can either be a local file or directory (Mbox/Mmdf or Maildir/Mh). + If Mutt was built with POP and/or IMAP support, folder can also be a + POP/IMAP folder URL. The URL syntax is described in Section 1.2, "URL + syntax", POP and IMAP are described in Section 3, "POP3 Support" and + Section 4, "IMAP Support" respectively. + + Mutt provides a number of advanced features for handling (possibly many) + folders and new mail within them, please refer to Section 9, "Handling + multiple folders" for details (including in what situations and how often + Mutt checks for new mail). + + The "unmailboxes" command is used to remove a token from the list of + folders which receive mail. Use "unmailboxes *" to remove all tokens. + + Note + + The folders 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 affects these characters (like $folder + and $spoolfile) should be set before the mailboxes command. If none of + these shorcuts are used, a local path should be absolute as otherwise mutt + tries to find it relative to the directory from where mutt was started + which may not always be desired. + + For Mbox and Mmdf folders, new mail is detected by comparing access and/or + modification times of files: Mutt assumes a folder has new mail if it + wasn't accessed after it was last modified. Utilities like biff or frm or + any other program which accesses the mailbox might cause Mutt to never + detect new mail for that mailbox if they do not properly reset the access + time. Other possible causes of Mutt not detecting new mail in these + folders are backup tools (updating access times) or filesystems mounted + without access time update support. + + In cases where new mail detection for Mbox or Mmdf folders appears to be + unreliable, the $check_mbox_size option can be used to make Mutt track and + consult file sizes for new mail detection instead. + +15. User defined headers + + Usage: + + my_hdr string + + unmy_hdr { * | field ... } + + The my_hdr command allows you to create your own header fields which will + be added to every message you send. + + For example, if you would like to add an "Organization:" header field to + all of your outgoing messages, you can put the command + + Example 3.10. Defining custom headers + + my_hdr Organization: A Really Big Company, Anytown, USA + + in your .muttrc. + + Note + + Space characters are not allowed between the keyword and the colon (":"). + The standard for electronic mail (RFC2822) says that space is illegal + there, so Mutt enforces the rule. + + If you would like to add a header field to a single message, you should + either set the $edit_headers variable, or use the function + (default: "E") in the compose 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 + +16. Specify default save mailbox + + Usage: + + save-hook [!]pattern mailbox + + This command is used to override the default mailbox used when saving + messages. mailbox will be used as the default if the message matches + pattern, see Message Matching in Hooks for information on the exact + format. + + To provide more flexibility and good defaults, Mutt applies the expandos + of $index_format to mailbox after it was expanded. + + Examples: + + Example 3.11. Using %-expandos in save-hook + + # default: save all to ~/Mail/ + save-hook . ~/Mail/%F + + # save from me@turing.cs.hmc.edu and me@cs.hmc.edu to $folder/elkins + save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins + + # save from aol.com to $folder/spam + save-hook aol\\.com$ +spam + + Also see the fcc-save-hook command. + +17. Specify default Fcc: mailbox when composing + + Usage: + + fcc-hook [!]pattern mailbox + + This command is used to save outgoing mail in a mailbox other than + $record. Mutt searches the initial list of message recipients for the + first matching regexp and uses mailbox as the default Fcc: mailbox. If no + match is found the message will be saved to $record mailbox. + + To provide more flexibility and good defaults, Mutt applies the expandos + of $index_format to mailbox after it was expanded. + + See Message Matching in Hooks for information on the exact format of + pattern. + + Example: fcc-hook [@.]aol\\.com$ +spammers + + The above will save a copy of all messages going to the aol.com domain to + the `+spammers' mailbox by default. Also see the fcc-save-hook command. + +18. Specify default save filename and default Fcc: mailbox at once + + Usage: + + fcc-save-hook [!]pattern mailbox + + This command is a shortcut, equivalent to doing both a fcc-hook and a + save-hook with its arguments, including %-expansion on mailbox according + to $index_format. + +19. Change settings based upon message recipients + + Usage: + + reply-hook [!]pattern command + + send-hook [!]pattern command + + send2-hook [!]pattern command + + These commands can be used to execute arbitrary configuration commands + based upon recipients of the message. pattern is used to match the + message, see Message Matching in Hooks for details. command is executed + when pattern matches. + + reply-hook is matched against the message you are replying to, instead of + the message you are sending. send-hook is matched against all messages, + both new and replies. + + Note + + reply-hooks are matched before the send-hook, regardless of the order + specified in the user's configuration file. + + send2-hook is matched every time a message is changed, either by editing + it, or by using the compose menu to change its recipients or subject. + send2-hook is executed after send-hook, and can, e.g., be used to set + parameters such as the $sendmail variable depending on the message's + sender address. + + For each type of send-hook or reply-hook, when multiple matches occur, + commands are executed in the order they are specified in the muttrc (for + that type of hook). + + 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 change the + language of the attributions and signatures based upon the recipients. + + Note + + send-hook's are only executed once after getting the initial list of + recipients. Adding a recipient after replying or editing the message will + not cause any send-hook to be executed. Also note that my_hdr commands + which modify recipient headers, or the message's subject, don't have any + effect on the current message when executed from a send-hook. + +20. Change settings before formatting a message + + Usage: + + message-hook [!]pattern command + + This command can be used to execute arbitrary configuration commands + before viewing or formatting a message based upon information about the + message. command is executed if the pattern matches the message to be + displayed. When multiple matches occur, commands are executed in the order + they are specified in the muttrc. + + See Message Matching in Hooks for information on the exact format of + pattern. + + Example: + + message-hook ~A 'set pager=builtin' + message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""' + +21. Choosing the cryptographic key of the recipient + + Usage: + + crypt-hook pattern keyid + + When encrypting messages with PGP/GnuPG or OpenSSL, you may want to + associate a certain key with a given e-mail address automatically, either + because the recipient's public key can't be deduced from the destination + address, or because, for some reasons, you need to override the key Mutt + would normally use. The crypt-hook command provides a method by which you + can specify the ID of the public key to be used when encrypting messages + to a certain recipient. + + The meaning of keyid is to be taken broadly in this context: You can + either put a numerical key ID here, an e-mail address, or even just a real + name. + +22. Adding key sequences to the keyboard buffer + + Usage: + + push string + + This command adds the named string to the keyboard buffer. The string may + contain control characters, key names and function names like the sequence + string in the macro command. You may use it to automatically run a + sequence of commands at startup, or when entering certain folders. For + example, the following command will automatically collapse all threads + when entering a folder: + + Example 3.12. Embedding push in folder-hook + + folder-hook . 'push ' + +23. Executing functions + + Usage: + + exec function [ function ...] + + This command can be used to execute any function. Functions are listed in + the function reference. "exec function" is equivalent to "push + ". + +24. Message Scoring + + Usage: + + score pattern value + + unscore { * | pattern ... } + + The score commands adds value to a message's score if pattern matches it. + pattern is a string in the format described in the patterns section (note: + For efficiency reasons, patterns which scan information not available in + the index, such as ~b, ~B or ~h, may not be used). value is a positive or + negative integer. A message's final score is the sum total of all matching + score entries. However, you may optionally prefix value with an equal sign + (=) to cause evaluation to stop at a particular entry if there is a match. + Negative final scores are rounded up to 0. + + The unscore command removes score entries from the list. You must specify + the same pattern specified in the score command for it to be removed. The + pattern "*" is a special token which means to clear the list of all score + entries. + +25. Spam detection + + Usage: + + spam pattern format + + nospam { * | pattern } + + Mutt has generalized support for external spam-scoring filters. By + defining your spam patterns with the spam and nospam commands, you can + limit, search, and sort your mail based on its spam attributes, as + determined by the external filter. You also can display the spam + attributes in your index display using the %H selector in the + $index_format variable. (Tip: try %?H?[%H] ? to display spam tags only + when they are defined for a given message.) + + Your first step is to define your external filter's spam patterns using + the spam command. pattern should be a regular expression that matches a + header in a mail message. If any message in the mailbox matches this + regular expression, it will receive a "spam tag" or "spam attribute" + (unless it also matches a nospam pattern -- see below.) The appearance of + this attribute is entirely up to you, and is governed by the format + parameter. format can be any static text, but it also can include + back-references from the pattern expression. (A regular expression + "back-reference" refers to a sub-expression contained within parentheses.) + %1 is replaced with the first back-reference in the regex, %2 with the + second, etc. + + If you're using multiple spam filters, a message can have more than one + spam-related header. You can define spam patterns for each filter you use. + If a message matches two or more of these patterns, and the + $spam_separator variable is set to a string, then the message's spam tag + will consist of all the format strings joined together, with the value of + $spam_separator separating them. + + For example, suppose I use DCC, SpamAssassin, and PureMessage. I might + define these spam settings: + + Example 3.13. Configuring spam detection + + spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1" + spam "X-Spam-Status: Yes" "90+/SA" + spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM" + set spam_separator=", " + + If I then received a message that DCC registered with "many" hits under + the "Fuz2" checksum, and that PureMessage registered with a 97% + probability of being spam, that message's spam tag would read + 90+/DCC-Fuz2, 97/PM. (The four characters before "=many" in a DCC report + indicate the checksum used -- in this case, "Fuz2".) + + If the $spam_separator variable is unset, then each spam pattern match + supersedes the previous one. Instead of getting joined format strings, + you'll get only the last one to match. + + The spam tag is what will be displayed in the index when you use %H in the + $index_format variable. It's also the string that the ~H pattern-matching + expression matches against for and functions. And it's + what sorting by spam attribute will use as a sort key. + + That's a pretty complicated example, and most people's actual environments + will have only one spam filter. The simpler your configuration, the more + effective mutt can be, especially when it comes to sorting. + + Generally, when you sort by spam tag, mutt will sort lexically -- that is, + by ordering strings alphanumerically. However, if a spam tag begins with a + number, mutt will sort numerically first, and lexically only when two + numbers are equal in value. (This is like UNIX's sort -n.) A message with + no spam attributes at all -- that is, one that didn't match any of your + spam patterns -- is sorted at lowest priority. Numbers are sorted next, + beginning with 0 and ranging upward. Finally, non-numeric strings are + sorted, with "a" taking lower priority than "z". Clearly, in general, + sorting by spam tags is most effective when you can coerce your filter to + give you a raw number. But in case you can't, mutt can still do something + useful. + + The nospam command can be used to write exceptions to spam patterns. If a + header pattern matches something in a spam command, but you nonetheless do + not want it to receive a spam tag, you can list a more precise pattern + under a nospam command. + + If the pattern given to nospam is exactly the same as the pattern on an + existing spam list entry, the effect will be to remove the entry from the + spam list, instead of adding an exception. Likewise, if the pattern for a + spam command matches an entry on the nospam list, that nospam entry will + be removed. If the pattern for nospam is "*", all entries on both lists + will be removed. This might be the default action if you use spam and + nospam in conjunction with a folder-hook. + + You can have as many spam or nospam commands as you like. You can even do + your own primitive spam detection within mutt -- for example, if you + consider all mail from MAILER-DAEMON to be spam, you can use a spam + command like this: + + spam "^From: .*MAILER-DAEMON" "999" + +26. Setting and Querying Variables + + 26.1. Commands + + The following commands are available to manipulate and query variables: + + Usage: + + set { [ no | inv ] variable | variable=value } [...] + + toggle variable [ variable ...] + + unset variable [ variable ...] + + reset variable [ variable ...] + + This command is used to set (and unset) configuration variables. There are + four basic types of variables: boolean, number, string and quadoption. + boolean variables can be set (true) or unset (false). number variables can + be assigned a positive integer value. string variables consist of any + number of printable characters and must be enclosed in quotes if they + contain spaces or tabs. You may also use the escape sequences "\n" and + "\t" for newline and tab, respectively. quadoption variables are used to + control whether or not to be prompted for certain actions, or to specify a + default action. A value of yes will cause the action to be carried out + automatically as if you had answered yes to the question. Similarly, a + value of no will cause the action to be carried out as if you had answered + "no." A value of ask-yes will cause a prompt with a default answer of + "yes" and ask-no will provide a default answer of "no." + + Prefixing a variable with "no" will unset it. Example: set noaskbcc. + + For boolean variables, you may optionally prefix the variable name with + inv to toggle the value (on or off). This is useful when writing macros. + Example: set invsmart_wrap. + + The toggle command automatically prepends the inv prefix to all specified + variables. + + The unset command automatically prepends the no prefix to all specified + variables. + + Using the function in the index menu, you can query the + 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 and quadoption + variables. + + The reset command resets all given variables to the compile time defaults + (hopefully mentioned in this manual). If you use the command set and + prefix the variable with "&" this has the same behavior as the reset + command. + + With the reset command there exists the special variable "all", which + allows you to reset all variables to their system defaults. + + 26.2. User-defined variables + + 26.2.1. Introduction + + Along with the variables listed in the Configuration variables section, + mutt supports user-defined variables with names starting with my_ as in, + for example, my_cfgdir. + + The set command either creates a custom my_ variable or changes its value + if it does exist already. The unset and reset commands remove the variable + entirely. + + Since user-defined variables are expanded in the same way that environment + variables are (except for the shell-escape command and backtick + expansion), this feature can be used to make configuration files more + readable. + + 26.2.2. Examples + + The following example defines and uses the variable my_cfgdir to + abbreviate the calls of the source command: + + Example 3.14. Using user-defined variables for config file readability + + set my_cfgdir = $HOME/mutt/config + + source $my_cfgdir/hooks + source $my_cfgdir/macros + # more source commands... + + A custom variable can also be used in macros to backup the current value + of another variable. In the following example, the value of the $delete is + changed temporarily while its original value is saved as my_delete. After + the macro has executed all commands, the original value of $delete is + restored. + + Example 3.15. Using user-defined variables for backing up other config + option values + + macro pager ,x '\ + set my_delete=$delete\ + set delete=yes\ + ...\ + set delete=$my_delete' + + Since mutt expands such values already when parsing the configuration + file(s), the value of $my_delete in the last example would be the value of + $delete exactly as it was at that point during parsing the configuration + file. If another statement would change the value for $delete later in the + same or another file, it would have no effect on $my_delete. However, the + expansion can be deferred to runtime, as shown in the next example, when + escaping the dollar sign. + + Example 3.16. Deferring user-defined variable expansion to runtime + + macro pager "\ + set my_old_pager_stop=\$pager_stop pager_stop\ + \ + set pager_stop=\$my_old_pager_stop\ + unset my_old_pager_stop" + + Note that there is a space between and the set + configuration command, preventing mutt from recording the macro's commands + into its history. + +27. Reading initialization commands from another file + + Usage: + + source filename + + This command allows the inclusion of initialization commands from other + files. For example, I place all of my aliases in ~/.mail_aliases so that I + can make my ~/.muttrc readable and keep my aliases private. + + 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 filename is considered + to be an executable program from which to read input (eg. source + ~/bin/myscript|). + +28. Configuring features conditionnaly + + Usage: ifdef item command + + This command allows to test if a feature has been compiled in, before + actually executing the command. Item can be either the name of a function, + variable, or command. Example: + + ifdef imap_keepalive 'source ~/.mutt/imap_setup' + +29. Removing hooks + + Usage: + + unhook { * | hook-type } + + This command permits you to flush hooks you have previously defined. You + can either remove all hooks by giving the "*" character as an argument, or + you can remove all hooks of a specific type by saying something like + unhook send-hook. + +30. Format Strings + + 30.1. Basic usage + + Format strings are a general concept you'll find in several locations + through the mutt configuration, especially in the $index_format, + $pager_format, $status_format, and other "*_format" variables. These can + be very straightforward, and it's quite possible you already know how to + use them. + + The most basic format string element is a percent symbol followed by + another character. For example, %s represents a message's Subject: header + in the $index_format variable. The "expandos" available are documented + with each format variable, but there are general modifiers available with + all formatting expandos, too. Those are our concern here. + + Some of the modifiers are borrowed right out of C (though you might know + them from Perl, Python, shell, or another language). These are the [-]m.n + modifiers, as in %-12.12s. As with such programming languages, these + modifiers allow you to specify the minimum and maximum size of the + resulting string, as well as its justification. If the "-" sign follows + the percent, the string will be left-justified instead of right-justified. + If there's a number immediately following that, it's the minimum amount of + space the formatted string will occupy -- if it's naturally smaller than + that, it will be padded out with spaces. If a decimal point and another + number follow, that's the maximum space allowable -- the string will not + be permitted to exceed that width, no matter its natural size. Each of + these three elements is optional, so that all these are legal format + strings: %-12s %4c %.15F %-12.15L + + Mutt adds some other modifiers to format strings. If you use an equals + symbol (=) as a numeric prefix (like the minus above), it will force the + string to be centered within its minimum space range. For example, %=14y + will reserve 14 characters for the %y expansion -- that's the X-Label: + header, in $index_format. If the expansion results in a string less than + 14 characters, it will be centered in a 14-character space. If the X-Label + for a message were "test", that expansion would look like " test ". + + There are two very little-known modifiers that affect the way that an + expando is replaced. If there is an underline ("_") character between any + format modifiers (as above) and the expando letter, it will expands in all + lower case. And if you use a colon (":"), it will replace all decimal + points with underlines. + + 30.2. Filters + + Any format string ending in a vertical bar ("|") will be expanded and + piped through the first word in the string, using spaces as separator. The + string returned will be used for display. If the returned string ends in + %, it will be passed through the formatter a second time. This allows the + filter to generate a replacement format string including % expandos. + + All % expandos in a format string are expanded before the script is called + so that: + + Example 3.17. Using external filters in format strings + + set status_format="script.sh '%r %f (%L)'|" + + will make mutt expand %r, %f and %L before calling the script. The example + also shows that arguments can be quoted: the script will receive the + expanded string between the single quotes as the only argument. + + A practical example is the mutt_xtitle script installed in the samples + subdirectory of the mutt documentation: it can be used as filter for + $status_format to set the current terminal's title, if supported. + +Chapter 4. Advanced Usage + + Table of Contents + + 1. Regular Expressions + + 2. Patterns: Searching, Limiting and Tagging + + 2.1. Pattern Modifier + + 2.2. Simple Patterns + + 2.3. Complex Patterns + + 2.4. Searching by Date + + 3. Using Tags + + 4. Using Hooks + + 4.1. Message Matching in Hooks + + 5. External Address Queries + + 6. Mailbox Formats + + 7. Mailbox Shortcuts + + 8. Handling Mailing Lists + + 9. Handling multiple folders + + 10. Editing threads + + 10.1. Linking threads + + 10.2. Breaking threads + + 11. Delivery Status Notification (DSN) Support + + 12. Start a WWW Browser on URLs + +1. Regular Expressions + + All string patterns in Mutt including those in more complex patterns must + be specified using regular expressions (regexp) in the "POSIX extended" + syntax (which is more or less the syntax used by egrep and GNU awk). For + your convenience, we have included below a brief description of this + syntax. + + The search is case sensitive if the pattern contains at least one upper + case letter, and case insensitive otherwise. + + Note + + Note that "\" must be quoted if used for a regular expression in an + initialization command: "\\". + + A regular expression is a pattern that describes a set of strings. Regular + expressions are constructed analogously to arithmetic expressions, by + using various operators to combine smaller expressions. + + Note + + Note that the regular expression can be enclosed/delimited by either " or + ' which is useful if the regular expression includes a white-space + character. See Syntax of Initialization Files for more information on " + and ' delimiter processing. To match a literal " or ' you must preface it + with \ (backslash). + + The fundamental building blocks are the regular expressions that match a + single character. Most characters, including all letters and digits, are + regular expressions that match themselves. Any metacharacter with special + meaning may be quoted by preceding it with a backslash. + + The period "." matches any single character. The caret "^" and the dollar + sign "$" are metacharacters that respectively match the empty string at + the beginning and end of a line. + + A list of characters enclosed by "[" and "]" matches any single character + in that list; if the first character of the list is a caret "^" then it + matches any character not in the list. For example, the regular expression + [0123456789] matches any single digit. A range of ASCII characters may be + specified by giving the first and last characters, separated by a hyphen + "-". Most metacharacters lose their special meaning inside lists. To + include a literal "]" place it first in the list. Similarly, to include a + literal "^" place it anywhere but first. Finally, to include a literal + hyphen "-" place it last. + + Certain named classes of characters are predefined. Character classes + consist of "[:", a keyword denoting the class, and ":]". The following + classes are defined by the POSIX standard in Table 4.1, "POSIX regular + expression character classes" + + Table 4.1. POSIX regular expression character classes + + +------------------------------------------------------------------------+ + | Character class | Description | + |-----------------+------------------------------------------------------| + | [:alnum:] | Alphanumeric characters | + |-----------------+------------------------------------------------------| + | [:alpha:] | Alphabetic characters | + |-----------------+------------------------------------------------------| + | [:blank:] | Space or tab characters | + |-----------------+------------------------------------------------------| + | [:cntrl:] | Control characters | + |-----------------+------------------------------------------------------| + | [:digit:] | Numeric characters | + |-----------------+------------------------------------------------------| + | | Characters that are both printable and visible. (A | + | [:graph:] | space is printable, but not visible, while an "a" is | + | | both) | + |-----------------+------------------------------------------------------| + | [:lower:] | Lower-case alphabetic characters | + |-----------------+------------------------------------------------------| + | [:print:] | Printable characters (characters that are not | + | | control characters) | + |-----------------+------------------------------------------------------| + | | Punctuation characters (characters that are not | + | [:punct:] | letter, digits, control characters, or space | + | | characters) | + |-----------------+------------------------------------------------------| + | [:space:] | Space characters (such as space, tab and formfeed, | + | | to name a few) | + |-----------------+------------------------------------------------------| + | [:upper:] | Upper-case alphabetic characters | + |-----------------+------------------------------------------------------| + | [:xdigit:] | Characters that are hexadecimal digits | + +------------------------------------------------------------------------+ + + A character class is only valid in a regular expression inside the + brackets of a character list. + + Note + + Note that the brackets in these class names are part of the symbolic + names, and must be included in addition to the brackets delimiting the + bracket list. For example, [[:digit:]] is equivalent to [0-9]. + + Two additional special sequences can appear in character lists. These + apply to non-ASCII character sets, which can have single symbols (called + collating elements) that are represented with more than one character, as + well as several characters that are equivalent for collating or sorting + purposes: + + Collating Symbols + + A collating symbol is a multi-character collating element enclosed + in "[." and ".]". For example, if "ch" is a collating element, + then [[.ch.]] is a regexp that matches this collating element, + while [ch] is a regexp that matches either "c" or "h". + + Equivalence Classes + + An equivalence class is a locale-specific name for a list of + characters that are equivalent. The name is enclosed in "[=" and + "=]". For example, the name "e" might be used to represent all of + "e" "e" and "e". In this case, [[=e=]] 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 described in Table 4.2, "Regular expression + repetition operators". + + Table 4.2. Regular expression repetition operators + + +------------------------------------------------------------------------+ + | Operator | Description | + |----------+-------------------------------------------------------------| + | ? | The preceding item is optional and matched at most once | + |----------+-------------------------------------------------------------| + | * | The preceding item will be matched zero or more times | + |----------+-------------------------------------------------------------| + | + | The preceding item will be matched one or more times | + |----------+-------------------------------------------------------------| + | {n} | The preceding item is matched exactly n times | + |----------+-------------------------------------------------------------| + | {n,} | The preceding item is matched n or more times | + |----------+-------------------------------------------------------------| + | {,m} | The preceding item is matched at most m times | + |----------+-------------------------------------------------------------| + | {n,m} | The preceding item is matched at least n times, but no more | + | | than m times | + +------------------------------------------------------------------------+ + + Two regular expressions may be concatenated; the resulting regular + expression matches any string formed by concatenating two substrings that + respectively match the concatenated subexpressions. + + Two regular expressions may be joined by the infix operator "|"; the + resulting regular expression matches any string matching either + subexpression. + + Repetition takes precedence over concatenation, which in turn takes + precedence over alternation. A whole subexpression may be enclosed in + parentheses to override these precedence rules. + + Note + + If you compile Mutt with the GNU rx package, the following operators may + also be used in regular expressions as described in Table 4.3, "GNU + regular expression extensions". + + Table 4.3. GNU regular expression extensions + + +------------------------------------------------------------------------+ + | Expression | Description | + |------------+-----------------------------------------------------------| + | \\y | Matches the empty string at either the beginning or the | + | | end of a word | + |------------+-----------------------------------------------------------| + | \\B | Matches the empty string within a word | + |------------+-----------------------------------------------------------| + | \\< | Matches the empty string at the beginning of a word | + |------------+-----------------------------------------------------------| + | \\> | Matches the empty string at the end of a word | + |------------+-----------------------------------------------------------| + | \\w | Matches any word-constituent character (letter, digit, or | + | | underscore) | + |------------+-----------------------------------------------------------| + | \\W | Matches any character that is not word-constituent | + |------------+-----------------------------------------------------------| + | \\` | Matches the empty string at the beginning of a buffer | + | | (string) | + |------------+-----------------------------------------------------------| + | \\' | Matches the empty string at the end of a buffer | + +------------------------------------------------------------------------+ + + Please note however that these operators are not defined by POSIX, so they + may or may not be available in stock libraries on various systems. + +2. Patterns: Searching, Limiting and Tagging + + Many of Mutt's commands allow you to specify a pattern to match (limit, + tag-pattern, delete-pattern, etc.). Table 4.4, "Pattern modifiers" shows + several ways to select messages. + + Table 4.4. Pattern modifiers + + +------------------------------------------------------------------------+ + | Pattern modifier | Description | + |------------------+-----------------------------------------------------| + | ~A | all messages | + |------------------+-----------------------------------------------------| + | ~b EXPR | messages which contain EXPR in the message body | + |------------------+-----------------------------------------------------| + | | messages which contain STRING in the message body. | + | =b STRING | If IMAP is enabled, searches for STRING on the | + | | server, rather than downloading each message and | + | | searching it locally. | + |------------------+-----------------------------------------------------| + | ~B EXPR | messages which contain EXPR in the whole message | + |------------------+-----------------------------------------------------| + | ~c EXPR | messages carbon-copied to EXPR | + |------------------+-----------------------------------------------------| + | %c GROUP | messages carbon-copied to any member of GROUP | + |------------------+-----------------------------------------------------| + | ~C EXPR | messages either to: or cc: EXPR | + |------------------+-----------------------------------------------------| + | %C GROUP | messages either to: or cc: to any member of GROUP | + |------------------+-----------------------------------------------------| + | ~d [MIN]-[MAX] | messages with "date-sent" in a Date range | + |------------------+-----------------------------------------------------| + | ~D | deleted messages | + |------------------+-----------------------------------------------------| + | ~e EXPR | messages which contains EXPR in the "Sender" field | + |------------------+-----------------------------------------------------| + | %e GROUP | messages which contain a member of GROUP in the | + | | "Sender" field | + |------------------+-----------------------------------------------------| + | ~E | expired messages | + |------------------+-----------------------------------------------------| + | ~F | flagged messages | + |------------------+-----------------------------------------------------| + | ~f EXPR | messages originating from EXPR | + |------------------+-----------------------------------------------------| + | %f GROUP | messages originating from any member of GROUP | + |------------------+-----------------------------------------------------| + | ~g | cryptographically signed messages | + |------------------+-----------------------------------------------------| + | ~G | cryptographically encrypted messages | + |------------------+-----------------------------------------------------| + | ~h EXPR | messages which contain EXPR in the message header | + |------------------+-----------------------------------------------------| + | ~H EXPR | messages with a spam attribute matching EXPR | + |------------------+-----------------------------------------------------| + | ~i EXPR | messages which match EXPR in the "Message-ID" field | + |------------------+-----------------------------------------------------| + | ~k | messages which contain PGP key material | + |------------------+-----------------------------------------------------| + | ~L EXPR | messages either originated or received by EXPR | + |------------------+-----------------------------------------------------| + | %L GROUP | message either originated or received by any member | + | | of GROUP | + |------------------+-----------------------------------------------------| + | ~l | messages addressed to a known mailing list | + |------------------+-----------------------------------------------------| + | ~m [MIN]-[MAX] | messages 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 | messages addressed to you (consults alternates) | + |------------------+-----------------------------------------------------| + | ~P | messages from you (consults alternates) | + |------------------+-----------------------------------------------------| + | ~Q | messages which have been replied to | + |------------------+-----------------------------------------------------| + | ~r [MIN]-[MAX] | messages with "date-received" in a Date range | + |------------------+-----------------------------------------------------| + | ~R | read messages | + |------------------+-----------------------------------------------------| + | ~s EXPR | messages having EXPR in the "Subject" field. | + |------------------+-----------------------------------------------------| + | ~S | superseded messages | + |------------------+-----------------------------------------------------| + | ~t EXPR | messages addressed to EXPR | + |------------------+-----------------------------------------------------| + | ~T | tagged messages | + |------------------+-----------------------------------------------------| + | ~u | messages addressed to a subscribed mailing list | + |------------------+-----------------------------------------------------| + | ~U | unread messages | + |------------------+-----------------------------------------------------| + | ~v | messages part of a collapsed thread. | + |------------------+-----------------------------------------------------| + | ~V | cryptographically verified messages | + |------------------+-----------------------------------------------------| + | ~x EXPR | messages which contain EXPR in the "References" | + | | field | + |------------------+-----------------------------------------------------| + | ~X [MIN]-[MAX] | messages with MIN to MAX attachments *) | + |------------------+-----------------------------------------------------| + | ~y EXPR | messages which contain EXPR in the "X-Label" field | + |------------------+-----------------------------------------------------| + | ~z [MIN]-[MAX] | messages with a size in the range MIN to MAX *) | + |------------------+-----------------------------------------------------| + | ~= | duplicated messages (see $duplicate_threads) | + |------------------+-----------------------------------------------------| + | ~$ | unreferenced messages (requires threaded view) | + |------------------+-----------------------------------------------------| + | | messages in threads containing messages matching | + | ~(PATTERN) | PATTERN, e.g. all threads containing messages from | + | | you: ~(~P) | + +------------------------------------------------------------------------+ + + Where EXPR is a regular expression. Special attention has to be made when + using regular expressions inside of patterns. Specifically, Mutt's parser + for these patterns will strip one level of backslash ("\"), which is + normally used for quoting. If it is your intention to use a backslash in + the regular expression, you will need to use two backslashes instead + ("\\"). You can force mutt to treat EXPR as a simple string instead of a + regular expression by using = instead of ~ in the pattern name. For + example, =b *.* will find all messages that contain the literal string + "*.*". Simple string matches are less powerful than regular expressions + but can be considerably faster. This is especially true for IMAP folders, + because string matches can be performed on the server instead of by + fetching every message. IMAP treats =h specially: it must be of the form + "header: substring" and will not partially match header names. The + substring part may be omitted if you simply wish to find messages + containing a particular header without regard to its value. + + *) The forms "<[MAX]", ">[MIN]", "[MIN]-" and "-[MAX]" are allowed, too. + + 2.1. Pattern Modifier + + Note + + Note that patterns matching 'lists' of addresses (notably c, C, p, P and + t) match if there is at least one match in the whole list. If you want to + make sure that all elements of that list match, you need to prefix your + pattern with "^". This example matches all mails which only has recipients + from Germany. + + ^~C \.de$ + + 2.2. Simple Patterns + + Mutt supports two versions of so called "simple searches" which are issued + if the query entered for searching, limiting and similar operations does + not seem to be a valid pattern (i.e. it does not contain one of these + characters: "~", "=" or "%"). If the query is supposed to contain one of + these special characters, they must be escaped by prepending a backslash + ("\"). + + The first type is by checking whether the query string equals a keyword + case-insensitively from Table 4.5, "Simple search keywords": If that is + the case, Mutt will use the shown pattern modifier instead. If a keyword + would conflict with your search keyword, you need to turn it into a + regular expression to avoid matching the keyword table. For example, if + you want to find all messages matching "flag" (using $simple_search) but + don't want to match flagged messages, simply search for "[f]lag". + + Table 4.5. Simple search keywords + + +----------------------------+ + | Keyword | Pattern modifier | + |---------+------------------| + | all | ~A | + |---------+------------------| + | . | ~A | + |---------+------------------| + | ^ | ~A | + |---------+------------------| + | del | ~D | + |---------+------------------| + | flag | ~F | + |---------+------------------| + | new | ~N | + |---------+------------------| + | old | ~O | + |---------+------------------| + | repl | ~Q | + |---------+------------------| + | read | ~R | + |---------+------------------| + | tag | ~T | + |---------+------------------| + | unread | ~U | + +----------------------------+ + + The second type of simple search is to build a complex search pattern + using $simple_search as a template. Mutt will insert your query properly + quoted and search for the composed complex query. + + 2.3. Complex Patterns + + 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 and that have the word "elkins" in the "From" header field. + + 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". + + Example 4.1. Using boolean operators in patterns + + !(~t mutt|~c mutt) ~f elkins + + Here is an example using white space in the regular expression (note the ' + and " delimiters). For this to match, the mail's subject must match the + "^Junk +From +Me$" and it must be from either "Jim +Somebody" or "Ed + +SomeoneElse": + + '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")' + + Note + + If a regular expression contains parenthesis, or a vertical bar ("|"), you + must enclose the expression in double or single quotes since those + characters are also used to separate different parts of Mutt's pattern + language. For example: ~f "me@(mutt\.org|cs\.hmc\.edu)" + + Without the quotes, the parenthesis wouldn't end. This would be separated + to two OR'd patterns: ~f me@(mutt\.org and cs\.hmc\.edu). They are never + what you want. + + 2.4. Searching by Date + + Mutt supports two types of dates, absolute and relative. + + Absolute. Dates must be in DD/MM/YY format (month and year are 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 before the given date will be selected. If you omit the maximum + (second) date, and specify "DD/MM/YY-", all messages after the given date + will be selected. If you specify a single date with no dash ("-"), only + messages sent on the given date will be selected. + + Error Margins. You can add error margins to absolute dates. An error + margin is a sign (+ or -), followed by a digit, followed by one of the + units in Table 4.6, "Date units". As a special case, you can replace the + sign by a "*" character, which is equivalent to giving identical plus and + minus error margins. + + Table 4.6. Date units + + +--------------------+ + | Unit | Description | + |------+-------------| + | y | Years | + |------+-------------| + | m | Months | + |------+-------------| + | w | Weeks | + |------+-------------| + | d | Days | + +--------------------+ + + Example: To select any messages two weeks around January 15, 2001, you'd + use the following pattern: + + Limit to messages matching: ~d 15/1/2001*2w + + Relative. This type of date is relative to the current date, and may be + specified as: + + o >offset (messages older than offset units) + + o function, which is bound to "shift-T" by default. Or you can + select individual messages by hand using the function, which + is bound to "t" by default. See patterns for Mutt's pattern matching + syntax. + + Once you have tagged the desired messages, you can use the "tag-prefix" + operator, which is the ";" (semicolon) key by default. When the + "tag-prefix" operator is used, the next operation will be applied to all + tagged messages if that operation can be used in that manner. If the + $auto_tag variable is set, the next operation applies to the tagged + messages automatically, without requiring the "tag-prefix". + + In macros or push commands, you can use the "tag-prefix-cond" operator. If + there are no tagged messages, mutt will "eat" the rest of the macro to + abort it's execution. Mutt will stop "eating" the macro when it encounters + the "end-cond" operator; after this operator the rest of the macro will be + executed as normal. + +4. Using Hooks + + A hook is a concept found in many other programs which allows you to + execute arbitrary commands before performing some operation. For example, + you may wish to tailor your configuration based upon which mailbox you are + reading, or to whom you are sending mail. In the Mutt world, a hook + consists of a regular expression or pattern along with a configuration + option/command. See + + o folder-hook + + o send-hook + + o message-hook + + o save-hook + + o mbox-hook + + o fcc-hook + + o fcc-save-hook + + for specific details on each type of hook available. + + Note + + If a hook changes configuration settings, these changes remain effective + until the end of the current mutt session. As this is generally not + desired, a default hook needs to be added before all other hooks to + restore configuration defaults. Here is an example with send-hook and the + my_hdr directive: + + Example 4.2. Combining send-hook and my_hdr + + send-hook . 'unmy_hdr From:' + send-hook ~C'^b@b\.b$' my_hdr from: c@c.c + + 4.1. Message Matching in Hooks + + Hooks that act upon messages (message-hook, reply-hook, send-hook, + send2-hook, save-hook, fcc-hook) are evaluated in a slightly different + manner. For the other types of hooks, a regular expression is sufficient. + But in dealing with messages a finer grain of control is needed for + matching since for different purposes you want to match different + criteria. + + Mutt allows the use of the search pattern language for matching messages + in hook commands. This works in exactly the same way as it would when + limiting or searching the mailbox, except that you are restricted to those + operators which match information mutt extracts from the header of the + message (i.e., from, to, cc, date, subject, etc.). + + 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 me@cs.hmc.edu. + + However, it is not required that you write the pattern to match using the + full searching language. You can still specify a simple regular expression + like the other hooks, in which case Mutt will translate your pattern into + the full language, using the translation specified by the $default_hook + variable. The pattern is translated at the time the hook is declared, so + the value of $default_hook that is in effect at that time will be used. + +5. External Address Queries + + Mutt supports connecting to external directory databases such as LDAP, + ph/qi, bbdb, or NIS through a wrapper script which connects to mutt 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, then each matching response on a single line, + each line containing a tab separated address then name then some other + optional information. On error, or if there are no matching addresses, + return a non-zero exit code and a one line error message. + + 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@does-not-exist.org 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 function (default: Q). + This will prompt for a query, then bring up the query menu which will list + the matching responses. From the query menu, you can select addresses to + create aliases, or to mail. You can tag multiple addresses to mail, start + a new query, or have a new query appended to the current responses. + + The other mechanism for accessing the query function is for address + completion, similar to the alias completion. In any prompt for address + entry, you can use the function (default: ^T) to run a + query based on the current address you have typed. Like aliases, mutt will + look for what you have typed back to the last space or comma. If there is + a single response for that query, mutt will expand the address in place. + If there are multiple responses, mutt will activate the query menu. At the + query menu, you can select one or more addresses to be added to the + prompt. + +6. Mailbox Formats + + Mutt supports reading and writing of four different mailbox formats: mbox, + MMDF, MH and Maildir. The mailbox type is autodetected, so there is no + need to use a flag for different mailbox types. When creating new + mailboxes, Mutt uses the default specified with the $mbox_type variable. + + mbox. This is the most widely used mailbox format for UNIX. All 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). + + MMDF. This is a variant of the mbox format. Each message is surrounded by + lines containing "^A^A^A^A" (four control-A's). + + MH. A radical departure from mbox and MMDF, a mailbox consists of a + directory and each message is stored in a separate file. The filename + indicates the message number (however, this is may not correspond to the + message number Mutt displays). Deleted messages are renamed with a comma + (,) prepended to the filename. Mutt detects this type of mailbox by + looking for either .mh_sequences or .xmhcache (needed to distinguish + normal directories from MH mailboxes). + + Maildir. The newest of the mailbox formats, used by the Qmail MTA (a + replacement for sendmail). Similar to MH, except that it adds three + subdirectories of the mailbox: tmp, new and cur. Filenames for the + messages are chosen in such a way they are unique, even when two programs + are writing the mailbox over NFS, which means that no file locking is + needed. + +7. Mailbox Shortcuts + + 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 $spoolfile (incoming) mailbox + + o > -- refers to your $mbox file + + o < -- refers to your $record file + + o ^ -- refers to the current mailbox + + o - or !! -- refers to the file you've last visited + + o ~ -- refers to your home directory + + o = or + -- refers to your $folder directory + + o @alias -- refers to the default save folder as determined by the + address of the alias + +8. Handling Mailing Lists + + 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 does not have + to be a mailing list, but that is what it is most often used for), and + what lists you are subscribed to. This is accomplished through the use of + the lists and subscribe commands in your muttrc. + + Now that Mutt knows what your mailing lists are, it can do several things, + the first of which is the ability to show the name of a list through which + you received a message (i.e., of a subscribed list) in the index menu + display. This is useful to distinguish between personal 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 the message + they reply to from the list, resulting in two or more copies being sent to + that person. The function, which by default is bound to "L" + in the index menu and pager, helps reduce the clutter by only replying to + the known mailing list addresses instead of all recipients (except as + specified by Mail-Followup-To, see below). + + Mutt also supports the Mail-Followup-To header. When you send a message to + a list of recipients which includes one or several subscribed mailing + lists, and if the $followup_to option is set, mutt will generate a + Mail-Followup-To header which contains all the recipients to whom you send + this message, but not your address. This indicates that group-replies or + list-replies (also known as "followups") to this message should only be + sent to the original recipients of the message, and not separately to you + - you'll receive your copy through one of the mailing lists you are + subscribed to. + + Conversely, when group-replying or list-replying to a message which has a + Mail-Followup-To header, mutt will respect this header if the + $honor_followup_to configuration variable is set. Using list-reply will in + this case also make sure that the reply goes to the mailing list, even if + it's not specified in the list of recipients in the Mail-Followup-To. + + Note + + When header editing is enabled, you can create a Mail-Followup-To header + manually. Mutt will only auto-generate this header if it doesn't exist + when you send the message. + + The other method some mailing list admins use is to generate a "Reply-To" + field which points back to the mailing list address rather than the author + of the message. This can create problems when trying to reply directly to + the author in private, since most mail clients will automatically reply to + the address given in the "Reply-To" field. Mutt uses the $reply_to + variable to help decide which address to use. If set to ask-yes or ask-no, + you will be prompted as to whether or not you would like to use the + address given in the "Reply-To" field, or reply directly to the address + given in the "From" field. When set to yes, the "Reply-To" field will be + used when present. + + The "X-Label:" header field can be used to further identify mailing lists + or list subject matter (or just to annotate messages individually). The + $index_format variable's "%y" and "%Y" escapes can be used to expand + "X-Label:" fields in the index, and Mutt's pattern-matcher can match + regular expressions to "X-Label:" fields with the "~y" selector. + "X-Label:" is not a standard message header field, but it can easily be + inserted by procmail and other mail filtering agents. + + Lastly, Mutt has the ability to sort the mailbox into threads. A thread is + a group of messages which all relate to the same subject. This is usually + organized into a tree-like structure where a message and all of its + replies are represented graphically. If you've ever used a threaded news + client, this is the same concept. It makes dealing with large volume + mailing lists easier because you can easily delete uninteresting threads + and quickly find topics of value. + +9. Handling multiple folders + + Mutt supports setups with multiple folders, allowing all of them to be + monitored for new mail (see Section 14, "Monitoring incoming mail" for + details). + + When in the index menu and being idle (also see $timeout), Mutt + periodically checks for new mail in all folders which have been configured + via the mailboxes command. The interval depends on the folder type: for + local/IMAP folders it consults $mail_check and $pop_checkinterval for POP + folders. + + Outside the index menu the directory browser supports checking for new + mail using the function which is unbound by default. Pressing + TAB will bring up a menu showing the files specified by the mailboxes + command, and indicate which contain new messages. Mutt will automatically + enter this mode when invoked from the command line with the -y option. + + For the pager, index and directory browser menus, Mutt contains the + function (bound to "." by default) which will print a list of + folders with new mail in the command line at the bottom of the screen. + + For the index, by default Mutt displays the number of mailboxes with new + mail in the status bar, please refer to the $index_format variable for + details. + + When changing folders, Mutt fills the prompt with the first folder from + the mailboxes list containing new mail (if any), pressing space will cycle + through folders with new mail. + +10. Editing threads + + Mutt has the ability to dynamically restructure threads that are broken + either by misconfigured software or bad behavior from some correspondents. + This allows to clean your mailboxes formats) from these annoyances which + make it hard to follow a discussion. + + 10.1. Linking threads + + Some mailers tend to "forget" to correctly set the "In-Reply-To:" and + "References:" headers when replying to a message. This results in broken + discussions because Mutt has not enough information to guess the correct + threading. You can fix this by tagging the reply, then moving to the + parent message and using the function (bound to & by + default). The reply will then be connected to this "parent" message. + + You can also connect multiple children at once, tagging them and using the + tag-prefix command (';') or the auto_tag option. + + 10.2. Breaking threads + + On mailing lists, some people are in the bad habit of starting a new + discussion by hitting "reply" to any message from the list and changing + the subject to a totally unrelated one. You can fix such threads by using + the function (bound by default to #), which will turn the + subthread starting from the current message into a whole different thread. + +11. Delivery Status Notification (DSN) Support + + RFC1894 defines a set of MIME content types for relaying information about + the status of electronic mail messages. These can be thought of as "return + receipts." + + To support DSN, there are two variables. $dsn_notify is used to request + receipts for different results (such as failed message, message delivered, + etc.). $dsn_return requests how much of your message should be returned + with the receipt (headers or full message). + + When using $sendmail for mail delivery, you need to use either Berkeley + sendmail 8.8.x (or greater) a MTA supporting DSN command line options + compatible to Sendmail: The -N and -R options can be used by the mail + client to make requests as to what type of status messages should be + returned. Please consider your MTA documentation whether DSN is supported. + + For SMTP delivery using $smtp_url, it depends on the capabilities + announced by the server whether mutt will attempt to request DSN or not. + +12. Start a WWW Browser on URLs + + If a message contains URLs, it is efficient to get a menu with all the + URLs and start a WWW browser on one of them. This functionality is + provided by the external urlview program which can be retrieved at + ftp://ftp.mutt.org/mutt/contrib/ and the configuration commands: + + macro index \cb |urlview\n + macro pager \cb |urlview\n + +1. Compressed folders Support (OPTIONAL) + + If Mutt was compiled with compressed folders support (by running the + configure script with the --enable-compressed flag), Mutt can open folders + stored in an arbitrary format, provided that the user has a script to + convert from/to this format to one of the accepted. The most common use is + to open compressed archived folders e.g. with gzip. In addition, the user + can provide a script that gets a folder in an accepted format and appends + its context to the folder in the user-defined format, which may be faster + than converting the entire folder to the accepted format, appending to it + and converting back to the user-defined format. There are three hooks + defined (open-hook, close-hook and append-hook) which define commands to + uncompress and compress a folder and to append messages to an existing + compressed folder respectively. For example: + + open-hook \\.gz$ "gzip -cd %f > %t" + close-hook \\.gz$ "gzip -c %t > %f" + append-hook \\.gz$ "gzip -c %t >> %f" + + You do not have to specify all of the commands. If you omit append-hook, + the folder will be open and closed again each time you will add to it. If + you omit close-hook (or give empty command) , the folder will be open in + the mode. If you specify append-hook though you'll be able to append to + the folder. Note that Mutt will only try to use hooks if the file is not + in one of the accepted formats. In particular, if the file is empty, mutt + supposes it is not compressed. This is important because it allows the use + of programs that do not have well defined extensions. Just use "." as a + regexp. But this may be surprising if your compressing script produces + empty files. In this situation, unset $save_empty, so that the compressed + file will be removed if you delete all of the messages. + + 1.1. Open a compressed mailbox for reading + + Usage: open-hook regexp "command" The command is the command that can be + used for opening the folders whose names match regexp. The command string + is the printf-like format string, and it should accept two parameters: %f, + which is replaced with the (compressed) folder name, and %t which is + replaced with the name of the temporary folder to which to write. %f and + %t can be repeated any number of times in the command string, and all of + the entries are replaced with the appropriate folder name. In addition, %% + is replaced by %, as in printf, and any other %anything is left as is. The + command should not remove the original compressed file. The command should + return non-zero exit status if it fails, so mutt knows something's wrong. + Example: + + open-hook \\.gz$ "gzip -cd %f > %t" + + If the command is empty, this operation is disabled for this file type. + + 1.2. Write a compressed mailbox + + Usage: close-hook regexp "command" This is used to close the folder that + was open with the open-hook command after some changes were made to it. + The command string is the command that can be used for closing the folders + whose names match regexp. It has the same format as in the open-hook + command. Temporary folder in this case is the folder previously produced + by the open-hook command. The command should not remove the decompressed + file. The command should return non-zero exit status if it fails, so mutt + knows something's wrong. Example: + + close-hook \\.gz$ "gzip -c %t > %f" + + If the command is empty, this operation is disabled for this file type, + and the file can only be open in the read-only mode. close-hook is not + called when you exit from the folder if the folder was not changed. + + 1.3. Append a message to a compressed mailbox + + Usage: append-hook regexp "command" This command is used for saving to an + existing compressed folder. The command is the command that can be used + for appending to the folders whose names match regexp. It has the same + format as in the open-hook command. The temporary folder in this case + contains the messages that are being appended. The command should not + remove the decompressed file. The command should return non-zero exit + status if it fails, so mutt knows something's wrong. Example: + + append-hook \\.gz$ "gzip -c %t >> %f" + + When append-hook is used, the folder is not opened, which saves time, but + this means that we can not find out what the folder type is. Thus the + default ($mbox_type) type is always supposed (i.e. this is the format used + for the temporary folder). If the file does not exist when you save to it, + close-hook is called, and not append-hook. append-hook is only for + appending to existing folders. If the command is empty, this operation is + disabled for this file type. In this case, the folder will be open and + closed again (using open-hook and close-hookrespectively) each time you + will add to it. + + 1.4. Encrypted folders + + The compressed folders support can also be used to handle encrypted + folders. If you want to encrypt a folder with PGP, you may want to use the + following hooks: + + open-hook \\.pgp$ "pgp -f < %f > %t" + close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" + + Please note, that PGP does not support appending to an encrypted folder, + so there is no append-hook defined. If you are using GnuPG instead of PGP, + you may use the following hooks instead: + + open-hook \\.gpg$ "gpg --decrypt < %f > %t" + close-hook \\.gpg$ "gpg --encrypt --recipient YourGpgUserIdOrKeyId < %t > %f" + + Note: the folder is temporary stored decrypted in the /tmp directory, + where it can be read by your system administrator. So think about the + security aspects of this. + +Chapter 5. Mutt's MIME Support + + Table of Contents + + 1. Using MIME in Mutt + + 1.1. Viewing MIME messages in the pager + + 1.2. The Attachment Menu + + 1.3. The Compose Menu + + 2. MIME Type configuration with mime.types + + 3. MIME Viewer configuration with mailcap + + 3.1. The Basics of the mailcap file + + 3.2. Secure use of mailcap + + 3.3. Advanced mailcap Usage + + 3.4. Example mailcap files + + 4. MIME Autoview + + 5. MIME Multipart/Alternative + + 6. Attachment Searching and Counting + + 7. MIME Lookup + + Quite a bit of effort has been made to make Mutt the premier text-mode + MIME MUA. Every effort has been made to provide the functionality that the + discerning MIME user requires, and the conformance to the standards + wherever possible. When configuring Mutt for MIME, there are two extra + types of configuration files which Mutt uses. One is the mime.types file, + which contains the mapping of file extensions to IANA MIME types. The + other is the mailcap file, which specifies the external commands to use + for handling specific MIME types. + +1. Using MIME in Mutt + + 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. + + 1.1. Viewing MIME messages in the pager + + When you select a message from the index and view it in the pager, Mutt + decodes the message to a text representation. Mutt internally supports a + number of MIME types, including text/plain, text/enriched, message/rfc822, + and message/news. In addition, the export controlled version of Mutt + recognizes a variety of PGP MIME types, including PGP/MIME and + application/pgp. + + 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-printable/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) --] + + 1.2. The Attachment Menu + + The default binding for view-attachments is `v', which displays the + attachment menu for a message. The attachment menu displays a list of the + attachments in a message. From the attachment menu, you can save, print, + pipe, delete, and view attachments. You can apply these operations to a + group of attachments at once, by tagging the attachments and by using the + "tag-prefix" operator. You can also reply to the current message from this + menu, and only the current attachment (or the attachments tagged) will be + quoted in your reply. You can view attachments as text, or view them using + the mailcap viewer definition. + + Finally, you can apply the usual message-related functions (like + , and the and functions) to attachments + of type message/rfc822. + + See the help on the attachment menu for more information. + + 1.3. The Compose Menu + + The compose menu is the menu you see before you send a message. It allows + you to edit the recipient list, the subject, and other aspects of your + message. It also contains a list of the attachments of your message, + including the main body. From this menu, you can print, copy, filter, + pipe, edit, compose, review, and rename an attachment or a list of tagged + attachments. You can also modifying the attachment information, notably + the type, encoding and description. + + Attachments appear as follows: + + - 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 (or + postponing, or canceling) 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 the edit-type command (default: ^T). + The next field is the encoding for the attachment, which allows a binary + message to be encoded for transmission on 7bit links. It can be changed + with the edit-encoding command (default: ^E). The next field is the size + of the attachment, rounded to kilobytes or megabytes. The next field is + the filename, which can be changed with the rename-file command (default: + R). The final field is the description of the attachment, and can be + changed with the edit-description command (default: d). + +2. MIME Type configuration with mime.types + + When you add an attachment to your mail message, Mutt searches your + personal mime.types file at ${HOME}/.mime.types, and then the system + mime.types file at /usr/local/share/mutt/mime.types or /etc/mime.types + + 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 as + text/plain. If the file contains binary information, then Mutt will mark + it as application/octet-stream. You can change the MIME type that Mutt + assigns to an attachment by using the edit-type command from the compose + menu (default: ^T). The MIME type is actually a major mime type followed + by the sub-type, separated by a '/'. 6 major types: application, text, + image, video, audio, and model have been approved after various internet + discussions. Mutt recognizes all of these if the appropriate entry is + found in the mime.types file. It also recognizes other major mime types, + such as the chemical type that is widely used in the molecular modeling + community to pass molecular data in various forms to various molecular + viewers. Non-recognized mime types should only be used if the recipient of + the message is likely to be expecting such attachments. + +3. MIME Viewer configuration with mailcap + + Mutt supports RFC 1524 MIME Configuration, in particular the Unix specific + format specified in Appendix A of RFC 1524. This file format is commonly + referred to as the mailcap format. Many MIME compliant programs utilize + the mailcap format, allowing you to specify handling for all MIME types in + one place for all programs. Programs known to use this format include + Netscape, XMosaic, lynx and metamail. + + In order to handle various MIME types that Mutt can not handle internally, + Mutt parses a series of external configuration files to find an external + handler. The default search string for these files is a colon delimited + list containing the following files: + + 1. $HOME/.mailcap + + 2. $PKGDATADIR/mailcap + + 3. $SYSCONFDIR/mailcap + + 4. /etc/mailcap + + 5. /usr/etc/mailcap + + 6. /usr/local/etc/mailcap + + where $HOME is your home directory. The $PKGDATADIR and the $SYSCONFDIR + directories depend on where mutt is installed: the former is the default + for shared data, the latter for system configuration files. + + The default search path can be obtained by running the following command: + + mutt -nF /dev/null -Q mailcap_path + + In particular, the metamail distribution will install a mailcap file, + usually as /usr/local/etc/mailcap, which contains some baseline entries. + + 3.1. The Basics of the mailcap file + + A mailcap file consists of a series of lines which are comments, blank, or + definitions. + + A comment line consists of a # character followed by anything you want. + + A blank line is blank. + + A definition line consists of a content type, a view command, and any + number of optional fields. Each field of a definition line is divided by a + semicolon ';' character. + + The content type is specified in the MIME standard type/subtype method. + For example, text/plain, text/html, image/gif, etc. In addition, the + mailcap format includes two formats for wildcards, one using the special + '*' subtype, the other is the implicit wild, where you only include the + major type. For example, image/*, or video, will match all image types and + video types, respectively. + + The view command is a Unix command for viewing the type specified. There + are two different types of commands supported. The default is to send the + body of the MIME message to the command on stdin. You can change this + behavior by using %s as a parameter to your view command. This will cause + Mutt to save the body of the MIME message to a temporary file, and then + call the view command with the %s replaced by the name of the temporary + file. In both cases, Mutt will turn over the terminal to the view program + until the program quits, at which time Mutt will remove the temporary file + if it exists. + + So, in the simplest form, you can send a text/plain message to the + external pager more on stdin: + + 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. + + Note + + Some older versions of lynx contain a bug where they will check the + mailcap file for a viewer for text/html. They will find the line which + calls lynx, and run it. This causes lynx to continuously spawn itself to + view the object. + + On the other hand, maybe you don't want to use lynx interactively, you + 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. + + 3.2. Secure use of mailcap + + The interpretation of shell meta-characters embedded in MIME parameters + can lead to security problems in general. Mutt tries to quote parameters + in expansion of %s syntaxes properly, and avoids risky characters by + substituting them, see the $mailcap_sanitize variable. + + Although mutt's procedures to invoke programs with mailcap seem to be + safe, there are other applications parsing mailcap, maybe taking less care + of it. Therefore you should pay attention to the following rules: + + Keep the %-expandos away from shell quoting. Don't quote them with single + or double quotes. Mutt does this for you, the right way, as should any + other program which interprets mailcap. Don't put them into backtick + expansions. Be highly careful with eval statements, and avoid them if + possible at all. Trying to fix broken behavior with quotes introduces new + leaks - there is no alternative to correct quoting in the first place. + + If you have to use the %-expandos' values in context where you need + quoting or backtick expansions, put that value into a shell variable and + reference the shell variable where necessary, as in the following example + (using $charset inside the backtick expansion is safe, since it is not + itself subject to any further expansion): + + text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ + && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1 + + 3.3. Advanced mailcap Usage + + 3.3.1. Optional Fields + + In addition to the required content-type and view command fields, you can + add semi-colon ';' separated fields to set flags and other options. Mutt + recognizes the following optional fields: + + copiousoutput + + This flag tells Mutt that the command passes possibly large + amounts of text on stdout. This causes Mutt to invoke a pager + (either the internal pager or the external pager defined by the + pager variable) on the output of the view command. Without this + flag, Mutt assumes that the command is interactive. One could 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. + + needsterminal + + Mutt uses this flag when viewing attachments with auto_view, in + order to decide whether it should honor the setting of the + $wait_key variable or not. When an attachment is viewed using an + interactive program, and the corresponding mailcap entry has a + needsterminal flag, Mutt will use $wait_key and the exit status of + the program to decide if it will ask you to press a key after the + external program has exited. In all other situations it will not + prompt you for a key. + + compose= + + This flag specifies the command to use to create a new attachment + of a specific MIME type. Mutt supports this from the compose menu. + + composetyped= + + This flag specifies the command to use to create a new attachment + of a specific MIME type. This command differs from the compose + command in that mutt will expect standard MIME headers on the + data. This can be used to specify parameters, filename, + description, etc. for a new attachment. Mutt supports this from + the compose menu. + + print= + + This flag specifies the command to use to print a specific MIME + type. Mutt supports this from the attachment and compose menus. + + edit= + + This flag specifies the command to use to edit a specific MIME + type. Mutt supports this from the compose menu, and also uses it + to compose new attachments. Mutt will default to the defined + editor for text attachments. + + nametemplate=