From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: mc.maxcanal@gmail.com, 24305@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#24305: 25.1; dired can't replace '\n' in file content (dired-do-find-regexp-and-replace)
Date: Thu, 25 Aug 2016 17:33:42 +0300 [thread overview]
Message-ID: <83mvk0ex4p.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1608251432300.5579@calancha-pc> (message from Tino Calancha on Thu, 25 Aug 2016 14:35:52 +0900 (JST))
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Thu, 25 Aug 2016 14:35:52 +0900 (JST)
> Cc: mc.maxcanal@gmail.com, dgutov@yandex.ru, tino.calancha@gmail.com
>
> As reported in NEWS file, since Emas 25.1 the key 'Q' is bound
> to a new command 'dired-do-find-regexp-and-replace'. The key 'A'
> is also bound to a new command: dired-do-find-regexp.
>
> The old commands use Emacs regexp engine, while the new commands
> use grep: this may cause that regexps which previously
> matched results, with the new commands don't match anymore.
>
> That seems the case in your example: the old command matches '\n', but
> the new one cannot:
The doc string says:
REGEXP should use constructs supported by your local ‘grep’ command.
IOW, the '\n' should be replaced by something Grep supports, like $ or
some such (I don't think I understand the exact use case to give a
100% accurate advice).
In any case, this is a duplicate of bug#23426, which see (well, the
beginning, before the discussion went haywire).
prev parent reply other threads:[~2016-08-25 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 22:17 bug#24305: 25.1; dired can't replace '\n' in file content (dired-do-find-regexp-and-replace) Max Canal
2016-08-25 5:35 ` Tino Calancha
2016-08-25 14:33 ` Eli Zaretskii [this message]
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=83mvk0ex4p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24305@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=mc.maxcanal@gmail.com \
--cc=tino.calancha@gmail.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.
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.