Attachment saving and piping: what of the headers?
Well, just when I thought I'd never need to ask a question here again :-) I started writing a script which will run as a sink of from the attachment view. I spent some minutes to make the script correctly (I thought) skip over the MIME headers, and only start the real processing after the empty line that separates the headers and the body. Then I saved a test attachment to a file. I tried both a straight save, and a pipe to a cat command. In either case, no headers are present, and neither is the separator line; the file just contains the body and that's that. I am confused. Is there a way to save a MIME part in mutt that includes the headers? FWIW, pipe_decode is unset. -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. Do obvious transformation on domain to reply privately _only_ on Usenet.
Re: Attachment saving and piping: what of the headers?
On 10.07.17 14:29, Ian Zimmerman wrote: > I tried both a straight save, and a pipe to a cat command. In either > case, no headers are present, and neither is the separator line; the > file just contains the body and that's that. Curious. Here, a "| cat > /tmp/fred" produced a copy of your post, complete with 80 lines of headers. That's with pipe_decode unset, and Mutt 1.8.0 (2017-02-23). > I am confused. Is there a way to save a MIME part in mutt that includes > the headers? > > FWIW, pipe_decode is unset. Strange indeed. In similar circumstances, I'd do a :set nopipe_decode, for emphasis. If a coffee and a break doesn't help with the gremlins, then a new mutt version? Erik
Re: Attachment saving and piping: what of the headers?
On 2017-07-11 13:05, Erik Christiansen wrote: > Curious. Here, a "| cat > /tmp/fred" produced a copy of your post, > complete with 80 lines of headers. That's with pipe_decode unset, and > Mutt 1.8.0 (2017-02-23). But that is not what I'm writing about. I'm just trying to save a single attachment from the attachment list. I expected the MIME headers (like Content-Type) to be prepended. It's not a big deal at all, in fact it makes my script simpler. It was just surprising. -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. Do obvious transformation on domain to reply privately _only_ on Usenet.
