From: Dmitry Gutov <dgutov@yandex.ru>
To: Juri Linkov <juri@linkov.net>
Cc: 23484@debbugs.gnu.org
Subject: bug#23484: 25.1.50; undo doesn't work properly in xref-query-replace-in-results
Date: Wed, 11 May 2016 01:03:14 +0300 [thread overview]
Message-ID: <f8f1505f-487c-a67d-0f60-1529e3e642e1@yandex.ru> (raw)
In-Reply-To: <8737pp1tt6.fsf@mail.linkov.net>
On 05/11/2016 12:34 AM, Juri Linkov wrote:
>> - Being able to replace _any_ regexp inside the matches is a feature
>> (though maybe it's not going to be very popular).
>
> Honestly speaking, the ‘.*’ thing is quite confusing.
You're probably right. We could provide a separate command with that
advanced feature (or only use ask for FROM with prefix argument). We
would still have `.*' under the covers in the default case, though.
> More natural syntax is ‘\&’ like is used in e.g.
> ‘occur-read-primary-args’ to collect the entire match.
I'm not sure how \& would be used. And the ability to use \1, \2, etc,
seems to depend on the original regexp. Which is a) currently unknowable
(and the original search may have been performed not using a regexp, but
e.g. by asking a specialized external program), b) not something the
user can choose when the command is e.g. xref-find-references.
next prev parent reply other threads:[~2016-05-10 22:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 19:06 bug#23484: 25.1.50; undo doesn't work properly in xref-query-replace-in-results Dmitry Gutov
2016-05-08 20:19 ` Juri Linkov
2016-05-08 20:26 ` Dmitry Gutov
2016-05-09 20:01 ` Juri Linkov
2016-05-09 20:10 ` Dmitry Gutov
2016-05-09 20:19 ` Dmitry Gutov
2016-05-10 21:34 ` Juri Linkov
2016-05-10 22:03 ` Dmitry Gutov [this message]
2016-05-11 20:48 ` Juri Linkov
2016-05-11 21:11 ` Dmitry Gutov
2016-05-12 20:57 ` Juri Linkov
2016-05-12 22:01 ` Dmitry Gutov
2016-05-14 20:34 ` Juri Linkov
2016-05-14 21:13 ` Dmitry Gutov
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=f8f1505f-487c-a67d-0f60-1529e3e642e1@yandex.ru \
--to=dgutov@yandex.ru \
--cc=23484@debbugs.gnu.org \
--cc=juri@linkov.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).