unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Donald H Locker <dhlocker@comcast.net>
Cc: 29680@debbugs.gnu.org
Subject: bug#29680: another grep-find anomalous behaviour
Date: Mon, 18 Dec 2017 18:21:21 +0200	[thread overview]
Message-ID: <83r2rsovlq.fsf@gnu.org> (raw)
In-Reply-To: <8b7fa7fd-9693-e2de-4eb8-84bcbbe4f427@comcast.net> (message from Donald H Locker on Mon, 18 Dec 2017 07:35:22 -0500)

> 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.





  reply	other threads:[~2017-12-18 16:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 20:36 bug#29680: 24.5; find-grep not finding a file or missing the grep Donald H Locker
2017-12-15 12:25 ` bug#29680: another grep-find anomalous behaviour Donald H Locker
2017-12-15 16:49   ` Eli Zaretskii
2017-12-15 16:52     ` Eli Zaretskii
2017-12-15 18:46     ` Donald H Locker
2017-12-15 20:42       ` Eli Zaretskii
2017-12-18 12:35         ` Donald H Locker
2017-12-18 16:21           ` Eli Zaretskii [this message]
2017-12-18 17:18             ` Donald H Locker

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r2rsovlq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=29680@debbugs.gnu.org \
    --cc=dhlocker@comcast.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).