GNU bug report logs - #29680
24.5; find-grep not finding a file or missing the grep

Previous Next

Full log

Message #26 received at 29680 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Donald H Locker <dhlocker <at> comcast.net>
Cc: 29680 <at> debbugs.gnu.org
Subject: Re: bug#29680: another grep-find anomalous behaviour
Date: Mon, 18 Dec 2017 18:21:21 +0200

> Cc: 29680 <at> debbugs.gnu.org
> From: Donald H Locker <dhlocker <at> comcast.net>
> Date: Mon, 18 Dec 2017 07:35:22 -0500
> 
> It would appear that quoting of the '*.log' part of the command is at 
> fault.  Changing the line from
> 
>    -name '*.log'
> to
> 
>    -name \\*.log
> 
> allows the find to proceed normally. There are several files with .log 
> extensions in the directory from which the find-grep fails.

Makes sense.

It's probably some subtle snafu with command-line quoting.  Were the
'qoutes' typed by you, or did Emacs produce them?

In any case, if you can spot where this quoting goes wrong, please
tell the details.  The combination of a native Windows Emacs and
Cygwin shell/utilities is relatively less well tested and has
subtleties, so I'm not surprised to hear about such problems.

Previous Next

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