From: Jesper Harder <harder@myrealbox.com>
Subject: Re: "rmail-dont-reply-to-names" doesn't work
Date: Mon, 21 Apr 2003 22:03:39 +0200 [thread overview]
Message-ID: <m3k7dn62jo.fsf@defun.localdomain> (raw)
In-Reply-To: <87ptnf4q3q.fsf@vectra.kalb.ath.cx>
kalb@aya.yale.edu writes:
> Anyway, I checked over the expressions and redid the changes through the
> customization routine, entering
>
> kalb@aya\.yale\.edu|{J,j}\.*\.{K,k}alb\.*artmouth\.{O,o}rg
>
> for both. One odd point is that with my (linux) version of grep you have
> to use the [] brackets while the emacs customization routine complains
> about "junk" unless the {} brackets are used.
Note that regular expressions in Emacs and grep don't use exactly the
same syntax. I think you want a regexp that looks something like this:
"\\(?:kalb@aya\\.yale\\.edu\\|\\(?:[jJ].*[kK]alb.*artmouth\\.[oO]rg\\)\\)"
prev parent reply other threads:[~2003-04-21 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 17:32 kalb
[not found] ` <87of2zzp3q.fsf@virgil.koldfront.dk>
2003-04-21 19:17 ` kalb
2003-04-21 20:03 ` Jesper Harder [this message]
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=m3k7dn62jo.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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).