OK, I have filed a new bug report for this request:
That's not possible. To find the dependencies, we need a trigger,
which is the command itself. So it must be bound.
I meant that the A/Q keys be left unbound if dependencies are not found.
Detecting the situation and signaling an error is probably a good
thing. But I'm not sure it isn't too late for such changes, unless we
want to delay the release.
The current state keeps the Windows user believing that the A/Q action did not find anything, without giving them a hint that they don't have find/grep installed (which would be the case most of the time). If we want the Windows users to use the new implementation, they at least should know that they are missing the executables and that they need to install them manually. IMO this counts like a blocking bug.
> - The requirement to have find/grep installed should also go to backward incompatible changes section in
As Dmitry points out, there is no such section.