[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:18:43 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0


                 Summary: wrong use of quotes in the error message
                 Project: findutils
            Submitted by: ametzler
            Submitted on: Sun 23 Dec 2018 04:18:41 PM CET
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Alexander E. Patrakov
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: None
           Fixed Release: None




this was submitted in the Debian BTS as https://bugs.debian.org/487496
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'


With e.g. en_US.UTF-8 Unicode quotes are used but wouldn't it be better to use
quotes understood by shell? 

I originally thought this was some gettext magic, but the cause is
quoting_style = locale_quoting_style. How about using c_quoting_style instead?


Reply to this item at:


  Message sent via Savannah

reply via email to

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