GNU bug report logs - #24305
25.1; dired can't replace '\n' in file content (dired-do-find-regexp-and-replace)

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Tino Calancha <tino.calancha <at> gmail.com>
Cc: mc.maxcanal <at> gmail.com, dgutov <at> yandex.ru, 24305 <at> debbugs.gnu.org
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 <at> gmail.com>
> Date: Thu, 25 Aug 2016 14:35:52 +0900 (JST)
> Cc: mc.maxcanal <at> gmail.com, dgutov <at> yandex.ru, tino.calancha <at> 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).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.