Why does `find -print0` still escape newlines?












1















I'm confused by this experiment (in Bash):



$ mkdir 'foon'

$ find . -print0 | od -c

0000000   .     .   /   f   o   o      n  

0000012


As you can see, "find" is correctly delimiting the output with null characters, but it escapes the newline in the directory name as "foon" with a backslash "n". Why is it doing this? I told it "-print0" which says "This allows file names that contain newlines ... to be correctly interpreted by programs that process the find output." The escaping should not be necessary, since "" is the delimiter, not "n".






coreutils






share























  • You made a directory called literally foon, with a backslash in its name.

    – Michael Homer
    2 mins ago


















1















I'm confused by this experiment (in Bash):



$ mkdir 'foon'

$ find . -print0 | od -c

0000000   .     .   /   f   o   o      n  

0000012


As you can see, "find" is correctly delimiting the output with null characters, but it escapes the newline in the directory name as "foon" with a backslash "n". Why is it doing this? I told it "-print0" which says "This allows file names that contain newlines ... to be correctly interpreted by programs that process the find output." The escaping should not be necessary, since "" is the delimiter, not "n".






coreutils






share























  • You made a directory called literally foon, with a backslash in its name.

    – Michael Homer
    2 mins ago
















1












1








1








I'm confused by this experiment (in Bash):



$ mkdir 'foon'

$ find . -print0 | od -c

0000000   .     .   /   f   o   o      n  

0000012


As you can see, "find" is correctly delimiting the output with null characters, but it escapes the newline in the directory name as "foon" with a backslash "n". Why is it doing this? I told it "-print0" which says "This allows file names that contain newlines ... to be correctly interpreted by programs that process the find output." The escaping should not be necessary, since "" is the delimiter, not "n".






coreutils






share














I'm confused by this experiment (in Bash):



$ mkdir 'foon'

$ find . -print0 | od -c

0000000   .     .   /   f   o   o      n  

0000012


As you can see, "find" is correctly delimiting the output with null characters, but it escapes the newline in the directory name as "foon" with a backslash "n". Why is it doing this? I told it "-print0" which says "This allows file names that contain newlines ... to be correctly interpreted by programs that process the find output." The escaping should not be necessary, since "" is the delimiter, not "n".






coreutils




coreutils





share












share










share



share










asked 8 mins ago









MetamorphicMetamorphic

27618




27618













  • You made a directory called literally foon, with a backslash in its name.

    – Michael Homer
    2 mins ago





















  • You made a directory called literally foon, with a backslash in its name.

    – Michael Homer
    2 mins ago



















You made a directory called literally foon, with a backslash in its name.

– Michael Homer
2 mins ago







You made a directory called literally foon, with a backslash in its name.

– Michael Homer
2 mins ago












2 Answers
2






active

oldest

votes


















0














The problem is not in find, but in how you're creating this directory. The single quoted string 'foon' is actually a 5-character string, of which the last two are a backslash and a lowercase "n".



Double-quoting it doesn't help either, since double-quoted strings in shell use backslash as an escape character, but don't really interpret any of the C-style backslash sequences.



In a shell such as bash or zsh, etc. (but not dash from Debian/Ubuntu), you can use $"...", which interprets those sequences:



$ mkdir $"foon"


Another option, that should work in any shell compatible with bourne shell is to insert an actual newline:



$ mkdir 'foo

'


That's an actual Return at the end of the first line, only closing the single quote on the second line.





share































    0














    Let's make a directory named foo plus a newline:



    $ mkdir $'foon'


    Now, let's use find:



    $ find .  -print0 | od -c
    
0000000   .     .   /   f   o   o  n  
    
0000011


    n is not escaped.



    The issue is that 'foon' is foo followed by followed by n. We can verify that with:



    $ printf '%s' 'foon' | od -c
    
0000000   f   o   o      n
    
0000005




    share























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "106"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f502460%2fwhy-does-find-print0-still-escape-newlines%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      The problem is not in find, but in how you're creating this directory. The single quoted string 'foon' is actually a 5-character string, of which the last two are a backslash and a lowercase "n".



      Double-quoting it doesn't help either, since double-quoted strings in shell use backslash as an escape character, but don't really interpret any of the C-style backslash sequences.



      In a shell such as bash or zsh, etc. (but not dash from Debian/Ubuntu), you can use $"...", which interprets those sequences:



      $ mkdir $"foon"


      Another option, that should work in any shell compatible with bourne shell is to insert an actual newline:



      $ mkdir 'foo
      
'


      That's an actual Return at the end of the first line, only closing the single quote on the second line.





      share




























        0














        The problem is not in find, but in how you're creating this directory. The single quoted string 'foon' is actually a 5-character string, of which the last two are a backslash and a lowercase "n".



        Double-quoting it doesn't help either, since double-quoted strings in shell use backslash as an escape character, but don't really interpret any of the C-style backslash sequences.



        In a shell such as bash or zsh, etc. (but not dash from Debian/Ubuntu), you can use $"...", which interprets those sequences:



        $ mkdir $"foon"


        Another option, that should work in any shell compatible with bourne shell is to insert an actual newline:



        $ mkdir 'foo
        
'


        That's an actual Return at the end of the first line, only closing the single quote on the second line.





        share


























          0












          0








          0







          The problem is not in find, but in how you're creating this directory. The single quoted string 'foon' is actually a 5-character string, of which the last two are a backslash and a lowercase "n".



          Double-quoting it doesn't help either, since double-quoted strings in shell use backslash as an escape character, but don't really interpret any of the C-style backslash sequences.



          In a shell such as bash or zsh, etc. (but not dash from Debian/Ubuntu), you can use $"...", which interprets those sequences:



          $ mkdir $"foon"


          Another option, that should work in any shell compatible with bourne shell is to insert an actual newline:



          $ mkdir 'foo
          
'


          That's an actual Return at the end of the first line, only closing the single quote on the second line.





          share













          The problem is not in find, but in how you're creating this directory. The single quoted string 'foon' is actually a 5-character string, of which the last two are a backslash and a lowercase "n".



          Double-quoting it doesn't help either, since double-quoted strings in shell use backslash as an escape character, but don't really interpret any of the C-style backslash sequences.



          In a shell such as bash or zsh, etc. (but not dash from Debian/Ubuntu), you can use $"...", which interprets those sequences:



          $ mkdir $"foon"


          Another option, that should work in any shell compatible with bourne shell is to insert an actual newline:



          $ mkdir 'foo
          
'


          That's an actual Return at the end of the first line, only closing the single quote on the second line.






          share











          share


          share










          answered 47 secs ago









          filbrandenfilbranden

          8,71621241




          8,71621241

























              0














              Let's make a directory named foo plus a newline:



              $ mkdir $'foon'


              Now, let's use find:



              $ find .  -print0 | od -c
              
0000000   .     .   /   f   o   o  n  
              
0000011


              n is not escaped.



              The issue is that 'foon' is foo followed by followed by n. We can verify that with:



              $ printf '%s' 'foon' | od -c
              
0000000   f   o   o      n
              
0000005




              share




























                0














                Let's make a directory named foo plus a newline:



                $ mkdir $'foon'


                Now, let's use find:



                $ find .  -print0 | od -c
                
0000000   .     .   /   f   o   o  n  
                
0000011


                n is not escaped.



                The issue is that 'foon' is foo followed by followed by n. We can verify that with:



                $ printf '%s' 'foon' | od -c
                
0000000   f   o   o      n
                
0000005




                share


























                  0












                  0








                  0







                  Let's make a directory named foo plus a newline:



                  $ mkdir $'foon'


                  Now, let's use find:



                  $ find .  -print0 | od -c
                  
0000000   .     .   /   f   o   o  n  
                  
0000011


                  n is not escaped.



                  The issue is that 'foon' is foo followed by followed by n. We can verify that with:



                  $ printf '%s' 'foon' | od -c
                  
0000000   f   o   o      n
                  
0000005




                  share













                  Let's make a directory named foo plus a newline:



                  $ mkdir $'foon'


                  Now, let's use find:



                  $ find .  -print0 | od -c
                  
0000000   .     .   /   f   o   o  n  
                  
0000011


                  n is not escaped.



                  The issue is that 'foon' is foo followed by followed by n. We can verify that with:



                  $ printf '%s' 'foon' | od -c
                  
0000000   f   o   o      n
                  
0000005





                  share











                  share


                  share










                  answered just now









                  John1024John1024

                  47k5110125




                  47k5110125






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Unix & Linux Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid …



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f502460%2fwhy-does-find-print0-still-escape-newlines%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      -

                      Popular posts from this blog

                      Loup dans la culture

                      Image
                      Loups sur une enluminure du Bestiaire d'Aberdeen Le loup est l'animal le plus emblématique de l'histoire de l'Eurasie, il était à l'honneur durant l'Antiquité chez la totalité des anciens peuples européens [ 1 ] . Sommaire 1 Le loup dans la mythologie 2 Les loups dans le folklore 2.1 L'évolution des mentalités 2.2 Le loup dans la psychanalyse 3 Le loup dans les œuvres culturelles 3.1 Le loup dans la littérature 3.1.1 Fables 3.1.2 Poésie 3.1.3 Romans 3.1.4 Littérature jeunesse 3.1.4.1 Quelques titres d'albums contemporains 3.1.5 Bande dessinée 3.2 Le loup à l'écran 3.2.1 Le cinéma et la télévision 3.2.2 Documentaires 3.2.3 Dessins animés 3.2.4 Jeux vidéo 3.3 Le loup en peinture et en sculpture 3.4 Le loup dans les œuvres musicales 4 Le loup et les noms propres 5 Bibliographie 6 Notes et références 7 Voir aussi 7.1 Articles connexes
                      Read more

                      How to solve the problem of ntp “Unable to contact time server” from KDE?

                      Image
                      1 0 I want to set date and time automatically but this error appears when I try to .. I'm using openSUSE, I tried different servers but it didn't work either, help please! It doesn't seem to be a network problem: $ ping pool.ntp.org 64 bytes from 41.78.128.17: icmp_seq=1 ttl=41 time=260 ms To the question of whether ntpd is installed and running: $ ps -C ntpd PID TTY TIME CMD i.e. there's no ntpd process running. $ rpm -qa | grep ntp yast2-ntp-client-3.1.12-1.7.noarch ntp-4.2.6p5-25.2.1.i586 Further information from the comments: $ sudo ntpdate pool.ntp.org 25 Sep 19:41:51 ntpdate[3162]: no server suitable for synchronization found networking kde opensuse ntp ntpd sh
                      Read more

                      ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux

                      Image
                      0 1 I have an ASUS Zenbook UX433,on which ASUS decided to innovate by embedding a Numpad inside the touchpad (see picture 1). Toggling between classic touchpad mode and numpad (also turns the touchpad LEDs on) can be done through the golden button in the top-right corner of the touchpad. However, on my Manjaro arch Linux config, this behavior does not work by default and I can only use the touchpad, no numpad. Has anyone been able to configure the numpad to work on Linux, or have any idea how this could be achieved? EDIT1: I have had a look at the official Windows drivers for the UX433FA TouchPad, but was not able to make anything of it. I tried installing them on Linux using tools like NDISWrapper, but they do not detect the TouchPad/Numpad hardware, and my understanding of drivers is too limited.
                      Read more