Clojurians Log v2

recent intellij release keeps freezing for me, so i also had to run killall java a couple of times recently, to get rid of the orphaned nrepl servers...

Yeah that’s why I like the separate Terminal process, and the remote nREPL connect. Otherwise, it works exactly the same for my purposes.

Of all macOS apps, http://Terminal.app has to be the most reliable 🙂. I don’t think it has crashed even once in… decades, haha. Must be some good-ol’ code.

i've seen some utube tech video or short criticizing ppl who are using http://Terminal.app, assuming they are uninterested in making their workflow more effective or something. i've used iTerm2 for quite awhile, until i've realized how much more memory does it consume, compared to the http://Terminal.app, so i've dropped it. 1 less app to install, update, configure on a dev workstation. i do have wezterm and ghostty at hand of course to test out more modern tui apps in truecolor and whatnot, but that's the exception. otherwise i use intellij's built-in terminal, because i very rarely need the shell. i can do most of my work from clojure REPLs. as a side-note, it's super annoying that basic things might not work when someone ssh from macOS to an ubuntu / debian / rpi or even nixos. last time ncdu was showing me garbled output when i've ssh'd from latest macOS to latest Debian trixie... im still seeing LC_LOCALE complaints from debian after decades. 😵‍💫

> criticizing ppl who are using http://Terminal.app Haha yeah… For me it works, I have other apps that help with workflow globally across the whole macOS (like BetterTouchTool)

It can do all sorts of fancy stuff, from window management to full-blown scripting/automation across the OS.

as a side-note, it’s super annoying that basic things might not work when someone ssh from macOS to an ubuntu / debian / rpi or even nixos. last time ncdu was showing me garbled output when i’ve ssh’d from latest macOS to latest Debian trixie...

I tried Ghostty and it didn’t have a basic search feature via UI; so it didn’t make the cut for me.

i.e. Cmd+F I think did nothing

I typically start the REPL on my own and then connect to it, but perhaps try adding a .nrepl-port file in the project root directory with just the port written in the file like 9876

The .nrepl-port file is not Cursive specific, it’s determined by nREPL. Assuming the Cursive nREPL uses the defaults, it might work.

Actually… I am not sure if nREPL overwrites that file…

Probably this https://nrepl.org/nrepl/usage/server.html#server-configuration

• Local configuration file .nrepl.edn

an example of a local config file: .nrepl.edn

{:bind         "localhost"
 :port         12345
 :ack          23456
 :handler      some.ns/awesome-handler
 :transport    nrepl.transport/bencode}

Seemed to work

hey, thank you, @raspasov! :)

No prob!

After all those years I still start my projects in the Terminal and connect to them from Cursive. It feels more… reliable?

I guess I just force quit IntelliJ and my Java process is still up haha… But it’s hidden out of sight lol

Once in a while IntelliJ would freeze/crash, and having the Clojure/JVM process in a separate Terminal (outside of IntelliJ) feels better to me.

Not that it matters that much for local dev.