bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#7785: rgrep is broken on woe32


From: Eli Zaretskii
Subject: bug#7785: rgrep is broken on woe32
Date: Thu, 06 Jan 2011 11:20:27 -0500

> Date: Thu, 6 Jan 2011 10:46:58 -0500
> From: Sam Steingold <address@hidden>
> Cc: address@hidden, address@hidden
> 
> of PATH globally:
> 
> (getenv "PATH")
> "c:\\gnu\\gnuwin32\\bin;C:\\WINDOWS\\system32;C:\\WINDOWS;C:\\WINDOWS\\System32\\Wbem;C:\\gnu\\clisp-2.49;C:\\Program
> Files\\TortoiseSVN\\bin;c:\\gnu\\cygwin\\bin;d:\\bin;C:\\Program Files
> (x86)\\TortoiseHg\\;C:\\Program Files
> (x86)\\Bazaar;C:\\gnu\\GnuTLS-2.10.1\\bin"
> 
> find . "(" -path "*/SCCS" -o -path "*/RCS"...-o -name "*.pyo" ")"
> -prune -o  -type f "(" -iname "*" -o -iname ".*" ")" -print0 | 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:        bundle ASDF2 as a module
> ./src/clisp/current/src/ChangeLog:513:        * Makefile.devel (update-asdf):
> new .PHONY target
> ./src/clisp/current/src/ChangeLog:515:        * modules/asdf: add (based on 
> asdf 2.008)
> ./src/clisp/current/src/ChangeLog:516:        * makemake.in, unix/INSTALL:
> mention asdf in the docs
> ./src/clisp/current/src/ChangeLog:590:        (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?

> sort of works, except these bugs in output:
> 1. "xargs: grep: No such file or directory"
> 2. "grep: ./src/clisp/c: No such file or directory"
> 3. "find: write error: Invalid argument"

The last one is simply a consequence of the fact that xargs exits
prematurely (due to the other errors) and the pipe is closed on the
reader side, which makes the writer (find) unhappy.  But the other 2
errors are puzzling...





reply via email to

[Prev in Thread] Current Thread [Next in Thread]