On 12/16/2018 4:53 PM, John Ericson wrote:
In GNU bash, -r, turns off special escape code handling. Configs don't have escape codes so it makes sense do this. Without that flag then, valid input stays valid, but some invalid input becomes valid too. So skipping that is unfortunate for GNU bash, but certainly makes sense for whatever odd shell you have.
The question that needs answered is what issue was being resolved by the addition of the -r? The resolution here may need filters based on the build host.
-- Earnie _______________________________________________ config-patches mailing list config-patches@gnu.org https://lists.gnu.org/mailman/listinfo/config-patches
