unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sam Steingold <sds@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, 7785@debbugs.gnu.org
Subject: bug#7785: rgrep is broken on woe32
Date: Wed, 5 Jan 2011 15:28:48 -0500	[thread overview]
Message-ID: <AANLkTikCjOdX3J15wqPANNThyTx5jUkT_gTDnVBnMPK-@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikDRQpJTq4rMLdp6UFMEXLsrfY4z9rn6OZ3wWiU@mail.gmail.com>

when I edit the command line manually so that it is shorter than 1024 chars,
the error message becomes extra bizarre:



-*- mode: grep; default-directory: "d:/.../" -*-
Grep started at Wed Jan 05 15:27:21

c:/gnu/cygwin/bin/find . \( -path  -o -path \*/attic -o -path \*/junk
-o -path \*/SCCS -o -path \*/RCS -o -path \*/CVS -o -path \*/MCVS -o
-path \*/.svn -o -path \*/.git -o -path \*/.hg -o -path \*/.bzr -o
-path \*/_MTN -o -path \*/_darcs -o -path \*/\{arch\} \) -prune -o \(
-name .\#\* -o -name \*.bc -o -name \*.exe -o -name \*.cmxa -o -name
\*.cmx -o -name \*.cmo -o -name \*.cmi -o -name \*.cma -o -name
\*.spit -o -name \*.spot -o -name \*.omc -o -name \*.data -o -name
\*.tp -o -name \*.vr -o -name \*.cps -o -name \*.fns -o -name \*.kys
-o -name \*.pgs -o -name \*.tps -o -name \*.vrs -o -name \*.pyc -o
-name \*.pyo \) -prune -o  -type f \( -iname \*.cc -o -iname
\*.\[ch\]xx -o -iname \*.\[ch\]pp -o -iname \*.\[CHh\] -o -iname \*.CC
-o -iname \*.HH -o -iname \*.\[ch\]\+\+ \) -print0 | xargs -0 -e grep
-i -nH gettempdir
'c:' is not recognized as an internal or external command,
operable program or batch file.

Grep exited abnormally with code 255 at Wed Jan 05 15:27:21




-- 
Sam Steingold <http://sds.podval.org>





  reply	other threads:[~2011-01-05 20:28 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 [this message]
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
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

  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=AANLkTikCjOdX3J15wqPANNThyTx5jUkT_gTDnVBnMPK-@mail.gmail.com \
    --to=sds@gnu.org \
    --cc=7785@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=ofv@wanadoo.es \
    /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).