From 58fbf95737a7601f6e139e39b9f69d102c7e858d Mon Sep 17 00:00:00 2001 From: nion Date: Tue, 1 Mar 2005 17:24:15 +0000 Subject: [PATCH] Nico Golde: fixed the documentation issue with escape sequences in manual.txt git-svn-id: svn://svn.berlios.de/mutt-ng/trunk@124 e385b8ad-14ed-0310-8656-cc95a2468c6d --- doc/Makefile.in | 2 +- doc/manual.txt | 4990 +++++++++++++++++++++++++++-------------------- 2 files changed, 2833 insertions(+), 2159 deletions(-) diff --git a/doc/Makefile.in b/doc/Makefile.in index fce11af..c42ec5c 100644 --- a/doc/Makefile.in +++ b/doc/Makefile.in @@ -102,7 +102,7 @@ uninstall: check: manual.txt: manual.sgml - if sgml2txt -c latin manual ; then \ + if linuxdoc -B txt --pass='-P -c' manual ; then \ uniq < manual.txt | expand > _manual.txt ; \ rm manual.txt ; \ mv _manual.txt manual.txt ;\ diff --git a/doc/manual.txt b/doc/manual.txt index 0b9b62f..6c8cec7 100644 --- a/doc/manual.txt +++ b/doc/manual.txt @@ -8,16 +8,15 @@ Table of Contents 1. Introduction - 1.1 Mutt Home Page - 1.2 Mailing Lists - 1.3 Software Distribution Sites - 1.4 IRC - 1.5 USENET - 1.6 Copyright + 1.2 Mutt-ng Home Page + 1.3 Mailing Lists + 1.4 Software Distribution Sites + 1.5 IRC + 1.6 Weblog + 1.7 Copyright 2. Getting Started - 2.1 Moving Around in Menus 2.2 Editing Input Fields 2.3 Reading Mail - The Index and Pager @@ -35,7 +34,6 @@ 2.7 Reading news via NNTP 3. Configuration - 3.1 Syntax of Initialization Files 3.2 Defining/Using aliases 3.3 Changing the default key bindings @@ -65,7 +63,6 @@ 3.27 Removing hooks 4. Advanced Usage - 4.1 Regular Expressions 4.2 Patterns 4.2.1 Pattern Modifier @@ -74,26 +71,34 @@ 4.3 Using Tags 4.4 Using Hooks 4.4.1 Message Matching in Hooks - 4.5 External Address Queries - 4.6 Mailbox Formats - 4.7 Mailbox Shortcuts - 4.8 Handling Mailing Lists - 4.9 Delivery Status Notification (DSN) Support - 4.10 POP3 Support (OPTIONAL) - 4.11 IMAP Support (OPTIONAL) - 4.11.1 The Folder Browser - 4.11.2 Authentication - 4.12 Managing multiple IMAP/POP accounts (OPTIONAL) - 4.13 Start a WWW Browser on URLs (EXTERNAL) + 4.5 Usingg the sidebar + 4.6 External Address Queries + 4.7 Mailbox Formats + 4.8 Mailbox Shortcuts + 4.9 Handling Mailing Lists + 4.10 Editing threads + 4.10.1 Linking threads + 4.10.2 Breaking threads + 4.11 Delivery Status Notification (DSN) Support + 4.12 POP3 Support (OPTIONAL) + 4.13 IMAP Support (OPTIONAL) + 4.13.1 The Folder Browser + 4.13.2 Authentication + 4.14 Managing multiple IMAP/POP accounts (OPTIONAL) + 4.15 Start a WWW Browser on URLs (EXTERNAL) + 4.16 Compressed folders Support (OPTIONAL) + 4.16.1 Open a compressed mailbox for reading + 4.16.2 Write a compressed mailbox + 4.16.3 Append a message to a compressed mailbox + 4.16.4 Encrypted folders 5. Mutt's MIME Support - 5.1 Using MIME in Mutt 5.1.1 Viewing MIME messages in the pager 5.1.2 The Attachment Menu 5.1.3 The Compose Menu - 5.2 MIME Type configuration with - 5.3 MIME Viewer configuration with + 5.2 MIME Type configuration with mime.types + 5.3 MIME Viewer configuration with mailcap 5.3.1 The Basics of the mailcap file 5.3.2 Secure use of mailcap 5.3.3 Advanced mailcap Usage @@ -106,7 +111,6 @@ 5.6 MIME Lookup 6. Reference - 6.1 Command line options 6.2 Configuration Commands 6.3 Configuration variables @@ -118,286 +122,319 @@ 6.3.6 allow_ansi 6.3.7 arrow_cursor 6.3.8 ascii_chars - 6.3.9 askbcc - 6.3.10 askcc - 6.3.11 ask_follow_up - 6.3.12 ask_x_comment_to - 6.3.13 attach_format - 6.3.14 attach_sep - 6.3.15 attach_split - 6.3.16 attribution - 6.3.17 autoedit + 6.3.9 ask_follow_up + 6.3.10 ask_x_comment_to + 6.3.11 askbcc + 6.3.12 askcc + 6.3.13 assumed_charset + 6.3.14 attach_format + 6.3.15 attach_sep + 6.3.16 attach_split + 6.3.17 attribution 6.3.18 auto_tag - 6.3.19 beep - 6.3.20 beep_new - 6.3.21 bounce - 6.3.22 bounce_delivered - 6.3.23 catchup_newsgroup - 6.3.24 charset - 6.3.25 check_new - 6.3.26 collapse_unread - 6.3.27 uncollapse_jump - 6.3.28 compose_format - 6.3.29 confirmappend - 6.3.30 confirmcreate - 6.3.31 connect_timeout - 6.3.32 content_type - 6.3.33 copy - 6.3.34 crypt_autopgp - 6.3.35 crypt_autosmime - 6.3.36 date_format - 6.3.37 default_hook - 6.3.38 delete - 6.3.39 delete_untag - 6.3.40 digest_collapse - 6.3.41 display_filter - 6.3.42 dotlock_program - 6.3.43 dsn_notify - 6.3.44 dsn_return - 6.3.45 duplicate_threads - 6.3.46 edit_headers - 6.3.47 editor - 6.3.48 encode_from - 6.3.49 envelope_from - 6.3.50 escape - 6.3.51 fast_reply - 6.3.52 fcc_attach - 6.3.53 fcc_clear - 6.3.54 folder - 6.3.55 folder_format - 6.3.56 followup_to - 6.3.57 followup_to_poster - 6.3.58 force_name - 6.3.59 forward_decode - 6.3.60 forward_edit - 6.3.61 forward_format - 6.3.62 forward_quote - 6.3.63 from - 6.3.64 gecos_mask - 6.3.65 group_index_format - 6.3.66 hdrs - 6.3.67 header - 6.3.68 help - 6.3.69 hidden_host - 6.3.70 hide_limited - 6.3.71 hide_missing - 6.3.72 hide_top_limited - 6.3.73 hide_top_missing - 6.3.74 history - 6.3.75 honor_followup_to - 6.3.76 hostname - 6.3.77 ignore_list_reply_to - 6.3.78 imap_authenticators - 6.3.79 imap_delim_chars - 6.3.80 imap_force_ssl - 6.3.81 imap_home_namespace - 6.3.82 imap_keepalive - 6.3.83 imap_list_subscribed - 6.3.84 imap_pass - 6.3.85 imap_passive - 6.3.86 imap_peek - 6.3.87 imap_servernoise - 6.3.88 imap_user - 6.3.89 implicit_autoview - 6.3.90 include - 6.3.91 indent_string - 6.3.92 index_format - 6.3.93 inews - 6.3.94 ispell - 6.3.95 keep_flagged - 6.3.96 locale - 6.3.97 mail_check - 6.3.98 mailcap_path - 6.3.99 mailcap_sanitize - 6.3.100 maildir_trash - 6.3.101 mark_old - 6.3.102 markers - 6.3.103 mask - 6.3.104 mbox - 6.3.105 mbox_type - 6.3.106 metoo - 6.3.107 menu_scroll - 6.3.108 meta_key - 6.3.109 mh_purge - 6.3.110 mh_seq_flagged - 6.3.111 mh_seq_replied - 6.3.112 mh_seq_unseen - 6.3.113 mime_forward - 6.3.114 mime_forward_decode - 6.3.115 mime_forward_rest - 6.3.116 mime_subject - 6.3.117 mix_entry_format - 6.3.118 mixmaster - 6.3.119 move - 6.3.120 message_format - 6.3.121 narrow_tree - 6.3.122 news_cache_dir - 6.3.123 news_server - 6.3.124 newsrc - 6.3.125 nntp_context - 6.3.126 nntp_load_description - 6.3.127 nntp_user - 6.3.128 nntp_pass - 6.3.129 nntp_poll - 6.3.130 nntp_reconnect - 6.3.131 pager - 6.3.132 pager_context - 6.3.133 pager_format - 6.3.134 pager_index_lines - 6.3.135 pager_stop - 6.3.136 crypt_autosign - 6.3.137 crypt_autoencrypt - 6.3.138 pgp_ignore_subkeys - 6.3.139 crypt_replyencrypt - 6.3.140 crypt_replysign - 6.3.141 crypt_replysignencrypted - 6.3.142 crypt_timestamp - 6.3.143 pgp_use_gpg_agent - 6.3.144 crypt_verify_sig - 6.3.145 smime_is_default - 6.3.146 smime_ask_cert_label - 6.3.147 smime_decrypt_use_default_key - 6.3.148 pgp_entry_format - 6.3.149 pgp_good_sign - 6.3.150 pgp_check_exit - 6.3.151 pgp_long_ids - 6.3.152 pgp_retainable_sigs - 6.3.153 pgp_show_unusable - 6.3.154 pgp_sign_as - 6.3.155 pgp_strict_enc - 6.3.156 pgp_timeout - 6.3.157 pgp_sort_keys - 6.3.158 pgp_create_traditional - 6.3.159 pgp_auto_traditional - 6.3.160 pgp_decode_command - 6.3.161 pgp_getkeys_command - 6.3.162 pgp_verify_command - 6.3.163 pgp_decrypt_command - 6.3.164 pgp_clearsign_command - 6.3.165 pgp_sign_command - 6.3.166 pgp_encrypt_sign_command - 6.3.167 pgp_encrypt_only_command - 6.3.168 pgp_import_command - 6.3.169 pgp_export_command - 6.3.170 pgp_verify_key_command - 6.3.171 pgp_list_secring_command - 6.3.172 pgp_list_pubring_command - 6.3.173 forward_decrypt - 6.3.174 smime_timeout - 6.3.175 smime_encrypt_with - 6.3.176 smime_keys - 6.3.177 smime_ca_location - 6.3.178 smime_certificates - 6.3.179 smime_decrypt_command - 6.3.180 smime_verify_command - 6.3.181 smime_verify_opaque_command - 6.3.182 smime_sign_command - 6.3.183 smime_sign_opaque_command - 6.3.184 smime_encrypt_command - 6.3.185 smime_pk7out_command - 6.3.186 smime_get_cert_command - 6.3.187 smime_get_signer_cert_command - 6.3.188 smime_import_cert_command - 6.3.189 smime_get_cert_email_command - 6.3.190 smime_default_key - 6.3.191 ssl_starttls - 6.3.192 certificate_file - 6.3.193 ssl_usesystemcerts - 6.3.194 entropy_file - 6.3.195 ssl_use_sslv2 - 6.3.196 ssl_use_sslv3 - 6.3.197 ssl_use_tlsv1 - 6.3.198 pipe_split - 6.3.199 pipe_decode - 6.3.200 pipe_sep - 6.3.201 pop_authenticators - 6.3.202 pop_auth_try_all - 6.3.203 pop_checkinterval - 6.3.204 pop_delete - 6.3.205 pop_host - 6.3.206 pop_last - 6.3.207 pop_reconnect - 6.3.208 pop_user - 6.3.209 pop_pass - 6.3.210 post_indent_string - 6.3.211 post_moderated - 6.3.212 postpone - 6.3.213 postponed - 6.3.214 preconnect - 6.3.215 print - 6.3.216 print_command - 6.3.217 print_decode - 6.3.218 print_split - 6.3.219 prompt_after - 6.3.220 query_command - 6.3.221 quit - 6.3.222 quote_regexp - 6.3.223 read_inc - 6.3.224 read_only - 6.3.225 realname - 6.3.226 recall - 6.3.227 record - 6.3.228 reply_regexp - 6.3.229 reply_self - 6.3.230 reply_to - 6.3.231 resolve - 6.3.232 reverse_alias - 6.3.233 reverse_name - 6.3.234 reverse_realname - 6.3.235 rfc2047_parameters - 6.3.236 save_address - 6.3.237 save_empty - 6.3.238 save_name - 6.3.239 score - 6.3.240 score_threshold_delete - 6.3.241 score_threshold_flag - 6.3.242 score_threshold_read - 6.3.243 send_charset - 6.3.244 sendmail - 6.3.245 sendmail_wait - 6.3.246 shell - 6.3.247 save_unsubscribed - 6.3.248 show_new_news - 6.3.249 show_only_unread - 6.3.250 sig_dashes - 6.3.251 sig_on_top - 6.3.252 signature - 6.3.253 simple_search - 6.3.254 smart_wrap - 6.3.255 smileys - 6.3.256 sleep_time - 6.3.257 sort - 6.3.258 sort_alias - 6.3.259 sort_aux - 6.3.260 sort_browser - 6.3.261 sort_re - 6.3.262 spoolfile - 6.3.263 status_chars - 6.3.264 status_format - 6.3.265 status_on_top - 6.3.266 strict_threads - 6.3.267 suspend - 6.3.268 text_flowed - 6.3.269 thread_received - 6.3.270 thorough_search - 6.3.271 tilde - 6.3.272 timeout - 6.3.273 tmpdir - 6.3.274 to_chars - 6.3.275 tunnel - 6.3.276 use_8bitmime - 6.3.277 use_domain - 6.3.278 use_from - 6.3.279 use_ipv6 - 6.3.280 user_agent - 6.3.281 visual - 6.3.282 wait_key - 6.3.283 weed - 6.3.284 wrap_search - 6.3.285 wrapmargin - 6.3.286 write_inc - 6.3.287 write_bcc - 6.3.288 x_comment_to + 6.3.19 autoedit + 6.3.20 beep + 6.3.21 beep_new + 6.3.22 bounce + 6.3.23 bounce_delivered + 6.3.24 catchup_newsgroup + 6.3.25 certificate_file + 6.3.26 charset + 6.3.27 check_new + 6.3.28 collapse_unread + 6.3.29 compose_format + 6.3.30 config_charset + 6.3.31 confirmappend + 6.3.32 confirmcreate + 6.3.33 connect_timeout + 6.3.34 content_type + 6.3.35 copy + 6.3.36 crypt_autoencrypt + 6.3.37 crypt_autopgp + 6.3.38 crypt_autosign + 6.3.39 crypt_autosmime + 6.3.40 crypt_replyencrypt + 6.3.41 crypt_replysign + 6.3.42 crypt_replysignencrypted + 6.3.43 crypt_timestamp + 6.3.44 crypt_use_gpgme + 6.3.45 crypt_verify_sig + 6.3.46 date_format + 6.3.47 default_hook + 6.3.48 delete + 6.3.49 delete_untag + 6.3.50 digest_collapse + 6.3.51 display_filter + 6.3.52 dotlock_program + 6.3.53 dsn_notify + 6.3.54 dsn_return + 6.3.55 duplicate_threads + 6.3.56 edit_headers + 6.3.57 editor + 6.3.58 encode_from + 6.3.59 envelope_from + 6.3.60 escape + 6.3.61 fast_reply + 6.3.62 fcc_attach + 6.3.63 fcc_clear + 6.3.64 file_charset + 6.3.65 folder + 6.3.66 folder_format + 6.3.67 followup_to + 6.3.68 followup_to_poster + 6.3.69 force_name + 6.3.70 forward_decode + 6.3.71 forward_decrypt + 6.3.72 forward_edit + 6.3.73 forward_format + 6.3.74 forward_quote + 6.3.75 from + 6.3.76 gecos_mask + 6.3.77 group_index_format + 6.3.78 hdrs + 6.3.79 header + 6.3.80 help + 6.3.81 hidden_host + 6.3.82 hide_limited + 6.3.83 hide_missing + 6.3.84 hide_thread_subject + 6.3.85 hide_top_limited + 6.3.86 hide_top_missing + 6.3.87 history + 6.3.88 honor_followup_to + 6.3.89 hostname + 6.3.90 ignore_list_reply_to + 6.3.91 imap_authenticators + 6.3.92 imap_delim_chars + 6.3.93 imap_force_ssl + 6.3.94 imap_headers + 6.3.95 imap_home_namespace + 6.3.96 imap_keepalive + 6.3.97 imap_list_subscribed + 6.3.98 imap_pass + 6.3.99 imap_passive + 6.3.100 imap_peek + 6.3.101 imap_reconnect + 6.3.102 imap_servernoise + 6.3.103 imap_user + 6.3.104 implicit_autoview + 6.3.105 include + 6.3.106 include_onlyfirst + 6.3.107 indent_string + 6.3.108 index_format + 6.3.109 inews + 6.3.110 ispell + 6.3.111 keep_flagged + 6.3.112 list_reply + 6.3.113 locale + 6.3.114 mail_check + 6.3.115 mailcap_path + 6.3.116 mailcap_sanitize + 6.3.117 maildir_trash + 6.3.118 mark_old + 6.3.119 markers + 6.3.120 mask + 6.3.121 max_line_length + 6.3.122 mbox + 6.3.123 mbox_type + 6.3.124 menu_context + 6.3.125 menu_scroll + 6.3.126 message_format + 6.3.127 meta_key + 6.3.128 metoo + 6.3.129 mh_purge + 6.3.130 mh_seq_flagged + 6.3.131 mh_seq_replied + 6.3.132 mh_seq_unseen + 6.3.133 mime_forward + 6.3.134 mime_forward_decode + 6.3.135 mime_forward_rest + 6.3.136 mime_subject + 6.3.137 mix_entry_format + 6.3.138 mixmaster + 6.3.139 move + 6.3.140 msgid_format + 6.3.141 narrow_tree + 6.3.142 news_cache_dir + 6.3.143 news_server + 6.3.144 newsrc + 6.3.145 nntp_context + 6.3.146 nntp_load_description + 6.3.147 nntp_pass + 6.3.148 nntp_poll + 6.3.149 nntp_reconnect + 6.3.150 nntp_user + 6.3.151 operating_system + 6.3.152 pager + 6.3.153 pager_context + 6.3.154 pager_format + 6.3.155 pager_index_lines + 6.3.156 pager_stop + 6.3.157 pgp_auto_decode + 6.3.158 pgp_autoinline + 6.3.159 pgp_check_exit + 6.3.160 pgp_clearsign_command + 6.3.161 pgp_decode_command + 6.3.162 pgp_decrypt_command + 6.3.163 pgp_encrypt_only_command + 6.3.164 pgp_encrypt_sign_command + 6.3.165 pgp_entry_format + 6.3.166 pgp_export_command + 6.3.167 pgp_getkeys_command + 6.3.168 pgp_good_sign + 6.3.169 pgp_ignore_subkeys + 6.3.170 pgp_import_command + 6.3.171 pgp_list_pubring_command + 6.3.172 pgp_list_secring_command + 6.3.173 pgp_long_ids + 6.3.174 pgp_mime_auto + 6.3.175 pgp_replyinline + 6.3.176 pgp_retainable_sigs + 6.3.177 pgp_show_unusable + 6.3.178 pgp_sign_as + 6.3.179 pgp_sign_command + 6.3.180 pgp_sort_keys + 6.3.181 pgp_strict_enc + 6.3.182 pgp_timeout + 6.3.183 pgp_use_gpg_agent + 6.3.184 pgp_verify_command + 6.3.185 pgp_verify_key_command + 6.3.186 pipe_decode + 6.3.187 pipe_sep + 6.3.188 pipe_split + 6.3.189 pop_auth_try_all + 6.3.190 pop_authenticators + 6.3.191 pop_checkinterval + 6.3.192 pop_delete + 6.3.193 pop_host + 6.3.194 pop_last + 6.3.195 pop_pass + 6.3.196 pop_reconnect + 6.3.197 pop_user + 6.3.198 post_indent_string + 6.3.199 post_moderated + 6.3.200 postpone + 6.3.201 postponed + 6.3.202 preconnect + 6.3.203 print + 6.3.204 print_command + 6.3.205 print_decode + 6.3.206 print_split + 6.3.207 prompt_after + 6.3.208 query_command + 6.3.209 quit + 6.3.210 quote_empty + 6.3.211 quote_quoted + 6.3.212 quote_regexp + 6.3.213 read_inc + 6.3.214 read_only + 6.3.215 realname + 6.3.216 recall + 6.3.217 record + 6.3.218 reply_regexp + 6.3.219 reply_self + 6.3.220 reply_to + 6.3.221 resolve + 6.3.222 reverse_alias + 6.3.223 reverse_name + 6.3.224 reverse_realname + 6.3.225 rfc2047_parameters + 6.3.226 save_address + 6.3.227 save_empty + 6.3.228 save_name + 6.3.229 save_unsubscribed + 6.3.230 score + 6.3.231 score_threshold_delete + 6.3.232 score_threshold_flag + 6.3.233 score_threshold_read + 6.3.234 send_charset + 6.3.235 sendmail + 6.3.236 sendmail_wait + 6.3.237 shell + 6.3.238 shorten_hierarchy + 6.3.239 show_new_news + 6.3.240 show_only_unread + 6.3.241 sidebar_delim + 6.3.242 sidebar_visible + 6.3.243 sidebar_width + 6.3.244 sig_dashes + 6.3.245 sig_on_top + 6.3.246 signature + 6.3.247 signoff_string + 6.3.248 simple_search + 6.3.249 sleep_time + 6.3.250 smart_wrap + 6.3.251 smileys + 6.3.252 smime_ask_cert_label + 6.3.253 smime_ca_location + 6.3.254 smime_certificates + 6.3.255 smime_decrypt_command + 6.3.256 smime_decrypt_use_default_key + 6.3.257 smime_default_key + 6.3.258 smime_encrypt_command + 6.3.259 smime_encrypt_with + 6.3.260 smime_get_cert_command + 6.3.261 smime_get_cert_email_command + 6.3.262 smime_get_signer_cert_command + 6.3.263 smime_import_cert_command + 6.3.264 smime_is_default + 6.3.265 smime_keys + 6.3.266 smime_pk7out_command + 6.3.267 smime_sign_command + 6.3.268 smime_sign_opaque_command + 6.3.269 smime_timeout + 6.3.270 smime_verify_command + 6.3.271 smime_verify_opaque_command + 6.3.272 smtp_auth_password + 6.3.273 smtp_auth_username + 6.3.274 smtp_host + 6.3.275 smtp_port + 6.3.276 sort + 6.3.277 sort_alias + 6.3.278 sort_aux + 6.3.279 sort_browser + 6.3.280 sort_re + 6.3.281 spam_separator + 6.3.282 spoolfile + 6.3.283 ssl_ca_certificates_file + 6.3.284 ssl_client_cert + 6.3.285 ssl_min_dh_prime_bits + 6.3.286 ssl_starttls + 6.3.287 ssl_use_sslv3 + 6.3.288 ssl_use_tlsv1 + 6.3.289 status_chars + 6.3.290 status_format + 6.3.291 status_on_top + 6.3.292 strict_mime + 6.3.293 strict_threads + 6.3.294 stuff_quoted + 6.3.295 suspend + 6.3.296 text_flowed + 6.3.297 thorough_search + 6.3.298 thread_received + 6.3.299 tilde + 6.3.300 timeout + 6.3.301 tmpdir + 6.3.302 to_chars + 6.3.303 trash + 6.3.304 tunnel + 6.3.305 umask + 6.3.306 uncollapse_jump + 6.3.307 use_8bitmime + 6.3.308 use_domain + 6.3.309 use_from + 6.3.310 user_agent + 6.3.311 visual + 6.3.312 wait_key + 6.3.313 weed + 6.3.314 wrap_search + 6.3.315 wrapmargin + 6.3.316 write_bcc + 6.3.317 write_inc + 6.3.318 x_comment_to + 6.3.319 xterm_icon + 6.3.320 xterm_set_titles + 6.3.321 xterm_title 6.4 Functions 6.4.1 generic 6.4.2 index @@ -412,55 +449,61 @@ 6.4.11 editor 7. Miscellany - 7.1 Acknowledgements 7.2 About this document ______________________________________________________________________ - 1. Introduction + 11.. IInnttrroodduuccttiioonn - Mutt is a small but very powerful text-based MIME mail client. Mutt + MMuutttt 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.1. Mutt Home Page - - http://www.mutt.org/ + This documentation additionaly contains documentation to MMuutttt--NNGG, a + fork from Mutt with the goal to fix all the little annoyances of Mutt, + to integrate all the Mutt patches that are floating around in the web, + and to add other new features. Features specific to Mutt-ng will be + discussed in an extra section. Don't be confused when most of the + documentation talk about Mutt and not Mutt-ng, Mutt-ng contains all + Mutt-ng features, plus many more. - 1.2. Mailing Lists + 11..11.. MMuutttt HHoommee PPaaggee - 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. + http://www.mutt.org/ - · mutt-announce@mutt.org -- low traffic list for announcements + 11..22.. MMuutttt--nngg HHoommee PPaaggee - · mutt-users@mutt.org -- help, bug reports and feature requests + http://mutt-ng.berlios.de/ - · mutt-dev@mutt.org -- development mailing list + 11..33.. MMaaiilliinngg LLiissttss - Note: all messages posted to mutt-announce are automatically forwarded - to mutt-users, so you do not need to be subscribed to both lists. + +o mutt-ng-users@lists.berlios.de -- This is where the mutt-ng user + support happens. - 1.3. Software Distribution Sites + +o mutt-ng-devel@lists.berlios.de -- The development mailing list for + mutt-ng - · ftp://ftp.mutt.org/mutt/ + 11..44.. SSooffttwwaarree DDiissttrriibbuuttiioonn SSiitteess - For a list of mirror sites, please refer to - http://www.mutt.org/download.html. + So far, there are no official releases of Mutt-ng, but you can + download daily snapshots from http://mutt-ng.berlios.de/snapshots/ - 1.4. IRC + 11..55.. IIRRCC - Visit channel #mutt on irc.freenode.net (www.freenode.net) to chat - with other people interested in Mutt. + Visit channel _#_m_u_t_t_n_g on irc.freenode.net (www.freenode.net) to chat + with other people interested in Mutt-ng. - 1.5. USENET + 11..66.. WWeebblloogg - See the newsgroup comp.mail.mutt. + If you want to read fresh news about the latest development in Mutt- + ng, and get informed about stuff like interesting, Mutt-ng-related + articles and packages for your favorite distribution, you can read + and/or subscribe to our Mutt-ng development weblog. - 1.6. Copyright + 11..77.. CCooppyyrriigghhtt Mutt is Copyright (C) 1996-2000 Michael R. Elkins and others @@ -479,7 +522,7 @@ along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA. - 2. Getting Started + 22.. GGeettttiinngg SSttaarrtteedd This section is intended as a brief overview of how to use Mutt. There are many other features which are described elsewhere in the @@ -495,7 +538,7 @@ at the command line. There are various command-line options, see either the mutt man page or the ``reference''. - 2.1. Moving Around in Menus + 22..11.. MMoovviinngg AArroouunndd iinn MMeennuuss Information is presented in menus, very similar to ELM. Here is a table showing the common keys used to navigate menus in Mutt. @@ -515,28 +558,28 @@ input textual data such as email addresses or filenames. The keys used to move around while editing are very similar to those of Emacs. - ^A or bol move to the start of the line - ^B or backward-char move back one char - Esc B backward-word move back one word - ^D or delete-char delete the char under the cursor - ^E or eol move to the end of the line - ^F or forward-char move forward one char - Esc F forward-word move forward one word - 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 ot 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 - history-up recall previous string from history - history-down recall next string from history - 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 - ^G n/a abort - n/a finish editing + ^A or bol move to the start of the line + ^B or backward-char move back one char + Esc B backward-word move back one word + ^D or delete-char delete the char under the cursor + ^E or eol move to the end of the line + ^F or forward-char move forward one char + Esc F forward-word move forward one word + 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 ot 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 + history-up recall previous string from history + history-down recall next string from history + 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 + ^G n/a abort + n/a finish editing You can remap the _e_d_i_t_o_r functions using the ``bind'' command. For example, to make the _D_e_l_e_t_e key delete the character in front of the @@ -617,9 +660,9 @@ Some of the status flags can be turned on or off using - · sseett--ffllaagg (default: w) + +o sseett--ffllaagg (default: w) - · cclleeaarr--ffllaagg (default: W) + +o cclleeaarr--ffllaagg (default: W) Furthermore, the following flags reflect who the message is addressed to. They can be customized with the ``$to_chars'' variable. @@ -652,8 +695,8 @@ \ toggle search pattern coloring ^ jump to the top of the message - In addition, many of the functions from the index are available in the - pager, such as delete-message or copy-message (this is one advantage + In addition, many of the functions from the _i_n_d_e_x are available in the + pager, such as _d_e_l_e_t_e_-_m_e_s_s_a_g_e or _c_o_p_y_-_m_e_s_s_a_g_e (this is one advantage over using an external pager to view messages). Also, the internal pager supports a couple other advanced features. @@ -724,17 +767,17 @@ See also: ``$strict_threads''. - 2.3.4. Miscellaneous Functions + 22..33..44.. MMiisscceellllaanneeoouuss FFuunnccttiioonnss - create-alias (default: a) + ccrreeaattee--aalliiaass (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: Specifying an ``$alias_file'' does not add the aliases specified + NNoottee:: Specifying an ``$alias_file'' does not add the aliases specified there-in, you must also ``source'' the file. - check-traditional-pgp (default: ESC P) + cchheecckk--ttrraaddiittiioonnaall--ppggpp (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 @@ -742,12 +785,12 @@ content types of the body parts containing PGP data; this is similar to the ``edit-type'' function's effect. - display-toggle-weed (default: h) + ddiissppllaayy--ttooggggllee--wweeeedd (default: h) Toggles the weeding of message header fields specified by ``ignore'' commands. - edit (default: e) + eeddiitt (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. @@ -755,7 +798,7 @@ to the current folder, and the original message will be marked for deletion. - edit-type + eeddiitt--ttyyppee (default: ^E on the attachment menu, and in the pager and index menus; ^T on the compose menu) @@ -770,24 +813,24 @@ There, it's used to fine-tune the properties of attachments you are going to send. - enter-command (default: ``:'') + eenntteerr--ccoommmmaanndd (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) + eexxttrraacctt--kkeeyyss (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) + ffoorrggeett--ppaasssspphhrraassee (default: ^F) This command wipes the passphrase(s) from memory. It is useful, if you misspelled the passphrase. - list-reply (default: L) + lliisstt--rreeppllyy (default: L) Reply to the current or tagged message(s) by extracting any addresses which match the regular expressions given by the ``lists or @@ -797,14 +840,14 @@ duplicate copies being sent to the author of the message you are replying to. - pipe-message (default: |) + ppiippee--mmeessssaaggee (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 behaviour of this function. - resend-message (default: ESC e) + rreesseenndd--mmeessssaaggee (default: ESC e) With resend-message, mutt takes the current message as a template for a new message. This function is best described as "recall from @@ -904,32 +947,32 @@ ``$status_format'' will change to a 'A' to indicate that you are in attach-message mode. - 2.4.1. Editing the message header + 22..44..11.. EEddiittiinngg tthhee mmeessssaaggee hheeaaddeerr When editing the header of your outgoing message, there are a couple of special features available. If you specify - Fcc: filename - Mutt will pick up filename just as if you had used the edit-fcc - function in the compose menu. + Fcc: _f_i_l_e_n_a_m_e + Mutt will pick up _f_i_l_e_n_a_m_e just as if you had used the _e_d_i_t_-_f_c_c + function in the _c_o_m_p_o_s_e 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 + Attach: _f_i_l_e_n_a_m_e [ _d_e_s_c_r_i_p_t_i_o_n ] + where _f_i_l_e_n_a_m_e is the file to attach and _d_e_s_c_r_i_p_t_i_o_n is an optional string to use as the description of the attached file. - When replying to messages, if you remove the In-Reply-To: field from - the header field, Mutt will not generate a References: field, which + When replying to messages, if you remove the _I_n_-_R_e_p_l_y_-_T_o_: field from + the header field, Mutt will not generate a _R_e_f_e_r_e_n_c_e_s_: field, which allows you to create a new message thread. Also see ``edit_headers''. - 2.4.2. Using Mutt with PGP + 22..44..22.. UUssiinngg MMuutttt wwiitthh PPGGPP If you want to use PGP, you can specify - Pgp: [ E | S | S ] + Pgp: [ E | S | S_<_i_d_> ] ``E'' encrypts, ``S'' signs and ``S'' signs with the given key, setting ``$pgp_sign_as'' permanently. @@ -965,24 +1008,24 @@ 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 + 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 letter ee 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'' + again, a ``--'' implies ``not for signing'', ``..'' implies that the key + is marked as an encryption key in one of the user-ids, and ``ss'' 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 + 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. - 2.4.3. Sending anonymous messages via mixmaster. + 22..44..33.. SSeennddiinngg aannoonnyymmoouuss mmeessssaaggeess vviiaa mmiixxmmaasstteerr.. You may also have configured mutt to co-operate with Mixmaster, an anonymous remailer. Mixmaster permits you to send your messages @@ -1018,7 +1061,7 @@ the other capabilities, please have a look at the mixmaster documentation. - 2.5. Forwarding and Bouncing Mail + 22..55.. FFoorrwwaarrddiinngg aanndd BBoouunncciinngg MMaaiill Bouncing and forwarding let you send an existing message to recipients that you specify. Bouncing a message uses the ``sendmail'' command to @@ -1037,7 +1080,7 @@ 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 + the content, therefore _$_m_i_m_e___f_o_r_w_a_r_d is a quadoption which, for example, can be set to ``ask-no''. The inclusion of headers is controlled by the current setting of the @@ -1081,18 +1124,22 @@ 33.. CCoonnffiigguurraattiioonn - While the default configuration (or ``preferences'') make Mutt usable - right out of the box, it is often desirable to tailor Mutt to suit - your own tastes. When Mutt is first invoked, it will attempt to read - 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. + While the default configuration (or ``preferences'') make Mutt-ng + usable right out of the box, it is often desirable to tailor Mutt to + suit your own tastes. When Mutt-ng 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/muttng/Muttngrc or + /etc/Muttngrc, Mutt-ng users will find this file in + /usr/local/share/muttng/Muttrc or /etc/Muttngrc. Mutt will next look + for a file named .muttrc in your home directory, Mutt-ng will look for + .muttngrc. If this file does not exist and your home directory has a + subdirectory named .mutt, mutt try to load a file named + .muttng/muttngrc. + + .muttrc (or .muttngrc for Mutt-ng) 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 @@ -1104,7 +1151,7 @@ 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. - 3.1. Syntax of Initialization Files + 33..11.. SSyynnttaaxx ooff IInniittiiaalliizzaattiioonn FFiilleess An initialization file consists of a series of ``commands''. Each line of the file may contain one or more commands. When multiple @@ -1112,7 +1159,7 @@ set realname='Mutt user' ; ignore x- - The hash mark, or pound sign (``#''), is used as a ``comment'' charac­ + The hash mark, or pound sign (``#''), is used as a ``comment'' charac- ter. You can use it to annotate your initialization file. All text after the comment character to the end of the line is ignored. For example, @@ -1126,7 +1173,7 @@ 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, - backtics are evaluated inside of double quotes, but not for single + backtics are evaluated inside of double quotes, but nnoott for single quotes. \ quotes the next character, just as in shells such as bash and zsh. @@ -1164,24 +1211,24 @@ The commands understood by mutt are explained in the next paragraphs. For a complete list, see the ``command reference''. - 3.2. Defining/Using aliases + 33..22.. DDeeffiinniinngg//UUssiinngg aalliiaasseess - Usage: alias key address [ , address, ... ] + Usage: alias _k_e_y _a_d_d_r_e_s_s [ , _a_d_d_r_e_s_s, ... ] It's usually very cumbersome to remember or type out the address of 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 a group (by specifying more - than one address), you must separate the addresses with a comma + NNoottee:: if you want to create an alias for a group (by specifying more + than one address), you mmuusstt separate the addresses with a comma (``,''). To remove an alias or aliases (``*'' means all aliases): - unalias [ * | key ... ] + unalias [ * | _k_e_y _._._. ] - alias muttdude me@cs.hmc.edu (Michael Elkins) - alias theguys manny, moe, jack + 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 @@ -1195,6 +1242,7 @@ 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: source /usr/local/share/Mutt.aliases @@ -1202,7 +1250,7 @@ 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 + mutt prompts for addresses, such as the _T_o_: or _C_c_: prompt. You can also enter aliases in your editor at the appropriate headers if you have the ``$edit_headers'' variable set. @@ -1214,21 +1262,21 @@ 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: RET), and use the exit key (default: q) to + _s_e_l_e_c_t_-_e_n_t_r_y key (default: RET), and use the _e_x_i_t key (default: q) to return to the address prompt. - 3.3. Changing the default key bindings + 33..33.. CChhaannggiinngg tthhee ddeeffaauulltt kkeeyy bbiinnddiinnggss - Usage: bind map key function + Usage: bind _m_a_p _k_e_y _f_u_n_c_t_i_o_n 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 + _m_a_p 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 + ggeenneerriicc 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 @@ -1236,85 +1284,85 @@ function in multiple menus instead of having multiple bind statements to accomplish the same task. - alias + aalliiaass 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 + aattttaacchh The attachment menu is used to access the attachments on received messages. - browser + bbrroowwsseerr The browser is used for both browsing the local directory structure, and for listing all of your incoming mailboxes. - editor + eeddiittoorr The editor is the line-based editor the user enters text data. - index + iinnddeexx The index is the list of messages contained in a mailbox. - compose + ccoommppoossee The compose menu is the screen used when sending a new message. - pager + ppaaggeerr The pager is the mode used to display message/attachment data, and help listings. - pgp + ppggpp The pgp menu is used to select the OpenPGP keys used for encrypting outgoing messages. - postpone + ppoossttppoonnee The postpone menu is similar to the index menu, except is used when recalling a message the user was composing, but saved until later. - 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 + _k_e_y is the key (or key sequence) you wish to bind. To specify a + control character, use the sequence _\_C_x, 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 + Note that the case of _x as well as _\_C is ignored, so that _\_C_A, _\_C_a, + _\_c_A and _\_c_a 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 consist of: - - \t tab - 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 + _\_1_7_7 is equivalent to _\_c_?). + + In addition, _k_e_y may consist of: + + \t tab + 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 + + _k_e_y does not need to be enclosed in quotes unless it contains a space (`` ''). - function specifies which action to take when key is pressed. For a + _f_u_n_c_t_i_o_n specifies which action to take when _k_e_y is pressed. For a complete list of functions, see the ``reference''. The special function noop unbinds the specified key sequence. - 3.4. Defining aliases for character sets + 33..44.. DDeeffiinniinngg aalliiaasseess ffoorr cchhaarraacctteerr sseettss - Usage: charset-hook alias charset - Usage: iconv-hook charset local-charset + Usage: charset-hook _a_l_i_a_s _c_h_a_r_s_e_t + Usage: iconv-hook _c_h_a_r_s_e_t _l_o_c_a_l_-_c_h_a_r_s_e_t The charset-hook command defines an alias for a character set. This is useful to properly display messages which are tagged with a @@ -1324,55 +1372,55 @@ set. This is helpful when your systems character conversion library insists on using strange, system-specific names for character sets. - 3.5. Setting variables based upon mailbox + 33..55.. SSeettttiinngg vvaarriiaabblleess bbaasseedd uuppoonn mmaaiillbbooxx - Usage: folder-hook [!]regexp command + Usage: folder-hook [!]_r_e_g_e_x_p _c_o_m_m_a_n_d 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 + can execute any configuration command. _r_e_g_e_x_p is a regular expression + specifying in which mailboxes to execute _c_o_m_m_a_n_d 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 + NNoottee:: 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 + quotes in order to distinguish it from the logical _n_o_t operator for the expression. - Note that the settings are not restored when you leave the mailbox. + Note that the settings are _n_o_t 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 + reading a different mailbox. To specify a _d_e_f_a_u_l_t command, use the pattern ``.'': folder-hook . set sort=date-sent - 3.6. Keyboard macros + 33..66.. KKeeyybbooaarrdd mmaaccrrooss - Usage: macro menu key sequence [ description ] + Usage: macro _m_e_n_u _k_e_y _s_e_q_u_e_n_c_e [ _d_e_s_c_r_i_p_t_i_o_n ] 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 + of actions. When you press _k_e_y in menu _m_e_n_u, Mutt will behave as if + you had typed _s_e_q_u_e_n_c_e. So if you have a common sequence of commands you type, you can create a macro to execute those commands with a single key. - menu is the ``map'' which the macro will be bound. Multiple maps may + _m_e_n_u is the ``map'' which the macro will be bound. 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 + _k_e_y and _s_e_q_u_e_n_c_e are expanded by the same rules as the ``key bindings''. There are some additions however. 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 + control characters in _s_e_q_u_e_n_c_e can also be specified as _^_x. In order + to get a caret (`^'') you need to use _^_^. Secondly, to specify a + certain key such as _u_p or to invoke a function directly, you can use + the format _<_k_e_y _n_a_m_e_> and _<_f_u_n_c_t_i_o_n _n_a_m_e_>. For a listing of key names see the section on ``key bindings''. Functions are listed in the ``function reference''. @@ -1382,138 +1430,137 @@ them more robust and portable, and also facilitates defining of macros in files used by more than one user (eg. the system Muttrc). - Optionally you can specify a descriptive text after sequence, which is + Optionally you can specify a descriptive text after _s_e_q_u_e_n_c_e, which is shown in the help screens. - Note: Macro definitions (if any) listed in the help screen(s), are + NNoottee:: Macro definitions (if any) listed in the help screen(s), are silently truncated at the screen width, and are not wrapped. - 3.7. Using color and mono video attributes - - Usage: color object foreground background [ regexp ] - Usage: color index foreground background pattern - Usage: uncolor index pattern [ pattern ... ] + 33..77.. UUssiinngg ccoolloorr aanndd mmoonnoo vviiddeeoo aattttrriibbuutteess + Usage: color _o_b_j_e_c_t _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d [ _r_e_g_e_x_p ] + Usage: color index _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d _p_a_t_t_e_r_n + Usage: uncolor index _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] If your terminal supports color, you can spice up Mutt by creating your own color scheme. To define the color of an object (type of - information), you must specify both a foreground color and a + information), you must specify both a foreground color aanndd a background color (it is not possible to only specify one or the other). - object can be one of: + _o_b_j_e_c_t can be one of: - · attachment + +o attachment - · body (match regexp in the body of messages) + +o body (match _r_e_g_e_x_p in the body of messages) - · bold (hiliting bold patterns in the body of messages) + +o bold (hiliting bold patterns in the body of messages) - · error (error messages printed by Mutt) + +o error (error messages printed by Mutt) - · header (match regexp in the message header) + +o header (match _r_e_g_e_x_p in the message header) - · hdrdefault (default color of the message header in the pager) + +o hdrdefault (default color of the message header in the pager) - · index (match pattern in the message index) + +o index (match _p_a_t_t_e_r_n in the message index) - · indicator (arrow or bar used to indicate the current item in a + +o indicator (arrow or bar used to indicate the current item in a menu) - · markers (the ``+'' markers at the beginning of wrapped lines in the + +o markers (the ``+'' markers at the beginning of wrapped lines in the pager) - · message (informational messages) + +o message (informational messages) - · normal + +o normal - · quoted (text matching ``$quote_regexp'' in the body of a message) + +o quoted (text matching ``$quote_regexp'' in the body of a message) - · quoted1, quoted2, ..., quotedN (higher levels of quoting) + +o quoted1, quoted2, ..., quotedNN (higher levels of quoting) - · search (hiliting of words in the pager) + +o search (hiliting of words in the pager) - · signature + +o signature - · status (mode lines used to display info about the mailbox or + +o status (mode lines used to display info about the mailbox or message) - · tilde (the ``~'' used to pad blank lines in the pager) + +o tilde (the ``~'' used to pad blank lines in the pager) - · tree (thread tree drawn in the message index and attachment menu) + +o tree (thread tree drawn in the message index and attachment menu) - · underline (hiliting underlined patterns in the body of messages) + +o underline (hiliting underlined patterns in the body of messages) - foreground and background can be one of the following: + _f_o_r_e_g_r_o_u_n_d and _b_a_c_k_g_r_o_u_n_d can be one of the following: - · white + +o white - · black + +o black - · green + +o green - · magenta + +o magenta - · blue + +o blue - · cyan + +o cyan - · yellow + +o yellow - · red + +o red - · default + +o default - · colorx + +o color_x - foreground can optionally be prefixed with the keyword bright to make + _f_o_r_e_g_r_o_u_n_d 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 + If your terminal supports it, the special keyword _d_e_f_a_u_l_t can be used + as a transparent color. The value _b_r_i_g_h_t_d_e_f_a_u_l_t is also valid. If + Mutt is linked against the _S_-_L_a_n_g library, you also need to set the + _C_O_L_O_R_F_G_B_G environment variable to the default colors of your terminal for this to work; for example (for Bourne-like shells): set COLORFGBG="green;black" export COLORFGBG - Note: The S-Lang library requires you to use the lightgray and brown - keywords instead of white and yellow when setting this variable. + NNoottee:: The _S_-_L_a_n_g library requires you to use the _l_i_g_h_t_g_r_a_y and _b_r_o_w_n + keywords instead of _w_h_i_t_e and _y_e_l_l_o_w when setting this variable. - Note: The uncolor command can be applied to the index object only. It - removes entries from the list. You must specify the same pattern + NNoottee:: The uncolor command can be applied to the index object only. It + removes entries from the list. You mmuusstt specify the same pattern specified in the color command for it to be removed. The pattern ``*'' is a special token which means to clear the color index list of all entries. - Mutt also recognizes the keywords color0, color1, ..., colorN-1 (N + Mutt also recognizes the keywords _c_o_l_o_r_0, _c_o_l_o_r_1, ..., _c_o_l_o_rNN--11 (NN being the number of colors supported by your terminal). This is useful when you remap the colors for your display (for example by - changing the color associated with color2 for your xterm), since color + changing the color associated with _c_o_l_o_r_2 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   [ regexp ] - Usage: mono index attribute pattern - Usage: unmono index pattern [ pattern ... ] + Usage: mono _<_o_b_j_e_c_t_> _<_a_t_t_r_i_b_u_t_e_> [ _r_e_g_e_x_p ] + Usage: mono index _a_t_t_r_i_b_u_t_e _p_a_t_t_e_r_n + Usage: unmono index _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - where attribute is one of the following: + where _a_t_t_r_i_b_u_t_e is one of the following: - · none + +o none - · bold + +o bold - · underline + +o underline - · reverse + +o reverse - · standout + +o standout - 3.8. Ignoring (weeding) unwanted message headers + 33..88.. IIggnnoorriinngg ((wweeeeddiinngg)) uunnwwaanntteedd mmeessssaaggee hheeaaddeerrss - Usage: [un]ignore pattern [ pattern ... ] + Usage: [un]ignore _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] Messages often have many header fields added by automatic processing systems, or which may not seem useful to display on the screen. This @@ -1539,9 +1586,9 @@ unignore organization organisation x-mailer: x-newsreader: x-mailing-list: unignore posted-to: - 3.9. Alternative addresses + 33..99.. AAlltteerrnnaattiivvee aaddddrreesssseess - Usage: [un]alternates regexp [ regexp ... ] + Usage: [un]alternates _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] With various functions, mutt will treat messages differently, depending on whether you sent them or whether you received them from @@ -1562,15 +1609,15 @@ 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 a 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. + unalternates command with exactly the same _r_e_g_e_x_p. Likewise, if the + _r_e_g_e_x_p for a alternates command matches an entry on the unalternates + list, that unalternates entry will be removed. If the _r_e_g_e_x_p for + unalternates is ``*'', _a_l_l _e_n_t_r_i_e_s on alternates will be removed. - 3.10. Mailing lists + 33..1100.. MMaaiilliinngg lliissttss - Usage: [un]lists regexp [ regexp ... ] - Usage: [un]subscribe regexp [ regexp ... ] + Usage: [un]lists _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] + Usage: [un]subscribe _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] Mutt has a few nice features for ``handling mailing lists''. In order to take advantage of them, you must specify which addresses belong to @@ -1598,44 +1645,45 @@ 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 addresssed to mutt-users@mutt.org. So, to tell Mutt that + receive mail addresssed to _m_u_t_t_-_u_s_e_r_s_@_m_u_t_t_._o_r_g. 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 + also happen to get mail from someone whose address is _m_u_t_t_- + _u_s_e_r_s_@_e_x_a_m_p_l_e_._c_o_m, you could use ``lists mutt-users@mutt\\.org'' or ``subscribe mutt-users@mutt\\.org'' to match only mail from the actual list. 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''. - 3.11. Using Multiple spool mailboxes + 33..1111.. UUssiinngg MMuullttiippllee ssppooooll mmaaiillbbooxxeess - Usage: mbox-hook [!]pattern mailbox + Usage: mbox-hook [!]_p_a_t_t_e_r_n _m_a_i_l_b_o_x 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 + _p_a_t_t_e_r_n is a regular expression specifying the mailbox to treat as a + ``spool'' mailbox and _m_a_i_l_b_o_x specifies where mail should be saved when read. - Unlike some of the other hook commands, only the first matching + Unlike some of the other _h_o_o_k commands, only the _f_i_r_s_t matching pattern is used (it is not possible to save read mail in more than a single mailbox). - 3.12. Defining mailboxes which receive mail + 33..1122.. DDeeffiinniinngg mmaaiillbbooxxeess wwhhiicchh rreecceeiivvee mmaaiill - Usage: [un]mailboxes [!]filename [ filename ... ] + Usage: [un]mailboxes [!]_f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ] This command specifies folders which can receive mail and which will be checked for new messages. By default, the main menu status bar displays how many of these folders have new messages. - When changing folders, pressing space will cycle through folders with + When changing folders, pressing _s_p_a_c_e will cycle through folders with new mail. Pressing TAB in the directory browser will bring up a menu showing the @@ -1647,23 +1695,23 @@ folders which receive mail. Use ``unmailboxes *'' to remove all tokens. - Note: new mail is detected by comparing the last modification time to + NNoottee:: new mail is detected by comparing the last modification time to the last access time. 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. Backup tools are another common reason for updated access times. - Note: the filenames in the mailboxes command are resolved when the + NNoottee:: the filenames in the mailboxes command are resolved when the command is executed, so if these names contain ``shortcut characters'' (such as ``='' and ``!''), any variable definition that affect these characters (like ``$folder'' and ``$spoolfile'') should be executed before the mailboxes command. - 3.13. User defined headers + 33..1133.. UUsseerr ddeeffiinneedd hheeaaddeerrss Usage: - my_hdr string - unmy_hdr field [ field ... ] + my_hdr _s_t_r_i_n_g + unmy_hdr _f_i_e_l_d [ _f_i_e_l_d ... ] The ``my_hdr'' command allows you to create your own header fields which will be added to every message you send. @@ -1675,13 +1723,13 @@ in your .muttrc. - Note: space characters are not allowed between the keyword and the + NNoottee:: space characters are _n_o_t allowed between the keyword and the colon (``:''). The standard for electronic mail (RFC822) 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 send-menu so that you can + should either set the ``edit_headers'' variable, or use the _e_d_i_t_- + _h_e_a_d_e_r_s function (default: ``E'') in the send-menu so that you can edit the header of your message along with the body. To remove user defined header fields, use the ``unmy_hdr'' command. @@ -1691,9 +1739,9 @@ unmy_hdr to cc - 3.14. Defining the order of headers when viewing messages + 33..1144.. DDeeffiinniinngg tthhee oorrddeerr ooff hheeaaddeerrss wwhheenn vviieewwiinngg mmeessssaaggeess - Usage: hdr_order header1 header2 header3 + Usage: hdr_order _h_e_a_d_e_r_1 _h_e_a_d_e_r_2 _h_e_a_d_e_r_3 With this command, you can specify an order in which mutt will attempt to present headers to you when viewing messages. @@ -1704,17 +1752,17 @@ hdr_order From Date: From: To: Cc: Subject: - 3.15. Specify default save filename + 33..1155.. SSppeecciiffyy ddeeffaauulltt ssaavvee ffiilleennaammee - Usage: save-hook [!]pattern filename + Usage: save-hook [!]_p_a_t_t_e_r_n _f_i_l_e_n_a_m_e This command is used to override the default filename used when saving - messages. filename will be used as the default filename if the - message is From: an address matching regexp or if you are the author - and the message is addressed to: something matching regexp. + messages. _f_i_l_e_n_a_m_e will be used as the default filename if the + message is _F_r_o_m_: an address matching _r_e_g_e_x_p or if you are the author + and the message is addressed _t_o_: something matching _r_e_g_e_x_p. See ``Message Matching in Hooks'' for information on the exact format - of pattern. + of _p_a_t_t_e_r_n. Examples: @@ -1723,18 +1771,18 @@ Also see the ``fcc-save-hook'' command. - 3.16. Specify default Fcc: mailbox when composing + 33..1166.. SSppeecciiffyy ddeeffaauulltt FFcccc:: mmaaiillbbooxx wwhheenn ccoommppoossiinngg - Usage: fcc-hook [!]pattern mailbox + Usage: fcc-hook [!]_p_a_t_t_e_r_n _m_a_i_l_b_o_x 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: + the first matching _r_e_g_e_x_p and uses _m_a_i_l_b_o_x as the default Fcc: mailbox. If no match is found the message will be saved to ``$record'' mailbox. See ``Message Matching in Hooks'' for information on the exact format - of pattern. + of _p_a_t_t_e_r_n. Example: fcc-hook [@.]aol\\.com$ +spammers @@ -1742,28 +1790,27 @@ to the `+spammers' mailbox by default. Also see the ``fcc-save-hook'' command. - 3.17. Specify default save filename and default Fcc: mailbox at once + 33..1177.. SSppeecciiffyy ddeeffaauulltt ssaavvee ffiilleennaammee aanndd ddeeffaauulltt FFcccc:: mmaaiillbbooxx aatt oonnccee - Usage: fcc-save-hook [!]pattern mailbox + Usage: fcc-save-hook [!]_p_a_t_t_e_r_n _m_a_i_l_b_o_x This command is a shortcut, equivalent to doing both a ``fcc-hook'' and a ``save-hook'' with its arguments. + 33..1188.. CChhaannggee sseettttiinnggss bbaasseedd uuppoonn mmeessssaaggee rreecciippiieennttss - 3.18. Change settings based upon message recipients - - Usage: reply-hook [!]pattern command - Usage: send-hook [!]pattern command - Usage: send2-hook [!]pattern command + Usage: reply-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d + Usage: send-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d + Usage: send2-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d These commands can be used to execute arbitrary configuration commands - based upon recipients of the message. pattern is a regular expression - matching the desired address. command is executed when regexp matches + based upon recipients of the message. _p_a_t_t_e_r_n is a regular expression + matching the desired address. _c_o_m_m_a_n_d is executed when _r_e_g_e_x_p matches recipients of the message. - 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 users's + reply-hook is matched against the message you are _r_e_p_l_y_i_n_g ttoo, instead + of the message you are _s_e_n_d_i_n_g. send-hook is matched against all + messages, both _n_e_w and _r_e_p_l_i_e_s. NNoottee:: reply-hooks are matched bbeeffoorree + the send-hook, rreeggaarrddlleessss of the order specified in the users's configuration file. send2-hook is matched every time a message is changed, either by @@ -1777,7 +1824,7 @@ (for that type of hook). See ``Message Matching in Hooks'' for information on the exact format - of pattern. + of _p_a_t_t_e_r_n. Example: send-hook mutt "set mime_forward signature=''" @@ -1786,34 +1833,34 @@ change the language of the attributions and signatures based upon the recipients. - Note: the send-hook's are only executed ONCE after getting the initial + NNoottee:: the 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. - 3.19. Change settings before formatting a message + 33..1199.. CChhaannggee sseettttiinnggss bbeeffoorree ffoorrmmaattttiinngg aa mmeessssaaggee - Usage: message-hook [!]pattern command + Usage: message-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d 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 + the message. _c_o_m_m_a_n_d is executed if the _p_a_t_t_e_r_n 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. + of _p_a_t_t_e_r_n. Example: message-hook ~A 'set pager=builtin' message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""' - 3.20. Choosing the cryptographic key of the recipient + 33..2200.. CChhoooossiinngg tthhee ccrryyppttooggrraapphhiicc kkeeyy ooff tthhee rreecciippiieenntt - Usage: crypt-hook pattern keyid + Usage: crypt-hook _p_a_t_t_e_r_n _k_e_y_i_d When encrypting messages with PGP or OpenSSL, you may want to associate a certain key with a given e-mail address automatically, @@ -1827,9 +1874,9 @@ can either put a numerical key ID here, an e-mail address, or even just a real name. - 3.21. Adding key sequences to the keyboard buffer + 33..2211.. AAddddiinngg kkeeyy sseeqquueenncceess ttoo tthhee kkeeyybbooaarrdd bbuuffffeerr - Usage: push string + Usage: push _s_t_r_i_n_g This command adds the named string to the keyboard buffer. The string may contain control characters, key names and function names like the @@ -1837,55 +1884,55 @@ automatically run a sequence of commands at startup, or when entering certain folders. - 3.22. Executing functions + 33..2222.. EExxeeccuuttiinngg ffuunnccttiioonnss - Usage: exec function [ function ... ] + Usage: exec _f_u_n_c_t_i_o_n [ _f_u_n_c_t_i_o_n ... ] This command can be used to execute any function. Functions are listed in the ``function reference''. ``exec function'' is equivalent to ``push ''. - 3.23. Message Scoring + 33..2233.. MMeessssaaggee SSccoorriinngg - Usage: score pattern value - Usage: unscore pattern [ pattern ... ] + Usage: score _p_a_t_t_e_r_n _v_a_l_u_e + Usage: unscore _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - 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'' + The score commands adds _v_a_l_u_e to a message's score if _p_a_t_t_e_r_n matches + it. _p_a_t_t_e_r_n 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 + _v_a_l_u_e 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 + optionally prefix _v_a_l_u_e 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 + The unscore command removes score entries from the list. You mmuusstt 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. - 3.24. Spam detection + 33..2244.. SSppaamm ddeetteeccttiioonn - Usage: spam pattern format - Usage: nospam pattern + Usage: spam _p_a_t_t_e_r_n _f_o_r_m_a_t + Usage: nospam _p_a_t_t_e_r_n 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 + _l_i_m_i_t, _s_e_a_r_c_h, and _s_o_r_t 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 + using the spam command. _p_a_t_t_e_r_n 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 + governed by the _f_o_r_m_a_t parameter. _f_o_r_m_a_t can be any static text, but + it also can include back-references from the _p_a_t_t_e_r_n 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. @@ -1894,16 +1941,16 @@ 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 + tag will consist of all the _f_o_r_m_a_t 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: - 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=", " + 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 @@ -1912,12 +1959,12 @@ report indicate the checksum used -- in this case, ``Fuz2''.) If the $spam_separator variable is unset, then each spam pattern match - supercedes the previous one. Instead of getting joined format strings, + supercedes the previous one. Instead of getting joined _f_o_r_m_a_t 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. + matching expression matches against for _s_e_a_r_c_h and _l_i_m_i_t 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 @@ -1925,12 +1972,12 @@ 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 + Generally, when you sort by spam tag, mutt will sort _l_e_x_i_c_a_l_l_y -- that is, by ordering strings alphnumerically. 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. + match _a_n_y 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 @@ -1942,12 +1989,12 @@ 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 + If the _p_a_t_t_e_r_n given to nospam is exactly the same as the _p_a_t_t_e_r_n 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 + _p_a_t_t_e_r_n for a spam command matches an entry on the nospam list, that + nospam entry will be removed. If the _p_a_t_t_e_r_n for nospam is ``*'', _a_l_l + _e_n_t_r_i_e_s _o_n _b_o_t_h _l_i_s_t_s 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 @@ -1957,35 +2004,35 @@ spam "^From: .*MAILER-DAEMON" "999" - 3.25. Setting variables + 33..2255.. SSeettttiinngg vvaarriiaabblleess - Usage: set [no|inv]variable[=value] [ variable ... ] - Usage: toggle variable [variable ... ] - Usage: unset variable [variable ... ] - Usage: reset variable [variable ... ] + Usage: set [no|inv]_v_a_r_i_a_b_l_e[=_v_a_l_u_e] [ _v_a_r_i_a_b_l_e ... ] + Usage: toggle _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] + Usage: unset _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] + Usage: reset _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] 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. + quadoption. _b_o_o_l_e_a_n variables can be _s_e_t (true) or _u_n_s_e_t (false). + _n_u_m_b_e_r variables can be assigned a positive integer value. - string variables consist of any number of printable characters. - strings must be enclosed in quotes if they contain spaces or tabs. - You may also use the ``C'' escape sequences \n and \t for newline and + _s_t_r_i_n_g variables consist of any number of printable characters. + _s_t_r_i_n_g_s must be enclosed in quotes if they contain spaces or tabs. + You may also use the ``C'' escape sequences \\nn and \\tt 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 + _q_u_a_d_o_p_t_i_o_n variables are used to control whether or not to be prompted + for certain actions, or to specify a default action. A value of _y_e_s 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 + answered yes to the question. Similarly, a value of _n_o will cause the 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.'' + of _a_s_k_-_y_e_s will cause a prompt with a default answer of ``yes'' and + _a_s_k_-_n_o 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 + For _b_o_o_l_e_a_n 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. @@ -1994,8 +2041,7 @@ 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 + Using the enter-command function in the _i_n_d_e_x menu, you can query the value of a variable by prefixing the name of the variable with a question mark: @@ -2012,9 +2058,9 @@ With the reset command there exists the special variable ``all'', which allows you to reset all variables to their system defaults. - 3.26. Reading initialization commands from another file + 33..2266.. RReeaaddiinngg iinniittiiaalliizzaattiioonn ccoommmmaannddss ffrroomm aannootthheerr ffiillee - Usage: source filename + Usage: source _f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ] This command allows the inclusion of initialization commands from other files. For example, I place all of my aliases in @@ -2024,22 +2070,22 @@ 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 _f_i_l_e_n_a_m_e is considered to be an executable program from which to read input (eg. source ~/bin/myscript|). - 3.27. Removing hooks + 33..2277.. RReemmoovviinngg hhooookkss - Usage: unhook [ * | hook-type ] + Usage: unhook [ * | _h_o_o_k_-_t_y_p_e ] 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. - 4. Advanced Usage + 44.. AAddvvaanncceedd UUssaaggee - 4.1. Regular Expressions + 44..11.. RReegguullaarr EExxpprreessssiioonnss All string patterns in Mutt including those in more complex ``patterns'' must be specified using regular expressions (regexp) in @@ -2075,8 +2121,8 @@ 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 + ``^'' then it matches any character nnoott in the list. For example, the + regular expression [[00112233445566778899]] 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 @@ -2088,51 +2134,50 @@ consist of ``[:'', a keyword denoting the class, and ``:]''. The following classes are defined by the POSIX standard: - [:alnum:] + [[::aallnnuumm::]] Alphanumeric characters. - [:alpha:] + [[::aallpphhaa::]] Alphabetic characters. - [:blank:] + [[::bbllaannkk::]] Space or tab characters. - [:cntrl:] + [[::ccnnttrrll::]] Control characters. - [:digit:] + [[::ddiiggiitt::]] Numeric characters. - [:graph:] + [[::ggrraapphh::]] Characters that are both printable and visible. (A space is printable, but not visible, while an ``a'' is both.) - [:lower:] + [[::lloowweerr::]] Lower-case alphabetic characters. - [:print:] + [[::pprriinntt::]] Printable characters (characters that are not control characters.) - [:punct:] + [[::ppuunncctt::]] Punctuation characters (characters that are not letter, digits, control characters, or space characters). - - [:space:] + [[::ssppaaccee::]] Space characters (such as space, tab and formfeed, to name a few). - [:upper:] + [[::uuppppeerr::]] Upper-case alphabetic characters. - [:xdigit:] + [[::xxddiiggiitt::]] Characters that are hexadecimal digits. A character class is only valid in a regular expression inside the 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]. + to the brackets delimiting the bracket list. For example, [[[[::ddiiggiitt::]]]] + is equivalent to [[00--99]]. Two additional special sequences can appear in character lists. These apply to non-ASCII character sets, which can have single symbols @@ -2140,41 +2185,41 @@ character, as well as several characters that are equivalent for collating or sorting purposes: - Collating Symbols + CCoollllaattiinngg SSyymmbboollss 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 + collating element, then [[[[..cchh..]]]] is a regexp that matches this + collating element, while [[cchh]] is a regexp that matches either ``c'' or ``h''. - Equivalence Classes + EEqquuiivvaalleennccee CCllaasssseess 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''. + represent all of ``e'' ``e'' and ``e''. In this case, [[[[==ee==]]]] + is a regexp that matches any of ``e'', ``e'' and ``e''. A regular expression matching a single character may be followed by one of several repetition operators: - ? The preceding item is optional and matched at most once. + ?? The preceding item is optional and matched at most once. - * The preceding item will be matched zero or more times. + ** The preceding item will be matched zero or more times. - + The preceding item will be matched one or more times. + ++ The preceding item will be matched one or more times. - {n} - The preceding item is matched exactly n times. + {{nn}} + The preceding item is matched exactly _n times. - {n,} - The preceding item is matched n or more times. + {{nn,,}} + The preceding item is matched _n or more times. - {,m} - The preceding item is matched at most m times. + {{,,mm}} + 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. + {{nn,,mm}} + 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 @@ -2188,85 +2233,88 @@ 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 + NNoottee:: If you compile Mutt with the GNU _r_x package, the following operators may also be used in regular expressions: - \\y + \\\\yy Matches the empty string at either the beginning or the end of a word. - \\B + \\\\BB 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 + \\\\ww Matches any word-constituent character (letter, digit, or underscore). - \\W + \\\\WW 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. - 4.2. Patterns + 44..22.. PPaatttteerrnnss Many of Mutt's commands allow you to specify a pattern to match (limit, tag-pattern, delete-pattern, etc.). There are several ways to select messages: - ~A all messages - ~b EXPR messages which contain EXPR in the message body - ~B EXPR messages which contain EXPR in the whole message - ~c USER messages carbon-copied to USER - ~C EXPR message is either to: or cc: EXPR - ~D deleted messages - ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range - ~E expired messages - ~e EXPR message which contains EXPR in the ``Sender'' field - ~F flagged messages - ~f USER messages originating from USER - ~g cryptographically signed messages - ~G cryptographically encrypted messages - ~H EXPR messages with a spam attribute matching EXPR - ~h EXPR messages which contain EXPR in the message header - ~k message contains PGP key material - ~i ID message which match ID in the ``Message-ID'' field - ~L EXPR message is either originated or received by EXPR - ~l message is addressed to a known mailing list - ~m [MIN]-[MAX] message in the range MIN to MAX *) - ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *) - ~N new messages - ~O old messages - ~p message is addressed to you (consults alternates) - ~P message is from you (consults alternates) - ~Q messages which have been replied to - ~R read messages - ~r [MIN]-[MAX] messages with ``date-received'' in a Date range - ~S superseded messages - ~s SUBJECT messages having SUBJECT in the ``Subject'' field. - ~T tagged messages - ~t USER messages addressed to USER - ~U unread messages - ~v message is part of a collapsed thread. - ~V cryptographically verified messages - ~x EXPR messages which contain EXPR in the `References' field - ~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) + ~A all messages + ~b EXPR messages which contain EXPR in the message body + ~B EXPR messages which contain EXPR in the whole message + ~c USER messages carbon-copied to USER + ~C EXPR message is either to: or cc: EXPR + ~D deleted messages + ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range + ~E expired messages + ~e EXPR message which contains EXPR in the ``Sender'' field + ~F flagged messages + ~f USER messages originating from USER + ~g cryptographically signed messages + ~G cryptographically encrypted messages + ~H EXPR messages with a spam attribute matching EXPR + ~h EXPR messages which contain EXPR in the message header + ~k message contains PGP key material + ~i ID message which match ID in the ``Message-ID'' field + ~L EXPR message is either originated or received by EXPR + ~l message is addressed to a known mailing list + ~m [MIN]-[MAX] message in the range MIN to MAX *) + ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *) + ~N new messages + ~O old messages + ~p message is addressed to you (consults alternates) + ~P message is from you (consults alternates) + ~Q messages which have been replied to + ~R read messages + ~r [MIN]-[MAX] messages with ``date-received'' in a Date range + ~S superseded messages + ~s SUBJECT messages having SUBJECT in the ``Subject'' field. + ~T tagged messages + ~t USER messages addressed to USER + ~U unread messages + ~v message is part of a collapsed thread. + ~V cryptographically verified messages + ~x EXPR messages which contain EXPR in the `References' field + ~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) + ~* ``From'' contains realname and (syntactically) valid + address (excluded are addresses matching against + alternates or any alias) Where EXPR, USER, ID, and SUBJECT are ``regular expressions''. Special attention has to be made when using regular expressions inside @@ -2277,7 +2325,7 @@ *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too. - 4.2.1. Pattern Modifier + 44..22..11.. PPaatttteerrnn MMooddiiffiieerr 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 @@ -2287,7 +2335,7 @@ ^~C \.de$ - 4.2.2. Complex Patterns + 44..22..22.. CCoommpplleexx PPaatttteerrnnss Logical AND is performed by specifying more than one criterion. For example: @@ -2295,17 +2343,17 @@ ~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 aanndd 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 + +o ! -- logical NOT operator - · | -- logical OR operator + +o | -- logical OR operator - · () -- logical grouping 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 @@ -2321,33 +2369,33 @@ '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")' Note that if a regular expression contains parenthesis, or a veritical - bar ("|"), you must enclose the expression in double or single quotes + bar ("|"), you mmuusstt 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 - seperated to two OR'd patterns: ~f me@(mutt\.org and cs\.hmc\.edu). + seperated to two OR'd patterns: _~_f _m_e_@_(_m_u_t_t_\_._o_r_g and _c_s_\_._h_m_c_\_._e_d_u_). They are never what you want. - 4.2.3. Searching by Date + 44..22..33.. SSeeaarrcchhiinngg bbyy DDaattee - Mutt supports two types of dates, absolute and relative. + Mutt supports two types of dates, _a_b_s_o_l_u_t_e and _r_e_l_a_t_i_v_e. - Absolute. Dates must be in DD/MM/YY format (month and year are + AAbbssoolluuttee. Dates mmuusstt 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 + all messages _b_e_f_o_r_e the given date will be selected. If you omit the + maximum (second) date, and specify ``DD/MM/YY-'', all messages _a_f_t_e_r 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 + EErrrroorr MMaarrggiinnss. You can add error margins to absolute dates. An error margin is a sign (+ or -), followed by a digit, followed by one of the following units: @@ -2362,18 +2410,18 @@ 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 + Limit to messages matching: ~d 15/1/2001*2w - Relative. This type of date is relative to the current date, and may + RReellaattiivvee. This type of date is relative to the current date, and may be specified as: - · >offset (messages older than offset units) + +o >_o_f_f_s_e_t (messages older than _o_f_f_s_e_t units) - · <offset (messages newer than offset units) + +o <_o_f_f_s_e_t (messages newer than _o_f_f_s_e_t units) - · =offset (messages exactly offset units old) + +o =_o_f_f_s_e_t (messages exactly _o_f_f_s_e_t units old) - offset is specified as a positive number with one of the following + _o_f_f_s_e_t is specified as a positive number with one of the following units: y years @@ -2385,12 +2433,12 @@ Limit to messages matching: ~d <1m - Note: all dates used when searching are relative to the local time + NNoottee:: all dates used when searching are relative to the llooccaall 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 + include a %[...] format, these are nnoott the dates shown in the main index. - 4.3. Using Tags + 44..33.. UUssiinngg TTaaggss Sometimes it is desirable to perform an operation on a group of messages all at once rather than one at a time. An example might be @@ -2403,7 +2451,7 @@ 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 + When the ``tag-prefix'' operator is used, the nneexxtt 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 @@ -2414,32 +2462,33 @@ 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.4. Using Hooks - A hook is a concept borrowed from the EMACS editor which allows you to + 44..44.. UUssiinngg HHooookkss + + A _h_o_o_k is a concept borrowed from the EMACS editor 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'' + world, a _h_o_o_k consists of a ``regular expression'' or ``pattern'' along with a configuration option/command. See - · ``folder-hook'' + +o ``folder-hook'' - · ``send-hook'' + +o ``send-hook'' - · ``message-hook'' + +o ``message-hook'' - · ``save-hook'' + +o ``save-hook'' - · ``mbox-hook'' + +o ``mbox-hook'' - · ``fcc-hook'' + +o ``fcc-hook'' - · ``fcc-save-hook'' + +o ``fcc-save-hook'' - for specific details on each type of hook available. + for specific details on each type of _h_o_o_k available. - Note: if a hook changes configuration settings, these changes remain + NNoottee:: 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 @@ -2448,7 +2497,7 @@ send-hook . 'unmy_hdr From:' send-hook ~C'^b@b\.b$' my_hdr from: c@c.c - 4.4.1. Message Matching in Hooks + 44..44..11.. MMeessssaaggee MMaattcchhiinngg iinn HHooookkss Hooks that act upon messages (send-hook, save-hook, fcc-hook, message- hook) are evaluated in a slightly different manner. For the other @@ -2458,7 +2507,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 + would when _l_i_m_i_t_i_n_g or _s_e_a_r_c_h_i_n_g 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.). @@ -2469,16 +2518,64 @@ 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. + _m_e_@_c_s_._h_m_c_._e_d_u. + 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 + the full searching language. You can still specify a simple _r_e_g_u_l_a_r + _e_x_p_r_e_s_s_i_o_n 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. - 4.5. External Address Queries + 44..55.. UUssiinngggg tthhee ssiiddeebbaarr + + The sidebar, a feature specific to Mutt-ng, allows you to use a + mailbox listing which looks very similar to the ones you probably know + from GUI mail clients. The sidebar lists all specified mailboxes, + shows the number in each and highlights the ones with new email Use + the following configuration commands: + + set sidebar_visible="yes" + set sidebar_width=25 + + If you want to specify the mailboxes you can do so with: + + set mbox='=INBOX' + mailboxes INBOX \ + MBOX1 \ + MBOX2 \ + ... + + You can also specify the colors for mailboxes with new mails by using: + + color sidebar_new red black + + The available functions are: + + sidebar-scroll-up Scrolls the mailbox list up 1 page + sidebar-scroll-down Scrolls the mailbox list down 1 page + sidebar-next Hilights the next mailbox + sidebar-next-new Hilights the next mailbox with new mail + sidebar-previous Hilights the previous mailbox + sidebar-open Opens the currently hilighted mailbox + + Reasonable key bindings look e.g. like this: + + bind index \Cp sidebar-prev + bind index \Cn sidebar-next + bind index \Cb sidebar-open + bind pager \Cp sidebar-prev + bind pager \Cn sidebar-next + bind pager \Cb sidebar-open + + macro index B ':toggle sidebar_visible^M' + macro pager B ':toggle sidebar_visible^M' + + You can then go up and down by pressing Ctrl-P and Ctrl-N, and switch + on and off the sidebar simply by pressing 'B'. + + 44..66.. EExxtteerrnnaall AAddddrreessss QQuueerriieess Mutt supports connecting to external directory databases such as LDAP, ph/qi, bbdb, or NIS through a wrapper script which connects to mutt @@ -2519,7 +2616,7 @@ will activate the query menu. At the query menu, you can select one or more addresses to be added to the prompt. - 4.6. Mailbox Formats + 44..77.. MMaaiillbbooxx FFoorrmmaattss Mutt supports reading and writing of four different mailbox formats: mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so @@ -2527,55 +2624,55 @@ 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 + mmbbooxx. 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 + 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 + MMMMDDFF. This is a variant of the _m_b_o_x 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 + MMHH. A radical departure from _m_b_o_x and _M_M_D_F, 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. Note: Mutt detects this type of + comma (,) prepended to the filename. NNoottee:: 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 + MMaaiillddiirr. The newest of the mailbox formats, used by the Qmail MTA (a + replacement for sendmail). Similar to _M_H, except that it adds three + subdirectories of the mailbox: _t_m_p, _n_e_w and _c_u_r. 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. - 4.7. Mailbox Shortcuts + 44..88.. MMaaiillbbooxx SShhoorrttccuuttss There are a number of built in shortcuts which refer to specific mailboxes. These shortcuts can be used anywhere you are prompted for a file or mailbox path. - · ! -- refers to your ``$spoolfile'' (incoming) mailbox + +o ! -- refers to your ``$spoolfile'' (incoming) mailbox - · > -- refers to your ``$mbox'' file + +o > -- refers to your ``$mbox'' file - · < -- refers to your ``$record'' file + +o < -- refers to your ``$record'' file - · - or !! -- refers to the file you've last visited + +o - or !! -- refers to the file you've last visited - · ~ -- refers to your home directory + +o ~ -- refers to your home directory - · = or + -- refers to your ``$folder'' directory + +o = or + -- refers to your ``$folder'' directory - · @alias -- refers to the ``default save folder'' as determined by + +o @_a_l_i_a_s -- refers to the ``default save folder'' as determined by the address of the alias - 4.8. Handling Mailing Lists + 44..99.. HHaannddlliinngg MMaaiilliinngg LLiissttss Mutt has a few configuration options that make dealing with large amounts of mail easier. The first thing you must do is to let Mutt @@ -2588,7 +2685,7 @@ 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 + the _i_n_d_e_x 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 @@ -2599,7 +2696,7 @@ to get quite large. Most people do not bother to remove the author of the message they are 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 + by default is bound to ``L'' in the _i_n_d_e_x menu and _p_a_g_e_r, 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). @@ -2631,10 +2728,10 @@ 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 + address to use. If set to _a_s_k_-_y_e_s or _a_s_k_-_n_o, 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 + ``From'' field. When set to _y_e_s, the ``Reply-To'' field will be used when present. The ``X-Label:'' header field can be used to further identify mailing @@ -2642,7 +2739,7 @@ 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 + 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. @@ -2654,7 +2751,39 @@ dealing with large volume mailing lists easier because you can easily delete uninteresting threads and quickly find topics of value. - 4.9. Delivery Status Notification (DSN) Support + 44..1100.. EEddiittiinngg tthhrreeaaddss + + Mutt has the ability to dynamically restructure threads that are + broken either by misconfigured software or bad behaviour from some + correspondents. This allows to clean your mailboxes formats) from + these annoyances which make it hard to follow a discussion. + + If you want to use these functions with IMAP, you need to compile Mutt + with the _-_-_e_n_a_b_l_e_-_i_m_a_p_-_e_d_i_t_-_t_h_r_e_a_d_s configure flag. + + 44..1100..11.. LLiinnkkiinngg tthhrreeaaddss + + 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 childs at once, tagging them and using + the tag-prefix command (';') or the auto_tag option. + + 44..1100..22.. BBrreeaakkiinngg tthhrreeaaddss + + 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. + + 44..1111.. DDeelliivveerryy SSttaattuuss NNoottiiffiiccaattiioonn ((DDSSNN)) SSuuppppoorrtt RFC1894 defines a set of MIME content types for relaying information about the status of electronic mail messages. These can be thought of @@ -2668,10 +2797,10 @@ message should be returned with the receipt (headers or full message). Refer to the man page on sendmail for more details on DSN. - 4.10. POP3 Support (OPTIONAL) + 44..1122.. PPOOPP33 SSuuppppoorrtt ((OOPPTTIIOONNAALL)) - If Mutt was compiled with POP3 support (by running the configure - script with the --enable-pop flag), it has the ability to work with + If Mutt was compiled with POP3 support (by running the _c_o_n_f_i_g_u_r_e + script with the _-_-_e_n_a_b_l_e_-_p_o_p flag), it has the ability to work with mailboxes located on a remote POP3 server and fetch mail for local browsing. @@ -2680,7 +2809,6 @@ You can select an alternative port by specifying it with the server, ie: pop://popserver:port/. - You can also specify different username for each folder, ie: pop://username@popserver[:port]/. @@ -2689,24 +2817,24 @@ can be controlled by the ``$pop_checkinterval'' variable, which defaults to every 60 seconds. - If Mutt was compiled with SSL support (by running the configure script - with the --with-ssl flag), connections to POP3 servers can be + If Mutt was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e script + with the _-_-_w_i_t_h_-_s_s_l flag), connections to POP3 servers can be encrypted. This naturally requires that the server supports SSL encrypted connections. To access a folder with POP3/SSL, you should use pops: prefix, ie: pops://[username@]popserver[:port]/. - Another way to access your POP3 mail is the fetch-mail function + Another way to access your POP3 mail is the _f_e_t_c_h_-_m_a_i_l 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 local mailbox you + NNoottee:: If you only need to fetch all messages to local mailbox you should consider using a specialized program, such as fetchmail - 4.11. IMAP Support (OPTIONAL) + 44..1133.. IIMMAAPP SSuuppppoorrtt ((OOPPTTIIOONNAALL)) - If Mutt was compiled with IMAP support (by running the configure - script with the --enable-imap flag), it has the ability to work with + If Mutt was compiled with IMAP support (by running the _c_o_n_f_i_g_u_r_e + script with the _-_-_e_n_a_b_l_e_-_i_m_a_p 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 @@ -2722,8 +2850,8 @@ You can also specify different username for each folder, ie: imap://username@imapserver[:port]/INBOX. - If Mutt was compiled with SSL support (by running the configure script - with the --with-ssl flag), connections to IMAP servers can be + If Mutt was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e script + with the _-_-_w_i_t_h_-_s_s_l flag), connections to IMAP servers can be encrypted. This naturally requires that the server supports SSL encrypted connections. To access a folder with IMAP/SSL, you should use imaps://[username@]imapserver[:port]/path/to/folder as your folder @@ -2738,15 +2866,15 @@ 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'' + the _t_o_g_g_l_e_-_s_u_b_s_c_r_i_b_e_d 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 + set mail_check=90 + set timeout=15 with relatively good results over my slow modem line. @@ -2754,28 +2882,30 @@ to v12.250, the server has been reported to disconnect a client if another client selects the same folder. - 4.11.1. The Folder Browser + 44..1133..11.. TThhee FFoollddeerr BBrroowwsseerr 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", + +o 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 + +o 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 delete mailboxes with the delete-mailbox command (bound to - d by default. You may also subscribe and unsubscribe to mailboxes - (normally these are bound to s and u, respectively). + +o 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.11.2. Authentication + 44..1133..22.. AAuutthheennttiiccaattiioonn Mutt supports four authentication methods with IMAP servers: SASL, GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add @@ -2792,7 +2922,7 @@ 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 with the _-_-_w_i_t_h_-_s_a_s_l flag. Mutt will try whichever methods are compiled in and available on the server, in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, @@ -2800,20 +2930,20 @@ There are a few variables which control authentication: - · ``$imap_user'' - controls the username under which you request + +o ``$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 + +o ``$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 + +o ``$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). - 4.12. Managing multiple IMAP/POP accounts (OPTIONAL) + 44..1144.. MMaannaaggiinngg mmuullttiippllee IIMMAAPP//PPOOPP aaccccoouunnttss ((OOPPTTIIOONNAALL)) If you happen to have accounts on multiple IMAP and/or POP servers, you may find managing all the authentication settings inconvenient and @@ -2824,14 +2954,14 @@ 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 . '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"' - 4.13. Start a WWW Browser on URLs (EXTERNAL) + 44..1155.. SSttaarrtt aa WWWWWW BBrroowwsseerr oonn UURRLLss ((EEXXTTEERRNNAALL)) - If a message contains URLs (unified resource locator = address in the - WWW space like http://www.mutt.org/), it is efficient to get a menu + If a message contains URLs (_u_n_i_f_i_e_d _r_e_s_o_u_r_c_e _l_o_c_a_t_o_r = address in the + WWW space like _h_t_t_p_:_/_/_w_w_w_._m_u_t_t_._o_r_g_/), 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 @@ -2840,7 +2970,150 @@ macro index \cb |urlview\n macro pager \cb |urlview\n - 5. Mutt's MIME Support + 44..1166.. CCoommpprreesssseedd ffoollddeerrss SSuuppppoorrtt ((OOPPTTIIOONNAALL)) + + If Mutt was compiled with compressed folders support (by running the + _c_o_n_f_i_g_u_r_e script with the _-_-_e_n_a_b_l_e_-_c_o_m_p_r_e_s_s_e_d 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. + + 44..1166..11.. OOppeenn aa ccoommpprreesssseedd mmaaiillbbooxx ffoorr rreeaaddiinngg + + Usage: open-hook _r_e_g_e_x_p "_c_o_m_m_a_n_d" + + The _c_o_m_m_a_n_d is the command that can be used for opening the folders + whose names match _r_e_g_e_x_p. + + The _c_o_m_m_a_n_d 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 _c_o_m_m_a_n_d should nnoott remove the original compressed file. The + _c_o_m_m_a_n_d 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 _c_o_m_m_a_n_d is empty, this operation is disabled for this file + type. + 44..1166..22.. WWrriittee aa ccoommpprreesssseedd mmaaiillbbooxx + + Usage: close-hook _r_e_g_e_x_p "_c_o_m_m_a_n_d" + + This is used to close the folder that was open with the ``open-hook'' + command after some changes were made to it. + + The _c_o_m_m_a_n_d string is the command that can be used for closing the + folders whose names match _r_e_g_e_x_p. 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 _c_o_m_m_a_n_d should nnoott remove the decompressed file. The _c_o_m_m_a_n_d + 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 _c_o_m_m_a_n_d is empty, this operation is disabled for this file + type, and the file can only be open in the readonly mode. + + ``close-hook'' is not called when you exit from the folder if the + folder was not changed. + + 44..1166..33.. AAppppeenndd aa mmeessssaaggee ttoo aa ccoommpprreesssseedd mmaaiillbbooxx + + Usage: append-hook _r_e_g_e_x_p "_c_o_m_m_a_n_d" + + This command is used for saving to an existing compressed folder. The + _c_o_m_m_a_n_d is the command that can be used for appending to the folders + whose names match _r_e_g_e_x_p. 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 _c_o_m_m_a_n_d should nnoott remove the decompressed file. The _c_o_m_m_a_n_d + 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 _c_o_m_m_a_n_d 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-hook''respectively) each time you will add + to it. + + 44..1166..44.. EEnnccrryypptteedd ffoollddeerrss + + 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. + + NNoottee:: 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. + + 55.. MMuutttt''ss MMIIMMEE SSuuppppoorrtt 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 @@ -2851,13 +3124,13 @@ IANA MIME types. The other is the mailcap file, which specifies the external commands to use for handling specific MIME types. - 5.1. Using MIME in Mutt + 55..11.. UUssiinngg MMIIMMEE iinn MMuutttt There are three areas/menus in Mutt which deal with MIME, they are the pager (while viewing a message), the attachment menu and the compose menu. - 5.1.1. Viewing MIME messages in the pager + 55..11..11.. VViieewwiinngg MMIIMMEE mmeessssaaggeess iinn tthhee ppaaggeerr When you select a message from the index and view it in the pager, Mutt decodes the message to a text representation. Mutt internally @@ -2873,13 +3146,14 @@ [-- Type: text/plain, Encoding: 7bit, Size: 10000 --] Where the Description is the description or filename given for the - attachment, and the Encoding is one of 7bit/8bit/quoted-print- - able/base64/binary. + 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) --] - 5.1.2. The Attachment Menu + 55..11..22.. TThhee AAttttaacchhmmeenntt MMeennuu The default binding for view-attachments is `v', which displays the attachment menu for a message. The attachment menu displays a list of @@ -2898,7 +3172,7 @@ See the help on the attachment menu for more information. - 5.1.3. The Compose Menu + 55..11..33.. TThhee CCoommppoossee MMeennuu 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 @@ -2926,7 +3200,7 @@ description of the attachment, and can be changed with the edit- description command (default: d). - 5.2. MIME Type configuration with mime.types + 55..22.. MMIIMMEE TTyyppee ccoonnffiigguurraattiioonn wwiitthh mmiimmee..ttyyppeess When you add an attachment to your mail message, Mutt searches your personal mime.types file at ${HOME}/.mime.types, and then the system @@ -2959,7 +3233,7 @@ mime types should only be used if the recipient of the message is likely to be expecting such attachments. - 5.3. MIME Viewer configuration with mailcap + 55..33.. MMIIMMEE VViieewweerr ccoonnffiigguurraattiioonn wwiitthh mmaaiillccaapp Mutt supports RFC 1524 MIME Configuration, in particular the Unix specific format specified in Appendix A of RFC 1524. This file format @@ -2981,13 +3255,14 @@ usually as /usr/local/etc/mailcap, which contains some baseline entries. - 5.3.1. The Basics of the mailcap file + 55..33..11.. TThhee BBaassiiccss ooff tthhee mmaaiillccaapp ffiillee 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 @@ -3026,10 +3301,10 @@ 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. + must use the %s syntax. NNoottee:: _S_o_m_e _o_l_d_e_r _v_e_r_s_i_o_n_s _o_f _l_y_n_x _c_o_n_t_a_i_n _a + _b_u_g _w_h_e_r_e _t_h_e_y _w_i_l_l _c_h_e_c_k _t_h_e _m_a_i_l_c_a_p _f_i_l_e _f_o_r _a _v_i_e_w_e_r _f_o_r _t_e_x_t_/_h_t_m_l_. + _T_h_e_y _w_i_l_l _f_i_n_d _t_h_e _l_i_n_e _w_h_i_c_h _c_a_l_l_s _l_y_n_x_, _a_n_d _r_u_n _i_t_. _T_h_i_s _c_a_u_s_e_s + _l_y_n_x _t_o _c_o_n_t_i_n_u_o_u_s_l_y _s_p_a_w_n _i_t_s_e_l_f _t_o _v_i_e_w _t_h_e _o_b_j_e_c_t_. 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 @@ -3045,7 +3320,7 @@ This is the simplest form of a mailcap file. - 5.3.2. Secure use of mailcap + 55..33..22.. SSeeccuurree uussee ooff mmaaiillccaapp The interpretion of shell meta-characters embedded in MIME parameters can lead to security problems in general. Mutt tries to quote @@ -3058,7 +3333,7 @@ care of it. Therefore you should pay attention to the following rules: - Keep the %-expandos away from shell quoting. Don't quote them with + _K_e_e_p _t_h_e _%_-_e_x_p_a_n_d_o_s _a_w_a_y _f_r_o_m _s_h_e_l_l _q_u_o_t_i_n_g_. 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 @@ -3075,15 +3350,15 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1 - 5.3.3. Advanced mailcap Usage + 55..33..33.. AAddvvaanncceedd mmaaiillccaapp UUssaaggee - 5.3.3.1. Optional Fields + 55..33..33..11.. OOppttiioonnaall FFiieellddss 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 + ccooppiioouussoouuttppuutt 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 @@ -3097,22 +3372,22 @@ 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 + nneeeeddsstteerrmmiinnaall Mutt uses this flag when viewing attachments with ``autoview'', 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 + entry has a _n_e_e_d_s_t_e_r_m_i_n_a_l 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= + ccoommppoossee==<> 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= + ccoommppoosseettyyppeedd==<> 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 @@ -3120,17 +3395,17 @@ filename, description, etc. for a new attachment. Mutt supports this from the compose menu. - print= + pprriinntt==<> This flag specifies the command to use to print a specific MIME type. Mutt supports this from the attachment and compose menus. - edit= + eeddiitt==<> 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=