On Jan 28, Brian Clark [[EMAIL PROTECTED]] wrote: > When I'm forwarding a message, is there any way to turn off the > inclusion of the complete headers? I've been weeding them myself for far > too long.
You will get the same headers in the forwarded version that you see when viewing the message, IFF you have $forward_decode set. BTW, this is probably the best behaviour, but it's contrary to what the manual currently indicates: Forwarding can be done by including the original message in the new message's body (surrounded by indicating lines) or including it as a MIME attachment, depending on the value of the ``$mime_forward'' variable. Decoding of attachments, like in the pager, can be controlled by the ``$forward_decode'' and ``$mime_forward_decode'' variables, respectively. The desired forwarding format may depend on the content, therefore $mime_forward is a quadoption which, for example, can be set to ``ask-no''. The inclusion of headers is controlled by the current setting of the ``$weed'' variable, unless ``mime_forward'' is set. Thoughts? > I've seen `set forward_weed' in a few .muttrc, and I'm guessing this is > yet another patch? :-) When I include it, I get a parse error when > loading mutt. $forward_weed was an old option that controlled this. It went away in 1.2: - The various weeding options are gone. You have one global option, $weed, now which can be influenced using configuration commands, or using the display-toggle-weed function (this used to be display-headers!). This option is applied when forwarding, replying, or printing messages. Essentially, this means that you have some "WYSIWIG-like" behaviour with respect to message header weeding.
msg23917/pgp00000.pgp
Description: PGP signature
