From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: What's wrong with this regexp?
Date: Wed, 07 Nov 2001 14:39:09 -0500 [thread overview]
Message-ID: <vxkd72us74y.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <k7x2z89k.fsf@hschmi22.userfqdn.rz-online.de> (Frank Schmitt's message of "Wed, 07 Nov 2001 20:32:55 +0100")
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.
BTW, nnmail-split-methods usage is case-insensitive unless you
explicitly turn off case-fold-search in nnmail-split-hook.
next prev parent reply other threads:[~2001-11-07 19:39 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 [this message]
2001-11-07 20:05 ` Frank Schmitt
2001-11-07 20:47 ` Norbert Koch
2001-11-09 9:50 ` Martin Monsorno
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=vxkd72us74y.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.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).