Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: another option for gcc-self ?
Date: Thu, 28 Feb 2013 15:34:08 +0100	[thread overview]
Message-ID: <87d2vkpkwv.fsf@gilgamesch.quim.ucm.es> (raw)
In-Reply-To: <878v6b9l8y.fsf@free.fr>

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]

>> "Julien" == Julien Cubizolles <j.cubizolles@free.fr> writes:

   > I'd like to be able to archive a copy of sent messages
   > * in an archive group named according to month-year
   > * and the group I was in.

   > I can do it by setting gnus-message-archive-group (I have a function
   > working) but I'd like to toggle this double-archiving fr certain groups
   > only. Using gcc-self one can leave a copy in the original group but it
   > tromps the setting of gnus-message-archive-group.

   > I can see several solutions :

   > * defining a new custom boolean group-parameter (I don't think that's
   >   easy) used by gnus-message-archive-group
   > * changing gcc-self so that it accepts a function as argument (not easy
   >   either) one could then use gcc-self-val (set by gcc-self) as the
   >   option for gnus-message-archive-group

   > Any other ideas ?

You could use bbdb, I have a bbdb extension which adds a gcc field to
your message, based on the bbdb entry of the recipient, but of course you must
then add such a field to each entry.

Uwe Brauer 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5556 bytes --]

  reply	other threads:[~2013-02-28 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 14:56 Julien Cubizolles
2013-02-28 14:34 ` Uwe Brauer [this message]
2013-03-07 21:27   ` Julien Cubizolles
2013-03-01 23:03 ` Dave Goldberg

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=87d2vkpkwv.fsf@gilgamesch.quim.ucm.es \
    --to=oub@mat.ucm.es \
    --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).