[bug #50259] -printf %h behaves weirdly with trailing slashes

Follow-up Comment #7, bug #50259 (project findutils): You're right, I missed the following test case: $ ./find foo// -printf "%p,%h,%f\n" foo//,foo/,foo/ foo//bar,foo/,bar I'll send an update soon. Thanks & have a nice day, Berny _

[bug #50259] -printf %h behaves weirdly with trailing slashes

Follow-up Comment #6, bug #50259 (project findutils): Great! Why limit it to a single trailing slash though? ___ Reply to this item at: ___ Message sen

[bug #50259] -printf %h behaves weirdly with trailing slashes

Follow-up Comment #5, bug #50259 (project findutils): With that patch, you can also have a look on what's changed compared to the installed version with the following snippet: $ mkdir -p foo/bar $ ln -snf foo foolink $ for opt in '' -H -L -P ; do printf "\n=== Differences for option: '

[bug #50259] -printf %h behaves weirdly with trailing slashes

Update of bug #50259 (project findutils): Assigned to:None => berny ___ Follow-up Comment #4: The attached patch fixes this. I also added some more test cases for "%h". Have a nice day,