I just noticed the following find applet behavior with regards to wildcards.
I don't think it's a bug as it shows in all find applets, but I'm puzzled
by what is happening.
It seems that when using wildcards and the search results contain a
wildcard match that contains a dash, then find uses the r
On Mon, Feb 5, 2018 at 11:01 AM, enh wrote:
> On Mon, Feb 5, 2018 at 10:43 AM, Rob Landley wrote:
>> On 02/05/2018 11:34 AM, enh wrote:
>>> On Sun, Feb 4, 2018 at 6:14 PM, Rob Landley wrote:
For some reason I thought the next release should happen the middle of
this month, but it turns
On 02/07/2018 05:36 AM, darken wrote:
> I just noticed the following find applet behavior with regards to wildcards.
> I don't think it's a bug as it shows in all find applets, but I'm
> puzzled by what is happening.
>
> It seems that when using wildcards and the search results contain a
> wildcar
This is because the wildcard argument to -iname needs *not* to be
expanded by the shell. It needs to be passed to find as a literal
unexpanded string still containing wildcards. Usually this means
single-quoting.
for example,
find . -iname '*data'
The -iname takes a single argument, and if the
