From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: RE: general perform-replace REPLACEMENTS arg for regexpquery-replacement?
Date: Mon, 17 Nov 2008 17:01:09 -0800 [thread overview]
Message-ID: <000101c94919$250e6440$0ab32382@us.oracle.com> (raw)
In-Reply-To: <873ahq3r0k.fsf@jurta.org>
> > Actually, after sending the mail and realizing that the
> > sequence would always be not just \@ but \@(, I thought
> > (and think) that perhaps simply \( would be
> > better. This is about passing a list. So I'd propose that.
> >
> > C-M-% RET abc RET \("<xyz>" "</xyz>")
> >
> > WDOT?
>
> Then we can perfectly use just the current syntax `\,'
> without inventing a new one, e.g.
>
> C-M-% RET abc RET \,'("<xyz>" "</xyz>")
Have you tried it? That was the first thing I tried.
The problem is that \, converts the sexp that follows it to a string.
> The only place currently preventing this is prin1-to-string that turns
> a list into a string. We could change it to keep the list intact.
Yes, but then you lose the ability to get the current behavior: replace by the
string, "(\"zzz\" \"aaa\")".
IMO, two different syntaxes are needed to separate the two different user
intentions: a sexp that evals to a string "(...)" and a sexp that evals to a
list of strings to pass to `perform-replace'.
For the second case, I think, as I said, that there is no need to provide for a
sexp that evals to the list; it is enough to provide for a literal list. IMO.
next prev parent reply other threads:[~2008-11-18 1:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 18:43 general perform-replace REPLACEMENTS arg for regexp query-replacement? Drew Adams
2008-11-15 22:31 ` general perform-replace REPLACEMENTS arg for regexpquery-replacement? Drew Adams
2008-11-16 22:34 ` Juri Linkov
2008-11-17 1:25 ` Drew Adams
2008-11-17 22:51 ` Juri Linkov
2008-11-18 1:01 ` Drew Adams [this message]
2008-11-18 22:18 ` Juri Linkov
2008-11-18 23:20 ` Drew Adams
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='000101c94919$250e6440$0ab32382@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.