Cc: ding <at> gnus.org
Topic: gnus-summary-resend-message doesn't do Gcc

Ivan Shmakov <oneingray@gmail.com> wrote:
>>>>>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> ...whereas a message to resend is never modified and is already
>> in some group.  Even if it is Gcc'd, Resent- headers don't appear
>> in the article buffer normally.  So, Gcc'ing it does only eat
>> disk, as especially to gcc-self, I think.

> Resent-From: is mentioned in the default gnus-visible-headers,
> not to mention that the latter is trivial to expand to cover any
> of the other headers just as well.

I forgot having excluded Resent headers from my `gnus-visible-headers',
sorry.

> However, my point is that I wish to be able to check my postings
> /as they were sent/.  Certain software, such as some mailing
> lists packages, and the like, are known to (occasionally) mangle
> message's header, body, or both.  There, having a local copy of
> the message sent could be quite a debugging aid.

Gcc to a `sent' group might be useful, I thought afterward.  So,
I tried making `gnus-summary-resend-message' do Gcc.  The new
user option `gnus-gcc-inhibit-gcc-self-when-resending' controls
whether to archive resent articles in the identical group or not.
The default value is t, i.e. inhibit.  A patch is below.