grep: conflicting matchers specified
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I'm using find with xargs and grep to find text which we need to translate in our application.
find . -name *.vue -not -path "./vendor/*" -not -path "./node_modules/*" -not -path "./public/*" -not -path "./data/*" | xargs -P1 -I grep -PHonE "(?:(?>label|title|placeholder|helpText|data-vv-as)=(?>".*?"|'.*?'))|translate((?>'([^']*).*?'|"([^"]*).*?"),?.*?)?|".*?")s?" >> $TMPFILE
The error I'm getting is grep: conflicting matchers specified
It worked before I changed the regex and added the -P argument.
I'm really confused, the regex seems fine and the command worked before, what matchers are conflicting? I'm not getting it.
grep find regular-expression xargs
New contributor
add a comment |Â
up vote
0
down vote
favorite
I'm using find with xargs and grep to find text which we need to translate in our application.
find . -name *.vue -not -path "./vendor/*" -not -path "./node_modules/*" -not -path "./public/*" -not -path "./data/*" | xargs -P1 -I grep -PHonE "(?:(?>label|title|placeholder|helpText|data-vv-as)=(?>".*?"|'.*?'))|translate((?>'([^']*).*?'|"([^"]*).*?"),?.*?)?|".*?")s?" >> $TMPFILE
The error I'm getting is grep: conflicting matchers specified
It worked before I changed the regex and added the -P argument.
I'm really confused, the regex seems fine and the command worked before, what matchers are conflicting? I'm not getting it.
grep find regular-expression xargs
New contributor
1
-P
means perl compatible mode and-E
means extended regular expression mode - you need to pick one
â steeldriver
Oct 4 at 13:56
@steeldriver thanks a lot! I probably should have read the man page a bit more carefully. Can you post that as an answer?
â MadClown
Oct 4 at 14:11
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm using find with xargs and grep to find text which we need to translate in our application.
find . -name *.vue -not -path "./vendor/*" -not -path "./node_modules/*" -not -path "./public/*" -not -path "./data/*" | xargs -P1 -I grep -PHonE "(?:(?>label|title|placeholder|helpText|data-vv-as)=(?>".*?"|'.*?'))|translate((?>'([^']*).*?'|"([^"]*).*?"),?.*?)?|".*?")s?" >> $TMPFILE
The error I'm getting is grep: conflicting matchers specified
It worked before I changed the regex and added the -P argument.
I'm really confused, the regex seems fine and the command worked before, what matchers are conflicting? I'm not getting it.
grep find regular-expression xargs
New contributor
I'm using find with xargs and grep to find text which we need to translate in our application.
find . -name *.vue -not -path "./vendor/*" -not -path "./node_modules/*" -not -path "./public/*" -not -path "./data/*" | xargs -P1 -I grep -PHonE "(?:(?>label|title|placeholder|helpText|data-vv-as)=(?>".*?"|'.*?'))|translate((?>'([^']*).*?'|"([^"]*).*?"),?.*?)?|".*?")s?" >> $TMPFILE
The error I'm getting is grep: conflicting matchers specified
It worked before I changed the regex and added the -P argument.
I'm really confused, the regex seems fine and the command worked before, what matchers are conflicting? I'm not getting it.
grep find regular-expression xargs
grep find regular-expression xargs
New contributor
New contributor
New contributor
asked Oct 4 at 13:32
MadClown
1
1
New contributor
New contributor
1
-P
means perl compatible mode and-E
means extended regular expression mode - you need to pick one
â steeldriver
Oct 4 at 13:56
@steeldriver thanks a lot! I probably should have read the man page a bit more carefully. Can you post that as an answer?
â MadClown
Oct 4 at 14:11
add a comment |Â
1
-P
means perl compatible mode and-E
means extended regular expression mode - you need to pick one
â steeldriver
Oct 4 at 13:56
@steeldriver thanks a lot! I probably should have read the man page a bit more carefully. Can you post that as an answer?
â MadClown
Oct 4 at 14:11
1
1
-P
means perl compatible mode and -E
means extended regular expression mode - you need to pick oneâ steeldriver
Oct 4 at 13:56
-P
means perl compatible mode and -E
means extended regular expression mode - you need to pick oneâ steeldriver
Oct 4 at 13:56
@steeldriver thanks a lot! I probably should have read the man page a bit more carefully. Can you post that as an answer?
â MadClown
Oct 4 at 14:11
@steeldriver thanks a lot! I probably should have read the man page a bit more carefully. Can you post that as an answer?
â MadClown
Oct 4 at 14:11
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
MadClown is a new contributor. Be nice, and check out our Code of Conduct.
MadClown is a new contributor. Be nice, and check out our Code of Conduct.
MadClown is a new contributor. Be nice, and check out our Code of Conduct.
MadClown is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f473240%2fgrep-conflicting-matchers-specified%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
-P
means perl compatible mode and-E
means extended regular expression mode - you need to pick oneâ steeldriver
Oct 4 at 13:56
@steeldriver thanks a lot! I probably should have read the man page a bit more carefully. Can you post that as an answer?
â MadClown
Oct 4 at 14:11