From: Sam Steingold <sds@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 7785@debbugs.gnu.org
Subject: bug#7785: rgrep is broken on woe32
Date: Thu, 6 Jan 2011 15:55:40 -0500 [thread overview]
Message-ID: <AANLkTi=OgdTmDNE_m0H++B5EbewaEFRspT3WHsns6t0=@mail.gmail.com> (raw)
In-Reply-To: <834o9lna5v.fsf@gnu.org>
On Thu, Jan 6, 2011 at 1:45 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> 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.
when I apply my w32-fns patch, I see this:
-*- mode: grep; default-directory: "~/" -*-
Grep started at Thu Jan 06 15:46:06
c:\gnu\gnuwin32\bin\find . "(" -path -o -path......o -name "*.tps" -o
-name "*.vrs" -o -name "*.pyc" -o -name "*.pyo" ")" -prune -o -type f
"(" -iname "*.[cdfh]" -o -iname "*.lisp" -o -iname "*.tst" -o -iname
"*.m4" -o -iname "*.in" -o -iname "Makefile*" -o -iname "*.xml" ")"
-print0 | c:\gnu\gnuwin32\bin\xargs -0 -e c:\gnu\gnuwin32\bin\grep -i
-nH "asdf"
c:\gnu\gnuwin32\bin\xargs: c:\gnu\gnuwin32\bin\grep: Invalid argument
Grep finished (matches found) at Thu Jan 06 15:46:09
--
Sam Steingold <http://sds.podval.org>
next prev parent reply other threads:[~2011-01-06 20:55 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 23:47 bug#7785: rgrep is broken on woe32 Sam Steingold
2011-01-05 1:05 ` Óscar Fuentes
2011-01-05 11:32 ` Eli Zaretskii
2011-01-05 20:25 ` Sam Steingold
2011-01-05 20:28 ` Sam Steingold
2011-01-05 20:50 ` Óscar Fuentes
2011-01-05 21:20 ` Sam Steingold
2011-01-05 21:26 ` Eli Zaretskii
2011-01-05 21:33 ` Eli Zaretskii
2011-01-05 22:29 ` Óscar Fuentes
2011-01-05 22:43 ` Sam Steingold
2011-01-06 12:09 ` bug#6784: " Eli Zaretskii
2011-01-06 15:25 ` Sam Steingold
2011-01-06 16:07 ` Eli Zaretskii
2011-01-08 21:00 ` bug#6784: " Chong Yidong
2011-01-08 22:13 ` bug#7785: " Laimonas Vėbra
2011-01-09 18:07 ` Eli Zaretskii
2011-01-09 17:59 ` Eli Zaretskii
2011-01-09 19:56 ` Michael Albinus
2011-01-10 20:57 ` Michael Albinus
2011-01-05 21:19 ` Eli Zaretskii
2011-01-05 22:45 ` Sam Steingold
2011-01-05 23:49 ` Sam Steingold
2011-01-05 23:52 ` Sam Steingold
2011-01-06 10:24 ` Eli Zaretskii
2011-01-06 15:17 ` Sam Steingold
2011-01-06 15:46 ` Sam Steingold
2011-01-06 16:20 ` Eli Zaretskii
2011-01-06 17:09 ` Sam Steingold
2011-01-06 18:45 ` Eli Zaretskii
2011-01-06 20:55 ` Sam Steingold [this message]
2011-01-06 21:05 ` Eli Zaretskii
2011-01-06 21:11 ` Sam Steingold
2011-01-07 7:24 ` Eli Zaretskii
2011-01-07 15:16 ` Sam Steingold
2011-01-07 16:24 ` Sam Steingold
2011-01-06 16:02 ` Eli Zaretskii
2011-01-06 16:51 ` Sam Steingold
2011-01-06 18:48 ` Eli Zaretskii
2011-01-06 16:04 ` Sam Steingold
2011-01-06 9:32 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=OgdTmDNE_m0H++B5EbewaEFRspT3WHsns6t0=@mail.gmail.com' \
--to=sds@gnu.org \
--cc=7785@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.