From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Michael Cook <michael@waxrat.com>
Cc: ding@gnus.org
Subject: Re: gnus-summary-resend-message and gcc
Date: Mon, 13 Feb 2012 10:35:54 +0900 [thread overview]
Message-ID: <b4mlio7v7k5.fsf@jpl.org> (raw)
In-Reply-To: <87d39l15pq.fsf@waxrat.com>
Michael Cook wrote:
> When I resend a message (gnus-summary-resend-message), a copy gets
> Gcc'ed into my gcc group. This didn't happen until recently after I
> updated to the latest git code (which I hadn't done in long time).
How do you add the Gcc header for your "gcc group" to a message
to resend?
I tried
(setq message-default-headers "Gcc: nnml:inbox\n")
(setq gnus-gcc-self-resent-messages 'none)
and saw no Gcc took place. Hm.
> Poking around in the code, I see that gnus-summary-resend-message
> adds gnus-agent-possibly-do-gcc to message-sent-hook, and adds
> gnus-summary-resend-message-insert-gcc to message-header-setup-hook.
> gnus-summary-resend-message-insert-gcc heeds
> gnus-gcc-self-resent-messages, which I've set to 'none.
> But gnus-agent-possibly-do-gcc calls gnus-inews-do-gcc, which
> seems to unconditionally do gcc.
But there should be no Gcc header in the message header then if
all is going right. The `message-resend' function modifies or
removes Gcc header according to `gnus-gcc-self-resent-messages',
so you can try this hook to see how the message header is then:
(add-hook 'message-sent-hook
(lambda nil
(copy-to-buffer (get-buffer-create "*testing*")
(point-min) (point-max))))
;; Consult the "*testing*" buffer after resending a message.
> Is something broken here? How do I get gnus-summary-resend-message
> not to do gcc?
next prev parent reply other threads:[~2012-02-13 1:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 20:21 Michael Cook
2012-02-13 1:35 ` Katsumi Yamaoka [this message]
2012-02-13 1:51 ` Katsumi Yamaoka
2012-02-13 18:39 ` Michael Cook
2012-02-13 23:38 ` Katsumi Yamaoka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4mlio7v7k5.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=michael@waxrat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).