From: David Kastrup <dak@gnu.org>
Subject: Re: multiple search strings in query-replace-regexp
Date: Sat, 07 Oct 2006 09:41:43 +0200 [thread overview]
Message-ID: <85iriwy3m0.fsf@lola.goethe.zz> (raw)
In-Reply-To: <200610070345.k973jLj2011358@powdermilk.math.berkeley.edu> (Ilya Zakharevich's message of "Fri\, 6 Oct 2006 20\:45\:21 -0700 \(PDT\)")
Ilya Zakharevich <nospam-abuse@ilyaz.org> writes:
> [A complimentary Cc of this posting was sent to
> David Kastrup
> <dak@gnu.org>],
I already told you to leave off "complimentary copies" to group
articles: they are a breach of netiquette since they add no valuable
information at all and tend to confuse the recipient into having to
reply multiple times: once in mail, and later, when the mistake has
been noticed, on the group again.
Please stop this nuisance. You can expect that people writing on
Usenet groups are also reading there.
> who wrote in article <85ejtlyuhv.fsf@lola.goethe.zz>:
>> >> C-M-% \(foo\)\|\(rock\)\|metal RET
>> >> \,(cond (\1 "bar") (\2 "house") ("goa")) RET
>> >
>> > To make it useful, one needs a function to count the number of
>> > parentheses in a given regular expression. Is there?
>
>> Uh WHAT? You just type the above stuff. Why would that not be
>> useful?
>
> How many people do you know who would type something like this? :-(
Well, enough for the idiom to be useful. That's why it was invented
and documented.
> And to have a "generally usable" wrapper, one needs a way to
> identify how many paren groups are inside your "foo" and "rock"
> regular expressions.
I can't actually think of a user interface for such a wrapper that
would not really complicate things. In particular if you want to
refer to matched groups in the replacements, it is pretty hard to come
up with anything close to a useful interface.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-10-07 7:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 11:17 multiple search strings in query-replace-regexp Florian Kaufmann
2006-10-06 11:27 ` Malte Spiess
2006-10-06 11:41 ` Florian Kaufmann
2006-10-06 11:51 ` David Kastrup
2006-10-06 21:45 ` Ilya Zakharevich
2006-10-06 22:01 ` David Kastrup
2006-10-07 3:45 ` Ilya Zakharevich
[not found] ` <200610070345.k973jLj2011358@powdermilk.math.berkeley.edu>
2006-10-07 7:41 ` David Kastrup [this message]
2006-10-07 8:57 ` Ilya Zakharevich
2006-10-07 9:11 ` David Kastrup
2006-10-07 22:04 ` Ilya Zakharevich
2006-10-08 13:47 ` Mathias Dahl
2006-10-08 20:55 ` Kim F. Storm
[not found] ` <mailman.7905.1160340972.9609.help-gnu-emacs@gnu.org>
2006-10-12 15:44 ` Mathias Dahl
2006-10-09 6:07 ` Stefan Monnier
2006-10-09 21:53 ` Ilya Zakharevich
2006-10-09 22:21 ` David Kastrup
2006-10-10 3:39 ` Ilya Zakharevich
2006-11-23 19:23 ` Stefan Monnier
2006-10-07 8:20 ` Malte Spiess
2006-10-07 8:40 ` David Kastrup
2006-10-06 12:41 ` Peter Dyballa
[not found] ` <mailman.7806.1160138473.9609.help-gnu-emacs@gnu.org>
2006-10-06 14:14 ` Florian Kaufmann
2006-10-06 15:14 ` David Kastrup
2006-10-06 15:29 ` Florian Kaufmann
2006-10-06 15:47 ` David Kastrup
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85iriwy3m0.fsf@lola.goethe.zz \
--to=dak@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).