Bug#565236: "reply-hook . set realname=foo" is executed too late

2010-06-13 Thread Francois Lallart
What is the point of coding hooks if configurations directives can't be set inside ? why would I have to set $realname before reply-hook but setting $from in it works great ? If spaces around "=" _sometimes_ lead to errors, it is a bug. somebody should work on that. as explained in http://wiki.m

Bug#565236: "reply-hook . set realname=foo" is executed too late

2010-06-12 Thread Michelle Konzack
Hello Francois Lallart, There is a problem in yout thinking... "realname" must be set BEFORE the hook becomes active. This is NOT ab bug but a feature. Also the use of arrond the "=" lead sometimes to errors: > reply-hook "~t 1...@home.tld" 'set realname = "set-realname-1"' > reply-hook "~t 2.

Bug#565236: "reply-hook . set realname=foo" is executed too late

2010-06-12 Thread Francois Lallart
I have the same probleme and manage to reproduce it with the code below, reply to test 1, your realname is global realname, then, reply to test 3, your realname is set-realname-1. you can also reply to test 2 then test 1, realname will be set-realname-2 in both cases. dir=$(mktemp -d) || exit $