Listing content from two directories with wildcard












0














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?










share|improve this question







New contributor




Daniel H is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1




    try ... ls /bin/?*e*? /usr/bin/?*e*?
    – JJoao
    21 mins ago










  • Oh sure your version works I forgot that the wildcard specifies a relative path. Thank you!
    – Daniel H
    19 mins ago
















0














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?










share|improve this question







New contributor




Daniel H is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1




    try ... ls /bin/?*e*? /usr/bin/?*e*?
    – JJoao
    21 mins ago










  • Oh sure your version works I forgot that the wildcard specifies a relative path. Thank you!
    – Daniel H
    19 mins ago














0












0








0







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?










share|improve this question







New contributor




Daniel H is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











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?







shell ls wildcards






share|improve this question







New contributor




Daniel H is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Daniel H is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Daniel H is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 28 mins ago









Daniel HDaniel H

1




1




New contributor




Daniel H is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Daniel H is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Daniel H is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1




    try ... ls /bin/?*e*? /usr/bin/?*e*?
    – JJoao
    21 mins ago










  • Oh sure your version works I forgot that the wildcard specifies a relative path. Thank you!
    – Daniel H
    19 mins ago














  • 1




    try ... ls /bin/?*e*? /usr/bin/?*e*?
    – JJoao
    21 mins ago










  • Oh sure your version works I forgot that the wildcard specifies a relative path. Thank you!
    – Daniel H
    19 mins ago








1




1




try ... ls /bin/?*e*? /usr/bin/?*e*?
– JJoao
21 mins ago




try ... ls /bin/?*e*? /usr/bin/?*e*?
– JJoao
21 mins ago












Oh sure your version works I forgot that the wildcard specifies a relative path. Thank you!
– Daniel H
19 mins ago




Oh sure your version works I forgot that the wildcard specifies a relative path. Thank you!
– Daniel H
19 mins ago










1 Answer
1






active

oldest

votes


















0














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:





  1. /usr/bin/[^e]*e*[^e] and

  2. /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).






share|improve this answer























  • 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
    8 mins ago












  • I see you have ! instead of ^ as I used; are you using bash?
    – Jeff Schaller
    2 mins ago











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
});


}
});






Daniel H is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















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









0














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:





  1. /usr/bin/[^e]*e*[^e] and

  2. /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).






share|improve this answer























  • 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
    8 mins ago












  • I see you have ! instead of ^ as I used; are you using bash?
    – Jeff Schaller
    2 mins ago
















0














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:





  1. /usr/bin/[^e]*e*[^e] and

  2. /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).






share|improve this answer























  • 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
    8 mins ago












  • I see you have ! instead of ^ as I used; are you using bash?
    – Jeff Schaller
    2 mins ago














0












0








0






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:





  1. /usr/bin/[^e]*e*[^e] and

  2. /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).






share|improve this answer














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:





  1. /usr/bin/[^e]*e*[^e] and

  2. /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).







share|improve this answer














share|improve this answer



share|improve this answer








edited 2 mins ago

























answered 14 mins ago









Jeff SchallerJeff Schaller

39k1053125




39k1053125












  • 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
    8 mins ago












  • I see you have ! instead of ^ as I used; are you using bash?
    – Jeff Schaller
    2 mins ago


















  • 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
    8 mins ago












  • I see you have ! instead of ^ as I used; are you using bash?
    – Jeff Schaller
    2 mins ago
















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
8 mins ago






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
8 mins ago














I see you have ! instead of ^ as I used; are you using bash?
– Jeff Schaller
2 mins ago




I see you have ! instead of ^ as I used; are you using bash?
– Jeff Schaller
2 mins ago










Daniel H is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Daniel H is a new contributor. Be nice, and check out our Code of Conduct.













Daniel H is a new contributor. Be nice, and check out our Code of Conduct.












Daniel H is a new contributor. Be nice, and check out our Code of Conduct.
















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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














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





















































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







Popular posts from this blog

CARDNET

Boot-repair Failure: Unable to locate package grub-common:i386

濃尾地震