# Bazaar merge directive format 2 (Bazaar 0.90) # revision_id: daniel.dehennin@baby-gnu.org-20090707210232-\ # uenjtpeindzsq9bb # target_branch: ../../gnus.head # testament_sha1: d8581219cb5d8a4ad733edd26cec02ee4306555e # timestamp: 2009-07-07 23:04:52 +0200 # source_branch: . # base_revision_id: daniel.dehennin@baby-gnu.org-20090623223900-\ # ydqdsazun1mg75c6 # # Begin patch === modified file 'lisp/gnus-msg.el' --- lisp/gnus-msg.el 2009-01-22 07:02:15 +0000 +++ lisp/gnus-msg.el 2009-07-07 21:02:32 +0000 @@ -1890,7 +1890,10 @@ (setq v (cond ((stringp value) - value) + (if (and (stringp match) + (match-beginning 1)) + (replace-match value nil nil group) + value)) ((or (symbolp value) (functionp value)) (cond ((functionp value) === modified file 'texi/gnus.texi' --- texi/gnus.texi 2009-06-08 22:47:52 +0000 +++ texi/gnus.texi 2009-07-07 21:02:32 +0000 @@ -13393,14 +13393,20 @@ name will be removed. If the attribute name is @code{eval}, the form is evaluated, and the result is thrown away. -The attribute value can be a string (used verbatim), a function with -zero arguments (the return value will be used), a variable (its value -will be used) or a list (it will be @code{eval}ed and the return value -will be used). The functions and sexps are called/@code{eval}ed in the -message buffer that is being set up. The headers of the current article -are available through the @code{message-reply-headers} variable, which -is a vector of the following headers: number subject from date id -references chars lines xref extra. +The attribute value can be a string, a function with zero arguments +(the return value will be used), a variable (its value will be used) +or a list (it will be @code{eval}ed and the return value will be +used). The functions and sexps are called/@code{eval}ed in the +message buffer that is being set up. The headers of the current +article are available through the @code{message-reply-headers} +variable, which is a vector of the following headers: number subject +from date id references chars lines xref extra. + +In the case of a string value, if the @code{match} is a regular +expression, a @samp{replace-match} is proceed on the value to replace +the positional parameters @samp{\@var{n}} by the corresponding +parenthetical matches (see @xref{Replacing the Text that Matched, , +Text Replacement, elisp, The Emacs Lisp Reference Manual}.) @vindex message-reply-headers