Gnus development mailing list
 help / color / mirror / Atom feed
From: Martin Monsorno <monsorno@gmx.de>
Cc: ding@gnus.org
Subject: Re: What's wrong with this regexp?
Date: Fri, 09 Nov 2001 10:50:41 +0100	[thread overview]
Message-ID: <lrofmcnuha.fsf@loki.exolution.lan> (raw)
In-Reply-To: <vxkd72us74y.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "Wed, 07 Nov 2001 14:39:09 -0500")

Karl Kleinpaste <karl@charcoal.com> writes:

> Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
> > Don't we use the regexp scheme documented under 
>> (x)emacs->Searching and Replacement->Regexp search?
>
> Yes, but it's a matter of the lisp reader's context: You have to
> double most occurrences of `\' in order to get them into a lisp
> expression.  What you type in the minibuffer as "\(a\|b\)" must become
> "\\(a\\|b\\)" when used in a string expression in elisp.
>

I had the same problem a few days ago, and finally found the solution
by searching through some of the "other peoples .gnus-files" on the
net. I suppose, just one little example with "\\(To\\|cc\\)" in the
info file about mail-splitting would help very much.

> BTW, nnmail-split-methods usage is case-insensitive unless you
>explicitly turn off case-fold-search in nnmail-split-hook.
>

This would also be nice to be in that info page.

-- 
Martin Monsorno
mailto:monsorno@gmx.de



  parent reply	other threads:[~2001-11-09  9:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-07 18:48 Frank Schmitt
2001-11-07 18:54 ` Norbert Koch
2001-11-07 19:32   ` Frank Schmitt
2001-11-07 19:39     ` Karl Kleinpaste
2001-11-07 20:05       ` Frank Schmitt
2001-11-07 20:47         ` Norbert Koch
2001-11-09  9:50       ` Martin Monsorno [this message]
2001-12-29 21:37         ` 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=lrofmcnuha.fsf@loki.exolution.lan \
    --to=monsorno@gmx.de \
    --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).