On 2017-03-03 Eric Blake <[email protected]> wrote: [...] > So while I'm okay with something like:
> find --trim-leading-dot > printing 'foo' instead of './foo', (and where you can wrap a function or > alias around it to always turn --trim-leading-dot on for your own > interactive dot), I am NOT okay with: > find '' > magically starting to produce successful output where POSIX requires it > to fail. >> But I've not said that you shouldn't remove the "./" or that you can't >> have the feature. You certainly can, you can change the code of GNU find >> any way you like. I will even try to help you do it, time allowing. I >> just won't be including this feature in the released version. > And I'm merely adding that such a change should be done via a > command-line option, not an environment variable. Hello, just to throw in another 2-cents: I think you should be careful about adding *another* option (or worse environment variable) to find. It is already a real complex command with corresponding very long documentation. Adding options has a therefore a generic cost. I personally think that the justification for this option (Afaiui: "./ is ugly.") does not outweigh *this* generic cost. And there is more than that, testsuite and implementation, plus further divergence from other find implementations. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
