commit d1023af3d1217c46c3999b5ac1185b8daa3017bc
parent 050ccc25afd5963c698882a1d51ecdba08967395
Author: Simon Tatham <anakin@pobox.com>
Date: Mon, 2 Nov 2015 18:49:52 +0000
Pass the message object to the "reply-to" hook.
This permits the hook to choose a different default mode for different
mailing lists.
Some mailing lists are mostly for discussion among the list members,
while others are used as points of contact for non-list-members to
mail a development team. If you're active on both kinds of mailing
list, you might well want to default to reply-to-list for the former
but reply-to-all for the latter; letting the "reply-to" hook see the
whole message allows its decision to depend on message.list_address.
Diffstat:
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/lib/sup/modes/reply_mode.rb b/lib/sup/modes/reply_mode.rb
@@ -36,6 +36,8 @@ Variables:
[:#{REPLY_TYPES * ', :'}]
The default behavior is equivalent to
([:list, :sender, :recipent] & modes)[0]
+ message: a message object representing the message being replied to
+ (useful values include message.is_list_message? and message.list_address)
Return value:
The reply mode you desire, or nil to use the default behavior.
EOS
@@ -130,7 +132,7 @@ EOS
types = REPLY_TYPES.select { |t| @headers.member?(t) }
@type_selector = HorizontalSelector.new "Reply to:", types, types.map { |x| TYPE_DESCRIPTIONS[x] }
- hook_reply = HookManager.run "reply-to", :modes => types
+ hook_reply = HookManager.run "reply-to", :modes => types, :message => @m
@type_selector.set_to(
if types.include? type_arg