How can I do an “or” search with find? [duplicate]












2
















This question already has an answer here:




  • How to search with GNU find for several file types at a time?

    3 answers




Essentially, I want to know how to run 2 (or more) find commands in one - an "or" search rather than an "and":



find . -name "*.pem"

find . -name "*.crt"





find regular-expression







share|improve this question















marked as duplicate by Christopher, Jeff Schaller, Mr Shunz, Thomas, msp9011 Jan 25 at 10:55


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.



















  • Also: How to use find command to search for multiple extensions

    – ilkkachu
    Jan 24 at 22:18
















2
















This question already has an answer here:




  • How to search with GNU find for several file types at a time?

    3 answers




Essentially, I want to know how to run 2 (or more) find commands in one - an "or" search rather than an "and":



find . -name "*.pem"

find . -name "*.crt"





find regular-expression







share|improve this question















marked as duplicate by Christopher, Jeff Schaller, Mr Shunz, Thomas, msp9011 Jan 25 at 10:55


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.



















  • Also: How to use find command to search for multiple extensions

    – ilkkachu
    Jan 24 at 22:18














2












2








2









This question already has an answer here:




  • How to search with GNU find for several file types at a time?

    3 answers




Essentially, I want to know how to run 2 (or more) find commands in one - an "or" search rather than an "and":



find . -name "*.pem"

find . -name "*.crt"





find regular-expression







share|improve this question

















This question already has an answer here:




  • How to search with GNU find for several file types at a time?

    3 answers




Essentially, I want to know how to run 2 (or more) find commands in one - an "or" search rather than an "and":



find . -name "*.pem"

find . -name "*.crt"




This question already has an answer here:




  • How to search with GNU find for several file types at a time?

    3 answers







find regular-expression




find regular-expression






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 24 at 22:18









ilkkachu

60k997169




60k997169










asked Jan 24 at 14:02









BrowncoatOkieBrowncoatOkie

816




816




marked as duplicate by Christopher, Jeff Schaller, Mr Shunz, Thomas, msp9011 Jan 25 at 10:55


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.









marked as duplicate by Christopher, Jeff Schaller, Mr Shunz, Thomas, msp9011 Jan 25 at 10:55


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.















  • Also: How to use find command to search for multiple extensions

    – ilkkachu
    Jan 24 at 22:18



















  • Also: How to use find command to search for multiple extensions

    – ilkkachu
    Jan 24 at 22:18

















Also: How to use find command to search for multiple extensions

– ilkkachu
Jan 24 at 22:18





Also: How to use find command to search for multiple extensions

– ilkkachu
Jan 24 at 22:18










2 Answers
2






active

oldest

votes


















13














find’s “or” operator is -o:



find . -name "*.pem" -o -name "*.crt"


It is short-circuiting, i.e. the second part will only be evaluated if the first part is false: a file which matches *.pem won’t be tested against *.crt.



-o has lower precedence than “and”, whether explicit (-a) or implicit; if you’re combining operators you might need to wrap the “or” part with parentheses:



find . ( -name "*.pem" -o -name "*.crt" ) -print


In my tests this is significantly faster than using a regular expression, as you might expect (regular expressions are more expensive to test than globs, and -regex tests the full path, not only the file name as -name does).






share|improve this answer


























  • Even better. Simpler and easier to remember.

    – BrowncoatOkie
    Jan 24 at 14:16



















1














While I was typing up this question, it occurred to me that find uses globbing rather than regex by default. But I bet there's a way to use regex!



Sure enough...I had to change the regextype to use posix-extended but that got me what I wanted.



find . -regextype posix-extended -regex ".*pem|.*crt"


Qaplah!






share|improve this answer
























  • Run a couple of finds with time at the start to analyse whether you're faster using regex or wildcards. If you're searching over files might be worth using locate.

    – pbhj
    Jan 24 at 14:16






  • 3





    ".*pem|.*crt" finds a name that ends with pem or crt, not a file with those extensions. You'll need .*.pem|.*.crt for that. But using regex for this isn't a good method anyway

    – phuclv
    Jan 24 at 14:17






  • 3





    @phuclv Actually, since the expression is not anchored to the end of the pathname, it may match anywhere, even in a parent directory name. This is because -regex is applied to the whole pathname and because unanchored regular expressions may match anywhere in the given string.

    – Kusalananda
    Jan 24 at 14:49













  • Regular-expression matching is a non-standard extension provided by some, but not necessarily all, implementations of find.

    – chepner
    Jan 24 at 20:45











  • @TavianBarnes that has already been mentioned by Kusalananda above]

    – phuclv
    Jan 29 at 14:32


















2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









13














find’s “or” operator is -o:



find . -name "*.pem" -o -name "*.crt"


It is short-circuiting, i.e. the second part will only be evaluated if the first part is false: a file which matches *.pem won’t be tested against *.crt.



-o has lower precedence than “and”, whether explicit (-a) or implicit; if you’re combining operators you might need to wrap the “or” part with parentheses:



find . ( -name "*.pem" -o -name "*.crt" ) -print


In my tests this is significantly faster than using a regular expression, as you might expect (regular expressions are more expensive to test than globs, and -regex tests the full path, not only the file name as -name does).






share|improve this answer


























  • Even better. Simpler and easier to remember.

    – BrowncoatOkie
    Jan 24 at 14:16
















13














find’s “or” operator is -o:



find . -name "*.pem" -o -name "*.crt"


It is short-circuiting, i.e. the second part will only be evaluated if the first part is false: a file which matches *.pem won’t be tested against *.crt.



-o has lower precedence than “and”, whether explicit (-a) or implicit; if you’re combining operators you might need to wrap the “or” part with parentheses:



find . ( -name "*.pem" -o -name "*.crt" ) -print


In my tests this is significantly faster than using a regular expression, as you might expect (regular expressions are more expensive to test than globs, and -regex tests the full path, not only the file name as -name does).






share|improve this answer


























  • Even better. Simpler and easier to remember.

    – BrowncoatOkie
    Jan 24 at 14:16














13












13








13







find’s “or” operator is -o:



find . -name "*.pem" -o -name "*.crt"


It is short-circuiting, i.e. the second part will only be evaluated if the first part is false: a file which matches *.pem won’t be tested against *.crt.



-o has lower precedence than “and”, whether explicit (-a) or implicit; if you’re combining operators you might need to wrap the “or” part with parentheses:



find . ( -name "*.pem" -o -name "*.crt" ) -print


In my tests this is significantly faster than using a regular expression, as you might expect (regular expressions are more expensive to test than globs, and -regex tests the full path, not only the file name as -name does).






share|improve this answer















find’s “or” operator is -o:



find . -name "*.pem" -o -name "*.crt"


It is short-circuiting, i.e. the second part will only be evaluated if the first part is false: a file which matches *.pem won’t be tested against *.crt.



-o has lower precedence than “and”, whether explicit (-a) or implicit; if you’re combining operators you might need to wrap the “or” part with parentheses:



find . ( -name "*.pem" -o -name "*.crt" ) -print


In my tests this is significantly faster than using a regular expression, as you might expect (regular expressions are more expensive to test than globs, and -regex tests the full path, not only the file name as -name does).







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 24 at 15:12

























answered Jan 24 at 14:04









Stephen KittStephen Kitt

173k24396471




173k24396471













  • Even better. Simpler and easier to remember.

    – BrowncoatOkie
    Jan 24 at 14:16



















  • Even better. Simpler and easier to remember.

    – BrowncoatOkie
    Jan 24 at 14:16

















Even better. Simpler and easier to remember.

– BrowncoatOkie
Jan 24 at 14:16





Even better. Simpler and easier to remember.

– BrowncoatOkie
Jan 24 at 14:16













1














While I was typing up this question, it occurred to me that find uses globbing rather than regex by default. But I bet there's a way to use regex!



Sure enough...I had to change the regextype to use posix-extended but that got me what I wanted.



find . -regextype posix-extended -regex ".*pem|.*crt"


Qaplah!






share|improve this answer
























  • Run a couple of finds with time at the start to analyse whether you're faster using regex or wildcards. If you're searching over files might be worth using locate.

    – pbhj
    Jan 24 at 14:16






  • 3





    ".*pem|.*crt" finds a name that ends with pem or crt, not a file with those extensions. You'll need .*.pem|.*.crt for that. But using regex for this isn't a good method anyway

    – phuclv
    Jan 24 at 14:17






  • 3





    @phuclv Actually, since the expression is not anchored to the end of the pathname, it may match anywhere, even in a parent directory name. This is because -regex is applied to the whole pathname and because unanchored regular expressions may match anywhere in the given string.

    – Kusalananda
    Jan 24 at 14:49













  • Regular-expression matching is a non-standard extension provided by some, but not necessarily all, implementations of find.

    – chepner
    Jan 24 at 20:45











  • @TavianBarnes that has already been mentioned by Kusalananda above]

    – phuclv
    Jan 29 at 14:32
















1














While I was typing up this question, it occurred to me that find uses globbing rather than regex by default. But I bet there's a way to use regex!



Sure enough...I had to change the regextype to use posix-extended but that got me what I wanted.



find . -regextype posix-extended -regex ".*pem|.*crt"


Qaplah!






share|improve this answer
























  • Run a couple of finds with time at the start to analyse whether you're faster using regex or wildcards. If you're searching over files might be worth using locate.

    – pbhj
    Jan 24 at 14:16






  • 3





    ".*pem|.*crt" finds a name that ends with pem or crt, not a file with those extensions. You'll need .*.pem|.*.crt for that. But using regex for this isn't a good method anyway

    – phuclv
    Jan 24 at 14:17






  • 3





    @phuclv Actually, since the expression is not anchored to the end of the pathname, it may match anywhere, even in a parent directory name. This is because -regex is applied to the whole pathname and because unanchored regular expressions may match anywhere in the given string.

    – Kusalananda
    Jan 24 at 14:49













  • Regular-expression matching is a non-standard extension provided by some, but not necessarily all, implementations of find.

    – chepner
    Jan 24 at 20:45











  • @TavianBarnes that has already been mentioned by Kusalananda above]

    – phuclv
    Jan 29 at 14:32














1












1








1







While I was typing up this question, it occurred to me that find uses globbing rather than regex by default. But I bet there's a way to use regex!



Sure enough...I had to change the regextype to use posix-extended but that got me what I wanted.



find . -regextype posix-extended -regex ".*pem|.*crt"


Qaplah!






share|improve this answer













While I was typing up this question, it occurred to me that find uses globbing rather than regex by default. But I bet there's a way to use regex!



Sure enough...I had to change the regextype to use posix-extended but that got me what I wanted.



find . -regextype posix-extended -regex ".*pem|.*crt"


Qaplah!







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 24 at 14:02









BrowncoatOkieBrowncoatOkie

816




816













  • Run a couple of finds with time at the start to analyse whether you're faster using regex or wildcards. If you're searching over files might be worth using locate.

    – pbhj
    Jan 24 at 14:16






  • 3





    ".*pem|.*crt" finds a name that ends with pem or crt, not a file with those extensions. You'll need .*.pem|.*.crt for that. But using regex for this isn't a good method anyway

    – phuclv
    Jan 24 at 14:17






  • 3





    @phuclv Actually, since the expression is not anchored to the end of the pathname, it may match anywhere, even in a parent directory name. This is because -regex is applied to the whole pathname and because unanchored regular expressions may match anywhere in the given string.

    – Kusalananda
    Jan 24 at 14:49













  • Regular-expression matching is a non-standard extension provided by some, but not necessarily all, implementations of find.

    – chepner
    Jan 24 at 20:45











  • @TavianBarnes that has already been mentioned by Kusalananda above]

    – phuclv
    Jan 29 at 14:32



















  • Run a couple of finds with time at the start to analyse whether you're faster using regex or wildcards. If you're searching over files might be worth using locate.

    – pbhj
    Jan 24 at 14:16






  • 3





    ".*pem|.*crt" finds a name that ends with pem or crt, not a file with those extensions. You'll need .*.pem|.*.crt for that. But using regex for this isn't a good method anyway

    – phuclv
    Jan 24 at 14:17






  • 3





    @phuclv Actually, since the expression is not anchored to the end of the pathname, it may match anywhere, even in a parent directory name. This is because -regex is applied to the whole pathname and because unanchored regular expressions may match anywhere in the given string.

    – Kusalananda
    Jan 24 at 14:49













  • Regular-expression matching is a non-standard extension provided by some, but not necessarily all, implementations of find.

    – chepner
    Jan 24 at 20:45











  • @TavianBarnes that has already been mentioned by Kusalananda above]

    – phuclv
    Jan 29 at 14:32

















Run a couple of finds with time at the start to analyse whether you're faster using regex or wildcards. If you're searching over files might be worth using locate.

– pbhj
Jan 24 at 14:16





Run a couple of finds with time at the start to analyse whether you're faster using regex or wildcards. If you're searching over files might be worth using locate.

– pbhj
Jan 24 at 14:16




3




3





".*pem|.*crt" finds a name that ends with pem or crt, not a file with those extensions. You'll need .*.pem|.*.crt for that. But using regex for this isn't a good method anyway

– phuclv
Jan 24 at 14:17





".*pem|.*crt" finds a name that ends with pem or crt, not a file with those extensions. You'll need .*.pem|.*.crt for that. But using regex for this isn't a good method anyway

– phuclv
Jan 24 at 14:17




3




3





@phuclv Actually, since the expression is not anchored to the end of the pathname, it may match anywhere, even in a parent directory name. This is because -regex is applied to the whole pathname and because unanchored regular expressions may match anywhere in the given string.

– Kusalananda
Jan 24 at 14:49







@phuclv Actually, since the expression is not anchored to the end of the pathname, it may match anywhere, even in a parent directory name. This is because -regex is applied to the whole pathname and because unanchored regular expressions may match anywhere in the given string.

– Kusalananda
Jan 24 at 14:49















Regular-expression matching is a non-standard extension provided by some, but not necessarily all, implementations of find.

– chepner
Jan 24 at 20:45





Regular-expression matching is a non-standard extension provided by some, but not necessarily all, implementations of find.

– chepner
Jan 24 at 20:45













@TavianBarnes that has already been mentioned by Kusalananda above]

– phuclv
Jan 29 at 14:32





@TavianBarnes that has already been mentioned by Kusalananda above]

– phuclv
Jan 29 at 14:32



-

Popular posts from this blog

Human spaceflight

Image
Human spaceflight From Wikipedia, the free encyclopedia Jump to navigation Jump to search "Space traveler" redirects here. For other uses, see Space traveler (disambiguation). @media all and (max-width:720px){.mw-parser-output .tmulti>.thumbinner{width:100%!important;max-width:none!important}.mw-parser-output .tmulti .tsingle{float:none!important;max-width:none!important;width:100%!important;text-align:center}} Apollo 11 crewmember Buzz Aldrin on the Moon, 1969 International Space Station crewmember Tracy Caldwell Dyson views the Earth, 2010 Space Shuttle Discovery heads into space with a crew aboard, STS-121 in 2006 Inside a space suit on the Canadarm, 1993 Human spaceflight (also referred to as crewed spaceflight or manned spaceflight ) is space travel with a crew or passengers aboard the spacecraft. Spacecraft carrying people may be operated directly, by human crew, or it may be e
Read more

Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

Image
0 1 What exactly does the error message beginning with E: mean? I assume it has to do with the file structure on Ubuntu-on-Windows, but what exactly? The following package was automatically installed and is no longer required: os-prober Use 'apt-get autoremove' to remove it. The following extra packages will be installed: libxslt1.1 The following NEW packages will be installed: libxslt1.1 xmlstarlet 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 435 kB of archives. After this operation, 1023 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu/ trusty/main libxslt1.1 amd64 1.1.28-2build1 [145 kB] Get:2 http://archive.ubuntu.com/ubuntu/ trusty/universe xmlstarlet amd64 1.5.0-1 [290 kB]
Read more

File:DeusFollowingSea.jpg

Image
File:DeusFollowingSea.jpg From Wikipedia, the free encyclopedia Jump to navigation Jump to search File File history File usage No higher resolution available. DeusFollowingSea.jpg ‎ (238 × 211 pixels, file size: 12 KB, MIME type: image/jpeg ) Summary [ edit ] Media data and Non-free use rationale Description Cover art of the Deus CD Following Sea Author or copyright owner Deus Source (WP:NFCC#4) rocksucker.co.uk Date of publication 2012 Use in article (WP:NFCC#7) Following Sea Purpose of use in article (WP:NFCC#8) to serve as the primary means of visual identification at the top of the article dedicated to the work in question. Not replaceable with free media because (WP:NFCC#1) n.a. Minimal use (WP:NFCC#3) Low res image used in infobox of the article on the album Respect for commercial opportunities (WP:NFCC#2) n.a. Fair use Fair use of co
Read more