Why does the .*(text|Text).* regular expression return results that do not match in zypper?
As part of a zypper search pattern to limit searches to results such as those below, the command returns outputs results that do not match the expression.
Sample search set
Text-Based WWW Browser
A Text-Based WWW Browser
Text browser
A text-based WWW browser
Browser text
The search pattern is zypper search '/.*(text|Text).*/'.
The output of the search however includes the following in addition to the sample above.
Administration of MySQL over the web
A small, easy to use editor
Simple Presentation Tool for Excellent Presentation
The regular expression was tested at https://regex101.com/r/O6KohE/1/ and it only limits the matches to the sample set which is the expected behavior.
Based on the resource (https://en.opensuse.org/User:Tsu2/Regular_Expressions) my understanding is that the expression is first operated on by the shell and subsequently passed to the command.
If the command grep -E file.txt is executed, it returns the following results.
Text-Based WWW Browser
A Text-Based WWW Browser
Text browser
A text-based WWW browser
Browser text
Why does the regular expression match unintended strings when running the zypper search '/.*(text|Text).*/'command?
regular-expression zypper
asked 37 mins ago
MotivatedMotivated
2027
add a comment |
As part of a zypper search pattern to limit searches to results such as those below, the command returns outputs results that do not match the expression.
Sample search set
Text-Based WWW Browser
A Text-Based WWW Browser
Text browser
A text-based WWW browser
Browser text
The search pattern is zypper search '/.*(text|Text).*/'.
The output of the search however includes the following in addition to the sample above.
Administration of MySQL over the web
A small, easy to use editor
Simple Presentation Tool for Excellent Presentation
The regular expression was tested at https://regex101.com/r/O6KohE/1/ and it only limits the matches to the sample set which is the expected behavior.
Based on the resource (https://en.opensuse.org/User:Tsu2/Regular_Expressions) my understanding is that the expression is first operated on by the shell and subsequently passed to the command.
If the command grep -E file.txt is executed, it returns the following results.
Text-Based WWW Browser
A Text-Based WWW Browser
Text browser
A text-based WWW browser
Browser text
Why does the regular expression match unintended strings when running the zypper search '/.*(text|Text).*/'command?
regular-expression zypper
asked 37 mins ago
MotivatedMotivated
2027
My understanding is that the expression is first operated on by the shell…I don't know zypper, but I think that seems unlikely. How would the shell know what to do with the pattern before sending it to the command? Also, shells don't tend to substitute strings in single quotes. This looks like it's some issue with zypper itself.
– Sparhawk
6 mins ago
@Sparhawk - I am basing my understanding on (en.opensuse.org/User:Tsu2/Regular_Expressions)
– Motivated
3 mins ago
add a comment |
As part of a zypper search pattern to limit searches to results such as those below, the command returns outputs results that do not match the expression.
Sample search set
Text-Based WWW Browser
A Text-Based WWW Browser
Text browser
A text-based WWW browser
Browser text
The search pattern is zypper search '/.*(text|Text).*/'.
The output of the search however includes the following in addition to the sample above.
Administration of MySQL over the web
A small, easy to use editor
Simple Presentation Tool for Excellent Presentation
The regular expression was tested at https://regex101.com/r/O6KohE/1/ and it only limits the matches to the sample set which is the expected behavior.
Based on the resource (https://en.opensuse.org/User:Tsu2/Regular_Expressions) my understanding is that the expression is first operated on by the shell and subsequently passed to the command.
If the command grep -E file.txt is executed, it returns the following results.
Text-Based WWW Browser
A Text-Based WWW Browser
Text browser
A text-based WWW browser
Browser text
Why does the regular expression match unintended strings when running the zypper search '/.*(text|Text).*/'command?
regular-expression zypper
asked 37 mins ago
MotivatedMotivated
2027
As part of a zypper search pattern to limit searches to results such as those below, the command returns outputs results that do not match the expression.
Sample search set
Text-Based WWW Browser
A Text-Based WWW Browser
Text browser
A text-based WWW browser
Browser text
The search pattern is zypper search '/.*(text|Text).*/'.
The output of the search however includes the following in addition to the sample above.
Administration of MySQL over the web
A small, easy to use editor
Simple Presentation Tool for Excellent Presentation
The regular expression was tested at https://regex101.com/r/O6KohE/1/ and it only limits the matches to the sample set which is the expected behavior.
Based on the resource (https://en.opensuse.org/User:Tsu2/Regular_Expressions) my understanding is that the expression is first operated on by the shell and subsequently passed to the command.
If the command grep -E file.txt is executed, it returns the following results.
Text-Based WWW Browser
A Text-Based WWW Browser
Text browser
A text-based WWW browser
Browser text
Why does the regular expression match unintended strings when running the zypper search '/.*(text|Text).*/'command?
regular-expression zypper
regular-expression zypper
asked 37 mins ago
MotivatedMotivated
2027
asked 37 mins ago
MotivatedMotivated
2027
edited 1 min ago
Motivated
asked 37 mins ago
MotivatedMotivated
2027
asked 37 mins ago
MotivatedMotivated
2027
asked 37 mins ago
MotivatedMotivated
2027
2027
My understanding is that the expression is first operated on by the shell…I don't know zypper, but I think that seems unlikely. How would the shell know what to do with the pattern before sending it to the command? Also, shells don't tend to substitute strings in single quotes. This looks like it's some issue with zypper itself.
– Sparhawk
6 mins ago
@Sparhawk - I am basing my understanding on (en.opensuse.org/User:Tsu2/Regular_Expressions)
– Motivated
3 mins ago
add a comment |
My understanding is that the expression is first operated on by the shell…I don't know zypper, but I think that seems unlikely. How would the shell know what to do with the pattern before sending it to the command? Also, shells don't tend to substitute strings in single quotes. This looks like it's some issue with zypper itself.
– Sparhawk
6 mins ago
@Sparhawk - I am basing my understanding on (en.opensuse.org/User:Tsu2/Regular_Expressions)
– Motivated
3 mins ago
My understanding is that the expression is first operated on by the shell… I don't know zypper, but I think that seems unlikely. How would the shell know what to do with the pattern before sending it to the command? Also, shells don't tend to substitute strings in single quotes. This looks like it's some issue with zypper itself.– Sparhawk
6 mins ago
My understanding is that the expression is first operated on by the shell… I don't know zypper, but I think that seems unlikely. How would the shell know what to do with the pattern before sending it to the command? Also, shells don't tend to substitute strings in single quotes. This looks like it's some issue with zypper itself.– Sparhawk
6 mins ago
@Sparhawk - I am basing my understanding on (en.opensuse.org/User:Tsu2/Regular_Expressions)
– Motivated
3 mins ago
@Sparhawk - I am basing my understanding on (en.opensuse.org/User:Tsu2/Regular_Expressions)
– Motivated
3 mins ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f496808%2fwhy-does-the-texttext-regular-expression-return-results-that-do-not-match%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f496808%2fwhy-does-the-texttext-regular-expression-return-results-that-do-not-match%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
My understanding is that the expression is first operated on by the shell…I don't know zypper, but I think that seems unlikely. How would the shell know what to do with the pattern before sending it to the command? Also, shells don't tend to substitute strings in single quotes. This looks like it's some issue with zypper itself.– Sparhawk
6 mins ago
@Sparhawk - I am basing my understanding on (en.opensuse.org/User:Tsu2/Regular_Expressions)
– Motivated
3 mins ago