Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: To/Cc address uniquification
Date: Tue, 31 Aug 2010 00:31:41 +0200	[thread overview]
Message-ID: <m3d3szhgvm.fsf@quimbies.gnus.org> (raw)

That should be a word.

A very common situation at work is that I've misconfigured the MTA on my
machine, so messages from me to

  To: cvs

is expanded by the MTA to

  To: cvs@beatriz.netfonds.no

instead of cvs@netfonds.no.  That, in itself, is OK, but then somebody
responds to it and somehow both cvs@beatriz.netfonds.no and
cvs@netfonds.no get in the To/Cc headers, and then everybody gets two of
everything and I have to edit the headers and AAARGH.

Now, sensible people might suggest that I just fix the configuration on
my MTA, but, man!  That's boring.

So I want some functionality in Message that would root out these
obvious duplicates.  But I want it to be general.

Here's what I envision:

(setq message-uniquifications
      '(("\\([^@]+\\)@netfonds.no" "\\1@.*\\.netfonds.no")
      ;; Meaning that if you have foo@netfonds.no in the recipient list,
      ;; then all instances of foo@.*.netfonds.no should be removed.
        ("bugzilla@" ".*")
      ;; Meaning that if bugzilla is in the recipient list, then remove
      ;; all the other addresses.
      ("\\([^@]+\\)@\\(.*\\)$" "\\1@.*\\.\\2")
      ;; This would be a general rule that most people might want...
      ))

Doesn't that sound slightly useful?

And there's the \1 literal string expansion thing again that we were
talking about earlier.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




             reply	other threads:[~2010-08-30 22:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30 22:31 Lars Magne Ingebrigtsen [this message]
2010-08-31  8:13 ` Steinar Bang
2010-08-31 14:39 ` Lars Magne Ingebrigtsen
2010-08-31 18:33 ` Ted Zlatanov
2010-08-31 18:41   ` Lars Magne Ingebrigtsen

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=m3d3szhgvm.fsf@quimbies.gnus.org \
    --to=larsi@gnus.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).