Changeset 5487:6fd1fa2d98bc
- Timestamp:
- 2008-08-22 08:49:07 (3 months ago)
- Author:
- Rocco Rutte <pdmef@…>
- Branch:
- HEAD
- Message:
-
Manual: fix/improve markup/content, see #3109
- Files:
-
Legend:
- Unmodified
- Added
- Removed
-
|
r5485
|
r5487
|
|
| | 1 | 2008-08-21 10:42 +0200 Rocco Rutte <pdmef@gmx.net> (15d93fe50e62) |
| | 2 | |
| | 3 | * init.h: Clarify documentation for $config_charset. Closes #2021. |
| | 4 | |
| | 5 | 2008-08-21 10:30 +0200 Rocco Rutte <pdmef@gmx.net> (bc8b07e9e95b) |
| | 6 | |
| | 7 | * ChangeLog, doc/manual.xml.head: Improve color/mono command synopsis. |
| | 8 | Closes #2630. |
| | 9 | |
| 1 | 10 | 2008-08-21 09:36 +0200 Rocco Rutte <pdmef@gmx.net> (4139ac196ca8) |
| 2 | 11 | |
-
|
r5485
|
r5487
|
|
| 187 | 187 | </thead> |
| 188 | 188 | <tbody> |
| 189 | | <row><entry>j or Down</entry><entry>next-entry</entry><entry>move to the next entry</entry></row> |
| 190 | | <row><entry>k or Up</entry><entry>previous-entry</entry><entry>move to the previous entry</entry></row> |
| 191 | | <row><entry>z or PageDn</entry><entry>page-down</entry><entry>go to the next page</entry></row> |
| 192 | | <row><entry>Z or PageUp</entry><entry>page-up</entry><entry>go to the previous page</entry></row> |
| 193 | | <row><entry>= or Home</entry><entry>first-entry</entry><entry>jump to the first entry</entry></row> |
| 194 | | <row><entry>* or End</entry><entry>last-entry</entry><entry>jump to the last entry</entry></row> |
| | 189 | <row><entry>j or <Down></entry><entry>next-entry</entry><entry>move to the next entry</entry></row> |
| | 190 | <row><entry>k or <Up></entry><entry>previous-entry</entry><entry>move to the previous entry</entry></row> |
| | 191 | <row><entry>z or <PageDn></entry><entry>page-down</entry><entry>go to the next page</entry></row> |
| | 192 | <row><entry>Z or <PageUp></entry><entry>page-up</entry><entry>go to the previous page</entry></row> |
| | 193 | <row><entry>= or <Home></entry><entry>first-entry</entry><entry>jump to the first entry</entry></row> |
| | 194 | <row><entry>* or <End></entry><entry>last-entry</entry><entry>jump to the last entry</entry></row> |
| 195 | 195 | <row><entry>q</entry><entry>quit</entry><entry>exit the current menu</entry></row> |
| 196 | 196 | <row><entry>?</entry><entry>help</entry><entry>list all keybindings for the current menu</entry></row> |
| … |
… |
|
| 297 | 297 | Mutt automatically filters out repeated items from the history. It |
| 298 | 298 | also mimics the behavior of some shells by ignoring items starting |
| 299 | | with a space. |
| 300 | | </para> |
| 301 | | |
| 302 | | <para> |
| 303 | | The latter feature can be useful in macros to not clobber the history's |
| 304 | | valuable entries with unwanted entries. |
| | 299 | with a space. The latter feature can be useful in macros to not clobber |
| | 300 | the history's valuable entries with unwanted entries. |
| 305 | 301 | </para> |
| 306 | 302 | |
| … |
… |
|
| 329 | 325 | <para> |
| 330 | 326 | Common keys used to navigate through and manage messages in the index |
| 331 | | are shown in <xref linkend="tab-key-index"/>. |
| 332 | | </para> |
| 333 | | |
| 334 | | <para> |
| 335 | | |
| | 327 | are shown in <xref linkend="tab-key-index"/>. How messages are presented |
| | 328 | in the index menu can be customized using the |
| | 329 | <link linkend="index-format">$index_format</link> variable. |
| | 330 | </para> |
| | 331 | |
| | 332 | <para> |
| 336 | 333 | <table id="tab-key-index"> |
| 337 | 334 | <title>Most common message index keys</title> |
| … |
… |
|
| 376 | 373 | </para> |
| 377 | 374 | |
| 378 | | <sect3> |
| 379 | | <title>Status Flags</title> |
| 380 | | |
| 381 | 375 | <para> |
| 382 | 376 | In addition to who sent the message and the subject, a short summary of |
| … |
… |
|
| 384 | 378 | Zero or more of the ``flags'' in <xref linkend="tab-msg-status-flags"/> |
| 385 | 379 | may appear, some of which can be turned on or off using these functions: |
| 386 | | </para> |
| 387 | | |
| 388 | | <itemizedlist> |
| 389 | | <listitem> |
| 390 | | |
| 391 | | <para> |
| 392 | | <emphasis role="bold">set-flag</emphasis> (default: w) |
| 393 | | </para> |
| 394 | | </listitem> |
| 395 | | <listitem> |
| 396 | | |
| 397 | | <para> |
| 398 | | <emphasis role="bold">clear-flag</emphasis> (default: W) |
| 399 | | </para> |
| 400 | | </listitem> |
| 401 | | |
| 402 | | </itemizedlist> |
| | 380 | <literal>set-flag</literal> and <literal>clear-flag</literal> bound by default |
| | 381 | to ``w'' and ``W'' respectively. |
| | 382 | </para> |
| 403 | 383 | |
| 404 | 384 | <para> |
| … |
… |
|
| 446 | 426 | </table> |
| 447 | 427 | |
| 448 | | </sect3> |
| 449 | | |
| 450 | 428 | </sect2> |
| 451 | 429 | |
| … |
… |
|
| 460 | 438 | |
| 461 | 439 | <para> |
| 462 | | |
| 463 | 440 | <table id="tab-key-pager"> |
| 464 | 441 | <title>Most common pager keys</title> |
| … |
… |
|
| 482 | 459 | </tgroup> |
| 483 | 460 | </table> |
| 484 | | |
| 485 | 461 | </para> |
| 486 | 462 | |
| … |
… |
|
| 488 | 464 | In addition to key bindings in <xref linkend="tab-key-pager"/>, |
| 489 | 465 | many of the functions from the <emphasis>index</emphasis> are available in |
| 490 | | the pager, such as <emphasis>delete-message</emphasis> or <emphasis>copy-message</emphasis> (this is one |
| 491 | | advantage over using an external pager to view messages). |
| | 466 | the pager, such as <literal>delete-message</literal> or <literal>copy-message</literal> |
| | 467 | (this is one advantage over using an external pager to view messages). |
| 492 | 468 | </para> |
| 493 | 469 | |
| … |
… |
|
| 550 | 526 | |
| 551 | 527 | <para> |
| 552 | | Mutt uses these attributes for handling text/enriched messages, and they |
| 553 | | can also be used by an external <link linkend="auto-view">autoview</link> |
| 554 | | script for highlighting purposes. <emphasis role="bold">Note:</emphasis> If you change the colors for your |
| | 528 | Mutt uses these attributes for handling <literal>text/enriched</literal> |
| | 529 | messages, and they can also be used by an external |
| | 530 | <link linkend="auto-view">autoview</link> script for highlighting purposes. |
| | 531 | <emphasis role="bold">Note:</emphasis> If you change the colors for your |
| 555 | 532 | display, for example by changing the color associated with color2 for |
| 556 | 533 | your xterm, then that color will be used instead of green. |
| … |
… |
|
| 625 | 602 | |
| 626 | 603 | <para> |
| 627 | | <emphasis role="bold">create-alias</emphasis><anchor id="create-alias"/> (default: a) |
| 628 | | |
| 629 | | </para> |
| 630 | | |
| | 604 | In addition, the <emphasis>index</emphasis> and <emphasis>pager</emphasis> |
| | 605 | have these interesting functions: |
| | 606 | </para> |
| | 607 | |
| | 608 | <variablelist> |
| | 609 | |
| | 610 | <varlistentry> |
| | 611 | <term></term> |
| | 612 | <listitem><para></para></listitem> |
| | 613 | </varlistentry> |
| | 614 | |
| | 615 | <varlistentry> |
| | 616 | <term> |
| | 617 | <literal>create-alias</literal><anchor id="create-alias"/> (default: a) |
| | 618 | </term> |
| | 619 | <listitem> |
| 631 | 620 | <para> |
| 632 | 621 | Creates a new alias based upon the current message (or prompts for a |
| … |
… |
|
| 636 | 625 | does not add the aliases specified there-in, you must also <link linkend="source">source</link> the file. |
| 637 | 626 | </para> |
| 638 | | |
| 639 | | <para> |
| 640 | | <emphasis role="bold">check-traditional-pgp</emphasis><anchor id="check-traditional-pgp"/> (default: ESC P) |
| 641 | | |
| 642 | | </para> |
| 643 | | |
| | 627 | </listitem> |
| | 628 | </varlistentry> |
| | 629 | |
| | 630 | <varlistentry> |
| | 631 | <term> |
| | 632 | <literal>check-traditional-pgp</literal><anchor id="check-traditional-pgp"/> (default: ESC P) |
| | 633 | </term> |
| | 634 | <listitem> |
| 644 | 635 | <para> |
| 645 | 636 | This function will search the current message for content signed or |
| … |
… |
|
| 650 | 641 | effect. |
| 651 | 642 | </para> |
| 652 | | |
| 653 | | <para> |
| 654 | | <emphasis role="bold">display-toggle-weed</emphasis><anchor id="display-toggle-weed"/> (default: h) |
| 655 | | |
| 656 | | </para> |
| 657 | | |
| 658 | | <para> |
| 659 | | Toggles the weeding of message header fields specified by <link linkend="ignore">ignore</link> commands. |
| 660 | | </para> |
| 661 | | |
| 662 | | <para> |
| 663 | | <emphasis role="bold">edit</emphasis><anchor id="edit"/> (default: e) |
| 664 | | |
| 665 | | </para> |
| 666 | | |
| | 643 | </listitem> |
| | 644 | </varlistentry> |
| | 645 | |
| | 646 | <varlistentry> |
| | 647 | <term> |
| | 648 | <literal>edit</literal><anchor id="edit"/> (default: e) |
| | 649 | </term> |
| | 650 | <listitem> |
| 667 | 651 | <para> |
| 668 | 652 | This command (available in the ``index'' and ``pager'') allows you to |
| … |
… |
|
| 672 | 656 | marked for deletion. |
| 673 | 657 | </para> |
| 674 | | |
| 675 | | <para> |
| 676 | | <emphasis role="bold">edit-type</emphasis><anchor id="edit-type"/> |
| | 658 | </listitem> |
| | 659 | </varlistentry> |
| | 660 | |
| | 661 | <varlistentry> |
| | 662 | <term> |
| | 663 | <literal>edit-type</literal><anchor id="edit-type"/> |
| 677 | 664 | |
| 678 | 665 | (default: ˆE on the attachment menu, and in the pager and index menus; ˆT on the |
| 679 | 666 | compose menu) |
| 680 | | </para> |
| 681 | | |
| | 667 | </term> |
| | 668 | <listitem> |
| 682 | 669 | <para> |
| 683 | 670 | This command is used to temporarily edit an attachment's content |
| … |
… |
|
| 695 | 682 | to send. |
| 696 | 683 | </para> |
| 697 | | |
| 698 | | <para> |
| 699 | | <emphasis role="bold">enter-command</emphasis><anchor id="enter-command"/> (default: ``:'') |
| 700 | | |
| 701 | | </para> |
| 702 | | |
| | 684 | </listitem> |
| | 685 | </varlistentry> |
| | 686 | |
| | 687 | <varlistentry> |
| | 688 | <term> |
| | 689 | <literal>enter-command</literal><anchor id="enter-command"/> (default: ``:'') |
| | 690 | </term> |
| | 691 | <listitem> |
| 703 | 692 | <para> |
| 704 | 693 | This command is used to execute any command you would normally put in a |
| … |
… |
|
| 707 | 696 | fly. |
| 708 | 697 | </para> |
| 709 | | |
| 710 | | <para> |
| 711 | | <emphasis role="bold">extract-keys</emphasis><anchor id="extract-keys"/> (default: ˆK) |
| 712 | | |
| 713 | | </para> |
| 714 | | |
| | 698 | </listitem> |
| | 699 | </varlistentry> |
| | 700 | |
| | 701 | <varlistentry> |
| | 702 | <term> |
| | 703 | <literal>extract-keys</literal><anchor id="extract-keys"/> (default: ˆK) |
| | 704 | </term> |
| | 705 | <listitem> |
| 715 | 706 | <para> |
| 716 | 707 | This command extracts PGP public keys from the current or tagged |
| 717 | 708 | message(s) and adds them to your PGP public key ring. |
| 718 | 709 | </para> |
| 719 | | |
| 720 | | <para> |
| 721 | | <emphasis role="bold">forget-passphrase</emphasis><anchor id="forget-passphrase"/> (default: |
| | 710 | </listitem> |
| | 711 | </varlistentry> |
| | 712 | |
| | 713 | <varlistentry> |
| | 714 | <term> |
| | 715 | <literal>forget-passphrase</literal><anchor id="forget-passphrase"/> (default: |
| 722 | 716 | ˆF) |
| 723 | | |
| 724 | | </para> |
| 725 | | |
| | 717 | </term> |
| | 718 | <listitem> |
| 726 | 719 | <para> |
| 727 | 720 | This command wipes the passphrase(s) from memory. It is useful, if |
| 728 | 721 | you misspelled the passphrase. |
| 729 | 722 | </para> |
| 730 | | |
| 731 | | <para> |
| 732 | | <emphasis role="bold">list-reply</emphasis><anchor id="list-reply"/> (default: L) |
| 733 | | |
| 734 | | </para> |
| 735 | | |
| | 723 | </listitem> |
| | 724 | </varlistentry> |
| | 725 | |
| | 726 | <varlistentry> |
| | 727 | <term> |
| | 728 | <literal>list-reply</literal><anchor id="list-reply"/> (default: L) |
| | 729 | </term> |
| | 730 | <listitem> |
| 736 | 731 | <para> |
| 737 | 732 | Reply to the current or tagged message(s) by extracting any addresses which |
| … |
… |
|
| 743 | 738 | the message you are replying to. |
| 744 | 739 | </para> |
| 745 | | |
| 746 | | <para> |
| 747 | | <emphasis role="bold">pipe-message</emphasis><anchor id="pipe-message"/> (default: |) |
| 748 | | |
| 749 | | </para> |
| 750 | | |
| | 740 | </listitem> |
| | 741 | </varlistentry> |
| | 742 | |
| | 743 | <varlistentry> |
| | 744 | <term> |
| | 745 | <literal>pipe-message</literal><anchor id="pipe-message"/> (default: |) |
| | 746 | </term> |
| | 747 | <listitem> |
| 751 | 748 | <para> |
| 752 | 749 | Asks for an external Unix command and pipes the current or |
| … |
… |
|
| 754 | 751 | <link linkend="pipe-sep">$pipe_sep</link> and <link linkend="wait-key">$wait_key</link> control the exact behavior of this function. |
| 755 | 752 | </para> |
| 756 | | |
| 757 | | <para> |
| 758 | | <emphasis role="bold">resend-message</emphasis><anchor id="resend-message"/> (default: ESC e) |
| 759 | | |
| 760 | | </para> |
| 761 | | |
| | 753 | </listitem> |
| | 754 | </varlistentry> |
| | 755 | |
| | 756 | <varlistentry> |
| | 757 | <term> |
| | 758 | <literal>resend-message</literal><anchor id="resend-message"/> (default: ESC e) |
| | 759 | </term> |
| | 760 | <listitem> |
| 762 | 761 | <para> |
| 763 | 762 | With resend-message, mutt takes the current message as a template for a |
| … |
… |
|
| 774 | 773 | as a message/rfc822 body part. |
| 775 | 774 | </para> |
| 776 | | |
| 777 | | <para> |
| 778 | | <emphasis role="bold">shell-escape</emphasis><anchor id="shell-escape"/> (default: !) |
| 779 | | |
| 780 | | </para> |
| 781 | | |
| | 775 | </listitem> |
| | 776 | </varlistentry> |
| | 777 | |
| | 778 | <varlistentry> |
| | 779 | <term> |
| | 780 | <literal>shell-escape</literal><anchor id="shell-escape"/> (default: !) |
| | 781 | </term> |
| | 782 | <listitem> |
| 782 | 783 | <para> |
| 783 | 784 | Asks for an external Unix command and executes it. The <link linkend="wait-key">$wait_key</link> can be used to control |
| … |
… |
|
| 786 | 787 | the return status of the named command. |
| 787 | 788 | </para> |
| 788 | | |
| 789 | | <para> |
| 790 | | <emphasis role="bold">toggle-quoted</emphasis><anchor id="toggle-quoted"/> (default: T) |
| 791 | | |
| 792 | | </para> |
| 793 | | |
| | 789 | </listitem> |
| | 790 | </varlistentry> |
| | 791 | |
| | 792 | <varlistentry> |
| | 793 | <term> |
| | 794 | <literal>toggle-quoted</literal><anchor id="toggle-quoted"/> (default: T) |
| | 795 | </term> |
| | 796 | <listitem> |
| 794 | 797 | <para> |
| 795 | 798 | The <emphasis>pager</emphasis> uses the <link linkend="quote-regexp">$quote_regexp</link> variable to detect quoted text when |
| … |
… |
|
| 799 | 802 | quoted text in the way. |
| 800 | 803 | </para> |
| 801 | | |
| 802 | | <para> |
| 803 | | <emphasis role="bold">skip-quoted</emphasis><anchor id="skip-quoted"/> (default: S) |
| 804 | | |
| 805 | | </para> |
| 806 | | |
| | 804 | </listitem> |
| | 805 | </varlistentry> |
| | 806 | |
| | 807 | <varlistentry> |
| | 808 | <term> |
| | 809 | <literal>skip-quoted</literal><anchor id="skip-quoted"/> (default: S) |
| | 810 | </term> |
| | 811 | <listitem> |
| 807 | 812 | <para> |
| 808 | 813 | This function will go to the next line of non-quoted text which come |
| 809 | 814 | after a line of quoted text in the internal pager. |
| 810 | 815 | </para> |
| | 816 | </listitem> |
| | 817 | </varlistentry> |
| | 818 | |
| | 819 | </variablelist> |
| 811 | 820 | |
| 812 | 821 | </sect2> |
| … |
… |
|
| 817 | 826 | <title>Sending Mail</title> |
| 818 | 827 | |
| | 828 | <sect2> |
| | 829 | <title>Introduction</title> |
| | 830 | |
| 819 | 831 | <para> |
| 820 | 832 | The bindings shown in <xref linkend="tab-key-send"/> are available in the |
| 821 | | <emphasis>index</emphasis> for sending messages. |
| | 833 | <emphasis>index</emphasis> and <emphasis>pager</emphasis> to start a new message. |
| 822 | 834 | </para> |
| 823 | 835 | |
| … |
… |
|
| 845 | 857 | |
| 846 | 858 | <para> |
| 847 | | Bouncing a message sends the message as is to the recipient you |
| 848 | | specify. Forwarding a message allows you to add comments or |
| | 859 | <emphasis>Bouncing</emphasis> a message sends the message as is to the recipient you |
| | 860 | specify. <emphasis>Forwarding</emphasis> a message allows you to add comments or |
| 849 | 861 | modify the message you are forwarding. These items are discussed |
| 850 | 862 | in greater detail in the next chapter ``<link linkend="forwarding-mail">Forwarding |
| … |
… |
|
| 867 | 879 | |
| 868 | 880 | <para> |
| 869 | | Mutt will then automatically start your <link linkend="editor">$editor</link> on the message body. If the <link linkend="edit-headers">$edit_headers</link> variable is set, the headers will be at |
| 870 | | the top of the message in your editor. Any messages you are replying |
| 871 | | to will be added in sort order to the message, with appropriate <link linkend="attribution">$attribution</link>, <link linkend="indent-string">$indent_string</link> and <link linkend="post-indent-string">$post_indent_string</link>. When forwarding a |
| 872 | | message, if the <link linkend="mime-forward">$mime_forward</link> |
| | 881 | Mutt will then automatically start your <link linkend="editor">$editor</link> |
| | 882 | on the message body. If the <link linkend="edit-headers">$edit_headers</link> |
| | 883 | variable is set, the headers will be at the top of the message in your editor. |
| | 884 | Any messages you are replying to will be added in sort order to the message, |
| | 885 | with appropriate <link linkend="attribution">$attribution</link>, |
| | 886 | <link linkend="indent-string">$indent_string</link> and |
| | 887 | <link linkend="post-indent-string">$post_indent_string</link>. |
| | 888 | When forwarding a message, if the <link linkend="mime-forward">$mime_forward</link> |
| 873 | 889 | variable is unset, a copy of the forwarded message will be included. If |
| 874 | 890 | you have specified a <link linkend="signature">$signature</link>, it |
| … |
… |
|
| 879 | 895 | Once you have finished editing the body of your mail message, you are |
| 880 | 896 | returned to the <emphasis>compose</emphasis> menu providing the functions |
| 881 | | show in <xref linkend="tab-func-compose"/>. |
| | 897 | show in <xref linkend="tab-func-compose"/> to modify, send or postpone the |
| | 898 | message. |
| 882 | 899 | </para> |
| 883 | 900 | |
| … |
… |
|
| 918 | 935 | |
| 919 | 936 | <para> |
| 920 | | <emphasis role="bold">Note:</emphasis> The attach-message function will prompt you for a folder to |
| | 937 | The compose menu is also used to edit the attachments for a message which can be eiter files |
| | 938 | or other messages. The <literal>attach-message</literal> function to will prompt you for a folder to |
| 921 | 939 | attach messages from. You can now tag messages in that folder and they |
| 922 | 940 | will be attached to the message you are sending. Note that certain |
| 923 | 941 | operations like composing a new mail, replying, forwarding, etc. are |
| 924 | | not permitted when you are in that folder. The %r in <link linkend="status-format">$status_format</link> will change to |
| | 942 | not permitted when you are in that folder. The %r in |
| | 943 | <link linkend="status-format">$status_format</link> will change to |
| 925 | 944 | a 'A' to indicate that you are in attach-message mode. |
| 926 | 945 | </para> |
| | 946 | |
| | 947 | </sect2> |
| 927 | 948 | |
| 928 | 949 | <sect2> |
| … |
… |
|
| 930 | 951 | |
| 931 | 952 | <para> |
| 932 | | When editing the header of your outgoing message, there are a couple of |
| 933 | | special features available. |
| 934 | | </para> |
| | 953 | When editing the header because of <link linkend="edit-headers">$edit_headers</link> |
| | 954 | being set, there are a couple of special features available. |
| | 955 | </para> |
| | 956 | |
| | 957 | <sect3> |
| | 958 | <title>Fcc: pseudo header</title> |
| 935 | 959 | |
| 936 | 960 | <para> |
| … |
… |
|
| 939 | 963 | <literal>Fcc:</literal> <emphasis>filename</emphasis> |
| 940 | 964 | |
| 941 | | Mutt will pick up <emphasis>filename</emphasis> |
| | 965 | as a header, Mutt will pick up <emphasis>filename</emphasis> |
| 942 | 966 | just as if you had used the <emphasis>edit-fcc</emphasis> function in the <emphasis>compose</emphasis> menu. |
| 943 | | </para> |
| | 967 | This header will not be included in sent messages. |
| | 968 | </para> |
| | 969 | |
| | 970 | </sect3> |
| | 971 | |
| | 972 | <sect3> |
| | 973 | <title>Attach: pseudo header</title> |
| 944 | 974 | |
| 945 | 975 | <para> |
| … |
… |
|
| 949 | 979 | |
| 950 | 980 | where <emphasis>filename</emphasis> is the file to attach and <emphasis>description</emphasis> is an |
| 951 | | optional string to use as the description of the attached file. |
| 952 | | </para> |
| 953 | | |
| 954 | | <para> |
| 955 | | When replying to messages, if you remove the <emphasis>In-Reply-To:</emphasis> field from |
| 956 | | the header field, Mutt will not generate a <emphasis>References:</emphasis> field, which |
| 957 | | allows you to create a new message thread. |
| 958 | | </para> |
| 959 | | |
| 960 | | <para> |
| 961 | | Also see <link linkend="edit-headers">$edit_headers</link>. |
| 962 | | </para> |
| 963 | | |
| 964 | | </sect2> |
| 965 | | |
| 966 | | <sect2> |
| 967 | | <title>Using Mutt with PGP</title> |
| | 981 | optional string to use as the description of the attached file. This header, too, won't be send |
| | 982 | out. |
| | 983 | </para> |
| | 984 | |
| | 985 | </sect3> |
| | 986 | |
| | 987 | <sect3> |
| | 988 | <title>Pgp: pseudo header</title> |
| 968 | 989 | |
| 969 | 990 | <para> |
| … |
… |
|
| 1056 | 1077 | </para> |
| 1057 | 1078 | |
| | 1079 | </sect3> |
| | 1080 | |
| | 1081 | <sect3> |
| | 1082 | <title>In-Reply-To: header</title> |
| | 1083 | |
| | 1084 | <para> |
| | 1085 | When replying to messages, the <emphasis>In-Reply-To:</emphasis> header contains the |
| | 1086 | Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a |
| | 1087 | <emphasis>References:</emphasis> field, which allows you to create a new message thread, for example |
| | 1088 | to create a new list to a mailing list without having to needing to enter the mailing list's address. |
| | 1089 | </para> |
| | 1090 | |
| | 1091 | </sect3> |
| | 1092 | |
| 1058 | 1093 | </sect2> |
| 1059 | 1094 | |
| 1060 | 1095 | <sect2> |
| 1061 | | <title>Sending anonymous messages via mixmaster.</title> |
| 1062 | | |
| 1063 | | <para> |
| 1064 | | You may also have configured mutt to co-operate with Mixmaster, an |
| | 1096 | <title>Sending anonymous messages via mixmaster</title> |
| | 1097 | |
| | 1098 | <para> |
| | 1099 | You may also have compiled mutt to co-operate with Mixmaster, an |
| 1065 | 1100 | anonymous remailer. Mixmaster permits you to send your messages |
| 1066 | 1101 | anonymously using a chain of remailers. Mixmaster support in mutt is for |
| … |
… |
|
| 1206 | 1241 | <para> |
| 1207 | 1242 | Bouncing and forwarding let you send an existing message to recipients |
| 1208 | | that you specify. Bouncing a message uses the <link linkend="sendmail">$sendmail</link> command to send a copy to alternative addresses as if |
| 1209 | | they were the message's original recipients. Forwarding a message, on |
| 1210 | | the other hand, allows you to modify the message before it is resent |
| 1211 | | (for example, by adding your own comments). The default key bindings |
| 1212 | | are shown in <xref linkend="tab-key-fwd"/>. |
| 1213 | | </para> |
| 1214 | | |
| 1215 | | <para> |
| 1216 | | |
| 1217 | | <table id="tab-key-fwd"> |
| 1218 | | <title>Message forwarding/bouncing keys</title> |
| 1219 | | <tgroup cols="3"> |
| 1220 | | <thead> |
| 1221 | | <row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row> |
| 1222 | | </thead> |
| 1223 | | <tbody> |
| 1224 | | <row><entry>f</entry><entry>forward</entry><entry>forward message</entry></row> |
| 1225 | | <row><entry>b</entry><entry>bounce</entry><entry>bounce (remail) message</entry></row> |
| 1226 | | </tbody> |
| 1227 | | </tgroup> |
| 1228 | | </table> |
| 1229 | | |
| | 1243 | that you specify. Bouncing a message sends a verbatim copy of a message |
| | 1244 | to alternative addresses as if they were the message's original recipients. |
| | 1245 | Forwarding a message, on the other hand, allows you to modify the message |
| | 1246 | before it is resent (for example, by adding your own comments). Bouncing |
| | 1247 | is done using the <literal>bounce</literal> function and forwarding |
| | 1248 | using the <literal>forward</literal> command bound to ``b'' and ``f'' |
| | 1249 | respectively. |
| 1230 | 1250 | </para> |
| 1231 | 1251 | |
| … |
… |
|
| 1257 | 1277 | <para> |
| 1258 | 1278 | At times it is desirable to delay sending a message that you have |
| 1259 | | already begun to compose. When the <emphasis>postpone-message</emphasis> function is |
| | 1279 | already begun to compose. When the <literal>postpone-message</literal> function is |
| 1260 | 1280 | used in the <emphasis>compose</emphasis> menu, the body of your message and attachments |
| 1261 | 1281 | are stored in the mailbox specified by the <link linkend="postponed">$postponed</link> variable. This means that you can recall the |
| … |
… |
|
| 1289 | 1309 | <chapter id="configuration"> |
| 1290 | 1310 | <title>Configuration</title> |
| | 1311 | |
| | 1312 | <sect1> |
| | 1313 | <title>Location of initialization files</title> |
| 1291 | 1314 | |
| 1292 | 1315 | <para> |
| … |
… |
|
| 1320 | 1343 | </para> |
| 1321 | 1344 | |
| | 1345 | </sect1> |
| | 1346 | |
| 1322 | 1347 | <sect1 id="muttrc-syntax" xreflabel="Syntax of Initialization Files"> |
| 1323 | 1348 | <title>Syntax of Initialization Files</title> |
| … |
… |
|
| 1422 | 1447 | </para> |
| 1423 | 1448 | |
| | 1449 | <para> |
| | 1450 | All configuration files are expected to be in the current locale as |
| | 1451 | specified by the <link linkend="charset">$charset</link> variable |
| | 1452 | which doesn't have a default value since it's determined by Mutt at startup. |
| | 1453 | If a configuration file is not encoded in the same character set the |
| | 1454 | <link linkend="config-charset">$config_charset</link> |
| | 1455 | variable should be used: all lines starting with the next are recoded |
| | 1456 | from $config_charset to $charset. |
| | 1457 | </para> |
| | 1458 | |
| | 1459 | <para> |
| | 1460 | This mechanism should be avoided if possible as it has the |
| | 1461 | following implications: |
| | 1462 | </para> |
| | 1463 | |
| | 1464 | <para> |
| | 1465 | <itemizedlist> |
| | 1466 | |
| | 1467 | <listitem><para>These variables should be set early in a configuration |
| | 1468 | file with $charset preceeding $config_charset so Mutt |
| | 1469 | know what character set to convert to.</para></listitem> |
| | 1470 | |
| | 1471 | <listitem><para>If $config_charset is set, it should be set |
| | 1472 | in each configuration file because the value is global and <emphasis>not</emphasis> |
| | 1473 | per configuration file.</para></listitem> |
| | 1474 | |
| | 1475 | <listitem><para>Because Mutt first recodes a line before it attempts to parse it, |
| | 1476 | a conversion introducing question marks or other characters as |
| | 1477 | part of errors (unconvertable characters, transliteration) may introduce syntax |
| | 1478 | errors or silently change the meaning of certain tokens (e.g. inserting |
| | 1479 | question marks into regular expressions).</para></listitem> |
| | 1480 | |
| | 1481 | </itemizedlist> |
| | 1482 | </para> |
| | 1483 | |
| 1424 | 1484 | </sect1> |
| 1425 | 1485 | |
| … |
… |
|
| 1557 | 1617 | <para> |
| 1558 | 1618 | In the alias menu, you can select as many aliases as you want with the |
| 1559 | | <emphasis>select-entry</emphasis> key (default: RET), and use the <emphasis>exit</emphasis> key |
| 1560 | | (default: q) to return to the address prompt. |
| | 1619 | <literal>select-entry</literal> key (default: <Return>), and use the |
| | 1620 | <emphasis>exit</emphasis> key (default: q) to return to the address prompt. |
| 1561 | 1621 | </para> |
| 1562 | 1622 | |
| … |
… |
|
| 1805 | 1865 | However, the sorting method is not restored to its previous value when |
| 1806 | 1866 | reading a different mailbox. To specify a <emphasis>default</emphasis> command, use the |
| 1807 | | pattern ``.'': |
| 1808 | | </para> |
| 1809 | | |
| 1810 | | <para> |
| 1811 | | |
| | 1867 | pattern ``.'' before other folder-hooks adjusting a value on a per-folder basis |
| | 1868 | because folder-hooks are evaluated in the order given in the configuration file. |
| | 1869 | The following example will set the <link linkend="sort">sort</link> variable |
| | 1870 | to <literal>date-sent</literal> for all folders but to <literal>threads</literal> |
| | 1871 | for all folders containing ``mutt'' in their name. |
| | 1872 | </para> |
| | 1873 | |
| | 1874 | <para> |
| 1812 | 1875 | <screen> |
| 1813 |