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

[Andreas Metzler]

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

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

Anyway


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 
`phc/*.tex''.

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:

  <https://savannah.gnu.org/bugs/?55272>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/