unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 6674@debbugs.gnu.org
Subject: bug#6674: PATCH: fix assignment of grep-find-use-xargs on Windows/MS-DOS
Date: Tue, 20 Jul 2010 14:57:03 +0200	[thread overview]
Message-ID: <AANLkTilrHsgP39uciyGPKk6EPHfO7TtVtUPhRKJ_wTCb@mail.gmail.com> (raw)
In-Reply-To: <878w564xtc.fsf@telefonica.net>

2010/7/20 Óscar Fuentes <ofv@wanadoo.es>:

> On Windows, when find-program points to a GNU-compatible `find'
> executable, grep-find-use-xargs is assigned the symbol 'gnu. The
> consequence of this is that `rgrep' ends building a command that
> contains a pipe: find <args> | xargs -0 grep <args> This ends with
> `find' reporting confusing errors about wrong arguments.

Yes, I get

c:/gnu/bin/find.exe: invalid predicate `-nam'

but the very same command works from the command line. So the right
thing would be to fix how rgrep invokes the command on Windows,
wouldn't it?

    Juanma





  reply	other threads:[~2010-07-20 12:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20  3:49 bug#6674: PATCH: fix assignment of grep-find-use-xargs on Windows/MS-DOS Óscar Fuentes
2010-07-20 12:57 ` Juanma Barranquero [this message]
2010-07-20 13:39   ` Óscar Fuentes
2010-07-20 14:24     ` Óscar Fuentes
2010-07-20 15:18       ` Juanma Barranquero
2010-07-20 16:56       ` Eli Zaretskii
2010-07-20 17:28       ` Eli Zaretskii
2010-07-20 17:42         ` Juanma Barranquero
2010-07-20 19:51         ` Óscar Fuentes
2010-07-20 21:41           ` Eli Zaretskii
2010-07-20 22:18             ` Eli Zaretskii
2010-07-21  0:38               ` Christoph
2010-07-21  1:22                 ` Óscar Fuentes
2010-08-02 10:26           ` Laimonas Vėbra
2010-08-02 15:23             ` Óscar Fuentes
2010-08-02 15:48             ` bug#6674: [PATCH] bug#6674: " Óscar Fuentes
2010-08-02 17:11               ` Andreas Schwab
2010-08-02 17:48               ` bug#6674: [PATCH fixed] " Óscar Fuentes
2010-08-02 19:07                 ` Eli Zaretskii
2010-08-02 19:47                   ` Juanma Barranquero
2010-08-02 19:57                   ` Óscar Fuentes
2010-08-02 20:11                     ` Juanma Barranquero
2010-08-02 20:15                     ` Óscar Fuentes
2010-08-03  2:56                     ` Eli Zaretskii
2010-07-20 16:46 ` bug#6674: PATCH: " Eli Zaretskii
2010-07-20 23:18 ` bug#6674: PATCH: fix assignment of grep-find-use-xargs on Windows Óscar Fuentes
2010-07-21  0:44   ` Christoph
2010-07-21  0:50     ` Juanma Barranquero
2010-07-21  0:57     ` Óscar Fuentes
2010-07-21  4:02     ` Eli Zaretskii
2010-07-21  4:05       ` Christoph
2010-08-02  2:21       ` Christoph
2010-08-02  3:10         ` Eli Zaretskii
2010-08-02  4:03           ` Christoph
2010-08-02 18:02             ` Eli Zaretskii
2010-08-02 20:17 ` bug#6674: Closing bug 6674 Óscar Fuentes

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=AANLkTilrHsgP39uciyGPKk6EPHfO7TtVtUPhRKJ_wTCb@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=6674@debbugs.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).