split file lines by regex delimeter












0















I want to split each line from input file by a non-alphanumeric regex W and print all the split chunks in the output file like so:



Input file:



www.wifi.in.ua

YI-HondBrychka


Output file:



www

wifi

in

ua

YI

HondBrynchka





regular-expression







share|improve this question



























    0















    I want to split each line from input file by a non-alphanumeric regex W and print all the split chunks in the output file like so:



    Input file:



    www.wifi.in.ua
    
YI-HondBrychka


    Output file:



    www
    
wifi
    
in
    
ua
    
YI
    
HondBrynchka





    regular-expression







    share|improve this question

























      0












      0








      0








      I want to split each line from input file by a non-alphanumeric regex W and print all the split chunks in the output file like so:



      Input file:



      www.wifi.in.ua
      
YI-HondBrychka


      Output file:



      www
      
wifi
      
in
      
ua
      
YI
      
HondBrynchka





      regular-expression







      share|improve this question














      I want to split each line from input file by a non-alphanumeric regex W and print all the split chunks in the output file like so:



      Input file:



      www.wifi.in.ua
      
YI-HondBrychka


      Output file:



      www
      
wifi
      
in
      
ua
      
YI
      
HondBrynchka





      regular-expression




      regular-expression






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 7 hours ago









      dizczadizcza

      103




      103






















          2 Answers
          2






          active

          oldest

          votes


















          1














          Try using the -o flag, to only print matching strings, e.g.



          $ cat <<HEREDOC | grep -Po 'w+'
          
www.wifi.in.ua
          
YI-HondBrychka
          
HEREDOC
          

          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka





          share|improve this answer
























          • Did you mean grep -Po 'w+' HEREDOC? This works, thank you.

            – dizcza
            7 hours ago











          • No, I meant what I wrote there - it works for me if I copy-paste it. In practice, I imagine you would use a file instead of a heredoc string, and it would look like grep -Po 'w+' /path/to/file.

            – igal
            6 hours ago











          • Substituting HEREDOC for path to file, cat <<HEREDOC | grep -Po 'w+' doesn't work for me while cat HEREDOC | grep -Po 'w+' (or better grep -Po 'w+' HEREDOC) works fine.

            – dizcza
            6 hours ago











          • It sounds to me like you're confused about what a heredoc is - it's not supposed to represent a file path. You can read more about "here documents" in the Bash manual: gnu.org/software/bash/manual/bashref.html#Here-Documents

            – igal
            6 hours ago











          • Oh, I see, I didn't know that. Thank you.

            – dizcza
            6 hours ago



















          0














          Replacing all matches of W with newlines, using Perl (from which the W expression originated):



          $ perl -pe '$_ =~ s/W/n/g' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          Or, more in line with the actual wording of the question:



          $ perl -pe '$_ = join("n", split(/W/)) . "n"' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          Expressing the PCRE W as the ERE [^[:alnum:]] and using GNU awk:



          awk -v RS='[^[:alnum:]]' 1 file


          The 1 is short for '{ print }' and this sets the input record separator to any W character. The records are then printed on individual lines.



          Or with GNU sed:



          sed 's/[^[:alnum:]]/n/g' file


          With tr, it becomes



          $ tr -c '[:alnum:]' 'n' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          where -c makes it replace each character that is not an [:alnum:] with a newline.






          share|improve this answer


























          • The last solution has an artifact of empty new lines. Compare tr -c '[:alpha:]' 'n' < HEREDOC with grep -Po '[a-zA-Z]+' HEREDOC if we add "Zhenek_Lebed98" to the input file HEREDOC.

            – dizcza
            6 hours ago











          • @dizcza Add -s to the command line. It will make it squeeze multiple newlines into one. But on the other hand, you do have an empty word between 9 and 8.

            – Kusalananda
            6 hours ago













          • Now it works as well.

            – dizcza
            6 hours ago











          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%2f505512%2fsplit-file-lines-by-regex-delimeter%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









          1














          Try using the -o flag, to only print matching strings, e.g.



          $ cat <<HEREDOC | grep -Po 'w+'
          
www.wifi.in.ua
          
YI-HondBrychka
          
HEREDOC
          

          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka





          share|improve this answer
























          • Did you mean grep -Po 'w+' HEREDOC? This works, thank you.

            – dizcza
            7 hours ago











          • No, I meant what I wrote there - it works for me if I copy-paste it. In practice, I imagine you would use a file instead of a heredoc string, and it would look like grep -Po 'w+' /path/to/file.

            – igal
            6 hours ago











          • Substituting HEREDOC for path to file, cat <<HEREDOC | grep -Po 'w+' doesn't work for me while cat HEREDOC | grep -Po 'w+' (or better grep -Po 'w+' HEREDOC) works fine.

            – dizcza
            6 hours ago











          • It sounds to me like you're confused about what a heredoc is - it's not supposed to represent a file path. You can read more about "here documents" in the Bash manual: gnu.org/software/bash/manual/bashref.html#Here-Documents

            – igal
            6 hours ago











          • Oh, I see, I didn't know that. Thank you.

            – dizcza
            6 hours ago
















          1














          Try using the -o flag, to only print matching strings, e.g.



          $ cat <<HEREDOC | grep -Po 'w+'
          
www.wifi.in.ua
          
YI-HondBrychka
          
HEREDOC
          

          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka





          share|improve this answer
























          • Did you mean grep -Po 'w+' HEREDOC? This works, thank you.

            – dizcza
            7 hours ago











          • No, I meant what I wrote there - it works for me if I copy-paste it. In practice, I imagine you would use a file instead of a heredoc string, and it would look like grep -Po 'w+' /path/to/file.

            – igal
            6 hours ago











          • Substituting HEREDOC for path to file, cat <<HEREDOC | grep -Po 'w+' doesn't work for me while cat HEREDOC | grep -Po 'w+' (or better grep -Po 'w+' HEREDOC) works fine.

            – dizcza
            6 hours ago











          • It sounds to me like you're confused about what a heredoc is - it's not supposed to represent a file path. You can read more about "here documents" in the Bash manual: gnu.org/software/bash/manual/bashref.html#Here-Documents

            – igal
            6 hours ago











          • Oh, I see, I didn't know that. Thank you.

            – dizcza
            6 hours ago














          1












          1








          1







          Try using the -o flag, to only print matching strings, e.g.



          $ cat <<HEREDOC | grep -Po 'w+'
          
www.wifi.in.ua
          
YI-HondBrychka
          
HEREDOC
          

          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka





          share|improve this answer













          Try using the -o flag, to only print matching strings, e.g.



          $ cat <<HEREDOC | grep -Po 'w+'
          
www.wifi.in.ua
          
YI-HondBrychka
          
HEREDOC
          

          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 7 hours ago









          igaligal

          5,7061535




          5,7061535













          • Did you mean grep -Po 'w+' HEREDOC? This works, thank you.

            – dizcza
            7 hours ago











          • No, I meant what I wrote there - it works for me if I copy-paste it. In practice, I imagine you would use a file instead of a heredoc string, and it would look like grep -Po 'w+' /path/to/file.

            – igal
            6 hours ago











          • Substituting HEREDOC for path to file, cat <<HEREDOC | grep -Po 'w+' doesn't work for me while cat HEREDOC | grep -Po 'w+' (or better grep -Po 'w+' HEREDOC) works fine.

            – dizcza
            6 hours ago











          • It sounds to me like you're confused about what a heredoc is - it's not supposed to represent a file path. You can read more about "here documents" in the Bash manual: gnu.org/software/bash/manual/bashref.html#Here-Documents

            – igal
            6 hours ago











          • Oh, I see, I didn't know that. Thank you.

            – dizcza
            6 hours ago



















          • Did you mean grep -Po 'w+' HEREDOC? This works, thank you.

            – dizcza
            7 hours ago











          • No, I meant what I wrote there - it works for me if I copy-paste it. In practice, I imagine you would use a file instead of a heredoc string, and it would look like grep -Po 'w+' /path/to/file.

            – igal
            6 hours ago











          • Substituting HEREDOC for path to file, cat <<HEREDOC | grep -Po 'w+' doesn't work for me while cat HEREDOC | grep -Po 'w+' (or better grep -Po 'w+' HEREDOC) works fine.

            – dizcza
            6 hours ago











          • It sounds to me like you're confused about what a heredoc is - it's not supposed to represent a file path. You can read more about "here documents" in the Bash manual: gnu.org/software/bash/manual/bashref.html#Here-Documents

            – igal
            6 hours ago











          • Oh, I see, I didn't know that. Thank you.

            – dizcza
            6 hours ago

















          Did you mean grep -Po 'w+' HEREDOC? This works, thank you.

          – dizcza
          7 hours ago





          Did you mean grep -Po 'w+' HEREDOC? This works, thank you.

          – dizcza
          7 hours ago













          No, I meant what I wrote there - it works for me if I copy-paste it. In practice, I imagine you would use a file instead of a heredoc string, and it would look like grep -Po 'w+' /path/to/file.

          – igal
          6 hours ago





          No, I meant what I wrote there - it works for me if I copy-paste it. In practice, I imagine you would use a file instead of a heredoc string, and it would look like grep -Po 'w+' /path/to/file.

          – igal
          6 hours ago













          Substituting HEREDOC for path to file, cat <<HEREDOC | grep -Po 'w+' doesn't work for me while cat HEREDOC | grep -Po 'w+' (or better grep -Po 'w+' HEREDOC) works fine.

          – dizcza
          6 hours ago





          Substituting HEREDOC for path to file, cat <<HEREDOC | grep -Po 'w+' doesn't work for me while cat HEREDOC | grep -Po 'w+' (or better grep -Po 'w+' HEREDOC) works fine.

          – dizcza
          6 hours ago













          It sounds to me like you're confused about what a heredoc is - it's not supposed to represent a file path. You can read more about "here documents" in the Bash manual: gnu.org/software/bash/manual/bashref.html#Here-Documents

          – igal
          6 hours ago





          It sounds to me like you're confused about what a heredoc is - it's not supposed to represent a file path. You can read more about "here documents" in the Bash manual: gnu.org/software/bash/manual/bashref.html#Here-Documents

          – igal
          6 hours ago













          Oh, I see, I didn't know that. Thank you.

          – dizcza
          6 hours ago





          Oh, I see, I didn't know that. Thank you.

          – dizcza
          6 hours ago













          0














          Replacing all matches of W with newlines, using Perl (from which the W expression originated):



          $ perl -pe '$_ =~ s/W/n/g' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          Or, more in line with the actual wording of the question:



          $ perl -pe '$_ = join("n", split(/W/)) . "n"' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          Expressing the PCRE W as the ERE [^[:alnum:]] and using GNU awk:



          awk -v RS='[^[:alnum:]]' 1 file


          The 1 is short for '{ print }' and this sets the input record separator to any W character. The records are then printed on individual lines.



          Or with GNU sed:



          sed 's/[^[:alnum:]]/n/g' file


          With tr, it becomes



          $ tr -c '[:alnum:]' 'n' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          where -c makes it replace each character that is not an [:alnum:] with a newline.






          share|improve this answer


























          • The last solution has an artifact of empty new lines. Compare tr -c '[:alpha:]' 'n' < HEREDOC with grep -Po '[a-zA-Z]+' HEREDOC if we add "Zhenek_Lebed98" to the input file HEREDOC.

            – dizcza
            6 hours ago











          • @dizcza Add -s to the command line. It will make it squeeze multiple newlines into one. But on the other hand, you do have an empty word between 9 and 8.

            – Kusalananda
            6 hours ago













          • Now it works as well.

            – dizcza
            6 hours ago
















          0














          Replacing all matches of W with newlines, using Perl (from which the W expression originated):



          $ perl -pe '$_ =~ s/W/n/g' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          Or, more in line with the actual wording of the question:



          $ perl -pe '$_ = join("n", split(/W/)) . "n"' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          Expressing the PCRE W as the ERE [^[:alnum:]] and using GNU awk:



          awk -v RS='[^[:alnum:]]' 1 file


          The 1 is short for '{ print }' and this sets the input record separator to any W character. The records are then printed on individual lines.



          Or with GNU sed:



          sed 's/[^[:alnum:]]/n/g' file


          With tr, it becomes



          $ tr -c '[:alnum:]' 'n' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          where -c makes it replace each character that is not an [:alnum:] with a newline.






          share|improve this answer


























          • The last solution has an artifact of empty new lines. Compare tr -c '[:alpha:]' 'n' < HEREDOC with grep -Po '[a-zA-Z]+' HEREDOC if we add "Zhenek_Lebed98" to the input file HEREDOC.

            – dizcza
            6 hours ago











          • @dizcza Add -s to the command line. It will make it squeeze multiple newlines into one. But on the other hand, you do have an empty word between 9 and 8.

            – Kusalananda
            6 hours ago













          • Now it works as well.

            – dizcza
            6 hours ago














          0












          0








          0







          Replacing all matches of W with newlines, using Perl (from which the W expression originated):



          $ perl -pe '$_ =~ s/W/n/g' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          Or, more in line with the actual wording of the question:



          $ perl -pe '$_ = join("n", split(/W/)) . "n"' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          Expressing the PCRE W as the ERE [^[:alnum:]] and using GNU awk:



          awk -v RS='[^[:alnum:]]' 1 file


          The 1 is short for '{ print }' and this sets the input record separator to any W character. The records are then printed on individual lines.



          Or with GNU sed:



          sed 's/[^[:alnum:]]/n/g' file


          With tr, it becomes



          $ tr -c '[:alnum:]' 'n' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          where -c makes it replace each character that is not an [:alnum:] with a newline.






          share|improve this answer















          Replacing all matches of W with newlines, using Perl (from which the W expression originated):



          $ perl -pe '$_ =~ s/W/n/g' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          Or, more in line with the actual wording of the question:



          $ perl -pe '$_ = join("n", split(/W/)) . "n"' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          Expressing the PCRE W as the ERE [^[:alnum:]] and using GNU awk:



          awk -v RS='[^[:alnum:]]' 1 file


          The 1 is short for '{ print }' and this sets the input record separator to any W character. The records are then printed on individual lines.



          Or with GNU sed:



          sed 's/[^[:alnum:]]/n/g' file


          With tr, it becomes



          $ tr -c '[:alnum:]' 'n' <file
          
www
          
wifi
          
in
          
ua
          
YI
          
HondBrychka


          where -c makes it replace each character that is not an [:alnum:] with a newline.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 6 hours ago

























          answered 7 hours ago









          KusalanandaKusalananda

          135k17255418




          135k17255418













          • The last solution has an artifact of empty new lines. Compare tr -c '[:alpha:]' 'n' < HEREDOC with grep -Po '[a-zA-Z]+' HEREDOC if we add "Zhenek_Lebed98" to the input file HEREDOC.

            – dizcza
            6 hours ago











          • @dizcza Add -s to the command line. It will make it squeeze multiple newlines into one. But on the other hand, you do have an empty word between 9 and 8.

            – Kusalananda
            6 hours ago













          • Now it works as well.

            – dizcza
            6 hours ago



















          • The last solution has an artifact of empty new lines. Compare tr -c '[:alpha:]' 'n' < HEREDOC with grep -Po '[a-zA-Z]+' HEREDOC if we add "Zhenek_Lebed98" to the input file HEREDOC.

            – dizcza
            6 hours ago











          • @dizcza Add -s to the command line. It will make it squeeze multiple newlines into one. But on the other hand, you do have an empty word between 9 and 8.

            – Kusalananda
            6 hours ago













          • Now it works as well.

            – dizcza
            6 hours ago

















          The last solution has an artifact of empty new lines. Compare tr -c '[:alpha:]' 'n' < HEREDOC with grep -Po '[a-zA-Z]+' HEREDOC if we add "Zhenek_Lebed98" to the input file HEREDOC.

          – dizcza
          6 hours ago





          The last solution has an artifact of empty new lines. Compare tr -c '[:alpha:]' 'n' < HEREDOC with grep -Po '[a-zA-Z]+' HEREDOC if we add "Zhenek_Lebed98" to the input file HEREDOC.

          – dizcza
          6 hours ago













          @dizcza Add -s to the command line. It will make it squeeze multiple newlines into one. But on the other hand, you do have an empty word between 9 and 8.

          – Kusalananda
          6 hours ago







          @dizcza Add -s to the command line. It will make it squeeze multiple newlines into one. But on the other hand, you do have an empty word between 9 and 8.

          – Kusalananda
          6 hours ago















          Now it works as well.

          – dizcza
          6 hours ago





          Now it works as well.

          – dizcza
          6 hours ago


















          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%2f505512%2fsplit-file-lines-by-regex-delimeter%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