[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Tavian Barnes
Subject: [bug #50259] -printf %h behaves weirdly with trailing slashes
Date: Fri, 10 Feb 2017 14:21:31 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Follow-up Comment #2, bug #50259 (project findutils):

> If the file's name contains no slashes (for example because it was named on
the command line and is in the current working directory), then “%h”
expands to “.”. This prevents “%h/%f” expanding to “/foo”, which
would be surprising and probably not desirable.

This looks to me like the intention was for "%h/%f" to be a valid path to the
file (otherwise, why have the special case at all?).

But I realise that it does exactly document the current behaviour.  Consider
this a feature request then?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]