From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-25 10597c9: Don't use 'find-program'
Date: Wed, 20 Apr 2016 22:27:31 +0300 [thread overview]
Message-ID: <26f2840a-f6fb-770b-d7ae-5757123b7bd9@yandex.ru> (raw)
In-Reply-To: <83poto9lu0.fsf@gnu.org>
On 04/17/2016 08:39 PM, Eli Zaretskii wrote:
> But since you asked: 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.
>
> Basically, imagine a system with several different ports of 'find',
> each port with its own advantages and bugs.
One way to handle this would be to keep find-program as a user option,
but add a few specialized ones which would default to the former's value.
next prev parent reply other threads:[~2016-04-20 19:27 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
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 [this message]
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=26f2840a-f6fb-770b-d7ae-5757123b7bd9@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--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).