Display data between two fixed patterns











up vote
-1
down vote

favorite












I've random data coming in from a source into a file. I have to read thru the file and extract only that portion of data which falls between particular patterns.



Example: Let's suppose the file myfile.out looks like this.



info-data
some more info-data
=================================================================
some-data
some-data
some-data
=================================================================

======================= CONFIG PARMS : ==========================
some-data
some-data
some-data
=================================================================

======================= REQUEST PARAMS : ========================
some-data
some-data
some-data
=================================================================

===================== REQUEST RESULTS ===========================
some-data
=================================================================
some-data
some-data
=================================================================
Data-I-Need
Data-I-Need
...
...
...
Data-I-Need
==========================F I N I S H============================

some-info-data


I'm looking for the data that matches this particular pattern only



=================================================================
Data-I-Need
Data-I-Need
...
...
...
Data-I-Need
==========================F I N I S H============================


I did try to look around a bit, like



How to select lines between two marker patterns which may occur multiple times with awk/sed



Bash. How to get multiline text between tags



But the awk, sed solutions given there doesn't seem to work, the commands don't give any errors or outputs.



I tried this



PATTERN1="================================================================="
PATTERN2="==========================F I N I S H============================"
awk -v PAT1="$PATTERN1" -v PAT2="$PATTERN2" 'flag{ if (/PAT2/){printf "%s", buf; flag=0; buf=""} else buf = buf $0 ORS}; /PAT1/{flag=1}' myfile.out


and



PATTERN1="================================================================="
PATTERN2="==========================F I N I S H============================"
awk -v PAT1="$PATTERN1" -v PAT2="$PATTERN2" 'PAT1 {flag=1;next} PAT2 {flag=0} flag { print }' file


Maybe it is due to the pattern? Or I'm doing something wrong.



Script will run on RHEL 6.5.










share|improve this question
























  • Do you need the start and end pattern as well with the data?
    – oliv
    Nov 9 at 13:08










  • @oliv no I don't need that.
    – Marcos
    Nov 9 at 13:47















up vote
-1
down vote

favorite












I've random data coming in from a source into a file. I have to read thru the file and extract only that portion of data which falls between particular patterns.



Example: Let's suppose the file myfile.out looks like this.



info-data
some more info-data
=================================================================
some-data
some-data
some-data
=================================================================

======================= CONFIG PARMS : ==========================
some-data
some-data
some-data
=================================================================

======================= REQUEST PARAMS : ========================
some-data
some-data
some-data
=================================================================

===================== REQUEST RESULTS ===========================
some-data
=================================================================
some-data
some-data
=================================================================
Data-I-Need
Data-I-Need
...
...
...
Data-I-Need
==========================F I N I S H============================

some-info-data


I'm looking for the data that matches this particular pattern only



=================================================================
Data-I-Need
Data-I-Need
...
...
...
Data-I-Need
==========================F I N I S H============================


I did try to look around a bit, like



How to select lines between two marker patterns which may occur multiple times with awk/sed



Bash. How to get multiline text between tags



But the awk, sed solutions given there doesn't seem to work, the commands don't give any errors or outputs.



I tried this



PATTERN1="================================================================="
PATTERN2="==========================F I N I S H============================"
awk -v PAT1="$PATTERN1" -v PAT2="$PATTERN2" 'flag{ if (/PAT2/){printf "%s", buf; flag=0; buf=""} else buf = buf $0 ORS}; /PAT1/{flag=1}' myfile.out


and



PATTERN1="================================================================="
PATTERN2="==========================F I N I S H============================"
awk -v PAT1="$PATTERN1" -v PAT2="$PATTERN2" 'PAT1 {flag=1;next} PAT2 {flag=0} flag { print }' file


Maybe it is due to the pattern? Or I'm doing something wrong.



Script will run on RHEL 6.5.










share|improve this question
























  • Do you need the start and end pattern as well with the data?
    – oliv
    Nov 9 at 13:08










  • @oliv no I don't need that.
    – Marcos
    Nov 9 at 13:47













up vote
-1
down vote

favorite









up vote
-1
down vote

favorite











I've random data coming in from a source into a file. I have to read thru the file and extract only that portion of data which falls between particular patterns.



Example: Let's suppose the file myfile.out looks like this.



info-data
some more info-data
=================================================================
some-data
some-data
some-data
=================================================================

======================= CONFIG PARMS : ==========================
some-data
some-data
some-data
=================================================================

======================= REQUEST PARAMS : ========================
some-data
some-data
some-data
=================================================================

===================== REQUEST RESULTS ===========================
some-data
=================================================================
some-data
some-data
=================================================================
Data-I-Need
Data-I-Need
...
...
...
Data-I-Need
==========================F I N I S H============================

some-info-data


I'm looking for the data that matches this particular pattern only



=================================================================
Data-I-Need
Data-I-Need
...
...
...
Data-I-Need
==========================F I N I S H============================


I did try to look around a bit, like



How to select lines between two marker patterns which may occur multiple times with awk/sed



Bash. How to get multiline text between tags



But the awk, sed solutions given there doesn't seem to work, the commands don't give any errors or outputs.



I tried this



PATTERN1="================================================================="
PATTERN2="==========================F I N I S H============================"
awk -v PAT1="$PATTERN1" -v PAT2="$PATTERN2" 'flag{ if (/PAT2/){printf "%s", buf; flag=0; buf=""} else buf = buf $0 ORS}; /PAT1/{flag=1}' myfile.out


and



PATTERN1="================================================================="
PATTERN2="==========================F I N I S H============================"
awk -v PAT1="$PATTERN1" -v PAT2="$PATTERN2" 'PAT1 {flag=1;next} PAT2 {flag=0} flag { print }' file


Maybe it is due to the pattern? Or I'm doing something wrong.



Script will run on RHEL 6.5.










share|improve this question















I've random data coming in from a source into a file. I have to read thru the file and extract only that portion of data which falls between particular patterns.



Example: Let's suppose the file myfile.out looks like this.



info-data
some more info-data
=================================================================
some-data
some-data
some-data
=================================================================

======================= CONFIG PARMS : ==========================
some-data
some-data
some-data
=================================================================

======================= REQUEST PARAMS : ========================
some-data
some-data
some-data
=================================================================

===================== REQUEST RESULTS ===========================
some-data
=================================================================
some-data
some-data
=================================================================
Data-I-Need
Data-I-Need
...
...
...
Data-I-Need
==========================F I N I S H============================

some-info-data


I'm looking for the data that matches this particular pattern only



=================================================================
Data-I-Need
Data-I-Need
...
...
...
Data-I-Need
==========================F I N I S H============================


I did try to look around a bit, like



How to select lines between two marker patterns which may occur multiple times with awk/sed



Bash. How to get multiline text between tags



But the awk, sed solutions given there doesn't seem to work, the commands don't give any errors or outputs.



I tried this



PATTERN1="================================================================="
PATTERN2="==========================F I N I S H============================"
awk -v PAT1="$PATTERN1" -v PAT2="$PATTERN2" 'flag{ if (/PAT2/){printf "%s", buf; flag=0; buf=""} else buf = buf $0 ORS}; /PAT1/{flag=1}' myfile.out


and



PATTERN1="================================================================="
PATTERN2="==========================F I N I S H============================"
awk -v PAT1="$PATTERN1" -v PAT2="$PATTERN2" 'PAT1 {flag=1;next} PAT2 {flag=0} flag { print }' file


Maybe it is due to the pattern? Or I'm doing something wrong.



Script will run on RHEL 6.5.







shell awk sed






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 9 at 13:54

























asked Nov 9 at 12:53









Marcos

396414




396414












  • Do you need the start and end pattern as well with the data?
    – oliv
    Nov 9 at 13:08










  • @oliv no I don't need that.
    – Marcos
    Nov 9 at 13:47


















  • Do you need the start and end pattern as well with the data?
    – oliv
    Nov 9 at 13:08










  • @oliv no I don't need that.
    – Marcos
    Nov 9 at 13:47
















Do you need the start and end pattern as well with the data?
– oliv
Nov 9 at 13:08




Do you need the start and end pattern as well with the data?
– oliv
Nov 9 at 13:08












@oliv no I don't need that.
– Marcos
Nov 9 at 13:47




@oliv no I don't need that.
– Marcos
Nov 9 at 13:47












4 Answers
4






active

oldest

votes

















up vote
0
down vote



accepted










This might work for you (GNU sed):



sed -r '/^=+$/h;//!H;/^=+F I N I S H=+$/!d;x;s/^[^n]*n|n[^n]*$//g' file


Store a line containing only ='s in the hold space (replacing anything that was there before). Append all other lines to hold space. If the current line is not a line containing ='s followed by F I N I S H followed by ='s, delete it. Otherwise, swap to the hold space, remove the first and last lines and print the remainder.






share|improve this answer




























    up vote
    0
    down vote













    Assuming you only need the data and not the pattern, using GNU awk:



    awk -v RS='n={26,}[ A-Z]*={28,}n' 'RT~/F I N I S H/' file


    The record separator RS is set to match lines with a series of = and some optional uppercase characters inbetween.



    The only statement is check if the record terminator RT (of the current record) has the FINISH keyword in it. If so, awk will print the whole record consisting of multiple lines.






    share|improve this answer























    • thanks...I'll test this
      – Marcos
      Nov 9 at 13:48










    • I realized, the pattern that I gave in question is not rite.... it's F I N I S H and not FINISH.
      – Marcos
      Nov 9 at 14:18










    • @Marcos I updated the answer with the new pattern. (You can change the statement RT~/.../ to match whatever string)
      – oliv
      Nov 9 at 14:29










    • it's not working, but the pattern is rite.
      – Marcos
      Nov 9 at 14:48










    • @Marcos What isn 't working exactly? Are you sure you use GNU awk?
      – oliv
      Nov 9 at 15:07


















    up vote
    0
    down vote













    sed can handle this.




    Assuming you want to keep the header and footer lines -




    $: sed -En '/^=+$/,/^=+F I N I S H=+$/ { /^=+$/ { x; d; }; /^[^=]/ { H; d; }; /^=+F I N I S H=+$/{ H; x; p; q; }; }' infile
    =================================================================
    Data-I-Need
    Data-I-Need
    ...
    ...
    ...
    Data-I-Need
    ==========================F I N I S H============================



    If not, use




    sed -En '/^=+$/,/^=+F I N I S H=+$/ { /^=+$/ { s/.*//g; x; d; }; /^[^=]/ { H; d; }; /^=+F I N I S H=+$/{ x; p; q; }; }' infile


    Note that if you aren't using GNU sed you'll need to insert newlines instead of all those semicolons.



    sed -En '
    /^=+$/,/^=+F I N I S H=+$/ {
    /^=+$/ {
    s/.*//g
    x
    d
    }
    /^[^=]/ {
    H
    d
    }
    /^=+F I N I S H=+$/{
    x
    p
    q
    }
    }' infile

    Data-I-Need
    Data-I-Need
    ...
    ...
    ...
    Data-I-Need



    Breaking it down -




    sed -En '...'


    The -En says to use extended pattern matching (the -E, which I really only used for the +'s), and not to output anything unless specifically asked (the -n).



    /^=+$/,/^=+F I N I S H=+$/ {...}


    says to execute these commands only between lines that are all ='s and lines that are all ='s except for F I N I S H in the middle somewhere. All the stuff between the {}'s will be checked on all lines between those. That does mean from the first =+ line, but that's ok, we handle that inside.



    (a) /^=+$/ { x; d; };
    (b) /^=+$/ { s/.*//g; x; d; };


    (a) says on each of the lines that are all ='s, swap (x) the current line (the "pattern space") with the "hold space", then delete (d) the pattern space. That keeps the current line and deletes whatever you might have accumulated above on false starts. (Remember -n keeps anything from printing till we want it.)



    (b) says erase the current line first, THEN swap and delete. It will still add a newline. Did you want that removed?



    /^[^=]/ { H; d; };


    Both versions use this. On any line that does not start with an =, add it to the hold space (H), then deletes the pattern space (d). The delete always restarts the cycle, reading the next record.



    (a) /^=+F I N I S H=+$/{ H; x; p; q; };
    (b) /^=+F I N I S H=+$/{ x; p; q; };


    On any line with the sentinel F I N I S H string between all ='s, (a) will first append (H) the pattern to the hold space - (b) will not. Both will then swap the pattern and hold spaces (x), print (p) the pattern space (which is now the value accumulated into the hold space), and then delete (d) the pattern space, triggering the next cycle.



    At that point, you will be outside the initial toggle, so unless another row of all ='s happens, you'll skip all the remaining lines. If one does it will again begin to accumulate records, but will not print them unless it hits another F I N I S H record.



    }' infile


    This just closes the script and passes in whatever filename you were using. Note that is is not an in-place edit...



    Hope that helps.






    share|improve this answer























    • this didn't work for me, I'll try to test more on this.
      – Marcos
      Nov 14 at 11:50










    • What did it do?
      – Paul Hodges
      Nov 14 at 14:30


















    up vote
    0
    down vote













    Although there is already a sed solution there, I like sed for its simplicity:



    sed -n '/^==*r*$/,/^==*F I N I S H/{H;/^==*[^F=]/h;${g;p}}' file


    In this sed command we made a range for our commands to be run against. This range starts with a line which begins, contains only and ends to = and then finishes on a line that starts with = and heads to F I N I S H. Now our commands:



    H appends each line immediately to hold space. Then /^==*[^F=]/h executes on other sections' header or footer that it replaces hold space with current pattern space.



    And at the last line we replaces current pattern space with what is in hold space and then print it using ${g;p}. The whole thing outputs this:



    =================================================================
    Data-I-Need
    Data-I-Need
    ...
    ...
    ...
    Data-I-Need
    ==========================F I N I S H============================





    share|improve this answer





















    • I do not need the header and footer lines.
      – Marcos
      Nov 9 at 16:56










    • Then piple results to sed '1d;$d;'
      – revo
      Nov 9 at 18:08










    • for some reason your solution didn't work out, I'll test further to understand why.
      – Marcos
      Nov 14 at 11:49










    • Please elaborate. it didn't work does not describe what the problem is, whether or not you get any result and if yes what is that. However I support @potong's answer. That has a nice idea behind.
      – revo
      Nov 14 at 11:53













    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    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',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2fstackoverflow.com%2fquestions%2f53226074%2fdisplay-data-between-two-fixed-patterns%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    4 Answers
    4






    active

    oldest

    votes








    4 Answers
    4






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote



    accepted










    This might work for you (GNU sed):



    sed -r '/^=+$/h;//!H;/^=+F I N I S H=+$/!d;x;s/^[^n]*n|n[^n]*$//g' file


    Store a line containing only ='s in the hold space (replacing anything that was there before). Append all other lines to hold space. If the current line is not a line containing ='s followed by F I N I S H followed by ='s, delete it. Otherwise, swap to the hold space, remove the first and last lines and print the remainder.






    share|improve this answer

























      up vote
      0
      down vote



      accepted










      This might work for you (GNU sed):



      sed -r '/^=+$/h;//!H;/^=+F I N I S H=+$/!d;x;s/^[^n]*n|n[^n]*$//g' file


      Store a line containing only ='s in the hold space (replacing anything that was there before). Append all other lines to hold space. If the current line is not a line containing ='s followed by F I N I S H followed by ='s, delete it. Otherwise, swap to the hold space, remove the first and last lines and print the remainder.






      share|improve this answer























        up vote
        0
        down vote



        accepted







        up vote
        0
        down vote



        accepted






        This might work for you (GNU sed):



        sed -r '/^=+$/h;//!H;/^=+F I N I S H=+$/!d;x;s/^[^n]*n|n[^n]*$//g' file


        Store a line containing only ='s in the hold space (replacing anything that was there before). Append all other lines to hold space. If the current line is not a line containing ='s followed by F I N I S H followed by ='s, delete it. Otherwise, swap to the hold space, remove the first and last lines and print the remainder.






        share|improve this answer












        This might work for you (GNU sed):



        sed -r '/^=+$/h;//!H;/^=+F I N I S H=+$/!d;x;s/^[^n]*n|n[^n]*$//g' file


        Store a line containing only ='s in the hold space (replacing anything that was there before). Append all other lines to hold space. If the current line is not a line containing ='s followed by F I N I S H followed by ='s, delete it. Otherwise, swap to the hold space, remove the first and last lines and print the remainder.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 10 at 13:26









        potong

        34.8k42960




        34.8k42960
























            up vote
            0
            down vote













            Assuming you only need the data and not the pattern, using GNU awk:



            awk -v RS='n={26,}[ A-Z]*={28,}n' 'RT~/F I N I S H/' file


            The record separator RS is set to match lines with a series of = and some optional uppercase characters inbetween.



            The only statement is check if the record terminator RT (of the current record) has the FINISH keyword in it. If so, awk will print the whole record consisting of multiple lines.






            share|improve this answer























            • thanks...I'll test this
              – Marcos
              Nov 9 at 13:48










            • I realized, the pattern that I gave in question is not rite.... it's F I N I S H and not FINISH.
              – Marcos
              Nov 9 at 14:18










            • @Marcos I updated the answer with the new pattern. (You can change the statement RT~/.../ to match whatever string)
              – oliv
              Nov 9 at 14:29










            • it's not working, but the pattern is rite.
              – Marcos
              Nov 9 at 14:48










            • @Marcos What isn 't working exactly? Are you sure you use GNU awk?
              – oliv
              Nov 9 at 15:07















            up vote
            0
            down vote













            Assuming you only need the data and not the pattern, using GNU awk:



            awk -v RS='n={26,}[ A-Z]*={28,}n' 'RT~/F I N I S H/' file


            The record separator RS is set to match lines with a series of = and some optional uppercase characters inbetween.



            The only statement is check if the record terminator RT (of the current record) has the FINISH keyword in it. If so, awk will print the whole record consisting of multiple lines.






            share|improve this answer























            • thanks...I'll test this
              – Marcos
              Nov 9 at 13:48










            • I realized, the pattern that I gave in question is not rite.... it's F I N I S H and not FINISH.
              – Marcos
              Nov 9 at 14:18










            • @Marcos I updated the answer with the new pattern. (You can change the statement RT~/.../ to match whatever string)
              – oliv
              Nov 9 at 14:29










            • it's not working, but the pattern is rite.
              – Marcos
              Nov 9 at 14:48










            • @Marcos What isn 't working exactly? Are you sure you use GNU awk?
              – oliv
              Nov 9 at 15:07













            up vote
            0
            down vote










            up vote
            0
            down vote









            Assuming you only need the data and not the pattern, using GNU awk:



            awk -v RS='n={26,}[ A-Z]*={28,}n' 'RT~/F I N I S H/' file


            The record separator RS is set to match lines with a series of = and some optional uppercase characters inbetween.



            The only statement is check if the record terminator RT (of the current record) has the FINISH keyword in it. If so, awk will print the whole record consisting of multiple lines.






            share|improve this answer














            Assuming you only need the data and not the pattern, using GNU awk:



            awk -v RS='n={26,}[ A-Z]*={28,}n' 'RT~/F I N I S H/' file


            The record separator RS is set to match lines with a series of = and some optional uppercase characters inbetween.



            The only statement is check if the record terminator RT (of the current record) has the FINISH keyword in it. If so, awk will print the whole record consisting of multiple lines.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Nov 9 at 14:27

























            answered Nov 9 at 13:13









            oliv

            8,2481130




            8,2481130












            • thanks...I'll test this
              – Marcos
              Nov 9 at 13:48










            • I realized, the pattern that I gave in question is not rite.... it's F I N I S H and not FINISH.
              – Marcos
              Nov 9 at 14:18










            • @Marcos I updated the answer with the new pattern. (You can change the statement RT~/.../ to match whatever string)
              – oliv
              Nov 9 at 14:29










            • it's not working, but the pattern is rite.
              – Marcos
              Nov 9 at 14:48










            • @Marcos What isn 't working exactly? Are you sure you use GNU awk?
              – oliv
              Nov 9 at 15:07


















            • thanks...I'll test this
              – Marcos
              Nov 9 at 13:48










            • I realized, the pattern that I gave in question is not rite.... it's F I N I S H and not FINISH.
              – Marcos
              Nov 9 at 14:18










            • @Marcos I updated the answer with the new pattern. (You can change the statement RT~/.../ to match whatever string)
              – oliv
              Nov 9 at 14:29










            • it's not working, but the pattern is rite.
              – Marcos
              Nov 9 at 14:48










            • @Marcos What isn 't working exactly? Are you sure you use GNU awk?
              – oliv
              Nov 9 at 15:07
















            thanks...I'll test this
            – Marcos
            Nov 9 at 13:48




            thanks...I'll test this
            – Marcos
            Nov 9 at 13:48












            I realized, the pattern that I gave in question is not rite.... it's F I N I S H and not FINISH.
            – Marcos
            Nov 9 at 14:18




            I realized, the pattern that I gave in question is not rite.... it's F I N I S H and not FINISH.
            – Marcos
            Nov 9 at 14:18












            @Marcos I updated the answer with the new pattern. (You can change the statement RT~/.../ to match whatever string)
            – oliv
            Nov 9 at 14:29




            @Marcos I updated the answer with the new pattern. (You can change the statement RT~/.../ to match whatever string)
            – oliv
            Nov 9 at 14:29












            it's not working, but the pattern is rite.
            – Marcos
            Nov 9 at 14:48




            it's not working, but the pattern is rite.
            – Marcos
            Nov 9 at 14:48












            @Marcos What isn 't working exactly? Are you sure you use GNU awk?
            – oliv
            Nov 9 at 15:07




            @Marcos What isn 't working exactly? Are you sure you use GNU awk?
            – oliv
            Nov 9 at 15:07










            up vote
            0
            down vote













            sed can handle this.




            Assuming you want to keep the header and footer lines -




            $: sed -En '/^=+$/,/^=+F I N I S H=+$/ { /^=+$/ { x; d; }; /^[^=]/ { H; d; }; /^=+F I N I S H=+$/{ H; x; p; q; }; }' infile
            =================================================================
            Data-I-Need
            Data-I-Need
            ...
            ...
            ...
            Data-I-Need
            ==========================F I N I S H============================



            If not, use




            sed -En '/^=+$/,/^=+F I N I S H=+$/ { /^=+$/ { s/.*//g; x; d; }; /^[^=]/ { H; d; }; /^=+F I N I S H=+$/{ x; p; q; }; }' infile


            Note that if you aren't using GNU sed you'll need to insert newlines instead of all those semicolons.



            sed -En '
            /^=+$/,/^=+F I N I S H=+$/ {
            /^=+$/ {
            s/.*//g
            x
            d
            }
            /^[^=]/ {
            H
            d
            }
            /^=+F I N I S H=+$/{
            x
            p
            q
            }
            }' infile

            Data-I-Need
            Data-I-Need
            ...
            ...
            ...
            Data-I-Need



            Breaking it down -




            sed -En '...'


            The -En says to use extended pattern matching (the -E, which I really only used for the +'s), and not to output anything unless specifically asked (the -n).



            /^=+$/,/^=+F I N I S H=+$/ {...}


            says to execute these commands only between lines that are all ='s and lines that are all ='s except for F I N I S H in the middle somewhere. All the stuff between the {}'s will be checked on all lines between those. That does mean from the first =+ line, but that's ok, we handle that inside.



            (a) /^=+$/ { x; d; };
            (b) /^=+$/ { s/.*//g; x; d; };


            (a) says on each of the lines that are all ='s, swap (x) the current line (the "pattern space") with the "hold space", then delete (d) the pattern space. That keeps the current line and deletes whatever you might have accumulated above on false starts. (Remember -n keeps anything from printing till we want it.)



            (b) says erase the current line first, THEN swap and delete. It will still add a newline. Did you want that removed?



            /^[^=]/ { H; d; };


            Both versions use this. On any line that does not start with an =, add it to the hold space (H), then deletes the pattern space (d). The delete always restarts the cycle, reading the next record.



            (a) /^=+F I N I S H=+$/{ H; x; p; q; };
            (b) /^=+F I N I S H=+$/{ x; p; q; };


            On any line with the sentinel F I N I S H string between all ='s, (a) will first append (H) the pattern to the hold space - (b) will not. Both will then swap the pattern and hold spaces (x), print (p) the pattern space (which is now the value accumulated into the hold space), and then delete (d) the pattern space, triggering the next cycle.



            At that point, you will be outside the initial toggle, so unless another row of all ='s happens, you'll skip all the remaining lines. If one does it will again begin to accumulate records, but will not print them unless it hits another F I N I S H record.



            }' infile


            This just closes the script and passes in whatever filename you were using. Note that is is not an in-place edit...



            Hope that helps.






            share|improve this answer























            • this didn't work for me, I'll try to test more on this.
              – Marcos
              Nov 14 at 11:50










            • What did it do?
              – Paul Hodges
              Nov 14 at 14:30















            up vote
            0
            down vote













            sed can handle this.




            Assuming you want to keep the header and footer lines -




            $: sed -En '/^=+$/,/^=+F I N I S H=+$/ { /^=+$/ { x; d; }; /^[^=]/ { H; d; }; /^=+F I N I S H=+$/{ H; x; p; q; }; }' infile
            =================================================================
            Data-I-Need
            Data-I-Need
            ...
            ...
            ...
            Data-I-Need
            ==========================F I N I S H============================



            If not, use




            sed -En '/^=+$/,/^=+F I N I S H=+$/ { /^=+$/ { s/.*//g; x; d; }; /^[^=]/ { H; d; }; /^=+F I N I S H=+$/{ x; p; q; }; }' infile


            Note that if you aren't using GNU sed you'll need to insert newlines instead of all those semicolons.



            sed -En '
            /^=+$/,/^=+F I N I S H=+$/ {
            /^=+$/ {
            s/.*//g
            x
            d
            }
            /^[^=]/ {
            H
            d
            }
            /^=+F I N I S H=+$/{
            x
            p
            q
            }
            }' infile

            Data-I-Need
            Data-I-Need
            ...
            ...
            ...
            Data-I-Need



            Breaking it down -




            sed -En '...'


            The -En says to use extended pattern matching (the -E, which I really only used for the +'s), and not to output anything unless specifically asked (the -n).



            /^=+$/,/^=+F I N I S H=+$/ {...}


            says to execute these commands only between lines that are all ='s and lines that are all ='s except for F I N I S H in the middle somewhere. All the stuff between the {}'s will be checked on all lines between those. That does mean from the first =+ line, but that's ok, we handle that inside.



            (a) /^=+$/ { x; d; };
            (b) /^=+$/ { s/.*//g; x; d; };


            (a) says on each of the lines that are all ='s, swap (x) the current line (the "pattern space") with the "hold space", then delete (d) the pattern space. That keeps the current line and deletes whatever you might have accumulated above on false starts. (Remember -n keeps anything from printing till we want it.)



            (b) says erase the current line first, THEN swap and delete. It will still add a newline. Did you want that removed?



            /^[^=]/ { H; d; };


            Both versions use this. On any line that does not start with an =, add it to the hold space (H), then deletes the pattern space (d). The delete always restarts the cycle, reading the next record.



            (a) /^=+F I N I S H=+$/{ H; x; p; q; };
            (b) /^=+F I N I S H=+$/{ x; p; q; };


            On any line with the sentinel F I N I S H string between all ='s, (a) will first append (H) the pattern to the hold space - (b) will not. Both will then swap the pattern and hold spaces (x), print (p) the pattern space (which is now the value accumulated into the hold space), and then delete (d) the pattern space, triggering the next cycle.



            At that point, you will be outside the initial toggle, so unless another row of all ='s happens, you'll skip all the remaining lines. If one does it will again begin to accumulate records, but will not print them unless it hits another F I N I S H record.



            }' infile


            This just closes the script and passes in whatever filename you were using. Note that is is not an in-place edit...



            Hope that helps.






            share|improve this answer























            • this didn't work for me, I'll try to test more on this.
              – Marcos
              Nov 14 at 11:50










            • What did it do?
              – Paul Hodges
              Nov 14 at 14:30













            up vote
            0
            down vote










            up vote
            0
            down vote









            sed can handle this.




            Assuming you want to keep the header and footer lines -




            $: sed -En '/^=+$/,/^=+F I N I S H=+$/ { /^=+$/ { x; d; }; /^[^=]/ { H; d; }; /^=+F I N I S H=+$/{ H; x; p; q; }; }' infile
            =================================================================
            Data-I-Need
            Data-I-Need
            ...
            ...
            ...
            Data-I-Need
            ==========================F I N I S H============================



            If not, use




            sed -En '/^=+$/,/^=+F I N I S H=+$/ { /^=+$/ { s/.*//g; x; d; }; /^[^=]/ { H; d; }; /^=+F I N I S H=+$/{ x; p; q; }; }' infile


            Note that if you aren't using GNU sed you'll need to insert newlines instead of all those semicolons.



            sed -En '
            /^=+$/,/^=+F I N I S H=+$/ {
            /^=+$/ {
            s/.*//g
            x
            d
            }
            /^[^=]/ {
            H
            d
            }
            /^=+F I N I S H=+$/{
            x
            p
            q
            }
            }' infile

            Data-I-Need
            Data-I-Need
            ...
            ...
            ...
            Data-I-Need



            Breaking it down -




            sed -En '...'


            The -En says to use extended pattern matching (the -E, which I really only used for the +'s), and not to output anything unless specifically asked (the -n).



            /^=+$/,/^=+F I N I S H=+$/ {...}


            says to execute these commands only between lines that are all ='s and lines that are all ='s except for F I N I S H in the middle somewhere. All the stuff between the {}'s will be checked on all lines between those. That does mean from the first =+ line, but that's ok, we handle that inside.



            (a) /^=+$/ { x; d; };
            (b) /^=+$/ { s/.*//g; x; d; };


            (a) says on each of the lines that are all ='s, swap (x) the current line (the "pattern space") with the "hold space", then delete (d) the pattern space. That keeps the current line and deletes whatever you might have accumulated above on false starts. (Remember -n keeps anything from printing till we want it.)



            (b) says erase the current line first, THEN swap and delete. It will still add a newline. Did you want that removed?



            /^[^=]/ { H; d; };


            Both versions use this. On any line that does not start with an =, add it to the hold space (H), then deletes the pattern space (d). The delete always restarts the cycle, reading the next record.



            (a) /^=+F I N I S H=+$/{ H; x; p; q; };
            (b) /^=+F I N I S H=+$/{ x; p; q; };


            On any line with the sentinel F I N I S H string between all ='s, (a) will first append (H) the pattern to the hold space - (b) will not. Both will then swap the pattern and hold spaces (x), print (p) the pattern space (which is now the value accumulated into the hold space), and then delete (d) the pattern space, triggering the next cycle.



            At that point, you will be outside the initial toggle, so unless another row of all ='s happens, you'll skip all the remaining lines. If one does it will again begin to accumulate records, but will not print them unless it hits another F I N I S H record.



            }' infile


            This just closes the script and passes in whatever filename you were using. Note that is is not an in-place edit...



            Hope that helps.






            share|improve this answer














            sed can handle this.




            Assuming you want to keep the header and footer lines -




            $: sed -En '/^=+$/,/^=+F I N I S H=+$/ { /^=+$/ { x; d; }; /^[^=]/ { H; d; }; /^=+F I N I S H=+$/{ H; x; p; q; }; }' infile
            =================================================================
            Data-I-Need
            Data-I-Need
            ...
            ...
            ...
            Data-I-Need
            ==========================F I N I S H============================



            If not, use




            sed -En '/^=+$/,/^=+F I N I S H=+$/ { /^=+$/ { s/.*//g; x; d; }; /^[^=]/ { H; d; }; /^=+F I N I S H=+$/{ x; p; q; }; }' infile


            Note that if you aren't using GNU sed you'll need to insert newlines instead of all those semicolons.



            sed -En '
            /^=+$/,/^=+F I N I S H=+$/ {
            /^=+$/ {
            s/.*//g
            x
            d
            }
            /^[^=]/ {
            H
            d
            }
            /^=+F I N I S H=+$/{
            x
            p
            q
            }
            }' infile

            Data-I-Need
            Data-I-Need
            ...
            ...
            ...
            Data-I-Need



            Breaking it down -




            sed -En '...'


            The -En says to use extended pattern matching (the -E, which I really only used for the +'s), and not to output anything unless specifically asked (the -n).



            /^=+$/,/^=+F I N I S H=+$/ {...}


            says to execute these commands only between lines that are all ='s and lines that are all ='s except for F I N I S H in the middle somewhere. All the stuff between the {}'s will be checked on all lines between those. That does mean from the first =+ line, but that's ok, we handle that inside.



            (a) /^=+$/ { x; d; };
            (b) /^=+$/ { s/.*//g; x; d; };


            (a) says on each of the lines that are all ='s, swap (x) the current line (the "pattern space") with the "hold space", then delete (d) the pattern space. That keeps the current line and deletes whatever you might have accumulated above on false starts. (Remember -n keeps anything from printing till we want it.)



            (b) says erase the current line first, THEN swap and delete. It will still add a newline. Did you want that removed?



            /^[^=]/ { H; d; };


            Both versions use this. On any line that does not start with an =, add it to the hold space (H), then deletes the pattern space (d). The delete always restarts the cycle, reading the next record.



            (a) /^=+F I N I S H=+$/{ H; x; p; q; };
            (b) /^=+F I N I S H=+$/{ x; p; q; };


            On any line with the sentinel F I N I S H string between all ='s, (a) will first append (H) the pattern to the hold space - (b) will not. Both will then swap the pattern and hold spaces (x), print (p) the pattern space (which is now the value accumulated into the hold space), and then delete (d) the pattern space, triggering the next cycle.



            At that point, you will be outside the initial toggle, so unless another row of all ='s happens, you'll skip all the remaining lines. If one does it will again begin to accumulate records, but will not print them unless it hits another F I N I S H record.



            }' infile


            This just closes the script and passes in whatever filename you were using. Note that is is not an in-place edit...



            Hope that helps.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Nov 9 at 15:15

























            answered Nov 9 at 14:50









            Paul Hodges

            2,5351320




            2,5351320












            • this didn't work for me, I'll try to test more on this.
              – Marcos
              Nov 14 at 11:50










            • What did it do?
              – Paul Hodges
              Nov 14 at 14:30


















            • this didn't work for me, I'll try to test more on this.
              – Marcos
              Nov 14 at 11:50










            • What did it do?
              – Paul Hodges
              Nov 14 at 14:30
















            this didn't work for me, I'll try to test more on this.
            – Marcos
            Nov 14 at 11:50




            this didn't work for me, I'll try to test more on this.
            – Marcos
            Nov 14 at 11:50












            What did it do?
            – Paul Hodges
            Nov 14 at 14:30




            What did it do?
            – Paul Hodges
            Nov 14 at 14:30










            up vote
            0
            down vote













            Although there is already a sed solution there, I like sed for its simplicity:



            sed -n '/^==*r*$/,/^==*F I N I S H/{H;/^==*[^F=]/h;${g;p}}' file


            In this sed command we made a range for our commands to be run against. This range starts with a line which begins, contains only and ends to = and then finishes on a line that starts with = and heads to F I N I S H. Now our commands:



            H appends each line immediately to hold space. Then /^==*[^F=]/h executes on other sections' header or footer that it replaces hold space with current pattern space.



            And at the last line we replaces current pattern space with what is in hold space and then print it using ${g;p}. The whole thing outputs this:



            =================================================================
            Data-I-Need
            Data-I-Need
            ...
            ...
            ...
            Data-I-Need
            ==========================F I N I S H============================





            share|improve this answer





















            • I do not need the header and footer lines.
              – Marcos
              Nov 9 at 16:56










            • Then piple results to sed '1d;$d;'
              – revo
              Nov 9 at 18:08










            • for some reason your solution didn't work out, I'll test further to understand why.
              – Marcos
              Nov 14 at 11:49










            • Please elaborate. it didn't work does not describe what the problem is, whether or not you get any result and if yes what is that. However I support @potong's answer. That has a nice idea behind.
              – revo
              Nov 14 at 11:53

















            up vote
            0
            down vote













            Although there is already a sed solution there, I like sed for its simplicity:



            sed -n '/^==*r*$/,/^==*F I N I S H/{H;/^==*[^F=]/h;${g;p}}' file


            In this sed command we made a range for our commands to be run against. This range starts with a line which begins, contains only and ends to = and then finishes on a line that starts with = and heads to F I N I S H. Now our commands:



            H appends each line immediately to hold space. Then /^==*[^F=]/h executes on other sections' header or footer that it replaces hold space with current pattern space.



            And at the last line we replaces current pattern space with what is in hold space and then print it using ${g;p}. The whole thing outputs this:



            =================================================================
            Data-I-Need
            Data-I-Need
            ...
            ...
            ...
            Data-I-Need
            ==========================F I N I S H============================





            share|improve this answer





















            • I do not need the header and footer lines.
              – Marcos
              Nov 9 at 16:56










            • Then piple results to sed '1d;$d;'
              – revo
              Nov 9 at 18:08










            • for some reason your solution didn't work out, I'll test further to understand why.
              – Marcos
              Nov 14 at 11:49










            • Please elaborate. it didn't work does not describe what the problem is, whether or not you get any result and if yes what is that. However I support @potong's answer. That has a nice idea behind.
              – revo
              Nov 14 at 11:53















            up vote
            0
            down vote










            up vote
            0
            down vote









            Although there is already a sed solution there, I like sed for its simplicity:



            sed -n '/^==*r*$/,/^==*F I N I S H/{H;/^==*[^F=]/h;${g;p}}' file


            In this sed command we made a range for our commands to be run against. This range starts with a line which begins, contains only and ends to = and then finishes on a line that starts with = and heads to F I N I S H. Now our commands:



            H appends each line immediately to hold space. Then /^==*[^F=]/h executes on other sections' header or footer that it replaces hold space with current pattern space.



            And at the last line we replaces current pattern space with what is in hold space and then print it using ${g;p}. The whole thing outputs this:



            =================================================================
            Data-I-Need
            Data-I-Need
            ...
            ...
            ...
            Data-I-Need
            ==========================F I N I S H============================





            share|improve this answer












            Although there is already a sed solution there, I like sed for its simplicity:



            sed -n '/^==*r*$/,/^==*F I N I S H/{H;/^==*[^F=]/h;${g;p}}' file


            In this sed command we made a range for our commands to be run against. This range starts with a line which begins, contains only and ends to = and then finishes on a line that starts with = and heads to F I N I S H. Now our commands:



            H appends each line immediately to hold space. Then /^==*[^F=]/h executes on other sections' header or footer that it replaces hold space with current pattern space.



            And at the last line we replaces current pattern space with what is in hold space and then print it using ${g;p}. The whole thing outputs this:



            =================================================================
            Data-I-Need
            Data-I-Need
            ...
            ...
            ...
            Data-I-Need
            ==========================F I N I S H============================






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Nov 9 at 15:27









            revo

            32k134680




            32k134680












            • I do not need the header and footer lines.
              – Marcos
              Nov 9 at 16:56










            • Then piple results to sed '1d;$d;'
              – revo
              Nov 9 at 18:08










            • for some reason your solution didn't work out, I'll test further to understand why.
              – Marcos
              Nov 14 at 11:49










            • Please elaborate. it didn't work does not describe what the problem is, whether or not you get any result and if yes what is that. However I support @potong's answer. That has a nice idea behind.
              – revo
              Nov 14 at 11:53




















            • I do not need the header and footer lines.
              – Marcos
              Nov 9 at 16:56










            • Then piple results to sed '1d;$d;'
              – revo
              Nov 9 at 18:08










            • for some reason your solution didn't work out, I'll test further to understand why.
              – Marcos
              Nov 14 at 11:49










            • Please elaborate. it didn't work does not describe what the problem is, whether or not you get any result and if yes what is that. However I support @potong's answer. That has a nice idea behind.
              – revo
              Nov 14 at 11:53


















            I do not need the header and footer lines.
            – Marcos
            Nov 9 at 16:56




            I do not need the header and footer lines.
            – Marcos
            Nov 9 at 16:56












            Then piple results to sed '1d;$d;'
            – revo
            Nov 9 at 18:08




            Then piple results to sed '1d;$d;'
            – revo
            Nov 9 at 18:08












            for some reason your solution didn't work out, I'll test further to understand why.
            – Marcos
            Nov 14 at 11:49




            for some reason your solution didn't work out, I'll test further to understand why.
            – Marcos
            Nov 14 at 11:49












            Please elaborate. it didn't work does not describe what the problem is, whether or not you get any result and if yes what is that. However I support @potong's answer. That has a nice idea behind.
            – revo
            Nov 14 at 11:53






            Please elaborate. it didn't work does not describe what the problem is, whether or not you get any result and if yes what is that. However I support @potong's answer. That has a nice idea behind.
            – revo
            Nov 14 at 11:53




















            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • 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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2fstackoverflow.com%2fquestions%2f53226074%2fdisplay-data-between-two-fixed-patterns%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







            這個網誌中的熱門文章

            Xamarin.form Move up view when keyboard appear

            Post-Redirect-Get with Spring WebFlux and Thymeleaf

            Anylogic : not able to use stopDelay()