James Youngman wrote: > On Fri, Nov 16, 2012 at 10:33 PM, Paul Eggert <egg...@cs.ucla.edu> wrote: >> On 11/16/12 14:10, Dmitry V. Levin wrote: >>> As I said, my proposal is to introduce a new FTS_ flag that would make >>> fts_open behave as before that change, and use this flag in findutils. >>> I haven't heard yet neither from Jim nor from other gnulib people whether >>> it is acceptable or there is a better way to fix the problem. >> >> I don't recall the details, but if this is the best proposal on >> the table then let's go for it. > > The other obvious alternative is to wrap fts_open in programs that > desire the trimming behaviour. Without looking at the code I'm going > to assume that this was at the time the less convenient alternative, > since if Jim had found that more convenient he'd have used it and not > changed fts.
Hi James, When I made that change to fts, I didn't realize it would render find's output non-compliant (of course), and I thought that the new behavior would be generally preferred. Perhaps I should have known better, after all these years: it seems nearly any time we've stripped trailing slashes at all but the highest levels, we've ended up having to undo it in the long run.
