[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#29680: another grep-find anomalous behaviour
From: |
Eli Zaretskii |
Subject: |
bug#29680: another grep-find anomalous behaviour |
Date: |
Mon, 18 Dec 2017 18:21:21 +0200 |
> Cc: 29680@debbugs.gnu.org
> From: Donald H Locker <dhlocker@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.
- bug#29680: 24.5; find-grep not finding a file or missing the grep, Donald H Locker, 2017/12/12
- bug#29680: another grep-find anomalous behaviour, Donald H Locker, 2017/12/15
- bug#29680: another grep-find anomalous behaviour, Eli Zaretskii, 2017/12/15
- bug#29680: another grep-find anomalous behaviour, Eli Zaretskii, 2017/12/15
- bug#29680: another grep-find anomalous behaviour, Donald H Locker, 2017/12/15
- bug#29680: another grep-find anomalous behaviour, Eli Zaretskii, 2017/12/15
- bug#29680: another grep-find anomalous behaviour, Donald H Locker, 2017/12/18
- bug#29680: another grep-find anomalous behaviour,
Eli Zaretskii <=
- bug#29680: another grep-find anomalous behaviour, Donald H Locker, 2017/12/18