On Sun, Feb 02, 2014 at 07:37:49PM -0600, David J. Weller-Fahy wrote: > * glphvgacs <[email protected]> [2014-02-02 18:25 -0600]: > > and this to hooks: > > folder-hook to:[email protected] '\ > > set autoedit=yes > > my_hdr To:' > > folder-hook to:[email protected] '\ > > my_hdr To:[email protected]' > > By the way, you may want to check your hooks thoroughly, as a second > address seems to have crept into your response. The second address > includes a trailing single quote ('). The "To:" header I received from > you via the mailing list is below. > #v+ > To: [email protected], [email protected]' > #v- >
appended address, i think, has to do with the order of folder's in my sidebar. so this is a snippet of my config: "drw [ --> ]" "notmuch://?query=folder:drw AND tag:unread NOT from:[email protected]" \ " [ <-- ]" "notmuch://?query=from:[email protected]&limit=512" \ " [ <--> ]" "notmuch://?query=folder:drw AND from:[email protected] AND to:[email protected]" \ " [ .. ]" "notmuch://?query=folder:drw" \ "list [ ycm ]" "notmuch://?query=tag:ycm-users" \ " [ vim ]" "notmuch://?query=tag:vim_use" \ " [ zsh ]" "notmuch://?query=tag:zsh-users" \ " [ mutt ]" "notmuch://?query=to:[email protected]" \ 'folder:' is for filesystem directories here; in particular there is path: .maildir/gmail/drw if i go to this very thread in [ <-- ], _after_ i've gone over [ ycm ] and do <list-reply> from there guess what happens: folder-hook tag:ycm-users "set autoedit=yes; my_hdr To:[email protected] and so i get: To: [email protected], [email protected] i don't know if there is a way to un-hook a hook when one leaves a folder, or rather when a pattern for a hook stops to evaluate TRUE. another guess, this might have something to do with the fact that there is no List-id: in mutt-users's headers (wonder why?) > This may or may not be related to the trailing space I noticed in your > hooks (the trailing space i on the first line of the second folder-hook > in the quoted content above). > > Regards, > -- > dave [ please don't CC me ] (') has to do with me not ever knowing how to wrap a *-hook line. brackets would be nice; something like: foo-hook (pattern) { set bar = baz } shouldn't harm anyone and help with clarity, imho. (hmm, i will check the man after i send this, it might be implemented and then i'm in trouble:) )
