Bash promises to leave incorrectly-formed brace expressions unchanged, and
this is why {} on input yields {} on find's command-line. {} is
incorrectly formed since it doesn't contain a sequence expression or a
comma. But is the same guarantee provided by other shells that also
perform brace expa
On 10/7/23 00:11, Keith Thompson wrote:
As of the latest version of findutils (commit e6e2d10a, Mon 2023-10-02),
the man and info documentation both incorrectly state that {} needs
to be escaped.
In the info documentation, section 3.3.1:
It replaces the string '{}' by the current file name bein
As of the latest version of findutils (commit e6e2d10a, Mon 2023-10-02),
the man and info documentation both incorrectly state that {} needs
to be escaped.
In the info documentation, section 3.3.1:
> It replaces the string '{}' by the current file name being processed
> everywhere it occurs in the
