Timeline for Replacing matching text after two matching lines
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 11, 2015 at 14:30 | vote | accept | Steve Parker | ||
| Nov 10, 2015 at 14:01 | history | edited | Stéphane Chazelas | CC BY-SA 3.0 |
added 683 characters in body
|
| Nov 10, 2015 at 13:50 | comment | added | mikeserv | @Otheus - no. it only expands expandables. S: the whitespace thing does indicate a closed loop. or the hold space, maybe. | |
| Nov 10, 2015 at 13:48 | comment | added | Otheus |
Will $/ within double-quotes confuse the shell?
|
|
| Nov 10, 2015 at 13:45 | comment | added | Otheus | The problem is that the whitespace before each line is a variable amount, but that amount must be consistent between a stanza's first child node and subsequent child nodes (but grand-children may have a different amount of leading whitespace). | |
| Nov 10, 2015 at 13:43 | comment | added | Stéphane Chazelas | @mikeserv, I don't know anything about YAML, I just extrapolated from the OP's sample. | |
| Nov 10, 2015 at 13:40 | history | edited | Stéphane Chazelas | CC BY-SA 3.0 |
added 1 character in body
|
| Nov 10, 2015 at 13:39 | comment | added | mikeserv | I thought so too - but I wasn't sure about the ending bit for YAML or if it was supposed to be a part of a different script so I enclosed the handler in its own little loop. you use a : too? that is a sure thing then? i think i'll just delete mine. i'm too fuzzy there. | |
| Nov 10, 2015 at 13:39 | history | edited | Stéphane Chazelas | CC BY-SA 3.0 |
added 160 characters in body
|
| Nov 10, 2015 at 13:33 | history | answered | Stéphane Chazelas | CC BY-SA 3.0 |