Hi. Cameron Simpson (12023-07-31): > Yes. For something to run lateryou would need to quote them (to defer their > interpretation). But it won't help with save-hook because it does not, > itself, run a command.
Thanks for confirming what I suspected. > I take it that you can't easily express what you want with a collection of > save hooks in the right order with clever patterns. My main purpose is to group threads in the same mailbox. For that, the external command will have an index of all the message-id in my archives, as people can reply months later. That would be too big. Also, I might want to take a shot at the “gzip classifies better than large language models” thing. > Go the macro, rebinding the "s" keystroke. That way it only fires when you > try to save. The <pipe-message> command can be used to feed the message > content to your script. Some macro which went: > > <pipe-message>your_script.sh >mutt-commands.txt<enter> > <enter-command>source mutt-commands.txt<enter> > <save-message> Thanks, that will save me a little time to figure out the syntax. Jon LaBadie (12023-07-31): > An alternative approach that I'm not sure is possible. > > If during delivery of your mail it is passes through > a filter like "procmail" before hitting your Inbox, > have the filter invoke your hueristics program "guess". Thanks. I had considered something like that. But the guess on a mail received at 13:00 and read at 15:02 might depend on the choice I made on a mail received at 12:00, read at 14:00 and saved at 14:01. (I am considering doing away with the concept of mailboxes entirely in my use case, and instead have a program populate a maildir in a tempfs with mails based on a search criteria, but that will require a little more work.) Regards, -- Nicolas George
signature.asc
Description: PGP signature
