From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: rgm@gnu.org, emacs-devel@gnu.org
Subject: Re: emacs-25 10597c9: Don't use 'find-program'
Date: Mon, 18 Apr 2016 21:25:55 +0300 [thread overview]
Message-ID: <83fuuiai4s.fsf@gnu.org> (raw)
In-Reply-To: <5714650E.2070008@cs.ucla.edu> (message from Paul Eggert on Sun, 17 Apr 2016 21:39:42 -0700)
> Cc: emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 17 Apr 2016 21:39:42 -0700
>
> Eli Zaretskii wrote:
> > you might have 2 versions of 'find' (under
> > different names), one that is good at invoking programs via -exec, the
> > other that supports the -print0 action.
>
> Is this sort of problem common under MS-Windows?
Yes. Find in particular has all kinds of semi-broken ports lying
around. It's why I needed to do my own port years ago: the best one
in existence then was abysmally slow. My port is much faster, and
generally doesn't lose features, but even it has deficiencies: for
example, the inode is always zero, so -inum doesn't work.
> It doesn't sound plausible in any GNUish or POSIXish system, where
> any find that supports -print0 should also support -exec.
Like I said: I don't expect this customization to be of any use for
GNU/Linux users.
next prev parent reply other threads:[~2016-04-18 18:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160411164301.22548.38008@vcs.savannah.gnu.org>
[not found] ` <E1apevV-0005sL-3G@vcs.savannah.gnu.org>
2016-04-11 21:56 ` emacs-25 10597c9: Don't use 'find-program' Glenn Morris
2016-04-11 22:00 ` Drew Adams
2016-04-12 2:29 ` Eli Zaretskii
2016-04-16 11:57 ` Eli Zaretskii
2016-04-16 17:40 ` Glenn Morris
2016-04-16 18:57 ` Eli Zaretskii
2016-04-17 17:15 ` Glenn Morris
2016-04-17 17:39 ` Eli Zaretskii
2016-04-18 4:39 ` Paul Eggert
2016-04-18 18:25 ` Eli Zaretskii [this message]
2016-04-18 16:10 ` Glenn Morris
2016-04-18 16:16 ` Glenn Morris
2016-04-18 18:47 ` Eli Zaretskii
2016-04-18 16:50 ` Glenn Morris
2016-04-18 18:50 ` Eli Zaretskii
2016-04-20 19:07 ` Glenn Morris
2016-04-20 19:24 ` Eli Zaretskii
2016-04-20 19:30 ` Stefan Monnier
2016-04-20 19:40 ` Eli Zaretskii
2016-04-20 20:08 ` Stefan Monnier
2016-04-20 22:54 ` John Wiegley
2016-04-18 18:45 ` Eli Zaretskii
2016-04-20 19:27 ` Dmitry Gutov
2016-04-20 19:37 ` Eli Zaretskii
2016-04-20 19:59 ` Stefan Monnier
2016-04-20 20:06 ` Dmitry Gutov
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=83fuuiai4s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rgm@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).