On Wed, Sep 25, 2002 at 03:34:50PM +0200, Sven Guckes wrote: : : * Eugene Lee <[EMAIL PROTECTED]> [2002-09-25 12:33]: : > : > The command "send-hook '~h address' command" : > causes Mutt to generate an error "h: not supported : > in this mode" that isn't documented anywhere. : : one more thing to fix in the documentation then.
BTW, I get the same error with send-hook and ~B too. :-) : > How do I get a send-hook to match a pattern within : > a custom header of the current message? : : do you mean "current header" as in "generated with 'my_hdr'"? Nope. That came off as vague. Let me specify. I'm looking at the header "Received:" and trying to find a match within for the pattern "for email_address_pattern". There's no search pattern to look at the "Received:" header (since "Received:" is almost always a multi-line header, the docs don't say whether its other search patterns match multi-line headers). That's where I'm stuck with send-hook and trying to use "~h". So to clarify what I meant above, "current message" is the message that I've currrently selected in index mode, or that I'm currently viewing. And I meant "custom header" to describe a header that's not specified by existing Mutt search patterns. I know message-hook supports ~h, but it only activates when I view the current message. And I don't want to remember to view a message to activate the hook. This wouldn't be a such problem with your standard GUI mail client because selecting the current message also means viewing the current message. But selecting and viewing are two different things according to Mutt, which IMO has unnecessarily complicated the way some hooks work. Sven, thanks for the help! -- Eugene Lee [EMAIL PROTECTED]
