Clash Royale CLAN TAG#URR8PPP
I have a task to list all files from /bin and /usr/bin that contain an e that is neither at the beginning nor at the end.
The wildcard is [!e]*e*[!e] and works.
(Tested commands cd /bin & ls -l [!e]*e*[!e]
The problem is I have to print the contents of both directories using this wildcard in one command. How do I do that?
|
show 1 more comment
I have a task to list all files from /bin and /usr/bin that contain an e that is neither at the beginning nor at the end.
The wildcard is [!e]*e*[!e] and works.
(Tested commands cd /bin & ls -l [!e]*e*[!e]
The problem is I have to print the contents of both directories using this wildcard in one command. How do I do that?
-
1
try …
ls /bin/?*e*? /usr/bin/?*e*?– JJoao
Jan 7 at 16:52 -
Oh sure your version works I forgot that the wildcard specifies a relative path. Thank you!
– Daniel H
Jan 7 at 16:54 -
/bin/egrepcontains aethat is neither at the beginning nor end, should it be matched? Your wildcard doesn’t match it.– Stéphane Chazelas
Jan 7 at 17:35 -
I might be pendantic and ask if “an” e means exactly one e or allows for more than one?
– Jeff Schaller
Jan 7 at 17:48 -
@StéphaneChazelas No. The filename must not begin with an
e– Daniel H
Jan 7 at 18:11
|
show 1 more comment
I have a task to list all files from /bin and /usr/bin that contain an e that is neither at the beginning nor at the end.
The wildcard is [!e]*e*[!e] and works.
(Tested commands cd /bin & ls -l [!e]*e*[!e]
The problem is I have to print the contents of both directories using this wildcard in one command. How do I do that?
I have a task to list all files from /bin and /usr/bin that contain an e that is neither at the beginning nor at the end.
The wildcard is [!e]*e*[!e] and works.
(Tested commands cd /bin & ls -l [!e]*e*[!e]
The problem is I have to print the contents of both directories using this wildcard in one command. How do I do that?
-
1
try …
ls /bin/?*e*? /usr/bin/?*e*?– JJoao
Jan 7 at 16:52 -
Oh sure your version works I forgot that the wildcard specifies a relative path. Thank you!
– Daniel H
Jan 7 at 16:54 -
/bin/egrepcontains aethat is neither at the beginning nor end, should it be matched? Your wildcard doesn’t match it.– Stéphane Chazelas
Jan 7 at 17:35 -
I might be pendantic and ask if “an” e means exactly one e or allows for more than one?
– Jeff Schaller
Jan 7 at 17:48 -
@StéphaneChazelas No. The filename must not begin with an
e– Daniel H
Jan 7 at 18:11
|
show 1 more comment
-
1
try …
ls /bin/?*e*? /usr/bin/?*e*?– JJoao
Jan 7 at 16:52 -
Oh sure your version works I forgot that the wildcard specifies a relative path. Thank you!
– Daniel H
Jan 7 at 16:54 -
/bin/egrepcontains aethat is neither at the beginning nor end, should it be matched? Your wildcard doesn’t match it.– Stéphane Chazelas
Jan 7 at 17:35 -
I might be pendantic and ask if “an” e means exactly one e or allows for more than one?
– Jeff Schaller
Jan 7 at 17:48 -
@StéphaneChazelas No. The filename must not begin with an
e– Daniel H
Jan 7 at 18:11
try … ls /bin/?*e*? /usr/bin/?*e*?
– JJoao
Jan 7 at 16:52
try … ls /bin/?*e*? /usr/bin/?*e*?
– JJoao
Jan 7 at 16:52
Oh sure your version works I forgot that the wildcard specifies a relative path. Thank you!
– Daniel H
Jan 7 at 16:54
Oh sure your version works I forgot that the wildcard specifies a relative path. Thank you!
– Daniel H
Jan 7 at 16:54
/bin/egrep contains a e that is neither at the beginning nor end, should it be matched? Your wildcard doesn’t match it.
– Stéphane Chazelas
Jan 7 at 17:35
/bin/egrep contains a e that is neither at the beginning nor end, should it be matched? Your wildcard doesn’t match it.
– Stéphane Chazelas
Jan 7 at 17:35
I might be pendantic and ask if “an” e means exactly one e or allows for more than one?
– Jeff Schaller
Jan 7 at 17:48
I might be pendantic and ask if “an” e means exactly one e or allows for more than one?
– Jeff Schaller
Jan 7 at 17:48
@StéphaneChazelas No. The filename must not begin with an e
– Daniel H
Jan 7 at 18:11
@StéphaneChazelas No. The filename must not begin with an e
– Daniel H
Jan 7 at 18:11
|
show 1 more comment
1 Answer
1
active
oldest
votes
You could boil it down to one command and one (typed) argument:
ls -d {/usr,}/bin/[^e]*e*[^e]
I added -d in case there to be subdirectories matching the pattern. That expands in phases to:
-
/usr/bin/[^e]*e*[^e]and /bin/[^e]*e*[^e]
after expanding the braces.
The [^e] requires something other than an e, followed by * anything, followed by an e, followed by * anything, followed by another non-e (followed implicitly by nothing — indicating the end of the filename).
-
Looks very interesting but it says: ls: cannot access ‘/usr/bin/[!e]*e*[!e]’: No such file or directory & ls: cannot access ‘/bin/[!e]*e*[!e]’: No such file or directory
– Daniel H
Jan 7 at 17:05
-
I see you have
!instead of^as I used; are you using bash?– Jeff Schaller
Jan 7 at 17:11 -
!is correct in globbing patterns. The pattern would remain unexpanded if it doesn’t match anything.– Kusalananda
Jan 7 at 17:25 -
@JeffSchaller I did try ^ instead of ! but it keeps print the same error. And yes, I use the bash.
– Daniel H
Jan 7 at 18:00
-
It would seem to me that you simply don’t have any of those files, then. Does that seem right?
– Jeff Schaller
Jan 7 at 18:13
add a comment |
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’);
});
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f493034%2flisting-content-from-two-directories-with-wildcard%23new-answer’, ‘question_page’);
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You could boil it down to one command and one (typed) argument:
ls -d {/usr,}/bin/[^e]*e*[^e]
I added -d in case there to be subdirectories matching the pattern. That expands in phases to:
-
/usr/bin/[^e]*e*[^e]and /bin/[^e]*e*[^e]
after expanding the braces.
The [^e] requires something other than an e, followed by * anything, followed by an e, followed by * anything, followed by another non-e (followed implicitly by nothing — indicating the end of the filename).
-
Looks very interesting but it says: ls: cannot access ‘/usr/bin/[!e]*e*[!e]’: No such file or directory & ls: cannot access ‘/bin/[!e]*e*[!e]’: No such file or directory
– Daniel H
Jan 7 at 17:05
-
I see you have
!instead of^as I used; are you using bash?– Jeff Schaller
Jan 7 at 17:11 -
!is correct in globbing patterns. The pattern would remain unexpanded if it doesn’t match anything.– Kusalananda
Jan 7 at 17:25 -
@JeffSchaller I did try ^ instead of ! but it keeps print the same error. And yes, I use the bash.
– Daniel H
Jan 7 at 18:00
-
It would seem to me that you simply don’t have any of those files, then. Does that seem right?
– Jeff Schaller
Jan 7 at 18:13
add a comment |
You could boil it down to one command and one (typed) argument:
ls -d {/usr,}/bin/[^e]*e*[^e]
I added -d in case there to be subdirectories matching the pattern. That expands in phases to:
-
/usr/bin/[^e]*e*[^e]and /bin/[^e]*e*[^e]
after expanding the braces.
The [^e] requires something other than an e, followed by * anything, followed by an e, followed by * anything, followed by another non-e (followed implicitly by nothing — indicating the end of the filename).
-
Looks very interesting but it says: ls: cannot access ‘/usr/bin/[!e]*e*[!e]’: No such file or directory & ls: cannot access ‘/bin/[!e]*e*[!e]’: No such file or directory
– Daniel H
Jan 7 at 17:05
-
I see you have
!instead of^as I used; are you using bash?– Jeff Schaller
Jan 7 at 17:11 -
!is correct in globbing patterns. The pattern would remain unexpanded if it doesn’t match anything.– Kusalananda
Jan 7 at 17:25 -
@JeffSchaller I did try ^ instead of ! but it keeps print the same error. And yes, I use the bash.
– Daniel H
Jan 7 at 18:00
-
It would seem to me that you simply don’t have any of those files, then. Does that seem right?
– Jeff Schaller
Jan 7 at 18:13
add a comment |
You could boil it down to one command and one (typed) argument:
ls -d {/usr,}/bin/[^e]*e*[^e]
I added -d in case there to be subdirectories matching the pattern. That expands in phases to:
-
/usr/bin/[^e]*e*[^e]and /bin/[^e]*e*[^e]
after expanding the braces.
The [^e] requires something other than an e, followed by * anything, followed by an e, followed by * anything, followed by another non-e (followed implicitly by nothing — indicating the end of the filename).
You could boil it down to one command and one (typed) argument:
ls -d {/usr,}/bin/[^e]*e*[^e]
I added -d in case there to be subdirectories matching the pattern. That expands in phases to:
-
/usr/bin/[^e]*e*[^e]and /bin/[^e]*e*[^e]
after expanding the braces.
The [^e] requires something other than an e, followed by * anything, followed by an e, followed by * anything, followed by another non-e (followed implicitly by nothing — indicating the end of the filename).
-
Looks very interesting but it says: ls: cannot access ‘/usr/bin/[!e]*e*[!e]’: No such file or directory & ls: cannot access ‘/bin/[!e]*e*[!e]’: No such file or directory
– Daniel H
Jan 7 at 17:05
-
I see you have
!instead of^as I used; are you using bash?– Jeff Schaller
Jan 7 at 17:11 -
!is correct in globbing patterns. The pattern would remain unexpanded if it doesn’t match anything.– Kusalananda
Jan 7 at 17:25 -
@JeffSchaller I did try ^ instead of ! but it keeps print the same error. And yes, I use the bash.
– Daniel H
Jan 7 at 18:00
-
It would seem to me that you simply don’t have any of those files, then. Does that seem right?
– Jeff Schaller
Jan 7 at 18:13
add a comment |
-
Looks very interesting but it says: ls: cannot access ‘/usr/bin/[!e]*e*[!e]’: No such file or directory & ls: cannot access ‘/bin/[!e]*e*[!e]’: No such file or directory
– Daniel H
Jan 7 at 17:05
-
I see you have
!instead of^as I used; are you using bash?– Jeff Schaller
Jan 7 at 17:11 -
!is correct in globbing patterns. The pattern would remain unexpanded if it doesn’t match anything.– Kusalananda
Jan 7 at 17:25 -
@JeffSchaller I did try ^ instead of ! but it keeps print the same error. And yes, I use the bash.
– Daniel H
Jan 7 at 18:00
-
It would seem to me that you simply don’t have any of those files, then. Does that seem right?
– Jeff Schaller
Jan 7 at 18:13
Looks very interesting but it says: ls: cannot access ‘/usr/bin/[!e]*e*[!e]’: No such file or directory & ls: cannot access ‘/bin/[!e]*e*[!e]’: No such file or directory
– Daniel H
Jan 7 at 17:05
Looks very interesting but it says: ls: cannot access ‘/usr/bin/[!e]*e*[!e]’: No such file or directory & ls: cannot access ‘/bin/[!e]*e*[!e]’: No such file or directory
– Daniel H
Jan 7 at 17:05
I see you have ! instead of ^ as I used; are you using bash?
– Jeff Schaller
Jan 7 at 17:11
I see you have ! instead of ^ as I used; are you using bash?
– Jeff Schaller
Jan 7 at 17:11
! is correct in globbing patterns. The pattern would remain unexpanded if it doesn’t match anything.
– Kusalananda
Jan 7 at 17:25
! is correct in globbing patterns. The pattern would remain unexpanded if it doesn’t match anything.
– Kusalananda
Jan 7 at 17:25
@JeffSchaller I did try ^ instead of ! but it keeps print the same error. And yes, I use the bash.
– Daniel H
Jan 7 at 18:00
@JeffSchaller I did try ^ instead of ! but it keeps print the same error. And yes, I use the bash.
– Daniel H
Jan 7 at 18:00
It would seem to me that you simply don’t have any of those files, then. Does that seem right?
– Jeff Schaller
Jan 7 at 18:13
It would seem to me that you simply don’t have any of those files, then. Does that seem right?
– Jeff Schaller
Jan 7 at 18:13
add a comment |
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’);
});
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f493034%2flisting-content-from-two-directories-with-wildcard%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’);
});
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave(‘#login-link’);
});
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave(‘#login-link’);
});
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
try …
ls /bin/?*e*? /usr/bin/?*e*?– JJoao
Jan 7 at 16:52
Oh sure your version works I forgot that the wildcard specifies a relative path. Thank you!
– Daniel H
Jan 7 at 16:54
/bin/egrepcontains aethat is neither at the beginning nor end, should it be matched? Your wildcard doesn’t match it.– Stéphane Chazelas
Jan 7 at 17:35
I might be pendantic and ask if “an” e means exactly one e or allows for more than one?
– Jeff Schaller
Jan 7 at 17:48
@StéphaneChazelas No. The filename must not begin with an
e– Daniel H
Jan 7 at 18:11