Timeline for How do I grep for multiple patterns with pattern having a pipe character?
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 6, 2019 at 6:57 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 40 characters in body |
| Nov 6, 2019 at 6:47 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 231 characters in body |
| Nov 6, 2019 at 6:38 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 166 characters in body |
| Nov 6, 2019 at 6:30 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | added 619 characters in body |
| Apr 19, 2018 at 10:29 | comment | added | northern-bradley | i always forget the -E and have to resort the google/here. but i think i like the multiple instances version with -e and am going to try to remember that one | |
| Nov 24, 2016 at 20:35 | comment | added | DrStrangepork | When all else fails, individual -e options is the simplest and safest bet | |
| Jun 7, 2016 at 11:27 | comment | added | Stéphane Chazelas | Note that egrep predates grep -E. It is not GNU specific (it certainly has nothing to do with Linux). Actually, you'll still find systems like Solaris where the default grep still doesn't support -E. | |
| S Jun 7, 2016 at 10:54 | history | suggested | Quentin Pradet | CC BY-SA 3.0 | Fix extended regexps url (https + anchor) |
| Jun 7, 2016 at 10:24 | review | Suggested edits | |||
| S Jun 7, 2016 at 10:54 | |||||
| May 20, 2015 at 9:45 | comment | added | Peter Mortensen | Perhaps it should be mentioned that for more complicated patterns where alternation is only to be for a part of the regular expression, it can be grouped with "\(" and "\)" (the escaping is for the default "basic regular expressions") (?). | |
| Jul 22, 2014 at 8:53 | comment | added | Gilles 'SO- stop being evil' | @TC1 Whether grep -F has an actual performance benefit depends on the grep implementation: some of them apply the same algorithm anyway, so that -F makes a difference only to the time spent parsing the pattern and not to the time searching. GNU grep isn't faster with -F, for example (it also has a bug that makes grep -F slower in multibyte locales — the same constant pattern with grep is actually significantly faster!). On the other hand BusyBox grep does benefit a lot from -F on large files. | |
| Jul 22, 2014 at 8:41 | comment | added | ramn | @TC1 fgrep is deprecated according to man page | |
| Apr 27, 2012 at 2:23 | comment | added | poige | @TC1, yeah, people often forget that grep uses regexp syntax — unix.stackexchange.com/questions/21020/… | |
| Apr 26, 2012 at 22:10 | vote | accept | Dan | ||
| Apr 26, 2012 at 9:37 | comment | added | TC1 | As a sidenote -- when the patterns are fixed, you should really get into the habit of fgrep or grep -F, for small patterns the difference will be negligible but as they get longer, the benefits start to show... | |
| Apr 26, 2012 at 1:13 | history | answered | Gilles 'SO- stop being evil' | CC BY-SA 3.0 |