From: Dmitry Gutov <dgutov@yandex.ru>
To: Kaushal Modi <kaushal.modi@gmail.com>,
23451@debbugs.gnu.org, drew.adams@oracle.com
Subject: bug#23451: 25.0.93; Clarify the dependency on find/grep for platforms not having those tools
Date: Mon, 29 May 2017 03:07:01 +0300 [thread overview]
Message-ID: <2d674c13-6626-bbd6-e461-c4de963167c4@yandex.ru> (raw)
In-Reply-To: <CAFyQvY1j1LMV7cpjYAEQnhav0c+bZ2ytYyXajEhbMxEFcGtRfg@mail.gmail.com>
On 5/4/16 9:02 PM, Kaushal Modi wrote:
> Another alternative would be (if we want to keep A/Q bindings) that a
> user-error or error be thrown if the correct external dependencies are not
> installed. The user should be let known that they need to install the GNU
> find/grep executables for their platform in order to use those commands.
I've made a step toward this in commit 3bc3dc4: if the status is not
zero and the process made some output, we signal a user error with
whatever output we have.
It's not exactly installation instructions, but it will at least tell
the user that something is wrong.
Previously, I had some problems using this approach, but failed to
document them properly. Let's see if someone manages to find them again.
Hopefully, the only thing missing before was the (/= (point-min)
(point-max)) check.
next prev parent reply other threads:[~2017-05-29 0:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 18:02 bug#23451: 25.0.93; Clarify the dependency on find/grep for platforms not having those tools Kaushal Modi
2017-05-29 0:07 ` Dmitry Gutov [this message]
2017-05-29 1:01 ` Dmitry Gutov
2017-05-29 2:58 ` npostavs
2017-05-29 4:19 ` Eli Zaretskii
2017-05-29 8:28 ` Dmitry Gutov
2017-05-29 8:50 ` Dmitry Gutov
2017-05-29 12:43 ` npostavs
2017-05-29 17:35 ` Eli Zaretskii
2017-05-29 22:00 ` Dmitry Gutov
2017-05-30 5:59 ` Eli Zaretskii
2017-05-30 8:11 ` Eli Zaretskii
2017-10-09 14:30 ` Kaushal Modi
2017-05-29 21:44 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d674c13-6626-bbd6-e461-c4de963167c4@yandex.ru \
--to=dgutov@yandex.ru \
--cc=23451@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=kaushal.modi@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.