From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#7785: rgrep is broken on woe32 Date: Thu, 06 Jan 2011 20:45:32 +0200 Message-ID: <834o9lna5v.fsf@gnu.org> References: <87d3oc17oo.fsf@telefonica.net> <83ipy3m4jv.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: dough.gmane.org 1294341316 28142 80.91.229.12 (6 Jan 2011 19:15:16 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 6 Jan 2011 19:15:16 +0000 (UTC) Cc: 7785@debbugs.gnu.org To: Sam Steingold Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Jan 06 20:15:09 2011 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PavIg-0000XR-S4 for geb-bug-gnu-emacs@m.gmane.org; Thu, 06 Jan 2011 20:15:07 +0100 Original-Received: from localhost ([127.0.0.1]:46088 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PauyY-000649-Ox for geb-bug-gnu-emacs@m.gmane.org; Thu, 06 Jan 2011 13:54:18 -0500 Original-Received: from [140.186.70.92] (port=59050 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PauyJ-00062C-3K for bug-gnu-emacs@gnu.org; Thu, 06 Jan 2011 13:54:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PauyC-0000z8-6M for bug-gnu-emacs@gnu.org; Thu, 06 Jan 2011 13:53:57 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:43047) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PauyC-0000z4-4r for bug-gnu-emacs@gnu.org; Thu, 06 Jan 2011 13:53:56 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from ) id 1Paujm-0000Zp-7Y; Thu, 06 Jan 2011 13:39:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 06 Jan 2011 18:39:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 7785 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 7785-submit@debbugs.gnu.org id=B7785.12943391012164 (code B ref 7785); Thu, 06 Jan 2011 18:39:02 +0000 Original-Received: (at 7785) by debbugs.gnu.org; 6 Jan 2011 18:38:21 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Pauj6-0000Yr-QF for submit@debbugs.gnu.org; Thu, 06 Jan 2011 13:38:21 -0500 Original-Received: from mtaout20.012.net.il ([80.179.55.166]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Pauj4-0000Ye-1U for 7785@debbugs.gnu.org; Thu, 06 Jan 2011 13:38:19 -0500 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LEM009006FXV500@a-mtaout20.012.net.il> for 7785@debbugs.gnu.org; Thu, 06 Jan 2011 20:45:27 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([77.127.127.157]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LEM009CX6RQVK10@a-mtaout20.012.net.il>; Thu, 06 Jan 2011 20:45:27 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Thu, 06 Jan 2011 13:39:02 -0500 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:43156 Archived-At: > Date: Thu, 6 Jan 2011 12:09:12 -0500 > From: Sam Steingold > Cc: ofv@wanadoo.es, 7785@debbugs.gnu.org >=20 > >> find . "(" -path "*/SCCS" -o -path "*/RCS"...-o -name "*.pyo" ")= " > >> -prune -o =C2=A0-type f "(" -iname "*" -o -iname ".*" ")" -print= 0 | xargs > >> -0 -e grep -i -nH "asdf" > >> xargs: grep: No such file or directory > >> ./src/clisp/current/src/ChangeLog:29: * modules/asdf/asdf.lisp: = update > >> to upstream "2.011" > >> ./src/clisp/current/src/ChangeLog:512: =C2=A0 =C2=A0 =C2=A0 = =C2=A0bundle ASDF2 as a module > >> ./src/clisp/current/src/ChangeLog:513: =C2=A0 =C2=A0 =C2=A0 = =C2=A0* Makefile.devel (update-asdf): > >> new .PHONY target > >> ./src/clisp/current/src/ChangeLog:515: =C2=A0 =C2=A0 =C2=A0 = =C2=A0* modules/asdf: add (based on asdf 2.008) > >> ./src/clisp/current/src/ChangeLog:516: =C2=A0 =C2=A0 =C2=A0 = =C2=A0* makemake.in, unix/INSTALL: > >> mention asdf in the docs > >> ./src/clisp/current/src/ChangeLog:590: =C2=A0 =C2=A0 =C2=A0 = =C2=A0(require): use the above, now > >> one can hook asdf into clisp > >> grep: ./src/clisp/c: No such file or directory > >> find: write error: Invalid argument > > > > Does this command work from the Windows shell, if you tweak PATH = to > > have the gnuwin32 directory be at the beginning? >=20 > yes, the same way. > I started cmd; prepended gnuwin to path, started emacs -Q from the > cmd; got the above in rgrep, then copied the command into the cmd a= nd > got the exact same output there, > EXCEPT that neither emacs nor cmd contain the > "grep: ./src/clisp/c: No such file or directory" So at least this error is somehow related to the fact that you invoke Emacs from the Cygwin bash. Can you see what are the differences in process-environment between the invocations from bash and from cmd? > error (the other two: > "xargs: grep: No such file or directory" > and > "find: write error: Invalid argument" > are present both in emacs and cmd). So this is no longer just an Emacs problem, it seems. What happens if you repeat this experiment, but this time give an explicit absolute file name for each program, find, xargs, and grep? (I'd like to be sure we know what binaries are involved.) To avoid hassles with quoting, please use backslashes in the file names.