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:
<http://savannah.gnu.org/bugs/?50259>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
