Does babashka.fs/parent do what you want? https://github.com/babashka/fs/blob/master/API.md#babashka.fs/parent

Ahaaa, yeah! It looks like it. I missed that because I didn't think to look for the word "parent" in the docs 😅

I'm quickly learning that one of my greatest weaknesses is not knowing what to search for and how to best navigate docs 😅

babashka.fs/parent was exactly what I needed 🙂

> I'm quickly learning that one of my greatest weaknesses is not knowing what to search for and how to best navigate docs 😅 > Not sure if I agree! I mostly know these things because Borkdude has been helping me out with stupid questions. Some things are hard to learn on one's own! I think asking "how would you ... ?" and "can I get feedback on this code?" questions is a great way to learn :)

I also think it's fair to just work with strings when you don't know the specific functions that could solve the task with less code. See for instance this thing I wrote: https://github.com/teodorlu/play.teod.eu/blob/42e9d3edc9dfe6958c2c87cbc2bde73d6c9f97fb/play.clj#L55 At that time, I wasn't familiar with babashka fs at all!

Also as a side note, I’d recommend against the use of pmap pretty much everywhere, specially if you’re seeing the need to use a doall after it. pmap though is easy doesn’t really add much value and is almost always not a good choice when using with side effects.

This particular code the overhead from managing the threads and the laziness would probably defeat the gains that you’re looking for 🙂

Referring to the find-repos example from @U01PE7630AC

Thanks for the advice, @U7ERLH6JX! When I use map it doesn't process the whole collection, so I had to use run! or doseq or pmap + doall. What would be the best approach in this scenario?

The problem with pmap is that it’s lazy and has chunking too like map. If you wanna do things in parallel and not care about laziness pmap is okay hence ruling out side effects. This thread should help: https://clojurians.slack.com/archives/C03S1KBA2/p1678968328528409

bb supports the nice executor framework that the JDK has and it’s a bit more involved but simpler solution. Also works nicely with the snappy virtual threads 😄

I’m starting bb with

❯ bb --socket-repl 5000
Babashka socket REPL started at 127.0.0.1:5000
Babashka v1.3.176 REPL.
Use :repl/quit or :repl/exit to quit the REPL.
Clojure rocks, Bash reaches.

user=>

❯ netcat localhost 5000
Babashka v1.3.176 REPL.
Use :repl/quit or :repl/exit to quit the REPL.
Clojure rocks, Bash reaches.

user=>

so far so good, right?

if i connect with inf-clojure on localhost 5000, i’m never seeing any output like a repl prompt. If i send stuff over localhost i see

(+ 1 1)

RTSP/1.0 403 Forbidden
Content-Length: 0
Server: AirTunes/675.4.1

but if i connect on 127.0.0.1 everything seems to work fine

does this ring a bell?

it seems like another server is running on that port maybe?

well the netcat seems to find the bb socket server

but it connects to 127.0.0.1, perhaps "localhost" does something slightly different, not sure

is something weird in your /etc/hosts maybe?

perhaps try a different port like 11223344

huh. yeah that seems to have worked

bizarre. i guess something else is on port 5000? can they be multiplexed?

sudo lsof -i :5000 on mac

COMMAND    PID     USER   FD   TYPE            DEVICE SIZE/OFF NODE NAME
ControlCe 2829 borkdude   21u  IPv4 0x7e0ffdd84f48315      0t0  TCP *:commplex-main (LISTEN)
ControlCe 2829 borkdude   22u  IPv6 0x7e0ffe24fd6c5cd      0t0  TCP *:commplex-main (LISTEN)

seems mac is running something on there

yeah i have similar. weird that it works for netcat

https://developer.apple.com/forums/thread/682332

does netcat localhost also work, instead of 127.0.0.1 then?

netcat always sees bb on port 5000

but emacs seems to see the airplay service

bizarre

yeah, dunno :)

well thanks for the help as always @U04V15CAJ

This is due to buffering. But there's already a stream by default with process/process and you can just read from that manually

You can also use {:out :inherit} if you don't actually want to capture it, but see it as it's written

The shell function does this by default

by default, :inherit goes to stdout of where my REPL was launched (which is a terminal window). can I get the same behavior as :inherit but for my REPL connection?