Changes between Version 3 and Version 4 of MuttFaq/Misc


Ignore:
Timestamp:
Oct 21, 2013 7:00:16 PM (4 years ago)
Author:
MichaelRay
Comment:


mayhem to hold the formatting of the original

Legend:

Unmodified
Added
Removed
Modified
  • MuttFaq/Misc

    v3 v4  
    11=== What is mutt's way to provide "templates" for sending new eMail? ===
    2 One simple way is:
     2One simple way is:[[br]]
    33# start a new eMail,
    44# fill in the template data & body,
    5 # in the compose-menu execute the function "<tt>write-fcc</tt>" and specify your template-folder.
    6 Then, to use a template, apply the "<tt>resend-message</tt>"
    7 function on the desired template and continue to fill out the
    8 missing data & body.
     5# in the compose-menu execute the function "<tt>write-fcc</tt>" and specify your template-folder.[[br]]
     6Then, to use a template, apply the "<tt>resend-message</tt>"[[br]]
     7function on the desired template and continue to fill out the[[br]]
     8missing data & body.[[br]]
    99
    10 You can also read a template from a file with partial headers and
     10You can also read a template from a file with partial headers and[[br]]
    1111body text when you launch mutt with <tt>-H &lt;file&gt;</tt>.
    1212
    1313=== How to make random signatures? ===
    14 You can specify a script that produces random STDOUT, which then
    15 can be used as signature, if you specify
     14You can specify a script that produces random STDOUT, which then[[br]]
     15can be used as signature, if you specify[[br]]
    1616 set signature="script|"
    1717
    1818=== What am I missing when I invoke mutt in batch mode from the cmd-line but it goes interactive? ===
    19 Please read ''carefully'' "<tt>mutt -h</tt>" for the desired arguments (and their ''order''),
    20 and make sure you specify a "body" file to be read from STDIN:
     19Please read ''carefully'' "<tt>mutt -h</tt>" for the desired arguments (and their ''order''),[[br]]
     20and make sure you specify a "body" file to be read from STDIN:[[br]]
    2121 mutt ... < body-file
    2222 cmd | mutt ...
    23 If you want an empty body (when you provide everything else via parameters),
    24 use <tt>/dev/null</tt> instead of the file name.
     23If you want an empty body (when you provide everything else via parameters),[[br]]
     24use <tt>/dev/null</tt> instead of the file name.[[br]]
    2525
    2626=== How can I access the development versions of Mutt? ===
    27 Periodic snapshots are available from ftp://ftp.mutt.org/mutt/devel/
     27Periodic snapshots are available from ftp://ftp.mutt.org/mutt/devel/[[br]]
    2828
    29 The source code is maintained in a Mercurial repository. You can pull your own copy for hacking with
     29The source code is maintained in a Mercurial repository. You can pull your own copy for hacking with[[br]]
    3030
    3131 hg clone http://dev.mutt.org/hg/mutt
    3232
    33 Because of a slight bug in the CVS import process (the default branch is called "HEAD" instead of "default"), you may have to use another command to get the latest version into your working directory after the clone:
     33Because of a slight bug in the CVS import process (the default branch is called "HEAD" instead of "default"),[[br]]
     34you may have to use another command to get the latest version into your working directory after the clone:[[br]]
    3435
    3536 hg update -C HEAD
    3637
    37 Afterwards, `hg pull -u` should keep you up to date.
     38Afterwards, `hg pull -u` should keep you up to date. [[br]]
    3839
    3940=== Where do I find the change log of the differences/ features between releases (stable, dev)? ===
    40 One way is to look at the !ChangeLog file packaged with the source distribution.
    41 However, it's cluttered with lots of code internal noise which probably makes it hard to find the
    42 relevant entries of interest for end-users.
     41One way is to look at the !ChangeLog file packaged with the source distribution.[[br]]
     42However, it's cluttered with lots of code internal noise which probably makes it hard to find the[[br]]
     43relevant entries of interest for end-users.[[br]]
    4344
    4445Therefore you better look at the UPDATING link on the MuttWiki start page for digested changes.
    4546
    4647=== Mutt config is pretty static, how to make it more dynamic even without ScriptSupport? ===
    47 There are still some ways to have the config adapt dynamically,
    48 maybe one of the ConfigTricks does it for you.
     48There are still some ways to have the config adapt dynamically,[[br]]
     49maybe one of the ConfigTricks does it for you.[[br]]
    4950
    5051=== What is the meaning of "mbox", "maildir", "mailbox" and "folder"? ===
    51 These terms are heavily OverloadedNames,
    52 meaning different people use the same terms for different meanings.
     52These terms are heavily OverloadedNames,[[br]]
     53meaning different people use the same terms for different meanings.[[br]]
    5354
    5455=== How to fix error 'Could not copy message'? ===
    55 A general-purpose error message.  Frequently, the reason is that your "$tmpdir" '''becomes''' full when you try to read this message.  Either free some hdd space in that volume, or use another volume. 
     56A general-purpose error message.  Frequently, the reason is that your "$tmpdir" '''becomes''' full when you try to read this message.[[br]]
     57Either free some hdd space in that volume, or use another volume.  [[br]]
    5658
    5759Other causes may be other 'helper' applications, including crytpo tools used to decrypt/verify signed/encrypted mail.  Enabling debug mode (if compiled in) may reveal more helpful error output.
    5860
    5961=== Switching folders is too slow with big folders, how to speed up? ===
    60 Upgrade to 1.5.15 or later (or wait for 1.6 ;), there is header caching included.
    61 Once the cache is built, you should notice an improvement.
    62 Beware to clear/ remove the cache when upgrading or debugging.
     62Upgrade to 1.5.15 or later (or wait for 1.6 ;), there is header caching included.[[br]]
     63Once the cache is built, you should notice an improvement.[[br]]
     64Beware to clear/ remove the cache when upgrading or debugging.[[br]]
    6365
    6466=== How to trigger a script on new mail? ===
    65 This doesn't work before 1.5.xx, so upgrade first.
     67This doesn't work before 1.5.xx, so upgrade first.[[br]]
    6668Then see the example in manual.txt about '''Filters''' and <tt>status_format</tt>.