[Top][All Lists]

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

[bug #55272] wrong use of quotes in the error message

From: Andreas Metzler
Subject: [bug #55272] wrong use of quotes in the error message
Date: Sun, 23 Dec 2018 10:23:02 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0

Follow-up Comment #1, bug #55272 (project findutils):

grrr. savanah swallowed half of the bug-report. Rich-text without preview


find . -name phc/\*.tex

The output is:

find: warning: Unix filenames usually don't contain slashes (though 
pathnames do).  That means that '-name `phc/*.tex'' will probably 
evaluate to false all the time on this system.  You might find the 
'-wholename' test more useful, or perhaps '-samefile'.  Alternatively, 
if you are using GNU grep, you could use 'find ... -print0 | grep -FzZ 

However, the backtick has special meaning in bash, and thus should be 
replaced with a single quote in the second and the last lines of the 
error message. I.e., the error message should suggest to run

find ... -print0 | grep -FzZ 'phc/*.tex'

How about using quoting_style = c_quoting_style?


Reply to this item at:


  Message sent via Savannah

reply via email to

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