This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-27
Channels
- # adventofcode (7)
- # announcements (31)
- # babashka (15)
- # beginners (14)
- # calva (45)
- # circleci (6)
- # clojure (27)
- # clojure-europe (19)
- # clojure-france (2)
- # clojure-gamedev (4)
- # clojure-uk (2)
- # clojurescript (26)
- # conjure (14)
- # data-science (6)
- # deps-new (7)
- # depstar (4)
- # emacs (13)
- # events (1)
- # fulcro (20)
- # graalvm (2)
- # hoplon (30)
- # joker (11)
- # london-clojurians (1)
- # malli (26)
- # pathom (2)
- # re-frame (13)
- # reagent (8)
- # reclojure (3)
- # reveal (8)
- # robots (4)
- # shadow-cljs (29)
- # sql (5)
- # tools-deps (28)
- # vim (4)
isn't this what glob is for btw? (https://candid82.github.io/joker/joker.filepath.html#glob)
Ah, maybe that would be sufficient! file-seq
also returns info on each entry.
glob
does not appear to be recursive per se, though it does support e.g. **
and variations.
But it might be suitable if all one needs is a limited amount of depth and no information on the info (such as type) for each entry.
Why would you use if it isn't recursive? With recursive I mean, it descends into subdirs
Ah, in Bash, one must apparently set globstar
to get the behavior we're expecting:
https://unix.stackexchange.com/questions/49913/recursive-glob
Go stdlib doesn't have out-of-the-box support for it, based on this discussion: https://stackoverflow.com/questions/26809484/how-to-use-double-star-glob-in-go