unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: sds@gnu.org, 7785-done@debbugs.gnu.org
Subject: bug#7785: rgrep is broken on woe32
Date: Wed, 05 Jan 2011 06:32:58 -0500	[thread overview]
Message-ID: <E1PaRbu-0004yP-LI@fencepost.gnu.org> (raw)
In-Reply-To: <87d3oc17oo.fsf@telefonica.net> (message from Óscar Fuentes on Wed, 05 Jan 2011 02:05:27 +0100)

> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Wed, 05 Jan 2011 02:05:27 +0100
> Cc: 7785@debbugs.gnu.org
> 
> Sam Steingold <sds@gnu.org> writes:
> 
> [snip]
> 
> > /usr/bin/find: invalid expression; I was expecting to find a ')'
> > somewhere but did not see one.
> >
> > Grep finished with no matches found at Tue Jan 04 18:42:28
> > =======================================
> >
> > when I paste the above command into a cygwin shell window, it works
> > just fine (finds what I need).
> > i.e., the () in the command are actually well balanced.
> 
> This looks like the string length restriction in cmdproxy.exe reported
> in
> 
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6674#74
> 
> It was patched, as indicated on the subsequent messages on that thread.

Indeed.  Sam, please use the latest pretest of Emacs 23.3, where this
problem should be fixed.

Closing the bug.





  reply	other threads:[~2011-01-05 11:32 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 [this message]
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
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=E1PaRbu-0004yP-LI@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=7785-done@debbugs.gnu.org \
    --cc=ofv@wanadoo.es \
    --cc=sds@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 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).