 | | From: | Ralf Hildebrandt | | Subject: | Problem when piping a mail to a program | | Date: | 20 Dec 2004 17:06:49 GMT |
|
|
 | When I pipe a mail to a program, this program doesn't see the heeader UNLESS
(!) I previously press "h" in the index view and pipe the mail afterwards.
Which setting controls this?
Right now I'm using 1.5.6+20040907i on Debian/testing
|
|
| | From: | Gary Johnson | | Subject: | Re: Problem when piping a mail to a program | | Date: | Mon, 20 Dec 2004 17:49:20 +0000 (UTC) |
|
|
| Ralf Hildebrandt wrote:
> When I pipe a mail to a program, this program doesn't see the heeader UNLESS
> (!) I previously press "h" in the index view and pipe the mail afterwards.
>
> Which setting controls this?
This behavior is controlled by the 'pipe_decode' and 'weed'
variables. If 'pipe_decode' is unset, 'weed' has no effect. If
'pipe_decode' and 'weed' are set, mutt will removed those headers
from piped messages as specified by your 'ignore' commands.
So you can include all headers in your piped messages by either
unsetting 'pipe_decode' or by unsetting 'weed' before piping, then
setting the variable again afterwards.
HTH,
Gary
|
|
| | From: | John Cordes | | Subject: | Re: Problem when piping a mail to a program | | Date: | Mon, 20 Dec 2004 17:39:03 GMT |
|
|
| Ralf Hildebrandt wrote:
> When I pipe a mail to a program, this program doesn't see the heeader UNLESS
> (!) I previously press "h" in the index view and pipe the mail afterwards.
>
> Which setting controls this?
>
> Right now I'm using 1.5.6+20040907i on Debian/testing
Probably you need to 'set pipe_decode=no', which I thought was
the default. Check in your .muttrc to see if maybe it is set to
'yes'.
--
John Cordes
|
|
| | From: | Ralf Hildebrandt | | Subject: | Re: Problem when piping a mail to a program | | Date: | 20 Dec 2004 17:52:59 GMT |
|
|
| On 2004-12-20, John Cordes wrote:
>> When I pipe a mail to a program, this program doesn't see the header UNLESS
>> (!) I previously press "h" in the index view and pipe the mail afterwards.
>>
>> Which setting controls this?
>>
>> Right now I'm using 1.5.6+20040907i on Debian/testing
>
> Probably you need to 'set pipe_decode=no', which I thought was
> the default. Check in your .muttrc to see if maybe it is set to
> 'yes'.
Nope, no mention of it at all.
I explicitly set it to "no" now. Let's see what happens...
|
|
| | From: | Alan Connor | | Subject: | Re: Problem when piping a mail to a program | | Date: | Mon, 20 Dec 2004 20:06:36 GMT |
|
|
| On 20 Dec 2004 17:52:59 GMT, Ralf Hildebrandt
wrote:
> On 2004-12-20, John Cordes wrote:
>
>>> When I pipe a mail to a program, this program doesn't see the
>>> header UNLESS (!) I previously press "h" in the index view
>>> and pipe the mail afterwards.
>>> Which setting controls this?
>>> Right now I'm using 1.5.6+20040907i on Debian/testing
>>
>> Probably you need to 'set pipe_decode=no', which I thought
>> was the default. Check in your .muttrc to see if maybe it is
>> set to 'yes'.
>
> Nope, no mention of it at all. I explicitly set it to "no"
> now. Let's see what happens...
Don't forget to check you /etc/Muttrc if it exists.
AC
|
|
| | From: | Peter H. Coffin | | Subject: | Re: Problem when piping a mail to a program | | Date: | Mon, 20 Dec 2004 15:42:44 -0600 |
|
|
| On 20 Dec 2004 17:06:49 GMT, Ralf Hildebrandt wrote:
> When I pipe a mail to a program, this program doesn't see the heeader UNLESS
> (!) I previously press "h" in the index view and pipe the mail afterwards.
>
> Which setting controls this?
>
> Right now I'm using 1.5.6+20040907i on Debian/testing
Check for something setting "pipe_decode" to yes, in your config, the
system-wide one, and any of the sourced config inclusions. (Section 6.2
of the big manual describes pipe_decode, and I've verified that it works
as described in my install by piping through a random pager.)
--
_ o
|/)
|
|
