Skip to content

Commit

Permalink
remove pgrep, fixing #40
Browse files Browse the repository at this point in the history
  • Loading branch information
@onceupon
onceupon committed Mar 16, 2023
1 parent a851316 commit 6576e5a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -306,8 +306,8 @@ echo "var=5;--var"| bc
grep = grep -G # Basic Regular Expression (BRE)
fgrep = grep -F # fixed text, ignoring meta-characters
egrep = grep -E # Extended Regular Expression (ERE)
pgrep = grep -P # Perl Compatible Regular Expressions (PCRE)
rgrep = grep -r # recursive
grep -P # Perl Compatible Regular Expressions (PCRE)
```

##### Grep and count number of empty lines
Expand Down

1 comment on commit 6576e5a

@mu578
Copy link

@mu578 mu578 commented on 6576e5a Mar 29, 2023 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To note for regular expressions in general, people tend to be driven solely toward grep with misplaced expectations; grep is useful for simple text matching; sed and awk in the other hand offer better access and options; e.g match/replace/edit patterns. Other point, truly learning regular expression grammars is a tremendous advantage ; regrettably speaking, from my experience, most of individuals stick with copy-paste examples thinking it is ok; they don't foresee or understand the gain of freedom it offers.

Please sign in to comment.