From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: saving copies of the messages sent in Gnus
Date: Thu, 02 Feb 2012 10:27:07 +0900 [thread overview]
Message-ID: <b4mmx922ff8.fsf@jpl.org> (raw)
In-Reply-To: <b4m1ure6212.fsf@jpl.org>
Katsumi Yamaoka wrote:
> Lars Magne Ingebrigtsen wrote:
>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>> 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.
>> It's a good idea.
I changed `gnus-gcc-inhibit-gcc-self-when-resending' into:
,----
| `gnus-gcc-self-resent-messages'
|
| Like `gcc-self' group parameter, only for unmodified resent messages.
| Applied to messages sent by `gnus-summary-resend-message'. Non-nil
| value of this variable takes precedence over any existing Gcc header.
|
| If this is `none', no Gcc copy will be made. If this is t, messages
| resent will be Gcc'd to the current group. If this is a string, it
| specifies a group to which resent messages will be Gcc'd. If this is
| nil, Gcc will be done according to existing Gcc header(s), if any.
| If this is `no-gcc-self', resent messages will be Gcc'd to groups that
| existing Gcc header specifies, except for the current group.
`----
The default value is `no-gcc-self'. Added to 真 Gnus.
next prev parent reply other threads:[~2012-02-02 1:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87sjlw9c9d.fsf@violet.siamics.net>
[not found] ` <87r51fvytj.fsf@marauder.physik.uni-ulm.de>
[not found] ` <b4m7h36lx6n.fsf@jpl.org>
[not found] ` <86aa82vwg4.fsf@gray.siamics.net>
2011-11-25 4:26 ` Katsumi Yamaoka
2012-01-03 21:37 ` Lars Magne Ingebrigtsen
2012-01-05 7:28 ` Katsumi Yamaoka
2012-01-05 10:43 ` Steinar Bang
2012-01-09 19:40 ` Steinar Bang
2012-02-02 1:27 ` Katsumi Yamaoka [this message]
2012-01-07 2:04 ` Ted Zlatanov
2012-01-07 6:21 ` Lars Magne Ingebrigtsen
2012-01-07 13:03 ` Ted Zlatanov
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=b4mmx922ff8.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
/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).