[All variants] Change settings

Hi, I have a big settings confg (file attached). There are a few separate tasks that I have to accomplish. All scripting/programming languages are appreciated.

1. I need to parse all values and output to stdout. Sample output (truncated):

VALUEA
2017-01-01
Lores ipsum
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

VALUEB
2017-02-02
...

2. I need to create a new setting DATEB and write it to file before TEXT by adding n days to value of DATEA. For example here I added 300 days (truncated):

#SETTINGSBEGIN VALUEA
#DATEA 2017-01-01
...
#DATEB 2017-10-28
TEXT
...
#SETTINGSEND

#SETTINGSBEGIN VALUEB
#DATEA 2017-02-02
...
#DATEB 2017-11-29
TEXT
...
#SETTINGSEND

#SETTINGSBEGIN VALUE
#DATEA 2017-03-03
...
#DATEB 2017-12-28
TEXT
...
#SETTINGSEND

You could use GNU awk like this:

gawk -v ADD_DAYS=300 '
 /#DATEA/ {
   DT = mktime(gensub(/-/, " ", "g", $2) " 0 0 0")
   DT += 24*60*60*ADD_DAYS
 }
 /#TEXT/ {
   print strftime("#DATEB %Y-%m-%d", DT)
 }
 1' settings.txt > settings_new.txt

You could try this in bash script, it does require GNU date for the date calculations:

#!/bin/bash
ADD_DAYS=300
while read line
do
    [[ "$line" = [#]DATEA\ * ]] && DB=$(date -d "${line#*DATEA } + ${ADD_DAYS}days" +%Y-%m-%d)
    [[ "$line" = [#]TEXT ]] && echo "#DATEB $DB"
    echo "$line"
done < settings.txt > settings_new.txt

Thanks again.

But how can I parse that file? Is it possible?

Yes the code in #3 above is parsing the file, it is only interested in lines that begin with "#DATEA "; or are equal to "#TEST".

What processing do you want to do with the file? Perhaps if you post your desired output.

I just want to output to stdout. This is the desired output:

OK sorry for the misunderstanding.

Here is a GNU awk solution:

gawk -v ADD_DAYS=300 '
/#DATEA/ {
  DT = mktime(gensub(/-/, " ", "g", $2) " 0 0 0")
  DT += 24*60*60*ADD_DAYS
  printf "VALUEA\n%s\n", $2
}
/#VALUE TITLE/ { print gensub(/.*"([^"]+)"/, "\\1","g") }
/#SETTINGSEND/ { print strftime("\nVALUEB\n%Y-%m-%d", DT) }
!/^#/' settings.txt

and here is bash version:

#!/bin/bash
ADD_DAYS=300
while read line
do
    if [[ "$line" = \#DATEA\ * ]]
    then
       DA=${line#*DATEA }
       DT=$(date -d "$DA + ${ADD_DAYS}days" +%Y-%m-%d)
       printf "VALUEA\n%s\n" "$DA"
    fi
    if [[ "$line" = \#VALUE\ TITLE=* ]]
    then
        line=${line%\"}
        echo "${line#*\"}"
    fi
    [[ "$line" = \#SETTINGSEND* ]] && printf "\nVALUEB\n%s\n" "$DT"
    [[ "$line" = \#* ]] || echo "$line"
done < settings.txt

edit: This bash solution uses a case statement, which I think looks a bit cleaner than the one above:

#!/bin/bash
ADD_DAYS=300
while read line
do
    case "$line" in
        [#]DATEA\ *)
           DA=${line#*DATEA }
           DT=$(date -d "$DA + ${ADD_DAYS}days" +%Y-%m-%d)
           printf "VALUEA\n%s\n" "$DA" ;;
        [#]VALUE\ TITLE=*)
            line=${line%\"}
            echo "${line#*\"}" ;;
        [#]SETTINGSEND*) printf "\nVALUEB\n%s\n" "$DT" ;;
        [#]*) ;;
        *) echo "$line" ;;
    esac
done < settings.txt

Sorry, but this time it is my fault! I truncated the desired output and you got me wrong.
I also forgot to mention that this script shouldn't calculate new date anything. It should only output to stdout.
Here is the full output that should be produced from settings.txt

VALUEA
2017-01-01
Lores ipsum

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

VALUEB
2017-02-02
Sed ut perspiciatis

Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?

VALUEC
2017-03-03
At vero eos et accusamus

At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas molestias excepturi sint occaecati cupiditate non provident, similique sunt in culpa qui officia deserunt mollitia animi, id est laborum et dolorum fuga.

Et harum quidem rerum facilis est et expedita distinctio.

Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime placeat facere possimus, omnis voluptas assumenda est, omnis dolor repellendus.

Temporibus autem quibusdam et aut officiis debitis aut rerum necessitatibus saepe eveniet ut et voluptates repudiandae sint et molestiae non recusandae.

Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus maiores alias consequatur aut perferendis doloribus asperiores repellat.

OK this here is awk for the new output:

gawk -v ADD_DAYS=300 '
/#(DATEA|SETTINGSBEGIN) / { print $2 }
/#VALUE TITLE/ { printf "%s\n\n", gensub(/.*"([^"]+)"/, "\\1","g") }
!/^#/' settings.txt

And a bash version using case statement:

#!/bin/bash
while read line
do
    case "$line" in
        [#]SETTINGSBEGIN\ *|[#]DATEA\ *) echo "${line#* }" ;;
        [#]VALUE\ TITLE=*)
            line=${line%\"} 
            printf "%s\n\n" "${line#*\"}" ;;
        [#]*)  ;;
        *) printf "%s\n" "$line" ;;
    esac
done < settings.txt

Thanks a lot! If I understand correctly, if there will be a new parameter, script will not output it, right?

That is correct, in the awk script this line: !/^#/ will only print lines that don't begin with a hash ( # ) character.

The same applies to the bash script implemented by this line [#]*) ;;

I understand. But the script will not parse any parameters until I know their exact names.

For example if I will not edit the script to parse #SETTINGSPARAMETER, script will not output it.

The problem is, that I have no idea what these names are. All I can say that they don't have spaces...