Timeline for How to grep -v and also exclude the next line after the match?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 16, 2020 at 15:50 | comment | added | ConstantFun | @Peter.O Thanks for clarifying. I feel kind of stupid now. xD | |
| Jul 14, 2020 at 17:12 | comment | added | don_crissti | @ConstantFun - RE is short for Regular Expression | |
| Jul 7, 2020 at 3:55 | comment | added | ConstantFun | @Peter.O What do you mean by RE? | |
| Oct 1, 2018 at 11:04 | history | edited | don_crissti | CC BY-SA 4.0 | added 25 characters in body |
| Aug 30, 2015 at 8:16 | comment | added | don_crissti | @Peter.O - thanks ! No, per the specs, an empty RE should always match the last RE used in the last command; the ! is not part of the RE, it's a sed thing. | |
| Aug 30, 2015 at 7:04 | comment | added | Peter.O | Interesting. I didn't realize that // matched /SomeTestAA/. I thought, in this case, it would have matched the negated expression: /SomeTestAA/!. (+1) | |
| Aug 30, 2015 at 1:23 | history | answered | don_crissti | CC BY-SA 3.0 |