[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#24305: 25.1; dired can't replace '\n' in file content (dired-do-find
From: |
Eli Zaretskii |
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 |
> 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).