Re: Can't ^C View Selected Attachment prompot
Matt Ackeret <[email protected]>
| Newsgroups | gmane.mail.pine.general |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 27 Oct 2006, Bert Driehuis wrote: > On Fri, 27 Oct 2006, Steven W. Orr wrote: > >> If I receive a spam message, I pipe it through a script I wrote which will >> do spam appropriate things with it. A subsequent message that needs to be >> piped will find that the pipe command that was last used will be >> remembered. >> >> Here's the catch. I run a mailinglist or two and if spam is sent to a >> list, then the message is sent as an attachment to the trap message that >> comes to me. I want to process the spam but the spam is not the whole >> message, but just section 2. So I hit v twice from the index to get to the >> part that is spam and it doesn't remember the last pipe command. >> >> So that leaves me with two questions: 1. Is this description coherent or >> do I need to expand on it? 2. Is anyone reading this to turn it into a bug >> to be fixed in a future release? > > I do the same thing, and I actually think this is a feature. After the first > invocation of the pipe-attachment command it does remember the command to use. (I have rarely used the pipe command but just figured out that he meant what I originally interpreted it as..) It remembers the command when you use the pipe command when viewing an entire message, but it does NOT remember the command when you use the pipe command from the view attachments list. I made /tmp/test and /tmp/test2, which just echoed test and test2, respectively. When I did | /tmp/test while viewing the original message, it would remember that the next time I tried to pipe when viewing the full message. But if I go into the view attachments, it does not remember that I piped to /tmp/test2 It DOES still remember /tmp/test for the full message pipe, so it apparently has separate pipe functionality, but does not cache what the user pipes to in the view attachments screen. _______________________________________________ Pine-info mailing list [email protected] http://mailman1.u.washington.edu/mailman/listinfo/pine-info