Gnus development mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@dcc.unicamp.br>
Cc: ding@gnus.org
Subject: Re: nnmail-split-fancy question
Date: 29 Apr 1999 00:42:28 -0300	[thread overview]
Message-ID: <orvhegt7mj.fsf@lua.lbi.dcc.unicamp.br> (raw)
In-Reply-To: Justin Sheehy's message of "28 Apr 1999 18:29:12 -0400"

On Apr 28, 1999, Justin Sheehy <justin@linus.mitre.org> wrote:

> Alexandre Oliva <oliva@dcc.unicamp.br> writes:

>> The problem is that all messages posted to bug-libtool end up in both
>> libtool and bug-libtool folders :-(

> `nnmail-crosspost' is a variable declared in Lisp.

You didn't read the rest of my message, did you? :-)

I value crossposting very much, but only when appropriate.  The point
is that, if a message was posted *only* to bug-libtool@gnu.org, I
don't want it to appear in my libtool mail group, only in bug-libtool.
But, if a message was posted to bug-libtool *and* libtool@gnu.org, I
want the message in both.

My particular problem is just an instance of a more general problem:
there's no way (that I know of) to match a *complete* e-mail address.
We can only match sub-strings that are a full word (or more than one
word), but I'd like to be able to say that I don't want to match
partial incomplete addresses, or at least to say `this must match a
complete e-mail address'.  Could somebody *please* prove me wrong? :-)

-- 
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
{oliva,Alexandre.Oliva}@dcc.unicamp.br  aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
*** E-mail about software projects will be forwarded to mailing lists



  reply	other threads:[~1999-04-29  3:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-28 17:43 Neil Crellin
1999-04-28 19:04 ` Alexandre Oliva
1999-04-28 22:29   ` Justin Sheehy
1999-04-29  3:42     ` Alexandre Oliva [this message]
1999-04-29  7:51   ` Kai.Grossjohann
1999-04-28 19:58 ` Per Abrahamsen
1999-05-03 19:12   ` Neil Crellin

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=orvhegt7mj.fsf@lua.lbi.dcc.unicamp.br \
    --to=oliva@dcc.unicamp.br \
    --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).