Timeline for Bash Shell Script uses Sed to create and insert multiple lines after a particular line in an existing file
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Oct 24, 2013 at 15:07 | history | edited | Gareth Rees | CC BY-SA 3.0 |
"find ... | while read file" is more space-efficient than "for file in $(find ...)"
|
| Apr 9, 2013 at 9:05 | comment | added | Gareth Rees | See updated answer for my response to your comment on #5. | |
| Apr 9, 2013 at 9:04 | history | edited | Gareth Rees | CC BY-SA 3.0 |
respond to comment
|
| Apr 9, 2013 at 8:08 | comment | added | Gareth Rees | Ah, an excerpt! This had me puzzled. | |
| Apr 9, 2013 at 2:34 | comment | added | GlenPeterson |
#2,3,6,8: Changes made and all work; thanks! #1: XML is an excerpt (fixed post). #7: Interesting, but p and c are sed-specific; no change made. #5: Error: sed: -e expression #1, char 153: unterminated 's' command I think it has to do with newlines #9: Ultimate output is a patch file. Everything in git, script makes multiple backups... "Wouldn't it be better to do it in one go?" Great question! Wish I could post whole project. I was trying to leverage existing tools, but after so many shims, the original tools are doing less than half the work. Thanks much for your time and Python code!
|
|
| Apr 9, 2013 at 2:16 | history | bounty ended | GlenPeterson | ||
| Apr 9, 2013 at 2:16 | vote | accept | GlenPeterson | ||
| Apr 8, 2013 at 13:08 | history | edited | Gareth Rees | CC BY-SA 3.0 |
not really any need for `re` here; also explain why `p;c` makes sense
|
| Apr 8, 2013 at 12:26 | history | edited | Gareth Rees | CC BY-SA 3.0 |
double-quote filename variables; find -type f
|
| Apr 8, 2013 at 11:29 | history | answered | Gareth Rees | CC BY-SA 3.0 |