Tjyylli

It took me a lot of time to make this, pls like. (YouTube Comments #1)

How to acknowledge an embarrassing job interview, now that I work directly with the interviewer?

How do creatures spend Hit Dice after a short rest (if they can do so)?

Why do neural networks need so many training examples to perform?

Why did Jodrell Bank assist the Soviet Union to collect data from their spacecraft in the mid 1960's?

What is the wife of a henpecked husband called?

How would an AI self awareness kill switch work?

When does coming up with an idea constitute sufficient contribution for authorship?

Can pricing be copyrighted?

Knowing when to use pictures over words

Cryptic with missing capitals

What do you call a fact that doesn't match the settings?

How to generate a matrix with certain conditions

If I delete my router's history can my ISP still provide it to my parents?

View Angle Calculation

How would one buy a used TIE Fighter or X-Wing?

Word or phrase for showing great skill at something without formal training in it

How experienced do I need to be to go on a photography workshop?

Finding radius of circle

Why avoid shared user accounts?

Using loops to create tables

Why did the villain in the first Men in Black movie care about Earth's Cockroaches?

Does my logo design convey the right feelings for a University Student's Council?

Slow moving projectiles from a hand-held weapon - how do they reach the target?

awk statement to validate and return fixed-structure data lines at start of file

awk + cut file between lines from ext ARGUsing awk to split text file every 10,000 linessed: how to replace line if found or append to end of file if not found?Replace Line Breaks on matching lines, using AWKawk print data in fixed columnAWK - print file and length in two lines in ENDHow to change a character on a certain line without delimiters with awkAdd spaces to the beginning of each matching lineText processing: transforming numbers in equivalent number of spaces in bashHow to parse multi-line log file in awk and output only single line with last known ip address

1

I have a file that starts like this

## CONFIG-PARAMS-START ##

##

## text1 text2 NNNNNNNNN (arbitrary_comment) ##

## text1 text2 NNNNNNNNN (arbitrary_comment) ##

## text1 text2 NNNNNNNNN (arbitrary_comment) ##

##

## CONFIG-PARAMS-END ##

<arbitrary rest of file>

Output:

I'd like to validate the file with awk, to check that it starts this way.

If yes, output just the data lines (not the start/end, or "bare" lines, or anything after this section), and if no, return a nonzero rc [$?] or some other easily testable condition such as [empty string].

File spec:

In modern (PRCE) regex terms, the data lines format is:

^##[[:space:]]*                    - starts with ## and optional spaces

  ([a-zA-Z0-9_-]+.)+)             - >=1 repetition of [text_string][dot] (no spaces)

    [[:space:]]+                   - spaces

      ([^[:space:]]+)              - block of non-spaces

        [[:space:]]+               - spaces

          ([0-9]+)                 - block of digits

            [[:space:]]            - spaces

              (.*                 - '(' + any text

                ##[[:space:]]*$    - 2 hashes, optional spaces + line end

( so a typical line might be ## abc.3ef. w;4o8c-uy3tu!ae 9938 (good luck!)##  )

There mustn't be any other lines (including empty/whitespace lines) before the first line, or anywhere else in the data block. Within each line, consecutive white space effectively acts as a single delimiter. White space after the first ## and before+after the last ## are all optional. There will typically be <15 lines in the section so size/speed/efficiency will be negligible considerations.

(The greedy capture on the 2nd last line isn't an issue, it'll backtrack minimally to match '##' in the final line)

Compatibility:
Wide compatibility is important, as the code will eventually need to be runnable on default/standard builds of different Linux, FreeBSD + other BSDs, maybe even other modern *nix platforms. (It's part of a patch for a widely used open-source package). Perhaps basic POSIX would provide a level field rather than assuming only some specific awk variant? Maintainability/ease of understanding is also useful for the same reason. Hoping greatly to avoid perl ;-)

I haven't quite got the hang of using awk for this sort of forward-and-backward referencing and checking, and even less an idea about managing compatibility / slight differences in implementations.

Awk skills would be appreciated to get a working version of this snippet!

compatibility awk

share|improve this question

edited 11 mins ago

Stilez

asked 17 mins ago

StilezStilez

77711022

add a comment | 

1

I have a file that starts like this

## CONFIG-PARAMS-START ##

##

## text1 text2 NNNNNNNNN (arbitrary_comment) ##

## text1 text2 NNNNNNNNN (arbitrary_comment) ##

## text1 text2 NNNNNNNNN (arbitrary_comment) ##

##

## CONFIG-PARAMS-END ##

<arbitrary rest of file>

Output:

I'd like to validate the file with awk, to check that it starts this way.

If yes, output just the data lines (not the start/end, or "bare" lines, or anything after this section), and if no, return a nonzero rc [$?] or some other easily testable condition such as [empty string].

File spec:

In modern (PRCE) regex terms, the data lines format is:

^##[[:space:]]*                    - starts with ## and optional spaces

  ([a-zA-Z0-9_-]+.)+)             - >=1 repetition of [text_string][dot] (no spaces)

    [[:space:]]+                   - spaces

      ([^[:space:]]+)              - block of non-spaces

        [[:space:]]+               - spaces

          ([0-9]+)                 - block of digits

            [[:space:]]            - spaces

              (.*                 - '(' + any text

                ##[[:space:]]*$    - 2 hashes, optional spaces + line end

( so a typical line might be ## abc.3ef. w;4o8c-uy3tu!ae 9938 (good luck!)##  )

There mustn't be any other lines (including empty/whitespace lines) before the first line, or anywhere else in the data block. Within each line, consecutive white space effectively acts as a single delimiter. White space after the first ## and before+after the last ## are all optional. There will typically be <15 lines in the section so size/speed/efficiency will be negligible considerations.

(The greedy capture on the 2nd last line isn't an issue, it'll backtrack minimally to match '##' in the final line)

Compatibility:
Wide compatibility is important, as the code will eventually need to be runnable on default/standard builds of different Linux, FreeBSD + other BSDs, maybe even other modern *nix platforms. (It's part of a patch for a widely used open-source package). Perhaps basic POSIX would provide a level field rather than assuming only some specific awk variant? Maintainability/ease of understanding is also useful for the same reason. Hoping greatly to avoid perl ;-)

I haven't quite got the hang of using awk for this sort of forward-and-backward referencing and checking, and even less an idea about managing compatibility / slight differences in implementations.

Awk skills would be appreciated to get a working version of this snippet!

compatibility awk

share|improve this question

edited 11 mins ago

Stilez

asked 17 mins ago

StilezStilez

77711022

add a comment | 

I have a file that starts like this

## CONFIG-PARAMS-START ##

##

## text1 text2 NNNNNNNNN (arbitrary_comment) ##

## text1 text2 NNNNNNNNN (arbitrary_comment) ##

## text1 text2 NNNNNNNNN (arbitrary_comment) ##

##

## CONFIG-PARAMS-END ##

<arbitrary rest of file>

Output:

I'd like to validate the file with awk, to check that it starts this way.

If yes, output just the data lines (not the start/end, or "bare" lines, or anything after this section), and if no, return a nonzero rc [$?] or some other easily testable condition such as [empty string].

File spec:

In modern (PRCE) regex terms, the data lines format is:

^##[[:space:]]*                    - starts with ## and optional spaces

  ([a-zA-Z0-9_-]+.)+)             - >=1 repetition of [text_string][dot] (no spaces)

    [[:space:]]+                   - spaces

      ([^[:space:]]+)              - block of non-spaces

        [[:space:]]+               - spaces

          ([0-9]+)                 - block of digits

            [[:space:]]            - spaces

              (.*                 - '(' + any text

                ##[[:space:]]*$    - 2 hashes, optional spaces + line end

( so a typical line might be ## abc.3ef. w;4o8c-uy3tu!ae 9938 (good luck!)##  )

There mustn't be any other lines (including empty/whitespace lines) before the first line, or anywhere else in the data block. Within each line, consecutive white space effectively acts as a single delimiter. White space after the first ## and before+after the last ## are all optional. There will typically be <15 lines in the section so size/speed/efficiency will be negligible considerations.

(The greedy capture on the 2nd last line isn't an issue, it'll backtrack minimally to match '##' in the final line)

Compatibility:
Wide compatibility is important, as the code will eventually need to be runnable on default/standard builds of different Linux, FreeBSD + other BSDs, maybe even other modern *nix platforms. (It's part of a patch for a widely used open-source package). Perhaps basic POSIX would provide a level field rather than assuming only some specific awk variant? Maintainability/ease of understanding is also useful for the same reason. Hoping greatly to avoid perl ;-)

I haven't quite got the hang of using awk for this sort of forward-and-backward referencing and checking, and even less an idea about managing compatibility / slight differences in implementations.

Awk skills would be appreciated to get a working version of this snippet!

compatibility awk

share|improve this question

edited 11 mins ago

Stilez

asked 17 mins ago

StilezStilez

77711022

## CONFIG-PARAMS-START ##

##

## text1 text2 NNNNNNNNN (arbitrary_comment) ##

## text1 text2 NNNNNNNNN (arbitrary_comment) ##

## text1 text2 NNNNNNNNN (arbitrary_comment) ##

##

## CONFIG-PARAMS-END ##

<arbitrary rest of file>

^##[[:space:]]*                    - starts with ## and optional spaces

  ([a-zA-Z0-9_-]+.)+)             - >=1 repetition of [text_string][dot] (no spaces)

    [[:space:]]+                   - spaces

      ([^[:space:]]+)              - block of non-spaces

        [[:space:]]+               - spaces

          ([0-9]+)                 - block of digits

            [[:space:]]            - spaces

              (.*                 - '(' + any text

                ##[[:space:]]*$    - 2 hashes, optional spaces + line end

share|improve this question

edited 11 mins ago

Stilez

asked 17 mins ago

StilezStilez

77711022

share|improve this question

edited 11 mins ago

Stilez

asked 17 mins ago

StilezStilez

77711022

asked 17 mins ago

StilezStilez

77711022

asked 17 mins ago

StilezStilez

77711022